cannot boot on a newer kernel

If none of the more specific forums is the right place to ask

cannot boot on a newer kernel

Postby MagicPoulp » 2020-11-18 06:55

UPDATE: this issue is solved. Installing firmware-linux fixed the problem.

Thanks for the help. I can boot on the buster-backports 5.5 kernel on my external SSD drive. But I cannot boot on 5.6 or 5.8. And I want to try a newer kernel.

Here is the error I get:
    ACPI warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument#4 mismatch - Found [Buffer], ACPI requires package(20200520/nsarguments-66)
    ACPI: \_SB.PCI0.PEG0.PEGP._DSM: failed to evaluated _DSM

I have installed all the firmwares I could.
http://cdimage.debian.org/cdimage/unoff ... /20191116/

I found some related threads. It seems related to NVIDIA. I do have an nvidia graphics card. (sorry I bought the computer long ago I know they are not open source friendly as AMD)
viewtopic.php?f=6&t=137096
https://alt.os.linux.mageia.narkive.com ... aluate-dsm

--
here is the list of debian firmwares for buster, but I only took 3 of them and from the buster repo
    amd64-microcode_3.20181128.1_amd64.deb firmware-intel-sound_20190114-2_all.deb firmware-samsung_20190114-2_all.deb
    amd64-microcode_3.20181128.1_i386.deb firmware-intelwimax_20190114-2_all.deb firmware-siano_20190114-2_all.deb
    atmel-firmware_1.3-4_all.deb firmware-ipw2x00_20190114-2_all.deb firmware-ti-connectivity_20190114-2_all.deb
    bluez-firmware_1.2-4_all.deb firmware-iwlwifi_20190114-2_all.deb firmware-zd1211_1.5-6_all.deb
    dahdi-firmware-nonfree_2.11.1.0.20170917-1_all.deb firmware-ivtv_20190114-2_all.deb
    firmware-amd-graphics_20190114-2_all.deb firmware-libertas_20190114-2_all.deb hdmi2usb-fx2-firmware_0.0.0~git20151225-2_all.deb
    firmware-ath9k-htc_1.4.0-97-g75b3e59+dfsg-3_all.deb firmware-linux-free_3.4_all.deb intel-microcode_3.20190618.1_amd64.deb
    firmware-atheros_20190114-2_all.deb firmware-misc-nonfree_20190114-2_all.deb intel-microcode_3.20190618.1_i386.deb
    firmware-b43-installer_019-4_all.deb firmware-myricom_20190114-2_all.deb ixp4xx-microcode_2.4-3_armel.deb
    firmware-b43legacy-installer_019-4_all.deb firmware-netronome_20190114-2_all.deb raspi3-firmware_1.20190215-1+deb10u1_arm64.deb
    firmware-bnx2_20190114-2_all.deb firmware-netxen_20190114-2_all.deb raspi3-firmware_1.20190215-1+deb10u1_armel.deb
    firmware-bnx2x_20190114-2_all.deb firmware-qcom-media_20190114-2_all.deb raspi3-firmware_1.20190215-1+deb10u1_armhf.deb
    firmware-brcm80211_20190114-2_all.deb firmware-qlogic_20190114-2_all.deb
    firmware-cavium_20190114-2_all.deb firmware-realtek_20190114-2_all.deb

Here is a proof that at least 3 firmwares are installed from the buster repo (not from buster-backports from which the kernel was taken):
    thierry@debian-thierry:~/downloads/temp$ sudo dpkg -l firmware-linux
    Önskat=Okänd(U)/Installera(I)/Radera(R)/Rensa(P)/Håll(H)
    | Status.=Ej inst.(N)/(I)nst./Konffil.(C)/(U)ppack./Halvkonf.(F)/(H)alvinst.
    | / Vänt.utl(W)/Föresl.utl(T)
    |/ Fel?Inget(=)/Ominstallera(R)/Båda(X) (Status,Fel: versaler=illa)
    ||/ Namn Version Arkitektur Beskrivning
    +++-==============-============-============-=====================================================================
    ii firmware-linux 20190114-2 all Binary firmware for various drivers in the Linux kernel (metapackage)

    thierry@debian-thierry:~/downloads/temp$ sudo dpkg -l firmware-linux-free
    Önskat=Okänd(U)/Installera(I)/Radera(R)/Rensa(P)/Håll(H)
    | Status.=Ej inst.(N)/(I)nst./Konffil.(C)/(U)ppack./Halvkonf.(F)/(H)alvinst.
    | / Vänt.utl(W)/Föresl.utl(T)
    |/ Fel?Inget(=)/Ominstallera(R)/Båda(X) (Status,Fel: versaler=illa)
    ||/ Namn Version Arkitektur Beskrivning
    +++-===================-============-============-=======================================================
    ii firmware-linux-free 3.4 all Binary firmware for various drivers in the Linux kernel
    thierry@debian-thierry:~/downloads/temp$ sudo dpkg -l firmware-misc-nonfree
    Önskat=Okänd(U)/Installera(I)/Radera(R)/Rensa(P)/Håll(H)
    | Status.=Ej inst.(N)/(I)nst./Konffil.(C)/(U)ppack./Halvkonf.(F)/(H)alvinst.
    | / Vänt.utl(W)/Föresl.utl(T)
    |/ Fel?Inget(=)/Ominstallera(R)/Båda(X) (Status,Fel: versaler=illa)
    ||/ Namn Version Arkitektur Beskrivning
    +++-=====================-============-============-=======================================================
    ii firmware-misc-nonfree 20190114-2 all Binary firmware for various drivers in the Linux kernel

MagicPoulp
 
Posts: 393
Joined: 2018-11-05 21:30

Re: cannot boot on a newer kernel

Postby stevepusser » 2020-11-18 18:59

For those that would prefer the package that actually has the firmware files for nouveau instead of a metapackage like firmware-linux, it's "firmware-misc-nonfree".
MX Linux packager and developer
User avatar
stevepusser
 
Posts: 12132
Joined: 2009-10-06 05:53

Re: cannot boot on a newer kernel

Postby MagicPoulp » 2020-11-19 13:39

ok good to know.

Why does buster stable (4.19) works with nouveau without having to install the firmware-misc-non free package, whereas it becomes needed with a backported kernel?
MagicPoulp
 
Posts: 393
Joined: 2018-11-05 21:30

Re: cannot boot on a newer kernel

Postby CwF » 2020-11-19 15:38

Back a year or so ago in a thread here I did mention this. Before Buster went stable on earlier kernels one of my images would pause for minutes and then spit out a vga mem allocation error of some kind, then continue fine to the desktop. That was a 750Ti with nouveau and without firmware. That machine is still Stretch and will skip Buster. Newer Bullseye images are built, but haven't ran on that machine yet, it still works.

Anyway, it seems there is some conditionality somewhere to fall back to basic function without the firmware. Maybe that is missing in the backported kernels. I usually don't use backports.
CwF
 
Posts: 810
Joined: 2018-06-20 15:16

Re: cannot boot on a newer kernel

Postby stevepusser » 2020-11-19 21:22

Part of the nouveau driver is in the kernel--it's not all in xserver-xorg-video-nouveau. The same goes for the other FLOSS video drivers, such as intel or amdgpu. I would suspect that the change occurred in the kernel part of the driver.
MX Linux packager and developer
User avatar
stevepusser
 
Posts: 12132
Joined: 2009-10-06 05:53


Return to General Questions

Who is online

Users browsing this forum: No registered users and 20 guests

fashionable