Thursday, 8 June 2017

Second look at Ubuntu 17.10 or Artful

UpdateThis work is superseded by my 'isorespin.sh' script which can respin an official ISO suitable for use on Intel Atom devices.



I've respun using my 'isorespin.sh' script the latest daily build of Ubuntu 17.10 (Artful Aardvark) from 'http://cdimage.ubuntu.com/ubuntu/daily-live/current' with the Ubuntu build of mainline kernel v4.12-rc4, the UCM files and my local package to add bluetooth (as RTL8723BS wifi is now fully supported). I've also added my 'linuxium-install-bootloader.sh' just for good measure:

Script '/usr/local/bin/isorespin.sh' called with '-i artful-desktop-amd64.iso -u -l rtl8723bt_4.12.0_amd64.deb -f linuxium-install-UCM-files.sh -f wrapper-linuxium-install-UCM-files.sh -c wrapper-linuxium-install-UCM-files.sh -f linuxium-install-bootloader.sh' ...
Work directory '/home/linuxium/artful' used ...
ISO '/home/linuxium/artful/artful-desktop-amd64.iso' respun ...
Bootloader 'GRUB' added ...
Kernel updated with mainline kernel version '4.12.0-041200rc4-generic' ...
Local package '/home/linuxium/artful/rtl8723bt_4.12.0_amd64.deb' added ...
File '/home/linuxium/artful/linuxium-install-UCM-files.sh' added ...
File '/home/linuxium/artful/wrapper-linuxium-install-UCM-files.sh' added ...
File '/home/linuxium/artful/linuxium-install-bootloader.sh' added ...
Command run ...
# wrapper-linuxium-install-UCM-files.sh
./linuxium-install-UCM-files.sh: Extracting UCM files ...
./linuxium-install-UCM-files.sh: Installing UCM files ...
./linuxium-install-UCM-files.sh: Reloading UCM driver ...
./linuxium-install-UCM-files.sh: Installation of UCM finished 
Respun ISO created as 'linuxium-v4.12-rc4-artful-desktop-amd64.iso' in '/home/linuxium/artful'.

Interestingly the new ISO builds have dropped Unity and now boot with the GNOME desktop as apparently Unity will only be available when upgrading from an earlier Ubuntu release.

Anyone interested to try it out can download my interim ISO from 'linuxium-v4.12-rc4-artful-desktop-amd64.iso'.

If you find this useful then please donate using the following link http://goo.gl/nXWSGf as everything helps with development costs.

26 comments:

  1. Hi Ian,
    Tried your Artful ISO (on Teclast Tbook 16 Power).
    Everything seems to be working out of the box (WiFi, sound including HDMI output, BT) except for TS (never worked anyway - cannot detect silead chip id in dmesg).
    One weird thing happened though. Boot messages and Ubuntu splash screen started normally, and then when desktop booted up, the screen was rotated upside down - 180 degrees:). Unplugged the detachable keyboard, connected another one and continue testing.
    Rotation does work to portrait mode when I turn the tablet.
    Indicator-multiload (which is one of my essentials) did not show up in the system bar? Xsensors work normally.
    Overall, I think I am too used to Unity and will miss it a lot!!!
    Otherwise, stable and solid!
    Cheers, G

    ReplyDelete
    Replies
    1. You can invert your screen with

      xrandr -o inverted

      from a terminal

      Delete
    2. Hi Goran,
      I also had the rotated screen issue so just used the display setting to rotate it 180 which was then saved next time I booted. Although the login screen was still upside down. I have had some interesting trouble with the battery indicator in the system bar, it worked fine, then I installed Solaar for my mouse which then seemed to replace the system battery which I could not get back even with removing Solaar... As far as the SD card, I have some mmc references in dmesg so I think it is finding it but I might have a bad card as I have a -110 error. I will try a new card when I have the chance. Sounds like we are getting there with the Tbook!

      Delete
    3. Thank you jsripples!
      Hi Mike, thanks for letting me know. I had battery indicator working only with one 17.04 iso I created with Ian's script (power supply not connected). Otherwise consistently not showing on everything else I tried (haven't had much time to test these days though). TS still not working but I found some useful info & might be making progress (you can PM me @ sevo1984 on Freaktab - sorry I am not good with G+ or other services, and I hope Ian wouldn't mind!). Thank you both, G

      Delete
    4. @Goran: Please post any useful information you find or progress you make for others to benefit from.

      Delete
    5. Hi all,
      so Ian, if you are happy with it I will keep posting here with my experiences so far?
      I will just summmarise that with the new 17.10 iso things have perhaps gone slightly backwards... Wifi is good but the bluetooth although it comes to life wit hthe systemctl command for some strange reason the on/off slider for pairing to a headset refuses to stay on... It worked fine on the 17.04 iso.
      Also, any info on the touchscreen would be great, I found a silead kernel module page but no idea if this would be compatible...
      Other than that, I did have a slight issue as when I installed 17.10 in exactly the same way as before on the usb stick it seemed to write grub on my mbr! So now I can't boot android, it goes straight to grub... I would quite like to keep the android for now so any suggestions would be great!
      Thanks, Mike.

      Delete
    6. Yes, keep posting as others may also have ideas or solutions to contribute. I'll have to look bluetooth on 17.10 in more detail. In terms of dual booting with Android if you are running on a device with the dual 32-bit/64-bit BIOS used for the Windows/Android combo devices then in the past installing Ubuntu depended on which bootloader you ran from. My latest 'isorespin.sh' script fixes this however it will mean that Ubuntu will always install and GRUB written to the default EFI partition. From memory I don't think Android uses GRUB so you would need to find an alternative way to boot both OS.

      Delete
    7. Thanks Ian!
      O.k. Regarding TS support (in my case Teclast Tbook 16 Power) I did manage to produce one silead_ts.fw file without errors using Win10 extracted SileadTouch.sys following instructions on this link:
      https://github.com/philipn1996/gsl-firmware/blob/master/firmware/trekstor/surftab-twin-10.1-ST10432-8/README.md#command-to-find-the-offsets-used-for-extraction
      Then I used default parameters for "fwtool" conversion (provided at the very end stage “Convert the firmware.fw_4”, bottom of this page), as I have no idea of "-w" and "-h" for my device (native reolution is 1920x1080).
      If my understanding is correct, it should work in combination with gslx680-acpi provided at: https://github.com/onitake/gslx680-acpi
      but I haven’t had time for proper testing yet.
      The reason for my optimism is that produced file is of very similar size and hex structure to the fw files provided @ onitake firmware repo and for the first time everything worked with no errors.

      Delete
    8. I can report that TS is working. Well, "w" and "h" are notably off the limits, needs more playing to find closer values. But xinput_calibrator makes it already perfectly usable. Tried on 16.04.2 isorespun with newest kernel. 16.04 is distro I normally use on all my devices as it is LTC, so I thought to give it a go. It's FAST, honestly!!!:)

      Delete
    9. Hi All,

      great work on the TS Goran, looks like progress! Any ideas on the BT issue, have you tested it Goran? Thanks,
      Mike.

      Delete
    10. Hi Mike,
      I don’t think that BT issue is necessarily all Linux related E.g. in Windows, I cannot connect to wireless display if Bluetooth mouse is connected. Similarly, occasional WiFi connection problems occur on new SSIDs in Windows. It usually takes a full power cycle or booting to Android to reset.
      Anyway, I think that playing with live iso is coming to an end, and it requires real installation for further testing and hopefully good use. In my case, sadly it won’t be 16.04.2 (no sound issue and a few more), I think I’ll stick to 17.04 instead as it does the job for me. Have you installed?
      True, SD card would be a best choice but it also requires BIOS tweaking and has a potential risk. They probably made it that way for a reason.. well, sort of:). Do we need to disable eMMC write protected option in BIOS to install? Further, on my device (M5F8) EFI shell is not working which is quite inconvenient..... etc etc. It definitely takes lots of time and patience to avoid bricking. Curently looking for a good step by step installation guide and backup options for the existing configuration (most recent Clonzilla as "disk to image"?). Keep us posted of your experience please.
      Goran

      Delete
  2. Hi, thanks for grate work!

    Live version work good, but while installation in progress, system logging out and I am not able to login back

    ReplyDelete
    Replies
    1. This is likely an issue with the NVRAM boot entries getting out of sync. Try removing them and recreating them using 'efibootmgr'.

      Delete
  3. I hope that Linux distros start supporting these 32 bit UEFI tablets properly in the near future.

    ReplyDelete
    Replies
    1. Unlikely. They are already dropping 32-bit distros and new devices now make use of 64-bit bootloaders which removes lots of the existing support issues.

      Delete
  4. Thanks for your work Linuxium! Everything works very well on my cherry trail laptop, a YEPO 737S (http://www.gearbest.com/laptops/pp_610148.html) apart from audio.
    I see two devices in alsamixer, but I can't get no sound from them through the speakers. I pasted my dmesg here: http://paste.ubuntu.com/24831792/
    Thanks again!

    ReplyDelete
    Replies
    1. Did you add the UCM files as above?

      Delete
    2. I used the ISO you linked, 'linuxium-v4.12-rc4-artful-desktop-amd64.iso'. It already has the UCM files, right? Do I need to do something else?
      Thanks for your reply!

      Delete
    3. As the audio in this laptop seems to be "bytchtnocodec" I added the UCM files from here: https://github.com/plbossart/UCM/tree/master/bytcht-nocodec

      Now I have yet another sound output device in the gnome control panel, and also an input sound device but still no audio...

      Delete
    4. It seems that this device (YEPO 737S) isn't using a recognized codec. Do you know or can you find out what the exact audio chip is?

      Delete
    5. Windows reports it as "Nuvoton SST Nau88L24". I've found a thread in the alsa devel mailing list (https://www.spinics.net/lists/alsa-devel/msg57505.html) and a github repo (https://github.com/joequant/nau8824/) that seem relevant, but I don't know how to proceed.
      Thanks again!

      Delete
    6. As the relevant people seem to be involved I'd watch the message thread you posted to see when a patch is proposed.

      Delete
  5. For info on hardware and plus: inxi
    sudo apt-get install inxi

    inxi -F

    System: Host: gerald-SurfTab-twin-11-6 Kernel: 4.12.0-041200rc4-generic x86_64 (64 bit)
    Desktop: KDE Plasma 5.10.1 Distro: Ubuntu 17.04
    Machine: Device: un-determined System: cube product: SurfTab twin 11.6 v: Hampoo_reserve
    Mobo: Hampoo model: Cherry Trail CR v: Hampoo_reserve
    UEFI: American Megatrends v: 5.11 date: 02/27/2017
    CPU: Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB
    clock speeds: max: 1920 MHz 1: 1856 MHz 2: 1797 MHz 3: 812 MHz 4: 1788 MHz
    Graphics: Card: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers
    Display Server: X.Org 1.19.3 drivers: modesetting (unloaded: fbdev,vesa)
    Resolution: 1920x1080@59.93hz
    GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail) GLX Version: 3.0 Mesa 17.0.3
    Audio: Card Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Low Power Engine Audio
    driver: HdmiLpeAudio
    Sound: Advanced Linux Sound Architecture v: k4.12.0-041200rc4-generic
    Network: Card: Failed to Detect Network Card!
    Drives: HDD Total Size: 2.0GB (Used Error!)
    ID-1: /dev/mmcblk0 model: N/A size: 62.5GB
    ID-2: USB /dev/sda model: Storage_Device size: 2.0GB
    Partition: ID-1: / size: 47G used: 7.8G (17%) fs: btrfs dev: /dev/mmcblk0p14
    ID-2: /home size: 47G used: 7.8G (17%) fs: btrfs dev: /dev/mmcblk0p14
    RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
    Sensors: System Temperatures: cpu: 59.0C mobo: N/A
    Fan Speeds (in rpm): cpu: N/A
    Info: Processes: 215 Uptime: 1:13 Memory: 1008.3/3852.3MB Client: Shell (bash) inxi: 2.3.8

    ReplyDelete
  6. Hey man great work, thanks for your effort. The iso you provided works great in live, I'm installing now to see if the installation goes well. On a side note, I know that some people have gotten used to unity but damn, gnome looks good in ubuntu colors :). Oh and apparently the 4.12-rc4 fixed a battery issue on my machine, where the battery was not recognized, so the indicator would not show. I think I read somewhere that half the 4.12 kernel is drivers, so I guess that was correct. Has any of you had time to test the stability of rc4(?), cause if everything goes well I'm thinking of keeping this as my daily driver for about a month, until I finish my exams and have time to find something more recent by those standards.

    ReplyDelete
    Replies
    1. There will still be a few more 'rc' kernels before v4.12 is released in a few weeks so the timing looks good as it will probably be ready for use after your exams.

      Delete
    2. Ok I'll wait for the stable 4.12 and keep this release candidate for testing, the installation didn't succeed either way, so I'll just chill until after the exams to experiment more, I guess I'm stuck with windows for now. Again, great work and thanks a lot.

      Delete