-
Search Results
-
Hi all,
(UPDATE: details of rfkill lists and effects – see details below bottom line.)
BOTTOM LINE:
I can’t use my built wireless card (a combo Wifi and Bluetooth Intel 4965) because of a stream of error messages that interfere with function). With the physical wireless switch turned OFF, I can use a usb wifi dongle OK. I think I either have a problem with rfkill, with the intel firmware, other bluetooth packages that I haven’t installed or a combination of these. Appreciate hearing any suggestions to diagnose and fix.Thanks in advance.
stevesr0
Details:
I am running an originally minimal Sid install which I have now increased by the addition of a “mild” Openbox based GUI and just attempted to enable the built in wireless, which is a combo wifi and Bluetooth card (Intel 4965).
However, when this is enabled, I get a continual stream of error messages (“unexpected event for opcode 0x0000”) which fill the screen in CLI mode and interfere with function when I am running X. “Rfkill block bluetooth” doesn’t help. If I disable the card completely USING THE PHYSICAL SWITCH and use a wifi USB dongle, I don’t get these errors and I can connect fine to the internet.
With former installs of Antix, I was able to use the built in wifi, so I am not sure what is causing the problem.
I didn’t have Bluetooth packages installed prior to attempting to enable wifi (using ceni). I have installed all the bluetooth related packages that seem necessary after this problem surfaced.
Perhaps one clue that I am not able to make sense of is that rfkill isn’t “reading” the block correctly when I have the physical switch turned off and on. (I will have to check this after I post this message and add the actual listings).
UPDATE – RFKILL list results:
Physical switch OFF:
phy0: Soft Block NO, Hard Block YES
phy1: Soft Block NO, Hard Block NO
(No Bluetooth line)Physical switch ON:
phy0: Soft Block YES, Hard Block NO
phy1: Soft Block YES, Hard Block NO
Bluetooth: Soft Block YES, Hard Block NOHave explored this on the internet. Have not seen a discussion of a similar problem.
- This topic was modified 1 year, 11 months ago by stevesr0.
- This topic was modified 1 year, 4 months ago by Brian Masinick. Reason: Title change
An update has not been possible for a few days. Here is the message from the terminal:
Preparing to unpack .../0-firmware-realtek_20210315-2~bpo10+1_all.deb ... Unpacking firmware-realtek (20210315-2~bpo10+1) over (20200918-1.0antix1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dDAqKy/0-firmware-realtek_20210315-2~bpo10+1_all.deb (--unpack): trying to overwrite '/lib/firmware/rtl_bt/rtl8723bs_config-OBDA8723.bin', which is also in package connman-bluetooth-firmware-antix 0.1.0 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)I don’t use bluetooth and don’t need it. Should I uninstall it and try the update again?
- This topic was modified 1 year, 11 months ago by banned.
Just done an upgrade and I have received the following which I have not had previously.
alastair@Dell-9300-antix1:~ $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: firmware-realtek 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/921 kB of archives. After this operation, 607 kB of additional disk space will be used. Do you want to continue? [Y/n] Y (Reading database ... 148734 files and directories currently installed.) Preparing to unpack .../firmware-realtek_20210315-2~bpo10+1_all.deb ... Unpacking firmware-realtek (20210315-2~bpo10+1) over (20200918-1.0antix1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-realtek_20210315-2~bpo10+1_all.deb (--unpack): trying to overwrite '/lib/firmware/rtl_bt/rtl8723bs_config-OBDA8723.bin', which is also in package connman-bluetooth-firmware-antix 0.1.0 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/firmware-realtek_20210315-2~bpo10+1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) alastair@Dell-9300-antix1:~Is there a fix please.
- This topic was modified 1 year, 12 months ago by Brian Masinick.
I have been experimenting a bit with pipewire, and I can say it is the perfect replacement for pulseaudio. I have no experience with JACK, so I will only explain how it works managing my audio on my system.
PipeWire is a server and user space API to deal with multimedia pipelines. It will be very important for Wayland server (streaming audio/video between applications and screen sharing), but it is still very useful for us xorg users.
Currently in antiX-bullseye-a2 (testing, future antiX 21), it is good enough to manage input/output audio for all my devices on my laptop. I have it set up mainly to replace pulseaudio (not installed on my system). It doesn’t require systemd and, though a service could be created for it, it is NOT needed. I have it installed with a bluetooth module, and I am able to stream audio to my bluetooth headphones (a bit jumpy, but good enough for me), use pavucontrol to manage the volume and switch between audio input/output, play audio in firefox (without apulse!!) and all this using less CPU % compared to pulseaudio (still uses more than just pure ALSA, but negligible in my experience). It also has a good audio level compared to when I am using pulseaudio and similar to pure ALSA (but this may depend on the device, and may only be my experience).
Official Debian Instructions here: https://wiki.debian.org/PipeWire
Summary of what I have done on my system:
1. Install pipewire with audio client libraries (optional, for replacing pulseaudio, jack and handling alsa requests) and bluetooth modules (optional, for bluetooth audio streaming).
sudo apt install pipewire pipewire-audio-client-libraries libspa-0.2-bluetooth
1.2 (Optional) I installed pavucontrol (without pulseaudio) to manage volume control and device switching. I prefer this to alsamixer and Sound Card Chooser. For what I use it, it is good enough.2. I add pipewire to the startup commands so it launches with the system. I edit ~/.desktop-session/startup and add it close to the beginning:
# Startup pipewire to manage my audio pipewire &3.(Optional) Prepare it to replace pulseaudio. I follow the Debian wiki instructions and create a file for pipewire:
sudo touch /etc/pipewire/media-session.d/with-pulseaudio
and also add another startup command to ~/.desktop-session/startup# Replace pulseaudio functionality with pipewire pipewire-pulse &4. (Optional) Also pipe all programs that would use alsa to use pipewire instead (makes it consistent with pulseaudio volume and lets me control all system audio with pavucontrol interface and same audio commands). I follow the Debian instructions and create the files:
sudo touch /etc/pipewire/media-session.d/with-alsa sudo cp /usr/share/doc/pipewire/examples/alsa.conf.d/99-pipewire-default.conf /etc/alsa/conf.d/5. (Optional) Let pipewire manage JACK. I have followed the Debian wiki instructions but I have never used JACK for anything before. I discovered qjackctl recently in a forum post and just wanted to see what it was. Maybe I will use this in the future, so I set it up anyway.
sudo touch /etc/pipewire/media-session.d/with-jack sudo cp /usr/share/doc/pipewire/examples/ld.so.conf.d/pipewire-jack-*.conf /etc/ld.so.conf.d/ sudo ldconfigHere is a screenshot of qjackctl of how the audio is set up right now on my system (using bluetooth headset that includes microphone to listen to youtube on firefox, with pavucontrol open to manage volume and input/output devices):

PROBLEMS:
Not everything is sunshine. There are shadows (at least for me).
A. Volumeicon is useless after setting all this up. The volume slider barely moves sometimes (it seems blocked by something), and others slightly moving it increases the volume to almost 100% (almost making me deaf). I have disabled it from startup, but I could use it for launching pavucontrol by changing the mixer command.
B. Default hotkeys/key-bindings for increasing/decreasing audio (using amixer command) doesn’t work properly. Sometimes it just blocks the audio in one channel and others volume goes too loud or too low, or gets stuck in mute. I have replaced them to use pulseaudio commands instead:pactl set-sink-volume @DEFAULT_SINK@ -5% pactl set-sink-volume @DEFAULT_SINK@ +5%C. It doesn’t remember volume levels at all from one session to the next (not a real problem compared to normal ALSA behavior, but it is worse compared to normal pulseaudio).
D. Related to B. Alsamixer doesn’t seem to match volume values with pulseaudio. They seem to work in different scales and show 0 when the other shows >0%, and jumps of 10% in one may be a 30% volume jump in the other.
E. Though long use of Bluetooth headphones has improved (no sudden disconnects after 5 minutes without audio output), I get more stuttering and distortions (sometimes), but it could be related to my bluetooth card or headset (always had some problems, so I am OK with current experience).So, this is my experience so far. Have you tested this out yourself? What was your experience?
antiX Live system enthusiast.
General Live Boot Parameters for antiX.