isamu Posted November 15, 2006 Report Share Posted November 15, 2006 Hi there again, I have a serious issue with the 2007 mdv , The usb driver used by these isnt working, it has the next specs Each and every usb device attached to the system goes down in a certain time, a printer after 5 pages dies, the usb flash and hdd disks via an ide-usb connector dies after few megas of transfer , a scanner when reading half page freezes, it simply stop working, al of this has been poved on other linux distros as FC 4 mdv 2006 and even windows and its does works (the laptop system as well works fine in windows and works with each and every device too). lspci report this 00:00.0 Host bridge: ATI Technologies Inc Unknown device 5a31 (rev 01) 00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:12.0 IDE interface: ATI Technologies Inc ATI 4379 Serial ATA Controller (rev 80) 00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) 00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) 00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80) 00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 81) 00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI (rev 80) 00:14.2 Audio device: ATI Technologies Inc SB450 HDA Audio (rev 01) 00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80) 00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80) 01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200M] 09:01.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 01) 09:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C (rev 10) 09:04.0 Ethernet controller: Atheros Communications, Inc. AR5005G 802.11abg NIC (rev 01) (the wifi link doesnt work too, but I dont use it) Some idea friends? Thanks lot again Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted November 16, 2006 Report Share Posted November 16, 2006 What's in your log file at the time of the failure? You can do this: tail -f /var/log/messages from a console window, then connect the device, try to use it, and then when it dies, check the log and post back what's on the screen there so we can take a look. Quote Link to comment Share on other sites More sharing options...
iphitus Posted November 17, 2006 Report Share Posted November 17, 2006 more directly than the logfile, which contains all system messages, get the output of 'dmesg' after the failure. I realise this goes into messages, but other stuff goes there too, and a full dmesg is more useful. James Quote Link to comment Share on other sites More sharing options...
isamu Posted November 17, 2006 Author Report Share Posted November 17, 2006 hi friends, here are the logs when trying to use an usb disk of 30 gb and even cant mount it!!! tail -f /var/log/messages Nov 17 12:59:53 localhost diskdrake[6508]: created directory /proc (and parents if necessary) Nov 17 12:59:53 localhost diskdrake[6508]: created directory /proc (and parents if necessary) Nov 17 12:59:57 localhost diskdrake[6508]: default cancel_clicked Nov 17 13:00:37 localhost diskdrake[6508]: created directory /mnt/win_c (and parents if necessary) Nov 17 13:00:37 localhost diskdrake[6508]: created directory / (and parents if necessary) Nov 17 13:00:37 localhost diskdrake[6508]: created directory /mnt/win_d (and parents if necessary) Nov 17 13:00:37 localhost diskdrake[6508]: created directory /mnt/cdrom (and parents if necessary) Nov 17 13:00:37 localhost diskdrake[6508]: created directory /proc (and parents if necessary) Nov 17 13:00:37 localhost diskdrake[6508]: created directory /proc (and parents if necessary) Nov 17 13:00:37 localhost diskdrake[6508]: ### Program is exiting ### and when cheking dmesg ALSA /home/skull0/Desktop/realtek-linux-audiopack-RHEL4U4-4.05b/alsa-driver-1.0.12-RHEL4U4-4.05b/pci/hda/hda_codec.c:213: hda_codec: invalid dep_range_val 0:7fff ACPI: PCI Interrupt 0000:09:02.0[A] -> GSI 21 (level, low) -> IRQ 20 eth0: RealTek RTL8139 at 0xcea2e000, 00:16:36:61:03:f0, IRQ 20 eth0: Identified 8139 chip type 'RTL-8100B/8139D' eth0: link up, 100Mbps, full-duplex, lpa 0x41E1 CSLIP: code copyright 1989 Regents of the University of California PPP generic driver version 2.4.2 NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver eth0: no IPv6 routers present usbcore: registered new driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver ip_tables: © 2000-2006 Netfilter Core Team Installing knfsd (copyright © 1996 okir@monad.swb.de). NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory NFSD: starting 90-second grace period Netfilter messages via NETLINK v0.30. ip_conntrack version 2.4 (1781 buckets, 14248 max) - 224 bytes per conntrack ClusterIP Version 0.8 loaded successfully ipt_recent v0.3.1: Stephen Frost <sfrost@snowman.net>. http://snowman.net/projects/ipt_recent/ netfilter PSD loaded - © astaro AG IFWLOG: register target usb 3-3: new high speed USB device using ehci_hcd and address 2 usb 3-3: configuration #1 chosen from 1 choice Initializing USB Mass Storage driver... scsi2 : SCSI emulation for USB Mass Storage devices usbcore: registered new driver usb-storage USB Mass Storage support registered. usb-storage: device found at 2 usb-storage: waiting for device to settle before scanning Vendor: HTS42403 Model: 0M9AT00 Rev: MAAO Type: Direct-Access ANSI SCSI revision: 00 SCSI device sdb: 58605120 512-byte hdwr sectors (30006 MB) sdb: Write Protect is off sdb: Mode Sense: 00 14 00 00 sdb: assuming drive cache: write through SCSI device sdb: 58605120 512-byte hdwr sectors (30006 MB) sdb: Write Protect is off sdb: Mode Sense: 00 14 00 00 sdb: assuming drive cache: write through sdb: sdb1 sdb2 sd 2:0:0:0: Attached scsi disk sdb usb-storage: device scan complete sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 2:0:0:0: Attached scsi generic sg1 type 0 usb 3-3: reset high speed USB device using ehci_hcd and address 2 usb 3-3: device not accepting address 2, error -110 usb 3-3: reset high speed USB device using ehci_hcd and address 2 usb 3-3: device not accepting address 2, error -110 usb 3-3: reset high speed USB device using ehci_hcd and address 2 usb 3-3: device not accepting address 2, error -110 usb 3-3: reset high speed USB device using ehci_hcd and address 2 usb 3-3: device not accepting address 2, error -110 usb 3-3: USB disconnect, address 2 2:0:0:0: scsi: Device offlined - not ready after error recovery 2:0:0:0: SCSI error: return code = 0x10000 end_request: I/O error, dev sdb, sector 24 Buffer I/O error on device sdb, logical block 3 2:0:0:0: rejecting I/O to dead device Buffer I/O error on device sdb, logical block 3 usb 3-3: new high speed USB device using ehci_hcd and address 3 usb 3-3: device not accepting address 3, error -110 usb 3-3: new high speed USB device using ehci_hcd and address 4 usb 3-3: device not accepting address 4, error -110 usb 3-3: new high speed USB device using ehci_hcd and address 5 usb 3-3: device not accepting address 5, error -110 usb 3-3: new high speed USB device using ehci_hcd and address 6 usb 3-3: device not accepting address 6, error -110 floppy0: no floppy controllers found floppy0: no floppy controllers found floppy0: no floppy controllers found floppy0: no floppy controllers found floppy0: no floppy controllers found floppy0: no floppy controllers found usb 3-3: new high speed USB device using ehci_hcd and address 7 usb 3-3: device not accepting address 7, error -110 usb 3-3: new high speed USB device using ehci_hcd and address 8 usb 3-3: device not accepting address 8, error -110 usb 3-3: new high speed USB device using ehci_hcd and address 9 usb 3-3: device not accepting address 9, error -110 usb 3-3: new high speed USB device using ehci_hcd and address 10 usb 3-3: device not accepting address 10, error -110 floppy0: no floppy controllers found floppy0: no floppy controllers found floppy0: no floppy controllers found floppy0: no floppy controllers found usb 3-1: new high speed USB device using ehci_hcd and address 11 usb 3-1: device not accepting address 11, error -110 usb 3-1: new high speed USB device using ehci_hcd and address 12 usb 3-1: device not accepting address 12, error -110 usb 3-1: new high speed USB device using ehci_hcd and address 13 usb 3-1: device not accepting address 13, error -110 usb 3-1: new high speed USB device using ehci_hcd and address 14 usb 3-1: device not accepting address 14, error -110 floppy0: no floppy controllers found floppy0: no floppy controllers found floppy0: no floppy controllers found floppy0: no floppy controllers found dunno if was the entire file because at the beginnig I saw much lines of ALSA because I conflicts with the soundcard (would be this is related? its an al861 of realtek using the hdaintel core of alsa but dont works, ask this because I think its using the same bus as the usb line think!!!) Thanks anyway for your valuable time Quote Link to comment Share on other sites More sharing options...
scarecrow Posted November 17, 2006 Report Share Posted November 17, 2006 Excuse me, but I think you are just messing things up for no apparent reason. Why did you try to install RedHat RPM's over your Mandy 2007 environment? This is 101% guaranteed to lead you to a totally broken system... Quote Link to comment Share on other sites More sharing options...
isamu Posted November 18, 2006 Author Report Share Posted November 18, 2006 (edited) Even when here appear a driver degined for redhat , there was a reason, mandriva 2006 and 2007 has a severe incompatibility with this hardware specific (all the hda-intel soundcores laptop based) and this was the driver with seemed to work, but seemed only because there is no sound with this and with the mdv driver and general driver for this hardware, so I suggest the chance this could be bugging me , bevcause I know my system uses the same pci bus for the sound a software modem and the pci implementation and until I see the usb subsystem its based on to the pci bus... .... :huh: messy right? I dont think this usb bug be due the fact I use a no working driver deigned for another distro,,,and it the end it was configurated to be adapted to this parameters...but anyway Im open to suggestions and thank for take your time to look around this jerk bug. ;) Thanks <alex PD... I almost dont use rpm I prefer to use source packages, and in fact this one was a tarball,. Thanks Edited November 18, 2006 by isamu Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.