Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #246283 > unrolled thread

Errors scrolling on boot

Back to article view | Back to linux.debian.user

Contents

  Errors scrolling on boot James Allsopp <jamesaallsopp@googlemail.com> - 2022-03-13 23:20 +0100
    Re: Errors scrolling on boot "Andrew M.A. Cater" <amacater@einval.com> - 2022-03-13 23:20 +0100
      Re: Errors scrolling on boot Charles Curley <charlescurley@charlescurley.com> - 2022-03-13 23:50 +0100
        Re: Errors scrolling on boot James Allsopp <jamesaallsopp@googlemail.com> - 2022-03-14 00:10 +0100
          Re: Errors scrolling on boot Charles Curley <charlescurley@charlescurley.com> - 2022-03-14 02:30 +0100

#246283 — Errors scrolling on boot

[Multipart message — attachments visible in raw view] — view raw

Hi,
I've just upgraded my system to Bullseye and run into a problem on reboot.

I'm just getting an error, endlessly:
[timestamp] Bluetooth: hci0: Reading Intel version information failed (-22)
[timestamp] Bluetooth: hci0:

There's an iwlwifi*.ucode error near the start but everything gets
overwhelmed with the Bluetooth errors.

I can't make these messages stop, and the system won't boot to a gui,
although I can log in as root. It's very hard to use. I really need an "OK,
I get it!" option so I can work on the machine. I've managed to stop
Bluetooth as a service, but still get these errors on reboot. The cards are
part of the MSI x570S motherboard, so I can't disconnect them to get a
working system.

Any ideas? I'm thinking I might have to chroot and use isenkram?
Thanks
James

[toc] | [next] | [standalone]

#246284

On Sun, Mar 13, 2022 at 10:10:40PM +0000, James Allsopp wrote:
> Hi,
> I've just upgraded my system to Bullseye and run into a problem on reboot.
> 
> I'm just getting an error, endlessly:
> [timestamp] Bluetooth: hci0: Reading Intel version information failed (-22)
> [timestamp] Bluetooth: hci0:
> 
> There's an iwlwifi*.ucode error near the start but everything gets
> overwhelmed with the Bluetooth errors.
> 
> I can't make these messages stop, and the system won't boot to a gui,
> although I can log in as root. It's very hard to use. I really need an "OK,
> I get it!" option so I can work on the machine. I've managed to stop
> Bluetooth as a service, but still get these errors on reboot. The cards are
> part of the MSI x570S motherboard, so I can't disconnect them to get a
> working system.
> 
> Any ideas? I'm thinking I might have to chroot and use isenkram?
> Thanks
> James

James,

If you used the official media without firmware: add contrib and non-free
to your /etc/apt/sources.list and try and install the firmware / boot with
the unofficial non-free .iso, use this as rescue medium and install the 
appropriate non-free firmware you may need.

If all else fails, give us more details of your system to help us debug
for you :)

All the very best, as ever,

Andy Cater

[toc] | [prev] | [next] | [standalone]

#246286

On Sun, 13 Mar 2022 22:16:46 +0000
"Andrew M.A. Cater" <amacater@einval.com> wrote:

> If you used the official media without firmware: add contrib and
> non-free to your /etc/apt/sources.list and try and install the
> firmware / boot with the unofficial non-free .iso, use this as rescue
> medium and install the appropriate non-free firmware you may need.

That sounds like an Intel wifi adapter. You may want the firmware
package firmware-iwlwifi.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#246289

[Multipart message — attachments visible in raw view] — view raw

Hi,
I found dmesg -D which stopped the errors scrolling but I can't find the
problem in the logs, or why it's not booting further. Would not having
these firmwares installed prevent the boot continuing? I'd understand that
I wouldn't have any wireless, but I've a very old usb dongle that will work.

The problem I have is that I also have var mounted as zfs, but that's not
mounting properly and I can't tell whether it's the upgrade stopping zfs
working or the firmwares stopping the boot before then.

dmesg isn't that informative and neither is journalctl -xe, unfortunately I
can't copy either.

Thanks
James

Would

On Sun, 13 Mar 2022 at 22:44, Charles Curley <
charlescurley@charlescurley.com> wrote:

> On Sun, 13 Mar 2022 22:16:46 +0000
> "Andrew M.A. Cater" <amacater@einval.com> wrote:
>
> > If you used the official media without firmware: add contrib and
> > non-free to your /etc/apt/sources.list and try and install the
> > firmware / boot with the unofficial non-free .iso, use this as rescue
> > medium and install the appropriate non-free firmware you may need.
>
> That sounds like an Intel wifi adapter. You may want the firmware
> package firmware-iwlwifi.
>
> --
> Does anybody read signatures any more?
>
> https://charlescurley.com
> https://charlescurley.com/blog/
>
>

[toc] | [prev] | [next] | [standalone]

#246295

On Sun, 13 Mar 2022 23:04:02 +0000
James Allsopp <jamesaallsopp@googlemail.com> wrote:

> Hi,
> I found dmesg -D which stopped the errors scrolling but I can't find
> the problem in the logs, or why it's not booting further.

Can you show us the last 40 lines or so of syslog where it stops
booting?

> Would not
> having these firmwares installed prevent the boot continuing?

Firmware for wifi, probably not. You just wouldn't get a network
connection.

> I'd
> understand that I wouldn't have any wireless, but I've a very old usb
> dongle that will work.

At least with the dongle you should be able to install firmware
packages to test them, copy log files to another computer so you can
email snippits to the list.


> 
> The problem I have is that I also have var mounted as zfs, but that's
> not mounting properly and I can't tell whether it's the upgrade
> stopping zfs working or the firmwares stopping the boot before then.

Now you tell us! Again, we'll need to see actual error messages, such
as log entries.

> 
> dmesg isn't that informative and neither is journalctl -xe,
> unfortunately I can't copy either.

You found the iwlwifi* error. Is that not in syslog or dmesg?

See above on the USB dongle.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web