LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Laptop and Netbook
User Name
Password
Linux - Laptop and Netbook Having a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).

Notices



Reply
 
Search this Thread
Old 08-12-2005, 02:02 PM   #1
shamrock_uk
Member
 
Registered: Dec 2003
Distribution: Debian 3.1, Ubuntu Breezy, Ubuntu Dapper
Posts: 30

Rep: Reputation: 15
Kernel compilation problems, distorted video and kernel panic


Evening all,

I've just attempted to compile a 2.6 kernel for a Slackware 10.1 installation on my Toshiba Satellite 1800 laptop - the default 2.4 kernel being the only thing stopping me from using it as my main distro.

I compiled it as per the instructions in the Slacker's Bible and both making and installing went without a hitch.

I also did as suggested and installed the kernel to a different directory than /boot (/test in this case), pointing lilo towards it, in order to avoid overwriting the existing kernel.

However, I now have two problems:

Despite my original kernel being unchanged, selecting it now gives me a kernel panic. Message is:

Code:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,4)
I'm a bit confused about this error seeing as the contents of /boot haven't changed and neither has the lilo entry for this kernel.

My second problem is when booting the second kernel
When selecting 'test' in Lilo (the new kernel) it boots successfully but with severe graphical distortions (as if the screen is repeating itself several times). Screenshot here (58k).

It's still possible to reach the CLI and, typing blind, launch X. The funny thing is that X loads perfectly and runs normally with no display problems at all.

For the record, I tried this procedure once before and this happened on my previous attempt. I was much less aggressive this time at paring down kernel size in the hope that would fix it, but obviously it didn't work! And I'm still puzzled why it's affecting my original setup.

Any explanations for this behaviour or advice on how to fix would be very welcome! Thanks in advance.

Last edited by shamrock_uk; 08-12-2005 at 02:03 PM.
 
Old 08-12-2005, 02:54 PM   #2
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
post your lilo.conf here

also i would recomed you tacking backup of lilo.conf before u do any changes
 
Old 08-12-2005, 03:33 PM   #3
shamrock_uk
Member
 
Registered: Dec 2003
Distribution: Debian 3.1, Ubuntu Breezy, Ubuntu Dapper
Posts: 30

Original Poster
Rep: Reputation: 15
Thanks for the speedy response.

Here's the contents:

Quote:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda4
label = Linux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
# Linux 2.6 bootable partition config begins
image = /test/vmlinuz
root = /dev/hda4
label = test
read-only
# 2.6 config ends
And I'll remember to backup next time

Edit - quick change of the occasional missed 'space' in the file, no change in symptoms after the correction.

Last edited by shamrock_uk; 08-12-2005 at 03:37 PM.
 
Old 08-12-2005, 04:26 PM   #4
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
well W.R T to your lilo.conf u surely have different vmlinuz file
further i would like to have a look at the O/P of

ls -l /boot
ls -l /test

regards
 
Old 08-12-2005, 05:20 PM   #5
shamrock_uk
Member
 
Registered: Dec 2003
Distribution: Debian 3.1, Ubuntu Breezy, Ubuntu Dapper
Posts: 30

Original Poster
Rep: Reputation: 15
Thanks for the help, and thanks for telling me about the -l switch, never used that before, it's handy!

I believe you've stumbled on the root of the problem, it looks like it's installed in /boot as well as a little bit in /test.

Quote:
root@darkstar:~# ls -l /boot
total 2290
lrwxrwxrwx 1 root root 37 2005-08-12 00:18 README.initrd ->
/usr/doc/mkinitrd-1.0.1/README.initrd
lrwxrwxrwx 1 root root 25 2005-08-12 13:11 System.map ->
System.map-generic-2.6.10
-rw-r--r-- 1 root root 805590 2005-01-22 21:07 System.map-generic-2.6.10
-rw-r--r-- 1 root root 512 2005-08-12 00:42 boot.0300
-rw-r--r-- 1 root root 512 2005-08-12 17:55 boot.0800
lrwxrwxrwx 1 root root 21 2005-08-12 13:11 config ->
config-generic-2.6.10
-rw-r--r-- 1 root root 50545 2005-01-22 21:07 config-generic-2.6.10
-rw-r--r-- 1 root root 5032 2004-05-21 07:19 diag1.img
-rw------- 1 root root 47616 2005-08-12 20:35 map
lrwxrwxrwx 1 root root 22 2005-08-12 13:11 vmlinuz ->
vmlinuz-generic-2.6.10
-rw-r--r-- 1 root root 1413281 2005-01-22 21:07 vmlinuz-generic-2.6.10
Quote:
root@darkstar:~# ls -l /test
total 2242
-rw-r--r-- 1 root root 790130 2005-08-12 17:55 System.map
-rw-r--r-- 1 root root 1503130 2005-08-12 17:55 vmlinuz
I guess that explains why my original boot option is screwing up. Is this situation basically non-salvagable? (A reinstall isn't a big deal yet - it's a clean system) I'll try following the guide the long way through and copy the files manually next time, perhaps that might stop it happening again...
 
Old 08-12-2005, 11:53 PM   #6
masand
Guru
 
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522

Rep: Reputation: 58
what commands did u run to compile ur kenrel

copying the files manually is more easy and safe

You can try and re-install the kernel from slack CD and where is your 2.4 kernel??

i cannot see that in /boot
did u install the 2.6 kernel from the slack CD as well??

regards
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
problems with new kernel compilation (2.4.31) fintanmcevoy Linux - Software 2 11-02-2005 10:27 AM
Kernel 2.4.22 compilation problems Arcosanti Slackware 3 04-17-2004 01:19 AM
kernel compilation problems h_lina_k Linux - Newbie 0 03-02-2004 03:23 PM
Compilation options in config and Kernel panic beejayzed Linux - Newbie 0 01-30-2004 05:56 PM
New Kernel Compilation / Panic KillerFry Linux - Newbie 1 08-28-2003 04:22 PM


All times are GMT -5. The time now is 01:04 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration