The officially official Devuan Forum!

You are not logged in.

#76 Re: Devuan » Increasing need for RAM » 2023-02-20 21:23:10

Oh, what I just found is quite interesting in this context after all (it's in German, but the charts are probably globally understandable):
https://gnulinux.ch/ressourcenverbrauch … umgebungen
Addendum: I missed an English source, it's here:
https://itvision.altervista.org/linux-d … usage.html

#77 Re: Devuan » Increasing need for RAM » 2023-02-20 21:05:18

aluma wrote:

... But the main "intruder" is modern sites, with their "decorations", browsers are forced to support them, although, in most cases, they are completely unnecessary.

Yes, I see it the same way. Unfortunately, nobody writes HTML in the editor these days. For many pages that would be enough and it would be better for the eye and orientation than those horrible pages created with CMS tools like Wordpress. If the actual information of a page in the source code is only 0.5%, then something is wrong. This code bloat is sick and it costs masses of electrical energy. We have the same thing with HTML mails. I once read that 1 less nuclear power plant would be needed on earth if everyone composing HTML mails switched to TXT mails.

#78 Re: Devuan » Increasing need for RAM » 2023-02-20 09:30:07

fsmithred wrote:

... Chimaera with 2G and 5G ... Daedalus with 2G and 5G

Yes, there is no difference or no significant difference.
For me it looks like this with Daedalus:
free -h
                                        total       used         free        shared     buff/cache      available
recovery mode                14 Gi      473 Mi      14 Gi       1.1 Mi      172 Mi            14 Gi
KDE Plasma Wayland     14 Gi      1,5 Gi       13 Gi       35  Mi      750 Mi            13 Gi

I find 473 Mi in recovery mode relatively high. That was the memory consumption including Xfce4 in the past. Less was used with LXQT and even less with LXDE.
Well, of course you also get something for this increased memory consumption. I don't want to grumble. But if you want an up-to-date system with Wayland for security reasons, it starts to get difficult with older systems.

#79 Re: Devuan » Increasing need for RAM » 2023-02-19 17:19:15

sgage wrote:

... Therefore, I decided long ago to simply trust in my kernel memory management overlords. Or something like that. :-)

Yes, exactly. I have also reached that point. Why shouldn't the RAM be used? It is there and it should not be there uselessly. That's why I don't worry much anymore when KDE Plasma consumes a bit more, especially when there is so much RAM. The system is probably intelligent enough.

#80 Re: Devuan » Increasing need for RAM » 2023-02-19 16:35:46

It's all not so simple. During my research I found that unused memory is actually wasted memory. Linux keeps data in main memory (RAM) as long as it is not needed for running or restarted programs. This data in RAM does not interfere, but it speeds up a lot when it is needed. The memory management regulates this. Therefore, the output of free is difficult to interpret. free says how much memory the system is using in advance, free does not say how much is actually needed at the moment. I just found this out in my research. Whether I have represented it all correctly, I don't know. Anyway, I mean that the result of free does not represent what the system actually needs right now.

#81 Re: Devuan » Increasing need for RAM » 2023-02-19 11:01:12

fsmithred wrote:

amd64 devuan desktop-live isos (xfce) in qemu with 3G ram. ...

Each release uses more resources. Run ps_mem.py to see that each program uses more resources in each release. I've been watching this for over 20 years and it's consistent.

Yes, but now it would be interesting to know if 3G ram uses less memory than 8G ram or 16G ram or 32G ram.

#82 Re: Devuan » Increasing need for RAM » 2023-02-18 22:03:17

charliebrownau wrote:

... EXE - Devuan with TDE https://exegnulinux.net/ ...

Wow, lots of stuff to think about. EXE GNU/LINUX: I hear about it for the first time ...

#83 Re: Desktop and Multimedia » Who has the better Wayland support? Mate or KDE Plasma? » 2023-02-18 19:39:56

Nili wrote:

... but i believe that KDE Plasma have the best and newest support for Wayland.

Yes, it could be. But Gnome causes less problems than KDE Plasma with Wayland and maybe the Mate people got the technology for Wayland from Gnome. Maybe I should just test it.
I'm also not sure if Wayland has been implemented in Mate as fully as in KDE Plasma yet.

#84 Re: Devuan » Increasing need for RAM » 2023-02-18 19:32:17

Thanks Nili, I can do something with that.
I thought so, but I didn't know it for sure:

Nili wrote:

The more RAM you have installed, the more it going to use.

On my desktop, where I'm writing right now, RAM may be consumed quietly. I don't begrudge the system that. But I also have other computers where RAM has to be saved. There startx / openbox is actually interesting. But here the memory consumption is mainly caused by browsers like Firefox. Then also other browsers etc. must be chosen.
I'm not interested in saving as much RAM as possible, but I'm still interested in the correlations. This is a purely technical interest.
Best regards

#85 Desktop and Multimedia » Who has the better Wayland support? Mate or KDE Plasma? » 2023-02-18 17:22:47

jue-gen
Replies: 8

I read that Mate 1.26 implemented Wayland for Atril, System Monitor, Pluma, Terminal and other components of the desktop. In Daedalus Wayland 1.26.0-1 is available. My question: who do you think supports Wayland better, KDE Plasma or Mate? I just want to use the desktop environment that supports Wayland better.

#86 Re: Devuan » Increasing need for RAM » 2023-02-18 12:56:05

sgage wrote:

... I don't think 420 MB used is that bad in this day and age.

No, it's actually not bad. And it fits with how I experienced it with Chimaera. The jump came for me only with Daedalus.

#87 Re: Devuan » Increasing need for RAM » 2023-02-18 10:50:36

Camtaf wrote:

Using XFCE/Firefox, & having been on the internet for some time now, here is my memory usage.....

$ free -m
               total        used        free      shared  buff/cache   available
Mem:            3731         993        1693         255        1044        2251
Swap:            255           0         255

This shows that the problem is really the KDE desktop.

This is how it looks here:

$ free -m
              gesamt       benutzt     frei      gemns.  Puffer/Cache verfügbar
Speicher:      15359        1547       13331          36         786       13811
Swap:            979           0         979

Yes, KDE requires a lot. Gnome but even more, I think. In the past, LXDE needed about 300, Xfce4 about 430, LXQt about 400 directly after startup. But as I said, it also depends on which services are started. I used to have KDE Plasma running at about 600 right after startup.
Maybe it has nothing to do with it, but I mean, at least at the same time as the 6* kernel arrived, the memory consumption went up.

#88 Devuan » Increasing need for RAM » 2023-02-18 08:14:40

jue-gen
Replies: 34

I am undecided where to put this topic. Therefore, I simply put it here. It also affects the future development of Devuan:

I increasingly notice that the need for memory is growing. I use Daedalus. Right now KDE Plasma needs 1.5Gi right after startup. Of course this depends on everything that is started with the desktop environment. Therefore I don't want to compare hard numbers here. But my impression is that the system with KDE Plasma demands twice as much RAM, Xfce4, LXQt and LXDE roughly two or three times. I observed this on a ThinkPad with 8 Gi and a desktop with 16 Gi.  About 1.5Gi right after startup I think is worth mentioning. What do you guys think?

#89 Re: News & Announcements » X.Org Security Advisory: Security issue in the X server » 2023-02-16 12:25:43

fsmithred wrote:

lxdm and sddm both run X as root. To check that, run

ps aux |grep X

Thanks for this! It looks like I'll have to give it some thought. I would be interested in more information on this topic and strategies for improvement.

#90 Re: News & Announcements » X.Org Security Advisory: Security issue in the X server » 2023-02-16 07:33:17

Head_on_a_Stick wrote:

... The default Xfce desktop for Devuan uses SLiM or LightDM and both run X under the root user so both are vulnerable to this exploit.

Starting the desktop via GDM or startx will cause X to be run under the normal user and so avoid this vulnerability completely. ... )

Perhaps I have not understood the problem correctly. SLiM or LightDM is clear. But I am thinking about it:
How is it with SDDM?
When I start Plasma Wayland, that is o.k.
But if I start e.g. LXDE with SDDM, how is that.

#91 Re: News & Announcements » X.Org Security Advisory: Security issue in the X server » 2023-02-11 19:41:27

hunter0one wrote:

... I like KDE applications, I do not like KDE Plasma. ...

Yes, I can understand that very well.
Wayland is apparently more secure. By the way, I liked to use KDE applications in LXDE or Xfce. Of course it was also very nice in LXQt. Now I came back to KDE (I started with KDE in 2001 [SuSE 7.2]) because I wanted Wayland and I like the KDE applications. Right now I like it quite a bit.
Have a nice rest of the weekend - best regards
Addendum: in continuous use, however, I now actually notice some problems. For example, the taskbar is gone from time to time, nothing can be inserted from the cache, etc. In LXQt, which I use in parallel on the same computer, these problems do not occur ... but there again I have no Wayland sad

#92 Re: News & Announcements » X.Org Security Advisory: Security issue in the X server » 2023-02-11 09:48:34

hunter0one wrote:

... I just stuck with KDE.

I always had trouble with KDE Plasma and Wayland. I've cursed it and wished it to hell. But your post triggered me yesterday to try it again (Daedalus). At least no crashes I noticed. And Wayland runs. I'm still reluctant, but I'm also optimistic and hope that it will be a usable and recommendable system when Dadalus becomes stable....

#93 Re: Installation » [SOLVED] Debian / non-free-firmware » 2023-02-01 18:09:37

MiyoLinux wrote:

Yes (No??? tongue ), it doesn't work on my chimaera installation. The OP referenced Debian unstable, so it probably hasn't worked its way down yet. If it does work its way down.

Unfortunately, I don't have a daedalus installation to try it on, but it does work on ceres.

With Daedalus (descended from Bookworm) it is available.

#94 Re: Installation » [SOLVED] Debian / non-free-firmware » 2023-02-01 17:37:25

I have added the line and commented out everything else for now until Daedalus is stable:

deb http://deb.devuan.org/merged daedalus main non-free contrib non-free-firmware

Nala works well with it:

nala update && nala upgrade && nala clean && nala autopurge && nala autoremove

Everything looks good.

#95 Installation » [SOLVED] Debian / non-free-firmware » 2023-02-01 07:45:29

jue-gen
Replies: 10

Debian apparently now recommends users who already have non-free and/or contrib in their sources to add the non-free-firmware entry to ensure that future access to non-free software continues:

deb http://deb.debian.org/debian/ unstable main contrib non-free non-free-firmware

Do I have to do the same for the Devuan-sources-list?

#96 Re: Desktop and Multimedia » shut down Daedalus: warning: alsactl store -e HOME= ... » 2023-01-31 20:51:41

MLEvD wrote:

Devuan has something missing in the alsa department, there's a value not saved in mate-media : Sound Preferences -> Hardware -> Profile, not persisting over reboot.

Ah, o.k., thank you. It does not affect my work with the computer. However, it is strange that I have the message on desktop PC, but not on my ThinkPad, although it is exactly the same system.
Best regards

#97 Desktop and Multimedia » shut down Daedalus: warning: alsactl store -e HOME= ... » 2023-01-27 21:27:35

jue-gen
Replies: 2

When I shut down Daedalus, I get this message:
Shutting down alsa ... warning: alsactl store -e HOME=/run/alsa -e xdg_runtime_Dir=/run/alsa/runtime failed with error message alsactl: get_control:255:Cannot read control 3.0.0Playback channelMap.0: invalid argument ... failed
Does anyone have any ideas about this?

#98 Re: Hardware & System Configuration » [SOLVED] No screen after suspend2ram » 2023-01-18 21:34:50

Head_on_a_Stick wrote:

Looks fine to me.

I love Devuan!

#99 Re: Hardware & System Configuration » [SOLVED] No screen after suspend2ram » 2023-01-18 20:14:47

chris2be8 wrote:

To get kernel driver info you need to use lspci -knn (pipe it into less to keep screen output searchable). See the man page for lspci.

Thank you.I have done it. It will look like this:

lspci -knn
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex [1022:1630]
	Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex [1022:1630]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634]
	Kernel driver in use: pcieport
00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634]
	Kernel driver in use: pcieport
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
	Kernel driver in use: pcieport
00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
	Kernel driver in use: pcieport
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51)
	Subsystem: ASRock Incorporation FCH SMBus Controller [1849:ffff]
	Kernel driver in use: piix4_smbus
	Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
	Subsystem: ASRock Incorporation FCH LPC Bridge [1849:ffff]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0 [1022:1448]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1 [1022:1449]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2 [1022:144a]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3 [1022:144b]
	Kernel driver in use: k10temp
	Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4 [1022:144c]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5 [1022:144d]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6 [1022:144e]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7 [1022:144f]
01:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller [1022:43d5] (rev 01)
	Subsystem: ASMedia Technology Inc. 400 Series Chipset USB 3.1 XHCI Controller [1b21:1142]
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
01:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller [1022:43c8] (rev 01)
	Subsystem: ASMedia Technology Inc. 400 Series Chipset SATA Controller [1b21:1062]
	Kernel driver in use: ahci
	Kernel modules: ahci
01:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge [1022:43c6] (rev 01)
	Kernel driver in use: pcieport
02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
	Kernel driver in use: pcieport
02:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
	Kernel driver in use: pcieport
02:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
	Kernel driver in use: pcieport
02:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
	Kernel driver in use: pcieport
02:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
	Kernel driver in use: pcieport
02:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port [1022:43c7] (rev 01)
	Kernel driver in use: pcieport
06:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
	Subsystem: Intel Corporation Wi-Fi 6 AX200 [8086:0084]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
07:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
	Subsystem: ASRock Incorporation Motherboard [1849:0612]
	Kernel driver in use: ahci
	Kernel modules: ahci
08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
	Subsystem: ASRock Incorporation Motherboard (one of many) [1849:8168]
	Kernel driver in use: r8169
	Kernel modules: r8169
09:00.0 Non-Volatile memory controller [0108]: Sandisk Corp WD Blue SN550 NVMe SSD [15b7:5009] (rev 01)
	Subsystem: Sandisk Corp WD Blue SN550 NVMe SSD [15b7:5009]
	Kernel driver in use: nvme
	Kernel modules: nvme
0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9)
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu
0a:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
0a:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
	Subsystem: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
	Kernel driver in use: ccp
	Kernel modules: ccp
0a:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1 [1022:1639]
	Subsystem: ASRock Incorporation Renoir USB 3.1 [1849:ffff]
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
0a:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1 [1022:1639]
	Subsystem: ASRock Incorporation Renoir USB 3.1 [1849:ffff]
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
0a:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3]
	Subsystem: ASRock Incorporation Family 17h (Models 10h-1fh) HD Audio Controller [1849:7893]
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
0b:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 81)
	Subsystem: ASRock Incorporation FCH SATA Controller [AHCI mode] [1849:ffff]
	Kernel driver in use: ahci
	Kernel modules: ahci
0b:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 81)
	Subsystem: ASRock Incorporation FCH SATA Controller [AHCI mode] [1849:ffff]
	Kernel driver in use: ahci
	Kernel modules: ahci

I do not find any error.
However, I am now actually reaching the limit of my understanding. Do you see a problem in this issue?
Tank You and best regards

#100 Re: Hardware & System Configuration » [SOLVED] No screen after suspend2ram » 2023-01-17 16:47:38

Many thanks to Head_on_a_Stick for the support. I have always found Devuan and this forum here very friendly.
Yes, the screen is back after suspend!
My wireless card works.
It all works now and I will continue to try to optimize the system. I think now I will soon have the best Linux I have ever had. ;-)
Addendum:
But with lspci I can't find any information about 'kernel driver in use' or amdgpu.

lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7
01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 XHCI Controller (rev 01)
01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01)
01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01)
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
06:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
07:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
09:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN550 NVMe SSD (rev 01)
0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev d9)
0a:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637
0a:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
0a:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
0a:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller
0b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
0b:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)

ip link gives this output:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 70:85:c2:99:3f:f4 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 7c:21:4a:8d:e3:1b brd ff:ff:ff:ff:ff:ff

Board footer

Forum Software