DisplayLink incompatibility
Just bought a new projector to use with Keynote. The projector has DisplayLink technology (video over USB). Unfortunately, I learned that Keynote is incompatible with DisplayLink. Something about Keynote requiring OpenGL acceleration. VGA works fine, but it sure would be convenient to use DisplayLink. (There also exists a relatively inexpensive wireless DisplayLink adapter.)
I submitted a bug report (but I think this is a known issue).
I know there's no solution for the time being (other than just using VGA), but I was just wondering if anyone had any thoughts about whether this CAN be addressed and fixed. Or is this just the nature of Keynote and thus no fix is possible?
thanks,
Tim
I'd be surprised to find out Keynote doesn't work over DisplayLink, but I haven't tested that out yet. I'll see if I can try tomorrow in the Apple Store.
Sorry, mistook this for DisplayPort Understand completely now why that won't work (and found a website with the description of what the problem is). It's not so much a Keynote problem, but a DisplayLink problem. They MAY be able to resolve it with a driver update, but that will wholly be on the side of those creating that driver software.
Similar Messages
-
G4Ti4200-VTD64 voltage incompatibility with MSI K7N2 Delta-ILSR??
Hello,
I have the MSI G4Ti4200-VTD64 (4X) video card.. I want to upgrade my motherboard to K7N2 Delta-ILSR. Is there any voltage incompatibility?? I heard that new mother boards will support only AGP 1.5V. Is the AGP voltage of K7N2 Delta-ILSR 1.5volts?? Is my video card compatible with this voltage?? I really want to retain my current video card as I am quite satisfied with it and I'm not willing to invest on a new one at the moment. If there is an incompatibility could you suggest another Socket A MB with good performance and SATA RAID support.
Thanks in advance
Regards,
JosephJoseph,
All 4X Vid Cards work on all 4X and 8X mobos. All 4X mobos work with all 4X and 8X Vid Cards.
Take Care,
Richard -
10.5.7 Fundamental Incompatibility with Mac Pro - Screen/System Lock ups
Hi all.
It looks like 10.5.7 is causing a lot of problems, but I think I found a problem that is very fundamental.
First, my system. It's one of the original Mac Pros with Quad Xeons at 2.66GHz. It has 24GB of RAM and several drives in there. I have 3 30" displays plugged into 3 NVIDIA GeForce 7300GT cards. I originally ran a 10.5.7 combo update on my 10.5.6 system, and experienced these problems (detailed below). As I was also running a beta of iTunes and the iPhone SDK (the 3rd release), and beta 2 of Safari 4, I thought this may have caused some trouble. So, I tried an experiment.
I bought a new Corsair 256GB SSD for my startup drive. Loaded my family pack of 10.5.6 onto it as a fresh install, and just applied the 10.5.7 combo update. I get the exact same behavior with no further software. So, this is a fundamental incompatibility of 10.5.7 with a machine having these specs.
Now the problems. They start with the primary (in my case center) screen locking while the other two screens keep working. Meaning, the primary display "works" but none of the windows move, the clock freezes...yet, if you move the mouse there and luckily grab a window, you could move it out onto the other 2 displays and it would allow you to continue to use the application. If you hit the CONTROLkey and scroll up and down (zooming the display in and out) it can sometimes "unlock" the primary display, but then there are many artifacts. For example, the shadows cast by windows appear as plain grey "dashboard esque" blocks and have black stripes at the edges. Also, at random times, the machine just seems to hang completely, and unlock a minute or 2 later. Eventually it locks for good.
Unfortunately this has lead me into a deadlock situation. My iTunes has been updated to the 3rd beta in the iPhone 3.0 SDK release. The library has been modified and only works with that version now. That version requires 10.5.7. So if I revert back to 10.5.6, I lose my iTunes Library or have to wait till the offical version of iTunes is realeased (although that may still require 10.5.7).
I see lots of people are having Firewire (800 in particular) problems, and I have several drives I need on Firewire. It's not a solution to yank them. It all works fine under 10.5.6, of course.
So the question is...is help on it's way? What to do!?
Thanks for any insights.
More info on the system below:
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 24 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B08
SMC Version (system): 1.7f10
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x8
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-2
PCIe Lane Width: x8
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: Display
Bus: PCIe
Slot: Slot-3
PCIe Lane Width: x4
VRAM (Total): 256 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0393
Revision ID: 0x00a1
ROM Revision: 3008
Displays:
Cinema HD:
Resolution: 2560 x 1600
Depth: 32-Bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Display Connector:
Status: No Display Connected
ATA Bus:
SONY DVD RW DW-D150A:
Model: SONY DVD RW DW-D150A
Revision: 1.MD
Serial Number:
Detachable Drive: No
Protocol: ATAPI
Unit Number: 0
Socket Type: Internal
Low Power Polling: No
Power Off: No
TSSTcorpCD/DVDW SH-S162L:
Model: TSSTcorpCD/DVDW SH-S162L
Revision: LC02
Serial Number:
Detachable Drive: No
Protocol: ATAPI
Unit Number: 1
Socket Type: Internal
Low Power Polling: No
Power Off: No
FireWire Bus:
Maximum Speed: Up to 800 Mb/sec
Built-in Hub:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
FreeAgent Go FW:
Manufacturer: Seagate
Model: 0x2200
GUID: 0x20370200105F82
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 200 Mb/sec
Sub-units:
FreeAgent Go FW Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x110
Product Revision Level: 410G
Sub-units:
FreeAgent Go FW SBP-LUN:
Capacity: 149.05 GB
Removable Media: Yes
BSD Name: disk5
Mac OS 9 Drivers: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Not Supported
Volumes:
Seagate149GBTote:
Capacity: 148.73 GB
Available: 132.95 GB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk5s2
Mount Point: /Volumes/Seagate149GBTote
Unknown Device:
Manufacturer: Unknown
Model: Unknown
GUID: 0x0
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
OEM ATA Device 00:
Manufacturer: OEM
Model: 0x0
GUID: 0x30E102E0454B7D
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Up to 200 Mb/sec
Sub-units:
OEM ATA Device 00 Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x110
Product Revision Level:
Sub-units:
OEM ATA Device 00 SBP-LUN:
Capacity: 931.51 GB
Removable Media: Yes
BSD Name: disk4
Mac OS 9 Drivers: No
Partition Map Type: GPT (GUID Partition Table)
S.M.A.R.T. status: Not Supported
Volumes:
TimeMachine:
Capacity: 931.19 GB
Available: 606.63 GB
Writable: Yes
File System: Case-sensitive Journaled HFS+
BSD Name: disk4s2
Mount Point: /Volumes/TimeMachine
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 800 Mb/sec
Connection Speed: Unknown
Unknown Device:
Manufacturer: Unknown
Model: Unknown
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Unknown
Memory Slots:
ECC: Enabled
DIMM Riser A/DIMM 1:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02007D11
DIMM Riser A/DIMM 2:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02006013
DIMM Riser B/DIMM 1:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x0200711F
DIMM Riser B/DIMM 2:
Size: 4 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x8551
Part Number: 0x373254353132393230454641335343322020
Serial Number: 0x02007012
DIMM Riser A/DIMM 3:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xA4730244
DIMM Riser A/DIMM 4:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0x70780241
DIMM Riser B/DIMM 3:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xE4760245
DIMM Riser B/DIMM 4:
Size: 2 GB
Type: DDR2 FB-DIMM
Speed: 667 MHz
Status: OK
Manufacturer: 0x830B
Part Number: 0x4E54324754373255344E4231424E2D334320
Serial Number: 0xF0770241I can only tell you that I've run 10.5.7 on my Mac Pro, same model as yours, without any problems. As a beta tester my Mac Pro was the main hardware on which 10.5.7 was tested. I currently have it installed on a first generation iMac, MacBook, and MacBook Pro as well as a second generation MacBook Pro. So far not a single problem.
But, I don't have multiple video cards nor do I use any beta version of iTunes (didn't know there was one since each system upgrade includes the current release) but I do use the Safari 4 Beta - the most recent version just released when 10.5.7 was released.)
I can suggest you read the following about updates of system software:
Essential Steps Before Updating OS X!
Please do things right before updating OS X in order to avoid problems.
A. Repair Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
B. Clone Using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the destination volume from the left side list.
3. Click on the Erase tab in the DU main window. Set the format type to Mac OS Extended (journaled, if available) and click on the Erase button. This step can be skipped if the destination has already been freshly erased.
4. Click on the Restore tab in the DU main window.
5. Select the destination volume from the left side list and drag it to the Destination entry field.
6. Select the source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
Destination means your backup drive (should be erased first.)
Source means your startup drive or volume.
C. Download the Standalone Combo Updater from Apple.
Be sure you quit all running applications and disconnect all peripherals (except original keyboard and mouse) before running the installer. When the installer is running do not use the computer in any way other than to respond to an installer dialog.
Install the update by double-clicking on the installer package icon. When the installation is completed Restart the computer. Your computer will boot twice - this is normal. Upon completion of the update use Disk Utility to repair permissions. Not all permissions will seem repaired. You will get spurious reports regarding permissions related to iTunes, Front Row. These can be ignored. They will appear every time you repair permissions.
Following these basic steps should prevent most if not all updating problems. Note that if you have unrepairable disk problems reported in Step A then DO NOT update your system until those problems are resolved.
If you find that you did not follow these suggestions, then you might consider reinstalling OS X and going about the process properly in the hope of a successful result:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update. -
USB DisplayLink Second Monitor
I have a ThinkVision USB Monitor that I've been trying to use with a Thinkpad T420 for quite some time.
My first attempt was with the udlfb module and xf86-video-fbdev on the linux-lts kernel. Wasn't so hot. I then attempted to use xf86-video-fbdev-for-displaylink, which is a replacement for the X fbdev driver. That package installs the drivers to the wrong directory, however, so I had to fix that first.
I can't remember if I got it working on the LTS kernel or not, but either way, I switched back to linux to see if the 3.9 kernel might have a fix.
The initial boot wasn't too pleasing.
Turned out the monitor was hijacking my framebuffer at boot time, and it would display all the console text itself. Wasn't pretty. I encountered the scheduling while atomic bug, which is apparently in need of some kernel patching to fix. I'd take the leap, but it doesn't even seem worth it until I can get X to use the display properly.
I got a single X display working, mostly in accordance with the DisplayLink Wiki page. That was cool, but I'd have to run a separate X session. Xinerama, TwinView (I was on nVidia), were not an option. Here's the Xorg.log from the DisplayLink-only setup:
X.Org X Server 1.14.1
Release Date: 2013-04-17
[ 8138.751] X Protocol Version 11, Revision 0
[ 8138.752] Build Operating System: Linux 3.8.7-1-ARCH x86_64
[ 8138.752] Current Operating System: Linux beefmaster 3.9.4-1-ARCH #1 SMP PREEMPT Sat May 25 16:14:55 CEST 2013 x86_64
[ 8138.752] Kernel command line: root=/dev/sda8 rw acpi_backlight=vendor acpi_osi=Linux
[ 8138.754] Build Date: 17 April 2013 02:37:06PM
[ 8138.754]
[ 8138.755] Current version of pixman: 0.30.0
[ 8138.756] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 8138.756] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 8138.759] (==) Log file: "/var/log/Xorg.1.log", Time: Sat Jun 1 17:19:00 2013
[ 8138.759] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 8138.760] (==) ServerLayout "X.org Configured"
[ 8138.760] (**) |-->Screen "ThinkVision" (0)
[ 8138.760] (**) | |-->Monitor "ThinkVisionMonitor"
[ 8138.760] (**) | |-->Device "ThinkVisionDevice"
[ 8138.760] (==) Automatically adding devices
[ 8138.760] (==) Automatically enabling devices
[ 8138.760] (==) Automatically adding GPU devices
[ 8138.760] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 8138.760] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 8138.760] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 8138.760] (II) Loader magic: 0x7fcc20
[ 8138.760] (II) Module ABI versions:
[ 8138.760] X.Org ANSI C Emulation: 0.4
[ 8138.760] X.Org Video Driver: 14.1
[ 8138.760] X.Org XInput driver : 19.1
[ 8138.760] X.Org Server Extension : 7.0
[ 8138.760] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 8138.761] (--) PCI:*(0:1:0:0) 10de:1057:17aa:21ce rev 161, Mem @ 0xf2000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
[ 8138.761] Initializing built-in extension Generic Event Extension
[ 8138.762] Initializing built-in extension SHAPE
[ 8138.763] Initializing built-in extension MIT-SHM
[ 8138.763] Initializing built-in extension XInputExtension
[ 8138.764] Initializing built-in extension XTEST
[ 8138.765] Initializing built-in extension BIG-REQUESTS
[ 8138.765] Initializing built-in extension SYNC
[ 8138.766] Initializing built-in extension XKEYBOARD
[ 8138.767] Initializing built-in extension XC-MISC
[ 8138.767] Initializing built-in extension SECURITY
[ 8138.768] Initializing built-in extension XINERAMA
[ 8138.769] Initializing built-in extension XFIXES
[ 8138.769] Initializing built-in extension RENDER
[ 8138.770] Initializing built-in extension RANDR
[ 8138.771] Initializing built-in extension COMPOSITE
[ 8138.771] Initializing built-in extension DAMAGE
[ 8138.772] Initializing built-in extension MIT-SCREEN-SAVER
[ 8138.772] Initializing built-in extension DOUBLE-BUFFER
[ 8138.773] Initializing built-in extension RECORD
[ 8138.774] Initializing built-in extension DPMS
[ 8138.774] Initializing built-in extension X-Resource
[ 8138.775] Initializing built-in extension XVideo
[ 8138.775] Initializing built-in extension XVideo-MotionCompensation
[ 8138.776] Initializing built-in extension XFree86-VidModeExtension
[ 8138.777] Initializing built-in extension XFree86-DGA
[ 8138.777] Initializing built-in extension XFree86-DRI
[ 8138.778] Initializing built-in extension DRI2
[ 8138.778] (II) LoadModule: "glx"
[ 8138.778] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 8138.778] (II) Module glx: vendor="X.Org Foundation"
[ 8138.778] compiled for 1.14.1, module version = 1.0.0
[ 8138.778] ABI class: X.Org Server Extension, version 7.0
[ 8138.778] (==) AIGLX enabled
[ 8138.778] Loading extension GLX
[ 8138.778] (II) LoadModule: "fbdev"
[ 8138.778] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 8138.778] (II) Module fbdev: vendor="X.Org Foundation"
[ 8138.778] compiled for 1.14.1, module version = 0.4.3
[ 8138.778] Module class: X.Org Video Driver
[ 8138.778] ABI class: X.Org Video Driver, version 14.1
[ 8138.778] (II) FBDEV: driver for framebuffer: fbdev
[ 8138.778] (++) using VT number 2
[ 8138.779] (WW) Falling back to old probe method for fbdev
[ 8138.779] (II) Loading sub module "fbdevhw"
[ 8138.779] (II) LoadModule: "fbdevhw"
[ 8138.779] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 8138.779] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 8138.779] compiled for 1.14.1, module version = 0.0.2
[ 8138.779] ABI class: X.Org Video Driver, version 14.1
[ 8138.779] (II) FBDEV(0): using /dev/fb1
[ 8138.779] (II) FBDEV(0): Creating default Display subsection in Screen section
"ThinkVision" for depth/fbbpp 16/16
[ 8138.779] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16
[ 8138.779] (==) FBDEV(0): RGB weight 565
[ 8138.779] (==) FBDEV(0): Default visual is TrueColor
[ 8138.779] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 8138.779] (II) FBDEV(0): hardware: udlfb (video memory: 2052kB)
[ 8138.779] (**) FBDEV(0): Option "fbdev" "/dev/fb1"
[ 8138.779] (**) FBDEV(0): Option "ReportDamage" "True"
[ 8138.779] (**) FBDEV(0): Damage reporting enabled. Disabling shadow framebuffer
[ 8138.779] (II) FBDEV(0): checking modes against framebuffer device...
[ 8138.779] (II) FBDEV(0): checking modes against monitor...
[ 8138.779] (--) FBDEV(0): Virtual size is 1366x768 (pitch 1366)
[ 8138.779] (**) FBDEV(0): Built-in mode "current": 72.0 MHz, 48.0 kHz, 60.0 Hz
[ 8138.779] (II) FBDEV(0): Modeline "current"x0.0 72.00 1366 1380 1436 1500 768 769 772 800 +hsync +vsync -csync (48.0 kHz b)
[ 8138.779] (==) FBDEV(0): DPI set to (96, 96)
[ 8138.779] (II) Loading sub module "fb"
[ 8138.779] (II) LoadModule: "fb"
[ 8138.779] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 8138.779] (II) Module fb: vendor="X.Org Foundation"
[ 8138.779] compiled for 1.14.1, module version = 1.0.0
[ 8138.779] ABI class: X.Org ANSI C Emulation, version 0.4
[ 8138.779] (==) FBDEV(0): Backing store disabled
[ 8138.779] (==) FBDEV(0): DPMS enabled
[ 8138.779] (==) RandR enabled
[ 8138.783] (II) AIGLX: Screen 0 is not DRI2 capable
[ 8138.783] (II) AIGLX: Screen 0 is not DRI capable
[ 8138.789] (II) AIGLX: Loaded and initialized swrast
[ 8138.789] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 8138.817] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 8138.817] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 8138.817] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 8138.817] (II) LoadModule: "evdev"
[ 8138.817] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 8138.817] (II) Module evdev: vendor="X.Org Foundation"
[ 8138.817] compiled for 1.14.0, module version = 2.8.0
[ 8138.817] Module class: X.Org XInput Driver
[ 8138.817] ABI class: X.Org XInput driver, version 19.1
[ 8138.817] (II) Using input driver 'evdev' for 'Power Button'
[ 8138.817] (**) Power Button: always reports core events
[ 8138.817] (**) evdev: Power Button: Device: "/dev/input/event5"
[ 8138.817] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 8138.817] (--) evdev: Power Button: Found keys
[ 8138.817] (II) evdev: Power Button: Configuring as keyboard
[ 8138.817] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event5"
[ 8138.817] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 8138.817] (**) Option "xkb_rules" "evdev"
[ 8138.817] (**) Option "xkb_model" "evdev"
[ 8138.817] (**) Option "xkb_layout" "gb"
[ 8138.817] (**) Option "xkb_options" "ctrl:nocaps"
[ 8138.831] (II) config/udev: Adding input device Video Bus (/dev/input/event6)
[ 8138.831] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 8138.831] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 8138.831] (II) Using input driver 'evdev' for 'Video Bus'
[ 8138.831] (**) Video Bus: always reports core events
[ 8138.831] (**) evdev: Video Bus: Device: "/dev/input/event6"
[ 8138.831] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 8138.831] (--) evdev: Video Bus: Found keys
[ 8138.831] (II) evdev: Video Bus: Configuring as keyboard
[ 8138.831] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:09/LNXVIDEO:01/input/input6/event6"
[ 8138.831] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 8138.831] (**) Option "xkb_rules" "evdev"
[ 8138.831] (**) Option "xkb_model" "evdev"
[ 8138.831] (**) Option "xkb_layout" "gb"
[ 8138.831] (**) Option "xkb_options" "ctrl:nocaps"
[ 8138.831] (II) config/udev: Adding input device Lid Switch (/dev/input/event3)
[ 8138.831] (II) No input driver specified, ignoring this device.
[ 8138.831] (II) This device may have been added with another device file.
[ 8138.831] (II) config/udev: Adding input device Sleep Button (/dev/input/event4)
[ 8138.831] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 8138.831] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 8138.831] (II) Using input driver 'evdev' for 'Sleep Button'
[ 8138.831] (**) Sleep Button: always reports core events
[ 8138.831] (**) evdev: Sleep Button: Device: "/dev/input/event4"
[ 8138.831] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 8138.831] (--) evdev: Sleep Button: Found keys
[ 8138.831] (II) evdev: Sleep Button: Configuring as keyboard
[ 8138.831] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4/event4"
[ 8138.831] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[ 8138.831] (**) Option "xkb_rules" "evdev"
[ 8138.831] (**) Option "xkb_model" "evdev"
[ 8138.831] (**) Option "xkb_layout" "gb"
[ 8138.831] (**) Option "xkb_options" "ctrl:nocaps"
[ 8138.831] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 8138.832] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event12)
[ 8138.832] (II) No input driver specified, ignoring this device.
[ 8138.832] (II) This device may have been added with another device file.
[ 8138.832] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event13)
[ 8138.832] (II) No input driver specified, ignoring this device.
[ 8138.832] (II) This device may have been added with another device file.
[ 8138.832] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event14)
[ 8138.832] (II) No input driver specified, ignoring this device.
[ 8138.832] (II) This device may have been added with another device file.
[ 8138.832] (II) config/udev: Adding input device Integrated Camera (/dev/input/event16)
[ 8138.832] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
[ 8138.832] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
[ 8138.832] (II) Using input driver 'evdev' for 'Integrated Camera'
[ 8138.832] (**) Integrated Camera: always reports core events
[ 8138.832] (**) evdev: Integrated Camera: Device: "/dev/input/event16"
[ 8138.832] (--) evdev: Integrated Camera: Vendor 0x4f2 Product 0xb221
[ 8138.832] (--) evdev: Integrated Camera: Found keys
[ 8138.832] (II) evdev: Integrated Camera: Configuring as keyboard
[ 8138.832] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input16/event16"
[ 8138.832] (II) XINPUT: Adding extended input device "Integrated Camera" (type: KEYBOARD, id 9)
[ 8138.832] (**) Option "xkb_rules" "evdev"
[ 8138.832] (**) Option "xkb_model" "evdev"
[ 8138.832] (**) Option "xkb_layout" "gb"
[ 8138.832] (**) Option "xkb_options" "ctrl:nocaps"
[ 8138.832] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event7)
[ 8138.832] (II) No input driver specified, ignoring this device.
[ 8138.832] (II) This device may have been added with another device file.
[ 8138.833] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
[ 8138.833] (II) No input driver specified, ignoring this device.
[ 8138.833] (II) This device may have been added with another device file.
[ 8138.833] (II) config/udev: Adding input device HDA Intel PCH Dock Headphone (/dev/input/event11)
[ 8138.833] (II) No input driver specified, ignoring this device.
[ 8138.833] (II) This device may have been added with another device file.
[ 8138.833] (II) config/udev: Adding input device HDA Intel PCH Dock Mic (/dev/input/event8)
[ 8138.833] (II) No input driver specified, ignoring this device.
[ 8138.833] (II) This device may have been added with another device file.
[ 8138.833] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event9)
[ 8138.833] (II) No input driver specified, ignoring this device.
[ 8138.833] (II) This device may have been added with another device file.
[ 8138.833] (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/event2)
[ 8138.833] (**) Logitech Gaming Mouse G400: Applying InputClass "evdev pointer catchall"
[ 8138.833] (II) Using input driver 'evdev' for 'Logitech Gaming Mouse G400'
[ 8138.833] (**) Logitech Gaming Mouse G400: always reports core events
[ 8138.833] (**) evdev: Logitech Gaming Mouse G400: Device: "/dev/input/event2"
[ 8138.833] (--) evdev: Logitech Gaming Mouse G400: Vendor 0x46d Product 0xc245
[ 8138.833] (--) evdev: Logitech Gaming Mouse G400: Found 12 mouse buttons
[ 8138.833] (--) evdev: Logitech Gaming Mouse G400: Found scroll wheel(s)
[ 8138.833] (--) evdev: Logitech Gaming Mouse G400: Found relative axes
[ 8138.833] (--) evdev: Logitech Gaming Mouse G400: Found x and y relative axes
[ 8138.833] (II) evdev: Logitech Gaming Mouse G400: Configuring as mouse
[ 8138.833] (II) evdev: Logitech Gaming Mouse G400: Adding scrollwheel support
[ 8138.833] (**) evdev: Logitech Gaming Mouse G400: YAxisMapping: buttons 4 and 5
[ 8138.833] (**) evdev: Logitech Gaming Mouse G400: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 8138.833] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input2/event2"
[ 8138.833] (II) XINPUT: Adding extended input device "Logitech Gaming Mouse G400" (type: MOUSE, id 10)
[ 8138.833] (II) evdev: Logitech Gaming Mouse G400: initialized for relative axes.
[ 8138.833] (**) Logitech Gaming Mouse G400: (accel) keeping acceleration scheme 1
[ 8138.833] (**) Logitech Gaming Mouse G400: (accel) acceleration profile 0
[ 8138.833] (**) Logitech Gaming Mouse G400: (accel) acceleration factor: 2.000
[ 8138.833] (**) Logitech Gaming Mouse G400: (accel) acceleration threshold: 4
[ 8138.834] (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/mouse0)
[ 8138.834] (II) No input driver specified, ignoring this device.
[ 8138.834] (II) This device may have been added with another device file.
[ 8138.834] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 8138.834] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 8138.834] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 8138.834] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 8138.834] (**) AT Translated Set 2 keyboard: always reports core events
[ 8138.834] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 8138.834] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 8138.834] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 8138.834] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 8138.834] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 8138.834] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[ 8138.834] (**) Option "xkb_rules" "evdev"
[ 8138.834] (**) Option "xkb_model" "evdev"
[ 8138.834] (**) Option "xkb_layout" "gb"
[ 8138.834] (**) Option "xkb_options" "ctrl:nocaps"
[ 8138.834] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event15)
[ 8138.834] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 8138.834] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "two finger scrolling"
[ 8138.834] (II) LoadModule: "synaptics"
[ 8138.834] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 8138.834] (II) Module synaptics: vendor="X.Org Foundation"
[ 8138.834] compiled for 1.14.1, module version = 1.7.1
[ 8138.834] Module class: X.Org XInput Driver
[ 8138.834] ABI class: X.Org XInput driver, version 19.1
[ 8138.834] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 8138.834] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 8138.834] (**) Option "Device" "/dev/input/event15"
[ 8138.846] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 8138.846] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5888 (res 75)
[ 8138.846] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4820 (res 105)
[ 8138.846] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 8138.846] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 8138.846] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
[ 8138.846] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 8138.846] (**) Option "EmulateTwoFingerMinZ" "40"
[ 8138.846] (**) Option "EmulateTwoFingerMinW" "8"
[ 8138.846] (**) Option "VertTwoFingerScroll" "on"
[ 8138.846] (**) Option "HorizTwoFingerScroll" "on"
[ 8138.846] (**) Option "TapButton1" "1"
[ 8138.846] (**) Option "TapButton2" "2"
[ 8138.846] (**) Option "TapButton3" "3"
[ 8138.846] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 8138.846] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 8138.849] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input15/event15"
[ 8138.849] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
[ 8138.849] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 8138.849] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 8138.849] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.036
[ 8138.849] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 8138.849] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 8138.849] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 8138.849] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 8138.849] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 8138.849] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 8138.849] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
[ 8138.849] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/event17)
[ 8138.849] (**) TPPS/2 IBM TrackPoint: Applying InputClass "evdev pointer catchall"
[ 8138.849] (**) TPPS/2 IBM TrackPoint: Applying InputClass "ThinkPad TrackPoint"
[ 8138.849] (II) Using input driver 'evdev' for 'TPPS/2 IBM TrackPoint'
[ 8138.850] (**) TPPS/2 IBM TrackPoint: always reports core events
[ 8138.850] (**) evdev: TPPS/2 IBM TrackPoint: Device: "/dev/input/event17"
[ 8138.850] (--) evdev: TPPS/2 IBM TrackPoint: Vendor 0x2 Product 0xa
[ 8138.850] (--) evdev: TPPS/2 IBM TrackPoint: Found 3 mouse buttons
[ 8138.850] (--) evdev: TPPS/2 IBM TrackPoint: Found relative axes
[ 8138.850] (--) evdev: TPPS/2 IBM TrackPoint: Found x and y relative axes
[ 8138.850] (II) evdev: TPPS/2 IBM TrackPoint: Configuring as mouse
[ 8138.850] (**) Option "EmulateWheel" "true"
[ 8138.850] (**) Option "EmulateWheelButton" "2"
[ 8138.850] (**) Option "YAxisMapping" "4 5"
[ 8138.850] (**) evdev: TPPS/2 IBM TrackPoint: YAxisMapping: buttons 4 and 5
[ 8138.850] (**) Option "XAxisMapping" "6 7"
[ 8138.850] (**) evdev: TPPS/2 IBM TrackPoint: XAxisMapping: buttons 6 and 7
[ 8138.850] (**) evdev: TPPS/2 IBM TrackPoint: EmulateWheelButton: 2, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 8138.850] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/serio2/input/input17/event17"
[ 8138.850] (II) XINPUT: Adding extended input device "TPPS/2 IBM TrackPoint" (type: MOUSE, id 13)
[ 8138.850] (II) evdev: TPPS/2 IBM TrackPoint: initialized for relative axes.
[ 8138.850] (**) TPPS/2 IBM TrackPoint: (accel) keeping acceleration scheme 1
[ 8138.850] (**) TPPS/2 IBM TrackPoint: (accel) acceleration profile 0
[ 8138.850] (**) TPPS/2 IBM TrackPoint: (accel) acceleration factor: 2.000
[ 8138.850] (**) TPPS/2 IBM TrackPoint: (accel) acceleration threshold: 4
[ 8138.850] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint (/dev/input/mouse2)
[ 8138.850] (II) No input driver specified, ignoring this device.
[ 8138.850] (II) This device may have been added with another device file.
[ 8138.850] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event1)
[ 8138.850] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
[ 8138.850] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
[ 8138.850] (II) Using input driver 'evdev' for 'ThinkPad Extra Buttons'
[ 8138.850] (**) ThinkPad Extra Buttons: always reports core events
[ 8138.850] (**) evdev: ThinkPad Extra Buttons: Device: "/dev/input/event1"
[ 8138.850] (--) evdev: ThinkPad Extra Buttons: Vendor 0x17aa Product 0x5054
[ 8138.850] (--) evdev: ThinkPad Extra Buttons: Found keys
[ 8138.850] (II) evdev: ThinkPad Extra Buttons: Configuring as keyboard
[ 8138.850] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input1/event1"
[ 8138.850] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 14)
[ 8138.850] (**) Option "xkb_rules" "evdev"
[ 8138.850] (**) Option "xkb_model" "evdev"
[ 8138.850] (**) Option "xkb_layout" "gb"
[ 8138.850] (**) Option "xkb_options" "ctrl:nocaps"
[ 8147.677] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 8181.528] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 8189.334] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 8593.711] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 8597.651] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 8604.061] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 13947.442] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 15638.705] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
I've since switched over to Nouveau, figuring I shouldn't at least taint my kernel if things might get to that level. This was nice, since KMS fixed the framebuffer hijack at boot and somewhere in the process solves the "Scheduling while atomic" bug. But it doesn't handle any better with the separate X displays thing.
This is when I say ok, great, let's set it up with Xinerama or something. Xorg isn't having it.
Here's my attempted dual-monitor xorg.conf, based on this forum thread:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "DisplayLinkScreen"
Screen 1 "ThinkpadScreen" LeftOf "DisplayLinkScreen"
Option "Xinerama" "on"
EndSection
Section "Monitor"
# 1600x900 @ 60.00 Hz (GTF) hsync: 55.92 kHz; pclk: 119.00 MHz
Identifier "ThinkpadMonitor"
VendorName "Unknown"
ModelName "AU Optronics Corporation"
HorizSync 36.5 - 54.7
VertRefresh 40.0 - 60.0
ModeLine "1600x900_60.00" 119.00 1600 1696 1864 2128 900 901 904 932 -hsync +vsync
# Option "DPMS"
EndSection
Section "Device"
Identifier "nvidiaCard"
Driver "nouveau"
VendorName "NVIDIA Corporation"
BoardName "NVS 4200M"
EndSection
Section "Screen"
Identifier "ThinkpadScreen"
Device "nvidiaCard"
Monitor "ThinkpadMonitor"
DefaultDepth 16
Option "Stereo" "0"
Option "metamodes" "1600x900_60 +0+0"
Option "FlatPanelProperties" "Scaling=Native"
Option "RegistryDwords" "OGL_MaxFramesAllowed=0x0; EnableBrightnessControl=1; PerfLevelSrc=0x3333"
Option "OnDemandVBlankInterrupts" "1"
Option "TripleBuffer" "1"
SubSection "Display"
Depth 16
EndSubSection
EndSection
################ DisplayLink Stuff ###################
Section "Device"
Identifier "DisplayLinkDevice"
Driver "fbdev"
BusID "USB" # needed to use multiple DisplayLink devices
Option "fbdev" "/dev/fb1" # change to whatever device you want to use
# Option "rotate" "CCW" # uncomment for rotation
EndSection
Section "Monitor"
Identifier "DisplayLinkMonitor"
EndSection
Section "Screen"
Identifier "DisplayLinkScreen"
Device "DisplayLinkDevice"
Monitor "DisplayLinkMonitor"
DefaultDepth 16
EndSection
Section "Module"
Load "glx"
EndSection
And here's the crash log:
[ 3568.803]
X.Org X Server 1.14.1
Release Date: 2013-04-17
[ 3568.805] X Protocol Version 11, Revision 0
[ 3568.806] Build Operating System: Linux 3.8.7-1-ARCH x86_64
[ 3568.807] Current Operating System: Linux beefmaster 3.9.4-1-ARCH #1 SMP PREEMPT Sat May 25 16:14:55 CEST 2013 x86_64
[ 3568.807] Kernel command line: root=/dev/sda8 rw acpi_backlight=vendor acpi_osi=Linux
[ 3568.808] Build Date: 17 April 2013 02:37:06PM
[ 3568.809]
[ 3568.810] Current version of pixman: 0.30.0
[ 3568.811] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3568.811] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3568.814] (==) Log file: "/var/log/Xorg.1.log", Time: Sat Jun 1 22:26:36 2013
[ 3568.815] (==) Using config file: "/etc/X11/xorg.conf"
[ 3568.816] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 3568.816] (==) ServerLayout "Layout0"
[ 3568.816] (**) |-->Screen "DisplayLinkScreen" (0)
[ 3568.816] (**) | |-->Monitor "DisplayLinkMonitor"
[ 3568.816] (**) | |-->Device "DisplayLinkDevice"
[ 3568.816] (**) |-->Screen "ThinkpadScreen" (1)
[ 3568.816] (**) | |-->Monitor "<default monitor>"
[ 3568.816] (==) No device specified for screen "ThinkpadScreen".
Using the first device section listed.
[ 3568.816] (**) | |-->Device "nvidiaCard"
[ 3568.816] (==) No monitor specified for screen "ThinkpadScreen".
Using a default monitor configuration.
[ 3568.816] (**) Option "Xinerama" "on"
[ 3568.816] (==) Automatically adding devices
[ 3568.816] (==) Automatically enabling devices
[ 3568.816] (==) Automatically adding GPU devices
[ 3568.816] (**) Xinerama: enabled
[ 3568.816] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 3568.816] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3568.816] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 3568.816] (II) Loader magic: 0x7fcc20
[ 3568.816] (II) Module ABI versions:
[ 3568.816] X.Org ANSI C Emulation: 0.4
[ 3568.816] X.Org Video Driver: 14.1
[ 3568.816] X.Org XInput driver : 19.1
[ 3568.816] X.Org Server Extension : 7.0
[ 3568.816] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 3569.037] (--) PCI:*(0:1:0:0) 10de:1057:17aa:21ce rev 161, Mem @ 0xf2000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
[ 3569.037] Initializing built-in extension Generic Event Extension
[ 3569.038] Initializing built-in extension SHAPE
[ 3569.038] Initializing built-in extension MIT-SHM
[ 3569.039] Initializing built-in extension XInputExtension
[ 3569.040] Initializing built-in extension XTEST
[ 3569.041] Initializing built-in extension BIG-REQUESTS
[ 3569.041] Initializing built-in extension SYNC
[ 3569.042] Initializing built-in extension XKEYBOARD
[ 3569.043] Initializing built-in extension XC-MISC
[ 3569.043] Initializing built-in extension SECURITY
[ 3569.044] Initializing built-in extension XINERAMA
[ 3569.045] Initializing built-in extension XFIXES
[ 3569.045] Initializing built-in extension RENDER
[ 3569.046] Initializing built-in extension RANDR
[ 3569.047] Initializing built-in extension COMPOSITE
[ 3569.047] Initializing built-in extension DAMAGE
[ 3569.048] Initializing built-in extension MIT-SCREEN-SAVER
[ 3569.049] Initializing built-in extension DOUBLE-BUFFER
[ 3569.049] Initializing built-in extension RECORD
[ 3569.050] Initializing built-in extension DPMS
[ 3569.050] Initializing built-in extension X-Resource
[ 3569.051] Initializing built-in extension XVideo
[ 3569.052] Initializing built-in extension XVideo-MotionCompensation
[ 3569.052] Initializing built-in extension XFree86-VidModeExtension
[ 3569.053] Initializing built-in extension XFree86-DGA
[ 3569.053] Initializing built-in extension XFree86-DRI
[ 3569.054] Initializing built-in extension DRI2
[ 3569.054] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 3569.054] (II) LoadModule: "glx"
[ 3569.054] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3569.054] (II) Module glx: vendor="X.Org Foundation"
[ 3569.054] compiled for 1.14.1, module version = 1.0.0
[ 3569.054] ABI class: X.Org Server Extension, version 7.0
[ 3569.054] (==) AIGLX enabled
[ 3569.054] Loading extension GLX
[ 3569.054] (II) LoadModule: "fbdev"
[ 3569.055] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 3569.055] (II) Module fbdev: vendor="X.Org Foundation"
[ 3569.055] compiled for 1.14.1, module version = 0.4.3
[ 3569.055] Module class: X.Org Video Driver
[ 3569.055] ABI class: X.Org Video Driver, version 14.1
[ 3569.055] (II) LoadModule: "nouveau"
[ 3569.055] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 3569.055] (II) Module nouveau: vendor="X.Org Foundation"
[ 3569.055] compiled for 1.14.0, module version = 1.0.7
[ 3569.055] Module class: X.Org Video Driver
[ 3569.055] ABI class: X.Org Video Driver, version 14.1
[ 3569.055] (II) FBDEV: driver for framebuffer: fbdev
[ 3569.055] (II) NOUVEAU driver
[ 3569.055] (II) NOUVEAU driver for NVIDIA chipset families :
[ 3569.055] RIVA TNT (NV04)
[ 3569.055] RIVA TNT2 (NV05)
[ 3569.055] GeForce 256 (NV10)
[ 3569.055] GeForce 2 (NV11, NV15)
[ 3569.055] GeForce 4MX (NV17, NV18)
[ 3569.055] GeForce 3 (NV20)
[ 3569.055] GeForce 4Ti (NV25, NV28)
[ 3569.055] GeForce FX (NV3x)
[ 3569.055] GeForce 6 (NV4x)
[ 3569.055] GeForce 7 (G7x)
[ 3569.055] GeForce 8 (G8x)
[ 3569.055] GeForce GTX 200 (NVA0)
[ 3569.055] GeForce GTX 400 (NVC0)
[ 3569.055] (++) using VT number 2
[ 3569.055] (WW) Falling back to old probe method for fbdev
[ 3569.055] (II) Loading sub module "fbdevhw"
[ 3569.055] (II) LoadModule: "fbdevhw"
[ 3569.055] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 3569.055] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 3569.055] compiled for 1.14.1, module version = 0.0.2
[ 3569.055] ABI class: X.Org Video Driver, version 14.1
[ 3569.055] (II) FBDEV(0): using /dev/fb1
[ 3569.055] (II) [drm] nouveau interface version: 1.1.0
[ 3569.056]
Fatal server error:
[ 3569.056] Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[ 3569.056]
[ 3569.056] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 3569.056] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
[ 3569.056] (EE)
[ 3569.058] Server terminated with error (1). Closing log file.
It's asking for busIDs for framebuffer devices. This problem has been around as far back as 2010, as seen in the Libdlo mailing list. I've been using the fix described there. It doesn't work.
I uninstall the custom xf86-video-fbdev from the AUR and install the standard Arch binary. Unlike the AUR version, it automatically places fbdev_drv.so in /usr/lib/xorg/modules/drivers as expected.
Same problem. Here's the log, mostly the same as earlier:
X.Org X Server 1.14.1
Release Date: 2013-04-17
[ 8754.488] X Protocol Version 11, Revision 0
[ 8754.489] Build Operating System: Linux 3.8.7-1-ARCH x86_64
[ 8754.490] Current Operating System: Linux beefmaster 3.9.4-1-ARCH #1 SMP PREEMPT Sat May 25 16:14:55 CEST 2013 x86_64
[ 8754.490] Kernel command line: root=/dev/sda8 rw acpi_backlight=vendor acpi_osi=Linux
[ 8754.492] Build Date: 17 April 2013 02:37:06PM
[ 8754.492]
[ 8754.493] Current version of pixman: 0.30.0
[ 8754.495] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 8754.495] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 8754.498] (==) Log file: "/var/log/Xorg.1.log", Time: Sat Jun 1 23:53:01 2013
[ 8754.499] (==) Using config file: "/etc/X11/xorg.conf"
[ 8754.499] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 8754.500] (==) ServerLayout "Layout0"
[ 8754.500] (**) |-->Screen "DisplayLinkScreen" (0)
[ 8754.500] (**) | |-->Monitor "DisplayLinkMonitor"
[ 8754.500] (**) | |-->Device "DisplayLinkDevice"
[ 8754.500] (**) |-->Screen "ThinkpadScreen" (1)
[ 8754.500] (**) | |-->Monitor "ThinkpadMonitor"
[ 8754.500] (**) | |-->Device "nvidiaCard"
[ 8754.500] (**) Option "Xinerama" "on"
[ 8754.500] (==) Automatically adding devices
[ 8754.500] (==) Automatically enabling devices
[ 8754.500] (==) Automatically adding GPU devices
[ 8754.500] (**) Xinerama: enabled
[ 8754.500] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 8754.500] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 8754.500] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 8754.500] (II) Loader magic: 0x7fcc20
[ 8754.500] (II) Module ABI versions:
[ 8754.500] X.Org ANSI C Emulation: 0.4
[ 8754.500] X.Org Video Driver: 14.1
[ 8754.500] X.Org XInput driver : 19.1
[ 8754.500] X.Org Server Extension : 7.0
[ 8754.500] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 8754.720] (--) PCI:*(0:1:0:0) 10de:1057:17aa:21ce rev 161, Mem @ 0xf2000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
[ 8754.720] Initializing built-in extension Generic Event Extension
[ 8754.721] Initializing built-in extension SHAPE
[ 8754.722] Initializing built-in extension MIT-SHM
[ 8754.722] Initializing built-in extension XInputExtension
[ 8754.723] Initializing built-in extension XTEST
[ 8754.724] Initializing built-in extension BIG-REQUESTS
[ 8754.725] Initializing built-in extension SYNC
[ 8754.725] Initializing built-in extension XKEYBOARD
[ 8754.726] Initializing built-in extension XC-MISC
[ 8754.727] Initializing built-in extension SECURITY
[ 8754.728] Initializing built-in extension XINERAMA
[ 8754.728] Initializing built-in extension XFIXES
[ 8754.729] Initializing built-in extension RENDER
[ 8754.730] Initializing built-in extension RANDR
[ 8754.730] Initializing built-in extension COMPOSITE
[ 8754.731] Initializing built-in extension DAMAGE
[ 8754.731] Initializing built-in extension MIT-SCREEN-SAVER
[ 8754.732] Initializing built-in extension DOUBLE-BUFFER
[ 8754.733] Initializing built-in extension RECORD
[ 8754.733] Initializing built-in extension DPMS
[ 8754.734] Initializing built-in extension X-Resource
[ 8754.735] Initializing built-in extension XVideo
[ 8754.735] Initializing built-in extension XVideo-MotionCompensation
[ 8754.736] Initializing built-in extension XFree86-VidModeExtension
[ 8754.736] Initializing built-in extension XFree86-DGA
[ 8754.737] Initializing built-in extension XFree86-DRI
[ 8754.737] Initializing built-in extension DRI2
[ 8754.737] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[ 8754.737] (II) LoadModule: "glx"
[ 8754.738] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 8754.738] (II) Module glx: vendor="X.Org Foundation"
[ 8754.738] compiled for 1.14.1, module version = 1.0.0
[ 8754.738] ABI class: X.Org Server Extension, version 7.0
[ 8754.738] (==) AIGLX enabled
[ 8754.738] Loading extension GLX
[ 8754.738] (II) LoadModule: "fbdev"
[ 8754.738] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 8754.738] (II) Module fbdev: vendor="X.Org Foundation"
[ 8754.738] compiled for 1.14.0, module version = 0.4.3
[ 8754.738] Module class: X.Org Video Driver
[ 8754.738] ABI class: X.Org Video Driver, version 14.1
[ 8754.738] (II) LoadModule: "nouveau"
[ 8754.738] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 8754.738] (II) Module nouveau: vendor="X.Org Foundation"
[ 8754.738] compiled for 1.14.0, module version = 1.0.7
[ 8754.738] Module class: X.Org Video Driver
[ 8754.738] ABI class: X.Org Video Driver, version 14.1
[ 8754.738] (II) FBDEV: driver for framebuffer: fbdev
[ 8754.738] (II) NOUVEAU driver
[ 8754.738] (II) NOUVEAU driver for NVIDIA chipset families :
[ 8754.738] RIVA TNT (NV04)
[ 8754.739] RIVA TNT2 (NV05)
[ 8754.739] GeForce 256 (NV10)
[ 8754.739] GeForce 2 (NV11, NV15)
[ 8754.739] GeForce 4MX (NV17, NV18)
[ 8754.739] GeForce 3 (NV20)
[ 8754.739] GeForce 4Ti (NV25, NV28)
[ 8754.739] GeForce FX (NV3x)
[ 8754.739] GeForce 6 (NV4x)
[ 8754.739] GeForce 7 (G7x)
[ 8754.739] GeForce 8 (G8x)
[ 8754.739] GeForce GTX 200 (NVA0)
[ 8754.739] GeForce GTX 400 (NVC0)
[ 8754.739] (++) using VT number 2
[ 8754.739] (WW) Falling back to old probe method for fbdev
[ 8754.739] (II) Loading sub module "fbdevhw"
[ 8754.739] (II) LoadModule: "fbdevhw"
[ 8754.739] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 8754.739] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 8754.739] compiled for 1.14.1, module version = 0.0.2
[ 8754.739] ABI class: X.Org Video Driver, version 14.1
[ 8754.739] (II) FBDEV(0): using /dev/fb1
[ 8754.739] (II) [drm] nouveau interface version: 1.1.0
[ 8754.739]
Fatal server error:
[ 8754.739] Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[ 8754.739]
[ 8754.739] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 8754.739] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
[ 8754.739] (EE)
[ 8754.742] Server terminated with error (1). Closing log file.
One thing I attempted was using the udl kernel module. If I remember correctly, it would detect the display, but I could not get it to show any output. Not adequate, and I'd be moving backwards since I'm suspecting this is a bug in fbdev.c, not the udlfb.
One of the issues I have with a multiseat configuration (which, honestly, really is not optimal anyhow) is that whichever X display I'm not using freezes completely until it gets focus again. There's probably a workaround for this issue (I hope), but seeing as others seem to have paved the way for solutions to this problem, I can only assume the answer for true multi-monitor support lies somewhere.
Edit 1:43 AM Sunday, June 2, 2013 (EDT)
Trying this out with bumblebee and proprietary nvidia drivers (nouveau doesn't currently play well with bumblebee). For what it's worth, here's my dmesg output:
[ 2.410269] udlfb: DisplayLink Lenovo LT1421 wide - serial #6V9BBRM1
[ 2.410273] udlfb: vid_17e9&pid_03e0&rev_0108 driver's dlfb_data struct at ffff880230bb1800
[ 2.410274] udlfb: console enable=1
[ 2.410275] udlfb: fb_defio enable=1
[ 2.410275] udlfb: shadow enable=1
[ 2.410376] udlfb: vendor descriptor length:17 data:17 5f 01 0015 05 00 01 03 00 04
[ 2.410380] udlfb: DL chip limited to 1500000 pixel modes
[ 2.410436] udlfb: allocated 4 65024 byte urbs
[ 2.503239] udlfb: 1366x768 @ 60 Hz valid mode
[ 2.503245] udlfb: Reallocating framebuffer. Addresses will change!
[ 2.504482] udlfb: 1366x768 @ 60 Hz valid mode
[ 2.504488] udlfb: set_par mode 1366x768
[ 2.507644] udlfb: DisplayLink USB device /dev/fb1 attached. 1366x768 resolution. Using 4104K framebuffer memory
Here's a list of related information I've found that isn't mentioned above:
Getting Hotplugging working with a DisplayLink USB to DVI adapter, keithp, July 2012
DisplayLink on Linux, Mulchman's Blog (archive)
Dual Monitor (Multi seat) setup with Displaylink USB Montors, red
DisplayLink protocol reference information, 2008
DisplayLink X server crashes, Libdlo mailing list
DisplayLink USB GPU Hot-Plugging On Linux, Phoronix, July 2012
Claims DisplayLink USB GPU hotplugging "now works properly under Linux." One year ago.
Mutli-monitor on the go, DisplayLink usb monitor, mitechie, November 2007
One of the only posts I've found where this actually is proven to work. It does not, however, work for me.
DisplayLink on Fedora Linux, nameq0, September 2011
Fedora 17 seems to have good support Pieaidie EINS!, May 2012
Somewhat relevant posts on Multiseat X:
Multiseat, X.org
MultiseatX, Ubuntu
Xorg Multiseat, Arch Wiki
Relevant Arch forum posts:
void7910 found a workaround with a separate X server and x2x
schrotti found a solution
camerongray and wassy had the same problem as me, never found a solution
camerongray claims it works in Fedora
nobody ever replied to GeoffTK
webdawg found a bunch of posts suggesting xrandr can detect DisplayLink. I haven't found this to be true.
suley couldn't get xrandr to detect DisplayLink
gjasso got it working (linked above, no success for me)
pjoter claims he configured a DisplayLink monitor to serve as a second graphics card, but provides no details whatsoever
BurntSushi claims RandR has no multi-GPU support in January 2013 ...
Pyro2927 had success setting his USB monitor to Screen 0, which I've done myself with no success
Last edited by ndt (2013-06-02 05:46:37)tbranyen—thanks a bunch for the post. I'm going to give that a shot, and update the wiki once I get my findings together on the matter.
Can you please tell me what kernel version you have gotten this working with, and the output of:
egrep -i " connected|card detect|primary dev" /var/log/Xorg.0.log
Also, the screen "garbage" you're seeing is an artifact of improper damage handling in the driver. I haven't discovered yet whether this is a problem with the kernel drivers or X, but the reason it occurs is this: DisplayLink manages to drive an entire display over USB by only updating pixels that are "damaged", or altered, each frame. When you initially load the screen, it spits garbage across the entire screen. On a normal display, this garbage is removed on the subsequently drawn frame. However, with DisplayLink, the graphics card does a bunch of calculations to see which frames specifically it has to change. It then sends to the USB screen data only for those particular pixels. A fairly ingenious solution, if you ask me, but when it goes wrong you see artifacts like you are describing.
In order to remove them, just maximize a window once. This will "damage" the entire screen and force it to redraw all pixels.
Edit:
I just got it working with your recommendations. It was funny, though - I had to use xrandr to offload my Intel card to the modesetting driver before I could get things functional.
$ xrandr --listproviders :(
Providers: number : 2
Provider 0: id: 0x66 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 2 outputs: 2 associated providers: 0 name:Intel
Provider 1: id: 0x41 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting
$ xrandr --setprovideroutputsource 1 0
$ xrandr
Screen 0: minimum 320 x 200, current 1600 x 900, maximum 8192 x 8192
LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
1600x900 60.0*+ 40.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
DVI-4 connected (normal left inverted right x axis y axis)
1366x768 60.0 +
$ xrandr --auto --output DVI-4 --right-of LVDS1
That's the command list I had to use to get it working.
And then I experienced the mouse bug that you described. And maximizing a window doesn't fix it like I had hoped (as it did with udlfb). So my guess is that udl still isn't perfect.
Last edited by ndt (2013-07-10 04:14:24) -
ICal -- Entourage Incompatibility?
I'm running Tiger 10.4.10, and Entourage 11.3.8. It would appear that there is (still) some latent incompabiliy between iCal-originated events and Entourage (MS Office 2004 for Mac) invitees. I have the latest versions of iCal (2.0.5), Tiger (10.4.10), and Entourage (11.3.8). I'm aware that there have been issues related to DST, but my understanding is that these should have been corrected by software upgrades.
It appears that the problem I'm seeing occurs only when iCal creates an event and invites an Entourage user. Here are my observations of such events:
1. In the invitation email as received by Entourage, the End Date is shown as *January 1, 1601*. Clearly this is incorrect.
2. The event posts to the entourage calendar, but with a duration of zero (even though the original event was created in iCal with a non-zero duration, say, 1 hour).
3. The event does NOT initially show up in any of the Entourage Calendar views (Month, for example). Apparently, this is due to the fact that the duration is zero.
4. If you open the event in Entourage and manually change the duration to a non-zero value, then the event will show up in Calendar views.
5. However, the event is still displayed in Calendar view with a start time that is *one hour earlier* than the actual start time (the event itself displays the correct start time).
Invitations originated by another instance of Entourage seem to post correctly in all respects, so it would appear that there is some sort of incompatibility issue between iCal and Entourage?
Is anyone else seeing this behavior and/or does anyone know of a fix for it?
Thanks!Me too. Same problems. Anyone?
-
Is there any incompatibility in using different JDBC and Oracle database versions?
Hi everybody,
I hope you can answer me ASAP.
Which version of JDBC driver for Oracle could I use to access an Oracle database version 8.0.4.3.0 running on a SUN machine?
Is it necessary to use the specific driver concerning to that version or could we use the JDBC version 8.1.6?
If we decide to use JDBC 8.1.6 to work against the 8.0.4.3.0 database, will we find any incompatibility or problem?
Thanks.
nullI don't know the answer to your question, but while looking for something else, I found a table listing "requirements and compatibilities for oracle jdbc drivers" that might answer your question:
http://technet.oracle.com/docs/products/oracle8i/doc_library/817_doc/java.817/a83724/getsta1.htm#1008206
(My aologies if that URL gets broken apart by this posting software and you have to piece it together.)
Hope this helps. -
Have downloaded the latest version of ITunes and now i get "Incompatable Application" I tunes will no longer open. have worked my way through FAQ and help to no avail. What am i doing wrong? currently running windows 7.
Have downloaded the latest version of ITunes and now i get "Incompatable Application" I tunes will no longer open. have worked my way through FAQ and help to no avail. What am i doing wrong? currently running windows 7.
-
As stated above. I need to upload pictures to my business website but now my upload box is just saying incompatable plug in. I wish I had never installed Lion as I was happy with my mac on its origional OS, I only installed it as my Java had disappeared and I was instructed on the java page that to upload the latest verion of Java I needed to upgrade to Lion. I am really not happy as I now cannot do the job on my mac that I bought the mac to do the job on. Please help. Is it possible to uninstall Lion without buggering up my mac and going back to my origional OS. I am on safari. Not even sure which version of Lion I have downloaded so I am sure you can tell I am not a teccy
Welcome to Apple Communities
Uninstall > http://fpdownload.macromedia.com/get/flashplayer/current/support/uninstall_flash _player_osx.dmg Finally, install Flash > http://get.adobe.com/flashplayer/otherversions -
Is Apple doing anything to fix the problem with displaylink in Mavericks?
I have been doing the Beta track for several years. Apple has been fairly good about ironing out the bugs before a release (as compared to Microsuck and other OS alternatives). But this problem with DisplayLink and Mavericks is about to kill me. I've been running multiple displays for several years and never had problems with prior OSX versions. My work computer (Macbook Pro) is still running Lion and works perfectly with DisplayLink and two 27" Samsung HD monitors. I would really love to get back to using the monitor setup with my Dev environment, however I can't even get a 2013 model Mavericks Macbook Pro to recognize that the DisplayLink device (IBM USB3.0 dock) is connected.
Once or twice I've gotten one monitor to show up after using the computer for a random amount of time. On that occasion, suddenly the main screen blinked and the second monitor came to life. I was reading webmail with Safari at the time and no other apps were running or had been started when it happened. This sort of thing isn't what I would classify as release-ready.
Every seed announcement I keep hoping for a fix, but after 3 since the Mav release, I'm beginning to lose hope. Anyone have info on how this might be made to work?
Thanks
DavidDisplayLink also points fingers at Apple, which may be completely valid, but expecting Apple to put much effort into problems that only affect third-party hardware using an unsupported interface seems a bit of wishful thinking.
However, rumor sites indicate a focus on graphics in the next update : http://www.macrumors.com/2014/03/06/apple-seeds-first-os-x-10-9-3-build-to-devel opers/ -
Apparent XP SP3 incompatibility with PC Suite 6.86...
On my Windows XP with SP3 I have installed PC Suite 6.86.9.3.
Since I have upgraded by SP2 to SP3, it appears that I cannot use PC Suite to connect to my NOKIA 6230.
The get connected wizard states that there is no connection type, although my Bluetooth is perfectly working.
I've already tried reinstalling the PC Suite program, rebooting the computer, etc.
Is this a "temporary" incompatibility ?
Any ideas on what to do?
Thanks!I have Nokia N80 IE..., PC suite works very well on Win XP 32bit SP2...., i am connecting over bluetooth
i have upgraded to SP3, and still works....
after few weeks, i did windows update, and installed small number of packages.., after this.., nokia pc suite doesnt recognize my mobile (and any other).., i can't select nothing (irda, bluetooth, USB)...
i tried with USB cabel, also.., but nothing happens...
i think problem is in windows upadate, bluetooth connection works differently or it's problem in nokia pc suite (latest- 6.68.9.3)...
other bluetooth software works fine now...
I am very angry because I cant sync my N80 and Outlook...
(sorry on my bad english) -
My old iPad 2 is updated to ios 7.1.2 but I have a new 4 which is only compatible with 7.0.4 from setup. How can I backup my account to the new iPad with this incompatibility?
What you need to do is temporarily set up your new 4. Just long enough to update the operating system. Then you can erase all content and settings - which puts it back to its out of box state, then set it up again, this time restoring it from the backup of your two.
So, using the same Apple ID on both - just to keep things easy - set up your 4. Just basically choose 'set up as new' to activate it, then immediately update the iOS to 7.1.2.
then erase all content and settings, which puts it back to 'llike new'...but the operating system will not reset, it'll remain 7.1.2
Then set it up again, this time choosing to 'restore from the backup' of your 2 and your 4 will be a near clone of your two. -
Pages 5.1 file incompatibility with Pages 5 and 5.01?
Can anyone who has access to both Pages 5.01 and Pages 5.1 on different machines test the following:
1. Create a file in Pages 5.01 using various text and objects eg TextBox, Shapes, Images, Charts and Tables labelling it as XYZ v5.01
I suggest opening a vertical ruler as well, because this is one of the update "features".
2. Open the same file in Pages 5.1 make a few minor changes and resave it relabelling it as XYZ v5.1
3. Reopen that in Pages 5.01 and see if it reports an incompatible version
If you could also pass it through iCloud (change the name to note) to check if that also renders it unopenable in Pages 5.01
Thank you
PeterProblem confirmed in AppleStore.
None of the New Pages 5.1, Keynote 6.1 & Numbers 3.1 files can be opened by previous versions.
In fact you get an error when trying to open the in built templates!
So now you have an endless succession of incompatibility even between minor updates.
Apple, Apple Apple!
What has happened to you? -
Adobe acrobat pro 9.5.5 incompatibility with preview
anybody having incompatibility btwn these two programs? when I edit a PDF in Acrobat Pro 9.5.5, like this:
and then open the edited PDF in Preview, it looks like this:
text boxes disappear, arrows disappear, some text turns to nonsense (here's another example, where text is not aligned properly in text box):
any thoughts?Unfortunately no. However, I did try converting several other stock photos that I have on my machine, and that worked fine. This leads me to believe there is something "different" about the first set of JPGs that I was trying to convert. Maybe a security setting on the camera that they were taken with? I'm still at a loss. But thanks for the suggestion that sparked the other idea
-
Since updating to the most recent Adobe Reader v11.0.10, getting an Adobe Reader Protected Mode: Adobe Reader cannot open in Protected Mode due do an incompatibility with your system configuration. Would you like to open Adobe Reader with Protected Mode disabled?
The solution I was looking for was to launch Adobe Reader in Protected Mode.
I could not identify issues preventing Protected Mode from starting. What ended up working, was to do a complete uninstall, followed by a reinstall. Now we can load Reader in Protected Mode. -
External Display Incompatibility
I recently upgraded to Snow Leopard (all software updates completed-10.6.1), and ever since, my external display (22" LG Flatron W2252TG) has been looping in and out of power saving mode. I am using a vga cord with a mini displayport to vga adaptor, and a late 2008 macbook (first version of unibody macbooks).
If I have the display plugged into a power outlet, and the vga cable plugged into the display, the screen says "check signal cable"...makes sense. However, when I attach the mini displayport adaptor (Firmware 1.0.3 or 1.3, I'm not quite sure), to the other end of the vga cable, the screen immediately says entering power saving mode. However, it never actually goes into it. It just turns the bulb display off (but the power light is still on), and then comes back to the message about going into power saving mode, and keeps looping.
The monitor works fine on any computer that doesn't require the mini displayport to vga adaptor, so I'm sure it's not the vga cable.
Also, I have tried all combinations of connecting the screen. I booted it in clamshell mode, not in clamshell mode, and attaching the screen after boot.
My only guess is that there is some incompatibility between snow leopard and the mini displayport to vga adaptor. Is anyone else having this issue? I called AppleCare and they of course blamed it on the monitor, but it works fine in several other computers (as long as the adaptor doesn't have to be used).I have the same issue.
I'm using MacBook White (Mid 2007) and external Samsung SyncMaster 205BW (at least I've been using…). My external display is connected via DVI and MiniDVI to DVI adapter.
The symptoms are the same.
Maybe you are looking for
-
How can I tell what version of Appletv I have?
I am having dificulity getting my AppleTV to work wiht my IPad 2.
-
How to extract CRM Install Base's serial # to BW?
Hello Gurus, I'm working on CRM services area. Now the questions is I have a requirement to extract Install Base's equipment serial number to BW. In a service order I can get Component number. With that component number I can go to IB53 tcode and
-
Using Powershell to change a Windows Service logon account name and password
Hi I have been sreaching the web on this and found a lot of advice none of which works. I want to write a scipt that will change service passwords. this is what I have $svc = get-wmiobject win32_service -filter "name='AdobeARMservice'" $svc.change
-
How to create multiple screen through FXML sccene builder then create thier
Hello guys I am loking for a way to create multiple screen through FXML sccene builder then create thier controls and navigate though them. Thank you at advance. Edited by: EJP on 6/06/2012 04:17:got rid of the SHOUTING. Don't do that here.
-
I just uninstall mackeeper from my mac, but i don't know if i have to do more stuff after it???
hey, I am very new on computers stuff and i thought mackeeper was safe, so I installed a free version first and before i buy it, my boyfriend did some research and we read i should have not installed it, it is not safe, i uninstalled it but i do not