|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
If my HP Stream14 laptop sits awhile, the bios resets to secure booting.
First suggestion is to reset the bios Second suggestion is to try to boot bsd.rd, on install media, as a rescue disk https://rexford.bio/w.p/rescue-your-openbsd-system/ Attempt to backup (not implying you're not careful - I skipped but was lucky) and then (U) update to reinstall. error removed Code:
# sha256 -h /var/db/kernel.SHA256 /bsd Last edited by shep; 11th April 2023 at 12:25 AM. Reason: corrected post install /var/db/ code tag |
|
||||
I went and double checked and my secure boot isn't enabled.
I was able to boot by doing Code:
boot>boot -c Code:
disable efi Quote:
Thanks.
__________________
"The basic tool for the manipulation of reality is the manipulation of words. If you can control the meaning of words, you can control the people who must use the words." -Philip K. Dick |
|
|||
I think we may have found a bug.
I have 2 systems. The first was running up-to-date -current and the update via bsd.rd went smoothly. The second was the rarely used laptop. I ended up using install73.img for a new install on the laptop and saw the shutdown message about kernel relinking failing. The laptop with the new install had the lower case kernel.SHA256 filename. I reported to bugs@openbsd.org and tech@openbsd.org. Edit: I was mistaken. The correct file name is /var/db/kernel.SHA256 Last edited by shep; 11th April 2023 at 01:30 PM. |
|
||||
Can you ssh into the machine? Does the caps lock key light toggle?
What is your graphics hardware? The machine might just have display problems. v7.3 incorporated Linux's 6.1.15 DRM stack, which is bigger than the rest of the OpenBSD base system combined, so I would look at that first. |
|
|||
Another potential cause is failing to install the bootblocks. At the end of the installation, there is a message that the system will not boot due to bootblocks failure. I'm guessing the issue has to do with remnants of the gpt/mbr boot sectors because the issue is resolved if I use gdisk to delete the gpt/protective mbr and dd if=/dev/zero(random) the first 1000 sectors.
I think you would have seen this unless it was an unattended install. If the machine will boot a live cd, it suggests disk problems, both installer and target, could be a potential cause. |
|
||||
Quote:
__________________
"The basic tool for the manipulation of reality is the manipulation of words. If you can control the meaning of words, you can control the people who must use the words." -Philip K. Dick |
|
||||
Check the X.Org log to see which DDX driver is being used — intel(4) has been essentially un-maintained since ~2008 and appears to be rotting badly so modesetting(4) should probably be preferred.
I know Debian stable now defaults to the modesetting DDX driver for Intel hardware newer than 2008 but I don't know how OpenBSD handles this. This X.Org configuration snippet should force modesetting(4) if it's not already being used: Code:
Section "Device" Identifier "Intel Graphics" Driver "modesetting" EndSection |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[npppd] hang on Starting peer | jonsec | OpenBSD General | 4 | 3rd October 2022 10:33 PM |
How to troubleshoot a hang in OpenBSD? | quisquous | OpenBSD General | 11 | 1st January 2014 09:21 PM |
Introduction plus SSH login hang question. | pico | OpenBSD General | 7 | 2nd April 2010 06:08 AM |
Dual-boot laptop won't boot OpenBSD after upgrade to 4.3 | kbeaucha | OpenBSD Installation and Upgrading | 17 | 30th May 2008 02:40 PM |