From: Chris G. <dj_...@ti...> - 2008-08-08 17:44:59
|
Hi all, I've got devil linux running very nicely on my little MSI machine. The problem is that the onboard ports are only usb 1.1 compliant. So I thought "I know, i'll buy a usb 2.0 PCI card" This all worked out well as i found a nice little one with a VIA chipset on ebay. It arrived, and i installed it. Now here's where the fun starts. Linux sees the device during boot-up. It also sees it if I type in lspci, but I can't see/mount any hdd's or memory sticks that I plug in. Has anybody any ideas please. In case its any help, here's what lspci has to say about it: this is the onboard one: 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) and this is the PCI one: 01:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 01:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 01:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) And dmesg says this: usb.c: registered new driver usbdevfs usb.c: registered new driver hub PCI: Found IRQ 5 for device 01:00.2 ehci_hcd 01:00.2: VIA Technologies, Inc. USB 2.0 ehci_hcd 01:00.2: irq 5, pci mem c881e000 usb.c: new USB bus registered, assigned bus number 1 ehci_hcd 01:00.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4 hub.c: USB hub found hub.c: 4 ports detected host/usb-uhci.c: $Revision: 1.275 $ time 19:10:59 Nov 20 2007 host/usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 12 for device 00:1f.2 PCI: Setting latency timer of device 00:1f.2 to 64 host/usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 12 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 10 for device 00:1f.4 PCI: Setting latency timer of device 00:1f.4 to 64 host/usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 3 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 11 for device 01:00.1 PCI: Sharing IRQ 11 with 00:1f.3 PCI: Sharing IRQ 11 with 00:1f.5 host/usb-uhci.c: USB UHCI at I/O 0xac00, IRQ 11 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 4 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 9 for device 01:00.0 PCI: Sharing IRQ 9 with 00:02.0 host/usb-uhci.c: USB UHCI at I/O 0xa800, IRQ 9 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 5 hub.c: USB hub found hub.c: 2 ports detected host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver usb.c: registered new driver hiddev usb.c: registered new driver hid hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vo...@su...> hid-core.c: USB HID support drivers Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. Initializing Cryptographic API IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 8192 bind 8192) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 802.1Q VLAN Support v1.8 Ben Greear <gr...@ca...> All bugs added by David S. Miller <da...@re...> RAMDISK: Compressed image found at block 0 hub.c: new USB device 00:1f.2-1, assigned address 2 Freeing initrd memory: 2522k freed VFS: Mounted root (cramfs filesystem) readonly. Mounted devfs on /dev Freeing unused kernel memory: 156k freed scsi0 : SCSI emulation for USB Mass Storage devices Vendor: Model: Hitachi HDT72503 Rev: V54O Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) /dev/scsi/host0/bus0/target0/lun0: p1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 hub.c: new USB device 00:1f.2-2, assigned address 3 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: Maxtor 2 Model: B010H1 Rev: 0 0 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 SCSI device sdb: 20012832 512-byte hdwr sectors (10247 MB) /dev/scsi/host1/bus0/target0/lun0: p1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 3 hub.c: new USB device 01:00.2-4, assigned address 2 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=2 (error=-110) hub.c: new USB device 01:00.2-4, assigned address 3 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=3 (error=-110) I've tried turning to onboard one off, and starting again with a blank config, neither of which work. Any help would be greatly appreciated.. Thanks in advance for your help. |
From: Heiko Z. <he...@zu...> - 2008-08-11 15:18:46
|
It may be an incomatability between the USB device and the Linux Kernel. Do the devices work on the USB 1.1 ports? You could also try the 1.3 version of DL (beta, but very stable), which is based on the 2.6 Kernel. Heiko Quoting Chris Grove <dj_...@ti...>: > > > Hi all, I've got devil linux running very nicely on my little MSI machine. The problem is that the onboard ports are only usb 1.1 compliant. So I thought "I know, i'll buy a usb 2.0 PCI card" This all worked out well as i found a nice little one with a VIA chipset on ebay. It arrived, and i installed it. Now here's where the fun starts. Linux sees the device during boot-up. It also sees it if I type in lspci, but I can't see/mount any hdd's or memory sticks that I plug in. Has anybody any ideas please. In case its any help, here's what lspci has to say about it: > this is the onboard one: > 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) > 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) > and this is the PCI one: > 01:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) > 01:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) > 01:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) > > > > > > > > > > > > > > > > And dmesg says this: > > > > > > > > usb.c: registered new driver usbdevfs > usb.c: registered new driver hub > PCI: Found IRQ 5 for device 01:00.2 > ehci_hcd 01:00.2: VIA Technologies, Inc. USB 2.0 > ehci_hcd 01:00.2: irq 5, pci mem c881e000 > usb.c: new USB bus registered, assigned bus number 1 > ehci_hcd 01:00.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4 > hub.c: USB hub found > hub.c: 4 ports detected > host/usb-uhci.c: $Revision: 1.275 $ time 19:10:59 Nov 20 2007 > host/usb-uhci.c: High bandwidth mode enabled > PCI: Found IRQ 12 for device 00:1f.2 > PCI: Setting latency timer of device 00:1f.2 to 64 > host/usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 12 > host/usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 2 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Found IRQ 10 for device 00:1f.4 > PCI: Setting latency timer of device 00:1f.4 to 64 > host/usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10 > host/usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 3 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Found IRQ 11 for device 01:00.1 > PCI: Sharing IRQ 11 with 00:1f.3 > PCI: Sharing IRQ 11 with 00:1f.5 > host/usb-uhci.c: USB UHCI at I/O 0xac00, IRQ 11 > host/usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 4 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Found IRQ 9 for device 01:00.0 > PCI: Sharing IRQ 9 with 00:02.0 > host/usb-uhci.c: USB UHCI at I/O 0xa800, IRQ 9 > host/usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 5 > hub.c: USB hub found > hub.c: 2 ports detected > host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver > usb.c: registered new driver hiddev > usb.c: registered new driver hid > hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vo...@su...[1]> > hid-core.c: USB HID support drivers > Initializing USB Mass Storage driver... > usb.c: registered new driver usb-storage > USB Mass Storage support registered. > Initializing Cryptographic API > IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP, IGMP > IP: routing cache hash table of 512 buckets, 4Kbytes > TCP: Hash tables configured (established 8192 bind 8192) > Linux IP multicast router 0.06 plus PIM-SM > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. > 802.1Q VLAN Support v1.8 Ben Greear <gr...@ca...[2]> > All bugs added by David S. Miller <da...@re...[3]> > RAMDISK: Compressed image found at block 0 > hub.c: new USB device 00:1f.2-1, assigned address 2 > Freeing initrd memory: 2522k freed > VFS: Mounted root (cramfs filesystem) readonly. > Mounted devfs on /dev > Freeing unused kernel memory: 156k freed > scsi0 : SCSI emulation for USB Mass Storage devices > Vendor: Model: Hitachi HDT72503 Rev: V54O > Type: Direct-Access ANSI SCSI revision: 02 > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 > SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) > /dev/scsi/host0/bus0/target0/lun0: p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 2 > hub.c: new USB device 00:1f.2-2, assigned address 3 > scsi1 : SCSI emulation for USB Mass Storage devices > Vendor: Maxtor 2 Model: B010H1 Rev: 0 0 > Type: Direct-Access ANSI SCSI revision: 02 > Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 > SCSI device sdb: 20012832 512-byte hdwr sectors (10247 MB) > /dev/scsi/host1/bus0/target0/lun0: p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 3 > hub.c: new USB device 01:00.2-4, assigned address 2 > usb_control/bulk_msg: timeout > usb.c: USB device not accepting new address=2 (error=-110) > hub.c: new USB device 01:00.2-4, assigned address 3 > usb_control/bulk_msg: timeout > usb.c: USB device not accepting new address=3 (error=-110) > > I've tried turning to onboard one off, and starting again with a blank config, neither of which work. Any help would be greatly appreciated.. Thanks in advance for your help. > > > > -- Regards Heiko Zuerker http://www.devil-linux.org[4] Links: ------ [1] mailto:vo...@su... [2] mailto:gr...@ca... [3] mailto:da...@re... [4] http://www.devil-linux.org/ ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Chris G. <dj_...@ti...> - 2008-08-12 17:45:21
|
Hi again. First off, Yes the devices do work on the USB 1.1 ports. Second, I've just spent 2 hours fighting with 1.3 with no luck. Whereas 1.2 sees the device plugged and just complains it can't assign an address, 1.3 just seems to completely ignore it all together. I'm just wondering whether or not there is any way of assigning IRQ's to a device as for some reason it seems to be IRQ sharing and I'm wondering whether that is causing a conflict. Thanks again for any help. From: dev...@li... [mailto:dev...@li...] On Behalf Of Heiko Zuerker Sent: 11 August 2008 16:19 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card It may be an incomatability between the USB device and the Linux Kernel. Do the devices work on the USB 1.1 ports? You could also try the 1.3 version of DL (beta, but very stable), which is based on the 2.6 Kernel. Heiko Quoting Chris Grove <dj_...@ti...>: Hi all, I've got devil linux running very nicely on my little MSI machine. The problem is that the onboard ports are only usb 1.1 compliant. So I thought "I know, i'll buy a usb 2.0 PCI card" This all worked out well as i found a nice little one with a VIA chipset on ebay. It arrived, and i installed it. Now here's where the fun starts. Linux sees the device during boot-up. It also sees it if I type in lspci, but I can't see/mount any hdd's or memory sticks that I plug in. Has anybody any ideas please. In case its any help, here's what lspci has to say about it: this is the onboard one: 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) and this is the PCI one: 01:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 01:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 01:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) And dmesg says this: usb.c: registered new driver usbdevfs usb.c: registered new driver hub PCI: Found IRQ 5 for device 01:00.2 ehci_hcd 01:00.2: VIA Technologies, Inc. USB 2.0 ehci_hcd 01:00.2: irq 5, pci mem c881e000 usb.c: new USB bus registered, assigned bus number 1 ehci_hcd 01:00.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4 hub.c: USB hub found hub.c: 4 ports detected host/usb-uhci.c: $Revision: 1.275 $ time 19:10:59 Nov 20 2007 host/usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 12 for device 00:1f.2 PCI: Setting latency timer of device 00:1f.2 to 64 host/usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 12 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 10 for device 00:1f.4 PCI: Setting latency timer of device 00:1f.4 to 64 host/usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 3 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 11 for device 01:00.1 PCI: Sharing IRQ 11 with 00:1f.3 PCI: Sharing IRQ 11 with 00:1f.5 host/usb-uhci.c: USB UHCI at I/O 0xac00, IRQ 11 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 4 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 9 for device 01:00.0 PCI: Sharing IRQ 9 with 00:02.0 host/usb-uhci.c: USB UHCI at I/O 0xa800, IRQ 9 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 5 hub.c: USB hub found hub.c: 2 ports detected host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver usb.c: registered new driver hiddev usb.c: registered new driver hid hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vo...@su...> hid-core.c: USB HID support drivers Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. Initializing Cryptographic API IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 8192 bind 8192) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 802.1Q VLAN Support v1.8 Ben Greear <gr...@ca...> All bugs added by David S. Miller <da...@re...> RAMDISK: Compressed image found at block 0 hub.c: new USB device 00:1f.2-1, assigned address 2 Freeing initrd memory: 2522k freed VFS: Mounted root (cramfs filesystem) readonly. Mounted devfs on /dev Freeing unused kernel memory: 156k freed scsi0 : SCSI emulation for USB Mass Storage devices Vendor: Model: Hitachi HDT72503 Rev: V54O Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) /dev/scsi/host0/bus0/target0/lun0: p1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 hub.c: new USB device 00:1f.2-2, assigned address 3 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: Maxtor 2 Model: B010H1 Rev: 0 0 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 SCSI device sdb: 20012832 512-byte hdwr sectors (10247 MB) /dev/scsi/host1/bus0/target0/lun0: p1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 3 hub.c: new USB device 01:00.2-4, assigned address 2 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=2 (error=-110) hub.c: new USB device 01:00.2-4, assigned address 3 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=3 (error=-110) I've tried turning to onboard one off, and starting again with a blank config, neither of which work. Any help would be greatly appreciated.. Thanks in advance for your help. -- Regards Heiko Zuerker http://www.devil-linux.org <http://www.devil-linux.org/> ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.0/1604 - Release Date: 11/08/2008 05:50 |
From: Chris G. <dj_...@ti...> - 2008-08-29 17:32:24
|
Hi. I've still got my problem with the USB ports on my PCI card not working, but I have another question. It's probably a bit of a silly question, but what is the differences between the 586 and the 686 builds? From: dev...@li... [mailto:dev...@li...] On Behalf Of Chris Grove Sent: 12 August 2008 18:45 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card Hi again. First off, Yes the devices do work on the USB 1.1 ports. Second, I've just spent 2 hours fighting with 1.3 with no luck. Whereas 1.2 sees the device plugged and just complains it can't assign an address, 1.3 just seems to completely ignore it all together. I'm just wondering whether or not there is any way of assigning IRQ's to a device as for some reason it seems to be IRQ sharing and I'm wondering whether that is causing a conflict. Thanks again for any help. From: dev...@li... [mailto:dev...@li...] On Behalf Of Heiko Zuerker Sent: 11 August 2008 16:19 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card It may be an incomatability between the USB device and the Linux Kernel. Do the devices work on the USB 1.1 ports? You could also try the 1.3 version of DL (beta, but very stable), which is based on the 2.6 Kernel. Heiko Quoting Chris Grove <dj_...@ti...>: Hi all, I've got devil linux running very nicely on my little MSI machine. The problem is that the onboard ports are only usb 1.1 compliant. So I thought "I know, i'll buy a usb 2.0 PCI card" This all worked out well as i found a nice little one with a VIA chipset on ebay. It arrived, and i installed it. Now here's where the fun starts. Linux sees the device during boot-up. It also sees it if I type in lspci, but I can't see/mount any hdd's or memory sticks that I plug in. Has anybody any ideas please. In case its any help, here's what lspci has to say about it: this is the onboard one: 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05) and this is the PCI one: 01:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 01:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 62) 01:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) And dmesg says this: usb.c: registered new driver usbdevfs usb.c: registered new driver hub PCI: Found IRQ 5 for device 01:00.2 ehci_hcd 01:00.2: VIA Technologies, Inc. USB 2.0 ehci_hcd 01:00.2: irq 5, pci mem c881e000 usb.c: new USB bus registered, assigned bus number 1 ehci_hcd 01:00.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4 hub.c: USB hub found hub.c: 4 ports detected host/usb-uhci.c: $Revision: 1.275 $ time 19:10:59 Nov 20 2007 host/usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 12 for device 00:1f.2 PCI: Setting latency timer of device 00:1f.2 to 64 host/usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 12 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 10 for device 00:1f.4 PCI: Setting latency timer of device 00:1f.4 to 64 host/usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 10 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 3 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 11 for device 01:00.1 PCI: Sharing IRQ 11 with 00:1f.3 PCI: Sharing IRQ 11 with 00:1f.5 host/usb-uhci.c: USB UHCI at I/O 0xac00, IRQ 11 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 4 hub.c: USB hub found hub.c: 2 ports detected PCI: Found IRQ 9 for device 01:00.0 PCI: Sharing IRQ 9 with 00:02.0 host/usb-uhci.c: USB UHCI at I/O 0xa800, IRQ 9 host/usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 5 hub.c: USB hub found hub.c: 2 ports detected host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver usb.c: registered new driver hiddev usb.c: registered new driver hid hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vo...@su...> hid-core.c: USB HID support drivers Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. Initializing Cryptographic API IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 8192 bind 8192) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 802.1Q VLAN Support v1.8 Ben Greear <gr...@ca...> All bugs added by David S. Miller <da...@re...> RAMDISK: Compressed image found at block 0 hub.c: new USB device 00:1f.2-1, assigned address 2 Freeing initrd memory: 2522k freed VFS: Mounted root (cramfs filesystem) readonly. Mounted devfs on /dev Freeing unused kernel memory: 156k freed scsi0 : SCSI emulation for USB Mass Storage devices Vendor: Model: Hitachi HDT72503 Rev: V54O Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB) /dev/scsi/host0/bus0/target0/lun0: p1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 2 hub.c: new USB device 00:1f.2-2, assigned address 3 scsi1 : SCSI emulation for USB Mass Storage devices Vendor: Maxtor 2 Model: B010H1 Rev: 0 0 Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 SCSI device sdb: 20012832 512-byte hdwr sectors (10247 MB) /dev/scsi/host1/bus0/target0/lun0: p1 WARNING: USB Mass Storage data integrity not assured USB Mass Storage device found at 3 hub.c: new USB device 01:00.2-4, assigned address 2 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=2 (error=-110) hub.c: new USB device 01:00.2-4, assigned address 3 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=3 (error=-110) I've tried turning to onboard one off, and starting again with a blank config, neither of which work. Any help would be greatly appreciated.. Thanks in advance for your help. -- Regards Heiko Zuerker http://www.devil-linux.org <http://www.devil-linux.org/> ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.0/1604 - Release Date: 11/08/2008 05:50 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.1/1605 - Release Date: 11/08/2008 16:59 |
From: Bruce S. <bw...@re...> - 2008-08-29 17:55:55
|
> what is the differences between the 586 and the 686 builds? It is the CPU option selected when the entire distro is compiled. You can run a i586 compiled distro on a 586 (Pentium/P5), or above (PPro, P-II, P-III, P-4, etc.) You cannot run a i686 compiled distro on a 586, or other CPU's that doesn't support the i686 instruction set. (PPro and above should be fine) Some older VIA/AMD CPU's have problems with the i686 distro. I don't recall the specific models. - BS |
From: Chris G. <dj_...@ti...> - 2008-08-29 19:11:52
|
Ok cool, So is there any chance that the different versions 586 and 686 might treat the PCI devices any difference?? I know it sounds like I'm grasping at straws here, but I really want to get these USB ports working. I copied 60gig the other days on the USB 1.1 ports and it took 25 hours!!! Here's hoping we can get to the bottom of this. -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Bruce Smith Sent: 29 August 2008 18:56 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card > what is the differences between the 586 and the 686 builds? It is the CPU option selected when the entire distro is compiled. You can run a i586 compiled distro on a 586 (Pentium/P5), or above (PPro, P-II, P-III, P-4, etc.) You cannot run a i686 compiled distro on a 586, or other CPU's that doesn't support the i686 instruction set. (PPro and above should be fine) Some older VIA/AMD CPU's have problems with the i686 distro. I don't recall the specific models. - BS ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.11/1639 - Release Date: 28/08/2008 07:39 |
From: Bruce S. <bw...@re...> - 2008-08-29 19:27:16
|
It shouldn't make any difference for USB. The i586 version _may_ have grsecurity enabled (is it working now Heiko)? But I don't know what difference that would make either. - BS On Fri, Aug 29, 2008 at 3:11 PM, Chris Grove <dj_...@ti...> wrote: > Ok cool, So is there any chance that the different versions 586 and 686 > might treat the PCI devices any difference?? I know it sounds like I'm > grasping at straws here, but I really want to get these USB ports working. I > copied 60gig the other days on the USB 1.1 ports and it took 25 hours!!! > Here's hoping we can get to the bottom of this. > > -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf Of > Bruce Smith > Sent: 29 August 2008 18:56 > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card > >> what is the differences between the 586 and the 686 builds? > > It is the CPU option selected when the entire distro is compiled. > > You can run a i586 compiled distro on a 586 (Pentium/P5), or above > (PPro, P-II, P-III, P-4, etc.) > > You cannot run a i686 compiled distro on a 586, or other CPU's that > doesn't support the i686 instruction set. (PPro and above should be > fine) > > Some older VIA/AMD CPU's have problems with the i686 distro. I don't > recall the specific models. > > - BS |
From: Heiko Z. <he...@zu...> - 2008-08-29 19:30:31
|
> -----Original Message----- > From: dev...@li... [mailto:devil- > lin...@li...] On Behalf Of Bruce Smith > Sent: Friday, August 29, 2008 2:27 PM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card > > It shouldn't make any difference for USB. > > The i586 version _may_ have grsecurity enabled (is it working now > Heiko)? > But I don't know what difference that would make either. Yes GRSecurity is working in 1.3. H. |
From: Chris G. <dj_...@ti...> - 2008-08-29 19:57:24
|
Ok, so that's all those possibilities exhausted. So what else can I try to get these ports working, or am I just destine to very sloooooow transfer rates?? -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Heiko Zuerker Sent: 29 August 2008 20:30 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card > -----Original Message----- > From: dev...@li... [mailto:devil- > lin...@li...] On Behalf Of Bruce Smith > Sent: Friday, August 29, 2008 2:27 PM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card > > It shouldn't make any difference for USB. > > The i586 version _may_ have grsecurity enabled (is it working now > Heiko)? > But I don't know what difference that would make either. Yes GRSecurity is working in 1.3. H. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
From: Dick M. <di...@fo...> - 2008-08-29 20:04:12
|
Chris Grove wrote: > Hi all, I've got devil linux running very nicely on my little MSI > machine. The problem is that the onboard ports are only usb 1.1 > compliant. So I thought "I know, i'll buy a usb 2.0 PCI card" This all > worked out well as i found a nice little one with a VIA chipset on ebay. > /dev/scsi/host0/bus0/target0/lun0: p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 2 > hub.c: new USB device 00:1f.2-2, assigned address 3 > scsi1 : SCSI emulation for USB Mass Storage devices > Vendor: Maxtor 2 Model: B010H1 Rev: 0 0 > Type: Direct-Access ANSI SCSI revision: 02 > Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 > SCSI device sdb: 20012832 512-byte hdwr sectors (10247 MB) > /dev/scsi/host1/bus0/target0/lun0: p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 3 > hub.c: new USB device 01:00.2-4, assigned address 2 > usb_control/bulk_msg: timeout > usb.c: USB device not accepting new address=2 (error=-110) > hub.c: new USB device 01:00.2-4, assigned address 3 > usb_control/bulk_msg: timeout > usb.c: USB device not accepting new address=3 (error=-110) USB controler is telling you it cannot set the address on the device you've plugged in; it's timing out. This could be a device error (possibly the caddy) or it could be scsi emulation problem. I have vague memory that scsi emulation was incompatible with atapi cdroms or some such. Try a USB stick, see if you can get that to work. The suggestion to move to linux 2.6 on DL 1.3 is probably a good one if it's a driver problem. Won't help if you've duff device. Dick |
From: Chris G. <dj_...@ti...> - 2008-08-29 20:14:36
|
The problem is that it's an HDD that works ok on the onboard USB ports. I've tried it with the newer kernel version but dmesg doesn't even see a device when you plug it in. It does however tell me that the device isn't running at full speed if I plug the HDD into the USB 1.1 ports. -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Dick Middleton Sent: 29 August 2008 21:04 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card Chris Grove wrote: > Hi all, I've got devil linux running very nicely on my little MSI > machine. The problem is that the onboard ports are only usb 1.1 > compliant. So I thought "I know, i'll buy a usb 2.0 PCI card" This all > worked out well as i found a nice little one with a VIA chipset on ebay. > /dev/scsi/host0/bus0/target0/lun0: p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 2 > hub.c: new USB device 00:1f.2-2, assigned address 3 > scsi1 : SCSI emulation for USB Mass Storage devices > Vendor: Maxtor 2 Model: B010H1 Rev: 0 0 > Type: Direct-Access ANSI SCSI revision: 02 > Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 > SCSI device sdb: 20012832 512-byte hdwr sectors (10247 MB) > /dev/scsi/host1/bus0/target0/lun0: p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 3 > hub.c: new USB device 01:00.2-4, assigned address 2 > usb_control/bulk_msg: timeout > usb.c: USB device not accepting new address=2 (error=-110) > hub.c: new USB device 01:00.2-4, assigned address 3 > usb_control/bulk_msg: timeout > usb.c: USB device not accepting new address=3 (error=-110) USB controler is telling you it cannot set the address on the device you've plugged in; it's timing out. This could be a device error (possibly the caddy) or it could be scsi emulation problem. I have vague memory that scsi emulation was incompatible with atapi cdroms or some such. Try a USB stick, see if you can get that to work. The suggestion to move to linux 2.6 on DL 1.3 is probably a good one if it's a driver problem. Won't help if you've duff device. Dick ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.13/1641 - Release Date: 29/08/2008 07:07 |
From: Chris G. <dj_...@ti...> - 2008-09-01 21:45:21
|
Ok, I tried a new approach at the weekend and put the USB card in another PC and booted DL from a CD. And guess what, it works! So it would appear that there is some form of incompatibility between the DL and the hardware of my little server. So here I've got a question, does DL use the computer's BIOS or does it override it and work independently?? Thanks for the help. -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Chris Grove Sent: 29 August 2008 21:15 To: di...@fo...; dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card The problem is that it's an HDD that works ok on the onboard USB ports. I've tried it with the newer kernel version but dmesg doesn't even see a device when you plug it in. It does however tell me that the device isn't running at full speed if I plug the HDD into the USB 1.1 ports. -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Dick Middleton Sent: 29 August 2008 21:04 To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-Linux with a PCI USB card Chris Grove wrote: > Hi all, I've got devil linux running very nicely on my little MSI > machine. The problem is that the onboard ports are only usb 1.1 > compliant. So I thought "I know, i'll buy a usb 2.0 PCI card" This all > worked out well as i found a nice little one with a VIA chipset on ebay. > /dev/scsi/host0/bus0/target0/lun0: p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 2 > hub.c: new USB device 00:1f.2-2, assigned address 3 > scsi1 : SCSI emulation for USB Mass Storage devices > Vendor: Maxtor 2 Model: B010H1 Rev: 0 0 > Type: Direct-Access ANSI SCSI revision: 02 > Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0 > SCSI device sdb: 20012832 512-byte hdwr sectors (10247 MB) > /dev/scsi/host1/bus0/target0/lun0: p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 3 > hub.c: new USB device 01:00.2-4, assigned address 2 > usb_control/bulk_msg: timeout > usb.c: USB device not accepting new address=2 (error=-110) > hub.c: new USB device 01:00.2-4, assigned address 3 > usb_control/bulk_msg: timeout > usb.c: USB device not accepting new address=3 (error=-110) USB controler is telling you it cannot set the address on the device you've plugged in; it's timing out. This could be a device error (possibly the caddy) or it could be scsi emulation problem. I have vague memory that scsi emulation was incompatible with atapi cdroms or some such. Try a USB stick, see if you can get that to work. The suggestion to move to linux 2.6 on DL 1.3 is probably a good one if it's a driver problem. Won't help if you've duff device. Dick ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.13/1641 - Release Date: 29/08/2008 07:07 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.13/1641 - Release Date: 29/08/2008 07:07 |