You are not logged in.
The "invalid misc" is what you need to look into. The other devices may be ok, but is this computer closer to any potential sources of interference?
rtl8168 is your ethernet.
The broadcom devices supported by the b43 driver will not work at all without proprietary firmware extracted from the wl vendor driver tarball. If you installed what was needed via downloading and installing with dpkg, then you've probably done enough, but it wouldn't hurt to enable contrib and non-free repositories as suggested, and do an upgrade, just in case whatever packages you downloaded were for an older release? Perhaps you can elaborate on why they were installed manually and where they were sourced from?
Or did you in fact instlll wl via some other source?
depends on the broadcom card i believe. Debian saying BCM4322 (only 14e4:432b);
as for the ethernet, devuan should have pulled in firmware-realtek had non-free been enabled in the sources.list (with an update upgrade) which i believe should cover the firmware for rtl8168 ?
these two packages is what should be installed to make it functional?
I cant see how reinstalling is going to help, as you have noticed you still have the same issue.
what is the output of this command from your terminal?
lspci -knn | grep -A3 "Network"
Commented out the two deb-src repos and it works now.
why would that cause a conflict?
Looks like they were not formatted correctly?
if you dont need the cdrom lines comment them out, you still have one not commented out. If you dont need src repos comment them out as well, unless you build packages from source?
the only lines you should need are like so...
deb http://deb.devuan.org/merged beowulf main non-free contrib
deb http://deb.devuan.org/merged beowulf-security main contrib non-free
deb http://deb.devuan.org/devuan beowulf-proposed-updates main contrib non-free
if you want source repos then like this ...
deb http://deb.devuan.org/merged beowulf main non-free contrib
deb-src http://deb.devuan.org/merged beowulf main non-free contrib
deb http://deb.devuan.org/merged beowulf-security main contrib non-free
deb-src http://deb.devuan.org/merged beowulf-security main contrib non-free
# beowulf-proposed-updates for ISO testing
deb http://deb.devuan.org/devuan beowulf-proposed-updates main contrib non-free
deb-src http://deb.devuan.org/devuan beowulf-proposed-updates main contrib non-free
Ok you need to add non-free and contrib repos to make your card work properly.
you need to purge the rtl8168 dkms package first though.
read this ... https://packages.debian.org/buster/r8168-dkms
and then read this ... https://wiki.debian.org/bcm43xx
yours is b43 and b43legacy section so you need contrib and non free added to sources list.
I noticed something odd though, in Tx excessive retries:164 Invalid misc:4054 Missed beacon:0 from iwconfig wlan0.
Invalid misc:4054
that is a huge number and from websearch this might be wifi interference?
Have a read here... https://unix.stackexchange.com/question … -to-fix-it
do you have non-free repositories added to your sources list?
what is the output of this file /etc/apt/sources.list
and is there anything in /etc/apt/sources.list.d/
sounds like /etc/apt/sources.list has not got the cdrom line/lines commented out.
This is what my sources list looks like, the cdrom lines should be commented out.
# deb cdrom:[Devuan GNU/Linux 3.1 beowulf amd64 - netinstall 20210211]/ beowulf contrib main non-free
#deb cdrom:[Devuan GNU/Linux 3.1 beowulf amd64 - netinstall 20210211]/ beowulf contrib main non-free
deb http://deb.devuan.org/merged beowulf main non-free contrib
# deb-src http://deb.devuan.org/merged beowulf main non-free contrib
deb http://deb.devuan.org/merged beowulf-security main contrib non-free
# deb-src http://deb.devuan.org/merged beowulf-security main contrib non-free
# beowulf-proposed-updates for ISO testing
deb http://deb.devuan.org/devuan beowulf-proposed-updates main contrib non-free
# deb-src http://deb.devuan.org/devuan beowulf-proposed-updates main contrib non-free
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual
.
AudibleThoughts - Have You Seen The Bear Yet
You could start here: https://pkginfo.devuan.org/cgi-bin/pack … 5-1+deb9u5
So you have updated to latest stable but want to use oldstable packages?, i think you may run into some dependency issues.
dice wrote:The way i see it is that linux is just a kernel, gnu coreutils are just software and without a framework around them they are unusable by themselves without interaction from one another, unless im mistaken?
Depends...
Something must load and start the kernel (kernel floppy, then prompting for root FS floppy), and there must be something that plays PID1, which could be a statically linked shell with lots of builtins (busybox?) and you'd need some pre-existing nodes in `/dev` or something like the old devfs to auto generate them.These parts already ™should™ give a running system.
Or gave... I think the last time I did such experiments was in 0.99.15 days.
busybox-static is an interesting piece of software, i believe this is more widely used by embedded systems like alpine linux and musl-libc based systems. Something i want to learn more about that is for sure.
Found this in regards to embedded debian. https://wiki.debian.org/Embedded_Debian
golinux high-fives dice
Id like to interject here..lol
The way i see it is that linux is just a kernel, gnu coreutils are just software and without a framework around them they are unusable by themselves without interaction from one another, unless im mistaken?
SystemD is like a goul'd from startgate sg1, it takes over the host operating system and enslaves all the children!
ah so a perl module was to blame.
glad you got it solved.
Debian is without a doubt a distro. Technically speaking, GNU is the operating system that nearly all of the distros are produced from. We just call it "Linux" because it's more conventional, despite it fundamentally being nothing more than a kernel.
oops yes you are right, i always get confused on the distro / distrollete meaning. Technically speaking the debian website calls it "The Universal Operating System" or "The Operating System". Which i believe is a better term than distro, personally.
dice wrote:Well that is what devuan is about. packages have been modified and maintained to work for the devuan environment, for instance libpam-elogind over libpam-systemd.You clearly do not understand...
no I get it, but we want to be purists and we can't be purists.. we are not a free systemd distro really.. because we can't.. .. we depends on a distro that already is systemd focused.. so maybe a new way is the best.. ? cos the situation is so ironic
debian is not a "distro" it is an operating system. Devuan does not use systemd as init.
Yeah there are a few red flags on this one i agree head on a stick. This sort of configuration can be done via devuan media alone.
Can i ask how the installation media went for you, is it using the debian installer or something custom?
You can check here for this sort of thing as well, devuan is a fork of debian. Most packages people use on devuan are from the debian repositories so it benefits everyone to ask questions here or there.
Black Metallic - Catherine Wheel - Ferment
Looks like a bug has been reported ?
Seems like a new derivative has been born. I have not tested this
Looks interesting fsmithred, i will have to take some time to look through the sysv init scripts and the runit scripts before i go trying to convert to native runit scripts. When i have the time i might set up a simple dwm X setup with just the basic init processes and start small first and see how i go.
What is the rpm you wish to convert?
I came across this via websearch.
https://stackoverflow.com/questions/663 … ild-failed
I wonder if using the correct architecture might be the issue, ie; instead of noarch use x86_64 and so on?
Thankyou Lorenzo, i will go over this tomorrow and report back. Much to be learnt.
dice wrote:^ You can remove systemd all you like but if programs being built upstream are dependant on systemd then it is a bit of a conundrum to say that devuan is not really systemd free imo. Remember that devuan is a fork of debian! Its not like voidlinux or slackware or puppy linux. The same can be said for artix linux as they use the same package management as archlinux who use systemd for the init system.
umm in this way.. we are moving to sysvinit.. not passing to another incmpatible environment.. so sysv.-init does not need all the systemd units.. but need some systemd proceses and programs.. so it not complety free and so then we will relly in systemd for evert? so we must use debian? .. my head are not in headhache XD..
i really hate systemd and i must work with it! puff
Well that is what devuan is about. packages have been modified and maintained to work for the devuan environment, for instance libpam-elogind over libpam-systemd.You clearly do not understand...
^ You can remove systemd all you like but if programs being built upstream are dependant on systemd then it is a bit of a conundrum to say that devuan is not really systemd free imo. Remember that devuan is a fork of debian! Its not like voidlinux or slackware or puppy linux. The same can be said for artix linux as they use the same package management as archlinux who use systemd for the init system.
Thanks fsmithred, im not on the system with runit at present but will check it tommorow.
I should probably set up a devuan system with runit-init before i say anything more. My interest here is on how far debian has got in regards to init diversity by using debian media, and it is looking promising.