Hi, To disable acpi permanently: # config -ef /bsd ukc > disable acpi ukc > quit
One thing I haven’t been able to do yet is get shutdown(8) to work with acpi disabled, as it ends up rebooting automatically and -p or -h options do not respond as they normally do. acpi(4) explains that acpi is also responsible for powering off the machine. /dev/apm might be an alternative for power management. Anyone with a clue for shutting down the system with acpi disabled? Cheers Andy Le mer. 13 avr. 2022 à 22:25, <[email protected]> a écrit : > Thanks. Your email gave me hope. > I thought it would never be possible to run OpenBSD on the hardware. > > > This is expected from the install kernel, it doesn't have DDB. > > This is important information. I think it would've been nice to see > something about it on man pages, documentation, download page or > somewhere noticable. I have a feeling there is something but I totally > missed it. > > > Try boot -c at the boot loader prompt ... I would first try "disable > > acpiec" and "quit" and see if that boots. > > This worked. Gave me a "UKC" prompt. > > boot> boot -c > ... > UKC> disable acpiec > 257 acpiec* disabled > UKC> quit > ... > > Then it booted like usual to install-upgrade screen. > > > ...What's needed is a dump of the ACPI tables, which you could get > > from another OS, but it would be helpful to try and get it booted into > > OpenBSD as this could give more information. > > I don't know how to have a OpenBSD dual booting install so I tried once > and then cancelled and then realized my whole HD was formatted!!! Even > though I cancelled!! > > I tried installing to a flash drive and it didn't get detected (probably > due to disabling acpiec). Then tried to install on the install media > itself. It seemed to work. > > Wifi wouldn't turn on, so had to connect ethernet cable. Installed file > sets from a mirror (I entered http, [enter], ftp.jaist.ac.jp, enter ... > -x*, -game*, -comp* - in case someone else gets to this thread in > future) since the install media doesn't have the file sets anymore and > has been already formatted for the installation. > > It was getting hot when installing file sets. So I pointed a table fan > at it just in case. :) > > After installing I rebooted and tried disabling acpiec first and it > worked like before. I quickly got a dmesg and dmesg.boot. > > Then I tried booting again and again disabling one by one of these each > time to see what happens: > > acpi0: boots > acpitimer: boots into ddb prompt > acpihpet: boots into ddb prompt > acpiac: boots into ddb prompt > acpibat: boots into ddb prompt > acpibtn: boots into ddb prompt > acpicpu: boots into ddb prompt > acpicmos: boots into ddb prompt > acpidock: boots into ddb prompt > acpiec: boots > acpimadt0: boots into ddb prompt > acpimcfg: boots into ddb prompt > acpiprt: boots into ddb prompt > acpisbs: boots into ddb prompt > acpitz: boots into ddb prompt > acpiasus: boots into ddb prompt > acpisony: boots into ddb prompt > acpithinkpad: boots into ddb prompt > acpitoshiba: boots into ddb prompt > acpivideo: boots into ddb prompt > acpivout: boots into ddb prompt > acpipwrres: boots into ddb prompt > > For some reason ssh access is not working even though port 22 is open. > I'll try to get the outputs and post it to @bugs. My email is > also having trouble so don't know how soon I can post it. > > > CPU spec sheet says it could support it, but maybe it's disabled by > > BIOS. IIRc 64-bit mode on some of the Atoms does not work > > brilliantly anyway. > > Will check later. >
