Fedlet: a Fedora Remix for Bay Trail tablets

Fedlet development is currently DORMANT

PLEASE NOTE: At present (October 2016), I do not have any time to work on Fedlet. Through the magic of Google, this looks like a current effort to get Linux (Ubuntu) running on Baytrail / Cherrytrail devices; you might want to try that.

EDIT FEB 2017: I still don’t have time for Fedlet, sorry. However, Nemanja Milosevic is doing stuff, and he links to this page, of another person who is…doing stuff. Hope this helps you.


Can you run Linux on a tablet? Sure you can!

Here’s video proof.

This is Fedlet, a Fedora remix for Intel Bay Trail-based tablet devices with 32-bit firmwares. Particularly the Dell Venue 8 Pro, which is what I have. It has been reported to work on the Lenovo Miix 2 and Asus T100. It may work on the Toshiba Encore and any other 32-bit firmware Bay Trail-based tablet.

It’s based on Fedora 23, more or less – but it has a slightly patched kernel, and a few other tweaks. Some of the Bay Trail support is not yet complete, and testers on various devices have reported instability. So this is not yet stable release quality, but it’s appropriate for playing around with these devices. Seriously, I mean it’s pretty experimental and nothing is guaranteed. This is for playing around and helping to make things better, it’s not a production OS. Please don’t install this if for some reason your Intel tablet is your primary work device or something.



Eleventh release of Fedlet.

  • Fedlet 20150810 for all 32-bit Baytrail hardware – SHA256SUM: 7b2b6a45df4738865481b9af17536f2f011b6c24a3c29fb9d6644dd21da2e545
  1. Fedora 23 Alpha-ish userland
  2. Kernel 4.2rc6
  3. Seems to be a bug where no OSK appears for Firefox; try installing Epiphany


Tenth release of Fedlet.

  • Fedora 20141209 for all 32-bit Baytrail hardware – SHA256SUM: c1fcf78e883d28345074bb48c814732a2dced2c79f54ee007c769e31a4fd134b
  1. Fedora 21(ish) userland – with 0-day updates
  2. Kernel 3.18.0, with Fedlet patches


Ninth release of Fedlet.

  • Fedlet 20141124 for all 32-bit Baytrail hardware – SHA256SUM: c64b859d5ec08dd1c6e15eb8e0553d1b775475e22c852062166a9ae63bfeac6a
  1. ~Fedora 21 Final TC4 userland
  2. Kernel 3.18rc6
  3. NVRAM map for Broadcom brcmfmac43241b4 (thanks “Brainwreck” of the Ubuntu T100 project) which may make wifi work OOTB on Asus T100
  4. Accelerometer-based rotation support for Venue 8 Pro (i.e. display rotates when you rotate the tablet)
  5. Backlight level control on Venue 8 Pro when booted with i915.force_backlight_pmic=1


Eighth release of Fedlet.

  • Fedlet 20141111 for all 32-bit Baytrail hardware – SHA256SUM: 3a4078db12b1ed17d9c330ef9c16d2690299212ec6f58867d64f2589a6afc088
  1. ~Fedora 21 Final TC1 userland
  2. Kernel 3.18rc4
  3. Patch from Jan-Michael Brummer to make Venue 8 Pro wifi work
  4. Has generic-release-cloud not generic-release-workstation, sorry, I’ll fix it for the next release


Seventh release of Fedlet, aka the “God, I’m still doing this?” release

  • Fedlet 20140929 for all 32-bit Baytrail hardware – SHA256SUM: aa2f1150e40965471fc2888db6aad7da52d98f36ce1224b630ba5ed99b28fd5e
  1. Current Fedora 21 userland, ~F21 Alpha
  2. Kernel 3.17rc6
  3. efibootmgr is back, so install might work (not tested)
  4. Patch from Jan-Michael Brummer for ‘Home’ button on V8P to act as ‘Super’ (start) key
  5. Patch from Jan-Michael Brummer for mic input (not tested yet)


Sixth release of Fedlet

  • Fedlet 20140911 for all 32-bit Baytrail hardware – SHA256SUM: d76574e38d5afab1cb84ac95dde3945376c76518d2610c8afdaa84305ba3f43e
  1. Updated to current Fedora 21 userland, ~= Fedora 21 Alpha TC7
  2. Based on Workstation kickstart
  3. Updated to 3.16 kernel with small Baytrail patch set, native modesetting should now work, no more hard-coded resolution hacks needed
  4. Sound driver and firmware included (but you still need to load a correct ALSA config to hear sound)
  5. Partial support for Venue 8 Pro built-in wireless (firmware included)
  6. Hardware button support for Venue 8 Pro
  7. Battery status support
  8. Install broken (missing efibootmgr)


Fifth release of Fedlet

  • Fedlet 20140310 for 8″, 800×1280 tablets
  1. Updated base packages and kernel
  2. Xorg hack to allow windows with integrated title bars to be dragged in GNOME (from Jan-Michael Brummer)


Fourth release of Fedlet

  1. Latest Fedora Rawhide base
  2. Kernel update: based on latest Rawhide, sound (and LPSS) support built in (but not working until you provide fw_sst_0f28.bin* in /usr/lib/firmware/intel and apply this mixer config), shutdown/reboot should work on Venue 8 Pro, T100 and Miix 2
  3. GNOME Terminal added to the Dash for convenience
  4. Updated the patched anaconda to latest Rawhide
  5. LibreOffice dropped to save space (I doubt anyone wants to use it on a tablet much…)


Third release of Fedlet

  1. Fix kernel performance regression
  2. Touch input rotation seems to work automagically now, so drop it from v8p-rotate (it’s now just a simple xrandr wrapper)
  3. Add a 10in (T100) build (untested)


Second release of Fedlet

  1. Repository configuration added (package: fedlet-repo)
  2. Useless custom build of xorg-x11-drv-intel dropped
  3. Kernel up to 3.14rc3 with some patches upstreamed, display hotplug reversion patch dropped and video= parameter adjusted to allow display to work with the hotplug reversion patch dropped
  4. anaconda bumped to latest version (with fedlet patch applied)


First release of Fedlet


  1. Boot
  2. X
  3. GNOME
  4. 2D, 3D and video playback acceleration
  5. Touchscreen
  6. CPU frequency scaling (pstates)
  7. USB (you can use a USB wifi adapter)
  8. Power monitoring (battery status)
  9. Sound (with ALSA config file)
  10. Wifi (on Venue 8 Pro at least, possibly also Asus T100)
  11. Hardware buttons (on Venue 8 Pro)
  12. Backlight control (on Venue 8 Pro, when booted with i915.force_backlight_pmic=1)
  13. Installation and boot of installed system (if you’re very brave)

Partly working

  1. KMS (hence accelerated video) on Venue 8 Pro seems to have quirks related to boot process, see notes below
  2. Suspend (kinda works since kernel 3.16 or so, but screen backlight may stay on, and various things may not survive the resume, e.g. touchscreen or rotation)

Not working

  1. Venue 8 Pro onboard Bluetooth
  2. Icon for rotation app is invisible with recent GNOME
  3. Most likely lots of other things

Unknown (please let me know!)

  1. Hardware support (wireless, bluetooth etc) on devices other than Venue 8 Pro


Not for 64-bit firmwares

64-bit firmware Bay Trail devices are showing up now: I wouldn’t recommend using Fedlet on those, probably, as most of the point of Fedlet is to be a 32-bit UEFI image for the 32-bit firmware Bay Trail devices. If you have a 64-bit firmware Bay Trail device, I’d probably suggest installing Fedora 21 Beta (or a Final TC/RC) then updating to a 3.18 kernel from the rawhide-kernel-nodebug repository. I could do a 64-bit build of the Fedlet kernel and the few other divergent packages, I guess.

Writing the image to USB

You can follow the standard Fedora USB writing instructions – both livecd-iso-to-disk --format --reset-mbr --efi and dd like methods should work. Do not use Rufus, unetbootin or any other ‘smart’ third party USB stick writer. They rarely work correctly, especially for UEFI booting. Tools that work like dd (several are mentioned on the page linked above) are fine.

Booting from USB on Venue 8 Pro

To boot from USB on the Venue 8 Pro, turn it off, connect the USB stick, then hold down the volume up button immediately after pressing the power button, until you see the Dell logo. This should take you into a boot menu from which you can pick your USB stick. You can also hold volume down to get into the firmware UI, where you can go to the Boot tab and move the USB stick up to the top position in the boot order (see note above about how different boot paths impact graphics).

Notes and tips

Native graphics on Venue 8 Pro

It seems to vary between devices, but I have found that graphics don’t work properly on the Venue 8 Pro (screen goes black when KMS kicks in) if you boot normally or through the firmware UI (hold volume down on boot). KMS always works if you boot through the boot device menu (hold volume up on boot). If you have a V8P and you’re getting the black-screen-on-boot problem, try different boot paths.


On most hardware, you should be able to make sound work with this ALSA state file. Download it and run alsactl -f /path/to/t100_B.state restore.

Connecting USB devices

If you don’t know this already you probably shouldn’t be playing with Fedlet, but in order to connect any USB devices, you need something called a “USB OTG cable”, which basically turns the micro-USB port on the tablet into a ‘regular’ USB port you can plug keyboards and USB sticks and things into. Available at any decent parts retailer for about $5, or any big box electronics store for about $25. Your choice.

If wifi isn’t working on your device, you can plug in a wireless USB adapter if you have a USB OTG adapter. I’m using an Asus USB-N10, it should work out of the box.

For ease of testing it’s probably a good idea to have a USB hub you can plug a wireless adapter (if needed), USB stick(s) and keyboard into.

Firefox extensions

The grab-and-drag and Go-Mobile extensions for Firefox are probably useful things to have.

Video playback acceleration

If you are legally allowed to – I can’t tell you whether you are or not, I am not a lawyer – you can install the libva-intel-driver package from RPM Fusion’s free repository. This will enable hardware-accelerated video playback in any app which speaks libva (for me, it fails on quite a few videos, have to dig into that).


If you’re very, very bold, you should be able to install Fedlet. On the Venue 8 Pro, the internal storage has a fairly big NTFS partition with Windows on it, and a bunch of smaller partitions. I’d recommend just destroying the big Windows partition and installing into that space: the other partitions are system and recovery partitions, if you leave them intact, it should be possible to recover the Windows installation later if you want to (I have not tested this).

If you do install this, get kernel updates from [my repository][19], and don’t install official kernel updates from the Fedora repos. We’re trying to get all the patches merged ASAP. I’ll try and remember to put updated kernel builds in my repo regularly. Stock kernels will now boot, at least, but (as of 3.16) shutdown/reboot may not work, battery status won’t work, and Venue 8 Pro wifi won’t work.

On the Venue 8 Pro at least, the firmware has an irritating habit of putting the Windows boot loader back at the top of the UEFI boot manager list if you attach or remove USB sticks (or sometimes, just for giggles). If you boot it with this setup it’ll go into Windows auto-recovery. I haven’t been brave enough to see what this does yet, I just force power off and go back into the firmware and put Fedlet (“Generic”) back at the top of the list.

What’s in it that’s different from Fedora?

The ‘sources’ for the outside-of-Fedora stuff that’s included in the image can be found in this github repository. There are:

  • Some kernel patches in the kernel/ directory which are applied to the kernel package in the image
  • Some Xorg config snippets and a trivial utility for rotating the screen on the Venue 8 Pro, in the xorg/ directory
  • The kickstart used to build the image, and a patch to python-imgcreate for building UEFI bootable 32-bit live images, in the ks/ directory
  • The patch that (hopefully) makes installation work smoothly in the anaconda/ directory
  • The necessary firmware for the Venue 8 Pro’s wifi adapter in the baytrail-firmware/ directory
  • The repository definition for the fedlet repo in the fedlet-repo/ directory
  • A (hopefully) working ALSA configuration file in the alsa/ directory

The packages that differ from pure Fedora Rawhide are all available from [this repository][19]. There is:

  • A patched anaconda which should allow installation to work cleanly
  • The kernel package patched with the patches from the git repository
  • The fedlet-repo package containing the repository definition
  • A package of the v8p-rotate utility
  • The baytrail-firmware package, currently containing only Venue 8 Pro wireless firmware (license proprietary-but-freely-redistributable)
  • A backport of Rawhide’s linux-firmware package, which contains the firmware needed for the sound adapter

All the variant packages have the dist tag ‘awb’ to make them easily distinguishable from official Fedora packages (except the linux-firmware package, which is just a backport).

The image should be roughly reproducible by just building a live image, using the kickstart, from a running Fedora 21 system, after applying the patch to python-imgcreate’s /usr/lib/python2.7/site-packages/imgcreate/live.py.

I cannot take any of the credit for the hard work on this: all I’ve done is write silly little scripts and stick the bits together. Multiple folks at Intel, Red Hat and elsewhere have done the tough work. An especial big thanks to Alan Coxm Aubrey Li, and Mika Westerberg at Intel, Jan-Michael Brummer at IAV (formerly of Intel), and Kalle Valo at Qualcomm (for the V8P wifi) who are really pushing the thing along.

548 Responses

  1. Alan Cox
    Alan Cox September 30, 2014 at 10:21 am | | Reply

    Runs fairly nicely on my T100TA

    Desktop seems very fragile but basics look sound. Does keep trying to give me a pop up keyboard when the real one is present.

    Giving hard disk install a spin now.. and it works

  2. Ron Coit
    Ron Coit September 30, 2014 at 10:38 am | | Reply

    Thanks for your reply, but just to let you know my lenovo MIIX2 8 could not find the boot loader until I turned off the boot flag on the first partion and turned on the boot flag on the EFI partion.

    I do know that althought it is not supposed to be part of the spec some BIOSes do use the boot flag to help locate the EFI partiton.


  3. Todor
    Todor September 30, 2014 at 1:59 pm | | Reply

    About these not found errors I posted about earlier, “Warning: /dev/disk/by-label/20140929-fedlet-i386 does not exist”, is Fedlet supposed to look for the disk with label “20140929-fedlet-i386” regardless of how I label the volume on my USB?

    Also, considering there exists a “/dev/disk/by-label/20140929-FE”, could I change something there to fix it?

  4. Alan
    Alan October 1, 2014 at 6:17 am | | Reply

    Keeps hanging. It actually seems to be a power management problem. When it idles a bit the i2c stops working properly and sometimes the MMC decides to curl up and die so you lose the rootfs.

    I think the i2c is supposed to be fixed again in the latest patches going upstream but the mmc is a new one

  5. BAud
    BAud October 1, 2014 at 2:21 pm | | Reply

    The live USB is currently working appropriately for me on Aspire Switch 10 (model: sw5-011 2 GB RAM, 32 GB storage + 500 GB hard disk in the keyboard). Some hardware still not recognized which was to be expected…

    I’m trying to install a dual boot (with the included win8.1), using another SDcard in the available slot.

    I’ve got a reliable configuration to boot with the Live USB, so I may give further details about the hardware if needed, through specific commands. You may follow my tests at http://mageiacauldron.tuxfamily.org/Blog20140912InstallFedlet

  6. Paulo Marques
    Paulo Marques October 1, 2014 at 5:29 pm | | Reply

    I tried installing 20140929-fedlet-i686.iso on my T100TA, but during the installation process, the system would hang at different points.

    I tried using the live system to do some tests, and since I was using the entire 64Gb for the installation, I tried doing:

    dd if=/dev/zero of=/dev/mmcblk0 bs=4k oflag=direct

    to write the entire flash. The copy wuold eventually fail, at different points. In the dmesg, it seems the errors always started with the mmc controller complaining about a timeout while waiting for an interrupt followed by the same driver complaining that it received an interrupt that it was not expecting. After that, the mmc controller could not talk to the eMMC device any more.

    Since this didn’t happen all the time, I tried installing a few times, until it finally succeded.

    The system now boots, but it is not really usable, because of just 2 major nags:

    – the kernel creates a device /dev/mmcblk0rpmb (Replay Protected Memory Block) that is supposed to be used with ioctls to access it. However there are probably a lot of systems that scan for partition / md superblock / lvm data in every block device that produce read requests to that device. The problem is that each attempt to read the device hangs the system for a long time which makes a single boot to take something like 15 minutes. I’ve found a patch here: https://dev-nell.com/rpmb-emmc-errors-under-linux.html that basically stops the rpmb from appearing as a block device. Applying this to an official kernel is probably overkill, but at this point, having a kernel parameter to turn this behavior on might make the system more usable.

    – the wifi card is not working. I’ve already installed a brcmfmac43241b4-sdio.txt nvram file that was kind of working using ubuntu (and I rebuilt initramfs) but the driver still can not complete a network scan and it always fails with a timeout message.

    On the plus side, the battery status indication is working (which it wasn’t on the ubuntu distro I tried before).

    Thank you for all your work on this. I’ll try to help testing and reporting, if you think it will help getting the system working sooner.

  7. WillN
    WillN October 7, 2014 at 11:24 am | | Reply

    I have an ASUS T100 Transformer. On your 9/11 Fedlet release, I could run the installer successfully. After the installation, it would error out trying to write a bootloader.

    On the 9/29 release, I get some kind of error after booting to the live OS. I don’t think that it tells me anything more than there was an error. I can still use the live OS though. When I run the installer, it now errors out trying to partition my HDD. It doesn’t make it to the actual installation.

    I am in no hurry, but I wanted you to know in case it’s helpful.

  8. Bruce
    Bruce October 7, 2014 at 12:31 pm | | Reply

    I am running the 7th release on my ASUS T100TA in live persistence mode its very nice good job. I am hopeful that wifi support/driver will be available soon. Please let me know if when that would be possible
    As for you install problem on the T100 you are trying to write to a secured boot sector is why it wont write to the boot sector of drive 0 so it cant write

  9. Bruce
    Bruce October 9, 2014 at 11:43 am | | Reply

    In regards to wifi and blue tooth wireless a suggestion both chips sets are most likely mobile chips and would need mobile coded drivers like on mobile phones android tabs so on!I hope this was a helpful suggestion.

  10. Bruce
    Bruce October 9, 2014 at 10:53 pm | | Reply

    I have but I am only running fedlet in live persistence mode and just have stated a few days ago Have everything working but wifi and bluetooth the rest works pretty good like to have fun with it over the winter.
    Cant seem to fined any usb wifi dongles around now that wifi is built to most devices and dont want to order one of the net it will arrive about the same time as the bug fix. The gps wifi works grate now all i need is the to internet get the maps ha ha ha
    what logs would be need I can get and make some copy and wonk on docs and test running any changes

  11. Bruce
    Bruce October 10, 2014 at 1:35 pm | | Reply

    ASUS T100 wifi adapter is IOBridge API and a shared adapter I am only guessing its sharing with the gps.I hope this info helps you all with the T100

  12. jeffp
    jeffp October 16, 2014 at 9:53 am | | Reply

    Just for info .. and perhaps I am playing catchup (most likely) .. have just managed to get a copy of the Fedora 20 Live media booting on the Miix2 8. Bit of a mish-mash of pieces pulled together – but essentially only playing with the UEFI boot files. I’ve only tried the 32 bit version so far thinking to reduce the number of potential variables that might get in the way. Picture here: https://dl.dropboxusercontent.com/u/84685556/20141016_174926.jpg Anyway .. a step forward. I was beginning to think the tablet was going to be a total waste of money :/

  13. Ray
    Ray October 19, 2014 at 12:34 am | | Reply

    I can confirm that the latest version of Fedlet (20140929) boots on an MSI S100. Out of the box the included keyboard works, but that’s about it.

    So far I have not managed to get the touch panel working or wifi (but I haven’t fiddled much yet).

  14. Giacomo
    Giacomo October 19, 2014 at 1:59 pm | | Reply

    The microphone problem on the asus T100 appears to be solved by this patch:
    Any idea when the new fedlet release will be ready?

  15. Alan German
    Alan German October 25, 2014 at 1:15 pm | | Reply

    I just tried seventh version of Fedlet from a live-USB on a T100. So far, I haven’t seen any mmcblk0rpmb timeout errors (which plague Ubuntu). I had no Wi-Fi connectivity through the on-board wireless card, but a TP-Link USB wireless adapter works just fine. I had one error message, something to the effect that a kernel error was detected. I submitted an error report.

    I would like to try installing Fedlet to a dedicated disk partition (dual-boot with Win 8). The installation instructions seem to suggest that one can select a specific partition (i.e. “I’d recommend just destroying the big Windows partition and installing into that space”). While I will give this a try once I have more time to play, could you confirm that the installation partition is selectable?

  16. Alan German
    Alan German October 26, 2014 at 4:38 pm | | Reply

    I found a couple of on-line tutorials on the use of anaconda and managed to set up my existing Ubuntu disk partition for the installation of Fedlet. Regrettably, the installation seemed to stall. Ctrl-Alt-F4 showed a seemingly endless loop of “Buffer I/O error on device mmcblk0p5.” I imagine that this problem is related to the timeout issues that I experienced previously with Ubuntu.

    If I can just put a good word in for the kernel patch that was mentioned earlier in this thread, the Google+ group trying to get Ubuntu to run on the T100 has one 32-bit version of the kernel to which the patch has been applied. While this doesn’t help with installing Ubuntu, replacing the installed kernel with the patched version (at least on my machiine) eliminates all the timeout errors and makes the system usable.

  17. MiW
    MiW October 27, 2014 at 6:36 am | | Reply


    I applied the patch from here http://permalink.gmane.org/gmane.linux.kernel.mmc/28179 to resolve the RPMB time out issue.
    This looks like the best patch, from intel.
    Works well without the time outs on my Arch install on an HP Omni 10.
    I have not been able to get sound, power or wifi working on this device, but it otherwise everything else works ok.
    Any hints on where to find a working /lib/firmware/brcm/brcmfmac43241b4-sdio.txt NVRAM?

    Getting the RPMB time outs resolved was important for ultrafast boot times, and it appeared to improve performance too.
    I’m going to try to experiment with patches from https://github.com/cawilliamson/linux-asus-t100ta and https://github.com/jfwells/linux-asus-t100ta next.

    Hope this helps,

  18. Sergey
    Sergey October 28, 2014 at 4:19 am | | Reply

    Rebuild, please Fedlet image “Fedlet 20140929 for all hardware” with the following drivers.
    https://github.com/hadess/gt9хх and https://github.com/hadess/rtl8723ас
    In Ubuntu, I was able to compile them, but in Fedlet compilation does not occur because of errors.
    Sorry for my bad english.

    1. Sergey
      Sergey October 29, 2014 at 4:02 am | | Reply

      Links is bad.
      New links:
      Wifi rtl8723BS – https://github.com/hadess/rtl8723as
      Touchscreen Goodix GT9113 – https://github.com/hadess/gt9xx
      Drivers work in Ubuntu on Onda V975w.

  19. StridAst
    StridAst October 28, 2014 at 4:35 pm | | Reply

    Is the Linux kernel you are using the same as the one from the Ubuntu repositories? Or is it modified? Trying to get WiFi working on my pipo W2 tablet. (Same WiFi chip as the drivers linked to by the comment above this one). Problem is 3.13 kernels won’t load the SDIO bus on this tablet. But the 3.16 kernels won’t boot the tablet at all. Fedlet boots but the touchscreen doesn’t work. So I’m trying to find a newer kernel that boots my tablet.

    1. Dosfish
      Dosfish November 1, 2014 at 10:18 pm | | Reply

      I’m trying to get a Voyo A1 mini working, Fedlet works great sans the touchscreen and wifi/bt (which is the same module, an rtl8723BS) and I’m surprised to hear that the touchscreen works in Ubuntu. Can you give me some more details, like which Ubuntu image you used and the results of xinput and syslog to do with the touchscreen?

      1. StridAst
        StridAst November 2, 2014 at 1:27 am | | Reply

        ok, i can answer that information tomorrow. 🙂 falling asleep here. but to give you a start, read up this thread: http://ubuntuforums.org/showthread.php?t=2249936

        started it trying to get ubuntu to recognize the wifi. progress was made. touchscreen and power button functionality in ubuntu are based off which kernel is in use. ubuntu 14.04.1 and ubuntu gnome 14.04.1 work right out of the box for touchscreen use. but not wifi. the kernel doesnt load the sdio bus at all, so i have no idea how to get it working. kernel 3.16.2 loads the sdio bus, power button and volume buttons! so i was able to get wifi working! but NOT bluetooth, and the touchscreen is broken in that kernel version. kernel 3.17.1 loads the touchscreen, sdio bus, but not the power buttons or the volume buttons. and was very very glitchy 3.18 kernels didnt boot at all.

        important to note: to get any kernel after the 3.13s (that i tried) to boot, i had to use “advanced options for ubuntu” in grub, then boot into recovery for that kernel, Then boot to desktop.

        still trying every single kernel one at a time to try to find one that works with everything or even just most things. and ive wiped my current installation of stock ubuntu 14.04.1 to go back to ubuntu gnome. but until i reinstall i cant run xinput etc. i remember the device name in xinput is FTSC1000:00 2802:5056 but that’s it off the top of my head

        ill post the details tomorrow on the ubuntu forums thread since i just realized how long this reply is.

  20. codenomad
    codenomad October 29, 2014 at 6:46 pm | | Reply

    This is great work, I was able to boot straight into Fedlet on a Dell Venue 11 Pro ( model 5130–the atom one ). Out of the box touch screen worked, wifi was detected but there’s some configuration still needed as it couldn’t detect my broadcasted SSID, sound seemed to work. I’ll be able to dig a little more once I get the keyboard later this week….

    Are you going to respin when the new Beta comes out on 11/4? Please?? 😀

  21. ceewhat
    ceewhat November 4, 2014 at 3:32 pm | | Reply

    On KMS:
    For me it seems to work maybe 1 out of every 10-20 tries.
    I’ve been at this fiddling with Android-x86 for the past week and haven’t had much luck figuring out why.

    The DRM dmesg logs from a working modeset and a nonworking one are near identical except for something about GPU frequency happening a little later on in the successful one.

    I just gave fedlet a few tries and KMS worked once and hasn’t since, weird stuff eh?

    Tablet: Acer Iconia W4-820

  22. Sergey
    Sergey November 12, 2014 at 7:10 am | | Reply

    Tell me, please, how to compile the driver in Fedlet.
    In Ubuntu 14.04 driver compiled without problems.
    When I type “make”, then in the console I see the following error “make(1): *** /lib/modules/3.18.0-0.rc4.git0.1.1awb.i686/build: No such file or directory. Stop”
    Before compiling I installed the following packages: sudo yum -y install gcc kernel-headers kernel-devel

    Sorry for my bad English.

  23. Alan Cox
    Alan Cox November 12, 2014 at 8:10 am | | Reply

    11/11 is a dud on T100 – dies with the hotdog logo. Will try and debug when I get a bit more time

    1. Will N
      Will N November 15, 2014 at 11:41 pm | | Reply

      I have a T100, and I was able to create partitions and start the installation. My machine froze during the installation at 76%. I waited almost an hour before powering it off. This is all with the 11/11 release.

      The best luck I’ve had is with the 9/11 release. I was able to get through the installation, but it errored out trying to install the boot loader. The 9/29 release errored out trying to create partitions for the installation.

  24. Andreas Lorensen
    Andreas Lorensen November 12, 2014 at 9:40 am | | Reply

    Great work. I hav a Lenovo MIIX2 and biggest wish is to run Fedora on it. Running Fedora on all other computeres in the household.

  25. Markus Larsson
    Markus Larsson November 16, 2014 at 7:45 am | | Reply

    Aside from major stability issues (like hanging every couple of minutes and only booting properly every third time) things are looking up.
    On my Lenovo Miix 2 10 most things work, except sound and screen rotation.
    I give close to no crap about the screen rotation but the lockups and no sound is worth looking in to.
    Stellar work though, I’m looking forward to having a proper linux tablet.

  26. david
    david November 18, 2014 at 10:05 am | | Reply

    trekstor surftab wintron 10.1 20141111 release works, sometimes,
    but i get kernel panics from time to time.
    also wlan doesnt work, sound neither.
    touchscreen works.
    anyways thanks for doing this.

    greetings david

  27. nmilosev
    nmilosev November 18, 2014 at 1:58 pm | | Reply

    Hello Adam!

    Toshiba Encore user here (first it seems) and big Fedora fan. Here are my observations.

    – Disabled Secure Boot in UEFI firmware settings. Used rufus to put 20141111 build on my trusty 2gb Kingston drive. Rebooted to usb from windows recovery setting. Got to the grub menu and loading screen but system won’t boot, reports error indicating it can’t find 20111111-fedlet-i686 labeled drive. Thought it was rufus messing up. Tried fedora usb drive creator, black screen after grub. Tried rawwrite, same black screen. Managed to mess up partitions on my flash drive, had to use diskpart to clear drive. Almost gave up. Tried one more time, used fedora live usb creator for Windows with persistent storage, BUT modified grub.cfg file on the flash drive to search for drive labeled ‘live’ (that’s what live usb creator named my flash drive). Fedlet booted fully in about 60 seconds.
    – Touchscreen works, hardware keys too, SIP shows up correctly when trying to input text, overall performance very good, graphics working fine.
    – Windows partitiom visible and accessible from nautilus.
    – Shutdown works
    – WiFi not showing up in networks 🙁 if you could write me some instructions, I could try to fix it, but alone I’m not smart enough
    – Audio wasn’t working, could not test with ALSA file, since no internet connection
    – Sensors not working (manual rotate working)
    – BT not working

    Other than Wi-Fi issue I was amazed how everything was, if there is a way to fix Wi-Fi it would be perfect!

    Thanks to everyone who helped make this project.

    Please give me a starting point on making WiFi working.

    Looking forward to hearing from you,

  28. Sam
    Sam November 20, 2014 at 12:05 am | | Reply

    I got one of the Insignia Flex 8 tablets (sells for $100) and I’ve been busily trying to get linux usable on it. This would be perfect as an introduction to linux because of price and battery life. It has Realtek 8723bs wifi+bt connected via SDIO (currently I can only get wifi to work, though), Intel SST audio (not working) and a goodix touchscreen. The mmc storage device, accelerometer, cameras, power button, volume buttons, auto-rotate buttons, video acceleration and sleep function don’t work. Here is a video I took of it: https://www.youtube.com/watch?v=SO6TD_kM2Rw

    Keep up the good work on Fedlet! Fedora’s my favorite distro besides arch and getting linux to work well on bay trail devices with mmc is going to be great!

  29. Sam
    Sam November 20, 2014 at 9:32 am | | Reply

    is the active stylus working for anyone?

  30. Vaidotas
    Vaidotas November 22, 2014 at 3:37 am | | Reply

    To get wireless working on Lenovo Miix 2 8 I had to do this:
    $ su
    # cp /lib/firmware/brcm/brcmfmac43241b4-sdio.bin /lib/firmware/brcm/brcmfmac43241b4-sdio.txt
    # rmmod brcmfmac
    # modprobe brcfmac

    Wireless options then appear in status menu and I was able to connect to my wireless network and browse the web with Firefox.
    Not sure why kernel tries to load txt file instead of bin.

    1. Vaidotas
      Vaidotas November 23, 2014 at 2:38 am | | Reply

      Trying to get more hardware working on Lenovo Miix 2 8.
      After loading T100 alsa state file I get sound, but only on “Front Right” channel on “speakers” (testing with “Test Speakers” function in sound settings). There’s only one speaker on tablet, so configuration might need tweaking to get both channels playing on same speaker. Volume setting works with hardware buttons too.
      On headphones channels are reversed. And is there any way to turn of sound from speaker when headphones are connected?
      Loading t100 state file displayed an error message in console:
      alsactl: sysfs_init:48: sysfs path ‘/sys’ is invalid

      Having wifi and sound working is awesome. Finally I’d like to figure out how to get video working with KMS. Currently it is impossible to get any logs, because after Plymouth starts screen goes blank and there’s no way to get into console and get any debug information.

  31. dhead666
    dhead666 November 25, 2014 at 2:43 am | | Reply


    Non Bay-Trail-T user here but still a frustrated Intel [mobile] Graphics user.
    If you still experience hangs then you might want to try Chris Wilson’s development branch, there’s a huge patch for 3.17.4 which does seems to solved hangs with my C720 Chromebook (2955U), notice that except i915.modeset=1 I do not use any drm or i915 kernel parameters, see https://bugs.freedesktop.org/show_bug.cgi?id=83677#c130

    I would love to hear if that helps as this is the main reason why I’m not getting a Bay-Trail-T tablet for Linux.

    I would much appreciate if someone could upload a video or share his/her experience with Gnome 3.14 in regards to touch gestures, ease of use of Nautilus, Gnome-Documents and Evince with touch gestures as I my main use for a Linux tablet is reading pdf documents.

    Does anyone know if other stylus than Wacom are working in Linux ?, is so then did you tried a note taking app like hoodle ?

  32. dkabot
    dkabot November 25, 2014 at 12:48 pm | | Reply

    Booted the 9th image on my Asus Vivotab Note 8 (http://www.asus.com/us/Tablets_Mobile/ASUS_VivoTab_Note_8_M80TA/) out of curiosity.

    Unfortunately, the default boot just errors out and my only hub is an old iMac G3 keyboard, so booting takes roughly a year.

    – Display (Works, but “Unknown Display” in settings)
    – Wi-Fi (Firefox can load sites)
    – USB boot device, keyboard and mouse (My only way to do anything, glad it’s working)
    – Power button (Screen blanked forever the first time, kind of worked the second)
    – Battery (Get a % remaining, and it goes down. Seems to roughly match what Windows said)
    – Bluetooth (Says it’s on, didn’t try connecting anything)

    Not Working:
    – Sound (Tried Youtube, got nothing)
    – Brightness (Slider moves, no changes)
    – Touch input (Sadly)
    – Pen input (It’s Wacom, but system detects nothing)
    – Any of the other buttons (Win button does nothing, ditto volume)
    – Front light (constantly on, usually represents camera in Windows but does some other things)

    If you want any info I might be able to get you from it, let me know. Haven’t seen any of these mentioned with “linux” yet aside from an Ubuntu forum thread that said “No”.

  33. Vaidotas
    Vaidotas November 25, 2014 at 2:05 pm | | Reply

    Done a quick check of 20141124 fedlet release on Lenovo Miix 2 8 tablet.
    * KMS video doesn’t work, boots only with nomodeset.
    * accelerometer rotation doesn’t work – how to check to see if accelerometer device is working?
    * wifi works out of the box
    * backlight control doesn’t work with provided kernel parameter – /sys/class/backlight/ empty
    * unmuting SPOL MIX SPKVOL R with t100 state loaded plays left audio channel through speaker. Sound input doesn’t work. Audio channels in headphones are reversed.
    * camera – no device found

  34. Rob
    Rob November 28, 2014 at 1:58 am | | Reply

    The 20141124 release of Fedlet is working brilliantly on the Lenovo Miix 2 8(apart from things mentioned by Vaidotas). Thanks!

  35. maxzrff
    maxzrff November 28, 2014 at 10:37 am | | Reply

    Accelerometer did not work for me either in my V8P. Where should I look for errors?

  36. Alan Cox
    Alan Cox December 1, 2014 at 8:44 am | | Reply

    Still fails on the European T100 at least.

    I wouldn’t advise using random nvram files either – it contains stuff that is not generic. The correct nvram for any device should be in the UEFI variables.

  37. Ray
    Ray December 1, 2014 at 11:34 am | | Reply

    Doing a little more investigation on the latest build (thanks!!) on a Dell Venue 11 Pro.

    I haven’t been able to pinpoint it, but after about 5 minutes the wifi driver crashes. The kernel messages gave SDIO issues, and a crash dump (which I couldn’t collect at the time). This is consistent, so I just need to have a usb key handy next time I try…

    The installer also fails when it does it’s investigation of the SSD. For some reason the individual partitions are coming up with a dirty bit that’s preventing using the partitions (note: the partitions have always been cleanly unmounted).

    Other side notes and gotchas:

    You can install rEFInd, but you can’t use bcdedit to point it to the refind.efi file (fails saying i/o error). I had to rename the refind.efi to one of the existing efi boot options (There are 2 on the Venue Pro 11 — UEFI OS and Windows). I’m not sure why the IO error, but it definitely seems like a firmware/windows issue. Renaming it to an existing entry worked a charm and dropped me right into rEFInd.

  38. Cool_Subs
    Cool_Subs December 1, 2014 at 11:49 am | | Reply

    Trying to install. Hung up adding USB as a boot option as it is different than before in my experience. The boot options in the firmware want me to point to a specific file to boot and I never had to do that before.

    Any help?

    1. Cool_Subs
      Cool_Subs December 1, 2014 at 11:58 am | | Reply

      Apologies, I seem to have answered my own question. My solution was to just type ‘BOOT’ in all caps instead of lowercase. Hopefully anybody else also having this problem will see this. Good luck, thank you for putting the effort in to create this!

  39. vito
    vito December 1, 2014 at 1:28 pm | | Reply

    wich software use for installation on usb? my installation abort from usb on t100.

    1. Cool_Subs
      Cool_Subs December 1, 2014 at 3:12 pm | | Reply
  40. Vaidotas
    Vaidotas December 1, 2014 at 1:34 pm | | Reply

    I’ve done some research and I think I found a similar issue: https://bugzilla.kernel.org/show_bug.cgi?id=86551 . But currently I have no way to test it.

  41. Chris Rorvick
    Chris Rorvick December 2, 2014 at 9:03 pm | | Reply

    I have a T100A (purchased in the US) and installed the 20141124 release this weekend, upgrading from 20140310. Sound and wifi work out out of the box now (woohoo!) but this kernel is much less stable. The system freezes up, sometimes before finishing booting, though I haven’t been able to caputure anything interesint when this happens via a serial console. Some things I’m seeing before, though:

    Lots of i2c read failures:

    [ 152.832508] i2c i2c-7: i2c read failed
    [ 273.094184] i2c i2c-7: i2c read failed
    [ 393.193482] i2c i2c-7: i2c read failed
    [ 513.329508] i2c i2c-7: i2c read failed

    Many of these are on a two minute interval as seen in the above example, but on some boots they are much more frequent. In one case I also got noise from asus_wmi:

    [ 258.605940] asus_wmi: Unknown key 79 pressed
    [ 258.636854] i2c i2c-7: i2c read failed
    [ 258.965949] i2c i2c-7: i2c read failed
    [ 258.979354] asus_wmi: Unknown key 79 pressed
    [ 259.027048] i2c i2c-7: i2c read failed
    [ 259.129159] i2c i2c-7: i2c read failed

    Got this once:

    [ 2374.940349] mmc1: ADMA error
    [ 2384.118998] mmc0: Timeout waiting for hardware interrupt.
    [ 2384.124272] mmcblk0: error -110 transferring data, sector 51453752, nr 64, cmd response 0x900, card status 0xc00
    [ 2384.124297] blk_update_request: I/O error, dev mmcblk0, sector 51453752
    [ 2384.124305] blk_update_request: I/O error, dev mmcblk0, sector 51453760
    [ 2384.124312] blk_update_request: I/O error, dev mmcblk0, sector 51453768

    This was followed by much of the same with some complaints from ext4 and the brcmfmac.

    I tried running a kernel with all the I2C debugging turned on but this seemed just blow up the kernel log. I’m going to keep digging but was curious if anyone is seeing similar issues?

    Thanks for the continued fedlet updates!

    1. Sebastien B
      Sebastien B January 26, 2015 at 12:40 am | | Reply

      Getting the same “mmc0: Timeout waiting for hardware interrupt” errors on Lenovo Tablet 10 (which has tons of additional other problems with Linux) when using the hard disk heavily, e.g. compiling a kernel. After this the hard disk stops responding, and this bug is crippling the machine pretty badly.

  42. Bobby Budnick
    Bobby Budnick December 4, 2014 at 8:58 pm | | Reply

    Does anyone know why sound isn’t working with the newer Bay Trail tablets including the Dell Venue 8 Pro 3000 series? I have given it everything I’ve got. Is there some kind of super secret inner circle linux commands to bypass: “baytrail-pcm-audio baytrail-pcm-audio: ipc: error DSP boot timeout” ? This happens on many Bay Trail tablets I have tested except the original Venue 8 Pro and Asus T100.

  43. Bobby Budnick
    Bobby Budnick December 6, 2014 at 7:34 am | | Reply

    I also wanted to update with a list of devices not working with this error:
    HP Stream 7
    Toshiba Encore Mini 7
    Toshiba Encore 2 8
    Dell Venue 8 Pro 3000 series
    Nextbook 8″

  44. Kyle
    Kyle December 6, 2014 at 8:11 am | | Reply

    Hi Adam, thanks for all of your work, you are helping a lot of people get Linux running on their tablets including me.

    I booted the latest Fedlet image on the new HP Stream 7 Bay Trail tablet (a great value at $99 US), it was nice to see things like the touchscreen and battery indicator working. Like some other people have reported here, the booting was unstable however, it would often hang at various places and I would have to restart it. Once it did boot, the U.I. seemed to respond slowly and when connected to the internet with a USB Wifi adapter, the tablet ran progressively slower until it was unusable. I also installed Fedlet to the tablet’s drive and saw the same behavior.

    I then booted an Ubuntu Mate 14.10 32-bit ISO with the 3.16 kernel. (I had to copy the Fedlet EFI directory to the Ubuntu USB and tweak the grub.cfg file for it to boot.) Ubuntu booted consistently and was fast and stable (although it does not have as much device support as Fedlet). I also installed it to the drive and it continues to run well.

    My question is, do you have any thoughts as to why the Fedlet image has the stability and performance issues while Ubuntu 14.10 does not? Thanks again.

    1. Bobby Budnick
      Bobby Budnick December 6, 2014 at 2:50 pm | | Reply

      Hi Kyle. Your sound is broken too, correct? I can help you get Ubuntu working with your Stream 7 with most of the hardware minus Bluetooth, motion sensor, and sound. Please let me know if you have any developments with sound because I have been working feverishly on it.

  45. Chris Rorvick
    Chris Rorvick December 6, 2014 at 11:29 am | | Reply

    I’m going to take a closer look at commit 5d98e61d337c (I2C/ACPI: Add i2c ACPI operation region support) introduced in the 3.17 merge window. It specifically mentions the T100A in the commit log, and it introduces the logic that is printing the “i2c read failed” message. I’ve determined that the return value is -121 but I don’t know what this means.

  46. Joost
    Joost December 6, 2014 at 1:37 pm | | Reply

    With 9th release on asus t100ta, kernel problem notifications keep popping up on desktop.

    [ 50.793044] WARNING: CPU: 3 PID: 735 at drivers/pinctrl/pinctrl-baytrail.c:322 byt_gpio_direction_output+0x97/0xa0()
    [ 50.793046] Potential Error: Setting GPIO with direct_irq_en to output

    my dmesg:

    1. Chris Rorvick
      Chris Rorvick December 6, 2014 at 2:26 pm | | Reply

      From the logs I still have I only see that once for my T100A. The message was added with commit ff998356b644 (pinctrl: baytrail: Warn if direct IRQ GPIO set to output) during the merge window of 3.17. So maybe it’s not a new issue, the kernel just complains about it now?

    2. Joost
      Joost December 9, 2014 at 2:27 am | | Reply

      Perhaps I forgot to mention, wifi worked fine on my T100 as I was typing that message 🙂

      The GPIO error only appeared once in DMESG, but appeared about 10x as a desktop popup until the laptop completely froze.

      Perhaps the freezing has something to do with the mmcblk0 errors that cause significant delay. There is a patch available that is supposed to solve this:

  47. André
    André December 7, 2014 at 2:41 am | | Reply

    I only get a blackscreen on my encore 8 after selecting the live USB drive (created with rufus from the latest ISO)

  48. Sam
    Sam December 7, 2014 at 6:07 pm | | Reply

    I’m installing Fedlet 20141124 on my Insignia Flex 8 tablet (Windows version) as we speak. I am also experiencing the errors relating to “mmcblk0 error transferring data…sector ######…” and my battery status doesn’t work, so we’ll see how it goes. I’m also hoping to get the sound working soon.

    Adam, could you add support for this device in your next release: https://github.com/hadess/rtl8723as

    Doesn’t anyone else here have one of these cheap Best Buy tablets?

  49. Jan
    Jan December 7, 2014 at 10:45 pm | | Reply

    Hi! I have installed Fedlet 9 on Lenovo Miix 3. The graphics, touch screen, keyboard/mouse cover are working, but I could not get wifi to work no matter what. The wireless card used is Realtek rtl 8723bs and should work with this driver:
    the problem is: the driver compiles, the module loads, a wireless interface pops up in the network manager GUI, but no wireless networks are detected. Furthermore, after loading this module, wireless card somehow locks up and does not even work in Winows unless I reset something in BIOS. I can’t unblock it with rfkill, as rfkill does not detect this interface.
    Any ideas?


    PS: I really like and respect your work on this project.

    1. Olivier
      Olivier December 22, 2014 at 12:03 am | | Reply

      I have the same 8723bs. It works in my case but suffer from stability issue and has limitations.

      wpa_supplicant do not work (so no WPA).
      WEP works with problems.
      unencrypted wifi work more or less reliably , but sometimes you have an error message and the card won’t work until rebooted (this mostly appears if we want to change anything in the network communication, once the connection is established it is more or less stable).

      Note that the networkmanager depends on wpa_supplicant and will most certainly not work. You have to configure the card with iwconfig (and be sure networkmanager don’t touch it before, see above).

Leave a Reply to Bjorn Cancel reply

Your email address will not be published. Required fields are marked *