View Issue Details

IDProjectCategoryView StatusLast Update
0007873Kali LinuxGeneral Bugpublic2022-09-23 16:45
Reporterhugoncalves Assigned Todaniruiz  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Version2022.3 
Summary0007873: After upgrading to 2022.3 Kali version, graphical issues (image blink)
Description

After upgrading to 2022.3 Kali version computer started to have graphical problems, image his always blink except when i start firefox browser (weird)

Steps To Reproduce

HW Specifications of my machine, is running Kali Linux

hugoncalves@kali:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 36 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GH
z
CPU family: 6
Model: 23
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
Stepping: 6
CPU(s) scaling MHz: 100%
CPU max MHz: 2534,0000
CPU min MHz: 800,0000
BogoMIPS: 5053,79
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mt
rr pge mca cmov pat pse36 clflush dts acpi mmx
fxsr sse sse2 ht tm pbe syscall nx lm constan
t_tsc arch_perfmon pebs bts rep_good nopl cpui
d aperfmperf pni dtes64 monitor ds_cpl vmx smx
est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm p
ti tpr_shadow vnmi flexpriority vpid dtherm
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 64 KiB (2 instances)
L1i: 64 KiB (2 instances)
L2: 6 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0,1
Vulnerabilities:
Itlb multihit: KVM: Mitigation: VMX disabled
L1tf: Mitigation; PTE Inversion; VMX EPT disabled
Mds: Vulnerable: Clear CPU buffers attempted, no mi
crocode; SMT disabled
Meltdown: Mitigation; PTI
Mmio stale data: Not affected
Spec store bypass: Vulnerable
Spectre v1: Mitigation; usercopy/swapgs barriers and __use
r pointer sanitization
Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB fi
lling
Srbds: Not affected
Tsx async abort: Not affected

Additional Information

After the last update/upgrade when i start the machine the image is always blinking
When i run the command htop everything looks good on processes nothing is out of normal situation
Probably the Hw is too old
Is there any possibilities to roll back this upgrade?
Hope anyone can answer me.

Thanks in advance

Activities

hugoncalves

hugoncalves

2022-08-17 13:48

reporter   ~0016589

hugoncalves@kali:~$ inxi -Fxz
System:
Kernel: 5.18.0-kali5-amd64 arch: x86_64 bits: 64 compiler: gcc v: 11.3.0
Desktop: Xfce v: 4.16.0 Distro: Kali GNU/Linux 2022.3 base: Debian testing
Machine:
Type: Laptop System: ASUSTeK product: G50V v: 1.0
serial: <superuser required>
Mobo: ASUSTeK model: G50V v: 1.0 serial: <superuser required>
BIOS: American Megatrends v: 207 date: 09/02/2008
Battery:
ID-1: BAT0 charge: 39.4 Wh (96.3%) condition: 40.9/51.3 Wh (79.7%)
volts: 12.3 min: 11.1 model: ASUSTEK M50--24 status: N/A
CPU:
Info: dual core model: Intel Core2 Duo T9400 bits: 64 type: MCP
arch: Penryn rev: 6 cache: L1: 128 KiB L2: 6 MiB
Speed (MHz): avg: 2532 high: 2534 min/max: 800/2534 cores: 1: 2534
2: 2530 bogomips: 10107
Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx
Graphics:
Device-1: NVIDIA G96M [GeForce 9700M GT] vendor: ASUSTeK driver: nouveau
v: kernel arch: Tesla bus-ID: 01:00.0
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: nouveau resolution: 1680x1050~60Hz
OpenGL: renderer: NV96 v: 3.3 Mesa 22.2.0-rc1 direct render: Yes
Audio:
Device-1: Intel 82801I HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0
Sound Server-1: ALSA v: k5.18.0-kali5-amd64 running: yes
Sound Server-2: PulseAudio v: 15.0 running: yes
Sound Server-3: PipeWire v: 0.3.56 running: yes
Network:
Device-1: Intel WiFi Link 5100 driver: iwlwifi v: kernel bus-ID: 03:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK U6V/U31J laptop driver: r8169 v: kernel port: e800
bus-ID: 06:00.0
IF: eth0 state: down mac: <filter>
Bluetooth:
Device-1: ASUSTek BT-253 Bluetooth Adapter type: USB driver: btusb v: 0.8
bus-ID: 4-1:2
Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: disabled
rfk-block: hardware: no software: no address: <filter>
Drives:
Local Storage: total: 447.14 GiB used: 18.78 GiB (4.2%)
ID-1: /dev/sda vendor: Fujitsu model: MHY2160BH size: 149.05 GiB
ID-2: /dev/sdb vendor: Seagate model: ST9320320AS size: 298.09 GiB
Partition:
ID-1: / size: 288.41 GiB used: 18.78 GiB (6.5%) fs: ext4 dev: /dev/sdb1
Swap:
ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) dev: /dev/sdb5
Sensors:
System Temperatures: cpu: 52.0 C mobo: N/A gpu: nouveau temp: 64.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 175 Uptime: 2h 32m Memory: 3.84 GiB used: 1.83 GiB (47.7%)
Init: systemd target: graphical (5) Compilers: gcc: 11.3.0 clang: 14.0.6-2
Packages: 2745 Shell: Bash v: 5.1.16 inxi: 3.3.20

hugoncalves

hugoncalves

2022-08-30 14:19

reporter   ~0016683

Any help please

steev

steev

2022-08-30 22:27

manager   ~0016685

The Kali team is very small, and does not have access to a large set of hardware. You will likely need to troubleshoot this and provide logs. I would recommend enabling ssh into the system, and then ssh in to it while it's showing the issues, and look at the dmesg output and the different log files in /var/log; Ones that may have some importance would be any in /var/log/lightdm, Xorg.X.log (where X is a number), and the kernel/syslog files.

Based on reading the info you have provided, it appears to be using nouveau for the gpu driver, have you tried the proprietary Nvidia cards already (documentation should be available at https://kali.org/docs )

hugoncalves

hugoncalves

2022-08-31 11:34

reporter   ~0016686

Thanks for your response
I found this article https://www.kali.org/docs/general-use/install-nvidia-drivers-on-kali-linux/
I have already correct the blinking problem, now i have to troubleshoot the resolution problem
Max resolution is 1280x768 it's very poor, it's my next step :)
Thanks for answering me :)

daniruiz

daniruiz

2022-09-23 16:45

manager   ~0016818

I'm closing this as it seems like the issue was solved with the nvidia drivers

Issue History

Date Modified Username Field Change
2022-08-17 13:39 hugoncalves New Issue
2022-08-17 13:48 hugoncalves Note Added: 0016589
2022-08-30 14:19 hugoncalves Note Added: 0016683
2022-08-30 22:27 steev Note Added: 0016685
2022-08-31 11:34 hugoncalves Note Added: 0016686
2022-09-23 16:45 daniruiz Note Added: 0016818
2022-09-23 16:45 daniruiz Assigned To => daniruiz
2022-09-23 16:45 daniruiz Status new => closed
2022-09-23 16:45 daniruiz Resolution open => no change required