panic: unlocking unlocked wait/wound mutex
Hi All, Does anyone know a remedy to this? The relevant part of the dmesg is as follows: [ 10,368692] wsdisplay0: screen 1 added (default, vt100 emulation) [ 10,368692] wsdisplay0: screen 2 added (default, vt100 emulation) [ 10,368692] wsdisplay0: screen 3 added (default, vt100 emulation) [ 10,368692] wsdisplay0: screen 4 added (default, vt100 emulation) [ 46,942227] panic: unlocking unlocked wait/wound mutex: 0x858023c90920 [ 46,942227] cpu0: Begin traceback... [ 46,942227] vpanic() at netbsd:vpanic+0x183 [ 46,942227] panic() at netbsd:panic+0x3c [ 46,942227] linux_ww_mutex_unlock() at netbsd:linux_ww_mutex_unlock+0x9e [ 46,942227] ttm_bo_release() at netbsd:ttm_bo_release+0xf3 [ 46,942227] amdgpu_bo_unref() at netbsd:amdgpu_bo_unref+0x1d [ 46,942227] amdgpu_vm_free_table() at netbsd:amdgpu_vm_free_table+0x53 [ 46,942227] amdgpu_vm_free_pts() at netbsd:amdgpu_vm_free_pts+0xeb [ 46,942227] amdgpu_vm_fini() at netbsd:amdgpu_vm_fini+0x270 [ 46,942227] amdgpu_driver_postclose_kms() at netbsd:amdgpu_driver_postclose_kms+0x101 [ 46,942227] drm_file_free() at netbsd:drm_file_free+0x1fb [ 46,942227] drm_close() at netbsd:drm_close+0x60 [ 46,942227] closef() at netbsd:closef+0x58 [ 46,942227] fd_close() at netbsd:fd_close+0x140 [ 46,942227] sys_close() at netbsd:sys_close+0x22 [ 46,942227] syscall() at netbsd:syscall+0x1fc [ 46,942227] --- syscall (number 6) --- [ 46,942227] netbsd:syscall+0x1fc: [ 46,942227] cpu0: End traceback... Thanks for any hint! Best regards, r0ller
starting X on AMD R9 Nano crashes system
x: 40 data: 117901057[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 41 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 42 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 43 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 44 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 45 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 46 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 47 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 49 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 50 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 51 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 53 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:read_indirect_azalia_reg: index: 56 data: 1[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 56 data: 1[ 3,322711] [HW_AUDIO]:AUDIO:read_indirect_azalia_reg: index: 55 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 55 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:read_indirect_azalia_reg: index: 55 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 55 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 58 data: 91827532[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 59 data: 11[ 3,322711] [HW_AUDIO]:[ 3,322711] AUDIO:az_configure: index: 4 data, 0xb, displayName SyncMaster: [ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 60 data: 1431864734[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 61 data: 228103241[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 62 data: 1668184403[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 63 data: 1953718605[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 64 data: 29285[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 65 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 66 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:read_indirect_azalia_reg: index: 84 data: 17[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 84 data: 16[ 3,322711] [HW_AUDIO]:AUDIO:read_indirect_azalia_reg: index: 84 data: 0[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 84 data: 2147483649[ 3,322711] [HW_AUDIO]:AUDIO:write_indirect_azalia_reg: index: 84 data: 2147483648[ 3,322711] [HW_AUDIO]:[ 3,322711] = AUDIO:dce_aud_az_enable: index: 4 data: 0x8000[ 3,322711] [SURFACE]:Pipe:0 0x85801348ccc8: addr hi:0xf4, addr low:0xf96000, src: 0, 0, 1920, 1080; dst: 0, 0, 1920, 1080;clip: 0, 0, 1920, 1080[ 3,322711] [SURFACE]:Pipe 0: width, height, x, y[ 3,322711] viewport:1920, 1080, 0, 0[ 3,322711] recout: 1920, 1080, 0, 0[ 3,342311] [SURFACE]:Pipe:0 0x85801348ccc8: addr hi:0xf4, addr low:0xf96000, src: 0, 0, 1920, 1080; dst: 0, 0, 1920, 1080;clip: 0, 0, 1920, 1080[ 3,342311] [SURFACE]:Pipe 0: width, height, x, y[ 3,342311] viewport:1920, 1080, 0, 0[ 3,342311] recout: 1920, 1080, 0, 0[ 3,352109] wsdisplay0 at amdgpufb0 kbdmux 1: console (default, vt100 emulation), using wskbd0[ 3,352109] wsmux1: connecting to wsdisplay0[ 10,368692] wsdisplay0: screen 1 added (default, vt100 emulation)[ 10,368692] wsdisplay0: screen 2 added (default, vt100 emulation)[ 10,368692] wsdisplay0: screen 3 added (default, vt100 emulation)[ 10,368692] wsdisplay0: screen 4 added (default, vt100 emulation)[ 46,942227] panic: unlocking unlocked wait/wound mutex: 0x858023c90920[ 46,942227] cpu0: Begin traceback...[ 46,942227] vpanic() at netbsd:vpanic+0x183[ 46,942227] panic() at netbsd:panic+0x3c[ 46,942227] linux_ww_mutex_unlock() at netbsd:linux_ww_mutex_unlock+0x9e[ 46,942227] ttm_bo_release() at netbsd:ttm_bo_release+0xf3[ 46,942227] amdgpu_bo_unref() at netbsd:amdgpu_bo_unref+0x1d[ 46,942227] amdgpu_vm_free_table() at netbsd:amdgpu_vm_free_table+0x53[ 46,942227] amdgpu_vm_free_pts() at netbsd:amdgpu_vm_free_pts+0xeb[ 46,942227] amdgpu_vm_fini() at netbsd:amdgpu_vm_fini+0x270[ 46,942227] amdgpu_driver_postclose_kms() at netbsd:amdgpu_driver_postclose_kms+0x101[ 46,942227] drm_file_free() at netbsd:drm_file_free+0x1fb[ 46,942227] drm_close() at netbsd:drm_close+0x60[ 46,942227] closef() at netbsd:closef+0x58[ 46,942227] fd_close() at netbsd:fd_close+0x140[ 46,942227] sys_close() at netbsd:sys_close+0x22[ 46,942227] syscall() at netbsd:syscall+0x1fc[ 46,942227] --- syscall (number 6) ---[ 46,942227] netbsd:syscall+0x1fc:[ 46,942227] cpu0: End traceback...Best regards,r0ller
cannot login to X after upgrade
Hi All,Sorry for sending an html email but locked myself out of my NetBSD. After upgrading to version 10 yesterday and rebooting, xdm started and I could log in. When starting it today, I cannot log in to X as the user/pw combo is reported as incorrect. However, I can log in with the same user/pw combo when switching to terminal. Special chars and keyboard layout is not an issue, that I've checked. Any ideas?Thanks,r0ller
Re: cannot login to X after upgrade
Sorry for the noise, turned out that after pkgin upgrade, some stuff like default wm (jwm) got broken dependencies which triggered these fawlty towers (symptoms on xdm login). On 4/6/24 21:31, r0ller wrote: Hi All, Sorry for sending an html email but locked myself out of my NetBSD. After upgrading to version 10 yesterday and rebooting, xdm started and I could log in. When starting it today, I cannot log in to X as the user/pw combo is reported as incorrect. However, I can log in with the same user/pw combo when switching to terminal. Special chars and keyboard layout is not an issue, that I've checked. Any ideas? Thanks, r0ller
[plain text] NetBSD 10 RC1 live image
Hi All, Just booted the following box via usb using the 10RC1 live image which normally runs 9.3: -AMD Ryzen 5 3600X -MSI B450 GAMING PRO CARBON MAX WIFI -2 Corsair 8gb DDR4 3200Mhz Vengeance Pro Black -radeon r9 nano 4GB video card -samsung 1TB sata2 hdd Improvements I encountered: -radeon r9 nano got identified correctly in dmesg -intel 9260 based integrated wifi identified correctly in dmesg (9.3 only recognizes an additional intel 7265 NGWG W wifi card) -poweroff shuts down the box correctly (9.3 gets only till the message saying something like: press any key to reboot) Mounting wd0a of course works but no clue how to test further the live image. But based on these I'm pretty sure that release 10 will run better on this box than 9.3. So waiting for the release :) Best regards, r0ller PS.: Sorry, earlier I sent an html version of this. I hope it landed in the wastebin.
NetBSD 10 RC1 live image
Hi All,Just booted the following box via usb using the 10RC1 live image which normally runs 9.3:-AMD Ryzen 5 3600X-MSI B450 GAMING PRO CARBON MAX WIFI-2 Corsair 8gb DDR4 3200Mhz Vengeance Pro Black-radeon r9 nano 4GB video card-samsung 1TB sata2 hddImprovements I encountered:-radeon r9 nano got identified correctly in dmesg-intel 9260 based integrated wifi identified correctly in dmesg (9.3 only recognizes an additional intel 7265 NGWG W wifi card)-poweroff shuts down the box correctly (9.3 gets only till the message saying something like: press any key to reboot)Mounting wd0a of course works but no clue how to test further the live image. But based on these I'm pretty sure that release 10 will run better on this box than 9.3. So waiting for the release :)Best regards,r0ller
Re: libc license
Hi All, Thanks for the clarification! Best regards, r0ller PS: If only the libc could be redistributed with 0BSD license, it would have a big impact on the embedded use cases. On 2023. 02. 10. 16:07, Greg Troxel wrote: Julian Coleman writes: If you want to redistribute libc, you need to provide some way to display the licences for every libc source file as part of the documentation for the embedded device. I think it is acceptable to ship the device with a paper license. There is no requirement that the device itself has to do the display. This license was written back in the days when you'd get a tape and a document explaining it.
libc license
Hi All, I read on netbsd.org that netbsd uses the 2 clause BSD license where the 2nd clause says: Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. What does this mean in embedded environments where only the libc would be redistributed in binary form? Thanks®ards, r0ller
Re: sending/receiving UTF-8 characters from terminal to program
It seems that all my previously sent emails to say thanks got lost so I give it another try: thanks to all who got involved and helped me! Problem is solved :) Best regards, r0ller On 1/21/23 12:26 AM, RVP wrote: On Fri, 20 Jan 2023, Valery Ushakov wrote: On Fri, Jan 20, 2023 at 15:09:44 +0100, r0ller wrote: Well, checking what printf results in, I get: $printf 'n?z'|hexdump -C 6e e9 7a |n.z| 0003 $printf $'n\uE9z'|hexdump -C 6e c3 a9 7a |n..z| 0004 It's definitely different from what you got for 'n?z'. What does that mean? In the second example you specify \uE9 which is the unicode code point for e with acute. It is then uncondionally converted by printf to UTF-8 (which is two bytes: 0xc3 0xa9) on output. Your terminal input is in 8859-1 it seems. That's it. The terminal emulator is not generating UTF-8 from the keyboard input. May be you need to specify -u8 option or utf8 resource? That would work. So would running uxterm instead of xterm, but, all of these mess-up command-line editing: Alt+key is converted into a char. code instead of an ESC+key sequence. R0ller, do this: 1. Add your locale settings in ~/.xinitrc (or ~/.xsession if using xdm): export LANG=hu_HU.UTF-8 export LC_CTYPE=hu_HU.UTF-8 export LC_MESSAGES=hu_HU.UTF-8 2. In ~/.Xresources, tell xterm to use the current locale when generating chars.: XTerm*locale: true The `-lc' option does the same thing. If using uxterm, the class-name becomes `UXTerm'. On Fri, 20 Jan 2023, Robert Elz wrote: I believe bash will take your current locale into account when doing that [...] That's correct. But as r0ller had a UTF-8 locale set, I didn't mention that. However, it is better to be precise, so thank you! -RVP
Re: sending/receiving UTF-8 characters from terminal to program
Hi All, That did the trick. Thanks to everyone! BR, r0ller PS: I replied already yesterday but that seems to get lost somehow. On 1/21/23 12:26 AM, RVP wrote: On Fri, 20 Jan 2023, Valery Ushakov wrote: On Fri, Jan 20, 2023 at 15:09:44 +0100, r0ller wrote: Well, checking what printf results in, I get: $printf 'n?z'|hexdump -C 6e e9 7a |n.z| 0003 $printf $'n\uE9z'|hexdump -C 6e c3 a9 7a |n..z| 0004 It's definitely different from what you got for 'n?z'. What does that mean? In the second example you specify \uE9 which is the unicode code point for e with acute. It is then uncondionally converted by printf to UTF-8 (which is two bytes: 0xc3 0xa9) on output. Your terminal input is in 8859-1 it seems. That's it. The terminal emulator is not generating UTF-8 from the keyboard input. May be you need to specify -u8 option or utf8 resource? That would work. So would running uxterm instead of xterm, but, all of these mess-up command-line editing: Alt+key is converted into a char. code instead of an ESC+key sequence. R0ller, do this: 1. Add your locale settings in ~/.xinitrc (or ~/.xsession if using xdm): export LANG=hu_HU.UTF-8 export LC_CTYPE=hu_HU.UTF-8 export LC_MESSAGES=hu_HU.UTF-8 2. In ~/.Xresources, tell xterm to use the current locale when generating chars.: XTerm*locale: true The `-lc' option does the same thing. If using uxterm, the class-name becomes `UXTerm'. On Fri, 20 Jan 2023, Robert Elz wrote: I believe bash will take your current locale into account when doing that [...] That's correct. But as r0ller had a UTF-8 locale set, I didn't mention that. However, it is better to be precise, so thank you! -RVP
Re: sending/receiving UTF-8 characters from terminal to program
Guys, thanks for everyone! Problem solved :D I'm really grateful to all of you. Best regards, r0ller On 1/21/23 12:26 AM, RVP wrote: On Fri, 20 Jan 2023, Valery Ushakov wrote: On Fri, Jan 20, 2023 at 15:09:44 +0100, r0ller wrote: Well, checking what printf results in, I get: $printf 'n?z'|hexdump -C 6e e9 7a |n.z| 0003 $printf $'n\uE9z'|hexdump -C 6e c3 a9 7a |n..z| 0004 It's definitely different from what you got for 'n?z'. What does that mean? In the second example you specify \uE9 which is the unicode code point for e with acute. It is then uncondionally converted by printf to UTF-8 (which is two bytes: 0xc3 0xa9) on output. Your terminal input is in 8859-1 it seems. That's it. The terminal emulator is not generating UTF-8 from the keyboard input. May be you need to specify -u8 option or utf8 resource? That would work. So would running uxterm instead of xterm, but, all of these mess-up command-line editing: Alt+key is converted into a char. code instead of an ESC+key sequence. R0ller, do this: 1. Add your locale settings in ~/.xinitrc (or ~/.xsession if using xdm): export LANG=hu_HU.UTF-8 export LC_CTYPE=hu_HU.UTF-8 export LC_MESSAGES=hu_HU.UTF-8 2. In ~/.Xresources, tell xterm to use the current locale when generating chars.: XTerm*locale: true The `-lc' option does the same thing. If using uxterm, the class-name becomes `UXTerm'. On Fri, 20 Jan 2023, Robert Elz wrote: I believe bash will take your current locale into account when doing that [...] That's correct. But as r0ller had a UTF-8 locale set, I didn't mention that. However, it is better to be precise, so thank you! -RVP
Re: sending/receiving UTF-8 characters from terminal to program
Well, checking what printf results in, I get: $printf 'néz'|hexdump -C 6e e9 7a |n.z| 0003 $printf $'n\uE9z'|hexdump -C 6e c3 a9 7a |n..z| 0004 It's definitely different from what you got for 'néz'. What does that mean? Thanks, r0ller On 1/20/23 9:55 AM, RVP wrote: On Fri, 20 Jan 2023, r0ller wrote: Thanks for your efforts to reproduce it :) I just don't get why it works for you with the same locales and why it doesn't for me. Are there any other settings that affect encoding besides LC variables and LANG? Since we seem to have the same flookup binary, check against the magyar.fst I used: https://github.com/r0ller/alice/tree/master/hi_android/foma Next check that the input you're feeding to flookup actually _is_ UTF-8. Both /bin/sh and bash output UTF-8 if given Unicode code- points in the form `\u'. So, $ printf 'néz' | hexdump -C 6e c3 a9 7a |n..z| 0004 $ printf $'n\uE9z' | hexdump -C 6e c3 a9 7a |n..z| 0004 $ If that works, then check those UTF-8 bytes against whatever the terminal emulator generated from your keystrokes for the `é' in `néz'. -RVP
Re: sending/receiving UTF-8 characters from terminal to program
Thanks for your efforts to reproduce it :) I just don't get why it works for you with the same locales and why it doesn't for me. Are there any other settings that affect encoding besides LC variables and LANG?Best regards,r0ller Eredeti levél Feladó: RVP Dátum: 2023 január 19 12:44:25Tárgy: Re: sending/receiving UTF-8 characters from terminal to programCímzett: r0ller On Wed, 18 Jan 2023, r0ller wrote: > echo néz|flookup magyar.fst > > it results in: > > néz +? > > However, when passing the string as: > > echo néz|flookup magyar.fst > > I get a successful analysis: > > néz +swConsonant+néz[stem]+CON > néz +swConsonant+néz[stem]+CON+Nom > néz néz[stem]+Verb+IndefSg3 > That should work--and it does. With a just compiled flookup (from foma-0.9.18.tar.gz in the link you provided, and the .fst file got by googling): ``` $ uname -a NetBSD x202e.localdomain 9.3_STABLE NetBSD 9.3_STABLE (GENERIC) #0: Sat Jan 7 15:04:01 UTC 2023 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 $ export LANG=hu_HU.UTF-8 $ export LC_CTYPE=hu_HU.UTF-8 $ export LC_MESSAGES=hu_HU.UTF-8 $ /tmp/F/bin/flookup -v flookup 1.03 (foma library version 0.9.18alpha) $ echo néz | /tmp/F/bin/flookup alice-master/hi_android/foma/magyar.fst néz +swConsonant+néz[stem]+CON néz +swConsonant+néz[stem]+CON+Nom néz néz[stem]+Verb+IndefSg3 $ echo néz | /tmp/F/bin/flookup alice-master/hi_android/foma/magyar.fst néz+? $ ``` -RVP
Re: sending/receiving UTF-8 characters from terminal to program
Thanks! That's what I suspect as well but I just can't figure out how to fix it.Best regards,r0ller Eredeti levél Feladó: Rhialto Dátum: 2023 január 19 16:33:08Tárgy: Re: sending/receiving UTF-8 characters from terminal to programCímzett: RVP I think there is some encoding confusion going on here. I still use boring old Latin-1 (iso 8859-1), and I saw the two occurrences of the word nz differently. > > echo néz|flookup magyar.fst > > echo néz|flookup magyar.fst The first case with 1 letter in the middle looking like an e + aigu, the second time as 2 characters, probably an utf-8 encoding. I'm not sure if this helps you directly but it may be a hint for something. -Olaf. -- ___ "Buying carbon credits is a bit like a serial killer paying someone else to \X/ have kids to make his activity cost neutral." -The BOFHfalu.nl@rhialto
sending/receiving UTF-8 characters from terminal to program
Hi All,My locale is as follows:export LANG="hu_HU.UTF-8"export LC_CTYPE="hu_HU.UTF-8"export LC_MESSAGES="hu_HU.UTF-8"The problem is that even though I can type the special characters of the locale everywhere (though it's funny in the terminal where they only appear after the third key press) in X but when echoing a string containing such chars like (áéíóöőúű) and piping them to a program, they arrive somehow differently compared to when the same string is passed by calling the same program. I don't have any other example than foma (https://fomafst.github.io). It has a tool called flookup which requires special morphological dictionaries which most probably noone uses here (except me) but when passing a string from the command line like:echo néz|flookup magyar.fstit results in:néz +?However, when passing the string as:echo néz|flookup magyar.fstI get a successful analysis:néz +swConsonant+néz[stem]+CONnéz +swConsonant+néz[stem]+CON+Nomnéz néz[stem]+Verb+IndefSg3When calling the api function behind flookup from a program passing the string 'néz', I also get the analysis successfully. I don't have a clear explanation for this (only partially) and I also wonder why the terminal does not translate the locale special utf-8 bytes back to a character when they're printed by the program. Actually, it's just inconvenient to always type the strings what I want to analyse in a program, compile and execute it instead of giving it a go from the shell.Could anyone explain me what happens here and how I can handle it?Thanks,r0ller
Re: Black rectangle on vnc screen
For the server you can specify:vncserver -geometry WidthxHeightbut I don't know if there's anything like that for the client. But automatically, it does not scale indeed. Eredeti levél Feladó: Mayuresh Dátum: 2023 január 2 16:31:17Tárgy: Re: Black rectangle on vnc screenCímzett: r0ller netbsd-users On Mon, Jan 02, 2023 at 03:04:41PM +0530, Mayuresh wrote: > So far no black rectangle. One issue with tightvnc is, it doesn't resize the session to fit the client screen. tigervnc client does that automatically. I couldn't find any CLI option to do that. -- Mayuresh
Re: Black rectangle on vnc screen
Hi Mayuresh,I also tried tigervnc recently (on 9.3 though) but could not make it work. So I tried tightvnc and both the server and client parts work fine. I can connect to the server running on NetBSD from a win11 laptop (using tightvnc there as well) and vice versa. There are two issues I noticed:1) the netbsd client usually aborts if the win11 laptop shows movies, anims, video chat, etc.2) NetBSD client cannot connect to vnc server running on android (droidvnc) while the windows client canBest regards,r0ller Eredeti levél Feladó: Mayuresh Dátum: 2023 január 1 17:31:52Tárgy: Black rectangle on vnc screenCímzett: netbsd-users I am using tigervnc-1.12.0.1.20.13nb5, server on NetBSD 9.2 amd64 and client on NetBSD 10.0 BETA amd64 and another client on Linux. The Linux client works fine, though the one on NetBSD 10.0 BETA intermittently shows black patches of rectangles on the screen. Has anyone experienced this and please suggest if a workaround if known. The NetBSD 10.0 BETA vnc client is running on a laptop with amdgpu X11 driver on an external HDMI screen. On the same laptop with amdgpu driver in the kernel disabled, when hdmi also gets disabled, the issue has, as yet, not occurred on the laptop monitor. -- Mayuresh
ffs2ea effects on rescue sw?
Hi All,Obviously I don't have the knowledge to judge this so this question may sound odd but will ffs2ea have any support of the existing data rescue solutions? I mean for example photorec (https://www.cgsecurity.org/wiki/PhotoRec) which works pretty well -this year it recovered me around 2 jpegs (some partially, some exactly) I deleted occassionally. By the way, it's not only good for image files and although the current version needs a small patch (can't recall, just a one liner) but it can be built from source.Nevertheless, the question is: will it work for ffs2ea?Best regards,r0ller
linux emulation questions
Hi All,I wanted to check if a linux program runs "better" if only linux specific code is invoked as it seems in certain cases the linux binaries find netbsd ones and execute them which leads to uncertain results. For example when a linux gradle install calls 'uname' and gets 'NetBSD' which results in 'unsupported platform'. So I created a PATH including only linux emulation specific directories like:export PATH=/usr/pkg/emul/linux/bin:/usr/pkg/emul/linux/sbin:/usr/pkg/emul/usr/bin:/usr/pkg/emul/linux/usr/sbinBut when starting the linux executable (Android Studio by the way), I get:./studio.sh: which: not foundIsn't 'which' part of the suse_base? Actually, all the suse_*-13.1* packages are installed and 'find' does not find 'which' anywhere under /usr/pkg/emul/linux.Another question is if it's possible to set up (similarly to PATH) that only linux libraries are searched for? I know that LD_LIBRARY_PATH can be set to list the linux lib dirs but that's checked last if I'm not mistaken.The last question is just a kind of security one: is it possible to tell the system that only a certain process and its children are enabled to emulate linux? I mean e.g. like a terminal could be launched with the linux emulation enabled option and whatever gets started there inherits that option.Best regards,r0ller
Re: the vine package in pkgin is wine64?
Hi Nia,Thanks for the link! However, there're plenty of win stuff that requires multiarch wine setup so neither 32 bit wine nor 64 bit wine is enough alone. E.g. even if the program is fully 64 bit but its installer is 32 bit, or if only one 32 bit lib is used then multiarch is required. I guess you know better than me but in case not: the wine64 package in pkgsrc/wip is multiarch although it's version is only 4.4. I hope it was documented during the google summer of code when it was developed how the package can be upgraded to newer versions, otherwise it'll get bitrotten :( Quite some time back I sent an email to the author about such docs to check if I was able to upgrade it but never got an answer.Best regards,r0ller Eredeti levél Feladó: nia Dátum: 2022 november 15 08:23:58Tárgy: Re: the vine package in pkgin is wine64?Címzett: r0ller On Fri, Nov 11, 2022 at 10:41:15PM +, r0ller wrote: > Running 32 bit win stuff does not work with that. I'm running 32-bit only WINE programs in a 32-bit NetBSD chroot (using sandboxctl). It works okay: https://washbear.neocities.org/wine-sandbox.html
Re: the vine package in pkgin is wine64?
Got the answer: that package in pkgin is just the wine64 package and not the WoW64. So running 32 bit win stuff does not work with that. That's a pity as the WoW64 (called wine64 in pkgsrc/wip) is only the 4.4 version. Eredeti levél Feladó: r0ller Dátum: 2022 november 11 11:14:40Tárgy: the vine package in pkgin is wine64?Címzett: netbsd-users@netbsd.org Hi All,I've just discovered that now there's a wine package in pkgin :) As I'm on amd64 it must be the wine64 which previously resided in pkgsrc/wip only, right?Therefore, I tried to enable the USER_LDT option and disable SVS in a custom kernel config but I couldn't build it (see my previous email: building new kernel on upgraded system).I know that SVS can be disabled via sysctl but is it possible to enable user_ldt on the fly as well?Best regards,r0ller
Re: building new kernel on upgraded system
No clue what was the problem but after having nuked /usr/src, fetching the same source again and building everything is fine. Eredeti levél Feladó: r0ller Dátum: 2022 november 10 14:00:51Tárgy: Re: building new kernel on upgraded systemCímzett: netbsd-users@NetBSD.org Hi All,Well, the doc helped but the build got stuck at:/usr/src/external/mit/epoll-shim/include/sys/unistd.has it tries to#include but the system does not find it. If I doexport CFLAGS=-I/usr/src/includewhich contains an ssp directory (with a unistd.h file) and then start to build the kernel then it gets stuck because of some other included files from that directory like:/usr/src/include/ssp/ssp.h:55:26: error: no previous prototype for '__ssp_real_read'Can someone help me figure out what to do?Thanks,r0ller Eredeti levél ----Feladó: r0ller Dátum: 2022 november 10 09:28:22Tárgy: Re: building new kernel on upgraded systemCímzett: netbsd-users@NetBSD.org Thanks! That'll help :) Eredeti levél Feladó: Michael van Elst Dátum: 2022 november 10 08:54:53Tárgy: Re: building new kernel on upgraded systemCímzett: netbsd-users@netbsd.orgr0l...@freemail.hu (r0ller) writes: > Hi All,I've just tried to build a custom configured kernel on a > system that was installed originally as 9.1 and later upgraded to > 9.2 and 9.3. Executed in /usr/srcbuild.sh toolswhich ended successfully > but the (beginning part of the) summary looks like:build.sh command: > ./build.sh toolsbuild.sh started: Wed Nov 9 21:56:45 CET 2022NetBSD > version: 9.1_STABLEMACHINE: amd64MACHINE_ARCH: x86_64Build platform: > NetBSD 9.3 amd64HOST_SH: /bin/shWhat does NetBSD version 9.1_STABLE > refer to? Weren't the system sources updated during the upgrades? > Honestly, I cannot recall how I upgraded the system (sysinst/sysupgrade).In > the end the question is: does that indicate that the custom kernel > will be built from a 9.1 source when I issue 'build.sh > kernel=MYKERNEL'?Thanks,r0ller The system sources weren't updated. You could unpack the source sets to get the release sources, but most people who build from sources prefer to track the stable branch. Here is the chapter from the guide that describes how you can fetch NetBSD sources: https://www.netbsd.org/docs/guide/en/chap-fetch.html
the vine package in pkgin is wine64?
Hi All,I've just discovered that now there's a wine package in pkgin :) As I'm on amd64 it must be the wine64 which previously resided in pkgsrc/wip only, right?Therefore, I tried to enable the USER_LDT option and disable SVS in a custom kernel config but I couldn't build it (see my previous email: building new kernel on upgraded system).I know that SVS can be disabled via sysctl but is it possible to enable user_ldt on the fly as well?Best regards,r0ller
Re: building new kernel on upgraded system
Hi All,Well, the doc helped but the build got stuck at:/usr/src/external/mit/epoll-shim/include/sys/unistd.has it tries to#include but the system does not find it. If I doexport CFLAGS=-I/usr/src/includewhich contains an ssp directory (with a unistd.h file) and then start to build the kernel then it gets stuck because of some other included files from that directory like:/usr/src/include/ssp/ssp.h:55:26: error: no previous prototype for '__ssp_real_read'Can someone help me figure out what to do?Thanks,r0ller Eredeti levél ----Feladó: r0ller Dátum: 2022 november 10 09:28:22Tárgy: Re: building new kernel on upgraded systemCímzett: netbsd-users@NetBSD.org Thanks! That'll help :) Eredeti levél Feladó: Michael van Elst Dátum: 2022 november 10 08:54:53Tárgy: Re: building new kernel on upgraded systemCímzett: netbsd-users@netbsd.orgr0l...@freemail.hu (r0ller) writes: > Hi All,I've just tried to build a custom configured kernel on a > system that was installed originally as 9.1 and later upgraded to > 9.2 and 9.3. Executed in /usr/srcbuild.sh toolswhich ended successfully > but the (beginning part of the) summary looks like:build.sh command: > ./build.sh toolsbuild.sh started: Wed Nov 9 21:56:45 CET 2022NetBSD > version: 9.1_STABLEMACHINE: amd64MACHINE_ARCH: x86_64Build platform: > NetBSD 9.3 amd64HOST_SH: /bin/shWhat does NetBSD version 9.1_STABLE > refer to? Weren't the system sources updated during the upgrades? > Honestly, I cannot recall how I upgraded the system (sysinst/sysupgrade).In > the end the question is: does that indicate that the custom kernel > will be built from a 9.1 source when I issue 'build.sh > kernel=MYKERNEL'?Thanks,r0ller The system sources weren't updated. You could unpack the source sets to get the release sources, but most people who build from sources prefer to track the stable branch. Here is the chapter from the guide that describes how you can fetch NetBSD sources: https://www.netbsd.org/docs/guide/en/chap-fetch.html
Re: building new kernel on upgraded system
Thanks! That'll help :) Eredeti levél Feladó: Michael van Elst Dátum: 2022 november 10 08:54:53Tárgy: Re: building new kernel on upgraded systemCímzett: netbsd-users@netbsd.orgr0l...@freemail.hu (r0ller) writes: > Hi All,I've just tried to build a custom configured kernel on a > system that was installed originally as 9.1 and later upgraded to > 9.2 and 9.3. Executed in /usr/srcbuild.sh toolswhich ended successfully > but the (beginning part of the) summary looks like:build.sh command: > ./build.sh toolsbuild.sh started: Wed Nov 9 21:56:45 CET 2022NetBSD > version: 9.1_STABLEMACHINE: amd64MACHINE_ARCH: x86_64Build platform: > NetBSD 9.3 amd64HOST_SH: /bin/shWhat does NetBSD version 9.1_STABLE > refer to? Weren't the system sources updated during the upgrades? > Honestly, I cannot recall how I upgraded the system (sysinst/sysupgrade).In > the end the question is: does that indicate that the custom kernel > will be built from a 9.1 source when I issue 'build.sh > kernel=MYKERNEL'?Thanks,r0ller The system sources weren't updated. You could unpack the source sets to get the release sources, but most people who build from sources prefer to track the stable branch. Here is the chapter from the guide that describes how you can fetch NetBSD sources: https://www.netbsd.org/docs/guide/en/chap-fetch.html
building new kernel on upgraded system
Hi All,I've just tried to build a custom configured kernel on a system that was installed originally as 9.1 and later upgraded to 9.2 and 9.3. Executed in /usr/srcbuild.sh toolswhich ended successfully but the (beginning part of the) summary looks like:build.sh command: ./build.sh toolsbuild.sh started: Wed Nov 9 21:56:45 CET 2022NetBSD version: 9.1_STABLEMACHINE: amd64MACHINE_ARCH: x86_64Build platform: NetBSD 9.3 amd64HOST_SH: /bin/shWhat does NetBSD version 9.1_STABLE refer to? Weren't the system sources updated during the upgrades? Honestly, I cannot recall how I upgraded the system (sysinst/sysupgrade).In the end the question is: does that indicate that the custom kernel will be built from a 9.1 source when I issue 'build.sh kernel=MYKERNEL'?Thanks,r0ller
android studio
Hi All,I had to change my windows laptop on which I developed android stuff so
while waiting for the new one I decided to give a try to android studio (via
linux emulation) on my NetBSD desktop. So here are the results.Installation
(well, starting studio.sh) works just fine, without any problems. I only had to
make sure that openjdk11 is found first in PATH instead of openjdk8.Opening any
projects and all the automatic plugin downloads seem to work fine.The first
problem you hit is when you start a gradle build. No matter which gradle
version you choose, you'll end up with the error: "Unknown platform: NetBSD".
Android studio always downloads their own version of gradle no matter if you
have it on NetBSD (currently, 6.8.3) but I'm not even sure if it's gradle or
one of their gradle plugins that complains. Besides, the downloaded gradle
versions are stored in hidden directories with generated names of hashes so
replacing a downloaded version with the NetBSD installed version is rather
tricky. I traced the command line gradle build by ktrace and was happy that it
hits uname as I thought simply prepending all the linux emul bins
(/usr/pkg/emul/linux/bin ... sbin ... /usr/bin ... /usr/sbin ...) to PATH will
do the trick. But it does not. Although, executing uname now returns Linux,
when executing gradle, it still reports the same problem: "Unknown platform:
NetBSD". I also found out that the file called Platform.java contains the check
by calling System.getProperty("os.name") but haven't even found it on the
system anywhere.So basically, got stuck. If anyone has any hint, it's welcome
:)Best regards,r0llerPS: By the way, stock (pkgin) Qt Creator runs just fine
with the new pkgsrc Qt6 and debugging via lldb also works (stock system gdb
cannot be used (haven't tried any other from pkgin) as it's compiled without
python scripting). So C++ develoipment seems feasible.
acpi problems
Hi All,I wanted to report this a long time ago but as usual I did not have enough time. Now, when upgrading from 9.2 to 9.3 (using sysupgrade) the issue hit me again as I took over the boot menu changes accidentally which removed the boot option to boot without ACPI. The box I have has a MSI B450 GAMING PRO CARBON MAX WIFI motherboard with amd ryzen 5 3600x and a radeon r9 nano gfx card. All that works fine (with NetBSD 9.3 as well) if I boot without acpi. If acpi is on, the system freezes -at least I never get the x logon screen. The last thing I see is the cursor in the top left corner on a black screen. Earlier I tried to generate a suitable xorg.conf to get the r9 nano work but never succeeded. So currently it works if acpi is off (I guess again) with a vesa driver.Does anyone have any idea how acpi and the r9 nano block "each other"?Thanks®ards,r0ller
Re: Android development
Hi Riza, As far as I can tell, natively not. I mean that linux emulation is definitely necessary. Mainly because the android dev environment is pretty much bound to Linux. I tried to build ndk on NetBSD but there are quite some stuff to change in their scripts -see 2) in this post: https://mail-index.netbsd.org/netbsd-users/2016/11/24/msg019072.html Even when using linux emulation, there's an unimplemented linux syscall (fallocate) which prevents writing out the binary in the end. However, I found a workaround by using named pipes (fifo) so building an android ndk lib on NetBSD is actually possible via Linux emulation. I'm doing it regularly and the ndk lib does work well on android. I cannot tell much about the sdk part but there are some who have tried Android Studio again via Linux emulation though I can't recall anything about how well it works. What I tried was Qt Creator to build an Android app. You can find my notes on it here (along with some others): https://github.com/r0ller/NetBSD-Qt-Notes After that you'll need to get all the different parts of the Android SDK (which Google makes harder and harder) that Qt Creator requires. In the end, it turned out that Qt Creator did not pick the right qmake but when copied the effective qmake call then it did build all the necessary libraries. That bug may have been resolved since then. However, there's a separate tool to build an apk of the generated artifacts which I did not succeed and haven't tried again. Best regards, r0ller Eredeti levél Feladó: Riza Dindir Dátum: 2021 szeptember 23 07:22:25 Tárgy: Android development Címzett: Netbsd-Users-List Hello All, Can we build android apps using the android sdk and adb on netbsd? Or any other means to develop android applications for mobile devices and smart phones? Regards, Riza
Re: pkgin does not install anything after upgrade to 9.2
Hi Greg, Thanks for the suggestion. I'm still doing the backup but will come back with the outcome. Best regards, r0ller Eredeti levél Feladó: Greg Troxel < g...@lexort.com (Link -> mailto:g...@lexort.com) > Dátum: 2021 július 9 13:06:24 Tárgy: Re: pkgin does not install anything after upgrade to 9.2 Címzett: r0ller < netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) Boot to single user and full fsck. Also make the backups you have been meaning to get around to right away
Re: pkgin does not install anything after upgrade to 9.2
Hi Greg, Thanks for your suggestions! It indeed seems to be corrupted :( I tried to nuke (rm -rf) the directory /usr/pkg/pkgdb/p5-Net-SSLeay-1.88nb1 but I got back that the directory is not empty which is pretty unusual for rm -rf. Now, when I try to list its contents, three files are shown: +COMMENT, +CONTENTS, +DESCR However, when listing with ls -al, I get the error: ls: +COMMENT: No such file or directory ls: +CONTENTS: No such file or directory ls: +DESCR: No such file or directory I tried to execute fsck for the node number (fsck 35752122) of the directory but I got back: fsck: cannot open '/dev/35752122': No such file or directory Is there any solution for this? Best regards, r0ller On 7/8/21 7:26 PM, Greg Troxel wrote: r0ller writes: The only error I see in pkg_install-err.log (which is not shown as error) which seems to block each pkg install is: pkg_admin: Cannot read +CONTENTS of package p5-Net-SSLeay-1.88nb1 Does anyone have any hint? pkg_admin rebuild-tree pkg_admin check make sure your variables in mk.conf are set to point to your pkgdb. See https://www.pkgsrc.org/pkgdb-change/ and set the variables even if you think it's not necessary. look in /usr/pkg/pkgdb/p5-Net-SSLeay-1.88nb1 and see if there is indeed no +CONTENTS. If true, you have had some corruption and I would rm -rf the p5-Net-SSLeay-1.88nb1 directory, and then you'll have to reinstall it.
pkgin does not install anything after upgrade to 9.2
Hi All, I've just upgraded from 9.0 (amd64) to 9.2 via sysinst successfully from ftp. Everything seems to work fine as earlier and surprisingly faster what is quite noticeable when starting firefox. However, after changing repositories.conf to point to amd64/9.2/All and upgrading all packages, nothing seems to have been upgraded and pkgin does not seem to install anything. There are many warnings about the platform difference (built for 9.0 vs 9.2) but no errors (except one maybe, see later). However, when e.g. installing firefox-86.0.1 pkgin acts as if it was doing its job, displays in the end the number of warnings (48 platform diff warns) and errors (0) but when I check the version with 'firefox --version' I still get 84.0. The only error I see in pkg_install-err.log (which is not shown as error) which seems to block each pkg install is: pkg_admin: Cannot read +CONTENTS of package p5-Net-SSLeay-1.88nb1 Does anyone have any hint? Thanks®ards, r0ller
debugging with Qt Creator
Hi All, Just sharing my continued adventures with Qt on NetBSD. This time debugging a non-Qt c++ project -Qt projects I have not yet tested. The good news is: it works :) However, there are some minor things one has to do: LLDB (doesn't really work, see description): -export LD_LIBRARY_PATH=/usr/pkg/lib otherwise Qt Creator does not find some shared libs -start Qt Creator and it will find the debugger if it's installed, you just have to select it for your kit -load a non-Qt c++ project, set a breakpoint and start the debugger in the debug menu like: Debug->Start Debugging->Start and Debug External Application -you'll get a popup with some options where you must decide how you want to start the debugger then hit ok -lldb will launch but if you set a breakpoint in a shared library it does not find its source so it jumps in the assembly and similarly it can't step in a function which is part of a shared library -otherwise it seems to work but due to the shared library limitation I stopped experimenting wiht it and it may even be a QT Creator bug as well since I found related bug reports from other platforms as well GDB: -upgrade gdb from 8.3 that comes with the system to 10.1 as the one shipped with the system does not support python scripting or what -I guess it was just not compiled like that. So Qt Creator will complain about that. -make sure that gdb 10.1 is found first in your PATH -I also do export LD_LIBRARY_PATH=/usr/pkg/lib since it was necessary for lldb but I haven't checked without it when using gdb -Start Qt Creator and it will find the debugger if it's installed, you just have to select it for your kit -gdb has a dedicated menü in Qt Creator Options unlike lldb so there's a ton of settings for it. If you have .gdbinit in your home it may be a good idea to check the option to ignore loading it. -load a non-Qt c++ project, set a breakpoint and start the debugger in the debug menu like: Debug->Start Debugging->Start and Debug External Application -you'll get a popup with some options where you must decide how you want to start the debugger then hit ok -Enjoy :) Everything I needed so far worked e.g. debugging shared library code, checking variable values, stack, analysing core dumps. Best regards, r0ller
epoll
Hi All, I tried to wrap in the linux syscalls an epoll implementation that seems to support NetBSD-9.1 https://github.com/jiixyj/epoll-shim but as I've never done such a thing before, it failed of course. First, I copied its source in the external/mit/epoll-shim directory and tried to include epoll.h via absolute path in linux_misc.c to support the epoll calls. This is definitely not the right way to do as when running build.sh it failed to find stdint.h (used in epoll.h) on the first try. I tried to find some docs about pulling in external sources but I haven't found anything that would describe how to do it. Can anyone give me any hint on this? Best regards, r0ller
updating linux subsystem?
Hi All, Does anyone know how to update the linux subsystem after installed on NetBSD? I installed suse-13.1 long ago but recently I bumped into a lib which required a newer glibc. I installed a newer one but it just frankensteined the linux subsystem so I nuked and reinstalled it. Suse-13.1 support ended in 2016 but fortunately I found an older version of the lib in question that worked with the existing glibc. Nevertheless, I pondered about if it's possible at all to update the linux libs? Thanks for any hints in advance! Best regards, r0ller
Qt5, Qt Creator, Qt Webassembly and Qt Android experience
Hi All, It took some time but I finally created a readme in a github repo where I published my notes about my Qt adventures on NetBSD. It's not yet a guide or a how-to but I'll try to take a step in that direction. The only thing I'm not sure about is improving the Qt Android part as it seems I found a workaround for it that fits me better of which I also wrote a few sentences in the end. Anyhow, here's the link: https://github.com/r0ller/NetBSD-Qt-Notes Best regards, r0ller
hardware upgrade info
Hi All, I upgraded my box for Christmas and as there are many questions about hw components asking which works and which not on NetBSD, here is what I experienced. The new hw is as follows: -AMD Ryzen 5 3600X -MSI B450 GAMING PRO CARBON MAX WIFI -2db Corsair 8gb DDR4 3200Mhz Vengeance Pro Black These I had already: -radeon r9 nano 4GB video card -samsung 1TB sata2 hdd The migration was as easy as I expected: I simply started the new box with the old hdd with an existing 9.0 installation and it booted just fine. There were two problems: 1) X did not start if ACPI was enabled (xdm or startx resulted in a black screen and the pc got frozen) so currently it's off which means poweroff does not turn off the box so I have to end it up by pressing the power button. 2) The intel 9260 based integrated wifi does not work though it's supported according to this: http://mail-index.netbsd.org/source-changes-hg/2018/04/09/msg74.html So I'm currently using the wifi card (via an m.2 to pcie adapter) from the previous box which is an Intel 7265 NGWG W. Nothing else required any fix :) Best regards, r0ller
Re: Looking for java an android devs on netbsd environment
Wow, this got pretty much truncated. This was the original: Hi John, Sorry for the late reply here as well :) You asked about some stuff which I was interested in as well but it took quite some time to figure them out. I also wanted to bring over the complete development to NetBSD for android based on qt so when you asked about qt creator I started to figure it out. There are some good and bad news. The bad is that it's difficult and I must admit I still not managed to deploy the compiled android app on the device but as you can guess it's possible to build a qt app for android on NetBSD
Re: Looking for java an android devs on netbsd environment
Hi John, Sorry for the late reply here as well :) You asked about some stuff which I was interested in as well but it took quite some time to figure them out. I also wanted to bring over the complete development to NetBSD for android based on qt so when you asked about qt creator I started to figure it out. There are some good and bad news. The bad is that it's difficult and I must admit I still not managed to deploy the compiled android app on the device but as you can guess it's possible to build a qt app for android on NetBSD
Re: netbsd.org unreachable
Hi, I did mean that I could not reach netbsd.org itself but the first indicator was that pkgin could not install any package after which I checked netbsd.org in the browser. I had no problem with visiting any other webpage so I even looked up an online ping app which also reported that netbsd.org is unreachable. Sorry for the noise if it was not the case but I did try to double check it. Best regards, r0ller Eredeti levél Feladó: Ignatios Souvatzis < ignat...@cs.uni-bonn.de (Link -> mailto:ignat...@cs.uni-bonn.de) > Dátum: 2020 augusztus 25 16:09:07 Tárgy: Re: netbsd.org unreachable Címzett: r0ller < r0l...@freemail.hu (Link -> mailto:r0l...@freemail.hu) > Hi one, On Tue, Aug 25, 2020 at 01:09:57PM +0200, r0ller wrote: > I guess you already know it but I don't know any better place to indicate > that netbsd.org is down :( what part of the domain, and what service? You have to be more specific. E.g. the mail and mailing list servers work fine at the moment, as indicated by our message, although it was delayed for a few hours leaving your webmail server. The web server is online too, as far as I can see. -is
netbsd.org unreachable
Hi All, I guess you already know it but I don't know any better place to indicate that netbsd.org is down :( Best regards, r0ller
Re: X server crashes after updating from 7.1 to 8.2
Hi, I also had similar experience with i915 drmkms so I ended up generating an xorg.conf and added the option AccelMethod in the device section like this which solved the issue: Option "AccelMethod" "uxa" That option is also mentioned in "man intel" but if I understand it correctly it is somewhat slower than the default "sna" method. Since then, I have no more crashes but it's indeed slower. Best regards, r0ller Eredeti levél Feladó: Silas < silas_nbli...@nocafe.net (Link -> mailto:silas_nbli...@nocafe.net) > Dátum: 2020 augusztus 4 17:40:29 Tárgy: X server crashes after updating from 7.1 to 8.2 Címzett: netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) Randomly, my X server crashes with apparent no reason. Most of the times, it happens when firefox tries to play a multimedia file, but it also happens randomly like when selecting a text on a PDF file (using evince3) or resizing a windows (I'm using i3 window manager). On NetBSD 7.1, I got strange patterns drawed on the screen. It looked as if it was a buffer overrun error that crashes the X server only on 8.2. Anyway, I don't know if anyone have had this issue before. Some information about my system follows below. The full Xorg.0.log is in https://pastebin.com/dJEAyHJH $ uname -a NetBSD hope 8.2 NetBSD 8.2 (GENERIC) #0: Tue Mar 31 05:08:40 UTC 2020 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64 $ dmesg | grep drm i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 0042 (rev. 0x12) drm: Memory usable by graphics device = 512M drm: Supports vblank timestamp caching Rev 2 (21.10.2013). drm: Driver supports precise vblank timestamp query. i915drmkms0: interrupting at ioapic0 pin 16 (i915) intelfb0 at i915drmkms0 i915drmkms0: info: registered panic notifier /var/log/Xorg.0.log error section: [ 614.976] (EE) Segmentation fault at address 0x7aee7ee3500c [ 614.976] (EE) Fatal server error: [ 614.976] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 614.976] (EE) [ 614.976] (EE) Please consult the The X.Org Foundation support at http://wiki.X.Org for help. [ 614.976] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 614.976] (EE) [ 614.982] (II) AIGLX: Suspending AIGLX clients for VT switch [ 615.328] (EE) Server terminated with error (1). Closing log file.
Re: does anyone have a working mozilla firefox-74.0 on 9.0 amd64?
Hi Greg, Mine works fine. However, my system is an upgraded one from 8.1 to 9.0 if it makes a difference. Then I installed firefox-74.0 and removed 68 (I guess that was its version). On the first run it complained about libepoxy like in this mail: https://mail-index.netbsd.org/pkgsrc-users/2020/01/29/msg030382.html So I followed that up to the solution which was to remove the installed libepoxy package: https://mail-index.netbsd.org/pkgsrc-users/2020/01/29/msg030384.html It worked out indeed, and since then firefox-74.0 runs just fine. Best regards, r0ller Eredeti levél Feladó: Greg A. Woods < wo...@planix.ca (Link -> mailto:wo...@planix.ca) > Dátum: 2020 július 2 02:34:48 Tárgy: does anyone have a working mozilla firefox-74.0 on 9.0 amd64? Címzett: NetBSD Users's Discussion List < port-am...@netbsd.org (Link -> mailto:port-am...@netbsd.org) > So, does anyone have a working mozilla firefox-74.0 on 9.0 amd64? I've been rebuilding another amd64 system starting with a stock 9.0 install, and I decided I should try firefox, since I haven't tried it in a very long time, so I just used "pkgin install firefox" to try However it just dumps core when I start it: Reading symbols from /usr/pkg/lib/firefox/firefox... (No debugging symbols found in /usr/pkg/lib/firefox/firefox) (gdb) run Starting program: /usr/pkg/lib/firefox/firefox [New process 17803] [Detaching after fork from child process 2656] [New LWP 2 of process 17803] Thread 1 "" received signal SIGSEGV, Segmentation fault. 0x7b1ac69aa96a in ?? () from /usr/pkg/lib/firefox/libxul.so (gdb) bt #0 0x7b1ac69aa96a in ?? () from /usr/pkg/lib/firefox/libxul.so #1 0x7b1ac980e571 in ?? () from /usr/pkg/lib/firefox/libxul.so #2 0x7b1ac980b18b in ?? () from /usr/pkg/lib/firefox/libxul.so #3 0x7b1ac9810278 in ?? () from /usr/pkg/lib/firefox/libxul.so #4 0x7b1ac98105d9 in ?? () from /usr/pkg/lib/firefox/libxul.so #5 0x0001e8c0a810 in ?? () #6 0x0001e8c068fd in _start () (gdb) (stripped binaries are a curse) -- Greg A. Woods Kelowna, BC +1 250 762-7675 RoboHack Planix, Inc. Avoncote Farms
Re: netbsd 9 upgrade experience
Hi Hauke, I bumped into an email in one of the netbsd lists of which I concluded that generating an xorg.conf and adding the option AccelMethod in the device section like this, solves the i915 drmkms issue: Option "AccelMethod" "uxa" So I gave it a try and it seems to be true :) That option is also mentioned in "man intel" but if I understand it correctly it is somewhat slower than the default "sna". But considering that this box is a bit more than ten years old with an integrated i915 (i950gma), 3gb ram and a pentium cpu, I don't care if it does not crash. Thanks for your help though! :) Best regards, r0ller Eredeti levél Feladó: Hauke Fath < hauke.f...@gmail.com (Link -> mailto:hauke.f...@gmail.com) > Dátum: 2020 június 23 15:10:11 Tárgy: Re: netbsd 9 upgrade experience Címzett: r0ller < r0l...@freemail.hu (Link -> mailto:r0l...@freemail.hu) > On Sat, 20 Jun 2020 20:19:08 + (GMT), r0ller wrote: > 3) xorg still crashes when it gets a little stress as it did in 8.1 > with i915drmkms enabled tough I hoped that upgrading to 9 will solve > it. See xdm.log and Xorg.0.log attached. You might be better off with wip/xf86-video-intel-git - it fixed similar problems for me on a HP EliteBook. But I don't know if you can run a pkgsrc X server alongside base X11, or if you need to build all things X from pkgsrc. Cheerio, Hauke -- The ASCII Ribbon Campaign Hauke Fath () No HTML/RTF in email Institut für Nachrichtentechnik /\ No Word docs in email TU Darmstadt Respect for open standards Ruf +49-6151-16-21344
Re: netbsd 9 upgrade experience
Hi All, Thanks Greg and Martin for the hints! I had to fix them manually but managed to get it done so postinstall does not complain when I let them checked. Today when I started up the system I got in dmesg this stuff but I haven't seen that after reboot: [ 1686,631400] kern error: [drm:(/usr/src/sys/external/bsd/drm2/dist/drm/i915/intel_sprite.c:132)intel_pipe_update_start] *ERROR* Potential atomic update failure on pipe A: -35 I don't know if it helps (if anyone has time for it at all) besides the xdm.log and Xorg.0.log sent yesterday. Best regards, r0ller Eredeti levél Feladó: Martin Husemann < mar...@duskware.de (Link -> mailto:mar...@duskware.de) > Dátum: 2020 június 21 07:53:58 Tárgy: Re: netbsd 9 upgrade experience Címzett: Greg Troxel < g...@lexort.com (Link -> mailto:g...@lexort.com) > On Sat, Jun 20, 2020 at 08:13:42PM -0400, Greg Troxel wrote: > This is the easy one. postinstall expects sources. You can use the -s > option. I unpack etc.tgz and xetc.tgz to /usr/netbsd-etc and pass that. > Amazingly, this is even in the manual, but it doesn't really say that > you need a plan for -s. Back in the days when sysinst started running postinstall after updates there were no cases when postinstall needed manual intervention. We need to deal with this in sysinst somehow(tm). The black xdm fields will go away once postinstall fixed "x11" properly (it is caused by missing resource entries in the xdm config files). Martin
netbsd 9 upgrade experience
Hi All, I've just upgraded from 8.1 to 9 (amd64) and I have some issues which I'd like to clairfy. Fortunately, the upgrade went smoothly and the system is up and running (I'm writing this in a web email client in firefox) so thanks to all :) Now, here are the issues I bumped into: 1) After system upgrade done via usb installer I got the message that postinstall fixes failed for: fontconfig gid x11. When I tried to execute postinstall afterwards, I got the error message that /usr/src is not a directory. 2) xlogin user and password fields became black (surprisingly, both fields are visible on xlogin when xdm starts) and I cannot see whatever I type in the user field. 3) xorg still crashes when it gets a little stress as it did in 8.1 with i915drmkms enabled tough I hoped that upgrading to 9 will solve it. See xdm.log and Xorg.0.log attached. Any hints are welcome! Thanks again to all for NetBSD9! Best regards, r0ller xdm.log Description: Binary data Xorg.0.log Description: Binary data
Re: wine64 (devel) and NetBSD 8.0
Hi, As far as I can recall, it will work only on 9.0 if the GSoC project got merged. If not, then you shall try current. Here's the last report from the GSoC project: http://blog.netbsd.org/tnf/entry/porting_wine_to_amd64_on1 Best regards, r0ller Eredeti levél Feladó: tlaro...@polynum.com (Link -> mailto:tlaro...@polynum.com) Dátum: 2020 április 17 10:50:31 Tárgy: wine64 (devel) and NetBSD 8.0 Címzett: netbsd-users@NetBSD.org (Link -> mailto:netbsd-users@NetBSD.org) Hello, Has anybody managed to have a working version of Wine on NetBSD 8.0 amd64? The only one compilable with pkgsrc is the wine-dev leading to a wine64. I have set the USER_LDT option in the kernel and tried the sysctl -w vm.user_va0_disable=0 but to no avail. even trying, under X11 (native version), to run: $ wine64 uninstaller (uninstaller being an exe provided with Wine) it coredumps. Trying a console only program (this is really for these ones I'm trying Wine since some closed source libraries are provided only for Windows---coordinates conversion for GIS programs) doesn't work. Does it work only with 9.x? Only for x86 and not amd64 ? Is there a way to track down? (there are messages about stack overflow so is FORTIFY_SOURCE a problem too?) Any hint will be greatly appreciated. TIA, -- Thierry Laronde http://www.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: Looking for java an android devs on netbsd environment
Hi, You haven't mentioned NDK but that works if you'd need it via linux emulation. At least, that's the part I do on NetBSD. Crosscompiling for 32bit arm is tricky though. 64bit arm crosscompiling works fine. Best regards, r0ller Eredeti levél Feladó: John m0t < j0...@inbox.lv (Link -> mailto:j0...@inbox.lv) > Dátum: 2020 április 3 16:27:37 Tárgy: Looking for java an android devs on netbsd environment Címzett: netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) Hello; I am trying to set a full production system to do android and java development in NetBSD. Is anyone doing it right now or ever done it before? I need to know if these things work on netbsd: a. android studio b. adb bridge c. eclipse d.intellij idea e. qt creator f. java (oracle java vs OpenJDK)(which version/versions? 1.8? 11?) any experience that you have is most most welcome and appreciated. Thank You. JB
setting keyboard map for xdm login
Hi All, I'm not entirely sure if I'm doing it right but I usually set the keyboard (setxkbmap) in Xsetup (/etc/X11/xdm/Xsetup_0) instead of .xinitrc (or .xsession for xdm) so that it's set up already for the logon screen. However, I forgot it recently at a fresh NetBSD installation and tried to look up the info from the NetBSD docs but I haven't found it anywhere. Fortunately, it came into my mind when I read through the xdm man page as it mentions Xsetup in some other context:) Provided that this practice is fine, is it worth mentioning in Chapter 9.3 of the NetBSD docs? If so, how can this change be triggered? Best regards, r0ller
adding a new linux syscall: fallocate
Hi All,
I'm trying to add a new linux syscall called fallocate just to map it to the
existing posix_fallocate whenever it's possible (as it is nonportable for its
mode as far as I can see). I've read some docs (but certain things may have
been overlooked) like:
https://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_fallocate.html
http://man7.org/linux/man-pages/man2/fallocate.2.html
https://www.netbsd.org/docs/internals/en/chap-processes.html#syscall_howto
https://www.netbsd.org/docs/kernel/programming.html#adding_a_system_call
What I've done so far on a NetBSD-8.0 VM after pulling its source:
1) modified: /usr/src/sys/compat/linux/arch/amd64/syscalls.master like:
285 STD { int|linux_sys||fallocate(int fd, int mode, linux_off_t offset,
linux_off_t len); }
2) added linux_sys_fallocate() to /usr/src/sys/compat/linux/common/linux_file.c
like:
int linux_sys_fallocate(int fd, int mode, linux_off_t offset, linux_off_t
len){
printf("Calling linux_sys_fallocate\n");
return EOPNOTSUPP;
}
Question: is that the right place to add linux_sys_fallocate()?
3) issued make in /usr/src/sys/compat/linux/arch/amd64 which seems to have done
its job right but do I need to do so as well in /usr/src/sys/compat/linux??? If
I do so I get:
don't know how to make syscalls.master. Stop.
4) rebuilt the GENERIC kernel which stopped when it got to linux_file.o. The
error message didn't say anything more only that it stopped there but judging
by that compiling linux_file.c went fine but linking failed.
Thanks for any hints!
Best regards,
r0ller
Re: What are all these core files?
Hi, Well, they seem to be dumps of the corresponding programs:) If you keep getting them even after deleting all, then something must continuously restart one or more programa that always terminate abnormally. Best regards, r0ller Eredeti levél Feladó: D'Arcy Cain < da...@netbsd.org (Link -> mailto:da...@netbsd.org) > Dátum: 2018 július 30 14:36:27 Tárgy: What are all these core files? Címzett: netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) I have suddenly started getting all of these core files in my home directory. If I delete them they just show up the next day again. They don't even appear to relate to actual programs. They seem to be related to screensavers. Does anyone know where they are coming from? Running NetBSD current as of Jul 26, 2018 on AMD64. -rw--- 1 darcy wheel 9508368 Jul 28 07:17 unknownpleasures.core -rw--- 1 darcy wheel 10165584 Jul 28 08:07 kaleidocycle.core -rw--- 1 darcy wheel 10205528 Jul 28 08:27 dangerball.core -rw--- 1 darcy wheel 10584760 Jul 28 09:07 topblock.core -rw--- 1 darcy wheel 7439016 Jul 28 09:17 glmatrix.core -rw--- 1 darcy wheel 10369352 Jul 28 09:57 geodesicgears.core -rw--- 1 darcy wheel 7489000 Jul 28 10:17 blocktube.core -rw--- 1 darcy wheel 11776960 Jul 28 10:57 endgame.core -rw--- 1 darcy wheel 9569472 Jul 28 11:07 hypnowheel.core -rw--- 1 darcy wheel 11002480 Jul 28 11:17 glknots.core -rw--- 1 darcy wheel 9555472 Jul 28 12:08 boing.core -rw--- 1 darcy wheel 20509320 Jul 28 12:17 flurry.core -rw--- 1 darcy wheel 10249632 Jul 28 12:37 vigilance.core -rw--- 1 darcy wheel 11316576 Jul 28 14:17 moebiusgears.core -rw--- 1 darcy wheel 26364688 Jul 28 14:27 pipes.core -rw--- 1 darcy wheel 11668728 Jul 28 15:17 moebius.core -rw--- 1 darcy wheel 9566592 Jul 28 16:18 lockward.core -rw--- 1 darcy wheel 7418520 Jul 28 17:07 peepers.core -rw--- 1 darcy wheel 414720 Jul 28 17:17 pacman.core -rw--- 1 darcy wheel 10266840 Jul 28 18:33 pinion.core -rw--- 1 darcy wheel 10248120 Jul 28 18:53 hilbert.core -rw--- 1 darcy wheel 10517680 Jul 28 21:13 quasicrystal.core -rw--- 1 darcy wheel 7439576 Jul 28 23:03 glplanet.core -rw--- 1 darcy wheel 7465928 Jul 29 01:43 timetunnel.core -rw--- 1 darcy wheel 10813960 Jul 29 01:53 tangram.core -rw--- 1 darcy wheel 10839968 Jul 29 02:03 glsnake.core -rw--- 1 darcy wheel 14342784 Jul 29 03:54 splitflap.core -rw--- 1 darcy wheel 20497576 Jul 29 04:04 cubestorm.core -rw--- 1 darcy wheel 9595960 Jul 29 04:24 gleidescope.core -rw--- 1 darcy wheel 11605256 Jul 29 04:34 rubik.core -rw--- 1 darcy wheel 7449936 Jul 29 05:14 winduprobot.core -rw--- 1 darcy wheel 11542584 Jul 29 05:24 polytopes.core -rw--- 1 darcy wheel 11155648 Jul 29 06:24 splodesic.core -rw--- 1 darcy wheel 7414128 Jul 29 06:44 stairs.core -rw--- 1 darcy wheel 11765680 Jul 29 07:04 hypertorus.core -rw--- 1 darcy wheel 9873080 Jul 29 07:24 juggler3d.core -rw--- 1 darcy wheel 12119176 Jul 29 07:34 romanboy.core -rw--- 1 darcy wheel 10312928 Jul 29 07:44 sproingies.core -rw--- 1 darcy wheel 9565232 Jul 29 07:54 jigsaw.core -rw--- 1 darcy wheel 9955136 Jul 29 08:04 stonerview.core -rw--- 1 darcy wheel 12159432 Jul 29 08:14 projectiveplane.core -rw--- 1 darcy wheel 20554544 Jul 29 08:24 sierpinski3d.core -rw--- 1 darcy wheel 7477600 Jul 29 08:44 skytentacles.core -rw--- 1 darcy wheel 7414128 Jul 29 08:54 cage.core -rw--- 1 darcy wheel 19977424 Jul 29 09:05 voronoi.core -rw--- 1 darcy wheel 9525536 Jul 29 09:15 cubetwist.core -rw--- 1 darcy wheel 9602992 Jul 29 09:35 circuit.core -rw--- 1 darcy wheel 9549672 Jul 29 09:55 noof.core -rw--- 1 darcy wheel 10362496 Jul 29 10:05 menger.core -rw--- 1 darcy wheel 10042096 Jul 29 10:15 hexstrut.core -- D'Arcy J.M. Cain http://www.NetBSD.org/ IM:da...@vex.net
Does sysupgrade work only for subsequent releases?
Hi All, I tried to do a sysupgrade for my system which I thought to be 7.1.1 and wanted to upgrade to 7.1.2 (and afterwards 8.0). So I carried out a sysupgrade, rebooted and I was surprised when executing uname that I got back 7.1 instead of 7.1.2. It seems I didn't screw up anything but that's exactly the reason why I am asking: does sysupgrade only support upgrade to subsequent (follow up) releases? Don't get me wrong, that's not an issue for me. I just want to make sure that I indeed haven't screwed up anything and now I can carry out an upgrade to 7.1.1 first, then to 7.1.2 and finally to 8.0. Thanks for any hints in advance! Best regards, r0ller
user_ldt support for wine32 in 8.0?
Hi All, Just wanted to ask if user_ldt support got finally included in 8.0? I've always wanted to find some time for testing it with the RCs but never managed to do so. Now, as 8.0 is released and I anyway plan to upgrade it's high time to get my hands dirty:) Thanks®ards, r0ller
NetBSD on Amazon EC2
Hi All, Not sure if I missed any emails in this topic but I've just realised that my EC2 instance is running again -meaning that I could log on via ssh:) Best regards, r0ller
Re: NetBSD on Amazon EC2
Hi All, Mine doesn't work either and rebooting it again does not help:( Best regards, r0ller Eredeti levél Feladó: Abhinav Upadhyay < er.abhinav.upadh...@gmail.com (Link -> mailto:er.abhinav.upadh...@gmail.com) > Dátum: 2017 november 4 08:05:07 Tárgy: Re: NetBSD on Amazon EC2 Címzett: Eric Haszlakiewicz < haw...@gmail.com (Link -> mailto:haw...@gmail.com) > On Sat, Nov 4, 2017 at 2:49 AM, Eric Haszlakiewicz wrote: > Up until today I was running a NetBSD server on Amazon's EC2 service, > but then I restarted it because Amazon told me they'd be forcing a > restart soon anyway, to "deploy important updates". > Of course, when I tried to start it back up, it failed. Trying to > start a brand new instance using the available NetBSD AMIs > (NetBSD-i386-7.0-201511211930Z-20151121-1234 (ami-9f8090fe)) also > fails in a similar way, specifically with errors like: > > Failed to read /local/domain/0/backend/vbd/7994/2050/feature-barrier. > Failed to read /local/domain/0/backend/vbd/7994/2050/feature-flush-cache. > and > xc_dom_probe_bzimage_kernel: kernel is not a bzImage > > Do these errors ring a bell with anyone? > Does anyone have a working AMI that I can use? Yes, my instance also was rebooted last night (automatically by AWS for maintenance) and now unreachable. No idea how to get it back. (Didn't try creating new instance) - Abhinav
Re: package upgrade strategy
Hi All, Thanks again for all the answers in the topic! I read all of them but I cannot answer each in separate emails so I just picked the latest to continue the thread. As earlier mentioned I agree with the advantages of the pkgsrc based solutions and in the meantime I also found a nice summary of the different approaches at https://wiki.netbsd.org/pkgsrc/how_to_upgrade_packages/ (better later than never). However, I pursued the issue further to get a workaround (till I have time to rebuild things via pkgsrc) with the binary packages and I think I found something based on which I could build something. I only tried it manually and it seems to work but of course in case of more pkgs a script would be better to manage all this: -in case a package needs to be updated to a newer version, copy its shared libs to a specific directory (say soold) -record the old pkg name (together with the one that required updating it) in an sqlite db and the files copied to the soold directory -add soold directory to LD_LIBRARY_PATH if it's not yet added The solution would be better if it was somehow possible to revert the changes i.e. if I don't like the newly installed stuff, i.e. just downgrade the packages to their earlier versions which could be figured out from the db file that keeps track of the removed pkgs. However, afaik binary pkg downgrade is not possible either pkgin or by the pkg_* tools. I guess this is against quite a many things and how they're meant to be done in NetBSD but as a workaround this may come handy. What do you think? Can anyone forsee already a "design flaw" or whatever that'd prevent this from being feasible? Thanks & regards, r0ller Eredeti levél Feladó: Greg Troxel < g...@lexort.com (Link -> mailto:g...@lexort.com) > Dátum: 2017 szeptember 30 18:09:06 Tárgy: Re: package upgrade strategy Címzett: r0ller < r0l...@freemail.hu (Link -> mailto:r0l...@freemail.hu) > pkgsrc is designed, more or less, to have packages built consistently from the same source tree. You can often get away with having some packages be old. Other than the old packages not depending on or being dependencies of newer ones, you're on thin ice. If a package is not available in a newer branch, that could be because it was removed from pkgsrc, or because it didn't build. You can check out the sources and have a look. You can also look at the mail archives for pkgsrc-bulk and see what happened, and find the build logs. It may be that midori builds on NetBSD 8 (not yet out) but not 7, or 7 but not 6. This can be about the versions of X things in the base system, or it can be about compilers. So looking at the build logs for various systems can be useful. pkgsrc does not require you to choose between building from source and binary packages. But, you should use a source tree consistent with the binary packages you are using. Right now I think the latest binary packages for NetBSD are from 2017Q2. 2017Q3 exists in source form (and I'm behind on drafting an announcement), but NetBSD's package building machines are down due to data center work (we are grateful guests). I expect binary packages within a few weeks. Also, you can build your own binary packages, and use them with pkgin. You just have to make a summary file, which is easy. pkg_info -X *gz | bzip2 > pkg_summary.bz2 So if you have a fast machine, you can build, and install them on the slower machine (just rsync them and add a repositories.conf line). Packages without active upstreams are harder to maintain and can tend to run into problems. Midori's last release appears to be from August of 2015. That's not really really old, but it's long enough to suggest a possible issue. If you want to run an older build of midori, it's going to expect dependencies that are ABI-compatible, and this rapidly gets difficult. Overall, I think your best (but not easiest) path to success will be to use 2017Q3 sources, update everything you can via the forthcoming binary packages, and then to build midori from source, perhaps fixing the build. We would then want to commit the fixes, and for anything that belongs upstream to be comitted there and then have a new release. So far it looks like the patches in pkgsrc for midori are very minor and not obviously appropriate for upstream.
Re: package upgrade strategy
Hi All,
Thanks for all your answers (Alistair, Brad, Jeff, Jeremy)! They all seem to
point in one direction i.e. to use pkgsrc with which I don't have any problem.
I'm kind of used to it but I hoped that there's a way to avoid compiling
relatively big programs (like seamonkey) in a case when I just want to check
something out and get rid of it if it does not fit the bill. The scenario is
something like that I have a 10 years old desktop for our kids (some say this
word is negative for native English speakers, I'm not one of them so please,
forgive) to play online flash games, watch youtube videos, etc. with 3gb ram,
intel core2 conroe cpu with 1 core+igp and a conroe asrock board which all
serves pretty well at their age for this purpose -at least with NetBSD;) Midori
did fit the bill for everything they wanted till they bumped into codecombat
which doesn't work. So I wanted to quickly check out another browser and this
is exactly when I don't have time to compile anything:) As mentioned, by
checking out the earlier 7.0 Q1 repo helped with seamonkey and codecombat runs
fine in that but in such cases compiling each browser till I find the right one
is not an option. I mean, before seamonkey I also checked out epiphany and
firefox, which have the same bug as midori in that online game. Finding out
that seamonkey fits the bill took roughly 15 mins, but compiling three browsers
would have taken a lot more than that. Don't get me wrong, in general I agree
with all your suggestions, I just hoped that there's still a way to keep
different versions of pkgs in parallel.
Best regards,
r0ller
Eredeti levél
Feladó: Alistair Crooks < a...@pkgsrc.org (Link -> mailto:a...@pkgsrc.org) >
Dátum: 2017 szeptember 28 18:20:31
Tárgy: Re: package upgrade strategy
Címzett: Jeff_W < j...@sdf.org (Link -> mailto:j...@sdf.org) >
On 28 September 2017 at 08:40, Jeff_W wrote:
> % cd /pkgsrc/foo/pkg-A
> % sudo make clean && sudo make replace
>
> If the above breaks pkg-C:
>
> % cd /pkgsrc/foo/pkg-C
> % sudo make clean && sudo make clean-depends && sudo make update
Orthogonal to this discussion - pkgsrc was modified to use
just-in-time su in the early 2000s, and avoids interesting issues like
fetching sources as root. You are definitely encouraged to use it.
If you'd prefer to use sudo, rather than su, put this in your etc/mk.conf:
.if exists(${LOCALBASE}/bin/sudo)
SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c
.endif
Best,
Alistair
Re: package upgrade strategy
Hi Brad, I'd do that if it was possible (having the newest versions of all my packages) but as said, midori is not available any more in the 7.1 package repo so it cannot be upgraded (not even the same version of midori is available with just an updated list of dependencies) and if I upgrade icu (to version 59), midori starts complaining about not finding the earlier version of it (version 58). What if I just used pkg_add for icu-59? Or if I mark icu-58 non-autoremovable by pkgin, would the install of icu-59 leave icu-58 untouched? Best regards, r0ller Eredeti levél Feladó: Brad Spencer < b...@anduin.eldar.org (Link -> mailto:b...@anduin.eldar.org) > Dátum: 2017 szeptember 28 14:13:53 Tárgy: Re: package upgrade strategy Címzett: r0ller < r0l...@freemail.hu (Link -> mailto:r0l...@freemail.hu) > r0ller writes: > Hi All, > > I hope someone can give an answer to this question from a newbie: how can I > handle situations when an already installed package (say A) needs to be > upgraded due to a newly installed package (say B) as it's being a dependency > for it but another already installed package (say C) still needs the older > version of package A? Upgrading package C may be thought of as help but it > disappeared from the 7.1 package repo and as far as I could see it was last > present in 7.0_2017Q1. > > If anyone is interested in the details, package A is icu, package B is > seamonkey and package C is midori. What I did for now was that I changed > /usr/pkg/etc/pkgin/repositories.conf so that it points to 7.0_2017Q1 and > installed seamonkey from that repo as the versions are not that different > (seamonkey-2.46nb7 in 7.0_2017Q1 and seamonkey-2.46nb8 in 7.1) and it left > icu untouched. By the way, what kind of difference is indicated by the number > in the 'nb' suffix? Another question would be if it's possible to > keep different versions of a package installed? I know in case of shared libs > it may be tricky because of the symlinks but the runtime linker is not > looking for the symlink I hope but the versioned soname, right? Any hints are > welcome! > > Best regards, > r0ller Hello... I have been running pkgsrc for a very long time and you won't like my answer Basically, you don't try to do this with piecemeal updates. It honestly will be simpler to delete all of the packages, saving configs first, and reinstall the new versions. This may sound quite extreme, but if you have the situation you describe there will be too many other interdependencies to make anything else reasonable and sane, especially in the long run. There are techniques to make this much less harsh then it would be otherwise, and I can tell you about them if you want, but I really suspect you will find it much simpler to do as I suggested. -- Brad Spencer - b...@anduin.eldar.org - KC8VKS http://anduin.eldar.org - & - http://anduin.ipv6.eldar.org [IPv6 only]
package upgrade strategy
Hi All, I hope someone can give an answer to this question from a newbie: how can I handle situations when an already installed package (say A) needs to be upgraded due to a newly installed package (say B) as it's being a dependency for it but another already installed package (say C) still needs the older version of package A? Upgrading package C may be thought of as help but it disappeared from the 7.1 package repo and as far as I could see it was last present in 7.0_2017Q1. If anyone is interested in the details, package A is icu, package B is seamonkey and package C is midori. What I did for now was that I changed /usr/pkg/etc/pkgin/repositories.conf so that it points to 7.0_2017Q1 and installed seamonkey from that repo as the versions are not that different (seamonkey-2.46nb7 in 7.0_2017Q1 and seamonkey-2.46nb8 in 7.1) and it left icu untouched. By the way, what kind of difference is indicated by the number in the 'nb' suffix? Another question would be if it's possible to keep different versions of a package installed? I know in case of shared libs it may be tricky because of the symlinks but the runtime linker is not looking for the symlink I hope but the versioned soname, right? Any hints are welcome! Best regards, r0ller
Re: Pulseaudio & browsers - anyone got something ELSE working?
Hi, Midori with oss (default) works fine here -amd64, NetBSD 7.1- meaning youtube, even flash and streaming via vlc plugin;) Best regards, r0ller Eredeti levél Feladó: Swift Griggs < swiftgri...@gmail.com (Link -> mailto:swiftgri...@gmail.com) > Dátum: 2017 augusztus 14 00:07:49 Tárgy: Pulseaudio & browsers - anyone got something ELSE working? Címzett: netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) So, just a few years ago, we had to have flash (a security nightmare) setup and working to do things like play a youtube video. That sucked because you never knew when someone was going to bend flash over and 0wn your system. My best defense was click-to-play plugins so flash only loaded when I needed it. That worked, at least. It didn't play nice with the sound device and often wouldn't release it until I closed the browser, but it was servicable. Fast forward a few years when sites started to pull their head out of their flash and embrace HTML5 and the in-browser streaming video standards that had only been sitting there a decade or so. I'm thinking "YEA!" no more flash, right? Plus, Gecko browsers are open source, so they ought to embrace more than one sound output meathod, right? ESD, Jack1, Jack2, Arts, OSS, Alsa, NAS, etc.. WRONG. Well, I was half right. Sites like Youtube seem to work in just about all our Mozilla-based browsers (Seamonkey, Firefox*). However, there seems to be NO CHOICE about what kind of sound device to output to. It's Pulseaudio or nothing, I guess. Well, my opinion is that Pulseaudio is a miserable failure at everything it does, since that's been my experience. I've got three NetBSD systems it fails to work on altogether, or has severe drawbacks (like it won't release the sound device - EVER, or it won't work unless it's run as root, despite 666 perms on the audio devs). Plus, nobody seems to want to *fix* Pulseaudio. Anyone who complains is an idiot, according to Pottering or his ilk. Is there ANY way to get sound via a browser without Pulseaudio ? Today I resort to downloading with youtube-dl or something similar and playing the resulting file with mplayer because at least that gives me enough flexibility to choose my sound output and not break it (which Pulseaudio does OFTEN by grabbing the sound device, refusing to release it, and being unkillable even with kill -9 - must reboot after that). Is there any other option besides taking more abuse from Pulseaudio or doing the plugin-download-play-from-CLI option ? I'm using amd64 and i386 ports. Is there a version in the panopoly of firefox versions that has anything-other-than-pulseaudio as an option for sound output that can still do HTML5 video? Has anyone found a formula that works and doesn't ruin the sound device until the end of time just because I played one HTML5 video? -Swift I'm even using SeamlessRDP to run browsers from Windows boxes. Ugh. Bleh. Puh. but at least I know 'rdesktop' will release the sound device!
vlc plugin
Hi All, As I haven't found the vlc plugin either by pkgin or in pkgsrc (maybe my fault), I gave a try to build it (by cloning current) and it did succeed:) It was a mere configure-gmake-gmake install thingy. This is an npapi plugin in question (https://code.videolan.org/videolan/npapi-vlc) but it works pretty well (even full screen) in midori -just like the newest npapi flash plugin. Best regards, r0ller
Re: flash24 on 7.1(amd64)
Hi Coypu, Thanks, that worked! Although, I find it a bit misleading that there's an adobe-flash-player24 directory as well which is kind of tempting but the right one is adobe-flash-player what indeed works with flash25 as well:) Best regards, r0ller Eredeti levél Feladó: coypu@sdf.org (Link -> mailto:coypu@sdf.org) Dátum: 2017 május 20 11:27:34 Tárgy: Re: flash24 on 7.1(amd64) Címzett: r0ller < r0ller@freemail.hu (Link -> mailto:r0ller@freemail.hu) > On Sat, May 20, 2017 at 11:51:01AM +0200, r0ller wrote: > Hi Coypu, > > Thanks, that'd be great! However, when I tried it yesterday, the flash package appeared that in the list of pkgin was not found in the 7.1 repo when trying to install it:( Where shall I indicate it? It looks like the flash player package is marked as 'redistribution not permitted', so there won't be a binary package for it. You can fetch it yourself if you grab pkgsrc: cvs -danoncvs@anoncvs.NetBSD.org:/cvsroot co pkgsrc cd pkgsrc/*/adobe-flash-player make install
Re: flash24 on 7.1(amd64)
Hi Coypu, Thanks, that'd be great! However, when I tried it yesterday, the flash package appeared that in the list of pkgin was not found in the 7.1 repo when trying to install it:( Where shall I indicate it? Thanks & regards, r0ller Eredeti levél Feladó: coypu@sdf.org (Link -> mailto:coypu@sdf.org) Dátum: 2017 május 19 14:25:00 Tárgy: Re: flash24 on 7.1(amd64) Címzett: r0ller < r0ller@freemail.hu (Link -> mailto:r0ller@freemail.hu) > On Fri, May 19, 2017 at 04:14:47PM +0200, r0ller wrote: > Hi All, > > Has anyone managed to get flash24 up and running on 7.1? The previous npapi version of flash (which was flash10 or 11, can't recall) worked for me in midori which I dared to update to the new flash24 npapi plugin after upgrading to 7.1 but it doesn't work. Although, the?http://netbsd.org/releases/formal-7/NetBSD-7.1.html page mentions among the highlights "Linux compatibility improvements, allowing, e.g., the use of Adobe Flash Player 24." This is the thread where it was discussed and made to work: http://mail-index.netbsd.org/pkgsrc-users/2017/02/thread1.html#024432 I'm not sure of the exact details and whether it all made it before 7.1
flash24 on 7.1(amd64)
Hi All, Has anyone managed to get flash24 up and running on 7.1? The previous npapi version of flash (which was flash10 or 11, can't recall) worked for me in midori which I dared to update to the new flash24 npapi plugin after upgrading to 7.1 but it doesn't work. Although, the http://netbsd.org/releases/formal-7/NetBSD-7.1.html page mentions among the highlights "Linux compatibility improvements, allowing, e.g., the use of Adobe Flash Player 24." Thanks & regards, r0ller
Re: no console login after sysupgrade from 7.0 to 7.1
Hi Leonardo, Thanks, that was it!:) Best regards, r0ller Eredeti levél Feladó: Leonardo Taccari < leot@NetBSD.org (Link -> mailto:leot@NetBSD.org) > Dátum: 2017 május 15 13:27:06 Tárgy: Re: no console login after sysupgrade from 7.0 to 7.1 Címzett: netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) Hello r0ller! r0ller writes: > Hi All, > > I recently upgraded my 7.0 (amd64) to 7.1 using sysupgrade and although I was very cautious during the upgrade process when answering all the questions about the config file changes, I may have done something wrong. So currently I cannot logon as root via the console but interestingly enough I can logon as normal user to X (started by xdm) and in an X terminal I can switch to root using su which accepts the root's pw. If I try to log on to the console as root, the logon simply hangs -does not even ask for a password. I haven't tried the console logon as normal user but will do this evening. Till then, if anyone has any hint, I'd appreciate that! > > Thanks & regards, > r0ller I think that /etc/ttys was (accidently!) overwritten, probably you'll want something like that (in a unified format, please notice the 4th column `off' vs `on'): -ttyE1 "/usr/libexec/getty Pc" wsvt25 off secure -ttyE2 "/usr/libexec/getty Pc" wsvt25 off secure -ttyE3 "/usr/libexec/getty Pc" wsvt25 off secure +ttyE1 "/usr/libexec/getty Pc" wsvt25 on secure +ttyE2 "/usr/libexec/getty Pc" wsvt25 on secure +ttyE3 "/usr/libexec/getty Pc" wsvt25 on secure
no console login after sysupgrade from 7.0 to 7.1
Hi All, I recently upgraded my 7.0 (amd64) to 7.1 using sysupgrade and although I was very cautious during the upgrade process when answering all the questions about the config file changes, I may have done something wrong. So currently I cannot logon as root via the console but interestingly enough I can logon as normal user to X (started by xdm) and in an X terminal I can switch to root using su which accepts the root's pw. If I try to log on to the console as root, the logon simply hangs -does not even ask for a password. I haven't tried the console logon as normal user but will do this evening. Till then, if anyone has any hint, I'd appreciate that! Thanks & regards, r0ller
Re: NetBSD on embedded devices
Hi Jukka, Well, I'm no expert in that but you may be interested in this video presented by khorben and ask him: https://www.youtube.com/watch?v=lQdhHcMFpKo Best regards, r0ller Eredeti levél Feladó: Jukka Marin < jukka.marin@embedtronics.fi (Link -> mailto:jukka.marin@embedtronics.fi) > Dátum: 2017 május 15 11:39:07 Tárgy: NetBSD on embedded devices Címzett: netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) Hello List, I am considering using a stripped down NetBSD on an embedded system. The system would boot from an SSD disk and the disk would be read-only except for a separate data partition for sqlite. The system will have httpd, sqlite, probably sshd, application software (one or more binaries) but not much else. On hardware side, I will probably have an x86 with "enough" RAM (a few gigabytes). I'm wondering what would be the best way of system updates. I would like to have two separate system images, one that is active and running and another which can be updated. At boot time, the system would have to check which image to boot from. (Or maybe I could use chroot or some such to select the image to use.. or just mount one or the other.. or use a virtual machine or.. ;-) Does anyone have suggestions for a system like this? How to make updates (via http) foolproof? I might use something like this to start development: http://www.qotom.net/goods-129-Q190G4+4+LAN+Mini+PC.html Thanks! -jm
Re: NetBSD/usermode status
Hi Kamil, Thanks! I'll give it a try. Best regards, r0ller Eredeti levél Feladó: Kamil Rytarowski < n54@gmx.com (Link -> mailto:n54@gmx.com) > Dátum: 2017 április 30 11:01:59 Tárgy: Re: NetBSD/usermode status Címzett: r0ller < netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) > I was told that usermode kernel requires custom hosting kernel with the following module: sys/arch/usermode/modules/syscallemu To build the usermode kernel we need to perform something similar to: cd /usr/src/sys/arch/amd64/conf config GENERIC_USERMODE cd ../compile/GENERIC_USERMODE make depend make To run it: ./netbsd There is need to resurrect build of it. Currently there might be no support to run the usermode version without NetBSD kernel on host. On 29.04.2017 14:08, r0ller wrote: > Hi Greg, > > Yepp, that I know, that's why I asked it:) However, as the question is > rather about the overhead of running code in one or the other way I > asked jym at NetBSD who told that -besides the fact that only > measurement can tell- based on his gut feeling, usermode should have > less overhead if we don't take into account I/O. > > Best regards, > r0ller > > Eredeti levél > Feladó: Greg Troxel < gdt@lexort.com (Link -> mailto:gdt@lexort.com) > > Dátum: 2017 április 29 11:51:10 > Tárgy: Re: NetBSD/usermode status > Címzett: r0ller < r0ller@freemail.hu (Link -> mailto:r0ller@freemail.hu) > > > r0ller <r0ller@freemail.hu> writes: >> By the way, does anyone know what would be faster: NetBSD domU on >> NetBSD/Xen dom0 or NetBSD/usermode? > That's a good question, but if you want a reliable setup to actually run > something, I would recommend Xen. There are a lot of people running > NetBSD/Xen, and I am not aware of a lot of NetBSD/userland use.
Re: NetBSD/usermode status
Hi Greg, Yepp, that I know, that's why I asked it:) However, as the question is rather about the overhead of running code in one or the other way I asked jym at NetBSD who told that -besides the fact that only measurement can tell- based on his gut feeling, usermode should have less overhead if we don't take into account I/O. Best regards, r0ller Eredeti levél Feladó: Greg Troxel < gdt@lexort.com (Link -> mailto:gdt@lexort.com) > Dátum: 2017 április 29 11:51:10 Tárgy: Re: NetBSD/usermode status Címzett: r0ller < r0ller@freemail.hu (Link -> mailto:r0ller@freemail.hu) > r0ller <r0ller@freemail.hu> writes: > By the way, does anyone know what would be faster: NetBSD domU on > NetBSD/Xen dom0 or NetBSD/usermode? That's a good question, but if you want a reliable setup to actually run something, I would recommend Xen. There are a lot of people running NetBSD/Xen, and I am not aware of a lot of NetBSD/userland use.
Re: NetBSD/usermode status
Hi All, By the way, does anyone know what would be faster: NetBSD domU on NetBSD/Xen dom0 or NetBSD/usermode? Thanks®ards, r0ller Eredeti levél Feladó: r0ller < r0ller@freemail.hu (Link -> mailto:r0ller@freemail.hu) > Dátum: 2017 április 27 07:18:03 Tárgy: Re: NetBSD/usermode status Címzett: netbsd-users@netbsd.org < netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) > Hi, Ok, that's already something that gives hope:) But where can I find a howto guide about it? Nothing pops up either in the netbsd.org domain or outside that except the ones I mentioned. Regards, r0ller Eredeti levél Feladó: Kamil Rytarowski < n54@gmx.com (Link -> mailto:n54@gmx.com) > Dátum: 2017 április 26 12:15:53 Tárgy: Re: NetBSD/usermode status Címzett: r0ller < netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) > On 26.04.2017 10:59, r0ller wrote: > Hi All, > > Just wanted to quickly ask if anyone knows if NetBSD/usermode is > available at all for general use since the last discussion I found in > the mail archives about it dates back to 2011 and does not reveal > anything of its state while the most recent hit on google is a pdf from > 2013 > (http://www.13thmonkey.org/documentation/NetBSD/EuroBSD2012-NetBSD_usermode-paper.pdf) > revealing some info about it but it's not a howto or tutorial about it. > > Best regards, > r0ller Lately we fixed and improved ptrace(2) to resurrect usermode kernel. However beyond ptrace(2) I'm not aware about any related work. You need recent NetBSD-current to host it on NetBSD.
Re: NetBSD/usermode status
Hi, Ok, that's already something that gives hope:) But where can I find a howto guide about it? Nothing pops up either in the netbsd.org domain or outside that except the ones I mentioned. Regards, r0ller Eredeti levél Feladó: Kamil Rytarowski < n54@gmx.com (Link -> mailto:n54@gmx.com) > Dátum: 2017 április 26 12:15:53 Tárgy: Re: NetBSD/usermode status Címzett: r0ller < netbsd-users@netbsd.org (Link -> mailto:netbsd-users@netbsd.org) > On 26.04.2017 10:59, r0ller wrote: > Hi All, > > Just wanted to quickly ask if anyone knows if NetBSD/usermode is > available at all for general use since the last discussion I found in > the mail archives about it dates back to 2011 and does not reveal > anything of its state while the most recent hit on google is a pdf from > 2013 > (http://www.13thmonkey.org/documentation/NetBSD/EuroBSD2012-NetBSD_usermode-paper.pdf) > revealing some info about it but it's not a howto or tutorial about it. > > Best regards, > r0ller Lately we fixed and improved ptrace(2) to resurrect usermode kernel. However beyond ptrace(2) I'm not aware about any related work. You need recent NetBSD-current to host it on NetBSD.
NetBSD/usermode status
Hi All, Just wanted to quickly ask if anyone knows if NetBSD/usermode is available at all for general use since the last discussion I found in the mail archives about it dates back to 2011 and does not reveal anything of its state while the most recent hit on google is a pdf from 2013 (http://www.13thmonkey.org/documentation/NetBSD/EuroBSD2012-NetBSD_usermode-paper.pdf) revealing some info about it but it's not a howto or tutorial about it. Best regards, r0ller
Re: qemu-i386 segfault
Hi Martin, Yepp, that's it indeed. No matter if I compile it with static or dynamic linking, it just runs fine natively. I only get the problem -be it either compiled this or that way- when trying to get it work via qemu-i386. That's why I asked if anyone has tried ever getting some user space i386 stuff run on amd64 via qemu -and the question is still valid:) Thanks & regards, r0ller P.S.: By the way, is it worth taking another turn in the pkgsrc mailing list in case of pkg related issues like this or most of them read anyway this list as well? Eredeti levél Feladó: Martin Husemann < martin@duskware.de > Tárgy: Re: qemu-i386 segfault Címzett: r0ller < r0ller@freemail.hu > On Tue, Dec 20, 2016 at 05:19:26PM +0100, r0ller wrote: > Then I launch qemu as: > > qemu-i386 -L /usr/lib/i386 -bsd NetBSD hello32 > > and I get a segfault. If I check the core dump file with gdb, then it says: But the static binary just works when you run it natively? In that case quemu is doing something wrong. Martin
Re: qemu-i386 segfault
Hi Martin, I'm doing something wrong then. I compile hello world with: clang -static -O2 -m32 -o hello32 hello.c for static and for dynamic linking like clang -O2 -m32 -o hello32 hello.c ldd (when compiled with dynamic linking) and file give correct results for the output always. Then I launch qemu as: qemu-i386 -L /usr/lib/i386 -bsd NetBSD hello32 and I get a segfault. If I check the core dump file with gdb, then it says: Program terminated with signal SIGSEGV, segmentation fault. #0 0x<address> in strchr() from /usr/lib/libc.so.12 Shouldn't I see there /usr/lib/i386/libc? Thanks & regards, r0ller Eredeti levél Feladó: Martin Husemann < martin@duskware.de > Tárgy: Re: qemu-i386 segfault Címzett: r0ller < r0ller@freemail.hu > On Tue, Dec 20, 2016 at 03:52:52PM +0100, r0ller wrote: > Hi Martin, > > That works of course:) The point is to get it done via qemu-i386 and > that's what doesn't work. But as I mentioned it may require > 32bit libc which I currently don't have at hand so I'll need to > get it from an i386 NetBSD install. Well, it works and uses a 32bit libc. try: ldd a.out For me it says: a.out: -lc.12 => /usr/lib/i386/libc.so.12 If you just want to test qemu, why not link statically? Martin
Re: qemu-i386 segfault
Hi Martin, That works of course:) The point is to get it done via qemu-i386 and that's what doesn't work. But as I mentioned it may require 32bit libc which I currently don't have at hand so I'll need to get it from an i386 NetBSD install. Best regards, r0ller Eredeti levél Feladó: Martin Husemann < martin@duskware.de > Tárgy: Re: qemu-i386 segfault Címzett: r0ller < r0ller@freemail.hu > On Tue, Dec 20, 2016 at 12:48:37PM +0100, r0ller wrote: > I wanted to play around a bit with qemu-i386 user space emulation so > I just compiled a C hello world to 32bit elf binary and gave it a try > but all what I got was a segfault. Well, it just comes into my mind > that it may need a 32bit libc (or some other libs) :D Is that > assumption right? Has anyone tried such a thing on an amd64 NetBSD-7.0? Try: cc -O2 -m32 hello.c file a.out ./a.out output for me is: a.out: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /usr/libexec/ld.elf_so, for NetBSD 7.99.51, not stripped hello world (but I am trying on -current, not 7.0) Martin
qemu-i386 segfault
Hi All, I wanted to play around a bit with qemu-i386 user space emulation so I just compiled a C hello world to 32bit elf binary and gave it a try but all what I got was a segfault. Well, it just comes into my mind that it may need a 32bit libc (or some other libs) :D Is that assumption right? Has anyone tried such a thing on an amd64 NetBSD-7.0? Thanks & regards, r0ller
Re: how to build 32-bit pkgsrc on amd64
Hi Mike & Ryo, Thanks for the hints! However, if I got right what Coypu wrote, there's no workaround for the win32 USER_LDT issue on amd64 NetBSD. It's good to know anyway that there're easier ways to get 32 bit libs than building everything via pkgsrc. Thanks again! Best regards, r0ller Eredeti levél Feladó: Mike Pumford < mpumford@mudcovered.org.uk > Tárgy: Re: how to build 32-bit pkgsrc on amd64 Címzett: netbsd-users@netbsd.org On 28/11/2016 11:34, Ryo ONODERA wrote: > Hi, > > If you can use chroot, pkgsrc/pkgtools/libkver and i386 sets will > create i386 environment in chroot. > For Example, > > # kver -p i386 -r 7.0 chroot /usr/chroot/netbsd-7/root-i386 /bin/sh > > on NetBSD/amd64-current will provide you NetBSD/i386 7.0 environment > in chroot. > Maybe pkgsrc/pkgtools/pkg_comp will be useful too, > however I have not tested pkg_comp. > pkg_comp could well be the way to go. Takes a bit of configuration but I've used it to build packages for quite a few configurations all from a 7-STABLE/amd64 system. I've done the following: 6.x-STABLE/i386 7.x-STABLE/i386 as well as a couple of different configurations of 7.x STABLE amd64. It automates the creation of the chroot and the libkver setup for non-native environments. Mike
Re: how to build 32-bit pkgsrc on amd64
Hi, Thanks for the hints but if I got it right there's no way to get win32 progs/libs running on an amd64 NetBSD. Well, that's a pity but I'll stick to wine64 then. For all the browser plugins (what was mostly my focus of all win stuff) I'll "just" need to try to get pipelight working. Yet another challenge:) Thanks again! Best regards, r0ller Eredeti levél Feladó: coypu@SDF.ORG Tárgy: Re: how to build 32-bit pkgsrc on amd64 Címzett: r0ller < r0ller@freemail.hu > On Sun, Nov 27, 2016 at 09:36:11PM +0100, r0ller wrote: > Hi All, > > There's a guide on how to build 32-bit pkgsrc on amd64 ( https://mail-index.netbsd.org/pkgsrc-users/2008/12/16/msg008887.html ) which I tried yesterday but with no success. During building bootstrap, I get an error: > > "ld: Relocatable linking with relocations from format elf32-i386 to format elf64-x86-64 is not supported" > > I googled a bit but the only advice I found was to pass the -m32 option to the compiler. The only way to do that was to modify the bootstrap script so that it puts all the lines into mk.conf already in step 2, that were described in?the guide a step later (step 3). However, that didn't help either. Actually, what I'd like to achieve is to have the 32-bit libs for wine so that my wine64 installation can run both 32 and 64 bit programs. Is this the right way to do it? By the way, do I need to install then one of the netbsd32_compat libs for the 32bit libs? If so, then the latest one (netbsd32_compat40) seems to be targeting NetBSD4.0 compatibility -where do I find netbsd32_compat for 6.0 or 7.0? I feel a bit confused about the wine multilib setup and there isn't much info about how to do it on NetBSD. Any help is welcome:) > > Thanks & regards, > r0ller Since II've attempted to do t he same, I'll try to close you in on the details: Generally, there is no need for netbsd32_compat itself now, as the compat libraries already exist. You will however find that some stuff is still missing, and that's fontconfig from 32bit Xorg. An alternative I've used is unpacking a full NetBSD i386 install into a directory (say "/emul/netbsd32") and then using: cd /emul/netbsd32 mkdir usr/pkgsrc; cp /etc/resolv.conf etc/; cp /etc/mk.conf etc/ mount -t null /dev dev/; mount -t null /dev/pts dev/pts; mount -t null /usr/pkgsrc usr/pkgsrc chroot . /bin/sh This is sufficient fo rbuilding 32bit wine on a 64bit machine. It's probably possible to just create a package that does this for us. However... You will now run into the real problem of real wine* on netbsd/amd64, USER_LDT. Programs you will attempt to run will all fail (all 32bit wine uses LDT stuff), because a syscall returns an error message. >From my best understanding (and I am not very familiar with x86): LDT is 'User-settable local descriptor table', some way of storing data within a process that is different. It is only used by 32bit Windows (and no unixes). NetBSD/i386 has some code that allows using it, but NetBSD/amd64 disables it, There are some differences between i386 and amd64, which mean in its current state it will not even build (a kernel that supports this). The differences are not particularly great, but personally I found it challenging because I'm not familiar with x86. * I call it real wine because most Windows is 32bit, and even most 64bit stuff is hidden by a 32bit launcher, I imagine in order to give a friendly warning instead of outright crashing. Some people are using i386 + PAE to continue taking advantage of their amounts of RAM purely for wine.
how to build 32-bit pkgsrc on amd64
Hi All, There's a guide on how to build 32-bit pkgsrc on amd64 ( https://mail-index.netbsd.org/pkgsrc-users/2008/12/16/msg008887.html ) which I tried yesterday but with no success. During building bootstrap, I get an error: "ld: Relocatable linking with relocations from format elf32-i386 to format elf64-x86-64 is not supported" I googled a bit but the only advice I found was to pass the -m32 option to the compiler. The only way to do that was to modify the bootstrap script so that it puts all the lines into mk.conf already in step 2, that were described in the guide a step later (step 3). However, that didn't help either. Actually, what I'd like to achieve is to have the 32-bit libs for wine so that my wine64 installation can run both 32 and 64 bit programs. Is this the right way to do it? By the way, do I need to install then one of the netbsd32_compat libs for the 32bit libs? If so, then the latest one (netbsd32_compat40) seems to be targeting NetBSD4.0 compatibility -where do I find netbsd32_compat for 6.0 or 7.0? I feel a bit confused about the wine multilib setup and there isn't much info about how to do it on NetBSD. Any help is welcome:) Thanks & regards, r0ller
Re: emscripten & android ndk on NetBSD
Hi Greg&All, I agree that a native build would be the best but I'm no python expert (and the android ndk scripts are in python) and I got quickly stuck in understanding why the build script fails. Nevertheless, that's my long term goal as well. However, for the time being the workaround I described works just fine -today I even tried using the .so on the phone and it ran without any problem. I admit that the workaround for the fallocate is kludgy but it can be made a bit handier if 'cat fifo > file &' is called in the project build script before invoking the compiler or even another solution that I found at stackoverflow ( http://stackoverflow.com/questions/27817046/unzip-file-to-named-pipe-and-file ) that uses the buffer command to the achieve the same but it requires installing the buffer pkg. Concerning implementing fallocate, I just don't feel that confident about OS development as I'm rather an application developer so I guess I'll end up getting the ndk installer work natively sooner than writing a new linux syscall. Best regards, r0ller Eredeti levél Feladó: Greg Troxel < gdt@lexort.com > Tárgy: Re: emscripten & android ndk on NetBSD Címzett: r0ller < r0ller@freemail.hu > r0ller writes: > 2) I also tried building android ndk but the python buildscript failed > and I have currently no time for getting really into it so I just It would be nice to have the android tools working natively some day. > tried the linux installation making use of the NetBSD linux > compatibility layer. The only thing I had to change was the check for But mostly the linux emulation works well. > the host so that in case of NetBSD, the script evaluates it to > "linux":) I almost managed to build my project that way but in > the end when the linker tries to write the shared library object > I'm building, it fails with the error message "function not > implemented". I made a ktrace and kdump showed that the reason was > "unimplemented fallocate" for the linux syscall. Is it planned > to have that implemented? Anyway, just for the record: for the time In general, there isn't central planning, so it will get implemented when someone writes and tests it. If you are interested in helping, I would recommend that you start by building -current from sources. Things tend to get implemented there, and some get pulled up to the release branch, but most just end up in the next release. I see that posix_fallocate(3) is implemented in NetBSD 7, and that fallocate(2) is said to be nonportable. So, if you were to make a new linux syscall that just did posix_fallocate and ignored the flags, it wouldn't be the right thing but it might actually work in practice. If not you can look into what flags are used and start implementing cases of interest. > being I created a named pipe with the name of the targeted shared > library and when the build hangs waiting for someone to read the pipe, > I just cat the named pipe into a file in another terminal:) It seemed > to spit out the .so that way and the file command recognizes it as an > ARM shared library but I haven't tried it out yet if it really > works on the phone. I'll let you know later:) If it does work, that's super news. The workaround sounds a bit kludgy, but building ok with a feasible workaround is a pretty good situation.
emscripten & android ndk on NetBSD
Hi All, This is my first mail to this list and hopefully I found the right user group with my topics -let me know if not. 1) The first topic would be asking for a kind of review (if anyone is interested) of what I posted about building emscripten on NetBSD in the google group of emscripten: https://groups.google.com/d/msg/emscripten-discuss/2z1NZrX3sA8/jNy4ACiIBwAJ Actually, they offered their support for NetBSD in the buildscript once I sort out a few problems/questions they listed in their answer: https://groups.google.com/d/msg/emscripten-discuss/2z1NZrX3sA8/9sYySK32BgAJ However, as I'm not a NetBSD expert, I thought I'd first let my changes in the buildscript checked by someone more knowledgeable. So that'd be one task while the next task would be to discuss their questions like the one concerning vanilla llvm build. Just as a side note, till now my emscripten build works fine without any hickups. Unfortunately, I haven't had the time since my post to try if a vanilla llvm would pose any problems on NetBSD or why building nodejs failed back then. 2) I also tried building android ndk but the python buildscript failed and I have currently no time for getting really into it so I just tried the linux installation making use of the NetBSD linux compatibility layer. The only thing I had to change was the check for the host so that in case of NetBSD, the script evaluates it to "linux":) I almost managed to build my project that way but in the end when the linker tries to write the shared library object I'm building, it fails with the error message "function not implemented". I made a ktrace and kdump showed that the reason was "unimplemented fallocate" for the linux syscall. Is it planned to have that implemented? Anyway, just for the record: for the time being I created a named pipe with the name of the targeted shared library and when the build hangs waiting for someone to read the pipe, I just cat the named pipe into a file in another terminal:) It seemed to spit out the .so that way and the file command recognizes it as an ARM shared library but I haven't tried it out yet if it really works on the phone. I'll let you know later:) Thanks for any help in advance! Best regards, r0ller
