Re: OpenBSD 5.2 AHCI problems with IBM x3250 M4

2013-03-12 Thread Roger Wiklund
On Sun, Mar 10, 2013 at 6:21 PM, Nick Holland
n...@holland-consulting.net wrote:
 Please keep it on the list...

 On 03/10/13 06:38, Roger Wiklund wrote:
 ...
 AHCI mode enabled and booting from CD:

 CD-ROM: 94
 Loading /5.2/I386/CDBOOT
 probing: pc0 pci mem[628K 3055M 444K 3M 1024M a20=on]
 disk: cd0
 OpenBSD/i386 CDBOOT 3.17
 boot boot hd0a:/bsd
 booting hd0a:/bsd

 And then it hangs, I've tried hd0a, hd1a, hd2a etc, same result.
 Looks like it can only find the cd0.

 yep, and that's your problem.  the BIOS is only exposing the CD to the
 boot system; your machine is broke.
 ...

 As someone suggested, check for firmware upgrades.  This system is
 probably incompatible with any non-UEFI OS, I doubt they want that.  If
 they do, return to vendor, they don't want your business.


 Nick.

Thanks!

Sorry, forgot to hit reply all.
I've sent a query to IBM regarding the issue.

I was thinking of a workaround base on the FAQ:

Kernel: /bsd: This is the goal of the boot process, to have the
OpenBSD kernel loaded into RAM and properly running. Once the kernel
has loaded, OpenBSD accesses the hardware directly, no longer through
the BIOS.

Is it possible to install the system in AHCI mode, then boot with a
bootable CD that contains the installed kernel, load it and when
OpenBSD then has access to the hardware tell it to mount the disk and
load the rest as usual?

Regards
Roger



Re: OpenBSD 5.2 AHCI problems with IBM x3250 M4

2013-03-12 Thread Roger Wiklund
On Tue, Mar 12, 2013 at 12:20 PM, Roger Wiklund roger.wikl...@gmail.com wrote:
 On Sun, Mar 10, 2013 at 6:21 PM, Nick Holland
 n...@holland-consulting.net wrote:
 Please keep it on the list...

 On 03/10/13 06:38, Roger Wiklund wrote:
 ...
 AHCI mode enabled and booting from CD:

 CD-ROM: 94
 Loading /5.2/I386/CDBOOT
 probing: pc0 pci mem[628K 3055M 444K 3M 1024M a20=on]
 disk: cd0
 OpenBSD/i386 CDBOOT 3.17
 boot boot hd0a:/bsd
 booting hd0a:/bsd

 And then it hangs, I've tried hd0a, hd1a, hd2a etc, same result.
 Looks like it can only find the cd0.

 yep, and that's your problem.  the BIOS is only exposing the CD to the
 boot system; your machine is broke.
 ...

 As someone suggested, check for firmware upgrades.  This system is
 probably incompatible with any non-UEFI OS, I doubt they want that.  If
 they do, return to vendor, they don't want your business.


 Nick.

 Thanks!

 Sorry, forgot to hit reply all.
 I've sent a query to IBM regarding the issue.

 I was thinking of a workaround base on the FAQ:

 Kernel: /bsd: This is the goal of the boot process, to have the
 OpenBSD kernel loaded into RAM and properly running. Once the kernel
 has loaded, OpenBSD accesses the hardware directly, no longer through
 the BIOS.

 Is it possible to install the system in AHCI mode, then boot with a
 bootable CD that contains the installed kernel, load it and when
 OpenBSD then has access to the hardware tell it to mount the disk and
 load the rest as usual?

 Regards
 Roger

Ah, boot -a from the installation cd lets me pick the root device.
However it hangs when I'm prompted root device (default cd0a):

Anyone come across this?



Re: OpenBSD 5.2 AHCI problems with IBM x3250 M4

2013-03-12 Thread Roger Wiklund
On Tue, Mar 12, 2013 at 3:43 PM, Roger Wiklund roger.wikl...@gmail.com wrote:
 On Tue, Mar 12, 2013 at 12:20 PM, Roger Wiklund roger.wikl...@gmail.com 
 wrote:
 On Sun, Mar 10, 2013 at 6:21 PM, Nick Holland
 n...@holland-consulting.net wrote:
 Please keep it on the list...

 On 03/10/13 06:38, Roger Wiklund wrote:
 ...
 AHCI mode enabled and booting from CD:

 CD-ROM: 94
 Loading /5.2/I386/CDBOOT
 probing: pc0 pci mem[628K 3055M 444K 3M 1024M a20=on]
 disk: cd0
 OpenBSD/i386 CDBOOT 3.17
 boot boot hd0a:/bsd
 booting hd0a:/bsd

 And then it hangs, I've tried hd0a, hd1a, hd2a etc, same result.
 Looks like it can only find the cd0.

 yep, and that's your problem.  the BIOS is only exposing the CD to the
 boot system; your machine is broke.
 ...

 As someone suggested, check for firmware upgrades.  This system is
 probably incompatible with any non-UEFI OS, I doubt they want that.  If
 they do, return to vendor, they don't want your business.


 Nick.

 Thanks!

 Sorry, forgot to hit reply all.
 I've sent a query to IBM regarding the issue.

 I was thinking of a workaround base on the FAQ:

 Kernel: /bsd: This is the goal of the boot process, to have the
 OpenBSD kernel loaded into RAM and properly running. Once the kernel
 has loaded, OpenBSD accesses the hardware directly, no longer through
 the BIOS.

 Is it possible to install the system in AHCI mode, then boot with a
 bootable CD that contains the installed kernel, load it and when
 OpenBSD then has access to the hardware tell it to mount the disk and
 load the rest as usual?

 Regards
 Roger

 Ah, boot -a from the installation cd lets me pick the root device.
 However it hangs when I'm prompted root device (default cd0a):

 Anyone come across this?

I compiled a custom kernel with the root path hard coded to sd0a, put
that on the CD and then it worked.
I think it's an OK workaround until IBM fixes the uEFI problem.

Did a simple dd with bs=1M count=1024M.

SSD
IDE write = 175MB/s
AHCI write = 250MB/s

Pretty significant difference.



Re: OpenBSD 5.2 AHCI problems with IBM x3250 M4

2013-03-10 Thread Alexey E. Suslikov
Roger Wiklund roger.wiklund at gmail.com writes:

 If I enable AHCI mode in UEFI/BIOS and boot from the cd52.iso, the
 installation finds the disk (sd0) and I can setup everything in fdisk
 and complete the installation.
 However when I reboot, the system can't find any operation system.

x3250 systems with UEFI are known to have boot
issues; maybe your machine needs firmware update.

(Search with google for MIGR-5090703 for example).

Cheers,
Alexey



OpenBSD 5.2 AHCI problems with IBM x3250 M4

2013-03-09 Thread Roger Wiklund
If I enable AHCI mode in UEFI/BIOS and boot from the cd52.iso, the
installation finds the disk (sd0) and I can setup everything in fdisk
and complete the installation.
However when I reboot, the system can't find any operation system.

It works if I change it to IDE mode, but I don't want that.
VMware ESXi 5.1 installs and boots just fine with AHCI mode.

I'm trying to figure out if the problem is with OpenBSD or my hardware
as the x3250 M4 runs UEFI and I guess has some sort of BIOS emulation.

I've tried 5.3 snapshot with the same result.

Any pointers?

Thanks!



Re: OpenBSD 5.2 AHCI problems with IBM x3250 M4

2013-03-09 Thread Nick Holland
On 03/09/13 19:26, Roger Wiklund wrote:
 If I enable AHCI mode in UEFI/BIOS and boot from the cd52.iso, the
 installation finds the disk (sd0) and I can setup everything in fdisk
 and complete the installation.
 However when I reboot, the system can't find any operation system.
 
 It works if I change it to IDE mode, but I don't want that.
 VMware ESXi 5.1 installs and boots just fine with AHCI mode.
 
 I'm trying to figure out if the problem is with OpenBSD or my hardware
 as the x3250 M4 runs UEFI and I guess has some sort of BIOS emulation.
 
 I've tried 5.3 snapshot with the same result.
 
 Any pointers?
 
 Thanks!
 

You will need to make sure the machine is in plain ol' BIOS mode.
Sounds like you have something fancier than anything I've got. :)

But...
if the system is coming back saying it can't find an os, that is a more
basic problem than OpenBSD -- that's a flubbed boot loader install or a
BIOS trying to boot from the wrong device.  To get the system to try to
boot, very little is required -- a partition marked active in the MBR,
and a valid signature (0xAA55), and the MBR code, and the BIOS to try
to boot from that.  If you aren't getting that, either the OpenBSD
installer is freaking out in some really odd way that I don't think
we've seen before on just your machine or you did something odd during
the install that you didn't think was important, or your BIOS is trying
to boot off the wrong thing (which I'm currently leaning towards).

You can test my theory...  boot off your CD, when you get to the boot
prompt, try boot hd0a:/bsd, see if it boots.  If not, try hd1a:/bsd
and any other hd*a that shows up before the boot prompt.  If it boots,
you have proven OpenBSD is compatible with your machine.  If you needed
to tell it hd1a or hd2a, then your BIOS is trying to boot from the wrong
device.

If that doesn't work, boot from the CD in ahci mode, and show us what
the output of fdisk sd0 looks like.

Nick.