Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-560 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I got the similar issue but for me looks like the issue is related to
the onboad Intel HD Graphics. When start the system without it nvidia
works fine and also switch to virtual terminals using Ctrl+Alt+F3 to
reinstall the driver. For this turned on the computer just with nvidia
connected and in th
If you mean purging Nvidia by running something like, apt remove --purge
'^nvidia-.*', yes I have tried that a couple of times via 'recovery
mode', and consequently switched to Nouveau, but that doesn't change
anything. I still get the same bootloading behavior. Does that imply
that it's not an nvi
That image does not suggest it is Nvidia issue. AFAIK the initial
ramdisk does not load the Nvidia module, but i may be wrong. Once you
brick the system, can you unbrick it from recovery mode by uninstalling
(and purging) the Nvidia driver.
--
You received this bug notification because you are a
Hi Dimitrij, Thanks for the suggestion. Unfortunately none of it works,
it's a total freeze, and even Ctrl+Alt+Del won't work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071680
Title:
Ubuntu fai
When you get stuck at the bootloading screen, please try to switch to
virtual terminals using, for example, Ctrl+Alt+3 or 4 or 5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071680
Title:
Ubuntu
** Also affects: nvidia-graphics-drivers-560 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071680
Title:
Ubuntu fails to boot
To manage notific
The last but not least: I'm facing the same issue after trying Ubuntu
24.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071680
Title:
Ubuntu fails to boot
To manage notifications about this bug
Unfortunately I can still reproduce this even after upgrading to the new
Nvidia 550-series drivers.
** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: ubuntu
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071680
Title:
Ubuntu fails to boot
To manage notifications about this bug go to:
https://bu
I have been unable to boot Ubuntu on my machine for quite a while now
(this also happens with Fedora 40 and Ubuntu 22.04), however, after a
long back and forth with Daniel, I have been unable to capture a log,
(journalctl, does not capture failed boot logs), and all I can get is
'recovery mode' boo
Okey, but unfortunately I don't get passed "Loading initial ramdisk ..." if I
don't boot into recovery mode. And unfortunately non of the non-(recovery mode)
failed boots get captured by journalctl.
Is there no workaround?
--
You received this bug notification because you are a member of Ubuntu
Any logs that say 'recovery nomodeset' at the top are not helpful here.
Please:
1. Boot *not* in recovery mode.
2. Reproduce the Xorg black screen bug.
3. Reboot.
4. Log into Wayland.
5. Run: journalctl -b-1 > prevboot.txt
6. Attach the resulting text file here.
** Changed in: linux (Ubunt
This time I've put prime-select to 'nvidia' (as opposed to intel), and
tried to boot using recovery mode.
But what I get is a completely black screen (no, log in screen). So I
attached the logs as well.
** Attachment added: "previous-(prime-select-nvidia).txt"
https://bugs.launchpad.net/ubunt
I just wanted to give an update on this, after upgrading to Linux
6.8.0-38-generic, and the corresponding Nvidia packages, No I even get
an blank screen when "logging into" Xorg.
Logging in, using Wayland for now solves the problem.
Attached the logs to the previous failed log in.
** Attachment
I had already done so, in fact this is how it already looks like:
GRUB_CMDLINE_LINUX_DEFAULT=""
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071680
Title:
Ubuntu fails to boot
To manage notifica
I was just reminded by bug 2072600, you might need to remove both
"splash" and "quiet" from the kernel command line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071680
Title:
Ubuntu fails to boot
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071680
Title:
Ubuntu fails to boot
To manage notifications about this bug go to:
https:
1. I removed the splash parameter, and the boot basically stops at:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9
2. No, currently not using any form of disk encryption
(I'm currently using the nvidia-535 (proprietary, tested), o
Also, are you using disk encryption?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071680
Title:
Ubuntu fails to boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
It sounds like we should ignore the fact that Nvidia-470 stopped working
if we can't discern that from the entire system failing to boot.
** Package changed: nvidia-graphics-drivers-470 (Ubuntu) => linux
(Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Summary changed:
Next please try booting, not in recovery mode, but also with the
"splash" kernel parameter removed. That should at least show you how far
the boot process is getting.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Yess, The 24.04 Live session works.
I have already tried purging all Nvidia-related packages, (using, apt-
get remove --purge '^nvidia-.*') and switching to the Nouveau driver,
won't work either.
Matter of fact I just finished a clean install, offline*, and without 3rd party
software, and that
Does booting the 24.04 live session from USB still work? If so then I'm
guessing the problem here is either a broken Nvidia driver or kernel
update.
The next thing I would try is to purge all Nvidia-related packages that
are installed. If that sounds too complicated then try just reinstalling
Ubun
Oh, I see. But that is what I did.
What happens the first time around, is that no Grub menu is shown and
what I get is a frozen bootloading screen. See:
https://askubuntu.com/questions/1516328/
So the only thing possible is to force shutdown (it doesn't 'reboot' via
Ctrl+Alt+Del), and after bo
Thanks but that log is from recovery mode. Please boot without recovery
mode first, then reboot into recovery mode and collect the log:
journalctl -b-1 > prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2071680/+attachment/5795452/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Hi Daniel,
Thanks for looking into this.
I've reproduced the failed boot, using the 535 driver (proprietary,
tested), and attached the logs.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2071680/+attachment/5795451/+files/lspci.t
Thanks for the bug report. Please reproduce a failed boot again so we
can get fresh logs. Then reboot in recovery and run:
lspci -k > lspci.txt
journalctl -b-1 > prevboot.txt
and attach the resulting text files here.
** Package changed: nvidia-graphics-drivers-535 (Ubuntu) =>
nvidia-graphi
Also the GTX 960M does not need a driver as old as 470. I strongly
recommend choosing either of the 535 or 550 drivers that are supported
by Ubuntu 24.04.
** Tags added: hybrid multigpu noble
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: New => Incomplete
--
You received t
** Description changed:
I have an Nvidia graphics hybrid setup (Geforce GTX 960M + Intel HD
Graphics 530), and Ubuntu 24.04 failed to boot after clean installing.
I switched to the 470-series driver instead of the default 535-series
- one, via "Recover mode" and things got working, until
32 matches
Mail list logo
