Porteus v5.01 (KDE) missing commands

[cparke]

I'm trying out the Porteus v5.01 KDE edition on my machine (which normally runs Ubuntu 18.04) via LIVE boot.

There are a few driver issues, namely the Broadcom BCM Wifi PCIe card and motherboard Audio. However, I am a bit puzzled how you left out vital Linux system administration commands like 'lspci' and 'modprobe' from the KDE version to save space, and I'm not sure how to install them?

It's also kind of puzzling that while there is no 'lspci' command installed, nevertheless the Porteus System Information utility can show 'lspci' output in the 'Misc' tab?

At any rate, my Wifi card is displayed as:
2f:00.0 Network controller [0280]: Broadcom Corporation BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
Subsystem: Dell Wireless 1520 Half-size Mini PCIe Card [1028:000e]
Kernel modules: bcma
In Ubuntu, the card works out of the box using the 'wl' kernel driver, which apparently is not included with Porteus either.

The onboard audio is also a bit puzzling, since it appears to be working in the system and I get sound from applications like the browser, but I get no sound for system sounds, including using the 'Test Sound' feature in the Sound Settings!

Once I am past these few issues, system looks great!

[Ed_P]

Welcome to Porteus cparke.

System commands require being executed in supervisory/root mode which is why you enter root's password when using the Porteus System Information app. For lspci in terminal enter sudo before the command, or enter su to run in supervisory mode.

[cparke]

I think you miss my point. It's not that I am not trying to execute 'lspci', for example, under root. It's that 'lspci' is totally missing on the KDE system! (i.e. it's not in /usr/bin)

[ncmprhnsbl]

think you miss my point. It's not that I am not trying to execute 'lspci', for example, under root. It's that 'lspci' is totally missing on the KDE system! (i.e. it's not in /usr/bin)

no, Ed is right.. the point being that lspci and other root stuff is in /sbin or /usr/sbin which is not in the unprivileged user's(guest) $PATH
it's just slackware doing things the old fashioned way.

[cparke]

Thank you for clarifying that! Yes, under sudo the command is available!