Forum Linux.mandriva port usb fonctionne mais pas ce que l'on branche !?

• # module

  Posté par Jack DeNoumea (site web personnel) le 13 juillet 2005 à 19:03. Évalué à 2.

  

  en root
  modprobe usb-storage
  modprobe sd_mod
  
  un petit dmesg pour vérifier qu'il a bien trouvé ta partition sur la clé et voila tu peux monter ta clé

  • [^] # Re: module

    Posté par larspseudo le 15 juillet 2005 à 10:08. Évalué à 1.

    

    J'ai bien fait ce que tu m'as conseille et le resultat est :
    
    
    [root@localhost ligue]# modprobe usb-storage
    [root@localhost ligue]# modprobe sd_mod
    [root@localhost ligue]# dmesg
    Linux version 2.6.11-6mdk (gb@n2.mandrakesoft.com) (gcc version 3.4.3 (Mandrakelinux 10.2 3.4.3-3mdk)) #1 Tue Mar 22 16:04:32 CET 2005
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000000bfd0000 (usable)
    BIOS-e820: 000000000bfd0000 - 000000000bfdf000 (ACPI data)
    BIOS-e820: 000000000bfdf000 - 000000000bfe0000 (ACPI NVS)
    BIOS-e820: 000000000bfe0000 - 000000000c000000 (reserved)
    BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
    0MB HIGHMEM available.
    191MB LOWMEM available.
    On node 0 totalpages: 49104
    DMA zone: 4096 pages, LIFO batch:1
    Normal zone: 45008 pages, LIFO batch:10
    HighMem zone: 0 pages, LIFO batch:1
    DMI 2.0 present.
    ACPI: RSDP (v000 IBM ) @ 0x000fd6e0
    ACPI: RSDT (v001 IBM TP600 0x00000001 0x00000000) @ 0x0bfd0000
    ACPI: FADT (v001 IBM TP600 0x00000001 0x00000000) @ 0x0bfd0100
    ACPI: BOOT (v001 IBM TP600 0x00000001 0x00000000) @ 0x0bfd0040
    ACPI: DSDT (v001 IBM TP600 0x00000101 MSFT 0x0100000c) @ 0x00000000
    ACPI: PM-Timer IO Port: 0xef08
    Allocating PCI resources starting at 0c000000 (gap: 0c000000:f3fe0000)
    Built 1 zonelists
    Local APIC disabled by BIOS -- you can enable it with "lapic"
    mapped APIC to ffffd000 (01181000)
    Initializing CPU#0
    Kernel command line: BOOT_IMAGE=linux ro root=301 resume=/dev/hda5 splash=silent
    bootsplash: silent mode.
    PID hash table entries: 1024 (order: 10, 16384 bytes)
    Detected 298.492 MHz processor.
    Using pmtmr for high-res timesource
    Console: colour dummy device 80x25
    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    Memory: 190264k/196416k available (2295k kernel code, 5644k reserved, 686k data, 264k init, 0k highmem, 0k BadRAM)
    Checking if this processor honours the WP bit even in supervisor mode... Ok.
    Calibrating delay loop... 589.82 BogoMIPS (lpj=294912)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    CPU: After generic identify, caps: 0183f9ff 00000000 00000000 00000000 0000000000000000 00000000
    CPU: After vendor identify, caps: 0183f9ff 00000000 00000000 00000000 00000000 00000000 00000000
    CPU: L1 I cache: 16K, L1 D cache: 16K
    CPU: L2 cache: 512K
    CPU: After all inits, caps: 0183f9ff 00000000 00000000 00000040 00000000 00000000 00000000
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    CPU: Intel Pentium II (Deschutes) stepping 02
    Enabling fast FPU save and restore... done.
    Checking 'hlt' instruction... OK.
    ACPI: Looking for DSDT in initrd... not found.
    ACPI: setting ELCR to 0200 (from 0800)
    checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
    Freeing initrd memory: 219k freed
    NET: Registered protocol family 16
    PCI: PCI BIOS revision 2.10 entry at 0xfd880, last bus=6
    PCI: Using configuration type 1
    mtrr: v2.0 (20020519)
    ACPI: Subsystem revision 20050211
    ACPI: Interpreter enabled
    ACPI: Using PIC for interrupt routing
    ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
    ACPI: PCI Root Bridge [PCI0] (00:00)
    PCI: Probing PCI hardware (bus 00)
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: Power Resource [PSIO] (on)
    ACPI: Embedded Controller [EC0] (gpe 9)
    ACPI: Power Resource [PFN0] (off)
    ACPI: Power Resource [PVID] (on)
    ACPI: Power Resource [PRSD] (off)
    ACPI: Power Resource [PDCK] (on)
    Linux Plug and Play Support v0.97 (c) Adam Belay
    pnp: PnP ACPI init
    pnp: PnP ACPI: found 17 devices
    PnPBIOS: Disabled
    PCI: Using ACPI for IRQ routing
    ** PCI interrupts are no longer routed automatically. If this
    ** causes a device to stop working, it is probably because the
    ** driver failed to call pci_enable_device(). As a temporary
    ** workaround, the "pci=routeirq" argument restores the old
    ** behavior. If this argument makes the device work again,
    ** please email the output of "lspci" to bjorn.helgaas@hp.com
    ** so I can fix the driver.
    pnp: 00:0c: ioport range 0x15e0-0x15ef has been reserved
    pnp: 00:0c: ioport range 0xef00-0xef3f could not be reserved
    pnp: 00:0c: ioport range 0xefa0-0xefaf has been reserved
    Simple Boot Flag at 0x33 set to 0x1
    IBM machine detected. Enabling interrupts during APM calls.
    apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
    apm: overridden by ACPI.
    audit: initializing netlink socket (disabled)
    audit(1121412298.742:0): initialized
    inotify device minor=63
    VFS: Disk quotas dquot_6.5.1
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
    devfs: boot_options: 0x0
    Initializing Cryptographic API
    Limiting direct PCI/PCI transfers.
    vesafb: framebuffer at 0xe0000000, mapped to 0xcc880000, using 1984k, total 1984k
    vesafb: mode is 800x600x16, linelength=1600, pages=1
    vesafb: protected mode interface info at c000:8e10
    vesafb: scrolling: redraw
    vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
    bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg size 35024 bytes,<6>...found (800x600, 34976 bytes, v3).
    Console: switching to colour frame buffer device 92x32
    fb0: VESA VGA frame buffer device
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    Real Time Clock Driver v1.12
    serio: i8042 AUX port at 0x60,0x64 irq 12
    serio: i8042 KBD port at 0x60,0x64 irq 1
    Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
    acpi_serial_add: no iomem or port address in UAR1 _CRS
    pnp: Device 00:02 activated.
    ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered
    RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
    pktcdvd: v0.2.0a 2004-07-14 Jens Axboe (axboe@suse.de) and petero2@telia.com
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    PIIX4: IDE controller at PCI slot 0000:00:07.1
    PIIX4: chipset revision 1
    PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xfcf0-0xfcf7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xfcf8-0xfcff, BIOS settings: hdc:DMA, hdd:pio
    Probing IDE interface ide0...
    hda: IBM-DADA-25120, ATA DISK drive
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    Probing IDE interface ide1...
    hdc: TOSHIBA CD-ROM XM-1702BC, ATAPI CD/DVD-ROM drive
    ide1 at 0x170-0x177,0x376 on irq 15
    hda: max request size: 128KiB
    hda: 10009440 sectors (5124 MB) w/460KiB Cache, CHS=10592/15/63, UDMA(33)
    hda: cache flushes not supported
    /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 >
    mice: PS/2 mouse device common for all mice
    input: AT Translated Set 2 keyboard on isa0060/serio0
    input: PS/2 Generic Mouse on isa0060/serio1
    md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
    NET: Registered protocol family 2
    IP: routing cache hash table of 1024 buckets, 8Kbytes
    TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
    TCP: Hash tables configured (established 8192 bind 8192)
    NET: Registered protocol family 1
    ACPI wakeup devices:
    LID0 SLPB PCI0 UAR1 MWV0 BAT0 USB0
    ACPI: (supports S0 S1 S3 S4 S5)
    BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
    devfs_mk_dev: could not append to parent for md/0
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: ... autorun DONE.
    RAMDISK: Compressed image found at block 0
    VFS: Mounted root (ext2 filesystem).
    EXT3-fs: INFO: recovery required on readonly filesystem.
    EXT3-fs: write access will be enabled during recovery.
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: hda1: orphan cleanup on readonly fs
    ext3_orphan_cleanup: deleting unreferenced inode 71996
    ext3_orphan_cleanup: deleting unreferenced inode 71994
    ext3_orphan_cleanup: deleting unreferenced inode 68693
    EXT3-fs: hda1: 3 orphan inodes deleted
    EXT3-fs: recovery complete.
    EXT3-fs: mounted filesystem with ordered data mode.
    Freeing unused kernel memory: 264k freed
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    USB Universal Host Controller Interface driver v2.2
    ACPI: PCI Interrupt Link [LNKD] disabled and referenced, BIOS bug.
    ACPI: PCI Interrupt Link [LNKD] BIOS reported IRQ 0, using IRQ 9
    ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
    PCI: setting IRQ 9 as level-triggered
    ACPI: PCI interrupt 0000:00:07.2[D] -> GSI 9 (level, low) -> IRQ 9
    uhci_hcd 0000:00:07.2: UHCI Host Controller
    uhci_hcd 0000:00:07.2: irq 9, io base 0x8400
    uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 2 ports detected
    bootsplash: status on console 0 changed to on
    EXT3 FS on hda1, internal journal
    SCSI subsystem initialized
    libata version 1.10 loaded.
    Adding 544280k swap on /dev/hda5. Priority:-1 extents:1
    kjournald starting. Commit interval 5 seconds
    EXT3 FS on hda6, internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    loop: loaded (max 8 devices)
    hdc: ATAPI 24X CD-ROM drive, 128kB Cache, DMA
    Uniform CD-ROM driver Revision: 3.20
    ACPI: AC Adapter [AC] (on-line)
    ACPI: Battery Slot [BAT0] (battery present)
    ACPI: Power Button (FF) [PWRF]
    ACPI: Lid Switch [LID0]
    ACPI: Sleep Button (CM) [SLPB]
    ACPI: Fan [FN00] (off)
    ACPI: Fan [FN20] (off)
    ACPI: Fan [FN60] (off)
    ibm_acpi: ec object not found
    ACPI: CPU0 (power states: C1[C1] C2[C2])
    ACPI: Thermal Zone [THM0] (49 C)
    ACPI: Thermal Zone [THM2] (30 C)
    ACPI: Thermal Zone [THM6] (28 C)
    ACPI: Video Device [VID0] (multi-head: yes rom: no post: no)
    Linux Kernel Card Services
    options: [pci] [cardbus] [pm]
    ACPI: PCI Interrupt Link [LNKA] disabled and referenced, BIOS bug.
    ACPI: PCI Interrupt Link [LNKA] BIOS reported IRQ 0, using IRQ 9
    ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9
    ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 9 (level, low) -> IRQ 9
    Yenta: CardBus bridge found at 0000:00:02.0 [1014:0092]
    Yenta: Enabling burst memory read transactions
    Yenta: Using CSCINT to route CSC interrupts to PCI
    Yenta: Routing CardBus interrupts to PCI
    Yenta TI: socket 0000:00:02.0, mfunc 0xfba97543, devctl 0x62
    Yenta TI: socket 0000:00:02.0 probing PCI interrupt failed, trying to fix
    Yenta TI: socket 0000:00:02.0 no PCI interrupts. Fish. Please report.
    Yenta: ISA IRQ mask 0x04b8, PCI irq 0
    Socket status: 30000006
    ACPI: PCI Interrupt Link [LNKB] disabled and referenced, BIOS bug.
    ACPI: PCI Interrupt Link [LNKB] BIOS reported IRQ 0, using IRQ 9
    ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
    ACPI: PCI interrupt 0000:00:02.1[B] -> GSI 9 (level, low) -> IRQ 9
    Yenta: CardBus bridge found at 0000:00:02.1 [1014:0092]
    Yenta: Using CSCINT to route CSC interrupts to PCI
    Yenta: Routing CardBus interrupts to PCI
    Yenta TI: socket 0000:00:02.1, mfunc 0xfba97543, devctl 0x62
    Yenta TI: socket 0000:00:02.1 probing PCI interrupt failed, trying to fix
    Yenta TI: socket 0000:00:02.1 no PCI interrupts. Fish. Please report.
    Yenta: ISA IRQ mask 0x04b8, PCI irq 0
    Socket status: 30000006
    cs: IO port probe 0xc00-0xcff: clean.
    cs: IO port probe 0xc00-0xcff: clean.
    cs: IO port probe 0x100-0x4ff: excluding 0x4d0-0x4d7
    cs: IO port probe 0x100-0x4ff: excluding 0x4d0-0x4d7
    cs: IO port probe 0xa00-0xaff: clean.
    cs: IO port probe 0xa00-0xaff: clean.
    Floppy drive(s): fd0 is 1.44M
    FDC 0 is a National Semiconductor PC87306
    NET: Registered protocol family 17
    Bluetooth: Core ver 2.7
    NET: Registered protocol family 31
    Bluetooth: HCI device and connection manager initialized
    Bluetooth: HCI socket layer initialized
    Bluetooth: L2CAP ver 2.7
    Bluetooth: L2CAP socket layer initialized
    Bluetooth: RFCOMM ver 1.5
    Bluetooth: RFCOMM socket layer initialized
    Bluetooth: RFCOMM TTY layer initialized
    NET: Registered protocol family 10
    Disabled Privacy Extensions on device c03b26e0(lo)
    IPv6 over IPv4 tunneling driver
    Disabled Privacy Extensions on device c9d37400(sit0)
    mtrr: 0xe0000000,0x200000 overlaps existing 0xe0000000,0x100000
    Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    ISO 9660 Extensions: RRIP_1991A
    bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3).
    bootsplash: status on console 0 changed to on
    bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3).
    bootsplash: status on console 1 changed to on
    bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3).
    bootsplash: status on console 2 changed to on
    bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3).
    bootsplash: status on console 3 changed to on
    bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3).
    bootsplash: status on console 4 changed to on
    bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 10640 bytes, v3).
    bootsplash: status on console 5 changed to on
    
    
    Initializing USB Mass Storage driver...
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usb 1-1: new full speed USB device using uhci_hcd and address 2
    usb 1-1: khubd timed out on ep0out
    usb 1-1: khubd timed out on ep0out
    usb 1-1: device not accepting address 2, error -110
    usb 1-1: new full speed USB device using uhci_hcd and address 3
    usb 1-1: khubd timed out on ep0in
    usb 1-1: device descriptor read/8, error -110
    usb 1-1: khubd timed out on ep0in
    usb 1-1: device descriptor read/8, error -110
    usb 1-1: new full speed USB device using uhci_hcd and address 4
    usb 1-1: khubd timed out on ep0in
    usb 1-1: khubd timed out on ep0out
    usb 1-1: device not accepting address 4, error -71
    usb 1-1: new full speed USB device using uhci_hcd and address 5
    usb 1-1: khubd timed out on ep0in
    atkbd.c: Keyboard on isa0060/serio0 reports too many keys pressed.
    usb 1-1: khubd timed out on ep0out
    usb 1-1: khubd timed out on ep0out
    usb 1-1: device not accepting address 5, error -110
    
    
    [root@localhost ligue]#
    
    
    
    Je dois t'avouer que pour moi C du charabia. Je peux neanmoins dire que la cle ne se monte toujours pas. Et lorsque je lis ce qu'affiche le dmesg, je crois comprendre qu'il y a un probleme avec le port usb mais je ne sais toujours pqs comment le resoudre. Si t'as une idee...

• # dmesg

  Posté par Adrien BUSTANY (site web personnel) le 13 juillet 2005 à 22:25. Évalué à 2.

  

  Est ce que dmesg t'indique qu'il a détecté la clé USB ?

• # Liste des périphériques

  Posté par Anthony Bourguignon (site web personnel) le 27 juillet 2005 à 15:00. Évalué à 1.

  

  Peux-tu brancher ta clé et donner le résultat d'un cat /proc/partitions. Un des problèmes que j'ai souvent rencontré c'est que windows bouffe complètement les partitions. Après un peu de temps d'utilisation, la fat est complètement naze et windows écrit en direct sur le disque (sda et non plus les sdax).
  
  Essaye aussi de faire un fdisk /dev/sda (en root) puis tu tapes 'p' à l'invite. Si y'a des erreurs, ca peut être ça.

Suivre le flux des commentaires

Note : les commentaires appartiennent à celles et ceux qui les ont postés. Nous n’en sommes pas responsables.