Re: usb-storage on SMP?

From: William Park (opengeometry_at_yahoo.ca)
Date: 01/17/05

  • Next message: Fruhwirth Clemens: "Re: Announce loop-AES-v3.0b file/swap crypto package"
    Date:	Mon, 17 Jan 2005 15:55:19 -0500
    To: Paulo Marques <pmarques@grupopie.com>
    
    

    On Mon, Jan 17, 2005 at 08:01:23PM +0000, Paulo Marques wrote:
    > William Park wrote:
    > >On Mon, Jan 17, 2005 at 06:26:33PM +0100, Rafael J. Wysocki wrote:
    > >
    > >>On Monday, 17 of January 2005 18:17, Thomas Zehetbauer wrote:
    > >>
    > >>>Hi,
    > >>>
    > >>>can anyone confirm that writing to usb-storage devices is working
    > >>>on SMP systems?
    > >>
    > >>Generally, it is. Recently, I've written some stuff to a USB
    > >>pendrive (using 2.6.10-ac7 or -ac9).
    > >
    > >
    > >Same here with Abit VP6 dual-P3 and 2.6.10. It shows up as /dev/sda,
    > >and I can do anything that I would do with normal harddisk.
    > >
    > >But, I still can't boot from it. :/ I can now mount it as root
    > >filesystem, but I can't load the kernel from USB key drive.
    >
    > huh?? Who's mounting the root filesystem, then :) ?
    >
    > If you mean that you can't get the BIOS to load the kernel for you, and
    > you're loading the kernel from a floppy or something, you should know
    > that some BIOS are pretty selective about what they consider a valid
    > boot partition.

    Hee, hee... yes, for now I boot from floppy first, then mount /dev/sda1
    as root filesystem. I, of course, want to get rid of the floppy. My
    motherboard is Mercury PVCLE266M-L with VIA C3 Samuel 2 cpu integrated
    on the board. It has tons of boot device options, and detects my USB
    key (SanDisk Cruzer Mini 256MB) as "USB RMD-FDD" and not as some kind of
    harddisk. I think that's the problem: motherboard thinks it's floppy,
    and LILO thinks it's SCSI harddisk (/dev/sda).

    >
    > I recommend that you use fdisk to set up one partition as FAT16 type
    > (even if you use another filesystem later), and make the partition
    > active. You might need to write a proper MBR on the pen also (IIRC
    > LILO as an option to do this).
    >
    > You might also need to pass a special "disk=/dev/sda bios=0x80" (or
    > something like that) option in your lilo.conf file, but that depends
    > how far in the boot process you're hanging.

    -- 
    William Park <opengeometry@yahoo.ca>, Toronto, Canada
    Slackware Linux -- because I can type.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Fruhwirth Clemens: "Re: Announce loop-AES-v3.0b file/swap crypto package"

    Relevant Pages

    • Re: Flames over -- Re: Which is simpler?
      ... the rest of us have been saying is a policy choice, one that the kernel ... When a hotpluggable bus (USB for sure, ... removable drives, they wouldn't have unmount before suspending and remount ... talking to the same fs if filesystem drivers were to help in that. ...
      (Linux-Kernel)
    • Re: USB camera connection fails with strange message
      ... > The problem is your kernel, it's IIRC the original RH 7.3 kernel ... This should solve your USB ... Is this a "weird filesystem" problem, ... looks suspicious from the error message, if it is indeed a "weird ...
      (comp.os.linux.misc)
    • Re: What to do when Ubuntu boots into Busybox CLI?
      ... You are browsing a filesystem in a ramdisk, that was already setup by grub ... This filesystem is used temporary by the kernel ... for loading device drivers that are necessary to access the harddisk and ... but your root filesystem didn't get mounted for some reason. ...
      (Ubuntu)
    • Several OOPSes in net/sched/sch_generic.c, kernel/softirq.c (and other places)
      ... I have witnessed several kernel oopses in a vanilla 2.6.32 kernel of different patch levels. ... As I have no idea how I can trigger this oops -- it just happens after a few hours of running -- I'll list what I'm using the machine for: it's running Debian squeeze with a custom built kernel, vanilla 2.6.32.7 (.config attached). ... A WLAN AP is running over the USB wireless stick, which is bridged with the LAN side of the one NIC. ... # Device Drivers ...
      (Linux-Kernel)
    • PROBLEM: Oops when using emi62 with 2.6.28
      ... With kernel 2.6.28 (and I don't really know which version of the kernel ... emi62 soundcard usb firmware oops ... 2000-2fff: PCI Bus 0000:02 ... # Infrared-port device drivers ...
      (Linux-Kernel)