mushi

mushi

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #74383
    mushi
    Participant
    • Posts: 10

    It’s not because of rEFInd, I’ve had same behaviour with GRUB

    #74382
    mushi
    Participant
    • Posts: 10

    I confirme the issue. I use Ubuntu 17.10 and at every reboot I lost the touchpad, sometimes in Windows (10) too… To avoid the problem the laptop isn’t powered down… Only sleeping… The only way I have found to restore touchpad is to boot with USB key with Ubuntu 17.10 (isorespined). This problem happens only when I boot on Ubuntu… I also suspect rEFInd… I’m not a specialist but it seems not possible to boot Ubuntu 17.10 with Grub (Apollo Lake problem)… If you find a solution plz post… ?

    Yep, on unlocked bios select “Intel Linux” in “Chipset OS Selection” parameter. After that at GRUB starts to work fine, I’ve successfuly installed Ubuntu 17.10 from vanilla image.

    #73201
    mushi
    Participant
    • Posts: 10

    For the touchpad problem on Linux/Ubuntu: Did you follow the directions he did on this post?  And the Grub startup param change on this post?

    There is no problem with touchpad in linux on V4. In KDE Neon touchpad worked perfectly w/o anything required on my side.
    After booting ubuntu it got stuck, and didn’t work even under windows, so this

    sudo modprobe -r psmouse
    sudo modprobe psmouse proto=imps

    obviously had no impact at all.

    #73175
    mushi
    Participant
    • Posts: 10

    Can comfirm this issue.
    Booting/installing Ubuntu 17.10 completely killed my touchpad, it wasn’t working even after reinstalling W10 (but device was present, so Windows did install drivers).

    Disconecting battery and pressing power button few times did trick for me, so maybe disconecting touchpad flex pcb/cable isn’t really necessary.
    Hope this never happens again during usage of Windows 10, ehe.

    Just for stats: system had rEFInd installed/booted with, but I don’t think that’s the root of problem.

    #72920
    mushi
    Participant
    • Posts: 10

    Even remastered version would run just fine.

    #72845
    mushi
    Participant
    • Posts: 10

    @dendrite
    I’ve seen at least one user claiming, that he got laptop to charge fully (LED color change and status in windows that battery is fully charged) by using charger from his friend’s ezbook 3 pro that charges properly.

    My led is in an unknown state, since I would get laptop on my hands only on 3 October.

    #72831
    mushi
    Participant
    • Posts: 10

    nswer to question 1: Mine does this also. I believe it’s a reporting issue from the battery itself but I haven’t seen any problems crop up from it.

    I’ll take a shot at  Question 1.

    That’s normal behavior for this laptop. The orange LED does not change color when the battery reached 100%.

    Actually users from 4PDA (russian forum about gadgets) say that it’s faulty charger.
    With some chargers (that came with laptop) LED does change color, with most of them it doesn’t.

    If someone have appropriate equipment (I guess something that can emitate load up to 36 watts?) and have this problem check that voltage is consistent 12v. If it’s lower, then it’s probably reason why it doesnt charge to full and change color.

    (I understand that there must be an step-down converter, because battery is only 7.4v, but still)

    #72818
    mushi
    Participant
    • Posts: 10

    Do you also know what is the hole on the top-right of the notebook, just near the power connector?

    Pretty sure it has no function, since it seems there is nothing mounted on PCB.

    https://techtablets.com/wp-content/uploads/2017/07/mainboard-3.jpg

    #72787
    mushi
    Participant
    • Posts: 10

    2. On the top of the notebook there are 5 led lights. One is always blue, the other four are always down. What they are supposed to do?

    Mic, mic, power, caps and scroll lock.

    #72745
    mushi
    Participant
    • Posts: 10

    I’m pretty sure you’ve removed EFI partition, so now notebook doesnt know what to boot from and drops to EFI console. It’s nowhere close to being a brick.

    Here’s how I see it:

    You’ve had windows on EMMC, then you had put SSD and installed another copy of windows on it. During install process installer sees that you already have windows installation on EMMC, so instead of making SSD bootable by creating another EFI partition on it, installer used existing EFI partition on EMMC to put info about new OS.

    Simpliest fix is just to reinstall windows on SSD (since you’ve already formated EMMC it would make new EFI on drive you point at, i.e. SSD).

Viewing 10 posts - 1 through 10 (of 10 total)

Lost Password

Skip to toolbar