Re: laptop Dell M4400 with -CURRENT?

El día Monday, May 11, 2009 a las 02:21:21PM +0200, Matthias Apitz escribió:

> El día Friday, May 08, 2009 a las 10:28:09AM -0500, Robert Noland escribió:
> 
> > I have ported the nouveau drm driver.
> > 
> > http://people.freebsd.org/~rnoland/drm-nouveau-043009.patch
> > 
> > It is working on NV50 cards, NV40 was working, but with WITNESS enabled
> > I seem to be getting a panic on NV40.  My NV40 card seems to be having
> > memory issues so I haven't been able to get and/or see the backtrace.  I
> > think it is just a locking issue which should be pretty easily solved if
> > I can get a clear backtrace.
> > 
> > You will need current libdrm and xf86-video-nouveau from ports.
> > 
> > This won't get you 3d right now, but should get you EXA + Xv.
> 
> Hello Robert,
> 
> I have applied your patch and ported xf86-video-nouveau from ports; all
> is fine now and the display comes up with 1920x1200 resolution;
> 
> I'm attaching Xorg.0.log so you can see what kind of chips the nouveau
> driver is detecting.
> 
> Thanks again for your work and help

....

Hello,

I have to admit that this message 'all is fine' was to fast; the Xorg
came only up *once* and let the KDE3.5.10 fully appear; I was even able
to switch the font size from 8 to 12, because with this high resolution
it was nearly unreadable.

after stopping X with Ctrl-Alt-BS I was never ever able to bring X + KDE
up; while KDE is initialising at some point the X goes into 100% of CPU
usage; it is not a CPU-loop itself inside the X server, but a loop of
SIG 14 as I can proof with truss from another session:

SIGNAL 14 (SIGALRM)
sigreturn(0xbfbfe500,0xe,0x0,0xbfbfe500,0x0,0x8127070) = 678420552 (0x286fe048)
SIGNAL 14 (SIGALRM)
sigreturn(0xbfbfe500,0xe,0x0,0xbfbfe500,0x0,0x8127070) = 678420552 (0x286fe048)
SIGNAL 14 (SIGALRM)
sigreturn(0xbfbfe500,0xe,0x0,0xbfbfe500,0x0,0x8127070) = 678420552 (0x286fe048)
SIGNAL 14 (SIGALRM)
...

when I only start via ~/.xinitrc a 'xterm' and 'twm' there is no
problem, but as soon I'm launching 'startkde' inside such a session the
above loop comes up and only power cycle bring the system back to life.

What can I do?

I have also removed ~/.kde and ~/Desktop to let KDE init a fresh
environment, no luck.

I'm not using HAL with KDE.

The 'vesa' driver works but only gives 1024x??? resolution (don't
remember the exact 2nd size right now), but this is not an option to go;
is it possible to get higher res with 'vesa'?

If someone wants me debugging something, please tell me how; I could
even provide SSH access to the laptop (because it is still nearly
empty), please contact me off-list for this.

Thanks for any hint.

	matthias
-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <guru_at_unixarea.de> - w http://www.unixarea.de/
People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD.