[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#992612: linux-image-5.10.0-8-amd64: Macbook3,1 fails to boot without nomodeset with nouveau



On Sat, Aug 21, 2021 at 10:03:20AM +0200, Salvatore Bonaccorso wrote:
> Control: tags -1 + moreinfo
> 
> Hi Rich,
> 
> On Sat, Aug 21, 2021 at 02:45:26AM -0400, Rich Ercolani wrote:
> > Package: src:linux
> > Version: 5.10.46-4
> > Severity: normal
> > X-Debbugs-Cc: rincebrain@gmail.com
> > 
> > Dear Maintainer,
> > 
> > (I have no idea how many people might run into this, but...)
> > 
> > I just had occasion to set up bullseye on an old Macbook Pro. After
> > convincing it to boot the installer
> > in the first place (which was "exciting"), the installer worked
> > fine...
> > 
> > ...then on first boot, I selected the top GRUB option, it booted,
> > and very shortly the display blanked and the system stopped
> > responding to any input that I could see.
> > 
> > I left it for a minute or two to see if it would come back, but no,
> > nothing visibly occurred. So I rebooted.
> > 
> > Drop the quiet from the kernel parameters, it goes up to something
> > mentioning nouveau and switching from EFI VGA to modesetting, and
> > then...stops, entirely, no response to VT switching or any other
> > commands, for at least the few minutes I waited. (I'll reboot and
> > take a photo shortly.)
> > 
> > So I try nomodeset, and we get all the way to X happily (in much
> > less time than I let it sit to see if it would come back, so I don't
> > think it would have come back...)
> > 
> > Slightly inconvenient. Fortunate that I didn't try the graphical
> > installer, I suppose.
> > 
> > I'll try fiddling with kdump and non-journald logging so I can get a
> > better idea what might be happening when it stops outputting...
> 
> #991941 and https://www.debian.org/releases/bullseye/amd64/ch06s04#completing-installed-system 
> Do you have needed firmware installed, which installer image did you
> use?

nevermind, skip the first question. The question raised by Ben in the
other bug though still holds (similarly in your case
firmware-misc-nonfree seems installed already).

Regards,
Salvatore


Reply to: