Previously:

http://www.linuxquestions.org/questi...ifacts-752779/

I recompiled the kernel, to recognize the right processor ( P4 family Celeron Mobile ) and did search for the modifications to the graphics part described in here: http://www.linuxquestions.org/questi...9/#post3670364

I also used the linked website ( http://www.puresimplicity.net/~delah...a/toshiba.html ) for some info on which module to[*] or [m] ( his .config there -> http://www.puresimplicity.net/~delah...toshiba/config )

The compiling took about 14 hours (which is a bit long), and the system wasn't very responsive afterwards: I could type much faster then the screen could handle. It took the laptop about 15 minutes to shutdown,. see attachment.

I followed this 'guide' for recompiling your own kernel:
http://blog.tpa.me.uk/slackware-kernel-compile-guide/

All went well, I got the new kernel into Lilo and stuff, and it boots, but X crashed on startup; Something must have gone wrong, but I presume it allready went wrong on compiling: I think, no matter how 'stupid' you compile your kernel, the compiling itself should allways go well and not eat all resources or finish with hanging processes.. or should it? ( compiling under a stock smp kernel )


See attached screenshot: I got plenty of time to find my digicam, put on some coffee, take the snapshot, change to macro, take another shot, check it and take another shot: It really hanged.

PS: Thusfar the stock installation allways worked fine with no hangs at all, only the artifacs with X made me not wanna use the laptop.

Anyone?

Attached Images

DSC01935.JPG (131.8 KB, 12 views)

Certainly doesn't look good.. have never seen a compile hang like that. I would be tempted to try eliminating causes by copying the source to another machine and trying to compile it there. If it works perfectly on another machine then I might start to consider the possibility of hardware problems.