Re: Recent web page changes
Hello Bob, Bob Proulx writes: > [...] > Looking at that page now I find that the netbsd-announce link is > missing a path part in the href url. > > netbsd-announce > > While it appears from the other two working links next to it that the > intent was that it should be this. > > netbsd-announce > > Could some kind soul with wiki change access priviledges double check > my poor typing transcription here and then correct that link? > > Thanks! :-) > [...] Nice catch, thank you very much for noticing and sharing it! I have just committed the fix as you have suggested!
Re: X server crashes after updating from 7.1 to 8.2
On Thu, Aug 06, 2020 at 09:12:23PM +0200, r0ller wrote: 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" This indeed helped me a lot! Thanks! Actually, when I received your email I was just upgrading to 9.0. I decided to first startx without this option and it happened that the experience with intel was the worst experience in all NetBSDs ever. Unlike NetBSD 7.1 that sometimes drawed strange patterns on the screen and NetBSD 8.2 that sometimes crashed X, in NetBSD 9.0 I get an utterly unusable X section, with mixed pixels, characters and mismatch between mouse pointer and window locations. Also, my dmesg was full of messages like that: ... [ 114.452971] 00017300 : 026e [ 114.452971] 00017304 : [ 114.452971] 00017308 : 0267 [ 114.452971] 0001730c : [ 114.452971] 00017310 : 0220 ... Is it a memory dump? I cannot see the beginning of the messages because they filled my entire dmesg buffer (I can compile a kernel with larger kern.msgbufsize if developers are interested in this). But 'Option "AccelMethod" "uxa"' solved everything like magic. I should RTFM before asking :-) I have this computer up for only 20 minutes, but I observe no crash for now. I'll let you know if something strange happens. 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. I'm not running any graphics intensive application to notice any difference and YouTube on Firefox plays fine, but let's see how far it goes. Thank you again.
Booting CDs in Qemu
Something simple I must be missing here. I downloaded the CD image of rEFInd from: http://sourceforge.net/projects/refind/files/0.12.0/refind-cd-0.12.0.zip/download Burned it to a CD and tried booting that CD on my PC. It doesn’t boot using BIOS, but it does boot using UEFI. So I know the CD is good. I saved the ISO file that I used to burn the CD. Tried booting the ISO file in qemu with: qemu-system-x86_64 -boot d -cdrom refind.iso -m 512 And got an error that it couldn’t boot with error code 0009. Ok this appears to mean that qemu tried booting it with a default BIOS boot which the CD isn’t configured for. The recommended solution is to either add the BIOS boot code to the CD or specify a OVMF/UEFI boot file to Qemu. Installed the OVMF package and tried booting again with: qmeu-system-x86_64 -bios /usr/pkg/share/ovmf/OVMFX64.bin —m 512 \ -boot d -cdrom refind.iso Got the Tianocore splash screen then the UEFI shell. Entered “exit” at the shell prompt and got a message "Graphics Console Started" and then nothing. Also tried the OVMFIA32.fd file with identical results. Adding “-vga std” to the command line didn’t change things either. For grins I added “-accel mvmm” to the command line and got the error: Failed to execute a VCPU So I have three questions: First, what am I missing to get this bootable CD to boot up in qemu? And second, is there a limitation in NVMM that prevents it from running this boot sequence? And finally, if I get the magic sequence that allows the CD to boot with qemu, is there a way of booting without getting the UEFI shell prompt? Thanks
Re: Booting CDs in Qemu
With: /usr/pkg/bin/qemu-system-x86_64 \ -device qemu-xhci \ -device usb-tablet \ -machine q35 \ -bios /usr/pkg/share/ovmf/OVMFX64.fd \ -m 4096 \ -k en-gb \ -smp 2 \ -accel nvmm \ -vnc :1 \ -drive format=raw,file=/dev/zvol/rdsk/pail/testu-new \ -net tap,fd=3 3<>/dev/tap1 \ -net nic \ -cdrom /iso/NetBSD-9.99.69-amd64.iso I was able to boot today's -current in efi mode, no problem. Obviously, I access the console over vnc. Chavdar On Thu, 6 Aug 2020 at 23:33, Robert Nestor wrote: > > Something simple I must be missing here. I downloaded the CD image of rEFInd > from: > > http://sourceforge.net/projects/refind/files/0.12.0/refind-cd-0.12.0.zip/download > > Burned it to a CD and tried booting that CD on my PC. It doesn’t boot using > BIOS, but it does boot using UEFI. So I know the CD is good. I saved the > ISO file that I used to burn the CD. > > Tried booting the ISO file in qemu with: > qemu-system-x86_64 -boot d -cdrom refind.iso -m 512 > > And got an error that it couldn’t boot with error code 0009. Ok this appears > to mean that qemu tried booting it with a default BIOS boot which the CD > isn’t configured for. The recommended solution is to either add the BIOS boot > code to the CD or specify a OVMF/UEFI boot file to Qemu. > > Installed the OVMF package and tried booting again with: > qmeu-system-x86_64 -bios /usr/pkg/share/ovmf/OVMFX64.bin —m 512 \ >-boot d -cdrom refind.iso > > Got the Tianocore splash screen then the UEFI shell. Entered “exit” at the > shell prompt and got a message "Graphics Console Started" and then nothing. > Also tried the OVMFIA32.fd file with identical results. Adding “-vga std” to > the command line didn’t change things either. > > For grins I added “-accel mvmm” to the command line and got the error: > Failed to execute a VCPU > > So I have three questions: First, what am I missing to get this bootable CD > to boot up in qemu? And second, is there a limitation in NVMM that prevents > it from running this boot sequence? And finally, if I get the magic sequence > that allows the CD to boot with qemu, is there a way of booting without > getting the UEFI shell prompt? > > Thanks --
Re: Booting CDs in Qemu
This helps a bit but still not quite there. Adding the “-device qemu-xhci -device usb-tablet -machine q35” gets me to the BIOS menu screen, but even after setting the boot device to the CDROM it still doesn’t boot up to the rEFInd screen. Also adding “-accel mvmm” didn’t hurt but didn’t get me any further in the boot. So I’m assuming that there’s something uniquely special about the rEFInd CDROM and how it’s configured for UEFI booting that doesn’t agree with Qemu? -bob On Aug 6, 2020, at 6:20 PM, Chavdar Ivanov wrote: > /usr/pkg/bin/qemu-system-x86_64 \ >-device qemu-xhci \ >-device usb-tablet \ >-machine q35 \ >-bios /usr/pkg/share/ovmf/OVMFX64.fd \ >-m 4096 \ >-k en-gb \ >-smp 2 \ >-accel nvmm \ >-vnc :1 \ >-drive format=raw,file=/dev/zvol/rdsk/pail/testu-new \ >-net tap,fd=3 3<>/dev/tap1 \ >-net nic \ >-cdrom /iso/NetBSD-9.99.69-amd64.iso
Re: Booting CDs in Qemu
On Fri, 7 Aug 2020 at 01:05, Robert Nestor wrote: > > Just dawned on me, I’m betting the NetBSD CD is configured to boot either via > BIOS or UEFI and Qemu is probably trying BIOS first since that’s its default. No, it definitely says that it is booting in EFI mode. if you interrupt it and drop to the command prompt, you can see the efivars. The graphics is also wsfb and the console looks like the NetBSD console after a UEFI boot; X -configure makes the relevant xorg.conf file (however, modesetting does not work, one has to change it to wsfb; also in my case - over VNC - the mouse driver has to be changed to 'ws', although even this way it works incorrectly). I tried to boot the rEFInd.iso file, I presume the same you've tried - of v. 0.12 - and got the same result as you - just the logo in the middle of the screen. I'll install manually rEFInd in the vm I just spun up to see if it can be recognized. > > -bob > > On Aug 6, 2020, at 6:20 PM, Chavdar Ivanov wrote: > > > With: > > > > > > /usr/pkg/bin/qemu-system-x86_64 \ > >-device qemu-xhci \ > >-device usb-tablet \ > >-machine q35 \ > >-bios /usr/pkg/share/ovmf/OVMFX64.fd \ > >-m 4096 \ > >-k en-gb \ > >-smp 2 \ > >-accel nvmm \ > >-vnc :1 \ > >-drive format=raw,file=/dev/zvol/rdsk/pail/testu-new \ > >-net tap,fd=3 3<>/dev/tap1 \ > >-net nic \ > >-cdrom /iso/NetBSD-9.99.69-amd64.iso > > > > > > I was able to boot today's -current in efi mode, no problem. > > Obviously, I access the console over vnc. > > > > Chavdar > > > > On Thu, 6 Aug 2020 at 23:33, Robert Nestor wrote: > >> > >> Something simple I must be missing here. I downloaded the CD image of > >> rEFInd from: > >> > >> http://sourceforge.net/projects/refind/files/0.12.0/refind-cd-0.12.0.zip/download > >> > >> Burned it to a CD and tried booting that CD on my PC. It doesn’t boot > >> using BIOS, but it does boot using UEFI. So I know the CD is good. I > >> saved the ISO file that I used to burn the CD. > >> > >> Tried booting the ISO file in qemu with: > >>qemu-system-x86_64 -boot d -cdrom refind.iso -m 512 > >> > >> And got an error that it couldn’t boot with error code 0009. Ok this > >> appears to mean that qemu tried booting it with a default BIOS boot which > >> the CD isn’t configured for. The recommended solution is to either add the > >> BIOS boot code to the CD or specify a OVMF/UEFI boot file to Qemu. > >> > >> Installed the OVMF package and tried booting again with: > >>qmeu-system-x86_64 -bios /usr/pkg/share/ovmf/OVMFX64.bin —m 512 \ > >> -boot d -cdrom refind.iso > >> > >> Got the Tianocore splash screen then the UEFI shell. Entered “exit” at > >> the shell prompt and got a message "Graphics Console Started" and then > >> nothing. Also tried the OVMFIA32.fd file with identical results. Adding > >> “-vga std” to the command line didn’t change things either. > >> > >> For grins I added “-accel mvmm” to the command line and got the error: > >>Failed to execute a VCPU > >> > >> So I have three questions: First, what am I missing to get this bootable > >> CD to boot up in qemu? And second, is there a limitation in NVMM that > >> prevents it from running this boot sequence? And finally, if I get the > >> magic sequence that allows the CD to boot with qemu, is there a way of > >> booting without getting the UEFI shell prompt? > >> > >> Thanks > > > > > > > > -- > > > --
Re: Booting CDs in Qemu
On Fri, 7 Aug 2020 at 01:11, Chavdar Ivanov wrote: > > On Fri, 7 Aug 2020 at 01:05, Robert Nestor wrote: > > > > Just dawned on me, I’m betting the NetBSD CD is configured to boot either > > via BIOS or UEFI and Qemu is probably trying BIOS first since that’s its > > default. > > No, it definitely says that it is booting in EFI mode. if you > interrupt it and drop to the command prompt, you can see the efivars. > The graphics is also wsfb and the console looks like the NetBSD > console after a UEFI boot; X -configure makes the relevant xorg.conf > file (however, modesetting does not work, one has to change it to > wsfb; also in my case - over VNC - the mouse driver has to be changed > to 'ws', although even this way it works incorrectly). > > I tried to boot the rEFInd.iso file, I presume the same you've tried - > of v. 0.12 - and got the same result as you - just the logo in the > middle of the screen. > > I'll install manually rEFInd in the vm I just spun up to see if it can > be recognized. I was able to install rEFInd manually in the efi partition of that NetBSD installation and boot it under OVMF (I rebooted the machine and just hit 'escape' in the VNC window, which got me to the EFI setup menu, where I located the relevant efi file and moved it to the top). Chavdar > > > > > -bob > > > > On Aug 6, 2020, at 6:20 PM, Chavdar Ivanov wrote: > > > > > With: > > > > > > > > > /usr/pkg/bin/qemu-system-x86_64 \ > > >-device qemu-xhci \ > > >-device usb-tablet \ > > >-machine q35 \ > > >-bios /usr/pkg/share/ovmf/OVMFX64.fd \ > > >-m 4096 \ > > >-k en-gb \ > > >-smp 2 \ > > >-accel nvmm \ > > >-vnc :1 \ > > >-drive format=raw,file=/dev/zvol/rdsk/pail/testu-new \ > > >-net tap,fd=3 3<>/dev/tap1 \ > > >-net nic \ > > >-cdrom /iso/NetBSD-9.99.69-amd64.iso > > > > > > > > > I was able to boot today's -current in efi mode, no problem. > > > Obviously, I access the console over vnc. > > > > > > Chavdar > > > > > > On Thu, 6 Aug 2020 at 23:33, Robert Nestor wrote: > > >> > > >> Something simple I must be missing here. I downloaded the CD image of > > >> rEFInd from: > > >> > > >> http://sourceforge.net/projects/refind/files/0.12.0/refind-cd-0.12.0.zip/download > > >> > > >> Burned it to a CD and tried booting that CD on my PC. It doesn’t boot > > >> using BIOS, but it does boot using UEFI. So I know the CD is good. I > > >> saved the ISO file that I used to burn the CD. > > >> > > >> Tried booting the ISO file in qemu with: > > >>qemu-system-x86_64 -boot d -cdrom refind.iso -m 512 > > >> > > >> And got an error that it couldn’t boot with error code 0009. Ok this > > >> appears to mean that qemu tried booting it with a default BIOS boot > > >> which the CD isn’t configured for. The recommended solution is to either > > >> add the BIOS boot code to the CD or specify a OVMF/UEFI boot file to > > >> Qemu. > > >> > > >> Installed the OVMF package and tried booting again with: > > >>qmeu-system-x86_64 -bios /usr/pkg/share/ovmf/OVMFX64.bin —m 512 \ > > >> -boot d -cdrom refind.iso > > >> > > >> Got the Tianocore splash screen then the UEFI shell. Entered “exit” at > > >> the shell prompt and got a message "Graphics Console Started" and then > > >> nothing. Also tried the OVMFIA32.fd file with identical results. > > >> Adding “-vga std” to the command line didn’t change things either. > > >> > > >> For grins I added “-accel mvmm” to the command line and got the error: > > >>Failed to execute a VCPU > > >> > > >> So I have three questions: First, what am I missing to get this > > >> bootable CD to boot up in qemu? And second, is there a limitation in > > >> NVMM that prevents it from running this boot sequence? And finally, if I > > >> get the magic sequence that allows the CD to boot with qemu, is there a > > >> way of booting without getting the UEFI shell prompt? > > >> > > >> Thanks > > > > > > > > > > > > -- > > > > > > > > -- > --
Re: Booting CDs in Qemu
Just dawned on me, I’m betting the NetBSD CD is configured to boot either via BIOS or UEFI and Qemu is probably trying BIOS first since that’s its default. -bob On Aug 6, 2020, at 6:20 PM, Chavdar Ivanov wrote: > With: > > > /usr/pkg/bin/qemu-system-x86_64 \ >-device qemu-xhci \ >-device usb-tablet \ >-machine q35 \ >-bios /usr/pkg/share/ovmf/OVMFX64.fd \ >-m 4096 \ >-k en-gb \ >-smp 2 \ >-accel nvmm \ >-vnc :1 \ >-drive format=raw,file=/dev/zvol/rdsk/pail/testu-new \ >-net tap,fd=3 3<>/dev/tap1 \ >-net nic \ >-cdrom /iso/NetBSD-9.99.69-amd64.iso > > > I was able to boot today's -current in efi mode, no problem. > Obviously, I access the console over vnc. > > Chavdar > > On Thu, 6 Aug 2020 at 23:33, Robert Nestor wrote: >> >> Something simple I must be missing here. I downloaded the CD image of >> rEFInd from: >> >> http://sourceforge.net/projects/refind/files/0.12.0/refind-cd-0.12.0.zip/download >> >> Burned it to a CD and tried booting that CD on my PC. It doesn’t boot using >> BIOS, but it does boot using UEFI. So I know the CD is good. I saved the >> ISO file that I used to burn the CD. >> >> Tried booting the ISO file in qemu with: >>qemu-system-x86_64 -boot d -cdrom refind.iso -m 512 >> >> And got an error that it couldn’t boot with error code 0009. Ok this >> appears to mean that qemu tried booting it with a default BIOS boot which >> the CD isn’t configured for. The recommended solution is to either add the >> BIOS boot code to the CD or specify a OVMF/UEFI boot file to Qemu. >> >> Installed the OVMF package and tried booting again with: >>qmeu-system-x86_64 -bios /usr/pkg/share/ovmf/OVMFX64.bin —m 512 \ >> -boot d -cdrom refind.iso >> >> Got the Tianocore splash screen then the UEFI shell. Entered “exit” at the >> shell prompt and got a message "Graphics Console Started" and then nothing. >> Also tried the OVMFIA32.fd file with identical results. Adding “-vga std” >> to the command line didn’t change things either. >> >> For grins I added “-accel mvmm” to the command line and got the error: >>Failed to execute a VCPU >> >> So I have three questions: First, what am I missing to get this bootable CD >> to boot up in qemu? And second, is there a limitation in NVMM that prevents >> it from running this boot sequence? And finally, if I get the magic sequence >> that allows the CD to boot with qemu, is there a way of booting without >> getting the UEFI shell prompt? >> >> Thanks > > > > -- >
Re: Booting CDs in Qemu
OK, thanks! I’m not sure I fully understand what you mean by “moved the relevant file to the top”. Do you mean you moved the \EFI\boot\bootx64.efi file to \EFI\bootx64.efi? There was an old reference I found in my search that seemed to imply this was a solution, but then I don’t see how the NetBSD CD booted. Doesn’t it’s bootx64.efi file live in \EFI\boot\bootx64.efi just like it does on the rEFInd CD? -bob On Aug 6, 2020, at 7:26 PM, Chavdar Ivanov wrote: > On Fri, 7 Aug 2020 at 01:11, Chavdar Ivanov wrote: >> >> On Fri, 7 Aug 2020 at 01:05, Robert Nestor wrote: >>> >>> Just dawned on me, I’m betting the NetBSD CD is configured to boot either >>> via BIOS or UEFI and Qemu is probably trying BIOS first since that’s its >>> default. >> >> No, it definitely says that it is booting in EFI mode. if you >> interrupt it and drop to the command prompt, you can see the efivars. >> The graphics is also wsfb and the console looks like the NetBSD >> console after a UEFI boot; X -configure makes the relevant xorg.conf >> file (however, modesetting does not work, one has to change it to >> wsfb; also in my case - over VNC - the mouse driver has to be changed >> to 'ws', although even this way it works incorrectly). >> >> I tried to boot the rEFInd.iso file, I presume the same you've tried - >> of v. 0.12 - and got the same result as you - just the logo in the >> middle of the screen. >> >> I'll install manually rEFInd in the vm I just spun up to see if it can >> be recognized. > > I was able to install rEFInd manually in the efi partition of that > NetBSD installation and boot it under OVMF (I rebooted the machine and > just hit 'escape' in the VNC window, which got me to the EFI setup > menu, where I located the relevant efi file and moved it to the top). > > Chavdar > >> >>> >>> -bob >>> >>> On Aug 6, 2020, at 6:20 PM, Chavdar Ivanov wrote: >>> With: /usr/pkg/bin/qemu-system-x86_64 \ -device qemu-xhci \ -device usb-tablet \ -machine q35 \ -bios /usr/pkg/share/ovmf/OVMFX64.fd \ -m 4096 \ -k en-gb \ -smp 2 \ -accel nvmm \ -vnc :1 \ -drive format=raw,file=/dev/zvol/rdsk/pail/testu-new \ -net tap,fd=3 3<>/dev/tap1 \ -net nic \ -cdrom /iso/NetBSD-9.99.69-amd64.iso I was able to boot today's -current in efi mode, no problem. Obviously, I access the console over vnc. Chavdar On Thu, 6 Aug 2020 at 23:33, Robert Nestor wrote: > > Something simple I must be missing here. I downloaded the CD image of > rEFInd from: > > http://sourceforge.net/projects/refind/files/0.12.0/refind-cd-0.12.0.zip/download > > Burned it to a CD and tried booting that CD on my PC. It doesn’t boot > using BIOS, but it does boot using UEFI. So I know the CD is good. I > saved the ISO file that I used to burn the CD. > > Tried booting the ISO file in qemu with: > qemu-system-x86_64 -boot d -cdrom refind.iso -m 512 > > And got an error that it couldn’t boot with error code 0009. Ok this > appears to mean that qemu tried booting it with a default BIOS boot which > the CD isn’t configured for. The recommended solution is to either add > the BIOS boot code to the CD or specify a OVMF/UEFI boot file to Qemu. > > Installed the OVMF package and tried booting again with: > qmeu-system-x86_64 -bios /usr/pkg/share/ovmf/OVMFX64.bin —m 512 \ > -boot d -cdrom refind.iso > > Got the Tianocore splash screen then the UEFI shell. Entered “exit” at > the shell prompt and got a message "Graphics Console Started" and then > nothing. Also tried the OVMFIA32.fd file with identical results. Adding > “-vga std” to the command line didn’t change things either. > > For grins I added “-accel mvmm” to the command line and got the error: > Failed to execute a VCPU > > So I have three questions: First, what am I missing to get this bootable > CD to boot up in qemu? And second, is there a limitation in NVMM that > prevents it from running this boot sequence? And finally, if I get the > magic sequence that allows the CD to boot with qemu, is there a way of > booting without getting the UEFI shell prompt? > > Thanks -- >>> >> >> >> -- >> > > > > -- >
/var/run mechanics
Greetings, We had recent power outage and noticed a problem about /var/run - few daemons could not start because there were no directories in /var/run. Like there is /var/run/named and there is no /var/run/opendkim, so opendkim will not run and i have to create manually. The only difference between present and non-present directories in /var/run seem the owner of non-present directories should be LDAP user (via nss_ldap), which apparently was unavailable at boot time when all the infrastructure was broken. I am not sure why /var/run have to be rebuilt upon every system start. If I am right - there is a problem of directories not created for yet non-available users. What could be done to avoid /var/run destruction or other way to avoid problems daemons. I can put something like "[[ ! -d /var/run/dir ]] && mkdir ..." in rc(8) prestart section but it seems to be ugly solution. -- Sincerely yours, Dima Veselov Physics R&D Establishment of Saint-Petersburg University
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.
amd-64 NetBSD9: Get laptop keyboard functions to work
Hi. I'm running amd-64 NetBSD 9 on a ASUS S200E laptop from 2012-2014. I was wondering how I would be able rebind (is that the word) some of the function keys to work (i.e the brightness). I'm looking at wsksymdef.h and I've read the man page for wsconsctl(8) but I can't figure it out. I would like to bind the brightness keys to 'xrandr'. Also is there a command equivalent to xrandr that I can use if I don't have X running? Thanks
Re: amd-64 NetBSD9: Get laptop keyboard functions to work
On Fri, Aug 07, 2020 at 03:38:51AM +, Ahi Brown wrote: > I would like to bind the brightness keys to 'xrandr'. First you have to find out if the key generates a key press/release event for the normal keyboard - that is not always the case (e.g. some notebooks require special ACPI key drivers to make the events available). To check, run xev and press the key. You should get something like: KeyPress event, serial 37, synthetic NO, window 0x301, root 0x3c4, subw 0x0, time 2350058, (173,63), root:(724,481), state 0x0, keycode 146 (keysym 0x1000ff14, apRepeat), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x301, root 0x3c4, subw 0x0, time 2350318, (173,63), root:(724,481), state 0x0, keycode 146 (keysym 0x1000ff14, apRepeat), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ... but probably (if you get anything at all) with a 0 keysum. If you get this, you can use xmodmap to bind a keysym and probably teach your window manager to map that keysym to some action. If you do not get anything, some ACPI binding will be needed (and I have never looked at those). Martin
