[SOLVED] Backlight and restart/shutdown won’t work

[Member aananshori]

I installed antiX 19.3 32 bit in Inspiron 11-3162 2.4.0 and updated Kernel: 5.8.7-antix.1-686-smp-pae. Backlight-brightness facility works BUT when I change the resolution by arrow keys nothing happened. Brightness remains still. I try “$ xbacklight -set 50” and it says “No outputs have backlight property,” and when I try to restart or shutdown it just log off, but when I do it from “$ antiX-cli-cc” it worked.

What should I do? please help.

Many thank
——-
System:
Host: antix1 Kernel: 5.8.7-antix.1-686-smp-pae i686 bits: 32 compiler: N/A
Desktop: IceWM 2.0.1
Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Portable System: Dell product: Inspiron 11-3162 v: 2.4.0
serial: <filter>
Mobo: Dell model: 09JC28 v: A00 serial: <filter> UEFI [Legacy]: Dell
v: 2.4.0 date: 01/31/2018
Battery:
ID-1: BAT0 charge: 8.3 Wh condition: 13.7/32.0 Wh (43%)
model: Samsung SD DELL PGYK561 status: Discharging
CPU:
Topology: Dual Core model: Intel Celeron N3050 bits: 64 type: MCP
arch: Airmont rev: 3 L2 cache: 1024 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 6400
Speed: 1978 MHz min/max: 480/2160 MHz Core speeds (MHz): 1: 2042 2: 649
Graphics:
Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx
Integrated Graphics
vendor: Dell driver: N/A bus ID: 00:02.0
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1368×768~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
direct render: Yes
Audio:
Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series
High Definition Audio
vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Sound Server: ALSA v: k5.8.7-antix.1-686-smp-pae
Network:
Device-1: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
vendor: Dell Vostro 3470 driver: ath9k v: kernel port: f040
bus ID: 01:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Qualcomm Atheros type: USB driver: btusb bus ID: 1-3:4
Drives:
Local Storage: total: 465.76 GiB used: 7.36 GiB (1.6%)
ID-1: /dev/sda vendor: Toshiba model: MQ01ABF050 size: 465.76 GiB
Partition:
ID-1: / size: 19.29 GiB used: 7.36 GiB (38.1%) fs: ext4 dev: /dev/sda7
ID-2: swap-1 size: 450.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda6
Sensors:
System Temperatures: cpu: 53.0 C mobo: 40.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 132 Uptime: 24m Memory: 1.87 GiB used: 495.8 MiB (25.9%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
inxi: 3.0.36

• This topic was modified 2 years, 3 months ago by aananshori.

[Member Xecure]

Helpful

Up

0

::

So, two problems:
1. Backlight-brightness doesn’t work.
2. Computer doesn’t poweroff or reboot from the desktop-session-exit menu.
Is this correct?

For 1. (No brightness control)
Did you boot from USB (before installation) using “failsafe” option form the menu?

I suspect the backlight brightness problem is related to using the vesa driver as the graphical xorg driver.
Did you install antiX from a USB drive? Do you still have the USB drive? If you do, try booting again and using the boot parameter
xorg=intel
and see if the brightness changes with backlight brightness when booting from USB (don’t install, this is just to test).

Also, from the live USB, does poweroff and reboot work on the antiX live session? If it does, it means something went wrong during the install. If it doesn’t, then we will figure out what error the desktop-session-exit program has.

Also, i think your computer may work a bit better with the x64 version of antiX, but we will explore this option if we cannot find a solution for your current problems.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member aananshori]

Helpful

Up

0

::

Xecure, thank you.

Yes I used USB.

I installed it using Safe Video Mode (SVM) because my screen turned blank when I choose to install in normal mode (above SVM) when install indicator hit “start init,” I wait and nothing happens.

This also happens if i choose normal mode by adding xorg=intel as well as when I choose SVM by adding intel after “xorg=”

When I use live-USB with SFM it goes well. Reboot and shutdown can proceed normally.

Should I use x64 installer?

Thank a lot.

[Member Xecure]

Helpful

Up

0

::

Download the iso with 4.19 kernel, make a live USB with it and try the xorg=intel boot parameter again in normal mode.
https://sourceforge.net/projects/antix-linux/files/Final/antiX-19/4.19_kernel/antiX-19.3_x64-full.iso/download

I have a device with an intel celeron N3060, and I can boot in live USB with xorg=intel boot parameter on normal UEFI boot. Yours is almost identical to mine, so this should work with the 4.19 kernel.
Try it out and see if it works. My guess is that the 4.9 kernel is missing some intel support for your cpu chip, but I am more positive the 4.19 does include that support.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member aananshori]

Helpful

Up

0

::

I already have my 19.3 X64 kernel Linux 4.9.235-antix.1-amd64-smp x86_64 and try putting xorg=intel as you suggested.
Holy Mary.. It works!

Thanks Xecure.

Btw, how should I mark it as solved?

[Member Xecure]

Helpful

Up

0

::

I am glad it worked.

Try to see if you can still edit your first post. It should also let you edit the post title.

Let us know if we can help with any other problem.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member userzero]

Helpful

Up

0

::

Fixed BlueZ security vulnerabilities kernels available
October 21, 2020 by anticapitalista

All users should update to the latest kernels via Package Installer, synaptic or cli-aptiX.

5.8.16 (antiX-17, antiX-19, testing and sid)
4.19.152 (antiX-17, antiX-19, testing and sid)
4.9.240 (antiX-17, antiX-19, testing and sid)
4.4.240 (antiX-17, antiX-19, testing and sid)

[Member aananshori]

Helpful

Up

0

::

Done.

Thank youu…

[Author]

Posts