Project

General

Profile

Actions

Bug #1264

closed

Xserver does not start on X31 and recent HEAD

Added by jspringe almost 16 years ago. Updated almost 16 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Hi,
as I do not use xorg on my server machines and did not update my laptop for some time I just noticed today
that xorg seems to be broken. When I boot up the 2.0.1 release and mount my current /usr partition the X server runs flawlessly. When booting HEAD X seems to start, system freezes displaying the console startup messages.
No keystrokes work, no kernel dump, nothing.
Using the vesa driver and turning off DRI also did not help.
As the same /usr partition works fine in the release I suspect there must be some kernel changes that caused this, any ideas ?

Regards,
Tobias

Actions #1

Updated by corecode almost 16 years ago

Could you try and bisect the changes so that we know which commit broke it?

For more info, read the git-bisect(1) page.

thanks!

Actions #2

Updated by jspringe almost 16 years ago

On Tue, 10 Feb 2009 13:40:51 +0000
"Simon 'corecode' Schubert \(via DragonFly issue tracker\)" <> wrote:

Yes I can do that, it might take some time however, as I have no machine to crossbuild right now,
and the laptop is rather slow.
BTW is there any reason I should get a CCVER not set error when changing to another git revision ?

Actions #3

Updated by corecode almost 16 years ago

Alternatively you can also grab kernels from a snapshot mirror and try them.

Regarding the CCVER, when/how does the error message happen exactly?

Actions #4

Updated by jspringe almost 16 years ago

Ok this is strange ...
I pulled in a kernel build from 30 of Jan and X boots up nicely.
So whatever broke it, it was repaired later on ...
The broken kernel was from 20 of Jan.
I am building a new kernel with HEAD as of now to ensure that the error is gone!

Actions #5

Updated by jspringe almost 16 years ago

Can be closed ...
After building a kernel with HEAD as of yesterday the problem is gone.
One of the commits after 20 of Jan must have fixed it :)

Actions

Also available in: Atom PDF