LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Suse/Novell
User Name
Password
Suse/Novell This Forum is for the discussion of Suse Linux.

Notices

Reply
 
Search this Thread
Old 02-15-2005, 07:27 AM   #1
Zhenya
Member
 
Registered: Sep 2004
Location: Maryland, USA
Distribution: Suse 9.3 Pro
Posts: 92

Rep: Reputation: 15
USB card reader and memory stick PROBLEM


My USB card reader and memory stick suddenly both stopped working on my SUse 9.2 pro box. 'dmesg' gives something like:

usb 3-5: new high speed USB device using address 4
usb 3-5: device not accepting address 4, error -32
usb 3-5: new high speed USB device using address 5
usb 3-5: device not accepting address 5, error -32

and if I try some more, I get similar results with different addresses. However, if I stick a different USB device (i.e. Bluetooth adapter) into the same port, it works just fine.

Does anyone has ever had the same problem? I don't even know where to look. My /sbin/cardmgr gives an error during the pcmcia boot startup process. Can it be involved in this problem (although I don't have any PCMCIA interfaces - it is a desktop)?
 
Old 02-15-2005, 08:57 AM   #2
Vlad-A
Member
 
Registered: May 2004
Location: Vienna, Austria
Distribution: Open SuSE 11, Mac OS X 10.5
Posts: 299

Rep: Reputation: 32
Suddenly stopped ...

Does it mean that the USB Reader and Memory Stick worked fine in the past with your system ?

Did you changed something in your system (e.g. updated kernel, etc. ) ?
What kernel version are you using ?
uname -a

Last edited by Vlad-A; 02-15-2005 at 08:58 AM.
 
Old 02-15-2005, 03:15 PM   #3
Zhenya
Member
 
Registered: Sep 2004
Location: Maryland, USA
Distribution: Suse 9.3 Pro
Posts: 92

Original Poster
Rep: Reputation: 15
... yes, suddenly stopped! :-( It worked really well before, and I have no idea what might have caused the problem. My kernel is the 2.6.8-24.11-smp, it is the last one from the Suse official YOU update. I thought that the newer kernel update might have brought this upon me, but I tried installing the old stock kernel back - still no success.

If I only new what package or module (-s) on Suse is responsible for the USB memory devices to work, I would probably have much more luck nailing down the problem. Do you know what it is?
 
Old 02-15-2005, 10:04 PM   #4
Vlad-A
Member
 
Registered: May 2004
Location: Vienna, Austria
Distribution: Open SuSE 11, Mac OS X 10.5
Posts: 299

Rep: Reputation: 32
You are of course right. It can be a broken kernel package. However it also
may be something wrong with the interrupt handling. You are using
2.6.8-24.11-smp which means that you have a dual processor system. Right ?
Try to boot with acpi=off boot option. If this does not help then try also noapic
(although this is not that gut with dual processor systems).

I suggest also you take a look on:
http://www.linux-usb.org/FAQ.html
Especially on the question:
Q: Why doesn't USB work at all? I get "device not accepting address"
and also on:
http://www.linux-usb.org/notAcceptFeedback.html

If nothing helps, you may try following:
Insert in your /etc/modprobe.conf following
options usbcore old_scheme_first=1
Detach your card reader abd usb stick. Reboot. Attach again
the reader and usb stick and see if everything works.
 
Old 02-16-2005, 06:51 PM   #5
Zhenya
Member
 
Registered: Sep 2004
Location: Maryland, USA
Distribution: Suse 9.3 Pro
Posts: 92

Original Poster
Rep: Reputation: 15
I do not have a multiprocessor system - it is just the way Intel's Hyper Threading technology works on Linux (but works - just fine!).

Thanks a lot for the info - now I at least have an idea of what is going on. Unfortunately nothing helped, and I am still trying to figure out what else I can do to fix it. I now I might have installed or tweaked something that caused this malfunction because I have another computer (a mini server) with the exactly same MB, the same Suse, and the same updates, and everything works there. However the kernel is 'default' there and not an 'smp'.

Do you think getting a separate PCI USB adapter card (that surely works with linux drivers) would work? Or will I run into the same problem (maybe the real problem is not in the USB adapter but in the compatability with the softwar and/or the system)?

If you have any other idea of what else I might try - I would be very glad. :-)

Anyway, thanks again,
 
Old 02-16-2005, 11:01 PM   #6
Vlad-A
Member
 
Registered: May 2004
Location: Vienna, Austria
Distribution: Open SuSE 11, Mac OS X 10.5
Posts: 299

Rep: Reputation: 32
Zhenya,

can you please post the output of lsmod ?
Are your USB Devices USB 1.1 or USB 2 ?
You may try also following boot option acpi=ht
There is also one additional thing you may try:
Try to boot with the default and not SMP kernel.
I know that you can only use the full advantage of HT
when you are using a smp kernel, but when there
are problems with hardware you may switch to a "normal" kernel.
Last but not least, compile your own kernel, dowloading the sources from
kernel.org.
 
Old 02-17-2005, 06:09 PM   #7
Zhenya
Member
 
Registered: Sep 2004
Location: Maryland, USA
Distribution: Suse 9.3 Pro
Posts: 92

Original Poster
Rep: Reputation: 15
Here is my lsmod:
=============================================================
Module Size Used by
nvidia 4822988 12
nvram 13832 0
snd_pcm_oss 66728 0
snd_mixer_oss 25216 1 snd_pcm_oss
snd_seq_midi 13856 0
snd_emu10k1_synth 12544 0
snd_emux_synth 45440 1 snd_emu10k1_synth
snd_seq_virmidi 11776 1 snd_emux_synth
snd_seq_midi_event 11904 2 snd_seq_midi,snd_seq_virmidi
snd_seq_midi_emul 12288 1 snd_emux_synth
snd_seq 63376 5 snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_event,snd_seq_midi_emul
snd_emu10k1 99592 1 snd_emu10k1_synth
snd_rawmidi 30628 3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1
snd_seq_device 13196 6 snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,snd_seq,snd_emu10k1,snd_rawmidi
snd_ac97_codec 76640 1 snd_emu10k1
snd_pcm 113284 3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_timer 31620 2 snd_seq,snd_pcm
snd_page_alloc 14600 2 snd_emu10k1,snd_pcm
snd_util_mem 9216 2 snd_emux_synth,snd_emu10k1
snd_hwdep 14212 2 snd_emux_synth,snd_emu10k1
snd 70532 17 snd_pcm_oss,snd_mixer_oss,snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,snd_seq_virmidi,snd_seq_midi _event,snd_seq_midi_emul,snd_seq,snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_t imer,snd_util_mem,snd_hwdep
soundcore 13792 1 snd
ipv6 272256 17
af_packet 26760 2
edd 14620 0
ds 22404 0
yenta_socket 24448 0
pcmcia_core 73652 2 ds,yenta_socket
joydev 13760 0
sg 42528 0
st 43164 0
sd_mod 22144 0
sr_mod 21156 0
scsi_mod 121412 4 sg,st,sd_mod,sr_mod
ehci_hcd 35204 0
ohci_hcd 25604 0
ohci1394 37764 0
ieee1394 116536 1 ohci1394
emu10k1_gp 7808 0
gameport 8832 1 emu10k1_gp
binfmt_misc 16392 1
ide_cd 44448 0
cdrom 42652 2 sr_mod,ide_cd
sis_agp 12164 1
agpgart 37804 2 sis_agp
evdev 13184 0
subfs 12672 3
nls_cp437 9856 1
vfat 18432 1
fat 49440 1 vfat
nls_utf8 6144 3
ntfs 100976 2
dm_mod 63104 0
usbcore 120164 4 ehci_hcd,ohci_hcd
sis900 24580 0
reiserfs 265808 1
=============================================================

I tried switching to the original kernel (the stock kernel that was on the Suse's CDs) but result was the same. I am not sure about kernel.org since Suse patches its kenels a lot, so some programs or modules may not work properly (or I don't understand something). By the way, what do you use, Suse? Did you also compiled your kernel by yourself? Any problems? Last time I tried compiling kernel for my Suse, I was not able to get subfs module working (wouldn't compile and the old one wouldn't work with the newere kernel). And didn't want to live without subfs (mounts CDs and DVDs automatically).

I tried modprobing various usb modules by hand (usb_storage, usbserial), but still with no luck.
 
Old 02-18-2005, 03:25 AM   #8
Vlad-A
Member
 
Registered: May 2004
Location: Vienna, Austria
Distribution: Open SuSE 11, Mac OS X 10.5
Posts: 299

Rep: Reputation: 32
Hello,

1) indeed patches SuSE the kernel. However let's take SuSE 9.2 for example.
Currently SuSE uses 2.6.8 kernel with patches. The kernel 2.6.8 was in kernel.org
last summer. I used it with my SuSE 9.1 since the SuSE 9.1 default kernel had problems with reading
UDF CD/DVD.

Currently the latest stable kernel at kernel.org is 2.6.10 with 2.6.11 being release candidate.
I can't imagine that the SuSE kernel has more current patches then 2.6.10.

2) What I am missing in your lsmod is usb_storage. You need this in order to access USB Sticks.
I also see a lot of modules loaded. Do you have also SCSI Devices attached ?
I suggest you disable all services you do not need. Also, since you do not have PCMCIA
disable starting PCMCIA. The easiest way to do this, is with:
YAST->System->Runlevel Editor
Look there for PCMCIA and other stuff you do want and disable it.
Reboot and see if everything works.

3) Regarding the non-smp kernel, I suggest you download following packages from from SuSE update ftp server:
ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/
kernel-default-2.6.8-24.11
kernel-source-2.6.8-24.11
kernel-docs-2.6.8-24.11
kernel-default-nongpl-2.6.8-24.11
kernel-um-2.6.8-24.11

Then install them with rpm -Uhv
You may also try the less gently approach with:
rpm -Uhv --nodeps

See if there is an entry for the kernel in /boot/grub/menu.lst added. If not add it manually Reboot!


4) With respect to compiling a new kernel
a) If you have downloaded teh sources from kernel.org then it's pretty straight-ahead and I did not
have any problems ever.

b) Regarding the recompiling the kernel from the SuSe provided source files. Well you have to be a little
bit carefull here. The problem that can occure is that you recompile the kernel with some
drivers compiled into it, and there are still loadable modules for that particular device in
/lib/modules.

What I do when I have to recompile from the SuSE Sources is following:

cd /usr/src/linux
make mrproper
make clean
cd /usr/src
Let's assume we are running kernel 2.6.8-24.11
Copy the sources
cp -r linux-2.6.8-24.11 linux-2.6.8-24.11-test
cd linux-2.6.8-24.11-test
Now edit the Makefile. There you will find a variable
EXTRAVERSION
Replace the value there with -test.
EXTRAVERSION=-test
This means that when we now compile the kernel the loadable modules will be
stored in /lib/modules/2.6.8-test and we will not interfear with 2.6.8-24.11
Now generate the config file with:
zcat /proc/config.gz > .config
make oldconfig && make prepare

You can now edit the .config file, to disable options, compile into
the kernel drivers or make them as loadable modules, etc.

Now recompile the kernel, copy the kernel image in /boot, create the initrd and make an
entry for the new kernel in the grub's menu.lst. You can now boot the new kernel,
but also have the old if something fails.


Hope this helps.

Good luck!

Last edited by Vlad-A; 02-18-2005 at 03:44 AM.
 
Old 02-19-2005, 10:23 AM   #9
Zhenya
Member
 
Registered: Sep 2004
Location: Maryland, USA
Distribution: Suse 9.3 Pro
Posts: 92

Original Poster
Rep: Reputation: 15
Hey, thanks for the kernel compilation info - I will try doing that sometime later when I have a time leeway in case I screw up something. Which kernel would you recommend me to get - Suse or kernel.org? Also, what do you think about more recent (not stable) versions of kernel?

About the modules, I myself wonder why I have so many sound modules loaded, what do you think? I have Sound Blaster's Audigy 2.

I tried loading usb_storage (and some other usb modules) by hand - but still, no luck.

Frankly, I hate to waste you time. So, if you feel we are getting nowhere, don't answer. :-) As for me, I will try recompiling the kernel sometime later, and if I have any questions I will post them here (if you don't mind). Thanks for your information, I feel I've learned something from your posts, and that's a good thing! :-)
 
Old 02-19-2005, 12:56 PM   #10
Vlad-A
Member
 
Registered: May 2004
Location: Vienna, Austria
Distribution: Open SuSE 11, Mac OS X 10.5
Posts: 299

Rep: Reputation: 32
1-a) I'll suggest you download the latest stable release from kernel.org which at this
moment is 2.6.10. I have made very good experience with it. I would wait a little
bit with the release candidates or how you call them "unstable". Actually they aren't unstabe, but not tested enough.
1-b) Regarding recompiling the SuSE Kernel: I really don't know
why someone would do that. A simple (re-) install of the kernel rpm packages would be enough.

2) I really do not know why there are so many sound modules. Perhaps this is normal for the
audigy card. Since I don't have one I can't tell for sure. Take a look in
YAST->Hardware->Sound what devices are set-up.

3) It may be that there is a possible HW Problem with your computer or the
module dependencies are messed up.
This may also help with the USB problem.

4) I suggest that you first create new depmod files. Log in as root.

Go into /boot directory and look for System.map-2.6.xx-yy files
In my case they are ( Since I do not have a SMP kernel, I am sure
that in your case the files are named similar but not the smae):
System.map-2.6.8-24.11-default
System.map-2.6.8-24.11-um

Now run:
depmod -F System.map-2.6.8-24.11-default
and
depmod -F System.map-2.6.8-24.11-um
(Use the names of your depmod files!!!!)

This will create new depmod files. Reboot your computer.
Do *not* forget to disable PCMCIA with the YAST Runlevel editor prior rebooting.

5) Also take a look you interrupts, ioports and dma
cat /proc/interrupts
cat /proc/ioports
cat /proc/dma

Take a look what devices are sharing one interrupt. You may also consider
to disable Audio for testing purposes (disable ALSA in the YAST Runlevel editor) if you see
that ohci (USB 1.1) and/or ehci (USB 2.0) devices are sharing the same inetrrupt with AUDIO.
with your sound-device. You may also delete your soundcard from YAST for testing purposes.
Make sure that no devices are sharing I/O ports.

6) If you have additional questions feel free to post them. No Problem at all.

Good luck!

Last edited by Vlad-A; 02-19-2005 at 01:00 PM.
 
Old 02-21-2005, 09:21 AM   #11
Zhenya
Member
 
Registered: Sep 2004
Location: Maryland, USA
Distribution: Suse 9.3 Pro
Posts: 92

Original Poster
Rep: Reputation: 15
OK, I ran moddep as you have said, I disabled pcmcia, then I load usb_storage by hand, and it still gibes the same error in dmesg. Here is the output of the procs you mentioned:

==================================================
jupiter:~ # cat /proc/dma
4: cascade
==================================================
jupiter:~ # cat /proc/ioports
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0376-0376 : ide1
03c0-03df : vesafb
03f6-03f6 : ide0
03f8-03ff : serial
0cf8-0cff : PCI conf1
9000-9007 : 0000:00:0a.1
9000-9007 : emu10k1-gp
9400-943f : 0000:00:0a.0
9400-943f : EMU10K1
9800-98ff : 0000:00:04.0
9800-98ff : sis900
b400-b40f : 0000:00:02.5
b400-b407 : ide0
b408-b40f : ide1
e600-e61f : 0000:00:02.1
==================================================
jupiter:~ # cat /proc/interrupts
CPU0
0: 206635 XT-PIC timer
1: 233 XT-PIC i8042
2: 0 XT-PIC cascade
3: 300 XT-PIC EMU10K1
4: 952 XT-PIC serial
5: 279 XT-PIC ohci1394, eth0
9: 18 XT-PIC ehci_hcd, ohci_hcd, ohci_hcd
10: 3 XT-PIC ohci1394
11: 18400 XT-PIC nvidia
12: 67 XT-PIC i8042
14: 14158 XT-PIC ide0
15: 816 XT-PIC ide1
NMI: 0
LOC: 206586
ERR: 0
MIS: 0
==================================================
dmesg
.
.
.
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb 1-5: new high speed USB device using address 4
usb 1-5: device not accepting address 4, error -32
usb 1-5: new high speed USB device using address 5
usb 1-5: device not accepting address 5, error -32
==================================================

The first three lines were generated after I did 'modprobe usb_storage' and the rest is the errors I got after inserting a USB memory stick (it is USB-2). I double checked by the way, both types of USB are enable in BIOS.

This is a state of 'acpi=off' kernel boot, with 'acpi=on' I get two columns in /proc/interrupts for CPU0 and CPU1, although CPU1 column is all zeroes.

I will try to recompile the kernel sometime later (in a week or two) and will let you know the result.
 
Old 02-21-2005, 09:53 AM   #12
Vlad-A
Member
 
Registered: May 2004
Location: Vienna, Austria
Distribution: Open SuSE 11, Mac OS X 10.5
Posts: 299

Rep: Reputation: 32
Hello Zhenya,

reagrding the
cat /proc/ioports output. Is this the entire output ?
I can't find there the USB units (ohci). Can you please check again
or verify that there aren't any USB controller in the output.
I mean I can see that USB has interrupt assigned but no IO-Ports.
That's strange. But perhaps those are using iomem.

I also need the output of lsusb and lspci -vvv. And of course
also
cat /proc/iomem

Last edited by Vlad-A; 02-21-2005 at 11:24 AM.
 
Old 02-21-2005, 12:26 PM   #13
Zhenya
Member
 
Registered: Sep 2004
Location: Maryland, USA
Distribution: Suse 9.3 Pro
Posts: 92

Original Poster
Rep: Reputation: 15
Yes, that was all I got from /proc/ioports.

Here is more info:
==================================================================
jupiter:~ # lsusb -vv

Bus 003 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.8-24.11-smp ohci_hcd
iProduct 2 OHCI Host Controller
iSerial 1 0000:00:03.1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 bytes 2 twice
bInterval 255

Bus 002 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.8-24.11-smp ohci_hcd
iProduct 2 OHCI Host Controller
iSerial 1 0000:00:03.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 bytes 2 twice
bInterval 255

Bus 001 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.8-24.11-smp ehci_hcd
iProduct 2 EHCI Host Controller
iSerial 1 0000:00:03.3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 bytes 2 twice
bInterval 12
==================================================================
jupiter:~ # lspci -vvv
0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS 645xx (rev 51)
Subsystem: Asustek Computer, Inc.: Unknown device 8086
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 32
Region 0: Memory at e0000000 (32-bit, non-prefetchable)
Capabilities: [c0] AGP version 3.5
Status: RQ=32 Iso- ArqSz=2 Cal=3 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3+ Rate=x4,x8
Command: RQ=1 ArqSz=0 Cal=3 SBA+ AGP+ GART64- 64bit- FW- Rate=x8

0000:00:01.0 PCI bridge: Silicon Integrated Systems [SiS]: Unknown device 0003 (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000e000-0000dfff
Memory behind bridge: df000000-dfffffff
Prefetchable memory behind bridge: eff00000-febfffff
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-

0000:00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25)
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0

0000:00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin B routed to IRQ 0
Region 4: I/O ports at e600 [size=32]

0000:00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
Subsystem: Asustek Computer, Inc.: Unknown device 8087
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 128
Interrupt: pin ? routed to IRQ 11
Region 4: I/O ports at b400 [size=16]

0000:00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 8087
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (20000ns max), cache line size 08
Interrupt: pin A routed to IRQ 9
Region 0: Memory at de800000 (32-bit, non-prefetchable)

0000:00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 8087
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (20000ns max), cache line size 08
Interrupt: pin B routed to IRQ 9
Region 0: Memory at de000000 (32-bit, non-prefetchable)

0000:00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (prog-if 20 [EHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 8087
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (20000ns max)
Interrupt: pin D routed to IRQ 9
Region 0: Memory at dd800000 (32-bit, non-prefetchable)
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

0000:00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
Subsystem: Asustek Computer, Inc.: Unknown device 80ff
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (13000ns min, 2750ns max)
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at 9800 [size=efee0000]
Region 1: Memory at dd000000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 00020000 [disabled]
Capabilities: [40] 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-

0000:00:09.0 FireWire (IEEE 1394): Texas Instruments TSB12LV23 IEEE-1394 Controller (prog-if 10 [OHCI])
Subsystem: Ads Technologies Inc: Unknown device 0000
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (750ns min, 1000ns max), cache line size 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at dc800000 (32-bit, non-prefetchable)
Region 1: Memory at dc000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] 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-

0000:00:0a.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
Subsystem: Creative Labs: Unknown device 1007
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 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 3
Region 0: I/O ports at 9400
Capabilities: [dc] 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-

0000:00:0a.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 04)
Subsystem: Creative Labs SB Audigy MIDI/Game Port
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Region 0: I/O ports at 9000
Capabilities: [dc] 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-

0000:00:0a.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04) (prog-if 10 [OHCI])
Subsystem: Creative Labs SB Audigy FireWire Port
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (500ns min, 1000ns max), cache line size 08
Interrupt: pin B routed to IRQ 5
Region 0: Memory at db800000 (32-bit, non-prefetchable)
Region 1: Memory at db000000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [44] 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+

0000:01:00.0 VGA compatible controller: nVidia Corporation NV35 [GeForce FX 5900XT] (rev a1) (prog-if 00 [VGA])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 248 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at df000000 (32-bit, non-prefetchable) [size=effe0000]
Region 1: Memory at f0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at 00020000 [disabled]
Capabilities: [60] 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-
Capabilities: [44] AGP version 3.0
Status: RQ=32 Iso- ArqSz=0 Cal=3 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=32 ArqSz=2 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8

==================================================================
jupiter:~ # cat /proc/iomem
00000000-0009fbff : System RAM
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000cf7ff : Video ROM
000f0000-000fffff : System ROM
00100000-3fffbfff : System RAM
00100000-00348add : Kernel code
00348ade-00416eff : Kernel data
3fffc000-3fffefff : ACPI Tables
3ffff000-3fffffff : ACPI Non-volatile Storage
db000000-db003fff : 0000:00:0a.2
db800000-db8007ff : 0000:00:0a.2
db800000-db8007ff : ohci1394
dc000000-dc003fff : 0000:00:09.0
dc800000-dc8007ff : 0000:00:09.0
dc800000-dc8007ff : ohci1394
dd000000-dd000fff : 0000:00:04.0
dd000000-dd000fff : sis900
dd800000-dd800fff : 0000:00:03.3
dd800000-dd800fff : ehci_hcd
de000000-de000fff : 0000:00:03.1
de000000-de000fff : ohci_hcd
de800000-de800fff : 0000:00:03.0
de800000-de800fff : ohci_hcd
df000000-dfffffff : PCI Bus #01
df000000-dfffffff : 0000:01:00.0
df000000-dfffffff : nvidia
e0000000-e7ffffff : 0000:00:00.0
eff00000-febfffff : PCI Bus #01
f0000000-f7ffffff : 0000:01:00.0
f0000000-f7ffffff : vesafb
fec00000-fec00fff : reserved
fee00000-fee00fff : reserved
ffff0000-ffffffff : reserved
==================================================================

... this is also when the kernel was given a 'acpi=off' parameter (in case it matters to know).
 
Old 02-21-2005, 03:26 PM   #14
Vlad-A
Member
 
Registered: May 2004
Location: Vienna, Austria
Distribution: Open SuSE 11, Mac OS X 10.5
Posts: 299

Rep: Reputation: 32
Everything looks good to me.


Let's try following.
Become root by: su -
Please insert the memory stick and the usb reader.
Then lsusb
I will give you for illustration what is displayed in my case, so you know what i mean
v-serer:/root# lsusb
Bus 004 Device 006: ID 0402:5634 ALi Corp.
Bus 004 Device 002: ID 0dda:2027 Integrated Circuit Solution, Inc.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 005: ID 03f0:2311 Hewlett-Packard
Bus 002 Device 004: ID 046d:08f0 Logitech, Inc.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 004: ID 0681:0001 Siemens Information and Communication Products
Bus 001 Device 001: ID 0000:0000

OK, here we have teh USB Stick at Bus 004 Device 006 (ALi Corp) with Vendor ID 0402 and Device ID 5634
Besides that there is an USB Card Reader at Bus 004 Device 002 (Integrated Circuit Solution, Inc.) with Vendor ID 0dda and device 2027

Please provide the output of lsusb in your case with inserted stick and reader

Now I need a detailed output of both devices which you can get with
lsusb -vv -s bus:device

So for the memory stick it will be
lsusb -vv -s 004:006
and for the reader it will be
lsusb -vv -s 004:002

Please provide the lsusb -vv -s for your USB Stick and Card Reader
 
Old 02-21-2005, 11:20 PM   #15
Vlad-A
Member
 
Registered: May 2004
Location: Vienna, Austria
Distribution: Open SuSE 11, Mac OS X 10.5
Posts: 299

Rep: Reputation: 32
Zhenya,

so far, from the Hardware point of view, everything looks good (at least to me), except that you can't use your memory stick and card reader.

Let's take a break and summarize:

With USB we have: low speed 1.5 MBit/s => USB 1.1
full speed 12 MBit/s => USB 1.1
and
high speed 480 MBit/s => USB 2.0

1) You write that your USB Bluetooth adapter works. Most Bluetooth adapters are USB 1.1. Let's assume it is a USB 1.1device
2) Your memory stick and card reader don't work. Let's assume those are USB 2.0 devices
Let's look at the message: usb 3-5: new high speed USB device using address 4
It also indicates that here we have an USB 2.0 device

3) We have ohci_hcd to deal with USB 1.1 and so far it looks that ohci_hcd works fine and so do USB 1.1 devices
Remark: I do not have ohci but uhci. This is since my USB host is Intel. In Linux for USB 1.1 controllers there are
uhci_hcd for Intel or Intel Compatible USB hosts and ohci_hcd for others.

4) We have ehci_hcd to deal with USB 2.0 and so far it seems that we have some trouble with USB 2.0 devices
Remark: ehci_hcd is used for all USB 2.0 hosts whether form Intel or not.

5) Most of the USB host controller shipped with newer computers support USB 1.1 *and* USB 2.0 => combi-host-controller
and the kernel usually loads ohci (or in my case uhci) prior ehci

Now let's try to load load ehci_hcd prior ohci_hcd.

Become root
su
Please edit /etc/sysconfig/kernel
Look there for:
MODULES_LOADED_ON_BOOT

It' usually empty so MODULES_LOADED_ON_BOOT=" "
Add within the quote marks ehci_hcd
so
MODULES_LOADED_ON_BOOT="ehci_hcd"

Reboot!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Mandriva LE - Memory stick USB 2.0 card reader silverbirch Mandriva 2 04-26-2005 03:46 AM
Memory Stick Duo Pro / Card Reader: Trouble! MMHein Linux - Hardware 1 09-28-2004 02:35 PM
Memory Stick Duo Pro / Card Reader: Trouble! MMHein Linux - General 1 09-28-2004 12:06 PM
Sony Memory Stick PC-Card Reader k4zau Linux - Hardware 4 03-30-2003 03:46 PM
memory stick / CF memory card reader X-dazed Linux - Newbie 1 01-21-2003 12:32 AM


All times are GMT -5. The time now is 08:25 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration