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.
|
 |
08-14-2003, 11:55 AM
|
#1
|
LQ Newbie
Registered: Aug 2003
Posts: 3
Rep:
|
You have passed an undefined mode number.
OK.. I know this topic has been brought up several times in this forum but despite my efforts i cant seem to get my framebuffering to stay working.
I am using a Gateway Solo PII 333mhz, 128mb, Trident video, Slack9, default 2.4.20 kernel and the 2.4.21 kernel.
Problem seems to go like this:
-install slack9
-chose for lilo to boot 1024x768x64k
-install lilo to MBR
-everything boots/runs pefect including framebuffering
-after about 1 or 2 reboots, it gives me the You have passed an undefined mode number error and remains fucked up no matter what i do
I have tried this several times, reformatting each time as i go. I also have tried the newer kernel and that gives me the same crap
I have had a little luck however, everynow and then it DOES work (for some odd fucking reason) but it will promplty go back to not working once i reboot. X doesnt work either in the text mode.
I have tried using hex, i have tried vga=scan , all , normal , etc. nothing works. However the first time i tried putting the hex it, it did work. But again, only for one boot. I have all the stuff enabled in Console Drivers.
my lilo.conf currently looks like this: (and i get the error)
boot=/dev/hda
change-rules
reset
vga=791
image = /boot/bzImage
root = /dev/hda1
label = Linux
read-only
the only thing that gives me something other than the error message when i boot, is using a 800x600 resolution, in which case it makes my screen flash blue lines. Not exactly working either ...
Anywho, any help would be much appriciated.
Just a little note, now i cannot the other kernel to boot, it gives me the flashing blue lines.
Last edited by acidslut; 08-14-2003 at 12:05 PM.
|
|
|
08-14-2003, 10:43 PM
|
#2
|
LQ Guru
Registered: Jan 2001
Posts: 24,149
|
First of all, try to refrain from using so much slang. This is an open forum and there's no need to use such descriptive words. And yes, some do get offended, if you only knew how many emails I get of people complaining about language used in members threads.
Second about the problem. I never use 64k framebuffering when booting to a console. It either never works or just causes problems. Have you tried a lower resolution like 1024x768x256?
Have you tried changing it to vga = normal in your lilo.conf file and running lilo to make the changes? Reformatting and or changing kernels most likely isn't going to change the errors your getting.
And I'm confused when you say: X doesn't work either in text mode?
|
|
|
08-15-2003, 12:12 AM
|
#3
|
Member
Registered: Jan 2003
Location: Ballston Lake, NY
Distribution: Slackware, Debian
Posts: 665
Rep:
|
vga=normal should work, now keep in mind you'd lose the nice little penguin up in the top left  but I'm sure you';ll manage
|
|
|
08-15-2003, 12:40 AM
|
#4
|
LQ Newbie
Registered: Aug 2003
Posts: 3
Original Poster
Rep:
|
sorry about the language...i've tried vga=normal and it works, but its not the desired resolution. I'm going to try the 256 one right now so hopefully that will do the trick. And as far as X goes, it gives me the "No screens found error" when i get the "you have passed a bla bla bla" in the begining. Again sorry about the language.
**i take that back, normal doesnt work either now (this is so messed up..). Things seem to work once then quit 
Last edited by acidslut; 08-15-2003 at 10:32 AM.
|
|
|
08-16-2003, 12:25 PM
|
#5
|
LQ Newbie
Registered: Aug 2003
Posts: 4
Rep:
|
i'm having the same problem now. I installed slack on an ooold machine, just for practice since i'm newish to linux. in windows, the monitor would only allow 640x480, but I could get the 1024x768x256 framebuffer to show up nicely. Now, trying to get slackware up on my own computer, none of the framebuffer modes work. I tried every one, and reinstalled lilo each time, but received the "undefined mode" crud. and running "startx" gives a garbage screen in the "normal" or "safe" mode (text mode maybe...the one w.o tux). is this a videocard/monitor problem or is it simply something else that needs to be setup?
|
|
|
08-17-2003, 11:00 PM
|
#6
|
LQ Newbie
Registered: Aug 2003
Posts: 3
Original Poster
Rep:
|
i think i mave have found something, in the bios i changed it from LCD&CRT output to just LCD (dunno why that would affect anything but it seems to have) and now it appears to be doing the framebuffering like a good little computer...i hope it lasts :\
|
|
|
All times are GMT -5. The time now is 11:10 AM.
|
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
|
|