Two monitor setup
I like my MacBook and FCE to work with my dv material.
The major problem is the limit of the area screen so I think to buy an adaptor to use one of my vga Iiyama 17.
But I dont have any experience about it so I need your advice.
In FCP, I use two monitors on my Mac Pro. It works a lot better and you can spread your workspace out.
Usuauly my browser is on my left monitor, and I have several bins opened. On my right monitor, I have my timeline and my Canvas/Viewer. Sometimes I have the audio window opened on my left monitor, as well as the color correcting tool.
You can edit more organized. It's a lot more fun as well.
-benny
Message was edited by: Benny P.
Similar Messages
-
24" cinema display with a 27" iMac as a two monitor setup.
I have just purchased a second hand 24" cinema display to use as with my 27" iMac as a twomonitor setup.
Connected it up and weked fine fot two days.
Now it keep flashing on & off never more than a fraction of a second.
I connected it to my MacBook Pro for about an hour and the problem did not appear.
I also tried the other Thunderbolt socket, still happened but not as often.
Any one an idea, hardware problem of software?
PatrickThe 27' iMac is Thunderbolt, less than a year old so under warranty, the 24" display is MiniPort, the Macbook MiniPort about 3 years old.
I have been using the setup since posting this descussion and it hasnt happened once in the past hour and a half, so its obviosly intermitant, the hardest fault of all to find.
Thank you for your reply.
Patrick -
Different virtual console on each monitor on a two monitor setup
I'm looking for information on how to configure my system so that I can have one virtual console on each of my monitors. Right now the left monitor is mirrored onto the right one. I'm talking about in runlevel 3 (no X!)
Have you tried to make a new Window ( in "File" menu) and then drag the new window to the other screen?
It's a very simple solution. Unless there is another problem you haven't mentioned. -
Maximising Safari on a dual-monitor setup (GUI behaviour in Window XP Pro)
When I maximise Safari on the 2nd monitor of my two-monitor setup, it disappears off-screen (but its icon still remains in the XP taskbar) and I am unable to bring it back into the viewable area. Consequently, I have to close Safari and reopen it to continue.
When I maximise Safari on the 1st monitor it fills the screen as I'd expect.
Windows XP ProConfirmed on another Dell D610/Windows XP dual-monitor setup.
However, when I maximise safari on the secondary monitor it still appears on the task bar, enabling me to right-click and Restore the window (whereupon it reappears).
Jon -
Preview app opens "split screen" on dual monitor setup
This is a minor issue, I rarely use the utilility "Preview" app. but I'd still like to understand this issue....I use a two monitor setup (MBP & StudioDisplay)..
The following happens if the window was last closed in "expanded" mode (you can see options for Drawer, rotate, etc)
When "Preview" launches and opens a window, it places the top portion of the window on the secondary display and bottom part of the window on the primary display.
This Does Not happen if the window was last closed in "non-exanded" (collasped) mode (sorry, I don't know the proper term).
In other words, in respect to it's position on the screen, when the window opens it always assumes it's in "collasped" mode.
Weird... any comments?There's something wrong with the way Preview handles dual monitors. In my case if I open a smallish item, for instance a small png, instead of opening in the upper left corner of my main monitor it opens so that about half an inch of the Preview window is sticking over onto the second monitor (which is to the left of my main monitor). I had never "collapsed" the tool bar before, so I just now tried that on a small png, then closed it and re-opened. Sure enough, without the toolbar it opens properly. Display the toolbar, close, reopen, and it sticks onto the second monitor. Weird indeed. Larger size files open normally.
This started with the Tiger version of Preview. If you wish you can send feedback:
http://www.apple.com/macosx/feedback/
Maybe it will help get this odd bug squashed in a future version of Preview.
Francine
Francine
Schwieder -
Spaces: trigger to run only in single-monitor setup?
I use a two-monitor setup, and when I'm away from my desk, I like to use spaces and organize my windows that way. I have my most-used applications set up in the spaces pref pane so they open in their own spaces. it works great.
but when I then return to my desk, I have the second screen, and I don't use spaces then. is there a way to set spaces to trigger on or off, depending on if my monitor is hooked up or not?I use a two-monitor setup, and when I'm away from my desk, I like to use spaces and organize my windows that way. I have my most-used applications set up in the spaces pref pane so they open in their own spaces. it works great.
but when I then return to my desk, I have the second screen, and I don't use spaces then. is there a way to set spaces to trigger on or off, depending on if my monitor is hooked up or not? -
Hello all,
With CS3 I am using a two monitor setup with the workspace at left (monitor 1) and all palettes at right. This setup works fine, but now and again, after minimizing PS (doing something else) and maximizing again, the image has disappeared from the workspace and hides behind the palettes on the right hand monitor. As this happens infrequently, I tend to forget that it hides there and this is very confusing.
Is there a setting I am missing that keeps the images on the workspace?
Regards, Sander Stolssanderstols wrote:
I am very sorry, but it seems I still haven't explained the problem clearly enough.
1) The setup is as you have it: primary at left - workspace on the primary.
2) Then I open an image (using the context menu; or dragging it from the Explorer window; or re-opening it from the PS File menu).
3) Most of the time the image opens on the workspace, but not always.
4) Sometimes the image opens on the secondary monitor and hides behind the palettes.
That is it. I want to do away with the situation 4) - it is confusing, especially as it happens only now and again.
Regards, Sander Stols
mmm... keep PS maximised on the primary monitor and a new image will open in the workspace. It's when it is not maximised that it could open outside the workspace....
In 2) above, dragging from Win Explorer to the PS workspace will open it there. Re-opening from the PS file menu may open outside the workspace unless PS is maximised.
I just tried out various permutations and combos and as i said, keep PS maximised on the primary monitor and a new image will open/re-open in the workspace.
If that doesn't help, try resetting your workspace, closing PS and reopening as maximised on the primary monitor.
Hope that helps... -
Windows 10 hiding taskbar in multi-monitors setup bug.
This bug persists since windows 8.1 and is already discussed
here, but it wasn't fixed in approx. half a year :( So, I'm gonna give it a try here.
Here's the screenshot of it in Windows 10.
Well, the bug is with incorrectly disappearing taskbar - taskbar "hides" not in the bottom of the screen, but "taskbar height pixels" higher (see the images in onedrive folder below). It hides in such a way only when you go to start screen
with visible taskbar, wait until it disappears and return to desktop in any way (by pressing the win key, by selecting desktop on startscreen or by clicking the windows logo in the lower left corner); this bug only appears with two monitors setup and
heavily depends on monitors position - the secondary monitor bottom should be below primary monitor bottom (I mean not physical location, of course, but monitors' relative location in "Screen resolution" menu). The bug didn't appear before Update
1; I can't confirm whether it is reproduceable only on my PC at the moment.
I have reproduced the bug on windows 8.1 U1 across several computers with 100% success rate: two macbooks pro retina, lenovo laptop, two desktops (on one of them I reproduced the bug via teamviewer). I've reproduced it today in VMWare with windows 10 Technical
Preview.
This bug is really annoying - when it happens, you need "to cast some magic" - move the mouse to the bottom of the screen, activate/deactivate several applications, etc. in order for taskbar to reappear properly, let alone the fact that it looks
unaesthetic.
Skydrive folder with bug screenshot
Screen recording of the bug
Step-by-step guide with screenshotsYeah, I already did it. I just wanted to open it here, because I've been trying to contact MS about this bug for almost half a year with no success, so I'm just trying to bring their attention to this thing in all ways possible. I could reproduce this bug
on all the systems I've tried so far, and I've managed to reproduce it even on VMWare in newly-installed windows 10 TP in a single try.
@rgggg
I can't understand what do you mean by weakness in graphics. It's a 100% functionality bug. Also, of course, I have nothing to do except reporting some non-existent bugs, making fake screenshots etc. I can't understand what do you mean about "intermediate
servers", and it's almost impossible to change every Windows iso distributive I've downloaded in such a way that this bug will appear there :D
C:\Users\Sfairat>fciv -both D:\Downloads\WindowsTechnicalPreview-x64-EN-US.iso
// File Checksum Integrity Verifier version 2.05.
MD5 SHA-1
9005dce26734bcde7f912c2c51ab1127 eb75a3d3c0f621f175b75dc65db036d0e00eac43 d:\dow
nloads\windowstechnicalpreview-x64-en-us.iso -
How to Setup Nouveau with Two Monitors? ("VGA-1 disconnected")
Hey Guys,
I have a sweet MythTV setup arranged like this: tower & flatpanel LCD in office with an old-fashioned CRT TV in the living room.
I am able to run movies/video on the CRT while the kitchen LCD can be used to do other stuff. (Am I describing two X sessions? A 'dual-monitor' setup?) I could move the cursor from one screen to the other--but couldn't drag windows from one screen to the other...
I'm using an NVIDIA driver (GeForce 8400 GS card)--but the nvidia stuff can cause problems (one recent upgrade of driver and kernel caused a 99% cpu issue.)
Because of that (and a lot of other problems--it's an old Arch install) I did a clean Arch install today on a separate partition and am hoping to use the Nouveau driver to drive both monitors in the same way I just described.
I've got Nouveau running and the kitchen LCD is fine.... When I turn on the CRT, it's black.
Unfortunately, xrandr says that the living room CRT (the tv) is "disconnected":
$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192
DVI-I-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 340mm x 270mm
1280x1024 60.0*+ 75.0
1280x960 60.0
1280x800 74.9 59.9
1152x864 75.0
1280x768 74.9 60.0
1024x768 75.1 70.1 60.0
1024x576 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
848x480 60.0
640x480 72.8 75.0 60.0
720x400 70.1
VGA-1 disconnected (normal left inverted right x axis y axis)
I know the cable/connection is fine, because I can boot into the 'old' install and everything still works (with the nvidia driver).
In case it might help, here is the xorg.conf from the 'working' nvidia setup:
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder57) Fri Dec 18 15:06:52 PST 2009
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 1024 0
Screen 1 "Screen1" LeftOf "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "HP f1905"
HorizSync 30.0 - 83.0
VertRefresh 50.0 - 76.0
Option "DPMS"
EndSection
Section "Monitor"
# HorizSync source: builtin, VertRefresh source: builtin
Identifier "Monitor1"
VendorName "Unknown"
ModelName "TV-0"
HorizSync 28.0 - 55.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
Option "Coolbits" "1"
Option "AddARGBGLXVisuals" "true"
Option "TripleBuffer" "false"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8400 GS"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
Option "Coolbits" "1"
Option "AddARGBGLXVisuals" "true"
Option "TripleBuffer" "false"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8400 GS"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "CRT: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "TV: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "enable"
# Option "RENDER" "disable"
EndSection
Can anyone help me figure out how to get this working with Nouveau?
Thanks in advance!By adding the following to the kernel line in the GRUB menu, I was able to get VGA-1 "connected":
video=VGA-1:e
but that had the side-effect of changing the resolution of DVI-I-1 to that of VGA-1, namely 1024x768.
These sections of the xorg log seem...um...pertinent.
13.304] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
[ 13.304] (II) NOUVEAU(0): Output VGA-1 has no monitor section
13.334] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1024x768
[ 13.334] (II) NOUVEAU(0): Output VGA-1 using initial mode 1024x768
13.355] (II) NOUVEAU(0): RandR 1.2 enabled
[ 13.355] (II) Initializing built-in extension Generic Event Extension
[ 13.355] (II) Initializing built-in extension SHAPE
[ 13.355] (II) Initializing built-in extension MIT-SHM
[ 13.355] (II) Initializing built-in extension XInputExtension
[ 13.355] (II) Initializing built-in extension XTEST
[ 13.355] (II) Initializing built-in extension BIG-REQUESTS
[ 13.355] (II) Initializing built-in extension SYNC
[ 13.355] (II) Initializing built-in extension XKEYBOARD
[ 13.355] (II) Initializing built-in extension XC-MISC
[ 13.355] (II) Initializing built-in extension SECURITY
[ 13.355] (II) Initializing built-in extension XINERAMA
[ 13.355] (II) Initializing built-in extension XFIXES
[ 13.355] (II) Initializing built-in extension RENDER
[ 13.355] (II) Initializing built-in extension RANDR
[ 13.355] (II) Initializing built-in extension COMPOSITE
[ 13.355] (II) Initializing built-in extension DAMAGE
Is XINERAMA the one that handles dual-monitors? Or is it RANDR...?
[ 13.214]
X.Org X Server 1.12.4
Release Date: 2012-08-27
[ 13.214] X Protocol Version 11, Revision 0
[ 13.214] Build Operating System: Linux 3.4.8-1-ARCH i686
[ 13.214] Current Operating System: Linux new-arch 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 08:15:06 UTC 2012 i686
[ 13.214] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=ff3a072f-2090-4fe6-b72e-b189fd134846 ro verbose video=VGA-1:e
[ 13.214] Build Date: 27 August 2012 08:08:29AM
[ 13.214]
[ 13.214] Current version of pixman: 0.26.2
[ 13.214] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 13.214] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 13.214] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 8 08:38:55 2012
[ 13.221] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 13.222] (==) No Layout section. Using the first Screen section.
[ 13.222] (==) No screen section available. Using defaults.
[ 13.222] (**) |-->Screen "Default Screen Section" (0)
[ 13.222] (**) | |-->Monitor "<default monitor>"
[ 13.222] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 13.222] (==) Automatically adding devices
[ 13.222] (==) Automatically enabling devices
[ 13.237] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 13.237] Entry deleted from font path.
[ 13.237] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 13.237] Entry deleted from font path.
[ 13.238] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 13.238] Entry deleted from font path.
[ 13.238] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 13.238] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 13.239] Entry deleted from font path.
[ 13.239] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 13.239] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 13.239] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 13.239] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 13.239] (II) Loader magic: 0x82225a0
[ 13.239] (II) Module ABI versions:
[ 13.239] X.Org ANSI C Emulation: 0.4
[ 13.239] X.Org Video Driver: 12.1
[ 13.239] X.Org XInput driver : 16.0
[ 13.239] X.Org Server Extension : 6.0
[ 13.240] (--) PCI:*(0:1:0:0) 10de:06e4:1462:1162 rev 161, Mem @ 0xfa000000/16777216, 0xe0000000/268435456, 0xf8000000/33554432, I/O @ 0x0000ef00/128, BIOS @ 0x????????/131072
[ 13.240] (--) PCI: (0:6:1:0) 4444:0803:0070:4000 rev 1, Mem @ 0xf4000000/67108864
[ 13.240] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 13.240] (II) LoadModule: "extmod"
[ 13.242] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 13.251] (II) Module extmod: vendor="X.Org Foundation"
[ 13.251] compiled for 1.12.4, module version = 1.0.0
[ 13.251] Module class: X.Org Server Extension
[ 13.251] ABI class: X.Org Server Extension, version 6.0
[ 13.251] (II) Loading extension MIT-SCREEN-SAVER
[ 13.251] (II) Loading extension XFree86-VidModeExtension
[ 13.251] (II) Loading extension XFree86-DGA
[ 13.251] (II) Loading extension DPMS
[ 13.251] (II) Loading extension XVideo
[ 13.251] (II) Loading extension XVideo-MotionCompensation
[ 13.251] (II) Loading extension X-Resource
[ 13.251] (II) LoadModule: "dbe"
[ 13.252] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 13.252] (II) Module dbe: vendor="X.Org Foundation"
[ 13.252] compiled for 1.12.4, module version = 1.0.0
[ 13.252] Module class: X.Org Server Extension
[ 13.252] ABI class: X.Org Server Extension, version 6.0
[ 13.252] (II) Loading extension DOUBLE-BUFFER
[ 13.252] (II) LoadModule: "glx"
[ 13.253] (WW) Warning, couldn't open module glx
[ 13.253] (II) UnloadModule: "glx"
[ 13.253] (II) Unloading glx
[ 13.253] (EE) Failed to load module "glx" (module does not exist, 0)
[ 13.253] (II) LoadModule: "record"
[ 13.253] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 13.253] (II) Module record: vendor="X.Org Foundation"
[ 13.253] compiled for 1.12.4, module version = 1.13.0
[ 13.253] Module class: X.Org Server Extension
[ 13.253] ABI class: X.Org Server Extension, version 6.0
[ 13.253] (II) Loading extension RECORD
[ 13.253] (II) LoadModule: "dri"
[ 13.254] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 13.255] (II) Module dri: vendor="X.Org Foundation"
[ 13.255] compiled for 1.12.4, module version = 1.0.0
[ 13.255] ABI class: X.Org Server Extension, version 6.0
[ 13.255] (II) Loading extension XFree86-DRI
[ 13.255] (II) LoadModule: "dri2"
[ 13.255] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 13.255] (II) Module dri2: vendor="X.Org Foundation"
[ 13.255] compiled for 1.12.4, module version = 1.2.0
[ 13.255] ABI class: X.Org Server Extension, version 6.0
[ 13.255] (II) Loading extension DRI2
[ 13.255] (==) Matched nouveau as autoconfigured driver 0
[ 13.255] (==) Matched nvidia as autoconfigured driver 1
[ 13.255] (==) Matched nv as autoconfigured driver 2
[ 13.255] (==) Matched vesa as autoconfigured driver 3
[ 13.255] (==) Matched fbdev as autoconfigured driver 4
[ 13.256] (==) Assigned the driver to the xf86ConfigLayout
[ 13.256] (II) LoadModule: "nouveau"
[ 13.256] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 13.261] (II) Module nouveau: vendor="X.Org Foundation"
[ 13.261] compiled for 1.12.2, module version = 1.0.1
[ 13.261] Module class: X.Org Video Driver
[ 13.261] ABI class: X.Org Video Driver, version 12.0
[ 13.261] (II) LoadModule: "nvidia"
[ 13.262] (WW) Warning, couldn't open module nvidia
[ 13.262] (II) UnloadModule: "nvidia"
[ 13.262] (II) Unloading nvidia
[ 13.262] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 13.262] (II) LoadModule: "nv"
[ 13.262] (WW) Warning, couldn't open module nv
[ 13.262] (II) UnloadModule: "nv"
[ 13.262] (II) Unloading nv
[ 13.262] (EE) Failed to load module "nv" (module does not exist, 0)
[ 13.262] (II) LoadModule: "vesa"
[ 13.262] (WW) Warning, couldn't open module vesa
[ 13.262] (II) UnloadModule: "vesa"
[ 13.262] (II) Unloading vesa
[ 13.262] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 13.262] (II) LoadModule: "fbdev"
[ 13.263] (WW) Warning, couldn't open module fbdev
[ 13.263] (II) UnloadModule: "fbdev"
[ 13.263] (II) Unloading fbdev
[ 13.263] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 13.263] (II) NOUVEAU driver
[ 13.263] (II) NOUVEAU driver for NVIDIA chipset families :
[ 13.263] RIVA TNT (NV04)
[ 13.263] RIVA TNT2 (NV05)
[ 13.263] GeForce 256 (NV10)
[ 13.263] GeForce 2 (NV11, NV15)
[ 13.263] GeForce 4MX (NV17, NV18)
[ 13.263] GeForce 3 (NV20)
[ 13.263] GeForce 4Ti (NV25, NV28)
[ 13.263] GeForce FX (NV3x)
[ 13.263] GeForce 6 (NV4x)
[ 13.263] GeForce 7 (G7x)
[ 13.263] GeForce 8 (G8x)
[ 13.263] GeForce GTX 200 (NVA0)
[ 13.263] GeForce GTX 400 (NVC0)
[ 13.263] (--) using VT number 7
[ 13.265] drmOpenDevice: node name is /dev/dri/card0
[ 13.265] drmOpenDevice: open result is 7, (OK)
[ 13.265] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 13.265] drmOpenDevice: node name is /dev/dri/card0
[ 13.265] drmOpenDevice: open result is 7, (OK)
[ 13.265] drmOpenByBusid: drmOpenMinor returns 7
[ 13.265] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 13.265] (II) [drm] nouveau interface version: 1.0.0
[ 13.265] (II) Loading sub module "dri"
[ 13.265] (II) LoadModule: "dri"
[ 13.265] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 13.265] (II) Module dri: vendor="X.Org Foundation"
[ 13.265] compiled for 1.12.4, module version = 1.0.0
[ 13.265] ABI class: X.Org Server Extension, version 6.0
[ 13.265] (II) NOUVEAU(0): Loaded DRI module
[ 13.265] drmOpenDevice: node name is /dev/dri/card0
[ 13.266] drmOpenDevice: open result is 8, (OK)
[ 13.266] drmOpenDevice: node name is /dev/dri/card0
[ 13.266] drmOpenDevice: open result is 8, (OK)
[ 13.266] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 13.266] drmOpenDevice: node name is /dev/dri/card0
[ 13.266] drmOpenDevice: open result is 8, (OK)
[ 13.266] drmOpenByBusid: drmOpenMinor returns 8
[ 13.266] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 13.266] (II) [drm] DRM interface version 1.4
[ 13.266] (II) [drm] DRM open master succeeded.
[ 13.266] (--) NOUVEAU(0): Chipset: "NVIDIA NV98"
[ 13.266] (II) NOUVEAU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 13.266] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 13.266] (==) NOUVEAU(0): RGB weight 888
[ 13.266] (==) NOUVEAU(0): Default visual is TrueColor
[ 13.266] (==) NOUVEAU(0): Using HW cursor
[ 13.266] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[ 13.266] (==) NOUVEAU(0): Page flipping enabled
[ 13.266] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[ 13.304] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
[ 13.304] (II) NOUVEAU(0): Output VGA-1 has no monitor section
[ 13.333] (II) NOUVEAU(0): EDID for output DVI-I-1
[ 13.333] (II) NOUVEAU(0): Manufacturer: HWP Model: 264f Serial#: 16843009
[ 13.333] (II) NOUVEAU(0): Year: 2006 Week: 24
[ 13.333] (II) NOUVEAU(0): EDID Version: 1.3
[ 13.333] (II) NOUVEAU(0): Digital Display Input
[ 13.333] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 38 vert.: 30
[ 13.333] (II) NOUVEAU(0): Gamma: 2.40
[ 13.333] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off
[ 13.333] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 13.333] (II) NOUVEAU(0): Default color space is primary color space
[ 13.333] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 13.333] (II) NOUVEAU(0): redX: 0.634 redY: 0.354 greenX: 0.286 greenY: 0.620
[ 13.333] (II) NOUVEAU(0): blueX: 0.138 blueY: 0.076 whiteX: 0.312 whiteY: 0.328
[ 13.333] (II) NOUVEAU(0): Supported established timings:
[ 13.333] (II) NOUVEAU(0): 720x400@70Hz
[ 13.333] (II) NOUVEAU(0): 640x480@60Hz
[ 13.333] (II) NOUVEAU(0): 640x480@72Hz
[ 13.333] (II) NOUVEAU(0): 640x480@75Hz
[ 13.333] (II) NOUVEAU(0): 800x600@60Hz
[ 13.333] (II) NOUVEAU(0): 800x600@72Hz
[ 13.333] (II) NOUVEAU(0): 800x600@75Hz
[ 13.333] (II) NOUVEAU(0): 832x624@75Hz
[ 13.333] (II) NOUVEAU(0): 1024x768@60Hz
[ 13.333] (II) NOUVEAU(0): 1024x768@70Hz
[ 13.333] (II) NOUVEAU(0): 1024x768@75Hz
[ 13.333] (II) NOUVEAU(0): 1280x1024@75Hz
[ 13.333] (II) NOUVEAU(0): 1152x864@75Hz
[ 13.333] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 13.333] (II) NOUVEAU(0): Supported standard timings:
[ 13.333] (II) NOUVEAU(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 13.333] (II) NOUVEAU(0): Supported detailed timing:
[ 13.333] (II) NOUVEAU(0): clock: 108.0 MHz Image Size: 340 x 270 mm
[ 13.333] (II) NOUVEAU(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
[ 13.333] (II) NOUVEAU(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
[ 13.333] (II) NOUVEAU(0): Ranges: V min: 50 V max: 76 Hz, H min: 30 H max: 83 kHz, PixClock max 145 MHz
[ 13.333] (II) NOUVEAU(0): Monitor name: HP f1905
[ 13.333] (II) NOUVEAU(0): Serial No: CNC624PNF4
[ 13.333] (II) NOUVEAU(0): EDID (in hex):
[ 13.333] (II) NOUVEAU(0): 00ffffffffffff0022f04f2601010101
[ 13.333] (II) NOUVEAU(0): 18100103e8261e8cee6760a25a499e23
[ 13.333] (II) NOUVEAU(0): 135054adef8081800101010101010101
[ 13.333] (II) NOUVEAU(0): 010101010101302a009851002a403070
[ 13.333] (II) NOUVEAU(0): 1300540e1100001e000000fd00324c1e
[ 13.333] (II) NOUVEAU(0): 530e000a202020202020000000fc0048
[ 13.333] (II) NOUVEAU(0): 502066313930350a20202020000000ff
[ 13.333] (II) NOUVEAU(0): 00434e43363234504e46340a20200001
[ 13.333] (II) NOUVEAU(0): EDID vendor "HWP", prod id 9807
[ 13.333] (II) NOUVEAU(0): Using EDID range info for horizontal sync
[ 13.333] (II) NOUVEAU(0): Using EDID range info for vertical refresh
[ 13.333] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 13.333] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 13.333] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 13.333] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 13.333] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 13.334] (II) NOUVEAU(0): Printing probed modes for output DVI-I-1
[ 13.334] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 13.334] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1280x800"x74.9 106.50 1280 1360 1488 1696 800 803 809 838 -hsync +vsync (62.8 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1280x768"x74.9 102.25 1280 1360 1488 1696 768 771 778 805 +hsync -vsync (60.3 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1280x768"x60.0 68.25 1280 1328 1360 1440 768 771 778 790 +hsync -vsync (47.4 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
[ 13.334] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 13.334] (II) NOUVEAU(0): EDID for output VGA-1
[ 13.334] (II) NOUVEAU(0): Printing probed modes for output VGA-1
[ 13.334] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[ 13.334] (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 13.334] (II) NOUVEAU(0): Output DVI-I-1 connected
[ 13.334] (II) NOUVEAU(0): Output VGA-1 connected
[ 13.334] (II) NOUVEAU(0): Using fuzzy aspect match for initial modes
[ 13.334] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1024x768
[ 13.334] (II) NOUVEAU(0): Output VGA-1 using initial mode 1024x768
[ 13.334] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 13.334] (--) NOUVEAU(0): Virtual size is 1024x768 (pitch 0)
[ 13.334] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[ 13.334] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 13.334] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[ 13.335] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 13.335] (**) NOUVEAU(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[ 13.335] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 13.335] (**) NOUVEAU(0): Driver mode "848x480": 33.8 MHz (scaled from 0.0 MHz), 31.0 kHz, 60.0 Hz
[ 13.335] (II) NOUVEAU(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[ 13.335] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 59.9 Hz
[ 13.335] (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 13.335] (**) NOUVEAU(0): Display dimensions: (380, 300) mm
[ 13.335] (**) NOUVEAU(0): DPI set to (68, 65)
[ 13.335] (II) Loading sub module "fb"
[ 13.335] (II) LoadModule: "fb"
[ 13.335] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 13.339] (II) Module fb: vendor="X.Org Foundation"
[ 13.339] compiled for 1.12.4, module version = 1.0.0
[ 13.339] ABI class: X.Org ANSI C Emulation, version 0.4
[ 13.339] (II) Loading sub module "exa"
[ 13.339] (II) LoadModule: "exa"
[ 13.340] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 13.341] (II) Module exa: vendor="X.Org Foundation"
[ 13.341] compiled for 1.12.4, module version = 2.5.0
[ 13.341] ABI class: X.Org Video Driver, version 12.1
[ 13.341] (II) Loading sub module "shadowfb"
[ 13.341] (II) LoadModule: "shadowfb"
[ 13.341] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 13.347] (II) Module shadowfb: vendor="X.Org Foundation"
[ 13.347] compiled for 1.12.4, module version = 1.0.0
[ 13.347] ABI class: X.Org ANSI C Emulation, version 0.4
[ 13.347] (--) Depth 24 pixmap format is 32 bpp
[ 13.348] (II) NOUVEAU(0): Opened GPU channel 2
[ 13.352] (II) NOUVEAU(0): [DRI2] Setup complete
[ 13.352] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 13.352] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 13.355] (II) EXA(0): Driver allocated offscreen pixmaps
[ 13.355] (II) EXA(0): Driver registered support for the following operations:
[ 13.355] (II) Solid
[ 13.355] (II) Copy
[ 13.355] (II) Composite (RENDER acceleration)
[ 13.355] (II) UploadToScreen
[ 13.355] (II) DownloadFromScreen
[ 13.355] (==) NOUVEAU(0): Backing store disabled
[ 13.355] (==) NOUVEAU(0): Silken mouse enabled
[ 13.355] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
[ 13.355] (II) NOUVEAU(0): [XvMC] Extension initialized.
[ 13.355] (==) NOUVEAU(0): DPMS enabled
[ 13.355] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 13.355] (--) RandR disabled
[ 13.355] (II) Initializing built-in extension Generic Event Extension
[ 13.355] (II) Initializing built-in extension SHAPE
[ 13.355] (II) Initializing built-in extension MIT-SHM
[ 13.355] (II) Initializing built-in extension XInputExtension
[ 13.355] (II) Initializing built-in extension XTEST
[ 13.355] (II) Initializing built-in extension BIG-REQUESTS
[ 13.355] (II) Initializing built-in extension SYNC
[ 13.355] (II) Initializing built-in extension XKEYBOARD
[ 13.355] (II) Initializing built-in extension XC-MISC
[ 13.355] (II) Initializing built-in extension SECURITY
[ 13.355] (II) Initializing built-in extension XINERAMA
[ 13.355] (II) Initializing built-in extension XFIXES
[ 13.355] (II) Initializing built-in extension RENDER
[ 13.355] (II) Initializing built-in extension RANDR
[ 13.355] (II) Initializing built-in extension COMPOSITE
[ 13.355] (II) Initializing built-in extension DAMAGE
[ 13.370] (II) NOUVEAU(0): NVEnterVT is called.
[ 13.421] (II) NOUVEAU(0): Setting screen physical size to 270 x 203
[ 13.421] resize called 1024 768
[ 13.559] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 13.559] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 13.559] (II) LoadModule: "evdev"
[ 13.559] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 13.560] (II) Module evdev: vendor="X.Org Foundation"
[ 13.560] compiled for 1.12.3.901, module version = 2.7.3
[ 13.561] Module class: X.Org XInput Driver
[ 13.561] ABI class: X.Org XInput driver, version 16.0
[ 13.561] (II) Using input driver 'evdev' for 'Power Button'
[ 13.561] (**) Power Button: always reports core events
[ 13.561] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 13.561] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 13.561] (--) evdev: Power Button: Found keys
[ 13.561] (II) evdev: Power Button: Configuring as keyboard
[ 13.561] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event4"
[ 13.561] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 13.561] (**) Option "xkb_rules" "evdev"
[ 13.561] (**) Option "xkb_model" "evdev"
[ 13.561] (**) Option "xkb_layout" "us"
[ 13.592] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 13.592] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 13.592] (II) Using input driver 'evdev' for 'Power Button'
[ 13.593] (**) Power Button: always reports core events
[ 13.593] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 13.593] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 13.593] (--) evdev: Power Button: Found keys
[ 13.593] (II) evdev: Power Button: Configuring as keyboard
[ 13.593] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3/event3"
[ 13.593] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 13.593] (**) Option "xkb_rules" "evdev"
[ 13.593] (**) Option "xkb_model" "evdev"
[ 13.593] (**) Option "xkb_layout" "us"
[ 13.593] (II) config/udev: Adding input device HDA Intel Line Out Side (/dev/input/event10)
[ 13.593] (II) No input driver specified, ignoring this device.
[ 13.593] (II) This device may have been added with another device file.
[ 13.594] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event11)
[ 13.594] (II) No input driver specified, ignoring this device.
[ 13.594] (II) This device may have been added with another device file.
[ 13.594] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event12)
[ 13.594] (II) No input driver specified, ignoring this device.
[ 13.594] (II) This device may have been added with another device file.
[ 13.594] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event13)
[ 13.594] (II) No input driver specified, ignoring this device.
[ 13.595] (II) This device may have been added with another device file.
[ 13.595] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event6)
[ 13.595] (II) No input driver specified, ignoring this device.
[ 13.595] (II) This device may have been added with another device file.
[ 13.595] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event7)
[ 13.595] (II) No input driver specified, ignoring this device.
[ 13.595] (II) This device may have been added with another device file.
[ 13.596] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event8)
[ 13.596] (II) No input driver specified, ignoring this device.
[ 13.596] (II) This device may have been added with another device file.
[ 13.596] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event9)
[ 13.596] (II) No input driver specified, ignoring this device.
[ 13.596] (II) This device may have been added with another device file.
[ 13.596] (II) config/udev: Adding input device Logitech Logitech Illuminated Keyboard (/dev/input/event0)
[ 13.596] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "evdev keyboard catchall"
[ 13.596] (II) Using input driver 'evdev' for 'Logitech Logitech Illuminated Keyboard'
[ 13.596] (**) Logitech Logitech Illuminated Keyboard: always reports core events
[ 13.597] (**) evdev: Logitech Logitech Illuminated Keyboard: Device: "/dev/input/event0"
[ 13.597] (--) evdev: Logitech Logitech Illuminated Keyboard: Vendor 0x46d Product 0xc318
[ 13.597] (--) evdev: Logitech Logitech Illuminated Keyboard: Found keys
[ 13.597] (II) evdev: Logitech Logitech Illuminated Keyboard: Configuring as keyboard
[ 13.597] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2.1/7-2.1:1.0/input/input0/event0"
[ 13.597] (II) XINPUT: Adding extended input device "Logitech Logitech Illuminated Keyboard" (type: KEYBOARD, id 8)
[ 13.597] (**) Option "xkb_rules" "evdev"
[ 13.597] (**) Option "xkb_model" "evdev"
[ 13.597] (**) Option "xkb_layout" "us"
[ 13.597] (II) config/udev: Adding input device Logitech Logitech Illuminated Keyboard (/dev/input/event1)
[ 13.597] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "evdev keyboard catchall"
[ 13.597] (II) Using input driver 'evdev' for 'Logitech Logitech Illuminated Keyboard'
[ 13.598] (**) Logitech Logitech Illuminated Keyboard: always reports core events
[ 13.598] (**) evdev: Logitech Logitech Illuminated Keyboard: Device: "/dev/input/event1"
[ 13.598] (--) evdev: Logitech Logitech Illuminated Keyboard: Vendor 0x46d Product 0xc318
[ 13.598] (--) evdev: Logitech Logitech Illuminated Keyboard: Found 1 mouse buttons
[ 13.598] (--) evdev: Logitech Logitech Illuminated Keyboard: Found scroll wheel(s)
[ 13.598] (--) evdev: Logitech Logitech Illuminated Keyboard: Found relative axes
[ 13.598] (II) evdev: Logitech Logitech Illuminated Keyboard: Forcing relative x/y axes to exist.
[ 13.598] (--) evdev: Logitech Logitech Illuminated Keyboard: Found absolute axes
[ 13.598] (II) evdev: Logitech Logitech Illuminated Keyboard: Forcing absolute x/y axes to exist.
[ 13.598] (--) evdev: Logitech Logitech Illuminated Keyboard: Found keys
[ 13.598] (II) evdev: Logitech Logitech Illuminated Keyboard: Configuring as mouse
[ 13.598] (II) evdev: Logitech Logitech Illuminated Keyboard: Configuring as keyboard
[ 13.598] (II) evdev: Logitech Logitech Illuminated Keyboard: Adding scrollwheel support
[ 13.598] (**) evdev: Logitech Logitech Illuminated Keyboard: YAxisMapping: buttons 4 and 5
[ 13.598] (**) evdev: Logitech Logitech Illuminated Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 13.598] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2.1/7-2.1:1.1/input/input1/event1"
[ 13.598] (II) XINPUT: Adding extended input device "Logitech Logitech Illuminated Keyboard" (type: KEYBOARD, id 9)
[ 13.598] (**) Option "xkb_rules" "evdev"
[ 13.598] (**) Option "xkb_model" "evdev"
[ 13.598] (**) Option "xkb_layout" "us"
[ 13.598] (II) evdev: Logitech Logitech Illuminated Keyboard: initialized for relative axes.
[ 13.598] (WW) evdev: Logitech Logitech Illuminated Keyboard: ignoring absolute axes.
[ 13.598] (**) Logitech Logitech Illuminated Keyboard: (accel) keeping acceleration scheme 1
[ 13.598] (**) Logitech Logitech Illuminated Keyboard: (accel) acceleration profile 0
[ 13.598] (**) Logitech Logitech Illuminated Keyboard: (accel) acceleration factor: 2.000
[ 13.598] (**) Logitech Logitech Illuminated Keyboard: (accel) acceleration threshold: 4
[ 13.599] (II) config/udev: Adding input device Logitech Logitech Illuminated Keyboard (/dev/input/event2)
[ 13.599] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "evdev pointer catchall"
[ 13.599] (II) Using input driver 'evdev' for 'Logitech Logitech Illuminated Keyboard'
[ 13.599] (**) Logitech Logitech Illuminated Keyboard: always reports core events
[ 13.599] (**) evdev: Logitech Logitech Illuminated Keyboard: Device: "/dev/input/event2"
[ 13.599] (--) evdev: Logitech Logitech Illuminated Keyboard: Vendor 0x46d Product 0xc318
[ 13.599] (--) evdev: Logitech Logitech Illuminated Keyboard: Found 9 mouse buttons
[ 13.599] (--) evdev: Logitech Logitech Illuminated Keyboard: Found scroll wheel(s)
[ 13.599] (--) evdev: Logitech Logitech Illuminated Keyboard: Found relative axes
[ 13.599] (--) evdev: Logitech Logitech Illuminated Keyboard: Found x and y relative axes
[ 13.599] (II) evdev: Logitech Logitech Illuminated Keyboard: Configuring as mouse
[ 13.599] (II) evdev: Logitech Logitech Illuminated Keyboard: Adding scrollwheel support
[ 13.599] (**) evdev: Logitech Logitech Illuminated Keyboard: YAxisMapping: buttons 4 and 5
[ 13.599] (**) evdev: Logitech Logitech Illuminated Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 13.599] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.2/usb7/7-2/7-2.1/7-2.1:1.2/input/input2/event2"
[ 13.599] (II) XINPUT: Adding extended input device "Logitech Logitech Illuminated Keyboard" (type: MOUSE, id 10)
[ 13.599] (II) evdev: Logitech Logitech Illuminated Keyboard: initialized for relative axes.
[ 13.599] (**) Logitech Logitech Illuminated Keyboard: (accel) keeping acceleration scheme 1
[ 13.599] (**) Logitech Logitech Illuminated Keyboard: (accel) acceleration profile 0
[ 13.599] (**) Logitech Logitech Illuminated Keyboard: (accel) acceleration factor: 2.000
[ 13.599] (**) Logitech Logitech Illuminated Keyboard: (accel) acceleration threshold: 4
[ 13.600] (II) config/udev: Adding input device Logitech Logitech Illuminated Keyboard (/dev/input/mouse0)
[ 13.600] (II) No input driver specified, ignoring this device.
[ 13.600] (II) This device may have been added with another device file.
[ 13.600] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[ 13.600] (II) No input driver specified, ignoring this device.
[ 13.600] (II) This device may have been added with another device file. -
Best Way to Hook-up Two Monitors - an LCD and CRT.
I have two monitors, a Samsung SyncMaster 940BX LCD with DVI and VGA ports, the other a Viewsonic CRT with VGA port that I use as a palette monitor.
Which is the best (most reliable) port on the Mac Mini to use for a VGA monitor, the Mini-DVI Port or the Mini DisplayPort? I have a Mini-DVI Port to VGA adapter from my PowerBook that I can use if needed, and will order whatever Mini DisplayPort adapter that I may need. Thanks.I would think that starting from DVI would be the better choice for running a VGA display. I say this because analog VGA output is part of the DVI standard, so it is accounted for, should be mature technology and should work.
DisplayPort, on the other hand, does not account for any VGA output. It is a strictly digital standard. Apple has created an adapter that has active electronics inside that uses digital signals for input and does a digital to VGA translation within the confines of the adapter. Strange but true.
From reading these forums over the years, one thing I have learned is there is no such thing as a sure thing. Some people report better results from the DVI port when running VGA and others say they could only get their VGA display to work from DisplayPort. So it seems it can depend on the display, too. In that case, you are probably stuck using trial and error to see what will work best for your setup because it's unlikely anyone else is going to have exactly the same two monitors you do. -
Dual monitor setup - need laptop on the left
Hi All
I'm running a dual monitor setup - specifically a HP G72 laptop and a widescreen monitor. I use the monitor as the default and sometimes I want to use the Laptop as a secondary screen for watching TV etc. My desktop is Enlightenment, I just changed to it from Gnome. My issue is that I want the laptop to be on the left of the monitor - that's how it is physically positioned - but when I switch the Laptop screen on all my applications shift over to the laptop screen. I've written 2 scripts, attached to hotkeys, one to turn the laptop off and the other to turn the laptop on. The script to turn the laptop on is as follows:
xrandr --output LVDS1 --mode 1600x900 --pos 1600x0 --rotate normal
--output VGA1 --primary --mode 1920x1080 --pos 0x0 --rotate normal --left-of LVDS1
This works fine, applications stay where they should be, except that the physical position is incorrect; VGA1 should be to the right of LVDS1 like this:
xrandr --output LVDS1 --mode 1600x900 --pos 1600x0 --rotate normal
--output VGA1 --primary --mode 1920x1080 --pos 0x0 --rotate normal --right-of LVDS1
However, when I use the second script all of the applications shift to the laptop but at least the physical position is correct. The issue appears to be something to do with laptops, almost as though when it's a laptop the default monitor is forced to be on the left. Has anybody got any suggestions how to get around this issue?
Thanks
RichardThis is due to your window manager treating the two monitors as a larger 'desktop' area - that combined with your specification of the pos=0x0 you are telling it to do this.
If you have only the VGA output on, the top left corner of the VGA monitor is 0x0. If you open a window, and it is placed 10 pixels in and down from the top left, it is at coordinates 10x10 in the x session. Then you turn on the laptop monitor and specify that the top left corner of the laptop monitor should now bo considered 0x0 - but nothing is done to move the windows, so the window with coordinates 10x10 is now near the top left of the laptop monitor.
I see 3 possible ways of acheiving what you want:
1) swap the "pos" parameters in your xrandr commands so that the monitor on the left is always at 0x0 and the one on the right is always at 1920x0 (or whatever). This will leave a large area of available X desktop that is not visible - I don't know how your window manager will treat this. It might try to map windows on the laptop screen space even though that screen is not on. I know openbox is easy to configure where it tries to place windows.
2) Keep the VGA monitor always at 0x0, but place the laptop monitor at a negative offset when you want it on. I don't actually know if X allows negative coordinates like that, but it's worth a shot.
3) Configure your window manager, or use a different window manager, so that it is aware of the two screens and treats them reasonably (e.g. moves windows when the desktop area is changed).
Last edited by Trilby (2014-07-12 12:15:42) -
Four monitor setup on 2013 mac pro using old 23" Cinema Displays
My current monitor setup on a 2009 mac pro is four monitors. Three 23" Apple Cinema Displays (aluminum, mid 2000's) and one large Sony HDTV mounted to the wall as a fourth monitor.
I achieve this via 2 Geforce 120 video cards, each with a mini display port and a Dvi port each.
My question is, can I retain this same exact monitor setup on a new 2013 Mac pro cylinder? If so, what adapters will be needed, and do they all plug into the thunderbolt ports?
Hearing all kinds of nightmares about multiple monitor problems with the new MP so want to be sure this will work before I drop big bucks.
Thanks!Thanks for the quick reply!
For the Tv I'm currently going VGA out of that to a Dvi adapter into the old Mac Pro. The 3 Cinema Displays are all ether direct Dvi to the video card and two I have to use a Dvi to mini display port adapter.
So for the new Mac Pro, assuming I don't use the HDMI port, I would need Dvi to minidisplayport adapters for each of the 3 cinema displays and a VGA to minidisplayport for the TV?
EDIT: And the mini display ports may as well all be active I guess, and they need to plug into the usb bus for power?
Thanks -
Dual monitor setup with seperate resolutions
hey guys!
i currentley run thye latest version of archlinux with the cinnamon desktop environment and an nvidia geforce 7300SE graphics card.
im running a dual monitor setup with one 27" 1920x1080 monitor and one 27" 1024X768 monitor
because they have the same physical size they line up perfectley but because the resolution is different programs/mouse cursor movement doesnt, is there any way (without changing the resolutions) to compensate this effect so that in the eyes of linux/cinnamon the monitors line up so that for example dragging a window goes seamlessley between the 2 monitors.
i HAVE found out the panning option in the nvidia x server settings, but that really isnt what i am looking for...
Last edited by RikSolo (2014-08-04 11:25:02)A magnifier following the window down to the pixel, zooming to the exact size of 540 pixels the 384 pixels window could create an illusion of just that. It would be highly impractical however, not mention all the hacking time. Even if you would manage to get two screen with different sized icons, so that they match visually, the windows and fonts resizing on the fly, wmctrl might help with windows alone, no their themes (buttons, borders thickness etc.), you would still be left with a visually differently sized mouse cursor. Technically such a feat should be possible, but who is going to code it? Nvidia?
Last edited by emeres (2014-08-04 18:48:59) -
Dual monitor setup without using the ADC?
Would it be possible to run a dual monitor setup using a DVI splitter cable from my (2009)Mac Pro?
I've seen some old forums referring to the 2006 models saying that this wouldn't work and instead you'd get the same image on both screens but the newer Mac Pros state they have "Dual-Link DVI ports".
Just wondering whether this means what I think it means and you can connect two monitors via a dual link cable and get essentially, two monitors running independently as opposed to the same thing on both??
Hope it's staightforward and me just being slow.The GT120 features one Dual Link DVI-I port and one Mini DisplayPort .
The DVI-I is Dual Link capable, and also can be directly adapted to VGA.
Single-Link DVI is a serial interface that carries three data bits in each signaling interval, as well as control signals. In general, Single-Link supports displays up to 1920 wide. Dual Link DVI is the same except that it carries six data bits in each signaling interval, supporting displays over 1920 wide.
DVI screen drawing is very similar to VGA screen drawing, and the data sent are digital "scan lines" left-to-right row data, top-to-bottom with entire screen data sent about every 60 Hertz. Analog VGA signals are sent at the same time on a separate set of pins.
DisplayPort and its Mini variant are inherently a packet interface, but can be coerced to produce a "Dual Mode" signal that approximates Single-Link DVI. Getting Dual-Link DVI or VGA from DisplayPort interface requires a non-trivial converter than contains chips and requires power.
Executive Summary:
If you have one display that is wider than 1920 or VGA, attach to the DVI-I connector with an appropriate cable.
Running a Mini DisplayPort display from the Mini DisplayPort requires only a cable.
Single-Link DVI can be had from the Mini DisplayPort with a cheap adapter.
Dual-Link DVI or VGA requires an expensive Active Powered converter which can cost US$100. -
Dual Monitor setup for Mac Mini???
I just bought a VGA Y-cable and split my monitor signal to two monitors. Unfortunatley the same thing is displayed on both screens where as I was looking for an extension to my desktop.
I found this http://www.national-tech.com/catalog/dvisplitter.htm (the top one for $ 146)
I was wondering if I split the signal with a dvi splitter rather than a vga splitter if i could have a dual monitor setup with more screen space...
Thanks,
Paulie
Mac Mini Mac OS X (10.3.9)This will do it for you: http://shopmatrox.com/usa/products/datasheet.asp?ID=788
ibook g4, mac mini core solo, powermac g4 gigabit ethernet Mac OS X (10.4.5)
Maybe you are looking for
-
Can I backup a single account on my mountain lion macbookpro?
I have a macbook pro with two accounts (me and my wife's), but I now need to separate her account on a different machine because I will take one machine to work. what is the best way to just backup her account and restore it on a different machine ru
-
Hi, I am working on a couple of new forms for requesting accounts. I have set up some nice drop down menu's but would like to fix them so that when a particular option is selected in one drop down, the next drop down will offer only the options for t
-
Hi, The Scenario is File to R/3 . The complete connection has established between XI and R/3 . The file is not transferred to the R/3 system . The SXMB_MONI shows the error as follows <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SO
-
CG36 - No virus scan profile is selected as the "default profile"
When running transaction CG36 - Import Reports, I'm getting this message in the job log: "No virus scan profile is selected as the "default profile" VSCAN 034 I" Do I have to set up a default profile for virus scan?
-
Switch Upgraded to 15.2-1.E1 From 12.2-55 and switch is not operable
Hi I need help if somebody has a solution for this problem I have a batch of new Cisco 3750X. Open box, it load without problem, it coming with IOS 3750-eUniversal 12.2-55. I have an USB with the new code c3750e-universalk9-mz.152-1.E1.bin