Forgive what must seem like a foolish question this late in the game, but
... exactly what is the *problem* with your system? The network config
report at the end of your message (the ifconfig and route output) look fine
-- both ppp0 and lo look to be set up correctly. Does the system communicate
properly over the ppp link? If not, how does it fail?
Or are you concerned only about the ugliness of the modprobe errors, even
though they reflect no actual, observed failures in your system's actual
operation? Or just the delays that are introduced by the modprobe attempts,
then failures, during boot/init?
If so, I suspect that to troubleshoot them, we'll need to see whatever
configuration file is generating them. At this point, I'm wondering if it is
something as simple as that linuxconf is trying to modprobe modules that are
already running (or in the case of ppp, is trying to modprobe a module for
something that is already compiled into the kernel).
In the end, I fear the problem is in your linuxconf settings. The fact that
it wants to rerun LILO to produce a non-working version encourages that
hypothesis. Since I don't run that app here, I am an unmlikely source for
help on problems specific to its configuration. But with this preliminary
work, perhaps someone more familiar with linuxconf will be able to focus in
on the actual problem.
BTW, this is what your reported LILO error means (for the little this
explanation is worth):
"LIL- The descriptor table is corrupt. This can either be caused by a
geometry mismatch or by moving /boot/map without running the map installer."
At 01:47 PM 7/12/00 +1000, [EMAIL PROTECTED] wrote [in part]:
...
>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.
...
>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
--
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
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
