Control: reassign 1049448 raspi-firmware
thanks
Hello Paul and slimshady,
I'm reassigning this bug to raspi-firmware, as it relates to an already known
issue; the fix has been uploaded already for several weeks in unstable+testing,
but I will now prepare an upload for stable as well.
I'll
Hi!
Diederik de Haas dijo [Tue, Jan 31, 2023 at 10:33:41PM +0100]:
> > Would they fit into a separate source package not associated with
> > raspi-config?
>
> I do strongly think they do not belong in the raspi-firmware package for the
> reason I retitled this bug and retitled my response
Vincent Blut dijo [Thu, Oct 06, 2022 at 12:48:58PM +0200]:
> > > Specifically, the required configuration options to enable all of its
> > > features are:
> > >CONFIG_INTEL_IDXD=m
> > >CONFIG_INTEL_IDXD_SVM=y
> >
> > Is this only applicable for the amd64 architecture or is it useful for
Package: linux-image-5.19.0-2-amd64
Severity: normal
X-Debbugs-Cc: jair.de.jesus.gonzalez.plascen...@intel.com,
miguel.bernal.ma...@intel.com
Hello,
I was recently approached by Intel engineers Jair de Jesús Gonzalez
Plascencia and Miguel Bernal Marín, both Cc:ed here. They asked me for
help to
Please note I'm currenlty shipping the required files in
raspi-firmware -- I believe their right place is in
firmware-brcm80211, so please just ping me (or better, raise a bug on
raspi-firmware) whent they are added to this package.
Thanks!
Package: firmware-brcm80211
Version: 20210818-1
Severity: normal
Tags: newcomer
The Raspberry Pi p400 is very similar to the 4 family, but the Wifi
chip is a slightly different model, and is thus not recognized when
running with Debian, not even with firmware-brcm80211.
We need the addition of
Control: Severity -1 normal
Ben Hutchings dijo [Fri, Apr 16, 2021 at 03:07:48PM +0200]:
> > During the boot process of the Raspberry Pi models 4 (4 and 8GB) and
> > p400, the console starts working correctly, but as the vc4 video gets
> > initialized, the console gets corrupted.
> [...]
>
> This
Control: notfound -1 5.9.15-1
Control: found -1 5.10.4-1
Marking two adjacent kernel versions where the breakage first appeared.
found 986863 5.10.0-6-arm64
notfound 986863 5.8.0-3-arm64
thanks
I blacklisted the vc4 module, and the console works reliably again, so
that's a way to get a working system. I will blacklist in the images I
produce, but this should not be needed for users to know!
I am also trying with a kernel
Philip Rinn dijo [Thu, Sep 10, 2020 at 12:09:29PM +0200]:
> Hi Gunnar,
>
> thanks for testing - but your message leaves me a little confused. You claim,
> the
> bug is fixed but you say
>
> > we have used only regular linux-image-armmp kernels (and have no
> > reason to suppose -lpae is
fixed 820622 4.19.132-1
thanks
Hello,
I have not seen this message appear in my RPi2, using stock Debian
kernels starting at 4.19 (even a bit before that, I think). I do not
use the LPAE kernel, as I understand it does not make much sense in
the RPi2 (sold only with 1GB RAM, and not expandable),
fixed 941597 5.7.17-1
thanks
I have some RPi3B+ using the arm64 Linuxkernel at version 5.7
(currently in testing), and they both shutdown and reboot reliably. I
believe this bug can now be closed.
signature.asc
Description: PGP signature
fixed 878332 4.19.132-1
fixed 878332 5.7.17-1
thanks
Hello,
This bug is no longer present in kernels shipped in Debian stable /
testing / unstable. Do note, though, that the Raspberry Pi 2 is sold
with 1GB RAM only and cannot be upgraded, and thus has no use for
LPAE, we have used only regular
Hi,
Just adding some info to this bug, for whoever stumbles upon it - I
just got a new HP laptop (HP Pavillion X360, 14", specific model
14-cd0004la) with this same wifi chip. I was able to install and use
the (very not official, run at your own risk!) drivers available at
Hi,
This bug is being added as several users (me included) have required
this information from the (unofficial) Raspberry Pi Debian "clean"
image.
There is a great number of devices with similar format, allowing for
GPIO communications, that would benefit from having SPIDEV enabled in
our
Cyril Brulebois dijo [Tue, Dec 25, 2012 at 04:35:58PM +0100]:
Right, that seems to be the case — Sorry for submitting a duplicate;
merging. I hope this can be fixed before the release.
unless we reach a number of duplicates counted on 2 digits, I'm happy
to have some of them. ;)
The
As a temporary workaround, or in case this is of any value: Logging in
from a second computer to the affected one allows you to:
- /etc/init.d/gdm stop
- Launch X and kill it (Ctrl-C)
- /etc/init.d/gdm start
And this time it works properly.
--
Gunnar Wolf • gw...@gwolf.org • (+52-55)5623-0154
17 matches
Mail list logo
