You are not logged in.
Pages: 1
Topic closed
I have researched this issue and tried every method I've read about. I followed the steps in the wik about adding i915 to the modules list and recompiling. I've tried including intel_agp to the modules as well.
I followed the beginner wiki and installed the video vesa drivers as well as the video Intel drivers.
I'm at a loss and would appreciate any help. If I start kms early the screen blanks out early. If I don't start it early it blanks out later. If I use nomodeset I can boot up and the display works but I'm unable to start x.
The backlight works and is on but the display doesn't show anything.
Offline
Did you remember to do both steps when disabling modesetting?: https://wiki.archlinux.org/index.php/Ke … odesetting
Offline
Did you remember to do both steps when disabling modesetting?: https://wiki.archlinux.org/index.php/Ke … odesetting
Yes I did the remake command after I put in the i915 into the modules. However, I still an unable to see anything unless I use nomodeset. And when I use nomodeset I can't use x.
Offline
You don't need to install both vesa and intel. The beginners guide says to install vesa only if you can't find another suitable driver that loads. I would uninstall it.
Also, did you try the second option listed in the wiki for the blank screen option of appending kernel parameter "video=SVIDEO-1:d"
I laugh, yet the joke is on me
Offline
I tried that after I put i915 in the modules list and I just tried it without the i915 in the modulea
Offline
What is your equipment?
I laugh, yet the joke is on me
Offline
When nomodeset stops you from starting X, what does your Xorg.0.log say?
6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.
Offline
Just disable the outputs you are not using, and if you have EDID issues, then you can try explicitly setting the mode you want for the output you are using.
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
Stebalien wrote:Did you remember to do both steps when disabling modesetting?: https://wiki.archlinux.org/index.php/Ke … odesetting
Yes I did the remake command after I put in the i915 into the modules. However, I still an unable to see anything unless I use nomodeset. And when I use nomodeset I can't use x.
My point was, did you install xf86-video-modesetting.
Offline
My point was, did you install xf86-video-modesetting.
Why would he do that? xf86-video-modesetting is meant to be used for chipsets that have a kernel module, but no userspace driver. Intel isn't one of those, Intel has a userspace driver - xf86-video-intel.
Well, there's a possibility deadheartsbeat doesn't actually have Intel graphics, because he has a CedarView machine.
Offline
Stebalien wrote:My point was, did you install xf86-video-modesetting.
Why would he do that? xf86-video-modesetting is meant to be used for chipsets that have a kernel module, but no userspace driver. Intel isn't one of those, Intel has a userspace driver - xf86-video-intel.
Yes, but it doesn't support UMS (user mode setting) so he can't use it with nomodeset. I was under the impression that xf86-video-modesetting is a generic Xorg driver that supports UMS but I may be wrong about that (if I am, the wiki should be updated to make this clear).
Offline
I was under the impression that xf86-video-modesetting is a generic Xorg driver that supports UMS but I may be wrong about that
You are indeed. xf86-video-modesetting works *only* with a KMS driver. That's it's point - to provide X on top of KMS. It has no acceleration whatsoever - no 2d accel, no 3d accel, no Xv.
I'd say that sentence about it should be removed from the wiki page.
Offline
For anyone else like me who stumbled into this thread, I wanted to post a solution. I'm using a Toshiba Saellite P70 (Intel Haswell i7) with the HD 4600 gpu. I fixed the kms blank black screen issue with a kernel paramter:
acpi_backlight=vendor
It's already noted in the troubleshooting section on the wiki. Though it took me awhile to try it, since it wasn't described as a way to resolve a blank screen.
Last edited by brianbaligad (2013-08-12 05:26:34)
Offline
@brianbaligad, this thread is just a bit over six months old. Though that is not that old for most forums, in this case the issue being discussed was about a kernel that has not been in our repos for probably ~5.75 months. This is what is referred to as necrobumping.
Also, acpi_backlight=vendor is probably not the most ideal solution, even if this were a current thread. As the command line argument suggests, it is dependent on what the actual hardware is in use. For example the thinkpad_acpi module throws a large multi-line warning that its use is deprecated, it is likely to run into issues, and to report any problems (presumably not caused by this kernel command line addition) to the relevant mailing list.
So I really rather think that your issue was a different one altogether.
Offline
Offline
Pages: 1
Topic closed