On 2024-04-17 16:37 +0200, Steffen Grunewald wrote:
> On Mon, 2024-04-15 at 14:55:06 +0800, Paul Wise wrote:
> > On Fri, 2024-04-12 at 09:28 +0200, Steffen Grunewald wrote:
> >
> > > Any attempt to boot a Bullseye (5.x) or Bookworm kernel (6.x) resulted in
> > > an early kernel panic.
> That's
On Wed, Apr 17, 2024 at 04:37:50PM +0200, Steffen Grunewald wrote:
> On Mon, 2024-04-15 at 14:55:06 +0800, Paul Wise wrote:
> > On Fri, 2024-04-12 at 09:28 +0200, Steffen Grunewald wrote:
> >
> > > Any attempt to boot a Bullseye (5.x) or Bookworm kernel (6.x) resulted in
> > > an early kernel
On Mon, 2024-04-15 at 14:55:06 +0800, Paul Wise wrote:
> On Fri, 2024-04-12 at 09:28 +0200, Steffen Grunewald wrote:
>
> > Any attempt to boot a Bullseye (5.x) or Bookworm kernel (6.x) resulted in
> > an early kernel panic.
>
> Try the latest sid kernel (6.7.9) and the latest upstream too.
On Fri, 2024-04-12 at 09:28 +0200, Steffen Grunewald wrote:
> Upgrading to Debian Buster was successful, the current kernel is 4.19.0-25
> aka 4.19.289-2. (It doesn't even properly identify the CPU, only gives a
> BogoMIPS value of 200.00.)
>
> Any attempt to boot a Bullseye (5.x) or Bookworm
Good morning,
I beg your pardon if this problem has been discussed before, but I couldn't
find anything useful in the list archives.
We've been operating a Gigabyte R120-T35-00 (Mainboard model MT30-GS2-00)
equipped with a Cavium ThunderX (CN8880) 32-core processor, for several
years now.
It was
5 matches
Mail list logo
