Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.boot > #75630 > unrolled thread
| Started by | Cyril Brulebois <kibi@debian.org> |
|---|---|
| First post | 2025-06-23 12:40 +0200 |
| Last post | 2025-06-29 18:00 +0200 |
| Articles | 6 — 2 participants |
Back to article view | Back to linux.debian.maint.boot
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Trixie RC1 error: init of i915 and HDMI codec failed Cyril Brulebois <kibi@debian.org> - 2025-06-23 12:40 +0200
Re: Trixie RC1 error: init of i915 and HDMI codec failed Cyril Brulebois <kibi@debian.org> - 2025-06-23 16:00 +0200
Re: Trixie RC1 error: init of i915 and HDMI codec failed Cyril Brulebois <kibi@debian.org> - 2025-06-23 16:20 +0200
Re: Trixie RC1 error: init of i915 and HDMI codec failed Cyril Brulebois <kibi@debian.org> - 2025-06-23 16:50 +0200
Re: Trixie RC1 error: init of i915 and HDMI codec failed Pascal Hambourg <pascal@plouf.fr.eu.org> - 2025-06-23 17:40 +0200
Re: Trixie RC1 error: init of i915 and HDMI codec failed Cyril Brulebois <kibi@debian.org> - 2025-06-29 18:00 +0200
| From | Cyril Brulebois <kibi@debian.org> |
|---|---|
| Date | 2025-06-23 12:40 +0200 |
| Subject | Re: Trixie RC1 error: init of i915 and HDMI codec failed |
| Message-ID | <L0MKJ-czs0-3@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi, john doe <johndoe65534@mail.com> (2025-06-23): > I'm seeing the below MSG when installing Trixie RC1 ([1]): > > Jun 22 14:17:10 kernel: [ 14.104424] pci 0000:00:1f.3: deferred probe > pending: sof-audio-pci-intel-mtl: init of i915 and HDMI codec failed If you're interested in speech synthesis (which isn't clear from your message), you can try this image: https://people.debian.org/~kibi/bug-1092977+intel/debian-13.0.0-amd64-NETINST-1+depmod+efd.iso Otherwise, that isn't an issue? > Is RC2 better on that front or should I provide more debug logs? There's no such thing, yet. Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
[toc] | [next] | [standalone]
| From | Cyril Brulebois <kibi@debian.org> |
|---|---|
| Date | 2025-06-23 16:00 +0200 |
| Message-ID | <L0PSh-cBil-5@gated-at.bofh.it> |
| In reply to | #75630 |
[Multipart message — attachments visible in raw view] — view raw
john doe <johndoe65534@mail.com> (2025-06-23): > It's giving me a kernel missmatch error and missing png file! ;^) Right, time flies. > > Otherwise, that isn't an issue? > > Why not? You quoted a log line. You haven't explained what the problem you're actually facing is. Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
[toc] | [prev] | [next] | [standalone]
| From | Cyril Brulebois <kibi@debian.org> |
|---|---|
| Date | 2025-06-23 16:20 +0200 |
| Message-ID | <L0QbD-cBF8-5@gated-at.bofh.it> |
| In reply to | #75635 |
[Multipart message — attachments visible in raw view] — view raw
john doe <johndoe65534@mail.com> (2025-06-23): > I would like to ensure that when Trixie is released I'll be able to install > Trixie with speech and not to have to grab a specific iso put together for > a bug. You could have mentioned this from the get-go, nobody can read your mind. Anyway, besides kernel/module mismatch, does speech synthesis start with the image I linked to? Having people test and report what's happening with such temporary images is how we make informed decisions regarding what to merge, and whether bug fixes or workaround are effective… Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
[toc] | [prev] | [next] | [standalone]
| From | Cyril Brulebois <kibi@debian.org> |
|---|---|
| Date | 2025-06-23 16:50 +0200 |
| Message-ID | <L0QEF-cBOU-1@gated-at.bofh.it> |
| In reply to | #75637 |
[Multipart message — attachments visible in raw view] — view raw
john doe <johndoe65534@mail.com> (2025-06-23):
> https://people.debian.org/~kibi/bug-1092977+intel/debian-13.0.0-amd64-NETINST-1+depmod+efd.iso
> when I select "Install with speech synthesis":
> - Invalid magic number
> - You need to load the kernel first , press any key to continue
> - PNG: not a png file
>
> Unless you did a new iso or I missed something else the answer is no
> because I'm blocked at the second error!
>
> Basically, I'm in a lloop between what to select and the above errors!
OK, thanks for the explanation.
There was no new ISO, I'm not publishing different things under the same
name (this could be very confusing!).
I cannot reproduce this issue with a brand new download of this image,
starting it under QEMU, with `-audio driver=pa,model=ac97` to verify the
speech synthesis kicks in. This is a BIOS boot by default.
Trying the same with OVMF firmware (meaning a UEFI boot, under Secure
Boot), the speech synthesis also starts fine.
Are you trying the image under some virtualization tool, or on real
hardware? If the latter, are you using some USB device? If so, how did
you copy the installation image onto it?
Just in case there was an issue during the download, here's the sha512
checksum:
3759594bd2bbb3b2d8381ba6ca8bc2b9fa37706edc9112a9e404b4a6649850b24f7a92213f258bf57b2e24a95f00dc24734c324ab5e900d0683705c59ac054f5 debian-13.0.0-amd64-NETINST-1+depmod+efd.iso
Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
[toc] | [prev] | [next] | [standalone]
| From | Pascal Hambourg <pascal@plouf.fr.eu.org> |
|---|---|
| Date | 2025-06-23 17:40 +0200 |
| Message-ID | <L0Rr3-cClf-1@gated-at.bofh.it> |
| In reply to | #75638 |
On 23/06/2025 at 17:13, john doe wrote: >>> when I select "Install with speech synthesis": >>> - Invalid magic number >>> - You need to load the kernel first , press any key to continue >>> - PNG: not a png file GRUB says vmlinuz is not a valid kernel image and the background image file is not a valid PNG file. This really looks like a corrupted installation media. > I did a cp command (`cp <SRC> <DEST>`) to copy the iso onto a USB key. Was any filesystem on the USB key mounted during the copy ? This can cause data corruption. > I'll reformat the USB key and use the dd CMD to give it an other shot > and maybe fire up a VM to confirm that the image is not corrupted. No need to use dd, cp should work fine assuming that the USB key is not in use. >> Just in case there was an issue during the download, here's the sha512 >> checksum: (...) > We have a checksum match! ;^) With the ISO image or the USB key ? If with the ISO image, you can compare it with the USB key contents : cmp image.iso /dev/usbkey (It is almost the same command as for the copy with cp, I use them both in a row) If there is no difference it should exit with a message saying it reached the end of the ISO image.
[toc] | [prev] | [next] | [standalone]
| From | Cyril Brulebois <kibi@debian.org> |
|---|---|
| Date | 2025-06-29 18:00 +0200 |
| Message-ID | <L32BH-e2ao-1@gated-at.bofh.it> |
| In reply to | #75637 |
[Multipart message — attachments visible in raw view] — view raw
john doe <johndoe65534@mail.com> (2025-06-24): > I can confirm that the image you linked to is talking back to me!!! ;^) Great, thanks. > Do you have any ETA on when I could get a netboot gtk image with those > changes included? I have just cleaned up the WIP I stashed in a branch, and merged it into master. The resulting netboot/gtk/mini.iso on amd64 is still letting me load i915.ko successfully. Manually-triggered daily builds are running on all relevant archs, which should make [1] replicate the local results, and let you play with it, and make sure any FTBFSes elsewhere are detected and can be tackled. 1. https://d-i.debian.org/daily-images/amd64/ Building and publishing should happen within a few hours. Of course, if firmware files are needed, the mini.iso won't help much, and you'll need to wait until the updated daily builds tickle down into net*inst* images[2], which should be a few more hours away. 2. https://cdimage.debian.org/cdimage/weekly-builds/amd64/ Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.boot
csiph-web