On Po 20.úno, Jonathan Nieder wrote: > reassign 660464 src:linux-2.6 3.2.4-1 > found 660464 linux-2.6/3.2.6-1 > tags 660464 + fixed-upstream > quit > > Mirek Jezbera wrote: > > > After another set of tests, I can confirm, that I have same problem with > > distribution kernel (linux-image-3.2.0-1-686-pae 3.2.4-1 - version in testing). > > I have booted this kernel twice and for the first time I have gui, but second > > time only black screen. > > Thanks. So it is intermittent. > > > I have recompiled kernel 3.2.6 (from unstable kernel sources 3.2.6-1) to have > > same options as working 3.3.0-rc1 kernel. From 5 boots I have gui three times > > and black screen twice. > > With linux kernel 3.3.0-rc1 I have always booted into gui. > > Ok. > > > When kernel fails to initialize gui, than I see message starting gdm, then > > screen is switched to higher resolution - I see gnome busy cursor (I can move > > with mouse and it is working). When there is also blinking text cursor in upper > > left corner, than no login screen will be visible - only blank screen (with > > working mouse cursor). > > Do you mean that there are three modes: successful, busy, blinking > text cursor? Only two modes - successfull and gui cursor + blinking text cursor together. I have tryed to gather more informations and I have discovered, that gdm is repetitively trying to start Xorg, but it fails and fills log with this: Feb 26 19:05:13 jezz-pc1 gdm-simple-slave[9499]: WARNING: Failed to get value: T he name :1.0 was not provided by any .service files Feb 26 19:05:13 jezz-pc1 gdm-simple-slave[9500]: WARNING: Failed to get value: The name :1.0 was not provided by any .service files Feb 26 19:05:13 jezz-pc1 gdm-simple-slave[9501]: WARNING: Failed to get value: The name :1.0 was not provided by any .service files Feb 26 19:05:13 jezz-pc1 gdm-simple-slave[9502]: WARNING: Failed to get value: The name :1.0 was not provided by any .service files > If you boot with the kernel parameter "text", does that avoid trouble? > How about if you run "modprobe radeon" from the console after doing > so? Text mode is working. I have tested starting Xorg from console. First start fails, but it loads radeon module. Next time Xorg is started successfully. > Can you attach /var/log/Xorg.0.log from a failure starting gdm, and > from a success for comparison? I have checked it, but there is no difference in logs. > [...] > > I don't use radeonfb for framebuffer - it is disabled in modprobe.d: > > $ grep radeon * > > fbdev-blacklist.conf:blacklist radeonfb > > radeon-kms.conf:options radeon modeset=1 > > I did not mean radeonfb but radeondrmfb. I have added radeon to /etc/modules (before fbcon module) and now gdm started (I have tryed it twice). Console is switched to higher resolution before gdm. This solves my problem. It seems, that there is some race condition issue in kernel. > Hope that helps, > Jonathan -- Jezz mail: jezz@hkfree.org jabber: jezz@njs.netlab.cz
Attachment:
signature.asc
Description: Digital signature