Hi Jim, Thanks for the detailed feedback.
Jim Pingle wrote: > On 12/2/2011 6:38 PM, Soren Kristensen wrote: >> In principle all recent USB flash sticks should work (older ones might >> not report back correctly what they are, the BIOS don't have any >> "special handling" table like most OS drivers). By older ones we're >> talking about 5+ years. >> >> I would like to see comBIOS screen dump until stop, and know the exact >> part so I can get one to investigate, I want to get it to *just* work. > > I updated to 1.41a and still had issues. I think it may just not like > some of the sticks I'm using. Check out the size it's reporting: Yes, it seems like that it don't like some sticks.... I have ordered some more USB flash sticks to test with, incl. one that another person reported the same problem with. Once I get them in a couple of days I should be able to identify the exact problem and fix it, it's most likely an issue with the sticks need a little time to become ready.... Be ensure I can see what's going on I also ordered an USB bus analyzer. Stopping at mounting / is probably out of my hand, once it get to there FreeBSD have taken over.... Best Regards, Soren Kristensen CEO & Chief Engineer Soekris Engineering, Inc. > ===================================================== > > comBIOS ver. 1.41a 20111203 Copyright (C) 2000-2011 Soekris Engineering. > > net6501 > > 1024 Mbyte Memory CPU Atom E6xx 1000 Mhz > > > SATA AHCI BIOS ver. 0.6 20110902 Copyright (C) 2003-2011 Intel Corporation > > Controller Bus#02, Device#06, Function#00: 02 Ports, 01 Devices > Port-00: Hard Disk, WDC WD2500BEVS-00UST0 > Port-01: No device detected > > Soekris USB Expansion ROM ver. 1.01 20111203 > > 81: USB 01 Xlt -2-32 Mbyte > > > Initializing Intel(R) Boot Agent GE v1.3.72 > PXE 2.1 Build 089 (WfM 2.0) > > Slot Vend Dev ClassRev Cmd Stat CL LT HT Base1 Base2 Int > -------------------------------------------------------------------- > 00:00:0 8086 4114 06000003 0007 0000 00 00 00 00000000 00000000 > 00:23:0 8086 8184 06040000 0107 0010 08 00 01 1FFF1000 A0FFA000 10 > 00:24:0 8086 8185 06040000 0107 0010 08 00 01 3FFF2000 A2FFA100 11 > 00:25:0 8086 8180 06040000 0107 0010 08 00 01 5FFF4000 A4FFA300 05 > 00:26:0 8086 8181 06040000 0107 0010 08 00 01 0FFF1000 00FFA000 09 > 00:31:0 8086 8186 06010000 0003 0000 00 00 80 00000000 00000000 > 02:02:0 8086 8804 0C031001 0106 0010 00 00 80 A0000B00 00000000 09 > 02:02:1 8086 8805 0C031001 0106 0010 00 00 80 A0000C00 00000000 09 > 02:02:2 8086 8806 0C031001 0106 0010 00 00 80 A0000D00 00000000 09 > 02:02:3 8086 8807 0C032001 0106 0010 00 00 80 A0000E00 00000000 09 > 02:06:0 8086 880B 01060101 0107 0010 00 00 00 00000000 00000000 11 > 02:08:0 8086 880C 0C031001 0106 0010 00 00 80 A0004800 00000000 10 > 02:08:1 8086 880D 0C031001 0106 0010 00 00 80 A0004900 00000000 10 > 02:08:2 8086 880E 0C031001 0106 0010 00 00 80 A0004A00 00000000 10 > 02:08:3 8086 880F 0C032001 0106 0010 00 00 80 A0004B00 00000000 10 > 02:10:1 8086 8811 07000200 0107 0010 00 00 80 00001041 A0004D00 09 > 02:10:2 8086 8812 07000200 0107 0010 00 00 80 00001049 A0004D10 09 > 02:12:2 8086 8817 0C800000 0106 0010 00 00 80 00000000 A0005000 05 > 02:12:3 8086 8818 0C090000 0106 0010 00 00 80 00000000 A0005200 05 > 03:00:0 111D 803A 0604000E 0107 0010 08 00 01 3FFF2000 A2FFA100 > 05:00:0 8086 10D3 02000000 0107 0010 08 00 00 A1000000 00000000 09 > 06:00:0 8086 10D3 02000000 0107 0010 08 00 00 A2000000 00000000 10 > 08:00:0 111D 803A 0604000E 0107 0010 08 00 01 5FFF4000 A4FFA300 > 10:00:0 8086 10D3 02000000 0107 0010 08 00 00 A3000000 00000000 10 > 11:00:0 8086 10D3 02000000 0107 0010 08 00 00 A4000000 00000000 11 > > 4 Seconds to automatic boot. Press Ctrl-P for entering Monitor. > > comBIOS Monitor. Press ? for help. > >> boot 81 > > No Boot device available, enter monitor. > > > comBIOS Monitor. Press ? for help. > > ===================================================== > > I get the same output with two different 2GB USB sticks. > > One of the keys that does not work is: > da0:<PNY USB 2.0 FD PMAP> Removable Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 1968MB (4030464 512 byte sectors: 255H 63S/T 250C) > > usbconfig -u 3 -a 2 dump_device_desc > ugen3.2:<USB 2.0 FD PNY> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON > > bLength = 0x0012 > bDescriptorType = 0x0001 > bcdUSB = 0x0200 > bDeviceClass = 0x0000 > bDeviceSubClass = 0x0000 > bDeviceProtocol = 0x0000 > bMaxPacketSize0 = 0x0040 > idVendor = 0x154b > idProduct = 0x0005 > bcdDevice = 0x0100 > iManufacturer = 0x0001<PNY> > iProduct = 0x0002<USB 2.0 FD> > iSerialNumber = 0x0003<6E6315000325> > bNumConfigurations = 0x0001 > > If there is any other info I can get about the device(s), let me know. > > I tracked down a 4GB stick and it was recognized OK: > > 81: USB 01 SanDisk U3 Cruzer Micro Xlt 995-128-63 4014 Mbyte > > And that does start to boot but stops at mounting root. The fstab is > right, as it uses ufs labels, and I already had a 10 second boot delay > to ensure the USB device was ready for the OS to mount it. That could > still be in the OS though I'll need to tweak it a bit to say for sure > what is happening there. It doesn't fail to a mountroot> prompt, it just > stops. > > For reference, one of the memstick images I'm trying to use can be found > here: > http://files.chi.pfsense.org/mirror/downloads/pfSense-memstick-2.0-RELEASE-i386.img.gz > > I did make one change. Because that image does not have the serial > console enabled I mounted the image on another FreeBSD box and activated > the serial console in /boot/loader.conf.local like so: > boot_multicons="YES" > boot_serial="YES" > > I moved on to a different test case after that: NanoBSD. If I try to > boot NanoBSD it is now at least getting to boot0 but at the F1/F2 prompt > to boot either NanoBSD slice, I just get # marks repeatedly. We've seen > this before on ALIX boards with older BIOS (Before 0.99h) and some other > BIOS implementations that for whatever reason did not like the method it > was using. > > I also tried flipping packet/nopacket on the boot loader with no > difference, I tried with boot0 and boot0sio and in each case I ended up > with just #'s like so: > > ============================= >> boot 81 > > 1 pfSense > 2 pfSense > 5 Drive 0 > > F6 PXE > Boot: 1 ##### > ============================= > > The NanoBSD image I used was this one: > http://files.chi.pfsense.org/mirror/downloads/pfSense-2.0-RELEASE-2g-i386-nanobsd.img.gz > Unlike the memstick image above the NanoBSD image has serial console by > default so it should really just work if imaged and booted. > > So in all it's still progressing, keep up the great work! > > Jim > _______________________________________________ > Soekris-tech mailing list > Soekris-tech@lists.soekris.com > http://lists.soekris.com/mailman/listinfo/soekris-tech _______________________________________________ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
