[Ubuntu-x-swat] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

2016-09-07 Thread seeker5528
Christopher, I filed the report and subscribled you. For others following here. Did also find out in my case it happens when the monitor is attached with a VGA cable. It does not happen if I use a DVI cable to connect the monitor. Still have to test have to test with monitor connected on HDMI

[Ubuntu-x-swat] [Bug 1621265] [NEW] lose monitor during boot up if I don't add 'nomodeset' to kernel options

2016-09-07 Thread seeker5528
Public bug reported: If I connect my monitor to my computer with a VGA cable, I have to stop at the grub menu and add 'nomodeset' to the kernel options with all the 4.4.0-* kernels. If I do not add 'nomodeset' to the kernel options, my monitor goes blank, complains of no video signal, then goes

[Ubuntu-x-swat] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

2016-09-05 Thread seeker5528
Symptoms are as reported by others. Whether it's during boot or attempting to enable after boot up. Screen goes black, reports no video, then goes to sleep. When it happens on boot, I can hit 'Ctrl'+'Alt'+'Del' or hit the power button and the machine will reboot or shut down so things are still

[Ubuntu-x-swat] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

2016-09-05 Thread seeker5528
Don't know where mode setting broke, had my box set aside for a while, so didn't get all my normal updating in. I'm on Yakkety. The most recent Ubuntu kernel that I have on my machine that did KMS was 4.3.0-5.16 None of the 4.4 kernels images work without adding nomodeset to the grub options.

[Ubuntu-x-swat] [Bug 588940] Re: Xorg freeze drm radeon 'Faild to schedule IB'

2010-06-12 Thread seeker5528
Had enough running time now to consider the issue closed, my best guess is that it must have been some kind of firmware issue that was fixed by the newer linux-firmware package, since I seem to be the only one that was affected, changing the status of the bug. ** Changed in:

[Ubuntu-x-swat] [Bug 588940] Re: Xorg freeze drm radeon 'Faild to schedule IB'

2010-06-07 Thread seeker5528
I'm a little hesitant to say this is fixed until I get more running time, but since the framebuffer and linux-firmware packages were updated I switched X back to using the radeon driver, ran for a while with no lock ups, took the 'nomodeset' option out of the boot up and am currently running Gnome

[Ubuntu-x-swat] [Bug 588940] Re: Xorg freeze drm radeon 'Faild to schedule IB'

2010-06-03 Thread seeker5528
Have you tried booting with pci=nomsi ? Nothing in /proc/interupts made it look like msi was being used, but I tried the 'pci=nomsi' thing anyway, no difference. There is a difference with the 'nomodeset' in there, in that it takes longer for there to be a problem, less likely to be hard locked,

[Ubuntu-x-swat] [Bug 588940] [NEW] Xorg freeze drm radeon 'Faild to schedule IB'

2010-06-02 Thread seeker5528
Public bug reported: Binary package hint: xorg Freezes at various times could be any time during boot or later. At times I am able to switch to VT 1 and see error messages displayed. Jun 2 12:03:49 ubuntu kernel: [ 578.361780] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule

[Ubuntu-x-swat] [Bug 588940] Re: Xorg freeze drm radeon 'Faild to schedule IB'

2010-06-02 Thread seeker5528
** Attachment added: system log since http://launchpadlibrarian.net/49576192/syslog ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/49575737/BootDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/49575738/Dependencies.txt ** Attachment

[Ubuntu-x-swat] [Bug 588940] Re: Xorg freeze drm radeon 'Faild to schedule IB'

2010-06-02 Thread seeker5528
I guess it should also be noted that I booted with some of my previously installed kernels including linux-image-2.6.32-22-generic and the issue is the same so it seems to be something in the mesa/xorg part of the equation. -- Xorg freeze drm radeon 'Faild to schedule IB'