On Sat, 2012-05-19 at 15:39 -0700, Paul Zimmerman wrote:
> Sorry I didn't save the Xorg.0.log in time from that boot of the 3.2 kernel. It might have
> been very informative.
>
> This machine has many problems with the X system. First it apparently does not
> report accurate screen size because the initial boot of both Lenny and Squeeze
> had a huge over-sized screen and I had to figure out how to get into a terminal
> window and edit xorg.conf to force a correct desktop size. This was done with a
> virtual screen.
xorg.conf is no longer required on most systems, and you may find that
the X server works better if you remove most of it.
[...]
> If I used the OpenChrome driver without the other option, "VBEModes",
> there would be a serious problem. Running the OpenChrome driver on this machine
> without that option causes hard lockups when you try to exit the desktop. So
> something to do with resetting from graphical mode to text mode directly instead of
> using the BIOS causes a hard lock. (Constant hard locks in the video drivers is what
> makes Windows completely unusable on this machine...)
>
> These weird behaviors make it look like internal tests are being updated and made
> stricter in progressing versions of OpenChrome and making the driver fussier. And it
> seems likely that some sort of conflict occurs between OpenChrome and the 3.2 kernel
> that causes the hang when I try to load it. So I cannot yet say if the ath5k driver in that
> kernel works on this machine.
Well, you should report that bug separately against
xserver-xorg-video-openchrome. But for now, please boot to single-user
mode ('rescue mode' in the GRUB menu) and test the ath5k driver from the
text console.
Ben.
--
Ben Hutchings
All extremists should be taken out and shot.
Attachment:
signature.asc
Description: This is a digitally signed message part