Forum Replies Created
-
AuthorPosts
-
January 29, 2017 at 2:32 pm #61183
What works: Bluetooth, Battery Percentage(didnt work on arch before), ( touchpad if you have the yepo 737s).
A sound adapter is finally shown as “Analog Output”, but has no audible output, neither through speakers or headphone jack.
Microphone is also not detected.Wifi is detected but doesn’t find Networks, when I create a Hotspot my other wifi devices also won’t see it
January 29, 2017 at 2:07 pm #61179It doesn’t seem like it’s too hard to fix! I’m glad you realised what it is, probably it has something to do with the screen settings, check for those. I await reply Alsetema.
Nope, not screen settings, I got it to work again narrowed it down to one of these 4 options that I changed from acpi to pci again:
In Advanced -> Chipset :
- ̶A̶u̶d̶i̶o̶ ̶-̶>̶ ̶L̶P̶E̶ ̶A̶u̶d̶i̶o̶ ̶S̶u̶p̶p̶o̶r̶t̶ (Also works without setting this to PCI, and Sound Device is still shown)
- ̶S̶C̶C̶ ̶-̶ ̶>̶ ̶S̶C̶C̶ ̶e̶M̶M̶C̶ (Also without that)
- SCC – > SCC SDIO <– Appareantly this is the reason, just like for the wifi. Screen stays black if this is set to acpi.
- S̶C̶C̶ ̶-̶ ̶>̶ ̶S̶C̶C̶ ̶S̶D̶ (Also check this just to be sure, also doesn’t matter)
So at least one of them seems to do the trick
January 29, 2017 at 1:53 pm #61177, just plain black. I waited for half an hour to see if it was just loading, but nothing. After this, I rebooted (by holding the power button since ctrl + alt + del did nothing and neither did alt + sys rq +b) and this time I chose the Install Ubuntu option instead. What happened is that it still didnt work, the Ubuntu load screen appears, but suddently the screen turns off. I could confirm the lapblet was still on since it had the little blue light on its right on, but same thing, it didn’t respond to any key combo, so I decided to turn it off.
I just tried it, with the right bios settings it booted without issues. A soundcard showed up, but no sound output. wifi was there, but didn’t find networks. Bluetooth appareantly worked. Touchpad and Hotkeys also worked.
Now i changed my bios back to defaults, and the issue you described occurs.
So i have to find out which bios setting it was that made it work, I had several settings set to pci instead of acpi.January 25, 2017 at 3:57 pm #60920@jreith okay this setting mentioned above in bios did not change the appearance in /sys/bus/sdio/devices. under /sys/bus/acpi/devices there are several devices listed but i can not figure out which is the right one.
ls /sys/bus/sdio/devices/ returns just one entry mmc2:0001:1 for me.
ls /sys/bus/sdio/drivers/ just shows a folder rtrtl8723bs, and in there is a symlink to /sys/bus/sdio/devices/mmc2:0001:1.In /sys/bus/acpi/devices there are several entrys starting with 80860F14: that are related to wifi.
Those things are the same, wether I use my patched kernel or the standard 4.8 kernel.
However if I change SDIO back from pci to acpi, /sys/bus/sdio/drivers/ is empty like expected.
January 25, 2017 at 3:25 pm #60918Today I recieved and replaced the screen (Chimei Innolux n133hse-*), my Yepo 737s works again.
Appareantly it seems like the Ezbook 2 has a different touchpad than the Yepo 737s. For me it also worked in the Antergos Live USB.
The wifi only works halfways: it is detected now, i can turn it on and off, but it doesn’t find any Networks. Therefore I’m also keeping a look at https://github.com/hadess/rtl8723bs.
Yes i compiled my own kernel, but I used the patches from https://github.com/ferbar/rtl8723bs/tree/master/patches_4.7, as the current arch kernel is 4.8 and things appareantly changed since the 4.5 kernel.Bluetooth also works now, you just have to clone https://github.com/lwfinger/rtl8723bs_bt and execute start_bt.sh on each boot(or auto start it, but still a bit dirty imho).
Sadly i didn’t get any further with sound yet, as it is hard to find any information, I tried it with search terms like “Intel Cherrytrail audio linux”, same with baytrail, “ES8316” but accurate information is rare. I tried to rebuild my kernel with several cherrytrail related patches, but they had no additional visible effect for me. Also i found it hard to keep track which patches relate to which kernel, and which patches would make other patches obsolete, etc…
For the touchpad, maybe it could help to play with the settings in Bios -> Advanced -> Chipset Configuration, for example “I2C Touch Devics”.
What i dont know is, if these settings just tell the mainboard which hardware device is actually connected, or if it changes the way the bios exposes the devices to the operating system.
January 18, 2017 at 1:46 pm #60632Ricardo, Im sorry for the issues you had, but dont spread this kind of wrong information and make everyone panic. BTW I also gave you explanations on how to fix your bios again, it doesn’t involve much time or money…
@Peter Willig, you changed the right setting as far as I remember, maybe look if it’s listed under /sys/bus/acpi/devicesIm taking short break on this since i destroyed my display, Im still awaiting my replacement screen to swap it out. Should arrive end of the month…
December 30, 2016 at 12:10 pm #59518No it should not. I had a similar issue on my Teclast X98 Air II when i updated using a wrong bios and bricked it. I just had to open the back, connect the flasher to the USB of my PC, and place the clip on the chip – Just like a clothespin. If it doesnt work, just try again and place it to the opposite site/turn it 180 degree. Sounds more complicated than it actually is.
December 30, 2016 at 11:45 am #59515A suitable usb to spi flasher should probably cost less than 10 bucks. The bios image is available in this forum.
Dont overdramatize this, you will get it back to work again somehow 😀
December 29, 2016 at 10:17 pm #59494Well, last Ressort would always be to manually flash the eeprom.
Maybe this thread is helpful: http://techtablets.com/forum/topic/bios-cmos-reset/
December 29, 2016 at 10:00 pm #59490Relax, it is most certainly not bricked.
Can you still reach the bios by pressing ESC during Boot? Which device did you switch to PCI? – there are many options in the bios.
If you can still reach bios, connect an external display using the mini HDMI or try to use the bios “blind” or reset CMOS. Is it possible that you changed the Gfx to PCI and not SDIO?
December 29, 2016 at 9:02 pm #59487The Touchpad worked out of the box in Antergos for me, also on the live usb. Sadly we cant rule out that the touchpad of the ezbook 2 and the yepo 737s differ…
December 29, 2016 at 8:06 pm #59484Well, wifi is alread figured out, See my previous post. After i compiled a patched kernel and changed the connection type to pci in bios, it is detected. We will probably need further patches as it wont find any networks.
Sound is still complicated, it could be an rt5640, which is used in Baytrail and also the z8500 cherrytrail. Maybe our z8300 SoC is using the same.
December 29, 2016 at 6:59 pm #59481I used my android phone wih USB tethering. You could also use a supported wifi stick.
Trackpad: Verify that xf86-input-libinput is installed and in use, if it still fails uninstall all other packages starting with xf86-input
December 29, 2016 at 6:00 pm #59476Wow, just wrote a long post explaining what I got working so far, after submittinh it was gone…
I have the Yepo 737s, which has similar specs.So, short form: Use latest Antergos with Kernel 4.8, Touchpad and standy work out of the box, Keyboard shortcuts also work including backlight control.
I got Bluetooth to work, Wifi is also detected now but doesnt find any APs.
Wifi: https://github.com/hadess/rtl8723bs, Bt: https://github.com/lwfinger/rtl8723bs_bt. You need to build your own kernel with the patch 0001-My-changes-for-4.7.0-rc7-for-Baytrail-T.patch
Still investigating Battery and sound. Maybe I will rewrite this post more detailed when my frustration is gone that the previous, detailed post just vanished. ATM Im buidling a new kernel including more patches, will report back.
-
AuthorPosts

