Windpad 110W eGalax Touchscreen drivers

Came across this while I was trying to get Linux working on my Windpad 110W recently...
http://home.eeti.com.tw/web20/eg/Touch_Drives.html
This site has working drivers for Linux, which enabled me to successfully install and use Ubuntu Linux on my Windpad. But I also noticed that they have drivers for various Windows versions (as well as for DOS!). Now, while Windows 7 natively seems to include touchscreen drivers, I don't have Windows 7 currently installed on my Windpad for testing, so thought this might be useful for others.
If you do decide to try these out, please post any feedback in this topic, especially if they improve on Windows' rather weak handling of this particular touchscreen.

I tried the drivers out. It seemed to have better tacking than the integrated Windows drivers, however, they did not support the multi-touch functionality.

Similar Messages

Windows 8 final on Windpad 110W

I'd like to report a 90% successful install of Windows 8 x64 Professional on the Windpad 110W. What I can't get working is revealed at the bottom.
Lessons learned:
The built in SSD card is very bad - it's actually slower than a mechanical hard drive, Windows 8 can barely run on it
I swapped my default Transcend mSATA card out with an Adata Sx300 64 gb chip, it works spectacularly, now the CPU is the bottleneck, as expected
Don't try installing 32-bit Windows 8 on this machine, many devices will not work properly
A clean install of Windows 8 (in my case from an external DVD) will get you all of the drivers you need except the GPS card and SD card reader, which are available on MSI's website
If the wireless doesn't work right try installing the O-Easy software to toggle it on; I'd suggest avoid using O-Easy as you can't close it normally, you must force-quit
Currently the Firefox 18 beta for Modern UI does not recognize the keyboard; all other apps seem to work alright
Runs HD video quite smoothly! Can balance a fair number of apps before the processor gets overwhelmed
Stuff that doesn't work:
I can only get either camera to work on the lowest image quality settings, with the built-in app or Skype - I'm using the latest AMD video/chipset drivers (it didn't work with the ones provided on MSI'swebsite either)
The switch to lock your view in one direction or another doesn't seem to work with any app I can find
The resolution is too low to dock an app to the side of another in the Modern UI interface
If anyone has any suggestions on how to get the higher resolutions for the camera to work let me know - thanks!
If you have any questions about how I managed to get various subsystems or apps running just ask.

I installed Windows 8 Pro x64 Upgrade from a USB flash drive on my WindPad Friday, and today I have almost everything working. I have some notes on my WindPad review post if you care to look there.
My experience:
* You have to install all of MSI's drivers, Microsoft's .NET 2 and MSI's oEasy and Dual Camera Switch for everything to work (auto-rotate, etc).
* Rotate lock switch works.
* The SSD is OK-ish, it's just Windows that sucks. Make sure you do a fresh install so that the partitions are correctly aligned to the blocks. How do I know it's Windows that's sucking? I also have Linux Mint on it, and it flies no problems.
* Once everything is installed and Windows isn't downloading anything in the background, it's fairly zippy except for file operations. The Metro UI is *always* zippy, unlike the desktop - I suspect it's completely loaded in RAM, as Task manager shows 1.1GB in use right after boot.
* The webcams worked on my machine originally, but failed after the first reboot... dwah?
* The missing USB/serial device is most likely the GPS/Bluetooth. If I remember correctly, it auto-installed after I used oEasy to turn on BT & GPS.

EEE 701 - Help getting eGalax touchscreen to work?

I just installed a touchscreen from dealextreme on my wife's old eee 701 and I'm hoping someone else around here has done so and has some insight as to drivers for this thing?
the device shows up with lsusb but I'm kinda lost where to go from here.
Last edited by ctarwater (2009-12-22 06:28:36)

ok gborzi, thanks for all your help earlier...I got it!
for anyone else interested, here's how I did it.
1) install xf86-input-evtouch from AUR
2) install ttf-freefont and xdialog
3) blacklist the usbtouchscreen module
4) run the touchscreen calibration script
5) open the /etc/evtouch/config file and delete everything after the 4th line (MAXY="xxxx")
6) open /usr/share/hal/fdi/policy/20thirdparty/50-eGalax.fdi and add the following 2 lines to the end:
<merge key="input.x11_options.swapy" type="string">true</merge>
<merge key="input.x11_options.rotate" type="string">CCW</merge>
I hope this helps anyone else trying to install a eGalax touchscreen.
here is my full eGalax.fdi file if anyone is interested: http://pastebin.com/f591374d8
here is my full evtouch config: http://pastebin.com/f17b8136e
These should work on all eGalax touchscreens installed on an eee701 since the hardware is the same.
here is a screenshot of my daughter's new computer. Thanks!
Last edited by ctarwater (2009-12-24 03:07:09)

[SOLVED] Samsung q1 ( egalax ) touchscreen not working with Xorg 1.6

I was using egalax touchscreen driver 2.06.2410 in my samsung Q1 :
http://home.eeti.com.tw/web20/eGalaxTou … Driver.htm
With the Xorg update to 1.6 version touchscreen stop working. If you want it back you can use this egalax_drv.so i got from eeti:
http://rapidshare.com/files/228797256/e … rv.so.html
Liquibyte and Kriblom kindly provided alternative (and probably better ) hosting:
http://www.liquibyte.com/driver/egalax_drv.so
http://dont-looze-touch.ovh.org/egalax_drv.so
It do worked for me using the 2.06.2410 driver and overwriting the old egalax_drv.so in /usr/lib/xorg/modules/input. I'm on 32 bit and i don't know if this do work in 64 bit too.
Last edited by ernia (2009-05-04 06:09:27)

Actually I've just gotten it. I'll just post mine in case it's useful to someone else.
Section "ServerLayout"
InputDevice "EETI" "SendCoreEvents"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "False"
Option "DontZap" "false"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
Modes "1024x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
Modes "1024x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1024x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
Modes "1024x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1024x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x600"
EndSubSection
EndSection
### Touch Configuration Beginning ###
Section "InputDevice"
Identifier "EETI"
Driver "egalax"
Option "Device" "usbauto"
Option "Parameters" "/var/lib/eeti.param"
Option "ScreenNo" "0"
EndSection
### Touch Configuration End ###
Editing for brevity.
Last edited by liquibyte (2009-05-03 19:54:42)

Windpad 110W : keyboard disappear from the screen

I bought a new computer which is Msi Windpad 110W
And I format the hard disk which was included windows 7 Home premium 64 bit
and I installed windows 7 starter 32 bit
but I am facing a problem after the format which is disappearing the key board from the screen
So, I need your help about this problem
thank you.

You mean no on-screen keyboard?
And yes, why Windows 7 Starter? It is a very crippled version of Windows, probably doesn't include the needed accessibilty features to provide the on-screen keyboard.
I should just reinstall Windows 7 Home Premium 64bit, if that's what yours came with.

How to flash bios in windpad 110w ?

Hello
I got windpad 110w today. I do not know to go bios page.
My camera do not work I think update bios.
I see "Press <Del> to enter Setup" But I can not push Del Because my windpad no have keyboard.
Somebody help me.
Thank you.
PS. I do not good English. Sorry.

You don't need to update the BIOS, you need to turn the camera on.
I believe from looking in the manual that you can do this by pressing the 'O-key', and then selecting the webcam there.

Repurpose the O-Key on the windpad 110W to act as the windows key

Hello everyone,
I have spent the last two weeks of my spare time to write a piece of software that you can run on your windpad 110W in order to repurpose the O-Key, which normally makes o-easy.exe visible, to work as the windows key. Install it, log out, log in again, change to the desktop and then press the O-Key, it will flip you forth and back between metro and desktop, just like the windows key from an ordinary keyboard (or the windows sensor key from my surface with windows rt).
I will not accept bug reports from people who complain that it doesn't work right after login without having invoked the desktop at least once. This doesn't even work if you have a USB keyboard attached to a Windows 8 box. Apart from that, let me know if you like it or not and whether it works for you or not. It comes with full source code and is distributed under the terms and conditions of GPL version 3. And it is digitally signed! Wow.
I almost forgot to tell: The name of the project is "So-Lazy". So google for the terms "so-lazy" and "windpad" and you should find it.
Stefan

Quote from: sku on 01-December-12, 18:41:53
I didn't mean that it doesn't work with a USB keyboard attached to it. I just initially thought, that immediately after logging in, when metro appears, a press on the button should get me to the desktop, and I spent a lot of time trying to find out why that doesn't work. After a while, I decided to try the same thing with a USB keyboard attached and found out that right after login, a press of the windows button doesn't get you to the desktop as well, so even with an ordinary keyboard you first have to type Windows-D to get to the desktop. But from then on you can flip between desktop and metro with the windows-key (or the o-key).
Anyone running Windows 8 x86 on the Windpad 110W and willing to try? I have only tested on x64 so far.
Stefan
Because the Windows key is actually not for toggling between "Metro" and "Desktop". It is for toggling between "Metro" and "Current screen". Before you do anything after login, the Metro is the only screen so nothing would happen by pressing the windows key

MOVED: How to turn on bluetooth feature in Windpad 110W and problem switching cameras

This topic has been moved to MSI Tablet PCs.
https://forum-en.msi.com/index.php?topic=167273.0

Windows 7 or Windows 8?
You'll need to install O-Easy to turn on/off the bluetooth module:
http://www.msi.com/product/windpad/WindPad-110W.html#/?div=Utility&os=Win7%2032

Windpad 110W Win 8.1 upgrade can no longer boot under AHCI

I recently upgraded my 110W to Win 8.1, but then discovered that it would not boot after the first reboot. As found in some forums, changing to IDE mode in BIOS allows it to boot, but performance is somewhat slower. I have tried chaning the storahci registries and restarting under AHCI (as suggested in numerous forums) but it didn't work. I think it is possibly related to some driver issue as there were issues when I tried to update to drivers newer than those on the MSI site (I now have the MSI drivers loaded). Any suggestion as to how that can be solved?
Also, shutdown and restart seems strange. The screen would go dark pretty quickly (as usual), but the power light on the side would stay on for about 2 minutes before it would reboot / shutdown. As suggested by some, I have turned off quick boot, but it is still the case.
Thanks.

It's possible that the driver isn't compatible for windows 8.1, so either you can try to find the driver for windows 8.1 or I would suggest to roll back to windows 8.

Win 8 Pro on Windpad 110W installation troubleshooting, PLEASE HELP

Please bare w/ me for a moment to give you a little history. I've got a 110W w/ Win 8 RP on it. I bought the Windpad used. The previous owner put replacaed the original hard drive w/ a 120GB, and I've been quite pleased w/ its performance. Initially it came w/ the Win 8 CP, and I downloaded the upgraded RP a couple months ago when all my Metro Apss quit working on CP. Now I'd finally like to upgrade to Win 8 Pro and be finished. I'm also attempting to change from the 32-bit OS to the 64-bit. Here is where I encounter trouble. If I try to install it from w/in the current OS it detects I'm running 32-bit and halts the installation w/ an error message. Therefore I've put the 3.3GB Win 8 Pro 64-bit.iso file on a USB thumb drive and am attempting to boot it from outside the OS, and bypass its detection. (as a side note: the reason I want the 64-bit is because I'd like to upgrade the RAM to 8GB). Anyhow, the previous owner also installed a dual boot for the device called Android-x86 which i don't care to have anymore as it really hasn't been a practical Android experience. Unlike my Android experiences w/ other tablets and phones; I love Android. Furthermore this dual boot has partitioned the hard drive too and a few GBs are dedicated to the Android portion. I'd like to do away with this Android-x86 dual boot, but am not sure how. Finally, I hooked up a keyboard and the USB drive w/ Win 8 Pro to the USB port via a USB hub, and selected F11 when the tablet loaded up. I was able to select between loading the USB drive or the SSD. I chose the USB hoping it would start a fresh install of WIN 8 Pro 64-bit. It didn't it went to the next screen that always appears after the MSI boot-loader image; the Android-x86 screen where it defaults to boot windows if I don't select Android after 5 seconds. I just want to be done w/ the Android-x86, and get a clean install of Win 8 Pro only on my machine. Any tips, pointers, or guidance in the right direction is greatly appreciated.
Thanks,
Rick

I'm going to attempt to recover the system w/ the Win 7 DVD recovery discs that come w/ the MSI machine, since that version of Win 7 is 64-bit. I don't have an external DVD drive so I'm putting the files on my USB stick, and hoping that I can just install them on the Windpad from it. If Win 7 successfully installs, because it's already 64-bit, I can just upgrade over the internet w/o getting the Microsoft error message that I can't install a 64-bit OS on a 32-bit system. I hope this works!

Can't get eGalax touchscreen Lilliput Eby701 working on linux 3.7x64

I recently purchased a 7" touchscreen for my carputer project which I am trying to use under arch. It is the Lilliput Eby701-np/c/t model.
DE: Ich kaufte vor kurzem ein 7 "Touchscreen für meine carputer Projekt, das ich versuche, unter Bogen verwenden werde. Es ist das Lilliput Eby701-np/c/t Modell.
I am running kernel 3.7.7-1 with nouveau loaded in kernel mode setting if it makes any difference. I cannot build xf86-input-evtouch from AUR and the eGalax driver doesn't function with my kernel (when I enable it, the touchscreen doesn't recognize input of any kind). The eGalax graphical driver utility runs and recognizes that the touchscreen is in fact connected via USB, but crashes every time I try to run the 4 point calibration.
DE: Ich bin mit Kernel 3.7.7-1 mit Jugendstil im Kernel-Modus-Einstellung geladen, wenn es einen Unterschied macht. Ich kann nicht bauen xf86-input-evtouch von AUR und eGalax Fahrer nicht mit meinem Kernel funktionieren (wenn ich sie zu aktivieren, der Touchscreen nicht erkennen Eingabe aller Art). Die eGalax grafische Treiberprogramm läuft und erkennt, dass der Touchscreen in der Tat über USB angeschlossen ist, sondern stürzt jedes Mal, wenn ich versuchen, die 4-Punkt-Kalibrierung laufen.
The only driver which "worked" was the one loaded by default (evdev) as soon as I plugged the touchscreen into my USB port. Unfortunately, the Y axis was inverted, the X and Y axes were swapped and the calibration wasn't even close to right. To "fix" the problem, I did the following:
DE: Der einzige Treiber, die "funzt" war das standardmäßiges evdev, sobald ich den Touchscreen steckt in meinem USB-Port. Leider wurde die Y-Achse invertiert, die X-und Y-Achsen wurden ausgetauscht und die Kalibrierung wurde nicht einmal nach rechts zu schließen. Um das Problem zu "melden", habe ich die folgenden gemacht:
Created a bash script:
sudo xinput set-prop 9 "Evdev Axes Swap" 1
sudo xinput set-prop 9 "Evdev Axis Inversion" 0, 1
sudo xinput set-prop 9 "Evdev Axis Calibration" 75, 1977, 105, 1860
created a *.service file in /etc/systemd/system/gdm.target.wants:
[Unit]
Description=Calibrates the touchscreen
[Service]
ExecStart=/home/sam/calibration.sh
[Install]
WantedBy=gdm.target
Then I enabled the service and restarted the computer. The service did not calibrate the touchscreen on boot (wheel with no password is enabled in sudoers for test purposes) and I had to log in in order to run the script. Then, when I logged out again, it reset the calibration making it impossible to use the gdm login without a keyboard.
DE: Dann habe ich den Systemdienst aktiviert und den Computer neu gestartet. Der Dienst hat nicht den Touchscreen bei booten kalibriert (wheel ohne Passwort in sudoers zu Testzwecken aktiviert) und ich musste einloggen, um das Skript auszuführen. Dann, wenn ich wieder abgemeldet hat, has es die Kalibrierung wiederhergestellt, und das gdm Login ohne echtes Tastatur unmöglicht.
This is clearly not the best way to deal with the problem. Has anybody else gotten this to work?
DE: Das ist auf jeden fall nicht das beste möglichkeit um das Problem zu melden. Hat jemand dieses Problem meldet?
EDIT: Falls sie nur Deutsch verstehen kann, hab ich das deutsche Übersetzung von Google Übersetzer oben und ein paar Fehler davon korrigiert. Ja, ich bin faul. lol
Last edited by kg6zvp (2013-02-14 19:15:42)

Thanks for your link but i don't think it has something to do with relinking libraries since i never had to to that on my first machine. I'm currently pursuing a different approach: I'm comparing the files used by ccpd and cups on both machines with each other. These are the results:
On the machine with working capt service:
http://pastebin.com/Fyif7zxz
http://pastebin.com/n0KQj14z
On the machine with defect capt service:
http://pastebin.com/rtUW5Gfm
http://pastebin.com/vh94E3Jv
One thing that i noticed is the two libraries resolv and nss which are used on the defect machine. Could it be that?
Last edited by Picoli (2013-02-24 22:49:25)

EGalax Touchscreen Detected But Not Working

I installed Arch Linux x64 in Lenovo S400 Touch, it has a "eGalax Inc. eGalaxTouch" Thouchscreen, i have tried most of the thread, yet i cant figure out how to get it to work!
Here is the output from lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b420 Chicony Electronics Co., Ltd
Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 0eef:a107 D-WAV Scientific Co., Ltd
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Here is the output from Xorg Log
[ 33.081] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00 (/dev/input/event5)
[ 33.081] (**) eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: Applying InputClass "evdev touchscreen catchall"
[ 33.133] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 15 paused 0
[ 33.134] (II) Using input driver 'evdev' for 'eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00'
[ 33.134] (**) eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: always reports core events
[ 33.134] (**) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: Device: "/dev/input/event5"
[ 33.134] (--) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: Vendor 0xeef Product 0xa107
[ 33.134] (--) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: Found absolute axes
[ 33.134] (--) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: Found absolute multitouch axes
[ 33.134] (II) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: No buttons found, faking one.
[ 33.134] (--) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: Found x and y absolute axes
[ 33.134] (--) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: Found absolute touchscreen
[ 33.134] (II) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: Configuring as touchscreen
[ 33.134] (**) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: YAxisMapping: buttons 4 and 5
[ 33.134] (**) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 33.134] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/0003:0EEF:A107.0001/input/input6/event5"
[ 33.134] (II) XINPUT: Adding extended input device "eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00" (type: TOUCHSCREEN, id 9)
[ 33.134] (II) evdev: eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: initialized for absolute axes.
[ 33.135] (**) eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: (accel) keeping acceleration scheme 1
[ 33.135] (**) eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: (accel) acceleration profile 0
[ 33.135] (**) eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: (accel) acceleration factor: 2.000
[ 33.135] (**) eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00: (accel) acceleration threshold: 4
[ 33.135] (II) config/udev: Adding input device eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00 (/dev/input/mouse0)
[ 33.135] (II) No input driver specified, ignoring this device.
[ 33.135] (II) This device may have been added with another device file.
[ 33.136] (II) config/udev: Adding input device Lenovo EasyCamera (/dev/input/event12)
[ 33.136] (**) Lenovo EasyCamera: Applying InputClass "evdev keyboard catchall"
[ 33.136] (**) Lenovo EasyCamera: Applying InputClass "system-keyboard"
[ 33.137] (II) systemd-logind: got fd for /dev/input/event12 13:76 fd 16 paused 0
[ 33.137] (II) Using input driver 'evdev' for 'Lenovo EasyCamera'
Here is the output from xinput --list
xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ eGalax Inc. eGalaxTouch EXC7910-1018-08.00.00 id=9 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Lenovo EasyCamera id=10 [slave keyboard (3)]
↳ Ideapad extra buttons id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]
Here is the output from xrandr
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 32767 x 32767
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm
1366x768 60.10*+
1024x768 60.00
800x600 60.32 56.25
640x480 59.94
DP1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Here is the output of lsmod
Module Size Used by
fuse 87590 3
ctr 12927 2
ccm 17534 2
coretemp 12820 0
hwmon 12930 1 coretemp
intel_rapl 17605 0
iosf_mbi 12682 1 intel_rapl
arc4 12536 2
brcmsmac 536435 0
cordic 12352 1 brcmsmac
brcmutil 13136 1 brcmsmac
b43 414640 0
mac80211 648753 2 b43,brcmsmac
x86_pkg_temp_thermal 12951 0
intel_powerclamp 17122 0
cfg80211 476584 3 b43,brcmsmac,mac80211
kvm_intel 143417 0
uvcvideo 84822 0
snd_hda_codec_hdmi 49263 1
ssb 65506 1 b43
rng_core 12808 1 b43
videobuf2_vmalloc 13286 1 uvcvideo
videobuf2_memops 12519 1 videobuf2_vmalloc
videobuf2_core 39635 1 uvcvideo
pcmcia 53108 2 b43,ssb
v4l2_common 12814 1 videobuf2_core
videodev 135040 3 uvcvideo,v4l2_common,videobuf2_core
pcmcia_core 18431 1 pcmcia
media 18365 2 uvcvideo,videodev
joydev 17063 0
snd_hda_codec_realtek 67322 1
snd_hda_codec_generic 63161 1 snd_hda_codec_realtek
rtsx_usb_ms 16899 0
memstick 13696 1 rtsx_usb_ms
bcma 46203 3 b43,brcmsmac
mousedev 17272 0
r8169 76869 0
kvm 435299 1 kvm_intel
mii 12675 1 r8169
iTCO_wdt 12831 0
iTCO_vendor_support 12649 1 iTCO_wdt
crct10dif_pclmul 13394 0
crc32_pclmul 12915 0
shpchp 35210 0
snd_hda_intel 26387 3
snd_hda_controller 26857 1 snd_hda_intel
ideapad_laptop 17447 0
snd_hda_codec 112621 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
ac 12715 0
crc32c_intel 21809 0
psmouse 107442 0
snd_hwdep 17244 1 snd_hda_codec
snd_pcm 88779 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
snd_timer 26614 1 snd_pcm
snd 73436 14 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
ghash_clmulni_intel 12978 0
thermal 17559 0
cryptd 18553 1 ghash_clmulni_intel
pcspkr 12595 0
serio_raw 12849 0
battery 17452 0
mei_me 17987 0
mei 75468 1 mei_me
soundcore 13031 2 snd,snd_hda_codec
sparse_keymap 12818 1 ideapad_laptop
rfkill 18867 3 cfg80211,ideapad_laptop
i2c_i801 16965 0
evdev 21544 13
lpc_ich 20768 0
mac_hid 12633 0
processor 27777 0
sch_fq_codel 17343 6
ext4 514390 1
crc16 12343 1 ext4
mbcache 17171 1 ext4
jbd2 86379 1 ext4
rtsx_usb_sdmmc 25280 0
led_class 12855 3 b43,brcmsmac,rtsx_usb_sdmmc
mmc_core 110613 3 b43,ssb,rtsx_usb_sdmmc
rtsx_usb 17487 2 rtsx_usb_sdmmc,rtsx_usb_ms
hid_multitouch 17057 0
usbhid 48596 0
hid 110513 2 hid_multitouch,usbhid
sd_mod 43575 2
atkbd 22254 0
libps2 12739 2 atkbd,psmouse
ahci 33248 1
libahci 27215 1 ahci
libata 181461 2 ahci,libahci
xhci_pci 12675 0
ehci_pci 12512 0
scsi_mod 147395 2 libata,sd_mod
xhci_hcd 152471 1 xhci_pci
ehci_hcd 69979 1 ehci_pci
usbcore 199382 7 uvcvideo,rtsx_usb,ehci_hcd,ehci_pci,usbhid,xhci_hcd,xhci_pci
usb_common 12561 1 usbcore
i8042 18002 2 libps2,ideapad_laptop
serio 18282 6 serio_raw,atkbd,i8042,psmouse
i915 1002518 3
button 12953 1 i915
intel_gtt 17848 1 i915
i2c_algo_bit 12744 1 i915
video 22205 1 i915
drm_kms_helper 98881 1 i915
drm 273079 5 i915,drm_kms_helper
i2c_core 50240 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev
I have blacklisted "usbtouchscreen" module
It seems to be detected, but i have no idea how to make it work, it isnt even registering any kind of touch event, i even tried installing eGalax driver from AUR, it still didnt work.
Please help me by pointing me in the right direction!
Any help is appreciated. Thank you!
Last edited by kshergil (2015-04-20 19:08:28)

i posted output of that command without starting X
Here is complete output after starting X
[samtech@M4800 ~]$ journalctl -b | grep -i bluetooth
Dec 10 21:37:45 localhost kernel: Bluetooth: Core ver 2.19
Dec 10 21:37:45 localhost kernel: Bluetooth: HCI device and connection manager initialized
Dec 10 21:37:45 localhost kernel: Bluetooth: HCI socket layer initialized
Dec 10 21:37:45 localhost kernel: Bluetooth: L2CAP socket layer initialized
Dec 10 21:37:45 localhost kernel: Bluetooth: SCO socket layer initialized
Dec 10 21:37:45 localhost kernel: Bluetooth: hci0: read Intel version: 370710018002030d00
Dec 10 21:37:45 localhost kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Dec 10 21:37:45 localhost kernel: Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
Dec 10 21:39:12 localhost NetworkManager[308]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
Last edited by samtech09 (2014-12-10 16:52:30)

Windpad 110W Tablet LCD light leak and dead pixels

Hello,
I've just received the 110W tablet (I'm in the USA) and the LCD exhibits what I'll call light leak, where the backlight leaks or bleeds through so that when viewing a dark background you can see white light around the perimeter of the display. The white light is in blotches and shows up around the display in various places. My tablet most noticeably shows light leak on the left side of the display. Has anyone else had this problem with their Windpad tablets?
I've seen this in several other tablets I've had (Eee Transformer, Xoom FE), and it may just be something we live with, but I'd like to get your feedback before I return it to find the replacement exhibits the same light leak problem.
Also, how about dead pixels? Mine has a dead (always black) pixel up at the top of the display which doesn't really bother me at all. Again, I'm just looking for your experience with these issues.
Thanks!

Quote from: blakebart on 06-September-12, 11:05:49
Interesting that you would return it for the dead pixel.
Absolutely, on a screen this size it would be very annoying. I have only ever had a dead pixel at work and made them change it.
I have no idea what MSI's dead pixel policy is though so that may affect whether you can return it or not.

TouchScreen Drivers for Windows 7

Hello, I installed Windows 7 in multiboot and I tried the touchscreen but it didn't work. I need a driver for my HP Pavilion n011dx x360. Please help as soon as possible!!!

Hi:
See if installing this graphics driver works for you...
http://h20566.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=5449369&swItemId=ob_132253_1&swEnvOid=405...

MOVED: How to flash bios in windpad 110w ?

This topic has been moved to Tablets Windpad.
https://forum-en.msi.com/index.php?topic=151361.0

You don't need to update the BIOS, you need to turn the camera on.
I believe from looking in the manual that you can do this by pressing the 'O-key', and then selecting the webcam there.

Windpad 110W eGalax Touchscreen drivers

Similar Messages

Maybe you are looking for