[BBaker]

What errors are you seeing in the dmesg log? I’ve noticed a bug in the I2C bus on various Cherry-Trail devices that had caused various drivers/modules from loading/working properly.

[BBaker]

Ricardo Simões wrote:

BBaker wrote:

…Given this bug, I would recommend you change from using the Linuxium release to a main Ubuntu release. I would download and install this one (Ubuntu 16.10 Beta2): http://releases.ubuntu.com/yakkety/ubuntu-16.10-beta2-desktop-amd64.iso

ubuntu 16.10 final came out today!!! Just in time for testing this, I’m currently downloading MATE version, and will test it tomorrow or over the week end, and report back here

Woohoo!

[BBaker]

Turns out Ubuntu 16.10 Final (not Beta) was just released today. So that’s the version to go with needless to say 🙂 I personally would recommend the Ubuntu or lighter weight Ubuntu Mate versions.
http://distrowatch.com

[BBaker]

update: I just create the install instructions for the Hi12 Goodix Touchscreen driver here:
https://forums.linuxmint.com/viewtopic.php?f=49&t=223426&p=1227190#p1227190
Note: this is not the final version of course. This is an “unofficial” version for testing made by @sergk who has a Hi12 and says it’s working.

[BBaker]

Hot news for Chuwi Hi12 owners! @sergk user over on the LM forum just reported getting the Goodix touchscreen driver working properly. It requires recompiling the driver and installation of a firmware file – he did it using the September 22 latest release of Ubuntu 16.10 Beta2. When the install procedure is nailed down I’ll post it. You can download the Ubuntu 16.10 Beta2 64bit ISO here: http://releases.ubuntu.com/yakkety/ubuntu-16.10-beta2-desktop-amd64.iso

In the meantime here’s the LM forum thread link:
https://forums.linuxmint.com/viewtopic.php?f=49&t=223426&p=1227178#p1227128

[BBaker]

Your dmesg log output shows an error that I’ve seen before with Chuwi tablets and also on other machines doing an internet search on it.
I think this failure on what I think is a low level I2C communication bus is causing the problem with the WiFi and other devices from properly loading.
It needs further research to find out what’s causing it but I have seen it’s a known Kernel bug.

“i2c_designware: probe of 808622C1:06 failed with error -110”

Given this bug, I would recommend you change from using the Linuxium release to a main Ubuntu release.
I would download and install this one (Ubuntu 16.10 Beta2): http://releases.ubuntu.com/yakkety/ubuntu-16.10-beta2-desktop-amd64.iso

[BBaker]

deleted

[BBaker]

Ricardo Simões wrote:

Ok here’s what I did: I executed lspci -nn -d 14e4: in the terminal but no output

I checked for broadcom firware files in /lib/firmware (output from ls in attachment) and found there a folder named brcm (output from ls also in attachment)… can you please check if there’s anything missing or misplaced?

Meanwhile I booted to Windows 10 again and went to device manager, it shows wi-fi as a Broadcom 802.11n Wireless SDIO Adapter and hardware IDs have values of SD\VID_02d0&PID_a9a6&FN_1 and SD\VID_02d0&PID_a9a6

Is there a linux driver for this?

I’ve also included a screenshot

<noscript></noscript>

what is your output from this instead:
lspci -nn -vv
And also what is the contents of this file:
cat /etc/modprobe.d/blacklist.conf

[BBaker]

These directions (for Ubuntu 16.04) might work for use without an internet connection. Do it on another machine and copy to USB drive…

run these Terminal commands:
cd ~
sudo apt-get purge bcmwl-kernel-source

then download these two files on another Windows or Linux machine with Internet access and use a USB drive to copy them to your home (~) directory. You can use FTP, browser, or ‘wget’ command if using Linux:
http://mirrors.kernel.org/ubuntu/pool/main/b/b43-fwcutter/b43-fwcutter_019-2_amd64.deb
http://www.lwfinger.com/b43-firmware/broadcom-wl-5.100.138.tar.bz2
after these to files are in your home directory do this:
sudo dpkg -i b43-fwcutter_019-2_amd64.deb
tar xfvj broadcom-wl-5.100.138.tar.bz2
sudo b43-fwcutter -w /lib/firmware broadcom-wl-5.100.138/linux/wl_apsta.o
sudo reboot

then after reboot if WiFi is still not working run:
dmesg > dmesg_log.txt && gedit dmesg_log.txt
and post the content to http://www.pastebin.com and post the URL here.
Also post the contents of the file /etc/modprobe.d/blacklist.conf

[BBaker]

I found a more explicit directions for getting the Broadcom B43 driver installed…

output of the lspci -nn -d 14e4: command should look something like this, does it?…

02:00.0 Network controller [0280]: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)

If yes, then follow these steps: [edit:] damn, I forgot without internet connection this won’t work. Can you use a USB Wifi adapter or some other way to get internet connection?…

sudo apt-get purge bcmwl-kernel-source
sudo apt-get update
sudo update-pciids
sudo apt-get install firmware-b43-installer
sudo reboot

[BBaker]

OK nothing shows up there identifying the device. Nothing is recognized. So let’s follow the Linux Kernel Wireless doc’s to see what we can find…
https://wireless.wiki.kernel.org/en/users/drivers/b43

Summary

You need to have firmware files (usually in /lib/firmware/) so b43(legacy) can upload them to the card and run properly.

List of hardware

To check for a present hardware model execute following command:

lspci -nn -d 14e4:

You should see something similar to my machine (with Realtek rtl8723be wifi) using different “10ec:” address…
brad@G50 ~ $ lspci -nn -d 10ec:
01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723]
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 10)

You’re output should identify which Broadcom Device BCM43XX you have (from that Kernel.org page linked above). Note: it’s also possible that it’s not on this list because it’s a recent/new device:

14e4:0576 not tested BCM43224 a/b/g/n ? wl/brcm80211
14e4:4301 yes (b43legacy) BCM4301 b B
14e4:4306 yes (b43legacy) BCM4306/2 b/g G
14e4:4307 yes BCM4306/3 b/g G
14e4:4311 yes BCM4311 b/g G wl
14e4:4312 yes BCM4311 a/b/g G (r8) wl
14e4:4313 not tested BCM4311 a ? wlno BCM4313 b/g/n LCN (r1) wl/brcm80211
14e4:4315 yes BCM4312 b/g LP (r1) wl
14e4:4318 yes BCM4318 b/g G (r7)
14e4:4319 yes BCM4318 a/b/g G
14e4:4320 yes (b43legacy) BCM4306/2 b/g G (r1) yes BCM4306/3 ? G (r2)
14e4:4321 partially BCM4321 ? N (r2)
14e4:4322 yes (3.18+) BCM4322 b/g/n N (r4) wl
14e4:4324 yes (b43legacy) BCM4306 a/b/g G (r1) yes BCM4306/3 a/b/g G (r5)
14e4:4325 yes (b43legacy) BCM4306/2 b/g G (r1)
14e4:4328 partially BCM4321 a/b/g/n N (r2) wl
14e4:4329 partially BCM4321 b/g/n N (r1) wl
14e4:432a not tested BCM4321 a/n N wl
14e4:432b partially BCM4322 a/b/g/n N (r4) wl
14e4:432c yes BCM4322 b/g/n N wl
14e4:432d not tested BCM4322 a/n N wl
14e4:4331 yes (3.2-rc3+) BCM4331 a/b/g/n HT (r1) wl
14e4:4350 yes (3.8+) BCM43222 a/b/g/n N (r6)
14e4:4353 yes (3.1+) BCM43224 a/b/g/n N (r6) wl/brcm80211
14e4:4357 yes (3.1+) BCM43225 b/g/n N (r6) wl/brcm80211
14e4:4358 yes (3.17+) BCM43227 b/g/n N (r16) wl
14e4:4359 yes (3.17+) BCM43228 a/b/g/n N (r16) wl
14e4:4360 no BCM4360 ? AC (r1)
14e4:4365 no BCM43142 b/g/n LCN40 (r3) wl
14e4:43a0 no BCM4360 a/b/g/n/ac AC? wlno BCM4352 a/b/g/n/ac ? wl
14e4:43a9 yes (3.17+) BCM43217 b/g/n N (r17)
14e4:43aa yes (3.17+) BCM43131 b/g/n N (r17)
14e4:43b1 no BCM4352 a/b/g/n/ac AC (r3) wl
14e4:4727 no BCM4313 b/g/n LCN (r1) wl/brcm80211
14e4:a8d6 not tested BCM43222 ? N (6)
14e4:a8d8 yes (3.6+) BCM43224 a/b/g/n N (r6) brcm80211 yes (3.6+) BCM43225 ? N (r6) brcm80211
14e4:a8db partially (3.18+) BCM43217 b/g/n N (r17)
14e4:a99d not tested BCM43421? ? ? wl

[BBaker]

@laroslov, come on man. I gave you a lot of help. At least you can reply and say if it worked or not?… so other people can know if it worked.

[BBaker]

Ricardo Simões wrote:

BBaker wrote:

For any BayTrail and CherryTrail devices this would be my recommendation to start with: http://techtablets.com/forum/topic/ubuntu-16-10-beta-2-for-intel-baytrail-and-cherrytrail-devices-2/

I’ve tried th new Ubuntu 16.10 Beta 2 for Intel Baytrail and Cherrytrail Devices from linuxium booting from a live usb and still no wi-fi, no sound, and no touchpad

Do you think it’s advisable to try to install it and then look for patches?

Yes. Install it. Then you can attempt to install the drivers/patches. Which WiFi device do you have? Is it the Realtek rtl8723bs? Open a Terminal window (Ctrl+Alt+T) and run this command and paste the output here:
lshw > lshwinfo.txt && gedit lshwinfo.txt

[BBaker]

@laroslov, is your WiFi working now?

[BBaker]

Matthai wrote:

I also tried Ubuntu 16.10 Beta 2, but it does not boot.

Probably better you report this to Linuxium in the comments on his page: http://linuxiumcomau.blogspot.com.br/2016/10/ubuntu-1610-beta-2-for-intel-baytrail.html or perhaps on his G+ page https://plus.google.com/+IanMORRISON or Facebook page: https://www.facebook.com/Linuxium/

[Author]

Posts