search

jakeday / linux-surface

Linux Kernel for Surface Devices
2.6k stars 243 forks source link

Touch screen not working surface book and surface pro 4 #487

Open AmroLouwe opened 5 years ago

AmroLouwe commented 5 years ago

I am completly new to this, so excuse my lack of knowledge, I just started using it few days ago I have a surface book and a surface pro 4 I have manged to follow the instructions from Jakeday with the latest kernel however touch screen and pen are not working at all on both devices. I am running a chrome os fork FydeOS on both devices as dual boot maybe this information helps

But can you help me

jamfor352 commented 5 years ago

Out of curiosity, how were you able to install the kernel on ChromeOS in the first place? Perhaps I am misunderstanding, but, isn't it only possible to install the kernels in the Linux container anyway? I couldn't get it working at least, would love to know how you did it!

AmroLouwe commented 5 years ago

As i said i am very new to all of this.... What i did is Installing the chrome OS fork fydeos on my computer Then there is an option to enable linux kernel apps in the settings, Then i get linux container Where i installed the linux-surface from jakeday, just like the instructions , but now the touch screen and pen are not working

jamfor352 commented 5 years ago

Can you check your Linux version in the Linux terminal with uname -r Then check the Linux version in the crosh shell (press Ctrl+Alt+T and a terminal will open up in a new window in Chrome, type 'shell' if you're in dev mode, then run the same command above)

Are they different values?

AmroLouwe commented 5 years ago

Yes they are of diifferent values!!!! What does that mean??

jamfor352 commented 5 years ago

So the Linux container, Crostini, is a container. This means it is separate from the underlying OS (ChromeOS) and as such new modules/kernels installed to it are not loaded in ChromeOS. Hence why you can't get touch working in ChromeOS.

There are ways of installing other kernels in ChromeOS. I'm actually experimenting with this myself on my Surface Pro 4, and will get back to you if I find a solution (I'm a software developer myself so this is a nice challenge!)

AmroLouwe commented 5 years ago

Oh thank you so much. I really hope you succeed. Thank you for the information at.. i hope you find the solution. Because for me the surface devices Is the best devices to run chrome os. Not the other devices in the market. Hardware wise.... I love my surface book and pro 4. But seeing that windows dropped the ball on creating a decent assistant vs Google assistant Or a surface phone (which i would be the first to jump to buy it) However chrome os and devices dont run all the functions i would need like legacy programs aphotoshop etc... So having it Dual boot was the best option I run windows when i need more power, and chrome when needing speed and sync with my phone. I am running my micro SD as a way to transfer files between the two OS locally.. it is a neat solution

AmroLouwe commented 5 years ago

Looking forward to hearing good news from you no matter how long it takes

jamfor352 commented 5 years ago

Just to clarify I'm not putting my all in this, I'm just messing around with it. If I even do succeed at getting the kernel to boot, that doesn't necessarily mean all the modules will work the way they do in regular Linux distros at the moment (for example, ChromeOS uses its own display server, Freon, rather than X/Wayland which might have compatibility issues). Might be that the touchscreen won't work no matter what. We'll see, though.

AmroLouwe commented 5 years ago

I understand that... But knowing someone is out there tryig to get it to work is great. At first i thought i was the only one having this issue and thought its because i couldn't understand the steps good enough

jamfor352 commented 5 years ago

Just so you know and don't hold out too much hope for too long, I wasn't able to get it working at all. Hopefully somebody more experienced & patient than me can manage better!

AmroLouwe commented 5 years ago

@jf352 Thanks a lot for trying...