| View previous topic :: View next topic |
| Author |
Message |
Kabuto
l33t
Joined: 01 Aug 2002
Posts: 701
|
 Posted: Thu Nov 10, 2005 3:11 pm Post subject: |
 |
|
| Your dmesg shows ehci USB initiallizing and setting up Bus 1 as USB 2.0 and uhci setting up 2-4. So it look like you have 3 or 4 controllers? |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54809
Location: 56N 3W
|
| Posted: Thu Nov 10, 2005 7:00 pm Post subject: |
|
|
fusion1275,
Please plug your camera in, wait for dmesg to show that its detected and failed, then post the content of /proc/bus/usb/devices.
If you want to make sense of that yourself, emerge and run usbview. I need the whole file so I can look at it in usbview too.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
fusion1275
Apprentice
Joined: 30 Oct 2005
Posts: 185
|
| Posted: Fri Nov 11, 2005 12:34 am Post subject: |
|
|
I have 4 usb ports on the back of the box here.
I plugged it in and then looked at the devices file and this is it here:
-r--r--r-- 1 root root 0 Nov 11 00:29 devices
Its empty!!
Is that normal? 
Here is the output of the dmesg once again:
| Code: | usb 3-2: new full speed USB device using uhci_hcd and address 17
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 17
usb-storage: waiting for device to settle before scanning
Vendor: DIGITAL Model: CAMERA Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
SCSI device sdb: 1002496 512-byte hdwr sectors (513 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 06 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 1002496 512-byte hdwr sectors (513 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 06 00 00
sdb: assuming drive cache: write through
sdb: sdb1
Attached scsi removable disk sdb at scsi5, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi5, channel 0, id 0, lun 0, type 0
usb-storage: device scan complete
usb 3-2: reset full speed USB device using uhci_hcd and address 17
usb 3-2: device descriptor read/64, error -110
usb 3-2: device descriptor read/64, error -110
usb 3-2: reset full speed USB device using uhci_hcd and address 17
usb 3-2: device descriptor read/64, error -110
usb 3-2: device descriptor read/64, error -110
usb 3-2: reset full speed USB device using uhci_hcd and address 17
usb 3-2: device not accepting address 17, error -110
usb 3-2: reset full speed USB device using uhci_hcd and address 17
usb 3-2: device not accepting address 17, error -84
scsi: Device offlined - not ready after error recovery: host 5 channel 0 id 0 lun 0
SCSI error : <5 0 0 0> return code = 0x50000
end_request: I/O error, dev sdb, sector 1002489
printk: 202 messages suppressed.
Buffer I/O error on device sdb1, logical block 1002264
scsi5 (0:0): rejecting I/O to offline device
Buffer I/O error on device sdb1, logical block 1002265
Buffer I/O error on device sdb1, logical block 1002266
Buffer I/O error on device sdb1, logical block 1002267
Buffer I/O error on device sdb1, logical block 1002268
Buffer I/O error on device sdb1, logical block 1002269
Buffer I/O error on device sdb1, logical block 1002270
usb 3-2: USB disconnect, address 17
scsi5 (0:0): rejecting I/O to device being removed
Buffer I/O error on device sdb1, logical block 1002264
Buffer I/O error on device sdb1, logical block 1002265
Buffer I/O error on device sdb1, logical block 1002266
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
scsi5 (0:0): rejecting I/O to device being removed
|
_________________
AMD XP 2600+
Mem: 1gb
Disk1: 60gb
Disk2: 250gb
Disk3: 250gb
Kernel: 2.6.19-r5
KDE: 3.5.5 |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54809
Location: 56N 3W
|
| Posted: Fri Nov 11, 2005 5:19 pm Post subject: |
|
|
fusion1275,
No thats not normal. It should contain all your USB connected devices , device descriptors.
That suggests that you dont gave support for usbfs in your kernel, or its not mounted. Check for the USB device filesystem option. It should get mounted automatically if its present.
For USB scanners and PTP cameras, its essental, since thats were the software looks to find the devices, otherwise its a very useful debug aid. Check your kernel and rebuild it if required.
Normally the file does not exist at all, rather then being empty.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
fusion1275
Apprentice
Joined: 30 Oct 2005
Posts: 185
|
| Posted: Sat Nov 12, 2005 2:41 am Post subject: |
|
|
Hi ya mate,
Listen I just wanna say thanks for all you hard work recently... I know all this is a real pain in the ass  And believe me its much appreaciated.
Ok I have taken a look into the usbfs issue you mentioned before. Below you will see an output from /var/log/messages, the mount command and my kernel options. Hope this helps a little!?!
/var/log/messages:
| Code: | pnp: PnP ACPI init
pnp: PnP ACPI: found 14 devices
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pnp: 00:01: ioport range 0xe400-0xe47f could not be reserved
pnp: 00:01: ioport range 0xe800-0xe81f could not be reserved
pnp: 00:0d: ioport range 0x290-0x297 has been reserved
|
Mount command from the console:
| Code: | fusion log # mount -t usbfs none /proc/bus/usb
mount: none already mounted or /proc/bus/usb busy
mount: according to mtab, usbfs is already mounted on /proc/bus/usb |
and last but least the kernel:
| Code: | <*> Support for Host-side USB
│ │[ ] USB verbose debug messages
│ │--- Miscellaneous USB options
│ │[*] USB device filesystem
│ │[ ] Enforce USB bandwidth allocation (EXPERIMENTAL)
│ │[ ] Dynamic USB minor allocation (EXPERIMENTAL)
│ │[ ] USB suspend/resume (EXPERIMENTAL)
│ │--- USB Host Controller Drivers
│ │<*> EHCI HCD (USB 2.0) support
│ │[ ] Full speed ISO transactions (EXPERIMENTAL)
│ │[ ] Root Hub Transaction Translators (EXPERIMENTAL)
│ │< > ISP116X HCD support
│ │<*> OHCI HCD support
│ │<*> UHCI HCD (most Intel and VIA) support
│ │< > SL811HS HCD support |
_________________
AMD XP 2600+
Mem: 1gb
Disk1: 60gb
Disk2: 250gb
Disk3: 250gb
Kernel: 2.6.19-r5
KDE: 3.5.5 |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54809
Location: 56N 3W
|
| Posted: Sat Nov 12, 2005 10:43 am Post subject: |
|
|
fusion1275,
Ah! Tnis is bad | Code: | <*> OHCI HCD support
<*> UHCI HCD (most Intel and VIA) support |
Choose only the right one.
If fact, if you have a recent USB 2.0 chip set, you don't need either, you choose
| Code: | <*> EHCI HCD (USB 2.0) support
Root Hub Transaction Translators (EXPERIMENTAL) |
and the EHCI driver uses the Transaction Translator to support USB 1.1.
If you want to build both USB 1.1 drivers, make them modules but only ever have ove loaded at a time.
Your /proc/bus/usb/devices will have entries like | Code: | T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3
B: Alloc= 0/900 us ( 0%), #Int= 1, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.12-gentoo-r9 ohci_hcd
S: Product=OHCI Host Controller
S: SerialNumber=0000:00:02.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms |
For each USB device you have. Its not a very user friendly format so for a better view of it.
You have VIA USB hardware , so you can remove OHCI HCD support from you kernel. Also you may want to add Himem Support (4GB)
Since your dmesg says | Code: | Warning only 896MB will be used.
Use a HIGHMEM enabled kernel.
896MB LOWMEM available.
On node 0 totalpages: 229376 |
and you have more memory than that. Himem will not affect you camera though.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
fusion1275
Apprentice
Joined: 30 Oct 2005
Posts: 185
|
| Posted: Sat Nov 19, 2005 9:35 pm Post subject: |
|
|
Sorry for not being on for a while... damn sickness got hold of me.
Right here is an update on this probem:
I altered the kernel and took out OHCI & UHCI then rebooted. When I did that and the box came back up none of my usb devices were detected at all. I couldnt mount my mp3 player and when I plugged in the camera it didnt even flicker in any of the logs at all.
So I recompiled again and just added UHCI. This has made my mp3 player come back to life as it was b4. BUT I still got all those errors when the camera gets plugged in. I installed "usbview" and here is the output from it with the camera plugged:
| Code: | DIGITAL CAMERA USB
Manufacturer: DSC
Speed: 12Mb/s (full)
USB Version: 1.00
Device Class: 00(>ifc)
Device Subclass: 00
Device Protocol: 00
Maximum Default Endpoint Size: 8
Number of Configurations: 1
Vendor Id: 0d64
Product Id: 5108
Revision Number: 1.00
Config Number: 1
Number of Interfaces: 1
Attributes: c0
MaxPower Needed: 0mA
Interface Number: 1
Name: usb-storage
Alternate Number: 0
Class: 08(Stor.)
Sub Class: 5
Protocol: 50
Number of Endpoints: 2
Endpoint Address: 82
Direction: In
Attribute: 2
Type: Bulk
Max Packet Size: 64
Interval: 0ms
Endpoint Address: 02
Direction: out
Attribute: 2
Type: Bulk
Max Packet Size: 64
Interval: 0ms
|
And still there are no entries in the /proc/bus/usb/devices file.
Any ideas?????
_________________
AMD XP 2600+
Mem: 1gb
Disk1: 60gb
Disk2: 250gb
Disk3: 250gb
Kernel: 2.6.19-r5
KDE: 3.5.5 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
