During the conection of the key USB, the commercial party (CDFS) does not come. The PC heats up a lot, can decelerated tremendously. Here are logs: Thank's Oct 14 22:52:17 localhost kernel: usb 2-3.2: New USB device found, idVendor=1e3d, idProduct=2092 Oct 14 22:52:17 localhost kernel: usb 2-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 14 22:52:17 localhost kernel: usb 2-3.2: Product: Flash Disk Oct 14 22:52:17 localhost kernel: usb 2-3.2: Manufacturer: CBM Oct 14 22:52:17 localhost kernel: usb 2-3.2: SerialNumber: 30194401F4AB0508 Oct 14 22:52:17 localhost kernel: scsi7 : usb-storage 2-3.2:1.0 Oct 14 22:52:17 localhost mtp-probe: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-3/2-3.2" Oct 14 22:52:17 localhost mtp-probe: bus: 2, device: 7 was not an MTP device Oct 14 22:52:18 localhost kernel: scsi 7:0:0:0: Direct-Access CBM Flash Disk 5.00 PQ: 0 ANSI: 2 Oct 14 22:52:18 localhost kernel: sd 7:0:0:0: Attached scsi generic sg2 type 0 Oct 14 22:52:18 localhost kernel: scsi 7:0:0:1: CD-ROM CBM Flash Disk 5.00 PQ: 0 ANSI: 2 Oct 14 22:52:18 localhost kernel: sd 7:0:0:0: [sdb] 8036584 512-byte logical blocks: (4.11 GB/3.83 GiB) Oct 14 22:52:18 localhost kernel: sr1: scsi3-mmc drive: 0x/0x caddy Oct 14 22:52:18 localhost kernel: sr 7:0:0:1: Attached scsi generic sg3 type 5 Oct 14 22:52:18 localhost kernel: sd 7:0:0:0: [sdb] Write Protect is off Oct 14 22:52:18 localhost kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through Oct 14 22:52:18 localhost kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through Oct 14 22:52:18 localhost kernel: sdb: Oct 14 22:52:18 localhost kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through Oct 14 22:52:18 localhost kernel: sd 7:0:0:0: [sdb] Attached SCSI removable disk Oct 14 22:52:18 localhost kernel: usb 2-3.2: reset high speed USB device using ehci_hcd and address 7 Oct 14 22:52:18 localhost kernel: sr 7:0:0:1: [sr1] Media Changed Oct 14 22:52:18 localhost kernel: sr 7:0:0:1: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Oct 14 22:52:18 localhost kernel: sr 7:0:0:1: [sr1] Sense Key : Unit Attention [current] Oct 14 22:52:18 localhost kernel: sr 7:0:0:1: [sr1] Add. Sense: Not ready to ready change, medium may have changed Oct 14 22:52:18 localhost kernel: sr 7:0:0:1: [sr1] CDB: Read(10): 28 20 00 00 00 00 00 00 02 00 Oct 14 22:52:18 localhost kernel: end_request: I/O error, dev sr1, sector 0 Oct 14 22:52:18 localhost kernel: Buffer I/O error on device sr1, logical block 0
Priority: Normal => HighTarget Milestone: --- => Mageia 1
CC: sysadmin-bugs => boklmComponent: Release (media, process) => RPM Packages
Mounting cdfs partitions from some USB disks works for me. I think more infos are needed : - What is this USB key ? Where does it come from, or how was it created ? - What is the kernel used ? - Does it work with other distributions, or other OS ?
Keywords: (none) => NEEDINFOPriority: High => NormalSeverity: critical => normal
My ubs key is a commercial key with an indelible party is. It's CDFS with windows7 The other party is a FAT32... No problem. I do not use the USB key, because the PC embale.... with windows7 the PC is normal My kernel is 2.6.38.8-desktop586-6.mga
Am I correct in understanding that this is a usb wireless dongle? If so, try installing usb-modeswitch.
CC: (none) => davidwhodgins
@ Thierry Does this mean you have a CBM external USB HD, with a CDFS and a FAT32 partition, and that both work fine with windows 7, but you can't mount he CDFS partition with Mageia 1, and instead your system gets overheated? Currently we have kernel-desktop-2.6.38.8-8.mga does the problem still exist?
CC: (none) => marja11
@ Thierry Please reply to the question above within two weeks from now, to avoid this bug being closed as OLD.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD
CC: boklm => (none)