Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi Ron! I would like to think also we can get this working today Perhaps I have helped us take the scenic route a little, but MichaelK has pointed the way to the direct route, I think!
As for /dev/modem it may or may not exist, in your case it appears not to exist. However it is often just a 'symbolic link' (comparable to a windows desktop shortcut) which actually points to another /dev item, like /dev/ttys-something, or in some cases, for example my intel 536ep modem, /dev/modem points to a device called /dev/536ep. So, not to worry if /dev/modem isn't around. You can create it though, and maybe wvdial would then work??.
If you were to create it, and point it at /dev/ttys0, and then open wvdial, maybe wvdial would find the modem.
Yes, the terminal is the right tool for the echo statements. You might try using root-priveleges in the terminal, if you haven't yet. (Or using a root terminal, basically)
As for Gnomeppp, it is reading from a configuration file which either has not yet been configured, or is misconfigured. If you can locate the file it is reading from, and remove the line indicated as being 'malformed' it may help, but it says it's ignoring it anyways..
Last edited by GrapefruiTgirl; 03-21-2007 at 12:46 PM.
well it's painfully obvious to me that I need to work a lot on commandline knowledge
ln -s /dev/ttyS0 /dev/modem ... and
ln -s /dev/ttyS1 /dev/modem
nothing was any better, guess it wasn't major lol
can't talk to my ISP until after 1 or 2 pm, for me that's an hour from now.
I do NOT want to give up on this modem; all signs are that it should work as well as any. Because I'm build a few computers for resale and want to set them up with Ubuntu, I have bought some PCI controller-based modems on ebay in the last couple of days. I'll be delighted if they work and I can get rid of the clutter of serial modem cables and box, but I still want this one 56sx92 to work in linux before I even try anything else.
I have rebooted a couple of times with different bios configs for serial port. As with all of today's computers there is but one physical connection but 2 ports are listed in bios. Beyond that device manager shows 2 16550 things, I don't really understand how or why they're there or what to do with them, oh well.
I suspect some part of the problem here may be because I'm using this box a) connected to the www via a networked windoze box vs. B) messing around with these linux tools directly. But I have tried safe-boot, running with the windoze box off, or it's dialup disable, or the linux network disabled, it seems the same no matter what.
I've also been thru kppp any number of times, with/wo following Best Data's instructions on their pdf. That's why I need to talk with my ISP, about ? DNS, and about PAP or other choices, seems it's gotta be something in that area. I cannot type in kppp's terminal box, assume that must require root but it doesn't ask for that so I'm a little lost there.
phoned my ISP, who did confirm my settings in kppp were okay.
The serial port seems a likely part of this problem. Ubuntu 6.10 doesn't have setserial, am downloading that now in hopes that'll help. That means working with tar.gz which has also been troublesome to me with Ubuntu, which opens it's Archive Manager which doesn't install anything. I think I've found tracks by which I can install, be finding out in a while.
Is this a dual boot PC? Did the serial cable come with the modem? There are two different kinds of cables. A straight through and a null modem. If not then this could be your problem. Also related to not seeing any lights when you tried the echo command. You need a null modem cable. It is similar to an ethernet crossover cable where pins 2 & 3 are crossed at one end.
Did you ever try the querymodem button in kppp. If so what happened?
I have a Zoom modem which has RD and TD lights. These flash when datat is being sent from/to the PC. When I try the
echo "atdt 555-1212" > /dev/ttyS0 command I do see these lights flicker.
You can try accessing your modem via minicom which is console aplication like hyperterminal. It might be a little much to figure out if you never have used command line stuff much.
yes, dual boot pc, XPhome and ubuntu 6.10 x64. This 56SX92 worked from the git-go in XP, still does if I go back into XP.
in 20+ years I've never known what a null-modem cable might be. The modem serial connectors are 25-pin on the modem to 9-pin on the box, came with the (new) modem.
kppp Query Modem returns the 10(?) blank ATI things.
p.s. I missed something in that minicom thing
commandline echo "atdt 555-1212" > /dev/ttyS0 and echo "atdt 555-1212" > /dev/ttyS1 returned only the prompt
echo "atdt 555-1212" > /dev/ttyS2 & echo "atdt 555-1212" > /dev/ttyS3
had to go to root for S4 & S5, returned nothing, doubt that I'd have to go further with that. I have no clue what returning nothing might mean, dumb thing. Nothing made lights blink - again only PWR and DATA lights are on of the 4-5 lights on this modem. At the beginning of all this only the PWR light was on, is that progress LOL?
oh oh, minicom <!-- this file was installed to automatically upgrade your machine from using
mini-commander to using Deskbar.
If you wish to continue using mini-commander, please recompile
GNOME-Applets with -enable-minicommander and your mini-commander applets
ronkz@gb-server:~$ -enable -minicommander
bash: -enable: command not found
bash: -enable-minicommander: command not found
ronkz@gb-server:~$ enable minicommander
bash: enable: minicommander: not a shell builtin
so for whatever reason it fell outta Ubuntu and the getback command doesn't work ??? So I'll be seeing what DeskCut is about I guess. .... well can't find that either
I downloaded the setmodem package today from sourceforge.net and next must fuss with trying to unravel a .tar.gz, sheez so later, thanx
As for the empty returnd from querying the modem, I've had PCI modems which worked fine, but returned empty query strings too. Modems can be pretty dumb. Particularly the software ones, unlike yours.
The tar.gz file you should be able to unzip from your desktop if you have any archive software like ARK installed. Just right clicking the file should give you an option like "Extract to.." or "Extract here..". For more info, read 'man tar' in a console.
A null modem cable (if you still don't know) is like a dummy-cable, like for connecting 2 computers directly together without a network or an 'internet' in between.
Sheesh is right.. For a modem that requires little or no software, this is ridiculous.
Michael, what do you suppose we could/should stick into kppp as far as some AT commands, to atleast maybe get this talking a bit, assuming the cable isn't an issue?
If it is... Well, it can't be the cable, if the modem works under Winduhs..
Last edited by GrapefruiTgirl; 03-21-2007 at 07:59 PM.
thanks for the link to ARK (I guess), so I installed that, but sorry, it's not about anything more than the whatever that came bundled in Ubuntu. Extract, big deal. Where the heck is Install? At best it seems back to the muddle of Terminal and trying to enter commands I don't understand. I can say this, if there's ANY other fileformat for downloading, forget tarballs, that's ancient history. I can't tell you how many of those I've downloaded and couldn't deal with, INCLUDING that every time I open LQ it wants me to download Adobe Flash Player, then have to do it manually, then can't get it installed, but must endure the message at LQ and elsewhere every time. guess I'm just dense.
No null-modem cable, I'm quite certain, that's not it at all -- I recall going thru the DOS days without one. I am feeling increasingly certain we need setserial, yet another mess because it's tar.gz.
Any way, the readme for setserial
The simplest way to configure the serial ports is to copy the provided
rc.serial file to the appropriate /etc/rc.d directory. For example,
to install rc.serial on a RedHat system, copy rc.serial to
/etc/rc.d/init.d/serial, and then run the command "chkconfig -add serial".
well I'm not using RedHat, and there's no /etc/rc.d/ and suddenly I would need to learn how to create that and find that one doesn't have that option in File Manager. Meanwhile there are many subs rc0.d...rc6.d but can't copy/paste into any such, and one can surmise that perhaps this paste needs to go into each of them, seems tedious and shaky to me, not even knowing if this'd work anyway.
surely I'm missing something to get this far off the mark?????????????????????? I do really think that we need to use setserial here but there must be some better/easier way to get that going. The download for that was kinda huge, we should make some use of it!
thanks, and sorry for that this sounds so bitchy, but it's been this entire week, c'mon!
Gosh.. I'm starting to feel bad that you are having such a hard time here.
OK, well, I'm not using Ubuntu (I did briefly) but here is some general information about how to use tarballs, and about compiling and installing stuff, and about rc.d ...
1..A tarball is nothing more than a bunch of files, rolled into a package, and compressed.
2... There are other things to download besides tarballs. There are RPM's too, and probably a few other things. However, it always comes down to installing the thing after it is extracted.
3.. My system doesn't use RPM's. I use tarballs, like 'tarball.tgz' or 'tarball.tar.gz'. Some linux operating systems have a built in mechanism for installing stuff and removing stuff in a graphical environment, very much like windows. Double-click it and follow the instructions.
Ubuntu may have one of these, I don't know, but it is likely that if it does, it's not going to like a tarball, so here's what you would typically do with a tarball:
I'll assume based on your last post that extracting it is not the problem..
In the resulting folder created by extracting the package, there will be a bunch of files, and usually among them will be a README and/or an INSTALL file, which contain basic instructions for what to do with the package.
Typically there will be a file called 'Makefile', and often there is a file called 'configure'. The README/INSTALL should explain IF and WHY you should use either the Makefile, or the Configure file, to install the package.
To use either, open a console. If the package is going to be installed SYSTEM-WIDE, you will need root priveleges. Many things which install only for USERS can be installed WITHOUT root priveleges, but not all. You will find out soon enough if you need root to install, because it will return errors and stop.
in the console, to use a makefile, type: make
to use a configure file, type: ./configure
usually after running the configure file, you then need to run the makefile.
after doing the above, you typically type: make install
And presto! Now the package has been compiled, and installed to wherever it's supposed to be installed to. And to use it, check the readme file or other instructions which come with the file. For example, for help, if you are using something called 'setserial', then you can probably type: setserial --help or setserial -help or setserial help or man setserial or info setserial.
Not all Linuxes use the rc.d init structure. Mine does, and many do, but I can't speak for Ubuntu.
I certainly feel for your frustration Ron, but here's an idea which may also get you much more accurate information relating to your specific Ubuntu system: Check out the Ubuntu Forum Put up some posts over there, as the Ubuntu users will surely be able to help you with the specifics of Ubuntu's ins and outs.
But of course, if I/we here can help you further, or I have missed or confused something in this post, please do come back and just ask I am as determined as you are to get that silly modem working!
Last edited by GrapefruiTgirl; 03-21-2007 at 10:41 PM.
That readme is indeed a bit vague. Infact, if I were to have followed the instructions there, it wouldn't have worked for me either, by default, because my system did not contain the 'chkconfig' function until I installed it!
As always, just post if ya need help
BTW - you say you have folders rc0.d to rc6.d ?? Those are usually inside the folder /etc/rc.d/ so perhaps Ubuntu actually DOES use the rc.init format. What is the name of the location where those rc0.d folders are located? That's most likely where you would put the rc.serial file, and then make sure it is CHMOD'd to executable (change the file's permissions by adding the 'executable' bit. You can either right-click the file from desktop, or use the console command chmod +x rc.serial)
Last edited by GrapefruiTgirl; 03-21-2007 at 11:28 PM.
not home yet, but a bit of success here. minicom is reinstalled, and so is setserial, both by using get-app... a stroke of good luck. I will now be trying to use those tools to hunt down my stupid serial modem. I'm seeing some things I don't understand, so cross fingers for me. Later
grapefruitTgirl, now I'm stuck. I have found/installed both setserial and minicom. by:
I'd say that setserial is a last resort, in how it works / what it does / unpredictable results / complexity.
So that leaves minicom, which I'm finding clumsy and incoherent. If you have some suggestion(s) they would be immensely appreciated.
A thought here... it seems that some/much of this stuff needs to be run in root but will run as user and then fail to stash needed changes. Seems that Ubuntu sometimes doesn't step in with root login. I just ran sudo kppp and wow were there errors! I could relay the output saved to a .txt file but don't find a link here to so that ??? Probably because Ubuntu is super-focused on it's gnome interface.
OK, I will have a read thru that link where you got the install instructions and get an idea what the deal is. I haven't used either minicom OR setserial myself, so I'll look at minicom first..
Generally (again I dont know what these 2 tools really do yet) stuff like this is installed as root, run or configured as root, and then 'used' as root by a user. Simply running something should be kinda like kppp, where one just clicks and goes.
Some people disagree, depending on the OS in question, but it is sometimes easier to get something working by manually configuring it, as opposed to using a desktop config-tool with a GUI.
Anyway, I'm going to have a look at those tools at that link, maybe even install minicom myself, and see what I can learn. Ill get back to you.