Bug#1032071: ARM firmware packages included in amd64 installation images

[Magnus Wallin]

> >Speaking for myself: I installed from a live image on the release day of 
> >Debian
> >12.
>
> OK, that explains it. Let's try to get this fixed before 12.1...
>
> I can see that there is already #1035382 open on the live side, let's> bump 
> the severity on that.
>
Aha, yes. Bug #1035382 seems to be the _actual_ bug for this.
Sorry if I mailed in the wrong bug report!

Bug#1032071: ARM firmware packages included in amd64 installation images

[Magnus Wallin]

> Hi Magnus, and thanks for the heads-up
>
> [ . . . ]
>
> Just because the raspi-firmware package is included on the d-i
> installation media, it shouldn't necessarily be installed on an amd64
> host. Or is this coming from live images?
>
Hi Steve!

Speaking for myself: I installed from a live image on the release day of Debian 
12.

Bug#1032071: ARM firmware packages included in amd64 installation images

[Magnus Wallin]

> Just a head's up that this is starting to affect numerous people.
> If at all possible to prioritize it would be great.
> 

Sorry: I somehow managed to not include links in my previous message.

Here below are examples of affected individuals and workarounds:
https://forums.debian.net/viewtopic.php?t=155195
https://forums.debian.net/viewtopic.php?t=154857


-- 
 Sent with Tutanota, enjoy secure & ad-free emails.

Bug#1032071: ARM firmware packages included in amd64 installation images

[Magnus Wallin]

On Wed, 5 Jul 2023 17:03:18 +0100 Steve McIntyre  wrote:
> On Mon, Feb 27, 2023 at 12:36:22PM +0100, Pascal Hambourg wrote:
> >Package: debian-cd
> >Version: 3.2.0
> >Severity: minor
> >
> >debian-bookworm-DI-alpha2-amd64-netinst.iso includes firmware packages for
> >ARM platforms:
> >
> > firmware-qcom-soc
> > firmware-samsung
> > firmware-ti-connectivity
> > raspi-firmware
> 
> Now all filtered in debian-cd unless we have an arm* architecture for
> the build.
> 
> >These packages add 34 MB to the ISO image, which is not negligible.
> >
> >Additionally, IIUC the installer only needs firmware for storage,
> >network/wireless and sound devices. It uses generic graphic drivers for
> >display so it does not need GPU firmware. The netinst image includes firmware
> >packages which do not seem to be needed by the installer:
> >
> > bluez-firmware (Bluetooth)
> > dahdi-firmware-nonfree (VoIP)
> > firmware-amd-graphics (GPU)
> > firmware-ast (GPU)
> > firmware-ivtv (MPEG codec)
> > firmware-realtek-rtl8723cs-bt (Bluetooth)
> > firmware-siano (TV receiver)
> > hdmi2usb-fx2-firmware (?)
> >
> >Among them, firmware-amd-graphics takes 12 MB.
> >Is it useful to include these packages in the netinst image ?
> >Couldn't they be downloaded from a mirror like other ordinary packages when
> >needed ?
> 
> I'm not currently filtering by build type, so I'm leaving these in.
> 
> >Note: it also includes firmware-linux-nonfree which is a meta-package not
> >containing any firmware file.
> 
> That's been fixed separately by other changes - we now check the
> contents of the firmware .debs too.
> 
> -- 
> Steve McIntyre, Cambridge, UK.st...@einval.com
> "Managing a volunteer open source project is a lot like herding
>  kittens, except the kittens randomly appear and disappear because they
>  have day jobs." -- Matt Mackall
> 
> 
> 

Just a head's up that this is starting to affect numerous people.
If at all possible to prioritize it would be great.

-- 
 Sent with Tutanota, enjoy secure & ad-free emails.

Bug#898074: linux-image-4.9.0-6-amd64: gdm3 fails to start

[Magnus Wallin]

This seems to have been solved with the most recent kernel update:
4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07)

After installing the above kernel everything again works as it should; gmd 
start without me having to ”wiggle the mouse” in order to get to the login 
screen.

Thanks to whoever fixed this issue!
--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com 

9. May 2018 23:08 by k.b...@web.de :


> I just wanted to verify that I just did not wait long enough for gdm3 to
> start. I reinstalled linux-image-4.9.0-6-amd64 and now the issue went
> away! So it seems to be some sort of race condition, whatsoever. I
> booted at least five times now without a single problem.
>
> -- 
> To unsubscribe, send mail to > 898074-unsubscr...@bugs.debian.org 
> > .

Bug#897631: Wiggling works!

[Magnus Wallin]

>This may sound like a silly request, but does GDM start up if you>wiggle the 
>mouse for a few seconds?Silly request or not, this actually works.
Tested on three different laptops (Dell, HP and Lenovo),
all running the latest kernel, and all having the same issue 
with GDM.

Would prefer a somewhat more permanent fix than, eh, ”wiggling” :)

--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com 

Bug#898074: Confirming gdm bug with kernel 4.9.0-6

[Magnus Wallin]

Confirming this bug on two different laptops (Dell and Lenovo) ; both running 
Debian 9 with kernel 4.9.0-6.

Booting from the previous kernel (4.9.0-6) works as expected (i.e. gdm starts 
in under five minutes!).

--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com 

Bug#859639:

[Magnus Wallin]

Update:
I can confirm that the solution (or workaround) provided by Uwe is working also 
on my ProBook 6450b.

First some hardware info:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated 
Graphics Controller (rev 02) (prog-if 00 [VGA controller])
    Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://tutanota.com

Bug#859639:

[Magnus Wallin]

I can confirm this bug on a HP ProBook 6450b.

The exact same thing happens as Uwe has described with kernel:
4.9.0-3-amd64

--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com