Click to See Complete Forum and Search --> : hcf modem


the_darkhorse13
10-20-2002, 09:35 PM
i have a laptop witha Rockwell HCF modem. I've downloaded the rpm and it worked great until I downloaded Firestarter. Since then KPPP won't recognize the modem anymore. its says
kpp can not find:
/dev/modem
now I've tried reinstalling the rpm and nothing changed. I went back to the Mandrake (8.2) Control Center and tried reconfiguring the modem, yet it won't let me saying that its a winmodem again. I never had this problem before. Also the text that came with the HCF rpm said tp configure it using the command hcfpciconfigure which isnt there. i found a file in the /usr/sbin folder yet it isnt an executable. The modem file in the /dev directory is there. It seems to be a link pointing to ttyS2 (my COM3 port for my modem) but there is no ttyS2 file anywhere. Should I make one myself and how would I do that? Any suggestions? Thanks

irlandes
10-20-2002, 10:13 PM
Originally posted by the_darkhorse13
i have a laptop witha Rockwell HCF modem. I've downloaded the rpm and it worked great until I downloaded Firestarter. Since then KPPP won't recognize the modem anymore. its says
kpp can not find:
/dev/modem
now I've tried reinstalling the rpm and nothing changed. I went back to the Mandrake (8.2) Control Center and tried reconfiguring the modem, yet it won't let me saying that its a winmodem again. I never had this problem before. Also the text that came with the HCF rpm said tp configure it using the command hcfpciconfigure which isnt there. i found a file in the /usr/sbin folder yet it isnt an executable. The modem file in the /dev directory is there. It seems to be a link pointing to ttyS2 (my COM3 port for my modem) but there is no ttyS2 file anywhere. Should I make one myself and how would I do that? Any suggestions? Thanks


I will try to talk you throught this step at a time. If you can't follow it, and don't get a better answer, send me a mail at brucemcgovern@earthlink.net though I am in Mexico City and only send mail once a day...

I am guessing ttyS2 is a device in /dev, because that's usually what it is.

Anyway, the command to make ttyS2 is:

mknod /dev/ttyS2 ? # #

See man mknod. The basic instructions I am giving you will work for any device, except a link. That's ln

In /dev/ with your browser, if you have a GUI, look at /dev/ttyS1 and see if it's three colored blocks, which means S1 is a block device. If so, since there is only the difference of the minor number between ttyS1 and ttyS2, then the command is:

mknod /dev/ttyS2 b # #

If it is a little monitor, the command would be:

mknod /dev/ttyS2 c # #

Now, we only have left the # #, right?

At a terminal prompt, type:

ls -l /dev/ttyS1

There will be some permissions stuff, then just before the date will be two numbers. By memory, I don't know if it will be 4 ? or a really big number (I am not in linux right now for technical reasons, or I would look it up for you.) but tty(Capital letter) is different from tty(small letter), so I am betting it won't be 4 ?.

But, whatever the numbers are for ttyS1, the first number will be the same, and the second number will be +1 for ttyS2.

Thus, it will be (hope this makes sense to you)

mknod /dev/ttyS2 b (0r c) (same number as ttyS1) (same number for ttyS2 + 1)

If ttyS1 is missing, try ttyS3 and subtract one instead of adding it; they are normally sequential.

Perhaps someone who is in linux can give you the correct numbers for # #...

There, now wasn't that simple? :-)

*****
As far as hcfpciconfigure, if you don't get an answer, send me a mail because I may lose this thread if I don't keep checking it, and I have "suggestions" on that too -- too late to type that now. It is a rpm command with parameters to list files in your hcf rpm. Or, I could check my 8.2 CD's, I suppose...

Usually, a command not found means you dn't have the rpm which contains that command file installed, but it sure sounds like it would be part of a hcf rpm, doesn't it?

Try re-installing that rpm. If it wiped out a device, who knows what it did? use upgrade mode, if that doesn't work, see man rpm and force it.

bwkaz
10-21-2002, 02:47 PM
Mandrake uses devfs. Which means your /dev directory is laid out a little differently -- but don't worry, mine is the same. ;)

My /dev/ttyS0 and /dev/ttyS1 files are actually symlinks themselves. They point, respectively, to /dev/tts/0 and /dev/tts/1. The mknod numbers (and block vs. character device status) on /dev/tts/0 and /dev/tts/1 should still be the same, though. What you'll have to do is either find an HCF driver that supports devfs (easy, but maybe not possible), or manually create the device in /dev/tts (on every boot), along with the symlink in /dev.

My devices are both character, my major number is 4, and the minor numbers are 64 and 65 for ttyS0 and ttyS1. So the mknod stuff would look like:

mknod /dev/tts/2 c 4 66

Then run ln -s tts/2 /dev/ttyS2, and try dialing again (if the ln command complains that ttyS2 already exists, then don't worry, it's actually smarter than I thought it would be).

This device might stay there over a reboot (actually, what happens is that it gets copied somewhere else and then restored after a reboot, but that's not really important), but try it to make sure.

the_darkhorse13
10-23-2002, 02:28 AM
okok, so far I've been able to create both the ttyS2 and the tts/2 but when i try and connect it goes on to say that the modem is busy all the time. I've even resorted to re-installing (hoping that something might change) yet the problem still lingers just the same. would I need to configure these devices to make them work? or do they strictly point to the com3 port. oh and to add to before, there is no ttyS1 (wierd?). I was also curious that maybe I might need to point the tts/2 to the hcfpciconfigure file? just wondering...

JP83
10-23-2002, 08:00 AM
Try download that driver in tar.gz package.

the_darkhorse13
10-24-2002, 05:42 PM
thanks bwkaz for the help on making links. that seemed to do the trick.

bwkaz
10-25-2002, 04:58 PM
Good!

You probably don't have a COM 2 serial port. If you don't, then that explains why you don't have a /dev/ttyS1 or a /dev/tts/1 device. With devfs, you don't see devices for hardware you don't have installed, which can be quite nice sometimes.