Linux and Lucent LT WinModem

[eBopBob 0]

Hey folks,

 

http://www.linuxcompatible.org/cdetail10291.html

 

I've just purchased SuSE Linux 9.1 Professional because I heard it came with plenty of WinModem drivers, and also came with a Lucent LT WinModem driver (driver version 9)...

 

That page only lists Mandrake 8.2 as being compatible.

 

Does anyone know if SuSE 9.1 Pro works with this modem or not?

If not, which does? I'm hoping to get the modem working without much hassle. I know that Knoppix 3.2 I think it was cannot pick up my modem.

 

Thanks all.

[Dapper Dan 0]

Hello eBopBob,

 

There comes that point to where you have to just dive in and see. Let us know what happens. Good luck.

[SoulNothing 0]

hey eBopBob i have a lucentwin modem as well all my tries havent worked but then again i stopped once i got cable but please share your results so i can use it thanks

[eBopBob 0]

hehe, so it seems no one has got it working yet?

I've also asked on plenty of other forums, and nothing, and various Linux IRC chats; still nothing.

 

I'll have it either tomorrow (thursday) or friday; then I'll install it (but make dual boot for windows in case the modem doesn't work, and never works) and see whether it picks it up or not. I'm really hoping it does pick it up as I know it comes with drivers for a Lucent LT WinModem; but are all the LT WinModems the same? Didn't they make different ones? I know on the Lucent page it says "Generic Driver" for all of 'em rather than giving a specific driver for each one, just hope the generic driver that comes with SuSE will work with mine... guess I'll have to wait and see.

 

After I get it, and install it, I'll let you guys know whether it picks it up automatically. Even if it doesn't, hopefully I'll be able to get it working after doing some things 'ere and there.

 

Wish me luck!

[Dapper Dan 0]

Chances are Suse will recognize it, but whether or not it will have a "driver" specific to it is a gamble. I think the only way to know for sure is just to try it.

 

Many of the hardware manufacturer's have gotten into the really sloppy habit of changing chipsets for a piece of hardware, and still giving the same model number in the sales information. So off you go, having done your homework, believing Bob's modem model A-1 will work with Linux.

 

After all, everything you read on the Internet says it will work. Then when you get the card, and it's actually a Bob's modem A-1(v2) using a different chipset than what will work with Linux.

 

If it won't work out and you have a little cash, I highly recommend the Actiontec external serial modem. It works out of the box, and the performance of it compared to most internal PCIs is noticeably better.

[eBopBob 0]

Hey there.

 

Thanks for your reply Dapper Dan. If I can't get the modem to work, I definitely will get that external modem; but I've hope it'll eventually work since I know now of five other people with same modem and it works for them.

 

I installed SuSE 9.1 Pro... everything went fine. It came to setting up my modem - I let it probe all me devices, and it detected my modem (and did it correctly; unlike for my monitor) and then said I must insert CD5 to install the ltmodem driver. So I did that - It start doing its stuff, and then it said all was detected and configured. Then it let my enter my dial-up number, username and password. Great I though - I really thought at this point it'd work just like that. It said my modem would be /dev/ttyLT0 so I left it as that; also read in a tutorial that it should be that.

 

 

I try to connect, and I get this

 

Quote:

SuSE Meta pppd (smpppd-ifcfg), Version 1.16 on linux.

 

Status is: disconnected

trying to connect to smpppd

connect to smpppd

Status is: disconnected

Status is: connecting

pppd[0]: Plugin passwordfd.so loaded.

pppd[0]: Failed to open /dev/ttyLT0: No such device or address

Status is: disconnecting

Status is: disconnected

pppd[0] died: Serial port open failed (exit code 7)

 

 

So, I go into /dev/ and look for ttyLT0 - It exists, yes. But it's 0b; meaning it's empty.

 

I try it with all the other options I have, which are:

Quote:

/dev/modem/

/dev/ACM0

/dev/ACM1

/dev/ACM2

/dev/ACM3

/dev/ttyS0

/dev/ttyS1

/dev/ttyS2

/dev/ttyS3

/dev/ttyLT0

 

I do "ls -l /dev/modem" and get "lrwxrwxrwx 1 root root 11 2004-08-01 17:56 /dev/modem -> /dev/ttyLT0"

 

 

Any help on this?

I'm thinking of re-installing SuSE and seeing if that'll help.

 

Thanks

[martouf 0]

do "ls -lL /dev/modem" or "ls -l /dev/ttyLT0" and post the output, please.

 

Note by adding the 'L' in the first command, you dereference the symbolic link

to show the (file)list ('ls') of the underlying device.

 

The second command is equivalent to the first, so just pick one and run it.

 

 

[eBopBob 0]

Hi there. Thanks for your reply.

 

ls -lL /dev/modem

crw-rw-r-- 1 root dialout 62, 64 2004-04-07 00:25 /dev/modem

 

ls -l /dev/ttyLT0

crw-rw-r-- 1 root dialout 62, 64 2004-04-07 00:25 /dev/ttyLT0

 

 

Some other person also suggested that I use wvdial, so I tried that out and got the following:

 

--> WvDial: Internet dialer version 1.54.0

--> Cannot open /dev/modem: No such device or address

--> Cannot open /dev/modem: No such device or address

--> Cannot open /dev/modem: No such device or address

 

 

 

But the thing is, I've been in the folder /dev/, and have seen that file. True, it contacts 0b meaning it is totally empty; but it's still there.

 

Any help is much appreciated.

[martouf 0]

according to this site, the Lucent LT modem drivers are initiated

with 'modprobe lt_serial' so both lt_modem and lt_serial are loaded.

 

do both of these kernel modules appear when you check using 'lsmod' ?

 

the device initiated by lt_serial is /dev/tts/LT0 not /dev/ttyLT0

 

the way to do a quick troubleshoot is to run 'minicom' and send some basic

AT commands to the modem - like, "AT<CR>" and "ATI4<CR>" where <CR> is the enter key.

 

you'll have to tell minicom which device name to use to connect to your modem.

try '/dev/ttyLT0' and '/dev/tts/LT0' before you try '/dev/modem'.

 

additionally, when you are starting up pppd or wvdial, are you doing so logged

in as an account belonging to the 'dialout' account group?

 

 

[eBopBob 0]

Hi there.

 

Thanks for your reply.

 

Quote:

linux:~ # modprobe lt_serial

FATAL: Module lt_serial not found.

linux:~ # modprobe ltserial

FATAL: Error inserting ltserial (/lib/modules/2.6.4-override-default/ltserial.ko): No such device

 

linux:~ # modprobe ltmodem

linux:~ # modprobe lt_modem

FATAL: Module lt_modem not found.

 

So, neither lt_serial nor lt_modem exist, however ltmodem does and it'd seem that ltserial does also, or may not. Not sure on that one to be honest.

 

 

Doing lsmod gives me the following. As you can see, only ltmodem is there however no ltserial, nor lt_serial. I'm guessing this is a bad sign, correct?

 

Quote:

linux:~ # lsmod

Module Size Used by

ppp_generic 28692 0

slhc 7424 1 ppp_generic

ltmodem 532720 0

usbserial 28912 0

parport_pc 35264 1

lp 10916 0

parport 37704 2 parport_pc,lp

edd 9240 0

joydev 10176 0

st 38940 0

sd_mod 19840 0

sr_mod 15652 0

scsi_mod 107980 3 st,sd_mod,sr_mod

ide_cd 36484 0

cdrom 36508 2 sr_mod,ide_cd

nvram 8328 0

snd_seq_oss 30976 0

snd_pcm_oss 56868 0

snd_mixer_oss 18688 1 snd_pcm_oss

snd_seq_midi 8864 0

snd_seq_midi_event 7680 2 snd_seq_oss,snd_seq_midi

snd_opl3_synth 16004 0

snd_seq_instr 7552 1 snd_opl3_synth

snd_seq_midi_emul 7680 1 snd_opl3_synth

snd_seq 54672 9 snd_seq_oss,snd_seq_midi,snd_seq_midi_event,snd_

opl3_synth,snd_seq_instr,snd_seq_midi_emul

snd_ainstr_fm 2816 1 snd_opl3_synth

processor 16040 0

snd_es1938 20772 4

snd_pcm 96776 2 snd_pcm_oss,snd_es1938

snd_page_alloc 11012 1 snd_pcm

snd_opl3_lib 10880 2 snd_opl3_synth,snd_es1938

speedstep_lib 3712 0

snd_timer 25476 3 snd_seq,snd_pcm,snd_opl3_lib

snd_hwdep 9732 1 snd_opl3_lib

gameport 4736 1 snd_es1938

snd_mpu401_uart 7808 1 snd_es1938

snd_rawmidi 24992 2 snd_seq_midi,snd_mpu401_uart

snd_seq_device 8328 6 snd_seq_oss,snd_seq_midi,snd_opl3_synth,snd_seq,

snd_opl3_lib,snd_rawmidi

snd 59524 26 snd_seq_oss,snd_pcm_oss,snd_mixer_oss,snd_seq_m

idi,snd_seq_midi_event,snd_opl3_synth,snd_seq_instr,snd_seq_midi_emul,snd_seq,sn

d_es1938,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidi,sn

d_seq_device

soundcore 8800 1 snd

freq_table 4612 0

ipt_TOS 2432 9

ipt_MASQUERADE 3584 1

ipt_LOG 5632 1

ipt_TCPMSS 4352 1

ipt_state 1920 12

hid 40640 0

uhci_hcd 29584 0

ds 17284 4

yenta_socket 15744 0

pcmcia_core 61636 2 ds,yenta_socket

intel_agp 17052 1

agpgart 28712 1 intel_agp

usbcore 96988 5 usbserial,hid,uhci_hcd

evdev 9600 0

ip6t_LOG 5504 2

ip6t_REJECT 7168 3

ip6table_mangle 2688 0

ipt_REJECT 6400 3

iptable_mangle 2816 1

iptable_filter 2816 1

ip_nat_ftp 4720 0

iptable_nat 21548 3 ipt_MASQUERADE,ip_nat_ftp

ip_conntrack_ftp 71856 1 ip_nat_ftp

ip_conntrack 30768 5 ipt_MASQUERADE,ipt_state,ip_nat_ftp,iptable_nat,

ip_conntrack_ftp

ip_tables 17152 9 ipt_TOS,ipt_MASQUERADE,ipt_LOG,ipt_TCPMSS,ipt_st

ate,ipt_REJECT,iptable_mangle,iptable_filter,iptable_nat

ip6table_filter 2560 1

ip6_tables 18448 4 ip6t_LOG,ip6t_REJECT,ip6table_mangle,ip6table_fi

lter

ipv6 244100 15 ip6t_REJECT,ip6_tables

binfmt_misc 9992 1

subfs 7296 2

linux:~ # lsmod

Module Size Used by

ppp_generic 28692 0

slhc 7424 1 ppp_generic

ltmodem 532720 0

usbserial 28912 0

parport_pc 35264 1

lp 10916 0

parport 37704 2 parport_pc,lp

edd 9240 0

joydev 10176 0

st 38940 0

sd_mod 19840 0

sr_mod 15652 0

scsi_mod 107980 3 st,sd_mod,sr_mod

ide_cd 36484 0

cdrom 36508 2 sr_mod,ide_cd

nvram 8328 0

snd_seq_oss 30976 0

snd_pcm_oss 56868 0

snd_mixer_oss 18688 1 snd_pcm_oss

snd_seq_midi 8864 0

snd_seq_midi_event 7680 2 snd_seq_oss,snd_seq_midi

snd_opl3_synth 16004 0

snd_seq_instr 7552 1 snd_opl3_synth

snd_seq_midi_emul 7680 1 snd_opl3_synth

snd_seq 54672 9 snd_seq_oss,snd_seq_midi,snd_seq_midi_event,snd_opl3_synth,snd_seq_instr,snd_seq_midi_emul

snd_ainstr_fm 2816 1 snd_opl3_synth

processor 16040 0

snd_es1938 20772 4

snd_pcm 96776 2 snd_pcm_oss,snd_es1938

snd_page_alloc 11012 1 snd_pcm

snd_opl3_lib 10880 2 snd_opl3_synth,snd_es1938

speedstep_lib 3712 0

snd_timer 25476 3 snd_seq,snd_pcm,snd_opl3_lib

snd_hwdep 9732 1 snd_opl3_lib

gameport 4736 1 snd_es1938

snd_mpu401_uart 7808 1 snd_es1938

snd_rawmidi 24992 2 snd_seq_midi,snd_mpu401_uart

snd_seq_device 8328 6 snd_seq_oss,snd_seq_midi,snd_opl3_synth,snd_seq,snd_opl3_lib,snd_rawmidi

snd 59524 26 snd_seq_oss,snd_pcm_oss,snd_mixer_oss,snd_seq_midi,snd_seq_midi_event,snd_opl3_synth,snd_seq_instr,snd_seq_midi_emul,snd_seq,snd_es1938,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device

soundcore 8800 1 snd

freq_table 4612 0

ipt_TOS 2432 9

ipt_MASQUERADE 3584 1

ipt_LOG 5632 1

ipt_TCPMSS 4352 1

ipt_state 1920 12

hid 40640 0

uhci_hcd 29584 0

ds 17284 4

yenta_socket 15744 0

pcmcia_core 61636 2 ds,yenta_socket

intel_agp 17052 1

agpgart 28712 1 intel_agp

usbcore 96988 5 usbserial,hid,uhci_hcd

evdev 9600 0

ip6t_LOG 5504 2

ip6t_REJECT 7168 3

ip6table_mangle 2688 0

ipt_REJECT 6400 3

iptable_mangle 2816 1

iptable_filter 2816 1

ip_nat_ftp 4720 0

iptable_nat 21548 3 ipt_MASQUERADE,ip_nat_ftp

ip_conntrack_ftp 71856 1 ip_nat_ftp

ip_conntrack 30768 5 ipt_MASQUERADE,ipt_state,ip_nat_ftp,iptable_nat,ip_conntrack_ftp

ip_tables 17152 9 ipt_TOS,ipt_MASQUERADE,ipt_LOG,ipt_TCPMSS,ipt_state,ipt_REJECT,iptable_mangle,iptable_filter,iptable_nat

ip6table_filter 2560 1

ip6_tables 18448 4 ip6t_LOG,ip6t_REJECT,ip6table_mangle,ip6table_filter

ipv6 244100 15 ip6t_REJECT,ip6_tables

binfmt_misc 9992 1

subfs 7296 2

nls_utf8 2176 1

nls_cp437 5888 1

vfat 14080 1

fat 43328 1 vfat

dm_mod 50044 0

reiserfs 233808 1

 

 

 

I've read a few How-To's and FAQs, and all say with a Lucent LT WinModem it must be /dev/ttyLT0. So I've no idea really. However I do know that /dev/tts/ does not exist. While /dev/ttyLT0 does. I also checked in the settings via YaST or YaST2 and it said that /dev/modem leads to /dev/ttyLT0.

 

 

 

When I do locate minicom, this is what I get.

 

Quote:

linux:~ # locate minicom

/usr/lib/python2.3/xml/dom/minicompat.py

/usr/lib/python2.3/xml/dom/minicompat.pyc

/usr/lib/python2.3/xml/dom/minicompat.pyo

/usr/share/doc/howto/en/html/Remote-Serial-Console-HOWTO/modem-minicom.html

 

I'm guessing this means I don't have minicom installed on my system? I tried doing minicom in Konsole, and it didn't work - I tried in root, and as a user. Neither worked. I did locate, and as you see it doesn't bring up much.

 

 

Yes, when I try to dialup via either wvdial or smpppd, I am in a user which is part of the dialout group. He's only part of the following groups: audio, dialout, modem, tty, uucp, video and www. He is NOT part of: users, at, bigsister, bin, cdrom, console, daemon, disk, distcc, floppy, ftp, games, kmem, localham, lp, mail, maildrop, man, named, news, nobody, ntadmin, postfix, privoxy, public, root, shadow, sshd, sys, trusted, utmp, vscan, wheel and xok.

So, he isn't part of a lot of groups. - Should I add my user to other groups such as users, anything?

 

 

Thanks. Much appreciated!!

[martouf 0]

1. yes, it looks like you don't have minicom installed. you probably want

to find the package and install it.

 

2. the account you're using belongs to the dialout group. That's good.

No need to change anything there.

 

3. what happens if you modprobe ltmodem first, then ltserial second?

 

4. you obviously have a different LT modem driver than the one I found

documentation about.. seems I found docs on the one for the 2.4 kernel (or earlier).

 

 

[eBopBob 0]

1) Ok thanks. I'll check the SuSE linux CDs and see if it comes on one of those. If not, I'll try and look for a source file and then try to compile and install it.

 

2) Ok.

 

3) I'll try that, and then post my results. But I think I've done that and I get the same, however I'll check again and let you know.

 

4) Yes, I've the 2.6 kernel and my current ltmodem driver is for the 2.6 kernel - Maybe my problem with ltserial is that it's for the 2.4 kernel? I'll also check if this actually exists "/lib/modules/2.6.4-override-default/ltserial.ko" as I've heard that SuSE forgot some of the files for lt modems, so I'll see whether it's there or not.

[jimf43 0]

Don't know about with Suse, but, it was just brought to my attention that the new SimplyMepis rc3 has specific support for Lucent winmodems. I know it works well with My Compaq PPresario 1500 which uses one.

[eBopBob 0]

Thanks for that jimf43.

 

I'll look into Mepis as well. I heard it was a pretty nice distro, and maybe if I can get it working with my current Lucent LT WinModem, not only will I be able to go on the net with Linux I'll also save €60!

 

If I were to get Mepis, how easy would it be to set it so that it installs on hda3, and have the swap as hda2 and leave hda1 alone?

(Currently: HDA1 Windows, HDA2 SWAP, HDA3 Suse Linux)

 

 

Thanks.