System.map problem suse-kernel 2.0.35 (LIL-)

System.map problem suse-kernel 2.0.35 (LIL-)

Post by Bjoern Guenz » Sun, 13 Sep 1998 04:00:00



Hallo!

calling for help once more...

I have downloaded the suse-kernel 2.0.35 (before that I had 2.0.33).
Compiling seemed to have gone well, but after executing 'make zlilo'
the system still booted the old kernel. So I copied the zImage to
/vmlinuz by hand, and it worked - but I recompiled it (in disregard of
the 'never touch a running system' wisdom) because I wanted yet
another module supported. Then by chance I read on in the SuSE
handbook and found that one should also copy System.map to the 'main
directory'. I assumed they were talking of /,  so I copied
/usr/src/linux/System.map to /System.map.

Since then Linux doesn't boot anymore, Lilo stops with LIL-, which
means 'the data in the map file is invalid', according to the
handbook...

Is there a way to fix the problem? I can still boot with a boot disk,
but the earlier I could get it back to normal, the better...

Many thanks in advance!

Bjoern

 
 
 

System.map problem suse-kernel 2.0.35 (LIL-)

Post by Bjoern Guenz » Sun, 13 Sep 1998 04:00:00


I have solved the probelm in the meantime - I use the Windows NT
bootmanager for booting, which means that I have to copy the
bootsector of the rootpartition to a nt-readable partition each time I
install a new kernel. I had totally forgotten about that - sorry for
wasting bandwith...

Bjoern

 
 
 

System.map problem suse-kernel 2.0.35 (LIL-)

Post by CHTvanWerkho.. » Sun, 13 Sep 1998 04:00:00


[..]
: another module supported. Then by chance I read on in the SuSE
: handbook and found that one should also copy System.map to the 'main
: directory'. I assumed they were talking of /,  so I copied
: /usr/src/linux/System.map to /System.map.

In RH System.map is a link to the map you'r using eg:
lrwxrwxrwx   1 root     root           19 Aug  9 12:54 System.map ->
System.map-2.0.35-2

: Since then Linux doesn't boot anymore, Lilo stops with LIL-, which
: means 'the data in the map file is invalid', according to the
: handbook...

Did you run /sbin/lilo after you compiled and copied to /vmlinuz ?
(I hope you cp'd the old image to a safe place first...)
Theo
--
Theo van Werkhoven              RH4.2 Linux                     Voorhout,

This will end your Windows session. Do you want to play another game?
Press any key to continue or any other key to quit.
(from r.h.f )

 
 
 

System.map problem suse-kernel 2.0.35 (LIL-)

Post by Bjoern Guenz » Tue, 15 Sep 1998 04:00:00


Many thanks for your reply! I have solved the problem in the meantime.
I did run lilo loads of times  :-) Only I forgot that I was using the
nt boot loader, too, and I needed to copy the bootsector to the nt
partition, too...

Bjoern


>[..]
>: another module supported. Then by chance I read on in the SuSE
>: handbook and found that one should also copy System.map to the 'main
>: directory'. I assumed they were talking of /,  so I copied
>: /usr/src/linux/System.map to /System.map.

>In RH System.map is a link to the map you'r using eg:
>lrwxrwxrwx   1 root     root           19 Aug  9 12:54 System.map ->
>System.map-2.0.35-2

>: Since then Linux doesn't boot anymore, Lilo stops with LIL-, which
>: means 'the data in the map file is invalid', according to the
>: handbook...

>Did you run /sbin/lilo after you compiled and copied to /vmlinuz ?
>(I hope you cp'd the old image to a safe place first...)
>Theo
>--
>Theo van Werkhoven          RH4.2 Linux                     Voorhout,

>This will end your Windows session. Do you want to play another game?
>Press any key to continue or any other key to quit.
>(from r.h.f )

 
 
 

1. Newbie-Having a problem mounting joliet with S.u.S.E. 5.3 (kernel 2.0.35)

Every information that I could find tells me that my current kernel
version should support the Joliet filesystem.  However, when I
recompiled the kernel, the make config did not ask me if I wanted joliet
support.  (It did ask me for a bunch of other file systems)

When I reboot, I try the following command:

mount -t joliet /dev/hdc1 /cd

and the system tells me it does not support joliet.

Yes, I have the correct paths.  I was able to mount an iso9660 cd with
the same paths.
I have 2.0.35 kernel.
I have S.u.S.E. 5.3.

I know I am doing something wrong, and I suspect that it is one of those
little things that will make me bang my head against the wall when I
find the answer.

Possible solutions:

1) The make config utility is referring to joliet by another name
2) The mount command expect another name than "joliet"
3) Your input...

Can anyone help?

ChrisB

2. Channel bonding kernel crash, workaround

3. System.map not parseable as a System.map

4. Sound on the B&W

5. new kernel OK but what about system.map, kernel.h and module-info

6. PostgreSQL

7. Kernel Upgrade problem: Incorrect kernel version with /boot/System.map

8. Bizarre 3.1.2b problem with Mach64

9. Kernel 2.0.35 - Kernel 2.0.36

10. Problems Compiling the kernel 2.0.35

11. problem to compile kernel(2.0.35)

12. iopl problem after rebuilding 2.0.35 kernel?

13. Kernel 2.0.35 Compile Problems