You are not logged in.
Pages: 1
I recently installed Arch Linux, when I booted from the usb device the text was pixelated.
I continued installation thinking maybe it's just the installation media, but when I booted for the first time the same problem persisted.
I installed X11, Intel driver and Deepin when started deepin everything was pixelated and it was laggy as hell, it even crashed.(Nano also crashed)
Here is some screenshots:
https://goo.gl/photos/45efaXMoqNYHKr986
https://goo.gl/photos/qorsnrT6DtTFWpJd9
https://goo.gl/photos/yb3ixVeYscRJfweq9
Here is what I tried to resolve this issue:
-I changed the resolution with no luck whatsoever.
-I uninstalled Intel driver.
- I reinstalled it and fell back to DRI 2 and uxa.
Nothing seems to fix the problem.
Note: I had Arch installed and working properly 10 months ago.
Note: The only screen that appears normal is the very first screen when booting from the disk (that loads the modules I think. The one that has green text, but the second screen that continues its work and has green text also is pixelated)
Note: This happened in the installation media, maybe it's a kernel problem with my video driver?
Believe me it's even worse the the screenshots.
Offline
What video driver(s)?
Not an Installation issue, moving to NC...
Offline
Intel HD 4600
I'm on Haswell
I tried disabling the acceleration and DRI, but none worked.
I set FreeTear True, but it didn't work.
Offline
You could try with the kernel's native modesetting. The Intel page on the wiki has the details.
Offline
I don't know what exactly you mean, but I just tried early KMS start and it didn't work.
Offline
See the note here: https://wiki.archlinux.org/index.php/In … stallation
Offline
Those are photos, no screenshots.
Does the problem manifest on actual screenshots as well?
Offline
@jasonwryan sorry for the late response tried that and it didn't work either.
@seth https://goo.gl/photos/7SoMsEkZ1Bsj1EFHA here is a link of a real screenshot, I viewed it on my phone it was displayed correctly, what does this mean?
Offline
The problem is somewhere between the scanout buffer and the display - either eg. an overdriven pixelclock (kernel bug or misconfiguration) or a hardware defect/interference.
Try
- booting some other live system
- booting in VGA mode (only applies to the linux console, not X11)
and see whether you get the same problem.
Also check dmesg for suspicious warnings/errors and at least post the output of "lspci -v" to specify your hardware.
Is this an integrated output or an external one?
Offline
@seth I booted to Solus which uses the kernel 4.12.7 and I found the same issue.
I booted to Ubuntu 16.04 which uses the kernel 4.4 and it worked perfectly, in fact I'm leaving this reply using Ubuntu.
I already have Windows installed and it works perfectly.
I'll try to fallback to an older kernel in Arch and see what happens.
The output of "lspci -v":
https://docs.google.com/document/d/e/2P … nOI06U/pub
Offline
Pages: 1