Windows selection loop… A weird behaviour

[Member cenga]

Dear All,

I run the Antix 19.2 live from USB and having that weird behaviour always, here is the video; https://streamable.com/9r9tio
What might be the reason, any clues will be appreciated.

Specs are;

System: Host: antix1 Kernel: 4.9.212-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: vga=791 quiet splasht disable=lxF
Desktop: IceWM 1.6.5 dm: SLiM 1.3.6
Distro: antiX-19.2_x64-full Hannie Schaft 27 March 2020
base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: TOSHIBA product: Satellite A350 v: PSAL6E-03000LTE
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: TOSHIBA model: KTKAA v: 1.00 serial: <filter> BIOS: TOSHIBA v: 2.30
date: 09/03/2009
Memory: RAM: total: 3.83 GiB used: 259.9 MiB (6.6%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
PCI Slots: Permissions: Unable to run dmidecode. Root privileges required.
CPU: Topology: Dual Core model: Intel Core2 Duo T6400 bits: 64 type: MCP arch: Penryn
family: 6 model-id: 17 (23) stepping: A (10) microcode: A0B L2 cache: 2048 KiB
bogomips: 7979
Speed: 1200 MHz min/max: 1200/2000 MHz Core speeds (MHz): 1: 1200 2: 1600
Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cx16 cx8 de
ds_cpl dtes64 dtherm dts est fpu fxsr ht kaiser lahf_lm lm mca mce mmx monitor msr mtrr
nopl nx pae pat pbe pdcm pebs pge pni pse pse36 rep_good sep ss sse sse2 sse4_1 ssse3
syscall tm tm2 tsc vme xsave xtpr
Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
Type: l1tf mitigation: PTE Inversion
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: tsx_async_abort status: Not affected
Graphics: Device-1: AMD RV620/M82 [Mobility Radeon HD 3450/3470]
vendor: Toshiba America Info Systems driver: radeon v: kernel bus ID: 01:00.0
chip ID: 1002:95c4
Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1920×1080~60Hz
OpenGL: renderer: AMD RV620 (DRM 2.49.0 / 4.9.212-antix.1-amd64-smp LLVM 7.0.1)
v: 3.3 Mesa 18.3.6 compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel 82801I HD Audio vendor: Toshiba America Info Systems
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:293e
Device-2: AMD RV620 HDMI Audio [Radeon HD 3450/3470/3550/3570] driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 1002:aa28
Sound Server: ALSA v: k4.9.212-antix.1-amd64-smp
Network: Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet
vendor: Toshiba America Info Systems RTL810xE driver: r8169 v: 2.3LK-NAPI port: 4000
bus ID: 0e:00.0 chip ID: 10ec:8136
IF: eth0 state: down mac: <filter>
Device-2: Intel WiFi Link 5100 driver: iwlwifi v: kernel port: 4000 bus ID: 14:00.0
chip ID: 8086:4232
IF: wlan0 state: down mac: <filter>
WAN IP: No WAN IP data found. Connected to the web? SSL issues?
Drives: Local Storage: total: 247.34 GiB used: 3.4 MiB (0.0%)
ID-1: /dev/sda vendor: Hitachi model: HTS543225L9SA00 size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 1.5 Gb/s rotation: 5400 rpm serial: <filter>
rev: C43C scheme: MBR
ID-2: /dev/sdb type: USB vendor: A-Data model: USB Flash Drive size: 14.45 GiB
block size: physical: 512 B logical: 512 B serial: <filter> rev: 1100 scheme: MBR
Message: No Optical or Floppy data was found.
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: N/A size: 3.03 GiB used: 3.4 MiB (0.1%) fs: overlay source: ERR-102
label: N/A uuid: N/A
ID-2: /live/boot-dev raw size: 14.45 GiB size: <root required> used: <root required>
fs: vfat dev: /dev/sdb1 label: ANTIX-LIVE uuid: 58B7-788A
ID-3: /live/linux raw size: 1.03 GiB size: <root required> used: <root required>
fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A
Unmounted: ID-1: /dev/sda1 size: 100.0 MiB fs: ntfs label: Sistem Ayr\xc4\xb1ld\xc4\xb1
uuid: 867C1F387C1F230B
ID-2: /dev/sda2 size: 232.79 GiB fs: ntfs label: N/A uuid: 4A2821C12821ACBF
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 speed: 480 Mb/s
chip ID: 1d6b:0002
Hub: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 speed: 480 Mb/s
chip ID: 1d6b:0002
Device-1: 2-3:4 info: A-DATA type: Mass Storage driver: usb-storage interfaces: 1
rev: 2.1 speed: 480 Mb/s chip ID: 125f:dd32 serial: <filter>
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Device-2: 6-1:2 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID
driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s
chip ID: 046d:c52b
Device-3: 6-2:3 info: Logitech type: Keyboard,HID driver: hid-generic,usbhid
interfaces: 2 rev: 2.0 speed: 12 Mb/s chip ID: 046d:c336 serial: <filter>
Hub: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 8-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Sensors: System Temperatures: cpu: 42.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http: //la.mxrepo.com/antix/buster buster main nonfree nosystemd
Active apt repos in: /etc/apt/sources.list.d/buster-backports.list
1: deb http: //deb.debian.org/debian buster-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http: //ftp.us.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http: //ftp.us.debian.org/debian/ buster main contrib non-free
2: deb http: //security.debian.org/ buster/updates main contrib non-free
No active apt repos in: /etc/apt/sources.list.d/onion.list
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 9.6% command: xorg pid: 5572 mem: 59.4 MiB (1.5%)
2: cpu: 5.3% command: gtkdialog pid: 6509 mem: 32.6 MiB (0.8%)
3: cpu: 3.9% command: slim pid: 5556 mem: 10.0 MiB (0.2%)
4: cpu: 2.4% command: apt-notifier.py started by: python pid: 6113 mem: 80.7 MiB (2.0%)
5: cpu: 1.2% command: [kworker/0:1] pid: 29 mem: 0.00 MiB (0.0%)
Memory top: 5
1: mem: 80.7 MiB (2.0%) command: apt-notifier.py started by: python pid: 6113 cpu: 2.4%
2: mem: 59.4 MiB (1.5%) command: xorg pid: 5572 cpu: 9.6%
3: mem: 32.6 MiB (0.8%) command: gtkdialog pid: 6509 cpu: 5.3%
4: mem: 30.2 MiB (0.7%) command: yad pid: 6566 cpu: 0.0%
5: mem: 28.5 MiB (0.7%) command: rox pid: 5882 cpu: 1.2%
Info: Processes: 153 Uptime: 1m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers:
gcc: 8.3.0 alt: 8 Client: shell wrapper v: 5.0.3-release inxi: 3.0.36

[Member Xecure]

Helpful

Up

0

::

cenga wrote:

Graphics: Device-1: AMD RV620/M82 [Mobility Radeon HD 3450/3470]
vendor: Toshiba America Info Systems driver: radeon v: kernel bus ID: 01:00.0
chip ID: 1002:95c4
Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1920×1080~60Hz
OpenGL: renderer: AMD RV620 (DRM 2.49.0 / 4.9.212-antix.1-amd64-smp LLVM 7.0.1)
v: 3.3 Mesa 18.3.6 compat-v: 3.0 direct render: Yes

I am almost 100% certain it is related to the radeon driver. Please test the 19.2 with kernel 4.19 to see if the fix was implemented in a newer kernel.
https://sourceforge.net/projects/antix-linux/files/Final/antiX-19/4.19_kernel/antiX-19.2-4.19_kernel_x64-full.iso/download
If it is not, it could lead to a wild chase for a correct driver to get it properly to work. Maybe an older driver could work, but you wouldn't be able to test it without remastering your live system.

I doubt a compositor would solve the problem, but it may reduce the flicker frequency.

Does anyone else have any suggestions?

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

[Member cenga]

Helpful

Up

0

::

Thanks for the advice and direct download link for 19.2 with kernel 4.19. Relevantly, I tried with that iso, and repeating window list issue is gone, however, screen flickering/tearing continues. Do you think if I try to install amdgpu drivers from amd website, it might be okay?

[Forum Admin anticapitalista]

Helpful

Up

0

::

Try installing mesa-vulkan-drivers

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member cenga]

Helpful

Up

0

::

unfortunately it didn’t solve the flickering/tearing issue. Anymore advices? I think it is related with outdated HD3450 GPU, isnt it?

[Member Xecure]

Helpful

Up

0

::

Maybe installing a compositor can reduce a bit the flickers. (sudo apt install compton, abd then compton & in terminal to see if it improves temporarly.

There was a driver that worked. It seems a change in the kernel broke it.
https://gitlab.freedesktop.org/drm/amd/-/issues/1045
If we can figure out what to change exactly, you could compile a costumized kernel to make it work. It would require some time, and you would need to at least create a live uSB that lets you create persistance and remaster.

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

[Member Xecure]

Helpful

Up

0

::

Also, what happens when you add radeon.modeset=0 as a boot parameter? Can you load the graphical environment or does it stop at tty 1?

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

[Member cenga]

Helpful

Up

0

::

Xecure, thanks for your help, but compton & radeon.modeset=0 trials didnt work. I wrote radeon.modeset=0 at grub screen as attached, and I wonder if it is the right place to add boot parameters.

On the other hand, I hear the fan noise quite loud and often, although I check the temperatures which are around 35-40 C, which is normal and the fan shouldn’t be loud. I suspect from GPU temp, but can’t see it through sensors.

Is there any driver like mesa-vulkan-drivers, I can try each until I see flickers/tears gone?

Attachments:

1. 

   WhatsApp-Image-2020-05-28-at-22.44.56.jpeg
   

[Member Xecure]

Helpful

Up

0

::

Xecure wrote:

…
When restarting, in grub, hit ‘e’ key. Use the arrow keys to navigate to the line that sais
linux /boot/vmlinuz-.... quiet splasht=fa
or something similar. At the end of that line try different boot parameters. After writing the boot parameter, then hit F10 to boot and see if the boot parameter worked. This change is temporary and will only work for that session, so you don’t have to worry about reseting the boot parameters.

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

[Member Xecure]

Helpful

Up

0

::

cenga wrote:

On the other hand, I hear the fan noise quite loud and often, although I check the temperatures which are around 35-40 C, which is normal and the fan shouldn’t be loud.

This seems to be something you see often with linux. There may be some special package to return fan control to the BIOS, but I have little experience with this. Maybe someone who has to deal with this more often can explain.

cenga wrote:

Is there any driver like mesa-vulkan-drivers, I can try each until I see flickers/tears gone?

I think this will be difficult.

Drivers

Support for newer AMD graphics hardware is provided by the xserver-xorg-video-amdgpu package. This will officially cover any cards that are part of GCN 1.2 (“GCN 3rd generation”) or newer. This generation consists of most chips released after June 2015. GCN 1.0 and GCN 1.1 cards (Manufactured January 2012 to June 2015) are supported experimentally and require extra kernel parameters to be set, as documented in the experimental section.

Support for GCN 1.1 and older chips is also provided by the xserver-xorg-video-ati driver wrapper package, which depends on three hardware-specific driver packages:

xserver-xorg-video-mach64

xserver-xorg-video-r128

xserver-xorg-video-radeon

The ATI driver package will autodetect whether your hardware has a Radeon, Rage 128, or Mach64 and earlier chip and load the radeon, r128, or mach64 video driver as appropriate.

Since the AMDGPU driver overlaps with the older Radeon driver for supporting GCN 1.0/1.1 GPUs, either driver can be used. The older Radeon driver does not support Vulkan or the ACO compiler and is often slower, but it is much more stable and is used by default.

https://wiki.debian.org/AtiHowTo#Drivers

I think the exact change for the kernel that made it start flickering for some users is:
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-5.2&id=2e26ccb119bde03584be53406bbd22e711b0d6e6

This would need to be studied, revert this change and compile a customized kernel.
This change fixed problems for others, so it cannot be included in the main kernel, but can be used in a customized kernel.
I believe that it was not included in the 4.9 kernel, but you still got the horrible flickering with this kernel, so maybe it is a different change that can stop the flickering and not this particular one.

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

[Member cenga]

Helpful

Up

0

::

I have some good & bad news. First, I’ll start with the good one,

– The computer I was trying to use were a laptop totally unassembled. The set-up were based on a motherboard only connected to an external fullhd screen with external keyb and mouse. Today, I assembled all and connected each internal device for the laptop, my aim was to use internal screen since maybe the flicker could dissappear.
Well, at the end, the flickering dissappered for the internal screen, which has 1366 x 768px.
When I connect external screen via HDMI, both screens worked without any flickering.
When I use only the external screen, flickering comes back. It is really strange. Anyway, I am agree with internal screen, or int + ext screens combination. Because, I did understood the issue may be caused due to kernel blocking some driver and a custom kernel may require which is not possible for my knowledge.

– The bad news, the internal wireless device does not work.

Network:  Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet driver: r8169 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           <strong>Device-2: Intel WiFi Link 5100 driver: iwlwifi</strong> 
           IF: wlan0 state: down mac: <filter> 

When I use antix control center, Network Interfaces (Ceni) software) the error is rfkill:WLAN soft blocked. and there is no network found.
I could open the wifi through Wifi Connect (Connman), but when I try to use WPA Supplicant Configuration, I can’t choose the adapter

So far so good, for core2duo device, it came back to life, thanks to antix.
Any advices for the wifi will be appreciated.

and also I need to find a way to control the fans, it is continously working without any reason .)

Attachments:

1. 

   screenshot_1.jpg
   

[Forum Admin anticapitalista]

Helpful

Up

0

::

You might need an older kernel – there is a 4.4 version available.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member Xecure]

Helpful

Up

0

::

Good thing the monitor is working. One thing solved, one more left.

cenga wrote:

When I use antix control center, Network Interfaces (Ceni) software) the error is rfkill:WLAN soft blocked. and there is no network found.

You need to unlock the wifi first in connman.
Disconnect Ethernet and restart the computer. Try connman again.

If connman doesn’t help, uninstall it completely, reboot, and try ceni again.
There have been others with wifi issues, the most recent one:
https://www.antixforum.com/forums/topic/how-to-i-connect-to-my-homes-wifi/

Have a look in the forum to see if anything helps.

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

[Author]

Posts