| View previous topic :: View next topic |
| Author |
Message |
edcjones
n00b
Joined: 04 Jul 2002
Posts: 60
|
 Posted: Fri Mar 21, 2003 1:56 am Post subject: A tale of two modems, one of which works |
 |
|
I started with a AMD Thunderbird 1G system with Gentoo 1.3 on it and vanilla 2.4.20 sources. It had a 33K modem and all worked well.
The motherboard in this machine died of oozing capacitors. It took the memory with it. Replaced them. I have since decided that the CPU became slightly flaky. Other hardware OK.
I bought a new V92 hardware ISA modem. I had problems installing it. The problem turned out to be some IRQ conflict. Disabling COM1 and COM2 fixed it. Now I had a machine I could put either modem in.
I built myself a new PC with an AMD XP-2000+ and an Asus A7V333 motherboard. It has a PCI hardware modem. I moved the hard drive with the Gentoo on it to the new machine. It worked!! Almost. Couldn't find the modem.
Put the hard drive back into the old machine. In the old machine, KPPP couldn't find the v92 modem. "dmesg" shows
| Quote: | devfs_register(1): could not append to parent, err: -17
devfs_register(a1): could not append to parent, err: -17
spurious 8259A interrupt: IRQ7. |
The devices "ttyS0", etc didn't even exist (I have devfs). The 33K modem stills works. Disabled the parallel port in the BIOS. Didn't help.
Google and Gentoo searches resulted in too many hits. I looked at a number of them, but I couldn't tell which might be useful.
Any idea what might be wrong? |
|
| Back to top |
|
 |
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
| Posted: Fri Mar 21, 2003 5:14 am Post subject: |
|
|
| precisely what kind of modem is it. There are a large class of ``modems'' that do not work with linux (although support has gotten better). What does /proc/pci tell you about the device? |
|
| Back to top |
|
|
edcjones
n00b
Joined: 04 Jul 2002
Posts: 60
|
| Posted: Fri Mar 21, 2003 2:00 pm Post subject: |
|
|
The oldest modem that always works is a "Zoltrix FM-335I ACF". It is a 33.6K ISA modem.
The newer ISA modem is a "Best Data 56SF-92" internal V.92 modem. In the past it has worked well with Gentoo.
The modem I bought for the new machine is an "Actiontec PCIV92212-01CW" V.90 / V.92 "controller-based" modem. The box says "Operating System- DOS, Windows 3.1, 95, 98, NT 4.0, ME, 2000, OS/2, and Linux". |
|
| Back to top |
|
|
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
| Posted: Fri Mar 21, 2003 2:15 pm Post subject: |
|
|
| Well that product seems to no longer be sold according to the actiontec website (all they have are standard winmodems). But what does /proc/pci say? |
|
| Back to top |
|
|
edcjones
n00b
Joined: 04 Jul 2002
Posts: 60
|
| Posted: Fri Mar 21, 2003 4:30 pm Post subject: |
|
|
Part of lspci -vv:
| Quote: | 00:0e.0 Communication controller: Lucent Microelectronics Venus Modem (V90, 56KFlex)
Subsystem: Actiontec Electronics Inc: Unknown device 0500
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 (63000ns min, 3500ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at db000000 (32-bit, non-prefetchable) [size=256]
Region 1: I/O ports at b800 [size=256]
Region 2: I/O ports at b400 [size=256]
Region 3: I/O ports at b000 [size=8]
Capabilities: [f8] 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- |
wvdialconf says:
| Quote: | ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 4800 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 4800 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 19200 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 19200 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 4800 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 4800 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 19200 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 19200 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS4<*1>: ATQ0 V1 E1 -- OK
ttyS4<*1>: ATQ0 V1 E1 Z -- OK
ttyS4<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyS4<*1>: Modem Identifier: ATI -- AEIGPM560LKTF1 Voice V2 V92cap
ttyS4<*1>: Speed 4800: AT -- OK
ttyS4<*1>: Speed 9600: AT -- OK
ttyS4<*1>: Speed 19200: AT -- OK
ttyS4<*1>: Speed 38400: AT -- OK
ttyS4<*1>: Speed 57600: AT -- OK
ttyS4<*1>: Speed 115200: AT -- OK
ttyS4<*1>: Max speed is 115200; that should be safe.
ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttyS4.
conf<Warn>: Can't read config file conf: No such file or directory
Modem configuration written to conf.
ttyS4<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" |
KPPP doesn't know about /dev/ttyS4. I did
| Code: | | ln -s /dev/ttyS4 /dev/modem |
and the modem now works! This is not a good solution. I am now looking for a
better way to do this.
Note: The hardware in my old machine was very flaky today. Right now I can't
trust anything it says about modems (although the 33K modem still works). |
|
| Back to top |
|
|
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
| Posted: Fri Mar 21, 2003 7:50 pm Post subject: |
|
|
| Why is using the symlink not a good think to do? I think that is exactly what you should do. Perhaps you could have devfsd set up to make the link but as long as it works and you now have a modem device I woul stick with what you have. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
