SuSE 9.2, USB ports, and IRQ10

SuSE 9.2, USB ports, and IRQ10

Post by Paul Cisz » Mon, 03 Jan 2005 11:08:37



I think I have figured out why SuSE 9.2 and FC3 cannot see any of my
USB ports:  They turn off IRQ10 during boot.  Does either of these
versions of Linux have a problem with IRQ10?  I suspect it is rather
an objection to my USB card, which is built in to the motherboard and
cannot be changed.  In which case, changing the IRQ, if I could figure
that out, would not help.

Any advice would be appreciated.

--
Please reply to:            | "When you are dealing with secretive regimes
pciszek at panix dot com    |  that want to deceive, you're never going to
Autoreply is disabled       |  be able to be positive." -Condoleezza Rice

 
 
 

SuSE 9.2, USB ports, and IRQ10

Post by Dances With Crow » Tue, 04 Jan 2005 00:27:18


On Sun, 2 Jan 2005 02:08:37 +0000 (UTC), Paul Ciszek staggered into the
Black Sun and said:

Quote:> I think I have figured out why SuSE 9.2 and FC3 cannot see any of my
> USB ports:  They turn off IRQ10 during boot.

What?  Why do you say that?  Follow up to this message with any lines
from dmesg that reference irq 10.

Quote:> Does either of these versions of Linux have a problem with IRQ10?

No.  The problem lies elsewhere.  Post the output of "lspci -vv | grep
-A6 USB" and "lsmod" as well as the lines from dmesg.

Quote:> suspect it is rather an objection to my USB card, which is built in to
> the motherboard and cannot be changed.  In which case, changing the
> IRQ, if I could figure that out, would not help.

Modern motherboards and OSes don't have a problem with sharing ISA IRQs,
so changing the USB chipset's IRQ will probably not solve anything.  You
should make sure that "Assign IRQ to USB" is set to Y in the BIOS Setup,
though.

--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /    mail: TRAP + SPAN don't belong
http://www.brainbench.com     /                Hire me!
-----------------------------/ http://crow202.dyndns.org/~mhgraham/resume

 
 
 

SuSE 9.2, USB ports, and IRQ10

Post by Paul Cisz » Tue, 04 Jan 2005 15:45:02


In article <slrnctg4j2.aqv.danSPANceswitTRAPhcr...@samantha.crow202.dyndns.org>,
Dances With Crows  <daSPANnceswithcroTRA...@gmail.com> wrote:

>On Sun, 2 Jan 2005 02:08:37 +0000 (UTC), Paul Ciszek staggered into the
>Black Sun and said:
>> I think I have figured out why SuSE 9.2 and FC3 cannot see any of my
>> USB ports:  They turn off IRQ10 during boot.

>What?  Why do you say that?  Follow up to this message with any lines
>from dmesg that reference irq 10.

First of all, an update:  I reset my motherboard to the factory
configuration, and SuSE has become more verbose about the USB problem.
(Also, my sound card started working with a couple, but not most, of
the audio players.  Yipee.)  A couple boots ago, I actually had the
following message pop up while I was browsing through the file system:

>Message from syslogd@linux at Sun Feb  1 21:08:21 2004 ...
>linux kernel: Disabling IRQ #10

I have not seen this message since.  Also, when I execute the usbview
command, I get a usbview window and an error message window that says:

>Cannot open the file /proc/bus/usb/devices

>Verify that you have USB compiled into your kernel,
>have the USB core modules loaded, and have the
>usbdevfs filesystem mounted.

I let SuSE 9.2 install everything it wanted to; if the USB core modules
aren't there, it's because they aren't part of the SuSE 9.2 install.

OK, now on to the information you asked for.  The first mention of IRQ 10
in the boot messages is this block:

>ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
>ACPI: PCI interrupt 0000:00:0f.1[A] -> GSI 10 (level, low) -> IRQ 10
>ACPI: PCI interrupt 0000:00:10.0[A] -> GSI 10 (level, low) -> IRQ 10
>ACPI: PCI interrupt 0000:00:10.1[A] -> GSI 10 (level, low) -> IRQ 10
>ACPI: PCI interrupt 0000:00:10.2[B] -> GSI 11 (level, low) -> IRQ 11
>ACPI: PCI interrupt 0000:00:10.3[B] -> GSI 11 (level, low) -> IRQ 11
>ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
>ACPI: PCI interrupt 0000:00:10.4[C] -> GSI 10 (level, low) -> IRQ 10
>ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 10 (level, low) -> IRQ 10
>ACPI: PCI interrupt 0000:00:12.0[A] -> GSI 10 (level, low) -> IRQ 10
>ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 10 (level, low) -> IRQ 10

Then, a while later:

>VP_IDE: IDE controller at PCI slot 0000:00:0f.1
>ACPI: PCI interrupt 0000:00:0f.1[A] -> GSI 10 (level, low) -> IRQ 10

Could it be that SuSE is trying to assign IRQ 10 to an IDE controller?

Later still, I see:

>via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
>ACPI: PCI interrupt 0000:00:12.0[A] -> GSI 10 (level, low) -> IRQ 10
>eth0: VIA Rhine II at 0xc800, 00:50:2c:a3:88:d6, IRQ 10.

The ethernet card isn't working either, and never has; could that be
due to a conflict?  Anyway, here is what I think is the important part:

>irq 10: nobody cared!
> [<c010868c>] __report_bad_irq+0x1c/0x70
> [<c010875b>] note_interrupt+0x5b/0x80
> [<c010894c>] do_IRQ+0xdc/0x120
> [<c0106cd8>] common_interrupt+0x18/0x20
> [<c01205f1>] __do_softirq+0x31/0xa0
> [<c0120686>] do_softirq+0x26/0x30
> [<c0108955>] do_IRQ+0xe5/0x120
> [<c0106cd8>] common_interrupt+0x18/0x20
> [<c0108d5c>] setup_irq+0x6c/0xb0
> [<e1289210>] rhine_interrupt+0x0/0x1f0 [via_rhine]
> [<c0108a3f>] request_irq+0x6f/0xb0
> [<e1288e8c>] rhine_open+0x2c/0xd0 [via_rhine]
> [<c0294548>] dev_open+0x58/0x70
> [<c029595c>] dev_change_flags+0x4c/0x110
> [<c02d3513>] devinet_ioctl+0x573/0x620
> [<c02d4ff6>] inet_ioctl+0x66/0x90
> [<c028cc0e>] sock_ioctl+0x16e/0x240
> [<c0160b5d>] sys_ioctl+0x17d/0x230
> [<c028caa0>] sock_ioctl+0x0/0x240
> [<c0105c69>] sysenter_past_esp+0x52/0x79
>handlers:
>[<e1289210>] (rhine_interrupt+0x0/0x1f0 [via_rhine])
>Disabling IRQ #10

As you can see, it explicitly says that it disabled IRQ #10.
Later it assigns it again:

>ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 10 (level, low) -> IRQ 10
>No.  The problem lies elsewhere.  Post the output of "lspci -vv | grep
>-A6 USB" and "lsmod" as well as the lines from dmesg.

Here goes lspci -vv | grep:

- Show quoted text -

>0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
>    Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 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-
>    Latency: 32, cache line size 08
>    Interrupt: pin A routed to IRQ 10
>    Region 4: I/O ports at b400 [size=32]
>    Capabilities: [80] Power Management version 2
>--
>0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
>    Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 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-
>    Latency: 32, cache line size 08
>    Interrupt: pin A routed to IRQ 10
>    Region 4: I/O ports at b800 [size=32]
>    Capabilities: [80] Power Management version 2
>--
>0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
>    Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 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-
>    Latency: 32, cache line size 08
>    Interrupt: pin B routed to IRQ 11
>    Region 4: I/O ports at bc00 [size=32]
>    Capabilities: [80] Power Management version 2
>--
>0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) (prog-if 00 [UHCI])
>    Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 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-
>    Latency: 32, cache line size 08
>    Interrupt: pin B routed to IRQ 11
>    Region 4: I/O ports at c000 [size=32]
>    Capabilities: [80] Power Management version 2
>--
>0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
>    Subsystem: VIA Technologies, Inc. USB 2.0
>    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, cache line size 08
>    Interrupt: pin C routed to IRQ 10
>    Region 0: Memory at ee021000 (32-bit, non-prefetchable)
>    Capabilities: [80] Power Management version 2

And lsmod:

- Show quoted text -

>Module                  Size  Used by
>nls_iso8859_1           4224  0
>nls_cp437               5888  0
>vfat                   13056  0
>fat                    43168  1 vfat
>udf                    84612  0
>thinkpad                6020  0
>evdev                   8960  0
>joydev                  9664  0
>sg                     35872  0
>st                     37404  0
>sr_mod                 16292  0
>ide_cd                 38176  0
>cdrom                  36508  2 sr_mod,ide_cd
>nvram                   8328  0
>usbserial              26856  0
>parport_pc             37824  1
>lp                     10536  0
>parport                37960  2 parport_pc,lp
>edd                    10012  0
>speedstep_lib           4228  0
>freq_table              4356  0
>thermal                17928  0
>processor              25640  1 thermal
>fan                     5380  0
>button                  8464  0
>battery                11396  0
>ac                      6404  0
>snd_pcm_oss            57896  0
>snd_mixer_oss          19200  1 snd_pcm_oss
>snd_via82xx            26276  1
>snd_ac97_codec         69728  1 snd_via82xx
>snd_pcm                96776  4 snd_pcm_oss,snd_via82xx,snd_ac97_codec
>snd_timer              24708  1 snd_pcm
>snd_page_alloc         10248  2 snd_via82xx,snd_pcm
>gameport                4608  1 snd_via82xx
>snd_mpu401_uart         7552  1 snd_via82xx
>snd_rawmidi            24356  1 snd_mpu401_uart
>snd_seq_device          8716  1 snd_rawmidi
>snd                    60164  10 snd_pcm_oss,snd_mixer_oss,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
>soundcore               9056  1 snd
>ipt_TOS                 2560  14
>ip6t_LOG                6656  17
>ip6t_limit              2432  17
>ipt_LOG                 6912  30
>ipt_limit               2432  30
>ipt_pkttype             1792  2
>af_packet              20872  2
>ip6t_state              2048  22
>ip6_conntrack          38404  1 ip6t_state
>ipt_state               2176  28
>ip6t_REJECT             7552  3
>ipt_REJECT              6784  3
>iptable_mangle          2944  1
>iptable_filter          3072  1
>ip6table_mangle         2688  0
>ip_nat_ftp              5232  0
>iptable_nat            23980  1 ip_nat_ftp
>ip_conntrack_ftp       72624  1 ip_nat_ftp
>ip_conntrack           43512  4 ipt_state,ip_nat_ftp,iptable_nat,ip_conntrack_ftp
>ip_tables              17664  9 ipt_TOS,ipt_LOG,ipt_limit,ipt_pkttype,ipt_state,ipt_REJECT,iptable_mangle,iptable_filter,iptable_nat
>ip6table_filter         2816  1
>ip6_tables             18816  6 ip6t_LOG,ip6t_limit,ip6t_state,ip6t_REJECT,ip6table_mangle,ip6table_filter
>ipv6                  237312  15 ip6_conntrack,ip6t_REJECT
>subfs                   7552  3
>nls_utf8                2176  2
>ntfs                   91888  2
>via_rhine              19972  0
>dm_mod                 54524  0
>mii                     4992  1 via_rhine
>usbcore               106724  2 usbserial
>reiserfs              242000  1
>sata_via                7428  1
>libata                 41860  1 sata_via
>sd_mod                 16912  2
>scsi_mod              111308  5 sg,st,sr_mod,libata,sd_mod

Thank you for your help.

--
Please reply to:                 | "So, what are you gonna do with
...

read more »

 
 
 

SuSE 9.2, USB ports, and IRQ10

Post by Paul Cisz » Wed, 05 Jan 2005 06:39:27


It turns out that there was a MIDI port using IRQ 10 as well, and once
I 86'd it, the USB ports, the Ethernet connection, and the Sound Card
*all* worked fine.

My only remaining hardware problem is finding a wireless LAN card that
will work.

--
Please reply to:            | "When you are dealing with secretive regimes
pciszek at panix dot com    |  that want to deceive, you're never going to
Autoreply is disabled       |  be able to be positive." -Condoleezza Rice

 
 
 

1. HELP: External USB Drive Not Seen by SuSE 9.2

My saga of the USB External Drives continues...  Last time I'd had problems
partitioning the drive and formatting.  I'd been kindly helped past the
format part via this NG, but could never get the formatting proper.
Basically, when I did ext3, I got a goofy message at the end of the format,
and with reiser, I got an journal error when I wrote a large chunk of stuff
to the drive.

After poking about the groups, it seemed that upgrading my kernel was the
best bet since I got the impression that external USB drives were handled
better in a later kernel.  (Mine was SuSE 8.2 with 2.4.something, and I was
unable to get YaST to update my kernel.)  OK, sez I, let's just bite ye olde
bullet and re-install SuSE 9.2.  (Woulda done 9.3, but can't FTP it yet, and
I'll be damned if I'm paying Microsoft prices to Novell for the box....)
The 9.2 FTP install was staggeringly tedious (why can't I set a checkbox to
keep retrying when it can't d/l a package rather then have to push that
RETRY button all night long?).  I also came THIS close to wiping out my data
drive because the install decided it would be better to install there rather
than on the existing root filesystem. DOH!  I just don't get some of these
defaults.  Anyway, I digress...

Seems the new kernel (2.6.8-24.16--since I applied YOU after the initial
install) seems to handle my drive even effing worse than the 2.4.whatever
did!  (I have a Seagate 250GB in an external enclosure into the USB 2.0 on
my MSI KM4M mobo--VIA chipset.)  I don't even have the old /dev/sda device I
used to.  When I look at /var/log/messages and grep for "usb" I see nasty
things like "device not accepting address x, error = -110" and "control
timeout on ep0out".  See these four all four possible addresses on the bus.

So I've taken a giant step backward with the new kernel, but I can take
comfort in the knowledge that everything now runs a little bit SLOWER than
it did on SuSE 8.2!!!!!  If this is progress, get me back my punch cards...

Anyhow, I think I'm missing a module or something, altho I see messages for
the "uhci" driver in the log, so I think I've got the USB2 stuff going.
BTW, the drive was ON and plugged in during install, and subsequent power
off/on, switching USB port, and reboots have had no effect.  It just can't
see this drive any more.  Any ideas?

TIA,
Paul

2. I Need Networking Reference Material

3. VPN Client on Suse 9.2

4. New hard disk - How to copy existing system over?

5. AttributeType not found: "gidNumber" errormessage - Openldap + samba + Suse 9.2

6. lilo.conf used from where?

7. NOT working: HP NX5000 w/Wireless card: Atheros ar5212 & SuSE 9.2

8. Please Help! - Stupid newbie question

9. Realtek8139 problem under SuSE 9.2

10. Will Suse 9.2 or 9.3 run on AMD Athlon 64 X2 (dual core)?

11. Router connection problem - SuSE 9.2

12. Problems with kppp dialer in SUSE 9.2

13. Samsung Clp-510 on Suse 9.2.