You are not logged in.
Hello,
I'm trying to set up a dual monitors; one screen is plugged to my ATI (it works fine), but I'm having problems to make the screen plugged on the integrated graphics.
I activated it in the bios, while I'm booting it starts to print the boot logs on the screen then it freezes after "Mounting /home...".
Here is what I have in journalctl after this line:
avril 14 10:04:55 dreamkey_desktop systemd[1]: Mounting /home...
avril 14 10:04:55 dreamkey_desktop kernel: [drm] ib test on ring 5 succeeded
avril 14 10:04:55 dreamkey_desktop kernel: [drm] Radeon Display Connectors
avril 14 10:04:55 dreamkey_desktop kernel: [drm] Connector 0:
avril 14 10:04:55 dreamkey_desktop kernel: [drm] DP-3
avril 14 10:04:55 dreamkey_desktop kernel: [drm] HPD4
avril 14 10:04:55 dreamkey_desktop kernel: [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
avril 14 10:04:55 dreamkey_desktop kernel: [drm] Encoders:
avril 14 10:04:55 dreamkey_desktop kernel: [drm] DFP1: INTERNAL_UNIPHY2
avril 14 10:04:55 dreamkey_desktop kernel: [drm] Connector 1:
avril 14 10:04:55 dreamkey_desktop kernel: [drm] DVI-I-1
avril 14 10:04:55 dreamkey_desktop kernel: [drm] HPD1
avril 14 10:04:55 dreamkey_desktop kernel: [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
avril 14 10:04:55 dreamkey_desktop kernel: [drm] Encoders:
avril 14 10:04:55 dreamkey_desktop kernel: [drm] DFP2: INTERNAL_UNIPHY1
avril 14 10:04:55 dreamkey_desktop kernel: [drm] CRT1: INTERNAL_KLDSCP_DAC1
avril 14 10:04:55 dreamkey_desktop kernel: [drm] Connector 2:
avril 14 10:04:55 dreamkey_desktop kernel: [drm] VGA-2
avril 14 10:04:55 dreamkey_desktop kernel: [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
avril 14 10:04:55 dreamkey_desktop kernel: [drm] Encoders:
avril 14 10:04:55 dreamkey_desktop kernel: [drm] CRT2: INTERNAL_KLDSCP_DAC2
avril 14 10:04:55 dreamkey_desktop kernel: [drm] fb mappable at 0xD045E000
avril 14 10:04:55 dreamkey_desktop kernel: [drm] vram apper at 0xD0000000
avril 14 10:04:55 dreamkey_desktop kernel: [drm] size 7299072
avril 14 10:04:55 dreamkey_desktop kernel: [drm] fb depth is 24
avril 14 10:04:55 dreamkey_desktop kernel: [drm] pitch is 6912
avril 14 10:04:55 dreamkey_desktop kernel: fbcon: radeondrmfb (fb1) is primary device
avril 14 10:04:55 dreamkey_desktop kernel: fbcon: Remapping primary device, fb1, to tty 1-63
avril 14 10:04:55 dreamkey_desktop systemd-fsck[248]: fsck.fat 3.0.26 (2014-03-07)
avril 14 10:04:55 dreamkey_desktop systemd-fsck[248]: /dev/sda1: 19 files, 6716/130812 clusters
avril 14 10:04:55 dreamkey_desktop kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: data=ordered
avril 14 10:04:55 dreamkey_desktop kernel: usb-storage 2-1.4:1.0: USB Mass Storage device detected
avril 14 10:04:55 dreamkey_desktop kernel: scsi8 : usb-storage 2-1.4:1.0
avril 14 10:04:55 dreamkey_desktop kernel: usbcore: registered new interface driver usb-storage
avril 14 10:04:55 dreamkey_desktop kernel: hidraw: raw HID events driver (C) Jiri Kosina
avril 14 10:04:55 dreamkey_desktop kernel: usbcore: registered new interface driver usbhid
avril 14 10:04:55 dreamkey_desktop kernel: usbhid: USB HID core driver
avril 14 10:04:55 dreamkey_desktop kernel: input: USB Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/0003:0461:4D15.0001/input/input13
avril 14 10:04:55 dreamkey_desktop kernel: hid-generic 0003:0461:4D15.0001: input,hidraw0: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:00:1a.0-1.6/input0
avril 14 10:04:55 dreamkey_desktop kernel: mousedev: PS/2 mouse device common for all mice
avril 14 10:04:55 dreamkey_desktop kernel: radeon 0000:01:00.0: fb1: radeondrmfb frame buffer device
avril 14 10:04:55 dreamkey_desktop kernel: [drm] Initialized radeon 2.37.0 20080528 for 0000:01:00.0 on minor 1
avril 14 10:04:55 dreamkey_desktop kernel: snd_hda_intel 0000:01:00.1: enabling device (0100 -> 0102)
avril 14 10:04:55 dreamkey_desktop kernel: hda-intel 0000:01:00.1: Handle VGA-switcheroo audio client
avril 14 10:04:55 dreamkey_desktop kernel: snd_hda_intel 0000:01:00.1: irq 51 for MSI/MSI-X
avril 14 10:04:55 dreamkey_desktop kernel: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
avril 14 10:04:55 dreamkey_desktop systemd[1]: Mounted /home.I tried to follow the PRIME instructions; xrandr and lshw can see the cards:
$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x93 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 3 associated providers: 0 name:radeon
Provider 1: id: 0x48 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 3 outputs: 6 associated providers: 0 name:Intel# lshw -C video
*-display
description: VGA compatible controller
product: Redwood PRO GL [FirePro V3800]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:01:00.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
configuration: driver=radeon latency=0
resources: irq:50 memory:d0000000-dfffffff memory:fe420000-fe43ffff ioport:e000(size=256) memory:fe400000-fe41ffff
*-display
description: Display controller
product: 2nd Generation Core Processor Family Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 09
width: 64 bits
clock: 33MHz
capabilities: msi pm bus_master cap_list
configuration: driver=i915 latency=0
resources: irq:47 memory:fe000000-fe3fffff memory:c0000000-cfffffff ioport:f000(size=64)But if I try "xrandr --setprovideroffloadsink 0x93 0x48" X crashes and reboots:
avril 14 10:10:09 dreamkey_desktop slim[323]: X: dispatch.c:3920: DetachUnboundGPU: Assertion `slave->isGPU' failed.
avril 14 10:10:09 dreamkey_desktop systemd-coredump[7073]: Process 375 (X) dumped core.What can I try? Thanks.
Offline
I'm still having no success to have my dual monitors.
I have an Ubuntu 13.10 on dual-boot for some specific projects, and the two screens work fine. Here is an excerpt of the xrandr output:
Screen 0: minimum 320 x 200, current 3120 x 1050, maximum 8192 x 8192
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DVI-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 270mm
1680x1050 60.0*+
1280x1024 75.0 60.0
1280x960 60.0
1152x864 75.0
1024x768 75.1 60.0
832x624 74.6
800x600 75.0 60.3 56.2
640x480 75.0 60.0
720x400 70.1
VGA-0 disconnected (normal left inverted right x axis y axis)
VGA2 connected 1440x900+1680+0 (normal left inverted right x axis y axis) 408mm x 255mm
1440x900 59.9*+ 75.0
1280x1024 75.0 60.0
1280x960 60.0
1152x864 75.0
1280x720 60.0
1024x768 75.1 70.1 66.0 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 75.0 72.8 66.7 60.0
720x400 70.1 If I compare to my Arch xrandr (see below), it seems that Ubuntu sees a VGA2 connected.
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
DVI-0 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 270mm
1680x1050 59.95*+
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.08 60.00
832x624 74.55
800x600 75.00 60.32 56.25
640x480 75.00 60.00
720x400 70.08
VGA-1 disconnected (normal left inverted right x axis y axis)I compared the list of loaded modules, but I didn't see something concerning the HD Graphics.
Offline
I think Ubuntu set up one screen for both monitors (look at the resolution), and in Arch you would have to address the second screen (or create a virtual one like in Ubuntu). Use the environment variable DISPLAY with xrandr:
env DISPLAY=:0.1 xrandr --props; env DISPLAY=:0.1 xrandr --output VGA2 --auto; env DISPLAY=:0.0 xrandr --propsI do not recall if you have to set up the screen yourself in xorg.conf or if it gets set up automatically these days.
Offline
I can get either the Intel to work, or the ATI to work, but not really together. I can get two out of three monitors to work and I've tried just about everything.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I can get either the Intel to work, or the ATI to work, but not really together.
That would make sense if you did not create and used two devices in xorg.conf, since then it would default to the first device specified by any means. Did you try setting up two screens (+2 monitors. +2 devices), as in xorg.conf screens?
I can get two out of three monitors to work and I've tried just about everything.
I thought you wanted to get 2 monitors to work.
I'm trying to set up a dual monitors
Last edited by emeres (2014-05-23 02:41:48)
Offline
nomorewindows wrote:I can get either the Intel to work, or the ATI to work, but not really together.
That would make sense if you did not create and used two devices in xorg.conf, since then it would default to the first device specified by any means. Did you try setting up two screens (+2 monitors. +2 devices), as in xorg.conf screens?
nomorewindows wrote:I can get two out of three monitors to work and I've tried just about everything.
I thought you wanted to get 2 monitors to work.
nomorewindows wrote:I'm trying to set up a dual monitors
Oops, I have three.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
That would have been too easy. Since I did not use hybrid graphics/two different gpus yet, I can only guess. You may want to try fglrx with two screens on one X server, and one intel screen on another. Looking further into how Ubuntu solved this (or did it only use 2 monitors?) might prove helpful also. You could try Mint also, although it probably does the same thing.
PS. Changing your threads title accordingly might attract the right people.
Offline
I've got an old AMD/ATI that works under XP (and Linux), but was discontinued support for Windows 7. But if I can get it to work under Linux it is more than nothing. Catalyst is more for newer cards. I'm not sure that fglrx is ...
PS. Changing your threads title accordingly might attract the right people.
I'm not OP.
Last edited by nomorewindows (2014-05-23 14:14:24)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I'm not OP.
Right, that explains a lot.
I've got an old AMD/ATI that works under XP (and Linux), but was discontinued support for Windows 7.
I know the pain, although mine HD4850 was only 2 or 3 years old when the normal support ended. By fglrx I meant catalyst. Still, running two X servers should be also possible in your case.
Offline
I was thinking that I may have to use xorg-server-xdmx. I could at times configure my xorg.conf to get a different screen on each monitor, but could only interact with the onboard primary. I could even get the ATI to run on one screen and then extend into the Intel screen, but the other ATI screen was just a duplicate of the over ATI screen.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Xdmx sound interesting. Why only at times? What was the crucial factor? The older generation of integrated gpus probably has limitations compared to the current one.
Offline
Xdmx sound interesting. Why only at times? What was the crucial factor? The older generation of integrated gpus probably has limitations compared to the current one.
I was modifying my xorg.conf to see if I could get it all to work (correctly/completely).
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Check my Post in this Thread
https://bbs.archlinux.org/viewtopic.php?id=176911
I got X.org to work with a Monitor connected to a Radeon and another connected to the Haswell GPU after some tinkering. However, it may not apply to your case if you say that it freezes while booting if you have the IGP enabled.
Last edited by zir_blazer (2014-05-23 18:30:48)
Offline
Does it matter that ServerLayout is at the bottom? I always put it at the top, since that's the way it always outputs from Xorg -configure. The Position, PrefertredMode, and Primary options all seem to be interesting. But I'm running one monitor on Intel, and two monitors VGA and DVI on the same ATI card. I've tried RightOf in my Monitor section. What you have there is probably gold for the OP.
Last edited by nomorewindows (2014-05-23 18:48:49)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
@nomorewindows The whole configuration should be parsed first and consider the xorg.conf.d folder. So no, it does not matter. What zir_blazer suggested is what I essentially had in mind. For your case you would need 2 devices, 3 monitors, 3 screens. The question is how is X handling those screens, if as one big virtual screen, there might be a problem, since those are usually limited.
Offline
@nomorewindows The whole configuration should be parsed first and consider the xorg.conf.d folder. So no, it does not matter. What zir_blazer suggested is what I essentially had in mind. For your case you would need 2 devices, 3 monitors, 3 screens. The question is how is X handling those screens, if as one big virtual screen, there might be a problem, since those are usually limited.
The few times I've gotten close to having three monitors, the screens on the ATI card would draw bogus artifacts and thus be unusable. So is he using the Xorg -configure xorg.conf along with xorg.conf.d or ...
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
-configure
When this option is specified, the Xorg server loads all video driver modules, probes for available hard‐
ware, and writes out an initial xorg.conf(5) file based on what was detected. This option currently has
some problems on some platforms, but in most cases it is a good way to bootstrap the configuration process.
This option is only available when the server is run as root (i.e, with real-uid 0).
The xorg.conf and xorg.conf.d files are composed of a number of sections which may be present in any order, or omit‐
ted to use default configuration values.
It is xorg.conf, and xorg.conf.d is just a folder where partial configuration for xorg.conf is stored. It states also that xorg.conf.d is parsed later, so it overwrites previous parts.
Well, try them one at a time. First the integrated on one screen, them radeon on two screen, and finally both together. Post what configurations work for each scenario. We will figure this out. Although like I said, there may be hardware limits. Did you ever had this kind of a setup on windows or something else (when your video card was still supported)? Artefacts may be related to hardware specific options, and there are lots of those. Let us get X on all monitors first.
Offline
Xorg manual wrote:-configure
When this option is specified, the Xorg server loads all video driver modules, probes for available hard‐
ware, and writes out an initial xorg.conf(5) file based on what was detected. This option currently has
some problems on some platforms, but in most cases it is a good way to bootstrap the configuration process.
This option is only available when the server is run as root (i.e, with real-uid 0).xorg.conf manual wrote:The xorg.conf and xorg.conf.d files are composed of a number of sections which may be present in any order, or omit‐
ted to use default configuration values.It is xorg.conf, and xorg.conf.d is just a folder where partial configuration for xorg.conf is stored. It states also that xorg.conf.d is parsed later, so it overwrites previous parts.
Well, try them one at a time. First the integrated on one screen, them radeon on two screen, and finally both together. Post what configurations work for each scenario. We will figure this out. Although like I said, there may be hardware limits. Did you ever had this kind of a setup on windows or something else (when your video card was still supported)? Artefacts may be related to hardware specific options, and there are lots of those. Let us get X on all monitors first.
It's RV100 on Windows XP. It works there as previously noted. Just haven't gotten it to work fully on Linux. I've actually tried xorg.conf.d in my last attempts, but it was starting to look like my xorg.conf.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
The script that I posted on that Thread was done by hand from scratch using as reference some examples I found on the wiki.
https://wiki.archlinux.org/index.php/AT … Head_setup
https://wiki.archlinux.org/index.php/NV … e_monitors
https://wiki.archlinux.org/index.php/Mu … _xorg.conf
In your case, you may want to add some more lines to specify on the GPU that drives two Monitors, what output each one uses. You may want to try with just two Monitors, one in each GPU, before plugging in the third one.
I don't recall if I tried to automatically generate a config file, chances are I did but it didn't worked. I don't recall neither what worked and what not until I made that script myself - recall some issues with Gnome that saw both screens but in the inverse order, and had to change the Monitor configuration on every reboot because Gnome didn't saved properly.
I choose Device, Monitor, Screen and ServerLayout order because it seemed the most logical startup order, and it worked that way, so didn't tried any other order. There are some some guides suggesting to use separate files for each type of entry and priority is dependent on the first two numbers at the beginning of the file name (07, 09, etc), but as it worked with all that in a single file, didn't bother having separate files, neither.
Most of the issues with artifacting and the like seems to rely on the Driver part. Maybe it tries to use a Driver it shouldn't, but I suppose your FirePro should work with the standard Radeon Driver. Check this:
https://wiki.archlinux.org/index.php/Xo … stallation
What I think than that table lacks is the alias that you use on xorg.conf for each Driver. xf86-video-ati = radeon, xf86-video-intel = intel. I had both installed.
Offline
The script that I posted on that Thread was done by hand from scratch using as reference some examples I found on the wiki.
https://wiki.archlinux.org/index.php/AT … Head_setup
https://wiki.archlinux.org/index.php/NV … e_monitors
https://wiki.archlinux.org/index.php/Mu … _xorg.confIn your case, you may want to add some more lines to specify on the GPU that drives two Monitors, what output each one uses. You may want to try with just two Monitors, one in each GPU, before plugging in the third one.
I don't recall if I tried to automatically generate a config file, chances are I did but it didn't worked. I don't recall neither what worked and what not until I made that script myself - recall some issues with Gnome that saw both screens but in the inverse order, and had to change the Monitor configuration on every reboot because Gnome didn't saved properly.
I choose Device, Monitor, Screen and ServerLayout order because it seemed the most logical startup order, and it worked that way, so didn't tried any other order. There are some some guides suggesting to use separate files for each type of entry and priority is dependent on the first two numbers at the beginning of the file name (07, 09, etc), but as it worked with all that in a single file, didn't bother having separate files, neither.Most of the issues with artifacting and the like seems to rely on the Driver part. Maybe it tries to use a Driver it shouldn't, but I suppose your FirePro should work with the standard Radeon Driver. Check this:
https://wiki.archlinux.org/index.php/Xo … stallation
What I think than that table lacks is the alias that you use on xorg.conf for each Driver. xf86-video-ati = radeon, xf86-video-intel = intel. I had both installed.
I'm not FirePro, just a radeon 7k. xf86-video-ati and xf86-video-intel is yes, what I'd be using. I don't think my setup is usable with catalyst, because ati-config states that it isn't a supported card. Maybe just a little tinkering around with xorg.conf / xorg.conf.d will do the job. I can definitely get dual head ati, just ignore the intel and it will work. My default xorg.conf produces lines for modesetting.
Last edited by nomorewindows (2014-05-23 20:32:26)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
Now if I do Xorg -configure I get:
(EE)
(EE) Backtrace:
(EE) 0: Xorg (xorg_backtrace+0x4f) [0x81dfd0f]
(EE) 1: Xorg (0x8048000+0x19baf4) [0x81e3af4]
(EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb77fb40c]
(EE) 3: /usr/lib/xorg/modules/drivers/radeon_drv.so (0xb6fe2000+0x419b6) [0xb70239b6]
(EE) 4: Xorg (DoConfigure+0xe25) [0x80af875]
(EE) 5: Xorg (0x8048000+0x77ad7) [0x80bfad7]
(EE) 6: Xorg (0x8048000+0x35187) [0x807d187]
(EE) 7: Xorg (0x8048000+0x1f19e) [0x806719e]
(EE) 8: /usr/lib/libc.so.6 (__libc_start_main+0xde) [0xb73cde2e]
(EE) 9: Xorg (0x8048000+0x1f1c4) [0x80671c4]
(EE)
(EE) Segmentation fault at address 0x14
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) Doesn't look like the RV100 wants to play.
Last edited by nomorewindows (2014-05-30 22:41:27)
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline