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

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:owns=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

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

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

Debian ships with no proprietary drm graphics drivers for

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.

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.

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

Now what do you recomend?

Thank you for your time and help.

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...

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?

1redto,

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.

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.

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.

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.

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) ....

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

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

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

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.

Well the more I think about it, It is possible that ubuntu had both screens working too, but they just weren't right, just like on mint and zorin. I don't remember. that may be why I moved on from ubuntu or it may have been the unity thing. I know they work because they work perfect in windows 10 for sure. I guess I will go to my other pc and make an ubuntu usb again and use it and see what happens. Thank you for helping me. I will let you know what happens in ubutu.

OK. I'm very happy. I installed ubuntu mate and both screens seem to be working perfectly!!!

I run the commands...
this is with ubuntu mate and both screens working great...

Now what do I check or write down and record so any linux I install I can make work great too?
Thanks for your help.

Good things are working correctly.
With all the different problems you describe without enough info for me. Being here in Texas.

All I can figure is maybe you have been corrupt iso downloads and then installing a file corrupted install. That is my take on this thread.

Anyways. Good that you are running OK now. That is all that matters.
Happy Trailz, Rok

What do you write down? Might I suggest learn how to do a md5sum of a linux iso before running a live linux installer. It will save you from grief if you learn this. Youtube is full of md5sum tutorials and what they mean and describe why I mention this,

Thanks. Yes it is working. (On a side note my screens are "LG" 42 inch TV's and This and seems like every other distro detects them as "Goldstar Company Ltd 72 inch" I am looking into that now. But I am glad they are working properly.)

I have used md5sum in the past, but kind of lost the habit as it seemed it always showed the right sum. I even often wondered if the sum tool could have a malware in itself, there is so many free tools, but as you suggest I will read up on it again.

I am learning alot and am going to keep learning. I have been reading about video stuff now due to all this frustration. In the past I think I always gave up and went back to windows. So now I am reading about mesa glxinfo grep lspci x org commands et cetera. right now if I type...
I get...
If you look in the screen shot I attached , you will see my additional drivers shows xorg open source driver used for AMD and also an UNknown: Unknown using microdode firmware for Intel (proprietary) I believe this may have something to do with my past problems. Mabee it's possible that other distro's need that (unknown thing) to make my system work correctly. This is just a hunch.

Anyway I want to find out exactly what is going on in this current install (working wonderful and smoothly!! seems perfect!) because it seems every other time I have tried any other distro they have never actually worked properly. That is mostly why I was jumping around. I thought if this has problems and I broke it trying to correct it, then why reinstall it if I know it isn't working properly on my system. So I might as well try another and see if it will work.

Now that my system seems to be working marvelous (except that it detects "Goldstar" 72inch when I have "LG" 42inch) I want to find out exactly what it is doing that is so correct or different than what every other distro does, so that I can install other distros and then manually set them if I have to so that they work too.

1redto,

Glad to hear that you have solved your problem.

Please mark this thread as solved using the Tools tab on your original post.

Thanks, but it is not solved until I reinstall debian and get this working under debian as the problem in the title
of this thread states, which I hope to do soon.
I am going to get "Debian GNU/Linux 8.2 (jessie)" and check with md5sum as..
instructed by "rokytnji" and after checking it with md5sum, I will make a usb and install it. I will update this thread with my progress very soon.

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

My monitors are working great in my current installation of Ubuntu / mate, aside from being detected as "Goldstar" 72inch when I have "LG" 42inch.

I am working on getting debian 8.2 iso and checking md5sum then will create the usb and install along side this ubuntu to see if my original problem can be corrected.

ok I got debian-live-8.2.0-amd64-mate-desktop.iso from http://cdimage.debian.org/debian-cd/...64/iso-hybrid/

here is the md5sum listed at http://cdimage.debian.org/debian-cd/...hybrid/MD5SUMS ...

981a8502d50df86b9cda41e54071e4fc debian-live-8.2.0-amd64-mate-desktop.iso

981a8502d50df86b9cda41e54071e4fc (ran md5sum see above code)
981a8502d50df86b9cda41e54071e4fc (copied from site, link above)

Looks like a good match!

Now I will make the live USB

There it is (makeing of the live USB)...

Now I will boot the live USB and install Debian.

OK, Bad News so far....

(This post is from my spare pc) I booted from the live usb and installed debian (I had to disable secure boot to get the live debian usb to boot) I resized the biggest partition to make room and installed on the free space. as per on screen instructions That detected the ubuntu installation, and I did everything like it suggested. after install upon rebooting my pc says no boot device available. I can't get in on ubuntu/mate or debian. the pc is bricked. (thus why I'm posting from my spare pc) soooo what I have decide to to try is ... I will try and reboot from the debian live usb, do a clean install of debian only, then install ubuntu/mate again and see how that goes...

I will report back with my progress soon.

my bad. Disregard my last post.. I set my pc to boot legacy mode in bios and now I got menu for ubuntu/mate and debian!!!!!!!!! I just booted ubuntu, both screens still work perfect!! now I will reboot and select debian (will be my first boot into it) be back soon i hope...

As explained earlier. No surprise that a Debian install is not running a proprietary video driver blob in it's iso.

No matter either if Mate is in Debian. So expect a repeat of earlier results.
Without certain firmware and drivers. I expect failure in yor next post.

http://crunchbang.org/forums/viewtopic.php?id=25472

http://unix.stackexchange.com/questi...ust-cloning-it

https://awesome.naquadah.org/wiki/Us...ltiple_Screens

Here I am!!

I am happy I didn't have to reinstall again.

You are right. Failure. now I can boot both that is good. but debian this screen good the other is black . I have been trying sooooooo hard please keep helping me. I really appreciate it, and someday I will help other noobs. Ok I will read the links you posted and wait for your suggestions...

Thanks.

rokytnji

Thanks. The first two links don't seem to help me.
now on the third link, am I supposed to copy all that code an put it in the terminal? I don't want to brake anything so I will wait for your reply.
respectfully with best regards...

If anyone want's to help. By all means please jump right in. I am all ears. I don't want to break my system , that is why I wait for rokytnji, and I am a noob so I respect elders and experience. but if anyone want to help please try. if I break it again I can always reinstall it. I am so ecstatic with linux over windows. I will never go back even if it is crap forever with linux it is better than windows. feel free to help me If you can. I know there are many others who want to get this working too on their computers.

I never post links to just copy and paste code. My bad for not mentioning that. I post those links so you get a understanding of linux files like /etc/X11/xorg.conf or ~./xinitrc.

Every ones gear is different as well as what distro makes them comfortable. You are actually corresponding with a GED educated self educated linux using biker (look at my profile)

I am not formally IT trained and never had a interest in running a computer. I just learn things as I go. Like you, mostly.

I commend your efforts and respond to your posts because I see a kindred soul who likes to tinker like I do. My efforts is mostly to try and teach you a understanding of linux file structure. What a file does. How to understand what a terminal is telling you. Things that I learned the hard way without a formal education, or even a burning interest in learning it.

I am just stubborn is all. Waiting on me is kind of a waste of time. I am busy with outside projects outside of the computer/linux world and only come here as a "pay it forward" kind of thing, for all the lessons I have learned from this site.

Use the search function on this forum. It is how I learn. Sorry I am a kind of a disappointment that I do not supply a non thinking fix for this in Debian.

But. Look at my thread started count. I have become proficient by silently plodding along
on my own without the "quick fix" method. It is how I learn.

Keep at it. It is like learning Spanish. At 1st you do not know what is going on. All you know is every body else seems to get along using Spanish OK while your head is hurting.
Then when things start to click and make sense. It gets easier and easier.

I never was a Windows Power user. Probably why I am comfortable learning Gnu/Linux.
My head is not dumbed down by Windows preconceived expectations by just a left click.

Here is my intro into using computers

Mainly for buying motorcycle parts off of ebay. So no. Read and Understand what those threads talk about. No direct copy and paste. As a example. I keep a vesa driver /etc/X11/xorg.conf in my pastebin account to give me a desktop. Just a couple of line changes from computer to computer.

Because I understand what I am doing. I know

changes from hardware to hardware and that


But because I understand Linux

so that line on this laptop would read

for that line instead. Because Bus ID is different from hardware to hardware and just copying and pasting my saved /etc/X11/xorg.conf vesa driver file will not cut the mustard.
It just won't work and I will have a black screen if I just copy and paste. I need to change a line or 2. Which comes from understanding how things work.

That was why I said run commands. Copy and paste readouts lets say into a text file labeled
1. ubuntu_vga_x2
2. debian_vga_x2

compare readouts. Try and understand the differences. You have a computer to search why they are different. Then figure it out. Then. Like me. You own it. You now know what you are doing.
Like speaking Spanish.

Learning just "Hola" will not make you fluent in Spanish.
Which is the same as a quick fix with copy and paste. Then not understand what you just did.
I got long winded because of Football playoffs are keeping me seated.

Back to using my day light to do some outside work.

Thank you very much. You have helped me alot.

You are a great person. I am glad I was fortunate to get help from you. If not I probably would have gave up.

What you say makes perfect sense, and I will do it.

I am going to make text files of the readouts to see the differences, and then post them and explore and learn what they mean so that I will understand what it going on.

Xorg.0.log in ubuntu/mate part 1
 

ok this file I found called Xorg.0.log is real long so I will post its contents in several posts (linuxQuestion.org wont allow a post as long (big)as this file is, it to big so I will divide it up into smaller posts)

Xorg.0.log in ubuntu/mate part 2
 

Xorg.0.log in ubuntu/mate part 3
 

Xorg.0.log in ubuntu/mate part 4
 

Xorg.0.log in ubuntu/mate part 5
 

Ok I know that is a lot of stuff above, but I hope it will be useful to resolve this issue.

The 5 above posts are the contents of a file called Xorg.0.log found in a folder called /var/log

This is from the environment of a booted ubuntu/mate that is using both monitors correctly.

The issue I hope to resolve is I would like to get debian to use both monitors..

The next posts will be the same file from the debian environment that is not using both monitors as it only detects and uses 1 monitor...

Xorg.0.log from debian/mate part1
 

Ok. Now I am booted into debian / mate...

Only 1 monitor is working. the one plugged into the on-board hdmi works. the other one (plugged into the hdmi on the card) is black (not being used, or not detected)

The following is the contents of Xorg.0.log from a folder called /var/log (this is broken into parts because it is too big to post in one post)..

Xorg.0.log from debian/mate part2
 

OK this is the end. you can see it was a little smaller on debian and was able to fit in two posts.

Ok. I know that is a lot of stuff to look at, but I hope it will help to get this resolved. I will be studying and searching google all i can. and trying to fix this.. Anyone who can help, I thank you very much.

Ok do ing this on both setups.....
now I'm on ubuntu/mate both screens work good... here is the output...

do ing this on both setups.....
now I'm on DEBIAN/mate ONLY ONE screens works...
THIS IS THE ENVIRONMENT THAT DON"T WORK RIGHT!!!!!!! here is the output...

If Ubuntu works - stick with it. Debian has an aversion to proprietary stuff and can be a PITA - especially with unique hardware setups.

Learn what you're doing with Ubuntu and when you gain some experience and knowledge then maybe branch out...

a·ver·sion
əˈvərZHən/Submit
noun
a strong dislike or disinclination.
"he had a deep-seated aversion to most forms of exercise"
synonyms: dislike of, antipathy for, distaste for, abhorrence of, hatred of, odium of, loathing of, detestation of, hostility toward; More
someone or something that arouses strong feelings of dislike.

Yhea ok. well yes I am sticking to ubuntu/mate, it is working on both screens, uhmm any way I am trying to solve this problem. I wont give up I wont just say oh well uhm i geuess its to hard to use debian so um screw it. NO!! I wont do that!! sorry. I will get this to work. PLEASE HELP ME EVERYONE WHO READS THIS!!!

For one, try to stay calm. Take a step back, wait for a while, look through the stages of your driver initialization. Unfortunately, there's a lot to wade through here. I'll look when I have time.

Thank you. I will stay calm as you suggest. I don't understand how to look through the stages of my driver initialization. Anyway thank you , thank you!

A noob with an attitude that loves to point other posts to this thread so they can shout, whine and beg. Are you like 12 years old?

A noob with an attitude i guess that's a good thing. It means he has some backbone! Thank you!
Now help me get my monitors working in debian...