Ralph Shumaker wrote:
Gus Wirth wrote:
At 00:21 09/20/2005 -0700, Ralph Shumaker wrote:
I'm able to set up a dialup entry using fc3's network device setup
(from the menu under System Tools, IIRC). The dialup setup knows
that the modem is on ttyS4 (just like in rh9). Activating gives
none of the normal dialup sounds, in fact, no sounds at all. A few
seconds later it responds with "Failed to activate {ppp0} with error
8". What is error 8? I haven't been able to find it yet.
Try either kermit or minicom to talk directly to the modem to make
sure it
is actually talking to the modem, i.e. type in AT and get an OK back. If
you can't get that far then there is something wrong at an even more
basic
level, like ttyS4 isn't really the device or the cable became
disconnected.
Gus
/dev/ttyS4 *is* the device in rh9. (I just looked.) And that's what
fc3 jumps onto.
There is no cable. It's a card in the PC. It is the one I'm using
right now to send this email from rh9. So it's definitely *not*
disconnected.
[snip]
00:29:32 $ minicom -s
minicom: there is no global configuration file /etc/minirc.dfl
Ask your sysadm to create one (with minicom -s).
00:29:36 $ su -
Password:
[EMAIL PROTECTED] root]# minicom -s
minicom: WARNING: configuration file not found, using defaults
(I found a default of /dev/ttyS1 which I changed to /dev/ttyS4, then
saved, then exited.)
Device /dev/ttyS4 lock failed: Operation not permitted.
[EMAIL PROTECTED] root]# logout
00:36:16 $ minicom
Device /dev/ttyS4 access failed: Permission denied.
00:36:31 $
"Permission denied." and "lock failed" are presumably due to the modem
currently being in use. I'll disconnect and try it again. If that
works, then I'll reboot over to fc3 (Xen is sounding really good right
about now.) and try it there. Then I'll come back to rh9 so I can
report. Wish me well.
I decided to report what I found here on rh9 first.
00:36:31 $ minicom
Device /dev/ttyS4 access failed: Permission denied.
00:47:48 $ minicom
Device /dev/ttyS4 access failed: Permission denied.
00:47:54 $ minicom
Device /dev/ttyS4 access failed: Permission denied.
00:47:56 $ ll /dev/ttyS4
crw-r----- 1 root uucp 4, 68 Sep 21 00:47 /dev/ttyS4
00:48:07 $ ll /dev/modem
lrwxrwxrwx 1 root root 10 Aug 3 10:23 /dev/modem ->
/dev/ttyS4
00:48:20 $ su -
Password:
[EMAIL PROTECTED] root]# minicom
Welcome to minicom 2.00.0
OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Jan 25 2003, 00:15:18.
Press CTRL-A Z for help on special keys
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
at
OK
CTRL-A Z for help | 38400 8N1 | NOR | Minicom 2.00.0 | VT102 | Offline
[EMAIL PROTECTED] root]# logout
00:49:37 $
I guess wvdial is what is allowing the regular users to access the modem.
Anyway, here on rh9, su is able to get a response from /dev/ttyS4, so
now for fc3.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
