Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 07-14-2004, 12:41 PM   #1
LQ Newbie
Registered: Jul 2004
Posts: 19

Rep: Reputation: 0
Question Console Resolution changed after rebuild

I'm running Slackware 10.0 on a Dual P3 Xeon system.

As a newb exercise, I was rebuilding the kernel. My standard console display, including all the startup messages is 50 lines x132 characters. I built a copy of the kernel, as a test, and the resolution stayed the same.
I went through a few files (sys.c, dma.c, timer.c; chosen b/c they had other printk's right there and so would probably not flood my screen) and added a printk or 2, and rebuilt the kernel.

This new kernel's console for some reason has a 80x25 resolution. I've been though lilo.conf and tried out various settings (vga=normal, vga=773, vga = 771, append="vga=ask"), but nothing changes it. And thinking about it, lilo.conf should affect all 3 kernels (the original, the copy, and the modified with printk's), whereas I'm only getting this issue in one. The video card can't be having issues because the higher resolution works using the other kernels. So it has to be an issue, logically it seems, with the kernel, but I didn't change anything, just added a few printk's (which, btw, do show up once in a while, so I know it worked).

This is mainly a minor inconvenience and a lot of curiosity, because no edits I did to those files (only adding printk's, and I didn't bump anything out of a loop or if by adding that line in) should have any effect on the console resolution.

Thanks in advance,
Old 07-14-2004, 12:59 PM   #2
LQ Newbie
Registered: Jul 2004
Posts: 19

Original Poster
Rep: Reputation: 0
Ah, and another random effect: on all kernels, I can't get a network connection. None whatsoever. when I try to ping the router (its worked in the past), I get

connect: Network is unreachable

Old 07-14-2004, 02:54 PM   #3
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 911Reputation: 911Reputation: 911Reputation: 911Reputation: 911Reputation: 911Reputation: 911Reputation: 911
You forgot to mention which version of the
kernel, and whether you were using the source
shipped with Slack, or a tar-ball from,
and in either case whether you have re-used the
.config file that had been used by Slack, or started
one from scratch. That all said I may have to add that
Slack's kernels by default aren't SMP capable ...


P.S.: If you need to add some info you
can actually just edit your post, no need
to post a response to yourself ;)

Last edited by Tinkster; 07-14-2004 at 02:55 PM.
Old 07-14-2004, 03:45 PM   #4
LQ Newbie
Registered: Jul 2004
Posts: 19

Original Poster
Rep: Reputation: 0
Ah, its kernel version 2.4.26, I've enabled SMP support using menuconfig, I believe its downloaded from and burned onto 2 CD's, but am not sure since I got them from a friend, and the config file was the one given by Slack, and modified for the multiple kernels as well as when I was tinkering with the vga settings.
Right now, it reads:

# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
timeout = 2400
# Override dangerous defaults that rewrite the partition table:

# 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/hda2
label = Linux
image = /boot/kernelChanged #this is the one with printk added
root = /dev/hda2
label = changed_kernel
image = /boot/newkernel #this is the copy
root = /dev/hda2
label = copy_kernel
# Linux bootable partition config ends

EDIT: And btw, I have Slack 10 running on another dual system, without the SMP enabled, and it works, so I don't think that is the source of the problem.

Thanks! and sorry for the lack of info,

Last edited by Dagda99; 07-14-2004 at 03:46 PM.
Old 07-15-2004, 04:12 PM   #5
LQ Newbie
Registered: Jul 2004
Posts: 19

Original Poster
Rep: Reputation: 0
Apparently the framebuffer got disabled for the new kernel.
To reset it, in menuconfig a couple settings must be enabled: was extremely helpful.


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
Changed resolution in Xwindow, now I can't see tcsanadi Red Hat 1 10-25-2005 12:58 PM
Help! I changed the resolution to the Xtermnal. fidelfs Linux - General 1 06-09-2004 12:35 AM
lose console framebuffer on kernel rebuild drigz Linux - General 4 06-05-2004 05:12 AM
I changed the resolution and now Gnome crashes Neoslash Fedora 2 04-03-2004 07:52 PM
changed to unsupported screen resolution!!! edzvan Linux - Newbie 1 03-30-2004 09:09 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 02:39 PM.

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