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.
The tux graphic that appears in the upper left corner during the debian boot process stays there after the box finishes starting up. I can get rid of it by switching to terminal 2 and then comming back to terminal 1 but, is there a way to automatically clear that graphic each time the computer finishes booting?
Distribution: tried a lot of 'em, now using kubuntu
Posts: 180
Rep:
When the runlevel switches to level 2, it should go away automatically. There must be something wrong somewhere in the framebuffer or your video driver...
It goes away automatically for you? That's wierd. I have debian installed on three computers and it stays put on all of them. My main computer at home has a GeForce III and the two other computers have SiS chipset cards. All of them load in text mode only and I run startx after logging in. I think most other people run XDM so maybe they aren't aware of this problem.
I've never have that problem even though I got rid of the XDM init scripts. Radeon 8500 on a Soyo Dragon+. Actually the first thing I do after installing a new system is roll a fresh kernel with the latest, and get rid of Tux in the process.
I guess I'll have to recompile or learn to live with it. The thing is, I've never yet successfully recompiled a kernel. hehe. There are several hundred options to run though - it's very intimidating.
It's not so bad as long as you're using menuconfig or xconfig. Personally I get to just turn a lot of sections off that I don't use (like SCSI, no there, boom done with that section). Get your config set, then make dep clean bzImage modules modules_install, let it do its compiling, cp ./arch/i386/boot/bzImage /boot/vmlinuz-2.4.21, vi /etc/lilo.conf add the new image, /sbin/lilo -v, done.
The "debian-way" to recompile a kernel is to make config/menuconfig/xconfig and then make-kpkg kernel-image. Then install the kernel image deb package and all of the copying, symlinking, and editing of lilo.conf is done for you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.