Compiling kernel modules for a CPU...?

I used AMD GPUs with Linux for years and can't recall compiling anything.

ryzen_smu for RyzenAdj
ths is due to  the fact that amd pstate on my laptop is wrongly configured using very high frequences while idle.

And again, I've never heared that someting does not work on pure Intel under Linux.

I used AMD GPUs with Linux for years and can't recall compiling anything.

No problems of any kind then nor ever since. What on earth are you talking about? AMD v's intel is a non-starter here, so I'm marking this SOLVED.

I had never had "something does not work" on pure Intel. But I had to compile some kernel modules for amd and amd graphics.

As always, it is setup that takes the time, but I'm almost there. Installing GBs of Thunderbird's profile will be the final act, and I'll go.

Still at least one update short of being done with the system files, 13.3 is now released so at least the basefiles package should be upgradable to show that for the version number.

root@9600k:~# cat /etc/os-release
PRETTY_NAME="Devuan GNU/Linux 6 (excalibur)"
NAME="Devuan GNU/Linux"
VERSION_ID="6"
VERSION="6 (excalibur)"
VERSION_CODENAME="excalibur"
ID=devuan
ID_LIKE=debian
HOME_URL="https://www.devuan.org/"
SUPPORT_URL="https://devuan.org/os/community"
BUG_REPORT_URL="https://bugs.devuan.org/"
root@9600k:~# cat /etc/debian_version 
13.3

This is a comparison between my new Byte3 (5 inches square, which is just over 12 cm, and 4 cm high) using neowofetch, and my 10-year-old Lenevo (16 x 4 inches and 12 inches high) using neowatch (latter is no longer in excaliber/Debian-13 as no longer supported):

The byte3:

alexk@star 
---------- 
OS: Devuan GNU/Linux 13.2 (excalibur) x86_64 
Host: Byte 1.0 
Kernel: 6.12.57+deb13-amd64 
Uptime: 1 hour, 4 mins 
Packages: 1570 (dpkg) 
Shell: bash 5.2.37 
Resolution: 1920x1080 @ 60.00Hz 
DE: Xfce 4.20 (x11) 
WM: Xfwm4 
WM Theme: Default 
Theme: Clearlooks-Phenix-Sapphire [GTK2/3] 
Icons: Deepsea [GTK2/3] 
Cursor: DMZ-White [GTK2/3] 
Terminal: xfce4-terminal 
Terminal Font: Monospace 12 
CPU: Intel 3 N355 (8) @ 3.9GHz 
GPU: Intel Graphics] 
Memory: 1.60 GiB / 31.19 GiB (5%) 
Network: 1 Gbps 
BIOS: coreboot 0.0 (12/04/2025) 

The Lenovo:

alexk@ng3 
--------- 
OS: Devuan GNU/Linux 6 (excalibur) x86_64 
Model: 90BJ008CUK Lenovo H30-05 
Kernel: 6.12.57+deb13-amd64 
Uptime: 4 days, 17 hours, 47 mins 
Packages: 3240 (dpkg) 
Shell: bash 5.2.37 
Resolution: 1920x1080 
DE: Xfce 4.20 
WM: Xfwm4 
WM Theme: Default 
Theme: Clearlooks-Phenix-Sapphire [GTK2/3] 
Icons: oxygen [GTK2/3] 
Terminal: xfce4-terminal 
Terminal Font: Monospace 12 
CPU: AMD A8-7410 APU with AMD Radeon R5 Graphics (4) @ 2.200GHz 
GPU: AMD ATI Radeon R4/R5 Graphics 
Memory: 2438MiB / 7362MiB

The byte is so fast that I want to move to it as soon as I can. As always, it is setup that takes the time, but I'm almost there. Installing GBs of Thunderbird's profile will be the final act, and I'll go.

hth

I'm an ex-internet professional + server admin and yet was flummoxed by "amd64" as the supported architecture.

I guarantee that if I asked 10 random "IT professionals" what "amd64" meant, most wouldn't know, so you're not alone.

AMD actually called it "x86-64 (tm)" :

https://web.archive.org/web/20120308025 … e_715.aspx

Intel implemented their version of x86-64 ("amd64") as "Intel 64".

I'm not 100% sure where the "amd64" terminology originated from, but it may not have been ADM themselves.  I only ever see that used by Linux distributions or FreeBSD for example.  I seem to recall that the Linux kernel sources had the options to build a kernel type of "hammer", which refers to the original x86-64/amd64 CPU.

No problems of any kind then nor ever since. What on earth are you talking about? AMD v's intel is a non-starter here,

Especially since the instruction set contained in both chips are virtually identical due to the cross licensing agreements they both have with each other for that technology. And have had since the beginning of AMD as required by the Department of Defense in the US for Intel to get the contracts to sell to them, they required backup source of supply for their chips they were buying.

The problems starts when some AMDs are in use on Linux.

As stated above: my old box was AMD64 (a processor actually made by AMD) and was first booted in May 2016 into Devuan. No problems of any kind then nor ever since. What on earth are you talking about? AMD v's intel is a non-starter here, so I'm marking this SOLVED.

This is why it got named amd64...

Unnamed processor architectures typically get called after their inventor, so “i” in i386/i686 stands for Intel, “m” in m68k for Motorola, “a” in aarch64 for Acorn, “m” in m32r for Mitsubishi, so when AMD presented their first 64-bit Athlon running some 3D demo on SUSE it got coined as “amd64”, with all letters probably because AMD is already an acronym.

sudo dd if=devuan_excalibur_6.1.0_amd64_netinstall.iso of=/dev/sdc bs=1M && sync

My existing screen has a HDMI option, so that was plugged into the Byte, as were an aged Dell keyboard via USB, mouse via USB, a LAN connection to my Virgin Media cable box, the external 18v power via DC jack + the USB stick.

Setup was a doddle:

The first issue was to spot the console warning to access the BIOS at startup. It was "F2", but that was on-screen for a very brief time.

Inside the BIOS it was easy to spot 'choose boot disk', with the internal 2TB SSD or the USB as options after that choice. Choosing 'USB' and 'reboot', everything occurred at astonishing speed afterwards.

My existing box is 10 years old, and one of the main reasons for getting a replacement is the gigabit LAN in the new one. Virgin have upgraded their Cable to an astonishing speed, but the old box was 10/100 LAN & that was the max it could handle. The new box is tiny outside but has 10 x the speed & capacity of the old one.

I was impressed by the intelligence of the setup in the ISO. It spotted my GB location & all the options for LAN setup (lan, wlan + bluetooth). The defaults for disk setup were also intelligent.

Finally, if you have not yet spotted it, only the intelligence of me & the Devuan page is lacking. I'm an ex-internet professional + server admin and yet was flummoxed by "amd64" as the supported architecture.

The Star-Labs Byte3 is working fine with Devuan. My main problem now is the amount of time that it is going to take me to set it up to my liking, so that I can drag myself away from the old box.

Not strictly correct.  HP actually designed the Itanium and the main target was actually HP-UX and the wider server market.

Yes I left out the server users phrase in that line. The wackypedia article on the joint HP/Intel effort makes for fascinating reading for those who did not live it like I did...

https://en.wikipedia.org/wiki/Itanium

Not about "patents" as such

.

I'm aware of that and the other info posted afterward, for brevity's sake I didn't post it all because OP just wanted an answer to his question so I made a quick reply.

https://us.starlabs.systems/pages/byte

Intel was out to abandon it users and force them onto the new processors that used the ia64

Not strictly correct.  HP actually designed the Itanium and the main target was actually HP-UX and the wider server market.

Intel was never out to "abandon" any users, as ultimately, with regards to the existing x86 PC market, that was always dictated and controlled by Microsoft.  At that time, 32 bit Windows on x86 hardware was still the de facto standard.