Unable to start X when booting with acpi=off or modeset=0
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unable to start X when booting with acpi=off or modeset=0
Hello
Yesterday I thought I had solved my "Blank screen boot"-issue when I successfully got
to the terminal login screen without the screen going black by booting with
Code:
Linux acpi=off
I spoke too soon. I found out shortly after that when trying to "startx" with acpi off gave me these errors:
Code:
WARNING: Error inserting i2c_algo_bit ("filepath"): No such device
WARNING: Error inserting intel_agp ("filepath"): No such device
WARNING: Error inserting drm ("filepath"): No such device
WARNING: Error inserting drm_kms_helper ("filepath"): No such device
FATAL: Error inserting i915 ("filepath") No such device
(EE) No devices detected.
Fatal server error:
no screens found
Then I read somewhere that booting with "i915.modeset=0" might work. So I removed acpi=off from lilo and added this,
and sure enough, I got to terminal login, but I get the same errors with "startx".
I must make it clear that I can successfully perform startx when I boot without "acpi=off" or "i915.modeset=0",
I am unable to see the screen but I can hear the KDE fanfare, etc.
Any kind soul willing to help me track down the culprit?
I have ran xorgsetup multiple times with different settings, but no dice. Any clue to what I
might have to do with my xorg.conf manually, seeing the automatic setup is of little success?
It seems that for your Xorg video-drivers acpi-dependent drivers need to be loaded .
Instead of "acpi=off" you could use "acpi_enforce_resources=lax" to prevent the strict execution of acpi .
I am actually using this parameter on my platform to get the temperature module registerd (it87) .
Without acpi-support my PC does not poweroff the PSU .
There is a bunch of acpi parameters for the boot line , look into the kernel source /Documentation/kernel-parameters.txt like "acpi_irq_[no]balance" or "pci=noacpi" .
Last edited by Karl Godt; 07-01-2011 at 09:00 AM.
Reason: wrote acpi_enforc_resources=lax
If I remove "acpi=off" and i915.modeset=0 it turns into a quite different issue, which I described in another thread.
Firstly, I have tried setting vga to normal, ask and several other settings in lilo.conf without success.
What happens if I omit the above from lilo.conf is that the system boots with a seemingly blank screen,
I am able to login and startx, but here is the detail that really confuses me:
The screen is not really black/blank. If I take a lamp and put it close up to the screen, I can actually see
text on the screen, if I look closely enough. The text is not "frozen" on the screen, when I input commands
and execute them, I see the text flowing upwards as usual.
The conclusion I make from this is that the monitor backlight/lamps turns off when booting with acpi enabled.
More specifically, the light goes off a couple of seconds after the LILO screen. If there is any more info
I can provide to make things clearer, let me know!
Thanks
UPDATE: My Linux system is on a laptop, and I thought it might be an idea to try with a different monitor.
So I connected on a separate monitor and it works perfectly. The backlight-issue is somehow specifically
related to the laptop then, but I've never heard of this problem before..
acpi_backlight= [HW,ACPI]
acpi_backlight=vendor
acpi_backlight=video
If set to vendor, prefer vendor specific driver
(e.g. thinkpad_acpi, sony_acpi, etc.) instead
of the ACPI video.ko driver.
No experience with that parameter .
This might be also put [with the right syntax] into
/etc/[modprobe.d]/modprobe.conf||acpi.conf||video.conf||distro.conf||driver.conf||etc
And this is f.ex.from /linux-2.6.33.7/Documentation/laptops/sony-laptop.txt :
Code:
Backlight control:
------------------
If your laptop model supports it, you will find sysfs files in the
/sys/class/backlight/sony/
directory. You will be able to query and set the current screen
brightness:
brightness get/set screen brightness (an integer
between 0 and 7)
actual_brightness reading from this file will query the HW
to get real brightness value
max_brightness the maximum brightness value
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.