It seems that 4.0.0-2 won't build on amd64:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787004
As 3.16.7-ckt11-1 never hit Sid it seems we currently have no Sid kernel
without the ext4 corruption bug?
Also, does anyone have a link to any documentation explaining the Debian
linux-image
Could I get a link to the SVN repo the fix is in, I can't seem to find
it here:
http://anonscm.debian.org/viewvc/kernel/dists/trunk/linux/debian/
Also, could we have some clarification on the numbering as the package
tracker says linux-image-4.0.0-1-amd64 (4.0.2-1) but the package that
doesn't bu
h
MODULES=dep set we're talking 219M of space used.
So I have no choice but to rebuild with >1gb /boot, unless i can figure
out how to shrink luks / and grow /boot
--
Simon John
re and it can't be
any of:
* remove plymouth or firmware (not practical for desktop)
* make /boot bigger (not upgrade friendly)
* MODULES=dep (not effective)
As for updating the docs and installer - my bookworm stable box has two
6.1 kernels in a 471mb /boot with room for a couple more, so
--
Simon John
pt only managed the latest one.
On an nvidia+mediatek+intel+realtek system I now have:
-rw-r--r-- 1 root root 108M Jul 25 00:15 initrd.img-6.9.10-amd64
-rw-r--r-- 1 root root 108M Jul 25 00:15 initrd.img-6.9.9-amd64
Thanks!
--
Simon John
ad suggesting a couple of
bugs that have fixes upstream:
https://www.reddit.com/r/VFIO/comments/glfgqs/qemu_5_vfio_no_longer_works_on_debian/
I'm using macos catalina and win10 guests to reproduce the issue, and
using Intel not AMD chips.
Cheers.
--
Simon John
On Wed, 27 May 2020 21:31:46 +0200 Salvatore Bonaccorso
wrote:
Source: linux
Version: 5.6.7-1
Control: submitter -1 deb...@the-jedi.co.uk
Forwarding this report as bug in the BTS.
On Mon, May 25, 2020 at 09:03:43PM +0100, Simon John wrote:
> Sorry to email directly but I've tried r
been looked at or is 5.7 due soon?
Regards.
--
Simon John
from snapshot.debian.org which works fine.
Regards.
--
Simon John
illa.redhat.com/show_bug.cgi?id=1038929
kvm-pit seemed to be eating a lot of cpu, qemu went defunct, macos guest
got a little further into its boot sequence.
Can we upgrade this bug so it gets some visibility, that's two major
kernel versions its not been fixed in now, let alone commented on.
--
Simon John
This looks a likely culprit:
https://bugzilla.kernel.org/show_bug.cgi?id=207489
--
Simon John
On Sun, 28 Jun 2020 10:41:41 +0200 Salvatore Bonaccorso
wrote:
Hi Simon,
Hi Salvatore, thanks for looking into this.
On Sun, Jun 28, 2020 at 01:01:01AM +0100, Simon John wrote:
> This looks a likely culprit:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=207489
The issue you a
/766043a69c76308f84cfa14b3f3a924f
Regards.
--
Simon John
Where would I look for some follow-up on this - upstream kernel.org?
--
Simon John
ntly, so i assume the guest didn't even start.
regards.
--
Simon John
Ah no, turns out I had disabled the gpu passthrough, when i re-enabled
it i just got a kernel panic from 5.8.0-rc5
On 19/07/2020 00:34, Simon John wrote:
I tried mainline 5.8.0-rc5 and I couldn't even get into gnome shell
after the gdm3 password prompt, just a black screen!
I tried ru
x27;t seem to use.
Regards.
--
Simon John
17 matches
Mail list logo
