|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
Difficulties disabling acpitz in the kernel
I am trying to install OpenBSD 7.0 on a Dell Wyse 3040 (Intel Atom x86_64, eMMC). Rebooting after the install hangs at the line:
acpitz on acpi0 Using boot -c results in the usb keyboard input not working at the UKC> prompt. I can disable acpitz on a kernel running in a virtualmachine and copy the kernel over, but then it hangs at the prompt: root device: Again with no usb keyboard input (boot -a results in the same). I've tried different usb ports with two different functioning USB keyboards which work at the boot> prompt and during install, just not at the UKC>/root device: prompts. PS/2 keyboard input and serial input are not available on this hardware. The root device is eMMC, which is probably why the kernel built in the virtual machine can't find the path/UID of the root device. In the BIOS, there don't appear to be any options related to enabling/disabling ACPI or temperature monitoring. Also nothing relating to a "legacy" USB mode. Is there another way to install a kernel on this machine with acpitz disabled? Last edited by jdpuller; 22nd October 2021 at 09:27 AM. Reason: clarificaiton |
|
||||
Hello, and welcome!
In the public NYCBUG database, I can find a dmesg for a Wyse 5060, but not a 3040: https://dmesgd.nycbug.org/index.cgi?do=view&id=5639 You might want to post your query to the misc@ mailing list -- it is a much larger community of users. |
|
||||
Quote:
You might try booting bsd.rd and immediately drop to the shell to create /etc/bsd.re-config with the following content: Code:
disable apitz The only problem is, I don't know if this is supported inside bsd.rd. Might be worth a try, though. The file itself works, I just tested it on an old i386 on which I installed 7.0 yesterday. Prior to 7.0 I used to disable a certain driver manually during each boot, due to some kernel error msgs. With the file in place and after KARL has finished reboot works automaticaly with a modified kernerl without requiring manual intervention. |
|
|||
Thanks for the suggestion. I had previously tried putting the disable command in bsd.re-config, without luck. It appears I'm still doing something incorrectly:
on boot it still hangs at acpitz0 on acpi0, as if the /etc/bsd.re-config had no effect. I'm fairly certain disable acpitz is correct, as that is verbatim what was modified in the virtualmachine kernel to get up to the root device prompt. Re-reading re-config(5), I cant figure out where I'm going wrong. |
|
||||
Yeah, that's what I was suspecting.
Quote:
See the section KERNEL BUILDING in the manpage: Quote:
|
|
|||
That was my impression as well, that bsd.re-config and config both require a normal boot (not bsd.rd). But as a novice, I wasn't sure.
Since a ramdisk boot is possible on this hardware, there is a lot of room for optimism that a normal boot is within reach. I was hoping there might be a way to disable modules/change the root device in the ramdisk, either during or post-install before attempting to build a custom kernel. set howto in boot(8) also looks promising, but I am not well versed enough in OpenBSD to know where to start. I don't know the available options are, or how to find them, short of digging through the source code. |
|
||||
Normally, the kernel will locate the "a" partition on the booted disk and assign it as the root filesystem. You can alter this with
boot> -a , which will cause the kernel to prompt for the drive and partition to use as the root filesystem. See the -a option in boot(8).
|
|
|||
I had tried that, couldn't type anything at the resulting prompt.
|
|
|||
Success!
I had mentioned that I was modifying/copying over a kernel from a (virtualbox) virtual machine. By default, virtualbox uses an IDE controller for openbsd machines, which leads to /dev/wd* disk names, whereas the eMMC on this hardware gets /dev/sd* names [0]. Customizing a kernel on a virtual machine with an AHCI controller and copying it over was successful. Detailed instructions for posterity: (on Wyse hardware) 1. Install OpenBSD. Hardware is EFI only (not MBR) 2. Reboot, at the boot prompt, enter: bsd.rd 3. Drop into (S)hell (virtualbox virtual machine) 4. Create an openbsd virtual machine [1] 5. Change system > processor to 2 to get the OpenBSD installer to build a mult-core kernel 6. Change storage > controller from IDE to AHCI (SATA) in order to get correct root device naming 7. Attach openbsd installer image, and boot virtual machine to install OpenBSD 8. When finished, reboot into normal kernel 9. After logging in, run: $ config -e -o /bsd.new /bsd ukc> disable acpitz ukc> quit 10. Attach a usb thumb drive (tested with FAT32). Replace X below with what the drive was enumerated with. run: $ mkdir /mnt2 $ mount_msdos /dev/sdXc /mnt2 $ cp -a /bsd.new /mnt2/bsd.new $ umount /mnt2 11. Remove usb key (on Wyse hardware) 12. Should still be in the shell from step 3. Plug in the usb key 13. You should see the usb key being recognized. Replace X in the commands below with what the drive was enumerated with, run $ cd /dev $ sh MAKEDEV sdX $ mount_msdos /dev/sdXc /mnt2 $ cp -a /mnt2/bsd.new /bsd $ umount /mnt2 $ reboot Done [0] https://www.openbsd.org/faq/faq14.html [1] Confirmed with both EFI and MBR virtualbox machines. MBR is easier to set up and is the virtualbox default. _If_ you want to use EFI to match the Wyse hardware, additionally modify the virtual machine by setting: system > Enable EFI A bootable vdi image also needs to be created from the .img installer, the .iso doesn't work with EFI as of this writing: $ VBoxManage convertdd install70.img install70.vdi --format VDI this image should be attached to the SATA controller that has the .vdi for the install. If the install disk doesn't boot automatically, load the installer by navigating fs1:\efi\... (note the backslashes) Last edited by jdpuller; 24th October 2021 at 02:33 PM. |
Tags |
acpitz, emmc, openbsd |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
about the kernel | bsdcord | OpenBSD Security | 11 | 12th May 2019 05:40 PM |
Yoga2 disabling touchscreen | scottro | OpenBSD Installation and Upgrading | 15 | 16th October 2016 02:40 AM |
Disabling Services Not Needed | EverydayDiesel | OpenBSD Security | 10 | 25th January 2010 01:20 PM |
disabling ctrl-c | malindang | FreeBSD General | 3 | 27th June 2008 12:06 AM |
Spin locks and interrupts disabling | n4uti1us | FreeBSD General | 5 | 20th May 2008 01:51 PM |