Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
Sorry for e-mailing on this old bug, but it seemed like the right thing to do, to attach the information about where to go next. Do you know where I could follow the development work (or lack thereof) on the upstream Mesa r300 big endian problem, to check the status, or to contribute to a solution? Is there a specific defect number? Sorry I just don't know where this work is being done. Any information you can provide to point me in the right direction would be helpful. Thanks very much. On Tue, 9/23/14, Michel Dänzer mic...@daenzer.net wrote: Subject: Re: Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC To: Bill Chatfield bill_chatfi...@yahoo.com Cc: 762...@bugs.debian.org Date: Tuesday, September 23, 2014, 9:17 PM On 23.09.2014 00:25, Bill Chatfield wrote: If I understand this correctly, then one of the defects in this situation is that the old radeonfb, nouveaufb, etc fb device drivers are still being compiled into the kernel. This shouldn't happen if they're not really supported by the rest of the system. I could file a bug in that regard, if that is the right thing to do. There is a file that attempts to blacklist all the old cardnamefb drivers, but since they are not loadable modules, this fails. You'd have to discuss that with the kernel package maintainers. I have determined that the reason why gdm and gnome will not run is because they require an accelerated driver, which radeonfb does not support. So I either have to use radeonfb with xfce or get the radeon/drm to work so I can run gnome. Unfortunately, the upsream Mesa r300 driver currently doesn't work correctly on big endian hosts. That would need to be fixed before you can run gnome-shell. So I'm afraid there's no obvious 'right thing to do', it's more a 'pick your poison' kind of situation. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1419447505.51960.yahoomailba...@web124701.mail.ne1.yahoo.com
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
On 23.09.2014 00:25, Bill Chatfield wrote: If I understand this correctly, then one of the defects in this situation is that the old radeonfb, nouveaufb, etc fb device drivers are still being compiled into the kernel. This shouldn't happen if they're not really supported by the rest of the system. I could file a bug in that regard, if that is the right thing to do. There is a file that attempts to blacklist all the old cardnamefb drivers, but since they are not loadable modules, this fails. You'd have to discuss that with the kernel package maintainers. I have determined that the reason why gdm and gnome will not run is because they require an accelerated driver, which radeonfb does not support. So I either have to use radeonfb with xfce or get the radeon/drm to work so I can run gnome. Unfortunately, the upsream Mesa r300 driver currently doesn't work correctly on big endian hosts. That would need to be fixed before you can run gnome-shell. So I'm afraid there's no obvious 'right thing to do', it's more a 'pick your poison' kind of situation. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/542229b5.5000...@daenzer.net
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
Got it. Thanks! On Tue, 9/23/14, Michel Dänzer mic...@daenzer.net wrote: Subject: Re: Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC To: Bill Chatfield bill_chatfi...@yahoo.com Cc: 762...@bugs.debian.org Date: Tuesday, September 23, 2014, 10:17 PM On 23.09.2014 00:25, Bill Chatfield wrote: If I understand this correctly, then one of the defects in this situation is that the old radeonfb, nouveaufb, etc fb device drivers are still being compiled into the kernel. This shouldn't happen if they're not really supported by the rest of the system. I could file a bug in that regard, if that is the right thing to do. There is a file that attempts to blacklist all the old cardnamefb drivers, but since they are not loadable modules, this fails. You'd have to discuss that with the kernel package maintainers. I have determined that the reason why gdm and gnome will not run is because they require an accelerated driver, which radeonfb does not support. So I either have to use radeonfb with xfce or get the radeon/drm to work so I can run gnome. Unfortunately, the upsream Mesa r300 driver currently doesn't work correctly on big endian hosts. That would need to be fixed before you can run gnome-shell. So I'm afraid there's no obvious 'right thing to do', it's more a 'pick your poison' kind of situation. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1411533145.1630.yahoomailba...@web124702.mail.ne1.yahoo.com
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
OK, so I need to prevent radeonfb from running? What is the best way to do that if it's compiled into the kernel? Do I need to compile another kernel or is there a way to configure it not to use that driver? Please forgive my ignorance. But I'm having trouble finding answers to these questions. If you could recommend a document I could go to, I'd be glad to read it. If I understand this correctly, then one of the defects in this situation is that the old radeonfb, nouveaufb, etc fb device drivers are still being compiled into the kernel. This shouldn't happen if they're not really supported by the rest of the system. I could file a bug in that regard, if that is the right thing to do. There is a file that attempts to blacklist all the old cardnamefb drivers, but since they are not loadable modules, this fails. I have determined that the reason why gdm and gnome will not run is because they require an accelerated driver, which radeonfb does not support. So I either have to use radeonfb with xfce or get the radeon/drm to work so I can run gnome. Thanks for your continuing help. On Sun, 9/21/14, Michel Dänzer mic...@daenzer.net wrote: Subject: Re: Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC To: Bill Chatfield bill_chatfi...@yahoo.com Cc: 762...@bugs.debian.org Date: Sunday, September 21, 2014, 8:59 PM On 19.09.2014 23:58, Bill Chatfield wrote: 2. Is radeonfb really supposed to be compiled into the kernel as it is, or should it have been built as a module? Why do you think they compiled it into the kernel? It was traditionally done like that on powerpc to provide a nice console experience and suspend/resume support on laptops. 3. If the kernel is activating radeonfb as we can see in dmesg, why would it also load the drm/radeon driver? Presumably, the radeon driver is loaded by udev because it declares that it supports your GPU. It could still be used by older upstream versions of xserver-xorg-video-radeon and libgl1-mesa-dri, but the current versions only support KMS anymore. I believe I answered your other questions in my previous two e-mails. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1411399513.86011.yahoomailba...@web124704.mail.ne1.yahoo.com
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
On Mon, Sep 22, 2014 at 08:25:13 -0700, Bill Chatfield wrote: OK, so I need to prevent radeonfb from running? What is the best way to do that if it's compiled into the kernel? Do I need to compile another kernel or is there a way to configure it not to use that driver? Please forgive my ignorance. But I'm having trouble finding answers to these questions. If you could recommend a document I could go to, I'd be glad to read it. Please read Michel's previous mails, he answered that already. Cheers, Julien signature.asc Description: Digital signature
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
My apologies, some of the messages had gone into my Spam folder, so I didn't see them. On Mon, 9/22/14, Julien Cristau jcris...@debian.org wrote: Subject: Re: Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC To: Bill Chatfield bill_chatfi...@yahoo.com, 762...@bugs.debian.org Cc: Michel Dänzer mic...@daenzer.net Date: Monday, September 22, 2014, 2:37 PM On Mon, Sep 22, 2014 at 08:25:13 -0700, Bill Chatfield wrote: OK, so I need to prevent radeonfb from running? What is the best way to do that if it's compiled into the kernel? Do I need to compile another kernel or is there a way to configure it not to use that driver? Please forgive my ignorance. But I'm having trouble finding answers to these questions. If you could recommend a document I could go to, I'd be glad to read it. Please read Michel's previous mails, he answered that already. Cheers, Julien -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1411414599.18127.yahoomailba...@web124706.mail.ne1.yahoo.com
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
On 19.09.2014 23:58, Bill Chatfield wrote: 2. Is radeonfb really supposed to be compiled into the kernel as it is, or should it have been built as a module? Why do you think they compiled it into the kernel? It was traditionally done like that on powerpc to provide a nice console experience and suspend/resume support on laptops. 3. If the kernel is activating radeonfb as we can see in dmesg, why would it also load the drm/radeon driver? Presumably, the radeon driver is loaded by udev because it declares that it supports your GPU. It could still be used by older upstream versions of xserver-xorg-video-radeon and libgl1-mesa-dri, but the current versions only support KMS anymore. I believe I answered your other questions in my previous two e-mails. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541f748f.2000...@daenzer.net
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
On 18.09.2014 23:33, Bill Chatfield wrote: It would seem so, but it is the right information. I double checked that it is right by booting without the video kernel parameter and running dmesg. Okay, so I think your original problem is because the Xorg fbdev driver uses the colour depth from console by default, and I guess the login manager you're using can't deal with that. You may want to report that against the login manager package, but you probably want to use a higher colour depth anyway. So you need to change it, either for console as you've been doing, or just for X in /etc/X11/xorg.conf or by having the login manager pass -depth XX on the Xorg command line. I got the same radeonfb lines that you show in your message. I think that's part of the problem, radeonfb is compiled into the kernel and active when drm/radeon are being used? Right, to use radeon KMS, you need to disable radeonfb with video=radeonfb:off on the kernel command line. That should give you at least 2D hardware acceleration, but suspend/resume won't work. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541bfc56.6020...@daenzer.net
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
On 19.09.2014 18:50, Michel Dänzer wrote: On 18.09.2014 23:33, Bill Chatfield wrote: It would seem so, but it is the right information. I double checked that it is right by booting without the video kernel parameter and running dmesg. Okay, so I think your original problem is because the Xorg fbdev driver uses the colour depth from console by default, and I guess the login manager you're using can't deal with that. To clarify, I mean it can't deal with depth 8 pseudo-colour. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541bfd92.3050...@daenzer.net
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
I've verified that I provided the correct dmesg. But, my knowledge of how this is supposed to work is lacking, so I don't know how to debug this. If you could answer some questions, that would help me figure out what to do next. I'd also really like to learn whatever you can tell me about it: 1. Will the kernel choose one of the drivers (radeonfb or radeon) if they're both present or do I need to completely block one of them to get it to work right? 2. Is radeonfb really supposed to be compiled into the kernel as it is, or should it have been built as a module? Why do you think they compiled it into the kernel? 3. If the kernel is activating radeonfb as we can see in dmesg, why would it also load the drm/radeon driver? 4. The login screen comes up and is functional because I can blindly type in my user id and password, but none of the components of the login screen are actually visible except for the mouse. Which component is failing in this scenario (Xorg, radeon(fb), gtk, etc) ? Thanks for your help! On Thu, 9/18/14, Michel Dänzer mic...@daenzer.net wrote: Subject: Re: Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC To: Bill Chatfield bill_chatfi...@yahoo.com Cc: 762...@bugs.debian.org Date: Thursday, September 18, 2014, 2:24 AM On 18.09.2014 13:23, Bill Chatfield wrote: [ 0.997986] radeonfb :00:10.0: enabling device (0006 - 0007) [ 1.193788] radeonfb :00:10.0: Invalid ROM contents [ 1.193813] radeonfb (:00:10.0): Invalid ROM signature 303 should be 0xaa55 [ 1.193823] radeonfb: Retrieved PLL infos from Open Firmware [ 1.193842] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz [ 1.193864] radeonfb: PLL min 12000 max 35000 [ 1.289994] i2c i2c-2: unable to read EDID block. [ 1.441986] i2c i2c-2: unable to read EDID block. [ 1.593986] i2c i2c-2: unable to read EDID block. [ 1.949865] radeonfb: Monitor 1 type LCD found [ 1.949881] radeonfb: EDID probed [ 1.949893] radeonfb: Monitor 2 type no found [ 1.949915] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0 [ 1.949981] radeonfb: Dynamic Clock Power Management enabled [ 1.982573] Console: switching to colour frame buffer device 160x53 [ 2.004457] radeonfb: Backlight initialized (radeonbl0) [ 2.004635] radeonfb (:00:10.0): ATI Radeon 4e50 NP This shows that radeonfb is still enabled, so it doesn't provide the information corresponding to the bug. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1411138730.93575.yahoomailba...@web124703.mail.ne1.yahoo.com
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
On 18.09.2014 13:23, Bill Chatfield wrote: [0.997986] radeonfb :00:10.0: enabling device (0006 - 0007) [1.193788] radeonfb :00:10.0: Invalid ROM contents [1.193813] radeonfb (:00:10.0): Invalid ROM signature 303 should be 0xaa55 [1.193823] radeonfb: Retrieved PLL infos from Open Firmware [1.193842] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz [1.193864] radeonfb: PLL min 12000 max 35000 [1.289994] i2c i2c-2: unable to read EDID block. [1.441986] i2c i2c-2: unable to read EDID block. [1.593986] i2c i2c-2: unable to read EDID block. [1.949865] radeonfb: Monitor 1 type LCD found [1.949881] radeonfb: EDID probed [1.949893] radeonfb: Monitor 2 type no found [1.949915] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0 [1.949981] radeonfb: Dynamic Clock Power Management enabled [1.982573] Console: switching to colour frame buffer device 160x53 [2.004457] radeonfb: Backlight initialized (radeonbl0) [2.004635] radeonfb (:00:10.0): ATI Radeon 4e50 NP This shows that radeonfb is still enabled, so it doesn't provide the information corresponding to the bug. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541a7aaf.30...@daenzer.net
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
It would seem so, but it is the right information. I double checked that it is right by booting without the video kernel parameter and running dmesg. I got the same radeonfb lines that you show in your message. I think that's part of the problem, radeonfb is compiled into the kernel and active when drm/radeon are being used? On a normal boot with a default configuration, radeonfb is active. It is blacklisted in /etc/modprobe.d/fbdev-blacklist.conf, but it's not compiled as an external kernel module (it's in the kernel itself) so the blacklisting doesn't work. On Thu, 9/18/14, Michel Dänzer mic...@daenzer.net wrote: Subject: Re: Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC To: Bill Chatfield bill_chatfi...@yahoo.com Cc: 762...@bugs.debian.org Date: Thursday, September 18, 2014, 2:24 AM On 18.09.2014 13:23, Bill Chatfield wrote: [ 0.997986] radeonfb :00:10.0: enabling device (0006 - 0007) [ 1.193788] radeonfb :00:10.0: Invalid ROM contents [ 1.193813] radeonfb (:00:10.0): Invalid ROM signature 303 should be 0xaa55 [ 1.193823] radeonfb: Retrieved PLL infos from Open Firmware [ 1.193842] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, System=392.00 MHz [ 1.193864] radeonfb: PLL min 12000 max 35000 [ 1.289994] i2c i2c-2: unable to read EDID block. [ 1.441986] i2c i2c-2: unable to read EDID block. [ 1.593986] i2c i2c-2: unable to read EDID block. [ 1.949865] radeonfb: Monitor 1 type LCD found [ 1.949881] radeonfb: EDID probed [ 1.949893] radeonfb: Monitor 2 type no found [ 1.949915] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0 [ 1.949981] radeonfb: Dynamic Clock Power Management enabled [ 1.982573] Console: switching to colour frame buffer device 160x53 [ 2.004457] radeonfb: Backlight initialized (radeonbl0) [ 2.004635] radeonfb (:00:10.0): ATI Radeon 4e50 NP This shows that radeonfb is still enabled, so it doesn't provide the information corresponding to the bug. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1411050789.6500.yahoomailba...@web124705.mail.ne1.yahoo.com
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
Package: xserver-xorg-video-ati Version: 1:7.4.0-2 Severity: important Dear Maintainer, * What led up to the situation? This happend with the default PowerPC install for Jessie testing. * What exactly did you do (or not do) that was effective (or ineffective)? I tried switching to a virtual console but got no response. I was able to blindly enter my userid and password so that the Xfce desktop came up, but in 8 bit color. If I run 'Xorg -configure' I get a segfault. If I boot with the following kernel parameters I get a normal visible session, but with software rendering. That is the configuration under which I'm sending this bug report, so automatically generated information might not be the same as when the bug occurs. video=radeonfb:1280x854-32@60 I have determined that radeonfb is compiled into the kernel, but drm and the newer radeon kernel modules are still being loaded. This seems wrong, but it is a default configuration. I'm happy to continue with the radeonfb driver since it provides suspend/resume capabilities for my laptop. But, I'm filing the bug because the default configuration is broken for PowerPC with the Radeon video card. Also, I'd like to get hardware rendering working. I can collect more info by logging in via ssh when the bug occurs. -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 Sep 14 15:37 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 2494636 Sep 8 20:43 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- :00:10.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV350/M10 [Mobility Radeon 9600 PRO Turbo] [1002:4e50] /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 3.14-2-powerpc (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-7) ) #1 Debian 3.14.15-2 (2014-08-09) Xorg X server log files on system: -- -rw-r--r-- 1 root root 22364 Sep 14 23:03 /var/log/Xorg.1.log -rw-r--r-- 1 root root 28598 Sep 16 14:51 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [37.150] X.Org X Server 1.16.0 Release Date: 2014-07-16 [37.150] X Protocol Version 11, Revision 0 [37.150] Build Operating System: Linux 3.2.0-4-powerpc64 ppc Debian [37.151] Current Operating System: Linux powerbook 3.14-2-powerpc #1 Debian 3.14.15-2 (2014-08-09) ppc [37.151] Kernel command line: root=UUID=7f71a9ac-30da-4195-89c5-6dffcbe357b4 ro video=radeonfb:1280x854-32@60 [37.151] Build Date: 09 September 2014 12:37:15AM [37.151] xorg-server 2:1.16.0-2+b1 (http://www.debian.org/support) [37.151] Current version of pixman: 0.32.6 [37.151]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [37.151] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [37.152] (==) Log file: /var/log/Xorg.0.log, Time: Tue Sep 16 14:51:14 2014 [37.206] (==) Using system config directory /usr/share/X11/xorg.conf.d [37.244] (==) No Layout section. Using the first Screen section. [37.244] (==) No screen section available. Using defaults. [37.244] (**) |--Screen Default Screen Section (0) [37.244] (**) | |--Monitor default monitor [37.258] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [37.258] (==) Automatically adding devices [37.258] (==) Automatically enabling devices [37.258] (==) Automatically adding GPU devices [37.457] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [37.457]Entry deleted from font path. [37.696] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [37.696] (==) ModulePath set to /usr/lib/xorg/modules [37.696] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [37.725] (II) Loader magic: 0x20710698 [37.725] (II) Module ABI versions: [37.725]X.Org ANSI C Emulation: 0.4 [37.725]X.Org Video Driver: 18.0 [37.725]X.Org XInput driver : 21.0 [37.725]X.Org Server Extension : 8.0 [37.727] (--) PCI:*(0:0:16:0) 1002:4e50:1002:4e50 rev 0, Mem @ 0xb800/134217728, 0xb000/65536, I/O @ 0x0400/256, BIOS @
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
On 18.09.2014 09:01, Bill Chatfield wrote: I tried switching to a virtual console but got no response. I was able to blindly enter my userid and password so that the Xfce desktop came up, but in 8 bit color. [...] If I boot with the following kernel parameters I get a normal visible session, but with software rendering. That is the configuration under which I'm sending this bug report, so automatically generated information might not be the same as when the bug occurs. Right, please provide the Xorg.0.log file and the output of dmesg corresponding to the bug. video=radeonfb:1280x854-32@60 I have determined that radeonfb is compiled into the kernel, but drm and the newer radeon kernel modules are still being loaded. This seems wrong, but it is a default configuration. I'm happy to continue with the radeonfb driver since it provides suspend/resume capabilities for my laptop. But, I'm filing the bug because the default configuration is broken for PowerPC with the Radeon video card. Also, I'd like to get hardware rendering working. Hardware acceleration is only possible with radeon KMS anymore, not with radeonfb. -- Earthling Michel Dänzer| http://www.amd.com Libre software enthusiast |Mesa and X developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/541a360d.9060...@daenzer.net
Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC
Xorg.0.log: [29.626] X.Org X Server 1.16.0 Release Date: 2014-07-16 [29.626] X Protocol Version 11, Revision 0 [29.626] Build Operating System: Linux 3.2.0-4-powerpc64 ppc Debian [29.626] Current Operating System: Linux powerbook 3.14-2-powerpc #1 Debian 3.14.15-2 (2014-08-09) ppc [29.626] Kernel command line: root=UUID=cc84edf8-5d66-4743-b12c-c1a21e26036b ro [29.626] Build Date: 09 September 2014 12:37:15AM [29.626] xorg-server 2:1.16.0-2+b1 (http://www.debian.org/support) [29.626] Current version of pixman: 0.32.6 [29.626]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [29.626] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [29.627] (==) Log file: /var/log/Xorg.0.log, Time: Thu Sep 18 00:12:07 2014 [29.832] (==) Using system config directory /usr/share/X11/xorg.conf.d [29.979] (==) No Layout section. Using the first Screen section. [29.979] (==) No screen section available. Using defaults. [29.979] (**) |--Screen Default Screen Section (0) [29.979] (**) | |--Monitor default monitor [30.044] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [30.044] (==) Automatically adding devices [30.044] (==) Automatically enabling devices [30.044] (==) Automatically adding GPU devices [30.278] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [30.278]Entry deleted from font path. [30.512] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [30.512] (==) ModulePath set to /usr/lib/xorg/modules [30.512] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [30.528] (II) Loader magic: 0x20562698 [30.528] (II) Module ABI versions: [30.528]X.Org ANSI C Emulation: 0.4 [30.528]X.Org Video Driver: 18.0 [30.528]X.Org XInput driver : 21.0 [30.528]X.Org Server Extension : 8.0 [30.530] (--) PCI:*(0:0:16:0) 1002:4e50:1002:4e50 rev 0, Mem @ 0xb800/134217728, 0xb000/65536, I/O @ 0x0400/256, BIOS @ 0x/131072 [30.591] (II) LoadModule: glx [30.635] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [31.774] (II) Module glx: vendor=X.Org Foundation [31.774]compiled for 1.16.0, module version = 1.0.0 [31.774]ABI class: X.Org Server Extension, version 8.0 [31.774] (==) AIGLX enabled [31.777] (==) Matched ati as autoconfigured driver 0 [31.777] (==) Matched modesetting as autoconfigured driver 1 [31.777] (==) Matched fbdev as autoconfigured driver 2 [31.777] (==) Assigned the driver to the xf86ConfigLayout [31.777] (II) LoadModule: ati [31.802] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [31.832] (II) Module ati: vendor=X.Org Foundation [31.832]compiled for 1.15.99.904, module version = 7.4.0 [31.832]Module class: X.Org Video Driver [31.832]ABI class: X.Org Video Driver, version 18.0 [31.832] (II) LoadModule: radeon [31.833] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [31.943] (II) Module radeon: vendor=X.Org Foundation [31.943]compiled for 1.15.99.904, module version = 7.4.0 [31.943]Module class: X.Org Video Driver [31.943]ABI class: X.Org Video Driver, version 18.0 [31.943] (II) LoadModule: modesetting [31.944] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [31.969] (II) Module modesetting: vendor=X.Org Foundation [31.969]compiled for 1.15.99.904, module version = 0.9.0 [31.969]Module class: X.Org Video Driver [31.969]ABI class: X.Org Video Driver, version 18.0 [31.969] (II) LoadModule: fbdev [31.970] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [31.971] (II) Module fbdev: vendor=X.Org Foundation [31.971]compiled for 1.15.99.904, module version = 0.4.4 [31.971]Module class: X.Org Video Driver [31.971]ABI class: X.Org Video Driver, version 18.0 [31.971] (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI), ATI Radeon Mobility X300 (M24) 3152 (PCIE), ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI), ATI Radeon X600 (RV380) 3E50 (PCIE), ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP), ATI Radeon 9500 AE (AGP),
