* Console Framebuffer Issues / GeForce4 - Red Hat stock kernel 2.4.20-13.9
@ 2003-05-24 17:39 Robert Keith Vaughan
2003-05-24 17:58 ` Gutko
0 siblings, 1 reply; 2+ messages in thread
From: Robert Keith Vaughan @ 2003-05-24 17:39 UTC (permalink / raw)
To: linux-fbdev-devel
Hello:
I apologize if this is the wrong list to post to, but it was suggested in a
post I dug up through a google search. I normally like to figure things out
for myself, but this one is really starting to tick me off.
I am using Red Hat 9.0 with the stock 2.4.20-13.9 kernel. I am attempting to
get framebuffer support working on the console with little success. The
relevant PC specs are as follows:
Athlon XP 2000+
1 GB RAM
Geforce4 ti4400
From what I have been able to ascertain, vesafb is compiled into this kernel
instead of loading as a module. I looked at the information for the rivafb
driver and it doesn't appear to support the GeForce4 cards. What info I have
been able to dig up suggests that you can get non-accelerated framebuffer
support for the GeForce4 using vesafb. I cannot, however, get it to work.
I have tried to pass the following kernel arguments via grub. All I get is a
blank screen"
video=vesafb,xres:1024,yres:768,bpp:16 vga=791
AND (just in case I COULD get the rivafb module to support it)
video=rivafb,xres:1024,yres:768,bpp:16 vga=791
I have played around with the bpp and vga= settings (trying 8, 16 and 24
respectively) . No luck. Get a blank console up until kdm loads. And I
don't see anthing in the dmesg logs either. Sigh.
When I issue fbset I get the following error:
open /dev/fb0: No such device
Which leads me to believe that the stock kernel isn't seeing a framebuffer
device despite the fact that vesafb is compiled in.
I have not yet tried to compile a custom kernel precisely because of 1.)
vesafb is complied into this kernel, AND 2.) Nothing I have read seems to
indicate that compiling rivafb into the kernel will help with my issue ( and
I have not been able to get rivafb to load as a module in any event...)
So, I am stumped. I'm sure its something stupid on my part....but could
anyone tell me A.) what I am doing wrong here, and/or B.) if anyone has
gotten console framebuffer support running on a stock Red Hat kernel...
Thanks for putting up with the long winded (and I sure stupid) questions..
Keith Vaughan
--
***************************************
Robert Keith Vaughan, CISSP
E-mail: rkvaughan@carolina.rr.com
**************************************
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Console Framebuffer Issues / GeForce4 - Red Hat stock kernel 2.4.20-13.9
2003-05-24 17:39 Console Framebuffer Issues / GeForce4 - Red Hat stock kernel 2.4.20-13.9 Robert Keith Vaughan
@ 2003-05-24 17:58 ` Gutko
0 siblings, 0 replies; 2+ messages in thread
From: Gutko @ 2003-05-24 17:58 UTC (permalink / raw)
To: linux-fbdev-devel
Robert Keith Vaughan wrote:
> Hello:
>
> I apologize if this is the wrong list to post to, but it was suggested in a
> post I dug up through a google search. I normally like to figure things out
> for myself, but this one is really starting to tick me off.
>
> I am using Red Hat 9.0 with the stock 2.4.20-13.9 kernel. I am attempting to
> get framebuffer support working on the console with little success. The
> relevant PC specs are as follows:
>
> Athlon XP 2000+
> 1 GB RAM
> Geforce4 ti4400
>
>>From what I have been able to ascertain, vesafb is compiled into this kernel
> instead of loading as a module. I looked at the information for the rivafb
> driver and it doesn't appear to support the GeForce4 cards. What info I have
> been able to dig up suggests that you can get non-accelerated framebuffer
> support for the GeForce4 using vesafb. I cannot, however, get it to work.
>
> I have tried to pass the following kernel arguments via grub. All I get is a
> blank screen"
>
> video=vesafb,xres:1024,yres:768,bpp:16 vga=791
>
> AND (just in case I COULD get the rivafb module to support it)
>
> video=rivafb,xres:1024,yres:768,bpp:16 vga=791
>
> I have played around with the bpp and vga= settings (trying 8, 16 and 24
> respectively) . No luck. Get a blank console up until kdm loads. And I
> don't see anthing in the dmesg logs either. Sigh.
>
> When I issue fbset I get the following error:
>
> open /dev/fb0: No such device
>
> Which leads me to believe that the stock kernel isn't seeing a framebuffer
> device despite the fact that vesafb is compiled in.
>
> I have not yet tried to compile a custom kernel precisely because of 1.)
> vesafb is complied into this kernel, AND 2.) Nothing I have read seems to
> indicate that compiling rivafb into the kernel will help with my issue ( and
> I have not been able to get rivafb to load as a module in any event...)
>
> So, I am stumped. I'm sure its something stupid on my part....but could
> anyone tell me A.) what I am doing wrong here, and/or B.) if anyone has
> gotten console framebuffer support running on a stock Red Hat kernel...
>
> Thanks for putting up with the long winded (and I sure stupid) questions..
>
> Keith Vaughan
>
try passing "mem=512M" to kernel in lilo. It worked for me...I also
have 1GB of ram
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-05-24 17:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-05-24 17:39 Console Framebuffer Issues / GeForce4 - Red Hat stock kernel 2.4.20-13.9 Robert Keith Vaughan
2003-05-24 17:58 ` Gutko
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).