X problems.

0 views
Skip to first unread message

hyjial

unread,
May 1, 2007, 4:52:53 AM5/1/07
to kernel...@nl.linux.org
Hi list,
I'm running Debian Etch with a 2.6.18 kernel on a T22
Thinkpad.
The default kernel (2.6.18-4) works well until I start
X. There, the system hangs on a void screen with
neither mouse nor keyboard working. I built a custom
2.6.18 kernel and I got the same problem. Actually, I
have to reboot once, twice or more before getting X
started ( everything works well then ).
I have once managed to get a custom kernel work fine,
but the USB subsystem didn't work ( no doubt there is
no connection between the two ). This means that by
configuring the kernel in a certain way, I can make it
work.
I have already had the same problem with the following
distros : (K)Ubuntu Dapper Drake and following,
Knoppix 5.1.1.
My question is : is it due to the kernel itself and
conflicting drivers or to userspace configuration ?
Thanks in advance.



___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to eca...@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ

Erik Mouw

unread,
May 1, 2007, 6:17:43 PM5/1/07
to hyjial, kernel...@nl.linux.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, May 01, 2007 at 10:52:53AM +0200, hyjial wrote:
> I'm running Debian Etch with a 2.6.18 kernel on a T22
> Thinkpad.
> The default kernel (2.6.18-4) works well until I start
> X. There, the system hangs on a void screen with
> neither mouse nor keyboard working. I built a custom
> 2.6.18 kernel and I got the same problem. Actually, I
> have to reboot once, twice or more before getting X
> started ( everything works well then ).

Sounds ACPI related to me.

> I have once managed to get a custom kernel work fine,
> but the USB subsystem didn't work ( no doubt there is
> no connection between the two ). This means that by
> configuring the kernel in a certain way, I can make it
> work.

Look at the config file to figure out what's different (except USB
support).

> I have already had the same problem with the following
> distros : (K)Ubuntu Dapper Drake and following,
> Knoppix 5.1.1.
> My question is : is it due to the kernel itself and
> conflicting drivers or to userspace configuration ?

Very hard to tell without any additional information. First of all, try
to recreate the problem with the new and shiny 2.6.21.1 kernel. If the
problem persists, post a kernel log and the config for that kernel so
people can actually help.


Erik

- - - - --
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGN7yG/PlVHJtIto0RAqNkAJ4l8Dqc6PS74KcddrGxD6ov4b+EzgCcCL8K
mdjePe/BtrX2aDBDLX68VnI=
=UlB0
-----END PGP SIGNATURE-----

Reply all
Reply to author
Forward
0 new messages