Bingo: Lucent v.92 dualchipset hardw modem now works great!

Discussion regarding the installation and configuration of Linux distributions.

Bingo: Lucent v.92 dualchipset hardw modem now works great!

Postby outstream » Wed Sep 24, 2003 10:23 pm

Hi guys
I am just a newbie here and on Linux platform having only 2 days experience.I have a bit of problem going on here I hope you people would give a little time to suggest me some solution.
I have installed Red Hat linux 9 and I am having difficulties in
installing my modem, initially when i installed red hat linux 9 i had
intel modem with ambient chipset but then two days later i replaced
it with Lucent v.92 dual chipset hardware modem, after installing the
modem in slot when i restarted computer, linux detected hardware
changes and it said something like "Lucent modem found" and then it
asked me do i want to configure my new Lucent modem, i said yes
configure it and it did the job, now the problem is when i try to
configure internet connection wizard in GNOME, on probing modem, it
fails it and says no modem found on your system, then i tried to run
minicom and checked if its configured, after ending minicom setting
when i ran minicom terminal, it wasnt working either, it wouldnt let
me type anything, i have this red hat book and it says in minicom
termial type AT press return and if it responds like OK this means
modem is configured successfully.
so guys these r the details of my problem.
I would be really greatful if i get any suggestions from any one who
has ever set up Lucent v.92 dual chipset hardware modem or any one
who can suggest any solutions to my problem.
Thanks for your precious time
Testing?What's that? If it compiles, its good, if it boots up it is perfect.
----------------------------------------------------
Imran
Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby outstream » Thu Sep 25, 2003 10:09 pm

Dear LinuxFreaK sir
w.salam
I am not sure I got u properly, what did you mean by contact Dr.Modem @ farhanksa ..I mean whats is that actually? an email address? is it like Dr.Modem @ farhanksa .com or Dr.Modem @ farhanksa .net or what?
I would really apprectiate if u give some of ur precious time to reply my message
Thanks
Best regards
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby farhanksa » Fri Sep 26, 2003 1:31 am

aoa
1.first choice should be external modem...
2.isa modem with jumpers for comport sertting
3.pci lucent mdoem.....

sir ur modem in basically a win-modem.. although its called hardmodem.
as u said that u r using rh9 and its default kernel is 2.4.20-9(not sure) and surely ur modem is pci modem....
to see kernel version use the cmd
uname -a
also try to post if u r not done with modem configuration after this post..output of the following cmds

lspci
lspci -v -v
scanpci
uname -a
cat /proc/pci
lsdev




also plss tell me did u install teh kernel source and development kit???e.g libraries..and gcc compiler?

unluckily we r now available the rpm for rh9 so u need to do bit more work...by downloading the zipped source code and compile it..
download source code from http://www.physcip.uni-stuttgart.de/heb ... 6a9.tar.gz
u need to have kernel source...libraries and compiler installed to work with that

Login as root.

gunzip filedownloaded.tar.gz

tar -xvf filedownloaded.tar

cd filedownloaded-directory

make install



good luck...
farhanksa
Subedar
 
Posts: 359
Joined: Sun Nov 03, 2002 6:40 am
ICQ: 116765501
WLM: farhan12@msn.com
Yahoo Messenger: commdsl@yahoo.com
Location: Lahore

Postby outstream » Fri Sep 26, 2003 12:09 pm

w.sakam sir farhanksa

sir ji I didnt know that my modem is a winmodem, i bought what i saw and on that box it was written "hardware modem". Yes I installed devlopment kit and gcc compiler.
I tried all those commands that u told me and u asked for output, so here it is:

[root@localhost root]# uname -a
Linux localhost.localdomain 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux
[root@localhost root]# ispci
bash: ispci: command not found
[root@localhost root]# ispci -v-v
bash: ispci: command not found
[root@localhost root]# ispci -v -v
bash: ispci: command not found
[root@localhost root]# scanpci

pci bus 0x0000 cardnum 0x00 function 0x00: vendor 0x1106 device 0x0601
VIA Technologies, Inc. VT8601 [Apollo ProMedia]

pci bus 0x0000 cardnum 0x01 function 0x00: vendor 0x1106 device 0x8601
VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]

pci bus 0x0000 cardnum 0x07 function 0x00: vendor 0x1106 device 0x0686
VIA Technologies, Inc. VT82C686 [Apollo Super South]

pci bus 0x0000 cardnum 0x07 function 0x01: vendor 0x1106 device 0x0571
VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE

pci bus 0x0000 cardnum 0x07 function 0x02: vendor 0x1106 device 0x3038
VIA Technologies, Inc. USB

pci bus 0x0000 cardnum 0x07 function 0x03: vendor 0x1106 device 0x3038
VIA Technologies, Inc. USB

pci bus 0x0000 cardnum 0x07 function 0x04: vendor 0x1106 device 0x3057
VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]

pci bus 0x0000 cardnum 0x07 function 0x05: vendor 0x1106 device 0x3058
VIA Technologies, Inc. VT82C686 AC97 Audio Controller

pci bus 0x0000 cardnum 0x09 function 0x00: vendor 0x109e device 0x036e
Brooktree Corporation Bt878 Video Capture

pci bus 0x0000 cardnum 0x09 function 0x01: vendor 0x109e device 0x0878
Brooktree Corporation Bt878 Audio Capture

pci bus 0x0000 cardnum 0x0a function 0x00: vendor 0x11c1 device 0x0440
Lucent Microelectronics 56k WinModem

pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1023 device 0x8500
Trident Microsystems CyberBlade/i1

root@localhost root]# cat /proc/pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 5).
Master Capable. Latency=8.
Prefetchable 32 bit memory at 0xe0000000 [0xe3ffffff].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP] (rev 0).
Master Capable. No bursts. Min Gnt=12.
Bus 0, device 7, function 0:
ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 64).
Bus 0, device 7, function 1:
IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 6).
Master Capable. Latency=32.
I/O at 0xd000 [0xd00f].
Bus 0, device 7, function 2:
USB Controller: VIA Technologies, Inc. USB (rev 26).
IRQ 9. Master Capable. Latency=32.
I/O at 0xd400 [0xd41f].
Bus 0, device 7, function 3:
USB Controller: VIA Technologies, Inc. USB (#2) (rev 26).
IRQ 9. Master Capable. Latency=32.
I/O at 0xd800 [0xd81f].
Bus 0, device 7, function 4:
Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 64).
IRQ 11.
Bus 0, device 7, function 5:
Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 80).
IRQ 5. I/O at 0xdc00 [0xdcff].
I/O at 0xe000 [0xe003]. I/O at 0xe400 [0xe403].
Bus 0, device 9, function 0:
Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 17).
IRQ 10.
Master Capable. Latency=32. Min Gnt=16.Max Lat=40. Prefetchable 32 bit memory at 0xe7000000 [0xe7000fff].
Bus 0, device 9, function 1:
Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 17).
IRQ 10.
Master Capable. Latency=32. Min Gnt=4.Max Lat=255. Prefetchable 32 bit memory at 0xe7001000 [0xe7001fff].
Bus 0, device 10, function 0:
Communication controller: Lucent Microelectronics 56k WinModem (rev 1).
IRQ 5.
Master Capable. No bursts. Min Gnt=252.Max Lat=14. Non-prefetchable 32 bit memory at 0xe7002000 [0xe70020ff].
I/O at 0xe800 [0xe807]. I/O at 0xec00 [0xecff].
Bus 1, device 0, function 0:
VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 106).
IRQ 11.
Master Capable. Latency=32.
Non-prefetchable 32 bit memory at 0xe5800000 [0xe5ffffff]. Non-prefetchable 32 bit memory at 0xe6000000 [0xe601ffff]. Non-prefetchable 32 bit memory at 0xe5000000 [0xe57fffff].

[root@localhost root]# isdev
bash: isdev: command not found
[root@localhost root]#

now let me brief u about devices in my system...the thing u saw as context capture..that is my web cam and the other thing is my tv tuner card...there is no ISA slot in my motherboard in which i can install the ISA modem, so yeah its PCI

I hope u get all what i wrote
Thanks for ur time and advance thanks in ur future suggestions about my problem
Good day
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

A correction

Postby barlas » Fri Sep 26, 2003 9:21 pm

AOA!

I am a newbie myself and dont know how to solve your problem, I just want to tell you that

lspci
lspci -v -v
lsdev

These commands starts with L not I. I think you should post your answer again with respect to these commands. It may help someone to solve your problem.
Aqeel Zafar
barlas
Naib Subedar
 
Posts: 315
Joined: Mon Jun 30, 2003 11:07 am
Website: http://aqeeliz.com
Location: Lahore, Pakistan

Postby outstream » Fri Sep 26, 2003 11:02 pm

aoa
thanks mr barlas sir
i didnt know those commands start with L not I, i think i`ll try em again and then post the output
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby outstream » Fri Sep 26, 2003 11:33 pm

AOA

okay yeah, i was wrong it wasnt 'I' in that command, it was 'L' and i tried it, herez the output

[root@localhost root]# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master
IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 1a)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio
Controller (rev 50)
00:09.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
00:09.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
00:0a.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01)
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a)
[root@localhost root]# lspci -v -v
00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05)
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 e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 2.0
Status: RQ=7 SBA+ 64bit- FW- Rate=x1,x2,x4
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>

00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia 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
Memory behind bridge: e4000000-e6ffffff
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:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
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:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master
IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. VT8235 Bus Master ATA133/100/66/33 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
Region 4: I/O ports at d000 [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:07.2 USB Controller: VIA Technologies, Inc. USB (rev 1a) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB 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 D routed to IRQ 9
Region 4: I/O ports at d400 [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:07.3 USB Controller: VIA Technologies, Inc. USB (rev 1a) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB 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 D routed to IRQ 9
Region 4: I/O ports at d800 [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:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
Subsystem: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
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 ? routed to IRQ 11
Capabilities: [68] 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:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio
Controller (rev 50)
Subsystem: VIA Technologies, Inc. VT82C686 AC97 Audio 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 C routed to IRQ 5
Region 0: I/O ports at dc00 [size=256]
Region 1: I/O ports at e000 [size=4]
Region 2: I/O ports at e400 [size=4]
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:09.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
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 (4000ns min, 10000ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at e7000000 (32-bit, prefetchable) [size=4K]
Capabilities: [44] Vital Product Data
Capabilities: [4c] 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:09.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
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 (1000ns min, 63750ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at e7001000 (32-bit, prefetchable) [size=4K]
Capabilities: [44] Vital Product Data
Capabilities: [4c] 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:0a.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01)
Subsystem: Lucent Microelectronics LT WinModem 56k Data+Fax+Voice+Dsvd
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 5
Region 0: Memory at e7002000 (32-bit, non-prefetchable) [size=256]
Region 1: I/O ports at e800 [size=8]
Region 2: I/O ports at ec00 [size=256]
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-
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a) (prog-if 00 [VGA])
Subsystem: Trident Microsystems CyberBlade/i1
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 11
Region 0: Memory at e5800000 (32-bit, non-prefetchable) [size=8M]
Region 1: Memory at e6000000 (32-bit, non-prefetchable) [size=128K]
Region 2: Memory at e5000000 (32-bit, non-prefetchable) [size=8M]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [80] AGP version 2.0
Status: RQ=32 SBA+ 64bit- FW- Rate=x1,x2,x4
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=<none>
Capabilities: [90] 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-

[root@localhost root]# lsdev
bash: lsdev: command not found


but lsdev didnt work
I`d be really greatful if u ppl give some views on this
Thanks
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby Faraz.Fazil » Sat Sep 27, 2003 10:40 am

First of all, if linux detects and configures your modem , it should work under normal circumstances.

So during the trouble shoot process, outstream, you have so far just did a hardware info probe and have not attempted to install the ltmodem driver manually.

Ok, now lets get back to the point, NOw the ltmodem driver is available in two forms:

1.(.tar.gz) (Check farhan's post for link)
2.RPM format (check the last part of this post to get the download location)

Now, installing using the rpm method is recommended coz, it will take very less time compared to installing from sources.Also in sources case, you will need to install the full (and configured) kernel source, only the kernel headers are not enough.This is not the case in rpm case, where u just have to install the rpm using rpm -Uvh command

So do this:

1.Download this rpm:

http://www.physcip.uni-stuttgart.de/heb ... 1.i386.rpm

(Note: there are different versions of this driver for different kernels)
Since you are running redhat 9 which has default 2.4.20-8 kernel therefore i have given u the link to download the driver for that kernel.If u have a different kernel, mention it to me and ill give u the download link for your kernel version.)

2.INstall the rpm using rpm -Uvh rpmname.rpm command.

3.Configure your modem and connections.

Also which dialup tool did u use?
I recommend KPPP or redhat-config-network.
Faraz.Fazil
Major General
 
Posts: 1024
Joined: Thu Jul 04, 2002 5:31 pm
WLM: faraz7476@hotmail.com
Location: Karachi/Pakistan/Earth/Universe

Postby outstream » Sat Sep 27, 2003 3:32 pm

AoA

thanks for ur reply Faraz.Fazil Sir

ok I did it all and I think it did install the modem, cuz it told me that it has done it to /dev/ttyLT0 or a symbolic link of which is /dev/modem...fine done...but again things are messing up...i think u`ll get a better idea of an extension problem of the original problem if i show u the output
so here it is

root@localhost root]# rpm -Uvh ltmodem-kv_2.4.20_20.8-8.26a9-1.i386.rpm
Preparing... ########################################### [100%]
1:ltmodem-kv_2.4.20_20.8 ########################################### [100%]
Diagnostic information is being written to /usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9/LTinstall.txt

A supported Lucent/Agere DSP chipset modem is identified: PCI_ID=11c1:0440
VENDOR 0x11c1 DEVICE 0x0440
ID are within the serviced ranges for Lucent/Agere DSP modems:
------------------------------------------
LUCENT 0x11c1 0x0440-0x045c
XIRCOM 0x115d 0x0000-0x000F
XIRCOM 0x115d 0x0440-0x045c
XIRCOM 0x115d 0x0010-0x03ff
-------------------------------------------
Drivers and their compiler kits are available at:
http://www.heby.de/ltmodem/

For more details read the Recording file.

redhat

scanmodem finished, proceeding with autoload section


Made modem device node /dev/ttyLT0
group ownership set to uucp
with symbolic link /dev/modem --> /dev/ttyLT0
Writing modules autoloading lines to /etc/modules.conf:
Using /sbin/depmod
Updating with: /sbin/depmod -a
Capturing output to /tmp/ltmodem/tmpfile and parsing.

Your system is lacking Default lines in /etc/modules.conf
which are usually needed to support the modem communications protocol PPP.
Some modem installations replace these Defaults
with lines specific to particular modem hardware.
There may be problems using the Lucent/Agere modem without these Default lines. The suspect lines are:
------------------------------
cat /tmp/ltmodem/tmpfile
------------------------------
and are being inserted in /usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9/LTinstall.txt for your judgement.
Should you insert them in /etc/modules.conf, inform the System with
/sbin/depmod -a


The modem drivers dependencies are properly resolved.



A folder has been installed in your Systems documentation,
/usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9
containing much useful guidance and uilities. Updates can be
downloaded from http://www.heby.de/ltmodem/ as DOCs.tgz

To get online, the Port to be specified in your dialout scripts is:
/dev/ttyLT0 or its symbolic, /dev/modem
A summary of installation actions with Advice is contained in: /usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9/LTinstall.txt

Browse DOCs/Ltmodem.html for issues that may be relevant to your system and useful URLs
Also see DOCs/LastAdvice
Some dialer utilities including KPPP require that Each User set up a configuration,
as there could be diverse configurations on multi-User systems.

Read DOCs/wvdial.txt for aid in configuring the smart dialup utility, WVDIAL

Otherwise, get Online and Enjoy
Relate problems to discuss@linmodems.org
Gratitude too, to discuss@linmodems.org


If not familar with the ltmodem drivers, run the interactive CHECKOUT utility by executing:
/usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9/utils/checkout


okay after this when i ran kppp, made connection there and after that when i clicked device tab and tried to query modem, it said "unable to open the modem". Then i went to redhat.com and browsed their documentation on rh9, there i found something on installing rpms, a command was told "rpm -q filename" to check if the package is installed, I tried it and here is the output



[root@localhost root]# rpm -q ltmodem-kv_2.4.20_20.8-8.26a9-1.i386.rpm
package ltmodem-kv_2.4.20_20.8-8.26a9-1.i386.rpm is not installed

[root@localhost root]# rpm -q ltmodem-kv_2.4.20_20.8-8.26a9-1.i386
package ltmodem-kv_2.4.20_20.8-8.26a9-1.i386 is not installed

[root@localhost root]# rpm -q ltmodem-kv_2.4.20_20.8-8.26a9-1
ltmodem-kv_2.4.20_20.8-8.26a9-1


now here it seems on the third command it worked and told package is there, but still its saying "unable to open the modem" when i try to use kppp. the one suggestion that i can make myself is , as u guys can also see from the output of the command where i tried to install the package, on one point it told me that some default lines are lacking and i may have to insert them manually to /etc/modules.conf.

I am not sure if my judjment is right here, if I am right could you please guide me how to insert those lines in /etc/modules.conf
I am really looking for guidelines from u guys
Thanks for your precious time
Good day.
Imran
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby Faraz.Fazil » Sat Sep 27, 2003 9:45 pm

Hmm..

It appears that your modem driver has been installed and configured correctly, but now a problem relating to the Point to POint (PPP) protocol is occuring.

To access the internet through a modem, u need the modem driver installed and you also require PPP to be supported and configured in the running kernel.

PPP support is available in two forms.It can be built right into the kernel or it can be in the form of modules which can be loaded or unloaded on the fly using /etc/modules.conf

By default most kernel's on most distros have PPP support, either built in or in the form of modules.

Verify that your kernel supports the PPP.
Also check if it is in the form of modules or if it is built into the kernel.

It may well be that since you changed the modem. the previous modem required ppp support built into the kernel, and during the redhat install it would have had the PPP suport builtin and it may be that your new lucent modem may require and support PPP only when PPP support is included in the form of modules.Modems like the SM56K also work only if PPP support is avilable in the form of modules.
It may also be that you existing kernel doesnot have any ppp support at all...although the chances are less.

If you kernel does not have ppp support or if nothing works, you may have to recompile your kernel and include PPP support in the form of modules...

But before that, and as a first step, p

Post the contents of the file: /usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9/LTinstall.txt

and also post the contents of your /etc/modules.conf file

Also try running the kudzu utility at this point in terminal to see if it does anything.
Also this time do create a connection with kppp and try connecting instead of just querying the modem
Faraz.Fazil
Major General
 
Posts: 1024
Joined: Thu Jul 04, 2002 5:31 pm
WLM: faraz7476@hotmail.com
Location: Karachi/Pakistan/Earth/Universe

Postby outstream » Sun Sep 28, 2003 12:52 am

AoA

mr Faraz.Fazil sir
actually i dont know how to check it if my kernel supports ppp as built in or as in modules, i am using rh9 and i think its same for all distroz of rh9, right? but i did open those both files that u said, here are the contents of

/usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9/LTinstall.txt



If you cannot resolve the problems, please send /usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9/LTinstall.txt to discuss@linmodems.org with Subject: LTinstallRPM
RECORD=/usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9/LTinstall.txt
Linux localhost.localdomain 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux
PWD=/
ENVIR=rpm
INSTALLER=/var/tmp/rpm-tmp.65524 1
TMPM=/tmp/ltmodem/tmpfile
FAST=1
LT_VERSION=8.26a9
TARGET_VERSION=2.4.20-20.8
TARGET_CPU=i686
SYSTEM_CPU=i686
GCC_DRIVERS=3
GCC_NOW=3.2.2
GCC_KERNEL=3
------------ beginning SCANMODEM section ------
If further help is needed, send a description of your problem to: discuss@linmodems.org
with this ModemData.txt Attached.
using the following in the email Subject Line:
scanmodem, redhat kernel 2.4.20-8

System info follows
==================================================
redhat Red Hat Linux release 9 (Shrike)
Script executed as: scanmodem
on system: Linux localhost.localdomain 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux
LSPCI=/sbin/lspci
UPDATE=2002 Nov 13
--------- lspci scan ----------------
00:00.0 Host bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia] (rev 05)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8601 [Apollo ProMedia AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 1a)
00:07.3 USB Controller: VIA Technologies, Inc. USB (rev 1a)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50)
00:09.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
00:09.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
00:0a.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01)
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i1 (rev 6a)
-------------------------------------
Reading more detail for the Device at:
PCI bus
-------
00:0a.0 Class 0780: 11c1:0440 (rev 01)
Subsystem 11c1:0440
00:0a.0 Communication controller: Lucent Microelectronics 56k WinModem (rev 01)
Subsystem: Lucent Microelectronics LT WinModem 56k Data+Fax+Voice+Dsvd
Flags: bus master, medium devsel, latency 0, IRQ 5
Memory at e7002000 (32-bit, non-prefetchable) [size=256]
I/O ports at e800 [size=8]
I/O ports at ec00 [size=256]
Capabilities: [f8] Power Management version 2

-------------------------------------------------------
11c1:0440 PCI bus PCI_ID with vendor component: 11c1
11c1:0440 and Subsystem PCI_ID with vendor: 11c1
-------------------------------------------------------
are key Sought Descriptions of your modem firmware.
Have them ready when visiting URLs with service software!!
For soft modems in AC'97 controller slots, the bus PCI_ID describes the Controller
and the Subsystem PCI_ID the modem card inserted into it. A soft modem chipset
must be determined (guessed ?) to guide the choice of driver resources.

It may be useful to download http://www.yourvote.com/pci/vendors.txt
and search it for vendor with and without caps, for example: both 114d and 114D
------------------------------------------------------------------------------------

DSP=1

A supported Lucent/Agere DSP chipset modem is identified: PCI_ID=11c1:0440
VENDOR 0x11c1 DEVICE 0x0440
ID are within the serviced ranges for Lucent/Agere DSP modems:
------------------------------------------
LUCENT 0x11c1 0x0440-0x045c
XIRCOM 0x115d 0x0000-0x000F
XIRCOM 0x115d 0x0440-0x045c
XIRCOM 0x115d 0x0010-0x03ff
-------------------------------------------
Drivers and their compiler kits are available at:
http://www.heby.de/ltmodem/

Checking primary Vendor=11c1 through major modem chipset Vendors

Vendor=11c1 corresponds to Lucent Technologies or subsidiary Agere Systems, Inc.
Information is at: http://www.agere.com/support/client/modem_drivers.html
but without any relevant to Linux.

Checking Subsystem Vendor=11c1 through major modem chipset Vendors

Vendor=11c1 corresponds to Lucent Technologies or subsidiary Agere Systems, Inc.
Information is at: http://www.agere.com/support/client/modem_drivers.html
but without any relevant to Linux.


0x0440 -- Mars 2 - data/fax/voice
Get Lucent/Agere information at:
http://www.agere.com/support/client/modem_drivers.html

The desired installer name is like:
========================================
ltmodem-kv-2.4.20_8-8.22a5-1.i686.rpm
----------------------------------------
ltmodem-kv-Kernel_FL-LTver--.CPU.rpm explains the versioning.
LTver 8.22a5 is the release of the resource
used in compiling and assembling driver packages.
8.22 is the Agere core code designation.

A suitable installer is not available as of this 2002 Nov 13 update.
Check in the section redhat at http://www.heby.de/ltmodem
for a subsequent Installer submission.
If not present use the ltmodem-8.22a5.tar.gz compiler kit.

The list of available Installers for redhat
is inserted into to /usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9/LTinstall.txt.2
GCCversion=3.2.2

The following information blocks just query some ppp support items.
====================================================================
grep ppp /etc/modules.conf
--------------------------------
--------------------------------
DEVPPP=crw------- 1 root root 108, 0 Jan 30 2003 /dev/ppp
DEVFS=
DEVFSD=

-------------- ending SCANMODEM section ----------------
DEVFS=
DEV_MODEM_LINK_ORIG=
DEVICE_NODE=/dev/ttyLT0
SYM_LINK1=/dev/modem
With permissions to group: dialout

MCFILE=/etc/modules.conf

UPDATE_MOD=/sbin/depmod -a

Your system is lacking Default lines in /etc/modules.conf
which are usually needed to support the modem communications protocol PPP.
Some modem installations replace these Defaults
with lines specific to particular modem hardware.
There may be problems using the Lucent/Agere modem without these Default lines.
The suspect lines are:

------------------------------
cat /tmp/ltmodem/tmpfile
------------------------------
and are being inserted in /usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9/LTinstall.txt for your judgement.
Should you insert them in /etc/modules.conf, inform the System with
/sbin/depmod -a

DEPMOD_A=passed
The following block has been written to /etc/modules.conf:
/etc/modules.conf
# lt_drivers: autoloading and insertion parameter usage
alias char-major-62 lt_serial
alias /dev/tts/LT0 lt_serial
alias /dev/modem lt_serial
# The next two lines are syntax examples, only Rarely Needed, to automate parameter usage during lt_drivers insertion. See documentation for details.
# options lt_modem vendor_id=0x115d device_id=0x0420
# options lt_modem Forced=3,0x130,0x2f8,0
# section for lt_drivers ends


Please browse /usr/share/doc/ltmodem-kv_2.4.20_20.8-8.26a9 to benefit from DOCs/ and utils/ therein



and here are the contents of /etc/modules.conf


alias char-major-81 bttv
alias usb-controller usb-uhci
alias sound-slot-0 via82cxxx_audio
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :


# lt_drivers: autoloading and insertion parameter usage
alias char-major-62 lt_serial
alias /dev/tts/LT0 lt_serial
alias /dev/modem lt_serial
# The next two lines are syntax examples, only Rarely Needed, to automate parameter usage during lt_drivers insertion. See documentation for details.
# options lt_modem vendor_id=0x115d device_id=0x0420
# options lt_modem Forced=3,0x130,0x2f8,0
# section for lt_drivers ends


and as u said, this time i didnt query modem, i just made a connection and tried to dial but right after pressing the dial button there, it said same "unable to open the modem", in kppp.
i`ll be waiting for ur suggestions
thanks for ur precious time
Good day
Imran
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby farhanksa » Sun Sep 28, 2003 12:55 am

aoa

sir just keep in mind that u need to change the /dev/ttyso from the kppp tab to /dev/modem if its linked by the driver u instaled.....or link it urself by
ln /dev/ttylt?? /dev/modem

change it to /dev/modem then try to query modem........if it kept u hold for 2 sec then guess that its worked........other wise it suddenly gives msg that modem not present......
farhanksa
Subedar
 
Posts: 359
Joined: Sun Nov 03, 2002 6:40 am
ICQ: 116765501
WLM: farhan12@msn.com
Yahoo Messenger: commdsl@yahoo.com
Location: Lahore

Postby outstream » Sun Sep 28, 2003 2:16 am

Aoa
sir farhanksa

in kppp, bu default it is /dev/modem, and yeah u r right, it doesnt gets me hold..just after pressing the dial buttton, in a blink of an eye it tells me "unable to open the modem"

thanks for ur precious time
Good day
Imran
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby outstream » Mon Sep 29, 2003 5:07 pm

some one please reply me?
linuxfreek, farhanksa..any one?
Testing?What's that? If it compiles, its good, if it boots up it is perfect.

----------------------------------------------------

Imran

Registered Linux User # 334322
outstream
Naib Subedar
 
Posts: 322
Joined: Wed Sep 24, 2003 10:04 pm
Location: islamabad

Postby Faraz.Fazil » Mon Sep 29, 2003 6:51 pm

Sorry for late reply ...but i was out for a one day vacation hehe.

Anywayz, i read those files.

First of all, it becomes pretty sure , that at this point the problem is not with the modem driver.INstead the problem is that your modem would work under linux only, if you include support for ppp in the form of modules.This is not surprising.Even modems like sm56 work only when ppp is in modules.

Now the /etc/modules.conf of yours indicates that either ppp is currently built directly into the kernel or it is not supported/configured at all, but is not in modules.Also by default ppp support in redhat 9,in most cases, is built into the kernel.

Therefore you need to recompile your kernel and include support for PPP and all related stuff to PPP in modules form...which will be loaded from /etc/modules.conf

I have already created a detailed step by step guide on how to recompile the kernel and what options you have.In your case, you are bound to use the source method i.e the one in which u download the .tar.gz file from kernel.org and recompile the kernel using the make commands.Check my post in the last part of the thread mentioned below for detailed instructions:

http://www.linuxpakistan.net/forum2x/vi ... highlight=

(check my post in last part)

I will be creating a seperate thread with that guide very soon

Beleive me getting this modem to work would not be a big problem..but will indeed require some efforts and patience on your side.
All you need to do is recompile to the latest 2.4.22 kernel available at kernel.org and include ppp support in module form.

You may try to catch me on msn at: faraz7476@hotmail.com if u have any trouble.

Good luck!
Faraz.Fazil
Major General
 
Posts: 1024
Joined: Thu Jul 04, 2002 5:31 pm
WLM: faraz7476@hotmail.com
Location: Karachi/Pakistan/Earth/Universe


Return to “%s” Installation

Who is online

Users browsing this forum: Bing [Bot] and 1 guest

cron