Linux on a Toshiba L300 1AY


Home Page | Comments | Articles | Faq | Documents | Search | Archive | Tales from the Machine Room | Contribute | Login/Register

In a spending-raptus, I bought a brand new Toshiba Laptop. Why the heck did I do that? Don't know. An half-backed answer was that the new machine is a dual-core and that's good since I usually run multiple virtual machines for work... but in reality, there was really no reason to do so.

Anyhow, I toke it home and started fooling around with it.

The Toshiba L300 1AY is of the L300 family, is equipped with an Intel Core2 (dual core) 2 Ghz, that makes for a pretty fast machine. It has a 250 Gb SATA hard disk attached to an Intel SATA controller, and a pile of other Intel chips. Actually, the only thing that is not Intel is the wired network card that is a Realtek 8101. Why the hell didn't they used an Intel? I've no idea.

This is the LSPCI of the machine:


00:00.0 Host bridge: Intel Corporation Unknown device 2a40 (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Unknown device 2a42 (rev 07) 
00:02.1 Display controller: Intel Corporation Unknown device 2a43 (rev 07)
00:1a.0 USB Controller: Intel Corporation USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation PCI Express Port 2 (rev 03)
00:1c.4 PCI bridge: Intel Corporation PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation USB UHCI Controller #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation USB UHCI Controller #6 (rev 03)
00:1d.7 USB Controller: Intel Corporation USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation Mobile LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Thermal Subsystem (rev 03)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI Express Fast Ethernet controller (rev 02)
03:00.0 Network controller: Intel Corporation Unknown device 4232

A cat /proc/cpuinfo reveal:


processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Core(TM)2 Duo CPU     T5800  @ 2.00GHz
stepping	: 13
cpu MHz		: 2000.000
cache size	: 2048 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm 
constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 
ssse3 cx16 xtpr pdcm lahf_lm
bogomips	: 3989.72
clflush size	: 64
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Core(TM)2 Duo CPU     T5800  @ 2.00GHz
stepping	: 13
cpu MHz		: 2000.000
cache size	: 2048 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx 
lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est 
tm2 ssse3 cx16 xtpr pdcm lahf_lm
bogomips	: 3990.12
clflush size	: 64
power management:

So there really are 2 cores in there...

The machine arrives with 2 Gb of ram, but I'm already planning to upgrade it to 4. In any event, it still runs with 2.


             total       used       free     shared    buffers     cached
Mem:       2977904    1347016    1630888          0      30552    1024996
-/+ buffers/cache:     291468    2686436
Swap:      8008392          0    8008392

Yes, I have 8 gig of swap. With 250 Gb of disk I don't see what's the problem.

There is also a webcam in there, as lsusb reveal:


Bus 008 Device 001: ID 1d6b:0001  
Bus 007 Device 001: ID 1d6b:0001  
Bus 006 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
Bus 006 Device 001: ID 1d6b:0001  
Bus 005 Device 001: ID 1d6b:0001  
Bus 004 Device 001: ID 1d6b:0001  
Bus 003 Device 001: ID 1d6b:0001  
Bus 002 Device 001: ID 1d6b:0002  
Bus 001 Device 002: ID 04f2:b070 Chicony Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002  

The mouse/keyboard combos are of course mine. The Chicony is the webcam.

I fumbled around and couldn't find my Slack 12.2 DVD anymore. Bummer. The only thing I could find was the old 12.0, so I installed that. The installation went without an hitch, really it was that easy. Then the problem started.

The wired network card to begin with, is (as said) a Realtek. The lspci says "02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI Express Fast Ethernet controller (rev 02)" unfortunately, it seems that the kernel doesn't have (yet) support for this beast, so I used the other laptop to search for the driver, distributed directly from Realtek, the driver is 'r8101-1.011.00', but probably by the time you read this, there will be a new version. Downloaded, compiled, insmod and I got internet connection.

At that point I decided to upgrade the kernel anyway, so I got the latest kernel (2.6.28) sources and recompiled the whole kernel. My config file is here.

Once recompiled and installed, I had to recompile the driver for the network card (of course), then a reboot later and I have the latest kernel. The only thing that bother me is a bug message during bootup:

pci 0000:00:1a.7: EHCI: BIOS handoff failed (BIOS bug?) 01010001

Not really sure what it means, maybe that there is a bug in the bios of this beast. But everything seems to works despite that message so... I think I'll live.

The videocard is an Intel Mobile GM45 Express Chipset (this is the technical denomination), that is supported by the latest Intel driver in Xorg 1.4. Unfortunately, the version of Xorg distributed with Slack 12.0 (1.3) doesn't support it. Since I couldn't find the bloody DVD nowhere and didn't wanted to wait for the new one to arrive, I downloaded the relevant X packages from packages.slackware.it and installed them myself.

If you're interested this is the list of the packages you need:


pixman-0.12.0-i486-1.tgz
x11-skel-7.1-noarch-6.tgz
xf86-input-keyboard-1.3.1-i486-1.tgz
xf86-input-mouse-1.3.0-i486-1.tgz
xf86-input-synaptics-0.15.2-i486-1.tgz
xf86-video-intel-2.4.3-i486-2.tgz
xf86-video-v4l-0.2.0-i486-1.tgz
xf86-video-vesa-1.3.0-i486-2.tgz
xf86driproto-2.0.4-noarch-1.tgz
xf86vidmodeproto-2.2.2-noarch-1.tgz
xfs-1.0.6-i486-1.tgz
xhost-1.0.2-i486-1.tgz
xmodmap-1.0.3-i486-1.tgz
xorg-cf-files-1.0.2-noarch-1.tgz
xorg-docs-1.4-noarch-1.tgz
xorg-server-1.4.2-i486-1.tgz

The VESA driver isn't specifically required but I got it just to be safe (few video adapter do not works with the vesa driver).

Once done a quick xorgcfg and the driver is up and running. This is the result of the /var/log/xorg.log:


X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Slackware 12.1 Slackware Linux Project
Current Operating System: Linux toshi 2.6.28-smp #4 SMP Wed Jan 28 09:24:54 CET 2009 i686
Build Date: 30 June 2008  11:35:29PM
 
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 28 10:54:06 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) Including the default font path /usr/share/fonts/TTF,/usr/share/fonts/OTF,
/usr/share/fonts/Type1,/usr/share/fonts/misc,/usr/share/fonts/75dpi/:unscaled.
(**) FontPath set to:
	/usr/share/fonts/TTF,
	/usr/share/fonts/OTF,
	/usr/share/fonts/Type1,
	/usr/share/fonts/misc,
	/usr/share/fonts/75dpi/:unscaled,
	/usr/share/fonts/TTF,
	/usr/share/fonts/OTF,
	/usr/share/fonts/Type1,
	/usr/share/fonts/misc,
	/usr/share/fonts/75dpi/:unscaled
(**) RgbPath set to "/usr/share/X11/rgb"
(**) ModulePath set to "/usr/lib/xorg/modules"
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81d0280
(II) Module ABI versions:
	X.Org ANSI C Emulation: 0.3
	X.Org Video Driver: 2.0
	X.Org XInput driver : 2.0
	X.Org Server Extension : 0.3
	X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	ABI class: X.Org Video Driver, version 2.0
(--) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2a40 card 1179,ff66 rev 07 class 06,00,00 hdr 00
(II) PCI: 00:02:0: chip 8086,2a42 card 1179,ff66 rev 07 class 03,00,00 hdr 80
(II) PCI: 00:02:1: chip 8086,2a43 card 1179,ff66 rev 07 class 03,80,00 hdr 80
(II) PCI: 00:1a:0: chip 8086,2937 card 1179,ff66 rev 03 class 0c,03,00 hdr 80
(II) PCI: 00:1a:1: chip 8086,2938 card 1179,ff66 rev 03 class 0c,03,00 hdr 00
(II) PCI: 00:1a:7: chip 8086,293c card 1179,ff66 rev 03 class 0c,03,20 hdr 00
(II) PCI: 00:1b:0: chip 8086,293e card 1179,ff66 rev 03 class 04,03,00 hdr 00
(II) PCI: 00:1c:0: chip 8086,2940 card 0000,0000 rev 03 class 06,04,00 hdr 81
(II) PCI: 00:1c:1: chip 8086,2942 card 0000,0000 rev 03 class 06,04,00 hdr 81
(II) PCI: 00:1c:4: chip 8086,2948 card 0000,0000 rev 03 class 06,04,00 hdr 81
(II) PCI: 00:1d:0: chip 8086,2934 card 1179,ff66 rev 03 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,2935 card 1179,ff66 rev 03 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,2936 card 1179,ff66 rev 03 class 0c,03,00 hdr 00
(II) PCI: 00:1d:3: chip 8086,2939 card 1179,ff66 rev 03 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,293a card 1179,ff66 rev 03 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev 93 class 06,04,01 hdr 01
(II) PCI: 00:1f:0: chip 8086,2919 card 1179,ff66 rev 03 class 06,01,00 hdr 80
(II) PCI: 00:1f:2: chip 8086,2929 card 1179,ff66 rev 03 class 01,06,01 hdr 00
(II) PCI: 00:1f:3: chip 8086,2930 card 1179,ff66 rev 03 class 0c,05,00 hdr 00
(II) PCI: 00:1f:6: chip 8086,2932 card 1179,ff66 rev 03 class 11,80,00 hdr 00
(II) PCI: 02:00:0: chip 10ec,8136 card 1179,ff66 rev 02 class 02,00,00 hdr 00
(II) PCI: 03:00:0: chip 8086,4232 card 8086,1201 rev 00 class 02,80,00 hdr 00
(II) PCI: End of PCI scan
(II) Intel Bridge workaround enabled
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,6), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
	[0] -1	0	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:28:0), (0,2,2), BCTRL: 0x0000 (VGA_EN is cleared)
(II) Bus 2 I/O range:
	[0] -1	0	0x00003000 - 0x00004fff (0x2000) IX[B]
(II) Bus 2 non-prefetchable memory range:
	[0] -1	0	0xd5700000 - 0xd66fffff (0x1000000) MX[B]
(II) Bus 2 prefetchable memory range:
	[0] -1	0	0xd0400000 - 0xd14fffff (0x1100000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 3: bridge is at (0:28:1), (0,3,3), BCTRL: 0x0000 (VGA_EN is cleared)
(II) Bus 3 I/O range:
	[0] -1	0	0x00002000 - 0x00002fff (0x1000) IX[B]
(II) Bus 3 non-prefetchable memory range:
	[0] -1	0	0xd4600000 - 0xd56fffff (0x1100000) MX[B]
(II) Bus 3 prefetchable memory range:
	[0] -1	0	0xd1500000 - 0xd24fffff (0x1000000) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 6: bridge is at (0:28:4), (0,6,7), BCTRL: 0x0000 (VGA_EN is cleared)
(II) Bus 6 I/O range:
	[0] -1	0	0x00001000 - 0x00001fff (0x1000) IX[B]
(II) Bus 6 non-prefetchable memory range:
	[0] -1	0	0xd3600000 - 0xd45fffff (0x1000000) MX[B]
(II) Bus 6 prefetchable memory range:
	[0] -1	0	0xd2500000 - 0xd34fffff (0x1000000) MX[B]
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 4: bridge is at (0:30:0), (0,4,4), BCTRL: 0x0000 (VGA_EN is cleared)
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(0:2:0) Intel Corporation Mobile Integrated Graphics Controller rev 7, 
Mem @ 0xd0000000/22, 0xc0000000/28, I/O @ 0x5110/3
(--) PCI: (0:2:1) Intel Corporation Mobile Integrated Graphics Controller rev 7, 
Mem @ 0xd3500000/20
(II) Addressable bus resource ranges are
	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
	[1] -1	0	0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
	[0] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[5] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
(II) Active PCI resource ranges:
	[0] -1	0	0xd4600000 - 0xd4601fff (0x2000) MX[B]
	[1] -1	0	0xd0400000 - 0xd040ffff (0x10000) MX[B]
	[2] -1	0	0xd0410000 - 0xd0410fff (0x1000) MX[B]
	[3] -1	0	0xd6704000 - 0xd6704fff (0x1000) MX[B]
	[4] -1	0	0xd6706000 - 0xd67060ff (0x100) MX[B]
	[5] -1	0	0xd6705000 - 0xd67057ff (0x800) MX[B]
	[6] -1	0	0xd6705800 - 0xd6705bff (0x400) MX[B]
	[7] -1	0	0xd6700000 - 0xd6703fff (0x4000) MX[B]
	[8] -1	0	0xd6705c00 - 0xd6705fff (0x400) MX[B]
	[9] -1	0	0xd3500000 - 0xd35fffff (0x100000) MX[B](B)
	[10] -1	0	0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
	[11] -1	0	0xd0000000 - 0xd03fffff (0x400000) MX[B](B)
	[12] -1	0	0x00003000 - 0x000030ff (0x100) IX[B]
	[13] -1	0	0x00005000 - 0x0000501f (0x20) IX[B]
	[14] -1	0	0x00005020 - 0x0000503f (0x20) IX[B]
	[15] -1	0	0x00005118 - 0x0000511b (0x4) IX[B]
	[16] -1	0	0x00005100 - 0x00005107 (0x8) IX[B]
	[17] -1	0	0x0000511c - 0x0000511f (0x4) IX[B]
	[18] -1	0	0x00005108 - 0x0000510f (0x8) IX[B]
	[19] -1	0	0x00005040 - 0x0000505f (0x20) IX[B]
	[20] -1	0	0x00005060 - 0x0000507f (0x20) IX[B]
	[21] -1	0	0x00005080 - 0x0000509f (0x20) IX[B]
	[22] -1	0	0x000050a0 - 0x000050bf (0x20) IX[B]
	[23] -1	0	0x000050c0 - 0x000050df (0x20) IX[B]
	[24] -1	0	0x000050e0 - 0x000050ff (0x20) IX[B]
	[25] -1	0	0x00005110 - 0x00005117 (0x8) IX[B](B)
(II) Active PCI resource ranges after removing overlaps:
	[0] -1	0	0xd4600000 - 0xd4601fff (0x2000) MX[B]
	[1] -1	0	0xd0400000 - 0xd040ffff (0x10000) MX[B]
	[2] -1	0	0xd0410000 - 0xd0410fff (0x1000) MX[B]
	[3] -1	0	0xd6704000 - 0xd6704fff (0x1000) MX[B]
	[4] -1	0	0xd6706000 - 0xd67060ff (0x100) MX[B]
	[5] -1	0	0xd6705000 - 0xd67057ff (0x800) MX[B]
	[6] -1	0	0xd6705800 - 0xd6705bff (0x400) MX[B]
	[7] -1	0	0xd6700000 - 0xd6703fff (0x4000) MX[B]
	[8] -1	0	0xd6705c00 - 0xd6705fff (0x400) MX[B]
	[9] -1	0	0xd3500000 - 0xd35fffff (0x100000) MX[B](B)
	[10] -1	0	0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
	[11] -1	0	0xd0000000 - 0xd03fffff (0x400000) MX[B](B)
	[12] -1	0	0x00003000 - 0x000030ff (0x100) IX[B]
	[13] -1	0	0x00005000 - 0x0000501f (0x20) IX[B]
	[14] -1	0	0x00005020 - 0x0000503f (0x20) IX[B]
	[15] -1	0	0x00005118 - 0x0000511b (0x4) IX[B]
	[16] -1	0	0x00005100 - 0x00005107 (0x8) IX[B]
	[17] -1	0	0x0000511c - 0x0000511f (0x4) IX[B]
	[18] -1	0	0x00005108 - 0x0000510f (0x8) IX[B]
	[19] -1	0	0x00005040 - 0x0000505f (0x20) IX[B]
	[20] -1	0	0x00005060 - 0x0000507f (0x20) IX[B]
	[21] -1	0	0x00005080 - 0x0000509f (0x20) IX[B]
	[22] -1	0	0x000050a0 - 0x000050bf (0x20) IX[B]
	[23] -1	0	0x000050c0 - 0x000050df (0x20) IX[B]
	[24] -1	0	0x000050e0 - 0x000050ff (0x20) IX[B]
	[25] -1	0	0x00005110 - 0x00005117 (0x8) IX[B](B)
(II) OS-reported resource ranges after removing overlaps with PCI:
	[0] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[5] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
	[0] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0xd4600000 - 0xd4601fff (0x2000) MX[B]
	[5] -1	0	0xd0400000 - 0xd040ffff (0x10000) MX[B]
	[6] -1	0	0xd0410000 - 0xd0410fff (0x1000) MX[B]
	[7] -1	0	0xd6704000 - 0xd6704fff (0x1000) MX[B]
	[8] -1	0	0xd6706000 - 0xd67060ff (0x100) MX[B]
	[9] -1	0	0xd6705000 - 0xd67057ff (0x800) MX[B]
	[10] -1	0	0xd6705800 - 0xd6705bff (0x400) MX[B]
	[11] -1	0	0xd6700000 - 0xd6703fff (0x4000) MX[B]
	[12] -1	0	0xd6705c00 - 0xd6705fff (0x400) MX[B]
	[13] -1	0	0xd3500000 - 0xd35fffff (0x100000) MX[B](B)
	[14] -1	0	0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
	[15] -1	0	0xd0000000 - 0xd03fffff (0x400000) MX[B](B)
	[16] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[17] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
	[18] -1	0	0x00003000 - 0x000030ff (0x100) IX[B]
	[19] -1	0	0x00005000 - 0x0000501f (0x20) IX[B]
	[20] -1	0	0x00005020 - 0x0000503f (0x20) IX[B]
	[21] -1	0	0x00005118 - 0x0000511b (0x4) IX[B]
	[22] -1	0	0x00005100 - 0x00005107 (0x8) IX[B]
	[23] -1	0	0x0000511c - 0x0000511f (0x4) IX[B]
	[24] -1	0	0x00005108 - 0x0000510f (0x8) IX[B]
	[25] -1	0	0x00005040 - 0x0000505f (0x20) IX[B]
	[26] -1	0	0x00005060 - 0x0000507f (0x20) IX[B]
	[27] -1	0	0x00005080 - 0x0000509f (0x20) IX[B]
	[28] -1	0	0x000050a0 - 0x000050bf (0x20) IX[B]
	[29] -1	0	0x000050c0 - 0x000050df (0x20) IX[B]
	[30] -1	0	0x000050e0 - 0x000050ff (0x20) IX[B]
	[31] -1	0	0x00005110 - 0x00005117 (0x8) IX[B](B)
(II) "extmod" will be loaded. This was enabled by default and also specified in the 
config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the 
config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the 
config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in 
the config file.
(II) "type1" will be loaded. This was enabled by default and also specified in 
the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the 
config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the 
config file.
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.13.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 0.3
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "xtrap"
(II) Loading /usr/lib/xorg/modules/extensions//libxtrap.so
(II) Module xtrap: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	Module class: X.Org Server Extension
	ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DEC-XTRAP
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
	compiled for 1.4.2, module version = 2.1.0
	Module class: X.Org Font Renderer
	ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "type1"
(II) Loading /usr/lib/xorg/modules/fonts//libtype1.so
(II) Module type1: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.2
	Module class: X.Org Font Renderer
	ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Type1
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 2.4.3
	Module class: X.Org Video Driver
	ABI class: X.Org Video Driver, version 2.0
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
	compiled for 1.4.0.90, module version = 1.3.0
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 2.0
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.3.1
	Module class: X.Org XInput Driver
	ABI class: X.Org XInput driver, version 2.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
	i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
	E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, G35, 965Q, 946GZ,
	965GM, 965GME/GLE, G33, Q35, Q33,
	Mobile Intel® GM45 Express Chipset,
	Intel Integrated Graphics Device, G45/G43, Q45/Q43
(II) Primary Device is: PCI 00:02:0
(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(--) Chipset Mobile Intel® GM45 Express Chipset found
(II) resource ranges after xf86ClaimFixedResources() call:
	[0] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0xd4600000 - 0xd4601fff (0x2000) MX[B]
	[5] -1	0	0xd0400000 - 0xd040ffff (0x10000) MX[B]
	[6] -1	0	0xd0410000 - 0xd0410fff (0x1000) MX[B]
	[7] -1	0	0xd6704000 - 0xd6704fff (0x1000) MX[B]
	[8] -1	0	0xd6706000 - 0xd67060ff (0x100) MX[B]
	[9] -1	0	0xd6705000 - 0xd67057ff (0x800) MX[B]
	[10] -1	0	0xd6705800 - 0xd6705bff (0x400) MX[B]
	[11] -1	0	0xd6700000 - 0xd6703fff (0x4000) MX[B]
	[12] -1	0	0xd6705c00 - 0xd6705fff (0x400) MX[B]
	[13] -1	0	0xd3500000 - 0xd35fffff (0x100000) MX[B](B)
	[14] -1	0	0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
	[15] -1	0	0xd0000000 - 0xd03fffff (0x400000) MX[B](B)
	[16] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[17] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
	[18] -1	0	0x00003000 - 0x000030ff (0x100) IX[B]
	[19] -1	0	0x00005000 - 0x0000501f (0x20) IX[B]
	[20] -1	0	0x00005020 - 0x0000503f (0x20) IX[B]
	[21] -1	0	0x00005118 - 0x0000511b (0x4) IX[B]
	[22] -1	0	0x00005100 - 0x00005107 (0x8) IX[B]
	[23] -1	0	0x0000511c - 0x0000511f (0x4) IX[B]
	[24] -1	0	0x00005108 - 0x0000510f (0x8) IX[B]
	[25] -1	0	0x00005040 - 0x0000505f (0x20) IX[B]
	[26] -1	0	0x00005060 - 0x0000507f (0x20) IX[B]
	[27] -1	0	0x00005080 - 0x0000509f (0x20) IX[B]
	[28] -1	0	0x000050a0 - 0x000050bf (0x20) IX[B]
	[29] -1	0	0x000050c0 - 0x000050df (0x20) IX[B]
	[30] -1	0	0x000050e0 - 0x000050ff (0x20) IX[B]
	[31] -1	0	0x00005110 - 0x00005117 (0x8) IX[B](B)
(II) resource ranges after probing:
	[0] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[1] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[2] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[3] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[4] -1	0	0xd4600000 - 0xd4601fff (0x2000) MX[B]
	[5] -1	0	0xd0400000 - 0xd040ffff (0x10000) MX[B]
	[6] -1	0	0xd0410000 - 0xd0410fff (0x1000) MX[B]
	[7] -1	0	0xd6704000 - 0xd6704fff (0x1000) MX[B]
	[8] -1	0	0xd6706000 - 0xd67060ff (0x100) MX[B]
	[9] -1	0	0xd6705000 - 0xd67057ff (0x800) MX[B]
	[10] -1	0	0xd6705800 - 0xd6705bff (0x400) MX[B]
	[11] -1	0	0xd6700000 - 0xd6703fff (0x4000) MX[B]
	[12] -1	0	0xd6705c00 - 0xd6705fff (0x400) MX[B]
	[13] -1	0	0xd3500000 - 0xd35fffff (0x100000) MX[B](B)
	[14] -1	0	0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
	[15] -1	0	0xd0000000 - 0xd03fffff (0x400000) MX[B](B)
	[16] 0	0	0x000a0000 - 0x000affff (0x10000) MS[B]
	[17] 0	0	0x000b0000 - 0x000b7fff (0x8000) MS[B]
	[18] 0	0	0x000b8000 - 0x000bffff (0x8000) MS[B]
	[19] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[20] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
	[21] -1	0	0x00003000 - 0x000030ff (0x100) IX[B]
	[22] -1	0	0x00005000 - 0x0000501f (0x20) IX[B]
	[23] -1	0	0x00005020 - 0x0000503f (0x20) IX[B]
	[24] -1	0	0x00005118 - 0x0000511b (0x4) IX[B]
	[25] -1	0	0x00005100 - 0x00005107 (0x8) IX[B]
	[26] -1	0	0x0000511c - 0x0000511f (0x4) IX[B]
	[27] -1	0	0x00005108 - 0x0000510f (0x8) IX[B]
	[28] -1	0	0x00005040 - 0x0000505f (0x20) IX[B]
	[29] -1	0	0x00005060 - 0x0000507f (0x20) IX[B]
	[30] -1	0	0x00005080 - 0x0000509f (0x20) IX[B]
	[31] -1	0	0x000050a0 - 0x000050bf (0x20) IX[B]
	[32] -1	0	0x000050c0 - 0x000050df (0x20) IX[B]
	[33] -1	0	0x000050e0 - 0x000050ff (0x20) IX[B]
	[34] -1	0	0x00005110 - 0x00005117 (0x8) IX[B](B)
	[35] 0	0	0x000003b0 - 0x000003bb (0xc) IS[B]
	[36] 0	0	0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	ABI class: X.Org Video Driver, version 2.0
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.1.0
	ABI class: X.Org Video Driver, version 2.0
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 0.1.0
	ABI class: X.Org Video Driver, version 2.0
(**) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) Mobile Intel® GM45 Express Chipset
(--) intel(0): Chipset: "Mobile Intel® GM45 Express Chipset"
(--) intel(0): Linear framebuffer at 0xC0000000
(--) intel(0): IO registers at addr 0xD0000000
(II) intel(0): 2 display pipes available.
(==) intel(0): Using EXA for acceleration
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules//libint10.so
(II) intel(0): initializing int10
(WW) intel(0): Bad V_BIOS checksum
(II) intel(0): Primary V_BIOS segment is: 0xc000
(II) intel(0): VESA BIOS detected
(II) intel(0): VESA VBE Version 3.0
(II) intel(0): VESA VBE Total Mem: 131008 kB
(II) intel(0): VESA VBE OEM: Intel(r)Cantiga Graphics Chip Accelerated VGA BIOS
(II) intel(0): VESA VBE OEM Software Rev: 1.0
(II) intel(0): VESA VBE OEM Vendor: Intel Corporation
(II) intel(0): VESA VBE OEM Product: Intel(r)Cantiga Graphics Controller
(II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"(II) Module "i2c" already built-in
(II) intel(0): Output VGA using monitor section Monitor0
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): Output LVDS has no monitor section
(II) intel(0): I2C bus "LVDSDDC_C" initialized.
(II) intel(0): Attempting to determine panel fixed mode.
(II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
(II) intel(0): EDID vendor "CMO", prod id 5460
(II) intel(0): Output TV has no monitor section
(II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
(II) intel(0): EDID vendor "GSM", prod id 22163
(II) intel(0): Using EDID range info for horizontal sync
(II) intel(0): Using EDID range info for vertical refresh
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1920x1200"x0.0  154.00  1920 1968 2000 2080 1200 1203 1209 
1235 +hsync -vsync (74.0 kHz)
(II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160 1200 1201 1204 
1250 +hsync +vsync (75.0 kHz)
(II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 
+hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 
-hsync -vsync (37.5 kHz)
(II) intel(0): Modeline "640x480"x0.0   25.20  640 656 752 800  480 490 492 525 
-hsync -vsync (31.5 kHz)
(II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 
-hsync +vsync (31.5 kHz)
(II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  
1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) intel(0): Modeline "1024x768"x0.0   78.80  1024 1040 1136 1312  
768 769 772 800 +hsync +vsync (60.1 kHz)
(II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 
771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 
601 604 625 +hsync +vsync (46.9 kHz)
(II) intel(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  
864 865 868 900 +hsync +vsync (67.5 kHz)
(II) intel(0): Modeline "1600x1200"x59.9  161.00  1600 1712 1880 2160  
1200 1203 1207 1245 -hsync +vsync (74.5 kHz)
(II) intel(0): Modeline "1280x1024"x74.9  138.75  1280 1368 1504 1728  
1024 1027 1034 1072 -hsync +vsync (80.3 kHz)
(II) intel(0): Modeline "1680x1050"x60.0  146.25  1680 1784 1960 2240  
1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
(II) intel(0): Modeline "1280x960"x74.9  130.00  1280 1368 1504 1728  
960 963 967 1005 -hsync +vsync (75.2 kHz)
(II) intel(0): Modeline "1920x1080"x60.0  173.00  1920 2048 2248 2576 
1080 1083 1088 1120 -hsync +vsync (67.2 kHz)
(II) intel(0): EDID vendor "GSM", prod id 22163
(II) intel(0): EDID vendor "CMO", prod id 5460
(II) intel(0): Output VGA connected
(II) intel(0): Output LVDS connected
(II) intel(0): Output TV disconnected
(II) intel(0): Output VGA using initial mode 1920x1200
(II) intel(0): Output LVDS using initial mode 1280x800
(II) intel(0): Monitoring connected displays enabled
(II) intel(0): detected 512 kB GTT.
(II) intel(0): detected 131068 kB stolen memory.
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Will not try to enable page flipping
(==) intel(0): Triple buffering disabled
(==) intel(0): Intel XvMC decoder disabled
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(**) intel(0): Display dimensions: (520, 320) mm
(**) intel(0): DPI set to (156, 95)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	ABI class: X.Org ANSI C Emulation, version 0.3
(II) Loading sub module "exa"
(II) LoadModule: "exa"
(II) Loading /usr/lib/xorg/modules//libexa.so
(II) Module exa: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 2.2.0
	ABI class: X.Org Video Driver, version 2.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"(II) Module "ramdac" already built-in
(II) intel(0): Comparing regs from server start up to After PreInit
(WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd000000a
(WW) intel(0): PP_STATUS before: on, ready, sequencing idle
(WW) intel(0): PP_STATUS after: on, ready, sequencing on
(WW) intel(0): Register 0x61114 (PORT_HOTPLUG_STAT) changed from 0x00000b00 to 0x00000f00
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x00000206 to 0x00000000
(WW) intel(0): PIPEASTAT before: status: VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS
(WW) intel(0): PIPEASTAT after: status:
(WW) intel(0): Register 0x71024 (PIPEBSTAT) changed from 0x80000206 to 0x00000206
(WW) intel(0): PIPEBSTAT before: status: FIFO_UNDERRUN VSYNC_INT_STATUS 
SVBLANK_INT_STATUS VBLANK_INT_STATUS
(WW) intel(0): PIPEBSTAT after: status: VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS
(WW) intel(0): Register 0x68000 (TV_CTL) changed from 0x100000d0 to 0x000c0010
(WW) intel(0): Register 0x68010 (TV_CSC_Y) changed from 0x00000000 to 0x0332012d
(WW) intel(0): Register 0x68014 (TV_CSC_Y2) changed from 0x00000000 to 0x07d30104
(WW) intel(0): Register 0x68018 (TV_CSC_U) changed from 0x00000000 to 0x0733052d
(WW) intel(0): Register 0x6801c (TV_CSC_U2) changed from 0x00000000 to 0x05c70200
(WW) intel(0): Register 0x68020 (TV_CSC_V) changed from 0x00000000 to 0x0340030c
(WW) intel(0): Register 0x68024 (TV_CSC_V2) changed from 0x00000000 to 0x06d00200
(WW) intel(0): Register 0x68028 (TV_CLR_KNOBS) changed from 0x00000000 to 0x00606000
(WW) intel(0): Register 0x6802c (TV_CLR_LEVEL) changed from 0x00000000 to 0x010b00e1
(WW) intel(0): Register 0x68030 (TV_H_CTL_1) changed from 0x00000000 to 0x00400359
(WW) intel(0): Register 0x68034 (TV_H_CTL_2) changed from 0x00000000 to 0x80480022
(WW) intel(0): Register 0x68038 (TV_H_CTL_3) changed from 0x00000000 to 0x007c0344
(WW) intel(0): Register 0x6803c (TV_V_CTL_1) changed from 0x00000000 to 0x00f01415
(WW) intel(0): Register 0x68040 (TV_V_CTL_2) changed from 0x00000000 to 0x00060607
(WW) intel(0): Register 0x68044 (TV_V_CTL_3) changed from 0x00000000 to 0x80120001
(WW) intel(0): Register 0x68048 (TV_V_CTL_4) changed from 0x00000000 to 0x000900f0
(WW) intel(0): Register 0x6804c (TV_V_CTL_5) changed from 0x00000000 to 0x000a00f0
(WW) intel(0): Register 0x68050 (TV_V_CTL_6) changed from 0x00000000 to 0x000900f0
(WW) intel(0): Register 0x68054 (TV_V_CTL_7) changed from 0x00000000 to 0x000a00f0
(WW) intel(0): Register 0x68060 (TV_SC_CTL_1) changed from 0x00000000 to 0xc1710088
(WW) intel(0): Register 0x68064 (TV_SC_CTL_2) changed from 0x00000000 to 0x4e2d1dc8
(WW) intel(0): Register 0x68070 (TV_WIN_POS) changed from 0x00000000 to 0x00360024
(WW) intel(0): Register 0x68074 (TV_WIN_SIZE) changed from 0x00000000 to 0x02640198
(WW) intel(0): Register 0x68080 (TV_FILTER_CTL_1) changed from 0x00000000 to 0x8000085e
(WW) intel(0): Register 0x68084 (TV_FILTER_CTL_2) changed from 0x00000000 to 0x00028283
(WW) intel(0): Register 0x68088 (TV_FILTER_CTL_3) changed from 0x00000000 to 0x00014141
(WW) intel(0): Register 0x68100 (TV_H_LUMA_0) changed from 0x00000000 to 0xb1403000
(WW) intel(0): Register 0x681ec (TV_H_LUMA_59) changed from 0x00000000 to 0x0000b060
(WW) intel(0): Register 0x68200 (TV_H_CHROMA_0) changed from 0x00000000 to 0xb1403000
(WW) intel(0): Register 0x682ec (TV_H_CHROMA_59) changed from 0x00000000 to 0x0000b060
(WW) intel(0): Register 0x321b (FBC_FENCE_OFF) changed from 0x62011d00 to 0xe401ac00
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC?  No, I don't.
(II) resource ranges after preInit:
	[0] 0	0	0xc0000000 - 0xcfffffff (0x10000000) MS[B]
	[1] 0	0	0xd0000000 - 0xd03fffff (0x400000) MS[B]
	[2] -1	0	0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
	[3] -1	0	0x000f0000 - 0x000fffff (0x10000) MX[B]
	[4] -1	0	0x000c0000 - 0x000effff (0x30000) MX[B]
	[5] -1	0	0x00000000 - 0x0009ffff (0xa0000) MX[B]
	[6] -1	0	0xd4600000 - 0xd4601fff (0x2000) MX[B]
	[7] -1	0	0xd0400000 - 0xd040ffff (0x10000) MX[B]
	[8] -1	0	0xd0410000 - 0xd0410fff (0x1000) MX[B]
	[9] -1	0	0xd6704000 - 0xd6704fff (0x1000) MX[B]
	[10] -1	0	0xd6706000 - 0xd67060ff (0x100) MX[B]
	[11] -1	0	0xd6705000 - 0xd67057ff (0x800) MX[B]
	[12] -1	0	0xd6705800 - 0xd6705bff (0x400) MX[B]
	[13] -1	0	0xd6700000 - 0xd6703fff (0x4000) MX[B]
	[14] -1	0	0xd6705c00 - 0xd6705fff (0x400) MX[B]
	[15] -1	0	0xd3500000 - 0xd35fffff (0x100000) MX[B](B)
	[16] -1	0	0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
	[17] -1	0	0xd0000000 - 0xd03fffff (0x400000) MX[B](B)
	[18] 0	0	0x000a0000 - 0x000affff (0x10000) MS[B](OprD)
	[19] 0	0	0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD)
	[20] 0	0	0x000b8000 - 0x000bffff (0x8000) MS[B](OprD)
	[21] 0	0	0x00005110 - 0x00005117 (0x8) IS[B]
	[22] -1	0	0x0000ffff - 0x0000ffff (0x1) IX[B]
	[23] -1	0	0x00000000 - 0x000000ff (0x100) IX[B]
	[24] -1	0	0x00003000 - 0x000030ff (0x100) IX[B]
	[25] -1	0	0x00005000 - 0x0000501f (0x20) IX[B]
	[26] -1	0	0x00005020 - 0x0000503f (0x20) IX[B]
	[27] -1	0	0x00005118 - 0x0000511b (0x4) IX[B]
	[28] -1	0	0x00005100 - 0x00005107 (0x8) IX[B]
	[29] -1	0	0x0000511c - 0x0000511f (0x4) IX[B]
	[30] -1	0	0x00005108 - 0x0000510f (0x8) IX[B]
	[31] -1	0	0x00005040 - 0x0000505f (0x20) IX[B]
	[32] -1	0	0x00005060 - 0x0000507f (0x20) IX[B]
	[33] -1	0	0x00005080 - 0x0000509f (0x20) IX[B]
	[34] -1	0	0x000050a0 - 0x000050bf (0x20) IX[B]
	[35] -1	0	0x000050c0 - 0x000050df (0x20) IX[B]
	[36] -1	0	0x000050e0 - 0x000050ff (0x20) IX[B]
	[37] -1	0	0x00005110 - 0x00005117 (0x8) IX[B](B)
	[38] 0	0	0x000003b0 - 0x000003bb (0xc) IS[B](OprU)
	[39] 0	0	0x000003c0 - 0x000003df (0x20) IS[B](OprU)
(II) intel(0): Kernel reported 716032 total, 1 used
(II) intel(0): I830CheckAvailableMemory: 2864124 kB available
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
[drm] failed to load kernel module "i915"
(EE) [drm] drmOpen failed.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
(**) intel(0): Framebuffer compression enabled
(**) intel(0): Tiling enabled
(==) intel(0): VideoRam: 262144 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
(II) intel(0): Page Flipping disabled
(==) intel(0): Write-combining range (0xc0000000,0x10000000)
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) EXA(0): Offscreen pixmap area of 46080000 bytes
(II) EXA(0): Driver registered support for the following operations:
(II)         Solid
(II)         Copy
(II)         Composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x00290fff: compressed frame buffer (2500 kB, 0x00000000b8020000 physical
)
(II) intel(0): 0x00291000-0x0029afff: HW cursors (40 kB)
(II) intel(0): 0x0029b000-0x002a2fff: logical 3D context (32 kB)
(II) intel(0): 0x002a3000-0x002b4fff: exa G965 state buffer (72 kB)
(II) intel(0): 0x002b5000-0x002b5fff: power context (4 kB)
(II) intel(0): 0x00300000-0x02a0ffff: front buffer (40000 kB) X tiled
(II) intel(0): 0x02a10000-0x05601fff: exa offscreen (45000 kB)
(II) intel(0): 0x10000000:            end of aperture
(II) intel(0): using SSC reference clock of 100 MHz
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
(II) intel(0): Output configuration:
(II) intel(0):   Pipe A is on
(II) intel(0):   Display plane A is now enabled and connected to pipe A.
(II) intel(0):   Pipe B is on
(II) intel(0):   Display plane B is now enabled and connected to pipe B.
(II) intel(0):   Output VGA is connected to pipe A
(II) intel(0):   Output LVDS is connected to pipe B
(II) intel(0):   Output TV is connected to pipe none
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) intel(0): using SSC reference clock of 100 MHz
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
(II) intel(0): Set up textured video
(II) intel(0): direct rendering: Failed
(WW) intel(0): Option "monitor-lcd" is not used
(WW) intel(0): Option "external" is not used
(--) RandR disabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension XAccessControlExtension
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) AIGLX: Screen 0 is not DRI capable
(II) Loading sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so
(II) Module GLcore: vendor="X.Org Foundation"
	compiled for 1.4.2, module version = 1.0.0
	ABI class: X.Org Server Extension, version 0.3
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
(II) intel(0): Setting screen physical size to 518 x 324
(**) Option "Protocol" "auto"
(**) Mouse0: Device: "/dev/input/mice"
(**) Mouse0: Protocol: "auto"
(**) Option "CorePointer"
(**) Mouse0: always reports core events
(**) Option "Device" "/dev/input/mice"
(==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5 6 7"
(**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7
(**) Mouse0: Buttons: 11
(**) Mouse0: Sensitivity: 1
(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "us"
(**) Keyboard0: XkbLayout: "us"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) evaluating device (Keyboard0)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) evaluating device (Mouse0)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded
(II) intel(0): EDID vendor "GSM", prod id 22163
(II) intel(0): Using hsync ranges from config file
(II) intel(0): Using vrefresh ranges from config file
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1920x1200"x0.0  154.00  1920 1968 2000 2080 
1200 1203 1209 1235 +hsync -vsync (74.0 kHz)
(II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160 
1200 1201 1204 1250 +hsync +vsync (75.0 kHz)
(II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  
600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  
480 481 484 500 -hsync -vsync (37.5 kHz)
(II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  
1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) intel(0): Modeline "1024x768"x0.0   78.80  1024 1040 1136 1312  
768 769 772 800 +hsync +vsync (60.1 kHz)
(II) intel(0): Modeline "1600x1200"x59.9  161.00  1600 1712 1880 2160  
1200 1203 1207 1245 -hsync +vsync (74.5 kHz)
(II) intel(0): Modeline "1280x1024"x74.9  138.75  1280 1368 1504 1728  
1024 1027 1034 1072 -hsync +vsync (80.3 kHz)
(II) intel(0): Modeline "1680x1050"x60.0  146.25  1680 1784 1960 2240  
1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
(II) intel(0): Modeline "1280x960"x74.9  130.00  1280 1368 1504 1728  
960 963 967 1005 -hsync +vsync (75.2 kHz)
(II) intel(0): Modeline "1920x1080"x60.0  173.00  1920 2048 2248 2576  
1080 1083 1088 1120 -hsync +vsync (67.2 kHz)
(II) intel(0): EDID vendor "GSM", prod id 22163
(II) intel(0): EDID vendor "CMO", prod id 5460
(II) intel(0): EDID vendor "GSM", prod id 22163
(II) intel(0): Using hsync ranges from config file
(II) intel(0): Using vrefresh ranges from config file
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1920x1200"x0.0  154.00  1920 1968 2000 2080  
1200 1203 1209 1235 +hsync -vsync (74.0 kHz)
(II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  
1200 1201 1204 1250 +hsync +vsync (75.0 kHz)
(II) intel(0): Modeline "1600x1200"x59.9  161.00  1600 1712 1880 2160  
1200 1203 1207 1245 -hsync +vsync (74.5 kHz)
(II) intel(0): Modeline "1280x1024"x74.9  138.75  1280 1368 1504 1728  
1024 1027 1034 1072 -hsync +vsync (80.3 kHz)
(II) intel(0): Modeline "1680x1050"x60.0  146.25  1680 1784 1960 2240 
1050 1053 1059 1089 -hsync +vsync (65.3 kHz)
(II) intel(0): Modeline "1280x960"x74.9  130.00  1280 1368 1504 1728 
960 963 967 1005 -hsync +vsync (75.2 kHz)
(II) intel(0): Modeline "1920x1080"x60.0  173.00  1920 2048 2248 2576 
1080 1083 1088 1120 -hsync +vsync (67.2 kHz)
(II) intel(0): EDID vendor "GSM", prod id 22163
(II) intel(0): EDID vendor "CMO", prod id 5460
(II) 3rd Button detected: disabling emulate3Button
(II) intel(0): EDID vendor "GSM", prod id 22163
(II) intel(0): Using hsync ranges from config file
(II) intel(0): Using vrefresh ranges from config file
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1920x1200"x0.0  154.00  1920 1968 2000 2080 
1200 1203 1209 1235 +hsync -vsync (74.0 kHz)
(II) intel(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  
1200 1201 1204 1250 +hsync +vsync (75.0 kHz)

I wanted a dual-head display, so I followed a couple of instructions on the internet and configured a dual head using xrandr. Configured a "virtual screen" larger enough to encompasse both my displays (xrandr -q will tell you how big it has to be), changed Xorg.conf (my xorg.conf is here) and a quick xrandr --output VGA --right-of LVDS later I have a dual-head display.

Note: you probably have to run xrandr as root. To do so you'll need first to disable the X authentication. So run 'xhost +' first, then su to root and then run xrandr. If you get an error that the screen can't be that big, is because you need to set the Virtual Screen size in your xorg.conf. In mine I have:


Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	DefaultDepth 24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Virtual 3200 1200
		Modes   "1280x800"
	EndSubSection
EndSection

Is the "Virtual" bit the important one, that way I setup a "screen" that is 3200x1200, then I use 1280 for one screen and 1920 rest for the other one. Of course your monitor is probably different from mine, so how do you know how big must be? Use xrandr. A xrandr -q reveal the followings:


Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 3200 x 1200
VGA connected 1920x1200+1280+0 (normal left inverted right x axis y axis) 518mm x 324mm
   1920x1200      60.0*+
   1920x1080      60.0  
   1600x1200      60.0     59.9  
   1680x1050      60.0  
   1280x1024      74.9     75.0  
   1280x960       74.9  
   1152x864       75.0  
   1024x768       75.1     60.0  
   800x600        75.0     60.3  
   640x480        75.0     60.0  
   720x400        70.1  
LVDS connected 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm
   1280x800       59.9*+
   1024x768       60.0  
   800x600        60.3  
   640x480        59.9  
TV disconnected (normal left inverted right x axis y axis)

The '1920x1200' is the external display, the 1280x800 is the internal one. Just adds up the horizontal size of both display and you know how big must be your 'virtual' screen to accomodate both.

You can see the whole effect in the picture:

Yet another Intel. This is an Intel HD Audio Controller that is supported by the default driver found in the kernel. Nothing to say here, it just worked.

You only have to remember to turn the volume up, the default config I think the volume is completely shut off, and there is a small 'wheel' on the front of the laptop that apparently doesn't do anything at all.

Yup, you betcha! It's an Intel. And is supported by the Intel driver in the kernel, you only need to add the correct firmware code in the hotplug directory.

The file is something like iwlwifi-5000-ucode, I don't add a link since is going to be replaced pretty soon by a new version, so just google it.

Unpack it and drop the resulting file in the hotplug dir (/lib/firmware).

The driver supports WPA and WEP. So just configure it and you're set. I could finally remove the wired cable that I used to copy the 20+ Gb of mp3s from my old laptop to the new one.

Since the whole point of the exercise was to run VMware on this baby, I had to install it. I decided (why? oh why?) to get the last version. And immediately began to hate that crappy web-interface. First of all, the stupid thing wants PAM. So I had to get it and compile it (Slack doesn't use pam for authentication) and create a special 'vmware-authd' config file in pam.d or it won't work. The file looks like this:


#%PAM-1.0
auth       required	pam_unix.so shadow nullok
account    required	pam_unix.so

Impressive huh?

Anyway, once done this you're not out of the wood yet. VMware require hald to run. Even if it isn't written anywhere. And I forgot to activate dnotify in my kernel. And without dnotify hald won't start. So go back, recompile the kernel, restart, start hald and vmware is finally happy.

I configured the Bios to support 'legacy USB' so my USB keyboard works during the bootup process, I also configured the bios to always use both the LCD and the external screen. If left in "automatic" the LCD display turn automatically off if an external screen is attached and I couldn't turn it on anymore... not really usefull as a dual-head.

If you enable the Intel sensor platform in the kernel, you can get the processor's temperatures and the like. Not really usefull, but it makes for a funny look in the 'monitor':

It simply works. Just run a /bin/echo -n mem > /sys/power/state and the machine goes into suspend mode. The same goes for hybernate. No problem at all.

It works. Using the default kernel or using the one compiled by myself, just use the V4l drivers. It works fine with Skype and with capture softwares. This is an image capture using 'motion':

The modem. Who uses one anymore?

Always use the last kernel available. In the beginning I had a huge amount of problemss with the video card and X 'cause I was using the old 2.6.21 kernel and the intel driver didn't liked it a bit. When I upgraded the kernel everything worked like a charm.

Bloody, fscking, shiny display! Why the heck do they have to make a display so shiny that I can use it to comb my hair? Can't see a bloody thing if the light is behind my back!

Haaalloooooo? Mr. Laptops producers? Could we please get back to bloody display that we can see? I don't give a flying duck if Apple is doing it and those morons pay big bucks for them, I want a display that doesn't look like my bathroom mirror! Thank you!

Why the heck is the connector for the microphone/earphone on the front? This way, if I put the lapdog on a stand I can't connect my earphone/speakers anymore. And since I am at it, all the bloody connectors are on the sides or on the front! There is bloody nothing in the back! Can we put the connectors back where they belongs? Pretty please?


Comments are added when and more important if I have the time to review them and after removing Spam, Crap, Phishing and the like. So don't hold your breath. And if your comment doesn't appear, is probably becuase it wasn't worth it.

28 messages this document does not accept new posts
DomShiny display... By Dom - posted 29/01/2009 01:30
Quote:" Bloody, fscking, shiny display! Why the heck do they have to make a display so shiny that I can use it to comb my hair? Can't see a bloody thing if the light is behind my back!"

Maybe for privacy purpose ? Nobody on your back or side can read what are you writing.. somtimes nor the user can do it.. I hate them too... really !

--
Dom


Riccardo Cagnassosubject By Riccardo Cagnasso - posted 29/01/2009 01:45

Domanda: con il sistema dual head che hai usato, hai un singolo desktop (un singolo x screen) "spalmato" sui due monitor giusto?Che è una schifezza mostruosa perchè diventa praticamente impossibile mettere una qualsiasi applicazioni in fullscreen (per non parlare se uno vuole usare un tiling windows manager). Chiedo perchè un po di tempo fa avevo provato a riavviare la mia vecchia installazione di ubuntu su il mio desktop che ha due monitor (e una scheda video nvidia 6600) e non sono riuscito a trovare modalità decenti di dual head. Cosa che mi lascia praticamente impossibilitato a usare qualsiasi cosa abbia xorg come ambiente grafico sul pc principale, e quindi tutti i *nix tolto osx.

--
Riccardo Cagnasso


Anonymous coward@ Riccardo Cagnasso By Anonymous coward - posted 26/08/2009 10:42

> Domanda: con il sistema dual head che hai usato, hai un singolo desktop (un singolo x screen) "spalmato" sui due monitor giusto?Che è una schifezza mostruosa perchè diventa praticamente impossibile mettere una qualsiasi applicazioni in fullscreen (per non parlare se uno vuole usare un tiling windows manager). Chiedo perchè un po di tempo fa avevo provato a riavviare la mia vecchia installazione di ubuntu su il mio desktop che ha due monitor (e una scheda video nvidia 6600) e non sono riuscito a trovare modalità decenti di dual head. Cosa che mi lascia praticamente impossibilitato a usare qualsiasi cosa abbia xorg come ambiente grafico sul pc principale, e quindi tutti i *nix tolto osx.

--
Anonymous coward


Davide Bianchi-AT- Riccardo Cagnasso By Davide Bianchi - posted 29/01/2009 07:41

> Domanda: con il sistema dual head che hai usato, hai un singolo desktop (un singolo x screen) "spalmato" sui due monitor giusto?Che è una schifezza mostruosa perchè diventa praticamente impossibile mettere una qualsiasi applicazioni in fullscreen

Quale parte di "IO VOGLIO UN DUALHEAD" non era chiara?

--
Davide Bianchi


Riccardo Cagnasso-AT- Davide Bianchi By Riccardo Cagnasso - posted 29/01/2009 10:59

> Quale parte di "IO VOGLIO UN DUALHEAD" non era chiara?
mmh non capisco. anche io uso due monitor, stavo parlando di "come" viene realizzato il dual head. mi è anche venuto il dubbio che dual head non sia sinonimo di "due monitor" bensì di una particolare modalità. ma wikipedia mi da ragione: http://en.wikipedia.org/wiki/Multi-monitor . A sto punto faccio notare come windows (da schifo in Xp e bene in Vista) e OSX abbiano una gestione un po più furba.Per esempio quando metti fullscreen un'applicazione, questa va a occupare tutto il monitor dove stava la finestra. Le barre del menu (bara di windows e dock su osx) stanno su un "monitor principale" in modo da evitare il fastidioso effetto "spezzettamento" etc etc. Tutto questo mi sembra piuttosto logico: insomma se ho due monitor, voglio due desktop, non un desktop più grosso.

--
Riccardo Cagnasso


Davide Bianchi-AT- Riccardo Cagnasso By Davide Bianchi - posted 29/01/2009 11:12

> > Quale parte di "IO VOGLIO UN DUALHEAD" non era chiara?
> mmh non capisco. anche io uso due monitor, stavo parlando di "come" viene realizzato il dual head.

Il dual-head lo puoi fare come ti pare, puoi anche avere due separati X servers ognuno con il suo display.

--
Davide Bianchi


Cobra78-AT- Davide Bianchi By Cobra78 - posted 29/01/2009 12:23

> > > Quale parte di "IO VOGLIO UN DUALHEAD" non era chiara?
> > mmh non capisco. anche io uso due monitor, stavo parlando di "come" viene realizzato il dual head.
>
> Il dual-head lo puoi fare come ti pare, puoi anche avere due separati X servers ognuno con il suo display.
> --
> Davide Bianchi

Che è quello che ad esempio faccio io col mio Notebook e la shceda nVidia: a casa ho due xserver separati, uno per monitor, totalmente indipendenti, ognuno con i suoi desktop virtuali, poi quando avvio il pc col monitor esterno scollegato l'altro xserver non viene proprio attivato.

Tra l'altro se usi un'nvidia con i driver proprietari è una sciocchezza abilitare questa modalità con l'utility grafica della nVidia stessa :-\)

--
Cobra78


Riccardo Cagnasso-AT- Cobra78 By Riccardo Cagnasso - posted 29/01/2009 12:59

Domanda: totalmente indipendenti significa che non posso comodamente spostare uan finestra da una parte all'altra?

--
Riccardo Cagnasso

Davide Bianchi-AT- Riccardo Cagnasso By Davide Bianchi - posted 30/01/2009 08:25

> Domanda: totalmente indipendenti significa che non posso comodamente spostare uan finestra da una parte all'altra?

Te voi la moglie 'briaca e la botte piena.

--
Davide Bianchi


lucac81 prima o poi mi registroDual Head By lucac81 prima o poi mi registro - posted 02/02/2009 11:38

Io qui al lavoro sto usando una scheda nvidia in dual-head con un singolo X server
Per fare le cose veloci ho usato l'utility inclusa con in driver binary (e mannaggia all'X automatico di ubuntu... quando non rileva il monitor da veramente i numeri) cmq ho un desktop esteso, nel senso che posso spostare le finestre da uno schermo all'altro, ma il fullscreen di ciascuna applicazione sta dentro un singolo schermo, e le barre di gnome sono nello schermo principale, anche la schermata di login di gdm.

La cosa bella di X11 è che te lo puoi veramente configurare come ti pare con piu schermi

--
lucac81 prima o poi mi registro


Riccardo Cagnasso-AT- lucac81 prima o poi mi registro By Riccardo Cagnasso - posted 03/02/2009 10:51

> Io qui al lavoro sto usando una scheda nvidia in dual-head con un singolo X server
> Per fare le cose veloci ho usato l'utility inclusa con in driver binary (e mannaggia all'X automatico di ubuntu... quando non rileva il monitor da veramente i numeri) cmq ho un desktop esteso, nel senso che posso spostare le finestre da uno schermo all'altro, ma il fullscreen di ciascuna applicazione sta dentro un singolo schermo, e le barre di gnome sono nello schermo principale, anche la schermata di login di gdm.

ecco QUESTO cercavo. la modalità dell'utility nvidia è mica "TwinView" o qualcosa del genere? Che non ho potuto provarla perchè mi crashava (scheda video poco standard). Comunque buono a sapersi.

--
Riccardo Cagnasso


lucac81 prima o poi mi registro-AT- Riccardo Cagnasso By lucac81 prima o poi mi registro - posted 03/02/2009 12:33

> > Io qui al lavoro sto usando una scheda nvidia in dual-head con un singolo X server
> > Per fare le cose veloci ho usato l'utility inclusa con in driver binary (e mannaggia all'X automatico di ubuntu... quando non rileva il monitor da veramente i numeri) cmq ho un desktop esteso, nel senso che posso spostare le finestre da uno schermo all'altro, ma il fullscreen di ciascuna applicazione sta dentro un singolo schermo, e le barre di gnome sono nello schermo principale, anche la schermata di login di gdm.
>
> ecco QUESTO cercavo. la modalità dell'utility nvidia è mica "TwinView" o qualcosa del genere? Che non ho potuto provarla perchè mi crashava (scheda video poco standard). Comunque buono a sapersi.
> --
> Riccardo Cagnasso

Si esatto è quello, ho appena controllato, cmq ricordo dalla documentazione che accompagnava i driver qualche tempo fa che si può settare anche direttamente dentro xorg.
Io l'unico problema l'ho avuto perchè l'xorg di ubuntu va in palla se cerca di auto configurarsi con un monitor di cui non riesce a fare il probe (i miei 2 misconosciuti 17" in questo caso) sistemati quelli è andato tutto liscio

--
lucac81 prima o poi mi registro


anonymous-AT- Riccardo Cagnasso By anonymous - posted 03/02/2009 12:36

> > Io qui al lavoro sto usando una scheda nvidia in dual-head con un singolo X server
> > Per fare le cose veloci ho usato l'utility inclusa con in driver binary (e mannaggia all'X automatico di ubuntu... quando non rileva il monitor da veramente i numeri) cmq ho un desktop esteso, nel senso che posso spostare le finestre da uno schermo all'altro, ma il fullscreen di ciascuna applicazione sta dentro un singolo schermo, e le barre di gnome sono nello schermo principale, anche la schermata di login di gdm.
>
> ecco QUESTO cercavo. la modalità dell'utility nvidia è mica "TwinView" o qualcosa del genere? Che non ho potuto provarla perchè mi crashava (scheda video poco standard). Comunque buono a sapersi.
> --
> Riccardo Cagnasso

Dimenticavo ti allego la configurazione dello schermo del mio xorg:

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "CRT-0: 1280x1024 +0+0, CRT-1: nvidia-auto-select +1280+0; CRT-0: nvidia-auto-select +0+0, CRT-1: nvidia-auto-select +1280+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection

Section "ServerFlags"
Option "Xinerama" "0"
EndSection

ovviamente questo è solo quello che riguarda la mod twinview

--
anonymous


Axel DominatoREHCI Bug By Axel DominatoR - posted 02/02/2009 16:57

Davide, puoi trovare due discussioni interessanti al riguardo in questi due link:
https://lists.linux-foundation.org/pipermail/bugme-new/2008-December/020541.html
http://kerneltrap.org/mailarchive/linux-usb/2008/12/3/4297594/thread#mid-4297594

Il problema e' causato dal mancato rispetto degli standard da parte della Intel. Nel primo link c'e' anche un modo per rattoppare il problema ( in maniera temporanea ).
Sembra possa causare qualche disagio, quindi non lo ignorerei completamente come bug.

--
Axel DominatoR ^^^ HC


Davide Bianchi-AT- Axel DominatoR By Davide Bianchi - posted 02/02/2009 17:08

> Il problema e' causato dal mancato rispetto degli standard da parte della Intel.

Aka: c'e' davvero un bug nel BIOS.

> Nel primo link c'e' anche un modo per rattoppare il problema

E dove sarebbe che io non l'ho visto?

--
Davide Bianchi


Axel DominatoR-AT- Davide Bianchi By Axel DominatoR - posted 02/02/2009 17:13

> E dove sarebbe che io non l'ho visto?
> --
> Davide Bianchi

"As the Intel (the author of said spec) is saying that this is just "general
information" that does not relate specifically DG45ID (and, by extension,
probably other motherboards manufactured by Intel) I'd suggest chancing the
value of msec from 5000 to 50 in /drivers/usb/host/pci-quirks.c on line 274.
Doing that would still be compliant to the specification[1] (the time that OS
must wait is not specified so why not assume the OS manufacturer can decide)."

Puoi provare anche tu a diminuire il valore di msec in quel file e dovrebbe essere possibile evitare il problema ( anche se non credo sia comunque una soluzione definitiva. Spero possano correggere il tutto con un aggiornamento del firmware ).

Leggendo su kerneltrap sembra comunque che stiano cercando di discutere della faccenda con il dipartimento Opensource Intel, quindi forse ci saranno novita' presto.

:-)

--
Axel DominatoR ^^^ HC


Davide Bianchi-AT- Axel DominatoR By Davide Bianchi - posted 02/02/2009 17:21

> probably other motherboards manufactured by Intel) I'd suggest chancing the
> value of msec from 5000 to 50 in /drivers/usb/host/pci-quirks.c on line 274.

Ah, no grazie, di fare il kernel-developer non ne ho voglia. E comunque non mi pare che il 'bug' dia tanti problemi.

--
Davide Bianchi


Axel DominatoR-AT- Davide Bianchi By Axel DominatoR - posted 02/02/2009 17:41

> Ah, no grazie, di fare il kernel-developer non ne ho voglia. E comunque non mi pare che il 'bug' dia tanti problemi.

Il problema che da e' che se stai trasferendo dati ad un'unita' di memoria esterna via USB e contemporaneamente stacchi un'altra periferica USB, allora puo' interrompersi il flusso dati. Se eviti di fare attacca/stacca giocattolini mentre trasferisci dati allora dovrebbe essere tutto ok :-\)

--
Axel DominatoR ^^^ HC


Alex ARNZDomande varie. By Alex ARNZ - posted 06/02/2009 14:02

Premetto che non uso Linux, ma FreeBSD eppure questo tuo resoconto dell'installazione mi ha aiutato più di quanto tu non possa pensare a risolvere un problema che avevo anche io con la configurazione dual-head.
Non voglio dilungarmi ma mi sono venute in mente alcune domande a cui, in questi anni non ho mai trovato risposta sul tuo sito:
1. La slack. Perchè?
2. Non ti piace KDE, quindi cosa hai installato?
3. Che programma usi per disegnare quel monitor carino di cui hai messo l'immagine verso la fine del resoconto?

E poi una domanda un po' più "tecnica". Io non ci capisco quasi niente di Database. Mi piacerebbe capirci "un po'" di Database. So che tu sei un esperto. Ci sono libri che conosci che mi potrebbero aituare seriamente? Italiano o Inglese non importa (anche in Tedesco, ma dubito che ne conosci). Niente M$ oriented, please.

--
--
Alex ARNZ
http://www.kuschelbaerchen.net


Davide Bianchi-AT- Alex ARNZ By Davide Bianchi - posted 06/02/2009 14:06

> 1. La slack. Perchè?

Perche'.

> 2. Non ti piace KDE, quindi cosa hai installato?

Twfm

> 3. Che programma usi per disegnare quel monitor carino di cui hai messo l'immagine verso la fine del resoconto?

E' semplicemente uno screen-shot di GKrellm.

> Ci sono libri che conosci che mi potrebbero aituare seriamente?

Leggi le FAQ si icsd che sono nella sezione 'FAQ' del sito:
http://www.soft-land.org/faq/icsdfaq

--
Davide Bianchi


Ammammataanelante... By Ammammata - posted 01/03/2009 21:20

certo che la pianta nella foto (sezione Two heads are better than one) che si protende verso la luce fa proprio tenerezza... ;-\)

--
Ammammata


Kaspaproc/acpi By Kaspa - posted 06/03/2009 21:50

Probabilmente non ti ha interessato il problema, ma sei riuscito per caso a far funzionare i tasti funzione? Sembra che il kernel non abbia attivata la sezione toshiba/proc/acpi, ma non c'è verso di attivarla...

--
blog.thekaspa.it
www.aimps.it


Davide Bianchi-AT- Kaspa By Davide Bianchi - posted 06/03/2009 22:51

> Probabilmente non ti ha interessato il problema, ma sei riuscito per caso a far funzionare i tasti funzione?

? i tasti funzione ? in che senso ?

--
Davide Bianchi


Kaspa-AT- Davide Bianchi By Kaspa - posted 08/03/2009 13:57

> ? i tasti funzione ? in che senso ?

Fn + F1-F12

--
Kaspa


Davide Bianchi-AT- Kaspa By Davide Bianchi - posted 08/03/2009 14:08

> > ? i tasti funzione ? in che senso ?
>
> Fn + F1-F12

F1-F4 non so bene a che dovrebbero servire, il resto funziona.

--
Davide Bianchi


Kaspa-AT- Davide Bianchi By Kaspa - posted 09/03/2009 21:07

> > > ? i tasti funzione ? in che senso ?
> >
> > Fn + F1-F12
>
> F1-F4 non so bene a che dovrebbero servire, il resto funziona.
> --
> Davide Bianchi

A me no....
confido che con Ubuntu 9.04 si risolva il problema... dovrebbe avere il kernel .28 ...

--
Kaspa


blkidinfo prestazioni scheda video By blkid - posted 22/03/2010 10:59

Ciao,
ho visto che hai un portatile tutto intel. E' da tempo che ti seguo e vorrei farti un paio di domande. Come ti va a prestazioni la scheda video? io ho una x3100 con un intel t2390 e dai driver >2.3 è diventato un disastro. Dall'elenco vedo che tu hai i 2.4.3. Potresti dirmi se noti rallentamenti strani nell'uso del DE (io ho gnome) e quanti fps fai in glxgears???

Io attualmente ho fedora13 alpha con gli ultimi driver (2.10) e non vado oltre i 400fps (ho provato pure fedora 12, 11, ubuntu, debian squeeze e non so più che altro), oltre ad avere una lentezza mostruosa che mi sembra di muovere un elefante col mouse invece di finestre (firefox è completamente inutilizzabile).

Avendo tu una gm45 ( la scheda video credo sia una x4500m/mhd) dovresti avere meno problemi, o non averne proprio.

Grazie mille!

--
blkid


Davide Bianchi@ blkid By Davide Bianchi - posted 22/03/2010 11:12

> Come ti va a prestazioni la scheda video?

Non mi lamento, ma non usandolo per giochi non e' che mi preoccupi molto.

> quanti fps fai in glxgears???

# glxgears
6446 frames in 5.0 seconds = 1289.126 FPS

--
Davide Bianchi


28 messages this document does not accept new posts

Previous Next

Davide Bianchi, works as Unix/Linux administrator for an hosting provider in The Netherlands.

Do you want to contribute? read how.  
 


This site is made by me with blood, sweat and gunpowder, if you want to republish or redistribute any part of it, please drop me (or the author of the article if is not me) a mail.


This site was composed with VIM, now is composed with VIM and the (in)famous CMS FdT.

This site isn't optimized for vision with any specific browser, nor it requires special fonts or resolution.
You're free to see it as you wish.

Web Interoperability Pleadge Support This Project
Powered By Gojira