Frozen system when booting with dual-head setup (updates)

Hi guys,
I made a fresh install a couple of weeks ago and I configured my system for a dual-head setup following the wiki. I activated KMS and added radeon to the kernel parameters.
My xorg.conf looks like this:
Section "Monitor"
Identifier "DVI-0"
Option "PreferredMode" "1920x1080"
Option "Position" "0 0"
EndSection
Section "Monitor"
Identifier "HDMI-0"
Option "PreferredMode" "1920x1080"
Option "Position" "1920 0"
EndSection
I was having random freezes for a couple of days, but I didn't pay too much attention to it. I hard rebooted my computer when it froze and it could boot normally that second time.
But after yesterday, last update to the open source drivers xf86-video-ati (1:7.5.0-2) and lib32-mesa-libgl (10.5.2-1), my system doesn't boot unless I disconnect one of the screens. When only one screen it's connected everything is fine. If I plug the second screen, it pops up the KDE service to configurate the second screen but as soon I press 'apply the chages' my system freezes and I had to hard reboot.
I've tried all possible combinations usingt different outputs from the screens, getting the same results. Two of them connected --> freezes after grub loading. One connected --> boot Ok, but as soon as I plug the second one and I apply changes, freezes.
I found one configuration that doesn't freeze my system. When I plug the second screen, as I said, KDE service automatically pops up. Before I was changing the positions of the screen, one beside the other one, and my system freezes when I apply the changes. If I just left the default configuration (one screen in top of the other), it doesn't freeze my system. After that, I can rearrange the screens, as I need them, and it doesn't freeze.
Here it is my grub.cfg
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 e36984ca-21d8-4191-ba2f-a09bf8ce6f88
else
search --no-floppy --fs-uuid --set=root e36984ca-21d8-4191-ba2f-a09bf8ce6f88
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 128c8e95-9496-49d1-9a9e-bc886662258d
else
search --no-floppy --fs-uuid --set=root 128c8e95-9496-49d1-9a9e-bc886662258d
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 128c8e95-9496-49d1-9a9e-bc886662258d
else
search --no-floppy --fs-uuid --set=root 128c8e95-9496-49d1-9a9e-bc886662258d
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-e36984ca-21d8-4191-ba2f-a09bf8ce6f88' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 128c8e95-9496-49d1-9a9e-bc886662258d
else
search --no-floppy --fs-uuid --set=root 128c8e95-9496-49d1-9a9e-bc886662258d
fi
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 rw quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
And my fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2 resto del disco
UUID=e36984ca-21d8-4191-ba2f-a09bf8ce6f88 / ext4 defaults,noatime,discard 0 1
# /dev/sda1 100MB
UUID=128c8e95-9496-49d1-9a9e-bc886662258d /boot ext4 defaults,noatime,discard 0 2
# /dev/sdc2 10GB
UUID=3959515c-30e4-4749-bc30-5babba3311e8 /var ext4 defaults 0 2
# /dev/sdc3 resto del disco
UUID=8ccc2ed9-35e5-4a4f-81f1-98cc8bfc4ed1 /home ext4 defaults,noatime 0 2
# /dev/sdc1
UUID=35e39da9-c942-434d-bbfc-deb5e40ee8be none swap defaults 0 0
#montaje de temp en ram
tmpfs /tmp tmpfs nodev,nosuid,size=3G 0 0
# External HDD
UUID=0ae5eb6a-8c4c-480c-8efe-609ae83f2bdc /media/External\040HDD ext4 defaults 0 0
# Seagate Expansion Drive
UUID=16668D4B668D2C95 /media/Seagate\040Expansion\040Driventfs-3g defaults,nofail 0 0
What else should I check?
Thanks in advance.
Edit: added info
Edit2: more tests.
Last edited by doblerone (2015-03-31 08:12:38)

Rexilion wrote:Maybe try looking at /var/log/pacman.log and see if you can downgrade packages (start with the kernel). See if that works around the problem.
Downgrading catalyst to 14.3 seems to have done the job. Thanks for the suggestion, marking as solved.
Inxsible wrote:bheinks, you have been on the forums long enough to be aware of the forum rules. Make use of an image hosting site.
Sorry, I don't post often and wasn't aware of the rules on images. I'll keep that in mind next time.

Similar Messages

  • [Solved] Catalyst graphical glitches with dual head setup

    Hello all, having a weird issue with my dual monitor setup where graphical glitches make my primary monitor completely unusable. The Tear Free feature of the proprietary catalyst driver is what seems to be causing it:
    Tear Free enabled:
    Tear Free disabled:
    I can safely enable it with one monitor disabled also. The issue is that without Tear Free enabled, I'm experiencing some serious screen tearing when watching videos and playing games.
    My video card is the XFX HD 7970 Double D and I'm using the latest version of catalyst (14.4), installed from Vi0L0's repo. The monitors are the same model with the same specs (1920x1200 @60Hz). I definitely used to be able to use Tear Free with my dual head setup at most a month ago, so some update at some point must have broken it. I temporarily switched back to the open source driver before I had found Tear Free to be the culprit and the performance is still hardly comparable.
    Any ideas? Thanks in advance.
    Last edited by bheinks (2014-05-15 02:38:45)

    Rexilion wrote:Maybe try looking at /var/log/pacman.log and see if you can downgrade packages (start with the kernel). See if that works around the problem.
    Downgrading catalyst to 14.3 seems to have done the job. Thanks for the suggestion, marking as solved.
    Inxsible wrote:bheinks, you have been on the forums long enough to be aware of the forum rules. Make use of an image hosting site.
    Sorry, I don't post often and wasn't aware of the rules on images. I'll keep that in mind next time.

  • Nouveau graphical tearing, dual-head setup

    I currently experience tearing while using the Nouveau drivers for my NVidia card. I experienced the same (or a similar) tearing issue while using the proprietary drivers, which, along with the inherent incompatibility with most of the linux graphics stack, led me to switch to Nouveau.
    I'm using the 3D support from nouveau-dri along with xf86-video-nouveau and the most recent Gnome 3 build in the official repositories.
    I have a dual-head setup with one 1024x768 IBM monitor to the left of a 1920x1080 Dell monitor. Both report 60Hz vertical refresh rate in their configuration menus.
    So far, my attempts to solve this problem have consisted of the following steps:
    1. Use a minimal xorg.conf and configure everything using the integrated Gnome display settings utility. The minimal xorg.conf was as follows:
    Section "Device"
    Identifier "nvidia"
    Driver "nouveau"
    Option "GLXVBlank" "true"
    EndSection
    2. Enable/disable the GLXVBlank flag in xorg.conf.
    I do not experience the same issue when booted to Windows 7, using the most recent official NVidia drivers.
    I would greatly appreciate any help anyone could offer on this issue, it is quite frustrating to boot into Windows to watch videos without horizontal breaks in every frame. Thanks!
    Output from xrandr --current is as follows:
    [ifx@melancholy ~]$ xrandr --current
    Screen 0: minimum 320 x 200, current 2944 x 1080, maximum 8192 x 8192
    DVI-I-1 connected 1920x1080+1024+0 (normal left inverted right x axis y axis) 477mm x 268mm
    1920x1080 60.0*+
    1280x1024 75.0 60.0
    1152x864 75.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    DVI-I-2 connected 1024x768+0+312 (normal left inverted right x axis y axis) 304mm x 228mm
    1024x768 60.0*+ 75.1 70.1
    832x624 74.6
    800x600 72.2 75.0 60.3 56.2
    640x480 72.8 75.0 60.0 59.9
    720x400 70.1
    My current xorg.conf is as follows:
    Section "Monitor"
    Identifier "Monitor0"
    Option "PreferredMode" "1920x1080_60.00"
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    Option "PreferredMode" "1024x768_60.00"
    Option "LeftOf" "Monitor0"
    EndSection
    Section "Device"
    Identifier "nvidia"
    Driver "nouveau"
    Option "Monitor-DVI-I-1" "Monitor0"
    Option "Monitor-DVI-I-2" "Monitor1"
    Option "GLXVBlank" "true"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    Virtual 2944 1080
    EndSubSection
    Device "nvidia"
    EndSection
    Section "ServerLayout"
    Identifier "Layout0"
    Screen "Screen0"
    EndSection
    Other information can be provided on request.

    Hello. I have the same problem. Not just on Arch. I've had this problem with many distros, graphics cards, and drivers across the board. Installing the proprietary nvidia driver fixes the video tearing (vsync) issue for me. However; A) it's Linux, I don't want to use proprietary anything (otherwise I'd be on a Mac); and B) the proprietary driver will not flip my display to portrait anyway.
    I basically have the same setup as Meyermagic. One GeForce 8600 GT, Two monitors (identical acers) 1680x1050 (oriented in portrait so 1050x1680 if you like), using open source Nouveau driver, created a minimal xorg file in /etc/X11/xorg.conf.d/20-nouveau.conf
    Section "Module"
    Load "glx"
    EndSection
    Section "Device"
    Identifier "Nvidia card"
    Driver "nouveau"
    Option "GLXVBlank" "true"
    EndSection
    Both monitors have a refresh rate of 60Hz. I still get really bad tearing as I drag windows across the screens.
    Again, I've had this issue with almost every Linux box I've built (the only time this is not even remotely an issue is on my Thinkpad T400 using the Intel graphics). I'm guessing I'm doing something wrong or I've just had bad luck because it is nearly impossible to find any support for this on any forum anywhere. Anything I do find is either a thread like this where someone asked the question and simply never got a response. Or it is some out-of-date forum that give you 10 ways to modify the xorg.conf none of which make any sense or don't work. Not to mention that xorg.conf is now depreciated anyways.
    Seriously, even if there is a wiki that concisely explains in excruciating detail how to actually modify the xorg conf files then I could figure it out for myself but I can't find that anywhere which makes me feel really stupid because I know it has to be out there. If there isn't an xorg wiki or xorg.com site or something that explains how to use the thing then I'm not sure I want to live on this planet anymore.
    If anyone can help in any way please do.

  • OpenOffice crash with dual-head presentation in Impress

    Hi, I have an issue with Impress, I hoped that version 3.2 would fix it but it's not so. Now I think it is a problem of my system.
    I have a dual head setup with an ATI card (Catalyst 10.5, xorg-server 1.7.6); I start a slide show with Impress on the secondary display, then when I press esc to return to Impress the program crashes. Starting it from the console I get this error messages:
    $ SAL_SYNCHRONIZE=1 soffice -impress
    ** (soffice:3129): WARNING **: Inhibit method failed
    ** (soffice:3129): WARNING **: Inhibit problem : The name org.gnome.ScreenSaver was not provided by any .service files
    ** (soffice:3129): WARNING **: UnInhibit method failed
    ** (soffice:3129): WARNING **: Inhibit problem : The name org.gnome.ScreenSaver was not provided by any .service files
    X-Error: RenderBadPicture (invalid Picture parameter)
    Major opcode: 155
    Minor opcode: 7
    Resource ID: 0x1800911
    Serial No: 40909 (40909)
    I think the warnings are harmless, and that X-Error is the problem. I don't know if I should file a bug upstream, I searched OO bug tracker but I didn't find anything.
    Thank you.

    Hey, I just discovered the same problem here... I believe it's exclusive with oo, and go-oo doesn't have it.
    EDIT:
    According to this, it has to do with gtk, a possibly workaround (at least for me) is running this first:
    export OOO_FORCE_DESKTOP="soffice"
    Then openoffice doesn't crash when you close the presentation :). Hope it helps until we find a real solution :).
    PS.- The warning still appears though.
    Last edited by pablox (2010-06-09 23:13:44)

  • MSI N560GTX-Ti Hawk PerfCap with Dual Monitor setup

    Hi guys,
    as far as I'm concerned, there shouldn't be a PerfCap when running a setup with two monitors on extend desktop setting, am I right? However, my GTX560-Ti does PerfCap and sometimes even does this while gaming (which is incredibly annoying). The only way to get it to clock up again is to reboot my PC.
    My question is, why is that and how can I get rid of this behavior? I already tried updating the VBIOS but it didn't help.
    Thanks in advance
    Monsterkater

    I'm sorry, I thought "PerfCap" would be a known term.
    As the title states, it's a MSI N560GTX-Ti Hawk. The Card is clocking down, GPU-Z reports "PerfCap Reason: Util" which is, according to Google Search, because it isn't challenged enough. However, when running a dual monitor setup it should (again according to Google Search) always run at the default speeds (950/1050/1900 Core/Memory/Shader). I have updated my signature to show my system details as listed in the Posting Guide.
    The temperatures under load are okay, the highest I have seen was 76°C GPU, 74°C Memory and 69°C VRM (all of them measured with MSI Afterburner). I have tried several drivers including Beta drivers and always checked "perform a clean installation". I also tried updating the VBIOS. I didn't know what else to try because Google Search doesn't yield much results for this.

  • Kdemod 4.2 with dual head

    I want to use dual head setting in kde 4.2 but it has bunch of issues. When in kde4 i issue the command
    xrandr --output VGA --left-of LVDS
    , it enable the dual head setup but the resolution defaults to 1024x768 for both my monitor and Laptop. When I change the resolution to the correct ones from the kde4 display setting in control panel, it screws up the dual head setup and the screens starts overlapping.
    Has anyone managed to set dual  head on kde4.

    Two weeks late, but anyway...
    You can set the position for the second monitor too.
    xrandr --output DVI-0 --pos 1680x0
    This works for my setup. The systemsettings xrandr module doesn't, how am I supposed to use that?

  • Bootsplash on a dual-head setup without KMS?

    Hello!
    I have been wanting to get a bootsplash working on my system, to get a feeling of a more polished system, but sadly I'm running the catalyst drivers for decent 3D game framerate, and it doesn't support KMS. It seemed like that would have been okay, and that for example plymouth could work through a framebuffer, but sadly I have dual-head with two different resolutions(1920x1200 and 1020x1280), and I couldn't get Uvesafb/v86d to work with that. I really want to get a bootsplash and I am willing to sacrafise some time to get it working. The main goal is just to get it working, but ideally I'd like it without any resolution changing or black flicker, as it's described here.  So Plymouth is my first-pick, as it looks "best".
    So far I have tried Splashy, FBsplash and Plymouth, with different degrees of success:
    FBsplash:
        Miscsplashutils(dependency) didn't build because freetype had been built without static linking(I don't know anything about this). I got it working with something I found in the comments though.
        But then FBsplash wouldn't build. And I gave it up.
    Splashy:
        Installation worked(splashy-full) after I modified the PKGBUILD with some automake patches so it should work with automake 1.14. But when I booted it the screen was just flickering black
    Plymouth:
        I got it installing, can't remeber if I needed some patches. And it worked, although only with a text-bootsplash. I also installed a framebuffer(Uvesafb/v86d) but that didn't work properly.
        The Plymouth loading anymation(spinfinity) continued into gdm.
    I am willing to retry everything and clearify what doesn't work, and why.
    Thanks to anyone who can help!
    Last edited by totokaka (2013-08-21 16:21:23)

    So I've been trying to get some development on this, and used most of the day to get uvesafb working.
    It is working quite good, but I don't get the native resolution of the screen(1920x1200), I only get 1600x1200.
    And my secound monitor is disabled, I suspect it's because the computer sends a resolution to big to both the screens, but it's really a a feature for me, as the terminal would be sideways on the secound monitor anyways.
    During my testing I also came to a new idea: Have the framebuffer, X and GDM originally only start the main monitor, and then leave it up to gnome to enable it. that way I would only get the flicker between GDM and gnome-shell, which I will get anyway, because it seems like everything ignores X's rotation of the screens, or at least doesnt support sideways. However I didn't find a way to get this working, any ideas?
    EDIT; My card is an HD6790, and as far as I can understand the GPU's bios is sending supported modes to uvesafb?
    Last edited by totokaka (2013-08-22 19:22:52)

  • Display sleep with dual monitor setup

    I'm running a 17" studio display and a 20" studio display as a two momitor setup on a dual G5 2.0. The menu bar is on the 17". Unless I have display sleep in energy saver set to never, the 17" will go to sleep at the interval set in the preference panel, even when the system is in use. So far the only way I've found to get the display back off sleep is to put the computer itself to sleep - keyboard shortcut or by using the power button on the 17" and then wake it up.
    I think this only started with 10.4.6. I can't upgrade to 10.4.7 yet - I run Avid Xpress Pro on the system and 10.4.7 gives dongle trouble. I've thrown away preference files, set and reset the sleep parameters. As it happens, I've had to reinstall the system a couple of weeks back, but the 17" studio still goes to sleep when it shouldn't.
    The problem doesn't occur if the menu bar is on the 20" cinema display, but that's not the way I want it.
    Anyone with the same problem,, or better a suggested solution?

    finally found the solution (apple i hope your reading
    this as this is a mad bug!)
    you need to have the dock on the bottom of the main
    screen in order to view the image on that screen.
    Wierd, I have my dock on the left side of my main screen... which is to the left of my secondary screen. Perhaps you cannot have the dock in-between screens?
    kgelner, how have you noticed the performance of your
    card when working with aperture? Im seriously
    debating upgrading mine as its just slow and annoying
    I find it usable but I'm also only working with TIFF files (my camera is not supported). I am also pretty strongly thinking about going with the X800xt card, which should be at least twice as fast. Some operations (like a lot of Spot & Patch repairs combined with Shadows/Highlights) do make things a bit laggy.
    I also have the 256MB version of the 9800, which I think helps with some of the larger images and operations.

  • Need help with dual monitor setup for KDE 3.5.5.

    Here's my hardware:
    NEC MultiSync LCD 1530V:  1024x768 (analog)
    Samsung SyncMaster 941BW: 1440x900 (digital)
    nVidia Dual head AGP video card.
    The dual monitor works under dual-boot Windows, boot up and pure Linux console.  I've googled around for help, changed my xorg.conf file accordingly to some sites, but it wasn't much help. 
    Here's my working xorg.conf:
    Section "ServerLayout"
        Identifier     "Simple Layout"
        Screen         "Screen 1" 0 0
        InputDevice    "Mouse1" "CorePointer"
        InputDevice    "Keyboard1" "CoreKeyboard"
    EndSection
    Section "Files"
        FontPath        "/usr/share/fonts/misc"
        FontPath        "/usr/share/fonts/75dpi"
        FontPath        "/usr/share/fonts/100dpi"
        FontPath        "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
        Load           "dbe"      # Double buffer extension
        SubSection     "extmod"
            Option         "omit xfree86-dga"   # don't initialise the DGA extension
        EndSubSection
        Load           "freetype"
        Load           "glx"
    EndSection
    Section "InputDevice"
        Identifier     "Keyboard1"
        Driver         "kbd"
        Option         "AutoRepeat" "500 30"
        Option         "XkbRules" "xorg"
        Option         "XkbModel" "pc101"
        Option         "XkbLayout" "us"
    EndSection
    Section "InputDevice"
        Identifier     "Mouse1"
        Driver         "mouse"
        Option         "Protocol" "Auto"    # Auto detect
        Option         "Device" "/dev/input/mice"
    EndSection
    Section "Monitor"
        Identifier     "NEC LCD1530V"
        HorizSync       31.5 - 48.5
        VertRefresh     50.0 - 70.0
    EndSection
    Section "Device"
        Identifier     "Standard VGA"
        Driver         "vga"
        VendorName     "Unknown"
        BoardName      "Unknown"
    EndSection
    Section "Device"
        Identifier     "NVIDIA GeForce"
        Driver         "nvidia"
        Option "NoLogo" "true"        
        EndSection
    Section "Screen"
        Identifier     "Screen 1"
        Device         "NVIDIA GeForce"
        Monitor        "NEC LCD1530V"
        DefaultDepth    24
        SubSection     "Display"
            Viewport    0 0
            Depth       8
            Modes      "1024x768"
        EndSubSection
        SubSection     "Display"
            Viewport    0 0
            Depth       16
            Modes      "1024x768"
        EndSubSection
        SubSection     "Display"
            Viewport    0 0
            Depth       24
            Modes      "1024x768"
        EndSubSection
    EndSection
    Using this xorg.conf file, only my NEC LCD analog monitor could display KDE while the Samsung digital can't.
    Any suggestions?   

    Thanks for your help guys, I'm halfway there.
    The second monitor shows the KDE desktop, but it isn't exactly what I expected.  Right now, both monitors display at 1024x768 (each) or 2048x768 (total).  The larger monitor stretches and distorts the display of 1024x768 to its natural resolution at 1440x900 and it isn't what I wanted.  Other than that, the dual desktop setup behaves what I expected to.
    Here's a snippet of my xorg.conf that currently works:
    Section "Monitor"
    Identifier "NEC LCD1530V"
    HorizSync 31.5 - 48.5
    VertRefresh 50.0 - 70.0
    EndSection
    Section "Monitor"
    Identifier "Samsung SyncMaster"
    HorizSync 31.5 - 60
    VertRefresh 60.0 - 70.0
    EndSection
    Section "Device"
    #VideoRam 131072
    # Insert Clocks lines here if appropriate
    Identifier "NVIDIA GeForce"
    Driver "nvidia"
    Option "NoLogo" "true"
    Option "TwinView" "true"
    Option "TwinViewOrientation" "LeftOf"
    Option "SecondMonitorHorizSync" "30-50"
    Option "SecondMonitorVertRefresh" "60"
    # Option "MetaModes" "1440x900, 1440x900; 1024x768, 1024x768"
    EndSection
    Section "Screen"
    Identifier "Screen 1"
    Device "NVIDIA GeForce"
    Monitor "NEC LCD1530V"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 8
    Modes "1024x768"
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    Modes "1024x768"
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    Modes "1024x768"
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen 2"
    Device "NVIDIA GeForce"
    Monitor "Samsung SyncMaster"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 8
    Modes "1440x900"
    EndSubSection
    EndSection
    Anyone have an idea?
    EDIT:  Oh snaps.  I just did a pacman -Syu and it upgraded Arch Linux to 0.8 and the 2nd monitor stopped working.

  • [solved] no sound when booting with webcam attached

    Hi everybody,
    hopefully this is the right section to post since I'm not quite sure if the problem is related to KDE or a general hardware thing. ;-)
    Anyway, the problem that I have is that I don't have any sound at all when booting my system while my webcam, a logitech 9000 pro, is attached to the USB port.
    Even when unplugging the webcam afterwards the sound does not work. I need to reboot my system first with the webcam detached and than it'll work again. I also did already manually insert the modules in /etc/rc.conf but no change. Every time it seems that the webcams audio interface will be recognized as the primary audio device.
    When not having the camera plugged in and plugging it in while KDE is up, everything works like a charm.
    But of course it bothers me quite big time to unplug the webcam every time after using it and rebooting the system again after I forgot to unplug it.
    I also checked for other modules to be loaded automatically (compared the output of lsmod before and after plugging in the webcam) but there was no change.
    So does anyone have an idea what to do in order to get the order of the audio devices right?
    Thank you!...
    Last edited by kurisutian (2009-11-23 19:34:10)

    In your /etc/rc.d/modprobe.d/modprobe.conf try to put zero index for your audio driver, so it will load first. In my case it's this line:
    options snd-hda-intel index=0

  • Dual head setup (mach64 - ATI Rage Mobility)

    hello everyone!
    I want to use a new extra monitor I got recently, with my laptop, I use aweosme.
    I have installed:
    xf86-video-mach64 (recompiled with dri support)
    mach64-dri (from community)
    mach64drm (from AUR)
    https://wiki.archlinux.org/index.php/Mach64
    Still I can't get OpenGL to work:
    ismaelvc@toybox ~ $ glxinfo | egrep "direct rendering|OpenGL renderer"
    direct rendering: Yes
    OpenGL renderer string: Gallium 0.4 on softpipe
    I don't really know if it got something to do with this but I post it anyway in case it is.
    xrandr doesnt detect the other monitor:
    ismaelvc@toybox ~ $ xrandr -q
    xrandr: Failed to get size of gamma for output default
    Screen 0: minimum 320 x 175, current 1024 x 768, maximum 1024 x 768
    default connected 1024x768+0+0 0mm x 0mm
    1024x768 87.0* 85.0 75.0 70.0 60.0 81.0
    832x624 75.0
    800x600 85.0 75.0 72.0 60.0 56.0
    640x480 85.0 75.0 73.0 60.0
    720x400 85.0
    640x400 85.0
    640x350 85.0
    512x384 87.0 85.0 75.0 70.0 60.0
    416x312 75.0
    400x300 85.0 75.0 72.0 60.0 56.0
    320x240 85.0 75.0 73.0 60.0
    360x200 85.0
    320x200 85.0
    320x175 85.0
    Still it displays exactly the same that gets displayed at my laptop.
    I used to had problems with the drivers, I needed both mach64 and radeon for it to detect the screen properly, until I created a "20-mach64.conf" with this:
    Section "Device"
    Identifier "Card0"
    Driver "mach64"
    Card "ATI Rage Mobility - Mach64"
    Option "DMAMode" "async"
    Option "ForcePCIMode" "false"
    Option "AgpMode" "2"
    Option "AgpSize" "32"
    Option "BufferSize" "2"
    Option "LocalTextures" "true"
    Option "EnablePageFlip" "true"
    EndSection
    Section "Module"
    #<Your modules>
    Load "glx"
    Load "dri"
    EndSection
    Section "DRI"
    Group "video" #change to any desired group to restrict access
    Mode 0660
    EndSection
    I have a doubt regarding the commented line that came as example in the mach64 wiki that reads <your modules>, I don't know what goes in there.
    Also I red this for some mach64 related xorg info:
    http://www.x.org/archive/X11R6.8.0/doc/ati5.html
    http://forums.fedoraforum.org/showthread.php?t=201482
    The last one is for a cursor problem I have, but it wont get fixed, neither, anyway the default xcursor looks good in awesome, I switched to cli apps form many tasks, and use uzbl now! all this plus arch is now so minimmal I love it lol!
    I red in a post (not in this one) mach64 chips supported dual head, but I can't find it again, I will post it when I find it.
    Thanks in advance!
    EDIT: ok here it is, where it say its supported: I don't understand all the configs.
    http://cgit.freedesktop.org/xorg/driver … ff432c36bf
    Last edited by ismaelvc (2012-06-29 03:52:09)

    Sorry to necrobump but I was seeing you get a lot of incorrect information on LinuxQuestions.
    The mach64 driver does NOT support dualhead. Some chips are capable of it but this feature has yet to be added to the driver. It is also not compatible with xrandr. The man page you linked to mentioning dualhead support is for xf86-video-ati. It is only accessible from the git history of xf86-video-mach64 because those drivers used to live in the same source tree.
    I can try to help with DRI if that's still not working for you.

  • No screen displayed when booting with options key held down

    When I hold the option key down to select which OS I want to boot into I am getting nothing displayed on the screen but the booting has paused waiting for my input because I can use the cursor keys and return to get the system to boot.
    Anyone got any ideas as to why I cant see the choices?
    Thanks
    Gary

    Just a quick follow up on this problem. I have just tried the Mac Mini on my TV using the HDMI port and I get the boot menu displayed when holding down the Option Key and it works fine. The issues are arising when I plug a VGA adaptor into the mini display port and use that with my monitor. The monitor is not reporting any out of range or sync signals while booting and I have tried 3 different monitors of various ages and all have the same result.
    I also get no apple logo or any display while OSX is loading when I use the monitor
    Gary

  • [Solved]Dual-Head Setup broken after last Kernelupgrade

    Hello,
    Yesterday I upgraded my from 4.0.2 to 4.0.3 and was kind of surprised when my second display didn't want to show a picture anymore. When booting everything looks good when sudenly one display gets black. It doesn't matter which Desktop I start, even when switching VT only one display is active, so it's not a Xorg-bug.
    Nothing shows up in journalctl oder dmesg and as far as the system is concerned everything works as expected. Everything worked as soon as I downgraded the Kernel to 4.0.2.
    Enabling testing and installing 4.0.4 didn't work either.
    So my question is, does anyone else experience this behaviour?
    thanks in advance
    - Radeon HD 77xx with open source drivers
    - two displays DVI (primary) and HDMI (secondary)
    Edit:
    I Just checked the kernel from today in testing (4.0.4-2) and saw something really interesting during boot.
    [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is invalid, remainder is 105
    May 22 16:24:55 Arbiter kernel: Raw EDID:
    May 22 16:24:55 Arbiter kernel: 00 ff ff ff ff ff ff 00 41 2f 00 00 01 01 01 01
    May 22 16:24:55 Arbiter kernel: 00 16 01 03 80 a0 5a 78 0a ee 91 a3 54 4c 99 26
    May 22 16:24:55 Arbiter kernel: 0f 50 54 a1 08 00 31 40 45 40 61 40 71 40 81 80
    May 22 16:24:55 Arbiter kernel: 01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
    May 22 16:24:55 Arbiter kernel: 45 00 a0 5a 00 00 00 1e 01 1d 80 18 71 1c 16 20
    May 22 16:24:55 Arbiter kernel: 58 2c 25 00 20 00 00 01 03 78 78 78 78 78 78 78
    May 22 16:24:55 Arbiter kernel: 78 78 78 78 78 78 78 78 78 78 78 78 78 78 78 78
    May 22 16:24:55 Arbiter kernel: ae ae ae ae ae ae ae ae ae ae ae ae ae ae ae ae
    May 22 16:24:55 Arbiter kernel: Raw EDID:
    May 22 16:24:55 Arbiter kernel: ae ae ae 23 23 23 23 23 23 23 23 23 23 23 23 23
    May 22 16:24:55 Arbiter kernel: 23 23 23 23 23 23 23 23 23 23 00 00 00 00 00 00
    May 22 16:24:55 Arbiter kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    May 22 16:24:55 Arbiter kernel: 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01
    May 22 16:24:55 Arbiter kernel: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
    May 22 16:24:55 Arbiter kernel: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
    May 22 16:24:55 Arbiter kernel: 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
    May 22 16:24:55 Arbiter kernel: 01 01 01 01 01 01 01 01 01 1d 1d 1d 1d 1d 1d 1d
    May 22 16:24:55 Arbiter kernel: Raw EDID:
    May 22 16:24:55 Arbiter kernel: 1d 1d 1d 1d 1d 1d 1d 1d 1d 1d 1d 1d 1c 1c 1c 1c
    May 22 16:24:55 Arbiter kernel: 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c 1c
    May 22 16:24:55 Arbiter kernel: 1c 1c 1c 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c
    May 22 16:24:55 Arbiter kernel: 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 2c 18 18 18 18 18
    May 22 16:24:55 Arbiter kernel: 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18
    May 22 16:24:55 Arbiter kernel: 18 18 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e
    May 22 16:24:55 Arbiter kernel: 9e 9e 9e 9e 9e 9e 9e 9e 9e 9e 8a 8a 8a 8a 8a 8a
    May 22 16:24:55 Arbiter kernel: 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a 8a
    May 22 16:24:55 Arbiter kernel: Raw EDID:
    May 22 16:24:55 Arbiter kernel: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
    May 22 16:24:55 Arbiter kernel: 10 10 10 10 00 00 00 00 00 00 00 00 00 00 00 00
    May 22 16:24:55 Arbiter kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    May 22 16:24:55 Arbiter kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    May 22 16:24:55 Arbiter kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    May 22 16:24:55 Arbiter kernel: 00 00 00 00 00 00 00 00 00 00 31 31 31 31 31 31
    May 22 16:24:55 Arbiter kernel: 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31
    May 22 16:24:55 Arbiter kernel: 31 31 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f
    May 22 16:24:55 Arbiter kernel: radeon 0000:02:00.0: HDMI-A-1: EDID block 0 invalid.
    May 22 16:24:55 Arbiter kernel: [drm:radeon_dvi_detect [radeon]] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID
    I have no clue what to make of it. As soon as I downgrade the kernel again, everything is normal.
    Last edited by raygenbogen (2015-06-09 14:34:18)

    I think I kinda 'solved' the problem by enabling early KMS in mkinitcpio.conf and switched my first Display to the second DVI-Port. It works now, but I don't know if this could be labeled as 'solved' since it's a pretty specific solution and propably doesn't apply to anyone else.
    Edit. The most recent Kernel 4.0.5 in Testing solved the problem for me.
    Last edited by raygenbogen (2015-06-09 14:34:01)

  • Getting white screen when booting with alt key

    Hi, I've installed windows 7 with boot camp on my brand new iMac 27" on OS X Lion.
    Everything works fine when I configure boot camp to start as mac, or as windows.
    However If I press the alt key when booting, as per this tutorial http://labnol.blogspot.com/2006/04/boot-camp-tutorial-install-windows-xp.html I get a white screen and that's it. Any Idea as to what might be the problem?

    Hi
    Try resetting the Parameter RAM (PRAM) - pronounced peeram. Restart the mac and depress the P, R, alt and command keys simultaneously. You should hear the boot chime. Keep the keys depressed until you hear the boot chime three more times. Release the keys thereafter.
    Other possibilities are: you're filling up the hard drive and you need to clear some space; a problem is developing with the hard drive and/or directory structure. You need to run a disk repair utility such as fsck, DU's Repair Disk coupled with Repairing Privileges or something 3rd-Party such as Disk Warrior.
    Tony

  • [Solved] "Version Magic" error when booting with m

    Hi, I compiled kernel 2.6.16.18  and I receive the following error when booting:
    ide_core: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    amd74xx: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    generic: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    ide_disk: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    cdrom: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    ide_cd: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    ide_floppy: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    sd_mod: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    libata: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    sata_nv: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    jbd: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    ext3: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    jfs: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    reiserfs: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    xfs: version magic '2.6.16-ARCH SMP preempt 686 gcc-4.0' should be '2.6.16.18-ARCH preempt 686 gcc-4.0'
    I compiled my kernel with this line:
    # make -s clean bzImage modules modules_install
    Any ideas?

    Ok, I fixed it.
    When doing mkinitrd auto it would make an initrd image from the modules at /lib/modules/2.6.16-ARCH when it had to do it from /lib/modules/2.6.16.18-ARCH
    I fixed it with 
    mkinitrd kernel_version=2.6.16.18-ARCH
    Also my menu.lst was wrong, a new image was created under the name of
    initrd-2.6.16.18-ARCH.img.
    My menu.lst pointed to initrd26.img. I didn't change it before because I didn't know, someone should update the wiki article about compiling the kernel from source.

Maybe you are looking for

  • While reviewing my account I used master debit card it didn't accept

    I just wanted to know its the fault of debit card it can be. If yes debit cards are not acceptable I'll use credit card next time. Their is one more thing does apple accept master card. If no is visa card is accepted

  • AUC settlements to Fixed assets

    hi i can able to settle the wbs value to auc, then after this  settlements rule tab for the wbs  become gray i can't able to enter the asset number  for the final settlements please guide to solve this error Regards raj

  • KDE 4 breaks konqueror in KDE 3

    i installed KDE 3.5.10 and then KDE 4 as soon as i installed KDE 4 most buttons on the toolbar in konqueror of KDE 3 disappeared. the commands work from the menu and the toolbar is configured to display the buttons but they are missing please help me

  • I am not able to open the app in Creative Coud

    i tried uninstalling and installing creative cloud but still same problem, when i go to apps a download error message appears (404) please i need some help

  • Intellisync error "Duplicate records found"

    I am trying to sync my BB 8300 with Outlook 2007.  I am using Blackberry Desk Manager 4.2.2.14. I was able to sync before but now it get this error "Duplicate records found in the device" and it won't sync. Any ideas to fix this problem? I tried to u