Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
Odd, I didn't know this. On the Apple PPC machines, OpenFirmware was limited to 128G for the B&W G3. Later, the limit was extended. You're right, the limitation is stupid. --- On Sat, 3/26/11, Kenneth R Westerback wrote: From: Kenneth R Westerback Subject: Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD. To: "Amarendra Godbole" Cc: "misc" Date: Saturday, March 26, 2011, 8:12 PM On Sat, Mar 26, 2011 at 11:28:32PM +0530, Amarendra Godbole wrote: > On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback > wrote: > > On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: > >> Hi, > >> > >> I have run into a deadend trying to understand, and troubleshoot this > >> problem. Hence, I would like some pointers. Following is what I did to > >> get my OpenBSD system running, and then subsequently messing it up (in > >> sequence): > >> > >> (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. > >> Did reserve ~140G for Windows, and then installed OpenBSD as described > > > > OpenBSD will reliably boot only if located <128GB. A > > recent change has made this explicit until a more reliable > > way of booting from >128GB can be found. > > > >> in FAQ. Things were fine for a couple of months. > >> > [...] > >> (4) grub started fine, and Windows XP boots fine, but when I try to > >> boot OpenBSD, I get something like this: > >> Loading... > >> probing: <> > >> disk: fd0 hd0+* > >> >> OpenBSD/i386 BOOT 2.13 > >> open(hd0a:/etc/boot.conf): Invalid argument > >> boot> > >> booting hd0a:/bsd: open hd0a:/bsd: Invalid argument > >> failed(22). will try ... > >> > >> And OpenBSD never boots. I don't recall changing anything else. From > >> what I know (very little), biosboot was able to load the 2nd stage > >> bootloader, but it now failed loading the kernel image. > >> > >> I can boot successfully into OpenBSD using a 4.8 boot CD though. I > >> tried running installboot again (mindlessly!), and get this error: > >> -- > >> OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 > >> Password: > >> boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c > >> /boot is 3 blocks x 16384 bytes > >> fs block shift 2; part offset 293603940; inode block 32, offset 10792 > >> master boot record (MBR) at sector 0 > >> partition 0: type 0x07 offset 63 size 293603877 > >> partition 1: type 0xA6 offset 293603940 size 377487360 > >> installboot: invalid location: all of /boot must be < sector 268435455. > > > > And here is the error now being generated. If you have a BIOS/Hardware > > combo that can actually boot from >128GB, you can recompile installboot > > and friends after changing the value of BIOSBOOT_MAXSEC in > sys/sys/disklabel.h. > > Okay, so I changed BOOTBIOS_MAXSEC and got installboot to work fine. > Nothing seems to have changed though, as I still run into the "booting > hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try..." > error message at boot>. You need to compile 'and friends', in particular a new /boot. And install it. This is done by cd /usr/src/sys/arch/[1386|amd64]/stand make clean make obj make make install /usr/mdec/installboot -v /boot /usr/mdec/biosboot all as root of course. > > What surprises me is OpenBSD booted fine *before* I had Windows XP, > and the ~143G partition was still present. Possibly something else is > broken... Nope. We introduced a hard limit of 128GB as the workable lowest common denominator while we research a reliable way to determine when it is safe to go beyond. On one of my recent machines, just to pick an example, the BIOS simply returns all zero's for all I/O attempted past 128GB. We do like to impose draconian new restrictions and debug code early in a release cycle. :-) The lack of a reliable way to safely go beyond 128GB, even with recent BIOSen is sad and no doubt the reason Windows wants the first 100MB or so for its boot, OpenSUSE 11.4 blew up when installed >128GB on a just purchased motherboard, etc. The second target for anyone with a time machine should be the morons who decided BIOS would be enough for anyone. > > "makeactive" in menu.lst for grub did not help either (as I had guessed). > > -Amarendra > [...] > All grub can do (to my knowledge) is grab and run the OpenBSD /boot program. And if it doesn't work ... Ken
Re: [FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
The 128G limit usually means from the beginning of the disk. I also use chainloader +1 for booting BSDs from x86 machines. Apologies for keeping the thread alive. --- On Sat, 3/26/11, Amarendra Godbole wrote: From: Amarendra Godbole Subject: Re: [FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD. To: "Kenneth R Westerback" Cc: "misc" Date: Saturday, March 26, 2011, 7:02 PM On Sun, Mar 27, 2011 at 12:23 AM, Kenneth R Westerback wrote: > On Sat, Mar 26, 2011 at 11:59:17PM +0530, Amarendra Godbole wrote: >> Okay, seems like I sent a hasty reply earlier. >> >> Got this fixed, by booting off a 4.8 CD, and "upgrading" - fsck all >> filesystems, say no to bsd, bsd.mp and base, it created device nodes, >> and congratulated me for completion of the upgrade. Rebooted, and the >> system came up nicely. > > And now has 4.8 or 4.9 installed? 4.9, since I said no to everything. I re-created device nodes after booting, so hopefully things are okay. >> Noticed two things: >> (a) the * after hd0+ is gone during boot> > > The '*' reports a failure to find an OpenBSD disklabel. > The '+' reports the BIOS claiming support of EDD, a.k.a. BIOS LBA, access. > >> (b) the disklabel now shows proper values for "boundstart" and >> "boundend" - earlier both were 0. > > Because earlier the OpenBSD partition was not found, and thus unable to > provide the bound information. Yes, that was nagging me earlier, but somehow I could not fix it - there is too much to understand for the i386 boot process, and the partition and disklabel is a source of confusion for me. Thanks for your pointers, I atleast had heart to continue trying to fix (agree, I did not understand all - but since the CD boot was working fine, and I have a full backup of my data, I decided to probe.) -Amarendra > >> >> Thanks to all those who replied. Now I am off to reading more about >> boot, and friends (though I am not sure if things are well at this >> point!). >> >> -Amarendra >> >> On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback >> wrote: >> > On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: >> >> Hi, >> >> >> >> I have run into a deadend trying to understand, and troubleshoot this >> >> problem. Hence, I would like some pointers. Following is what I did to >> >> get my OpenBSD system running, and then subsequently messing it up (in >> >> sequence): >> >> >> >> (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. >> >> Did reserve ~140G for Windows, and then installed OpenBSD as described >> > >> > ? ? ? ? ? ? ? OpenBSD will reliably boot only if located <128GB. A >> > ? ? ? ? ? ? ? recent change has made this explicit until a more reliable >> > ? ? ? ? ? ? ? way of booting from >128GB can be found. >> > >> >> in FAQ. Things were fine for a couple of months. >> >> >> >> (2) Installed Windows XP ghost image to the first partition. Sadly, >> >> ntldr was not installed so machine still booted directly into OpenBSD >> >> >> >> (3) Installed grub. Here is what /grub/menu.lst looks like: >> >> default 0 timeout 5 >> >> title Windows XP >> >> root (hd0,0) >> >> chainloader +1 >> >> >> >> title OpenBSD >> >> root (hd0,1) >> >> chainloader +1 >> >> >> >> (4) grub started fine, and Windows XP boots fine, but when I try to >> >> boot OpenBSD, I get something like this: >> >> Loading... >> >> probing: <> >> >> disk: fd0 hd0+* >> >> >> OpenBSD/i386 BOOT 2.13 >> >> open(hd0a:/etc/boot.conf): Invalid argument >> >> boot> >> >> booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >> >> ?failed(22). will try ... >> >> >> >> And OpenBSD never boots. I don't recall changing anything else. From >> >> what I know (very little), biosboot was able to load the 2nd stage >> >> bootloader, but it now failed loading the kernel image. >> >> >> >> I can boot successfully into OpenBSD using a 4.8 boot CD though. I >> >> tried running installboot again (mindlessly!), and get this error: >> >> -- >> >> OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 >> >> Password: >> >> boot: /boot
Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
On Sat, Mar 26, 2011 at 11:28:32PM +0530, Amarendra Godbole wrote: > On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback > wrote: > > On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: > >> Hi, > >> > >> I have run into a deadend trying to understand, and troubleshoot this > >> problem. Hence, I would like some pointers. Following is what I did to > >> get my OpenBSD system running, and then subsequently messing it up (in > >> sequence): > >> > >> (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. > >> Did reserve ~140G for Windows, and then installed OpenBSD as described > > > > OpenBSD will reliably boot only if located <128GB. A > > recent change has made this explicit until a more reliable > > way of booting from >128GB can be found. > > > >> in FAQ. Things were fine for a couple of months. > >> > [...] > >> (4) grub started fine, and Windows XP boots fine, but when I try to > >> boot OpenBSD, I get something like this: > >> Loading... > >> probing: <> > >> disk: fd0 hd0+* > >> >> OpenBSD/i386 BOOT 2.13 > >> open(hd0a:/etc/boot.conf): Invalid argument > >> boot> > >> booting hd0a:/bsd: open hd0a:/bsd: Invalid argument > >> failed(22). will try ... > >> > >> And OpenBSD never boots. I don't recall changing anything else. From > >> what I know (very little), biosboot was able to load the 2nd stage > >> bootloader, but it now failed loading the kernel image. > >> > >> I can boot successfully into OpenBSD using a 4.8 boot CD though. I > >> tried running installboot again (mindlessly!), and get this error: > >> -- > >> OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 > >> Password: > >> boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c > >> /boot is 3 blocks x 16384 bytes > >> fs block shift 2; part offset 293603940; inode block 32, offset 10792 > >> master boot record (MBR) at sector 0 > >> partition 0: type 0x07 offset 63 size 293603877 > >> partition 1: type 0xA6 offset 293603940 size 377487360 > >> installboot: invalid location: all of /boot must be < sector 268435455. > > > > And here is the error now being generated. If you have a BIOS/Hardware > > combo that can actually boot from >128GB, you can recompile installboot > > and friends after changing the value of BIOSBOOT_MAXSEC in > sys/sys/disklabel.h. > > Okay, so I changed BOOTBIOS_MAXSEC and got installboot to work fine. > Nothing seems to have changed though, as I still run into the "booting > hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try..." > error message at boot>. You need to compile 'and friends', in particular a new /boot. And install it. This is done by cd /usr/src/sys/arch/[1386|amd64]/stand make clean make obj make make install /usr/mdec/installboot -v /boot /usr/mdec/biosboot all as root of course. > > What surprises me is OpenBSD booted fine *before* I had Windows XP, > and the ~143G partition was still present. Possibly something else is > broken... Nope. We introduced a hard limit of 128GB as the workable lowest common denominator while we research a reliable way to determine when it is safe to go beyond. On one of my recent machines, just to pick an example, the BIOS simply returns all zero's for all I/O attempted past 128GB. We do like to impose draconian new restrictions and debug code early in a release cycle. :-) The lack of a reliable way to safely go beyond 128GB, even with recent BIOSen is sad and no doubt the reason Windows wants the first 100MB or so for its boot, OpenSUSE 11.4 blew up when installed >128GB on a just purchased motherboard, etc. The second target for anyone with a time machine should be the morons who decided BIOS would be enough for anyone. > > "makeactive" in menu.lst for grub did not help either (as I had guessed). > > -Amarendra > [...] > All grub can do (to my knowledge) is grab and run the OpenBSD /boot program. And if it doesn't work ... Ken
Re: [FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
On Sun, Mar 27, 2011 at 12:23 AM, Kenneth R Westerback wrote: > On Sat, Mar 26, 2011 at 11:59:17PM +0530, Amarendra Godbole wrote: >> Okay, seems like I sent a hasty reply earlier. >> >> Got this fixed, by booting off a 4.8 CD, and "upgrading" - fsck all >> filesystems, say no to bsd, bsd.mp and base, it created device nodes, >> and congratulated me for completion of the upgrade. Rebooted, and the >> system came up nicely. > > And now has 4.8 or 4.9 installed? 4.9, since I said no to everything. I re-created device nodes after booting, so hopefully things are okay. >> Noticed two things: >> (a) the * after hd0+ is gone during boot> > > The '*' reports a failure to find an OpenBSD disklabel. > The '+' reports the BIOS claiming support of EDD, a.k.a. BIOS LBA, access. > >> (b) the disklabel now shows proper values for "boundstart" and >> "boundend" - earlier both were 0. > > Because earlier the OpenBSD partition was not found, and thus unable to > provide the bound information. Yes, that was nagging me earlier, but somehow I could not fix it - there is too much to understand for the i386 boot process, and the partition and disklabel is a source of confusion for me. Thanks for your pointers, I atleast had heart to continue trying to fix (agree, I did not understand all - but since the CD boot was working fine, and I have a full backup of my data, I decided to probe.) -Amarendra > >> >> Thanks to all those who replied. Now I am off to reading more about >> boot, and friends (though I am not sure if things are well at this >> point!). >> >> -Amarendra >> >> On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback >> wrote: >> > On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: >> >> Hi, >> >> >> >> I have run into a deadend trying to understand, and troubleshoot this >> >> problem. Hence, I would like some pointers. Following is what I did to >> >> get my OpenBSD system running, and then subsequently messing it up (in >> >> sequence): >> >> >> >> (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. >> >> Did reserve ~140G for Windows, and then installed OpenBSD as described >> > >> > ? ? ? ? ? ? ? OpenBSD will reliably boot only if located <128GB. A >> > ? ? ? ? ? ? ? recent change has made this explicit until a more reliable >> > ? ? ? ? ? ? ? way of booting from >128GB can be found. >> > >> >> in FAQ. Things were fine for a couple of months. >> >> >> >> (2) Installed Windows XP ghost image to the first partition. Sadly, >> >> ntldr was not installed so machine still booted directly into OpenBSD >> >> >> >> (3) Installed grub. Here is what /grub/menu.lst looks like: >> >> default 0 timeout 5 >> >> title Windows XP >> >> root (hd0,0) >> >> chainloader +1 >> >> >> >> title OpenBSD >> >> root (hd0,1) >> >> chainloader +1 >> >> >> >> (4) grub started fine, and Windows XP boots fine, but when I try to >> >> boot OpenBSD, I get something like this: >> >> Loading... >> >> probing: <> >> >> disk: fd0 hd0+* >> >> >> OpenBSD/i386 BOOT 2.13 >> >> open(hd0a:/etc/boot.conf): Invalid argument >> >> boot> >> >> booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >> >> ?failed(22). will try ... >> >> >> >> And OpenBSD never boots. I don't recall changing anything else. From >> >> what I know (very little), biosboot was able to load the 2nd stage >> >> bootloader, but it now failed loading the kernel image. >> >> >> >> I can boot successfully into OpenBSD using a 4.8 boot CD though. I >> >> tried running installboot again (mindlessly!), and get this error: >> >> -- >> >> OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 >> >> Password: >> >> boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c >> >> /boot is 3 blocks x 16384 bytes >> >> fs block shift 2; part offset 293603940; inode block 32, offset 10792 >> >> master boot record (MBR) at sector 0 >> >> ? ? ? ? partition 0: type 0x07 offset 63 size 293603877 >> >> ? ? ? ? partition 1: type 0xA6 offset 293603940 size 377487360 >> >> installboot: invalid location: all of /boot must be < sector 268435455. >> > >> > And here is the error now being generated. If you have a BIOS/Hardware >> > combo that can actually boot from >128GB, you can recompile installboot >> > and friends after changing the value of BIOSBOOT_MAXSEC in >> > sys/sys/disklabel.h. >> > >> > If you have any knowledge on how to reliably detect that the BIOS/Hardware >> > will correctly support EDD access beyond 128GB, we are very interested. >> > >> > Ken >> > >> >> -- >> >> >> >> disklabel reads: >> >> -- >> >> OpenBSD_49$ disklabel sd0 >> >> # /dev/rsd0c: >> >> type: SCSI >> >> disk: SCSI disk >> >> label: ST9320423AS >> >> duid: 93cf9b951f02f209 >> >> flags: >> >> bytes/sector: 512 >> >> sectors/track: 63 >> >> tracks/cylinder: 255 >> >> sectors/cylinder: 16065 >> >> cylinders: 38913 >> >> total sectors: 625142448 >> >> boundstart: 0 >> >> boundend: 0 >> >> drivedat
[FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
Okay, seems like I sent a hasty reply earlier.
Got this fixed, by booting off a 4.8 CD, and "upgrading" - fsck all
filesystems, say no to bsd, bsd.mp and base, it created device nodes,
and congratulated me for completion of the upgrade. Rebooted, and the
system came up nicely.
Noticed two things:
(a) the * after hd0+ is gone during boot>
(b) the disklabel now shows proper values for "boundstart" and
"boundend" - earlier both were 0.
Thanks to all those who replied. Now I am off to reading more about
boot, and friends (though I am not sure if things are well at this
point!).
-Amarendra
On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback
wrote:
> On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote:
>> Hi,
>>
>> I have run into a deadend trying to understand, and troubleshoot this
>> problem. Hence, I would like some pointers. Following is what I did to
>> get my OpenBSD system running, and then subsequently messing it up (in
>> sequence):
>>
>> (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
>> Did reserve ~140G for Windows, and then installed OpenBSD as described
>
> OpenBSD will reliably boot only if located <128GB. A
> recent change has made this explicit until a more reliable
> way of booting from >128GB can be found.
>
>> in FAQ. Things were fine for a couple of months.
>>
>> (2) Installed Windows XP ghost image to the first partition. Sadly,
>> ntldr was not installed so machine still booted directly into OpenBSD
>>
>> (3) Installed grub. Here is what /grub/menu.lst looks like:
>> default 0 timeout 5
>> title Windows XP
>> root (hd0,0)
>> chainloader +1
>>
>> title OpenBSD
>> root (hd0,1)
>> chainloader +1
>>
>> (4) grub started fine, and Windows XP boots fine, but when I try to
>> boot OpenBSD, I get something like this:
>> Loading...
>> probing: <>
>> disk: fd0 hd0+*
>> >> OpenBSD/i386 BOOT 2.13
>> open(hd0a:/etc/boot.conf): Invalid argument
>> boot>
>> booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
>> failed(22). will try ...
>>
>> And OpenBSD never boots. I don't recall changing anything else. From
>> what I know (very little), biosboot was able to load the 2nd stage
>> bootloader, but it now failed loading the kernel image.
>>
>> I can boot successfully into OpenBSD using a 4.8 boot CD though. I
>> tried running installboot again (mindlessly!), and get this error:
>> --
>> OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
>> Password:
>> boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
>> /boot is 3 blocks x 16384 bytes
>> fs block shift 2; part offset 293603940; inode block 32, offset 10792
>> master boot record (MBR) at sector 0
>> partition 0: type 0x07 offset 63 size 293603877
>> partition 1: type 0xA6 offset 293603940 size 377487360
>> installboot: invalid location: all of /boot must be < sector 268435455.
>
> And here is the error now being generated. If you have a BIOS/Hardware
> combo that can actually boot from >128GB, you can recompile installboot
> and friends after changing the value of BIOSBOOT_MAXSEC in
sys/sys/disklabel.h.
>
> If you have any knowledge on how to reliably detect that the BIOS/Hardware
> will correctly support EDD access beyond 128GB, we are very interested.
>
> Ken
>
>> --
>>
>> disklabel reads:
>> --
>> OpenBSD_49$ disklabel sd0
>> # /dev/rsd0c:
>> type: SCSI
>> disk: SCSI disk
>> label: ST9320423AS
>> duid: 93cf9b951f02f209
>> flags:
>> bytes/sector: 512
>> sectors/track: 63
>> tracks/cylinder: 255
>> sectors/cylinder: 16065
>> cylinders: 38913
>> total sectors: 625142448
>> boundstart: 0
>> boundend: 0
>> drivedata: 0
>>
>> 16 partitions:
>> #size offset fstype [fsize bsize cpg]
>> a: 2104508293603940 4.2BSD 2048 163841 # /
>> b: 8385937295708448swap
>> c:6251424480 unused
>> d: 41945696304094400 4.2BSD 2048 163841 # /usr
>> e: 4192960346040096 4.2BSD 2048 163841 # /tmp
>> f: 20964832350233056 4.2BSD 2048 163841 #
/usr/local
>> g: 4192960371197888 4.2BSD 2048 163841 #
/usr/X11R6
>> h:125821056375390848 4.2BSD 2048 163841 # /home
>> j: 8385952501211904 4.2BSD 2048 163841 # /var
>> k: 8385920509597856 4.2BSD 2048 163841 #
/usr/src
>> l: 12578912517983776 4.2BSD 2048 163841 #
/usr/obj
>> OpenBSD_49$
>> --
>>
>> dmesg is
>> -
>> OpenBSD 4.9-current (kernel) #5: Wed Mar 23 23:58:17 IST 2011
>> r...@zimbu.vxindia.veritas.com:/home/amar/site-specific/builds/kernel
>> cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz ("GenuineIntel"
>> 686-class) 2.40 GHz
>> cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SE
Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback wrote: > On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: >> Hi, >> >> I have run into a deadend trying to understand, and troubleshoot this >> problem. Hence, I would like some pointers. Following is what I did to >> get my OpenBSD system running, and then subsequently messing it up (in >> sequence): >> >> (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. >> Did reserve ~140G for Windows, and then installed OpenBSD as described > > OpenBSD will reliably boot only if located <128GB. A > recent change has made this explicit until a more reliable > way of booting from >128GB can be found. > >> in FAQ. Things were fine for a couple of months. >> [...] >> (4) grub started fine, and Windows XP boots fine, but when I try to >> boot OpenBSD, I get something like this: >> Loading... >> probing: <> >> disk: fd0 hd0+* >> >> OpenBSD/i386 BOOT 2.13 >> open(hd0a:/etc/boot.conf): Invalid argument >> boot> >> booting hd0a:/bsd: open hd0a:/bsd: Invalid argument >> failed(22). will try ... >> >> And OpenBSD never boots. I don't recall changing anything else. From >> what I know (very little), biosboot was able to load the 2nd stage >> bootloader, but it now failed loading the kernel image. >> >> I can boot successfully into OpenBSD using a 4.8 boot CD though. I >> tried running installboot again (mindlessly!), and get this error: >> -- >> OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 >> Password: >> boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c >> /boot is 3 blocks x 16384 bytes >> fs block shift 2; part offset 293603940; inode block 32, offset 10792 >> master boot record (MBR) at sector 0 >> partition 0: type 0x07 offset 63 size 293603877 >> partition 1: type 0xA6 offset 293603940 size 377487360 >> installboot: invalid location: all of /boot must be < sector 268435455. > > And here is the error now being generated. If you have a BIOS/Hardware > combo that can actually boot from >128GB, you can recompile installboot > and friends after changing the value of BIOSBOOT_MAXSEC in sys/sys/disklabel.h. Okay, so I changed BOOTBIOS_MAXSEC and got installboot to work fine. Nothing seems to have changed though, as I still run into the "booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try..." error message at boot>. What surprises me is OpenBSD booted fine *before* I had Windows XP, and the ~143G partition was still present. Possibly something else is broken... "makeactive" in menu.lst for grub did not help either (as I had guessed). -Amarendra [...]
Re: [FIXED] Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
On Sat, Mar 26, 2011 at 11:59:17PM +0530, Amarendra Godbole wrote: > Okay, seems like I sent a hasty reply earlier. > > Got this fixed, by booting off a 4.8 CD, and "upgrading" - fsck all > filesystems, say no to bsd, bsd.mp and base, it created device nodes, > and congratulated me for completion of the upgrade. Rebooted, and the > system came up nicely. And now has 4.8 or 4.9 installed? > > Noticed two things: > (a) the * after hd0+ is gone during boot> The '*' reports a failure to find an OpenBSD disklabel. The '+' reports the BIOS claiming support of EDD, a.k.a. BIOS LBA, access. > (b) the disklabel now shows proper values for "boundstart" and > "boundend" - earlier both were 0. Because earlier the OpenBSD partition was not found, and thus unable to provide the bound information. > > Thanks to all those who replied. Now I am off to reading more about > boot, and friends (though I am not sure if things are well at this > point!). > > -Amarendra > > On Sat, Mar 26, 2011 at 7:01 PM, Kenneth R Westerback > wrote: > > On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote: > >> Hi, > >> > >> I have run into a deadend trying to understand, and troubleshoot this > >> problem. Hence, I would like some pointers. Following is what I did to > >> get my OpenBSD system running, and then subsequently messing it up (in > >> sequence): > >> > >> (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current. > >> Did reserve ~140G for Windows, and then installed OpenBSD as described > > > > ? ? ? ? ? ? ? OpenBSD will reliably boot only if located <128GB. A > > ? ? ? ? ? ? ? recent change has made this explicit until a more reliable > > ? ? ? ? ? ? ? way of booting from >128GB can be found. > > > >> in FAQ. Things were fine for a couple of months. > >> > >> (2) Installed Windows XP ghost image to the first partition. Sadly, > >> ntldr was not installed so machine still booted directly into OpenBSD > >> > >> (3) Installed grub. Here is what /grub/menu.lst looks like: > >> default 0 timeout 5 > >> title Windows XP > >> root (hd0,0) > >> chainloader +1 > >> > >> title OpenBSD > >> root (hd0,1) > >> chainloader +1 > >> > >> (4) grub started fine, and Windows XP boots fine, but when I try to > >> boot OpenBSD, I get something like this: > >> Loading... > >> probing: <> > >> disk: fd0 hd0+* > >> >> OpenBSD/i386 BOOT 2.13 > >> open(hd0a:/etc/boot.conf): Invalid argument > >> boot> > >> booting hd0a:/bsd: open hd0a:/bsd: Invalid argument > >> ?failed(22). will try ... > >> > >> And OpenBSD never boots. I don't recall changing anything else. From > >> what I know (very little), biosboot was able to load the 2nd stage > >> bootloader, but it now failed loading the kernel image. > >> > >> I can boot successfully into OpenBSD using a 4.8 boot CD though. I > >> tried running installboot again (mindlessly!), and get this error: > >> -- > >> OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0 > >> Password: > >> boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c > >> /boot is 3 blocks x 16384 bytes > >> fs block shift 2; part offset 293603940; inode block 32, offset 10792 > >> master boot record (MBR) at sector 0 > >> ? ? ? ? partition 0: type 0x07 offset 63 size 293603877 > >> ? ? ? ? partition 1: type 0xA6 offset 293603940 size 377487360 > >> installboot: invalid location: all of /boot must be < sector 268435455. > > > > And here is the error now being generated. If you have a BIOS/Hardware > > combo that can actually boot from >128GB, you can recompile installboot > > and friends after changing the value of BIOSBOOT_MAXSEC in > > sys/sys/disklabel.h. > > > > If you have any knowledge on how to reliably detect that the BIOS/Hardware > > will correctly support EDD access beyond 128GB, we are very interested. > > > > Ken > > > >> -- > >> > >> disklabel reads: > >> -- > >> OpenBSD_49$ disklabel sd0 > >> # /dev/rsd0c: > >> type: SCSI > >> disk: SCSI disk > >> label: ST9320423AS > >> duid: 93cf9b951f02f209 > >> flags: > >> bytes/sector: 512 > >> sectors/track: 63 > >> tracks/cylinder: 255 > >> sectors/cylinder: 16065 > >> cylinders: 38913 > >> total sectors: 625142448 > >> boundstart: 0 > >> boundend: 0 > >> drivedata: 0 > >> > >> 16 partitions: > >> # ? ? ? ? ? ? ? ?size ? ? ? ? ? offset ?fstype [fsize bsize ?cpg] > >> ? a: ? ? ? ? ?2104508 ? ? ? ?293603940 ?4.2BSD ? 2048 16384 ? ?1 # / > >> ? b: ? ? ? ? ?8385937 ? ? ? ?295708448 ? ?swap > >> ? c: ? ? ? ?625142448 ? ? ? ? ? ? ? ?0 ?unused > >> ? d: ? ? ? ? 41945696 ? ? ? ?304094400 ?4.2BSD ? 2048 16384 ? ?1 # /usr > >> ? e: ? ? ? ? ?4192960 ? ? ? ?346040096 ?4.2BSD ? 2048 16384 ? ?1 # /tmp > >> ? f: ? ? ? ? 20964832 ? ? ? ?350233056 ?4.2BSD ? 2048 16384 ? ?1 # > >> /usr/local > >> ? g: ? ? ? ? ?4192960 ? ? ? ?371197888 ?4.2BSD ? 2048 16384 ? ?1 # > >> /usr/X11R6 > >> ? h: ? ? ? ?125821056 ? ? ? ?375390848 ?4.2BSD ? 2048 16384 ? ?1 # /home > >> ? j:
Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
Sometimes you need to add makeactive to the entry.
--- On Sat, 3/26/11, Amarendra Godbole wrote:
From: Amarendra Godbole
Subject: Messed up OpenBSD boot after dualbooting via grub - cannot boot
without OpenBSD boot CD.
To: "misc"
Date: Saturday, March 26, 2011, 11:56 AM
Hi,
I have run into a deadend trying to understand, and troubleshoot this
problem. Hence, I would like some pointers. Following is what I did to
get my OpenBSD system running, and then subsequently messing it up (in
sequence):
(1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
Did reserve ~140G for Windows, and then installed OpenBSD as described
in FAQ. Things were fine for a couple of months.
(2) Installed Windows XP ghost image to the first partition. Sadly,
ntldr was not installed so machine still booted directly into OpenBSD
(3) Installed grub. Here is what /grub/menu.lst looks like:
default 0 timeout 5
title Windows XP
root (hd0,0)
chainloader +1
title OpenBSD
root (hd0,1)
chainloader +1
(4) grub started fine, and Windows XP boots fine, but when I try to
boot OpenBSD, I get something like this:
Loading...
probing: <>
disk: fd0 hd0+*
>> OpenBSD/i386 BOOT 2.13
open(hd0a:/etc/boot.conf): Invalid argument
boot>
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
failed(22). will try ...
And OpenBSD never boots. I don't recall changing anything else. From
what I know (very little), biosboot was able to load the 2nd stage
bootloader, but it now failed loading the kernel image.
I can boot successfully into OpenBSD using a 4.8 boot CD though. I
tried running installboot again (mindlessly!), and get this error:
--
OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
Password:
boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
/boot is 3 blocks x 16384 bytes
fs block shift 2; part offset 293603940; inode block 32, offset 10792
master boot record (MBR) at sector 0
partition 0: type 0x07 offset 63 size 293603877
partition 1: type 0xA6 offset 293603940 size 377487360
installboot: invalid location: all of /boot must be < sector 268435455.
--
disklabel reads:
--
OpenBSD_49$ disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: ST9320423AS
duid: 93cf9b951f02f209
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 38913
total sectors: 625142448
boundstart: 0
boundend: 0
drivedata: 0
16 partitions:
#size offset fstype [fsize bsize cpg]
a: 2104508293603940 4.2BSD 2048 163841 # /
b: 8385937295708448swap
c:6251424480 unused
d: 41945696304094400 4.2BSD 2048 163841 # /usr
e: 4192960346040096 4.2BSD 2048 163841 # /tmp
f: 20964832350233056 4.2BSD 2048 163841 # /usr/local
g: 4192960371197888 4.2BSD 2048 163841 # /usr/X11R6
h:125821056375390848 4.2BSD 2048 163841 # /home
j: 8385952501211904 4.2BSD 2048 163841 # /var
k: 8385920509597856 4.2BSD 2048 163841 # /usr/src
l: 12578912517983776 4.2BSD 2048 163841 # /usr/obj
OpenBSD_49$
--
dmesg is
-
OpenBSD 4.9-current (kernel) #5: Wed Mar 23 23:58:17 IST 2011
r...@zimbu.vxindia.veritas.com:/home/amar/site-specific/builds/kernel
cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES
T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
,AES
real mem = 1998659584 (1906MB)
avail mem = 1955794944 (1865MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/26/10, BIOS32 rev. 0 @
0xfdbe0, SMBIOS rev. 2.6 @ 0xe0010 (78 entries)
bios0: vendor LENOVO version "6QET61WW (1.31 )" date 10/26/2010
bios0: LENOVO 3680LA2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT
TCPA SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4)
EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 132MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES
T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
,AES
cpu2 at mainbus0: apid
Re: Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
On Sat, Mar 26, 2011 at 05:26:06PM +0530, Amarendra Godbole wrote:
> Hi,
>
> I have run into a deadend trying to understand, and troubleshoot this
> problem. Hence, I would like some pointers. Following is what I did to
> get my OpenBSD system running, and then subsequently messing it up (in
> sequence):
>
> (1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
> Did reserve ~140G for Windows, and then installed OpenBSD as described
OpenBSD will reliably boot only if located <128GB. A
recent change has made this explicit until a more reliable
way of booting from >128GB can be found.
> in FAQ. Things were fine for a couple of months.
>
> (2) Installed Windows XP ghost image to the first partition. Sadly,
> ntldr was not installed so machine still booted directly into OpenBSD
>
> (3) Installed grub. Here is what /grub/menu.lst looks like:
> default 0 timeout 5
> title Windows XP
> root (hd0,0)
> chainloader +1
>
> title OpenBSD
> root (hd0,1)
> chainloader +1
>
> (4) grub started fine, and Windows XP boots fine, but when I try to
> boot OpenBSD, I get something like this:
> Loading...
> probing: <>
> disk: fd0 hd0+*
> >> OpenBSD/i386 BOOT 2.13
> open(hd0a:/etc/boot.conf): Invalid argument
> boot>
> booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
> failed(22). will try ...
>
> And OpenBSD never boots. I don't recall changing anything else. From
> what I know (very little), biosboot was able to load the 2nd stage
> bootloader, but it now failed loading the kernel image.
>
> I can boot successfully into OpenBSD using a 4.8 boot CD though. I
> tried running installboot again (mindlessly!), and get this error:
> --
> OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
> Password:
> boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
> /boot is 3 blocks x 16384 bytes
> fs block shift 2; part offset 293603940; inode block 32, offset 10792
> master boot record (MBR) at sector 0
> partition 0: type 0x07 offset 63 size 293603877
> partition 1: type 0xA6 offset 293603940 size 377487360
> installboot: invalid location: all of /boot must be < sector 268435455.
And here is the error now being generated. If you have a BIOS/Hardware
combo that can actually boot from >128GB, you can recompile installboot
and friends after changing the value of BIOSBOOT_MAXSEC in sys/sys/disklabel.h.
If you have any knowledge on how to reliably detect that the BIOS/Hardware
will correctly support EDD access beyond 128GB, we are very interested.
Ken
> --
>
> disklabel reads:
> --
> OpenBSD_49$ disklabel sd0
> # /dev/rsd0c:
> type: SCSI
> disk: SCSI disk
> label: ST9320423AS
> duid: 93cf9b951f02f209
> flags:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 255
> sectors/cylinder: 16065
> cylinders: 38913
> total sectors: 625142448
> boundstart: 0
> boundend: 0
> drivedata: 0
>
> 16 partitions:
> #size offset fstype [fsize bsize cpg]
> a: 2104508293603940 4.2BSD 2048 163841 # /
> b: 8385937295708448swap
> c:6251424480 unused
> d: 41945696304094400 4.2BSD 2048 163841 # /usr
> e: 4192960346040096 4.2BSD 2048 163841 # /tmp
> f: 20964832350233056 4.2BSD 2048 163841 # /usr/local
> g: 4192960371197888 4.2BSD 2048 163841 # /usr/X11R6
> h:125821056375390848 4.2BSD 2048 163841 # /home
> j: 8385952501211904 4.2BSD 2048 163841 # /var
> k: 8385920509597856 4.2BSD 2048 163841 # /usr/src
> l: 12578912517983776 4.2BSD 2048 163841 # /usr/obj
> OpenBSD_49$
> --
>
> dmesg is
> -
> OpenBSD 4.9-current (kernel) #5: Wed Mar 23 23:58:17 IST 2011
> r...@zimbu.vxindia.veritas.com:/home/amar/site-specific/builds/kernel
> cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz ("GenuineIntel"
> 686-class) 2.40 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
> ,AES
> real mem = 1998659584 (1906MB)
> avail mem = 1955794944 (1865MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 10/26/10, BIOS32 rev. 0 @
> 0xfdbe0, SMBIOS rev. 2.6 @ 0xe0010 (78 entries)
> bios0: vendor LENOVO version "6QET61WW (1.31 )" date 10/26/2010
> bios0: LENOVO 3680LA2
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT
> TCPA SSDT SSDT SSDT
> acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4)
> EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4)
> acpitimer0 at acpi0: 3579
Messed up OpenBSD boot after dualbooting via grub - cannot boot without OpenBSD boot CD.
Hi,
I have run into a deadend trying to understand, and troubleshoot this
problem. Hence, I would like some pointers. Following is what I did to
get my OpenBSD system running, and then subsequently messing it up (in
sequence):
(1) Installed OpenBSD/i386 on my Thinkpad X201, and built -current.
Did reserve ~140G for Windows, and then installed OpenBSD as described
in FAQ. Things were fine for a couple of months.
(2) Installed Windows XP ghost image to the first partition. Sadly,
ntldr was not installed so machine still booted directly into OpenBSD
(3) Installed grub. Here is what /grub/menu.lst looks like:
default 0 timeout 5
title Windows XP
root (hd0,0)
chainloader +1
title OpenBSD
root (hd0,1)
chainloader +1
(4) grub started fine, and Windows XP boots fine, but when I try to
boot OpenBSD, I get something like this:
Loading...
probing: <>
disk: fd0 hd0+*
>> OpenBSD/i386 BOOT 2.13
open(hd0a:/etc/boot.conf): Invalid argument
boot>
booting hd0a:/bsd: open hd0a:/bsd: Invalid argument
failed(22). will try ...
And OpenBSD never boots. I don't recall changing anything else. From
what I know (very little), biosboot was able to load the 2nd stage
bootloader, but it now failed loading the kernel image.
I can boot successfully into OpenBSD using a 4.8 boot CD though. I
tried running installboot again (mindlessly!), and get this error:
--
OpenBSD_49$ sudo /usr/mdec/installboot -n -v /boot /usr/mdec/biosboot sd0
Password:
boot: /boot proto: /usr/mdec/biosboot device: /dev/rsd0c
/boot is 3 blocks x 16384 bytes
fs block shift 2; part offset 293603940; inode block 32, offset 10792
master boot record (MBR) at sector 0
partition 0: type 0x07 offset 63 size 293603877
partition 1: type 0xA6 offset 293603940 size 377487360
installboot: invalid location: all of /boot must be < sector 268435455.
--
disklabel reads:
--
OpenBSD_49$ disklabel sd0
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: ST9320423AS
duid: 93cf9b951f02f209
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 38913
total sectors: 625142448
boundstart: 0
boundend: 0
drivedata: 0
16 partitions:
#size offset fstype [fsize bsize cpg]
a: 2104508293603940 4.2BSD 2048 163841 # /
b: 8385937295708448swap
c:6251424480 unused
d: 41945696304094400 4.2BSD 2048 163841 # /usr
e: 4192960346040096 4.2BSD 2048 163841 # /tmp
f: 20964832350233056 4.2BSD 2048 163841 # /usr/local
g: 4192960371197888 4.2BSD 2048 163841 # /usr/X11R6
h:125821056375390848 4.2BSD 2048 163841 # /home
j: 8385952501211904 4.2BSD 2048 163841 # /var
k: 8385920509597856 4.2BSD 2048 163841 # /usr/src
l: 12578912517983776 4.2BSD 2048 163841 # /usr/obj
OpenBSD_49$
--
dmesg is
-
OpenBSD 4.9-current (kernel) #5: Wed Mar 23 23:58:17 IST 2011
r...@zimbu.vxindia.veritas.com:/home/amar/site-specific/builds/kernel
cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
,AES
real mem = 1998659584 (1906MB)
avail mem = 1955794944 (1865MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/26/10, BIOS32 rev. 0 @
0xfdbe0, SMBIOS rev. 2.6 @ 0xe0010 (78 entries)
bios0: vendor LENOVO version "6QET61WW (1.31 )" date 10/26/2010
bios0: LENOVO 3680LA2
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT
TCPA SSDT SSDT SSDT
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4)
EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 132MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
,AES
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu2:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT
,AES
cpu3 at mainbus0: apid 5 (
