My first post here. My main development machine has been running Libranet 2.7 (Debian 2.4.19) for many months now. Just the other day, I finally got the usr pci internal 56k modem running. A day and a half later, the machine hung. After reviewing the logs, the only thing of importance was 'modprobe' complaining about the usb drivers. Here is an 'lspci -vv' output:

00:00.0 Host bridge: VIA Technologies, Inc. VT8367 [KT266]
Subsystem: ABIT Computer Corp.: Unknown device 7405
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: 8
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW- Rate=x1,x2
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
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. VT8367 [KT266 AGP] (prog-if 00 [Normal decode])
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
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: ec000000-edffffff
Prefetchable memory behind bridge: e0000000-e7ffffff
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:0b.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550])
Subsystem: US Robotics/3Com USR 56k Internal Voice Modem (Model 2976)
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 A routed to IRQ 5
Region 0: I/O ports at d000 [size=8]
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=2 PME-

00:0f.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink] (rev 78)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC
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 (2500ns min, 2500ns max), cache line size 08
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at d400 [size=128]
Region 1: Memory at ef000000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at <unassigned> [disabled] [size=128K]
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=2 PME-

00:11.0 ISA bridge: VIA Technologies, Inc.: Unknown device 3147
Subsystem: VIA Technologies, Inc.: Unknown device 3147
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
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. Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. Bus Master IDE
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
Interrupt: pin A routed to IRQ 0
Region 4: I/O ports at d800 [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.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 23) (prog-if 00 [UHCI])
Subsystem: ABIT Computer Corp.: Unknown device 7405
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 D routed to IRQ 5
Region 4: I/O ports at dc00 [size=32]
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:11.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 23) (prog-if 00 [UHCI])
Subsystem: ABIT Computer Corp.: Unknown device 7405
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 D routed to IRQ 5
Region 4: I/O ports at e000 [size=32]
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-

01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 514c (prog-if 00 [VGA])
Subsystem: Unknown device 174b:7149
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 (2000ns min), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at c000 [size=256]
Region 2: Memory at ed000000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [58] AGP version 2.0
Status: RQ=47 SBA+ 64bit- FW+ Rate=x1,x2
Command: RQ=0 SBA+ AGP- 64bit- FW- Rate=<none>
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-

According to the above output, there is a conflict between the usb controller and the internal modem.

Ideally, I would like to change the irq on the internal modem from 5 to 12. That would clear up the problem.

The machine in question only runs Linux. How can I change the irq on this modem? Usr's website makes no mention of Linux. All utilties are win.

I have consider using 'setpci' but I don't know the proper register name(s) for this pci internal modem.

Please help.
rick

oh werd, i need same help

An update. The same machine hung after running for about 22hrs.

After looking at some related posts about irq conflicts. I figured that the output from '/proc/interrupts' might be a good idea. Here it is:

CPU0
0: 48585 XT-PIC timer
1: 1139 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 0 XT-PIC serial
5: 9382 XT-PIC usb-uhci, usb-uhci, serial
8: 3 XT-PIC rtc
10: 119 XT-PIC eth0
12: 8928 XT-PIC PS/2 Mouse
14: 10466 XT-PIC ide0
15: 10 XT-PIC ide1
NMI: 0
ERR: 0

This snapshot was taken with 'ppp' active and within X-Windows. The mouse is on irq 12 so I guess I'll have to change my target irq to 13.

Thanks in advance for your help.
rick

how do you change the irq bro?

That is exactly what I am trying to find out. According to my research, changing the IRQ on a PCI card involves changing one or more of the register contents in the card itself. In Linux, this is done using 'setpci'. However, you must know the register name to change (which varies from card to card) and the length of the register itself (byte, word, long word).

I do not want to take a chance poking around (there is a term I have not heard or used in some time) in the card without knowing exactly what I am doing.

If the machine in question had a Win partition, I would simply install the utilities from usr and change the IRQ. I thought of booting from a DOS disk but the only utilities available are Win graphical so you cannot even boot Win98 into a console.

The machine in question has become completly unstable and I have shut it down until this issue is resolved.

rick

i have a windows partition, how do i change the irqs in windows?

If you have a Win partition and can boot into it, thats great.

Find the model number for your modem. If your like me and bought an OEM version, you will have a hard time finding this. This model number is one usr's uses internally. If you cannot find the model number according to usr, first download the product number locator program (Win) from www.usr.com and run it.

Once you have the model number download the entrie program suite for that modem. There should be a configuration utility in that suite of programs. This program will allow you to change the irq and i/o port used. Once this change has been made, Linux will recognize the change on next boot.

What a pain in you know where. I can now see why so many people tell us to get an external modem.

rick

Or you can find the specific model searching for the FCC ID

http://www.fcc.gov/oet/fccid/

Or you can simple change the IRQ interrupt at bios

I did not realize that you can change the IRQ used at the bios level. Can this be done without changing anything in modem card itself?

Read this:

http://www.scyld.com/expert/irq-conflict.html

http://www.turtlebeach.com/site/kb_ftp/5304008.asp

Nicely done angelrod.

I read both pages and will attempt to change the irq of the modem asap.

I hope that h1tman also got the message.