[Bug 28422] X freese in many cases

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Jul 24 05:28:34 PDT 2010


https://bugs.freedesktop.org/show_bug.cgi?id=28422

--- Comment #66 from DEMAINE Benoit-Pierre <benoit at demaine.info> 2010-07-07 08:58:34 PDT ---
Created an attachment (id=36838)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=36838)
z04 xorg.log

--- Comment #67 from DEMAINE Benoit-Pierre <benoit at demaine.info> 2010-07-24 05:28:34 PDT ---
(In reply to comment #42)
> > You tell me to build a kernel, but not what I should do with it. I know a dozen
> > of different ways to start Xorg ... In this bug, I do what you ask, not what
> > you think. In comment 40, you do not ask me anything.
> 
> So if I understood you correctly you now have a 2.6.34 kernel with Xen patches
> installed?
> Check the following: Go to the kernel source directory and start "make
> xconfig". Make sure that you have set "Enable modesetting on radeon by default"
> in "Direct Rendering Manager". "ATI Radeon (DRM Radeon)" should be compiled as
> a module.

Module names, and module place change every 6 months. Inside the 2.6 tree, I
have seen several drivers change place 4 times. Do not "describe" with words.
Be technical, and tell me the symbole name.

An other reason to use symbole names: if you knew it, you could grep directly
in my kernel conf ... if I already have it or not.

An other reason to use symbole names: if I don't find it at the place you
describe, I can search it. Then, I would either see the new place, or see the
deps that make it not appear (last week I had to activate 8 deps before I could
make my new wifi card driver appear in the menus).

> should be compiled as a module.

Why not hardlinked ?

> Did you add "radeon" and "fbcon" to your autoload config?

This is irrelevant. Because, even when modules are not declared in /etc, my
distribution discovers them anyway. It may happen I list them in autoload, and
it refuses to load them (and of course, does not say why, or life would be too
easy). The "hotplug" stack in Linux distributions became too big for me, too
many changes, too many services, I can do not master it whole anymore: hal
halevt devfs (when i started, it just came out, and I still have to use it on
very old machines, so, devfs is still in use on some of my box) udev (which
changed shape 3 times in 10y), coldplug (now removed from Debian), hotplug
(partly replaced by udev in some distros), sysfs (which has some bits in
kernel, and also contributes loading modules and firmwares), X (which sometimes
asks udev to handle some things like keyboard layout).

And sometimes, X developers fight on IRC because they do not agree between
themselves when I ask in which section of xorg.conf I should declare some
features (or wonder why some keywords work when I put them at the wrong place).

> What is your grub entry for the new kernel?

This kind of answer already is in Xlogs (search pattern "Kernel command line").
If you are an X dev, I wonder why you ask me such questions.

> Have you installed the ucode firmware?

Now, yes.

> Does the new kernel boot correctly?

Yes.

> Start X without a xorg.conf.

In Gentoo, it always leaded me to freese (or use only one card, and bugs even
with only one). Archlinux could start X nicely, and generate a working conf;
this conf now works in Gentoo.

No clue why. 

> Output of lsmod could probably also be useful.

I am not using a Debian with "all existing modules compiled in". I have a
Gentoo, and build my kernel myself. Look at my kernel conf.

> If KMS is enabled you should have the following line in your Xorg.0.log: [KMS]
> Kernel modesetting enabled.

Look at the dmesg. I have always provided them.

I provide all the logs you could need, and until now, most things I am asked
have answers in logs I had previously provided.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the xorg-driver-ati mailing list