Unexpected Shutdowns

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
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Unexpected Shutdowns

Post by omg_me »

Hi :)
My Linux Mint shuts down "randomly" (or at least without clear pattern so far). The screen simply turns black and after some time I get the Cryptsetup unlock screen.

What I've tried so far, without luck/errors:
  • Reinstall Linux Mint
  • Run Memtest86+
The last shutdown I observed was at Aug 27, 14:44. var/log/syslog around that time contains the following

Code: Select all

Aug 27 14:40:16 gam0r-PC kernel: [ 3162.382722] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:40:25 gam0r-PC kernel: [ 3171.047680] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:40:25 gam0r-PC kernel: [ 3171.047685] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:40:25 gam0r-PC kernel: [ 3171.047687] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:40:25 gam0r-PC kernel: [ 3171.047689] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:40:34 gam0r-PC kernel: [ 3180.389627] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:40:34 gam0r-PC kernel: [ 3180.389639] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:40:34 gam0r-PC kernel: [ 3180.389648] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:40:34 gam0r-PC kernel: [ 3180.389653] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:40:40 gam0r-PC kernel: [ 3186.387994] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:40:40 gam0r-PC kernel: [ 3186.388006] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:40:40 gam0r-PC kernel: [ 3186.388015] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:40:40 gam0r-PC kernel: [ 3186.388020] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:40:46 gam0r-PC kernel: [ 3192.387411] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:40:46 gam0r-PC kernel: [ 3192.387425] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:40:46 gam0r-PC kernel: [ 3192.387435] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:40:46 gam0r-PC kernel: [ 3192.387441] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:10 gam0r-PC kernel: [ 3216.388598] pcieport 0000:00:1c.4: AER: Multiple Corrected error received: 0000:00:1c.4
Aug 27 14:41:10 gam0r-PC kernel: [ 3216.388627] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Aug 27 14:41:10 gam0r-PC kernel: [ 3216.388635] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00001001/00002000
Aug 27 14:41:10 gam0r-PC kernel: [ 3216.388640] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:10 gam0r-PC kernel: [ 3216.388645] pcieport 0000:00:1c.4: AER:    [12] Timeout               
Aug 27 14:41:14 gam0r-PC kernel: [ 3219.742137] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:14 gam0r-PC kernel: [ 3219.742149] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:14 gam0r-PC kernel: [ 3219.742158] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:14 gam0r-PC kernel: [ 3219.742164] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:16 gam0r-PC kernel: [ 3222.383988] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:16 gam0r-PC kernel: [ 3222.384002] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:16 gam0r-PC kernel: [ 3222.384012] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:16 gam0r-PC kernel: [ 3222.384018] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:16 gam0r-PC kernel: [ 3222.385056] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:16 gam0r-PC kernel: [ 3222.385069] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:16 gam0r-PC kernel: [ 3222.385079] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:16 gam0r-PC kernel: [ 3222.385085] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.087775] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.087788] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.087798] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.087804] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.381832] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.381843] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.381852] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.381857] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.382855] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.382866] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.382875] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:22 gam0r-PC kernel: [ 3228.382880] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:25 gam0r-PC kernel: [ 3231.175915] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:25 gam0r-PC kernel: [ 3231.175920] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:25 gam0r-PC kernel: [ 3231.175922] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:25 gam0r-PC kernel: [ 3231.175924] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:28 gam0r-PC kernel: [ 3234.388167] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:28 gam0r-PC kernel: [ 3234.388181] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:28 gam0r-PC kernel: [ 3234.388192] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:28 gam0r-PC kernel: [ 3234.388198] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:34 gam0r-PC kernel: [ 3240.387965] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:34 gam0r-PC kernel: [ 3240.387977] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:34 gam0r-PC kernel: [ 3240.387985] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:34 gam0r-PC kernel: [ 3240.387991] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:34 gam0r-PC kernel: [ 3240.388785] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:34 gam0r-PC kernel: [ 3240.388796] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:34 gam0r-PC kernel: [ 3240.388804] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:34 gam0r-PC kernel: [ 3240.388809] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:40 gam0r-PC kernel: [ 3246.388335] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:40 gam0r-PC kernel: [ 3246.388346] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:40 gam0r-PC kernel: [ 3246.388355] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:40 gam0r-PC kernel: [ 3246.388361] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:43 gam0r-PC kernel: [ 3249.686283] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:43 gam0r-PC kernel: [ 3249.686296] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:43 gam0r-PC kernel: [ 3249.686307] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:43 gam0r-PC kernel: [ 3249.686313] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:41:52 gam0r-PC kernel: [ 3258.387865] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:41:52 gam0r-PC kernel: [ 3258.387877] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:41:52 gam0r-PC kernel: [ 3258.387886] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:41:52 gam0r-PC kernel: [ 3258.387891] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:42:22 gam0r-PC kernel: [ 3288.387488] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:42:22 gam0r-PC kernel: [ 3288.387500] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:42:22 gam0r-PC kernel: [ 3288.387509] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:42:22 gam0r-PC kernel: [ 3288.387514] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:42:47 gam0r-PC kernel: [ 3313.102220] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:42:47 gam0r-PC kernel: [ 3313.102232] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:42:47 gam0r-PC kernel: [ 3313.102241] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:42:47 gam0r-PC kernel: [ 3313.102246] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:42:53 gam0r-PC kernel: [ 3319.085266] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:42:53 gam0r-PC kernel: [ 3319.085280] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:42:53 gam0r-PC kernel: [ 3319.085290] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:42:53 gam0r-PC kernel: [ 3319.085296] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:42:54 gam0r-PC kernel: [ 3320.109968] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:42:54 gam0r-PC kernel: [ 3320.109982] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:42:54 gam0r-PC kernel: [ 3320.109993] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:42:54 gam0r-PC kernel: [ 3320.110000] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:42:57 gam0r-PC kernel: [ 3323.661970] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:42:57 gam0r-PC kernel: [ 3323.661984] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:42:57 gam0r-PC kernel: [ 3323.661995] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:42:57 gam0r-PC kernel: [ 3323.662002] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:04 gam0r-PC kernel: [ 3330.383816] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:04 gam0r-PC kernel: [ 3330.383828] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:04 gam0r-PC kernel: [ 3330.383837] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:04 gam0r-PC kernel: [ 3330.383843] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:22 gam0r-PC kernel: [ 3348.388938] pcieport 0000:00:1c.4: AER: Multiple Corrected error received: 0000:00:1c.4
Aug 27 14:43:22 gam0r-PC kernel: [ 3348.388966] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:22 gam0r-PC kernel: [ 3348.388976] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:22 gam0r-PC kernel: [ 3348.388982] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:34 gam0r-PC kernel: [ 3360.387010] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:34 gam0r-PC kernel: [ 3360.387021] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:34 gam0r-PC kernel: [ 3360.387030] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:34 gam0r-PC kernel: [ 3360.387035] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:35 gam0r-PC kernel: [ 3361.180211] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:35 gam0r-PC kernel: [ 3361.180216] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:35 gam0r-PC kernel: [ 3361.180219] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:35 gam0r-PC kernel: [ 3361.180220] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:40 gam0r-PC kernel: [ 3366.386103] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:40 gam0r-PC kernel: [ 3366.386115] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:40 gam0r-PC kernel: [ 3366.386123] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:40 gam0r-PC kernel: [ 3366.386129] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:40 gam0r-PC kernel: [ 3366.387495] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:40 gam0r-PC kernel: [ 3366.387508] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:40 gam0r-PC kernel: [ 3366.387518] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00002001/00002000
Aug 27 14:43:40 gam0r-PC kernel: [ 3366.387524] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:44 gam0r-PC kernel: [ 3369.718046] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:44 gam0r-PC kernel: [ 3369.718059] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:44 gam0r-PC kernel: [ 3369.718069] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:44 gam0r-PC kernel: [ 3369.718076] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:46 gam0r-PC kernel: [ 3372.388484] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:46 gam0r-PC kernel: [ 3372.388496] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:46 gam0r-PC kernel: [ 3372.388505] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:46 gam0r-PC kernel: [ 3372.388510] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:52 gam0r-PC kernel: [ 3378.385518] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:52 gam0r-PC kernel: [ 3378.385529] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:52 gam0r-PC kernel: [ 3378.385538] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:52 gam0r-PC kernel: [ 3378.385544] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:52 gam0r-PC kernel: [ 3378.386504] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:52 gam0r-PC kernel: [ 3378.386515] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:52 gam0r-PC kernel: [ 3378.386523] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:52 gam0r-PC kernel: [ 3378.386529] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:58 gam0r-PC kernel: [ 3384.387332] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:58 gam0r-PC kernel: [ 3384.387343] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:58 gam0r-PC kernel: [ 3384.387352] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:58 gam0r-PC kernel: [ 3384.387357] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:43:58 gam0r-PC kernel: [ 3384.388627] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:43:58 gam0r-PC kernel: [ 3384.388638] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:43:58 gam0r-PC kernel: [ 3384.388647] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:43:58 gam0r-PC kernel: [ 3384.388652] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:44:01 gam0r-PC kernel: [ 3386.830008] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:44:01 gam0r-PC kernel: [ 3386.830019] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:44:01 gam0r-PC kernel: [ 3386.830028] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:44:01 gam0r-PC kernel: [ 3386.830034] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:44:04 gam0r-PC kernel: [ 3390.388646] pcieport 0000:00:1c.4: AER: Multiple Corrected error received: 0000:00:1c.4
Aug 27 14:44:04 gam0r-PC kernel: [ 3390.388674] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Transmitter ID)
Aug 27 14:44:04 gam0r-PC kernel: [ 3390.388682] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=000010c1/00002000
Aug 27 14:44:04 gam0r-PC kernel: [ 3390.388688] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:44:04 gam0r-PC kernel: [ 3390.388692] pcieport 0000:00:1c.4: AER:    [ 6] BadTLP                
Aug 27 14:44:04 gam0r-PC kernel: [ 3390.388696] pcieport 0000:00:1c.4: AER:    [ 7] BadDLLP               
Aug 27 14:44:04 gam0r-PC kernel: [ 3390.388700] pcieport 0000:00:1c.4: AER:    [12] Timeout               
Aug 27 14:44:10 gam0r-PC kernel: [ 3396.330926] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:44:10 gam0r-PC kernel: [ 3396.330941] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:44:10 gam0r-PC kernel: [ 3396.330954] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:44:10 gam0r-PC kernel: [ 3396.330961] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:44:22 gam0r-PC kernel: [ 3408.382043] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:44:22 gam0r-PC kernel: [ 3408.382054] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:44:22 gam0r-PC kernel: [ 3408.382063] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:44:22 gam0r-PC kernel: [ 3408.382069] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:44:22 gam0r-PC kernel: [ 3408.383043] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:44:22 gam0r-PC kernel: [ 3408.383055] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:44:22 gam0r-PC kernel: [ 3408.383064] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:44:22 gam0r-PC kernel: [ 3408.383069] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:44:28 gam0r-PC kernel: [ 3414.188630] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:44:28 gam0r-PC kernel: [ 3414.188643] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:44:28 gam0r-PC kernel: [ 3414.188654] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:44:28 gam0r-PC kernel: [ 3414.188660] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:44:46 gam0r-PC kernel: [ 3431.886029] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:44:46 gam0r-PC kernel: [ 3431.886043] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:44:46 gam0r-PC kernel: [ 3431.886053] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:44:46 gam0r-PC kernel: [ 3431.886059] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:44:52 gam0r-PC kernel: [ 3438.387047] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:44:52 gam0r-PC kernel: [ 3438.387059] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:44:52 gam0r-PC kernel: [ 3438.387067] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:44:52 gam0r-PC kernel: [ 3438.387073] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:44:58 gam0r-PC kernel: [ 3444.387071] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
Aug 27 14:44:58 gam0r-PC kernel: [ 3444.387083] pcieport 0000:00:1c.4: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Aug 27 14:44:58 gam0r-PC kernel: [ 3444.387092] pcieport 0000:00:1c.4: AER:   device [8086:9d14] error status/mask=00000001/00002000
Aug 27 14:44:58 gam0r-PC kernel: [ 3444.387097] pcieport 0000:00:1c.4: AER:    [ 0] RxErr                 
Aug 27 14:54:10 gam0r-PC systemd-modules-load[602]: Inserted module 'lp'
Aug 27 14:54:10 gam0r-PC systemd-modules-load[602]: Inserted module 'ppdev'
...
last -x shows

Code: Select all

grubi    tty7         :0               Thu Aug 27 14:54    gone - no logout
runlevel (to lvl 5)   5.4.0-42-generic Thu Aug 27 14:54   still running
reboot   system boot  5.4.0-42-generic Thu Aug 27 14:54   still running
grubi    tty7         :0               Thu Aug 27 13:47 - crash  (01:06)
runlevel (to lvl 5)   5.4.0-42-generic Thu Aug 27 13:47 - 14:54  (01:06)
reboot   system boot  5.4.0-42-generic Thu Aug 27 13:47   still running
grubi    tty7         :0               Wed Aug 26 14:33 - crash  (23:14)
runlevel (to lvl 5)   5.4.0-26-generic Wed Aug 26 14:33 - 13:47  (23:14)
reboot   system boot  5.4.0-26-generic Wed Aug 26 14:33   still running
grubi    tty7         :0               Wed Aug 26 10:39 - crash  (03:53)
runlevel (to lvl 5)   5.4.0-26-generic Wed Aug 26 10:39 - 14:33  (03:53)
reboot   system boot  5.4.0-26-generic Wed Aug 26 10:39   still running
shutdown system down  5.4.0-26-generic Tue Aug 25 22:24 - 10:39  (12:15)
Further background information:

Code: Select all

inxi -Fxz
System:
  Kernel: 5.4.0-42-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.6.7 Distro: Linux Mint 20 Ulyana 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: LENOVO product: 81AX v: Lenovo V330-15IKB 
  serial: <filter> 
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40697 WIN serial: <filter> 
  UEFI: LENOVO v: 6SCN35WW date: 06/21/2018 
Battery:
  ID-1: BAT0 charge: 23.9 Wh condition: 27.4/30.6 Wh (89%) 
  model: CPT-COS L17C2PB3 status: Discharging 
CPU:
  Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP 
  arch: Kaby Lake rev: A L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 31999 
  Speed: 800 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel 
  bus ID: 00:02.0 
  Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.8 
  direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
  Sound Server: ALSA v: k5.4.0-42-generic 
Network:
  Device-1: Intel Dual Band Wireless-AC 3165 Plus Bluetooth driver: iwlwifi 
  v: kernel port: efa0 bus ID: 02:00.0 
  IF: wlp2s0 state: up mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Lenovo driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
  IF: enp3s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 476.94 GiB used: 164.05 GiB (34.4%) 
  ID-1: /dev/nvme0n1 vendor: Western Digital 
  model: PC SN520 SDAPMUW-512G-1101 size: 476.94 GiB 
Partition:
  ID-1: / size: 466.30 GiB used: 163.84 GiB (35.1%) fs: ext4 dev: /dev/dm-1 
  ID-2: /boot size: 704.5 MiB used: 204.4 MiB (29.0%) fs: ext4 
  dev: /dev/nvme0n1p2 
  ID-3: swap-1 size: 980.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2 
Sensors:
  System Temperatures: cpu: 40.0 C mobo: 36.0 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 253 Uptime: 29m Memory: 18.91 GiB used: 1.80 GiB (9.5%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38 
  
I'm not sure the reported corrected error is causing this problem or what the next steps to debug this would be.
Thank you for your help!
twerq
Level 2
Level 2
Posts: 68
Joined: Sun Jul 05, 2020 10:55 am

Re: Unexpected Shutdowns

Post by twerq »

Hi omg_me,

you should check CPU/GPU temperature statistics. Seems like your notebook overheating.
1000
Level 3
Level 3
Posts: 128
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

I found something like this
https://askubuntu.com/questions/771899/ ... -corrected

However it looks like the problem with what is connected to the cable ( hard drive , monitor, I don't know )
https://en.wikipedia.org/wiki/Periphera ... terconnect

" cpu: 40.0 C mobo: 36.0 C " looks OK, I don't see GPU temp.
asinoro
Level 6
Level 6
Posts: 1137
Joined: Mon Feb 12, 2018 11:43 am

Re: Unexpected Shutdowns

Post by asinoro »

There are many issues with this driver: i915 check these:
search.php?keywords=i915+solved
User avatar
SMG
Level 5
Level 5
Posts: 774
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

If I punched in the numbers correctly, there is a newer BIOS for your machine which became available on June 17, 2020. Here is the Readme for that BIOS update. It may help if you have a way to install it.
LM20.0 Cinnamon
antikythera
Level 6
Level 6
Posts: 1472
Joined: Thu Jul 02, 2020 12:52 pm
Contact:

Re: Unexpected Shutdowns

Post by antikythera »

Good call:
4. Update KBC 6SEC20WW.
4-1. DOA intermittent NO power issue: Lenovo request add W/A - Disable PSL mode for load code fail issue
Don't take life so seriously, nobody gets out alive anyway!
AMSTRAD CPC6128 - 128KB RAM, 3" Hitachi Floppy Diskette Drive, External Sony Cassette Recorder, Locomotive BASIC 1.1, CTM-644 Monitor
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

Sorry for my late response. And a huge thanks for all your inputs!
twerq wrote:
Fri Aug 28, 2020 2:33 pm
Hi omg_me,

you should check CPU/GPU temperature statistics. Seems like your notebook overheating.
Thanks. I started logging the temperatures to check if they were too high the next time it shuts down.
1000 wrote:
Fri Aug 28, 2020 3:02 pm
I found something like this
https://askubuntu.com/questions/771899/ ... -corrected

However it looks like the problem with what is connected to the cable ( hard drive , monitor, I don't know )
https://en.wikipedia.org/wiki/Periphera ... terconnect

" cpu: 40.0 C mobo: 36.0 C " looks OK, I don't see GPU temp.
The temperature was not logged at the point of the shutdown, so it might have been higher then. The logs will tell me more... I'll follow the guide and to see how it turns out, thank you!
asinoro wrote:
Mon Aug 31, 2020 1:45 am
There are many issues with this driver: i915 check these:
search.php?keywords=i915+solved
Thanks, I'll browse through those at some point.
SMG wrote:
Mon Aug 31, 2020 11:13 am
If I punched in the numbers correctly, there is a newer BIOS for your machine which became available on June 17, 2020. Here is the Readme for that BIOS update. It may help if you have a way to install it.
Oh, I see. I think I'll start with the BIOS update then. Highly appreciated.
antikythera wrote:
Mon Aug 31, 2020 11:27 am
Good call:
4. Update KBC 6SEC20WW.
4-1. DOA intermittent NO power issue: Lenovo request add W/A - Disable PSL mode for load code fail issue
Yeah, that indeed looks promising. Thank you!
twerq
Level 2
Level 2
Posts: 68
Joined: Sun Jul 05, 2020 10:55 am

Re: Unexpected Shutdowns

Post by twerq »

Yeah, man. Tell us how it's going.

Cheers.
antikythera
Level 6
Level 6
Posts: 1472
Joined: Thu Jul 02, 2020 12:52 pm
Contact:

Re: Unexpected Shutdowns

Post by antikythera »

1000 wrote:
Fri Aug 28, 2020 3:02 pm
I found something like this
https://askubuntu.com/questions/771899/ ... -corrected

However it looks like the problem with what is connected to the cable ( hard drive , monitor, I don't know )
https://en.wikipedia.org/wiki/Periphera ... terconnect

" cpu: 40.0 C mobo: 36.0 C " looks OK, I don't see GPU temp.
The GPU temp will be roughly the same as it's integrated into the CPU die.
Don't take life so seriously, nobody gets out alive anyway!
AMSTRAD CPC6128 - 128KB RAM, 3" Hitachi Floppy Diskette Drive, External Sony Cassette Recorder, Locomotive BASIC 1.1, CTM-644 Monitor
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

Just had a shutdown some minutes ago, the last log looks well temperature-wise, I guess:

Code: Select all

Sat 05 Sep 2020 09:40:01 AM CEST
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +40.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +39.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +39.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +38.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +40.0°C  (high = +100.0°C, crit = +100.0°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:           8.47 V  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +35.0°C  

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +36.5°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +39.0°C  (crit = +98.0°C)
temp2:        +37.0°C  (crit = +126.0°C)
The BIOS update turns out to be trickier than expected, as Lenovo only provides an .exe and I currently don't have dual-boot to run it on Windows... I wrote them to check if they have an ISO available, but don't expect them to.
I've seen some posts (e.g. https://help.ubuntu.com/community/BIOSUpdate), where they show different options. To me, the FreeDOS option seems the most practical so far.
If someone has experience in doing such an operation, all hints are welcome.
twerq
Level 2
Level 2
Posts: 68
Joined: Sun Jul 05, 2020 10:55 am

Re: Unexpected Shutdowns

Post by twerq »

You should go with FreeDOS, pretty simple and straightforward.
Boot load from usb-stick, which you can prepare in your linux environment. After boot load you'll find yourself at. the shell prompt. Then cd d: to change drive to "d:" (you should figure out your letter though). dir to list directory (like ls in bash). And name.exe enter to execute firmware procedure.
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

Ok cool, thanks.
I'll be away for the next seven/eight days, but after that I'll try to do that and will let you know, how it went.
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

twerq wrote:
Sat Sep 05, 2020 5:28 am
You should go with FreeDOS, pretty simple and straightforward.
Boot load from usb-stick, which you can prepare in your linux environment. After boot load you'll find yourself at. the shell prompt. Then cd d: to change drive to "d:" (you should figure out your letter though). dir to list directory (like ls in bash). And name.exe enter to execute firmware procedure.
I'm already stuck at the second step: I prepared a bootable USB drive (with "USB Image Writer" and UNetbootin) and adjusted the boot order in the BIOS. But the computer does not boot into the USB drive, but skips it and boots straight into Linux Mint again.

Any idea what might cause this and how to fix it?

I've tried with secureboot enabled and disabled and both in legacy as well as UEFI mode...

EDIT: I've created another bootable device with Windows, which is not booted either. So I thought I'd try again with the Linux Mint installer, as this was the last which I was able to boot. That one still works properly.
asinoro
Level 6
Level 6
Posts: 1137
Joined: Mon Feb 12, 2018 11:43 am

Re: Unexpected Shutdowns

Post by asinoro »

Use the whole usb and write it with the command:

Code: Select all

sudo  dd status=progress  bs=4096 if=/location of your iso/linuxmint.iso  of= /dev/sdx ; sync  
Where sdx the location of your usb.
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

Sorry, I was probably not clear - the Linux Mint bootable USB is the only thing I can boot into. FreeDOS (what I actually would lik to boot into) and Windows ISO/IMGs did not work.

Thanks for the hint to use the whole USB. I tried again with the command you suggested (modified for the FreeDOS img) - but again, no luck...
User avatar
SMG
Level 5
Level 5
Posts: 774
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

omg_me wrote:
Sat Sep 12, 2020 6:44 am
Sorry, I was probably not clear - the Linux Mint bootable USB is the only thing I can boot into. FreeDOS (what I actually would lik to boot into) and Windows ISO/IMGs did not work.

Thanks for the hint to use the whole USB. I tried again with the command you suggested (modified for the FreeDOS img) - but again, no luck...
I do not know about FreeDOS, but in this thread [SOLVED] cannot boot from bootable stick I learned the program that comes with Mint does not work for creating a bootable Windows USB. One needs to use WoeUSB to create a Windows bootable USB.
LM20.0 Cinnamon
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

Nice catch. Indeed - after flashing the USB drive with WoeUSB (and NTFS File System), I was able to boot from the USB drive with Legacy Mode enabled - or at least it didn't boot directly into Linux Mint.

But I did not get much further - what I can see on the screen is:

Code: Select all

*** UEFI:NTFS (x64) ***

[INFO] UEFI v2.50 (Phoenix Technologies Ltd., 0x12345678)
[INFO] LENOVO 6SCN35WW
[INFO] LENOVO 81AX
...
some more logs
...
[INFO] This system uses 64-bit x86 UEFI => searching for x64 EFI bootloader
[FAIL] Could not locate 'efi\boot\bootx64.efi': [14] Not Found
When I look at the USB drive in Linux, i can see two partitions, one called UEFI_NTFS containing

Code: Select all

├── EFI
│   ├── Boot
│   │   ├── bootaa64.efi
│   │   ├── bootarm.efi
│   │   ├── bootia32.efi
│   │   └── bootx64.efi
│   └── Rufus
│       ├── exfat_aa64.efi
│       ├── exfat_arm.efi
│       ├── exfat_ia32.efi
│       ├── exfat_x64.efi
│       ├── ntfs_aa64.efi
│       ├── ntfs_arm.efi
│       ├── ntfs_ia32.efi
│       └── ntfs_x64.efi
└── readme.txt
and the other one

Code: Select all

.
├── ARCHIVER
├── BASE

├── BOOT
├── DEVEL
├── EDIT
├── GAMES
├── grub
│   ├── fonts
│   └── i386-pc
├── NET
├── PKGINFO
├── SOUND
└── UTIL
So, assuming it uses the correct partition, it should be able to find it...?

The solution here (https://superuser.com/questions/1096820 ... or-dual-bo) seemed to be creating a FAT32 bootable stick using Rufus, which is not an option for me...
1000
Level 3
Level 3
Posts: 128
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

I am also trying. Without success. :(
For now I tried download Freedos image FD12FULL.img file ( Full USB option on website )
and install with " restore partition " with gnome-disks app in Linux Mint
but after reboot I see only
_
I can only show what I'm reading
https://wiki.archlinux.org/index.php/Fl ... from_Linux
User avatar
SMG
Level 5
Level 5
Posts: 774
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

omg_me wrote:
Sat Sep 12, 2020 1:40 pm
The solution here (https://superuser.com/questions/1096820 ... or-dual-bo) seemed to be creating a FAT32 bootable stick using Rufus, which is not an option for me...
That person also turned off legacy mode. Did you try doing that and running the USB?
LM20.0 Cinnamon
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

Yes. But without legacy mode it directly boots into Linux Mint....
Post Reply

Return to “Newbie Questions”