LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Setting Up My ASUS ROG Strix X570-E / AMD Ryzen 9 5950X - Can't UEFI Boot (https://www.linuxquestions.org/questions/slackware-14/setting-up-my-asus-rog-strix-x570-e-amd-ryzen-9-5950x-cant-uefi-boot-4175716405/)

Valdin 09-04-2022 06:29 PM

Setting Up My ASUS ROG Strix X570-E / AMD Ryzen 9 5950X - Can't UEFI Boot
 
The fantastic help I got from the forum picking out the parts for my Slackware development workstation:

https://www.linuxquestions.org/quest...rt-4175715828/

Have all the parts except the NVMe drive which is due to arrive in a couple of days.

The case is very nice and very configurable. Did not know this when I picked it out. Took some time to understand how to move parts around for my specific needs. One over tightened screw ended up taking an hour or so to loosen was the only problem.

The core system is setup - CPU/cooler, memory, GPU, mouse and keyboard. The sensors show the CPU is 39C.

I have setup a Current USB drive and successfully booted to a Slackware Live system. Tried installing the Current live to a spare 6TB drive. Did not know/remember about the 2TB limit. Learned how to format a single 6TB system partition and installed Current to it.

Can not get the machine to boot off the 6TB Slackware drive. The USB drive boots without problem. The 6TB shows up in the UEFI BIOS.

I will wait until the 2TB NVMe drive arrives to permanently setup my storage, but it would be good to figure out why the UEFI BIOS is not booting the newly install Current drive.

The last time I setup a completely new Slackware drive was when UEFI was still something new and not used by most systems. Reading up on how to properly setup a UEFI Linux boot disk but any help would be appreciated.

Valdin 09-04-2022 06:32 PM

One additional problem I had was in the live Current USB system was both KDE and Xfce having problems rearranging the layout of my three monitors. Some times it worked and sometimes I would just get a greyed out confirmation dialog that I could not click on and had to wait for the safety timeout.

LuckyCyborg 09-04-2022 06:37 PM

With all respect, Current does NOT mean Latest Slackware, BUT the Development Tree of Slackware, and it's published for those who want to debug Slackware, hence for beta-testers. It randomly may or many not work, and when it is broke, is expected the user to be capable to fix it.

The Latest Slackware is obviously Slackware 15.0.

Valdin 09-04-2022 06:52 PM

Are you saying that Current has changed the way Slackware is booted by UEFI BIOS from what is in the latest stable releases?

LuckyCyborg 09-04-2022 07:04 PM

Quote:

Originally Posted by Valdin (Post 6378136)
Are you saying that Current has changed the way Slackware is booted by UEFI BIOS from what is in the latest stable releases?

I'm saying that Current is not for rookies, BUT for the experienced Slackers who knows to handle the eventual issues.

And BTW, "development machine" usually means "stable computer" and depending on what is developed, even a Core 2 Duo with 4GB memories is more than enough.

I know several people who are PHP developers, who write custom sites and their machines are like this, even they run a complete LAMP stack in background and open hundred of files in their editors.

So, congratulations for wasting a truck-load of money! Now let's see what you will develop. :hattip:

Valdin 09-04-2022 07:10 PM

Quote:

Originally Posted by LuckyCyborg (Post 6378138)
I'm saying that Current is not for rookies, BUT for the experienced Slackers who knows to handle the eventual issues.

And BTW, "development machine" usually means "stable computer" and depending on what is developed, even a Core 2 Duo with 4GB memories is more than enough.

I know several people who are PHP developers, who write custom sites and their machines are like this, even they run a complete LAMP stack in background and open hundred of files in their editors.

So, congratulations for wasting a truck-load of money! Now let's see what you develop. :hattip:

This type of juvenile response has no place on this forum. Please stop participating in this thread.

Daedra 09-04-2022 09:10 PM

Glad to hear you got your system up and going. You can run -current if you want to, there is nothing wrong with that. However it is a moving target and might be better to stick with 15.0 if you just need a rock solid system. First thing, how did you set up your partitons. On a UEFI system you need to use GTP. Also did you create a EFI partition?

Valdin 09-04-2022 09:40 PM

Quote:

Originally Posted by Daedra (Post 6378148)
Glad to hear you got your system up and going. You can run -current if you want to, there is nothing wrong with that. However it is a moving target and might be better to stick with 15.0 if you just need a rock solid system. First thing, how did you set up your partitons. On a UEFI system you need to use GTP. Also did you create a EFI partition?

I will be setting up my permanent drive layout once my NVMe drive arrives.

Wanted to see if the updated drivers were now available as you linked to in my previous thread:
https://www.phoronix.com/news/Linux-...WMI-EC-Sensors

I may have missed or incorrectly setup my EFI partition. When I used the live installer it only created a 2TB out of the 6TB. So I setup the partitions manually with gparted. I will do it again.

Did a few quick test builds of one of my large C++ projects. Incredibly fast compared to my old system with only four or so threads.

The live system handled the RTX 3090 Ti and the three 2560x1400 screens without a problem. Haven't run any tests other than gears yet.

Daedra 09-04-2022 10:10 PM

I did forget to ask, but Slackware is the only OS on the system? If you were dual booting Windows 10 then you would already have a EFI partition. If not then you would need to create one.

Valdin 09-04-2022 10:41 PM

Quote:

Originally Posted by Daedra (Post 6378158)
I did forget to ask, but Slackware is the only OS on the system? If you were dual booting Windows 10 then you would already have a EFI partition. If not then you would need to create one.

Just Slackware.

Daedra 09-04-2022 10:56 PM

In that case a pure UEFI system needs an EFI partition. If the 6TB drive is just for testing, then you can make a partition scheme like this...
Code:

250M EFI system partition
5G of swap
and the rest as an ext4 partiton.

You can do this with cfdisk before you start the installer. Or you can use something like gparted-live to make your partitions with a GUI. When you make the 250 EFI partition make sure you flag it as an EFI partition so the Slackware installer will pick it up.

USUARIONUEVO 09-04-2022 11:42 PM

development enviroment + -current

Perfect choice for rookies ... /ironic off here.


You talk arround live system , ... latest problems we see on -current are exactly with EFI/UEFI and some early kernels from 5.19 branch.

You read the forum ?
Dte of your iso?
Kernel ?
grub or elilo ?

You can continue say juvenile responses ,but , the reality is you are juvenile slackware user and offended when some say some evident things when you go with -current

And after this , other user to my ignore list , congrats. :=)

For stable enviroments , use stable isos , easy and juvenile thing all know except you , the ancient slackware user.

Valdin 09-05-2022 01:51 AM

Quote:

Originally Posted by Daedra (Post 6378162)
In that case a pure UEFI system needs an EFI partition. If the 6TB drive is just for testing, then you can make a partition scheme like this...
Code:

250M EFI system partition
5G of swap
and the rest as an ext4 partiton.

You can do this with cfdisk before you start the installer. Or you can use something like gparted-live to make your partitions with a GUI. When you make the 250 EFI partition make sure you flag it as an EFI partition so the Slackware installer will pick it up.

Redid the partition with cfdisk instead of gparted and everything worked perfectly.

The system is installed to the 6TB disc and running perfectly. Still have some cable management and other minor tasks to finish with the case, but have been back to work for the past hour right where my old Slackware system died.

Thank you once again, Daedra.

Regnad Kcin 09-11-2022 05:37 PM

Incidentally, -current is the most up-to-date version of Slackware and it is quite stable and seldom causes trouble.
I generally will follow the comments in Linux Questions and look at what is changing.
For me, Slackware is --current and has been for several years and across a few version updates already


All times are GMT -5. The time now is 07:35 AM.