Bug 17081 - please add 'Option "AccelMethod" "uxa"' by default for now for "artifacts" intel cards
Summary: please add 'Option "AccelMethod" "uxa"' by default for now for "artifacts" in...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords:
Depends on:
Blocks: 17989
  Show dependency treegraph
 
Reported: 2015-11-03 22:26 CET by w unruh
Modified: 2022-06-26 16:45 CEST (History)
3 users (show)

See Also:
Source RPM: drakx-kbd-mouse-x11
CVE:
Status comment:


Attachments

Description w unruh 2015-11-03 22:26:41 CET
Description of problem:
I have just installed kenrel 4.1.8 from updates in MGA5, and the screen is producing artifacts. In particular short pairs of lines on the screen (maybe about 30 pixels long, and in pairs separated by about 5 pixels.) withing the lines the pixels seem to be displaced from where they should be. (On one boot, there were a huge bunch of of them in the center of the screen, so the mageia word on the bootup had two images, displaced about 1/4 of a character width from each other) Usually they are short. and they occur on top of a Konsole window-- the location is usually toward the edge-- left or right-- of the window. If a word is typed at the location that word's pixels get fragmented. This is extremely annoying. 

When I installed kenel 3.19.8, the problem seems to have disappeared, so it definitely seems to have something to do with the kernel graphics driver.


Version-Release number of selected component (if applicable): 
The system was updated on Nov 1 (urpmi --auto-select --update) 
But it seems to be the kernel 4.1.8 that is causing the problem.

How reproducible: I rebooted 5 times with the 4.1.8 kernel, and it occured each time. One pair of lines obscured a couple of desktop icons on the left hand side. 
And the others occured when I opened a Konsole. The location of the Konsole line pairs depended on how large I made the window for the konsole-- hopping around discontinuously while I resized the window. 

 


Steps to Reproduce: Boot 4.1.8 kernel. Sometimes the spash screen was corrupted. Sometimes it waited until I logged on and booted into X from the kdm screen and then my home desktop was corrupted as above consistantly.
 


Output of lspci

00:00.0 Host bridge: Intel Corporation 82G35 Express DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 02)
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA Controller [IDE mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801HR/HO/HH (ICH8R/DO/DH) 2 port SATA Controller [IDE mode] (rev 02)
03:00.0 IDE interface: JMicron Technology Corp. JMB368 IDE controller
04:03.0 Communication controller: MosChip Semiconductor Technology Ltd. PCI 9835 Multi-I/O Controller (rev 01)
04:05.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 70)


Video monitor Acer H236HL -- driven with VGA input. 


Reproducible: 

Steps to Reproduce:
Comment 1 w unruh 2015-11-04 19:08:18 CET
This seems to be fixed by
bugs.mageia.org/show_bug.cgi?id=16655#c75
Added 
Option      "AccelMethod"  "uxa"
to /etc/X11/xorg.conf in the 
Section "Device" 
and on reboot, the artifacts in kernel 4.1.8 are gone. Lets hope they do not reappear.

Whatever sets up xorg.conf needs to have some logic to put in this line automatically since many users will have no idea what is going on.
Samuel Verschelde 2015-11-16 11:48:08 CET

CC: (none) => thierry.vignaud, tmb

Comment 2 Samuel Verschelde 2015-12-07 13:57:22 CET
It's either a kernel or XFdrake issue, I don't know which one is responsible. Assigning to Thierry who can reassign if needed.

Assignee: bugsquad => thierry.vignaud
Source RPM: kernel 4.1.8 => drakxtools

Comment 3 Marja Van Waes 2016-03-14 08:44:11 CET
Got the artifacts for the first time yesterday on this system with old intel 810 and later card
https://wiki.mageia.org/en/User:Marja/QA/Hardware#Lenovo_ThinkPad_SL510
after having updated X11-server the day before.

Will *all* intel cards work well with 

     Option "AccelMethod" "uxa"

added to /etc/X11/xorg.conf ?

If so, can that please be added for all those cards?

Or, if it is known which ranges of intel cards are better off with that option, add it for those ranges only?

Whiteboard: (none) => MGA5TOO
Version: 5 => Cauldron
Summary: kernel 4.1.8 produces screen artifacts on Intel graphics. => please add 'Option "AccelMethod" "uxa"' by default for intel cards
CC: (none) => marja11
Hardware: i586 => All

Marja Van Waes 2016-03-14 08:45:15 CET

Blocks: (none) => 17989

Comment 4 Thomas Backlund 2016-03-14 08:47:38 CET
We cant add it blindly for all intel, as "sna" is the one getting speed improvements fonr newer intel hw... and I think upstream Intel want to obsolete "uxa" at some point...
Comment 5 Marja Van Waes 2016-03-14 08:57:50 CET
(In reply to Thomas Backlund from comment #4)
> We cant add it blindly for all intel, as "sna" is the one getting speed
> improvements fonr newer intel hw... and I think upstream Intel want to
> obsolete "uxa" at some point...

adjusting summary.... or is this stupid to ask at all, because if this isn't addressed differently, we'll have a problem when "uxa" is obsoleted.

(Btw, was it a coincidence that I only got the problem here after latest X11 server?)

Summary: please add 'Option "AccelMethod" "uxa"' by default for intel cards => please add 'Option "AccelMethod" "uxa"' by default for now for "artifacts" intel cards

Comment 6 Marja Van Waes 2016-03-14 09:02:02 CET
(In reply to Marja van Waes from comment #5)
> (In reply to Thomas Backlund from comment #4)
> > We cant add it blindly for all intel, as "sna" is the one getting speed
> > improvements fonr newer intel hw... and I think upstream Intel want to
> > obsolete "uxa" at some point...
> 
> adjusting summary.... or is this stupid to ask at all, because if this isn't
> addressed differently, we'll have a problem when "uxa" is obsoleted.
> 

Forget that, I didn't see it was about Intel obsoleting uxa ... that'll only be valid for Cards that don't yet exist
Comment 7 Thierry Vignaud 2016-07-12 02:13:25 CEST
Wrong package

Source RPM: drakxtools => drakx-kbd-mouse-x11

Comment 8 sturmvogel 2022-06-26 16:45:19 CEST
As this bug was filed against MGA5 which is EOL since 2015...and the affected hardware is now between 23 years (Marja's Intel 810) and 16 years (w unruh's 82G35 Express) old...

..and this bug got no update for 6 years...

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.