Okay, so I have managed to build an image now, that's the good news:
> https://people.debian.org/~glaubitz/debian-10.0-sparc64-grub-NETINST-1.iso
The bad news is, it doesn't boot yet:
{0} ok boot cdrom
Boot device: /virtual-devices@100/channel-devices@200/disk@1 File and args:
ERROR:
(Leave the bug tracker, I'll close the bug)
On 4/24/19 10:43 PM, Mark Cave-Ayland wrote:
> Is it possible to see the source for sparc64-ieee1275-cdcore anywhere? A
> quick search
> doesn't return anything obvious.
The regular grub2 packaging source is on salsa, see:
Closing as the bug report is obviously invalid as bootinfo.txt is not
required on sparc and sparc64.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546
On 24/04/2019 21:30, Frank Scheiner wrote:
> On 4/24/19 22:07, John Paul Adrian Glaubitz wrote:
>> On 4/24/19 9:46 PM, Mark Cave-Ayland wrote:
>>> For reference the CHRP bootinfo.txt isn't a configuration file, but is
>>> actually
>>> parsed by CHRP-compliant open firmwares directly - SPARC
On 4/24/19 22:07, John Paul Adrian Glaubitz wrote:
> On 4/24/19 9:46 PM, Mark Cave-Ayland wrote:
>> For reference the CHRP bootinfo.txt isn't a configuration file, but is
>> actually
>> parsed by CHRP-compliant open firmwares directly - SPARC firmwares, including
>> OpenBIOS don't support them.
Source: grub2
Version: 2.02+dfsg1-17
Severity: normal
User: debian-sparc@lists.debian.org
Usertags: sparc64
Hello!
I have started working on switching the bootloader for debian-installer from
silo to grub-ieee1275 on sparc and sparc64.
For that, I have looked at the corresponding code in
On 4/24/19 9:46 PM, Mark Cave-Ayland wrote:
> For reference the CHRP bootinfo.txt isn't a configuration file, but is
> actually
> parsed by CHRP-compliant open firmwares directly - SPARC firmwares, including
> OpenBIOS don't support them. Can you explain why grub on SPARC is trying to
> access
>
On 24/04/2019 23:05, John Paul Adrian Glaubitz wrote:
> Okay, so I have managed to build an image now, that's the good news:
>
>> https://people.debian.org/~glaubitz/debian-10.0-sparc64-grub-NETINST-1.iso
>
> The bad news is, it doesn't boot yet:
>
> {0} ok boot cdrom
> Boot device:
On 25/04/2019 05:18, Mark Cave-Ayland wrote:
> On 24/04/2019 23:05, John Paul Adrian Glaubitz wrote:
>
>> Okay, so I have managed to build an image now, that's the good news:
>>
>>> https://people.debian.org/~glaubitz/debian-10.0-sparc64-grub-NETINST-1.iso
>>
>> The bad news is, it doesn't boot
On 4/25/19 6:18 AM, Mark Cave-Ayland wrote:
> FWIW I think you're pretty close here: as you say, you just need to fix the
> bits
> which set up a sun partition label and inject the bootloader. So the bit you
> need to
> re-enable to get this to work should be this:
>
> add_mkisofs_opt
On 4/25/19 7:23 AM, Mark Cave-Ayland wrote:
> Oh wait, now I see it: SILO's isofs.b also includes a mini-ISO9660 driver to
> enable
> the PROM to read from the CDROM. So given that grub on SPARC64 is already
> working for
> a disk install then this aspect should already have been solved i.e.
On 15381 March 1977, Aurelien Jarno wrote:
> It would be nice to have a bit more than 2 weeks to do all of that.
Ok. How much? Is 6 or 8 weeks better? I don't think, given how long this
is on the table already, it doesn't make much difference if its 2 or 8.
Just something thats clear defined
12 matches
Mail list logo