Language Selection

English French German Italian Portuguese Spanish

Ubuntu Desktop and Server

Filed under
Ubuntu
  • Ubuntu 17.10 Breaks the BIOS on Some Lenovo Laptops

    If you get a Lenovo laptop for xmas and plan on installing Ubuntu 17.10 on it take my advice and don’t.

    You heard me: do not install Ubuntu.

    According to bug reports filed on Launchpad, the official Ubuntu bug tracker, installing Ubuntu 17.10 may inadvertently corrupt the BIOS on a raft of Lenovo laptops, including the Lenovo Yoga line.

    Which is seriously bad news.

    Those affected say that after installing Ubuntu 17.10 the BIOS on their device is no longer able to save settings (like changing boot order and device, which is often required when dual-booting), that settings reset after a reboot, some are not able to exit BIOS, while others are left unable boot from USB.

  • Ubuntu Server Development Summary – 19 Dec 2017

    The purpose of this communication is to provide a status update and highlights for any interesting subjects from the Ubuntu Server Team. If you would like to reach the server team, you can find us at the #ubuntu-server channel on Freenode. Alternatively, you can sign up and use the Ubuntu Server Team mailing list.

More in Softpedia

  • Ubuntu 17.10 Corrupts the BIOS of Some Lenovo Laptops, Respin ISOs Coming Soon

    Lubuntu developer Simon Quigley informs us that many users are reporting corrupt BIOS on their Lenovo laptops when attempting to install the latest Ubuntu 17.10 (Artful Aardvark) operating system.

    The issue is causing the BIOS of several Lenovo laptops to no longer save new settings. Once you've installed Ubuntu 17.10 and you reboot the laptop, the system will start with the old BIOS settings. The cause appears to be related with the intel-spi-* drivers in the Linux kernel, which aren't ready for use.

    Lenovo B40-70, Lenovo B50-70, Lenovo B50-80, Lenovo Flex-10, Lenovo G40-30, Lenovo G50-70, Lenovo G50-80, Lenovo S20-30, Lenovo U31-70, Lenovo Y50-70, Lenovo Y70-70, Lenovo Yoga Thinkpad (20C0), Lenovo Yoga 2 11" - 20332, Lenovo Z50-70, Lenovo Z51-70, and Lenovo IdeaPad 100-15IBY are among the Lenovo laptops known to be affected by the issue. A Toshiba S50t-B laptop is also affected.

In Phoronix

  • Ubuntu 17.10 Temporarily Pulled Due To A BIOS Corrupting Problem

    Canonical has temporarily pulled the download links for Ubuntu 17.10 "Artful Aardvark" from the Ubuntu website due to ongoing reports of some laptops finding their BIOS corrupted after installing this latest Ubuntu release. The issue is appearing most frequently with Lenovo laptops but there are also reports of issues with other laptop vendors as well.

    This issue appears to stem from the Intel SPI driver in the 17.10's Linux 4.13 kernel corrupting the BIOS for a select number of laptop motherboards. Canonical is aware of this issue and is planning to disable the Intel SPI drivers in their kernel builds. Canonical's hardware enablement team has already verified this works around the problem, but doesn't provide any benefit if your BIOS is already corrupted.

More on this

  • Canonical pulls Ubuntu 17.10 over UEFI corruption issue

    Canonical has pulled downloads for its Ubuntu 17.10 Linux distribution following reports that it can trigger a bug in the UEFI firmware of selected Lenovo, Acer, and Toshiba laptops, corrupting the BIOS and disabling the ability to boot from USB Drives.

  • Ubuntu 17.10 can brick some laptops

    Downloads of Ubuntu 17.10 have been disabled due to an issue that can cause it to corrupt the firmware on some laptops. Lenovo laptops appear to be the most affected, but the problem is apparently not limited to them. The intel-spi driver has been named as the source of the problem; it's not clear whether other distributions may also be affected. If you downloaded 17.10, you might want to hold off on installing it.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

GNOME Desktop: Flatpak and Random Wallpaper Gnome Extension

  • Flatpak in detail, part 2
    The first post in this series looked at runtimes and extensions. Here, we’ll look at how flatpak keeps the applications and runtimes on your system organized, with installations, repositories, branches, commits and deployments.
  • Flatpak – a history
    I’ve been working on Flatpak for almost 4 years now, and 1.0 is getting closer. I think it might be interesting at this point to take a retrospective look at the history of Flatpak.
  • Random Wallpaper Gnome Extension Changes Your Desktop Background With Images From Various Online Sources
    Random Wallpaper is an extension for Gnome Shell that can automatically fetch wallpapers from a multitude of online sources and set it as your desktop background. The automatic wallpaper changer comes with built-in support for downloading wallpapers from unsplash.com, desktopper.co, wallhaven.cc, as well as support for basic JSON APIs or files. The JSON support is in fact my favorite feature in Random Wallpaper. That's because thanks to it and the examples available on the Random Wallpaper GitHub Wiki, one can easily add Chromecast Images, NASA Picture of the day, Bing Picture of the day, and Google Earth View (Google Earth photos from a selection of around 1500 curated locations) as image sources.

today's howtos

KDE: QtPad, Celebrating 10 Years with KDE, GSoC 2018

  • QtPad - Modern Customizable Sticky Note App for Linux
    In this article, we'll focus on how to install and use QtPad on Ubuntu 18.04. Qtpad is a unique and highly customizable sticky note application written in Qt5 and Python3 tailored for Unix systems.
  • Celebrating 10 Years with KDE
    Of course I am using KDE software much longer. My first Linux distribution, SuSE 6.2 (the precursor to openSUSE), came with KDE 1.1.1 and was already released 19 years ago. But this post is not celebrating the years I am using KDE software. Exactly ten years ago, dear Albert committed my first contribution to KDE. A simple patch for a problem that looked obvious to fix, but waiting for someone to actually do the work. Not really understanding the consequences, it marks the start of my journey within the amazing KDE community.
  • GSoC 2018 – Coding Period (May 28th to June 18th): First Evaluation and Progress with LVM VG
    I got some problems during the last weeks of Google Summer of Code which made me deal with some challenges. One of these challenges was caused by a HD physical problem. I haven’t made a backup of some work and had to rework again in some parts of my code. As I already knew how to proceed, it was faster than the first time. I had to understand how the device loading process is made in Calamares to load a preview of the new LVM VG during its creation in Partition Page. I need to list it as a new storage device in this page and deal with the revert process. I’ve implemented some basic fixes and tried to improve it.

Open Hardware: Good for Your Brand, Good for Your Bottom Line

Chip makers are starting to catch on to the advantages of open, however. SiFive has released an entirely open RISC-V development board. Its campaign on the Crowd Supply crowd-funding website very quickly raised more than $140,000 USD. The board itself is hailed as a game-changer in the world of hardware. Developments like these will ensure that it won't be long before the hardware equivalent of LEGO's bricks will soon be as open as the designs built using them. Read more