Closed marler8997 closed 3 years ago
Is this with the on-board Intel GPU or do you have a discrete GPU (AMD/Nvidia) installed?
Onboard. I don't have an external "discrete GPU" installed on that machine.
Just out of curiosity, does this happen with all outputs? HDMI, VGA, and DVI?
EDIT:
Which version of NixOS are you using? Could you SSH into that box once it's running and check dmesg output as well as your NixOS version using nix-shell -p nix-info --run "nix-info -m"
I think the solution is to modify Nix's kernel config to support more graphics hardware.
Do you know which kernel configuration options might be missing? Could you add the output of uname -a
from that Ubuntu install, and the output of zcat /proc/config.gz
? This would help identifying which kernel options are different. Additionally, the output of dmesg
from both the working Ubuntu, and non-working NixOS could help, if the kernel is noisy enough about the features.
Since the P7H55-M LE motherboard is for ~2010-era CPUs, this shouldn't be an issue of the kernel being too old for the hardware.
@devshell
It was just on the HDMI output. I didn't have a VGA or DVI monitor available at the time.
@samueldr
Well Nix is on it now. I can't use a monitor but I can still use XServer from a remote machine.
It would take quite a bit of work to get Ubuntu back onto it, but I do still have Ubuntu 16.04 installed at work which should have the same kernel config. I'll get the config from that tomorrow and let you know. That's a good idea.
marler8997@z620dev016:~$ uname -a
Linux z620dev016 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 GNU/Linux
Note that /proc/config.gz
doesn't exist. But it looks like Ubuntu stores the config in /boot
:
(EDIT @lheckemann: collapsed)
@marler8997 Would you be able to boot the problematic machine with a standard Ubuntu Desktop Live image from USB or CD/DVD? Boot it all the way up into live mode and then check the kernel config and dmesg outputs?
I could with a bit of effort. But the kernel config will be the same that I already sent (except that the kernel on the CD will probably be an older version with a slightly different config, but graphics work with either version).
But the dmesg output might be helpful. It will have to wait untill next Tuesday though. I'm out of town and don't have access to the hardware until then.
Am I understanding right that nomodeset
made graphics output work in the installer? If so, you should probably be able to get it working in the installed system by setting boot.kernelParams = ["nomodeset"];
in your system configuration, or one-off by editing the kernel params (works in GRUB and systemd-boot) by pressing e on the boot menu entry.
I think the best shot we’d have at fixing this is if you could get the console output immediately after the freeze, like you did for the VirtualBox issue.
@marler8997 Did you get around to the above suggestions?
I think the real issue here is this: if you boot with nomodeset
in the installer, that should be added to boot.kernelParams
in the generated config. I have seen a number of laptops not showing anything on the monitor when using kms.
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
I had the same problem (on both arch and nixos) where the graphics would start to glitch a few seconds through startup. Adding nomodeset
in grub seems to prevent that, however it also doesn't scale the console correctly.
I marked this as stale due to inactivity. → More info
I don't believe there is anything actionable in this issue. Closing as otherwise it will stay open forever with vaguely similar reports.
If you, @marler8997, are still experiencing that specific issue on the same hardware, please re-open with more details about what you expect we can do to help.
Anyone else with "the same" or a similar issue, please open a new issue so your specific problem can be looked at, investigated and hopefully a fix found. Feel free to reference this issue though.
Sorry I havent had enough motiviation to hook up a monitor and retest this on my closet PC. I'm fine with closing.
Issue description
I installed NixOS on bare metal in a computer of mine this last weekend...and graphics did not work. They just stop updating after a certain point in the boot, however, the OS still boots and you can still type commands. Even though I couldn't see what was going on, I was able to issue a "poweroff" command from the keyboard and turn of the computer with it. I had to use the
(nomodeset)
option to boot Nix, and after installing nix, graphics still do not work.This is the same experience I had on virtualbox (see https://github.com/NixOS/nixpkgs/issues/58070) with the
VMSVGA
graphics controller, however, this time I can't fix it by changing the graphics controller since it's actual hardware.This means I can't use nix on my ASUS P7H55-M LE Motherboard.
Steps to reproduce
Unfortunately this requires hardware. But the steps to reproduce is simply to take a NixOS minimal installation CD and boot with it on hardware. Graphics won't work but you can still install NixOS using the
(nomodeset)
boot option. However, even after you install nix, graphics still wont work.Notes
The graphics stop working very early in boot. I believe this is a problem with the kernel config. I think the solution is to modify Nix's kernel config to support more graphics hardware. I was able to install Ubuntu on this same machine, which tells me that the linux kernel does support my hardware, it's just that Nix's configuration does not enable it.