HOWTO Mount an usb file system at boot time ??? - Setup

This is a discussion on HOWTO Mount an usb file system at boot time ??? - Setup ; Hi everybody, does anyone know how to mount at boot time the file system from an usb pen driver? Which is the proper 'kernel command line' ? I tried with simply "root=/dev/sda1" but it doesn't work, this is the boot ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: HOWTO Mount an usb file system at boot time ???

  1. HOWTO Mount an usb file system at boot time ???

    Hi everybody,
    does anyone know how to mount at boot time the file system from an usb
    pen driver?
    Which is the proper 'kernel command line' ?

    I tried with simply "root=/dev/sda1" but it doesn't work,

    this is the boot log:


    dBUG> show
    base: 16
    baud: 115200
    server: 192.168.0.21
    client: 192.168.0.23
    gateway: 0.0.0.0
    netmask: 255.255.255.0
    filename: ./M5329claudia/M5329_image.bin
    filetype: Image
    autoboot: Autoboot from network
    ethaddr: 00:08:EE:00:F7:6D
    kcl: root=/dev/sda1
    dBUG> go
    Linux version 2.6.17.7-uc1 (claudia@LinuxHost) (gcc version 4.1.0
    (CodeSourcery Freescale 4.1-14)) #70 Thu May
    24 17:00:25 CEST 2007


    uClinux/COLDFIRE(m532x)
    COLDFIRE port done by Greg Ungerer, gerg@snapgear.com
    Flat model support (C) 1998,1999 Kenneth Albanowski, D. Jeff Dionne
    Built 1 zonelists
    Kernel command line: root=/dev/sda1
    PID hash table entries: 256 (order: 8, 1024 bytes)
    Console: colour dummy device 80x25
    Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
    Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
    Memory available: 30284k/32768k RAM, (1642k kernel code, 321k data)
    Mount-cache hash table entries: 512
    NET: Registered protocol family 16
    USB-MCF532x: (HOST module) EHCI device is registered
    USB-MCF532x: (OTG module) EHCI device is registered
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    NET: Registered protocol family 2
    IP route cache hash table entries: 256 (order: -2, 1024 bytes)
    TCP established hash table entries: 1024 (order: 0, 4096 bytes)
    TCP bind hash table entries: 512 (order: -1, 2048 bytes)
    TCP: Hash tables configured (established 1024 bind 512)
    TCP reno registered
    JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
    io scheduler noop registered
    io scheduler cfq registered (default)
    Initing M532x Framebuffer
    Console: switching to colour frame buffer device 80x30
    fb0: M532x FB frame buffer device
    ISA-Philips-Basic-CAN memory mapped CAN Driver 3.0_ColdFire_FlexCAN
    (c) May 22 2007 15:18:47
    ColdFire internal UART serial driver version 1.00
    ttyS0 at 0xfc060000 (irq = 90) is a builtin ColdFire UART
    ttyS1 at 0xfc064000 (irq = 91) is a builtin ColdFire UART
    RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
    loop: loaded (max 8 devices)
    nbd: registered device at major 43
    FEC ENET Version 0.2
    fec: PHY @ 0x1, ID 0x20005c90 -- DP83848
    eth0: ethernet 00:08:ee:00:f7:6d
    uclinux[mtd]: RAM probe address=0x4020b298 size=0x12000
    Creating 1 MTD partitions on "RAM":
    0x00000000-0x00012000 : "ROMfs"
    uclinux[mtd]: set ROMfs to be root filesystem
    NAND device: Manufacturer ID: 0x20, Chip ID: 0x73 (ST Micro NAND 16MiB
    3,3V 8-bit)
    Scanning device for bad blocks
    Creating 1 MTD partitions on "NAND 16MiB 3,3V 8-bit":
    0x00000000-0x01000000 : "M5329 flash partition 1"
    QSPI: spi->max_speed_hz 250000
    QSPI: Baud set to 160
    COLDFIRE-QSPI: probed and master registered
    QSPI device driver installed OK
    ColdFire QSPI (at 0x4010ad54) called request_irq without a dev_id!
    QSPI: Unable to attach ColdFire QSPI interrupt vector=95
    usbmon: debugfs is not available
    MCF532x USB EHCI: is found. ID=0x5 Rev=0x41
    ehci ehci.1: EHCI Host Controller
    ehci ehci.1: new USB bus registered, assigned bus number 1
    ehci ehci.1: irq 176, io mem 0xfc0b4000
    ehci ehci.1: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    MCF532x USB EHCI: is found. ID=0x5 Rev=0x41
    ehci ehci.0: EHCI Host Controller
    ehci ehci.0: new USB bus registered, assigned bus number 2
    ehci ehci.0: irq 175, io mem 0xfc0b0000
    ehci ehci.0: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 1 port detected
    ehci-mcf532x: can't find transceiver!
    Initializing USB Mass Storage driver...
    usb 1-1: new full speed USB device using ehci and address 2
    usb 1-1: not running at top speed; connect to a high speed hub
    usb 1-1: configuration #1 chosen from 1 choice
    scsi0 : SCSI emulation for USB Mass Storage devices
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new driver usbhid
    drivers/usb/input/hid-core.c: v2.6:USB HID core driver
    ts: Compaq touchscreen protocol output
    ads7843 spi1.1: touchscreen, irq 68
    input: ADS784x Touchscreen as /class/input/input0
    TCP bic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    Root-NFS: No NFS server available, giving up.
    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
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
    block(2,0)


    thanks in advance
    Claudia


  2. Re: HOWTO Mount an usb file system at boot time ???

    cla14ago wrote:
    > does anyone know how to mount at boot time the file system from an usb
    > pen driver?
    > I tried with simply "root=/dev/sda1" but it doesn't work,


    > Initializing USB Mass Storage driver...
    > usb 1-1: new full speed USB device using ehci and address 2


    Had the same problem a few minutes ago and found the solution:
    Add the kernel parameter rootdelay=5 after root=/dev/sda1.
    That lets the kernel wait 5 seconds before trying to access the
    root filesystem. These 5 seconds are needed for the usb-storage system
    to find the attached USB drive.


+ Reply to Thread