Connecting to Internet via modem
Most common question, how to connect to internet using standard winmodem. I read some infos, but it still isn't working.
Here's what I do:
1. I got newly scanModem.sh and it detected my Modem as Lucent/Ageere, which is correct since that Win Xp is detecting it as Lucent WinModem.
2. Since I got kernel 2.6.15-23-386 it says it need those Martian drivers to work so I downloaded needed tarball (martian-full-20061203.tar.gz)
3. Installed needed kernel/linux headers, make application and gcc C compiler and compilation went without any probelms (or it isn't?). I used standard commands: make, sudo make install.
4. Got GNOME-ppp to work and under options it auto-detected my modem as /dev/ttyLTM0 which was not in settings combobox.
5. When I enter dial number (user and password along) and dialed number, I didn't hear modem dialing (like he is doing in XP) and log says "sending password" and there it does nothing.
What I am doing wrong?
Connecting to internet via modem
I know this thread is a few months old, but I thought I'd drop a piece of advice for any body that may still using the verson of the martian driver mentioned in the first post(martian-full-20061203.tar.gz).
Back in feb. of 2007, I was able to get this driver working on the very first try in edgy. Then I killed the OS trying to setup Neverwinter Nights, oops.:p Unfortunately when I reinstalled ubuntu, I forgot to back up the instance of the driver I had, and had to download a new instance. I never got that driver to work right again on dapper, edgy, or fiesty. Then for some reason or another I decided to try the version released before 20061203, and voila....never had a problem with the older version.
So if you're using 20061203, please, don't. Besides, there was a new release in august 2007, and it seems too work fine.
Connecting to internet via modem
If anyone is still looking for a guide to installing this modem, here are the steps I took to set up my modem. I used wvdial for my dialer app. The only catch to this is that "martian_modem --daemon" has to be ran manually every time you reboot, and it has to be run as root. There is a way to make it so you don't have to do that, but at the end of june, I was just happy I could finally make it work again. (Note the issue I mentioned on my last post with the 20061203 driver version.) So I haven't looked in to the fancy stuff yet.
If you are using edgy or later, you might not need to do step 2 through 4, but for dapper and earlier this is a chicken and egg kind of thing, cause you need some type of internet connection for the first 4 steps.
And theoretically, from what I've read, you're only required to update the headers and restricted modules. Since this is a perfect world, I just when ahead and updated everything in step 2.
1. Use Ubuntu:Feisty - to guide you through adding repositories.
2. Open synaptic, search for linux, and make sure that "linux-generic" (as for dapper it's just "linux") is marked for upgrade. Also make sure that the latest version of the headers, image, and restricted modules are marked in the same list.
3. Wait for several hours....assuming you're connecting via internet connection sharing provided by another PC that can already dial out. Recommended time to do this,....just before bedtime. ;)
4. The next morning...before breakfast, reboot. After the system comes back up connect to the internet again. Open a console, and run
sudo apt-get install build-essential linux-headers-`uname -r` wvdial
then go have breakfest.
(NOTE: I used a hyphen, not single quote, on both sides of uname-r)
5. Now we can compile.
sudo make install
(If either of these commands return several errors, Make sure you've did you the installs mentioned in steps 2, 3, and 4.)
I, of course :rolleyes:, ran into issues with the automate and helper scripts, so to ensure that everything was done right I did all the following.
6. sudo mknod --mode=0660 /dev/ttySM0 c 62 64
7. sudo ln -s /dev/ttySM0 /dev/modem
8. sudo modprobe martian_dev
9. sudo gedit /etc/udev/rules.d/ltmodem.rules
Add the following lines and save the file.
# ltmodem KERNEL="ttyLTM0",
Finally we're finished with the driver, so we'll go into dialing.
10. sudo martian_modem --daemon
(NOTE: Step 10 has to entered every time after a rebooting or logging in.)
Create the initial configuration for wvdial.
11. sudo wvdialconf /etc/wvdial.conf
Hopefully in the output, at the end of at least some of the lines that start with ttySM0, there is an OK at the end of the line. If not, and you did run the command in step 10, then we've got issues, and you'll have to back track on your progress for any missed commands or errors.
Configure wvdial for your ISP.
12. sudo gedit /etc/wvdial.conf
Remove the semicolon before PHONE=
and put in the number you will dial after PHONE=. Dashes not required in the number. Do the same for the lines with USERNAME= and PASSWORD=, but of course provide your username and password instead of the phone number.
Add the following lines:
Carrier Check = no
Auto Redial = yes
Save and close the file.
Now prepare for the moment of truth. DIAL!!!
13. Type in wvdial and hit enter.
Now you can watch the modem in action as it connects, hopefully. If you get permission errors when you run wvdial, you probably got caught by the catch. Try doing step 10 again, then wvdial.
After you see the primary and secondary DNS numbers in the output, you should be on the information super highway and browsing. And another catch. Don't close this prompt or kill the command, it will cause the modem to disconnect. If you do see the DNS numbers and the output seems to have stoped, but you can't browse or make any contact to the internet, disable any other network interfaces that might be active, and redial. Especially if you havean RALink wireless card.
Hope this amazing adventure helps and was worth a 4K download speed. I tried to fill in all pitfalls that I ran in to on my 4 month quest. I felt that may other gides left a lot of little details out. Especially for having to deal with dial up for the first time in anything but winblows.
Any questions, advice, or shortcuts are welcome.