PS CC Intel IGP hd4600
I want to use PS CC With intel i5, with Intel® HD Graphics 4600 IGP, can I use the videocard specific features with this? Like I using a dedicated GPU, just slower of course.
Sorry, no solution to the problem, but a confirmation. I do have the same problem (Intuos Pro and Pen & Touch) showing the problem with ACR 8.5 and Photoshop (2014, CC and 6, these were updated with ACR 8.5) . No such problem before ACR 8.5 and no problem with LR 5.5 (also containing ACR 8.5).
I hope there will be a solution from Adobe soon, since sems to be caused by the ACR update.
Windows 8.1 in my case and latest Wacom Intuos driver installed.
Thomas
Similar Messages
-
Intel Graphics HD4600, Windows 8.1 x64, Driver: 3379 - problem with GPU clock
My notebook is Lenovo B5400.
In my notebook I have Core i3 4000m with HD4600.
When i run gpu benchmark gpu clock goes to 1100MHz (it's fine), but if my system is in IDLE, gpu clock is 600MHz (it should be 400MHz).
I tested it with driers 3345 too and problem was the same.
How to fix this?
Log from GPU-Z, i was waiting to my system hibernation (screen is off after 5 minutes): http://wklej.to/Tol36
After I bought the notebook I run Bios Update Utility, may its the problem, but on Lenovo site there is only one version of BIOS (1.02-1.04) - I have this version now!!
How to repair this??
I have balanced power plan turned on, but tried witth power saving too!halo?
now have Windows 7 x64 with latest Intel gpu drivers from lenovo drivers site and situation is identical.
(I see thinkpad power manager says that gpu is on 150% (400*1,5=600), so it isnt gpu-z problem) -
System freeze after resume from suspend to RAM
Hi,
since quite a while (probably ever) I am unable to suspend my computer to RAM because everytime it freezes a few seconds after resuming, never to become alive again until a reboot. After some investigation, I managed to get kernel logs by taking a picture of my screen. The logs were not written to disk, hence I didn't see anything before. I had to write these by hand, I hope I didn't insert any mistakes:
kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2
kernel: sas: trying to find task 0xfff880008b5b680
kernel: sas: sas_scsi_find_task: aborting task 0xfff880008b5b680
kernel: sas: sas_scsi_find_task: task 0xfff880008b5b680 is aborted
kernel: sas: sas_eh_handle_sas_errors: task 0xfff880008b5b680 is aborted
kernel: sas: trying to find task 0xffff8804606ccb40
kernel: sas: sas_scsi_find_task: aborting task 0xffff8804606ccb40
kernel: sas: sas_scsi_find_task: task 0xffff8804606ccb40 is aborted
kernel: sas: sas_eh_handle_sas_errors: task 0xffff8804606ccb40 is aborted
kernel: sas: ata7: end_device-0:0: cmd error handler
kernel: sas: ata8: end_device-0:1: cmd error handler
kernel: sas: ata7: end_device-0:0: dev error handler
kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: ata7.00: failed command: READ VERIFY SECTOR(S)
kernel: ata7.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
res 40/00:48:a0:79:88/00:00:07:00:00/40 Emask 0x4 (timeout)
kernel: ata7.00: status { DRDY }
kernel: ata7: hard resetting link
kernel: sas: ata8: end_device-0:1: dev error handler
kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: ata8.00: failed command: READ VERIFY SECTOR(S)
kernel: ata8.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
kernel: ata8.00: status { DRDY }
kernel: ata8: hard resetting link
This issue seems to be related to disk failures like bad sectors but I am quite sure, that my SSDs are in a good shape. I ran some SMART tests, they all turned out to be okay. Suspending from my dual-booted Windows works fine as well (although if the bad sector would be on the linux partition, it would probably not affect Windows).
Here's my setup:
$ lsblk -St
NAME HCTL TYPE VENDOR MODEL REV TRAN NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
sda 1:0:0:0 disk ATA Corsair Force 3 2 sata sda 0 512 0 512 512 0 cfq 128 128 0B
sdb 7:0:0:0 disk ST1000DM 003-9YN162 NDP3 usb sdb 0 512 0 512 512 1 cfq 128 128 0B
sdc 0:0:0:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdc 0 512 0 512 512 0 cfq 128 128 0B
sdd 0:0:1:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdd 0 512 0 512 512 0 cfq 128 128 0B
sr0 2:0:0:0 rom TSSTcorp CDDVDW SH-222AL SB00 sata sr0 0 512 0 512 512 1 cfq 128 128 0B
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs Recovery 567437B974379B27
├─sda2 vfat DC2D-099E /boot
├─sda3
├─sda4 ntfs FEBED982BED933BD
├─sda5 ext4 arch 41bad924-84a2-4e0a-9cd4-4ea723a2a5a3 /
└─sda6 swap 793fb3c1-8bec-4023-a7c3-ee94eee2e67a [SWAP]
sdb
└─sdb1 ntfs HDDRIVE2GO 2212E50812E4E231
sdc
└─sdc1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
└─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
sdd
└─sdd1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
└─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
I am not sure which one of the disks causes the freeze but I assume it's the revodrive because the logs talk about two drives. The Revodrive internally holds two drives, which are set up to operate in a RAID 0. Windows is installed on the Corsair drive, and has no access to the Revodrive. However, I used to run Windows on the Revodrive a few years ago, and it worked just fine.
Another interesting thing is that when I try to test suspend to RAM, the system does not freeze, nor produce errors. This only happens if none is written to /sys/power/pm_test (which means no automated wake-up, no testing).
Any ideas on how I could narrow down this issue? Thanks a lot!
EDIT
I just checked and confirmed that this issue is originating from the OCZ Revodrive:
$ dmesg | grep ata7.00 | head
[ 7.136432] ata7.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
[ 7.136436] ata7.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.146442] ata7.00: configured for UDMA/133
$ dmesg | grep ata8.00 | head
[ 7.310018] ata8.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
[ 7.310023] ata8.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.320022] ata8.00: configured for UDMA/133
Last edited by tuttiarch (2015-01-31 15:54:29)Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once... -
System freeze after resume from suspend
I am running arch for about 5 month now and I always had freezes after resuming from suspend (to ram - systemctl suspend) every once in a while (like once a week or less). The freezes increased massively over the last month or so and for about 2 weeks now it happens 95% of the times I resume from suspend.
The monitor turns on and shows things exactly how I left them, but is completely unresponsible EXCEPT for I can switch to another TTY (Ctrl+Shift+F*), however I cannot type or do anything in it...
It doesnt have anything to do with the X server as it also happens after I suspend from TTY (without any X running).
I also checked journalctl -b -1 (shows previous boot, since I always have to hard-reset the system) but it doesnt show anything after:
Mar 13 17:16:54 Ununhaswellium systemd-sleep[3624]: Suspending system...
(the suspend event before resuming)
Are there any log files that could give a hint on what exactly goes on after the resume?
Im running the latest official 3.13.6-1 kernel and updated my BIOS to the latest beta version yesterday - didnt help either...
Ive read pretty much every thread on the internet by now about freezes after resume from suspend but none really helped
Last edited by CharlieBra7o (2014-03-15 09:58:51)Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once... -
GT70 Barebone - Strange issue after upgarde to GTX980M
Hi
I just upgraded my Laptop (Medion Erazer X7825) with a GTX980M. Amazing card - fast - silent - a dream.
Unfortunately I'm having a real strange issue with that machine now:
Booting with a external screen connected to HDMI crashes the Intel HD4600 driver and the fan starts to spin real fast. I checked CPU and GPU temps but they seem perfectly ok (about 50 degree celsius). In addition the backlight of the laptop screen is lit but it is not detectable or usable.
Booting without external screen and everything is fine. If I connect it after boot the machine switches the main display to the external screen and the laptop screen is not lit any more. Everything fine so far.
Once I activate the Laptop Screen as second screen however the fan goes crazy again after a few minutes. The only good thing is - I could in theorie use both screens that way.
If the fan spins up it does so suddenly and violently and without any obvious reason: CPU and GPU temps are really low and no 3D app is running.
Medion is selling the same machine (same chassis, still GT70 based so I assume same hardware) with a gtx980m pre installed. However Medion is not providing any firmware updates for the Erazer series.
I think this is an issue that is most probably related to bios and/or vbios and could be fixed. I just need to get in touch with someone who has access to the right ressources and know how.
If someone could help me with requiring either the bios and vbios of an Medion Erazer X7835 - OR with a matching MSI GT70 Bios and a better GTX980M MSI bios than I have that would be a great help. Last step would be to advise me a little on how to flash because the medion bios is crippled - i CAN'T disable secure boot unfortunately.
Any other help or advise with the issue would also be highly apprectiated.
My GT70 Bios reads:
1763EM71 and E1763IM7.50B
My GTX980M vBios reads:
84.04.22.00.0A
UPDATE 2014-12-21:
I also just found out that the way I connect the external monitor does also make a difference: If I connect via VGA cable the intel HD driver is not crashing even when I connect before boot. And the fan is keeping it's silence - at least as far as I can tell right now.Quote from: chc on 25-December-14, 17:42:17
Really weird symptom.....But why you think that Intel Graphic driver crashed?! Have you seen other failure besides fan went nuts?
Yes. The device manager showed an error with the HD 4600 iGP. And the intel HD control panel did not show up. Furthermore the internal display was not detected/unusuable.
So this is where I stand right now:
With the help of a very kind soul here I updated my Bios and EC to a very recent Medion version.
The intel driver is not crashing any more with the monitor connected using HDMI at boot.
However the fan/EC is still going into panic mode after a random time.
With the new bios/ec firmware I can run 3d benchmarks for hours as long as I do NOT connect the external screen. The intel driver seems also to be not crashing any more. As soon as I do connect an internal monitor after some time - fan in panic mode and does not calm down again.
All temperature readings I can see a perfectly fine (CPU, HD4600 GPU and 980m GPU).
I'm really desperate right now. I THINK it is somehow connected to optimus and an issue with intel igp + gtx980m.
I would like to try another vBios if I could just get a hold of it.
Right now it's reading "84.04.22.00.0A (P04 B-oard)" (exactly this - including the P04 B-oard).
If someone is able to share a newer/different MSI vBios or has the clevo bios the card had originally (which I lost) please post a link or PM me.
I'm about to give up :( -
Multiseat with Lightdm broken after updating Mesa
Hi,
I've been using a multiseat configuration for months now, and it was working almost perfectly (almost - multiseating is far from being really stable yet IMHO, but anyway).
I updated mesa-libgl a few days ago and confirmed packages replacement, but right after rebooting my second seat didn't work anymore. The display stays black and no login screen shows up, although I suppose a signal is still sent as the monitor doesn't go into sleep mode. The first seat on the other side is working as usual, no difference noted.
In the processes, I can only see one Xorg instance (used by the first seat), when I'm supposed to have tow instances, one for each seat and with different parameters. It's like the second seat is crashing, but I can see no trace of such crash in the logs (kernel.log or everything.log). Even the Xorg.1.log contains all the informations as if the display was running fine.
The day after updating Mesa, I also updated Lightdm but it didn't change anything (I had a brief hope for a moment).
My configuration is the following :
- Nvidia GTX 760: used on seat0 as dual-head with Nouveau driver (Layout-Main in Xorg)
- Intel GMA: used on seat1 on single-head with Intel driver (Layout-Aux in Xorg)
I'm using Lightdm with this configuration:
[LightDM]
minimum-vt=1
run-directory=/run/lightdm
[SeatDefaults]
greeter-session=lightdm-gtk-greeter
greeter-show-manual-login=true
session-wrapper=/etc/lightdm/Xsession
greeter-setup-script=/usr/bin/numlockx on
[Seat:0]
xserver-command=/usr/bin/X :0 -sharevts
xserver-layout=Layout-Main
[Seat:1]
xserver-command=/usr/bin/X :1 -sharevts -novtswitch
xserver-layout=Layout-Aux
The Xorg configuration for the seats is divided into two files:
/etc/X11/xorg.conf.d/50-serverlayout-main.conf
Section "ServerLayout"
Identifier "Layout-Main"
Screen "Screen-Main" 0 0
InputDevice "Logitech-Illuminated" "CoreKeyboard"
InputDevice "Logitech-G100S" "CorePointer"
Option "AllowEmptyInput" "true"
EndSection
Section "InputDevice"
Identifier "Logitech-G100S"
Driver "evdev"
Option "Protocol" "auto"
Option "Device" "/dev/input/by-id/usb-Logitech_G100s_Optical_Gaming_Mouse-event-mouse"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
Option "GrabDevice" "on" # prevent send event to other X-servers
EndSection
Section "InputDevice"
Identifier "Logitech-Illuminated"
Driver "evdev"
Option "XkbLayout" "fr"
Option "XkbModel" "pc104"
Option "Device" "/dev/input/by-id/usb-Logitech_Logitech_Illuminated_Keyboard-event-kbd"
Option "GrabDevice" "on" # prevent send event to other X-servers
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Samsung"
ModelName "Samsung SyncMaster 2433"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 60.0
Option "DPMS"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Samsung"
ModelName "Samsung SyncMaster 2333sw"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 60.0
Option "DPMS"
EndSection
Section "Device"
Identifier "NVIDIA-GTX760"
Driver "nouveau"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 760"
EndSection
Section "Screen"
Identifier "Screen-Main"
Device "NVIDIA-GTX760"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
/etc/X11/xorg.conf.d/51-serverlayout-aux.conf
Section "ServerLayout"
Identifier "Layout-Aux"
Screen "Screen-Aux" 0 0
InputDevice "K400r-keyboard" "CoreKeyboard"
InputDevice "K400r-keyboard-multimedia" "SendCoreEvents"
InputDevice "K400r-mouse" "CorePointer"
Option "AllowEmptyInput" "true"
EndSection
Section "InputDevice"
Identifier "K400r-mouse"
Driver "evdev"
Option "Protocol" "auto"
Option "Device" "/dev/input/by-id/usb-Logitech_USB_Receiver-if02-mouse"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
Option "GrabDevice" "on" # prevent send event to other X-servers
EndSection
Section "InputDevice"
Identifier "K400r-keyboard"
Driver "evdev"
Option "XkbLayout" "fr"
Option "XkbModel" "pc104"
Option "Device" "/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse"
Option "GrabDevice" "on" # prevent send event to other X-servers
EndSection
Section "InputDevice"
Identifier "K400r-keyboard-multimedia"
Driver "evdev"
Option "Device" "/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse"
Option "XkbModel" "evdev"
Option "GrabDevice" "on"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Compaq"
ModelName "Compaq Q2159"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 60.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Intel-I915"
Driver "intel"
VendorName "Intel"
BoardName "Intel IGP"
BusID "PCI:0:2:0"
# Option "NoAccel" "True"
# Option "DRI" "False"
# Option "TearFree" "true"
# Option "AccelMethod" "sna"
EndSection
Section "Screen"
Identifier "Screen-Aux"
Device "Intel-I915"
Monitor "Monitor1"
DefaultDepth 24
EndSection
When I disable the primary seat configuration in Xorg files (I just prevent the file from being loaded), and after I restart Lightm via
# systemctl restart lightdm
the display shows up correctly on the secondary seat (and not on the primary, which is logical so far). So in the end it seems I just cannot have both seat running at the same time, but individually they work fine.
My logical assumption is that the recent upgrade of the Mesa packages somehow broke this configuration, but I cannot find why and how.
FYI, here's what I tried:
- play with Intel drivers options in Xorg (NoAccel, DRI, ...)
- play with Xorg options on the command line of each seat (-sharevts, -novtswitch)
- switch to Nvidia proprietary drivers (but here also, only the primary seat works, but that may be for a totally different reason, which is why I used Nouveau ever since I set up this configuration)
Here are the Xorg log files:
Xorg.0.log
X.Org X Server 1.16.1
Release Date: 2014-09-21
[ 6.853] X Protocol Version 11, Revision 0
[ 6.853] Build Operating System: Linux 3.16.1-1-ARCH x86_64
[ 6.853] Current Operating System: Linux leto 3.16.3-1-ARCH #1 SMP PREEMPT Wed Sep 17 21:54:13 CEST 2014 x86_64
[ 6.854] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=83e16b30-5b35-4b15-9bce-5ec87c00d46d rw quiet
[ 6.854] Build Date: 21 September 2014 10:53:13AM
[ 6.854]
[ 6.854] Current version of pixman: 0.32.6
[ 6.854] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 6.854] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 6.854] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 3 23:21:15 2014
[ 6.855] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 6.855] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 6.857] (==) ServerLayout "Layout-Main"
[ 6.857] (**) |-->Screen "Screen-Main" (0)
[ 6.857] (**) | |-->Monitor "Monitor0"
[ 6.857] (**) | |-->Device "NVIDIA-GTX760"
[ 6.857] (**) |-->Input Device "Logitech-Illuminated"
[ 6.857] (**) |-->Input Device "Logitech-G100S"
[ 6.857] (==) Automatically adding devices
[ 6.857] (==) Automatically enabling devices
[ 6.857] (==) Automatically adding GPU devices
[ 6.858] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 6.858] Entry deleted from font path.
[ 6.859] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 6.860] Entry deleted from font path.
[ 6.860] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 6.860] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 6.860] Entry deleted from font path.
[ 6.860] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 6.860] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 6.860] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 6.860] (II) Loader magic: 0x818d80
[ 6.860] (II) Module ABI versions:
[ 6.860] X.Org ANSI C Emulation: 0.4
[ 6.860] X.Org Video Driver: 18.0
[ 6.860] X.Org XInput driver : 21.0
[ 6.860] X.Org Server Extension : 8.0
[ 6.861] (EE) systemd-logind: failed to get session: PID 656 does not belong to any known session
[ 6.861] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 6.861] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 6.862] (--) PCI: (0:0:2:0) 8086:0412:1458:d000 rev 6, Mem @ 0xdb400000/4194304, 0xc0000000/268435456, I/O @ 0x0000f000/64
[ 6.862] (--) PCI:*(0:1:0:0) 10de:1187:1462:2848 rev 161, Mem @ 0xda000000/16777216, 0xd0000000/134217728, 0xd8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 6.862] (II) Open ACPI successful (/var/run/acpid.socket)
[ 6.862] (II) LoadModule: "glx"
[ 6.863] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 6.873] (II) Module glx: vendor="X.Org Foundation"
[ 6.873] compiled for 1.16.1, module version = 1.0.0
[ 6.873] ABI class: X.Org Server Extension, version 8.0
[ 6.873] (==) AIGLX enabled
[ 6.873] (II) LoadModule: "nouveau"
[ 6.874] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 6.875] (II) Module nouveau: vendor="X.Org Foundation"
[ 6.875] compiled for 1.16.1, module version = 1.0.11
[ 6.875] Module class: X.Org Video Driver
[ 6.875] ABI class: X.Org Video Driver, version 18.0
[ 6.875] (II) LoadModule: "evdev"
[ 6.875] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 6.877] (II) Module evdev: vendor="X.Org Foundation"
[ 6.877] compiled for 1.16.0, module version = 2.9.0
[ 6.877] Module class: X.Org XInput Driver
[ 6.877] ABI class: X.Org XInput driver, version 21.0
[ 6.877] (II) NOUVEAU driver
[ 6.877] (II) NOUVEAU driver for NVIDIA chipset families :
[ 6.877] RIVA TNT (NV04)
[ 6.877] RIVA TNT2 (NV05)
[ 6.877] GeForce 256 (NV10)
[ 6.877] GeForce 2 (NV11, NV15)
[ 6.877] GeForce 4MX (NV17, NV18)
[ 6.877] GeForce 3 (NV20)
[ 6.877] GeForce 4Ti (NV25, NV28)
[ 6.878] GeForce FX (NV3x)
[ 6.878] GeForce 6 (NV4x)
[ 6.878] GeForce 7 (G7x)
[ 6.878] GeForce 8 (G8x)
[ 6.878] GeForce GTX 200 (NVA0)
[ 6.878] GeForce GTX 400 (NVC0)
[ 6.878] (++) using VT number 1
[ 6.878] (II) [drm] nouveau interface version: 1.1.2
[ 6.878] (II) Loading sub module "dri2"
[ 6.878] (II) LoadModule: "dri2"
[ 6.878] (II) Module "dri2" already built-in
[ 6.878] (--) NOUVEAU(0): Chipset: "NVIDIA NVE4"
[ 6.878] (**) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 6.878] (==) NOUVEAU(0): RGB weight 888
[ 6.878] (==) NOUVEAU(0): Default visual is TrueColor
[ 6.878] (==) NOUVEAU(0): Using HW cursor
[ 6.878] (==) NOUVEAU(0): GLX sync to VBlank enabled.
[ 6.878] (==) NOUVEAU(0): Page flipping enabled
[ 6.878] (==) NOUVEAU(0): Swap limit set to 1 [Max allowed 2]
[ 6.878] (==) NOUVEAU(0): Page flipping synced to vblank by kernel.
[ 6.878] (II) NOUVEAU(0): Initializing outputs ...
[ 6.935] (II) NOUVEAU(0): Output DVI-I-1 using monitor section Monitor0
[ 6.965] (II) NOUVEAU(0): Output DVI-D-1 has no monitor section
[ 6.967] (II) NOUVEAU(0): Output HDMI-1 has no monitor section
[ 7.073] (II) NOUVEAU(0): Output DP-1 has no monitor section
[ 7.073] (II) NOUVEAU(0): 4 crtcs needed for screen.
[ 7.076] (II) NOUVEAU(0): Allocated crtc nr. 0 to this screen.
[ 7.076] (II) NOUVEAU(0): Allocated crtc nr. 1 to this screen.
[ 7.076] (II) NOUVEAU(0): Allocated crtc nr. 2 to this screen.
[ 7.076] (II) NOUVEAU(0): Allocated crtc nr. 3 to this screen.
[ 7.134] (II) NOUVEAU(0): EDID for output DVI-I-1
[ 7.134] (II) NOUVEAU(0): Manufacturer: SAM Model: 5c8 Serial#: 1129132596
[ 7.134] (II) NOUVEAU(0): Year: 2009 Week: 46
[ 7.134] (II) NOUVEAU(0): EDID Version: 1.3
[ 7.134] (II) NOUVEAU(0): Digital Display Input
[ 7.134] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 52 vert.: 29
[ 7.134] (II) NOUVEAU(0): Gamma: 2.20
[ 7.134] (II) NOUVEAU(0): DPMS capabilities: Off
[ 7.134] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 7.134] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 7.134] (II) NOUVEAU(0): redX: 0.647 redY: 0.334 greenX: 0.284 greenY: 0.607
[ 7.134] (II) NOUVEAU(0): blueX: 0.151 blueY: 0.071 whiteX: 0.312 whiteY: 0.329
[ 7.134] (II) NOUVEAU(0): Supported established timings:
[ 7.134] (II) NOUVEAU(0): 640x480@60Hz
[ 7.134] (II) NOUVEAU(0): 800x600@56Hz
[ 7.134] (II) NOUVEAU(0): 800x600@60Hz
[ 7.134] (II) NOUVEAU(0): 1024x768@60Hz
[ 7.134] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 7.134] (II) NOUVEAU(0): Supported standard timings:
[ 7.134] (II) NOUVEAU(0): #0: hsize: 1280 vsize 800 refresh: 60 vid: 129
[ 7.134] (II) NOUVEAU(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 7.134] (II) NOUVEAU(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 7.134] (II) NOUVEAU(0): #3: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 7.134] (II) NOUVEAU(0): #4: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
[ 7.134] (II) NOUVEAU(0): #5: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 7.134] (II) NOUVEAU(0): Supported detailed timing:
[ 7.134] (II) NOUVEAU(0): clock: 148.5 MHz Image Size: 521 x 293 mm
[ 7.134] (II) NOUVEAU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 7.134] (II) NOUVEAU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 7.134] (II) NOUVEAU(0): Ranges: V min: 56 V max: 60 Hz, H min: 30 H max: 81 kHz, PixClock max 175 MHz
[ 7.134] (II) NOUVEAU(0): Monitor name: SyncMaster
[ 7.134] (II) NOUVEAU(0): Serial No: H9XSB06266
[ 7.134] (II) NOUVEAU(0): Supported detailed timing:
[ 7.134] (II) NOUVEAU(0): clock: 148.5 MHz Image Size: 521 x 293 mm
[ 7.134] (II) NOUVEAU(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
[ 7.134] (II) NOUVEAU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 7.134] (II) NOUVEAU(0): Supported detailed timing:
[ 7.134] (II) NOUVEAU(0): clock: 74.2 MHz Image Size: 521 x 293 mm
[ 7.134] (II) NOUVEAU(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
[ 7.134] (II) NOUVEAU(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 7.134] (II) NOUVEAU(0): Supported detailed timing:
[ 7.134] (II) NOUVEAU(0): clock: 74.2 MHz Image Size: 521 x 293 mm
[ 7.134] (II) NOUVEAU(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
[ 7.134] (II) NOUVEAU(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 7.134] (II) NOUVEAU(0): Supported detailed timing:
[ 7.134] (II) NOUVEAU(0): clock: 27.0 MHz Image Size: 521 x 293 mm
[ 7.134] (II) NOUVEAU(0): h_active: 720 h_sync: 732 h_sync_end 796 h_blank_end 864 h_border: 0
[ 7.134] (II) NOUVEAU(0): v_active: 576 v_sync: 581 v_sync_end 586 v_blanking: 625 v_border: 0
[ 7.134] (II) NOUVEAU(0): Supported detailed timing:
[ 7.134] (II) NOUVEAU(0): clock: 27.0 MHz Image Size: 521 x 293 mm
[ 7.134] (II) NOUVEAU(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
[ 7.134] (II) NOUVEAU(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
[ 7.134] (II) NOUVEAU(0): Number of EDID sections to follow: 1
[ 7.134] (II) NOUVEAU(0): EDID (in hex):
[ 7.134] (II) NOUVEAU(0): 00ffffffffffff004c2dc80534324d43
[ 7.134] (II) NOUVEAU(0): 2e13010380341d782aeed1a555489b26
[ 7.134] (II) NOUVEAU(0): 1250542308008100814081809500a940
[ 7.134] (II) NOUVEAU(0): b30001010101023a801871382d40582c
[ 7.134] (II) NOUVEAU(0): 450009252100001e000000fd00383c1e
[ 7.134] (II) NOUVEAU(0): 5111000a202020202020000000fc0053
[ 7.134] (II) NOUVEAU(0): 796e634d61737465720a2020000000ff
[ 7.134] (II) NOUVEAU(0): 00483958534230363236360a20200111
[ 7.134] (II) NOUVEAU(0): 02010400023a80d072382d40102c4580
[ 7.134] (II) NOUVEAU(0): 09252100001e011d007251d01e206e28
[ 7.134] (II) NOUVEAU(0): 550009252100001e011d00bc52d01e20
[ 7.134] (II) NOUVEAU(0): b828554009252100001e8c0ad0902040
[ 7.134] (II) NOUVEAU(0): 31200c4055000925210000188c0ad08a
[ 7.134] (II) NOUVEAU(0): 20e02d10103e96000925210000180000
[ 7.134] (II) NOUVEAU(0): 00000000000000000000000000000000
[ 7.134] (II) NOUVEAU(0): 0000000000000000000000000000005e
[ 7.134] (II) NOUVEAU(0): Not using mode "1920x1080" (vrefresh out of range)
[ 7.134] (II) NOUVEAU(0): Not using mode "1280x720" (vrefresh out of range)
[ 7.134] (II) NOUVEAU(0): Not using mode "720x576" (vrefresh out of range)
[ 7.134] (II) NOUVEAU(0): Printing probed modes for output DVI-I-1
[ 7.134] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 7.134] (II) NOUVEAU(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 7.134] (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 7.164] (II) NOUVEAU(0): EDID for output DVI-D-1
[ 7.164] (II) NOUVEAU(0): Manufacturer: SAM Model: 4de Serial#: 1129132595
[ 7.164] (II) NOUVEAU(0): Year: 2009 Week: 6
[ 7.164] (II) NOUVEAU(0): EDID Version: 1.3
[ 7.164] (II) NOUVEAU(0): Digital Display Input
[ 7.164] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 51 vert.: 29
[ 7.164] (II) NOUVEAU(0): Gamma: 2.20
[ 7.164] (II) NOUVEAU(0): DPMS capabilities: Off
[ 7.164] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 7.164] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 7.164] (II) NOUVEAU(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
[ 7.164] (II) NOUVEAU(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
[ 7.164] (II) NOUVEAU(0): Supported established timings:
[ 7.164] (II) NOUVEAU(0): 640x480@60Hz
[ 7.164] (II) NOUVEAU(0): 800x600@56Hz
[ 7.164] (II) NOUVEAU(0): 800x600@60Hz
[ 7.164] (II) NOUVEAU(0): 1024x768@60Hz
[ 7.164] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 7.164] (II) NOUVEAU(0): Supported standard timings:
[ 7.164] (II) NOUVEAU(0): #0: hsize: 1280 vsize 800 refresh: 60 vid: 129
[ 7.164] (II) NOUVEAU(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 7.164] (II) NOUVEAU(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 7.164] (II) NOUVEAU(0): #3: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 7.164] (II) NOUVEAU(0): #4: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 7.164] (II) NOUVEAU(0): #5: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
[ 7.164] (II) NOUVEAU(0): Supported detailed timing:
[ 7.164] (II) NOUVEAU(0): clock: 138.5 MHz Image Size: 477 x 268 mm
[ 7.164] (II) NOUVEAU(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
[ 7.164] (II) NOUVEAU(0): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1111 v_border: 0
[ 7.164] (II) NOUVEAU(0): Ranges: V min: 56 V max: 61 Hz, H min: 30 H max: 75 kHz, PixClock max 175 MHz
[ 7.164] (II) NOUVEAU(0): Monitor name: SyncMaster
[ 7.164] (II) NOUVEAU(0): Serial No: H9XS201897
[ 7.164] (II) NOUVEAU(0): EDID (in hex):
[ 7.164] (II) NOUVEAU(0): 00ffffffffffff004c2dde0433324d43
[ 7.164] (II) NOUVEAU(0): 0613010380331d782aee91a3544c9926
[ 7.164] (II) NOUVEAU(0): 0f50542308008100814081809500b300
[ 7.164] (II) NOUVEAU(0): a940010101011a3680a070381f403020
[ 7.164] (II) NOUVEAU(0): 3500dd0c1100001a000000fd00383d1e
[ 7.164] (II) NOUVEAU(0): 4b11000a202020202020000000fc0053
[ 7.164] (II) NOUVEAU(0): 796e634d61737465720a2020000000ff
[ 7.164] (II) NOUVEAU(0): 00483958533230313839370a2020008b
[ 7.164] (II) NOUVEAU(0): Printing probed modes for output DVI-D-1
[ 7.164] (II) NOUVEAU(0): Modeline "1920x1080"x59.9 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
[ 7.164] (II) NOUVEAU(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 7.164] (II) NOUVEAU(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 7.164] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 7.164] (II) NOUVEAU(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 7.164] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 7.164] (II) NOUVEAU(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 7.164] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 7.164] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 7.164] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 7.164] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 7.166] (II) NOUVEAU(0): EDID for output HDMI-1
[ 7.270] (II) NOUVEAU(0): EDID for output DP-1
[ 7.270] (II) NOUVEAU(0): Output DVI-I-1 connected
[ 7.270] (II) NOUVEAU(0): Output DVI-D-1 connected
[ 7.270] (II) NOUVEAU(0): Output HDMI-1 disconnected
[ 7.270] (II) NOUVEAU(0): Output DP-1 disconnected
[ 7.270] (II) NOUVEAU(0): Using exact sizes for initial modes
[ 7.270] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1920x1080
[ 7.270] (II) NOUVEAU(0): Output DVI-D-1 using initial mode 1920x1080
[ 7.270] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 7.270] (--) NOUVEAU(0): Virtual size is 1920x1080 (pitch 0)
[ 7.270] (**) NOUVEAU(0): Driver mode "1920x1080": 138.5 MHz (scaled from 0.0 MHz), 66.6 kHz, 59.9 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "1920x1080"x59.9 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
[ 7.270] (**) NOUVEAU(0): Driver mode "1600x1200": 162.0 MHz (scaled from 0.0 MHz), 75.0 kHz, 60.0 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 7.270] (**) NOUVEAU(0): Driver mode "1680x1050": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 59.9 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 7.270] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 7.270] (**) NOUVEAU(0): Driver mode "1440x900": 88.8 MHz (scaled from 0.0 MHz), 55.5 kHz, 59.9 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 7.270] (**) NOUVEAU(0): Driver mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 7.270] (**) NOUVEAU(0): Driver mode "1280x800": 71.0 MHz (scaled from 0.0 MHz), 49.3 kHz, 59.9 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 7.270] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 7.270] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 7.270] (**) NOUVEAU(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 7.270] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[ 7.270] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 7.270] (==) NOUVEAU(0): DPI set to (96, 96)
[ 7.270] (II) Loading sub module "fb"
[ 7.270] (II) LoadModule: "fb"
[ 7.270] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 7.272] (II) Module fb: vendor="X.Org Foundation"
[ 7.272] compiled for 1.16.1, module version = 1.0.0
[ 7.272] ABI class: X.Org ANSI C Emulation, version 0.4
[ 7.272] (II) Loading sub module "shadowfb"
[ 7.272] (II) LoadModule: "shadowfb"
[ 7.272] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 7.272] (II) Module shadowfb: vendor="X.Org Foundation"
[ 7.272] compiled for 1.16.1, module version = 1.0.0
[ 7.272] ABI class: X.Org ANSI C Emulation, version 0.4
[ 7.272] (--) Depth 24 pixmap format is 32 bpp
[ 7.278] (II) NOUVEAU(0): Channel setup complete.
[ 7.279] (II) NOUVEAU(0): [COPY] async initialised.
[ 7.280] (II) NOUVEAU(0): [DRI2] Setup complete
[ 7.280] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 7.280] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 7.281] (II) Loading sub module "exa"
[ 7.281] (II) LoadModule: "exa"
[ 7.281] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 7.281] (II) Module exa: vendor="X.Org Foundation"
[ 7.281] compiled for 1.16.1, module version = 2.6.0
[ 7.281] ABI class: X.Org Video Driver, version 18.0
[ 7.281] (II) EXA(0): Driver allocated offscreen pixmaps
[ 7.281] (II) EXA(0): Driver registered support for the following operations:
[ 7.281] (II) Solid
[ 7.281] (II) Copy
[ 7.281] (II) Composite (RENDER acceleration)
[ 7.281] (II) UploadToScreen
[ 7.281] (II) DownloadFromScreen
[ 7.281] (==) NOUVEAU(0): Backing store enabled
[ 7.281] (==) NOUVEAU(0): Silken mouse enabled
[ 7.282] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
[ 7.282] (II) NOUVEAU(0): [XvMC] Extension initialized.
[ 7.282] (**) NOUVEAU(0): DPMS enabled
[ 7.282] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 7.282] (--) RandR disabled
[ 7.363] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 7.363] (II) AIGLX: enabled GLX_ARB_create_context
[ 7.363] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 7.363] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 7.363] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 7.363] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 7.363] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 7.363] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 7.363] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 7.363] (II) AIGLX: Loaded and initialized nouveau
[ 7.363] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 7.365] (II) NOUVEAU(0): NVEnterVT is called.
[ 7.420] (II) NOUVEAU(0): Setting screen physical size to 508 x 285
[ 7.420] resize called 1920 1080
[ 7.445] (II) Using input driver 'evdev' for 'Logitech-Illuminated'
[ 7.445] (**) Option "CoreKeyboard"
[ 7.445] (**) Logitech-Illuminated: always reports core events
[ 7.445] (**) evdev: Logitech-Illuminated: Device: "/dev/input/by-id/usb-Logitech_Logitech_Illuminated_Keyboard-event-kbd"
[ 7.503] (--) evdev: Logitech-Illuminated: Vendor 0x46d Product 0xc318
[ 7.503] (--) evdev: Logitech-Illuminated: Found keys
[ 7.503] (II) evdev: Logitech-Illuminated: Configuring as keyboard
[ 7.503] (II) XINPUT: Adding extended input device "Logitech-Illuminated" (type: KEYBOARD, id 6)
[ 7.503] (**) Option "xkb_rules" "evdev"
[ 7.503] (**) Option "xkb_model" "pc104"
[ 7.503] (**) Option "xkb_layout" "fr"
[ 7.513] (II) Using input driver 'evdev' for 'Logitech-G100S'
[ 7.513] (**) Option "CorePointer"
[ 7.513] (**) Logitech-G100S: always reports core events
[ 7.513] (**) evdev: Logitech-G100S: Device: "/dev/input/by-id/usb-Logitech_G100s_Optical_Gaming_Mouse-event-mouse"
[ 7.583] (--) evdev: Logitech-G100S: Vendor 0x46d Product 0xc247
[ 7.583] (--) evdev: Logitech-G100S: Found 12 mouse buttons
[ 7.583] (--) evdev: Logitech-G100S: Found scroll wheel(s)
[ 7.583] (--) evdev: Logitech-G100S: Found relative axes
[ 7.583] (--) evdev: Logitech-G100S: Found x and y relative axes
[ 7.583] (II) evdev: Logitech-G100S: Configuring as mouse
[ 7.583] (II) evdev: Logitech-G100S: Adding scrollwheel support
[ 7.583] (**) Option "Emulate3Buttons" "no"
[ 7.583] (**) evdev: Logitech-G100S: YAxisMapping: buttons 4 and 5
[ 7.583] (**) evdev: Logitech-G100S: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 7.583] (II) XINPUT: Adding extended input device "Logitech-G100S" (type: MOUSE, id 7)
[ 7.583] (II) evdev: Logitech-G100S: initialized for relative axes.
[ 7.583] (**) Logitech-G100S: (accel) keeping acceleration scheme 1
[ 7.583] (**) Logitech-G100S: (accel) acceleration profile 0
[ 7.583] (**) Logitech-G100S: (accel) acceleration factor: 2.000
[ 7.583] (**) Logitech-G100S: (accel) acceleration threshold: 4
[ 7.584] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 7.584] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 7.584] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 7.584] (**) Power Button: Applying InputClass "system-keyboard"
[ 7.584] (II) Using input driver 'evdev' for 'Power Button'
[ 7.584] (**) Power Button: always reports core events
[ 7.584] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 7.584] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 7.584] (--) evdev: Power Button: Found keys
[ 7.584] (II) evdev: Power Button: Configuring as keyboard
[ 7.584] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event1"
[ 7.584] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 7.584] (**) Option "xkb_rules" "evdev"
[ 7.584] (**) Option "xkb_model" "pc104"
[ 7.584] (**) Option "xkb_layout" "fr"
[ 7.584] (II) config/udev: Adding input device Video Bus (/dev/input/event11)
[ 7.584] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 7.584] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 7.584] (**) Video Bus: Applying InputClass "system-keyboard"
[ 7.584] (II) Using input driver 'evdev' for 'Video Bus'
[ 7.584] (**) Video Bus: always reports core events
[ 7.584] (**) evdev: Video Bus: Device: "/dev/input/event11"
[ 7.584] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 7.584] (--) evdev: Video Bus: Found keys
[ 7.584] (II) evdev: Video Bus: Configuring as keyboard
[ 7.584] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input14/event11"
[ 7.584] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 9)
[ 7.584] (**) Option "xkb_rules" "evdev"
[ 7.584] (**) Option "xkb_model" "pc104"
[ 7.584] (**) Option "xkb_layout" "fr"
[ 7.584] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 7.584] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 7.584] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 7.584] (**) Power Button: Applying InputClass "system-keyboard"
[ 7.584] (II) Using input driver 'evdev' for 'Power Button'
[ 7.584] (**) Power Button: always reports core events
[ 7.584] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 7.584] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 7.584] (--) evdev: Power Button: Found keys
[ 7.584] (II) evdev: Power Button: Configuring as keyboard
[ 7.584] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event0"
[ 7.584] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 10)
[ 7.584] (**) Option "xkb_rules" "evdev"
[ 7.584] (**) Option "xkb_model" "pc104"
[ 7.584] (**) Option "xkb_layout" "fr"
[ 7.585] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event15)
[ 7.585] (II) No input driver specified, ignoring this device.
[ 7.585] (II) This device may have been added with another device file.
[ 7.585] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event16)
[ 7.585] (II) No input driver specified, ignoring this device.
[ 7.585] (II) This device may have been added with another device file.
[ 7.585] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event17)
[ 7.585] (II) No input driver specified, ignoring this device.
[ 7.585] (II) This device may have been added with another device file.
[ 7.585] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event18)
[ 7.585] (II) No input driver specified, ignoring this device.
[ 7.585] (II) This device may have been added with another device file.
[ 7.585] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=3 (/dev/input/event12)
[ 7.585] (II) No input driver specified, ignoring this device.
[ 7.585] (II) This device may have been added with another device file.
[ 7.585] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=7 (/dev/input/event13)
[ 7.585] (II) No input driver specified, ignoring this device.
[ 7.585] (II) This device may have been added with another device file.
[ 7.585] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=8 (/dev/input/event14)
[ 7.585] (II) No input driver specified, ignoring this device.
[ 7.585] (II) This device may have been added with another device file.
[ 7.585] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4024 (/dev/input/event23)
[ 7.585] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "evdev pointer catchall"
[ 7.585] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "evdev keyboard catchall"
[ 7.585] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "evdev pointer catchall"
[ 7.585] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "evdev keyboard catchall"
[ 7.585] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "system-keyboard"
[ 7.585] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:4024'
[ 7.585] (**) Logitech Unifying Device. Wireless PID:4024: always reports core events
[ 7.585] (**) evdev: Logitech Unifying Device. Wireless PID:4024: Device: "/dev/input/event23"
[ 7.585] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Vendor 0x46d Product 0xc52b
[ 7.586] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Found 20 mouse buttons
[ 7.586] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Found scroll wheel(s)
[ 7.586] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Found relative axes
[ 7.586] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Found x and y relative axes
[ 7.586] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Found absolute axes
[ 7.586] (II) evdev: Logitech Unifying Device. Wireless PID:4024: Forcing absolute x/y axes to exist.
[ 7.586] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Found keys
[ 7.586] (II) evdev: Logitech Unifying Device. Wireless PID:4024: Configuring as mouse
[ 7.586] (II) evdev: Logitech Unifying Device. Wireless PID:4024: Configuring as keyboard
[ 7.586] (II) evdev: Logitech Unifying Device. Wireless PID:4024: Adding scrollwheel support
[ 7.586] (**) evdev: Logitech Unifying Device. Wireless PID:4024: YAxisMapping: buttons 4 and 5
[ 7.586] (**) evdev: Logitech Unifying Device. Wireless PID:4024: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 7.586] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.1/1-11.1:1.2/0003:046D:C52B.0006/0003:046D:C52B.0008/input/input26/event23"
[ 7.586] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:4024" (type: KEYBOARD, id 11)
[ 7.586] (**) Option "xkb_rules" "evdev"
[ 7.586] (**) Option "xkb_model" "pc104"
[ 7.586] (**) Option "xkb_layout" "fr"
[ 7.586] (II) evdev: Logitech Unifying Device. Wireless PID:4024: initialized for relative axes.
[ 7.586] (WW) evdev: Logitech Unifying Device. Wireless PID:4024: ignoring absolute axes.
[ 7.586] (**) Logitech Unifying Device. Wireless PID:4024: (accel) keeping acceleration scheme 1
[ 7.586] (**) Logitech Unifying Device. Wireless PID:4024: (accel) acceleration profile 0
[ 7.586] (**) Logitech Unifying Device. Wireless PID:4024: (accel) acceleration factor: 2.000
[ 7.586] (**) Logitech Unifying Device. Wireless PID:4024: (accel) acceleration threshold: 4
[ 7.586] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4024 (/dev/input/mouse1)
[ 7.586] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "system-keyboard"
[ 7.586] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:4024'
[ 7.586] (**) Logitech Unifying Device. Wireless PID:4024: always reports core events
[ 7.586] (**) evdev: Logitech Unifying Device. Wireless PID:4024: Device: "/dev/input/mouse1"
[ 7.586] (EE) evdev: Logitech Unifying Device. Wireless PID:4024: Unable to query fd: Inappropriate ioctl for device
[ 7.630] (EE) PreInit returned 2 for "Logitech Unifying Device. Wireless PID:4024"
[ 7.630] (II) UnloadModule: "evdev"
[ 7.630] (II) config/udev: Adding input device HD Webcam C525 (/dev/input/event25)
[ 7.630] (**) HD Webcam C525: Applying InputClass "evdev keyboard catchall"
[ 7.630] (**) HD Webcam C525: Applying InputClass "evdev keyboard catchall"
[ 7.630] (**) HD Webcam C525: Applying InputClass "system-keyboard"
[ 7.630] (II) Using input driver 'evdev' for 'HD Webcam C525'
[ 7.630] (**) HD Webcam C525: always reports core events
[ 7.630] (**) evdev: HD Webcam C525: Device: "/dev/input/event25"
[ 7.630] (--) evdev: HD Webcam C525: Vendor 0x46d Product 0x826
[ 7.630] (--) evdev: HD Webcam C525: Found keys
[ 7.630] (II) evdev: HD Webcam C525: Configuring as keyboard
[ 7.630] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-11/1-11.2/1-11.2.1/1-11.2.1:1.2/input/input28/event25"
[ 7.630] (II) XINPUT: Adding extended input device "HD Webcam C525" (type: KEYBOARD, id 12)
[ 7.630] (**) Option "xkb_rules" "evdev"
[ 7.630] (**) Option "xkb_model" "pc104"
[ 7.630] (**) Option "xkb_layout" "fr"
[ 7.630] (II) config/udev: Adding input device Microsoft X-Box 360 pad (/dev/input/event24)
[ 7.630] (II) No input driver specified, ignoring this device.
[ 7.630] (II) This device may have been added with another device file.
[ 7.630] (II) config/udev: Adding input device Microsoft X-Box 360 pad (/dev/input/js1)
[ 7.630] (II) No input driver specified, ignoring this device.
[ 7.630] (II) This device may have been added with another device file.
[ 7.630] (II) config/udev: Adding input device Logitech Logitech(R) Precision(TM) Gamepad (/dev/input/event22)
[ 7.630] (II) No input driver specified, ignoring this device.
[ 7.630] (II) This device may have been added with another device file.
[ 7.630] (II) config/udev: Adding input device Logitech Logitech(R) Precision(TM) Gamepad (/dev/input/js0)
[ 7.630] (II) No input driver specified, ignoring this device.
[ 7.630] (II) This device may have been added with another device file.
[ 7.631] (II) config/udev: Adding input device Logitech Logitech Illuminated Keyboard (/dev/input/event19)
[ 7.631] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "evdev keyboard catchall"
[ 7.631] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "evdev keyboard catchall"
[ 7.631] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "system-keyboard"
[ 7.631] (II) Using input driver 'evdev' for 'Logitech Logitech Illuminated Keyboard'
[ 7.631] (**) Logitech Logitech Illuminated Keyboard: always reports core events
[ 7.631] (**) evdev: Logitech Logitech Illuminated Keyboard: Device: "/dev/input/event19"
[ 7.631] (WW) evdev: Logitech Logitech Illuminated Keyboard: device file is duplicate. Ignoring.
[ 7.663] (EE) PreInit returned 8 for "Logitech Logitech Illuminated Keyboard"
[ 7.663] (II) UnloadModule: "evdev"
[ 7.663] (II) config/udev: Adding input device Logitech Logitech Illuminated Keyboard (/dev/input/event20)
[ 7.663] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "evdev keyboard catchall"
[ 7.663] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "evdev keyboard catchall"
[ 7.663] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "system-keyboard"
[ 7.663] (II) Using input driver 'evdev' for 'Logitech Logitech Illuminated Keyboard'
[ 7.663] (**) Logitech Logitech Illuminated Keyboard: always reports core events
[ 7.663] (**) evdev: Logitech Logitech Illuminated Keyboard: Device: "/dev/input/event20"
[ 7.663] (--) evdev: Logitech Logitech Illuminated Keyboard: Vendor 0x46d Product 0xc318
[ 7.663] (--) evdev: Logitech Logitech Illuminated Keyboard: Found 1 mouse buttons
[ 7.663] (--) evdev: Logitech Logitech Illuminated Keyboard: Found scroll wheel(s)
[ 7.663] (--) evdev: Logitech Logitech Illuminated Keyboard: Found relative axes
[ 7.663] (II) evdev: Logitech Logitech Illuminated Keyboard: Forcing relative x/y axes to exist.
[ 7.663] (--) evdev: Logitech Logitech Illuminated Keyboard: Found absolute axes
[ 7.663] (II) evdev: Logitech Logitech Illuminated Keyboard: Forcing absolute x/y axes to exist.
[ 7.663] (--) evdev: Logitech Logitech Illuminated Keyboard: Found keys
[ 7.663] (II) evdev: Logitech Logitech Illuminated Keyboard: Configuring as mouse
[ 7.663] (II) evdev: Logitech Logitech Illuminated Keyboard: Configuring as keyboard
[ 7.663] (II) evdev: Logitech Logitech Illuminated Keyboard: Adding scrollwheel support
[ 7.663] (**) evdev: Logitech Logitech Illuminated Keyboard: YAxisMapping: buttons 4 and 5
[ 7.663] (**) evdev: Logitech Logitech Illuminated Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 7.663] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.1/0003:046D:C318.0002/input/input23/event20"
[ 7.663] (II) XINPUT: Adding extended input device "Logitech Logitech Illuminated Keyboard" (type: KEYBOARD, id 13)
[ 7.663] (**) Option "xkb_rules" "evdev"
[ 7.663] (**) Option "xkb_model" "pc104"
[ 7.663] (**) Option "xkb_layout" "fr"
[ 7.663] (II) evdev: Logitech Logitech Illuminated Keyboard: initialized for relative axes.
[ 7.663] (WW) evdev: Logitech Logitech Illuminated Keyboard: ignoring absolute axes.
[ 7.663] (**) Logitech Logitech Illuminated Keyboard: (accel) keeping acceleration scheme 1
[ 7.663] (**) Logitech Logitech Illuminated Keyboard: (accel) acceleration profile 0
[ 7.663] (**) Logitech Logitech Illuminated Keyboard: (accel) acceleration factor: 2.000
[ 7.663] (**) Logitech Logitech Illuminated Keyboard: (accel) acceleration threshold: 4
[ 7.663] (II) config/udev: Adding input device Logitech G100s Optical Gaming Mouse (/dev/input/event21)
[ 7.663] (**) Logitech G100s Optical Gaming Mouse: Applying InputClass "evdev pointer catchall"
[ 7.663] (**) Logitech G100s Optical Gaming Mouse: Applying InputClass "evdev pointer catchall"
[ 7.664] (II) Using input driver 'evdev' for 'Logitech G100s Optical Gaming Mouse'
[ 7.664] (**) Logitech G100s Optical Gaming Mouse: always reports core events
[ 7.664] (**) evdev: Logitech G100s Optical Gaming Mouse: Device: "/dev/input/event21"
[ 7.664] (WW) evdev: Logitech G100s Optical Gaming Mouse: device file is duplicate. Ignoring.
[ 7.690] (EE) PreInit returned 8 for "Logitech G100s Optical Gaming Mouse"
[ 7.690] (II) UnloadModule: "evdev"
[ 7.690] (II) config/udev: Adding input device Logitech G100s Optical Gaming Mouse (/dev/input/mouse0)
[ 7.690] (II) No input driver specified, ignoring this device.
[ 7.690] (II) This device may have been added with another device file.
[ 7.690] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event3)
[ 7.690] (II) No input driver specified, ignoring this device.
[ 7.690] (II) This device may have been added with another device file.
[ 7.690] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event7)
[ 7.690] (II) No input driver specified, ignoring this device.
[ 7.690] (II) This device may have been added with another device file.
[ 7.690] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event8)
[ 7.690] (II) No input driver specified, ignoring this device.
[ 7.690] (II) This device may have been added with another device file.
[ 7.690] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event9)
[ 7.690] (II) No input driver specified, ignoring this device.
[ 7.690] (II) This device may have been added with another device file.
[ 7.690] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event10)
[ 7.690] (II) No input driver specified, ignoring this device.
[ 7.690] (II) This device may have been added with another device file.
[ 7.690] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event4)
[ 7.690] (II) No input driver specified, ignoring this device.
[ 7.690] (II) This device may have been added with another device file.
[ 7.690] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event5)
[ 7.690] (II) No input driver specified, ignoring this device.
[ 7.690] (II) This device may have been added with another device file.
[ 7.690] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event6)
[ 7.690] (II) No input driver specified, ignoring this device.
[ 7.690] (II) This device may have been added with another device file.
[ 7.691] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 7.691] (II) No input driver specified, ignoring this device.
[ 7.691] (II) This device may have been added with another device file.
[ 14.821] (II) NOUVEAU(0): EDID vendor "SAM", prod id 1246
[ 14.821] (II) NOUVEAU(0): Using hsync ranges from config file
[ 14.821] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 14.821] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 14.821] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
[ 14.821] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 14.821] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 14.821] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 14.821] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 14.821] (II) NOUVEAU(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 14.821] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 14.821] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 14.821] (II) NOUVEAU(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 14.821] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 14.821] (II) NOUVEAU(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 14.963] resize called 3840 1080
[ 15.466] (II) NOUVEAU(0): EDID vendor "SAM", prod id 1246
[ 15.466] (II) NOUVEAU(0): Using hsync ranges from config file
[ 15.466] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 15.466] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 15.466] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
[ 15.466] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 15.466] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 15.466] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 15.466] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 15.466] (II) NOUVEAU(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 15.466] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 15.466] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 15.466] (II) NOUVEAU(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 15.466] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 15.466] (II) NOUVEAU(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 15.747] (II) NOUVEAU(0): EDID vendor "SAM", prod id 1246
[ 15.747] (II) NOUVEAU(0): Using hsync ranges from config file
[ 15.747] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 15.747] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 15.747] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
[ 15.747] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 15.747] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 15.747] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 15.747] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 15.747] (II) NOUVEAU(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 15.747] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 15.747] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 15.747] (II) NOUVEAU(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 15.747] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 15.747] (II) NOUVEAU(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 15.947] (II) NOUVEAU(0): EDID vendor "SAM", prod id 1246
[ 15.947] (II) NOUVEAU(0): Using hsync ranges from config file
[ 15.947] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 15.947] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 15.947] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
[ 15.947] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 15.947] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 15.947] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 15.947] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 15.947] (II) NOUVEAU(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 15.947] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 15.947] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 15.947] (II) NOUVEAU(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 15.947] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 15.947] (II) NOUVEAU(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 16.180] (II) NOUVEAU(0): EDID vendor "SAM", prod id 1246
[ 16.180] (II) NOUVEAU(0): Using hsync ranges from config file
[ 16.180] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 16.180] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16.180] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
[ 16.180] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 16.180] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 16.180] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 16.180] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 16.180] (II) NOUVEAU(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 16.180] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 16.180] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 16.180] (II) NOUVEAU(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 16.180] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 16.180] (II) NOUVEAU(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 16.398] (II) NOUVEAU(0): EDID vendor "SAM", prod id 1246
[ 16.398] (II) NOUVEAU(0): Using hsync ranges from config file
[ 16.398] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 16.398] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16.398] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
[ 16.398] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 16.398] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 16.398] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 16.398] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 16.398] (II) NOUVEAU(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 16.398] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 16.398] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 16.398] (II) NOUVEAU(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 16.398] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 16.398] (II) NOUVEAU(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 16.705] (II) NOUVEAU(0): EDID vendor "SAM", prod id 1246
[ 16.705] (II) NOUVEAU(0): Using hsync ranges from config file
[ 16.705] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 16.705] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16.705] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
[ 16.705] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 16.705] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 16.705] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 16.705] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 16.705] (II) NOUVEAU(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
[ 16.705] (II) NOUVEAU(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 16.705] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 16.705] (II) NOUVEAU(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 16.705] (II) NOUVEAU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 16.705] (II) NOUVEAU(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 3613.510] (II) config/udev: removing device Logitech Unifying Device. Wireless PID:4024
[ 3613.557] (II) evdev: Logitech Unifying Device. Wireless PID:4024: Close
[ 3613.557] (II) UnloadModule: "evdev"
[ 3613.617] (II) config/udev: removing device HD Webcam C525
[ 3613.647] (II) evdev: HD Webcam C525: Close
[ 3613.647] (II) UnloadModule: "evdev"
[ 3614.988] (II) config/udev: Adding input device Logitech Logitech(R) Precision(TM) Gamepad (/dev/input/js0)
[ 3614.988] (II) No input driver specified, ignoring this device.
[ 3614.988] (II) This device may have been added with another device file.
[ 3614.988] (II) config/udev: Adding input device Logitech Logitech(R) Precision(TM) Gamepad (/dev/input/event23)
[ 3614.988] (II) No input driver specified, ignoring this device.
[ 3614.988] (II) This device may have been added with another device file.
[ 3614.989] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4024 (/dev/input/mouse1)
[ 3614.989] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "system-keyboard"
[ 3614.989] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:4024'
[ 3614.989] (**) Logitech Unifying Device. Wireless PID:4024: always reports core events
[ 3614.989] (**) evdev: Logitech Unifying Device. Wireless PID:4024: Device: "/dev/input/mouse1"
[ 3614.989] (EE) evdev: Logitech Unifying Device. Wireless PID:4024: Unable to query fd: Inappropriate ioctl for device
[ 3615.023] (EE) PreInit returned 2 for "Logitech Unifying Device. Wireless PID:4024"
[ 3615.023] (II) UnloadModule: "evdev"
[ 3615.023] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4024 (/dev/input/event22)
[ 3615.023] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "evdev pointer catchall"
[ 3615.023] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "evdev keyboard catchall"
[ 3615.023] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "evdev pointer catchall"
[ 3615.023] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "evdev keyboard catchall"
[ 3615.023] (**) Logitech Unifying Device. Wireless PID:4024: Applying InputClass "system-keyboard"
[ 3615.023] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:4024'
[ 3615.023] (**) Logitech Unifying Device. Wireless PID:4024: always reports core events
[ 3615.023] (**) evdev: Logitech Unifying Device. Wireless PID:4024: Device: "/dev/input/event22"
[ 3615.023] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Vendor 0x46d Product 0xc52b
[ 3615.023] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Found 20 mouse buttons
[ 3615.023] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Found scroll wheel(s)
[ 3615.023] (--) evdev: Logitech Unifying Device. Wireless PID:4024: Found relative axes
[ 3615.02shillshocked wrote:Since version 1.12, LightDM now relies on systemd-logind for seat
management. It means LightDM van load seats automatically as they are added
from logind.
Ha! I searched something like that during my investigations, I was wondering if it wasn't about the recent logind changes, but I gave up due to the lack of documentation -
HP, I need you to support your Hardware!!
Two weeks ago I bought a HP Pavilion dm3 1104tx at Harvey Norman (Sydney,Au) link to HN.
The offical Product specification DOES NOT specify it has Hybrid Graphics (do not confuse with nvidia optimus) but it does (nvidia g 105m + intel igp) (ref: see advanced details) and I NEED TO DISABLE Hybrid Graphics (I wouldn't have bought it if I knew it had hybrid graphics).
specs: Link (HP) (or in Advanced Details)
Why do I need to disable Hybrid Graphics?
Infew words: I cant install the nvidia Verde drivers (the official ones) unless I disable the integrated graphics (iGPU).
Keep hybrid graphics on implies that I wouldnt be able to use the new CUDA features nor the 3D vision that comes with the new drivers, I wouldn't get driver bug fixes, no FLASH GPU ACCELERATION no newer features and I wouldnt be able to use the nvidia GPU on linux (I know I know, HP does not support linux on this product, this is like a "side effect"), among many other things.
Also the intel igp is really bad, i get tearing all the time, has awful performance and I DIDN'T EVEN PAY TO HAVE IT (AND THEY NEVER SPECIFIED I'D GET THAT) --- I DONT WANT IT---
So i'd be happy by using only the nvidia dGPU (the g 105m one the specs).
For references please read the Advanced Details.
NOW, THE LOGIC THING TO DO IS ASK HP TO FIX THIS, since I bought the computer ~2 weeks ago (I cant return it anymore), BUT tech support was, as always, NOT helpful at all (they dont know anything at all).
Again, all I want to do is disable the intel iGPU, And HP CANT expect me to solve this by myself, and not fixing this means they dont support their own hardware.
HOW CAN I CONTACT SOMEONE AT HP THAT IS ABLE TO DEAL WITH ADVANCED SUPPORT PROBLEMS??????
HP, IF YOU ARE READING I WANT YOU TO UPDATE THE INSYDEH20 BIOS OF THE DM3-1104TX, I NEED TO SHUT DOWN THE iGPU THAT I DIDNT PAY FOR, NEITHER WAS IN THE OFFICIAL SPECS.
I cant even believe hp has products like this... Im very satisfied with my HP Mini 311, please do not let me down!!.
I want to use my dm3!!
E. Arturo
Apologies if this is too "confusing" English is not my first language.
---------------------------ADVANCED DETAILS------SKIP-IF-YOU-DON'T-WANT-TO-READ-TECHNICAL-INFO--------------------------
Specs Link (HP):
The specs in Harvey Norman are the same.
The command 'lspci | grep VGA' on linux outputs:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
01:00.0 VGA compatible controller: nVidia Corporation G98M [GeForce G105M] (rev a2)
That confirms that the dm3-1104tx *has* hybrid graphics, and it is enabled.
HP nvidia drivers are obsolete (2009, keep in mind nvidia releases drivers ~2 times a month (this affects me as no bug fixes and/or new features are provided))
ref: Drivers (HP)
the official nvidia drivers can't be installed "Notebooks supporting Hybrid Power technology with Intel chipsets are not supported by this release."
ref:Drivers (nVidia) (under supported products)
nvidia claims HP is responsible for the support of this card, ref: nVidia forums (means no drivers unless HP releases new drivers (its been two years since they updated their drivers!!) or updates bios to let me shut down IGP)
This happens if I try to install the nvidia Driver, THIS IS THE MOST IMPORTANT THING, IF I KNEW THIS COMPUTER HAD HYBRID GRAPHICS I WOULDNT HAVE BOUGHT IT, AS I NEED THE NEW NVIDIA DRIVERS AS SOON AS THEY ARE RELEASED (AGAING, THE SPECS NEVER SPECIFY THE FACT THAT THIS COMPUTER HAS HYBRID GRAPHICS).
Nvidia stopped support for hybrid power (means no new drivers) "Support for Hybrid Power, a Hybrid SLI technology, is discontinued and not available with this driver"
ref: Nvidia no longer supports hybrid power
There is a "modded" driver to use the optimus driver on the hybrid hardware (but im not going to use it as is too buggy and does not work properly)
ref:unofficial hybrid drivers
The insyde bios has an advanced hidden menu in which the iGPU can be turned off
HP support doesn't even know the existence of this menu. And this menu is of curse not visible by default in the setup utility.
example of unlocked BIOS (this is my 311 not my dm3, if this was my dm3 I wouldn't be here):
This is my Hp 311. Advanced -> Video Configuration (theren you can shut down the iGPU")
in my hp mini 311 i can access the advanced menu by pressing "A" immediately after "F10" at start up (but it doesnt work on my dm3)
ref: "F10" + "A" = Advanced Menu
Also in this forum they modded the HP 311 bios to display the Advanced menu by default: HP Mini Bios Hack
the nvidia drivers can be installed if the integrated graphics are disabled.
quote from the nvidia driver: "notebook and all-in-one desktop designs with switchable (hybrid) or Optimus graphics will not work if means to disable the integrated graphics in hardware are not available." (linux driver, under additional information) (means that if I disable the iGPU i can use the drivers)
*note although this is for the linux drivers It should also apply to the windows drivers, I'll add reference as soon as I get it.
ref: Drivers (nvidia) (see under additional info )
ive dumped the bios (InsydeH20) to a binary file and dissembled the setup utility (using marcan's python scripts on linux) and found that the advanced menu is actually there (but hidden) (but I don't know how to enable it)
marcan's blog: Marcan's Blog (he wrote the scripts to enable VT but they can be used to dissemble the setup utility)
python scripts : Insyde Hack Tools
-this the stock BIOS for the dm3 1104tx-
how to flash with a modded BIOS: Undocumented way to Flash Insyde BIOSes (also they mod bioses but they haven't been able to help me so far)
proof that the advanced menu exists on HPs: HP latops have "Advanced" menu in BIOS
also there is an "official" leaked tool from insyde called ezh20 which can be used to mod insyde bioses with a hexeditor.
Notes:
1 Im NOT trying to get support for Linux, Im just using linux as a tool
2 I do not have the leaked ezH20 tool as that might be illegal.
3 All I want is to disable the Integrated GPU
-----------------------------------------------END ADVANCED DETAILS----------------------------------------------------------------------------------That is a horse of another color. I understand and sympathize. Somebody needs to help and I will post this on another board to see if there is some inside HP support available to you. Best I can do.
-
Few questions about Lenovo G550
Hello, I plan to buy an inexpensive laptop, propably it will be a Lenovo G550L but I got few questions about this model. Here are my questions:
1. What 320GB hard disks are mounted inside G550L, Western Digital, Seagate or Hitachi (exact model if possible)?
2. How are the hinges of LCD screen in this model, cause they look pretty weak. Do they break easy, does anyone got any experience with this type of hinges which are "forward type" instead of normal?
2. I have noticed that there are two types of laptop chassis in this model one is matte black and another is grey glare. How to determine which model has which finish? Which finish got laptops with T4300, 3GB RAM, 320GB HDD, Intel IGP x4500, no card reader, no hdmi.
Thanks in advance.
Regardsmy friend samsung any net, toshiba regza link, panasonic viera link is their special TM to support CEC
but just for their product not other products,for instance a samsung dvd player and a samsung lcd can sync easily with with hdmi cable
and in this case you dont need an extra remote control to control dvd besides tv.just with having a remote you can control both of them or the other audio visual products from that campany
please think???? how could you control your lenovo when it does not have a remote?
every device need to send signals to the remote not by just some wires like HDMI
lcd has a remote and a dvd player also has a remote and if those are from a unit company,they share a common signal with HDMI cable ,then you could control both of them with just one remote.
this can ease your work,as you dont need a lot of remote around your devices
but they should be from just a unit producer cause they uses different protocols
and of course they want to sell their various products and oblige you to buy other products from that producer to have the compability for having just one remote. -
Current situation for 945GM and below users -- downgrade only option?
I'm running ArchLinux on an Acer 5610-4610(Intel 945GM, 950GMA), and I've almost(...*almost*) gotten used to seeing mesa, xorg-server, and such being on the pacman ignore notification when I update(I can't use the latest xf86-video-intel and therefore the latest dependencies an utterly handicapping reduction in performance), and this recent fiasco I've had with the transition to hotplugging makes matters even worse.
Staying with downgraded xorg-server means ignoring evdev and such upgrades, I would imagine, so my question is this: is my only option until kernel-2.6.29 is released(a month 1/2 from now?) to keep this growing number of packages downgraded to retain usability on ArchLinux?Ronin-Sage wrote:
I'm running ArchLinux on an Acer 5610-4610(Intel 945GM, 950GMA), and I've almost(...*almost*) gotten used to seeing mesa, xorg-server, and such being on the pacman ignore notification when I update(I can't use the latest xf86-video-intel and therefore the latest dependencies an utterly handicapping reduction in performance), and this recent fiasco I've had with the transition to hotplugging makes matters even worse.
Staying with downgraded xorg-server means ignoring evdev and such upgrades, I would imagine, so my question is this: is my only option until kernel-2.6.29 is released(a month 1/2 from now?) to keep this growing number of packages downgraded to retain usability on ArchLinux?
Could you elaborate on your problems? Why you can't use the latest Intel drivers? Do they have a bug that prevents you from using them? Is the bug an upstream one or Arch specific? Arch is not even using the latest, but the 2.4.x series.
And you say that staying with the old packages is utterly handicapping performance for you? You mean that if you do upgrade your packages you get much better performance but also some showstopper bug?
I have two desktops with an Intel IGP and don't have any problems. One has the latest G45 chipset and the other an old 845G one. Also a laptop with GM965 has no problems, but that one's running Ubuntu, not Arch. -
G530 Motherboard/CPU Upgrades?
Hi all,
My girlfriend has a G530 that I just had to pull apart after it took a little bit of a swim. Aside from needing a keyboard nothing was damaged, but I noticed something interesting while I had it apart: Next to the northbridge there are what appear to be solder pads for a discrete GPU and RAM for it. Thing is, I can't seem to find a single system that has a board with the same layout as the G530's that has a discrete GPU on it. Does anyone know if any other systems got this board with a GPU on it? If I can find a board with one I'd be tempted to throw it in the G530 just to say that I did.
Also, has anyone tried throwing something like a T9300 or T8300 in one of these things? The T4200 + Intel IGP + painfully slow hard drive conspire to give me an eye twitch whenever I get stuck using the darn thing and I'd kinda like to liven it up a bit.
Thanks.
W700DS: C2E QX9300 | FX3700 | 8GB | 120GB OCZ Vertex SSD + 500GB WD Caviar Blue | Digitizer + Color Calibrator
W500: C2D T9400 | FGL V5700 | 8GB | 160GB Intel X25M G2 SSD
Workstation: 2x Xeon E5410 | 18GB | HD3870 | 3x 60GB OCZ Summit SSDs (RAID 0) + 1TB Seagate 7200.11Hi
IMHO dual processor upgrades have advantages and disadvantages.
On the one hand OS X does make good use of dual processors and most apps these days seem to be multithreaded to some degree. I guess this will only improve in the future as more machines are released with dual processors and/or dual cores and more software is produced to take advantage of them. I guess the main exception is games, some of which only make use of one processor, but then if you're running more than one app at a time, you'll still be using both processors to some degree.
On the other hand, dual processor upgrades are more expensive, both processors share the same relatively slow 133MHz system bus and in general are 'only' 40% faster than a single processor running at the same speed, they generate more heat and most 7447 based upgrades are overclocked, so two overclocked processors are perhaps going to be more problematical.
I agree with PB PM in that a single 1.4GHz 7455 based upgrade (with level 3 cache) would give you the most bang for the buck. IMHO the 466MHz Digital Audio G4 is the computer likely to gain the most from a processor upgrade, as it was the slowest G4 produced to still have a 133MHz bus and x4 AGP slot etc. -
[SOLVED]T61 new panel: have to change EDID
Hi Compañeros,
I have a very special problem here and i hope, someone could help me fixing it ;-)
My Laptops (Lenovo T61 14.1'' SXGA 1400x1050 Intel IGP) Panel broke and i ordered a new one, same modelnumber.
I installed it, but the screen stays black, is just somehow "lit" but nothing to be seen.
Ok, so i changed the inverter too, still no luck.
dmesg shows the following:
[ 0.697497] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 0.749439] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 24
[ 0.749507] Raw EDID:
[ 0.749557] 00 ff ff ff ff ff ff 00 30 ae 22 40 00 00 00 00
[ 0.749623] 1a 11 01 03 80 1d 15 78 ea 6f 95 9c 54 4c 87 26
[ 0.749674] 21 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
[ 0.749725] 01 01 01 01 01 01 30 2a 78 20 51 1a 10 40 30 70
[ 0.749777] 00 ff ff ff ff ff ff 00 30 ae 22 40 00 00 00 00
[ 0.749837] 1a 11 01 03 80 1d 15 78 ea 6f 95 9c 54 4c 87 26
[ 0.749900] 21 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
[ 0.749973] 01 01 01 01 01 01 30 2a 78 20 51 1a 10 40 30 70
ok, I investigated further and found
http://forum.thinkpads.com/viewtopic.php?f=29&t=77733 and
http://www.thinkwiki.org/wiki/Installin … /T60_or_61
I had to read that there is some supercool logic that prevents panels not certified by lenovo from beeing activated. unbelievable.
*Sigh* I even managed to read the EDID of my old panel, which is:
EDID BYTES:
0x 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 | 00 FF FF FF FF FF FF 00 30 AE 22 40 00 00 00 00
10 | 00 0F 01 03 80 1D 15 78 EA 2D 05 97 57 51 8A 27
20 | 23 50 54 21 08 00 81 80 01 01 01 01 01 01 01 01
30 | 01 01 01 01 01 01 30 2A 78 20 51 1A 10 40 30 70
40 | 13 00 1E D6 10 00 00 19 25 23 78 20 51 1A 10 40
50 | 30 70 13 00 1E D6 10 00 00 19 00 00 00 0F 00 90
60 | 43 32 90 43 28 0F 01 00 4C A3 50 34 00 00 00 FE
70 | 00 4C 54 4E 31 34 31 50 34 2D 4C 30 32 0A 00 19
and although i'm just a normal user i do see differences here :-)
My question now:
How do i get this f****** vendor id into my nonglare new panel?
For Win-users there is Powerstrip, but you have to pay a lot and pm to author for unlocking the writing abillity…
But it should be possible to change these values.
How do i do this?
Any help appreciated.
Thank you
Last edited by dogo77 (2011-11-28 09:54:02)Hi again.
So, this morning i found the solution on this very fine blog:
https://blog.voodoo-arts.net/content/ed … C3%A4ndern
everything worked smothely. Maybe somtimes this will be a help for others :-)
nevertheless, thanks for reading. -
This is a make-or-break question for a workstation machine: Can the w540 output 10-bit color (adobeRGB, video, photo, rendering) over its TB port?
The silence from Lenovo and Nvidia suggests NO, despite Quadro's internal capability - possibly still gated by the Optimus/Intel IGP. (BTW: Galaxy S4 recently got an award for its adobeRGB coverage... a phone)
Internally, w540's IPS panel; externally, the Quadro over DP/TB; both are natural matches for a 10b flow - unless the Intel/IGP side of the Optimus would limit Quadro's 32b color packing out of the IGP video buffer...
But then one can not claim WS-class and ISV if true 10b rendering is impossible with Optimus!
The latter sad assumption seems to be indeed the case for Intel's HD4000 'Optimus'; see tijo's post in http://forum.notebookreview.com/dell-latitude-vostro-precision/733144-m4700-nvidia-quadro-intel-hd40...
Net: If the w540 can NOT drive my 10b monitors over DP/TB, this is a deal breaker. Hard to believe that Optimus w/ the latest Intel IGP still can't output 10b color in AD2013 - and reason to avoid Optimus/IGP, if true.
However, i hope i'm wrong and that the w540 supports 10b workflows.
MitchMore details on the W540 Thunderbolt port and the W540 display topology:
Now, as you can see there, the W540 has two display-modes, that can be changed in the BIOS: Standard and Advanced. In Standard-Mode, all dsplay connections are handled by the Intel HD 4600. In Advanced Mode, alll display connections on the Dock are handled by the Quadro K1100M / K2100M. Since all W540 versions have Optimus, the internal screen has to be 6-bit, since the HD 4600 sill can´t drive 10bit displays. But an external 10 bit monitor connected over the dock with an W540 in Advanced mode should work.
Not sure about the internal ports of the Notebook. We will see if it will work or not. -
New MBA Sandy Bridge Graphics vs. Current NVIDIA
Is anyone here familiar with the new Sandy Bridge Intel Graphics and the current MBA's NVIDIA offering? I've read that the new Intel IGP is supposed to be "on par" with the NVIDIA chip, but I'm curious if this will actually be the case, or if it's possible that Apple will have Sandy Bridge alongside a dedicated mobile video card still - or if the new MBA graphics will disappointingly lag behind in graphics.
Thanks!
.t2hHi Take,
If you ever have a chance to browse the MacBook Pro forums, you'll find that a lot of people weren't aware of Apple's design decision. What's worse... these are from people that already bought the machine. I suppose if you're an "old school" Apple person then you just assumed that the Pro line has the discrete. You figure until the introduction of the 13" MBP and Apple's brief experiment with the cheaper entry point of the 15" MBP, all of the MacBook Pros had discrete GPUs, whereas the MacBook had the shared.
Even more surprising was that the recent refresh of the 13" MacBook Pro didn't include the LCD panel found in the 13" MacBook Air with the 1440x900 resolution, it's still using the 1280x800.
Unless you're an avid gamer, the Intel HD 3000 & Nvidia 320M are perfectly adequate. I've yet to encounter a game I couldn't run, albeit, on lower settings. Regarding the update, we'll have to wait and see. But it's no secret that the recent refresh of the MacBook Air was a huge success for Apple (they're very public about that), so you'd have to assume that Apple will continue to ensure that it stays current with technology. -
"Battlefield 2" crashes on Equium A200
Can anyone tell me if bf2 runs on the Equium A200 using Vista? I am told the chip set will run it (from Intel website), and it is possible to run it using vista in administrator mode, but the game keeps crashing back to the desk top!
I have downloaded all the latest patches! HelpHi. I dont know what graphic card you have on your laptop but I guess you have a X3100 Intel IGP. In order to play this game and most of the game, you may have to turn off the HW T&L and use the SW T&L. Google "How to turn of HW mode on X3100" you will get more instruction about this. This will solve your problem.
http://forums.computers.toshiba-europe.com/forums/thread.jspa?messageID=120284
Sincerely.
Message was edited by: anhchuong
Has just found my post on the other forum. Use this if you have X3100 http://forums.computers.toshiba-europe.com/forums/thread.jspa?messageID=120284 -
[Solved] Xorg Error Dell Vostro 3700
Hi guys,
I have been using Arch for quite a few years. I just got a new laptop in the form of a Dell Vostro 3700 with a Nvidia GT 330m.
When I go to start X I get an error saying that "no screens are found". I have "nvidia" and "nvidia-utils" installed. I am thinking this
is a driver issue as Dell computers do not support drivers straight from nvidia.
Any advice would be appreciated.
Cheers
Last edited by serideth (2010-12-09 13:09:25)I will try the Nouveau driver, It has switchable graphics (which wasn't listed by Dell when I bought it) and the switching happens automatically when I plug in the AC (meaning I don't have to log out to switch like the old switchable graphics) but I am not sure whether it is Optimus (No mention by Dell that it is Optimus enabled).
Edit.
Just confirmed out that It DOES have switchable GPU's and Nvidia Optimus which you would think Dell would have advertised in giant writing on their website.
So now to setup arch with the Intel drivers.
I will let you know how it goes.
Second Edit.
Installed the xf86-video-intel drivers and its working now. Attempting to use the Nouveau or the official Nvidia drivers causes Xorg to return the previous error. This seems to be an incompatibility issue with laptops with switchable graphics and/or Nvidia Optimus. Linux can only utilize the Intel IGP, which is fine for me since I will only use my Arch install to code and leave gaming to W7 with Steam, however if you are planning on using Linux as your primary/only OS on your laptop with switchable graphics/Optimus be advised you will only be able to use the integrated graphics. A fix does not appear to be coming anytime soon either.
Thanks for everyone's help.
Cheers
Last edited by serideth (2010-12-09 13:14:26)
Maybe you are looking for
-
[APP: soa-infra] . Unable to fetch/generate encryption key.
Hello; I am installing Fusion Middleware 11.1.1.7 on a Windows 2008 R2 64 bit server that is running in Oracle VM. Components installed: Oracle SE database Enterprise RCU WLS - 10.3.6 OSB SOA BAM Web Center. I am not sure why I am getiting this messa
-
Design options for interfacing RFC as Receiver
hello guys , Need some ideas in developing a scenario for interfacing RFC as receiver from a stored procedure call on DB side , what would be best and easy way to interface this RFC? Best regards Krishna
-
What is role of a functional consultant in ADP applications integration?
please explain this to me. what an SAP functional does with we are integrating other modules with ADP for payroll. Regards, Jess.
-
Storage clause : Maximum size of extent
What is the Maximum size of single extent in 10.2.0.4.0 ? is it same for smallfile and bigfile ?
-
I have upgraded from 10.8 to 10.10.I have two 30" monitors which I use.
I spread out my mixer screen on both displays. When I try to use both screens the display will only show part of the screen and the remaining mixer screen fades on the other display. How can I fix this. Is this a new function for Yosemite? I tried