Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Another mighty query, this time concerning modems. I have a HSP56 MicroModem (of PCtel origin) installed in my PC, and it
is proving to be a bit of rotter (!) to setup. I know from reading the various FAQs that you can coerce it to work under Linux, but the websites didn't tell me just how difficult it would be.
I have installed drivers, which I am trying to get to work. The next problem is using setserial:
my syntax is
setserial /dev/ttyS2 uart 16550A irq 9
however, the I/O port address seems to be questionable. According to WinME (yuk), it says that this lies in the range DC00-DC3F, which seem a bit high compared with other values mentioned in,say, the SuSE linux manual.
Should I specify
setserial /dev/ttyS2 uart 16550A irq 9 0xDC00 ?
(assuming that the port address is octal - does anyone know of a way in Windoze rather than going via the Start->Settings->Control Panel->System route to verify this address.
Its all OK until I get to
and insmod ptserial
at which point Linux grumbles about a kernel mismatch, saying that the modules were compiled using the 2.4.4 Kernel, but
SuSE uses 2.4.4-4GB, and it won't allow me to install them.
The website you mention discusses the use of a fixscript routine to correct this error, but even this doesn't allow me to install.
It is then that the FAQ mentions "recompiling the kernel" ... and my heart sank
recompiling the kernel is not a terribly difficult task (i did it within a week of my first succesful linux installation) ;-)
just refer to the kernel-howto o
for more info on ur types of modem refer to www.linmodems.org (or u can become a member too)
u can also use the -f option for the insmod command (ie, insmod -f pctel.o)
and remember, u will find the modem at /dev/ttyS15
and it is usually linked to /dev/modem
firstly, every modem requires a serial port to function
well, as this is an internal modem (connected to a pci or a isa slot), it has to emulate a serial port
now in dos, the driver makes the modem emulate com 3/com 4
but these serial ports usually have conflicts and hence in linux the drivers make the modem emulate com 14 (/dev/ttyS15)
this /dev/ttyS15 is also symlinked to /dev/modem
You are correct, I have never heard of ttyS15 and using it in configuring a modem.
If your modem is a hardware modem and you can set the com and irq manually on the board..
Try this, if you know there are no irq conflicts or the such.
# setserial /dev/ttyS2 irq 9
( I usually don't put the i/o address in the setserial command, it seems to work most of the time without declaring that in the command )
I have my own modem set on com3 or ttyS2, and irq 9. Linux doesn't detect or did not detect it so that is the command to get it to recognize my modem and go from there. Then I put the setserial in my startup files so I wouldn't have to do that everytime.
well tis modem *is* a winmodem (the word hsp :- host signal processing makes it obvious) and and i have a modem with the same chipset and minicom, mgetty detects it on /dev/ttyS15
the modem driver is configured like that
i always hate to tell people to give up, but the winmodem battle is not one that linux users tend to walk away from.
i take it for granted that you've been over www.linmodems.org time and time again, you tried every serial port available, and mixed and matched every setting you could find until your fingers bled, leaving the red marks on the keyboard as the only token of your struggle.
remember, there ARE linux compatible modems out there. i know from experience that you tend to doubt that after a while. sometimes you just have to accept that the square peg won't fit in the round hole.