Page 1 of 3 123 LastLast
Results 1 to 10 of 24

Thread: HU: A bug from 17.10 that might affect us with 18.04-to-be...

  1. #1
    Join Date
    Oct 2008
    Location
    ExodusHair<Čubura
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    HU: A bug from 17.10 that might affect us with 18.04-to-be...

    Ignota nulla curatio morbi.

  2. #2
    Join Date
    Feb 2010
    Location
    South of the Maple Trees
    Beans
    9,316
    Distro
    Xubuntu 18.04 Bionic Beaver

    Re: HU: A bug from 17.10 that might affect us with 18.04-to-be...

    From the bug report.
    SRU Justification

    Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines.

    Fix: Disable this driver.

    Test Case: Fix has been verified by our HWE team on affected hardware.

    Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver.

    ---
    Cheers & Beers, uRock

  3. #3
    Join Date
    Aug 2006
    Beans
    613

    Re: HU: A bug from 17.10 that might affect us with 18.04-to-be...

    I blame the laptop manufacturers for going off-standard with their BIOS/UEFI builds.
    Ryzen 7 2700X / Corsair H115i / Asus B350M TUF Gaming / 32GB 3200MHz C14 Team Group Dark Pro/
    Asus Strix 1080 Advanced / 500GB Samsung 870 Evo / 1TB 2.5" SSD / BeQuiet! 1kW /
    Thermaltake Core V21 / Acer Predator X34A / Win10 / Kubuntu 21.04

  4. #4
    Join Date
    Feb 2010
    Location
    South of the Maple Trees
    Beans
    9,316
    Distro
    Xubuntu 18.04 Bionic Beaver

    Re: HU: A bug from 17.10 that might affect us with 18.04-to-be...

    Lenovo is known for their colorful BIOS builds. https://thehackernews.com/2015/09/le...top-virus.html
    Cheers & Beers, uRock

  5. #5
    Join Date
    Dec 2012
    Location
    Fancy Gap Virginia
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: HU: A bug from 17.10 that might affect us with 18.04-to-be...

    Greetings,

    Quote Originally Posted by uRock View Post
    Lenovo is known for their colorful BIOS builds.
    They are definitely building them.

    sudo dmidecode -s bios-vendor
    [sudo] password for rrnbtter:
    LENOVO
    rrnbtter@rrnbtter-110-15ISK:~$
    After Investigating all of this I think I did the right thing to wipe Win10, set bios to legacy and Install my 17.10 (now 18.04 dev) without UEFI. That being said, I have yet to see my 110-15isk on the list. But it is a Lenovo Bios.
    Last edited by rrnbtter; December 22nd, 2017 at 04:46 PM.

  6. #6
    Join Date
    Aug 2016
    Location
    Wandering
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: HU: A bug from 17.10 that might affect us with 18.04-to-be...

    Quote Originally Posted by rrnbtter View Post
    Greetings,



    They are definitely building them.

    sudo dmidecode -s bios-vendor
    [sudo] password for rrnbtter:
    LENOVO
    rrnbtter@rrnbtter-110-15ISK:~$
    After Investigating all of this I think I did the right thing to wipe Win10, set bios to legacy and Install my 17.10 (now 18.04 dev) without UEFI. That being said, I have yet to see my 110-15isk on the list. But it is a Lenovo Bios.
    +1 Same here.
    Code:
    sudo dmidecode -s bios-vendor
    [sudo] password for me: 
    AMI
    And:
    Code:
    Machine:   Device: desktop System: HP product: 750-417c v: 1.01 serial: N/A
               Mobo: HP model: 828A v: 1.01 serial: N/A
               UEFI [Legacy]: AMI v: F.14 date: 09/19/2016
    HP's aren't much better.
    Try and install a Nvidia GPU card on one of these in UEFI with Windows 10.
    With realization of one's own potential and self-confidence in one's ability, one can build a better world.
    Dalai Lama>>
    Code Tags

  7. #7
    Join Date
    Jan 2010
    Location
    India
    Beans
    Hidden!
    Distro
    Ubuntu Budgie 20.04 Focal Fossa

    Re: HU: A bug from 17.10 that might affect us with 18.04-to-be...

    Hi, I am using Xubuntu 18.04. After reading all that I am feeling a bit nervous. How can I be sure this bug doesn't effect my hardware ?
    Code:
     $ sudo dmidecode -s bios-vendor [sudo] password for mypc:  American Megatrends Inc.
    I know I may be worrying for no reason but still needed to know I am safe.
    Last edited by linuxyogi; December 23rd, 2017 at 11:32 PM.
    Ubuntu Budgie 20.04

  8. #8
    Join Date
    Dec 2012
    Location
    Fancy Gap Virginia
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: HU: A bug from 17.10 that might affect us with 18.04-to-be...

    Greetings,
    Are you dual booting Windows OS?
    What kernel are you using, output of "uname -a".
    If it is just a linux install, output of [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
    Just for starter's.

  9. #9
    Join Date
    Jan 2010
    Location
    India
    Beans
    Hidden!
    Distro
    Ubuntu Budgie 20.04 Focal Fossa

    Re: HU: A bug from 17.10 that might affect us with 18.04-to-be...

    Quote Originally Posted by rrnbtter View Post
    Greetings,
    Are you dual booting Windows OS?
    What kernel are you using, output of "uname -a".
    If it is just a linux install, output of [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
    Just for starter's.
    No I am not dual booting Windows.

    Code:
    $ uname -a
    Linux mypc 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
    Code:
    $ [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
    EFI boot on HDD
    Ubuntu Budgie 20.04

  10. #10
    Join Date
    Dec 2012
    Location
    Fancy Gap Virginia
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: HU: A bug from 17.10 that might affect us with 18.04-to-be...

    Greetings,
    Not booting Windows = Good!
    Kernel 4.13.0-21 has been released to fix this problem. It is in the "Proposed" repos.
    If you are not booting Windows then a Legacy install is the safer option.

    Note: It seems to me that much of this problem is due to bios tampering on behalf of the PC vendors. So the question as to whether you are at risk at all may be hard to determine. Lenovo has been the big culprit but the problem has been found elsewhere.

    If it were me, I would backup /Home and set the bios to legacy and reinstall.
    Last edited by rrnbtter; December 23rd, 2017 at 07:40 PM.

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •