You are not logged in.
Pages: 1
Yes, audio works fine through my sound card, wired speakers works and wired earphones too.
Bluetooth is the only problem, it doesn't connect to any of my devices, that worked perfectly in the previous Devuan.
Hi soren and ralph.ronnquist,
I tried the suggested configuration without success...
I also compared a working ubuntu conf with my current local one, they are pretty the same...
Anyway, I also tried this earphones on a ubuntu machine (22.04), upgraded recently, and encountered the same error.
I fixed the issue by removing and rediscovering the device trough blueman, but doing the same hasn't go well on Devuan...
Also purging and reinstalling all the blueman and bluetooth packages on Devuan hasn't resolved the issue, just to check that the problem wasn't an old configuration somewhere.
I'm out of ideas...
Hi ralph.ronnquist, thanks for your reply.
I had seen that post already, I don't know what kind of gui is mentioned there, but there's no "audio profile" in blueman-manager.
The connection sometimes starts, but a timeout occurs right after, as per image.
I also tried to remove the paired device and pairing again, but it doesn't pair anymore...
I also tried removing and reloading btusb module, but without success...
Hello everyone, I experiencing some problems with bluetooth under Devuan 5.
I have the following bluetooth usb dongle:
Bus 002 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
It worked right in Devuan 4, and still working right under Ubuntu 22.04, just to excluding a falty hardware...
Trying to connect every device throug Blueman applet, ending in the following error message:
Connection failed: br-connection-page-timeout
Pulseaudio and the pulseaudio-bluetooth module are installed as well.
What can it be?
@Pix3l: please read the beowulf release notes, the answer you seek is there. Your posts in this thread are off topic.
I think it's inherent, since I try to help it to fix the problem and provide my experiences.
From devuan 2 to 3, this packages seems to went somekind of broken (like many others as I experienced).
The file /etc/pulse/client.conf.d/00-disable-autospawn.conf is not part of the deb package, it's generated by pulseaudio, and even by uncommenting or set to true autospawn, I experienced the same problems.
So, the solution for me was to switch to a next release, and solved...
That's all.
I inspected the devuan 2 and 3 pulseaudio packages, to see how the differs, but apart from some additions in configuration files, I don't see any change in default options.
Also the /etc/xdg/autostart/pulseaudio.desktop, that I think should start automatically the daemon, is there without any differences.
I think the main problem can be the daemon binary itself, and for test I recompiled it from source (14.0), there are also options to avoid systemd entirely, along others things:
--disable-systemd-daemon --disable-systemd-login --disable-systemd-journal
The original devaun packages includes some systemd services file under /usr/lib/systemd anyway.
After that, everything work without any problem, pulseaudio starts automatically at every boot.
Since I switched to devuan 3, I also experienced this issue, at every startup I need to manually start pulseaudio everytime to make firefox audible.
pulseaudio --start -v
Sick of this, I recompiled the latest version of pulseaudio from source (without systemd support by configure options), and the mute problem (on firefox) solved itself.
This issue was not present in the package for devuan 2, I think the new one is somekind of broken...
Even after reinstalling the system, the problem persists.
I switched back to devuan 2 since the 3 gave me only a lot of problems, not only networking related...
Really disappointed...
Does a directory called /var/db exist? If not try sudo mkdir /var/db
NB: I'm only guessing since I don't use DHCP. But the "can't create /var/db/dhclient.leases: No such file or directory" message looks suspicious.
Chris
Hi Chris, thanks for the reply.
No, it doesn't exists... Anyway, this error occurs only with dhclient 4.4.2, that I compiled by my self for test, the repository one is 4.4.1.
Hello,
I'm using Devuan 3, installed from scratch, and since my last packages upgrade last friday, the dhcp at boot always fail.
After login, I try /etc/init.d/networking restart and I receive an error about a wrong packet size, that I never experienced before.
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
dhclient.c:2978: Failed to send 300 byte long packet over fallback interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
done.
I also upgraded dhclient to 4.4.2 from sources, but always fails through boot and manually via /etc/init.d/networking.
It works only directly called:
$ sudo dhclient -4 eth0 -v
Internet Systems Consortium DHCP Client 4.4.2
Copyright 2004-2020 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
can't create /var/db/dhclient.leases: No such file or directory
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPOFFER of 192.168.0.2 from 192.168.0.1
DHCPREQUEST for 192.168.0.2 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.0.2 from 192.168.0.1
bound to 192.168.0.2 -- renewal in 42379 seconds.
What can I do to fix this issue? What can I check?
Since I switching from Devuan 2 to 3 there are only problems...
Hello everyone,
Since I switch from devuan 1 to 2, I experienced two kind of issues with some graphical tools and games.
The first issue affect some allegro based games in the repository, like Alex the allegator 4 and Ballz (So far, only these two were tested), trying to play result in system slowdown, 100% cpu peaks and very slow responses from the system.
The second one, results in some incorrect rendering on graphical tools, like Kolourpaint (Reference here).
Since all of these problems where not experienced in devuan 1.0, and I switched with a fresh install to 2.0 version, does someone has any kind of idea of what can cause those problems? Or has experienced the same kind of issue?
Some new version of Xserver packages or intel drivers?
My graphics card as shown from lshw and glxinfo output on rendering:
*-display
description: VGA compatible controller
product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 06
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:30 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64) memory:c0000-dffff
glxinfo | grep rendering
direct rendering: Yes
I experienced the issue in both Xfce and Trinity Desktop.
Edit 7/4/2019
Just for testing, I downgraded xserver-xorg-video-intel video driver from 2.99 to 2.21, and problem persist.
So I think the problem is somewhere else...
Edit 13/9/2019
I suspected that the problem was the graphical driver (intel i915), so uninstalled the xorg driver and VAAPI driver packages and test the games and apps, same problem.
The driver was still loaded, because it was provided also by the kernel too.
So, I blacklisted it, and well, now alex4 and ballz (I tried this two only so far) works smoothly and well!
Also KolourPaint doesn't not have the problem anymore.
$ dpkg -S i915
linux-image-4.9.0-9-amd64: /lib/modules/4.9.0-9-amd64/kernel/drivers/gpu/drm/i915
libgl1-mesa-dri:amd64: /usr/lib/x86_64-linux-gnu/dri/i915_dri.so
libgl1-mesa-dri:i386: /usr/lib/i386-linux-gnu/dri/i915_dri.so
To test, I reinstalled the xorg driver and playing around with Xorg configs.
$ cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
BusID "PCI:0:2:0"
EndSection
This seems to fix the problem.
Pages: 1