Re: Current state of the Linux kernel on SPARC

John Paul Adrian Glaubitz <[email protected]>
Newsgroups gmane.linux.debian.ports.sparc
Message-ID <b966b1f705d6554b1bbdba80399f266eb12eac27.camel@physik.fu-berlin.de>
Hi Jeremy,

On Tue, 2025-09-02 at 00:38 -0400, Jeremy Leonard wrote:
> I have installed Debian on my Ultra 1 with a UltraSparc 1 CPU. This is
> the first time I've ever had any success in getting any linux distro
> installed over the past 3 years! Wow, did it take a while! 
> 
> I do have one issue I don't believe is related to the patches.

FWIW, the patches are not part of Debian yet. They have all been tested
out of tree.

> I can boot to Grub but grub fails to boot.
> 
> Can't read disk label.
> Can't open disk label package

Can you take a screenshot of this?

I would suggest raising this question on the grub-devel mailing list as
I have also observed a similar problem with QEMU.

Installing works, but booting the installed system with GRUB doesn't
work. No idea yet what the problem is.

> I'm still looking for a solution to this but haven't found it yet.
> Any pointers here would be appreciated. I did boot into the rescue
> CD from Debian and updated GRUB2 and reinstall it. That didn't seem
> to help. The partition table type on my disk is sun and I do have
> the sparc64-ieee1275 modules for grub installed.

I don't know yet. This needs to be investigated by a GRUB developer.

> Once I overcome this grub hurdle is there any process I should run to
> more thoroughly test this install? Something that would stress test
> these new patches explicitly? Are there any stats or other info from
> this system that would be helpful with validating this is working properly now?

You would need to install my test kernel first before stress-testing:

https://people.debian.org/~glaubitz/sparc64/

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.