[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Powerbook6,8 issues



On Sun, 2005-11-13 at 09:39 +1100, Benjamin Herrenschmidt wrote:
> > Random lines flickering in the screen when i use the keyboard in Xorg
> > (tried the default Xorg from sid and the experimental 6.9 packages) it's
> > really anoying and I'm afraid they are damaging the panel in someway.
> 
> It's probably not damaging the panel... Do you use an fbdev driver like
> rivafb ? Does it work better if you don't (use offb, that is
> video=ofonly on the kernel command line) ? Also make sure your X.org is
> configured to use the "nv" driver.

Yes i was using the nv driver and the rivafb from 2.6.13.4, I tried
video=ofonly with the same behavoir before I installed ubuntu (I wanted
to confirm it worked there since a coworker has the same laptop and the
display worked fine in ubuntu) tomorrow I will reinstall debian and try
some new things, like the xscreensaver downgrade Antonio suggested (how
the hell can xscreensaver be causing that, I don't know) then maybe
installing the ubuntu xorg in debian and if that work compile xorg to
try to identify the patch that fixes things.
 
> > dmasound doesn't work, just the snd-powermac alsa driver and that gives
> > a very ugly sound output :-(.
> 
> What do you mean by "very ugly" ? snd-powermac generally works better
> than dmasound.

Well it sounds bad, let's say very "noisy" i already tried ajusting all
the channels in alsamixer but I never get a confortable sound (using
beep-media-player & xmms alsa output).

> > The most annoying thing for me: The laptop doesn't suspend at all, I
> > still have my old ibook g3 with a radeon m7 and the sleep support is a
> > feature I'm very attached too. I'm a experienced C developer (no kernel
> > experience however) and would like to try to work on this, but I need
> > some pointers (Ben? :-), as I understad the problem with the sleep
> > support is the rivafb module not supporting the resume operation. Is
> > there any documentation on the chip ? refence code ? ways to reverse
> > enginer the os x driver behavior? (tools and methods). I would really,
> > really, really love to have this working.
> 
> The problem is that there are no specs whatsoever from nvidia, nothing
> at all, and the MacOS X driver afaik isn't an "ndrv" (thus can't be
> "spied" using my old ndrver tool)

So we have no hope ? :'-( Nothing ? Nada ? no ugly hack ? no dirty
workaround ? maybe not shutting down the nvidia chip completly ?
something ?






Reply to: