Nick Rout wrote:
ls -l /dev/modem, and you should get something like this:All done & correct - returns to orig status:
lr-xr-xr-x 1 root root 7 Aug 10 17:17 /dev/modem ->
/dev/ttyS15 (thats all one line)
[EMAIL PROTECTED] dev]# ls -l mod*
lrwxrwxrwx 1 root root 11 Aug 12 15:55 modem -> /dev/ttyS15
lrwxrwxrwx 1 root root 11 Aug 9 20:45 modem.bak -> /dev/ttyS15 {original}
(discovered no dialout / kpppd error until "#ln -sf /dev/ttyS0 /dev/modem" issued to overwrite this again, temporarily)
now if you point kppp at /dev/modem it should work.It didn't, as before (applet used).
if it doesn't it may be because the driver isn't working (I just tried to get one of those useless things going the other day and gave up after a while, may try again), or because permissions are wrong on /dev/ttyS15.
[EMAIL PROTECTED] dev]# ls -l ttyS15 crw-rw-rw- 1 root uucp 62, 79 Aug 12 15:57 ttyS15
c? uucp(= serial comms)? no x?
Sure, to what please? Have I overwritten/damaged it already?, using cat (stalled)?Please note that permission on /dev/modem are irrelevant. permissions on a link are inherited from the target file (ie /dev/ttyS15) and what ls tells you about /dev/modem's ownership & permissions is misleading. in other words if you want to fiddle with the permissions do it to the target (/dev/ttyS15).
Well spotted, but I d-l'd & unpacked 0.9.6, which made its own dir:I see you are using version 0.9.5 of the driver. I believe there is a version 0.9.6 about somewhere on the net, I found some reference to it when I was trying to get the damn thing going the other day.
[EMAIL PROTECTED] pctel-0.9.6]# pwd /root/data/in/Modem/PCTel/pctel-0.9.6
INSTALL file confirms this ver. but..
Aug 9 20:50:58 localhost kernel: AC97 modem device found: devnum = 80000E00, devid = 1039/7013
Aug 9 20:50:58 localhost kernel: iobase_0=0xd800,
iobase_1=0xd400,irq=5 Aug 9 20:50:58 localhost kernel: PCTel driver
version 0.9.5 [5.05c-4.27.215 (09-14-2001)] (MR) (2002-01-31)
*************
..is what we get in that - dated code.
Fair comment; this one's here & running now tho, just waiting to be accessed:I nearly wrote "a version" as "aversion" which is what linux (and windows for that matter) users should have to these crap motherboards IMHO!
"Modem ready.. The modem does not respond."
* * This may well be the fault area * * Modem was installed as root, so perm's to set correctly?Part of your problems might be that you have too many levels of
symbolic linkage for the application program to plough through. I
always put the actual device node name for the physical peripheral
device in the kppp config.
Hunting my way back thru what's recently been said on kppp, looking for config file too..
- any further input can be reserved until Thursday meeting, if you so wish
- not giving up!
- if it succeeds, backward module compilitation gcc3 of gcc2.o could work for John's sm200d_lnx.o too?
Cheers all
~ Rik
