Best Data v.92 serial modem registers as IDE
 

New modem, works fine in winXP but I am desparate to escape M$. Using and really like Ubuntu 6.10x64, but...

In Device Manager it's not listed under Serial, nor under 16550, the darn thing shows up as an IDE sub-component ID'd as 56SX-92. But my Device Manager doesn't do anything, just shows the hardware, can't do any moving or fixing or deleting with it.

kppp can sorta find it as ttyS0, enuf to trigger an MR light in the modem but nothing more. Gnome-ppp finds nadda. I am a windoze/dos puter old-timer but am very clumsy with Terminal. This sort of trouble, usually modem, has kept me from transitioning for 3 years now. Can/would someone please help?

Sh**t..LOL, I had a bunch of info for you here, then my browser crashed :( Grr!
Well, let's see, where was I.. OK, I think that unit has a conexant chipset in it. According to the hardware compatibility list here on LQ, that device gets a 10/10 for compatibility. You will find it as ttys4, according to one of the pages I will post below.
It apparently uses a smartlink driver, which should already be available in Ubuntu for you to use. If the device isn't getting detected (which it actually seems it is) you will need to either modprobe, hotplug, or insmod the driver into the kernel manually. Ubuntu sees it as 56sx-92, so chances are it is being detected.
First, here's the HCL, where the modem gets good reviews:
http://www.linuxquestions.org/hcl/sh...p?product=1203
Here's the linuxant site, where you can get drivers for conexant modems for linux. Save this as a last resort, but if you do end up here, get the modem chipset identifier for Windows, and use it to get the chipset info of the modem before returning there for the driver.
http://www.linuxant.com/drivers/?PHP...22c7656b1a0d00
Here's amother hardware forum, where you might learn some more about that modem and Linux:
http://www.linuxcompatible.org/Best_...SL_c11746.html

Now.. If you open a console window and type LSMOD, see if in the list, there is a module that looks like the modem driver, something like smartlink, 56-something, or something that appears to be a modem driver module. If there is something there, or you aren't sure, copy and paste the results into here and post it; we'll try to determine if the mdoem driver is loaded. If not, we'll deal with that situation later.:)
And if it IS there, then is should mainly be a matter of locating the device and using it.
Let us know how you make out, either way.
Good luck! and Welcome to Linux.

Here's some more useful info, from this thread:
http://www.linuxquestions.org/questi...d.php?t=319516
I have the exact same modem as you..and so far..it's worked well with the linspire distro. . Is your modem connected to the COM1 serial port ? If so, at least in linspire..you have to select /dev/ttyS0 in the modem device field for your modem to work properly. On the installation cd that your modem came with, in the manual on the cd, there are specific instructions how to set up the modem using linux. I hope this helps.

oops, not IDE
 

GrapefruiTgirl, thanks so much

first must admit a blunder - that IDE entry was NOT this modem, it was the name of Best Data CD in that IDE. A real duh! and I apologize to all here and at Ubuntu. For me, that's progress

This modem is supposed to be a controller-based modem, I'm not sure what Conexant should have to do with it, but...

meanwhile I finally fumbled thru scanModem for the nth time but finally did that properly(?) so have a bunch of files to read, but after 3 solid days of this fumbling it'll have to be in the morning. Yes, it found something Conexant but apparently a softmodem also installed in my box, as that's an hsfmodem which I don't care to deal with just now, if ever. Seems that scanModem thing is designed for softmodems, not hardmodems as I think the 56sx92 must be.

So in the morning I'll get back at all this, I am just too tired to think anymore. "I shall return" -- thanx, Ron

Ron, you're welcome.
LOL, that's funny stuff :) detecting the CD in the drive! Hehe, well no need to apologize; you've learned something which will stay with you ;)
You're correct, your modem IS a controller-based modem, according to what I've read. There are very few manufacturers out there who make modem chipsets; Conexant happens to be one of them, and they supply chips to probably dozens of modem 'manufacturers'; that's what Conexant has to do with it: Your modem might say "Best Data" on it, but it contains a Conexant chipset, which is what the driver is concerned with.
Scanmodem should have produced a file or other output with some data like serial numbers, part numbers, and the like, which you can use to identify the chipset and thus determine which driver you should be using.
Now regarding the softmodem it detected; are you certain you only have the modem, and no others, or do you actually have a softmodem installed as well?? If you are correct, and you may well be, then scanmodem maybe won't detect the serial modem. I can't say for sure, as I've never had an external modem.
Anyhow, your next step should be to check out the documentation on the CD, and see if there is actually Linux instructions in there :) that should simplify things!

little progress report
 

for the time being, I am going to shut down my box and remove the PCI modem within. Reasoning; that's definitely a winmodem which may be a separate project someday in the future, but at this time I don't want to have to sort that out of the scanModem reports. So when I reboot I will do scanModem again. This will be the 3rd time for that, the 1st was a total flop because I didn't find the instructions, the 2nd probably contains info from both modems which adds to the confusion, 3rd time hopefully a charm. So don't bother to reply to this, I'll get back here later today with whatever seems appropriate.

But I feel compelled to comment that these sorts of headaches with Linux are surely the reason that so many newbies (myself included) just give up and return to M$. I've been 3 years now screwing with this off/on, and this time I am determined to succeed, as darnit BG is NOT going to control my puter and my life any more! That has been the last straw for me.

I still have much to do on this, so later... Ron

a tad of progress, not there yet
 

Removing the PCI winmodem (yes, conexant chipset) helped a tad on rebooting, bring the DATA light on, but neither kppp nor gnomeppp could make it work. Among other things, I tried the kppp terminal but couldn't type into in, not that I know much about what to type anyway.

http://www.linuxcompatible.org/Best_...SL_c11746.html refers to an USB modem, mine isn't that, it's serial.

scanModem running for the 3rd time did not find my 56SX92, think that's because it's hunting down win/linmodems, huh?

kppp seems okay with setting ttyS0, but doesn't trigger it dialing; gnomeppp isn't okay with any of ttyS1-4, everything is "no modem found". And yes, I DID disconnect my network & modem on my win-box while messing with this.

My ISP is rather smaller localish, but does have a couple of Linux guys on-staff. Guess that'll be my next move, I did read the thread at LQ which you provided, didn't see much else in there which might help, so guess I'm still stuck. :study:

OK, can you tell me what the screen returns when you type into a console 'lsmod' ? Copy and paste the results of that command into here. Let's see if the device actually has been detected, and the module/driver has in fact been loaded. If this is the case, the thing to do next is figure out what the command set is for the modem, i.e. what commands might have to be programmed into the kppp in order to make the modem respond. If the module is not loaded in the 'lsmod' list, we'll load it manually, and continue to the next step:
When you open kppp, name your modem; put in your account name and password; put the dialing phone number you use, and set ttys0 as the modem; now on the 'modems' tab, select your modem and click 'edit'; next you should somewhere see a button called "Query Modem" and press it. The result in the little window should be a series of 8 or 10 ATI's or AT's with data after them. It doesn't matter what it says for the moment, but please let me know if you got to this section and if the modem replied.
:) Stick with it; if you want to let me help you ditch Windows, I will!

lsmod
 

ronkz@gb-server:~$ ismod
bash: ismod: command not found
ronkz@gb-server:~$ Ismod
bash: Ismod: command not found
ronkz@gb-server:~$ lsmod
Module Size Used by
ppp_generic 36384 0
slhc 9856 1 ppp_generic
binfmt_misc 16012 1
rfcomm 51360 0
l2cap 31744 5 rfcomm
bluetooth 64644 4 rfcomm,l2cap
nfsd 301840 13
exportfs 8448 1 nfsd
lockd 84880 2 nfsd
sunrpc 205640 8 nfsd,lockd
radeon 128544 2
drm 105128 3 radeon
cpufreq_userspace 6560 0
cpufreq_stats 9312 0
freq_table 7104 1 cpufreq_stats
cpufreq_powersave 3456 0
cpufreq_ondemand 10928 0
cpufreq_conservative 11272 0
video 22920 0
tc1100_wmi 10632 0
sbs 20928 0
sony_acpi 7704 0
pcc_acpi 19968 0
i2c_ec 7808 1 sbs
hotkey 14536 0
dev_acpi 17540 0
button 9888 0
battery 14088 0
container 6656 0
ac 8328 0
asus_acpi 21924 0
nls_iso8859_1 6912 1
nls_cp437 8704 1
vfat 17920 1
fat 65456 1 vfat
nls_utf8 3840 1
ntfs 109128 1
ipv6 334432 8
af_packet 29452 2
lp 16584 0
snd_intel8x0 42024 1
snd_ac97_codec 127064 1 snd_intel8x0
snd_ac97_bus 4352 1 snd_ac97_codec
sg 44584 0
tsdev 11136 0
usblp 18176 0
i2c_ali1563 9988 0
snd_pcm_oss 57344 0
snd_mixer_oss 22784 1 snd_pcm_oss
snd_pcm 108168 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 31112 1 snd_pcm
i2c_ali1535 9604 0
i2c_ali15x3 10500 0
i2c_core 29312 4 i2c_ec,i2c_ali1563,i2c_ali1535,i2c_ali15x3
parport_pc 43560 1
parport 49932 2 lp,parport_pc
evdev 14592 1
pcspkr 5248 0
8139cp 29696 0
8139too 34816 0
mii 8192 2 8139cp,8139too
snd 79016 8 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
psmouse 51088 0
serio_raw 10244 0
floppy 76648 0
soundcore 14112 1 snd
snd_page_alloc 13200 2 snd_intel8x0,snd_pcm
shpchp 49068 0
pci_hotplug 38912 1 shpchp
ext3 164880 1
jbd 74024 1 ext3
ehci_hcd 40456 0
ohci_hcd 25988 0
usbcore 167840 4 usblp,ehci_hcd,ohci_hcd
ide_generic 2944 0
sd_mod 25728 5
sata_uli 10500 4
libata 88984 1 sata_uli
scsi_mod 181424 3 sg,sd_mod,libata
ide_cd 39584 0
cdrom 43816 1 ide_cd
generic 7940 0
alim15x3 15128 0 [permanent]
thermal 19472 0
processor 38280 1 thermal
fan 7432 0
vesafb 11048 0
capability 7304 0
commoncap 10752 1 capability
vga16fb 16656 1
cfbcopyarea 5376 2 vesafb,vga16fb
vgastate 10368 1 vga16fb
cfbimgblt 4352 2 vesafb,vga16fb
cfbfillrect 6272 2 vesafb,vga16fb
fbcon 45824 72
tileblit 4736 1 fbcon
font 10240 1 fbcon
bitblit 8064 1 fbcon
softcursor 3968 1 bitblit
ronkz@gb-server:~$

I haven't even read the above as yet, forgive me, first time I have used that anyway. Be aware I ran that while being online from my win-box modem, if that might change the report. ditto for anything following in this post.

quite sure (not absolute) that the modem's on ttys1. kppp - All I get is "modem ready" then "modem initializing", nothing in the log except "expecting OK". Modem Query results all blank, with or w/o "wait for dialtone".

Stick with it; if you want to let me help you ditch Windows, I will! YES YES YES
I need to phone my ISP in the morning, might help with the config here. Have company due soon, so that's all for tonite, folks. thanx again, Ron

:) No worries.. I think we're in luck, and am checking for some further info from a far more knowledgeable LQ member than I, who has used this modem before successfully.
I am thinking I see the module loaded there in the list, the slhc module..
As for contacting your ISP, you should already have the necessary stuff if you are dialing out using Windoze already, i.e., your email/login, and password.
Anyhow, for the time being, have a great night, and we shall hopefully tackle this in the morning! I think we just need to stick some Hayes commands into it (standard modem commands) and off it'll go.
:) SV

I believe the slhc module contains routines to compress and uncompress tcp packets for transmission over serial lines and required by required by ppp.

An external serial modem does not require any drivers. scanmodem fails because it is neither a PCI or softmodem device. An external serial modem is the most compatable with linux.

If you computer only has one serial port then the device should be /dev/ttyS0. You can try this command to see of the modem responds.
echo "atdt 555-1212" > /dev/ttyS0

Awesome, thank you for adding that information, MichaelK :) That may be Just the Thing!!
And so, providing the modem does respond, then it is a matter of sticking in the right commands/command set, and all should be well?

Yes all should be well

thanks for joining in here, michaelk, and for all your great efforts, GrapefruitTgirl. I'm feeling somehow we will get there today, would that be super super!

gnomeppp, set either ttys0 or ttys1 returns:

--> Ignoring malformed input line: ";Do NOT edit this file by hand!"
--> WvDial: Internet dialer version 1.56
--> Cannot set information for serial port.
--> Initializing modem.
--> Sending: ATX3
--> Sending: ATQ0
--> Re-Sending: ATX3
--> Modem not responding.


using Terminal (is that the correct tool to use?):
echo "atdt 555-1212" > /dev/ttyS0 or
echo "atdt 555-1212" > /dev/ttyS1
returns nothing

lights on 56SX92 modem show PWR and DATA, all the time, never noticed any change.

next will call my ISP (zianet.com), supposed to be a couple of linux guys there including the owner

wvdial says it can't open /dev/modem no such file/directory.
I've not yet phoned my ISP, but the above should tell us something major??

/dev/modem would be a link to the actual serial port device i.e. /dev/ttyS0.
It isn't a major problem. You can create a link with the ln command:

ln -s /dev/ttyS0 /dev/modem

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..

ln -s /dev/ttyS0 /dev/modem
 

well it's painfully obvious to me that I need to work a lot on commandline knowledge

ran
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.

will be back after ISP chat. thanx to both

ISP not much help
 

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.

Anyway, still needing advice here, thanx

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
should reappear.
then
ronkz@gb-server:~$ -enable -minicommander
bash: -enable: command not found
ronkz@gb-server:~$ -enable-minicommander
bash: -enable-minicommander: command not found
ronkz@gb-server:~$ enable minicommander
bash: enable: minicommander: not a shell builtin
ronkz@gb-server:~$


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..
:scratch::scratch::scratch:

minicom is a command line serial communications program. With minicom you can directly talk to the modem. minicom could be used as a diagnostic tool for the modem.

I am not familiar with this particular modem. I assume the data light illuminating is a good thing but do not know why kppp isn't working.

It could be a setup problem with serial port settings. The online manual is very basic.

ARK and setserial
 

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!

install basics
 

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.
SO:
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.
OK, now.....
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!
Best wishes!
Sasha

tarballs
 

dang, grapefruit, you are clear as a bell tonight!

it never occurred to me that maybe I also need to look at a couple of other files after "extract", but that 'readme' file via Ubundu sure left me out in the woods!

I don't know how much longer I'll keep going tonight, but you deserve a pat. so here'tis.

:) 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)

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

howto? minicom or setserial
 

grapefruitTgirl, now I'm stuck. I have found/installed both setserial and minicom. by:
http://www.linux.org/docs/ldp/howto/Modem-HOWTO-10.html#ss10.1
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.

thank you again.
Ron

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.
:)

http://www.linux.com/howtos/Remote-S...-minicom.shtml

On quick glance, setserial does not look like something you need. You have a new kernel, a modern machine, and a fairly recent modem, etc..
minicom looks fairly straight forward.. I am not using a modem right now, I'm using ethernet, otherwise I'd install minicom and see how it went.
Can you get us a copy of all the errors produced when you typed 'sudo kppp' ??
There's no button as you say, however if you type something like:
sudo kppp > logfile
then all output will be directed to a file in your current directory, named logfile. Use whatever name you like. Then copy the file and post it here.

NOTE: I would consider it somewhat weird to have to be root or sudo, to use kppp.
You could locate the program itself (kppp) in the /bin or /usr or /usr/bin directory and see who owns it, and what group.
While you're at it, if you can get to the USERS/GROUP editor for the system, make sure that you as a USER are a member of the GROUP that is the modem. The group is probably named MODEM. Make sure your user account is a member of that group.

yes, minicom
 

Thanx again -

yes I think Minicom will be far the better tool, but sure not much as a gui. I'll be messing with it meanwhile to try and be more conversant with it, and await your reply.

Meanwhile I have several PCI hardmodems purchased, mostly 3cp5610A, which should bypass this serial headache. But we do need to know how to deal with this particular serial modem (actually I have TWO of them now!). My main thought is that one needs to be using the full KDE interface rather than Gnome, simply because Best Data provides instruction using KDE which doesn't seem to run right in a Gnome environment.

If it would be better with you to go private or use Yahoo! IM, it might make this easier?

Ron

Tell ya what, I agree RE: chatting on IM.. One in here would be great. I recently reinstalled my OS, without Dropline Gnome (it was a mistake installing that LOL) and for some reason I am missing the SSL component to run my IM client (Gaim). WHat I WILL do now though, is see if I can get the SSL restored/re-installed, and update here.
My email address on my LQ profile is the same as I use for IM (using MSN profile, I don't use Yahoo, but I may be able to connect to you at a Yahoo address, it's pretty capable)

Now, if you think the serial modem is a headache, you may want to think twice about using a PCI modem.
Check if it is in the HCL anywhere, and post the make/model/chipset here if you know that stuff, and I'll poke around after I mess with my SSL encryption.

Do they have a private chat here? I'll happily chat with you, but I thought we had to be paying/contributing members?
Finally, the Best Data info should work the same in KDE and Gnome; perhaps different GUI tools, but the underlying stuff should be the same.
Chat soon ;)

UPDATE: Whew! Not a matter of 'click-click' to get Gaim working.. Hadda repair my shared libraries a few times, and drill some holes through the firewall.. However, I am now back online :) so if you would like to chat, I should be there. (I think I have it set up right).

Its been so long since I've used my analog modem are the driver for you serial port loaded modprobe 8250. Im running slackware my serial driver is built into the kernel yours might be to. Here's some more info http://www.linuxquestions.org/questi...d.php?t=178924

serial ports
 

Boow:
Device Manager shows 3 serial entries
8250
16550A for ttyS1 and for ttyS0

ttyS_ links appear within /dev/
and within /sys/class/tty/

strlist for /dev/... and for /org/freedesktop/Hal/devices/pnp_PNP0501 ...

One would think that'd be enough, but it's not working! Modems are such a huge pain, huh?

none of these show my serial modem 56SX92 as connected to any of those, unless that PNP0501 thing be it - I don't know where that came from! Obviously then all that's needed is some command which will establish a link in a useful manner. I surely don't know what I'm doing on this!

Now working on that with setserial and with minicom, but thus far have not discovered the right commands, so still need help.

the link you provided may prove helpful, thanx

Unless I missed it it doesn't look like the serial module is loaded. That's needed to make the modem work.

Also, double check the tty it's being assigned to through demesg. That modem will work in Linux as it's a hardware modem. To be honest adding modems can be a real pain in the *ss but it can be dome.

Right now I'm heavily medicated but I'll take a better look at this thread tomorrow.

modprobe 8250
 

... didn't work, forgotten just what but like not found, yet platform serial 8250 shows up in device manager.

I moved my cable connection from COM2 to COM1 and bingo, the modem works on ttyS0 (moved from ttyS0), showed some life at last and dialed, altho immediately disconnects. Odd, it was fine on COM2 in winXP.

And since have run wvdialconf, which apparently cleaned up a bunch of tangles from using gnome-ppp, kppp, minicom, setserial... newbie problem. Between that and perhaps phoning my ISP I think I'll be okay now.

Linux distro-builders really need to clean up dialup configuration; the mysteries would chase most any newbie away. Nobody wants a computer these days without internet! I'm a linux newbie but a puter oldie, and this took me over a solid week. Without great help from LQ and Ubuntu forums I would never had made it.

But I figure I can get it working okay now, thanks all.

Yea lol my best data just conked out on me. It was less than a year old but what do you expect for 15 bucks. screw it now that I get 1mbit downloads on broadband.