The gparted site says that gparted is usable on x86 systems.
My system -- with *no* OS on it yet -- will be AMD64 based.
If gparted won't work in this environment, what other pre-OS-
install program will?
Thanks in advance! - PMA
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Partitioning a new AMD system via gparted
-
- Posts: 210
- Joined: 2021-08-13 19:55
- Location: Minnesota
- Has thanked: 7 times
- Been thanked: 41 times
Re: Partitioning a new AMD system via gparted
By x86 and x86-64, they are referring to the processor instruction set type of your CPU, either 32 bit or 64 bit respectively, which are used by both Intel and AMD, not the type of OS that you want to install.
FYI, the Debian installer already has a built in partitioner that you can use, so you don't need GParted at all.
FYI, the Debian installer already has a built in partitioner that you can use, so you don't need GParted at all.
Last edited by dlu2021 on 2022-10-05 03:26, edited 1 time in total.
Re: Partitioning a new AMD system via gparted
fdisk, gdisk, parted ... all CLI, cfdisk ... curses, but for GUI there's gnome disks.If gparted won't work in this environment, what other pre-OS-
install program will?
- stevepusser
- Posts: 12930
- Joined: 2009-10-06 05:53
- Has thanked: 41 times
- Been thanked: 72 times
Re: Partitioning a new AMD system via gparted
To be pedantic, the "x86-64" architecture used by modern Intel/AMD/maybe others? CPUs was developed by AMD, not Intel. Intel was pushing their own 64-bit architecture which never caught on, and eventually adopted AMD's. So it was probably called amd64 by Debian from the start, and the name has stuck.
MX Linux packager and developer
-
- Posts: 13
- Joined: 2023-11-05 16:03
- Has thanked: 1 time
- Been thanked: 1 time
Re: Partitioning a new AMD system via gparted
As I understand it apparently the Linux kernel developers have baked AMD processor and PU drivers into the kernel so that we as the users don't have to worry about killing ourselves looking for and debugging issues with faulty proprietary drivers. Further, I'd recommend that the original poster try a program like darks Boot and Nuke(DBAN).