weird screen behaviour

Forum Forums General Hardware weird screen behaviour

  • This topic has 10 replies, 4 voices, and was last updated Apr 20-8:28 am by roland.
Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #57568
    Member
    roland

    I post this problem in Hardware despite feeling the solution may lie with a software change. I have had these strange effects with other similar but not identical PCs and with 3 or 4 display units including old 15″ and 14″ glass monitors, a portable flat screen tv with elongated format, and a more regular shaped flat screen commercial monitor. All manual adjustments possible on the displays have been tried without success. The PCs that have offended are both MSI 64bit, but have performed quite normally under release 13 and 16, but have shown this problem under release 17 and 19. I have 2 other PCs that work normally with these same monitors leading me to think that the particular graphics chipset on these MSI mainboards is to blame.

    The install of 19.3 is completely up to date. The background and windows never correspond to the physical monitor boundaries, so parts are missing usually at the top of the display. When a window is located up there I cannot see the 3 minimise maximise and close buttons. Other parts of the display are splashed around the screen apparently randomly, and I can wipe them away using the mouse cursor arrow, but any mouse or application activity soon brings them back again. It´s no use my attempting to show you a screenshot because the screen buffer looks quite correct, although I attach such a shot to emphasise the point.

    AR&R does not offer the screen layouts that are possible with the current monitor, only 800×600 and 640×480, all monitors I have tried will work with much more. I searched the forum for clues and located Anticapitalista´s post about changing screen resolution but when I looked in /usr/local/bin I found no file called screen_resolution.sh so was unable to proceed with this suggestion.

    I can manage to work with it by wiping away the trash using the mouse arrow so I can see the workspaces and other items, but it is getting on my nerves.

    System: Host: antix1 Kernel: 4.9.235-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-4.9.235-antix.1-amd64-smp
    root=UUID=4cc8d1a2-4449-48df-a00a-bc326eed2407 ro vga=0x0317 quiet
    Desktop: IceWM 2.3.1 dm: SLiM 1.3.6
    Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020
    base: Debian GNU/Linux 10 (buster)
    Machine: Type: Desktop Mobo: MICRO-STAR model: MS-7253 v: 1.0 serial: <filter> BIOS: Phoenix
    v: 1.6 date: 08/16/2007
    Memory: RAM: total: 1.83 GiB used: 628.7 MiB (33.5%)
    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: AMD Athlon 64 X2 6000+ bits: 64 type: MCP arch: K8 rev.F+
    family: F (15) model-id: 43 (67) stepping: 3 microcode: N/A L2 cache: 2048 KiB
    bogomips: 8000
    Speed: 2000 MHz min/max: 1000/3000 MHz Core speeds (MHz): 1: 2000 2: 2000
    Flags: 3dnow 3dnowext 3dnowprefetch apic clflush cmov cmp_legacy cr8_legacy cx16 cx8 de
    extapic extd_apicid fpu fxsr fxsr_opt ht lahf_lm lm mca mce mmx mmxext msr mtrr nopl nx
    pae pat pge pni pse pse36 rdtscp rep_good sep sse sse2 svm syscall tsc vme vmmcall
    Vulnerabilities: Type: itlb_multihit status: Not affected
    Type: l1tf status: Not affected
    Type: mds status: Not affected
    Type: meltdown status: Not affected
    Type: spec_store_bypass status: Not affected
    Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
    Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
    Type: srbds status: Not affected
    Type: tsx_async_abort status: Not affected
    Graphics: Device-1: VIA K8M890CE/K8N890CE [Chrome 9] vendor: Micro-Star MSI driver: N/A
    bus ID: 01:00.0 chip ID: 1106:3230
    Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 800×600~N/A
    OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1
    direct render: Yes
    Audio: Device-1: VIA VT8237A/VT8251 HDA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    bus ID: 80:01.0 chip ID: 1106:3288
    Sound Server: ALSA v: k4.9.235-antix.1-amd64-smp
    Network: Device-1: VIA VT6102/VT6103 [Rhine-II] vendor: Micro-Star MSI driver: via-rhine v: N/A
    port: f200 bus ID: 00:12.0 chip ID: 1106:3065
    IF: eth0 state: down mac: <filter>
    Device-2: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc bus ID: 1-3:4
    chip ID: 0cf3:9271 serial: <filter>
    IF: wlan0 state: up mac: <filter>
    IP v4: <filter> type: dynamic scope: global broadcast: <filter>
    IP v6: <filter> scope: link
    WAN IP: <filter>
    Drives: Local Storage: total: 149.05 GiB used: 5.03 GiB (3.4%)
    ID-1: /dev/sda vendor: Hitachi model: HCP725016GLAT80 size: 149.05 GiB block size:
    physical: 512 B logical: 512 B speed: <unknown> rotation: 7200 rpm serial: <filter>
    rev: A4CA scheme: MBR
    Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-RAM GSA-H22N rev: 1.00
    dev-links: cdrom,cdrw,dvd,dvdrw
    Features: speed: 48 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
    state: running
    RAID: Message: No RAID data was found.
    Partition: ID-1: / raw size: 29.59 GiB size: 29.00 GiB (98.01%) used: 5.03 GiB (17.3%) fs: ext4
    dev: /dev/sda5 label: rootantiX19 uuid: 4cc8d1a2-4449-48df-a00a-bc326eed2407
    ID-2: swap-1 size: 4.88 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60)
    cache pressure: 50 (default 100) dev: /dev/sda6 label: swap
    uuid: 83528a0c-ddf6-4c12-8eb1-2e27358725a5
    Unmounted: ID-1: /dev/sda1 size: 1 KiB fs: <root required> label: N/A uuid: N/A
    ID-2: /dev/sda7 size: 114.57 GiB fs: ext4 label: antiX2
    uuid: 281f3ca7-88f9-44d7-8c99-cdba87c5a42d
    USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0 speed: 480 Mb/s
    chip ID: 1d6b:0002
    Device-1: 1-3:4 info: Qualcomm Atheros AR9271 802.11n type: Network driver: ath9k_htc
    interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 0cf3:9271 serial: <filter>
    Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
    chip ID: 1d6b:0001
    Device-2: 2-1:2 info: Weltrend type: Keyboard,HID driver: hid-generic,usbhid
    interfaces: 2 rev: 1.1 speed: 1.5 Mb/s chip ID: 040b:2000
    Device-3: 2-2:3 info: Pixart Imaging Optical Mouse type: Mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s chip ID: 093a:2510
    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
    Device-4: 4-2:2 info: Alcor Micro Flash Card Reader/Writer type: Mass Storage
    driver: usb-storage interfaces: 1 rev: 2.0 speed: 12 Mb/s chip ID: 058f:6362
    serial: <filter>
    Hub: 5-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: 38.0 C mobo: N/A
    Fan Speeds (RPM): N/A
    Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
    1: deb https: //anorien.csc.warwick.ac.uk/mxlinux/packages/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.pt.debian.org/debian/ buster-updates main contrib non-free
    Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http: //ftp.pt.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: 34.6% command: chromium pid: 5411 mem: 160.1 MiB (8.5%)
    2: cpu: 28.3% command: xorg pid: 2889 mem: 65.7 MiB (3.5%)
    3: cpu: 6.9% command: chromium pid: 5349 mem: 134.9 MiB (7.1%)
    4: cpu: 2.8% command: gtkdialog pid: 9376 mem: 28.9 MiB (1.5%)
    5: cpu: 2.3% command: chromium pid: 4753 mem: 237.5 MiB (12.6%)
    Memory top: 5
    1: mem: 237.5 MiB (12.6%) command: chromium pid: 4753 cpu: 2.3%
    2: mem: 188.0 MiB (10.0%) command: chromium pid: 4805 cpu: 0.2%
    3: mem: 160.1 MiB (8.5%) command: chromium pid: 5411 cpu: 34.6%
    4: mem: 134.9 MiB (7.1%) command: chromium pid: 5349 cpu: 6.9%
    5: mem: 105.0 MiB (5.5%) command: chromium pid: 4777 cpu: 0.0%
    Info: Processes: 188 Uptime: 33m 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

    Attachments:
    #57570
    Forum Admin
    anticapitalista
    Helpful
    Up
    0
    :D

    What if you remove vga=0x0317 from your grub entry?

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

    antiX with runit - leaner and meaner.

    #57615
    Member
    roland
    Helpful
    Up
    0
    :D

    I found 4 files containing the text vga=0x0317 but wishing to proceed with caution I respond with the file list, and the next question – should I comment out the entire line where it occurs or simply remove the text from within the line?

    /etc/default/grub
    /etc/default/grub.ucf-dist
    /boot/grub/grub.cfg
    /proc/cmdline

    #57617
    Forum Admin
    anticapitalista
    Helpful
    Up
    0
    :D

    /etc/default/grub

    Simply remove the text from within the line

    Then, before rebooting

    sudo update-grub

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

    antiX with runit - leaner and meaner.

    #57693
    Member
    roland
    Helpful
    Up
    0
    :D

    I edited the text in /etc/default/grub by inserting a hash in col 1, as simply removing the text would have left the line looking somehow incomplete.

    This has cured the strange display effects and the screen now behaves normally at 800×600.

    However AR&R only offers 2 layouts, 800×600 and 640×480, but on another PC with exactly the same install there are at least 26 variants offered from 1024×768 downwards, on an old 14înch glass monitor.

    Have you any suggestions as to how I can get it to offer more layout options?

    #57696
    Forum Admin
    anticapitalista
    Helpful
    Up
    0
    :D

    Do you have an /etc/X11/xorg.conf file? If you have, rename it to something like xorg.conf.bak
    Reboot.
    Also, can you post the contents of /boot/grub/grub.cfg

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

    antiX with runit - leaner and meaner.

    #57720
    Member
    roland
    Helpful
    Up
    0
    :D

    Renaming /etc/X11/xorg.conf followed by a cold boot brought the display up to 1024×768 as default, and AR&R lists 1024×768, 800×600, 640×480 and 720×400 available in that order. There was a brief (1-2 sec) corrupt screen before the wallpaper and toolbar appeared, all aluminium rubbish.

    The display now appears as it should except the boot process text messages now appear like VGA messages rather than SVGA and there are very many more of them, racking over the terminal somewhat faster than I can read but they appear to be organised informative messages and definitely not error diagnostics I would guess.

    I attach the contents of /etc/X11/xorg.conf and /boot/grub/grub.cfg

    Thanks for your competent efforts!

    #57775
    Member
    Xecure
    Helpful
    Up
    0
    :D

    Graphics: Device-1: VIA K8M890CE/K8N890CE [Chrome 9] vendor: Micro-Star MSI driver: N/A
    bus ID: 01:00.0 chip ID: 1106:3230
    Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 800×600~N/A
    OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1
    direct render: Yes

    After removing the xorg.conf file, what does
    inxi -Gxxx
    show?

    VIA graphics has had problems with the current xorg version, as reported here:
    https://www.antixforum.com/forums/topic/how-to-use-antix-on-computers-with-a-motherboard-with-sis-or-via-chipset/

    It has been observed that an older xorg version seems to have better support for these VIA graphic chipsets, providing better range of resolutions.

    #57846
    Member
    roland
    Helpful
    Up
    0
    :D

    roland@antix1:~/Desktop
    $ inxi -Gxxx
    Graphics:
    Device-1: VIA K8M890CE/K8N890CE [Chrome 9] vendor: Micro-Star MSI
    driver: N/A bus ID: 01:00.0 chip ID: 1106:3230
    Display: x11 server: X.Org 1.20.4 driver: openchrome
    unloaded: fbdev,modesetting,vesa resolution: 1024×768~85Hz
    OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
    compat-v: 3.1 direct render: Yes
    roland@antix1:~/Desktop
    $

    I looked through the correspondence from the Brazilian member but it all seemed aimed at 32-bit installations, and I cannot claim to have followed much of it anyway, neither did I wish to get involved in compiling special kernels. Instead I installed kernel 5.10.27 which is the latest the software updater offers on this PC and I am finding things very satisfactory although it´s early days.

    System: Host: antix1 Kernel: 5.10.27-antix.1-amd64-smp x86_64 bits: 64 compiler: N/A
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.27-antix.1-amd64-smp
    root=UUID=4cc8d1a2-4449-48df-a00a-bc326eed2407 ro
    Desktop: IceWM 2.3.2 dm: SLiM 1.3.6
    Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020
    base: Debian GNU/Linux 10 (buster) ç

    I am pleased to remark that this very limited little PC certainly gets on with the job, the latest antiX with its minimalised components runs quite a bit faster than I would have expected from such a puny little assembly of hardware. Additionally the sound was working as it should, straight out of the box, not always the case.

    Audio: Device-1: VIA VT8237A/VT8251 HDA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    bus ID: 80:01.0 chip ID: 1106:3288
    Sound Server: ALSA v: k5.10.27-antix.1-amd64-smp

    #57847
    Member
    marcelocripe
    Helpful
    Up
    0
    :D

    Hi Roland,

    I am following your topic with the aim of learning.

    If I was able to correctly understand the translation from English to Portuguese (pt-BR), do you have a VIA K8M890CE/K8N890CE video device operating well with the kernel: 5.10.27?
    Are there no flaws in the menus, faulty construction of images or slowness of the antiX graphical interface?
    What was the procedure you did to install 64-bit antiX on your hard drive and still have the kernel: 5.10.27?

    Excuse me for asking you so many questions, this information is very useful for me, since I installed it in a motherboard P4M900-M7 FE rev .: 7.0 with video chip Via TV8237A and with 64-bit processor at ISO “antiX-19 -legacy-bet2_386-base.iso”, which Xecure kindly built, was the only one that antiX worked well on this computer. I tested before ISO Legacy, antiX 64-bit with kernel 4.19.180 (official version), the other ISO built by Xecure “pseudo-antiX-19.3_x64.iso” with kernel 5.8.16, but there were menu failures, construction defective images or slowness of the antiX graphical interface.

    There are many video devices from the VIA and SIS brands in Brazil, in the case of Via it seems to have one in each home and continue to be sold by “national” resellers of products built in China, according to the specification requested by these resellers.

    I hope that you will be able to correctly understand my texts translated by the internet translator into the English language.

    I thank you for sharing your experience with antiX.

    marcelocripe
    (Original text in Brazilian Portuguese)

    ———-

    Olá Roland,

    Eu estou acompanhando o seu tópico com o objetivo de aprender.

    Se eu consegui compreender corretamente a tradução do idioma inglês para o português (pt-BR), você está com um dispositivo de vídeo VIA K8M890CE/K8N890CE operando bem com o kernel: 5.10.27?
    Não há falhas nos menus, construção defeituosa das imagens ou lentidão da interface gráfica do antiX?
    Qual foi o procedimento que você realizou para instalar o antiX de 64 bits no disco rígido e ainda ter o kernel: 5.10.27?

    Desculpe-me por te fazer tantas perguntas, esta informação é muito útil para mim, haja vista que eu instalei em uma placa-mãe P4M900-M7 FE rev.: 7.0 com chip de vídeo Via TV8237A e com processador de 64 bits a ISO “antiX-19-legacy-bet2_386-base.iso”, que o Xecure construiu gentilmente, foi a única que funcionou bem o antiX neste computador. Eu testei antes da ISO Legacy, o antiX 64 bits com kernel 4.19.180 (versão oficial), a outra ISO construída pelo Xecure “pseudo-antiX-19.3_x64.iso” com kernel 5.8.16, mas ocorreram falhas nos menus, construção defeituosa das imagens ou lentidão da interface gráfica do antiX.

    Os dispositivos de vídeo das marca VIA e SIS existem muitos no Brasil, no caso dos Via parece ter um em cada casa e continuam sendo comercializados por revendedores “nacionais” de produtos construídos da China, conforme a especificação solicitada por estes revendedores.

    Eu espero que você consiga compreender corretamente os meus textos traduzidos pelo tradutor da internet para o idioma inglês.

    Eu agradeço por compartilhar a sua experiência com o antiX.

    marcelocripe
    (Texto original em idioma Português do Brasil)

    #57864
    Member
    roland
    Helpful
    Up
    0
    :D

    Hi Marcelo,

    Yes I have the VIA graphics chipset on this mainboard working very well now after going through the suggestions made my Anticapitalista to present a satisfactory range of screen resolutions, which you can see in the above exchanges. I have been using antiX on this little commercial PC since the days of Luddite (13.1) with every satisfaction, this install of 19.3 is the first install that has given graphics troubles which have been simply the inability to offer and auto-select the most suitable resolution(s). On the credit side I an finding 19.3 to run very fast indeed making the PC more attractive to use than ever before.

    I chose kernel 5.10.27 because that is the highest numbered on offer in the software installer menu but there was no intelligence behind that choice in fact I may try another back in the 4.n range because I am experiencing ´freezing´ on a particular workspace after saving a file from chromium web browser to a folder, a problem I have experienced before, as if the focus has been lost but the other workspaces are still usable. Lack of technical knowledge compels me to experiment with such problems, with occasional success!

Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.