Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to figure out how to use a Sprint wireless modem (Merlin C201) on a new Dell Inspiron 700m running SimplyMEPIS 3.3. It seems clear that the card is recognized, because the card's signal light goes from red to green after a minute or so.
After searching around, I found this shell script that is supposed to automatically enable the card:
I tried running that as root, but did see any action--but then, I have no idea what I am doing , and am not actually sure of the best way to "run" a shell script!
Have you tried using the regular tool to set it up?
startmenu > Internet > Connection > KPPP
From what I just googled, it sounds like it should act like a regular dialup device.
The page where the scriptwriter got his info is [ here ]. It is a tutorial with lots of good debugging helps too, but it also looks like it may be holdover from older versions of linux that had less support for easy dialup configuration. If the card is there and recognized by the system, try setting it up in KPPP first.
On second thought, you could also run the following command (at the command line) to see if it is truely recognized. Have the card plugged into the slot when you run the command.
Type "dmesg" at the command line and scroll through the output looking for mention of the card or any of the ttyS devices.
I'm assuming you were talking about ttyS0, ttyS1, .... The monitor is generally associated with tty0 , it isn't even an option in kppp.
I looked over the script, it is quite simple and should work, however it assumes that the card is initialized as ttyS3, which could have been the initial problem. If you need to change that, you will now need to modify one file by hand that the script generated (basically change "ttyS3" to the proper device name). That file is /etc/ppp/peers/cdma . And you will also need to change "ttyS3" at the bottom of the script.
Kppp should work too, and it will have better integration with the desktop. Make sure that pppd isn't running and hogging the device you need (hit CTRL-ESC simultaneously to pull up the "systemguard").
EDIT: And in case you don't know, the phone number to use with that card should be 777. The script automatically uses that number, but kppp will likely need you to input it.
Sorry I have not answered sooner, but have been out of town. I appreciate your looking at the script, and will try to get it working over the next couple of days. I already tried changing ttyS3 to ttyS1 but that did not appear to do anything, and I still get the message that the "modem is busy." But now I have some time to go at it with a vengance!
This is the only thing that has not worked with SimplyMEPIS, and it is really minor, but I want it all to work without having to keep M$ XP around, if you know what I mean.
Well, I am back in town and have returned to this problem. I cleaned off all the files and folders I had created following posted advice, and ran the script in a terminal. It appeared to set the card to ttyS3 dynamically and create the files it needs, so I was on the wrong track all together!
The script now starts just fine, and then goes to "Connecting"--where it hangs! It is clear that I am a lot closer to having it work, I just need to get through the last few yards/meters...
The script does not dynamically set which ttyS the card is recognized as, it only assumes that the card is ttyS3. Did you verify that the card is in fact ttyS3 (dmesg should have input regarding that) ?
I was looking at this part of the script when I said that:
echo "Please enter the Serial Port you want to use for your PCS connection \[/dev/ttyS3\]";
read COM_PORT_NEW
if [ ! $COM_PORT_NEW ]; then
COM_PORT_NEW=/dev/ttyS3
fi;
echo "$COM_PORT_NEW is the port you are going to use";
Since I accepted the default, it appears that to me that the script then sets the port as ttyS3--not?
dmesg has no mention of ttyS3 anywhere, just ttyS0 and ttyS1 which have been there from when I installed
That part of the script sets which serial device you attempt to connect to. The kernel sets up which serial device your card is.
If the kernel sets up ttyS3, then it *should* list it in the system logs (ie: dmesg).
ttyS0 and ttyS1 commonly correspond to (in windows-speak) com1 and com2, the two serial "com" ports/sockets that many computers have on the back (often near the monitor's socket). Many newer computers have only one com port, are you sure that both ttyS0 and ttyS1 have been there since installation?
Try plugging, unplugging, and re-plugging in the card, then check the bottom of dmesg. What does it say?
I don't know if it would get you anything, but you could try looking through the system info center in the control center for mention of your card, the ttyS devices, or the card ID number that you get from lspci. That is hard to read though.
Now this is interesting! I put the card into an older laptop (Dell Inspiron 3800) that does not have an internal wireless card or an internal modem. Then inserted the live CD SimplyMEPIS, and I could see during boot and in dmesg that it found ttyS03:
ttyS03 at port 0x02e8 (irq-9) is a 16C950/954
What does that mean? Is there an irq conflict? Do I have to I reinstall MEPIS on my new laptop, this time with the card in, to get it to work?
Hmm. That is interesting. Perhaps there is some kind of conflict.
You shouldn't need to reinstall with the card in, hotplug should take care of that when the card is inserted. You could try it, but I wouldn't expect magic results (though you never know).
To continue debugging what you've got, type the following, as root, at the command line:
Code:
tail -f /var/log/messages
That command will show you the very bottom (tail ) of the system messages, and will dynamically add new messages as they occur.
While tail is showing you the messages, unplug and replug the card, and see what messages you get.
EDIT: By the way, did it work on the older laptop?
Starting with your last question: yes, I connected and was able to use email and browser! It did not however seem to recognize the command given at the bottom of the script to disconnect:
stop_sprint_pcs.sh
Maybe I needed to specify location:
/sbin/stop_sprint_pcs.sh
To be clear: SimplyMEPIS 3.3 was installed on that old laptop, but the card did not work on the laptop itself. But when I used the live CD with the install option "older hardware" then it ran fine. I can't remember which option I used when I installed on the old laptop, but I am wondering if going that install route inserts serial (or other) modules that are not used for the "newer hardware" route. I am going to reinstall on the old laptop using the "older hardware" option with the card inserted when I get a chance to see if it makes a difference.
Now I will turn to your other point and get back. Thanks again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
, it isn't even an option in kppp. 
) of the system messages, and will dynamically add new messages as they occur. 
