Bug 679264 - [RV100] gnome-shell can not start on ATI Radeon 7000/VE
Summary: [RV100] gnome-shell can not start on ATI Radeon 7000/VE
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-22 04:45 UTC by Atsushi
Modified: 2018-04-11 09:31 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-02 13:07:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg with drm.debug=0x04 (123.92 KB, text/plain)
2011-03-06 05:11 UTC, Atsushi
qd_linux5_kvm: review+
Details
Xorg.0.log (35.98 KB, text/plain)
2011-03-06 05:12 UTC, Atsushi
qd_linux5_kvm: review+
Details
/var/log/messages (166.77 KB, text/plain)
2011-03-06 05:12 UTC, Atsushi
qd_linux5_kvm: review+
Details
dmesg with adding kernel parameter drm.debug=0x04 in fedora 15 nightly build 20110403 (123.95 KB, text/plain)
2011-04-06 05:22 UTC, Atsushi
qd_linux5_kvm: review+
Details
Xorg.log in Fedora 15 nightly build 20110403 (36.29 KB, text/plain)
2011-04-06 05:24 UTC, Atsushi
no flags Details
/var/log/messages in Fedora 15 nightly build 20110403 (123.43 KB, text/plain)
2011-04-06 05:25 UTC, Atsushi
no flags Details
figure after liveuser login in Fedora 15 nighly build 20110403 (480.71 KB, image/jpeg)
2011-04-06 05:39 UTC, Atsushi
no flags Details

Description Atsushi 2011-02-22 04:45:24 UTC
Description of problem:
Start LiveCD  downloaded from http://serverbeach1.fedoraproject.org/pub/alt/stage/15-Alpha.RC1/Live/i686/Fedora-15-Alpha-i686-Live-Desktop.iso.
gnome-shell can not start, usually gnome panel.

Version-Release number of selected component (if applicable):
Fedora 15-Alpha.RC1

How reproducible:


Steps to Reproduce:
1.Insert LiveCD.
2.PC boot.
3.login as liveuser.
  
Actual results:
gnome-shell can not start

Expected results:
gnome-shell start

Additional info:
lspci |grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]

glxinfo |grep render
direct rendering: Yes
OpenGL renderer string: Mesa DRI R100 (RV100 5159) 20090101  NO-TCL DRI2

glxinfo |grep Open
OpenGL vendor string: Tungsten Graphics, Inc.
OpenGL renderer string: Mesa DRI R100 (RV100 5159) 20090101  NO-TCL DRI2
OpenGL version string: 1.3 Mesa 7.10-devel
OpenGL extensions:

Comment 1 Atsushi 2011-02-22 04:59:52 UTC
yum install destop-effects.
select gnome-shell

error message as below.

** (desktop-effects:4138): WARNING **: AT-SPI: Accessibility bus not found - Using session bus.

Gtk-Message: Failed to load module "pk-gtk-module"
Window manager warning: Log level 16: AT-SPI: Accessibility bus not found - Using session bus.

(mutter:4153): Clutter-DEBUG: Signal type minimize not supported

(mutter:4153): Clutter-DEBUG: Signal type maximize not supported

(mutter:4153): Clutter-DEBUG: Signal type restore not supported

      JS LOG: Cannot create "Network" item, .desktop file not found or corrupt.
      JS LOG: GNOME Shell started at Tue Feb 22 2011 13:56:18 GMT-0500 (EST)
*********************************WARN_ONCE*********************************
File radeon_swtcl.c function r100_swtcl_flush line 325
Rendering was 4 commands larger than predicted size. We might overflow  command buffer.
***************************************************************************
drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info.

** (metacity:4225): WARNING **: AT-SPI: Accessibility bus not found - Using session bus.

Window manager warning: Failed to load theme "Clearlooks": Failed to find a valid file for theme Clearlooks

Gtk-Message: Failed to load module "pk-gtk-module"

** (gnome-panel:4228): WARNING **: AT-SPI: Accessibility bus not found - Using session bus.

Comment 2 Jean-François Fortin Tam 2011-02-27 20:12:57 UTC
I'm thinking this might be the same as bug #673848 ?

Comment 3 Matěj Cepl 2011-03-01 11:32:10 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 4 Atsushi 2011-03-06 05:11:15 UTC
Created attachment 482489 [details]
dmesg with drm.debug=0x04

Comment 5 Atsushi 2011-03-06 05:12:05 UTC
Created attachment 482490 [details]
Xorg.0.log

Comment 6 Atsushi 2011-03-06 05:12:50 UTC
Created attachment 482491 [details]
/var/log/messages

Comment 7 Atsushi 2011-03-06 05:48:48 UTC
not use xorg.conf file.
Start LiveCD  downloaded from
http://serverbeach1.fedoraproject.org/pub/alt/stage/15-Alpha.RC2/Live/i686/Fedora-15-Alpha-i686-Live-Desktop.iso.

Comment 8 Chuck Ebbert 2011-03-15 07:33:55 UTC
The correct component is xorg-x11-drv-ati

Comment 9 Chuck Ebbert 2011-03-25 18:17:45 UTC
Please don't add aliases like that. Those aliases are global and make it look like this is the only bug in the world that has something to do with gnome-shell.

Comment 10 Matěj Cepl 2011-04-05 06:08:57 UTC
Just to confirm, when you upgrade to the latest packages from F15 updates-testing, you still don't gnome-shell, right?

Thank you for filing the bug.

Comment 11 Matěj Cepl 2011-04-05 06:10:35 UTC
Alternatively you can try LiveCD ISO from http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/

Comment 12 Jean-François Fortin Tam 2011-04-05 13:12:20 UTC
FWIW, I tested the gnome3 fedora livecd (which is only days old) and no, it doesn't work.

Comment 13 Matěj Cepl 2011-04-05 16:08:23 UTC
Not sure, what this is, but doesn't look like Xorg:

Mar  6 14:02:37 localhost kernel: [  181.015420] Uhhuh. NMI received for unknown reason 2d on CPU 0.
Mar  6 14:02:37 localhost kernel: [  181.015430] Do you have a strange power saving mode enabled?
Mar  6 14:02:37 localhost kernel: [  181.015435] Dazed and confused, but trying to continue
Mar  6 14:04:19 localhost kernel: [  283.246254] Uhhuh. NMI received for unknown reason 3d on CPU 0.
Mar  6 14:04:19 localhost kernel: [  283.246265] Do you have a strange power saving mode enabled?
Mar  6 14:04:19 localhost kernel: [  283.246270] Dazed and confused, but trying to continue
Mar  6 14:05:20 localhost pam: gdm-autologin[1264]: DEBUG(+): unhandled property HomeDirectory
Mar  6 14:05:20 localhost pam: gdm-autologin[1264]: DEBUG(+): ActUserManager: user changed
Mar  6 14:05:20 localhost pam: gdm-autologin[1264]: DEBUG(+): unhandled property HomeDirectory
Mar  6 14:05:42 localhost kernel: [  365.876961] gnome-power-man[1571]: segfault at 0 ip 001d36d0 sp bf806330 error 4 in libgio-2.0.so.0.2800.0[130000+12a000]
Mar  6 14:05:43 localhost abrt[1949]: saved core dump of pid 1571 (/usr/bin/gnome-power-manager) to /var/spool/abrt/ccpp-1299438342-1571.new/coredump (27381760 bytes)
Mar  6 14:05:43 localhost abrtd: Directory 'ccpp-1299438342-1571' creation detected
Mar  6 14:05:43 localhost abrtd: New crash /var/spool/abrt/ccpp-1299438342-1571, processing
Mar  6 14:05:43 localhost abrtd: RunApp('/var/spool/abrt/ccpp-1299438342-1571','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
Mar  6 14:07:37 localhost kernel: [  480.917191] Uhhuh. NMI received for unknown reason 3d on CPU 0.
Mar  6 14:07:37 localhost kernel: [  480.917201] Do you have a strange power saving mode enabled?
Mar  6 14:07:37 localhost kernel: [  480.917207] Dazed and confused, but trying to continue
Mar  6 14:08:27 localhost kernel: [  530.843943] TCP lp registered
Mar  6 14:08:46 localhost pulseaudio[1538]: ratelimit.c: 1 events suppressed
Mar  6 14:08:47 localhost kernel: [  551.595134] Uhhuh. NMI received for unknown reason 3d on CPU 0.
Mar  6 14:08:47 localhost kernel: [  551.595146] Do you have a strange power saving mode enabled?
Mar  6 14:08:47 localhost kernel: [  551.595152] Dazed and confused, but trying to continue

Comment 14 Matěj Cepl 2011-04-05 16:18:29 UTC
I am not sure what comment 13 means, but it doesn't like something Xorg-related. Reassigning back to kernel, and I am willing to be corrected.

Comment 15 Atsushi 2011-04-06 05:21:01 UTC
thanks reply for Matej Cepl and Jean-François Fortin Tam.

I test using 
http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ as 20110403.17 desktop i686.

In this case, can show panel, not only wallpaper.
but, no action by mouse click both left and right.

attachment as figure, dmesg, Xorg.0.log, messages.log.

I think kernel need correct, because compiz can work in old kernel(fedora 14) as https://bugzilla.redhat.com/show_bug.cgi?id=668720.

Comment 16 Atsushi 2011-04-06 05:22:45 UTC
Created attachment 490132 [details]
dmesg with adding kernel parameter drm.debug=0x04 in fedora 15 nightly build 20110403

Comment 17 Atsushi 2011-04-06 05:24:16 UTC
Created attachment 490133 [details]
Xorg.log in Fedora 15 nightly build 20110403

Comment 18 Atsushi 2011-04-06 05:25:10 UTC
Created attachment 490135 [details]
/var/log/messages in Fedora 15 nightly build 20110403

Comment 19 Atsushi 2011-04-06 05:39:51 UTC
Created attachment 490140 [details]
figure after liveuser login in Fedora 15 nighly build 20110403

show panel, but no action by mouse click.

Comment 20 Don Zickus 2011-04-07 14:20:42 UTC
(In reply to comment #14)
> I am not sure what comment 13 means, but it doesn't like something
> Xorg-related. Reassigning back to kernel, and I am willing to be corrected.

Those unknown NMIs are a red herring.  They are the result of using the perf/nmi_watchdog on a Pentium4 box.  It is a known issue we are working on.  Booting with nmi_watchdog=0, will remove them.  They are harmless anyway (despite what the message says :-)).

Cheers,
Don

Comment 21 Adel Gadllah 2011-04-10 12:32:19 UTC
gnome-shell isn't expected to work on r100 (or r200) you need >= r300 for radeon cards for it to work.

Comment 22 Atsushi 2011-04-10 13:18:55 UTC
Really, ok. i will buy new PC. This session closed.

Comment 23 Adam Williamson 2011-04-26 16:21:24 UTC
jglisse: is that accurate? I believe when I asked you and airlied before, you suggested any Radeon should work (but pre-Radeon cards would not).

Comment 24 Joachim Frieben 2011-05-09 14:04:06 UTC
(In reply to comment #21)
There is no reason to assume that the GNOME shell would not work with R1xx and R2xx chips. I am even fairly sure that it worked correctly some time during the development cycle of F15 for my Radeon 7200 (R100). However, I have just tried yesterday's nightly build, and the GNOME desktop now actually switches to fallback mode. Why is this bug's status "CLOSED NOTABUG"? According to my memory, fallback mode for said hardware is a regression which occurred not a long time ago.

Comment 25 Adam Williamson 2011-05-09 15:31:44 UTC
it's not a regression, it's an intentional change. The radeon maintainers, jglisse and airlied, have said that it's not practical to implement full, non-buggy support for the Shell on these adapters, so Shell has been updated to force them to fallback mode.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 26 Joachim Frieben 2011-05-09 17:19:16 UTC
(In reply to comment #25)
After launching "gnome-shell --replace", the GNOME shell gets launched successfully and actually runs without issues on my Radeon 7200 (R100).

Comment 27 Adam Williamson 2011-05-09 19:22:52 UTC
it does not run 'without issues', there are known bugs in shell rendering on r100 and r200; I forget what they are exactly, I don't have the reference to hand unfortunately. but that's why this was changed.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 28 Atsushi 2011-05-10 00:49:09 UTC
thans reply to Adam, Christoph.

1. try 20110509.17-nightlybuild-desktop.

boot to fallback mode. 

2. gnome-shell --replace from gnome-terminal.
can not work gnome-shell too.
error message as below.

Window manager warning: Log level 16: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject
Window manager warning: Log level 16: Error registering polkit authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject (polkit-error-quark 0)
      JS LOG: GNOME Shell started at Mon May 09 2011 20:33:12 GMT-0400 (EDT)
*********************************WARN_ONCE*********************************
File radeon_swtcl.c function r100_swtcl_flush line 325
Rendering was 4 commands larger than predicted size. We might overflow  command buffer.
***************************************************************************
drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream. See dmesg for more info.
gnome-shell-calendar-server[2065]: Got HUP on stdin - exiting

3. this bug's status return from "CLOSED NOTABUG" to "ASSIGNED"

sorry, i watch only CLOSE, do not know second select someone.
And, i want to know the link to GNOME-Shell about r100.

Comment 29 Adam Williamson 2011-05-10 01:08:59 UTC
well, that's your driver failing to do the shell properly.

the bug should be closed, because the radeon driver maintainers consider it impossible to support the Shell properly on r100 and r200 hardware, so there is no work to perform here.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 30 Atsushi 2011-05-10 02:17:30 UTC
mhhh, i want to make sure specifications of Shell on r100.
then, will close.

Comment 31 Adel Gadllah 2011-05-10 08:09:19 UTC
(In reply to comment #29)
> well, that's your driver failing to do the shell properly.
> 
> the bug should be closed, because the radeon driver maintainers consider it
> impossible to support the Shell properly on r100 and r200 hardware, so there is
> no work to perform here.

Well it is not just a driver issues, the hardware isn't really powerful enough to provide a proper experience.

Comment 32 Adel Gadllah 2011-06-02 13:07:39 UTC
(In reply to comment #29)
> well, that's your driver failing to do the shell properly.
> 
> the bug should be closed, because the radeon driver maintainers consider it
> impossible to support the Shell properly on r100 and r200 hardware, so there is
> no work to perform here.


Note You need to log in before you can comment on or make changes to this bug.