Hi, thanks for your suggestions.
I have my kernel image compiled with usb, usb-storage, ext2/3 and it does not
work. The usbkey is detecting when loading the kernel image though. This is
what I get:
RedBoot> exec -c "console=ttyAM0,115200 root=/dev/sda1 rootwait"
Using base address 0x00218000 and length 0x001bbdf0
Uncompressing
Linux........................................................................................................
............. done, booting the kernel.
Linux version 2.6.27.4-matt (gcc version 4.1.0) #11 PREEMPT Thu
May 21 15:47:45 IST 2009
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=40007177
Machine: Technologic Systems TS-72xx SBC
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 4 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: console=ttyAM0,115200 root=/dev/sda1 rootwait
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 8MB 8MB 8MB 8MB = 32MB total
Memory: 28640KB available (3336K code, 333K data, 116K init)
Calibrating delay loop... 99.73 BogoMIPS (lpj=498688)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 592 bytes
NET: Registered protocol family 16
ep93xx: PLL1 running at 400 MHz, PLL2 at 192 MHz
ep93xx: FCLK 200 MHz, HCLK 100 MHz, PCLK 50 MHz
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (extended precision)
msgmni has been set to 55
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver2 ports, IRQ sharing disabled
Serial: AMBA driver
apb:uart1: ttyAM0 at MMIO 0x808c0000 (irq = 52) is a AMBA
console [ttyAM0] enabled
apb:uart2: ttyAM1 at MMIO 0x808d0000 (irq = 54) is a AMBA
apb:uart3: ttyAM2 at MMIO 0x808e0000 (irq = 55) is a AMBA
ep93xx-eth version 0.1 loading
ep93xx_mii_bus: probed
Generic PHY 0:01: PHY supports MII frame preamble suppression
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)
net eth0: ep93xx on-chip ethernet, IRQ 39, 00:d0:69:41:ce:62
Driver 'sd' needs updating - please use bus_type methods
GPIO-18 autorequested
usbmon: debugfs is not available
ep93xx-ohci ep93xx-ohci: EP93xx OHCI
ep93xx-ohci ep93xx-ohci: new USB bus registered, assigned bus number 1
ep93xx-ohci ep93xx-ohci: irq 56, io mem 0x80020000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EP93xx OHCI
usb usb1: Manufacturer: Linux 2.6.27.4-matt ohci_hcd
usb usb1: SerialNumber: ep93xx
usb 1-3: new full speed USB device using ep93xx-ohci and address 2
usb 1-3: configuration #1 chosen from 1 choice
usb 1-3: New USB device found, idVendor=1307, idProduct=0165
usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-3: Product: USB Flash Drive
usb 1-3: Manufacturer: USB 2.0
usb 1-3: SerialNumber: a524c4270f45ea
usbcore: registered new interface driver libusual
usbcore: registered new interface driver usbtest
mice: PS/2 mouse device common for all mice
ep93xx-rtc ep93xx-rtc: rtc core: registered ep93xx as rtc0
rtc-m48t86 rtc-m48t86: rtc core: registered m48t86 as rtc1
rtc-m48t86 rtc-m48t86: battery ok
i2c /dev entries driver
i2c-gpio i2c-gpio.0: using pins 14 (SDA) and 15 (SCL)
Registered led device: green
Registered led device: red
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
IPv4 over IPv4 tunneling driver
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
ep93xx-rtc ep93xx-rtc: setting system clock to 1970-01-01 00:00:43 UTC (43)
Waiting for root device /dev/sda1...
regards,
Magda
--- In Matthieu Crapet <> wrote:
>
> No initrd is required. /dev/sda1 is discovered at kernel boot time.
> then "mount /" is done. If everything is builtin, it's fine.
> I tested it with lenny rootdisk.
>
> Regards,
> Matt
>
> j.chitte wrote:
> >
> >
> > --- In <ts-7000%40yahoogroups.com>,
> > Matthieu Crapet <mcrapet@> wrote:
> > >
> > > Hi,
> > >
> > > Make sure that your kernel has buildin : usb + usb-storage + fs ext2/3.
> > >
> > > RedBoot> load -r -b 0x00218000 -h 192.168.1.48 zImage
> > > RedBoot> exec -c "console=ttyAM0,115200 root=/dev/sda1 rootwait"
> > >
> > > The "rootwait" is important because the /dev/sda1 (which is your usbkey
> > > is not discovered yet).
> > >
> > > I have made recently a debian rootdisk (eabi) for somebody. It's basic
> > > 144mo.
> > > http://mcrapet.free.fr/tmp/nfsroot-lenny-20090508.tar.bz2
> > <http://mcrapet.free.fr/tmp/nfsroot-lenny-20090508.tar.bz2>
> > > Hope it can help.
> > >
> > > Regards,
> > > Matthieu
> > >
> > >
> >
> > Isn't it necessary to provide an initrd with a basic /dev structure ?
> >
> > Thanks for that image , it could be a useful test tool.
> >
> > regards.
> >
> > > s.magda@ wrote:
> > > >
> > > >
> > > >
> > > > I am trying to boot from a USB key by running the following command:
> > > >
> > > > exec -c "console=ttyAM0,115200 root=/dev/sda1"
> > > >
> > > > and my error message is:
> > > >
> > > > "VFS: Unable to mount root fs via NFS, trying floppy.
> > > > VFS: Cannot open root device sda1 or unknown-block (2,0)
> > > > Please append a correct "root=" boot option: here are the available
> > > > partitions:
> > > > kernel panic - not syncing: VFS: unable to mount root fs on
> > > > unknown-block (2,0)"
> > > >
> > > > I've created a ext2 partition on sda1 with the debian system on it by
> > > > executing:
> > > > > fdisk /dev/sda1
> > > > >mkfs.ext2 /dev/sda1
> > > > >mount /dev/sda1 /mnt
> > > > >tar -C /mnt -xf ./debian-sarge-udev-19-05-2009_backup.tgz
> > > > >fsck /dev/sda1
> > > >
> > > > I wonder if there is something that I have to activate on my kernel
> > > > configuration to enable booting from USB flash, I am using 2.6.27.4
> > > > vanilla kernel with Matt's patches.
> > > >
> > > > Thanks a million,
> > > >
> > > > Magda
> > > >
> > > > -
> > > > -- In <ts-7000%40yahoogroups.com>
> > <ts-7000%40yahoogroups.com>,
> > > > Jason Stahls <jason@> wrote:
> > > > >
> > > > > s.magda@ wrote:
> > > > > > I have the exact same problem!
> > > > > >
> > > > > > Can anyone help?
> > > > >
> > > > > What command line in Redboot are you guys using, and where are you
> > > > > trying to boot from?
> > > > >
> > > > > This,
> > > > >
> > > > > Root-NFS: No NFS server available, giving up.
> > > > > > VFS: Unable to mount root fs via NFS, trying floppy.
> > > > > > VFS: Cannot open root device "usb0" or unknown-block(2,0)
> > > > > > Please append a correct "root=" boot option
> > > > > > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > > > unknown-block(2,0)
> > > > >
> > > > >
> > > > > Tells you that it was unable to mount the root FS, this is
> > passed to
> > > > the
> > > > > kernel from reboot as root=
> > > > >
> > > > > --
> > > > > Jason Stahls
> > > > >
> > > >
> > > >
> > >
> >
> >
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|