Forum Home
Press F1
Thread ID: 15778	2002-02-17 00:08:00	Linux & winmodem still	Guest (0)	Press F1

Post ID	Timestamp	Content	User
35973	2002-02-17 00:08:00	Hi and thanx to everyone who helped, although I still can't get it to work. Here goes I ran the 'ls -l /dev/modem' command which returned the following; 'lrwxrwxrwx 1 root root 12 feb 17 11:28 /dev/modem -> /dev/ttyHSF0' which was highlighted in red and flashing. Any idea what it means? I still get the same error message when I try connecting with the dialer. thank you in advance Nigel T	Guest (0)
35974	2002-02-17 01:33:00	What distributions are you running? In Red Hat 7.2 I had to download the src.rpm files and rebuild it then install the rpm file it created. In the console it told me that /dev/ttyHSF0 would be /dev/modem I then setup the dialer using instructions from the HOWTOS to set up RP3. I think the HOWTOS were on PPP. I did everything as root in a console. When I tried the X-Window to set it up before it didn't work for me. (Well it dialed out but I couldn't use my web browser)	Guest (0)
35975	2002-02-17 02:11:00	redhat 7.1 is what I am using, if that helps.	Guest (0)
35976	2002-02-17 03:21:00	Looking good, Nigel. That link is right. I think that the problem now is that you aren't loading the 'module' (Linux name for loadable driver). The Linux people had a script to do this; I don't know how the manufactrurers do it. You might need a command like 'insmod xxblah' of 'depmod xxblah' ... Have a read (again) of the Conexant+Rockwell-modem-HOWTO and the Linmodem-HOWTO documents. I don't think you will have to compile your module. If the RPM system loaded it without complaints it should be OK. Another command: 'lsmod' tells you what modules are loaded at the moment. Look for the module name: 'locate *.o | more', or 'find /usr/lib/modules -name *.o | more'. You should recognise a suitable name. Then 'su -', then 'insmod nameofit' or 'depmod nameofit' (without the '.o') -- whichever works without errors. Then 'lsmod' to see if it's there. Then try using the modem again. Keep at it -- obviously we're nearly there. You might understand why I use external modems. Things which are 'possible' aren't always desirable. Simple is always better.	Guest (0)
35977	2002-02-17 03:22:00	Its highlighted because the link is broken because /dev/ttyHSF0 doesn't exist. My guess would be that the driver hasn't been installed correctly.	Guest (0)
35978	2002-02-17 03:44:00	P.S. Ooops -- thanks B M -- thought it was just an odd LSCOLOR set. However, the device entry /dev/ttyHSF0 does exist, so the installation must have got far enough for the link to have been created. So I think the module will have been stored. But I'm pretty sure that the module is not being installed automatically. Sure that the RPM did not give error messages, Nigel?	Guest (0)
1