I couldn't find the specific solution online as I tried multiple solutions from both forums and other sources
Code: Select all
System:
Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Xfce 4.14.2 tk: Gtk 3.24.13 info: xfce4-panel wm: xfwm4
dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal
Machine:
Type: Portable System: Alienware product: M17xR3 v: A08 serial: <filter>
Mobo: Alienware model: M17xR3 v: A08 serial: <filter> UEFI: Alienware
v: A08 date: 07/29/2011
Battery:
ID-1: BAT1 charge: 0 Wh condition: N/A volts: 5.8/11.1
model: Simplo DELL 5WP5W13R type: Li-ion serial: <filter> status: Unknown
CPU:
Topology: Quad Core model: Intel Core i7-2630QM bits: 64 type: MT MCP
arch: Sandy Bridge rev: 7 L2 cache: 6144 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31895
Speed: 797 MHz min/max: 800/2900 MHz Core speeds (MHz): 1: 797 2: 797
3: 797 4: 531 5: 546 6: 525 7: 547 8: 797
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0116
Device-2: AMD Granville [Radeon HD 6850M/6870M] vendor: Dell
driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:68a8
Display: x11 server: X.Org 1.20.8 driver: ati,modesetting,radeon
unloaded: fbdev,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2)
v: 3.3 Mesa 20.0.8 compat-v: 3.0 direct render: Yes
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: Dell Alienware M17x R3 driver: snd_hda_intel v: kernel
bus ID: 00:1b.0 chip ID: 8086:1c20
Device-2: AMD Juniper HDMI Audio [Radeon HD 5700 Series] vendor: Dell
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aa58
Sound Server: ALSA v: k5.4.0-58-generic
Network:
Device-1: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet vendor: Dell
driver: atl1c v: 1.0.1.1-NAPI port: 5000 bus ID: 07:00.0
chip ID: 1969:1083
IF: enp7s0 state: down mac: <filter>
Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel
port: 5000 bus ID: 0d:00.0 chip ID: 8086:422b
IF: wlp13s0 state: up mac: <filter>
Drives:
Local Storage: total: 111.80 GiB used: 16.66 GiB (14.9%)
ID-1: /dev/sda vendor: Western Digital model: WDS120G2G0A-00JH30
size: 111.80 GiB speed: 3.0 Gb/s serial: <filter> rev: 0000 scheme: GPT
Partition:
ID-1: / size: 109.05 GiB used: 16.65 GiB (15.3%) fs: ext4 dev: /dev/sda2
Sensors:
System Temperatures: cpu: 44.0 C mobo: N/A gpu: radeon temp: 29 C
Fan Speeds (RPM): N/A
Repos:
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http://packages.linuxmint.com ulyssa main upstream import backport #id:linuxmint_main
2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:
Processes: 230 Uptime: 35m Memory: 7.72 GiB used: 2.43 GiB (31.5%)
Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash
v: 5.0.17 running in: xfce4-terminal inxi: 3.0.38 Computer boots fine when restarting but if shutdown for a few hours, I got a kernel panic each time. For some reason it only happened if the computer was off for a few hours, it did not happen if it was booted within a few minutes of shutting down.
When a previous kernel is available in the grub menu then it can be used to boot successfully, but only once.
If computer is shutdown for a few hours then the problem returns and the last kernel used then no longer works either.
After trying a few things I eventually read that bios sometimes has trouble locating root on larger drives(my drive is pretty small but thought it might be the problem)
So I did a clean efi install instead of legacy and that seems to have eliminated the problem.
I believe it may be a problem with my bios in particular or it could be something completely different, but the solution has now held up for a few days with no further issues.
