Quote:
Code:
pawn57@deb:~$ su root Code:
pawn57@pawn57-Inspiron-660:~$ cat /var/log/Xorg.0.log | grep -i "dri" | grep -v -i "driver" Code:
pawn57@deb:~$ cat /var/log/Xorg.0.log | grep -i "dri" | grep -v -i "driver" |
X.org is a little newer on Ubuntu. How would you feel about doing a separate install of Stretch/Testing?
|
Quote:
|
So your problem appears to be here:
Quote:
Quote:
Code:
lsmod |
Quote:
As always I get this error... Code:
[drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
Quote:
Code:
root@debian:/home/pawn57# lsmod Code:
dmesg | grep -E 'drm|radeon' | grep -iE 'firmware|microcode' Code:
root@debian:/home/pawn57# dmesg | grep -E 'drm|radeon' | grep -iE 'firmware|microcode' |
For one thing, you have to remember that this is Stretch, so you'll want to use Stretch repositories, not jessie ones. I'm not sure if that could be the problem, but replace "jessie" with "stretch", then update.
|
After that, please post your Xorg.0.log from Stretch if you've got everything configured correctly. (That is, not including your second monitor.)
|
Quote:
|
That's true, but if you test in Stretch, then you will have better insight into how actually to get it working in Jessie.
|
1 Attachment(s)
Amazing! I reinstalled debian and firmware-linux-nonfree package. https://wiki.debian.org/AtiHowTo
Then I was reading at http://superuser.com/questions/94592...and-3-monitors Then I entered this command (from that page)... Code:
xrandr --setprovideroutputsource 1 0 I know have BOTH monitors working in debian!!! but will probly have to run that command each time I boot until I set it auto some how as the page I copied it from says .. Quote:
Thanks to everyone who has been trying to help me! This is my install below... Code:
root@debian:/home/pawn57# lsb_release -irc |
Probably the easiest way is to make an autostart in MATE that runs that same command. It would be nice to know a) what xrandr is doing here, and b) why Debian doesn't do it automatically.
|
1 Attachment(s)
Quote:
My main concern now is getting the display to behave normal or properly. It has errors. It is not working like it should as I explained a few posts ago. (I remember there was a few distros that it came on automatically in, but had some problems simmiler to this but slightly different. I think MINT was one.) It is capable of working properly, as it does in windows and ubuntu/mate as proof. I have attatched an actual photograph below to show the abnormal behavior, as it doesn't show up in screen shots. This is the display on the right connected to the (Radeon HD 8670 / R7 250) that is having problems as seen in the attatched photograph. |
Quote:
|
Recent warning about Debian Unstable that applies to what you are testing.
http://forum.siduction.org/index.php?topic=6032.0 I know you are not messing with Sid. Just posting recent info in case someone suggests it. |
Stretch is Testing. Stretch is the next release of Debian after Jessie. In a few months, Stretch will become Stable, and Jessie will be bumped to Oldstable. But it's currently being tested, thus the name. Packages are being updated because bugs and security problems are being found. So your sources.list would have every instance of "jessie" replaced with "stretch" or "testing" which are one and the same.
|
All times are GMT -5. The time now is 05:52 AM. |