Re: Updated installer images
On 09/11/2017 11:23 AM, Frank Scheiner wrote: On 09/10/2017 07:42 PM, John Paul Adrian Glaubitz wrote: On 09/10/2017 06:32 PM, Frank Scheiner wrote: I yesterday tested the image from [1] (SHA256: b07736dfa5bd167352d8f17f1d9bfc62fa9762f5496d0d134801b91f80bfb6b4) on an Ultra 10. Sadly the boot loader installation still didn't work. Unfortunately I also forgot to go back and check the available menu items before finishing up the installation without boot loader installation. I could later on install the boot loader manually via the rescue mode, so a workaround is still possible with the current image. Can you please re-run the installation and save the installation log from /var/log/syslog? I can't really work on this problem if I don't have any debug logs. Ok, I have two syslog files at hand (see attachments). One before finishing up at the "nobootloader" step and one when the installation was finished. Hope this helps. I forgot to mention that this time the installer correctly detected the installed ATA disk. So maybe it didn't detect it last time because of the original partitioning. This time I already had a Sun disklabel and the partitions from the last try on it.
Re: Updated installer images
On 09/10/2017 07:42 PM, John Paul Adrian Glaubitz wrote: On 09/10/2017 06:32 PM, Frank Scheiner wrote: I yesterday tested the image from [1] (SHA256: b07736dfa5bd167352d8f17f1d9bfc62fa9762f5496d0d134801b91f80bfb6b4) on an Ultra 10. Sadly the boot loader installation still didn't work. Unfortunately I also forgot to go back and check the available menu items before finishing up the installation without boot loader installation. I could later on install the boot loader manually via the rescue mode, so a workaround is still possible with the current image. Can you please re-run the installation and save the installation log from /var/log/syslog? I can't really work on this problem if I don't have any debug logs. Ok, I have two syslog files at hand (see attachments). One before finishing up at the "nobootloader" step and one when the installation was finished. Hope this helps. You could try installing "silo-installer" using "anna install silo-installer" after switching to a terminal using Alt+Fn keys. Did that: ``` ~ # anna install silo-installer CAPB backup GET anna/retriever ~ # echo $? 0 ``` ...but it looked like it hang after the "CAPB backup" message. Hitting the Enter key it emitted the "GET [...]" message and exited. Although it exited with 0 I don't think it worked and the installer menu also didn't change. I believe these are the relevant lines from the syslog (happened after finishing the installation so not included in the above mentioned logs): ``` Sep 10 18:50:50 main-menu[192]: INFO: Menu item 'di-utils-shell' selected Sep 10 18:52:06 anna[7511]: sh: Sep 10 18:52:06 anna[7511]: /usr/lib/debian-installer/retriever/: Permission denied Sep 10 18:52:06 anna[7511]: Sep 10 18:52:06 anna[7511]: sh: Sep 10 18:52:06 anna[7511]: /usr/lib/debian-installer/retriever/: Permission denied Sep 10 18:52:06 anna[7511]: ``` I later also tried `anna-install silo-installer` but that also didn't change anything on the installer menu, the corresponding log entry is most likely this one: ``` Sep 10 18:55:54 anna-install: Installing silo-installer ``` Cheers, Frank syslog-after-installation-finished.gz Description: application/gzip syslog-before-finishing-up.gz Description: application/gzip
Re: Updated installer images
Hi John. Thanks a lot for these images for alpha, I will be trying them soon probably, as I was unlucky with some previous ones. :) Thanks. 2017-09-10 21:35 GMT+02:00 Anatoly Pugachev : > On Sun, Sep 10, 2017 at 10:12 PM, Christoph Biedl > wrote: > > John Paul Adrian Glaubitz wrote... > > > >> Please test and report back on the individual architecture > >> mailing lists > > > > So far, the ride for ppc64 has been *extremely* painful. This is not > > necessarly due to your efforts, but it feels a lot like nobody ever has > > tried to set up Debian on a G5 using netboot. > > > > So far (might be incomplete, and I'm both tired and fairly upset): > > > > * Any reasonable documentation on this anywhere? No about how to set up > > DHCP/TFTP server, I've done this many time. But what about which files > > are needed, and how to provide a netboot-adjusted yaboot.conf, and > > mostly: How to make yaboot make using it? > > > > * The OF bootloader needs two rounds to load yaboot. > > > > * yaboot should either get a decent on-line help or see bitrot. > > > > * yaboot's "conf /path/to/config" command, when initially using netboot, > > happiliy ignores the file name but retrieves 01-xx-yy-xx-yy-xx-yy > > using TFTP instead. > > > > * After a lot of trickery, the installer's vmlinux now gets loaded. At a > > whopping 6 kbyte/sec (yes: six kilobytes). Just to remind you, kernel > > and initrd take some 35 megabytes, and the G5 has already turned to > > airplane mode. My neighbors will love me. > > > > This isn't getting anywhere useful soon. > > I was able to install netboot sparc64 ldom (but not latest sid version > , which is too big to load by OBP. There's also #645657 debian bug, > but somehow it got closed). > > Also, installed ppc64 LPAR, failed to install yaboot and using grub2 > on Power8 server, but that installation wasn't netboot, but usual > iso/cdrom install. > > I could probably try to install test ppc64 lpar with netboot just to > check how it will go, but i need to know where do i get netboot image, > since https://cdimage.debian.org/cdimage/ports/ does not have netboot > images. > > Thanks > > -- Witold Baryluk My PGP keys for 2017-02-17 - 2019-02-17: 5B8C 48CB 8B2F CF53 CA55 0995 16D9 6FA2 20A8 F130 https://functor.xyz/pgp/witold.baryluk-gmail.gpg.asc https://keys.mailvelope.com/pks/lookup?op=get&search=0x16D96FA220A8F130