ACPI Error: Region SystemCMOS (ID= 5) has no handler
Hello NetBSDers, Below I've pasted in green error messages that spuriously came on the console. Are they of little consequence, or should they be reported somewhere? Kernel is 10RC6 GENERIC Regards, Henry from /var/log/messages: Apr 3 16:41:02 koti /netbsd: [ 1747.3716301] ACPI Error: No handler for Region [CMS0] (0x85dc5b0e1108) [SystemCMOS] (20221020/evregion-184) Apr 3 16:41:02 koti /netbsd: [ 1747.3716301] ACPI Error: Region SystemCMOS (ID= 5) has no handler (20221020/exfldio-320) Apr 3 16:41:02 koti /netbsd: [ 1747.3716301] ACPI Error: Aborting method \_SB.P CI0.LPCB.EC0._Q33 due to previous error (AE_NOT_EXIST) (20221020/psparse-580) Apr 3 17:11:03 koti /netbsd: [ 1747.3716301] ACPI Err autoconfiguration error: GPE query method _Q33 failed: AE_NOT_EXISTACPI Error: No handler for Region [CMS 0] (0x85dc5b0e1108) [SystemCMOS] (20221020/evregion-184) Apr 3 17:11:03 koti /netbsd: [ 3548.7103020] ACPI Error: Region SystemCMOS (ID= 5) has no handler (20221020/exfldio-320) Apr 3 17:11:03 koti /netbsd: [ 3548.7103020] ACPI Error: Aborting method \_SB.P CI0.LPCB.EC0._Q33 due to previous error (AE_NOT_EXIST) (20221020/psparse-580) Apr 3 17:41:04 koti /netbsd: [ 1747.3716301] ACPI Err autoconfiguration error: GPE query method _Q33 failed: AE_NOT_EXISTACPI Error: No handler for Region [CMS 0] (0x85dc5b0e1108) [SystemCMOS] (20221020/evregion-184) Apr 3 17:41:04 koti /netbsd: [ 5350.0589732] ACPI Error: Region SystemCMOS (ID= 5) has no handler (20221020/exfldio-320) Apr 3 17:41:04 koti /netbsd: [ 5350.0589732] ACPI Error: Aborting method \_SB.P CI0.LPCB.EC0._Q33 due to previous error (AE_NOT_EXIST) (20221020/psparse-580) Apr 3 18:11:06 koti /netbsd: [ 1747.3716301] ACPI Err autoconfiguration error: GPE query method _Q33 failed: AE_NOT_EXISTACPI Error: No handler for Region [CMS 0] (0x85dc5b0e1108) [SystemCMOS] (20221020/evregion-184)
Re: can't find visudo
Can't believe my own carelessness. Somewhere along the line pkg/sbin got dropped from $PATH. But it was worth it to expose my stupidity in order to be reminded of pkg_info. Thanks Alistair! 2024年4月1日(月) 4:31 Alistair Crooks : > > > > On Sun, 31 Mar 2024 at 07:00, Henry wrote: >> >> I installed sudo via pkgsrc. To make use of it, though, I need >> visudo, but I can't find it anywhere. There's a man page for visudo, >> but it doesn't say where it is. >> > To find out the files that were installed when you installed the package, you > can use the pkg_info command: > > > pkg_info -L sudo > Information for sudo-1.9.15p5: > > Files: > /usr/pkg/bin/cvtsudoers > /usr/pkg/bin/sudo > /usr/pkg/bin/sudoedit > /usr/pkg/bin/sudoreplay > /usr/pkg/include/sudo_plugin.h > /usr/pkg/lib/sudo/audit_json.la > /usr/pkg/lib/sudo/audit_json.so > /usr/pkg/lib/sudo/group_file.la > /usr/pkg/lib/sudo/group_file.so > /usr/pkg/lib/sudo/libsudo_util.la > /usr/pkg/lib/sudo/libsudo_util.so > /usr/pkg/lib/sudo/libsudo_util.so.0 > /usr/pkg/lib/sudo/libsudo_util.so.0.0.0 > /usr/pkg/lib/sudo/sudo_noexec.la > /usr/pkg/lib/sudo/sudo_noexec.so > /usr/pkg/lib/sudo/sudoers.la > /usr/pkg/lib/sudo/sudoers.so > /usr/pkg/lib/sudo/system_group.la > /usr/pkg/lib/sudo/system_group.so > /usr/pkg/man/man1/cvtsudoers.1 > /usr/pkg/man/man5/sudo.conf.5 > /usr/pkg/man/man5/sudo_logsrv.proto.5 > /usr/pkg/man/man5/sudo_logsrvd.conf.5 > /usr/pkg/man/man5/sudo_plugin.5 > /usr/pkg/man/man5/sudoers.5 > /usr/pkg/man/man5/sudoers_timestamp.5 > /usr/pkg/man/man8/sudo.8 > /usr/pkg/man/man8/sudo_logsrvd.8 > /usr/pkg/man/man8/sudo_sendlog.8 > /usr/pkg/man/man8/sudoedit.8 > /usr/pkg/man/man8/sudoreplay.8 > /usr/pkg/man/man8/visudo.8 > /usr/pkg/sbin/sudo_logsrvd > /usr/pkg/sbin/sudo_sendlog > /usr/pkg/sbin/visudo > /usr/pkg/share/doc/sudo/CONTRIBUTING.md > /usr/pkg/share/doc/sudo/CONTRIBUTORS.md > /usr/pkg/share/doc/sudo/ChangeLog > /usr/pkg/share/doc/sudo/HISTORY.md > /usr/pkg/share/doc/sudo/LICENSE.md > /usr/pkg/share/doc/sudo/NEWS > /usr/pkg/share/doc/sudo/README.md > /usr/pkg/share/doc/sudo/SECURITY.md > /usr/pkg/share/doc/sudo/TROUBLESHOOTING.md > /usr/pkg/share/doc/sudo/UPGRADE.md > /usr/pkg/share/examples/sudo/cvtsudoers.conf > /usr/pkg/share/examples/sudo/pam.conf > /usr/pkg/share/examples/sudo/sudo.conf > /usr/pkg/share/examples/sudo/sudo_logsrvd.conf > /usr/pkg/share/examples/sudo/sudoers > /usr/pkg/share/examples/sudo/syslog.conf > > Best, > Alistair
can't find visudo
Hope you are all well. I installed sudo via pkgsrc. To make use of it, though, I need visudo, but I can't find it anywhere. There's a man page for visudo, but it doesn't say where it is. TIA Henry
using screenblank
Hope everyone is doing well. Two questions concerning /usr/sbin/screenblank: 1) How do I get the text console screen to unblank/resume? The defaults, keyboard and mouse activity, don't work. I've also tried "-i /dev/wskbd1" and "-i /dev/wsmouse1" to no avail. All I've been able to do is login over tcp and kill -9 the screenblank process. (Thank goodness that works.) 2) Once I get 1) solved, what file would be a good place to put the screenblank command line so that the screenblanker will start its countdown at the login prompt, so I don't have to login to manually start screenblank? TIA Henry
Re: can't get the install USB to boot
Thank you all very much for continuing with this thread. I should have replied sooner to say that Martin's advice to use netbsd-INSTALL.gz was perfect for my situation where I wanted an entirely "clean", overwrite install (including /etc and /var), and had limitations on disk space. The install went extremely smoothly, and has only once issued a green-text error, which was not fatal in any way. I only wish I could do more rigorous testing to help get the release candidate ready for official release. Best, Henry 2024年3月26日(火) 2:01 Havard Eidnes : > > >> In order to test NetBSD-10.0, I copied the latest kernel to the root > >> directory of a [partially] working NetBSD-9.3 system. Absolutely > >> fantastic: super fast boot-up, AND the '/sbin/shutdown -p' glitch with > >> the 9.x series is fixed! THANK YOU developers for your hard work. > >> > >> Now, is there a way to update all the binary sets other than using the > >> install image sysinst? Or can you remind me how to get the install > >> disk to complete its boot? I REALLY want to get NetBSD 10 on this > >> machine. > >> > >> T(a million)IA > > The way I usually do upgrades is following this manual route, > which presumes you have already upgraded the kernel, and you are > already running the new kernel, and you have sufficient disk > space to extract the new code: > > - make a new "repository directory" to temporarily store the >install sets > > - fetch all the install sets you want to install into this >directory > > - Do not install the etc.tar.xz set directly, as that will reset >your configuration files (/etc/rc.conf, for instance) > >su >sh >cd / >for s in ; do > progress -f /repository-directory/$s.tar.xz tar xfzpB - >done > > - run "etcupdate -s /repository-directory/etc.tar.xz", and >follow the instructions, including running the postinstall >script as directed, and add any new required users and >groups. > > For good measure, reboot, so that all daemons start using the new > code. > > Regards, > > - Håvard
TPM: best to have it "hidden" or "available"?
In BIOS security settings, TPM on the HP Pavilion laptop I am working on is "hidden." I notice there is a NetBSD tpm driver, so I am wondering if it is safer security wise to have TPM available to the OS, or to leave it hidden. TIA Henry PS If you see this Martin, thank you very much for the instructions on how to upgrade with netbsd-INSTALL.gz. It worked perfectly and smoothly.
can't get the install USB to boot
I couldn' get the install image (NetBSD-10.0_RC6-amd64-install.img.gz) to boot. It keeps stopping at "uhid2 at uhidev0 report id 7: input=0, output=0 feature=256." I was plagued with this problem with the NetBSD-9 series, too, but I can't remember how I got around it. In order to test NetBSD-10.0, I copied the latest kernel to the root directory of a [partially] working NetBSD-9.3 system. Absolutely fantastic: super fast boot-up, AND the '/sbin/shutdown -p' glitch with the 9.x series is fixed! THANK YOU developers for your hard work. Now, is there a way to update all the binary sets other than using the install image sysinst? Or can you remind me how to get the install disk to complete its boot? I REALLY want to get NetBSD 10 on this machine. T(a million)IA Henry
Re: Which ARM SBC would work well with NetBSD?
I've been listening in, and I thank you all very much for your input. I have 0 experience with an SBC, but want to move to a low-power-consumption basic web and file server. Because of the battery options which would allow me to do without a UPS, I'm seriously considering the olimex a20-onlinuxino-lime2. Some questions from this newbie: o can I create a NetBSD bootable micro SD card, or does one have to use Debian or Android on these A-20 Olimex SBCs? o can I hook up a serial concole via a standard RS232 cable? o after the initial install of NetBSD, can I have the computer boot from a USB (preferably C-type, but standard type okay)? Or is it better to just get a board with the eMMC flash memory option and boot from that? o is there a cookbook-kind of howto document on installing NetBSD on ARM architecture SBCs? Many TIA, Henry 2023年3月6日(月) 20:18 Mayuresh : > > On Sun, Mar 05, 2023 at 12:40:57PM +0100, Benny Siegert wrote: > > I highly recommend the Pine64 devices. I have an A64-LTS, which has > > been rock-solid. The RockPro64 is the one with the highest > > performance. > > Thank you all for the responses - many of which are recommending pine64 > devices. > > I am considering Rock64 instead of RockPro64. Are there any reports on 1. > its stability and 2. NetBSD compatibility? > > -- > Mayuresh >
Re: how to turn off devices that monitor sensors
Well, you've taken me MUCH further than I've been for a year, and I appreciate your efforts to help tremendously! For the record, the architecture is amd64. Yes, both `reboot` and `halt` work perfectly with a current (9.99.96 and later) kernel. Neither worked with 9.2 STABLE. Maybe Netbsd 10 will be the magic release. Fingers crossed. Best regards, Henry 2022年6月21日(火) 19:05 Robert Elz : > > Date:Tue, 21 Jun 2022 10:29:54 +0900 > From:Henry > Message-ID: > > > | Thank you for the ideas. The manufacture date of this HP Pavillion > | Notebook 15-au123d was 07/01/2017. NetBSD is installed UEFI. > > That should all be new enough that ACPI should work fine, and if the > other OS's (well windows) can shut down, then I'd assume that entering > S5 state should make that happen for NetBSD as well. > > What other hardware exists in that system? > > Does reboot (or shutdown -r) work correctly? > > | I tried `boot -2' but the startup stopped at the following. I don't > | know how to proceed. > | boot device: > | root device: > > At that point you should be able to type ? and get a list > of possible root device values, pick the right one, and type it. > > But it is possible that without ACPI the disk isn't being seen by > NetBSD at all, and there will be nothing appropriate in that list. > > This is about as far as I can take it, I don't know the x86 architecture > or the MD x86 code nearly well enough to suggest anything else that you > can try. > > kre >
Re: how to turn off devices that monitor sensors
Thank you for the ideas. The manufacture date of this HP Pavillion Notebook 15-au123d was 07/01/2017. NetBSD is installed UEFI. I tried `boot -2' but the startup stopped at the following. I don't know how to proceed. boot device: root device: The machine works without any problem, including power-off shutdown, with Windows 10. I swapped out the harddisk that Win 10 was on with an SSD, onto which I installed NetBSD. Other than `/sbin/shutdown -p` not working (which however is fatal to my use of the machine as a remote workstation), things seem to be working well (with current, not under 9.2 STABLE). Henry 2022年6月14日(火) 21:04 Robert Elz : > > You might try "boot -2 netbsd" to disable ACPI completely, > in which case NetBSD would not be able to request ACPI S5 state > to shut down and power off (would need to use older BIOS > interfaces). > > If your system is an older one (HP model numbers mean nothing > to me) then it shoukd work OK without ACPI. > > You could also confirm whether other OS's are able to > power off that particular system (the test needs to be > of that exact system, as minor variations like what BIOS > rev is installed, what other hardware, and the BIOS > config all could alter the results. Installing other > systems should not be needed, "live" cd/dvd boots (or > USB stick) should be sufficient to test this. > > But testing NetBSD with ACPI disabled first is the quick > test to perform. > > kre
Re: how to turn off devices that monitor sensors
As you both predicted, disabling those drivers at boot didn't solve the problem; the machine still freezes at "acpi0: entering state S5". At least now I know the problem lies elsewhere. Thank you. I went through the BIOS settings, and I cannot see anything which would be forcing the system to stay on. Wake-on-lan is disabled. I even tried disabling TPM and BIOS security features. Any other ideas? The machine, an HP Pavilion Notebook 15-au123cl, seems so ordinary. I will not be able to use it as I had hoped, because I cannot power it down remotely. Very sad. Thank you all again. Henry 2022年6月12日(日) 19:39 Robert Elz : > > Date:Sun, 12 Jun 2022 18:18:26 +0900 > From:Henry > Message-ID: > > > | The machine freezes with the last messages to the console: > | acpi0: entering state S5 > > S5 is "off" (more or less), the system should be doing nothing except > waiting for someone (or something) to request that it be turned on again. > > It looks as if your system is one of those which NetBSD doesn't know how > to really shut down, or the BIOS has bugs which are preventing that from > happening. Do you have any "Wake on" type events configured in the BIOS? > If so, you might want to try disabling those and see if that might make > a difference - the BIOS might be keeping the system more alive that you > want so that wake on lan, or wake on usb keyboard, or something can work. > > | acpitz0: workqueue busy: updates stopped > | coretemp0: workqueue busy: updates stopped > | coretemp1: workqueue busy: updates stopped > > As Martin said, that's just noise, because the BIOS hasn't reset enough to > stop that stuff from interrupting, and is apparently keeping enough power > enabled to the ram (or at least caches) that enough of NetBSD is still > around to report that stuff, I agree with Martin, those are almost certainly > not related to your issue (they're a symptom caused by it, not causing it). > [I also would agree that there's potentially a driver bug, once the system > is off (or supposed to be off) nothing should be being processed at all.] > > kre > > ps: this might, or might not, make it direct from me to gmail, so I hope > you're subscribed to netbsd-users so you can get the reply that way. gmail > doesn't like me, and tends to bounce mail I send. > >
Re: how to turn off devices that monitor sensors
In my post to the port-amd64 list with subject "/sbin/poweroff not working (NetBSD-current)", I reported that `/sbin/shutdown -p` fails to poweroff the machine. The machine freezes with the last messages to the console: acpi0: entering state S5 acpitz0: workqueue busy: updates stopped coretemp0: workqueue busy: updates stopped coretemp1: workqueue busy: updates stopped I was thinking maybe if I turned those devices off before executing poweroff, maybe it would complete and the machine would turn off. Wishful thinking? Henry 2022年6月12日(日) 16:32 Martin Husemann : > > On Sat, Jun 11, 2022 at 06:10:43PM +0900, Henry wrote: > > How can I stop devices such as acpibat0, acpitz0 or coretemp0 that > > monitor environmental sensors? > > May I ask why you want to disable them? > > Martin
how to turn off devices that monitor sensors
How can I stop devices such as acpibat0, acpitz0 or coretemp0 that monitor environmental sensors? TIA Henry
Re: help with "SMTP error: 454 4.7.1 : Relay access denied"
Thanks, Greg. 2022年5月22日(日) 22:43 Greg Troxel : > Henry writes: > > [portions snipped] > > fetchmail: SMTP error: 454 4.7.1 : Relay access denied > > Reading first message addressed to > > lower.upper%axel.knet.ne...@lfknet-pop.xspmail.jp (22114 bytes) > > Messages not deleted from server. > [portions snipped] > Why do you have addresses with user%domain1@domain2? I haven't seen > that in use since the days of CHAOSnet/UUCP/BITNET/ARPANET mail > gateways. Oh, you would absolutely shudder if you knew the state of the majority of ISPs in Japan. Your question, however, lead me to the answer to how to get postfix to accept the mail. By adding `` smtpname "name@my.domain" `` to .fetchmailrc, the problem was solved. The following postfix configuration apparently was okay. > > In /etc/postfix/main.cf, add: > > smtpd_recipient_restrictions = > > permit_mynetworks, > > check_recipient_access hash:/etc/postfix/recipient_access, > > permit_sasl_authenticated, > > reject_unauth_destination > > Add "name@my.domain OK" to recipient_access; > > then, `postmap /etc/postfix/recipient_access` > > Stop and start postfix. Many thanks also go to Rhialto and Bruce for turning me on to the "mda" keyword. That hint helped me understand why sendmail (an mta) had been working for me, while I had initial problems with postfix. While I do use procmail, it would require more caution in taking mail from fetchmail than I feel confident with. I'll be looking into maildrop; sounds like a nifty program. Regards, Henry
help with "SMTP error: 454 4.7.1 : Relay access denied"
More than a decade too late, but I am finally moving from sendmail to postfix. Unfortunately, fetchmail doesn't work anymore; I get the following error (translated from Japanese): fetchmail: SMTP error: 454 4.7.1 : Relay access denied Reading first message addressed to lower.upper%axel.knet.ne...@lfknet-pop.xspmail.jp (22114 bytes) Messages not deleted from server. I'm testing with postfix version 2.11.4; fetchmail version 6.3.26. I've tried MANY variations of the following without luck. In /etc/postfix/main.cf, add: smtpd_recipient_restrictions = permit_mynetworks, check_recipient_access hash:/etc/postfix/recipient_access, permit_sasl_authenticated, reject_unauth_destination Add "name@my.domain OK" to recipient_access; then, `postmap /etc/postfix/recipient_access` Stop and start postfix. I've run out of ideas. Any help much appreciated. Henry
Re: is there a NOACPI GENERIC kernel for NetBSD-9.2_STABLE?
Thanks! Unfortunately, however, lots of errors (like "couldn't map pci interrupt") during the boot process, and the system stopped with these last two lines: boot device: root device: Still at a loss, Henry 2021年9月27日(月) 1:10 : > > Drop to boot prompt and type "boot -2". The -2 flag disables ACPI and > doesn't require a new build. > (A kernel without ACPI would require all ACPI code everywhere to be > conditional, and it might be a non-trivial effort to get there).
is there a NOACPI GENERIC kernel for NetBSD-9.2_STABLE?
I installed NetBSD-9.2_STABLE amd64 on an HP Pavilion Notebook, 15-au123cl. Previously I reported (NetBSD-9.1) that /sbin/shutdown was not working. Rebooting (-r switch) resulted in a hang at the line "uhid2 at uhidev0 report id 7: input=0, output=0 feature=256". This is still what happens with NetBSD-9.2. Trying to power off with `/sbin/shutdown -p` previously resulted in a hang with the last four lines: acpitz0: workqueue busy: updates stopped core1temp0: workqueue busy: updates stopped core2temp: workqueue busy: updates stopped acpibat0: workqueue busy: updates stopped Strangely and unexpectedly, however, the system started to hang much earlier in the shutdown process at the line: "acpi0: entering state S5". I can't imagine what I could have done to change its behavior, but the system consistently hangs now at that point. I remember many years ago there was a kernel on the install disk that had acpi turned off. There doesn't appear to be one now, but I think it would be worth trying one if a no-acpi kernel for NetBSD-9.2 is available somewhere. I've been trying to solve this problem for months now without success, so if anyone has other ideas on how to get over this hurdle, I am all ears. dmesg for GENERIC is appended below. Henry 1.00] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, [ 1.00] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, [ 1.00] 2018, 2019, 2020 The NetBSD Foundation, Inc. All rights reserved. [ 1.00] Copyright (c) 1982, 1986, 1989, 1991, 1993 [ 1.00] The Regents of the University of California. All rights reserved. [ 1.00] NetBSD 9.2 (GENERIC) #0: Wed May 12 13:15:55 UTC 2021 [ 1.00] mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC [ 1.00] total memory = 12173 MB [ 1.00] avail memory = 11793 MB [ 1.00] cpu_rng: RDSEED [ 1.00] rnd: seeded with 256 bits [ 1.00] timecounter: Timecounters tick every 10.000 msec [ 1.00] Kernelized RAIDframe activated [ 1.00] running cgd selftest aes-xts-256 aes-xts-512 done [ 1.00] timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 [ 1.03] efi: systbl at pa 8a29d018 [ 1.03] HP HP Pavilion Notebook (Type1ProductConfigId) [ 1.03] mainbus0 (root) [ 1.03] ACPI: RSDP 0x8AEFD014 24 (v02 HPQOEM) [ 1.03] ACPI: XSDT 0x8AEBB188 00011C (v01 HPQOEM SLIC-MPC HP 0113) [ 1.03] ACPI: FACP 0x8AEE2000 00010C (v05 HPQOEM SLIC-MPC HP 0004) [ 1.03] ACPI: DSDT 0x8AEBF000 01FEAD (v02 HPQOEM 8215 ACPI 0004) [ 1.03] ACPI: FACS 0x8AE5C000 40 [ 1.03] ACPI: UEFI 0x8AEFC000 000236 (v01 HPQOEM 8215 0001 HP 0004) [ 1.03] ACPI: UEFI 0x8AEFB000 42 (v01 HPQOEM 8215 0002 HP 0004) [ 1.03] ACPI: SSDT 0x8AEF3000 0072D9 (v01 HPQOEM 8215 1000 ACPI 0004) [ 1.03] ACPI: MSDM 0x8AEF2000 55 (v03 HPQOEM SLIC-MPC 0001 HP 0004) [ 1.03] ACPI: SSDT 0x8AEF1000 0004C8 (v02 HPQOEM 8215 1000 ACPI 0004) [ 1.03] ACPI: SSDT 0x8AEF 46 (v02 HPQOEM 8215 3000 ACPI 0004) [ 1.03] ACPI: TPM2 0x8AEEF000 34 (v03 HPQOEM 8215 HP 0004) [ 1.03] ACPI: SSDT 0x8AEEB000 00313E (v02 HPQOEM 8215 3000 ACPI 0004) [ 1.03] ACPI: SSDT 0x8AEE7000 0032B8 (v02 HPQOEM 8215 1000 ACPI 0004) [ 1.03] ACPI: ASF! 0x8AEE6000 A5 (v32 HPQOEM 8215 0001 HP 0004) [ 1.03] ACPI: ASPT 0x8AEE5000 34 (v07 HPQOEM 8215 0001 HP 0004) [ 1.03] ACPI: BOOT 0x8AEE4000 28 (v01 HPQOEM 8215 0001 HP 0004) [ 1.03] ACPI: DBGP 0x8AEE3000 34 (v01 HPQOEM SLIC-MPC 0001 HP 0004) [ 1.03] ACPI: HPET 0x8AEE1000 38 (v01 HPQOEM 8215 0001 HP 0004) [ 1.03] ACPI: APIC 0x8AEE BC (v03 HPQOEM 8215 0001 HP 0004) [ 1.03] ACPI: MCFG 0x8AEDF000 3C (v01 HPQOEM 8215 0001 HP 0004) [ 1.03] ACPI: SSDT 0x8AEBE000 0001BC (v02 HPQOEM 8215 1000 ACPI 0004) [ 1.03] ACPI: LPIT 0x8AEBD000 94 (v01 HPQOEM 8215 HP 0004) [ 1.03] ACPI: WSMT 0x8AEBC000 28 (v01 HPQOEM 8215 HP 0004) [ 1.03] ACPI: SSDT 0x8AEBA000 00029F (v02 HPQOEM 8215 ACPI 0004) [ 1.03] ACPI: SSDT 0x8AEB9000 000346 (v01 HPQOEM 8215 ACPI 0004) [ 1.03] ACPI: SSDT 0x8AEB5000 003002 (v02 HPQOEM 8215 1000 ACPI 0004)
can' seem to mount a usb memory stick
Hi and TIA for help, When I plugged the usb stick in, it seemed to be recognized correctly as sd0. I tried to mount it with: # mount -t msdos /dev/sd0a /mnt but got the error: mount_msdos: /dev/sd0a on /mnt: Device not configured What am I doing wrong? Henry
Re: reboot hangs at "uhid2 at uhidev9 report id 7 ..."
Very sorry, that should have been "uhidev0" (not "9"). "uhidev0" identifies itself as: uhidev0 at uhub1 port 8 configuration 1 interface 0 uhidev0: eGalax Inc. (0xeef) eGalaxTouch EXC3000-0367-44.01.00 (0xc04d), rev 2.01/67.02, addr 3, iclass 3/1 uhidev0; 7 report ids I guess that is the touchpad. However, the problem, I think, is elsewhere. After letting the computer sit for two days with the power off, I powered it on, and the system came up normally, and with a login prompt. I could login as "root" as expected. It seems that rebooting (/sbin/shutdown -r) caused the problem described in my original post. When I do that, the system tries to reboot, but hangs at the "uhid2 at uhidev0" line. Additionally, "/sbin/shutdown -p" is not working. The machine starts to shut down, but I get the following: acpibat0: workqueue busy: updates stopped acpitz0: workqueue busy: updates stopped core1temp0: workqueue busy: updates stopped core2temp: workqueue busy: updates stopped The system hangs on that last line, and the computer never shuts down. Do you think I should start a new thread on the port-amd64 list? Thanks much, Henry 2021年5月6日(木) 1:55 Rhialto : > > On Wed 05 May 2021 at 15:18:03 +0900, Henry wrote: > > I recently installed 9.1 on a HP 15-au123cl. The install seemed to go > > fairly smoothly, and I was able to get the sets via ftp. > > > > The system kept booting into single user mode, but searching around I > > finally figured out that I needed to edit /etc/rc.conf. I thought I > > had successfully changed to rc_configured=YES. > > The installer is also supposed to do that for you, so there must have > been something weird there. > > > However, since then, whenever I try to boot the machine it hangs at: > > [ 4.7432765] uhid2 at uhidev9 report id 7: input=0, output=0 feature=256 > > (the numbers in brackets change; I have seen 7582388, 225.834047, > > 4.9366070). > > There seems to be nothing else to do other than to hold down the power > > button and shut the computer off. > > The "[ 4.7432765]" is a timestamp so it's not so strange that it > varies a bit. > > "uhid" is a "human interface device", usually a mouse or keyboard. There > should be a line earlier in the output, starting with "uhidev9:" which > tells you what sort of device it is. For example, for my mouse: > > uhidev0: Logitech (0x46d) USB Optical Mouse (0xc05a), rev 2.00/54.00, addr 1, > iclass 3/1 > > > What can I do to get the computer to boot? (Or, did the computer > > suddenly give out on me?) > > Hopefully that will tell you which device it is, and you can try to > unplug it and then boot. Sometimes devices like iPhones present > themselves as multiple devices to the computer. The high number (9) may > be explained by something like that. > > > Henry > -Olaf. > -- > ___ Q: "What's an anagram of Banach-Tarski?" -- Olaf "Rhialto" Seibert > \X/ A: "Banach-Tarski Banach-Tarski." -- rhialto at falu dot nl
reboot hangs at "uhid2 at uhidev9 report id 7 ..."
I recently installed 9.1 on a HP 15-au123cl. The install seemed to go fairly smoothly, and I was able to get the sets via ftp. The system kept booting into single user mode, but searching around I finally figured out that I needed to edit /etc/rc.conf. I thought I had successfully changed to rc_configured=YES. However, since then, whenever I try to boot the machine it hangs at: [ 4.7432765] uhid2 at uhidev9 report id 7: input=0, output=0 feature=256 (the numbers in brackets change; I have seen 7582388, 225.834047, 4.9366070). There seems to be nothing else to do other than to hold down the power button and shut the computer off. What can I do to get the computer to boot? (Or, did the computer suddenly give out on me?) TIA Henry
hosts(5) manpage update
Hi all, I wasn't sure which mailing list to send this to, but I figured this would get a fair number of eyes. The hosts(5) manpage still includes a section that dates from 1983(!) and while interesting from an historic perspective is probably very confusing to any modern user: "This file may be created from the official host data base maintained at the Network Information Control Center (NIC), though local changes may be required to bring it up to date regarding unofficial aliases and/or unknown hosts. As the data base maintained at NIC is incomplete, use of the name server is recommended for sites on the DARPA Internet." Perhaps the time has come for its removal. -Henry
Re: utf-8, Englush, Japanese
I cannot really answer your question since I use PuTTY on a Win10 PC to access my NetBSD workstation in text mode only. In my .cshrc file I have: setenv LANG ja_JP.UTF-8 setenv LC_CTYPE ja_JP.UTF-8 setenv LC_MESSAGES ja_JP.UTF-8 #setenv LC_ALL ja_JP.UTF-8 In other words I don't touch LC_ALL because there seem to be applications important to me that don't like it being set. Henry 2020年11月10日(火) 3:07 Steve Blinkhorn : > > What is current best practice for working with UTF-8 encoding? I have > a project which requires editing of mixed English and Japanese text. > Setting LC_ALL to en_GB.UTF-8 cause the warning: > > Warning: locale not supported by C library, locale unchanged > > with every X-related command, but I do not know which C library. Vim > fails to display Japanese characters in an xterm, but will if it is > called via a uxterm, which seems to have no manpage for NetBSD. > > -- > Steve Blinkhorn >
help using /usr/bin/netpgp
I'm not having any luck using /usr/bin/netpgp to verify the integrity of downloaded files. I wasn't sure from the man page what the correct command line would be, but using the format I used in the past with gpg, `netpgp --verify gnupg-2.2.1.tar.bz2.sig gnupg-2.2.1.tar.bz2` failed with: "gnupg-2.2.1.tar.bz2.sig": verification failure: 0 invalid signatures, 2 unknown signatures "gnupg-2.2.1.tar.bz2": No signatures found - is this a signed file? I thought maybe it failed because I hadn't imported a public key yet, so I downloaded the public keys and named one of them "publickey.txt". I then ran `netpgpkeys --import-key publickey.txt`, but got: Can't free 545 (0x221) Can't free 547 (0x223) Error: Subpacket too long Can't free 545 (0x221) Error: Subpacket too long /usr/src/crypto/external/bsd/netpgp/lib/netpgp/../../dist/src/lib/packet -parse.c:1793: PGP_E_PROTO_UNKNOWN_SS, Unknown signature subpacket type (33) /usr/src/crypto/external/bsd/netpgp/lib/netpgp/../../dist/src/lib/packet -parse.c:1793: PGP_E_PROTO_UNKNOWN_SS, Unknown signature subpacket type (35) /usr/src/crypto/external/bsd/netpgp/lib/netpgp/../../dist/src/lib/packet -parse.c:1793: PGP_E_PROTO_UNKNOWN_SS, Unknown signature subpacket type (33) Cannot import key from file publickey.txt Help on how to proceed much appreciated. TIA Henry
installing on "extended partition" while preserving OS X
I'm trying to install NetBSD 7.0.2 on a MacBook Pro, but keep OS X. It should be possible, but trying to install from the install CD TOTALLY destroyed the guid structure. Fortunately, I was able to reconstruct the partition structure, although I ended up having to re-format the EFI partition using newfs_msdos in OS X Terminal. Although I lost the Apple *.efi, I was able to re-install the rEFInd bootloader, which I was planning on using anyway. After restoring it, the partion scheme looks like the following (gpt show disk0): start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 6 40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B 409640 100555104 2 GPT part - 48465300--11AA-AA11-00306543ECAC 1009647441269536 3 GPT part - 426F6F74--11AA-AA11-00306543ECAC 102234280 139898408 4 GPT part - 49F48D5A-B10E-11DC-B99B-0019D1879648 2421326887815024 5 GPT part - 49F48D32-B10E-11DC-B99B-0019D1879648 249947712 121935 250069647 32 Sec GPT table 250069679 1 Sec GPT header Partition index 1 is EFI, 2 is OS X, 3 is recovery disk, 4 is NetBSD ffs, and 5 is NetBSD swap. Weird is, rEFInd seems to recognize the NetBSD partition, but if I click on the NetBSD icon, I get the message: "No bootable device -- insert boot disk and press any key". Judging from the font and white text on black, I suspect the message is coming from [something] NetBSD. I'm pretty sure all the binary sets were installed on the specified partition 4, and more than likely are intact. Is there some way to get NetBSD to boot without messing with the EFI partition? (Or even using the EFI partition, but not formatting it or changing the type from efi.) Thanks, Henry
