On Mit, 2011-01-05 at 16:43 -0500, dpickett wrote:
On Jan 5, 2011, at 9:53 AM, Michel Dänzer wrote:
On Die, 2011-01-04 at 14:35 -0500, dpickett wrote:
The monitor does not go blank: it loses signal as the entire machine
locks up. After starting X, I see a brief flash of text, then the
Referenced the modeline in the Display subsection, but didn't see to change
anything. I read through the xorg_conf man page and constructed what I think is
the minimal xorf_conf I could, but no avail.
Grepping the xorg.log for 1680 gives:
(II) RADEON(0): Adding Screen mode: 1680x1050
(II)
On Die, 2011-01-04 at 14:35 -0500, dpickett wrote:
The monitor does not go blank: it loses signal as the entire machine
locks up. After starting X, I see a brief flash of text, then the
monitor flashes no signal and the entire machine locks up. An ssh
session on another machine is locked up,
On Jan 5, 2011, at 9:53 AM, Michel Dänzer wrote:
On Die, 2011-01-04 at 14:35 -0500, dpickett wrote:
The monitor does not go blank: it loses signal as the entire machine
locks up. After starting X, I see a brief flash of text, then the
monitor flashes no signal and the entire machine locks up.
On Mon, 2011-01-03 at 18:10 -0500, dpickett wrote:
The xorg.log and gdm log do look different, though. It doesn't look
like the card is freezing up any more.
Indeed, looks like X is up and running with the DRI enabled now. So what
are the current symptoms, blank monitor? Can you switch to
The monitor does not go blank: it loses signal as the entire machine locks up.
After starting X, I see a brief flash of text, then the monitor flashes no
signal and the entire machine locks up. An ssh session on another machine is
locked up, and I can not ping the Linux machine. The only way to
On Son, 2011-01-02 at 16:46 -0500, dpickett wrote:
I'm seeing a few more entries for drm in the dmesg output, but the
kernlog looks like it's not updating.
There is DRM debugging output now, but nothing from the X server
startup. If the system stays responsive after X startup, make sure to
On Sun, Jan 2, 2011 at 00:56:52 -0500, dpickett wrote:
image=/boot/vmlinux
label=Linux
read-only
initrd=/boot/initrd.img
append=video=ofonly
It needs to be added to the 'append' line.
Cheers,
Julien
signature.asc
Description: Digital signature
On Fre, 2010-12-31 at 21:13 -0500, dpickett wrote:
I added drm.debug=7 to my /etc/yaboot.conf, which is, I think, the
right way. dmesg and kernlog text files attached. From my untutored
reading of the files, it looks as if drm is being enabled.
Well, that didn't work — as you can see, there's
On Sat, Jan 1, 2011 at 18:26:23 -0500, dpickett wrote:
Dec 31 19:00:11 G5 kernel: [0.00] Kernel command line: root=/dev/sdb3
ro video=ofonly
Dec 29 21:33:13 G5 kernel: [0.00] Kernel command line: root=/dev/sdb3
ro video=ofonly
Dec 29 21:49:58 G5 kernel: [0.00]
From what I understand, I should add drm.debug=7 to my yaboot.conf, run ybin
and reboot. This is what I did. If I'm wrong, please tell me what I'm doing
wrong. yaboot.conf attached.
## yaboot.conf generated by debian-installer
##
## run: man yaboot.conf for details. Do not make changes until
On Don, 2010-12-30 at 16:06 -0500, dpickett wrote:
firmware-linux wasn't installed. I installed it and rebooted. Same
blank screen, but this time the machine froze up completely. I
couldn't ssh into it or ping it.
Grepping dmesg for AGP produces:
[0.711199] Linux agpgart interface
Just booted and attempted to start X. This is the Xorg.0.log from that attempt.
X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.26-2-powerpc64 ppc Debian
Current Operating System: Linux G5 2.6.32-5-powerpc64 #1 SMP Fri Dec 10
On Fre, 2010-12-31 at 03:44 -0500, dpickett wrote:
Just booted and attempted to start X. This is the Xorg.0.log from that
attempt.
No change... Still not sure why the DRI ends up being disabled. :( Can
you try booting with drm.debug=7 on the kernel command line, starting X
and providing the
On Don, 2010-12-30 at 00:28 -0500, dpickett wrote:
Installed Debian Squeeze. Looks like things are somewhat better.
For the first reboot after install I got an enlarged mouse cursor in
the middle of a blank screen. I then copied over the last xorg_conf
file and rebooted. X started, I got a
Looks like my system is a Lenny system. Should I try Squeeze?
On Dec 27, 2010, at 5:02 AM, Michel Dänzer wrote:
On Mon, 2010-12-27 at 10:57 +0100, Michel Dänzer wrote:
On Sam, 2010-12-25 at 17:29 -0500, dpickett wrote:
It appears the entire machine is locking up when I try to startx.
I
On Sam, 2010-12-25 at 17:29 -0500, dpickett wrote:
It appears the entire machine is locking up when I try to startx.
I can boot the machine into Linux single mode and ssh into it from
another machine. When I type startx the see several lines of text
flash by, and then a blank screen. The
On Mon, 2010-12-27 at 10:57 +0100, Michel Dänzer wrote:
On Sam, 2010-12-25 at 17:29 -0500, dpickett wrote:
It appears the entire machine is locking up when I try to startx.
I can boot the machine into Linux single mode and ssh into it from
another machine. When I type startx the see
It appears the entire machine is locking up when I try to startx.
I can boot the machine into Linux single mode and ssh into it from another
machine. When I type startx the see several lines of text flash by, and then
a blank screen. The ssh window on the other machine freezes. I can't ping the
On Don, 2010-12-23 at 17:13 -0500, dpickett wrote:
In /etc/modprobe.d there is radeon-kms.conf.
more radeon-kms.conf gives: options radeon modeset=0
I removed radeon-kms.conf from the /etc/modprobe.d directory and
rebooted. Still got a blank screen, but the xorg.log attached no
longer
On Wed, Dec 22, 2010 at 17:53:58 -0500, dpickett wrote:
Result of sudo modprobe radeon
[193.258609] [drm] Initialized drm 1.1.0 20060810
[193.276846] radeon: Unknown parameter 'modeset'
FATAL: Error inserting radeon
(/lib/modules/2.6.26-2-powerpc64/kernel/drivers/char/drm/radeon.ko):
In /etc/modprobe.d there is radeon-kms.conf.
more radeon-kms.conf gives: options radeon modeset=0
I removed radeon-kms.conf from the /etc/modprobe.d directory and rebooted.
Still got a blank screen, but the xorg.log attached no longer shows the GPU
timing out.
X.Org X Server 1.4.2
Release
On Die, 2010-12-21 at 17:42 -0500, dpickett wrote:
Package: X11-common
Version: 1:7.3+20
Error message from Xorg.0.log: (EE) RADEON(0): [dri]
RADEONDRIGetVersion failed to open the DRM
Are there any hints in the dmesg output as to why the radeon kernel
module fails to load / initialize? If
On Mit, 2010-12-22 at 03:47 -0500, dpickett wrote:You will have to forgive me, because I am a relative Linux newcomer,and may not be able to answer all your questions.I did do 'dmesg | grep drm', but it returns nothing. dmesg | grep agpreturns as it should.Please provide the actual output rather
Package: X11-common
Version: 1:7.3+20
Error message from Xorg.0.log: (EE) RADEON(0): [dri] RADEONDRIGetVersion failed
to open the DRM
To reproduce this bug, I have to boot into X on my machine. Machine goes
through normal start up procedures, starts X and presents a completely blank
screen.
25 matches
Mail list logo
