On 12-Jul-00 Ray Olszewski wrote:
> 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?
>
Yes it does, I apologise for wasting bandwidth on a 'problem' that I've since
found out is a bug in the earlier version of kppp that I was using.
> 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?
>
modprobe has no visible problems during boot/init, everything seems to boot
fine.
I don't think it's normal operation, but I guess it's not really a *problem*
if, whenever I exit linuxconf, modprobe takes about 40 seconds looking for ppp0
and lo. or that it can't find /dev/ttyS1 when I connect to the internet. It all
seems pretty weird, but you're right: there are no actual, observed failures in
my system's operation.
> 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).
I don't know, but I thought lo and ppp0 are network interfaces, not modules?
and, forgive me my naivety, /dev/ttyS1 is my modem device?
Gee, now I'm _really_ confused, I think I should go away and learn a bit more
about what modprobe wants when it looks for these things; and how to ask
questions that are a little more directed. I am sorry if I seem a little stupid
at the moment. However, if you will please bear with me while I intellectually
undress a little more...
>
> 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."
>
this is most certainly the case. when I recompiled the kernel I copied the
bzImage to /boot/ and added an entry for it in lilo.conf before rerunning lilo.
But I don't know anything about 'the map installer' and I fear my /boot/ folder
has become a bit of a mess. here's what it looks like:
drwxr-xr-x 2 root root 1024 Jul 12 20:49 .
drwxr-xr-x 25 root root 1024 Jun 27 19:19 ..
-rw------- 1 root root 32768 Jul 12 20:49 System.map
-rw-r--r-- 1 root root 151249 Jul 7 17:52 System.map-2.2.16
-rw-r--r-- 1 root root 186704 Jun 2 1999 System.map-2.2.5-22
-rw-r--r-- 1 root root 165704 Jun 2 1999 System.map-2.2.5-22BOOT
-rw-r--r-- 1 root root 197682 Jun 2 1999 System.map-2.2.5-22smp
-rw------- 1 root root 40448 Jun 28 18:30 bkupSystem.map-2.2.16
-rw-r--r-- 1 root root 512 May 13 06:35 boot.0300
-rw-r--r-- 1 root root 4544 Apr 13 1999 boot.b
-rw-rw-r-- 1 root root 507775 Jul 7 18:40 bzImage
-rw-r--r-- 1 root root 612 Apr 13 1999 chain.b
-rw-r--r-- 1 root root 470247 Jun 30 23:01 kernel-2.2.16
-rw-rw-r-- 1 root root 690251 Jun 27 17:36 kernel-2.2.5
lrwxrwxrwx 1 root root 23 Jul 1 09:29 map ->
/boot/System.map-2.2.16
lrwxrwxrwx 1 root root 20 May 13 06:34 module-info ->
module-info-2.2.5-22
-rw-r--r-- 1 root root 11773 Jun 2 1999 module-info-2.2.5-22
-rw-r--r-- 1 root root 11773 Jun 2 1999 module-info-2.2.5-22smp
-rw-r--r-- 1 root root 620 Apr 13 1999 os2_d.b
-rwxrwxr-x 1 root root 1106920 Jul 7 17:53 vmlinux
-rwxrwxr-x 1 root root 1163920 Jun 30 23:48 vmlinux-2.2.16
-rwxr-xr-x 1 root root 1469282 Jun 2 1999 vmlinux-2.2.5-22
-rwxr-xr-x 1 root root 1275613 Jun 2 1999 vmlinux-2.2.5-22BOOT
-rwxr-xr-x 1 root root 1568295 Jun 2 1999 vmlinux-2.2.5-22smp
lrwxrwxrwx 1 root root 16 May 13 06:34 vmlinuz ->
vmlinuz-2.2.5-22
-rw-r--r-- 1 root root 617297 Jun 2 1999 vmlinuz-2.2.5-22
-rw-r--r-- 1 root root 530924 Jun 2 1999 vmlinuz-2.2.5-22BOOT
-rw-r--r-- 1 root root 640899 Jun 2 1999 vmlinuz-2.2.5-22smp
-rw-rw-r-- 1 root root 507777 Jul 7 18:39 zImage
-rwxr-xr-x 1 root root 451797 Jul 7 17:50 zImageold
I really can't remember what I've changed around here. I'm sure I changed,
amongst other things, the symlink for 'map' -probably incorrectly. there are
things in there that I think are wrong, like maybe the bzImage needs to be
executable, as the 'zImageold' is?
thankyou for your patience with my ignorance.
d,
> 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.
> ....
__________________________________________________
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
