Re: Supermicro MBD-A1SAi-2550F
# a...@alexhornung.com / 2014-07-25 10:34:35 +0100: > I have a A1SAi-2550F running DragonFly. Installing from a usb stick was > no problem as long as it was in one of the usb2.0 ports. In the usb3.0 > ports it couldn't mountroot because the xhci driver wasn't loaded by > default. > > I have had neither bootloader nor other issues with the A1SAi-2550F and > DragonFly. thank you sir! the lack of xhci was indeed the problem. i went to the boot loader prompt: OK load kernel OK load xhci OK boot and it's booted to completion! is it time to have xhci loaded by default? -- roman
Re: Supermicro MBD-A1SAi-2550F
>> prompt> lsdev >> prompt> set vfs.root.mountfrom="ufs:da0s1a" >> prompt> boot > > OK lsdev > cd devices: > disk devices: > disk0: BIOS drive C: > * disk0s1a: FFS This is the root device. > disk1: BIOS drive D: > disk1s1: Unknown fs: 0xee > disk2: BIOS drive E: > disk2s1: Unknown fs: 0xee > pxe devices: > OK set vfs.root.mountfrom="ufs:da0s1a" > OK boot > kernel text=0x972528 data=... > > ... > > at this point, disk1, disk2 are da0, da1; disk0 is (ISTR) da8. Since disk0 has the rootdev, try da8s1a, > set vfs.root.mountfrom="ufs:da8s1a" > boot Peeter --
Re: Supermicro MBD-A1SAi-2550F
On 2014-06-21 19:23, Roman Neuhauser wrote: having just bought a Supermicro MBD-A1SAi-2550F motherboard[1] i proceeded and failed to boot 3.8.1 and 3.8.0 from several different USB sticks. FreeBSD-10.0-RELEASE-amd64-memstick.img boots normally. the system hangs on exit from the F1/F5 menu (boot0 i believe?). I have a A1SAi-2550F running DragonFly. Installing from a usb stick was no problem as long as it was in one of the usb2.0 ports. In the usb3.0 ports it couldn't mountroot because the xhci driver wasn't loaded by default. I have had neither bootloader nor other issues with the A1SAi-2550F and DragonFly. Cheers, Alex
Re: Supermicro MBD-A1SAi-2550F
# karu.pr...@gmail.com / 2014-07-24 12:35:09 +0900: > Hi Roman > > That's good to hear! At least we know now that it was the A20 bug that > prevented booting in the first place. > > I see the mount error every time I boot from a memstick. And I believe > I understand what is the problem but don't know where or how to fix it > in the code; at least not now. A workaround could be to specify the > correct root device at the boot menu. When you see the boot menu, go > to prompt, ie hit ''Esc" or "9"(?). Unfortunately it's not > straightforward to find the correct root device since the boot program > and the kernel name it differently. You have to guess and try. The > devices you can get with lsdev, > > prompt> lsdev > prompt> set vfs.root.mountfrom="ufs:da0s1a" > prompt> boot OK lsdev cd devices: disk devices: disk0: BIOS drive C: * disk0s1a: FFS disk1: BIOS drive D: disk1s1: Unknown fs: 0xee disk2: BIOS drive E: disk2s1: Unknown fs: 0xee pxe devices: OK set vfs.root.mountfrom="ufs:da0s1a" OK boot kernel text=0x972528 data=... ... at this point, disk1, disk2 are da0, da1; disk0 is (ISTR) da8. Mounting root from ufs:da0s1a no disk named 'da0s1a' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 ... mountroot> at this point the keyboard is dead (it's a wireless Logitech thing connected using a USB dongle). > if that does not work, substitute for da5s1a and da8s1a and try again. > Hope something works! my 10min quota is drained today, cu later :) -- roman
Re: Supermicro MBD-A1SAi-2550F
On Tue, Jun 24, 2014 at 12:35 AM, Roman Neuhauser wrote: > now, before i get to boot-debugging-related questions... I did some debugging and made some progress but no solution yet. I compared the sys/boot/pc32/boot1.S of DFly and FBSD and found that DFly got stuck in the subroutine seta20 that enables the A20 gate. (I put some putstr-s around the loop; unfortunately no gdb in this situation.) FBSD code has a timecount which exits the loop without enabling it if enough time has passed, so it gets through the loop. The reason DFly got stuck was that apparently apple has discarded legacy hardware A20 and DFly was spinning forever in that loop trying to set the gate. Interestingly, DFly's cdboot has that timecount, otherwise it would not boot on a macbook either. So I got boot1.S to print a char just before jumping to boot2 at line 265. However, it did not get to boot2. I have no idea why. Any ideas how to debug or where to look further? Peeter --
Re: Supermicro MBD-A1SAi-2550F
# jus...@shiningsilence.com / 2014-06-21 17:46:24 -0400: > On Sat, Jun 21, 2014 at 2:23 PM, Roman Neuhauser wrote: > > having just bought a Supermicro MBD-A1SAi-2550F motherboard[1] > > i proceeded and failed to boot 3.8.1 and 3.8.0 from several > > different USB sticks. FreeBSD-10.0-RELEASE-amd64-memstick.img > > boots normally. > > > > the system hangs on exit from the F1/F5 menu (boot0 i believe?). > > > > PXE should work but i still prefer having a means of booting > > from a USB stick. what can i do to help fix this? > > > > [1] http://www.supermicro.com/products/motherboard/atom/x10/a1sai-2550f.cfm > > Try the 3.6.3 image - we switched USB to a new version between now and > then. If it does work, immediately upgrade to 3.8 and see what > happens. If it still has problems, we can hopefully get more > debugging info from a fully installed system. as i mentioned in another email, 3.6.3 img suffered from the same problem; 3.8.1 *iso* boots ok when i mount it using the vendor-provided IPMI client[2]. now, before i get to boot-debugging-related questions... i was planning to run a software RAID1 on the two SSDs i have in the machine, however, the system presents them as da{0,1}, and natacontrol shows nothing. do i have another option besides buying a controller card? i want to use HAMMER for the whole thing, if it makes any difference. [2] ftp://ftp.supermicro.com/utility/SMCIPMITool/Jar/SMCIPMITool_2.8.1_jar_20140319.zip -- roman
Re: Supermicro MBD-A1SAi-2550F
On Mon, Jun 23, 2014 at 12:36 AM, Roman Neuhauser wrote: >> The hang is immediately after the boot prompt; I've seen this since 4 >> yrs ago on my laptop (macbookpro) and believe it could be due to >> (U)EFI that I see your machine also has. > > it's all set to "legacy" mode, i don't think this is the culprit. > (i tried with UEFI, with indistinguishable result. Sure agreed. What I meant was that if you have a UEFI machine then even when it emulates BIOS style booting, then curiously DFly does not boot whereas FBSD does. Peeter --
Re: Supermicro MBD-A1SAi-2550F
# karu.pr...@gmail.com / 2014-06-22 17:10:33 +0900: > Correct me if Im wrong but I understand you don't even see kernel > booting? If true, then seems not related to the new usb stack since > this kicks in much later in the booting process. seems right. > The hang is immediately after the boot prompt; I've seen this since 4 > yrs ago on my laptop (macbookpro) and believe it could be due to > (U)EFI that I see your machine also has. it's all set to "legacy" mode, i don't think this is the culprit. (i tried with UEFI, with indistinguishable result. -- roman
Re: Supermicro MBD-A1SAi-2550F
# jus...@shiningsilence.com / 2014-06-21 17:46:24 -0400: > Try the 3.6.3 image - we switched USB to a new version between now and > then. If it does work, immediately upgrade to 3.8 and see what > happens. If it still has problems, we can hopefully get more > debugging info from a fully installed system. same outcome: gets "stuck" leaving boot0. -- roman
Re: Supermicro MBD-A1SAi-2550F
I don't think FreeBSD uses boot0 on their memstick image. At least I didn't get the F-key menu last time... You could try making a dragonfly image without boot0. Either by commenting out the boot0cfg -B -o nopacket line in nrelease/Makefile or by mounting it as a vn device and running fdisk -IB on it. I'm not 100% sure the second way will work. cheers, Max On Sun, Jun 22, 2014 at 10:10 AM, karu.pruun wrote: > Correct me if Im wrong but I understand you don't even see kernel > booting? If true, then seems not related to the new usb stack since > this kicks in much later in the booting process. The hang is > immediately after the boot prompt; I've seen this since 4 yrs ago on > my laptop (macbookpro) and believe it could be due to (U)EFI that I > see your machine also has. Also, might be more related to boot (ie > boot1 + boot2) rather than boot0 since I have a situation where DFly > and FBSD both live in the MBR partitions and DFly's boot0 is able to > boot FBSD, but not itself! Exactly the same phenomenon: I get the boot > prompt (where actually the partitions are F1 = DFly, F3 = FBSD) > > F1 DF/FBSD > F3 DF/FBSD > > and then hitting F3 boots FBSD, but F1 hangs. I can still boot DFly > with an ISO image (get the prompt, set currdev etc and boot), but it's > cumbersome. > > I don't know what the fix is; would like to hear if anyone has a solution. > > In the future (when I'll have some more time), I'd be interested in > working towards integrating UEFI booting into DFly. > > Btw, when you'll get your machine to boot, can you tell if it works > with the new usb? > > Peeter > > -- > > > > > On Sat, Jun 21, 2014 at 2:23 PM, Roman Neuhauser > wrote: > >> having just bought a Supermicro MBD-A1SAi-2550F motherboard[1] > >> i proceeded and failed to boot 3.8.1 and 3.8.0 from several > >> different USB sticks. FreeBSD-10.0-RELEASE-amd64-memstick.img > >> boots normally. > >> > >> the system hangs on exit from the F1/F5 menu (boot0 i believe?). > >> > >> PXE should work but i still prefer having a means of booting > >> from a USB stick. what can i do to help fix this? > >> > >> http://www.supermicro.com/products/motherboard/atom/x10/a1sai-2550f.cfm > >> > >> -- > >> roman >
Re: Supermicro MBD-A1SAi-2550F
Correct me if Im wrong but I understand you don't even see kernel booting? If true, then seems not related to the new usb stack since this kicks in much later in the booting process. The hang is immediately after the boot prompt; I've seen this since 4 yrs ago on my laptop (macbookpro) and believe it could be due to (U)EFI that I see your machine also has. Also, might be more related to boot (ie boot1 + boot2) rather than boot0 since I have a situation where DFly and FBSD both live in the MBR partitions and DFly's boot0 is able to boot FBSD, but not itself! Exactly the same phenomenon: I get the boot prompt (where actually the partitions are F1 = DFly, F3 = FBSD) F1 DF/FBSD F3 DF/FBSD and then hitting F3 boots FBSD, but F1 hangs. I can still boot DFly with an ISO image (get the prompt, set currdev etc and boot), but it's cumbersome. I don't know what the fix is; would like to hear if anyone has a solution. In the future (when I'll have some more time), I'd be interested in working towards integrating UEFI booting into DFly. Btw, when you'll get your machine to boot, can you tell if it works with the new usb? Peeter -- > On Sat, Jun 21, 2014 at 2:23 PM, Roman Neuhauser wrote: >> having just bought a Supermicro MBD-A1SAi-2550F motherboard[1] >> i proceeded and failed to boot 3.8.1 and 3.8.0 from several >> different USB sticks. FreeBSD-10.0-RELEASE-amd64-memstick.img >> boots normally. >> >> the system hangs on exit from the F1/F5 menu (boot0 i believe?). >> >> PXE should work but i still prefer having a means of booting >> from a USB stick. what can i do to help fix this? >> >> http://www.supermicro.com/products/motherboard/atom/x10/a1sai-2550f.cfm >> >> -- >> roman
Re: Supermicro MBD-A1SAi-2550F
Try the 3.6.3 image - we switched USB to a new version between now and then. If it does work, immediately upgrade to 3.8 and see what happens. If it still has problems, we can hopefully get more debugging info from a fully installed system. On Sat, Jun 21, 2014 at 2:23 PM, Roman Neuhauser wrote: > having just bought a Supermicro MBD-A1SAi-2550F motherboard[1] > i proceeded and failed to boot 3.8.1 and 3.8.0 from several > different USB sticks. FreeBSD-10.0-RELEASE-amd64-memstick.img > boots normally. > > the system hangs on exit from the F1/F5 menu (boot0 i believe?). > > PXE should work but i still prefer having a means of booting > from a USB stick. what can i do to help fix this? > > http://www.supermicro.com/products/motherboard/atom/x10/a1sai-2550f.cfm > > -- > roman