Whenever I boot into my installed Ubuntu system, the entire system restarts. I am able to get to the GRUB menu and select the Ubuntu OS, however while booting Ubuntu, my entire PC restarts. The only message I get to see before the entire system restarts is this: Base address is 0 assuming no IPMI interace. Sometimes my entire screen also has red stripes and becomes distorted You can view the image here: The weird thing is, when I pass in the nomodeset paramater this issue does not occur, however my entire screen becomes stretched and weird. I try changing the screen resolution however I have no other option except 800x600 I do not believe the issue is with my graphics card since windows boots up fine and the screen resolution is also fine, however it also restarts a couple of times before booting up. Currently, I reinstalled Ubuntu, erasing everything on my Hard disk hoping that would fix the issue, however the issue still arises. PC Specifications: HP Compaq 8200 Elite SFF Intel core i5-2500k CPU Intel HD 3000 graphics card

I'm trying to prevent nvidia driver from modesetting as an integrated GPU (i915) is doing it. I'm only using this nvidia card on linux for rendering (PRIME), no modesetting. I've tried blacklisting it in modprobe.d and via kernel options, but it still gets loaded. Nvidia driver doesn't seem to have any configuration option to tell it to stop trying to modeset the displays when they get connected. Is there any other way to force a module to not be loaded? I've tried to just remove the /usr/lib/modules/6.5.9-arch2-1/extramodules/nvidia-modeset.ko.xz module file, but then dracut-rebuild won't work (refuses to produce initrd).

I'm trying to install Linux Mint on my 2010 21.5" iMac. I managed to install it after booting from the usb drive with the nomodeset option, but I haven't been able to boot from the actual install so far. The typical recommendation I found from googling is: on the boot selector screen (I'm using rEFInd) hold Shift and select grub options, then press e to edit the boot options and add nomodeset after where it says quiet splash. However, this does not work for me - I still get a black screen when it tries to boot up.

So, I've searched around for answers that can help me, and I don't think I've found a page that has a solution that works for me. I really hope I'm not asking a duplicate, somehow, and just missed it. (Note about edit: off-by-one error fixed in Debian versions.) PARTIAL-SOLVE EDIT: Turns out I'm a little bit stupid. I forgot to un-blacklist the nouveau driver (I had created /etc/modprobe.d/blacklist-nouevau.conf when figuring out the nvidia driver install long, long ago), and just commented out the line that said blacklist nouveau and options nouveau modeset=0. I now have a much more reasonably-scaled GUI in Gnome, so that much is behaving as expected. It doesn't get me the use of my graphics card on Debian, but maybe that's an upcoming fix. Thanks for those who responded; if anyone has any idea how to solve the graphics driver part, I'm still looking to solve that portion, but at least I can do (some) work, again! The TL;DR version of this is that I upgraded to Debian 13 (trixie) from Debian 12 (bookworm), and now no longer have a GNOME GUI without adding nomodeset to grub, which makes it very undesirable to do my day-to-day work, and I'm trying to find solutions. I'm working on older hardware (12-year-old CPU and GPU), and am having trouble either using the nouveau driver to solve the problem and getting rid of the nvidia-legacy-390xx-driver or getting the proprietary driver working again. Here is the output of neofetch that gives my kernel, hardware specs, etc:

OS: Debian GNU/Linux trixie/sid x86_64 
Kernel: 6.3.0-1-amd64 
Uptime: 27 mins 
Packages: 4359 (dpkg) 
Shell: bash 5.2.15 
Resolution: 640x480 
DE: GNOME 
WM: Mutter 
WM Theme: Adwaita 
Theme: Adwaita-dark [GTK2/3] 
Icons: gnome [GTK2/3] 
Terminal: gnome-terminal 
CPU: Intel i5-2500K (4) @ 3.700GHz 
GPU: NVIDIA GeForce GTX 560 Ti 
GPU: Intel 2nd Generation Core Process 
Memory: 3484MiB / 15903MiB

I also have full-disk encryption enabled through LUKS, and am dual-booting alongside Windows 7. (I don't really use Windows except for gaming anymore, so I don't think that's related.) I tried booting into Debian a couple days ago after the first time in a long time. At that time, it was still Debian bookworm. Prior to upgrading, I had noticed a behavior where, after booting past grub, the cursor ("_") screen would appear, and then go dark. If I blindly entered my LUKS password and gave it a moment, I would hear my hardware work on something and GNOME would eventually load, and I could proceed as normal. Since I had not updated in a very long time (months), I ran updates, noted that I'd be updating to Debian 12, and then shut down. When I came back the next day, I now could no longer boot into GNOME, and was met with a black screen. I tried entering my LUKS password, and again, I can hear the hardware work on something, but nothing actually changes on the screen. Trying to change to a different tty does not yield any command prompt, and I have to reboot to get back to grub and set the nomodeset flag to get into any kind of GUI. I thought perhaps there was an Nvidia issue, so I decided to try to remove the Nvidia driver and go back to nouveau as a temporary solution. This did not prove fruitful; I can now only get to a GUI of any kind past boot when enabling "nomodeset" in the grub menu. I did try to reinstall the proprietary Nvidia drivers, thinking that perhaps they just needed to be reconfigured after the update, after all. However, there, too, I ran into trouble: I know that I am supposed to be using the nvidia-legacy-390xx-driver package, because that is what is supported and documented on the [Debian Wiki page](https://wiki.debian.org/NvidiaGraphicsDrivers) . I also noticed, though, that when I run nvidia-detect, I get an error that I have not seen, before:

Detected NVIDIA GPUs:
01:00.0 VGA compatible controller : NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1)

Checking card:  NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1)
Uh oh. Failed to identify your Debian suite.

I also check if I can even install the driver package itself without needing to verify nvidia-detect, or even just to search the repository for the package, I get something even more baffling, to me

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package nvidia-legacy-390xx-driver

Sorting... Done
Full Text Search... Done
nvidia-legacy-check/testing 525.116.04-1 amd64
  check for NVIDIA GPUs requiring a legacy driver

I tried editing /etc/apt/sources.list to include bullseye-backports main contrib non-free-firmware, and then I was able to find the driver package. When I tried to install the legacy driver, however, a bunch of packages could not be installed because of a dependency issue on xserver-xorg-core, which needed to be version < 2:1.20.99 but had been upgraded to version 2:21.1.7-3, which is the current version of that package. As a result, I can't even try to re-install the proprietary legacy driver and see if that will resolve the issue. I'm not sure where to go, from here. Does anyone have any idea how to solve this, either by fixing the nouveau side or by trying to get the legacy-390xx-driver reinstalled? Thanks for any help you folks can offer!

I'll preface this by saying I've been searching high and low for a solution, and the closest thing I found was this thread over at Ask Different . *Background*: I have an ailing MacBook Pro 1,1 that I am trying to breathe a second life into using Linux to do some C++ development work. Eclipse is my IDE of choice (mainly so I can be consistent with other computers I have around the house), so I kind of need X/a-GUI-of-some-sort. I've completed a plain Jane install of Debian (Jessie) using the i686 build, and the system is pretty damn solid. However, the system freezes with this error message on boot: fb: switching to radeondrmfb from EFI VGA The fix found at Think Different was to add nomodeset as a boot option. This gets me into the system, and it is passably usable, but can be better, I'm sure. Some information on the setup: - Debian (Jessie) build - I have tried recompiling a 3.x kernel to see if it was something in the newer 4.x kernel, but the problem persists - Using the latest rEFInd to boot into the system - lspci -nnk reports VGA compatible controller : Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] [1002:71c5] for my graphics card The issue sounds similar to this one, which also does not have an answer. It has been almost a full decade (if not more) since I've played with Linux (think 2.2.x series kernels when PowerPC was cutting edge), so some of this stuff is very very new to me. So some high level questions. - What the heck is nomodeset, and what does it do? The closest answer I've found is that nomodeset tells the (newer) Linux kernels not to do any of the heavy lifting with the video card -- presumably this is because video drivers were moved into the kernel? I'm not sure how accurate that is. - Are there other kernel options I may be able to try? I could not find an exhaustive list of options - some are specific to distros, some to boot loaders, etc. - If I can boot into the system using nomodeset as a kernel prompt, is there a way to load the Radeon driver after the fact? - Barring that, can I not configure X in some way to use hardware video rendering vs. software video rendering? I envision booting into text-only mode, and then updating some config option in X, then launching X.

I need this because my dell notebook video card is only not freezing if I use nomodeset on grub. But then, I am limited to 4:3 resolutions (right?). So, I am looking for a way to not stretch the screen image (1024x768) on the full resolution (1920x1080) monitor. I wanted to let the 1024x768 (or 1440x1080) be in the middle of the screen (with a black margin on each side), not stretching! I cant find a way to command xrandr to do that, I tried many things on the --output and --pos but nothing help to accomplish that. Even better would be if there was some way to tell VESA to use 1920x1080 directly tho. related: https://unix.stackexchange.com/questions/644634/normal-hd-on-ultra-wide-monitor-without-stretching-pixels wont work: https://askubuntu.com/a/614242/46437 https://superuser.com/a/1245757/157532 (for 2 monitors, not my case) https://superuser.com/a/485165/157532 :( ...

**Setup** I'm trying to build a new media PC, and chose a low-power Intel Core i5 10600T processor, which has an integrated UHD 630 graphics chip. The motherboard is an ASUS Prime B560M-A and the display used is a Sony Bravia KDL-55W905A. I am using Debian testing (Bullseye), XFCE and lightdm. **Problem details** It seems that no displays are detected by the graphics chip at all. I get graphics at boot time and in BIOS, but when the system tries to start X, the screen goes blank permanently. Nothing is displayed in the X terminal and regular terminals cannot be accessed with for ex. Ctrl-Alt-F[something]. However, as expected, the computer responds normally to SSH access and I can interact with it remotely. The Xorg log file is here: https://pastebin.com/XCpjxe3y The offending line seems to be this: [ 3.859] (WW) modeset(0): No outputs definitely connected, trying again... lspci -v gives this output which seems fine: 00:02.0 VGA compatible controller: Intel Corporation CometLake-S GT2 [UHD Graphics 630] (rev 03) (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 Flags: bus master, fast devsel, latency 0, IRQ 140, IOMMU group 1 Memory at 6000000000 (64-bit, non-prefetchable) [size=16M] Memory at 4000000000 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] Capabilities: Vendor Specific Information: Len=0c Capabilities: Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: Process Address Space ID (PASID) Capabilities: Address Translation Service (ATS) Capabilities: Page Request Interface (PRI) Kernel driver in use: i915 Kernel modules: i915 dmesg log shows problems with the video card at 1.046225, 1.061414, 1.063566 and 1.063917: https://pastebin.com/M1DCCDZ4 **What have I tried** For the record, I have an older and slower media PC machine with Core i5 4590T and its integrated graphics chip. This system works perfectly fine with the same TV. - The motherboard has two HDMI outputs and one DP output. None of these work. - Different cables have been tried, including cables which work with the same TV and the older media PC machine. - When booting from an Ubuntu liveCD, The exact same thing happens. - I cannot access xrandr to check on displays, because X does not start. - Setting i915.modeset=0 in grub config gets me to X at 1024x768 (only). In this state, xrandr runs, but does does not seem to give any sensible output and the resolution cannot be changed from X settings. - Finally, the xserver-xorg-video-intel package description states that it should not be used for systems newer than 2007. I have uninstalled the package, but this did not seem to have any effect. The Xorg log after this has been done is here: https://pastebin.com/MwqvwmWL I'm at my wit's end. Of course I could order a low-end graphics card and add it to the system, but would prefer not to. Any help is appreciated. **Additional questions** As said, if I set i915.modeset=0, I get to X, but the graphics are severely limited. I am also unsure about what the option truly does internally. Can I work with this state in some way to force a better resolution? Does HW acceleration work in this state?

# Linux issues on iMac I have Ubuntu 18.04.4 LTS and Arch Linux installed on an iMac, which I think doesn't support KMS. I have gotten Ubuntu to work with several desktops, window managers, and display managers. When I attempted to install Manjaro, nothing worked, even with nomodeset, so I tried Arch. I have gotten the TTYs to work on Arch, but not X (I haven't tried Wayland yet). The problems I have had so far: - Booting without nomodeset results in a black unresponsive screen - I can't successfully startx or xinit on Arch even with nomodeset - Suspending in Ubuntu results in a black unresponsive screen - Ubuntu brightness keys don't work, but an image on the screen says it does I have a bunch of information, please let me know if any is unnecessary, or if I need to add more details. ## More boot info When I boot without nomodeset I see some info ending with the following:

*Error* No UMS support in radeon module!

At this point, the resolution sharpens slightly, then the screen goes black. With nomodeset, the screen doesn't go black but shows more logs, then proceeds to the login screen. UPDATE: I used to be able to see that message, but I can't seem to bring it back. Everything else is the same, though. ## Ubuntu 18.04 System info (as found in settings GUI): - Memory: 3.8 GiB - Processor: Intel® Core™️ i3 CPU 540 @ 3.07GHz x 4 - Graphics: llvmpipe (LLVM 9.0, 128 bits) - GNOME: 3.28.2 - OS type: 64-bit - Disk: 376.9 GB lspci | grep VGA prints 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] cat /var/log/Xorg.0.log prints a whole bunch of stuff, let me know if you need any of it. ## Arch startx & prints:

X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
Build Operating System: Linux Arch Linux
Current Operating System: Linux amc-arch 5.6.5-arch3-1 #1 SMP PREEMPT Sun, 19, Apr 2-2- 13:14:25 +0000 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=/dev/sda3 nomodeset
Build Date: 30 March 2020 05:05:45AM

Current version of pixman: 0.38.4
        before reporting problems, check http://wiki.x.org 
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file:"/var/log/Xorg.0.log", Time: Mon Apr 20 19:53:22 2020
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
ile at "/var/log/Xorg.0.log" for additional information.(EE) (EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Job 1, 'startx &' has ended

The log file is smaller, but still big. Let me know if it is necessary. # KMS - Kernel Mode Setting I have looked around the internet, and I believe the issue is kernel mode setting. If you know about this, I would appreciate help. Is the only solution an external graphics card that supports KMS? Can I use or make a window manager or desktop environment that doesn't require KMS? Can I make a suggestion to the Linux Kernel to make an alternative to KMS that will still work? Why does Ubuntu work (mostly) but Manjaro doesn't?

I hope you can help me. I tied a few solutions to similar problems, but none seemed to have worked for me. My set-up: - **OS**: Linux Kubuntu 19.10 - **MB**: ASUS PRIME B350-PLUS - **CPU**: AMD Ryzen 3 1300X - **GPU**: ATI Radeon HD 5450 (Dual Monitors, 2 x DVI 1920x1080) - **RAM**: 2x4GiB DDR4 - **SSD**: Boot drive is a Western Digital M.2 SSD This setup worked flawlessly until 2 weeks ago. I updated my BIOS around that time. After that the problems kept coming. The problem manifests itself as follows: **Boot number 1:** 1. BIOS information is showing 2. GRUB comes up, I select Kubuntu and hit enter 3. The screen turns black, the keyboard and mouse turn off (backlight and mouse light) 4. The 2 monitors go into power-saving mode, usb devices turn back on 5. Nothing happens, HDD_LED stays on permanently Then I press the reset button after a few minutes. **Boot number 2:** 1. BIOS information is showing 2. GRUB comes up, I select Kubuntu and hit enter 3. The screen turns black, the keyboard and mouse turn off (backlight and mouse light) 4. usb devices turn back on 5. Login screen appears Note that the screens never go into power saving mode. There is no splash screen as I turned that off with nosplash. I tried booting with nomodeset. This seems to work every time so far. But that cannot be the permanent solution to my problem, since that mode lacks the necessary support for two screens with that resolution. What I would like to know is, do you know any solution for this problem? And is there a way to read the boot messages from the previous boot? Maybe they can tell me more. ---------- **UPDATE** I finally managed to get dmesg of a failed boot (I waited on a failed boot for several minutes, to ensure that dmesg is written to /var/log/dmesg, then after the next successful boot, I found the log in /var/log/dmesg.0). This caught my eye: [ 22.864019] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 22.864030] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 27.868014] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 27.868024] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 27.868032] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BE9E (len 821, WS 0, PS 0) @ 0xBEFB [ 32.872012] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 32.872021] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CB6C (len 72, WS 0, PS 0) @ 0xCB9B [ 37.876016] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 37.876025] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 42.880011] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 42.880020] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 47.884011] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 47.884020] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 52.888015] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 52.888024] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 52.888095] kernel: [drm:cypress_dpm_set_power_state [radeon]] *ERROR* rv770_restrict_performance_levels_before_switch failed [ 57.892010] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 57.892019] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 57.892028] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing BE9E (len 821, WS 0, PS 0) @ 0xBEFB [ 62.896010] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 62.896019] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CB6C (len 72, WS 0, PS 0) @ 0xCB9B [ 67.900011] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 67.900020] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 72.904010] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 72.904018] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 77.908011] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 77.908020] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 82.912010] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 82.912018] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 87.916009] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 87.916018] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 92.920008] kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [ 92.920017] kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C79C (len 62, WS 0, PS 0) @ 0xC7B8 [ 93.142085] kernel: EXT4-fs (nvme0n1p2): mounted filesystem with ordered data mode. Opts: (null) This must be the problem. But only on some boots. Now I need to find out how to fix it. ---------- **UPDATE** I remembered that I updated my BIOS a few weeks before I noticed the problems. Within these few intermittend weeks I barely used the computer, so maybe the problem was already there, I just did not see it. I was running "Version 5220 2019/09/24". So I reverted back to "Version 5216 2019/09/09". I did so by putting the .CAP file on a stick and "upgrading" the BIOS from within the BIOS menu. This took some time, but worked. After that I just booted and had no problem since. So maybe the last BIOS update was the problem. The changes for that version contain (according to ASUS): 1. Update AGESA 1.0.0.3ABBA to improve system performance. 2. Removes Gen 4 support when using Ryzen 3000 CPUs. Maybe one of these things broke Linux? Windows had no problem. BTW: If you have a similar problem with Linux sporadically not booting on this motherboard try "iommu=soft" as a parameter in the boot item for linux in GRUB.

I just installed Linux Mint (first time using Linux) on my HP G7 255. I don't have experience with programming or Linux in general, but for over an hour I can't connect to the internet. I have to say at this point that in the booting process in order not to have a black screen I changed "quiet splash" to nomodeset (no idea what are those, but it worked, read that it has to do with the drivers). I would really appreciate some help here, I read about 10 different forum discussions on this topic but I didn't understand a lot. $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 04:0e:3c:f0:75:4e brd ff:ff:ff:ff:ff:ff # dmesg | grep fail ACPI Error: [\_SB_.PCI0.GPP2.BCM5] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210) ACPI Error: 1 table load failures, 12 successful (20170831/tbxfload-246) ACPI Error: [WLVD] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) [ 0.137990] ACPI Error: [WLVD] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) [ 0.233009] ACPI Error: [WLVD] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) [ 0.328972] ACPI Error: [WLVD] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)

I've lovingly installed Fedora 28 (actually 27, then upgraded into 28 -- but this occurred at the start of the 27 install), onto my Dell Inspiron 1545. PROBLEM STATEMENT: I have to use NOMODESET to even receive a useable GUI. Without that switch present in the cmdline, I receive a GUI on F1 console as described below - just a mouse pointer. I can actually hit END (I think) and receive a GUI popup that asks for english/other languages, but that closes after I click something, and I'm back to the pretty desktop picture, mouse pointer, and nothing else. BACKGROUND: Attempted a USB-based install to my Inspiron 1545 (4GB RAM, 128GB SSD), and the only way I could proceed with the GUI installation was to provide NOMODESET on the cmdline (e, to edit) for the install process. It was decidedly low-res (due to having to use NOMODESET to install), but I figured a driver sort-out was in order after install and it would give me full resolution. No joy. COMPLAINT: **I'm now stuck in 1024x768.** No amount of fiddling, troubleshooting has gotten me joy. And **NOMODESET** is hardcoded in the cmdline (understandably, as that's what I started the installation with, so it kept it, I believe) -- which is the only way I can boot to a GUI and use LXDE (which is the default desktop options I picked). This gui is 1024x768, and nothing with XRANDR or anything else will change it. DETAILS: (1) The laptop itself is somewhat a monster - the LCD screen was physically REMOVED from the laptop - the whole thing, so it's only the laptop bottom. It's ugly, but still works. In fact ^^ it worked with Windows, no issues, displaying on the external Sanyo LCD monitor at the full resolution (1360x768) with no problem. Also, LXDE works with NOMODESET, but only at 1024x768. (2) When I REMOVE 'nomodeset' from the cmdline, it will boot just fine - but I am presented with the greeter background (the fiber optic blue graphic), a mouse pointer, and nothing else. The other terminals (ALT-F[2-8]) provide a normal text console login, which works fine. The ALT-F1 (primary console), again, shows the Fedora background greeter, a mouse pointer (which moves), and nothing else. (3) Here are some (hopefully) relevant diagnostics I've performed both WITH and WITHOUT the NOMODESET parameter in the cmdline (grub boot line): First, **lspci** to ensure we have a valid supported graphics chipset: **[root@Towel ~]# lspci -nnk | grep -A3 VGA** 00:02.0 VGA compatible controller : Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) Subsystem: Dell Device [1028:02aa] Kernel modules: i915 00:02.1 Display controller : Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) What does inxi say with NOMODESET present in the cmdline: **[root@Towel ~]# inxi -SMCGx** System: Host: Towel Kernel: 4.19.14-200.fc28.x86_64 x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: LXDE 0.9.3 Distro: Fedora release 28 (Twenty Eight) Machine: Type: Portable System: Dell product: Inspiron 1545 v: N/A serial: 5DQG7H1 Mobo: Dell model: 0G848F serial: .5DQG7H1.CN701668CR02E3. BIOS: Dell v: A14 date: 12/07/2009 CPU: Topology: Dual Core model: Intel Pentium Dual T3400 bits: 64 type: MCP arch: Core Merom rev: D L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 8645 Speed: 998 MHz min/max: 1000/2167 MHz Core speeds (MHz): 1: 998 2: 998 Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Dell driver: N/A bus ID: 00:02.0 Display: server: Fedora Project X.org 1.19.6 driver: vesa unloaded: fbdev,modesetting resolution: 1024x768~N/A OpenGL: renderer: llvmpipe (LLVM 6.0 128 bits) v: 3.3 Mesa 18.0.5 direct render: Yes Now, without NOMODESET in the cmdline: **[root@Towel ~]# inxi -SMCGx** System: Host: Towel Kernel: 4.19.13-200.fc28.x86_64 x86_64 bits: 64 compiler: gcc v: 8.2.1 Console: tty 2 Distro: Fedora release 28 (Twenty Eight) Machine: Type: Portable System: Dell product: Inspiron 1545 v: N/A serial: 5DQG7H1 Mobo: Dell model: 0G848F serial: .5DQG7H1.CN701668CR02E3. BIOS: Dell v: A14 date: 12/07/2009 CPU: Topology: Dual Core model: Intel Pentium Dual T3400 bits: 64 type: MCP arch: Core Merom rev: D L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 8645 Speed: 998 MHz min/max: 1000/2167 MHz Core speeds (MHz): 1: 998 2: 998 Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: server: X.org 1.19.6 driver: modesetting unloaded: fbdev,vesa tty: 170x48 Message: Advanced graphics data unavailable in console for root. How about Xorg.0.log with NOMODESET present in the cmdline: **[root@Towel ~]# cat /var/log/Xorg.0.log | grep driver** [ 18.877] X.Org XInput driver : 24.1 [ 18.945] (==) Matched modesetting as autoconfigured driver 0 [ 18.945] (==) Matched fbdev as autoconfigured driver 1 [ 18.945] (==) Matched vesa as autoconfigured driver 2 [ 18.945] (==) Assigned the driver to the xf86ConfigLayout [ 18.945] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 18.951] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 18.952] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 18.954] (II) FBDEV: driver for framebuffer: fbdev [ 18.954] (II) VESA: driver for VESA chipsets: vesa [ 20.419] ABI class: X.Org XInput driver, version 24.1 [ 20.419] (II) Using input driver 'libinput' for 'Power Button' [ 20.427] (II) No input driver specified, ignoring this device. [ 20.429] (II) Using input driver 'libinput' for 'Sleep Button' [ 20.437] (II) No input driver specified, ignoring this device. [ 20.437] (II) No input driver specified, ignoring this device. [ 20.440] (II) Using input driver 'libinput' for 'Logitech USB Receiver' [ 20.447] (II) Using input driver 'libinput' for 'Logitech USB Receiver Mouse' [ 20.460] (II) No input driver specified, ignoring this device. [ 20.464] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control' [ 20.474] (II) Using input driver 'libinput' for 'Logitech USB Receiver System Control' [ 20.486] (II) Using input driver 'libinput' for 'Dell WMI hotkeys' [ 20.501] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard' [ 20.509] (II) Using input driver 'libinput' for 'AlpsPS/2 ALPS GlidePoint' [ 20.525] (II) No input driver specified, ignoring this device. [ 20.545] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control' [ 20.545] (**) Option "_source" "_driver/libinput" And Xorg.0.log with NOMODESET removed/absent: **[root@Towel ~]# cat /var/log/Xorg.0.log | grep driver** [ 18.506] X.Org XInput driver : 24.1 [ 18.620] (==) Matched modesetting as autoconfigured driver 0 [ 18.620] (==) Matched fbdev as autoconfigured driver 1 [ 18.620] (==) Matched vesa as autoconfigured driver 2 [ 18.620] (==) Assigned the driver to the xf86ConfigLayout [ 18.621] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 18.631] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 18.633] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 18.635] (II) FBDEV: driver for framebuffer: fbdev [ 18.635] (II) VESA: driver for VESA chipsets: vesa [ 18.669] (II) glamor: OpenGL accelerated X.org driver based. [ 19.354] (II) modeset(0): [DRI2] DRI driver: i965 [ 19.354] (II) modeset(0): [DRI2] VDPAU driver: va_gl [ 19.648] ABI class: X.Org XInput driver, version 24.1 [ 19.648] (II) Using input driver 'libinput' for 'Video Bus' [ 19.673] (II) Using input driver 'libinput' for 'Power Button' [ 19.684] (II) No input driver specified, ignoring this device. [ 19.686] (II) Using input driver 'libinput' for 'Sleep Button' [ 19.702] (II) No input driver specified, ignoring this device. [ 19.703] (II) No input driver specified, ignoring this device. [ 19.705] (II) Using input driver 'libinput' for 'Logitech USB Receiver' [ 19.714] (II) Using input driver 'libinput' for 'Logitech USB Receiver Mouse' [ 19.731] (II) No input driver specified, ignoring this device. [ 19.733] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control' [ 19.743] (II) Using input driver 'libinput' for 'Logitech USB Receiver System Control' [ 19.756] (II) Using input driver 'libinput' for 'Dell WMI hotkeys' [ 19.771] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard' [ 19.781] (II) Using input driver 'libinput' for 'AlpsPS/2 ALPS GlidePoint' [ 19.793] (II) No input driver specified, ignoring this device. [ 19.843] (II) Using input driver 'libinput' for 'Logitech USB Receiver Consumer Control' [ 19.843] (**) Option "_source" "_driver/libinput" What about dmesg without NOMODESET in the cmdline? [ 9.632354] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. And finally, to wrap up a new set of commands I learned recently, I also played with xrandr, and asked it to tell me what IT thought the displays, etc., were: [root@Towel ~]# xrandr --verbose xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768 default connected 1024x768+0+0 (0x2ae) normal (normal) 0mm x 0mm Identifier: 0x2ad Timestamp: 19525 Subpixel: no subpixels Clones: CRTC: 0 CRTCs: 0 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: 1024x768 (0x2ae) 0.000MHz *current h: width 1024 start 0 end 0 total 1024 skew 0 clock 0.00KHz v: height 768 start 0 end 0 total 768 clock 0.00Hz 800x600 (0x2af) 0.000MHz h: width 800 start 0 end 0 total 800 skew 0 clock 0.00KHz v: height 600 start 0 end 0 total 600 clock 0.00Hz 640x480 (0x2b0) 0.000MHz h: width 640 start 0 end 0 total 640 skew 0 clock 0.00KHz v: height 480 start 0 end 0 total 480 clock 0.00Hz Notice the 'default' as the name for the only display? This is probably due to the system seeing the attached LCD - disattached/gone -- and the VGA connected to the external display (e.g., 'default'). And some hwinfo goodness: [root@Towel ~]# hwinfo --monitor 28: None 00.0: 10000 Monitor [Created at monitor.97] Unique ID: rdCR.dwn9oRFeFS2 Hardware Class: monitor Model: "LCD TV" Vendor: SAN Device: eisa 0x0000 "LCD TV" Resolution: 640x480@60Hz Resolution: 800x600@60Hz Resolution: 1024x768@60Hz Resolution: 1280x720@60Hz Resolution: 1360x768@60Hz Year of Manufacture: 2015 Week of Manufacture: 0 Detailed Timings #0: Resolution: 1360x768 Horizontal: 1360 1424 1536 1792 (+64 +176 +432) +hsync Vertical: 768 771 777 795 (+3 +9 +27) +vsync Frequencies: 85.50 MHz, 47.71 kHz, 60.02 Hz Driver Info #0: Max. Resolution: 1360x768 Vert. Sync Range: 23-63 Hz Hor. Sync Range: 15-69 kHz Bandwidth: 85 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown ... So, in summary: (1) Installed Centos 27 with NOMODESET (as no other options worked) (2) Stuck with NOMODESET in command line (but I have removed it to test) (3) Workable gui with NOMODESET parameter passed, but stuck at 1024x768 (4) i915 driver seems to load with NOMODESET absent/removed, but no workable gui (maybe due to laptop screen being physically absent) P.S. I have tried as well putting video.allow_duplicates=1 into the cmdline, but this yields absolutely no difference that I was aware of. P.P.S. I have heard that since my laptop lid with the LCD actually triggers a reed switch in the base of the unit, the laptop may be expecting the circuit to be closed (via the reed switch being activated, through the action of closing the lid) before the laptop would become unconfused and offer any sort of useability to the i915 configuration. Willing to try that this weekend, if I can figure out how to do this. -- Updated with Xorg.0.log w/ and w/o Modeset -- -> With Modeset: https://pastebin.com/muYey8SJ -> Without Modeset: https://pastebin.com/JrSbSs7N

I need to install Elementary OS on my (late 2009) iMac 11.1. I am booting from an external USB and in when presented with a GRUB menu, I choose "Install Elementary OS" and then press e key to edit and add nomodeset and then I press F10 to boot. With Elementary OS installed, I run into problems after rebooting. First I get GRUB to go in normal or recovery mode, I use nomodeset again to boot in normal mode but instead of the GUI, I get a command line and it asks me for a username/password. After that, I run startx and get a No screens found error. I think it has something to do with my graphics card driver (Radeon 4850HD). Does anyone know how to get back to the GUI mode?

My laptop which has an Nvidia GeForce 310M GPU is 9 years old and it has been OK with all Ubuntu releases until now. What is the difference between 18.04 and previous releases that causes the black (or purple) screen while loading the live installation? Is it the kernel? For instance, do kernel developers ditch the old hardware in updates? I am asking this because I want to know if I can ever use updated distros (e.g. Debian) without nomodeset and graphic problems due to it.

When I boot I get this errors: nouveau gr: failed to load gr/sw_nonctx nouveau DRM: failed to create kernel channel -22 But all the stuff it's working fine. When I add in /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="nomodeset nouveau.setmode=0" I'm not getting this error anymore. Should I use nomodeset nouveau.setmode=0 ?

When I insert my USB or enter a DVD with Kali installer in it, it all works fine until I'm in the installation window (after I reboot the computer). I press the Kali Live option on the menu and wait until it finishes loading. After it is done I suddenly get a black screen with a white little bar at the top left. I can't press or write anything (and no I don't have a mouse cursor on the screen). What can it be? I downloaded the last Kali version 1.10 and tried 1.09 as well which I had a while ago. The same disks and USB worked perfectly on my laptop. Here's a picture: More information about my computer: When I try to add the nomodeset option in the boot I get this:

I'm on a Debian distro, it's been a long time that I edited Openbox menu.xml, so I forgotten that I had to use obmenu or whatever, I opened it in a normal text editor, edited something in the right-click menu. Then saved then restarted Openbox without reconfiguring it. And now I can still login, after that all I see is a black screen with the mouse cursor. I tried opening the terminal using the Super key + T keyboard combination, but I can't see anything at all, no terminal, no web browser, just a cursor and a black screen. Note, I can't boot to a live CD, due to a nomodeset issue. If nomodeset is on, my PC won't boot correctly, so I always set it to off, but when booting from a live CD, you can't set it to off.

I just got a Dell Precision 7520 which comes with Ubuntu 16.04 and the NVIDIA Quadro M1200 GPU. I installed Linux Mint 18.2 and then the nvidia-375 apt package. After reboot I hear the Mint jingle and the screen is blank. From my research this seems to have something to do with nomodeset, however during boot holding down Shift does not bring up any menus.

How can I write an openSUSE script that will change my boot menu.lst file and add nomodeset automatically both to failsafe and normal boot option? This script is for SUSE Studio I'm going to write it under the "Run script whenever the appliance boots" for the first boot.

I'm trying to get X to work on a ThinkPad W530. I set the BIOS to only use the integrated graphics, I attempt to boot. The display goes blank when KMS is executed and does not recover. I append nomodeset or i915.modeset=0. Then it does boot, does not attempt to change resolution while in console mode, but I cannot start X. I see in dmesg: [drm:drm_pci_agp_init] *ERROR* Cannot initialize the agpgart module. DRM: Fill_in_dev failed. I have the latest BIOS for my system, and I've tried the kernels: 3.7.2, 3.9.5 and 3.10-rc5. This is a Slackware 14.0 64-bit distro. It seems that the i915 module cannot work when nomodeset is used, and that there is some bug which makes the display turn blank. Is there some way around this?

I recently had at work an HP zbook 15 G3 (dual graphic cards: Intel integrated and Nvidia Quadro) I had first Ubuntu with Plasma desktop installed by the lab (worked OK except with second screen and docking station), which I decided to replace by OpenSUSE Leap 42.1, with Plasma too. First I could not install without passing the nomodeset option to the kernel. With nomodeset, the installation went fine, and when I rebooted, I saw that I had no way to control screen brightness/backlight, which was at a painful maximum. Not with the applet, nor with the Fn keys. The /sys/class/backlight was empty. I decided to go on and install bumblebee with Nvidia proprietary drivers. (blacklisted nouveau, mkinitrd, etc). So far no problems, bumblebee worked fine, but still no backlight control. The /sys/class/backlight was empty. If I removed the nomodeset from the kernel options, (keeping nouveau.modeset=0 and nouveau in the blacklist), then I would see intel_backlight in /sys/class/backlight, and could control backlight from the applet. I discovered later that the module i915 is needed for this to happen (I tried to see with i915.modeset=0/1) Nevertheless, after 3 to 15 minutes maximum, the desktop would randomly freeze: the mouse would stutter twice, then everything would freeze: no mouse or keyboard control, and I had to reset with power button. There was the same behavior with nouveau without bumblebee: as soon as I remove nomodeset, the crash is bound to happen. I have a temporary workaround now, where I disable integrated graphics in the BIOS, and installed the binary driver from the Nvidia website, while still booting with the nomodeset option. /sys/class/backlight now contains acpi_video0, and control works only through the applet. There is no error in xorg log, nor in journalctl, except spamming "kscreen: Primary output changed from blablabla", which still happens now. I'm at loss to find the culprit, especially because it worked in Ubuntu. How can I find which modeset doesn't please my configuration? I would really appreciate the Optimus technology for battery life and heat.