Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
02-03-2005, 11:32 AM
|
#1
|
LQ Newbie
Registered: Oct 2004
Posts: 23
Rep:
|
Failed attempt at 2.6.10
Alright, apparently I'm not as cool as I thought I was.
So I downloaded the new kernel sources and attempted to install it. Everything compiled fine, I edited lilo.conf - no problems.
When I boot - nothing displays on the screen. It appears to be loading stuff for a while, but at some point it just stops. It may have enetered X, but I don't really know. I can't SSH into it, so I have no access.
Thankfully, I can boot into the older kernel. In my somewhat shortsighted brilliance, I figured I could fix things by copying the older kernel to replacing the new kernel and attempt to re-build 2.6.10.
That failed. It never gets past the Lilo screen. So, how do I properly restore the older kernel? And any ideas as to what the hell I did wrong with the older one?
I'm sure this isn't all that helpful without any config files, but I don't have right now.
I guess my main concern is that if I re-compile 2.6.10 and install it, that my working 2.4.26 will be over-written since it's "old." And that's a big no-bueno 'cause I don't have all that much faith in the 2.6.10 working on the first try. So how do I properly restore the 2.4.26 to the boot instead of the old.
I hope that's not all mindless dribble. Let me know. Thanks.
|
|
|
02-03-2005, 11:45 AM
|
#2
|
Senior Member
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721
Rep:
|
hi there,
so, you can startup with a floppy/cd .
then, when you build a new kernel, copy it to " /boot/vmlinuz-2.6.10 "
instead of overwriting the old one.
then you've got to edit your " lilo.conf " file to add it ( so at boot you'll have choice )
you need to run " lilo" to write a new mbr acc. to the new settings.
... and for the " blackscreenboot "; i think you need frame-buffer-support
build in ( not as a module )
edit: i think you just need to run " #lilo " to boot your old kernel again
( as you copied the old kernel again to /boot )
egag
Last edited by egag; 02-03-2005 at 11:48 AM.
|
|
|
02-03-2005, 02:30 PM
|
#3
|
Member
Registered: Aug 2003
Location: Akron, OH
Distribution: Slackware 14.2-stable, Ubuntu 16.04 LTS
Posts: 401
Rep:
|
I definitely agree with egag ... I used my 2.4 .config files as starting points for my initial 2.6 builds and the "blank screen" was one of the first problems I faced. You must indeed build framebuffer support into your kernel for it to work properly. That or you must put "vga = normal" in LILO to boot into a normal text-based screen.
|
|
|
02-03-2005, 04:17 PM
|
#4
|
Member
Registered: Nov 2004
Location: Columbus, Ohio
Distribution: Slackware-Current / Debian
Posts: 795
Rep:
|
yessir, definately the framebruffer
|
|
|
02-03-2005, 05:54 PM
|
#5
|
Member
Registered: Jan 2004
Location: Atlanta, GA
Distribution: Slackware 12.2
Posts: 82
Rep:
|
Do not start with your 2.4.x config file for kernel 2.6.10. You need to build in VGA and frame buffer into your kernel. I had the same problem and no one apparently knew the exact configuration. Ok, here's what I have in my kernel enabled in order to take advantage of higher resolution in my console mode:
{2.6.10}
Code:
Device Drivers ->
Graphic Support ->[*] Support for frame buffer devices
<M> VGA 16-color graphics support[*] VESA VGA graphic support
--- console display driver support ->[*] Video mode selection support
<*> Framebuffer console support[*] Select compiled-in fonts[*] VGA 8x8 font[*] VGA 8x16 font
|
|
|
02-08-2005, 08:24 PM
|
#6
|
LQ Newbie
Registered: Oct 2004
Posts: 23
Original Poster
Rep:
|
Re: Failed attempt at 2.6.10
yes, running lilo fixed my booting the old kernel problem.
and yes it did take me over a week to try it. i'm just not at home enough
now let's try this rebuilding w/ framebuffer built in
is there a starter config file anywhere I can use?
thanks a bunch!
-Jason
Quote:
Originally posted by icpsvt
Alright, apparently I'm not as cool as I thought I was.
So I downloaded the new kernel sources and attempted to install it. Everything compiled fine, I edited lilo.conf - no problems.
When I boot - nothing displays on the screen. It appears to be loading stuff for a while, but at some point it just stops. It may have enetered X, but I don't really know. I can't SSH into it, so I have no access.
Thankfully, I can boot into the older kernel. In my somewhat shortsighted brilliance, I figured I could fix things by copying the older kernel to replacing the new kernel and attempt to re-build 2.6.10.
That failed. It never gets past the Lilo screen. So, how do I properly restore the older kernel? And any ideas as to what the hell I did wrong with the older one?
I'm sure this isn't all that helpful without any config files, but I don't have right now.
I guess my main concern is that if I re-compile 2.6.10 and install it, that my working 2.4.26 will be over-written since it's "old." And that's a big no-bueno 'cause I don't have all that much faith in the 2.6.10 working on the first try. So how do I properly restore the 2.4.26 to the boot instead of the old.
I hope that's not all mindless dribble. Let me know. Thanks.
|
|
|
|
02-08-2005, 09:25 PM
|
#7
|
Member
Registered: Feb 2004
Location: Canada
Distribution: Slackware
Posts: 479
Rep:
|
The exact same thing happened to me. I had to change my lilo config. Nothing shows up but it still works ... boot up and wait a bit until ur sure it's booted. Then type in user name and password
then type startx and X will boot up.
edit /etc/lilo.conf and look around and change whatever looks close to this to "vga = normal" (mine was vga = 773 I changed to vga = normal and everything was ok)
|
|
|
All times are GMT -5. The time now is 12:31 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|