Difference between revisions of "ASUS EeeTop ET1602"

From LinuxMCE
Jump to: navigation, search
 
(14 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
[[Category: Hardware]]
 
[[Category: Hardware]]
 +
{{Versioninfo}}
 
[[Category: Cores]]
 
[[Category: Cores]]
 
[[Category: Media Directors]]
 
[[Category: Media Directors]]
 +
 +
 +
[[Image:Eeetop-1602.jpg]]<BR>
  
 
  {| align="right"
 
  {| align="right"
 
   | __TOC__
 
   | __TOC__
 
   |}
 
   |}
−
 
−
{{stub}}
 
  
 
=== Introduction ===
 
=== Introduction ===
Line 17: Line 19:
  
 
=== Configuring the touch screen ===
 
=== Configuring the touch screen ===
 +
 +
==== Add your Eee Top as an MD ====
 +
Connect your Eee Top to the LAN side of your Core (set it for PXE boot in BIOS first of course) and power it up. The Eee Top should start to PXE boot and you will see the following yellow text on screen - "We have announced ourselves to the Router..." and you should see that the script "DisklessSetup.sh" is running. This stage will take some time... be patient. The Eee Top will then reboot and continue the setup process. After a few mins the Eee Top will be sitting there in the AVwizard... with a blank screen. Now we are ready to continue onto the next step...
 +
 +
==== Use Web Admin to identify the ID of your Eee Top ====
 +
Go to Web Admin on your Core and then to Wizard -> Devices -> Media Directors and scroll down to the bottom of the page. The last Media Director listed will be your recently added Eee Top. Make a note of the number with a '#' in front of it next to the drop down that is used to select the room the MD should be in. This number is the 'Moon' number or unique ID of the MD.
 +
 +
==== SSH into your Eee Top ====
 +
Go to your Core (or ssh into your Core from another computer), open a Konsole window and sudo yourself;
 +
sudo su -
 +
 +
==== chroot yourself to the Eee Top ====
 +
Use chroot to gain access to your Eee Top so that we can make the changes in the following steps;
 +
chroot /usr/pluto/diskless/<Moon No. from above step>
 +
 +
Your prompt should change and you are now working on the Eee Top's file system.
  
 
==== Install the evtouch driver ====
 
==== Install the evtouch driver ====
Line 146: Line 164:
 
  <b> DefaultDepth 24
 
  <b> DefaultDepth 24
 
  SubSection "Display"
 
  SubSection "Display"
−
  Modes "1366x768"
+
  Modes "1024x768"
−
  Virtual 1366 768
+
  Virtual 1024 768
 
  EndSubSection</b>
 
  EndSubSection</b>
 
  Option "XvmcUsesTextures" "true"
 
  Option "XvmcUsesTextures" "true"
Line 184: Line 202:
 
  Option "RENDER" "true"
 
  Option "RENDER" "true"
 
  EndSection
 
  EndSection
 +
 +
* Note: The native resolution of the panel is 1366x768, but with the vesa driver you have to use 1024x768 or you'll get into trouble (the Launch Manager crashes on startup). Starting with Ubuntu 9.10 you can use the intel driver intead of vesa, and you should be able to run with the native resolution.
  
 
==== Finalize ====
 
==== Finalize ====
 
* Reboot
 
* Reboot
 +
* Complete the AVwizard selecting UI1
 
You need to reboot so that udev creates the symlink properly. That, or you open up the EeeTop to disconnect and reconnect the USB port (if there is a USB header in there of course)
 
You need to reboot so that udev creates the symlink properly. That, or you open up the EeeTop to disconnect and reconnect the USB port (if there is a USB header in there of course)
 
* Enjoy your touchscreen
 
* Enjoy your touchscreen

Latest revision as of 17:09, 28 September 2010

Version Status Date Updated Updated By
710 Unknown N/A N/A
810 Unknown N/A N/A
1004 Unknown N/A N/A
1204 Unknown N/A N/A
1404 Unknown N/A N/A
Usage Information
Eeetop-1602.jpg

Introduction

Asus launched a really nice gadget called the EeeTop ET1602 (There's also a ET1603, with a battery and an ATI video card, but that's for a premium).

LinuxMCE would run nicely on this thing, if it weren't for the screen turning off when X starts with the intel driver. Ironically, it works fine with the vesa driver.

The touchscreen works perfectly with the evtouch driver. The calibration data seems to be stored in the device itself, and the calibration utility is Windows-only, but it shouldn't need any refining unless you want pixel-perfect touching.

Configuring the touch screen

Add your Eee Top as an MD

Connect your Eee Top to the LAN side of your Core (set it for PXE boot in BIOS first of course) and power it up. The Eee Top should start to PXE boot and you will see the following yellow text on screen - "We have announced ourselves to the Router..." and you should see that the script "DisklessSetup.sh" is running. This stage will take some time... be patient. The Eee Top will then reboot and continue the setup process. After a few mins the Eee Top will be sitting there in the AVwizard... with a blank screen. Now we are ready to continue onto the next step...

Use Web Admin to identify the ID of your Eee Top

Go to Web Admin on your Core and then to Wizard -> Devices -> Media Directors and scroll down to the bottom of the page. The last Media Director listed will be your recently added Eee Top. Make a note of the number with a '#' in front of it next to the drop down that is used to select the room the MD should be in. This number is the 'Moon' number or unique ID of the MD.

SSH into your Eee Top

Go to your Core (or ssh into your Core from another computer), open a Konsole window and sudo yourself; 

sudo su -

chroot yourself to the Eee Top

Use chroot to gain access to your Eee Top so that we can make the changes in the following steps; 

chroot /usr/pluto/diskless/<Moon No. from above step>

Your prompt should change and you are now working on the Eee Top's file system.

Install the evtouch driver

apt-get install xserver-xorg-input-evtouch

Configure udev

Configure udev so it creates a stable symlink. The /dev/input/eventX entry may change, so this symlink will be used to point to it Create the /etc/udev/rules.d/69-touchscreen.rules file with this content: 

KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="1bfd", ATTRS{idProduct}=="1688", SYMLINK+="input/evtouch"

Setup xorg.conf

My xorg.conf looks like this right now (The changes relevant to the Eee Top are in bold): 

Section "ServerLayout"
	Identifier	"XFree86 Configured"
	Screen	  0	"Screen0"	0 0
	InputDevice	"Mouse0"	"CorePointer"
	InputDevice	"Keyboard0"	"CoreKeyboard"
	InputDevice	"Touch0"
EndSection

Section "Files"
	#RgbPath		"/usr/X11R6/lib/X11/rgb"
	ModulePath	"/usr/lib/xorg/modules"
	FontPath	"/usr/share/fonts/X11"
	FontPath	"/usr/X11R6/lib/X11/fonts/misc/"
	FontPath	"/usr/X11R6/lib/X11/fonts/Speedo/"
	FontPath	"/usr/X11R6/lib/X11/fonts/Type1/"
	FontPath	"/usr/X11R6/lib/X11/fonts/CID/"
	FontPath	"/usr/X11R6/lib/X11/fonts/75dpi/"
	FontPath	"/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection

Section "Module"
	Load	"dbe"
	Load	"extmod"
	Load	"record"
	Load	"xtrap"
	Load	"speedo"
	Load	"type1"
	Load	"glx"
	Load	"int10"
	Load	"v4l"
	Load	"dri"
EndSection

Section "InputDevice"
	Identifier	"Keyboard0"
	Driver		"keyboard"
	Option		"XkbLayout"		"us"
	Option		"XkbVariant"	"basic"
	Option		"XkbModel"		"pc105"
EndSection

Section "InputDevice"
	Identifier	"Mouse0"
	Driver		"mouse"
	Option		"Protocol"		"auto"
	Option		"Device"		"/dev/input/mice"
	Option		"ZAxisMapping"	"4 5"
EndSection

Section "InputDevice"
	Identifier	"Touch0"
	Driver		"evtouch"
	Option		"device"	"/dev/input/evtouch"
	Option		"MinX"	"1"
	Option		"MinY"	"1"
	Option		"MaxX"	"4096"
	Option		"MaxY"	"4096"
	Option		"ReportingMode" "Raw"
	Option	"Emulate3Buttons" "false"
	Option	"Emulate3Timeout" "50"
	Option	"SendCoreEvents" "on"
	Option	"MoveLimit" "0"
EndSection

Section "Monitor"
	Identifier	"Monitor0"
	VendorName	"Unknown Monitor Vendor"
	ModelName	"Unknown Monitor Model"
	Modeline 	"1280x720" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
	Modeline	"800x600" 38.22 800 832 910 1024 600 601 604 620 -hsync +vsync
	HorizSync	20-500
	VertRefresh	60
EndSection

Section "Device"
	#Option		"NoAccel"
	#Option		"SWcursor"
	#Option		"ColorKey"
	#Option		"CacheLines"
	#Option		"Dac6Bit"
	#Option		"DRI"
	#Option		"NoDDC"
	#Option		"ShowCache"
	#Option		"XvMCSurfaces"
	Identifier	"Card0"
	#Driver		"intel"
	Driver		"vesa"
	VendorName	"Unknown Vendor Name"
	BoardName	"Unknown Board Name"
	Option		"LinearAlloc"		"16384"
	#BusID		"PCI:0:2:0"
#	Option		"NoDDC"				"true"
	Option "XvmcUsesTextures" "true"
	Option "renderAccel" "true"
	Option "NoDDCValue"
	Option "UseEDID" "false"
	Option "ExactModeTimingsDVI" "true"
	Option "NoLogo" "true"
	Option "NoBandWidthTest" "true"
	Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"
	Option "DynamicTwinView" "false"
	Option "UseEvents" "true"
	Option "AllowGLXWithComposite" "true"
	Option "AddARGBGLXVisuals" "true"
	Option "Monitor-Unknown-1" "Disabled Monitor"
	Option "Monitor-VGA" "Disabled Monitor"
	Option "Monitor-TV" "Disabled Monitor"
	Option "Monitor-LVDS" "Monitor0"
EndSection

Section "Screen"
	Identifier	"Screen0"
	Device		"Card0"
	Monitor		"Monitor0"
	DefaultDepth	24
	SubSection "Display"
		Modes		"1024x768"
		Virtual		1024 768
	EndSubSection
	Option "XvmcUsesTextures" "true"
	Option "renderAccel" "true"
	#Option "NoDDCValue"
	#Option "UseEDID" "false"
	Option "ExactModeTimingsDVI" "true"
	Option "NoLogo" "true"
	Option "NoBandWidthTest" "true"
	Option "ModeValidation" "NoDFPNativeResolutionCheck, NoEdidMaxPClkCheck, NoMaxPClkCheck, AllowInterlacedModes, AllowNon60HzDFPModes"
	Option "DynamicTwinView" "false"
	Option "UseEvents" "true"
	Option "AllowGLXWithComposite" "true"
	Option "AddARGBGLXVisuals" "true"
	Option	"TVStandard"	"720p"
EndSection

Section "ServerFlags"
	Option	"AllowMouseOpenFail"	"true"
	Option	"BlankTime"		"0"
	Option	"StandbyTime"	"0"
	Option	"SuspendTime"	"0"
	Option	"OffTime"		"0"
	Option	"AIGLX"			"Off"
EndSection
Section "Monitor"
	Identifier	"Disabled Monitor"
	Option		"Enable" "false"
	Option		"Ignore" "true"
	Modeline 	"1280x720" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
	HorizSync	20-500
	VertRefresh	59-61
EndSection
Section "Extensions"
	Option "Composite" "false"
	Option "RENDER" "true"
EndSection
  • Note: The native resolution of the panel is 1366x768, but with the vesa driver you have to use 1024x768 or you'll get into trouble (the Launch Manager crashes on startup). Starting with Ubuntu 9.10 you can use the intel driver intead of vesa, and you should be able to run with the native resolution.

Finalize

  • Reboot
  • Complete the AVwizard selecting UI1

You need to reboot so that udev creates the symlink properly. That, or you open up the EeeTop to disconnect and reconnect the USB port (if there is a USB header in there of course)

  • Enjoy your touchscreen
Retrieved from "http://wiki.linuxmce.org/index.php?title=ASUS_EeeTop_ET1602&oldid=25333"