second monitor not working. Debian GNU/Linux 8.2 (jessie) ( Radeon HD 8670 / R7 250 AND Xeon E3-1200 )

1redto · 01-15-2016, 12:28 AM

I have onboard hdmi and an added card with hdmi. if I install windows or ubuntu, both monitors work automatically without me doing anything. I have debian installed by itself currently and only the hdmi onboard is working. I am new to linux and jsut discovered the terminal and researched some comands to get the outputs displayed below. Can anyonone help me get my other hdmi monitor working with this debian installation? Thanks

pawn57@debian:~$ uname -r
3.16.0-4-amd64
pawn57@debian:~$ cat /proc/version
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt20-1+deb8u2 (2016-01-02)
pawn57@debian:~$ cat /proc/sys/kernel/{ostype,osrelease,version}
Linux
3.16.0-4-amd64
#1 SMP Debian 3.16.7-ckt20-1+deb8u2 (2016-01-02)
pawn57@debian:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.2 (jessie)
Release: 8.2
Codename: jessie

pawn57@debian:~$ lspci

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4)
00:1f.0 ISA bridge: Intel Corporation B75 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
03:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
pawn57@debian:~$

pawn57@debian:~$ xrandr

Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm
1920x1080 60.00*+ 60.00 59.94 30.00 24.00 29.97 23.98
1920x1080i 60.00 59.94
1280x1024 60.02
1360x768 60.02
1152x864 59.97
1280x720 60.00 59.94
1024x768 60.00
800x600 60.32
720x480 60.00 59.94
640x480 60.00 59.94 59.94
720x400 70.08
DP1 disconnected (normal left inverted right x axis y axis)

I typed dmesg and a lot of data came up but what I copied below seemed to be odd or maybe bad. I hope not...

BELOW is some of the info that displayed when I typed dmesg...

[ 14.793248] ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB_.PCI0.SBUS.SMBI) (20140424/utaddress-254)
[ 14.793253] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 14.868432] pstore: Registered efi as persistent store backend
[ 14.913962] [drm] Initialized drm 1.1.0 20060810
[ 14.930462] mei_me 0000:00:16.0: irq 45 for MSI/MSI-X
[ 15.001892] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20140424/utaddress-254)
[ 15.001897] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 15.001901] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140424/utaddress-254)
[ 15.001903] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 15.001904] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140424/utaddress-254)
[ 15.001906] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 15.001907] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20140424/utaddress-254)
[ 15.001909] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 15.001910] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 15.038487] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 15.205297] snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
[ 15.205455] snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
[ 15.205511] snd_hda_intel 0000:01:00.1: Handle VGA-switcheroo audio client
[ 15.205514] snd_hda_intel 0000:01:00.1: Force to non-snoop mode
[ 15.205737] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
[ 15.205806] snd_hda_intel 0000:01:00.1: irq 47 for MSI/MSI-X
[ 15.307940] [drm] Memory usable by graphics device = 2048M
[ 15.307955] checking generic (d0000000 300000) vs hw (d0000000 10000000)
[ 15.307957] fb: switching to inteldrmfb from simple
[ 15.307992] Console: switching to colour dummy device 80x25
[ 15.308061] [drm] Replacing VGA console driver
[ 15.329588] i915 0000:00:02.0: irq 48 for MSI/MSI-X
[ 15.329601] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 15.329602] [drm] Driver supports precise vblank timestamp query.
[ 15.329709] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=none

wns=none
[ 15.434798] fbcon: inteldrmfb (fb0) is primary device
[ 15.449755] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input7
[ 15.460646] Console: switching to colour frame buffer device 240x67
[ 15.460736] [drm:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder A
[ 15.460737] [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
[ 15.465233] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 15.465235] i915 0000:00:02.0: registered panic notifier

1redto · 01-15-2016, 12:58 AM

Clarification; I did not pit the emotion icon in the following line...
(added extra space around the colon hope that removes it.)

[ 15.329709] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=none : owns=none

1redto · 01-15-2016, 08:19 PM

If nobody can help, where can I find out if it is possible to fix?
Am I stuck with only one display if I stay with debian?

rokytnji · 01-15-2016, 09:38 PM

Quote:

If nobody can help, where can I find out if it is possible to fix? Am I stuck with only one display if I stay with debian?

Nope. You shouldn't. Hint

Code:

xvidtune -show

Code:

glxinfo | grep -i "direct rendering"

Code:

cat /var/log/Xorg.0.log | grep -i "dri" | grep -v -i "driver"

Debian ships with no proprietary drm graphics drivers for

Code:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250]

So you are using the open source driver I bet instead. My above commands will reveal what you are running. You can run those commands in Ubuntu and Debian and compare the differences then.
Ubuntu is not as strict as Debian when it comes to including proprietary support for hardware like video cards. Debian uses only free software.

Edit: you should put your terminal readouts like dmesg and lspci in code tags like I did mine in my post.

1redto · 01-15-2016, 10:32 PM

Quote:

Originally Posted by rokytnji

Nope. You shouldn't. Hint

Thank you! for trying to help. I sooo appreciate it!

Does "Nope. You shouldn't. Hint" mean I should't use debian?

Update: I made a live usb for Mint 17.3 Mate and intsalled it. That is what I'm booted into at the moment. With this mint/mate both my monitors are working but the one connected to the video card has a problem. When ever I drag a window on it, it leaves a trail of the movement on the screen. Do you know how to remedy this in Mint? I went ahead and entered the codes you gave me but it still does it. I am going to attach a photo of the screen for you. Then I will boot back into debian and enter the codes you left and try to follow the driver link you posted for me.

Thanks for helping me.

1redto · 01-15-2016, 10:51 PM

Quote:

Originally Posted by rokytnji

....

Ok. I'm back in debian (only 1 monitor, working)
I try to do the directions in the link but getting errors see below...

Code:

pawn57@debian:~$ deb http://httpredir.debian.org/debian/ jessie main contrib non-free
bash: deb: command not found
pawn57@debian:~$ sudo deb http://httpredir.debian.org/debian/ jessie main contrib non-free
[sudo] password for pawn57: 
pawn57 is not in the sudoers file.  This incident will be reported.
pawn57@debian:~$ su root
Password: 
root@debian:/home/pawn57# deb http://httpredir.debian.org/debian/ jessie main contrib non-free
bash: deb: command not found
root@debian:/home/pawn57#

???
now I will do the other codes...

Code:

root@debian:/home/pawn57# xvidtune -show
"1920x1080"   148.50   1920 2008 2052 2200   1080 1084 1089 1125 +hsync +vsync

root@debian:/home/pawn57# glxinfo | grep -i "direct rendering"
direct rendering: Yes
root@debian:/home/pawn57# cat /var/log/Xorg.0.log | grep -i "dri" | grep -v -i "driver"
[    13.989] (II) xfree86: Adding drm device (/dev/dri/card0)
[    14.837] (II) Loading sub module "dri2"
[    14.837] (II) LoadModule: "dri2"
[    14.837] (II) Module "dri2" already built-in
[    14.845] (II) intel(0): [DRI2] Setup complete
[    14.875] (II) intel(0): direct rendering: DRI2 Enabled
[    15.821] (II) GLX: Initialized DRI2 GL provider for screen 0
root@debian:/home/pawn57#

Now what do you recomend?

Thank you for your time and help.

1redto · 01-15-2016, 11:11 PM

I see I misunderstood the first direction. I was suposed to add to sources. Now am trying to open it to edit and it was read only so I try looking at permissions and am blocked...

1redto · 01-15-2016, 11:46 PM

I really hope I get my monitor working but i am just curious...

Just a side thought. Why does linux drivers have to be so difficult? What difference does it make if people use the free driver or the proprietary one? If the proprietary driver works and I use it am I supposed to pay the company that made it because I chose to use it? If I am supposed to pay them if I use it how does that work? Do I write them a letter and say "Dear AMD/ATI, I'm using you driver because the linux one don't work. How much should I pay you? Would you like me to send you a check?"...
If it's not required to pay them and there driver works but the linux one don't then why on earth does the distro include the broken driver instead of the good one?

beachboy2 · 01-16-2016, 03:49 AM

1redto,

Quote:

Why does linux drivers have to be so difficult?

Because most hardware is made for Microsoft operating systems. The hardware is not made with Linux in mind. That is the way things are.

Some manufacturers are more Linux-friendly than others (e.g Intel and HP).

I suggest that you reply to rokytnji with all the information he requested.

He is extremely knowledgeable in such matters and he should be able to help you fix this problem.

1redto · 01-16-2016, 05:49 AM

Quote:

Originally Posted by rokytnji

Nope. You shouldn't. Hint

Well I followed the link you gave me and managed to add the source and update the driver then reboot and both screens were black. so I rebooted into mint and was trying to fix it from there and when I rebooted it was still black on both screens. so then I rebooted to mint again and apparently I screwed it up when I was trying to fix debian. so now neither will boot. I am currently booted from a live usb of zorin. Both monitors are working but there is intermittent artifacts and mouse disappearing and flickering a lot but at least the computer is working and I see both monitors. I suppose I will install this zorn now since it is working except for the flickering. I am so frustrated. I really would like a solid linux that is traditional, works excellent and is really fast, simple and secure. I don't want to go back to windows 10. it works good but I hate the fact that it gives the user so little control of what the pc does and how it operates.

1redto · 01-16-2016, 07:40 AM

Quote:

Originally Posted by rokytnji

...

Now I have zorin os 9 installed. when I boot I can select debian, debian advanced options, mint, mint advanced options, zorin, zorin advanced options. debian and mint are broken. zorin works on both screens but the mouse cursor flickers bad on the screen connected to the onboard hdmi. and the other screen has some artifact problems, it seems not to refresh repaint itself quickly or something like that at times. it is hard to explain but I know its not working like it should.

1redto · 01-16-2016, 08:46 AM

Quote:

Originally Posted by rokytnji

...

Now that I am running zorin os 9, If I go to additional drivers and choose fglrx driver and reboot I only get the screen connected to the AMD card, but it works perfect. the mouse, the moving of the windows around, the cursor and pointer all work perfect. Why does the other display not come on? Now if I go and change it back to AMD/ATI display driver wrapper from xserver-xorg-video-ati then reboot both screens come on but neither one behaves perfect. They both seem to struggle to act the way they should. Is it possible that instead of using the AMD fglrx (the only other option listed in "additional drivers" settings) there might be a flgr for the Xeon onboard hdmi that might work both screens if used? Or is there a way to use the AMD fglrx (only other option appearing in "additional drivers" setting, which works perfect but only one screen comes on, and then do something to make the other screen come on too? I would love to get them both to work perfect like they should. What do you recomend I do? Thank you for your time and help. Anyone reading this who can offer help, I appreciate it.

1redto · 01-16-2016, 08:59 AM

I will show you the results of the codes you told me to do....
both ways (now, ... then I will change the driver, reboot and post the new results)

This is in zorin and using fglrx and only one screen working (but working perfect) ....

Code:

pawn57@pawn57-Inspiron-660:~$ xvidtune -show
"1920x1080"   148.50   1920 2008 2052 2200   1080 1084 1089 1125 +hsync +vsync

pawn57@pawn57-Inspiron-660:~$ glxinfo | grep -i "direct rendering"
direct rendering: Yes
pawn57@pawn57-Inspiron-660:~$ cat /var/log/Xorg.0.log | grep -i "dri" | grep -v -i "driver"
[    28.958] (II) xfree86: Adding drm device (/dev/dri/card0)
[    28.959] Initializing built-in extension DRI3
[    28.959] Initializing built-in extension XFree86-DRI
[    28.959] Initializing built-in extension DRI2
[    30.446] (==) fglrx(0): NoDRI = NO
[    30.446] Loading extension ATIFGLRXDRI
[    30.446] (II) fglrx(0): doing swlDriScreenInit
[    30.446] (II) fglrx(0): swlDriScreenInit done
[    30.477] (II) fglrx(0): DRI initialization successfull
[    30.617] (II) fglrx(0): [DRI] installation complete
[    30.911] (EE) AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
[    30.911] (EE) AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
[    30.911] (EE) AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]
[    32.270] (II) fglrx(0): OverDrive5 Detected!
[    32.426] (II) config/udev: Adding drm device (/dev/dri/card0) card0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[    32.426] (II) config/udev: Ignoring already known drm device (/dev/dri/card0)
pawn57@pawn57-Inspiron-660:~$

rokytnji · 01-16-2016, 09:19 AM

I thought you were going to compare Debian readouts, with working readouts in like Ubuntu, so you could on your own

Quote:

where can I find out if it is possible to fix?

But I see you are all over the place , now on Zorin 9. Which I have never used for one.

lets see something. Lets see if zorin has

Code:

inxi -Fxx

If command not found. Look for inxi in Zorin package manager and install it and then rerun the command.

1redto · 01-16-2016, 09:23 AM

Well I changed the drive back and rebooted and now zorin is broke. It fashes up a screen that says you are running in low grafix or something and there is no mouse and then it eventually locks up or just goes to promt. so I just used the zorin live usb to boot. I dont know what to do. Mabee I will reinstall zorin. I am sad and discouraged.