On Mon, Sep 19, 2011 at 4:33 PM, Alan McKinnon <alan.mckin...@gmail.com>wrote:
> On Mon, 19 Sep 2011 16:23:23 +0100 > Datty <datty....@gmail.com> wrote: > > > Thanks for the reply, I have looked at the document but unfortunately > > I can't use Nouveau because I need 3d so I went for what I could use. > > I've dropped uvesafb totally as it was pretty much useless anyway. It > > has sort of helped a little, its coming up what seems like more often > > than before but its still blanking quite a lot on boot. A few minutes > > of switching terminals does eventually bring it up but there doesn't > > seem to be any reasoning behind why it does and doesn't work. Nothing > > jumps out at me in the log either. > > Sounds like a race condition between the kernel and the uvesafb driver. > Only one of them can control the screen at any given time and console > handover is a tricky business (IIRC this was one of the very things that > drove the development of KMS). Perhaps every now and then uvesafb just > ahppened to grab (or ungrab) the console at just the right time. > > -- > Alan McKinnnon > alan.mckin...@gmail.com > > A bit of a gap since my last reply but I ended up having to remove Gentoo while I needed my laptop for work. I've rebuilt it all now based around gnome 3.2 but the screen issue still stands. I've only got VESA framebuffer in and nvidia-drivers-285.05.09. I'll try it without any framebuffer drivers but I'm a bit nervous I'll end up not being able to see anything! Any more ideas would be greatly appreciated. Thanks Oliver Smith
