Fuzzy Display on my G4

I am fortunate that my sister gave me her G4 FW800
I use it for a musical recording program called ProTools.
I got ProTools last year as well as OS X(10.4.10) updated and all.
My Sony display is fuzzy now and has been going between fuzzy and normal since I either loaded OS X or ProTools.
I was browsing my computer and I believe the video card is:
ATI Radeon 9000 Pro
Resolution is 1024x768
Does anyone know of problems with OS X as far as display? Thanks

Generally means the monitor is toast. They don't last forever. Many monitors can be serviced. There are many adjustments inside them to tweak. But Monitors are cheap anyway.

Similar Messages

Fuzzy Display - PC Won't Boot

Hi there,
I have a friend who was using her PC (a Pavilion a1000 running XP3) when it suddenly gave the BSoD. She hard re-booted, now it gives a fuzzy display and won't boot past the HP logo screen. I can't get into the BIOS setup, or safe mode. It won't get beyond the logo. There are no error codes or beeps. Just freezes at the logo with the fuzzy display.
Before I do anything else, does this sound like something obvious to anyone? Any input is appreciated. And if more information is needed, just let me know and I'll gladly supply. Thank you in advance.
This question was solved.
View Solution.

GTifeld, welcome to the forum.
Without the full model number I can't be specific. However, from the models in that series it appears that the computer is 8 years old.
My first thought when I see these symptoms with older computers is a failing/failed power supply unit (PSU). Here is a guide to help you troubleshoot the PSU.
If it appears to be okay, then, check to assure that the memory is seated properly. Over time the memory can shift. Also, it could have failed, as well. While you are at it, check all of the other components and clean inside of the case.
Please click "Accept as Solution" if your problem is solved.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

Premiere CS4 - Export is Fuzzy, Display is Clear - need help

I'm on a MacBook Pro, and running Premiere Pro CS4.
I need to export a Quicktime (.mov) with h.264 at 1280 x 720.
This is a quick edit, so I'm just piecing together a .PNG photo (opening), another .mov file (the main file), and then a closing graphic (that is also .mov).
So, the main file is 1280 x 720, FPS is 23.98. The video is clear and crisp. When I import into my project, the video is also clear and perfect.
The closing graphic is similar size, but FPS is 29.97. It's a .mov file.
These are the project settings:
Editing Mode: Desktop
Timebase: 29.97 frames/second
Frame size: 1280 x 720
Square Pixels
Progressive Scan
Display format: 30 fps Dro-Frame Timecode
Video Preview: Quicktime
Codec: H.264
In my timeline and in the monitor, everything looks crisp and clean. And when I export the file, I have it set at 1280 x 720 Quicktime H.264. (Progressive Scan, 29.97) The preview looks crisp and clear. But after I export it, in the edited version, the video is fuzzy. The words on the opening slate are fuzzy.
And the end slate does not render properly. There are lines that run across it and it's very pixalated.
I'm new at Adobe Premiere. So I am a beginner at all this. If you could help me figure out what I am doing wrong, I'd be grateful.

Hmm... My CS5/AVCHD 1st Impressions http://forums.adobe.com/thread/652694?tstart=0 includes a link to what I built for CS5
Your computer is going to be a bit slower, but I don't see anything really obvious that would cause the output to be choppy
But... have you considered converting to HDV to see if that edits better for you?
Convert AVCHD to HDV http://forums.adobe.com/thread/390605?tstart=0
or use Cineform Neo Scene http://www.cineform.com/neoscene/
Added... Looking at my notes, I use a different AVCHD setting in CS5... have you tried other AVCHD project settings?

T500 fuzzy display after Fn+F7

I have switched to a T500 with Windows XP.
When I use a projector and hit Fn + F7, the projector displays the image clearly.
However the display on my T500 becomes fuzzy.
Does anyone know if this is normal?
I have tried changing the display setting, but it did not help.
My colleagues also experience same problem.
Sometimes after Fn+F7, the display on the lapto zooms in.
Any suggestion would be appreciated.
Thanks!

I believe the reason you are seeing a blurry image is because your display adapter (video card) changes the resolution of your screen in order to match the resolution of your projector. Because your LCD screen's resolution is much higher than the projector's, the screen will temporarily become blurry until you unplug the video cable. You can otherwise use a lower resolution that your LCD can handle and perhaps that might improve clarity.

Fuzzy display caused by WoW prefs!

I thought my trusty Mitsubishi monitor was going west, either that or i need glasses. Looking at text on a web page the whole thing looks slightly fuzzy / blurry.
I've found that i can make this 'go away' by running MoniTOR to check the settings. Viola nice clear monitor again.
Once i run WoW the monitor displays the blurry image again
I would delete the prefs file if i could find it and im open to any other fixes.

MoniTor lets you check and adjust almost all parameters on CRT and TFT screens.
http://www.macupdate.com/info.php/id/16655/monitor

Fuzzy display on HDM on brand new Mac Mini

I Have a brand new, purchased less than 2 -weeks ago, Mac Mini. I have a brand new Asus monitor. I am using an HDMI to HDMI cable. The text is more than fuzzy. I have tried the HDMI to DVI converter that came with the Mac Mini, as well as a two other HDMI cables and a completely different monitor. I Have also read several other posts that state that the HDMI port on the Mac Mini is has this known issue of fuzzy text. I have tried making several adjustments on the monitor with no relief. Does anyone have any insight on what else I can try? I thought it was an issue with Mountain Lion, then just the Mac mini in general, It's pretty irritating that I Just spent over $1800 and it looks like crap. Any suggestions?

I don't get it. I've had 5 different models of monitor (4 monitors, 1 1080p TV to be accurate) connected to my Mac mini (Late 2012) via HDMI, and all have looked great. I have an Acer 231SHL connected as my 2nd monitor to my Mac mini's HDMI port right now. (My primary monitor is a 27" 2560x1440 and connected via a mini DisplayPort to DisplayPort connector.) I've variously used the Acer, a Dell, an AOC, an HP, and a Vizio (26" TV). I've even used two HDMI connections at once (straight HDMI and MDP->HDMI).
I wonder what the difference is.
John

Fuzzy Display on External Monitors MAC Book Pro

Morning all,
Right, I've had my MBP for over 6 months now and I love it. Great piece of kit, and I wish I'd come across to OSX years ago. Having said that, I've come across an annoying issue with using external monitors. I have the latest MBP and the software version is 10.9.4. The issue is I have two monitors plugged into the MAC via Mini-Port to DVI to HDMI cables. The main issue is the fonts are quite fuzzy. It's not terrible, but its very frustrating. The weird thing is if I connect to my windows machine via Remote Desktop when Windows loads up its crisp and clear, yet everything behind that window on the same screen on the MAC is fuzzy. Very peculiar.
Secondly the resolution isnt the best. Especially considering what these monitors are capable of on my Windows PC.
I'm sure this must be a common issue? Hopefully there is an easy solution. I can put up with it, but considering how much I've paid for the MAC I would expect a lot better. Just so you know, I'm not tecky on the MAC at all!
Thanks in advance for any assistance!
Glassy

Russell Jones1
Before I run out and buy a Blue Ray drive, I want to know if it will work along with my internal Superdrive?
Bingo
http://eshop.macsales.com/shop/blu-ray

Fuzzy display

Hello,
I just replaced the logic and PAV board on a Snow iMac and now the screen is really fuzzy. I hooked it up to an external monitor and it was fine. Any ideas? Is the CRT hooped?

Just FYI, for future questions, please make sure you're posting in the correct iMac forum. This one is for the new Intel-powered iMac Core Duo which of course doesn't have a CRT.
Regards.

T410 VGA display issues

I am finding on our T410 systems we are getting in that the VGA output is so bad my customers are complaining. The display has colors washed out and are fuzzy. I even compared this to the previous models on the same display.
T60/T61 both looked good (analog but good)
T400 less crisp and less color
T410 color and line edge are bad.
Anyone else seeing this? We are using discrete graphic versions and it seems as if this is part was made poorly to force adoption of display port. For my company that is a ways off as we do not re-bury monitors with every new system. (Not to mention that Lenovo did not have a monitor with display port until recently)
Anyone else?

I have had fuzzy display with VGA and after numerous phone conversations with the customer support, I had my motherboard replaced last week. Guess what !!! The problem is not resolved. I still have the fuzzy display and it is really annoying.
Despite of having dock (which only supports VGA) I have to use DVI externally and I cannot use external display at work because they all have only VGA...
I always wanted Thinkpad until I bought this T410. And now I say, NEVER AGAIN...

Mini Displayport to VGA and flicker in 1600x1200

Hi all
I've got an old PC laptop that I used with my CRT monitor until I bought the unibody MBP and the adapter.
The joke : 1600x1200 is only available at 60Hz which is horrible for the eyes... whereas my 6 year old laptop can do 75Hz at 1600x1200 on the same screen.
Having this definition on the CRT would match the 1400x900 of the unibody. I can't believe it can't do such a thing. This adapter/graphics card combo truly is a bag of annoyances (fuzzy display with the 9600GT enabled, and now this, it's getting frustrating)
I've already tried SwitchRes and it doesn't work at all (it seems I can't add new display modes)

Are you in Mirrored Mode or Extended Mode? In order to get that kind of resolution, you need to be in Extended Mode by going to Display Preferences and unclicking Mirrored.

Changing screen resolution and rotation more easily?

Hi!
I frequently switch between two screen configurations of my LCD: the standard 1024x768 and 768x1024 rotated in portrait mode. The switching process is somewhat tedious:
open sys preferences,
select 90° rotation -> Mac OS switches to 1024x768 rotated
(which my monitor doesn't support -> fuzzy display)
click OK to confirm new resolution
select 768x1024
click OK in dialog
click OK to confirm new resolution
I wish I could use the menu bar thing to switch resolutions, but it doesn't offer rotation. Even if I could eliminate the two-step resolution switching, it would save a lot of trouble. I've tried editing the plist file in /Library/Preferences, but my mini seems to ignore it.
Any suggestions?
thanks
Hendrik
mini G4 Mac OS X (10.4.10)

I have not found anyway to resize the incoming screen, in iChat or the Built-in Screen Sharing app.
7:08 PM Tuesday; January 26, 2010

Were are the default settings for the screen resolution

?

The default resolution for any LCD display is usually it's maximum, which is the resolution at which the display is sharpest (for lower resolutions, an LCD display as to interpolate which results in a slightly fuzzy display). The maximum resolution for the built-in LCD for all models of MacBook (not the MacBook Pro) is 1280 by 800.

How to use the iCloud password update on an iMac?

I have changed my password for iCloud and my iMac keeps telling me that i will have to reset the password through the app.com website. I have done this three times and the iMac still does not update my password. So i am thinking that i will have to reset my computer, is this a good option, if so
how do i do this?

Unfortunately Apple has not (yet) implemented a resolution independent GUI. This means that the only way to change the size of text overall is to change the resolution of the display - System Preferences > Displays. The problem with this is that LCDs have one resolution that's native. Changing the resolution of your display will make the font larger but it will tend to redult in a fuzzy display. However it is worth playing with since iMacs generally do have more than one resolution that works without fuzziness. Whether any of them will meet your needs is another story.
But as you found with Safari, it is possible to change the resolution of individual applications. While we cannot change the native resolution of the menubar and some aspects of an application, we can change some of them. For example, I have Word & Excel configured to automatically display file contents at 150%. Not all programs offer this capability but many do.

Resolution of MacBook Pro display - always this fuzzy??

I should have done my homework, but...
I'm very sensitive to the fuzziness of the MacBook Pro display (especially the nearly grey and poorly defined letters on Word) and, to tell the truth, it's making my stomach turn and giving me a headache. I just received this computer through work, can't return it, and I'm stuck with it for three years now. what can I do or purchase to make the display CRYSTAL CLEAR (as in laser print quality)?
Will an external monitor help? Which one?
How can my iPod touch look so brilliant and this $2,500 laptop so archaic?
Thanks for any and all help,
Ants

The reason your iPod Touch looks sharper is that it has a much higher pixel density than the MBP. Your iPod's screen is 163 ppi (pixels per inch) versus 110 ppi for the MBP. However, if it looks very fuzzy, I would agree with the other responder that your resolution isn't set to the screen's native resolution (1440 x 900) or that you are zoomed in (press control and scroll down on your mouse scroll wheel or two-fingered scroll on with the trackpad).

Screen display looks fuzzy using xf86-video-intel on a HP Pavilion 23

Hello,
First off I want to say, thank you for Arch! Been using some distros on and off and I think I found my /home! I made a full plunge into Linux a bit ago after some Windows 8.1 issues, switched to Arch and not looking back. Anyways, So far all my computers are either Arch or Manjaro which I am moving more towards straight arch as Manjaro does have some issues when updating your system (dependency loops). All and all not bad, just liking the full control of a pure system then building from scratch.
Ok, the issue at hand. I have removed Windows 8.1 from my HP All in One Pavilion 23 machine....what a nightmare that was.... Everything was good after turning off secure boot. I installed Arch Linux (3.14.4-1) x86_64, and I am having issues getting the xf86-video-intel driver to play nice with X.
I have taken a screenshot:
Screenshot
I notice this starts right after the choosing the Arch Linux from the boot option menu. It starts the load nice and crisp but after a second the screen flickers with some lines at the top of the screen, random colors, only about the top 3rd of the screen. This modules begin to load but the terminal text looks blocky and horrible.
I am using Openbox 3.5.2-6 with slim 1.3.6-4. Running xorg-server 1.15.1-1 and xorg-server-utils 7.6-3 with all the dependencies of course.
Output from pacman queries for video drivers
xf86-video-intel 2.99.911-2
xf86-video-vesa 2.3.2-4
lspci output
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H87 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
04:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
my /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="i915"
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
,my /etc/default/grub.conf
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
And last my /var/log/Xorg.0.log
[ 15.641]
X.Org X Server 1.15.1
Release Date: 2014-04-13
[ 15.641] X Protocol Version 11, Revision 0
[ 15.641] Build Operating System: Linux 3.14.0-4-ARCH x86_64
[ 15.641] Current Operating System: Linux localhost 3.14.4-1-ARCH #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014 x86_64
[ 15.641] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=0c1916a0-b631-478f-ac6b-aa5d123f75cd rw quiet splash
[ 15.641] Build Date: 14 April 2014 08:39:09AM
[ 15.641]
[ 15.641] Current version of pixman: 0.32.4
[ 15.641] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 15.641] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 15.641] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun 1 17:05:15 2014
[ 15.687] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 15.687] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 15.739] (==) No Layout section. Using the first Screen section.
[ 15.739] (==) No screen section available. Using defaults.
[ 15.739] (**) |-->Screen "Default Screen Section" (0)
[ 15.739] (**) | |-->Monitor "<default monitor>"
[ 15.764] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 15.764] (**) | |-->Device "Intel Graphics"
[ 15.764] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 15.764] (==) Automatically adding devices
[ 15.764] (==) Automatically enabling devices
[ 15.764] (==) Automatically adding GPU devices
[ 15.793] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 15.793] Entry deleted from font path.
[ 15.795] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 15.795] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 15.795] (**) Extension "Composite" is enabled
[ 15.795] (**) Extension "RENDER" is enabled
[ 15.795] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 15.795] (II) Loader magic: 0x804c80
[ 15.795] (II) Module ABI versions:
[ 15.795] X.Org ANSI C Emulation: 0.4
[ 15.795] X.Org Video Driver: 15.0
[ 15.795] X.Org XInput driver : 20.0
[ 15.796] X.Org Server Extension : 8.0
[ 15.796] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 15.798] (--) PCI:*(0:0:2:0) 8086:0412:103c:2b0f rev 6, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64
[ 15.798] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 15.798] Initializing built-in extension Generic Event Extension
[ 15.798] Initializing built-in extension SHAPE
[ 15.798] Initializing built-in extension MIT-SHM
[ 15.798] Initializing built-in extension XInputExtension
[ 15.798] Initializing built-in extension XTEST
[ 15.798] Initializing built-in extension BIG-REQUESTS
[ 15.798] Initializing built-in extension SYNC
[ 15.798] Initializing built-in extension XKEYBOARD
[ 15.798] Initializing built-in extension XC-MISC
[ 15.798] Initializing built-in extension SECURITY
[ 15.798] Initializing built-in extension XINERAMA
[ 15.798] Initializing built-in extension XFIXES
[ 15.798] Initializing built-in extension RENDER
[ 15.799] Initializing built-in extension RANDR
[ 15.799] Initializing built-in extension COMPOSITE
[ 15.799] Initializing built-in extension DAMAGE
[ 15.799] Initializing built-in extension MIT-SCREEN-SAVER
[ 15.799] Initializing built-in extension DOUBLE-BUFFER
[ 15.799] Initializing built-in extension RECORD
[ 15.799] Initializing built-in extension DPMS
[ 15.799] Initializing built-in extension Present
[ 15.799] Initializing built-in extension DRI3
[ 15.799] Initializing built-in extension X-Resource
[ 15.799] Initializing built-in extension XVideo
[ 15.799] Initializing built-in extension XVideo-MotionCompensation
[ 15.799] Initializing built-in extension XFree86-VidModeExtension
[ 15.799] Initializing built-in extension XFree86-DGA
[ 15.799] Initializing built-in extension XFree86-DRI
[ 15.799] Initializing built-in extension DRI2
[ 15.799] (II) "glx" will be loaded by default.
[ 15.799] (II) LoadModule: "dri2"
[ 15.799] (II) Module "dri2" already built-in
[ 15.799] (II) LoadModule: "glamoregl"
[ 15.808] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 15.917] (II) Module glamoregl: vendor="X.Org Foundation"
[ 15.917] compiled for 1.15.0, module version = 0.6.0
[ 15.917] ABI class: X.Org ANSI C Emulation, version 0.4
[ 15.917] (II) LoadModule: "glx"
[ 15.917] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 15.928] (II) Module glx: vendor="X.Org Foundation"
[ 15.929] compiled for 1.15.1, module version = 1.0.0
[ 15.929] ABI class: X.Org Server Extension, version 8.0
[ 15.929] (==) AIGLX enabled
[ 15.929] Loading extension GLX
[ 15.929] (II) LoadModule: "intel"
[ 15.929] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 15.955] (II) Module intel: vendor="X.Org Foundation"
[ 15.955] compiled for 1.15.0, module version = 2.99.911
[ 15.955] Module class: X.Org Video Driver
[ 15.955] ABI class: X.Org Video Driver, version 15.0
[ 15.955] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 15.956] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000
[ 15.956] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100
[ 15.956] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200
[ 15.956] (++) using VT number 7
[ 15.971] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4600
[ 15.971] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2
[ 15.971] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 15.971] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 15.971] (==) intel(0): RGB weight 888
[ 15.971] (==) intel(0): Default visual is TrueColor
[ 15.971] (**) intel(0): Option "AccelMethod" "sna"
[ 15.971] (**) intel(0): Option "DRI" "true"
[ 15.971] (**) intel(0): Option "TearFree" "true"
[ 15.972] (**) intel(0): Framebuffer tiled
[ 15.972] (**) intel(0): Pixmaps tiled
[ 15.972] (**) intel(0): "Tear free" enabled
[ 15.972] (**) intel(0): Forcing per-crtc-pixmaps? no
[ 15.972] (II) intel(0): Output eDP1 has no monitor section
[ 15.972] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output eDP1
[ 15.972] (II) intel(0): Output VGA1 has no monitor section
[ 15.972] (II) intel(0): Output DP1 has no monitor section
[ 15.972] (II) intel(0): Output HDMI1 has no monitor section
[ 15.972] (II) intel(0): Output DP2 has no monitor section
[ 15.972] (II) intel(0): Output HDMI2 has no monitor section
[ 15.972] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 15.972] (--) intel(0): Output eDP1 using initial mode 1920x1080 on pipe 0
[ 15.972] (==) intel(0): DPI set to (96, 96)
[ 15.972] (II) Loading sub module "dri2"
[ 15.972] (II) LoadModule: "dri2"
[ 15.972] (II) Module "dri2" already built-in
[ 15.972] (==) Depth 24 pixmap format is 32 bpp
[ 15.986] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend
[ 15.986] (==) intel(0): Backing store enabled
[ 15.986] (==) intel(0): Silken mouse enabled
[ 15.986] (II) intel(0): HW Cursor enabled
[ 15.986] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 15.987] (==) intel(0): DPMS enabled
[ 15.987] (II) intel(0): [DRI2] Setup complete
[ 15.987] (II) intel(0): [DRI2] DRI driver: i965
[ 15.987] (II) intel(0): [DRI2] VDPAU driver: i965
[ 15.987] (II) intel(0): direct rendering: DRI2 Enabled
[ 15.987] (==) intel(0): hotplug detection: "enabled"
[ 15.987] (--) RandR disabled
[ 16.067] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 16.067] (II) AIGLX: enabled GLX_ARB_create_context
[ 16.067] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 16.067] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 16.067] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 16.067] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 16.067] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 16.067] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 16.067] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 16.067] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 16.067] (II) AIGLX: Loaded and initialized i965
[ 16.067] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 16.085] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 16.107] (II) intel(0): Setting screen physical size to 508 x 285
[ 16.375] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 16.375] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 16.375] (II) LoadModule: "evdev"
[ 16.383] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 16.402] (II) Module evdev: vendor="X.Org Foundation"
[ 16.402] compiled for 1.15.1, module version = 2.9.0
[ 16.402] Module class: X.Org XInput Driver
[ 16.402] ABI class: X.Org XInput driver, version 20.0
[ 16.402] (II) Using input driver 'evdev' for 'Power Button'
[ 16.402] (**) Power Button: always reports core events
[ 16.402] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 16.402] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 16.402] (--) evdev: Power Button: Found keys
[ 16.402] (II) evdev: Power Button: Configuring as keyboard
[ 16.402] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 16.402] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 16.402] (**) Option "xkb_rules" "evdev"
[ 16.402] (**) Option "xkb_model" "pc104"
[ 16.402] (**) Option "xkb_layout" "us"
[ 16.442] (II) config/udev: Adding input device Video Bus (/dev/input/event2)
[ 16.442] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 16.442] (II) Using input driver 'evdev' for 'Video Bus'
[ 16.442] (**) Video Bus: always reports core events
[ 16.442] (**) evdev: Video Bus: Device: "/dev/input/event2"
[ 16.442] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 16.442] (--) evdev: Video Bus: Found keys
[ 16.442] (II) evdev: Video Bus: Configuring as keyboard
[ 16.442] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input2/event2"
[ 16.442] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 16.442] (**) Option "xkb_rules" "evdev"
[ 16.442] (**) Option "xkb_model" "pc104"
[ 16.442] (**) Option "xkb_layout" "us"
[ 16.443] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 16.443] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 16.443] (II) Using input driver 'evdev' for 'Power Button'
[ 16.443] (**) Power Button: always reports core events
[ 16.443] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 16.443] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 16.443] (--) evdev: Power Button: Found keys
[ 16.443] (II) evdev: Power Button: Configuring as keyboard
[ 16.443] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 16.443] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 16.443] (**) Option "xkb_rules" "evdev"
[ 16.443] (**) Option "xkb_model" "pc104"
[ 16.443] (**) Option "xkb_layout" "us"
[ 16.444] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 16.444] (II) config/udev: Adding input device HP High Definition 1MP Webcam (/dev/input/event8)
[ 16.444] (**) HP High Definition 1MP Webcam: Applying InputClass "evdev keyboard catchall"
[ 16.444] (II) Using input driver 'evdev' for 'HP High Definition 1MP Webcam'
[ 16.444] (**) HP High Definition 1MP Webcam: always reports core events
[ 16.444] (**) evdev: HP High Definition 1MP Webcam: Device: "/dev/input/event8"
[ 16.444] (--) evdev: HP High Definition 1MP Webcam: Vendor 0x4f2 Product 0xb40b
[ 16.444] (--) evdev: HP High Definition 1MP Webcam: Found keys
[ 16.444] (II) evdev: HP High Definition 1MP Webcam: Configuring as keyboard
[ 16.444] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input8/event8"
[ 16.444] (II) XINPUT: Adding extended input device "HP High Definition 1MP Webcam" (type: KEYBOARD, id 9)
[ 16.444] (**) Option "xkb_rules" "evdev"
[ 16.444] (**) Option "xkb_model" "pc104"
[ 16.445] (**) Option "xkb_layout" "us"
[ 16.445] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event14)
[ 16.445] (**) NextWindow Touchscreen: Applying InputClass "evdev touchscreen catchall"
[ 16.445] (II) Using input driver 'evdev' for 'NextWindow Touchscreen'
[ 16.445] (**) NextWindow Touchscreen: always reports core events
[ 16.445] (**) evdev: NextWindow Touchscreen: Device: "/dev/input/event14"
[ 16.445] (--) evdev: NextWindow Touchscreen: Vendor 0x1926 Product 0x33e
[ 16.445] (--) evdev: NextWindow Touchscreen: Found absolute axes
[ 16.445] (--) evdev: NextWindow Touchscreen: Found absolute multitouch axes
[ 16.445] (II) evdev: NextWindow Touchscreen: No buttons found, faking one.
[ 16.445] (--) evdev: NextWindow Touchscreen: Found x and y absolute axes
[ 16.445] (--) evdev: NextWindow Touchscreen: Found absolute touchscreen
[ 16.445] (II) evdev: NextWindow Touchscreen: Configuring as touchscreen
[ 16.445] (**) evdev: NextWindow Touchscreen: YAxisMapping: buttons 4 and 5
[ 16.445] (**) evdev: NextWindow Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 16.446] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:1926:033E.0001/input/input14/event14"
[ 16.446] (II) XINPUT: Adding extended input device "NextWindow Touchscreen" (type: TOUCHSCREEN, id 10)
[ 16.446] (II) evdev: NextWindow Touchscreen: initialized for absolute axes.
[ 16.446] (**) NextWindow Touchscreen: (accel) keeping acceleration scheme 1
[ 16.446] (**) NextWindow Touchscreen: (accel) acceleration profile 0
[ 16.446] (**) NextWindow Touchscreen: (accel) acceleration factor: 2.000
[ 16.446] (**) NextWindow Touchscreen: (accel) acceleration threshold: 4
[ 16.446] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/mouse2)
[ 16.446] (II) No input driver specified, ignoring this device.
[ 16.446] (II) This device may have been added with another device file.
[ 16.447] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event9)
[ 16.447] (II) No input driver specified, ignoring this device.
[ 16.447] (II) This device may have been added with another device file.
[ 16.447] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event10)
[ 16.447] (**) NextWindow Touchscreen: Applying InputClass "evdev pointer catchall"
[ 16.447] (II) Using input driver 'evdev' for 'NextWindow Touchscreen'
[ 16.447] (**) NextWindow Touchscreen: always reports core events
[ 16.447] (**) evdev: NextWindow Touchscreen: Device: "/dev/input/event10"
[ 16.447] (--) evdev: NextWindow Touchscreen: Vendor 0x1926 Product 0x33e
[ 16.447] (--) evdev: NextWindow Touchscreen: Found 3 mouse buttons
[ 16.447] (--) evdev: NextWindow Touchscreen: Found absolute axes
[ 16.447] (--) evdev: NextWindow Touchscreen: Found x and y absolute axes
[ 16.447] (--) evdev: NextWindow Touchscreen: Found absolute touchscreen
[ 16.447] (II) evdev: NextWindow Touchscreen: Configuring as touchscreen
[ 16.447] (**) evdev: NextWindow Touchscreen: YAxisMapping: buttons 4 and 5
[ 16.447] (**) evdev: NextWindow Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 16.448] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.2/0003:1926:033E.0003/input/input10/event10"
[ 16.448] (II) XINPUT: Adding extended input device "NextWindow Touchscreen" (type: TOUCHSCREEN, id 11)
[ 16.448] (II) evdev: NextWindow Touchscreen: initialized for absolute axes.
[ 16.448] (**) NextWindow Touchscreen: (accel) keeping acceleration scheme 1
[ 16.448] (**) NextWindow Touchscreen: (accel) acceleration profile 0
[ 16.448] (**) NextWindow Touchscreen: (accel) acceleration factor: 2.000
[ 16.448] (**) NextWindow Touchscreen: (accel) acceleration threshold: 4
[ 16.448] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/js0)
[ 16.448] (II) No input driver specified, ignoring this device.
[ 16.448] (II) This device may have been added with another device file.
[ 16.449] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/mouse0)
[ 16.449] (II) No input driver specified, ignoring this device.
[ 16.449] (II) This device may have been added with another device file.
[ 16.449] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/event11)
[ 16.449] (**) Hewlett Packard HP Wireless Keyboard Kit: Applying InputClass "evdev keyboard catchall"
[ 16.449] (II) Using input driver 'evdev' for 'Hewlett Packard HP Wireless Keyboard Kit'
[ 16.449] (**) Hewlett Packard HP Wireless Keyboard Kit: always reports core events
[ 16.449] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: Device: "/dev/input/event11"
[ 16.449] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Vendor 0x461 Product 0x4e25
[ 16.449] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found keys
[ 16.449] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as keyboard
[ 16.449] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:0461:4E25.0004/input/input11/event11"
[ 16.449] (II) XINPUT: Adding extended input device "Hewlett Packard HP Wireless Keyboard Kit" (type: KEYBOARD, id 12)
[ 16.449] (**) Option "xkb_rules" "evdev"
[ 16.449] (**) Option "xkb_model" "pc104"
[ 16.449] (**) Option "xkb_layout" "us"
[ 16.450] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/event12)
[ 16.450] (**) Hewlett Packard HP Wireless Keyboard Kit: Applying InputClass "evdev keyboard catchall"
[ 16.450] (II) Using input driver 'evdev' for 'Hewlett Packard HP Wireless Keyboard Kit'
[ 16.450] (**) Hewlett Packard HP Wireless Keyboard Kit: always reports core events
[ 16.450] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: Device: "/dev/input/event12"
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Vendor 0x461 Product 0x4e25
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found 1 mouse buttons
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found scroll wheel(s)
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found relative axes
[ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Forcing relative x/y axes to exist.
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found absolute axes
[ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Forcing absolute x/y axes to exist.
[ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found keys
[ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as mouse
[ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as keyboard
[ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Adding scrollwheel support
[ 16.450] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: YAxisMapping: buttons 4 and 5
[ 16.450] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 16.450] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.1/0003:0461:4E25.0005/input/input12/event12"
[ 16.450] (II) XINPUT: Adding extended input device "Hewlett Packard HP Wireless Keyboard Kit" (type: KEYBOARD, id 13)
[ 16.450] (**) Option "xkb_rules" "evdev"
[ 16.450] (**) Option "xkb_model" "pc104"
[ 16.450] (**) Option "xkb_layout" "us"
[ 16.451] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: initialized for relative axes.
[ 16.451] (WW) evdev: Hewlett Packard HP Wireless Keyboard Kit: ignoring absolute axes.
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) keeping acceleration scheme 1
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration profile 0
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration factor: 2.000
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration threshold: 4
[ 16.451] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/event13)
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: Applying InputClass "evdev pointer catchall"
[ 16.451] (II) Using input driver 'evdev' for 'Hewlett Packard HP Wireless Keyboard Kit'
[ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: always reports core events
[ 16.451] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: Device: "/dev/input/event13"
[ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Vendor 0x461 Product 0x4e25
[ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found 3 mouse buttons
[ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found scroll wheel(s)
[ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found relative axes
[ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found x and y relative axes
[ 16.452] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as mouse
[ 16.452] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Adding scrollwheel support
[ 16.452] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: YAxisMapping: buttons 4 and 5
[ 16.452] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 16.452] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.2/0003:0461:4E25.0006/input/input13/event13"
[ 16.452] (II) XINPUT: Adding extended input device "Hewlett Packard HP Wireless Keyboard Kit" (type: MOUSE, id 14)
[ 16.452] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: initialized for relative axes.
[ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) keeping acceleration scheme 1
[ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration profile 0
[ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration factor: 2.000
[ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration threshold: 4
[ 16.452] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/mouse1)
[ 16.452] (II) No input driver specified, ignoring this device.
[ 16.452] (II) This device may have been added with another device file.
[ 16.453] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event6)
[ 16.453] (II) No input driver specified, ignoring this device.
[ 16.453] (II) This device may have been added with another device file.
[ 16.453] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event5)
[ 16.453] (II) No input driver specified, ignoring this device.
[ 16.453] (II) This device may have been added with another device file.
[ 16.453] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event4)
[ 16.453] (II) No input driver specified, ignoring this device.
[ 16.453] (II) This device may have been added with another device file.
[ 16.453] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 16.453] (II) No input driver specified, ignoring this device.
[ 16.453] (II) This device may have been added with another device file.
[ 16.454] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event7)
[ 16.454] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 16.454] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
[ 16.454] (**) HP WMI hotkeys: always reports core events
[ 16.454] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event7"
[ 16.454] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
[ 16.454] (--) evdev: HP WMI hotkeys: Found keys
[ 16.454] (II) evdev: HP WMI hotkeys: Configuring as keyboard
[ 16.454] (**) Option "config_info" "udev:/sys/devices/virtual/input/input7/event7"
[ 16.454] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 15)
[ 16.454] (**) Option "xkb_rules" "evdev"
[ 16.454] (**) Option "xkb_model" "pc104"
[ 16.454] (**) Option "xkb_layout" "us"
[ 1192.410] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 1811.202] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 5455.421] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none

I saw your post, and had found it incredulous that you have a 1920x1080 display. A bit of research and I found I was wrong.
So, it appears you are driving the panel at its native resolution. Unfortunately, trying to determine what you mean by "Fuzzy" is probably going to be like trying to nail Jello to a tree. But, let's give it a shot. Is it fuzzy before you start X? Are lines and shapes fuzzy? Or is it just text that is fuzzy?
If it is just fonts, it could be a problem with hinting. Hinting is where the edges of fonts are deliberately fuzzed and feathered to get the kerning correct when the physical pixels of the display don't quite line up. This works well, unless the thing doing the hinting does not understand the geometry of the display. In a color LCD, each pixel is actually made up of smaller sub pixels, generally three -- A red, a green, and a blue. Green is usually in the middle. Some displays have Two greens per pixel, arranged RGBG. Some displays even have yellow subpixels. Sometimes the subpixels are arranged left to right, sometimes they are arranged top to bottom. Long story short, if you have hinting enabled, but the geometry is configured incorrectly, bad things happen. Take a look at this wiki article

Fuzzy Display on my G4

Similar Messages

Maybe you are looking for