Whilst the first of January maybe a public holiday for some it didn't stop Canonical releasing new Ubuntu and Lubuntu 17.04 (Zesty Zapus) Daily Build ISOs. So I've re-spun them to includes the 4.9 kernel with all the latest drivers and fixes for Bay Trail and Cherry Trail devices.
This is my first Lubuntu Alpha build ISO for anyone wanting to test the latest development work with the lightweight variant of Ubuntu.
Also as some Cherry Trail devices use the RTL8723BS wifi chip I've fine tuned these latest ISOs to improve its support.
To try an ISO
Ubuntu comes with everything. All the essential applications, like an office suite, browsers, email and media apps come pre-installed and thousands more games and applications are available in the Ubuntu Software Centre.
Lubuntu is a fast, energy saving and lightweight variant of Ubuntu using LXDE. It is popular with PC and laptop users running on low-spec hardware.
66 comments:
Hi I installed Lubuntu 17.04 Alpha on a Pendo pad 7"
Install, boot and wifi works but not much else.
Outline of issue:
Touch Screen
Battery is found but stuck at 100%
No audio
Name of device:
Pendo 7"
MN: PNDPPW81QI7BLK
URL from pastebin:
https://paste.ubuntu.com/23751801/
Also have a HWiNFO32 I'll post up to my git hub
I will keep nutting away at it and try get every thing up and running.
thanks mate
Installed Lubintu on Vorke V1 (J3160).
Works a lot faster, than 16.04
Thanks!
Lubuntu
Ian, Thanks for the first working Linux for Minix Neo Z64A. Much appreciated.
I've been playing with the Lubuntu image (Lubuntu 17.04 Alpha0101 Linuxium). Will not report userland issues, because I've converted it to Mate, and that turned out a bit messy. Wifi performance is much improved vs your 16.04.1 LTS, no more huge CPU load.
One issue which occurs both on the install itself as on the Live SD is, that the system will never reboot or shutdown. It will show the splash screen animation, and ask to remove the installation media (Live image), but will never actually reboot. I left it for an hour once, but still not.
'shutdown -f now' also does not shutdown.
dmesg:
http://paste.ubuntu.com/23775376/
Thanks
joris
Hiya, big thanks for the new iso's :)
I installed the lubuntu one on my stick, started out great!
But when i started some youtube videos or music from soundcloud, I get random audio pops.. Might it be some power saver settings intefering maybe? Any tips/ideas to how I might fix it?
I randomly get half a second silence followed by a pop and sound comes back.
Regards, stianfan
Hi,
I've tried to install both the Ubuntu and Lbuntu images on BayTrail Intel Stick, both internal storage and to a ssd connected on a usb hub. In both cases, it installs fine, the EFI Boot shows up in the bios, but it does not want to boot from it. If I attempt to force it (F10 in bios for boot menu) it tries to boot, and returns to the bios.
Any ideas?
Thank you kindly,
D
Tried the ubuntu one, but it failed to install. got an dkpg error.
and btw my stick is called BOXSTK1AW32SC
stianfan
The shutdown/reboot issue is a known issue still to be fixed unfortunately.
What was the error?
Possibly the NVRAM is corrupt? Have you tried deleting all the boot entries using 'efibootmgr' and then recreating those you need?
1. Start with the ICS switched off.
2. Connect your LiveUSB (i.e. installation USB).
3. Power on the ICS and press F10 and boot from the USB.
4. Open a terminal windows and enter:
sudo su -
# if efibootmgr isn't already installed enter:
apt-get install efibootmgr
5. Remove any boot entries that may have been created through the earlier install or attempts to get things working by entering:
for BOOTENTRY in 0 1 2 3 4 5 6 7 8 9
do
efibootmgr -b ${BOOTENTRY} -B
done
6. Create an Ubuntu boot entry by entering:
efibootmgr -c -d /dev/mmcblk0 -p 1 -l \\EFI\\ubuntu\\grubx64.efi -L Ubuntu
7. Reboot and press F10 and boot from the newly created Ubuntu entry.
Note: This assumes you are booting from the 64-bit bootloader. If not you will need to modify the command in step 6 from 'grubx64.efi' to 'grubia32.efi'.
Thanks a lot! I will give this a try :) (I assumed deleting the efi partition sorts this, and it is recreated by the installer).
I re-downloaded the ISO and tried it again with DD mode in rufus, got a second error now: Error installing grub-efi-amd64-signed.
subprocess installed post-installation script returned error exit status 1
Then i tried it again writing is ISO mode in rufus and got the same error.
Seems like i got some corruption in my first DL, but still won't install for me.
Then I DL'ed the "faster boot" one from your previous post, that one worked fine.
Booting Try before option, or just install doesn't seem to make any difference.
Hope this helps :-)
oh, and also noticed that when i click past that error it tells me:"An error occured while instaling packages:
E:Sub-process/usr/bin/dpkg returned an error code (1)
The following packages are in a broken state:"
But there is nothing listed.
Deleting the EFI partition and adding new entries through the installer is often how the NVRAM gets corrupt as it seems to get out of sync. Using 'efibootmgr' is often the best/only way to fix it.
Most likely a package version has changed that I've missed or being an alpha build something has changed and is no longer compatible. In the interim, try installing without being connected to the internet (or vice-versa if your weren't connected) as this sometimes works as a workaround.
Tried with and without internet, looks like the same error. It fails to install grub, but doing so manually doesn't get the install to boot either.
FYI Android 7.1.1 x86_64 has been released with the 4.9 kernel, can you check it out and email them your patches since it sounds like they need em. :) https://groups.google.com/forum/#!topic/android-x86/MdaiRnECwtU
Hey I was wondering if you found a solution? I am also getting this error when installing the ubuntu 17.04 iso. Weirdly the Lubuntu version of the ISO installs fine but has no sound and I get lots of broken dependencies when installing packages. The Ubuntu version has working sound and packages install fine when I used to live version but It wont install
I did not unfortunately, so I'm sticking with 16.04 for now.
Thank you for the above distro works brilliantly on my LINX 1010 finds all of the hardware including the sound. i have had problems with trying to install it to the i "hdd"(i now it isnt) but i think i need to clear out the UEFI of all old UBUNTU installs.
many thanks
Nigel
Tried lubuntu on "Morfine M1+" stick. Wifi, sound and video works. gnome-mplayer has problem playing video but mpv works fine.
Overall better than Windows 10.
Booted Lubuntu in live mode on Prestigio Smartbook 116A. Wifi works, but it seems me the sound works only after initial boot into Windows 10. The battery shows 100% all the time.
Thanks for providing this.
I've tried zesty-lubuntu-desktop-alpha-010117-linuxium.iso and get a blank screen. The blanks screen can be cleared by setting i915.modeset=0 on the linux line in the grub config.
I have read that this kernel patch fixes the issue https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=bb98e72adaf9d19719aba35f802d4836f5d5176c. Is this patch in yout kernel?
Thanks
I'm currently building new kernels and ISOs.
Sometimes the NVRAM gets confused and a 'reset' is required to fix it.
Unfortunately Morefine the company isn't interested in running Ubuntu on their devices.
Battery needs some additional patches which I am looking in to.
The patch is not in my released kernels but is in my development version which I am currently working on.
Hi Ian,
FYI, Got the exact same problem as Stian Fanavoll for Ubuntu, and Lubuntu is working fine. Have installed it on a Tablet, so i think ubuntu is better for the touch screen.
Thanks,
Andre
Thanks for the efforts~!
I have Acer Switch 10, I tried the 17.04 Alpha Ubuntu load 010117. it has a broadcom sdio wifi, with firmware not loading. dmesg | grep [i dont remember what I grepped for] gives:
mmc0:0001:1: Direct firmware load for brcm/brcmfmac43241b4-sdio.bin failed with error -2.
Is this enough info?
Does this need a change built into the kernel, or is this something I can fix with a local mod outside of building a kernel?
I found the file that was mentioned in the message in /lib/firmware/brcm/.
Mike.
Tried on an ezbook 2 wifi work fine, boot speed is good but no sound, and battery indicator is not really optional for a netbook, funny fact when the battery is empty actually this machine just crash but don't turn off, need to force it to shutdown, thanks for your hard work. Amazing project. Love it.
Please try my latest Ubuntu pseudo Alpha 2 ISO to see if this is now fixed.
Please try my latest Ubuntu pseudo Alpha 2 ISO to see if this is now fixed. If not, please make sure you have copied over the relevant NVRAM wifi text file from your Windows partition to see if this helps.
Please try my latest Ubuntu pseudo Alpha 2 ISO to see if this is now fixed. I've specifically added patches for the battery indicator.
Please try my latest Ubuntu pseudo Alpha 2 ISO as this is now fixed. This now supersedes the ISO above.
Yes, I will try it.
And if the NVRAM from windows needs to be tried, I will review and find how to do that.
OK, pseudo alpha 2 is going, I got the same error, but this time I found a USB wifi laying around, so I uploaded the dmesg output. paste.ubuntu.com/23891051
I'm not sure where to copy the text file from windows to... Is there a doc or a how-to?
I did copy all the broadcom stuff I could find in windows/sys32/drivers
I figured out what to do with the text file, and got the wifi working, , and I went to upload dmesg again and it took the session down. re-trying.
After rebooting, and redoing to use only the built-in card, I can install "pastebinit", when I try to pipe the dmesg output into "pastebinit", the session crashes.
Maybe the text file from windows for the NVRAM has some settings that don't work. I found the text file in windows from the listed drivers. I copied the file into a new file in /lib/firmware/brcm/ called brcmfmac43241b4-sdio.txt .
I saved the dmesg output to a file, as well, I can try to "pastebinit" it, as well as the contents of the windows txt file.
The dmesg output that would show the modpribe when I got the broadcom card working is: 23891666
(I pasted the file I had saved earlier.)
The contents of the text file from windows is in 23891671 .
For the wifi issue did you copy across the Windows driver file stored in NVRAM? The file should look something like '/sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113' and you should copy it using 'cat /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 > /lib/firmware/brcm/brcm/brcmfmac43241b4-sdio.txt'. Substitute the NVRAM filename your find for the 'nvram-*' filename in the command.
I've also released a version 2 of the pseudo Alpha 2 ISO so I'd be interested to hear how well that works on your device. The wifi still might not work until your copy across the Windows driver NVRAM file and also run 'sudo modprobe -r brcmfmac' followed by 'sudo modprobe brcmfmac' as before.
I've respun my pseudo Ubuntu 17.04 pseudo Alpha 2 ISO as version 2. Please give it a try to see if it works better on your device.
Hi there
Any news on this issue?
Thanks
OK, I'll try #3 version and try getting the NVRAM correctly, I was doing it wrong.
I'll answer back to a newer blog entry.
nice work!
only one step away for daily usage.
device:
CSL Panther Tab 7 (Z3735G 1GB RAM)
working:
Wifi, Sound, Touch, Accelerometer, USB OTG
not working:
- auto rotate ( fixed with scripting https://gist.github.com/Links2004/5976ce97a14dabf773c3ff98d03c0f61 )
- back light control ( screen LEDs always on )
- without intel_idle.max_cstate=2 the system Freeze
dmesg: https://gist.github.com/Links2004/93987ab3f0ae79423d1ccd548ce9320d
the backlight problem is the only think blocking my from us it as main system, need to much battery if it stays on.
have tried some kernel parameters for backlight but no they have no effect.
video.use_bios_initial_backlight=0
acpi_backlight=vendor
i915.force_backlight_pmic=1
not getting any useful controls in /sys/class/backlight/
dmesg shows two think you may want to look for
- a stack trace for mmc
- [drm:pwm_setup_backlight [i915]] *ERROR* Failed to own the pwm chip
Would you be willing to try a test kernel build to see if it addresses backlighting? I'd provide it as a kernel update script which means after testing you can simply purge the test kernel to return to the 'before testing' state.
sure, with windows the tablet is useless anyway ;)
I've updated my 'Bleeding edge Ubuntu 4.10.0-5.7 kernel with 17.04 pseudo Alpha 2 ISO' (see http://linuxiumcomau.blogspot.com.au/2017/01/bleeding-edge-ubuntu-4100-57-kernel.html) with a new ISO and kernel update script that should now help with the backlight issue. If you had previously installed my Version 3 release 2 ISO then you can simply download and install the Version 4 kernel upgrade script. If in any doubt it is better to download and use Version 4 ISO to ensure full support for the patched kernel.
have tried the kernel update, and ISO booting no change.
with out acpi_backlight=vendor i get a non functional
/sys/class/backlight/acpi_video0 and with it noting.
the logs still shows
[drm:pwm_setup_backlight [i915]] *ERROR* Failed to own the pwm chip
I can provide you more logs or dumps from the system if you need some.
some good news i have found the GPIO's for the volume keys.
GPIO 410 is volume down
GPIO 411 is volume up
gpiochip0: GPIOs 410-511, parent: platform/INT33FC:00, INT33FC:00:
gpio-0 (sysfs ) in hi pad-85 offset:0xaa0 mux:0 up 20k
gpio-1 (sysfs ) in hi pad-89 offset:0xb20 mux:0 up 20k
currently I have no idea how I get linux to send them as keyboard input.
@Links2004: Can you test backlight on https://goo.gl/BYADSn please?
@Linuxium does not work, no change in the dmesg (Failed to own the pwm chip)
Thanks. I'll have to think on this some more!
Hi Ian,
had issues when installing the Ubuntu 16.10 directly.
after I installed Ubuntu 16.10, my compute stick can't find a bootable device.
So, what I did was, install Ubuntu 14.04 and then upgrade to 16.10.
My system was able to boot with Ubuntu 16.10.
I do get some, once in a while system hangs.
I'm not sure what I missed out during the installation procedure.
I have an Intel Compute Stick STCK1A32WFC.
noel
(noelbee@gmail.com)
I'd recommend you try my latest ISOs at http://linuxiumcomau.blogspot.com.au/2017/02/ubuntu-16042-and-updated-ubuntu-1704.html
thanks! will give it a shot :).
By the way, do you have a recommended Docker App for your images?
I've installed Cairo-Dock but still I get errors from time to time. :(
Hi Ian,
just tried it, but still I got the same results.
I'm redirected to the EFI Shell once I rebooted my compute stick after installation.
are there any additional steps or scripts to run before restarting the compute stick?
Please try the seven command in my reply '17 January 2017 at 02:58' to 'Unknown' above. Deleting and adding new entries through the installer is often how the NVRAM gets corrupt as it seems to get out of sync. Using 'efibootmgr' is often the best/only way to fix it.
Hi Ian,
I've tried the steps as suggested, but here's what I got.
noel
----------------------------------------------------
root@ubuntu:~# efibootmgr -v
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0002,0000
Boot0000* ubuntu VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0001* UEFI : USB : Generic Flash Disk 8.07 : PART 0 : OS Bootloader PciRoot(0x0)/Pci(0x1d,0x0)/USB(0,0)/USB(0,0)/USB(1,0)/HD(1,MBR,0x90,0x800,0xe78800)..BO
Boot0002* UEFI : Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
root@ubuntu:~# for i in 0 1 2 3 4 5 6 7 8 9
> do
> efibootmgr -b $i -B
> done
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0002
Boot0001* UEFI : USB : Generic Flash Disk 8.07 : PART 0 : OS Bootloader
Boot0002* UEFI : Built-in EFI Shell
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0002
Boot0002* UEFI : Built-in EFI Shell
BootCurrent: 0001
Timeout: 2 seconds
No BootOrder is set; firmware will attempt recovery
Could not delete variable: No such file or directory
Could not delete variable: No such file or directory
Could not delete variable: No such file or directory
Could not delete variable: No such file or directory
Could not delete variable: No such file or directory
Could not delete variable: No such file or directory
Could not delete variable: No such file or directory
root@ubuntu:~# efibootmgr -v
BootCurrent: 0001
Timeout: 2 seconds
No BootOrder is set; firmware will attempt recovery
root@ubuntu:~# efibootmgr -v
BootCurrent: 0001
Timeout: 2 seconds
No BootOrder is set; firmware will attempt recovery
root@ubuntu:~# efibootmgr -c -d /dev/mmcblk0 -p 1 -l \\EFI\\ubuntu\\grubx64.efi -L Ubuntu
Could not prepare Boot variable: No such file or directory
root@ubuntu:/dev# find / -name grubx64* -print
/media/ubuntu/e3d37f9d-51de-49d5-84c1-369c3bb892f1/usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed
/cdrom/EFI/BOOT/grubx64.efi
find: ‘/run/user/999/gvfs’: Permission denied
root@ubuntu:/dev# ls -l /
total 4
drwxr-xr-x 2 root root 3468 Jan 27 07:48 bin
drwxr-xr-x 4 root root 60 Feb 23 16:01 boot
drwxr-xr-x 13 root root 4096 Jan 1 1970 cdrom
drwxr-xr-x 21 root root 4380 Feb 23 16:01 dev
drwxr-xr-x 145 root root 560 Feb 23 16:01 etc
drwxr-xr-x 3 root root 60 Feb 23 16:01 home
lrwxrwxrwx 1 root root 33 Feb 21 16:04 initrd.img -> boot/initrd.img-4.10.0-9-linuxium
drwxr-xr-x 27 root root 60 Feb 23 16:01 lib
drwxr-xr-x 2 root root 43 Jan 27 07:33 lib64
drwxr-xr-x 3 root root 80 Feb 23 16:02 media
drwxr-xr-x 2 root root 3 Jan 27 07:33 mnt
drwxr-xr-x 3 root root 39 Jan 27 07:43 opt
dr-xr-xr-x 237 root root 0 Feb 23 16:01 proc
drwxr-xr-x 22 root root 350 Feb 21 16:04 rofs
drwx------ 6 root root 100 Feb 23 16:03 root
drwxr-xr-x 31 root root 960 Feb 23 16:02 run
drwxr-xr-x 2 root root 4746 Feb 21 16:04 sbin
drwxr-xr-x 2 root root 3 Jan 13 18:39 snap
drwxr-xr-x 2 root root 3 Jan 27 07:33 srv
dr-xr-xr-x 13 root root 0 Feb 23 16:01 sys
drwxrwxrwt 12 root root 300 Feb 23 16:17 tmp
drwxr-xr-x 14 root root 100 Feb 23 16:01 usr
drwxr-xr-x 20 root root 160 Feb 23 16:01 var
lrwxrwxrwx 1 root root 30 Feb 21 16:04 vmlinuz -> boot/vmlinuz-4.10.0-9-linuxium
----------------------------------------------------
I'd try re-installing Ubuntu now that your NVRAM is clear. You are installing Ubuntu to the eMMC as a complete disk installation?
yup, i'm installing Ubuntu to the eMMC as a complete disk installation, wiping out windows :)
so, another approach would be:
1. run Ubuntu using the USB Installer.
2. clear out NVRAM
for i in 0 1 2 3 4 5 6 7 8 9
> do
> efibootmgr -b $i -B
> done
3. run the Installation process
After that, it's rock N roll? I won't be getting the "No Boot device" error anymore?
I would boot from USB, clear out NVRAM, then reboot from USB and run the installation process.
cool! will do as per advise. :)
I'll provide a feedback once done.
thanks,
noel
hi! can i have the link for this iso?
See 'http://linuxiumcomau.blogspot.com/2019/03/ubuntu-announced-new-point-releases-for.html' for links to ISOs that are currently available.
Post a Comment
All comments now moderated so that spam can be deleted.