LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-24-2004, 03:00 PM   #1
MDesigner
Member
 
Registered: Jun 2004
Distribution: openSUSE 10.2
Posts: 69

Rep: Reputation: 15
Slackware 10 - Botched kernel 2.6.7 upgrade


I installed Slackware 10, and then followed the instructions on CD2 to install the new kernel. I installpkg'd the kernel and kernel modules, went to /boot, ran the mkinitrd (with the options specified in the README), added a new entry in lilo.conf to point to /boot/initrd.gz, ran lilo, rebooted. Now, whether I try to boot into 2.4 or 2.6.7, the machine locks up. These are the last few lines I get before lockup:

PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Transparent bridge - 0000:00:1e.0
PCI: Using IRQ router PIIX/ICH [8006/2440] at 0000:00:1f.0
vesafb: probe of vesafb0 failed with error -6
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)

Any idea where I went wrong? And how I should go about fixing this?

Thanks!
 
Old 06-24-2004, 03:40 PM   #2
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,286

Rep: Reputation: 69
try add append="vga=ask" to your lilo config file because it seems that the framebuffer feature does not load.
 
Old 06-24-2004, 03:43 PM   #3
MDesigner
Member
 
Registered: Jun 2004
Distribution: openSUSE 10.2
Posts: 69

Original Poster
Rep: Reputation: 15
OK. I'll have to reinstall Slackware since I can't get into it anymore
 
Old 06-24-2004, 04:26 PM   #4
Toth
Member
 
Registered: Aug 2003
Posts: 83

Rep: Reputation: 15
Quote:
Originally posted by MDesigner
OK. I'll have to reinstall Slackware since I can't get into it anymore
No you don't!

Just read the message that pops up on the Slackware boot screen. Basically, enter something like the following at the boot prompt:

bare.i noinitrd root=/dev/hdaX ro

where /dev/hdaX is your root partition. This will load up your new Slackware system using the bare.i kernel from the CD. From there you can attempt to fix whatever is causing your system not to boot and then try booting from the hard disk again.
 
Old 06-24-2004, 04:40 PM   #5
MDesigner
Member
 
Registered: Jun 2004
Distribution: openSUSE 10.2
Posts: 69

Original Poster
Rep: Reputation: 15
OK. I tried putting this in the 2.6.7 entry in lilo.conf:

append = "vga=ask"

lilo didn't like it. So I put just "vga=ask" in the global settings at the top, instead of vga=773 (1024x768x256). It never asked me anything, but it booted just great!

root@opus:/home/samh# uname -a
Linux opus 2.6.7 #1 Wed Jun 16 16:23:03 PDT 2004 i686 unknown unknown GNU/Linux

Woohoo.. Thanks!
 
Old 06-24-2004, 05:27 PM   #6
MDesigner
Member
 
Registered: Jun 2004
Distribution: openSUSE 10.2
Posts: 69

Original Poster
Rep: Reputation: 15
It's doing it again. Arrrghh.. 2.6.7 doesn't agree with me.
 
Old 06-25-2004, 05:16 AM   #7
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,286

Rep: Reputation: 69
And what is the error displayed at boot now ?
 
Old 06-25-2004, 08:57 AM   #8
MDesigner
Member
 
Registered: Jun 2004
Distribution: openSUSE 10.2
Posts: 69

Original Poster
Rep: Reputation: 15
Same error
 
Old 06-25-2004, 09:01 AM   #9
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,286

Rep: Reputation: 69
Can you put your lilo config here and the output for ls /boot ?
 
Old 06-25-2004, 11:06 AM   #10
MDesigner
Member
 
Registered: Jun 2004
Distribution: openSUSE 10.2
Posts: 69

Original Poster
Rep: Reputation: 15
OK I reformatted, tried again.. got 2.6.7 working, but I had it working before at one point too.. so..doesn't mean much

At this point of 2.6.7 working fine, here's the info you requested:

lilo.conf:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# 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
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda1
label = Linux
read-only
# Linux bootable partition config ends

# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.7
initrd = /boot/initrd.gz
root = /dev/hda1
label = Linux267
read-only
# Linux bootable partition config ends

And here's ls /boot:
README.initrd@ config@ map
System.map@ config-generic-2.6.7 vmlinuz@
System.map-generic-2.6.7 config-ide-2.4.26 vmlinuz-generic-2.6.7
System.map-ide-2.4.26 diag1.img vmlinuz-ide-2.4.26
boot.0300 initrd-tree/
boot_message.txt initrd.gz
 
Old 06-25-2004, 11:19 AM   #11
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,286

Rep: Reputation: 69
That seems ok,
Can I suggest you to leave "windows habits" which consist to solve problems by formating the drive. In GNU/Linux you can always repair system without reformating and often without rebooting.
 
Old 06-25-2004, 11:28 AM   #12
MDesigner
Member
 
Registered: Jun 2004
Distribution: openSUSE 10.2
Posts: 69

Original Poster
Rep: Reputation: 15
Yeah, it seems to work fine now.. I think the vga=773 (1024x768x256) was making the system throw a fit. No surprise though, the video card blows

So.. if not reformat, what do you suggest? How exactly do I repair problems? (especially if I was unable to even boot normally)...
 
Old 06-25-2004, 12:42 PM   #13
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,286

Rep: Reputation: 69
You can boot with the 2nd slackware CD and then use command from this cd, for mount your hard drive etc.. You can then edit config, check logs...

[edit]
You should make a floppy boot also try /sbin/makebootdisk

Last edited by keefaz; 06-25-2004 at 12:45 PM.
 
Old 06-25-2004, 05:12 PM   #14
marsques
Member
 
Registered: Jan 2004
Location: Manchester
Distribution: slackware...
Posts: 343

Rep: Reputation: 31
funnily enough i did have a similar kinda problem... after booting the PC with kernel 2.6.7 the screen went blank... but after a couple of minutes when i enter ma user name and password and type "startx" x loads fine and i can carry on using linux...

but after editing lilo just to boot normal without doing any fancy to the screen its working fine...

is there anything special u need to do to lilo for it to boot say

1024x768x256 with the 2.6.7 kernel?

coz 2.4.25 boots just fine with the above option (773)
 
Old 06-25-2004, 05:16 PM   #15
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,286

Rep: Reputation: 69
marsques> Have you got a nvidia card ? If so you have to compile kernel with vesa framebuffer support but no vga framebuffer.
 
  


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
botched upgrade: is this a good fix? yocompia Slackware 2 04-06-2007 03:18 PM
Slackware Kernel upgrade carlosinfl Slackware 8 06-18-2005 12:33 AM
Slackware 10.1 kernel upgrade killed my network - help! clowntoe Slackware 13 06-10-2005 11:52 AM
adaptec.s kernel upgrade for slackware? cybrjackle Slackware 2 12-09-2003 07:58 PM
Botched kernel compile, recover from CD? Zb7 Slackware 9 09-02-2003 09:32 PM


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

Main Menu
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