[i have edited this, as it's starting to baalllloooon, I hope the reformat
doesn't annoy]
>
> One very odd thing is this line:
>
>>Jul 12 10:34:40 localhost modprobe: modprobe: Can't locate module /dev/ttyS1
>
> Since /dev/ttyS1 is not a module (it's a device), modprobe should never be
> trying to locate it. This suggests to me that you have some fundamental
> configuration error that is not very well identified by the log output you
> sent us. Perhaps we need to see the script that runs pppd (intact EXCEPT
> that you should replace any password with Xs).
>
> More generally, I'm not sure why linuxconf would generate a hundred or so
> modprobe messages ... or any modprobe messages, for that matter ... I don't
> use linuxconf myself ... but it would be more instructive to see the
> messages generated during boot/init by modprobe or insmod than this batch.
linuxconf is one of the last things to start during the boot/init process.
> Finally, tell us some basics: what Linux distribution and version? What
> steps did you follow in compiling your kernel? Do the modules on the system
> match the kernel (does /lib/modules/2.2.16/ exist? did you do a "make
> modules_install" as the last step in your kernel compile process, before you
> moved the new kernel into place and re-ran lilo?)?
I'm running RedHat 6.2, kernel 2.2.16. My original original, full (c.d.)
install was RH6.0, 2.2.5, but I have since updated. I updated modprobe when I
did this (2.3.10). My new-kernel compilation(s) have been with make xconfig,
compiling _in_ ppp support, as well as support for the kernel module-loader.
selected highlights from my saved kernel config file /usr/src/linux/mineconfig:
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
CONFIG_KMOD=y
(I had even more trouble with modules when I enabled CONFIG_MODVERSIONS.
I'm not sure why as the help-file suggests this would make it possible to use
older modules...?)
# Network device support
#
CONFIG_NETDEVICES=y
[...]
# CONFIG_FDDI is not set
# CONFIG_PLIP is not set
CONFIG_PPP=y
[...]
CONFIG_FAT_FS=m
# CONFIG_MSDOS_FS is not set
CONFIG_VFAT_FS=m
CONFIG_ISO9660_FS=m
and so on..
after compiling I did a make modules make modules_install, and the directory
/lib/modules/2.2.16/*/* accurately reflects my compilation, as does the
modules.dep file. the iso9660 module, for instance, works fine. I copied the
bzImage from the compile to /boot and made an entry for it in /etc/lilo.conf:
image = /boot/bzImage
label = aAaaaRk
vga = normal
root = /dev/hda7
then reran lilo, (which, actually, linuxconf is constantly nagging me to let it
run, which, if I let it, gives me the lilo prompt at boot of LIL-, which freezes
the boot process)
> Similarly, the output of "ifconfig -a" and "route -n" would tell us (and
> you) more about your connectivity than the log messages.
this is my /etc/ppp/ppp-on script (which is exactly the same as
/usr/sbin/ppp-on), without the verbose comments:
#!/bin/sh
TELEPHONE=9664-5100
ACCOUNT=integer
PASSWORD=[XXXXX]
LOCAL_IP=0.0.0.0
REMOTE_IP=0.0.0.0
NETMASK=255.255.255.0
export TELEPHONE ACCOUNT PASSWORD
DIALER_SCRIPT=/etc/ppp/ppp-on-dialer
exec /usr/sbin/pppd debug lock modem crtscts /dev/ttyS1 115200 \
asyncmap 20A0000 escape FF kdebug 0 $LOCAL_IP:$REMOTE_IP \
noipdefault netmask $NETMASK defaultroute connect $DIALER_SCRIPT
_______e_n_d_s___h_e_r_e_________
My /etc/ppp/ppp-on-dialer script looks as it does in any of the HOWTO docs.
The output of ifconfig -a after a very quick session online
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:704 errors:0 dropped:0 overruns:0 frame:0
TX packets:704 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
ppp0 Link encap:Point-to-Point Protocol
inet addr:203.109.153.98 P-t-P:203.56.11.99 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:552 Metric:1
RX packets:685 errors:0 dropped:0 overruns:0 frame:0
TX packets:584 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
output of route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
203.56.11.99 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 203.56.11.99 0.0.0.0 UG 0 0 0 ppp0
after all this, I should say that I've since been to the kppp website and have
found out that the reporting of no ppp-kernel support is a bug that has since
been fixed, =). but this knowledge doesn't change the fact that modprobe is up
to some funny stuff, running far optimally.
sorry if this is overkill or underinformative. let me know if I should a) give
you more info, or b) let sleeping dogs lie.
takcq.
d.
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
