Mailing List Archive: MythTV: Users

splashy + nvidia + framebuffer

Index | Next | Previous | View Threaded

yan at seiner

Mar 15, 2008, 10:27 AM

Post #1 of 7 (734 views)
Permalink

splashy + nvidia + framebuffer

Has anyone any success in getting splashy running with the nvidia evil
binary module?

I can't even get the framebuffer working.

I've built a 2.6.24 kernel with vesafb built in. The system boots but
vga=791 gives me an unknown video mode.

Scanning for modes returns only text modes; no video fb modes.

I've tried adding

video=vesafb to the kernel line; no joy.

The default debian 2.6.22 kernel has the same behavior.

I must be missing some magic incantation that will enable kernel
framebuffer support.....

Is there some /proc or /sys thing I can check to see if my kernel has
framebuffer support?

--Yan
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

yan at seiner

Mar 15, 2008, 11:28 AM

Post #2 of 7 (714 views)
Permalink

Re: splashy + nvidia + framebuffer [In reply to]

Scott D. Davilla wrote:
>
> If you are Ubuntu (maybe applies to debian too), they by default
> blacklist most all framebuffers. The incantation is
>
> Commented those lines in /etc/modprobe.d/blacklist-framebuffer :
> #blacklist nvidiafb
> #blacklist vesafb
> Added those lines to /etc/initramfs-tools/modules:
> fbcon
> vesafb
> Then running update-initramfs.
Well the crazy thing is that I can't get vesafb or fbcon to build as
modules. I'm using a vanilla 2.6.24 kernel. The only option I have is
to build them into the kernel....

Anyone know how to build those as modules in 2.6.24?

_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

halovanic at gmail

Mar 15, 2008, 1:19 PM

Post #3 of 7 (715 views)
Permalink

Re: splashy + nvidia + framebuffer [In reply to]

I'm not sure what the issue is; i was running a stock 2.6.22 debian kernel
and framebuffer itself seemed to work fine. Did the 2.6.24 kernel make the
switch to uvesafb from vesafb?

The real problem I encountered on debian was that even with a working
framebuffer, splashy kept making the system hang on boot; some sort of
problem with libdirectfb causing it to timeout:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454917

On 3/15/08, Yan Seiner <yan[at]seiner.com> wrote:
>
> Scott D. Davilla wrote:
> >
> > If you are Ubuntu (maybe applies to debian too), they by default
> > blacklist most all framebuffers. The incantation is
> >
> > Commented those lines in /etc/modprobe.d/blacklist-framebuffer :
> > #blacklist nvidiafb
> > #blacklist vesafb
> > Added those lines to /etc/initramfs-tools/modules:
> > fbcon
> > vesafb
> > Then running update-initramfs.
> Well the crazy thing is that I can't get vesafb or fbcon to build as
> modules. I'm using a vanilla 2.6.24 kernel. The only option I have is
> to build them into the kernel....
>
> Anyone know how to build those as modules in 2.6.24?
>
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users[at]mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>

yan at seiner

Mar 16, 2008, 5:09 PM

Post #4 of 7 (709 views)
Permalink

Re: splashy + nvidia + framebuffer [In reply to]

Alex Halovanic wrote:
>
> I'm not sure what the issue is; i was running a stock 2.6.22 debian
> kernel and framebuffer itself seemed to work fine. Did the 2.6.24
> kernel make the switch to uvesafb from vesafb?
>
> The real problem I encountered on debian was that even with a working
> framebuffer, splashy kept making the system hang on boot; some sort of
> problem with libdirectfb causing it to timeout:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454917
>
Hmmm...

I've got 2.6.24 uvesafb set up and starting but I'm getting

/uvesafb: Getting VBE into block failed (eax=0x4f00, err=1)
//uvesafb: vbe_init() failed with -22

And of course google is mute on this. I get a handful of hits but nothing that would explain this.

I can see two possibilites:

1. My mobo + video card doesn't support vesa 2.0
2. I'm trying to set an unsupported mode.

The video card is a nVidia 6200 and the mobo is a ///WinFast/// K8S755A

Any ideas anyone?
/

>
> On 3/15/08, *Yan Seiner* <yan[at]seiner.com <mailto:yan[at]seiner.com>> wrote:
>
> Scott D. Davilla wrote:
> >
> > If you are Ubuntu (maybe applies to debian too), they by default
> > blacklist most all framebuffers. The incantation is
> >
> > Commented those lines in /etc/modprobe.d/blacklist-framebuffer :
> > #blacklist nvidiafb
> > #blacklist vesafb
> > Added those lines to /etc/initramfs-tools/modules:
> > fbcon
> > vesafb
> > Then running update-initramfs.
> Well the crazy thing is that I can't get vesafb or fbcon to build as
> modules. I'm using a vanilla 2.6.24 kernel. The only option I
> have is
> to build them into the kernel....
>
> Anyone know how to build those as modules in 2.6.24?
>
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users[at]mythtv.org <mailto:mythtv-users[at]mythtv.org>
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
> !DSPAM:47dc2f7731841804284693!
> ------------------------------------------------------------------------
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users[at]mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
> !DSPAM:47dc2f7731841804284693!
>

_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

yan at seiner

Mar 16, 2008, 9:12 PM

Post #5 of 7 (690 views)
Permalink

Re: splashy + nvidia + framebuffer [In reply to]

Yan Seiner wrote:
> Hmmm...
>
> I've got 2.6.24 uvesafb set up and starting but I'm getting
>
> /uvesafb: Getting VBE into block failed (eax=0x4f00, err=1)
> //uvesafb: vbe_init() failed with -22
>
> And of course google is mute on this. I get a handful of hits but nothing that would explain this.
>
> I can see two possibilites:
>
> 1. My mobo + video card doesn't support vesa 2.0
> 2. I'm trying to set an unsupported mode.
>
> The video card is a nVidia 6200 and the mobo is a ///WinFast/// K8S755A
>
> Any ideas anyone?
>

So this is becoming sort of like the Holy Grail... Seems that klibc, the
kernel, and v86d all must be compiled by the same version of gcc, and
also (apparently) during the same phase of the moon, after appropriate
sacrifice....

Anyway, more later - I'm learning more about debian's initrd, kernel
building, and astrology than I really want to know...

--Yan
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

ron at ronfrazier

Mar 17, 2008, 4:46 AM

Post #6 of 7 (708 views)
Permalink

Re: splashy + nvidia + framebuffer [In reply to]

> Has anyone any success in getting splashy running with the nvidia evil
> binary module?
>
> I can't even get the framebuffer working.
>
> I've built a 2.6.24 kernel with vesafb built in. The system boots but
> vga=791 gives me an unknown video mode.

The nvidia binary really doesn't have anything to do with it. I was
able to install splashy onto a bare bones debian 2.6.24 machine.
Literally, bare bones. I deselected EVERY option during the install,
did an apt-get update and dist-upgrade, installed openssh, then
splashy. Everything worked fine. It was only after I got it all
working that I then installed the nvidia driver. This was a machine
with a nvidia 7100 on the motherboard.

Have you tried any other video modes than just 791? Here are some
different modes:

resolution = 8bit / 15bit / 16bit / 24bit
640x480 = 769 / 784 / 785 / 786
800x600 = 771 / 787 / 788 / 789
1024x768 = 773 / 790 / 791 / 792
1280x1024 = 775 / 793 / 794 / 795

You don't have to use the same resolution or bit depth for booting as
you do for X.

> Scanning for modes returns only text modes; no video fb modes.

I presume the above modes wont work then, but I suppose its worth a
shot to try a couple others.

> I must be missing some magic incantation that will enable kernel
> framebuffer support.....

It must be very specific to your video card, because I just used a
basic debian testing install. The only boot options I added were
"vga=792 splash"

What is the source of your debian install? Is it possible you got a
nightly build that had some problems?....Actually, I see you mentioned
building the kernel. Have you tried it with a default kernel? If not,
give it a try. Maybe you missed something in your rebuild.

--
Ron
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

yan at seiner

Mar 17, 2008, 6:13 AM

Post #7 of 7 (688 views)
Permalink

Re: splashy + nvidia + framebuffer [In reply to]

Ronald Frazier wrote:
>
> Have you tried any other video modes than just 791? Here are some
> different modes:
>
> resolution = 8bit / 15bit / 16bit / 24bit
> 640x480 = 769 / 784 / 785 / 786
> 800x600 = 771 / 787 / 788 / 789
> 1024x768 = 773 / 790 / 791 / 792
> 1280x1024 = 775 / 793 / 794 / 795
>
> You don't have to use the same resolution or bit depth for booting as
> you do for X.
>
>
I've tried several. The problem is that the /dev/fb? device[s] aren't
being created at all, so there's nothing to set the mode for.
>
>
> It must be very specific to your video card, because I just used a
> basic debian testing install. The only boot options I added were
> "vga=792 splash"
>
>
> What is the source of your debian install? Is it possible you got a
> nightly build that had some problems?....Actually, I see you mentioned
> building the kernel. Have you tried it with a default kernel? If not,
> give it a try. Maybe you missed something in your rebuild.
>
>

I'm running debian lenny. I've had the same behavior with the stock
debian 2.6.22 kernel and my own 2.6.24 kernel.

I'm beginning to suspect that my hardware doesn't support framebuffer
and/or vesa, although I've never heard of such a thing. I suppose it's
possible. One more thing the manufacturers can leave off to save a few
pennies.

--Yan
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com