SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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)?
... 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?
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).
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.
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. :-)
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
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.
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
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:
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/
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
What I do when I have to recompile from the SuSE Sources is following:
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
Now edit the Makefile. There you will find a variable
Replace the value there with -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.
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! :-)
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):
depmod -F System.map-2.6.8-24.11-default
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
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.
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
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
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
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.
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
Let's try following.
Become root by: su -
Please insert the memory stick and the usb reader.
I will give you for illustration what is displayed in my case, so you know what i mean
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
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
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.
Please edit /etc/sysconfig/kernel
Look there for:
It' usually empty so MODULES_LOADED_ON_BOOT=" "
Add within the quote marks ehci_hcd