[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



Also (I've never used this before, so I might be holding it wrong, but...):
$ isenkram-lookup
cheese
ethtool
pcscd
scdaemon
$

On Sat, Aug 21, 2021 at 4:15 AM Rich <rincebrain@gmail.com> wrote:
>
> Hi Salvatore,
> I used firmware-11.0.0-amd64-netinst.iso. And yes, I did not manually
> install firmware-misc-nonfree since this initially failed, and I still
> got a black screen which did not ever resolve or respond to VT
> switching unless I used nomodeset and deleted quiet. (With quiet
> removed, it doesn't black out, but it does stop ever responding after
> it prints the "switching from EFI VGA" line.)
>
> I'll reboot in a bit and wait longer and see what happens...
>
> grep -C3 nouveau on syslog for, I believe, one of the failed boots says:
> Aug 21 02:28:06 struth kernel: [    2.209185] TSC found unstable after
> boot, most likely due to broken BIOS. Use 'tsc=unstable'.
> Aug 21 02:28:06 struth kernel: [    2.209187] sched_clock: Marking
> unstable (2208942206, 241638)<-(2215089173, -5905242)
> Aug 21 02:28:06 struth kernel: [    2.221262] clocksource: Switched to
> clocksource hpet
> Aug 21 02:28:06 struth kernel: [    2.305362] nouveau 0000:01:00.0:
> enabling device (0002 -> 0003)
> Aug 21 02:28:06 struth kernel: [    2.305517] checking generic
> (c0030000 710000) vs hw (d2000000 1000000)
> Aug 21 02:28:06 struth kernel: [    2.305519] checking generic
> (c0030000 710000) vs hw (c0000000 10000000)
> Aug 21 02:28:06 struth kernel: [    2.305521] fb0: switching to
> nouveaufb from EFI VGA
> Aug 21 02:28:06 struth kernel: [    2.305686] Console: switching to
> colour dummy device 80x25
> Aug 21 02:28:06 struth kernel: [    2.305783] nouveau 0000:01:00.0:
> vgaarb: deactivate vga console
> Aug 21 02:28:06 struth kernel: [    2.305843] nouveau 0000:01:00.0:
> NVIDIA G84 (084700a2)
> Aug 21 02:28:06 struth kernel: [    2.306955] nouveau 0000:01:00.0:
> Invalid PCI ROM header signature: expecting 0xaa55, got 0x0001
> Aug 21 02:28:06 struth kernel: [    2.306966] nouveau 0000:01:00.0:
> bios: unable to locate usable image
> Aug 21 02:28:06 struth kernel: [    2.306975] nouveau 0000:01:00.0:
> bios ctor failed, -22
> Aug 21 02:28:06 struth kernel: [    2.306984] nouveau: probe of
> 0000:01:00.0 failed with error -22
> Aug 21 02:28:06 struth kernel: [    2.324639] random: fast init done
> Aug 21 02:28:06 struth kernel: [    2.385518] ata1.00: ATAPI: HL-DT-ST
> DVDRW  GSA-S10N, AP09, max UDMA/33
> Aug 21 02:28:06 struth kernel: [    2.457249] usb 4-1: new high-speed
> USB device number 2 using ehci-pci
> --
>
> On Sat, Aug 21, 2021 at 4:03 AM Salvatore Bonaccorso <carnil@debian.org> 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?
> >
> > Regards,
> > Salvatore


Reply to: