Ubuntu GNOME - Corrupted screen at boot...HELP!


Recommended Posts

I'm having some trouble with Ubuntu. Kindly note that I am a newbie to Linux. This is my hardware setup:

 

MSI AM1 motherboard: https://www.msi.com/Motherboard/AM1I.html#hero-overview

Processor: AMD Sempron APU 2650 1.45 Ghz with Radeon R3 graphics

RAM: Corsair 4 GB DDR3 (single stick)

 

I have installed Ubuntu GNOME 16.04 after a few tries. The issue I faced during installation and the one I face during boot is a corrupted display. I have to turn off / reset the system multiple times before it works. I have updated it fully after installation, and also installed a proprietary AMD driver that was under the Additional Drivers section.

 

I get the GRUB boot screen below:

IMG_20160703_134659.jpg

 

After I select it, I get this:

IMG_20160703_134713.jpg

 

I have to hard reset / turn off the system multiple times before it boots.

 

Please help!! :cry::cry:

It looks like a video driver incompatibility. I would reboot until you get a usable system up and running, back up all of your important data then look for another video driver (either the Ubuntu suggested or another version of the proprietary driver). You might also want to try different versions of either Ubuntu or a variation (like Mint or Debian) in a Live CD to see if the video works better with one of them. As another alternative, you could try Xubuntu for a different desktop since it uses less resources than Gnome or KDE.

 

Hope that this helps!

1 minute ago, Barney T. said:

It looks like a video driver incompatibility. I would reboot until you get a usable system up and running, back up all of your important data then look for another video driver (either the Ubuntu suggested or another version of the proprietary driver. You might also want to try different versions of either Ubuntu or a variation (like Mint or Debian) in a Live CD to see if the video works better with one of them.

 

Hope that this helps!

But the thing is, it does eventually boot with the exact same settings (BIOS). Earlier today I was configuring software and users in Ubuntu, no issues. The issue is only during boot. I tried booting with a Mint distro, same graphic corruption. So it is definitely a graphics issue, just that it happens before booting. If and when it eventually boots, everything works perfectly. Also, no drivers showed up under Additional Drivers in the OS.

Yeah, this is a tough one. Since drivers load at boot up, I think that it is an incompatibility instead of a corruption (since you can get it booted up from time to time. here is an incompatibility with the distro and your boot up. Again, if there are valuable files on this computer, I would save them first. Then you can try other distros or solutions.

 

Some others having this problem:

 

http://askubuntu.com/questions/460591/ubuntu-14-04-screen-corruption-on-live-desktop-amd-7970

 

http://www.computerhope.com/forum/index.php?topic=127818.0

You'li have to try the Live CD. Linux distros can be burned in .iso format as an image file and booted up as a Live CD. This installs the distro to RAM instead of the had drive. Then, you can see if it works better with your hardware. Post how this works and we can move forward! Each distro has it's own make up so the driver make-up could be different. Based on your computer hardware, the results will be different. Good luck and let us know.

40 minutes ago, Barney T. said:

You'li have to try the Live CD. Linux distros can be burned in .iso format as an image file and booted up as a Live CD. This installs the distro to RAM instead of the had drive. Then, you can see if it works better with your hardware. Post how this works and we can move forward! Each distro has it's own make up so the driver make-up could be different. Based on your computer hardware, the results will be different. Good luck and let us know.

I've tried with Fedora and Mint. They don't even let me boot into the Live environment! Same corrupted screen when I select the boot without installing options in each of them.

23 minutes ago, Mindovermaster said:

Tried exactly like mentioned in the link you gave, same problem.

Hmmm, looks like something in your hardware might not be compatible with Linux. The fact that other distros are unable to fix this problem points to hardware (still most likely your video card). Also, your GRUB menu boots up fine, so I believe that Ubuntu is installed correctly on your hard drive. Another option is to try another video card (if you have one lying around) and try to boot up using that instead. NVIDIA has always had a better track record with Linux.You'd have to select it in the BIOS or in the Linux settings. I am sorry that you are having such problems! :(

45 minutes ago, Barney T. said:

NVIDIA has always had a better track record with Linux.

Truth, that. When I moved from my Radeon 7850 to my 750Ti, my system became a lot better...

3 hours ago, Mindovermaster said:

thats exactly what i was thinking tbh, Linux Mint 18 did this with me also, nomodeset fixed this issue for me on mint (intel HD gfx)

I've run into this issue before. It's always, always driver-related. It's got nothing to do with your hardware "going bad" or anything, so don't panic. :) 

 

Common problem. Nvidia users will see this a lot when using the open-source driver, and it will mostly correct itself; ie, there will still be artifacts on the screen but the user can at least get the system installed and then the proprietary drivers installed afterwards and the problem is eliminated upon next reboot.

 

I've only ever had one chipset that had Radeon R3 graphics on the chip in the house, a 5350 APU, and I never could get it running properly with Linux. Installed Windows on it and it's actually a fairly decent machine for what it is.

 

My advice is to get yourself a cheap Nvidia card, like a 610. They're $35~$55 on Newegg, and they'll push most games ... if you turn the graphics settings all the way down. I could get 25~55 fps in The Secret World with my old one. That's playable in my book. :yes: 

11 hours ago, Unobscured Vision said:

I've run into this issue before. It's always, always driver-related. It's got nothing to do with your hardware "going bad" or anything, so don't panic. :) 

 

Common problem. Nvidia users will see this a lot when using the open-source driver, and it will mostly correct itself; ie, there will still be artifacts on the screen but the user can at least get the system installed and then the proprietary drivers installed afterwards and the problem is eliminated upon next reboot.

 

I've only ever had one chipset that had Radeon R3 graphics on the chip in the house, a 5350 APU, and I never could get it running properly with Linux. Installed Windows on it and it's actually a fairly decent machine for what it is.

 

My advice is to get yourself a cheap Nvidia card, like a 610. They're $35~$55 on Newegg, and they'll push most games ... if you turn the graphics settings all the way down. I could get 25~55 fps in The Secret World with my old one. That's playable in my book. :yes: 

 

14 hours ago, Barney T. said:

Hmmm, looks like something in your hardware might not be compatible with Linux. The fact that other distros are unable to fix this problem points to hardware (still most likely your video card). Also, your GRUB menu boots up fine, so I believe that Ubuntu is installed correctly on your hard drive. Another option is to try another video card (if you have one lying around) and try to boot up using that instead. NVIDIA has always had a better track record with Linux.You'd have to select it in the BIOS or in the Linux settings. I am sorry that you are having such problems! :(

 

Looks like my only option is to run Windows on it then. The problem is this is a Mini ITX board, so there is only 1 PCI-E slot. I need this slot later on for a LAN card, as I intend to have a PFSense router VM running as well.

 

Thanks for all your help! :)

Understood. Yeah, that would be a problem. I suggest you try an older version of Mint based on 14.04 Ubuntu that has the proprietary drivers, such as 17.3. It'll be supported until 2019, and AMD have already said they're going to have something figured out by the end of the year.

 

Unless this was Mint 17.3/Ubuntu 14.04.x; in which case yeah .. but my own experience says you'll end up much the same way I did -- getting Windows for that particular hardware.

 

I have to say that for AMD being a full member of the OSS Foundation and everything, they sure are a bunch of foot-dragging sloths when it comes to actually supporting their own products on Linux and having some proper drivers. It's quite disgusting, really.

On 7/4/2016 at 8:17 PM, Unobscured Vision said:

Understood. Yeah, that would be a problem. I suggest you try an older version of Mint based on 14.04 Ubuntu that has the proprietary drivers, such as 17.3. It'll be supported until 2019, and AMD have already said they're going to have something figured out by the end of the year.

Oh, so 17.3 will not give me this problem then? If yes, that would be awesome! I tried the latest MInt 18 and plain Ubuntu 16.04. Strange that the older version of the OS has the drivers and not the new!! :s

Actually I think I'll just proceed with installing WIndows on it. It is an additional cost because of the license, but it is hassle free. And I can always run OwnCloud and PFSense in VM's. :)

 

Do you think this setup will be up to the task? Windows 10, the above mentioned VM's and incremental backups from computers on LAN. Incremental individual files that is, not image backups.

  • 2 weeks later...
On 7/3/2016 at 7:26 AM, Barney T. said:

Hmmm, looks like something in your hardware might not be compatible with Linux. The fact that other distros are unable to fix this problem points to hardware (still most likely your video card). Also, your GRUB menu boots up fine, so I believe that Ubuntu is installed correctly on your hard drive. Another option is to try another video card (if you have one lying around) and try to boot up using that instead. NVIDIA has always had a better track record with Linux.You'd have to select it in the BIOS or in the Linux settings. I am sorry that you are having such problems! :(

You're right. Back in the early.. stone age days of Linux, 95-98-ish, I tried linux(AMD 600Mhz Slot A CPU day) but kept getting corrupt screens. my cards weren't up on drivers. So  I concur with Barney. even though that was many moons ago. But same exact problem. if you get your system back up, go to the forums and let the devs of the distros know of your issues. the only way for them to get the issue fixed.

This topic is now closed to further replies.
  • Posts

    • A coalition of publishers sued OpenAI and Microsoft over scraping content without consent by Hamid Ganji Image via Depositphotos.com AI companies often rely on readily available internet content to train their chatbots and provide users with instant answers. This method of AI training is fast and relatively inexpensive, but using a website’s content without permission or compensation is not something publishers like to see, and this is exactly why Microsoft and OpenAI are now being sued. As reported by Bloomberg, a group of publishers that collectively own nearly 400 newspapers has filed a lawsuit against OpenAI and Microsoft. The coalition argues that the two companies scraped their content to build AI chatbots like ChatGPT and Copilot without paying any compensation. The complaint, filed in the U.S. District Court for the Southern District of New York, argues that while AI products have generated billions of dollars in market value using publishers’ work, none of that value has been shared with the publishers. The plaintiffs are seeking statutory damages and injunctive relief for alleged copyright infringement and violations of the Digital Millennium Copyright Act. “Defendants systematically and secretly crawled the Publishers’ websites—including content behind paywalls and other access restrictions—and copied the Publishers’ articles, stories, and other original works onto their own servers without authorization,” the complaint states. The publishers also described the AI boom as a “death knell for local journalism” if AI companies that scrape content for free are not held accountable. Former New Jersey Attorney General Matthew Platkin and his law firm, Platkin LLP, are representing the publishers. “Our models empower innovation, are trained on publicly available data, and are grounded in fair use,” OpenAI spokesperson Drew Pusateri told Bloomberg. This is not the first lawsuit involving the unauthorized use of publishers’ content by AI firms, but it is one of the largest coalitions ever formed against the free use of content by AI chatbots. In 2024, OpenAI and Microsoft also faced a similar lawsuit from eight newspapers that claimed AI products were benefiting from their content without permission.
    • Rufus alternative Ventoy now supports Windows 11's mandatory update, fixes major boot bug by Sayan Sen While Microsoft has its own official Media Creation Tool used for making bootable USB media, there are some popular third-party utilities as well which offer additional options like bypassing system requirements, Microsoft Account creation, and more. One of these is Ventoy, and the software has received its latest update today. In fact, the app actually got a slew of updates over the last couple of days, three version releases in total, to be specific. The first release, version 1.1.13, was pulled as there was some unspecified error in the update, and as such, the corrected version 1.1.14 was pushed out. Following that on very short notice, 1.1.15 was published as well. For those unfamiliar, Ventoy is an open-source utility that lets users create a bootable USB drive once and then simply copy ISO, WIM, IMG, VHD, or EFI files onto it without repeatedly formatting the drive. It supports both legacy BIOS and UEFI boot modes, Secure Boot, and a wide range of operating systems, making it one of the most versatile tools in the category. The biggest change in version 1.1.14 is an updated Secure Boot shim file aimed at resolving the UEFI CA 2023 issue, which is basically a compatibility problem that has affected Secure Boot environments on some systems. If you recall, we reported about severe boot issues on HP devices following the release of updated Secure Boot 2023 keys. For anyone who may not be aware, back in early 2024, Microsoft announced that it was updating Secure Boot keys as they were going to become 15 years old in 2026, which is also when they are set to expire. As such, the new 2023 certificates have been rolling out with the newest Windows 11 updates. Updated boot manager and Secure Boot certificates are crucial for protection against malware like bootkits. These are mandatory updates. Alongside that, the VentoyPlugson graphical plugin configurator was updated in sync with the release. The update also introduces a new VTOY_SECURE_BOOT_POLICY option within the Global Control plugin, giving users more flexibility in managing Secure Boot behavior. Ventoy has also received a fix for a startup issue when Secure Boot was disabled. Microsoft does officially allow users to boot systems without Secure Boot as long as the PC is Secure Boot capable. The full changelog is given below: Update secure boot shim file to solve the UEFI CA 2023 issue. The new release use a new CA, so you need to enroll the new key for the first boot time. VentoyPlugson update synchronously. Global control plugin add a VTOY_SECURE_BOOT_POLICY option. Fix the boot issue when Secure Boot is disabled in the UEFI firmware. You can download the latest version of the app here on Ventoy's official GitHub repo or from Neowin software stories.
    • Windows 11 is fine, no issues on any of the machines I've run it on since release. The stricter security requirements are a good thing, sometimes the baseline needs to change and people will winge, but it is what it is. Happened with the move from 9x to NT - broke compatability Happened with XP SP2 when security started to become a serious consideration Certainly happend with Vista that brought in UAC, the concept of not running as admin (something that has been the norm in Linux/Unix from pretty much the start) and a completely new driver stack. Windows 11 will probably get looked back at as the point where even consumer and SMB IT was dragged kicking and screaming into a somewhat secure by default configuration.
    • Bluestacks has been emulating Android on Windows for fifteen years. It's janky and riddled with ads though, so WSA looked like it was going to be a huge improvement over the emulator experience. Too bad Microsoft dropped the ball on that.
    • Classic. China would be nothing without Western, Japanese, and South Korean technology.
  • Recent Achievements

    • Rookie
      krychek57 went up a rank
      Rookie
    • Grand Master
      Jaybonaut went up a rank
      Grand Master
    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      441
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      134
    4. 4
      Michael Scrip
      78
    5. 5
      Xenon
      77
  • Tell a friend

    Love Neowin? Tell a friend!