You are not logged in.
Pages: 1
Thanks everyone
, I removed the Architecture: ... line plus updated my system and finally the 32bit juice is started flowing. 😋
This is how devuan.sources looks like now:
## Devuan 7 freia
## The new style method of using repositories to install software.
## This /etc/apt/sources.list.d/devuan.sources is new style and location file
## The /etc/apt/old.style.sources.list contains the same as this.
## https://linuxconfig.org/ubuntus-repository-configuration-ubuntu-sources-have-moved-to-etc-apt-sources-list-d-ubuntu-sources
## Normal freia sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia
#freia-backports freia-proposed-updates freia-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
## freia security sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia-security
Components: main non-free contrib non-free-firmware
Enabled: no
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpgMaybe dpkg can't deal with the deb822 sources?
I was wondering the same. I've never seen anything like this in any debian-based system. adding 32-bit support is usually a one-liner. As you said, Probably dpkg can't deal with deb822 cause it's outdated or something.
Regards and have a nice day.
Thank you so much for replying.
As you may see, it's a non-free package.
Yes I have non-free repos enabled in my devuan.sources as shown in post #1. However the Architectures: entry is amd64 is this the issue?
Well, the devuan.sources as shown in post #1 does only contain amd64 as architecture. There is no i386. While non-free is in there.
So should I add the i386 architecture to devuan.sources?
Could you please elaborate how can I add it?
Do I need to add it like that?
Could you please check if this is ok:
## 32-bit freia sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia
#freia-backports freia-proposed-updates freia-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: i386I already have run sudo apt-get update. Unfortunately it still gives me the same error message. ![]()
~ $ sudo apt-get update
Hit:1 https://nvidia.github.io/libnvidia-container/stable/deb/amd64 InRelease
Get:2 http://deb.devuan.org/merged freia InRelease [43.4 kB]
Hit:3 https://dl.winehq.org/wine-builds/debian forky InRelease
Fetched 43.4 kB in 2s (25.2 kB/s)
Reading package lists... Done
~ $ sudo apt install nvidia-driver-libs:i386
Package nvidia-driver-libs:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Error: Package 'nvidia-driver-libs:i386' has no installation candidateHello guys. I'm here again and this time, apparently I can't install this library on my system. ![]()
This time https://pkginfo.devuan.org/ CAN actually find the package for devuan freia but my package manager says that its not available. I think it's not configured properly but I couldn't figure it out.
I only ran sudo dpkg --add-architecture i386 to add 32bit support. (Do I need to add anything to devuan.sources?)
This is the output of dpkg
~ $ dpkg --print-foreign-architectures
i386and apt
$ sudo apt install nvidia-driver-libs:i386
[sudo] password for mypc:
Package nvidia-driver-libs:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Error: Package 'nvidia-driver-libs:i386' has no installation candidateand this is my devuan.sources:
~ $ cat /etc/apt/sources.list.d/devuan.sources
## Devuan 7 freia
## The new style method of using repositories to install software.
## This /etc/apt/sources.list.d/devuan.sources is new style and location file
## The /etc/apt/old.style.sources.list contains the same as this.
## https://linuxconfig.org/ubuntus-repository-configuration-ubuntu-sources-have-moved-to-etc-apt-sources-list-d-ubuntu-sources
## Normal freia sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia
#freia-backports freia-proposed-updates freia-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
## freia security sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia-security
Components: main non-free contrib non-free-firmware
Enabled: no
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64Thank you for answering.
May I ask why there isn't an official WINE package in freia repos?
Is it possible to install wine on devuan freia?
https://pkginfo.devuan.org/ shows nothing for freia and sudo apt install wine returns this:
Package wine is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Error: Package 'wine' has no installation candidateHere is my sources.list
~ $ cat /etc/apt/sources.list.d/devuan.sources
## Devuan 7 freia
## The new style method of using repositories to install software.
## This /etc/apt/sources.list.d/devuan.sources is new style and location file
## The /etc/apt/old.style.sources.list contains the same as this.
## https://linuxconfig.org/ubuntus-repository-configuration-ubuntu-sources-have-moved-to-etc-apt-sources-list-d-ubuntu-sources
## Normal freia sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia
#freia-backports freia-proposed-updates freia-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
## freia security sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia-security
Components: main non-free contrib non-free-firmware
Enabled: no
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64My first reaction was: that lib is outdated.
Indeed, It's outdated but it is a crutial for A LOT of AppImages out there to run properly.
I ended up with an isolated solution to keep everything separated from apt/system packages.
Downloaded libfuse deb from ubuntu questing repo.
Extracted the *.so files and put it inside /opt/libfuse2/
Made a conf file inside /etc/ld.so.conf.d/
Like this:
$ cat /etc/ld.so.conf.d/fuse2compat.conf
/opt/libfuse2/Then I ran: sudo ldconfig
This package is needed by a dozen of my AppImages to work properly. They refuse to open without this package.
running sudo apt search libfuse returns this:
golang-github-hanwen-go-fuse-dev/testing 2.8.0-1 all
Native Go bindings for the FUSE kernel module
libfuse3-4/testing,now 3.18.2-1 amd64 [installed,automatic]
Filesystem in Userspace (library) (3.x version)
libfuse3-dev/testing 3.18.2-1 amd64
Filesystem in Userspace (development) (3.x version)
python3-pyfuse3/testing 3.4.0-3+b4 amd64
Python 3 bindings for libfuse 3 with asynchronous API
python3-pyfuse3-doc/testing 3.4.0-3 all
Python 3 bindings for libfuse 3 with asynchronous API (documentation)How can I install this library on my system?
Thank you so much for anwering in datails and helping me out with this. Everything is working as expected now.
You have until 2030 or so as well but you should consider switching too the new format devuan.sources too. My current file that has all of these things enabled.
Good to know. I swtiched to the new style. Thanks for the tip.
There were some small issues that I want to mention:
1. I changed http://gnlug.org/pub/devuan/merged to http://deb.devuan.org/merged. It was slow for me.
Hopefully those are mirrors and I didn't mess things up. Right?
2. It looks like that the way you commented the Suites: section wasn't correct. apt was still seeking for non-existant things.
I put the comment in a newline and it worked.
...
Get:3 http://deb.devuan.org/merged freia InRelease [43.4 kB]
Ign:4 http://deb.devuan.org/merged #freia-backports InRelease
Ign:5 http://deb.devuan.org/merged freia-proposed-updates InRelease
Ign:6 http://deb.devuan.org/merged freia-updates InRelease
Err:7 http://deb.devuan.org/merged #freia-backports Release
404 Not Found
Err:8 http://deb.devuan.org/merged freia-proposed-updates Release
404 Not Found
Err:9 http://deb.devuan.org/merged freia-updates Release
404 Not Found
Get:10 http://deb.devuan.org/merged freia/main amd64 Packages [9,866 kB]
...Here's my final config:
## Devuan 7 freia
## The new style method of using repositories to install software.
## This /etc/apt/sources.list.d/devuan.sources is new style and location file
## The /etc/apt/old.style.sources.list contains the same as this.
## https://linuxconfig.org/ubuntus-repository-configuration-ubuntu-sources-have-moved-to-etc-apt-sources-list-d-ubuntu-sources
## Normal freia sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia
#freia-backports freia-proposed-updates freia-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
## freia security sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia-security
Components: main non-free contrib non-free-firmware
Enabled: no
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64The security repository is for fixes that apply to already released software while it is a still supported version, the unreleased versions get fixed by new uploads to the development repositories. Which then find their way into the testing/unstable branches of those repositories.
Thank you for your answer.
BTW it looks like freia-updates doesn't exist either. Should I remove the second line too?
I changed everything in /etc/apt/sources.list from Excalibur to Freia. However I don't have -security in my sources.list because it apparently doesn't exist.
Is it OK?
deb http://deb.devuan.org/merged freia main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged freia-updates main contrib non-free non-free-firmware
#deb http://deb.devuan.org/merged freia-security main contrib non-free non-free-firmwareThank you all for taking your time. 🧡
Indeed the package was fontsnaps. Running sudo apt purge fontsnaps got rid of it.
Hello. Which package is related to these files:
/usr/share/applications/LARGER_FONTS.desktop
/usr/share/applications/SMALLER_FONTS.desktop
adjfontsize🎉 Thank you so much for helping me. After upgrading that package, the dongle is working as expected. ![]()
TLDR, for users who might stumble upon this:
1. Enable backports by adding the backports repo to the file (For me it was there i just uncommented it): /etc/apt/sources.list
2. Install newer version of the Linux kernel from the backports repo: sudo apt install linux-image-amd64/daedalus-backports
3. Upgrade Realtek packages: sudo apt install -t daedalus-backports firmware-realtek
4. Reboot your system.
I don't know how new this adapter is. The firmware is from 2023, two years old. In any case installing the backports firmware is worth a try.
Linux kernel 6.2 was officially released on February19,2023 according to chatgpt. I'll give it a shot
Does the command
# modprobe rtl8xxxu
change anything?
It returned nothing and inxi is the same. So probably it did nothing.
How did you install Devuan? Which release are you using?
I installed Devuan from desktop-live ISOs.
Hello, I'm currently testing Devuan on my machine. everything is fine except my WiFi dongle. The RTL8188FTV/FU has been supported by the Linux kernel since 6.2.
I enabled backports and upgraded my kernel to 6.12. but nothing changed. Note that on the same machine, Ubuntu and any other distro with a recent kernel brings up the WiFi device, Devuan is the exception here.🙁
~$ inxi -N
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
Device-2: Realtek RTL8188FTV 802.11b/g/n 1T1R 2.4G WLAN Adapter type: USB
driver: N/Aon ubuntu 25 the output of inxi -N for my usb device is rtl8xxxu or something like that....
kernel version:
~$ uname -r
6.12.43+deb12-amd64~$ apt list --installed | grep realtek
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
firmware-realtek/stable,now 20230210-5 all [installed]maybe I should fetch this firmware from backports? IDK.
Regards.
Pages: 1