Linux Mint on Chuwi Hi10 & Hi12 Tablets

Linux Mint on Chuwi Hi10 & Hi12 Tablets

TechTablets Forums Chuwi Forums Chuwi Hi10 Discussion Linux Mint on Chuwi Hi10 & Hi12 Tablets

This topic contains 431 replies, has 58 voices, and was last updated by  Brad 2 months, 1 week ago.

Viewing 15 posts - 406 through 420 (of 432 total)
  • Author
    Posts
  • #69515

    Yoghurt
    Participant
    • Posts: 4

    It seems we are close to get a fix. Did you try with the latest kernel (4.13-rc1) ?

     

    Yes. Im on 4.13-rc1. Speakers do NOT work, but headphones do. I also got UCM files installed.

    #69539

    Jerror
    Participant
    • Posts: 14

    I just tried Linuxium’s latest spin (julyshakedown, 4.13rc1). Audio situation is the same as my Arch 4.12 install: no sound by any means, even with the UCM files installed. How are you getting headphone audio? Incidentally, if you don’t see any audio devices listed/can’t change volume with hardware keys, set “realtime-scheduling = no” in /etc/pulse/daemon.conf. Pulseaudio currently has an issue with hdmi-audio on Cherrytrail and this is a workaround.

    On the latest kernels the only thing blocking backlight control is the pwm driver: pwm-lpss and pwm-lpss-platform have to be loaded early (ie., in initramfs) so that they’re available to i915 on init; if they’re not loaded you’ll see “[drm:pwm_setup_backlight [i915]] *ERROR* Failed to own the pwm chip” and have no backlight control. I’m not sure how to get these drivers if they’re not in your kernel, but if they’re available as modules or builtin just add them to initramfs and you’ll get backlight; eg., in the latest Linuxium spin they’re installed as modules (check lsmod), so just add them to initramfs the Ubuntu way:

    • Add lines to /etc/initramfs-tools/modules with the name of each module, pwm-lpss and pwm-lpss-platform
    • sudo update-initramfs -u

    Reboot and enjoy backlight control!

    I found most of this wisdom on Hans de Goede’s blog. He’s been working on Cherry Trail support in Fedora, and is responsible for a lot of recent support in trunk kernel.

     

    #69543

    Brad
    Participant
    • Posts: 436

    what is the audio device/chip in the non working tablet(s)?

    #69749

    Yoghurt
    Participant
    • Posts: 4

    what is the audio device/chip in the non working tablet(s)?

    rt5651

    Someone might look into these files. Especially the UCM/HiFi

    * UCM File. Quite empty EnableSequencefor Speakers.  https://github.com/plbossart/UCM/blob/master/bytcr-rt5651/HiFi#L157

    * Codec source code. https://github.com/torvalds/linux/blob/master/sound/soc/codecs/rt5651.c#L321

    * Board source code. https://github.com/torvalds/linux/blob/master/sound/soc/intel/boards/bytcr_rt5651.c#L53

    * UCM installation. Copy HiFi to /usr/share/alsa/ucm, folder may needs to be created. See https://github.com/plbossart/UCM/tree/master/bytcr-rt5651

    * To apply changes do pulseaudio –kill ; pulseaudio –verbose

    UCM: I tried to add LOUT L/R and OUT to Speaker sequence, but had no success yet. The device is visible in list, the meters also tells there is/should be audio output (when playing a music track), but there is nothing to hear in real.

    EnableSequence [
    cdev “hw:bytcrrt5651”
    cset “name=’Speaker Switch’ on”
    cset “name=’LOUT L Playback Switch’ on”
    cset “name=’LOUT R Playback Switch’ on”
    cset “name=’OUT Playback Volume’ 100”
    ]

    #70030

    myoha
    Participant
    • Posts: 4

    Hi everyone, I red through the whole topic but couldnt find anything about android and linux combo. So my question is, is it possible to delete the win 10 partition from the chuwi hi 12 and install f.ex. linux over the win 10, while keeping the andtoid?

     

    #72468

    Brad
    Participant
    • Posts: 436

    Hi everyone, I red through the whole topic but couldnt find anything about android and linux combo. So my question is, is it possible to delete the win 10 partition from the chuwi hi 12 and install f.ex. linux over the win 10, while keeping the andtoid?

      The answer is (probably) but also depends on your Linux skills. Here is a blog of a guy who did it on a Hi10 Pro installing “BlackArch” distro. Prob requires intermediate to expert Linux knowledge… or a lot of patience?
    https://jonathansblog.co.uk/blackarch-on-the-chuwi-hi10pro

    #72469

    Brad
    Participant
    • Posts: 436

    This might also help. Same guy installing Ubuntu on the Hi10.
    https://jonathansblog.co.uk/ubuntu-on-the-chuwi-hi10-pro

    That said, nowadays with the newer kernels supporting Cherry-Trail there is probably a much easier way. Like using Linuxium’s ISO respin script. (google it)

    #72893

    Yi-Ping Huang
    Participant
    • Posts: 16

    I did some test on my Hi10 Plus. It’s usable now. I have to tether my phone’s internet to the tablet however.

    https://github.com/yiping-huang/arch_on_hi10plus

    #72902

    Brad
    Participant
    • Posts: 436

    I did some test on my Hi10 Plus. It’s usable now. I have to tether my phone’s internet to the tablet however. https://github.com/yiping-huang/arch_on_hi10plus

     You should try Antergos Gnome 17.9.  It is really just Arch underneath.  Maybe it won’t work any better but worth a try.
    About your wifi.  One guy with a Hi12 had to do this… “Booted into Bios/ South Bridge/ LPSS & SCC CONFIGURATION/ SCC SDIO Support = changed acpi to PCI then saved and exit. After reboot, wifi working!”  This page also confirms this (at least on the Hi12 BIOS settings).

    #72905

    Yi-Ping Huang
    Participant
    • Posts: 16

    I did some test on my Hi10 Plus. It’s usable now. I have to tether my phone’s internet to the tablet however. https://github.com/yiping-huang/arch_on_hi10plus

    You should try Antergos Gnome 17.9. It is really just Arch underneath. Maybe it won’t work any better but worth a try. About your wifi. One guy with a Hi12 had to do this… “Booted into Bios/ South Bridge/ LPSS & SCC CONFIGURATION/ SCC SDIO Support = changed acpi to PCI then saved and exit. After reboot, wifi working!” This page also confirms this (at least on the Hi12 BIOS settings).

    Actually I have already done that. And GenZ in page 27 also has the symptom.

    So I think the problem is model specific.

    By the way, WIFI worked in official android and windows dual setup.

    #72930

    Brad
    Participant
    • Posts: 436

    I did some test on my Hi10 Plus. It’s usable now. I have to tether my phone’s internet to the tablet however. https://github.com/yiping-huang/arch_on_hi10plus

    You should try Antergos Gnome 17.9. It is really just Arch underneath. Maybe it won’t work any better but worth a try. About your wifi. One guy with a Hi12 had to do this… “Booted into Bios/ South Bridge/ LPSS & SCC CONFIGURATION/ SCC SDIO Support = changed acpi to PCI then saved and exit. After reboot, wifi working!” This page also confirms this (at least on the Hi12 BIOS settings).

    Actually I have already done that. And GenZ in page 27 also has the symptom. So I think the problem is model specific. By the way, WIFI worked in official android and windows dual setup.

    Have you tried connecting to another wifi router or forcing 802.11g connection instead of “n” or “auto” (config in your router?)?
    If you do something like below terminal commands do you see errors in the output?
    (note: the output text is with my rtl8723be wifi driver and wlp1s0 device (use ‘ifconfig’ to see your wireless device name)…

    ifconfig
    modinfo rtl8723bs
    sudo lspci -v | grep -A9 RTL8723
    dmesg > /dev/null
    sudo modprobe -rv rtl8723bs
    sudo modprobe -v rtl8723bs
    dmesg | grep wlp1s0

    [ 3.169463] rtl8723be 0000:01:00.0 wlp1s0: renamed from wlan0
    [ 4.633189] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [ 5.346417] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [ 5.820084] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [ 5.908554] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [ 17.427845] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [ 18.478138] wlp1s0: authenticate with 18:d6:c7:b5:09:4c
    [ 18.497299] wlp1s0: send auth to 18:d6:c7:b5:09:4c (try 1/3)
    [ 18.500174] wlp1s0: authenticated
    [ 18.503421] wlp1s0: associate with 18:d6:c7:b5:09:4c (try 1/3)
    [ 18.513691] wlp1s0: RX AssocResp from 18:d6:c7:b5:09:4c (capab=0x411 status=0 aid=1)
    [ 18.513926] wlp1s0: associated
    [ 18.513951] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
    [22574.223308] wlp1s0: deauthenticating from 18:d6:c7:b5:09:4c by local choice (Reason: 3=DEAUTH_LEAVING)
    [22574.723599] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [22581.346608] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [22581.926942] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [22582.404530] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [22582.454406] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [22584.949194] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [22586.004107] wlp1s0: authenticate with 18:d6:c7:b5:09:4c
    [22586.023386] wlp1s0: send auth to 18:d6:c7:b5:09:4c (try 1/3)
    [22586.025660] wlp1s0: authenticated
    [22586.032796] wlp1s0: associate with 18:d6:c7:b5:09:4c (try 1/3)
    [22586.042976] wlp1s0: RX AssocResp from 18:d6:c7:b5:09:4c (capab=0x411 status=0 aid=1)
    [22586.043195] wlp1s0: associated
    [22586.043339] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
    [32508.465321] wlp1s0: deauthenticating from 18:d6:c7:b5:09:4c by local choice (Reason: 3=DEAUTH_LEAVING)
    [32518.755121] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [32518.806307] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [32521.299665] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [32522.349110] wlp1s0: authenticate with 18:d6:c7:b5:09:4c
    [32522.369240] wlp1s0: send auth to 18:d6:c7:b5:09:4c (try 1/3)
    [32522.372325] wlp1s0: authenticated
    [32522.374715] wlp1s0: associate with 18:d6:c7:b5:09:4c (try 1/3)
    [32522.384903] wlp1s0: RX AssocResp from 18:d6:c7:b5:09:4c (capab=0x411 status=0 aid=1)
    [32522.385122] wlp1s0: associated
    [32522.385268] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
    [33296.583522] wlp1s0: deauthenticating from 18:d6:c7:b5:09:4c by local choice (Reason: 3=DEAUTH_LEAVING)
    [33318.157339] rtl8723be 0000:01:00.0 wlp1s0: renamed from wlan0
    [33318.197847] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [33318.895785] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [33319.370378] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [33319.427381] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [33321.916118] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
    [33322.991368] wlp1s0: authenticate with 18:d6:c7:b5:09:4c
    [33323.010836] wlp1s0: send auth to 18:d6:c7:b5:09:4c (try 1/3)
    [33323.016776] wlp1s0: authenticated
    [33323.020068] wlp1s0: associate with 18:d6:c7:b5:09:4c (try 1/3)
    [33323.030245] wlp1s0: RX AssocResp from 18:d6:c7:b5:09:4c (capab=0x411 status=0 aid=1)
    [33323.030480] wlp1s0: associated
    [33323.030497] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready

     

     

    #72931

    Brad
    Participant
    • Posts: 436

    Also @Yi-Ping what is your output of this?…

    sudo iw list
    sudo iw dev wlp1s0 scan

    <disable wifi> then run…
    sudo iw event -t
    <enable wifi> then attempt to connect to the AP. Should see something like…

    1506978415.266763: wlp1s0 (phy #0): scan started
    1506978416.256900: wlp1s0 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472, “”
    1506978416.268058: wlp1s0 (phy #0): scan started
    1506978417.263587: wlp1s0 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472, “”
    1506978417.820050: wlp1s0 (phy #0): scan started
    1506978418.813579: wlp1s0 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472, “TP-LINK_094C” “”
    1506978418.833992: wlp1s0: new station 18:d6:c7:b5:09:4c
    1506978418.837258: wlp1s0 (phy #0): auth 18:d6:c7:b5:09:4c -> 00:71:cc:56:d1:fd status: 0: Successful
    1506978418.851006: wlp1s0 (phy #0): assoc 18:d6:c7:b5:09:4c -> 00:71:cc:56:d1:fd status: 0: Successful
    1506978418.851195: wlp1s0 (phy #0): connected to 18:d6:c7:b5:09:4c

    #73068

    Brad
    Participant
    • Posts: 436

    FYI, regarding the Chuwi Hi12 touchscreen driver (Goodix) for Linux, it has been recently reported that it works with Kernel 4.12 but broke in Kernel 4.13.
    There is a workaround for 4.13 but you will have to re-compile the driver –> https://bugzilla.kernel.org/show_bug.cgi?id=156511#c62
    This probably is true also for the Hi10… uses same Goodix TS device, no?
    Hopefully it will get fixed again in 4.14 or later.

    #73199

    Yi-Ping Huang
    Participant
    • Posts: 16

    Sorry for late replying.

    Simply enabling 802.11b/g in the router does the trick.

    I didn’t even remember I set the router to 802.11n only mode.

    I don’t know about goodix touchscreen.

    But for Hi10Plus, gslx680 driver is working fine in both 4.13 and 4.14 rc2.

    #73200

    Brad
    Participant
    • Posts: 436

    Sorry for late replying. Simply enabling 802.11b/g in the router does the trick. I didn’t even remember I set the router to 802.11n only mode. I don’t know about goodix touchscreen. But for Hi10Plus, gslx680 driver is working fine in both 4.13 and 4.14 rc2.

      Great. Glad you got it working and didn’t even have to mess with all that Linux terminal command debugging 😉 Sorry, I thought the Hi10 uses the Goodix touchscreen not the Silead GSL1680.  Maybe just the Hi12 uses Goodix.

Viewing 15 posts - 406 through 420 (of 432 total)

You must be logged in to reply to this topic.

Lost Password