USB Problems [solved]

January 4, 2005

i have a digital camera, ngage and zire72 PDA --- all i link to my pc thru their respective USB cables. as I recall my USB with MDK10.0 worked fine, all the devices were mounted without hassles, and i could access the files off the memory card in each respective device.

since moving to 10.1 community and official i have not been able to use MDK to use any of my usb devices - including my optical usb mouse (this includes the installation process - i had to get a usb/ps2 convertor thingy to fix that problem). all my USB devices work perfectly well on win2k (i run dual boot) and i also took off MDK for a few hours to try out slackware, worked fine there.... basically when i plug in a device in a terminal it will say "disabling IRQ #21" -- after i either leave the device in, or disconnect it, i cannot open the Control Centre etc. and my pc hangs when i try to reset it.

basically just asking is there some fix to this? all USB options are enabled in my bios. i have a relatively new computer, and ill post specs if they're required for an answer. i've been on MDK for a while, but still nowhere near as competent with it as I should be. so if I need to do any console commands, please tell me.

thanks in advance =)

Gowator · January 4, 2005

The Zire72 will take a little messing about but not much, but first obviously the USB needs to be working.

I haven't actually tried my Zire in MDK but it does work in Debian with jpilot (although kpilot locks up)

All that is mising is the alias in the modules.conf which identifies the device and tells mdk to load visor.ko which is the module used.

First off though the USB...

What motherboard do you have?

Also can you as root in a console type

lspci -v -v

and copy and paste the output?

January 4, 2005

yep i own this pc and all, so i have root access. the zire72 is not a huge deal, i was just using it as an example that usb wasn't working =) . I didn't get a box when i bought this motherboard (nothin illegal lol), but from the below output, i assume I got this one: Giga-byte Technology GA-7VAX Mainboard .

here's the output logged in as root of the lspci -v -v command you suggested.

# lspci -v -v
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600 AGP] Host Bridge
       Subsystem: Giga-byte Technology GA-7VAX Mainboard
       Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort+ >SERR- <PERR+
       Latency: 8
       Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
       Capabilities: [80] AGP version 3.5
               Status: RQ=32 Iso- ArqSz=0 Cal=2 SBA+ ITACoh- GART64- HTrans- 64 bit- FW+ AGP3+ Rate=x4,x8
               Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW+ Rate=x 8
       Capabilities: [c0] Power Management version 2
               Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot -,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (prog-if 00 [Normal  decode])
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR+ FastB2B-
       Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort+ >SERR- <PERR-
       Latency: 0
       Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
       I/O behind bridge: 00009000-00009fff
       Memory behind bridge: e8000000-e9ffffff
       Prefetchable memory behind bridge: c0000000-dfffffff
       BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
       Capabilities: [80] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot -,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
       Subsystem: Creative Labs SBLive! Player 5.1
       Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 32 (500ns min, 5000ns max)
       Interrupt: pin A routed to IRQ 18
       Region 0: I/O ports at a000 [size=32]
       Capabilities: [dc] Power Management version 1
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot -,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:0a.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07)
       Subsystem: Creative Labs Gameport Joystick
       Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 32
       Region 0: I/O ports at a400 [size=8]
       Capabilities: [dc] Power Management version 1
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot -,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller  (rev 80) (prog-if 00 [UHCI])
       Subsystem: Giga-byte Technology GA-7VAX Mainboard
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 32, cache line size 08
       Interrupt: pin A routed to IRQ 21
       Region 4: I/O ports at a800 [size=32]
       Capabilities: [80] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3h ot+,D3cold+)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME+

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller  (rev 80) (prog-if 00 [UHCI])
       Subsystem: Giga-byte Technology GA-7VAX Mainboard
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 32, cache line size 08
       Interrupt: pin B routed to IRQ 21
       Region 4: I/O ports at ac00 [size=32]
       Capabilities: [80] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3h ot+,D3cold+)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller  (rev 80) (prog-if 00 [UHCI])
       Subsystem: Giga-byte Technology GA-7VAX Mainboard
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 32, cache line size 08
       Interrupt: pin C routed to IRQ 21
       Region 4: I/O ports at b000 [size=32]
       Capabilities: [80] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3h ot+,D3cold+)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) (prog-if 20 [EHC I])
       Subsystem: Giga-byte Technology GA-7VAX Mainboard
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 32, cache line size 10
       Interrupt: pin D routed to IRQ 19
       Region 0: Memory at ea000000 (32-bit, non-prefetchable) [size=256]
       Capabilities: [80] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3h ot+,D3cold+)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
       Subsystem: Giga-byte Technology GA-7VAX Mainboard
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping+ SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 0
       Capabilities: [c0] Power Management version 2
               Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot -,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/ C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
       Subsystem: Giga-byte Technology GA-7VAX Mainboard
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 32
       Interrupt: pin A routed to IRQ 22
       Region 4: I/O ports at b400 [size=16]
       Capabilities: [c0] Power Management version 2
               Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot -,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 A C97 Audio Controller (rev 50)
       Subsystem: Giga-byte Technology GA-7VAX Onboard Audio (Realtek ALC650)
       Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Interrupt: pin C routed to IRQ 22
       Region 0: I/O ports at b800 [size=256]
       Capabilities: [c0] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot -,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:13.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139 C+ (rev 10)
       Subsystem: Realtek Semiconductor Co., Ltd. RT8139
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 32 (8000ns min, 16000ns max)
       Interrupt: pin A routed to IRQ 18
       Region 0: I/O ports at bc00 [size=256]
       Region 1: Memory at ea001000 (32-bit, non-prefetchable) [size=256]
       Capabilities: [50] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3h ot+,D3cold+)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:14.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller ( rev 46) (prog-if 10 [OHCI])
       Subsystem: Giga-byte Technology: Unknown device 1000
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 32 (8000ns max), cache line size 08
       Interrupt: pin A routed to IRQ 16
       Region 0: Memory at ea002000 (32-bit, non-prefetchable) [size=2K]
       Region 1: I/O ports at c000 [size=128]
       Capabilities: [50] Power Management version 2
               Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot +,D3cold+)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] ( prog-if 00 [VGA])
       Subsystem: C.P. Technology Co. Ltd PowerColor R96A-C3N
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 255 (2000ns min), cache line size 08
       Interrupt: pin A routed to IRQ 16
       Region 0: Memory at c0000000 (32-bit, prefetchable) [size=256M]
       Region 1: I/O ports at 9000 [size=256]
       Region 2: Memory at e9000000 (32-bit, non-prefetchable) [size=64K]
       Expansion ROM at <unassigned> [disabled] [size=128K]
       Capabilities: [58] AGP version 3.0
               Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 6 4bit- FW+ AGP3+ Rate=x4,x8
               Command: RQ=32 ArqSz=0 Cal=0 SBA+ AGP+ GART64- 64bit- FW+ Rate=x 8
       Capabilities: [50] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot -,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Seconda ry)
       Subsystem: C.P. Technology Co. Ltd: Unknown device 2065
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
       Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
       Latency: 32 (2000ns min), cache line size 08
       Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
       Region 1: Memory at e9010000 (32-bit, non-prefetchable) [size=64K]
       Capabilities: [50] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot -,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=0 PME-

hopefully this helps. thanks.

Gowator · January 4, 2005

Hmm,

I can see the USB controller is reporting and has 3x USB1.1 and 1xUSB2.0 controller.

(so good news)

as root ...

can you

lsmod

this will show which modules are loading....

we really need to check you don't have a USB1.1 and USB2.0 conflict...

(The Zire we can sort out later)

p.s. Anyone else please jump in .... don't wait for me if you have suggestions...

January 4, 2005

as asked for mate =)

# lsmod
Module                  Size  Used by
isofs                  31352  1
udf                    86340  0
usb-storage            65504  0
scsi_mod              104044  1 usb-storage
ehci-hcd               26244  0
uhci-hcd               28752  0
usbcore               103172  5 usb-storage,ehci-hcd,uhci-hcd
fglrx                 228028  7
md5                     3584  1
ipv6                  230916  8
rfcomm                 32348  0
l2cap                  19876  5 rfcomm
bluetooth              39076  4 rfcomm,l2cap
snd-seq-midi            6624  0
snd-emu10k1-synth       6656  0
snd-emux-synth         34976  1 snd-emu10k1-synth
snd-seq-virmidi         5632  1 snd-emux-synth
snd-seq-midi-emul       7200  1 snd-emux-synth
snd-seq-oss            31232  0
snd-seq-midi-event      6080  3 snd-seq-midi,snd-seq-virmidi,snd-seq-oss
snd-seq                47440  8 snd-seq-midi,snd-emux-synth,snd-seq-virmidi,snd-seq-midi-emul,snd-seq-oss,snd-seq-midi-event
snd-via82xx            22372  0
gameport                3328  1 snd-via82xx
snd-mpu401-uart         5856  1 snd-via82xx
snd-pcm-oss            49480  0
snd-mixer-oss          17376  1 snd-pcm-oss
snd-emu10k1            90728  1 snd-emu10k1-synth
snd-rawmidi            19300  4 snd-seq-midi,snd-seq-virmidi,snd-mpu401-uart,snd-emu10k1
snd-pcm                81800  3 snd-via82xx,snd-pcm-oss,snd-emu10k1
snd-timer              20356  2 snd-seq,snd-pcm
snd-seq-device          6344  7 snd-seq-midi,snd-emu10k1-synth,snd-emux-synth,snd-seq-oss,snd-seq,snd-emu10k1,snd-rawmidi
snd-ac97-codec         69392  2 snd-via82xx,snd-emu10k1
snd-page-alloc          7400  3 snd-via82xx,snd-emu10k1,snd-pcm
snd-util-mem            3232  2 snd-emux-synth,snd-emu10k1
snd-hwdep               6916  2 snd-emux-synth,snd-emu10k1
snd                    45988  15 snd-emux-synth,snd-seq-virmidi,snd-seq-oss,snd-seq,snd-via82xx,snd-mpu401-uart,snd-pcm-oss,snd-mixer-oss,snd-emu10k1,snd-rawmidi,snd-pcm,snd-timer,snd-seq-device,snd-ac97-codec,snd-hwdep
soundcore               7008  1 snd
af_packet              16072  0
floppy                 55088  0
8139too                20928  0
mii                     4224  1 8139too
eth1394                17000  0
ide-cd                 37280  1
cdrom                  37724  1 ide-cd
ohci1394               30788  0
ieee1394              292056  2 eth1394,ohci1394
loop                   12520  0
nls_iso8859-1           3680  5
ntfs                  147964  3
supermount             34804  3
via-agp                 7360  1
agpgart                27752  2 via-agp
ext3                  120680  2
jbd                    49080  1 ext3

aRTee · January 4, 2005

Side question: have you updated the KDE stuff - seems there are various issues with usb storage stuff on KDE, from locking konquerors to locking systems and then some, all fixed with the updates.

Gowator · January 4, 2005

well it seems to be creating the USB 1.1 and 2.0

ehci-hcd               26244  0
uhci-hcd               28752  0

lets see if you can mount it....As root in CLI

now if your digital camera is USB mass storage compatible then you should be able to plug it in and moiunt by hand (Im following aRTee's advice about updates here and presuming we will leave KDE out of the equation till later)

mount /dev/sda1 /mnt/removeable

you might need to try sda2 ..etc.

this will check 2 things

a.. that the device file is being created

b.. that it can be mounted...

the USB keyb is a pain to test.. if you unlug the ps/2 to test it its likely to just lock up... so lets see if we can get one device working 1st/

usbview is a good tool.. if KDe control centre is locking up lets try installing usbview

(just urpmi usbview)

January 6, 2005

mount /dev/sda1 /mnt/removeable

i do that, and change /sda1 to /sda2 /sda3 etc etc etc.

the output is:

mount /dev/sda1 /mnt/removeable/
mount: you must specify the filesystem type

i have USBVIEW. i don't use KDE, i use Gnome, but i've tried KDE with my usb devices and still no luck.

Gowator · January 6, 2005

OK... what does usbview 'see'

the windows manager shouldn't matter but aRTee pointed out some probs that happen in KDE..so its good we stay in Gnome... itr rules out a potential prob...

We need to work out why the devices aren't firing up?

January 6, 2005

its sees

EHCI HOST CONTROLLER

UHCI HOST CONTROLLER

then each of them when clicked have details behidn them. the only details that differ in them are their serial numbers, and the EHCI has a faster speed of 480mb/s, as opposed to the UHCI's having 12mb/s full speed or some crap :P

January 18, 2005

*bump* i've still had no luck with this problem. I reverted back to MDK10 community edition, and my USB devices work, but I'd rather use the latest official vers (10.1), so im back to trying to fix this.

this an extract from my syslog, which only recently in an IRC i learnt existed (a testiment to my n00bness :P )

hope this can shed some light on the situation? (the below i believe is the output of what happened when i plugged in my digital camera, a nikon coolpix 2200)

Jan 18 17:28:30 2Dope kernel: [pg0+812068736/1069613056] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 18 17:28:30 2Dope kernel: [<f0a60f80>] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 18 17:28:30 2Dope kernel: [pg0+812068736/1069613056] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 18 17:28:30 2Dope kernel: [<f0a60f80>] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 18 17:28:30 2Dope kernel: [pg0+812068736/1069613056] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 18 17:28:30 2Dope kernel: [<f0a60f80>] (usb_hcd_irq+0x0/0x70 [usbcore])
Jan 18 17:28:30 2Dope kernel: Disabling IRQ #21
Jan 18 17:28:30 2Dope kernel: usb 2-2: new full speed USB device using address 2
Jan 18 17:28:35 2Dope kernel: usb 2-2: control timeout on ep0out
Jan 18 17:28:40 2Dope kernel: usb 2-2: control timeout on ep0out
Jan 18 17:28:41 2Dope kernel: usb 2-2: device not accepting address 2, error -110
Jan 18 17:28:41 2Dope kernel: usb 2-2: new full speed USB device using address 3
Jan 18 17:28:46 2Dope kernel: usb 2-2: control timeout on ep0out
Jan 18 17:28:51 2Dope kernel: usb 2-2: control timeout on ep0out
Jan 18 17:28:51 2Dope kernel: usb 2-2: device not accepting address 3, error -110
Jan 18 18:01:00 2Dope CROND[6061]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly) 
Jan 18 18:07:56 2Dope kernel: hdd: request sense failure: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error }
Jan 18 18:07:56 2Dope kernel: hdd: request sense failure: error=0x7fIllegalLengthIndication EndOfMedia Aborted Command MediaChangeRequested LastFailedSense 0x07 
Jan 18 19:01:00 2Dope CROND[8328]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly) 
Jan 18 20:01:00 2Dope CROND[10497]: (root) CMD (nice -n 19 run-parts /etc/cron.hourly) 
Jan 18 20:01:51 2Dope kernel: usb 2-2: new full speed USB device using address 4
Jan 18 20:01:56 2Dope kernel: usb 2-2: control timeout on ep0out

Gowator · January 18, 2005

its sees

EHCI HOST CONTROLLER

UHCI HOST CONTROLLER

UHCI HOST CONTROLLER

UHCI HOST CONTROLLER

then each of them when clicked have details behidn them. the only details that differ in them are their serial numbers, and the EHCI has a faster speed of 480mb/s, as opposed to the UHCI's having 12mb/s full speed or some crap :P

<{POST_SNAPBACK}>

OK but what i mean is you need to attach the digital camera which hopefully has a USB Mass storage mode (i.e. it works without drivers in windows and appears as a disk)

The Ngage I don't know but i know the Zire won't work without a little hacking...

What we need is to get a standard device working first like hopefully the camera. Once we know its working then we can fix the Zire and look at the ngage...

In other words USBVIEW should show the camera or its storage card etc.

We need to know if this is happening or not.

January 18, 2005

PROBLEM SOLVED

im not quite sure how, but in #mandrake on freenode, i've been asking about my problem a bit, and _ranger_ came up with a suggestion of adding

pci = noapic

to the end of my kernel boot options thing.

thanks very much to all that helped. i dunno what this option really does, but it worked, and hopefully this advice can help some others =)

sellis · February 5, 2005

Looks like this is a known problem with interrupt allocation between certain USB controllers and the APIC (advanced programmable interrupt controller?) subsystem. Some additional references, courtesy of Google:

http://seclists.org/lists/linux-kernel/2003/May/2621.html

http://www.ussg.iu.edu/hypermail/linux/ker...304.2/0476.html

I'm having a similar problem with USB at the moment and am just off to check if this does the trick for me...

wilco1973 · February 5, 2005

advanced programmable interrupt controller?

yep that is correct :cheesy:

USB Problems [solved]

Recommended Posts

Guest J2Dope

Link to comment

Share on other sites

Link to comment

Share on other sites

Guest J2Dope

Link to comment

Share on other sites

Link to comment

Share on other sites

Guest J2Dope

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Guest J2Dope

Link to comment

Share on other sites

Link to comment

Share on other sites

Guest J2Dope

Link to comment

Share on other sites

Guest J2Dope

Link to comment

Share on other sites

Link to comment

Share on other sites

Guest J2Dope

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation