An engineer's life around Kyoto

My laptop PC is fairly old and running Debian wheezy. Though it's not powerful, I am trying to run Xen 4.1. At my first trial, Xen dom0 kernel itself launched without a trouble, but just after the X server started the display was filled with textual black and white patterns and lost reaction to keyboard and mouse input. I got disappointed and kept away from Xen for a while. Today, I tried again Xen 4.1 following the "Google Teacher"'s work around for some kinds of Intel's integrated video controller. Before launching dom0, I added the following setting to /etc/X11/xorg.conf: Section "Device"         Identifier "myvideodevice"         Driver "intel"         Option "AccelMethod" "sna" EndSection After I checked that the setting is actually effective by restarting X server and looking into X server's log messages,  I reboot the system and launched dom0. As before, th...

I recently tried to set up Xen on my Squeeze box, with intel 945GM graphics controller. I followed the instruction on Xen - Debian Wiki . I installed the Xen hypervisor, kernel, xen-tools and other stuff, then created a domU image of Ubuntu natty. After that, I rebooted the system. But when X server was about to be launched, the screen became black out,  both keyboard and mouse don't work anymore. I reread the article on the wiki, and figured out the Xorg driver for Intel graphics controller  is suspicious. So, I changed the Xorg driver 'intel' to 'fbdev' wrting /etc/X11/xorg.conf , and rebooted.  This workaround works out! The drawback of the workaround is, 'intel' driver specific features, including DRI and XvMC, are disabled.

I have been a  Debian GNU/Linux user since 2007. Since then, I experienced several major OS upgrades (dist-upgrade).  But every time I dist-upgrade, some trouble annoyed me. The most recent problem was related to the seting of Xorg server. When starting up X server (from gdm3), the xserver process couldn't find the glx symbols. In the /var/log/Xorg.0.log: (EE) GLX error: Can not get required symbols. This prevented Compiz Fusion window manager from working on the X desktop. Although the hardware video driver was "intel", it seams that some extra glx code for Nvidia caused the trouble. The following command fixed the problem:   aptitude purge fglx-glx fglx-driver nvidia-vdpau-driver (I don't know which package was actually problematic.) If you have a glx related problem with the intel graphic controller chip, try removing unrelated packages that supposed be combined with nvidia or Radeon! That save you some (small amount of ) disk spaces :-) B...