DebianThis forum is for the discussion of Debian 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.
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.
O.k. i've compiled the kernel and added the vga and other stuff to the menu.lst
but the screen stays black.
Also when it's done booting i'm in the dark
When i remove the options all is well but no frameoverlay
Ahaaaa!!!
(you might want to edit this in your original post)
In order to get the framebuffer working with a NVIDIA card you should also load rivatnt as a Module.
Leaving it out results in no framebuffer at all.
Compiling it into the kernel results in no longer being able to install your nvidia driver
Well, when I posted this I thought I'd found something that worked.... It does work I guess, but not the framebuffer in all cases. Can you post your details for chipset and what you entered in /boot/grub/menu.lst to get the framebuffer working? I'll edit the original post so that hopefully someone else is not lead down the wrong path.
My desktop has an nforce2 chipset with integrated graphics and what I did in the original post works (including installing the Nvidia drivers).
I installed the testing kernel sources instead of the unstable ones.
And i didn't bother to install the win4lin stuff
In menuconfig i made sure i hade rivatnt driver installed as a loadable module and not compiled into the kernel. hence the M
You need it for the rivafb module wich provides the framebuffer (hence rivafb)
Quote:
Graphics support --->[*] Support for frame buffer devices[*] VESA VGA graphics support[*] VGA
<M> RIVA tnt (or something nvidia like) !!!!! Watch it it's an M not a star!!!!
Console display driver support --->[*] Video mode selection support
<*> Framebuffer Console support[*] Select compiled-in fonts[*] VGA 8x8 font[*] VGA 8x16 font
Logo Configuration --->[*] Debian GNU/Linux Open Use logo (NEW)
And followed your instructions from there on.
I have a geforce ti4200 card
Bootsplash also works now except for the progress bar once i figure out how that works i'll post a howto
I had a similar problem and it took me a while to find the solution.
Basically, you need to make sure that support for whatever type of device your root partition is mounted on is compiled into the kernel (NOT as a module).
For me, this involved changing some of the IDE drivers from module to built-in. For some reason, the default setting has them as modules.
I can look into the details when I get home from work if it would help anyone.
a simple stupid question
¿can I just remove the kernel source after a succesful compilation? It uses a lot of disk space and I don't plan to compile it again
thanks
Yes, you can remove the kernel source tree, provided you won't want to compile anything against it (future kernel modules). Also, you don't need to keep it in /usr/src. You can keep the source tree in your /home directory and compile the kernel as a user. Only need to be root to install the kernel, not build it...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.