Close

Register Now!

To Get More Info and Daily Reward.

Please login or register.
Advanced search    

News:

Pages: [1]   Go Down

Author Topic: B350M Gaming Pro Bios 7A39v2J not working for me  (Read 296 times)

0 Members and 1 Guest are viewing this topic.

ejbiowTopic starter

  • PRIVATE E-2
  • **
  • Offline Offline
  • Posts: 5
B350M Gaming Pro Bios 7A39v2J not working for me
« on: 17-December-18, 00:29:25 »

I flashed this BIOS and found I could not get Ubuntu 18.04 to even show me the prompt for my decryption key, my monitor claimed it wasn't attached to a source. If I started Ubuntu in emergency mode I could decrypt my drive, but if I told the operating system to boot normally only one of my 3 monitors were recognized, and I couldn't get it past 1024x768. I believe it uses a 4.15 kernel, and had always booted reliably before..

Debian Testing would boot SOMETIMES with the standard repository kernel (4.18.0-3-amd64) and a bit more reliably with a more modern 4.19.0-9.1-liquorix-amd64 kernel.

I was forced to back off to Version: 2.H0 of the kernel to get Ubuntu to behave properly. That had been what I was using before, I didn't try the 'I' kernel version.

AMD Ryzen 3 2200G with Radeon Vega Graphics

Graphics:
 Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega
 Mobile Series]
 driver: amdgpu v: kernel
 Display: server: X.Org 1.20.3 driver: amdgpu,ati
 unloaded: fbdev,modesetting,vesa
 resolution: 2560x1440~60Hz, 1920x1080~60Hz, 1920x1200~60Hz
 OpenGL: renderer: AMD RAVEN (DRM 3.27.0
 4.19.0-9.1-liquorix-amd64 LLVM 7.0.1)
 v: 4.5 Mesa 18.2.6

1x8GB DDR4
G.SKill F4-3000C16-8GISB
 Speed: 2133 MT/s

I realize that Linux desktop users are just a rounding error of the market and hardware makers don't really care much about them, but I figured I'd report it on the forum and you could at least include a warning for Linux users in the release notes. The note specifically claimed that the V2.J BIOS "Improve compatibility with Raven CPU", which is what I have, and I'm afraid it did not.
p, li { white-space: pre-wrap; }
p, li { white-space: pre-wrap; }
p, li { white-space: pre-wrap; }
Logged

plutomate

  • MAJOR GENERAL
  • ***
  • Offline Offline
  • Posts: 3010
Re: B350M Gaming Pro Bios 7A39v2J not working for me
« Reply #1 on: 19-December-18, 05:14:24 »

usually ppl say there's no point to upgrade BIOS if there's no problem, if 2.H works for you then it's better to just stick with it imo. 
but i do know MSI still tries to add patch for linux from time to time, maybe you can write them a ticket?
Logged

ejbiowTopic starter

  • PRIVATE E-2
  • **
  • Offline Offline
  • Posts: 5
Re: B350M Gaming Pro Bios 7A39v2J not working for me
« Reply #2 on: 23-December-18, 20:26:27 »

I agree, and I wouldn't have updated (or even looked for an update) if I hadn't had an issue.

Ubuntu (18.04) didn't have an problem (except of a single freeze), but Debian Testing would not boot with the repository kernel in any reliable way, maybe one time in 5 I'd get to the GUI with 4.18.0-3-amd64 (and once there Debian was fine). So I installed the Liquorix kernel (4.19) and it seems stable, but I was hoping a BIOS update would enable me to boot with the regular kernel. Liquorix updates too often, requiring more bandwidth and requiring me frequently remove older kernels so I don't fill up my /boot partition and can start my encrypted system. I wouldn't have looked at the liquorix kernel if I didn't have problems booting Debian testing on my 3 Raven Ridge systems, 2400G, 2200G & 200GE, two with the B350M Gaming Pro. So all 3 Raven Ridge systems are using the liquorix kernel, at least until Debian starts using the 4.19 kernel.

Also, I was looking to run my 3000 speed DDR4 at something close to its rated speed, so I figured a recent kernel would be better.
Logged

ejbiowTopic starter

  • PRIVATE E-2
  • **
  • Offline Offline
  • Posts: 5
Re: B350M Gaming Pro Bios 7A39v2J not working for me
« Reply #3 on: 15-January-19, 22:38:13 »

7A39v2K from January 2019 is working with both Debian Testing and Ubuntu Bionic. I can run my supposedly 3000 Mhz RAM (G.SKill F4-3000C16-8GISB) at 2933 MHz (XMP Profile 2) in Debian Testing, but only at 2133 in Ubuntu Bionic 18.04. I haven't tried messing with any other settings like voltage.  I guess I'll run at 2133 until the next BIOS comes out, or maybe I should try a 4.19 kernel in Ubuntu Bionic. Yes, I know, I'm talking to myself, what self-respecting computer user would use Linux? 

FWIW, Debian testing is working fine with the current 4.19 mainline kernel introduced some time in the last few weeks to supersede 4.18, so I can uninstall Liquorix.
Logged
Pages: [1]   Go Up