Re: Not able to pass BIOS drive check with OpenBSD drive attached
Hi, > > My questions to you are: Has anybody ran into similar issues and was > able to resolve them? Do you think this is a OpenBSD related issue and > actually solveable (in a reasonable amount of time)? > I had the same issue with an Intel NUC D54250WYK. After installing OpenBSD5.5, no way to boot any system (blank screen at start). Fortunately Intel released a UEFI update that I could apply and everything is fine since then. Denis
Re: Not able to pass BIOS drive check with OpenBSD drive attached
On 07/31/14 12:58, Adrian Jervolino wrote: Hey misc@, I tried installing OpenBSD on our (previously FreeBSD 9.2 later 10.0) server the other day and ran into a weird issue. Boot and installation of my (emulated) install55.iso worked fine, but once installed, I'm not able to pass the (AHCI or IDE) BIOS drive check. What I mean by that is that the boot process is stuck at Debug LED code a2 (or a3 for IDE) and it's not even possible to enter the BIOS setup with the drive attached. The motherboard is a 1150 ASRock server motherboard (C226 WS) with a AMI UEFI BIOS. There is this weird legacy support module called CSM which I never heared about and wasn't able t dig alot of information up. I followed the BIOS' guide on resolving these kinds of issues (essentally clearing CMOS and updating the BIOS), with no success. Additionally I fiddled with every drive- or boot-related knob there is. I tried installing amd64 and i386, to both SSD and later HDD, booted the installed drives on systems currently running OpenBSD, tried booting my existing SNAPSHOT installation. Everything is working everywhere except on the server motherboard. My questions to you are: Has anybody ran into similar issues and was able to resolve them? Do you think this is a OpenBSD related issue and actually solveable (in a reasonable amount of time)? Swaping the motherboard is currently no option, so I'm thankfull for every hint. not run into this variant myself, but I'm guessing the BIOS is reading the MBR and choking because it isn't the one it expects. One trick that might work -- the MBR code doesn't HAVE to be the OpenBSD MBR code, so could I suggest booting a windows 95 or 98 floppy or CD, and doing an "FDISK /MBR"? You will probably have to do this on a different machine. Not really an OpenBSD issue if OpenBSD code isn't even running, really. Nick. OpenBSD 5.5 (RAMDISK_CD) #237: Wed Mar 5 09:43:42 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
Re: Not able to pass BIOS drive check with OpenBSD drive attached
Hello Adrian, On 31.07.2014 18:59, Adrian Jervolino wrote: > > My questions to you are: Has anybody ran into similar issues and was > able to resolve them? Do you think this is a OpenBSD related issue and > actually solveable (in a reasonable amount of time)? > > Swaping the motherboard is currently no option, so I'm thankfull for > every hint. We ran into this issue twice so far, once beginning of the year with a couple of Gigabyte boards and some weeks ago with a couple of Intel 4th Generation NUCs. The NUCs were simple to solve as Intel has provided a BIOS Patch. With the Gigabytes, after one week we had analyzed it so far that simply attaching a HDD used under OpenBSD (not only a system disk that was installed upon) would trigger this problem. Rewriting the partition table with fdisk on another machine let the 'faulty' boards access their bios again and see the disks. Our suspicion at the time was the block size used by the OpenBSD system (512 vs 4k) We also disable UEFI boot in the bios. Cheers, Kim
Re: Not able to pass BIOS drive check with OpenBSD drive attached
Hello Kim, On Fri, Aug 01, 2014 at 10:56:48AM +0200, Kim Zeitler wrote: > Hello Adrian, > > On 31.07.2014 18:59, Adrian Jervolino wrote: > > > > My questions to you are: Has anybody ran into similar issues and was > > able to resolve them? Do you think this is a OpenBSD related issue and > > actually solveable (in a reasonable amount of time)? > > > > Swaping the motherboard is currently no option, so I'm thankfull for > > every hint. > > Our suspicion at the time was the block size used by the OpenBSD system > (512 vs 4k) > > We also disable UEFI boot in the bios. Yep, I can see how you arrived at this conclusion. In sheer desperation I installed GRUB2. Now it's constantly rebooting, so I think there is no real problem with the MBRi boot code. Of course I "disabled" the UEFI. "disabled" hence the lack of disabling capabilities, since I'm only able to launch something called the CSM. Adrian
Re: Not able to pass BIOS drive check with OpenBSD drive attached
On 14-08-01 05:33 AM, Adrian Jervolino wrote: Yep, I can see how you arrived at this conclusion. In sheer desperation I installed GRUB2. Now it's constantly rebooting, so I think there is no real problem with the MBRi boot code. Of course I "disabled" the UEFI. "disabled" hence the lack of disabling capabilities, since I'm only able to launch something called the CSM. Adrian FYI, the mysterious "CSM" is simply the Compatibility Support Module, this is fairly standard terminology for "MBR emulation support" among UEFI implementations. Obviously the quality of any given vendor's CSM will vary :-/. Looking for details on it, the original vendor of it, etc. is about as useful as trying to track down who's responsible for this "MBR" stuff - barking up the wrong tree altogether, there's no single piece of software named CSM. -- -Adam Thompson athom...@athompso.net
