**** BEGIN LOGGING AT Sun Feb 27 02:59:57 2011
Feb 27 05:42:02 <dmb_> heh
Feb 27 10:43:12 <CapnKernel1> Hello.
Feb 27 10:43:41 <CapnKernel1> I'm using a SheevaPlug for the first time.  I can't get the bootloader to see USB devices.
Feb 27 10:44:01 <CapnKernel1> When I type "usb start", the bootloader doesn't see the devices, just the hub.
Feb 27 10:44:21 <CapnKernel1> The two devices are a USB memory device, and a USB to SATA bridge to a SATA hard disk.
Feb 27 10:45:00 <kerio> booting from usb is... "flaky"
Feb 27 10:45:01 <kerio> at best
Feb 27 10:45:59 <CapnKernel1> please tell me more.
Feb 27 10:46:42 <CapnKernel1> Do you mean the bootloader only sees some devices, or that running from flash has problems?
Feb 27 10:50:40 <kerio> no, booting from usb is very luck-dependant
Feb 27 10:51:48 <CapnKernel1> By "luck" do you mean with the same equipment it sometimes works and sometimes doesn't?
Feb 27 10:52:11 <CapnKernel1> Or do you mean it only works with some equipment, but the equipment that works, works 100% of the time?
Feb 27 10:53:24 <CapnKernel1> Is it a Linux problem, a bootloader problem, or a hardware problem?
Feb 27 10:54:02 <kerio> it's a bootloader problem, and with the same equipment sometimes works and sometimes doesn't
Feb 27 10:54:14 <kerio> maybe upgrading uboot would make it easier, but it's not guaranteed
Feb 27 10:54:22 <CapnKernel1> I see.
Feb 27 10:54:24 <kerio> me, i just boot from the NAND
Feb 27 10:54:28 <kerio> (fuck yeah)
Feb 27 10:54:48 <CapnKernel1> How about SD?  Is that unreliable too?
Feb 27 10:55:19 <CapnKernel1> (I'd like to try something out [Fedora ARM] without changing the NAND, at least not until I've verified Fedora ARM will do what I want)
Feb 27 10:55:51 <CapnKernel1> Maybe I can put the kernel on SD, and the root FS on USB.  Then the bootloader doesn't have to do anything with USB.
Feb 27 10:55:53 <kerio> the sd is reliable, afaik
Feb 27 10:56:05 <kerio> you can also just keep trying :)
Feb 27 10:56:38 <kerio> put reset at the end of the bootcmd
Feb 27 10:56:40 <CapnKernel1> By "keep trying", do you mean that if I run "usb start" enough times, eventually the bootloader will see an attached USB device?
Feb 27 10:56:51 <kerio> or that, yeah
Feb 27 10:56:52 <kerio> maybe!
Feb 27 10:57:22 <kerio> not sure if they fixed it in the latest uboots
Feb 27 10:59:23 <CapnKernel1> Discovering this isn't giving me the first-user experience I was hoping for :-(
Feb 27 10:59:35 <CapnKernel1> kerio: But thanks for your advice
Feb 27 11:00:24 <CapnKernel1> Someone else had hardware problems: http://plugcomputer.org/plugforum/index.php?topic=828.0
Feb 27 11:01:14 <kerio> just boot from the nand
Feb 27 11:02:12 <CapnKernel1> I see.  If the NAND linux can see a USB device, it's not defective hardware.
Feb 27 11:11:22 <CapnKernel1> I'm in the NAND debian Linux.  Both the USB memory device and the SATA hard disk are recognised, so it's unlikely to be faulty hardware.
Feb 27 11:13:37 <CapnKernel1> Cool, now the bootloader recognises the SATA hd
Feb 27 11:13:42 <kerio> it's not faulty hardware, it's a common problem in the bootloader
Feb 27 11:13:54 <CapnKernel1> ok
Feb 27 11:22:56 <CapnKernel1> (Getting message "Error: unrecognized/unsupported machine ID")
Feb 27 11:25:08 <CapnKernel1> http://pastebin.com/WwbEnQ67
Feb 27 11:34:03 <CapnKernel1> Something to do with "arcNumber"?
Feb 27 13:46:40 <mwester> CapnKernel1,  check the plug wiki -- search for arcNumber; IIRC the default passed in by the bootloader is a number chosen by Marvell rather than the number assigned by the kernel folks. So if you boot a non-Marvell kernel, you need to set a u-boot variable to pass in the correct machine id.
Feb 27 13:51:42 <CapnKernel1> mwester: thank you
Feb 27 14:11:13 <kerio> mwester: i thought the problem was that the default kernel didn't care about arcNumber because it was compiled in
Feb 27 14:11:21 <kerio> and so arcNumber wasn't defined by default
**** ENDING LOGGING AT Mon Feb 28 02:59:57 2011