- This topic has 56 replies, 10 voices, and was last updated May 14-3:07 am by Wallon.
-
Posts
-
Xecure
Sound…for me… “connecting to pulse”spinning wheels.
Then, updated to “testing”
Doesn’t see my hdmi
alpha 2 no problem…back to it !So, pulseaudio is installed and launched at startup, but pavucontrol cannot see it running?
Also, we need info on audio output (headphones, HDMI, USB speakers, etc.). Also comparing the kernel might help with figuring this out.
Compare also
inxi -Axxx
if you are using the same kernel in a2 and 19.4 testingantiX Live system enthusiast.
General Live Boot Parameters for antiX.
Brian Masinick
inxi -Gxxx Graphics: Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:1616 class-ID: 0300 Device-2: NVIDIA GK208BM [GeForce 920M] vendor: Dell driver: N/A bus-ID: 08:00.0 chip-ID: 10de:1299 class-ID: 0302 Device-3: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 2-5:3 chip-ID: 064e:920b class-ID: 0e02 serial: HF1026-T838-HN01-2-REV4261 Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz s-dpi: 96 OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 20.3.4 direct render: YesThis is shown from antiX 21, which works. I do not have antiX 19 to make a comparison; 19.4 replaced 19.3.
Intel_backlight used by the Backlight Brightness Control.--
Brian MasinickBrian Masinick
I’ll check for an old antiX USB drive. If I find one I’ll compare with whatever other versions I have available.
--
Brian MasinickBrian Masinick
Found a USB with antiX 19.3:
sudo inxi -Gxxx Graphics: Device-1: Intel HD Graphics 5500 vendor: Dell driver: N/A bus ID: 00:02.0 chip ID: 8086:1616 Device-2: NVIDIA GK208M [GeForce 920M] vendor: Dell GK208BM driver: N/A bus ID: 08:00.0 chip ID: 10de:1299 Display: server: X.Org 1.20.4 driver: vesa resolution: 1368x768~N/A OpenGL: renderer: llvmpipe (LLVM 7.0 256 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1 direct render: YesThis one doesn’t work with the backlight either, shows
no backlight controller. Maybe I didn’t have it previously afterall, but it does work in the test antiX21 and on some other distributions that have backlight programs. Offhand MX Linux has one.--
Brian MasinickXecure
ound a USB with antiX 19.3:
Graphics:
Device-1: Intel HD Graphics 5500 vendor: Dell driver: N/A bus ID: 00:02.0
chip ID: 8086:1616
[…]
Display: server: X.Org 1.20.4 driver: vesa resolution: 1368×768~N/AThis one doesn’t work with the backlight either, shows
Did you boot in failsafe or safe video mode for the antiX 19.3/19.4 editions? This is the only reason I can find for it using vesa driver instead of intel i915 driver.
If you can boot on a live antix 19.4 and use the bootcode
xorg=intel
Does it boot to the desktop, and does the backlight-brightness work?antiX Live system enthusiast.
General Live Boot Parameters for antiX.Brian Masinick
I did boot into failsafe mode on at least one of my tests. I’ll try the boot code xorg=intel and see if that makes a difference.
Meanwhile, on MX Linux 19.4 right clicking on the “Computer” shows the power level and allows me to adjust display brightness there.
The controller is definitely available and working, so I’ll try your suggestion to see if I can overcome the issue.I was beginning to suspect my runit scheduler, but I had a similar problem with a regular antiX 17.4.1 USB image too, but I’m pretty sure I was using Failsafe and therefore adding xorg=intel is an excellent suggestion.
--
Brian MasinickXecure
Remember that failsafe or safe video should only be used when normal booting doesn’t work. It will always set the video driver to vesa, which will always perform worse than the specific driver, and in some cases also not give other benefits, like changing screen brightness.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Brian Masinick
I added xorg=intel instead of running failsafe.
I also found brightness startup services that were not enabled and I enabled them and rebooted; that still didn’t solve it.
If the problem is on my end and not in a missing software component, I am on the right track.I’ll do some more digging with boot parameters, start-up settings, and anything else I can find and I’ll also compare distros that work with those that don’t.
Eventually something will become clear. My eyes aren’t very good these days and that impedes my diagnostic skills, but I’ll get there nevertheless.--
Brian Masinick
LikkMii
Liquorix kernel got it right
Anonymous
Tested creation of personal snapshot. Boots fine.
Label displayed for the first entry on the legacy bootmenu screen is simply “antix” (noquotes).
Previously, did the use of iso-snapshot with default settings yield a label bearing a YYYYMMDD suffix? Seems different, but maybe the change was intentional, by design.an observation: slim-themes-extras-antix is not listed as a dependency of slim package, so no warning is issued if that package is purged… but its removal will, per the default configuration, cause slim to fail (cannot find background image, so it pukes/quits).
Just a FWIW note: .desktop (and menu entries) remain if calcurse or luckybackup package is purged
ControlCenter } Hardware } Mouse Configuration
adjusting “cursor size” seemed to have no effect (even after loogut/login)Brian Masinick
xserver-xorg-video-intel – X.Org X server — Intel i8xx, i9xx display driver
firmware-misc-nonfree – Binary firmware for various drivers in the Linux kernelThese packages should be loaded in order to support the backlight capabilities. I’ll see if that makes a difference on the antiX releases prior to 21 A2 (which has these packages and it works).
--
Brian Masinick
Wallon
Dear All,
HPLIP installed with MX Package Installer.
Impossible to add a printer with HPLIP.
A permission is requested.
If I enter my ID and my password, it doesn’t work.Attachments:
- You must be logged in to reply to this topic.
