Another AMD Dual Boot Problem

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
TiBike
Level 2
Level 2
Posts: 88
Joined: Sun May 04, 2014 12:29 pm

Another AMD Dual Boot Problem

Post by TiBike »

Hi All,

My Mint20 / Windows 10 dual boot installation is giving me grief. I’m keen to persist – don’t want to go back to just WIndoze. From another thread I started - lots of solutions but the issues have now evolved - I understand it’s down to a driver problem not uncommon with AMD processors. The wonderful guys there have helped me get this far, but now it seems it needs AMD-specific experience. I’ve followed the first part of the ‘Solving freezes during the boot sequence’ fix in the Release Notes, so can now boot into Mint if I hit ‘e’ and replace ‘quiet splash’ with ‘nomodeset’. But without the nomodeset option, if I try to boot into Mint then it loops back to the Grub screen after several seconds, and this is then frozen and all I can do is hold the power button to shutdown. Windows 10 is fine.

When I run the Driver Manager in Mint, I get 'Your computer does not need any additional drivers'. So I’m clueless what to do next.

But below is a pile of info I was asked for in the other thread (and one elsewhere), which I’m hoping will be useful.

Any help very much appreciated!

-----------------------------------------------------------

Before starting, I reset Windows 10 (6yr old inherited PC), and let it install all its updates. I’ve only given it permission to update once more since adding the Mint dual boot, although it may have updated slyly other times, but anyway symptoms haven’t changed, and I’ve now disabled updates.
For the dual boot, I mostly followed this tutorial: https://www.tecmint.com/install-linux-m ... uefi-mode/
- I used ‘Something else’, like the tutorial says and cos that’s what I’d done years ago with Mint17 & WinXP on a prehistoric (now dying) PC.
- For swap I used 4Gb (seems I have 3Gb RAM?), and for root 20Gb (online advice seems to suggest 15Gb min and no point having much more than 20Gb).
- And for partition type, I used 'logical' for all 3 (the tutorial has conflicting advice on ‘logical’ or 'primary’).
- I’ve also turned off Fast Startup, and we found Secure Boot was already disabled & left the MSI Boot Mode setting as ‘UEFI’

Code: Select all

    
$ inxi -Fxnz
System:    Kernel: 5.4.0-47-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Xfce 4.14.2 Distro: Linux Mint 20 Ulyana 
           base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: MSI model: FM2-A55M-E33 (MS-7721) v: 2.0 serial: <filter> UEFI: American Megatrends v: 11.3 
           date: 07/16/2013 
CPU:       Topology: Dual Core model: AMD A4-5300 APU with Radeon HD Graphics bits: 64 type: MCP arch: Piledriver rev: 1 
           L2 cache: 1024 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 13574 
           Speed: 2622 MHz min/max: 1400/3400 MHz Core speeds (MHz): 1: 2695 2: 2695 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Trinity 2 [Radeon HD 7480D] vendor: Micro-Star MSI driver: N/A 
           bus ID: 00:01.0 
           Display: x11 server: X.Org 1.20.8 driver: ati,fbdev unloaded: modesetting,radeon,vesa resolution: 1280x1024~77Hz 
           OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Trinity HDMI Audio vendor: Micro-Star MSI driver: snd_hda_intel 
           v: kernel bus ID: 00:01.1 
           Device-2: Advanced Micro Devices [AMD] FCH Azalia vendor: Micro-Star MSI driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 
           Sound Server: ALSA v: k5.4.0-47-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel 
           port: e000 bus ID: 01:00.0 
           IF: enp1s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 223.57 GiB used: 6.87 GiB (3.1%) 
           ID-1: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB 
Partition: ID-1: / size: 18.21 GiB used: 6.69 GiB (36.7%) fs: ext4 dev: /dev/sda6 
           ID-2: /home size: 135.56 GiB used: 153.8 MiB (0.1%) fs: ext4 dev: /dev/sda7 
           ID-3: swap-1 size: 3.77 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 11.6 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 179 Uptime: 29m Memory: 3.12 GiB used: 1.07 GiB (34.4%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 
           Shell: bash v: 5.0.17 inxi: 3.0.38 

Code: Select all

$ sudo fdisk -l 
[sudo] password for xxxx:              
Disk /dev/sda: 223.58 GiB, 240057409536 bytes, 468862128 sectors
Disk model: KINGSTON SA400S3
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B1DDE742-8D84-4DB1-A24F-188189ECA27B

Device         Start       End   Sectors   Size Type
/dev/sda1       2048   1023999   1021952   499M Windows recovery environment
/dev/sda2    1024000   1226751    202752    99M EFI System
/dev/sda3    1226752   1259519     32768    16M Microsoft reserved
/dev/sda4    1259520 130940927 129681408  61.9G Microsoft basic data
/dev/sda5  130940928 138846207   7905280   3.8G Linux swap
/dev/sda6  138846208 177907711  39061504  18.6G Linux filesystem
/dev/sda7  177907712 468860927 290953216 138.8G Linux filesystem

Code: Select all

$ sudo blkid
/dev/sda1: UUID="FC6CD51D6CD4D40C" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="889a90f4-6dec-486a-bf84-7a1b82189f7f"
/dev/sda2: UUID="305A-AD2B" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="356faf0f-0bb8-45bd-bc78-95c9e39f7103"
/dev/sda4: UUID="7AF661BBF66177F1" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="af16dc70-5e6d-4f8e-b731-1173b961538b"
/dev/sda5: UUID="31069ebd-1e3c-4450-a61f-0ff0ba7aea66" TYPE="swap" PARTUUID="6af103d2-eb80-4d14-bdb2-f02361e37f44"
/dev/sda6: UUID="2d298611-db39-42da-a3d6-0484c0e8b678" TYPE="ext4" PARTUUID="aa6bcf18-283c-44a9-b570-62de479ffba5"
/dev/sda7: UUID="71bcf867-f262-4bb9-8306-ddfbfd8b3dbd" TYPE="ext4" PARTUUID="6dc126dd-3eb9-4bfc-95c0-3b421f8fc0c7"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="0a893a1d-bf58-4b6b-babd-ffb2d591c438"

Code: Select all

$ dmesg | grep -i "error\|warn\|fail\|microcode\|firmware"
[    0.006572] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20190816/tbfadt-615)
[    0.274691] acpi PNP0A03:00: _OSC failed (AE_SUPPORT); disabling ASPM
[    0.605385] Initramfs unpacking failed: Decoding failed
[    1.067080] RAS: Correctable Errors collector initialized.
[    1.067907] microcode: CPU0: patch_level=0x06001119
[    1.068925] microcode: CPU1: patch_level=0x06001119
[    1.069734] microcode: Microcode Update Driver: v2.2.
[    1.388019] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[    4.694242] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
[    5.932126] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
[   15.162974] random: 7 urandom warning(s) missed due to ratelimiting

Code: Select all

$ apt showxserver-xorg-video-amdgpu
apt
Usage: apt command [options]
       apt help command [options]

Commands:
  add-repository   - Add entries to apt sources.list
  autoclean        - Erase old downloaded archive files
  autoremove       - Remove automatically all unused packages
  build            - Build binary or source packages from sources
  build-dep        - Configure build-dependencies for source packages
  changelog        - View a package's changelog
  check            - Verify that there are no broken dependencies
  clean            - Erase downloaded archive files
  contains         - List packages containing a file
  content          - List files contained in a package
  deb              - Install a .deb package
  depends          - Show raw dependency information for a package
  dist-upgrade     - Upgrade the system by removing/installing/upgrading packages
  download         - Download the .deb file for a package
  edit-sources     - Edit /etc/apt/sources.list with your preferred text editor
  dselect-upgrade  - Follow dselect selections
  full-upgrade     - Same as 'dist-upgrade'
  held             - List all held packages
  help             - Show help for a command
  hold             - Hold a package
  install          - Install/upgrade packages
  list             - List packages based on package names
  policy           - Show policy settings
  purge            - Remove packages and their configuration files
  recommends       - List missing recommended packages for a particular package
  rdepends         - Show reverse dependency information for a package
  reinstall        - Download and (possibly) reinstall a currently installed package
  remove           - Remove packages
  search           - Search for a package by name and/or expression
  show             - Display detailed information about a package
  showhold         - Same as 'held'
  showsrc          - Display all the source package records that match the given package name
  source           - Download source archives
  sources          - Same as 'edit-sources'
  unhold           - Unhold a package
  update           - Download lists of new/upgradable packages
  upgrade          - Perform a safe upgrade
  version          - Show the installed version of a package
User avatar
Pjotr
Level 22
Level 22
Posts: 15501
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Another AMD Dual Boot Problem

Post by Pjotr »

Update your BIOS. This looks like it:
https://www.msi.com/Motherboard/support ... M-E33.html

Does that help any?
Tip: 10 things to do after installing Linux Mint 20 Ulyana
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
TiBike
Level 2
Level 2
Posts: 88
Joined: Sun May 04, 2014 12:29 pm

Re: Another AMD Dual Boot Problem

Post by TiBike »

Thanks, Pjotr. Update BIOS - Oh, OK, never done that before - scarey! My IT skills are pretty basic, but I know enough to check first if there are any risks or anything I should know about (noted your language is promising but not 100% confident :) )?

And I assume we're using 'BIOS' and 'UEFI' interchangeably here? From my limited reading, I'd understood they're two different things, and that UEFI (what I have) is a more modern replacement of BIOS interfaces.

And some questions on the 'Notes' that come with that latest BIOS release if you/someone wouldn't mind helping me through (their Notes in italics, my questions in plain font):

* Please download and execute the file in USB pen drive only. System will restart several times to update system BIOS with NVRAM & ROMHOLE. Please DO NOT remove the USB pen drive until BIOS updated successfully.
Do I just write the downloaded .rar file to an empty USB, plug it in, press the power button, and wait for a 'successful completion message'? Or not so simple? Or from quick search, maybe install WinRAR (or MInt equivalent) and extract the rar to the USB?

* Please make sure you have read the SOP before you update the BIOS.
Any idea where I find this? Maybe it'll be in the rar?

* Please use Trinity CPU to update BIOS before changing to Richland CPU.
Ignore this I suppose - stick with whatever CPU I have?

* There is no way to reflash back to BIOS version Axx if you already updated to version Bxx.
Again flags up questions of risk for me. But if the risks are minimal, of course I have expert advice :) .

Many thanks for the input!
User avatar
Pjotr
Level 22
Level 22
Posts: 15501
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Another AMD Dual Boot Problem

Post by Pjotr »

Your carefulness is very sensible. Because I've discovered something strange:

inxi says your motherboard is MSI model: FM2-A55M-E33 (MS-7721)

When I Google for FM2-A55M-E33, I come to the MSI BIOS webpage mentioned in my previous message, namely the webpage for the FM2-A55M-E33.
The number of the BIOS update on that webpage is strange, namely B.6. Which is odd because your current BIOS version number (according to inxi) is 2.0. It doesn't make sense that all of a sudden a B is introduced in the version number.

But when I Google for MS-7721, I come to this MSI BIOS webpage, which is for the FM2-A55M-E35:
https://www.msi.com/Motherboard/support ... M-E35.html
This time, the BIOS update number makes sense, namely 2.4 (which indicates it's the fourth update since 2.0).

I advise to boot into the BIOS settings and to verify what the right E number is: E33 or E35. My hunch is that you have the E35, but that's just a hunch....

Finally: everything you do, is fully at your own risk. There are no guarantees. A BIOS update gone wrong, might brick your motherboard.

But on the other hand: BIOS updates are there for a reason. They fix things that were broken. So personally, I always apply all BIOS updates for my machines. I always accept the risk (which did cost me a motherboard once, back in 2004, but that was the only time that things went wrong).
Tip: 10 things to do after installing Linux Mint 20 Ulyana
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
TiBike
Level 2
Level 2
Posts: 88
Joined: Sun May 04, 2014 12:29 pm

Re: Another AMD Dual Boot Problem

Post by TiBike »

Thanks for clarity on the risks, and for checking over the inxi output.

However, I can't find an E number in the BIOS/UEFI:
'Home' screen:
https://drive.google.com/file/d/1dAvh1I ... p=drivesdk
Settings -> System Status:
https://drive.google.com/file/d/1dBTBN6 ... p=drivesdk
I couldn't see an E number elsewhere, but probably you know better where to look?

On the other hand, from the Utilities tab I have a 'Live Update' option:
https://drive.google.com/file/d/1dGDLHk ... p=drivesdk
No idea if clicking on it would kick something off or give more options. Might it be safer route?
User avatar
Pjotr
Level 22
Level 22
Posts: 15501
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Another AMD Dual Boot Problem

Post by Pjotr »

TiBike wrote:
Sat Sep 12, 2020 8:22 am
On the other hand, from the Utilities tab I have a 'Live Update' option:
https://drive.google.com/file/d/1dGDLHk ... p=drivesdk
No idea if clicking on it would kick something off or give more options. Might it be safer route?
In this case: absolutely yes. I strongly advise to use the "Live Update" feature and nothing else.
Tip: 10 things to do after installing Linux Mint 20 Ulyana
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
TiBike
Level 2
Level 2
Posts: 88
Joined: Sun May 04, 2014 12:29 pm

Re: Another AMD Dual Boot Problem

Post by TiBike »

So clicking or double-clicking the 'Live Update' button does nothing. Zilch. Maybe it's a placeholder for software that's not installed? In any case, starting to Google that lack of response brings up a few forum posts reporting bricked MBs from MSI Live Update (saying eg. it's good for updating drivers but not BIOS).

So perhaps we're back to figuring out whether I have the E33 or E35? Any ideas how?

Or, possibly more comfortable for me (depending on the answer!), are there any other options for resolving the symptoms I have?

Thanks!
User avatar
Pjotr
Level 22
Level 22
Posts: 15501
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Another AMD Dual Boot Problem

Post by Pjotr »

What information does this method produce:
https://easylinuxtipsproject.blogspot.c ... html#ID7.2
(item 7.2)
Tip: 10 things to do after installing Linux Mint 20 Ulyana
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
TiBike
Level 2
Level 2
Posts: 88
Joined: Sun May 04, 2014 12:29 pm

Re: Another AMD Dual Boot Problem

Post by TiBike »

That also says E33. Is that all you wanted from that output? The Windows 'System Info' says the same. I certainly agree with you though that the version numbering seems appropriate for the E35.
User avatar
Pjotr
Level 22
Level 22
Posts: 15501
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: Another AMD Dual Boot Problem

Post by Pjotr »

TiBike wrote:
Sat Sep 12, 2020 1:07 pm
That also says E33. Is that all you wanted from that output? The Windows 'System Info' says the same. I certainly agree with you though that the version numbering seems appropriate for the E35.
I'm unsure how to proceed here. Perhaps it's best to forget about updating the BIOS.

The only safe method in this case, namely Live Update, appears to be impossible. However, there's this straw to clutch at: did you try Live Update when connected to the internet by ethernet cable? If not, do so now.
Tip: 10 things to do after installing Linux Mint 20 Ulyana
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
User avatar
SMG
Level 5
Level 5
Posts: 714
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Another AMD Dual Boot Problem

Post by SMG »

There are two main parts to graphics--a device driver and a display driver.

In order to be able to get the correct graphic driver, the kernel has to recognize the graphics card and assign it a device driver. The N/A below is the fact the kernel does not have this card in its list. That is why you get a black screen when you do not run nomodeset.

Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Trinity 2 [Radeon HD 7480D] vendor: Micro-Star MSI driver: N/A bus ID: 00:01.0

This is not a new card, so it is not as if you would need a newer kernel for it to be on the list. I went to the AMD Support site to see what they had listed. I could not find the Radeon HD 7480D card in their drop-down lists. I think that mean there are only Windows drivers available for this card.

Nomodeset is a way to bypass graphics driver problems and is usually done so an updated graphics display driver can be installed. However, in your case, there is no graphics device driver. The radeon display driver is there because the kernel recognizes you have a Radeon card, but the driver is unloaded because you ran nomodeset. That is the reason for the ERROR message.

Display:
x11 server: X.Org 1.20.8 driver: ati,fbdev unloaded: modesetting,radeon,vesa resolution: 1280x1024~77Hz
OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8 direct render: Yes

[drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!

I am not aware of a way to force the kernel to load a graphics device driver. It is my understanding it is either in the list or it is not. There are ways to force a display driver to load, but I do not know if one could force the display driver to load and have it work properly if the device driver is not loaded.

Perhaps others may know a way to work around this issue.
LM20.0 Cinnamon
TiBike
Level 2
Level 2
Posts: 88
Joined: Sun May 04, 2014 12:29 pm

Re: Another AMD Dual Boot Problem

Post by TiBike »

Thanks for digging into this SMG. So do I understand right that the problem is:

Graphics device driver: There isn't a Linux Mint graphics device driver for the Radeon HD 7480D, or at least not in the kernel list (only a Windows 10 driver this card).

Graphics display driver: This is all present and correct for Mint, but just isn't loaded with nomodeset.

So, yeh, if anyone knows of a workaround to load a graphics device driver that's not in the kernel list (if it even exists anywhere?), that would be awesome. Or if there are any other workarounds that might deal with a missing graphics device driver? Thanks!
TiBike
Level 2
Level 2
Posts: 88
Joined: Sun May 04, 2014 12:29 pm

Re: Another AMD Dual Boot Problem

Post by TiBike »

This kind-of feels like a dumb question (well, it's a newbies forum!), but since it seems to be no nice workaround for my missing Radeon device driver, what would be the consequence of always booting with nomodeset? As far as I can see, everything works OK with editing to nomodeset in Grub. I think I can edit /etc/default/grub to go in that way by default? But is there some bad downside to that?

Alternatively, are Cinnamon or Mate worth trying? Could they be any different?

Thanks.
User avatar
SMG
Level 5
Level 5
Posts: 714
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Another AMD Dual Boot Problem

Post by SMG »

TiBike wrote:
Wed Sep 16, 2020 1:34 pm
This kind-of feels like a dumb question (well, it's a newbies forum!), but since it seems to be no nice workaround for my missing Radeon device driver, what would be the consequence of always booting with nomodeset? As far as I can see, everything works OK with editing to nomodeset in Grub. I think I can edit /etc/default/grub to go in that way by default? But is there some bad downside to that?
It would probably depend on what software you use as to whether the display would have problems.

I did find a Dell support article which has a permanent nomodeset option listed Manual "nomodeset" Kernel Boot Line Option for Linux Booting.
TiBike wrote:
Wed Sep 16, 2020 1:34 pm
Alternatively, are Cinnamon or Mate worth trying? Could they be any different?
They are different desktop environments which still use the same Mint kernel, so the lack of device driver would still be the same.

I do not know if other versions of linux might work with your computer. You could try doing a search to see what versions of linux others have installed on the computer model you have to see what might work.
LM20.0 Cinnamon
TiBike
Level 2
Level 2
Posts: 88
Joined: Sun May 04, 2014 12:29 pm

Re: Another AMD Dual Boot Problem

Post by TiBike »

SMG wrote:
Wed Sep 16, 2020 2:06 pm
It would probably depend on what software you use as to whether the display would have problems.
Any chance of a rough guide on the sort of things that would / wouldn't work? Cheers.
Main uses are browsing, emails, YouTube, LibreOffice, photos, ripping & editing music files.
SMG wrote:
Wed Sep 16, 2020 2:06 pm
I did find a Dell support article which has a permanent nomodeset option listed Manual "nomodeset" Kernel Boot Line Option for Linux Booting.
Thanks. Curious that they add 'nomodeset' to 'quiet splash' rather than replace 'quiet splash'. Guess it doesn't matter?
User avatar
SMG
Level 5
Level 5
Posts: 714
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Another AMD Dual Boot Problem

Post by SMG »

I really do not know enough to make a guess as to what might or might not work properly. I think it would depend both on your hardware and what code is being used by the programs which means there are many variables.

I've not really played much with grub to know all the nuances, perhaps someone else can provide some feedback.
LM20.0 Cinnamon
pbear
Level 14
Level 14
Posts: 5367
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Another AMD Dual Boot Problem

Post by pbear »

TiBike wrote:
Wed Sep 16, 2020 3:14 pm
Thanks. Curious that they add 'nomodeset' to 'quiet splash' rather than replace 'quiet splash'. Guess it doesn't matter?
Correct, either way works. (Which means, you can replace rather than append, if you like.) My assumption always has been that Mint replaces on the assumption you'll want to see whether there are any error messages. There's no connection between the two parameters otherwise. By the way, with or without quiet splash makes no difference to boot time. It's just a matter of what's displayed on screen while the elves are setting up the shop.
motoryzen
Level 3
Level 3
Posts: 107
Joined: Sun Dec 08, 2019 12:25 am

Re: Another AMD Dual Boot Problem

Post by motoryzen »

TiBike wrote:
Wed Sep 16, 2020 1:34 pm
Alternatively, are Cinnamon or Mate worth trying? Could they be any different?
They are different desktop environments which still use the same Mint kernel, so the lack of device driver would still be the same.

-- Well I recommend trying Mate on a different storage drive as to not mess up your Cinnamon install. Now everyone's mileage may vary a little, but my experience with mate ( be it Ubuntu OR Mint) has not been good. Primary reasoning = UNstable. No matter what I did..or if I did absolutely nothing except occasionally move the mouse, or left click or right click any item on the panel or desktop or in the File manager..it would just lock up for no reason

Btw this is on the EXACT same hardware I've ran Mint xfce and Cinnamon on for many years on old off and on as I tried Mint since version 12 days. Hopefully, whatever was causing this problem has been resolved. I legit loved how easy it was to add anything I wanted to the Mate panel, no bs, just find it , left click and drag. No special right click, Add, paste a nemo /path/to/folder stuff ( which isn't a big deal but Mate is SOOOO much easier to do the same thing just left click and dragging the items).

Perhaps if you try it you wouldn't mind letting me know how it went? Cheers --
pbear
Level 14
Level 14
Posts: 5367
Joined: Wed Jun 21, 2017 12:25 pm
Location: San Francisco

Re: Another AMD Dual Boot Problem

Post by pbear »

motoryzen wrote:
Wed Sep 16, 2020 10:44 pm
Now everyone's mileage may vary a little, but my experience with mate ( be it Ubuntu OR Mint) has not been good. Primary reasoning = UNstable. No matter what I did..or if I did absolutely nothing except occasionally move the mouse, or left click or right click any item on the panel or desktop or in the File manager..it would just lock up for no reason
You're the only person I've seen report this problem. Lots of folks use Mate (though Cinnamon is more popular), so something about your machine.
TiBike
Level 2
Level 2
Posts: 88
Joined: Sun May 04, 2014 12:29 pm

Re: Another AMD Dual Boot Problem

Post by TiBike »

OK, so I think I have 2 options: A permanent edit to /etc/default/grub or try another Linux distro. I guess on the 2nd, I'm looking for something not based on ubuntu to maybe get the device driver I need?

On the permanent edit to /etc/default/grub, this kind-of feels dodgy to me, so I just wanna be careful. Does nomodeset pick up some other more generic software to drive the graphics that doesn't quite fit the hardware? Obviously I can test everything more thoroughly over a week or two's normal use, but I'm just wondering whether there's potential for this fix to interact badly with future updates. If I'm happy after 2 weeks, am I likely happy for years to come, or is this risky? Actually, I see you (SMG) say "I think it would depend both on your hardware and what code is being used by the programs"; since the code can change, maybe that answers my question.
Post Reply

Return to “Newbie Questions”