SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I recently installed Slack 9.0b (or what is to become it) and love it. I use the 1024x768 framebuffer in my text console (using rivafb), but I went to install rivaTV, drivers for a TV tuner on my Asus V7100 Deluxe Combo. In order for that install to stop whining, I had to disable the framebuffer, and now when i want it back, it does nothing. When i switch to a text console, it messes up, is in some insanely big resolution (either 640 or even 320) and creates two purple dots instead of a cursor. When i switch back to X, the server corrupts and I have to reboot (the three-fingered salute doesn't work).
I read about this in a forum, but it didn't help at all. The person who responded said to stop using NVdriver, and instead use the nv driver that comes with X. However, if it worked before I installed rivaTV, how can i make it work again?
edit: i sort of fixed it; stupid ol' me forgot to run /sbin/lilo after he edited lilo.conf. However, I still can't turn the framebuffer OFF properly....
I had a similar problem when the 2.4.X kernels first came out when I wanted to have both OpenGL support on both VT's and XFree86. After a bit of thinking, and a bit of tinkering, I realized what the cause was for crashes, lock ups and the such. . . BUT, since I was in denial I searched Google nontheless to prove my theory wrong. . . Unfortunately my theory held. . . 8^(
And this is a quote I found in Google which proved it:
Q: My system hangs when vt-switching if I have rivafb enabled.
A: Using both rivafb and the NVdriver kernel module at the same
time is currently broken. In general, using two independent
software drivers to drive the same piece of hardware is a bad
In short, you can only use one of the drivers. Since you are trying to use XFree86, then I would suggest recompiling the kernel back to using regular vesa for your vt's and use the NVdriver for your XFree86 sessions. . .
If you have a native NVidia chipset you want to use the NVdriver for you card to take full advantage of its processing power and features. The nv driver that comes with XFree86 uses a software render for OpenGL based on MESA, which means you will have OpenGL support for your card, but performance will be un-acceptable because the rendering is not performed directly by your card's native OpenGL hardware renderer.
well, i got the framebuffer in the first place with liloconfig, and it asked me if i wanted a framebuffer. the framebuffer worked before AND after i installed the NVdriver. However, when i disabled the framebuffer and booted to a shell, the shell was messed up big time. i would like to know how to properly disable the framebuffer (unloading the rivafb module at boottime) as vga=normal in lilo.conf does nothing. it works great now, but when i want to use rivaTV (the TV module I explained earlier), I need to disable the framebuffer.
interestingly enough, ive gotten so confused that i really dont know what im asking anymore.....
If rivafb is a module (&& assuming you have the vesa frame buffer present as a backup fb), then you can tell lilo to load the default vesa instead of rivafb with the following line in lilo: append="video=vesa:mtrr: pmipal: pro: ywrap" <- Get rid off the spaces . . . spaces added, otherwise you get !!!! >8^(
(Make sure you rerun lilo)
A side note(s): If rivafb is compiled in the kernel, then you can disable it with the line video=rivafb: off <- Get rid off the space. . . similar reason as above