Loki3
06-27-2002, 04:08 AM
The steps to configure your Lucent Chipset WinModem...
1.Find out wether you have a WinModem
WinModem Database (http://www.idir.net/~gromitkc/winmodem.html) 2.Find out if you have a drivers for your WinModem
www.linmodems.org (http://www.linmodems.org) 3.Download and Install your drivers(use a package, much easier). Turn off Plug and Play in your BIOS if it's on or it'll make a mess of things.
4.Add the modules(drivers) to your system.
A.Navigate to the directory in which your drivers are installed. With Red Hat 7.3
this is /lib/modules/2.4.18-3/*. This could be a different path depending on you
distrbution of linux.
B.Use the command lsmod or /sbin/lsmod to see if your modules are alreadly loaded
C.Use the command insmod * or modprobe * to load the module where * is name of modules. If the following commands don't work
make sure your logged in as root and try /sbin/lsmod or /sbin/insmod or whatever other command your trying to run.
D.Use the lsmod command again to verfiy that your modules loaded
5.Edit startup scripts to autoload modules
A.Navigate to the directory in which your startup scripts are kept. In Red Hat 7.3
this /etc/rc.d
B.Use vi or any other text editor to open your startup script. I use rc.local
but I think rc.sysinit would work too. Be careful not to **** with any of the orignal commands.
C.Add the commands to load the modules on boot. Use insmod, /sbin/insmod, modprobe, or
/sbin/modprobe * where * is the name of your module. Use the same command that you used on step 4C. Make sure to add some comments
using the <#blah,blah, this a comment> form with <> removed of course. That way in
the future you'll remember what the hell you were doing. Save and exit.
6.Check serial port designations
A.This is where it gets wishy-washy. First find out where your symlink /dev/modem is pointed.
Use the ls -a -l /dev/modem command to figure that out.
B.Next I suggest you read the info that came with your drivers. If you can't find any you should be able to back track
far enough to get the email address of guy who wrote the driver he'll point you in the right direction. I found mine in
/usr/share/doc/* where * is your driver name. Also there might be some helpful scripts there. I used one called checkout
which made sure everything was working and fixed it if it didn't. Excute scripts by ./* where * is the name of script.
I suggest you learn a little more about the scripts from READMEs before running them.
C.Determine from your information which serial port your driver uses. For example mine uses /dev/LT0 instead of the
default /dev/ttySx. Again try to refer to your user information.
D.If your symlink is pointed elsewhere delete it with the following command rm -i /dev/modem
E.Create a new symlink with the command ln -s /dev/* /dev/modem where * is the apporiate serial port
7.Configure ISP account. I used kppp and even I could figure it out without having to run crying to the help manauls. You'll
need a bunch of information from you ISP so if you don't have it call and whine until they send it to you. You'll need the
following information from your ISP:
A.Local telephone dial-in number(s)
B.User login name
C.User password
D.e-mail address
E.e-mail host
F.News host
8.Troubleshooting -> Well if the above didn't help whine and complain to all the people on the linuxnewbie.org BBS. Thats
what I did and it worked ;-). Also email your driver creator for help if your really stumped or email me if you have a problem
specific to the chipset I configured, otherwise there's not much I can do, I'm still a newbie too.
_Loki
P.S.Thanks to all my peeps who helped me get this **** configured. Shout out to mdwatts and fancypiper!
[ 27 June 2002: Message edited by: Loki3 ]
[ 27 June 2002: Message edited by: Loki3 ]
1.Find out wether you have a WinModem
WinModem Database (http://www.idir.net/~gromitkc/winmodem.html) 2.Find out if you have a drivers for your WinModem
www.linmodems.org (http://www.linmodems.org) 3.Download and Install your drivers(use a package, much easier). Turn off Plug and Play in your BIOS if it's on or it'll make a mess of things.
4.Add the modules(drivers) to your system.
A.Navigate to the directory in which your drivers are installed. With Red Hat 7.3
this is /lib/modules/2.4.18-3/*. This could be a different path depending on you
distrbution of linux.
B.Use the command lsmod or /sbin/lsmod to see if your modules are alreadly loaded
C.Use the command insmod * or modprobe * to load the module where * is name of modules. If the following commands don't work
make sure your logged in as root and try /sbin/lsmod or /sbin/insmod or whatever other command your trying to run.
D.Use the lsmod command again to verfiy that your modules loaded
5.Edit startup scripts to autoload modules
A.Navigate to the directory in which your startup scripts are kept. In Red Hat 7.3
this /etc/rc.d
B.Use vi or any other text editor to open your startup script. I use rc.local
but I think rc.sysinit would work too. Be careful not to **** with any of the orignal commands.
C.Add the commands to load the modules on boot. Use insmod, /sbin/insmod, modprobe, or
/sbin/modprobe * where * is the name of your module. Use the same command that you used on step 4C. Make sure to add some comments
using the <#blah,blah, this a comment> form with <> removed of course. That way in
the future you'll remember what the hell you were doing. Save and exit.
6.Check serial port designations
A.This is where it gets wishy-washy. First find out where your symlink /dev/modem is pointed.
Use the ls -a -l /dev/modem command to figure that out.
B.Next I suggest you read the info that came with your drivers. If you can't find any you should be able to back track
far enough to get the email address of guy who wrote the driver he'll point you in the right direction. I found mine in
/usr/share/doc/* where * is your driver name. Also there might be some helpful scripts there. I used one called checkout
which made sure everything was working and fixed it if it didn't. Excute scripts by ./* where * is the name of script.
I suggest you learn a little more about the scripts from READMEs before running them.
C.Determine from your information which serial port your driver uses. For example mine uses /dev/LT0 instead of the
default /dev/ttySx. Again try to refer to your user information.
D.If your symlink is pointed elsewhere delete it with the following command rm -i /dev/modem
E.Create a new symlink with the command ln -s /dev/* /dev/modem where * is the apporiate serial port
7.Configure ISP account. I used kppp and even I could figure it out without having to run crying to the help manauls. You'll
need a bunch of information from you ISP so if you don't have it call and whine until they send it to you. You'll need the
following information from your ISP:
A.Local telephone dial-in number(s)
B.User login name
C.User password
D.e-mail address
E.e-mail host
F.News host
8.Troubleshooting -> Well if the above didn't help whine and complain to all the people on the linuxnewbie.org BBS. Thats
what I did and it worked ;-). Also email your driver creator for help if your really stumped or email me if you have a problem
specific to the chipset I configured, otherwise there's not much I can do, I'm still a newbie too.
_Loki
P.S.Thanks to all my peeps who helped me get this **** configured. Shout out to mdwatts and fancypiper!
[ 27 June 2002: Message edited by: Loki3 ]
[ 27 June 2002: Message edited by: Loki3 ]