You are not logged in.
Edge Of Allegiance by Timbuk 3.
Pale Moon looks promising
No, it doesn't: https://digdeeper.neocities.org/ghost/b … l#palemoon
^ I've never needed to add any users to the audio group to get the sound working in Debian.
@OP: it doesn't look like PulseAudio is running so try starting it and see if that changes anything.
You can also try
# alsactl initBut it looks like the system doesn't recognise an analogue soundcard, which is strange.
Can we see
lspci -k | grep -iA2 AudioWhich logs shall I post to pastebin for an analysis?
The X.Org log, /var/log/messages & /var/log/syslog.
Try this:
auto eth0
iface eth0 inet static
address 10.5.5.31/24
gateway 10.5.5.1
metric 10
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 10.5.5.1
dns-search lan.atHome
# WLAN @ Home
auto wlan0
iface wlan0 inet static
address 10.5.5.32/24
gateway 10.5.5.1
metric 20
dns-nameservers 10.5.5.1
dns-search lan.atHome
wpa-ssid SSID
wpa-psk passwdThe metric keyword assigns a priority to the interface, a lower metric value causes that interface to be favoured over the other.
I don't want to switch my complete home network from static to dynamic adresses right now
You can set specific address with a DHCP client.
I've never tried having both ethernet and wireless configured via /etc/network/interfaces and my Debian system is gone now so I can't fiddle with it to test what works (sorry).
If you're using chimaera then perhaps try iwd for the wireless connection. That can both associate with the SSID and assign the IP addresses all by itself.
I think the RTNETLINK error is because the gateway is defined twice.
Try using DHCP for the wireless interface.
Is the AMD graphics firmware installed? The µcode package should also be installed but I'm not sure if there are any fixes for the Ryzen 4000 series yet.
Linux will gain some M1 support for v5.13:
Users shouldn't need to be in the audio group for the speakers to work.
@OP: can we see
aplay -l
amixerCan we see
ip a
ip r
ping -c3 8.8.8.8
ping -c3 google.com
rfkill list allEDIT: I presume wpa-sssid & wpa-psk have the actual SSID & password filled in (rather than SSID & passwd)?
The amdgpu drivers are part of the kernel, AMD contribute directly to them so they are official. They also provide the firmware, which can be downloaded and added to /lib/firmware/ manaully if need be. If you want to try a newer kernel in Devuan then perhaps look at https://liquorix.net/ — their bullseye versions should be compatible with beowulf.
But I suspect your artefact problems are due to Mesa. IIRC there was a recent thread over at the Arch forums in which an AMD user fixed the glitches by using the mesa-git AUR package, which should also be installable in Artix. The most recent Mesa packages in Debian are only available from the experimental repositories and they are the same as the Arch (non-AUR) versions. The versions in sid/ceres should catch up once Debian 11 has been released though.
EDIT: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4691
Please open a new thread for your new query. Try to stick to one question per thread and please choose a title that succinctly describes the actual problem at hand so as to aid SEO. Thanks.
@trizen is the author, I just supply the Debian & *buntu packages.
- EEE is not supported on all Intel(R) Ethernet Network devices or at all link speeds.
Check
# ethtool --show-eee eth0I think this is the e1000 driver but the 82566DM-2 controller uses the e1000e driver.
Oh yes, sorry, my mistake. The 4.19 kernel documentation doesn't seem to have a section for the e1000e module, or at least not that I can find.
Here's the page for my 5.11 kernel: https://www.kernel.org/doc/html/v5.11/n … 1000e.html
You can also use the modinfo command.
No error for madeup_nonsense=1 then?
The error message is printed to the kernel ring buffer rather than stdout or stderr:
$ doas dmesg | grep e1000e
[13821.559641] e1000e: unknown parameter 'EEE' ignored
[13821.559729] e1000e: Intel(R) PRO/1000 Network Driver
[13821.559730] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[13922.922522] e1000e: unknown parameter 'madeup_nonsense' ignored
[13922.922575] e1000e: Intel(R) PRO/1000 Network Driver
[13922.922575] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
$Check for the available module parameters:
ls /sys/module/e1000e/parametersOfficial documentation here: https://www.kernel.org/doc/html/v4.19/n … e1000.html
So now the unknown parameter is known?
No:
$ doas modprobe -v e1000e madeup_nonsense=1
insmod /lib/modules/5.11.16-zen1-1-zen/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko.xz madeup_nonsense=1
$What folder? The file is at /usr/share/polkit-1/actions/com.ubuntu.pkexec.synaptic.policy
Is there a frontend for that
The wpagui package works with /etc/network/interfaces if this line is used instead of the wpa-ssid & wpa-psk lines:
wpa-conf /etc/wpa_supplicant/wpa_supplicant.confThen create the configuration file with these options listed to allow it to be altered by wpagui:
ctrl_interface=/run/wpa_supplicant
update_config=1Legacies of the Sword: The Kashima-Shinryu and Samurai Martial Culture by Karl Friday
It finally arrived. A very good book — the author is both a professor of Japanese history and also a shihan (Kashima-Shinryū instructor) so it is an authoritative text on the subject. Now I just have to wait for the local chapter to re-open. Bloody COVID.
I also received my copy of A Canticle For Leibowitz by Walter M. Miller, a seminal science fiction classic.
Does that method require dbus?
Connecting via /etc/network/interfaces & ifupdown does not require dbus.
Then I believe you could use iwctl to make connections
/etc/network/interfaces uses wpa_supplicant rather than iwd. The iwd version in beowulf is pre-release and so probably should not be used.
For what purpose do you want to set up policy kit?
If you want to use pkexec to launch GUI applications with superuser privileges (which is a bad idea) then you can create some authorisation rules for the programs. See the files provided by synaptic & gparted for examples of this.
Is policy kit even necessary?
No.
is that all there is to it ?
Yes. But it might be worth resetting the hardware clock & /etc/adjtime after the system clock has been updated:
# hwclock --systohcIf you need to change the time zone use this first:
# dpkg-reconfigure tzdataEdit /etc/initramfs-tools/conf.d/resume to
RESUME=noneThen
# update-initramfs -u -k allNote that you don't appear to have a swap file at all so you should probably remove that term from the title and OP.