I originally tried UEFI boot.

The grub-install didn't work there either, and I was not able to boot from command mode,

so I switched from UEFI/GPT to BIOS/MBR.

The grub-install still doesn't work, but at least I am able to boot from command mode.

For the grub-install, I wasn't using the --bootloader-id option, so I will give that a try.

Best regards,

Dave

On Wednesday, July 1, 2020, 07:45:13 AM CDT, Hans Bezemer <hbezemer@kliksafe.nl> wrote:

On 20/07/01 02:22AM, david mccooey wrote:
> Hello,
> I am installing CRUX 3.5 on a new computer.
> I started with the ISO on a USB stick, and installed onto a SSD drive.
> The grub2 installation didn't work for some reason, but I managed to boot Linux on the SSD drive using the grub command line.
I had the same problem for a uefi boot (assuming that you have a uefi boot also).
When using:
grub-install --target=x86_64-efi --efi-directory=<path/to/efi/dir> --bootloader-id=GRUB
followed by:
grub-mkconfig -o /boot/grub/grub.cfg
It worked.

Regards,

Hans

> Now I am trying to bring my ports structure up to date.
> When I type "ports -u", it says "Updating file list from crux.nu::ports/crux-3.5/core/", and hangs there for several minutes.
> It fails with the following messages:
> rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110)rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]Error: Running rsync failed ()Updating failed
> It then tries to get "opt" and "xorg", but they time out as well with the same messages.
>
> From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
> Any help would be appreciated.
> Thank you,
> Dave

> _______________________________________________
> CRUX mailing list
> CRUX@lists.crux.nu
> https://lists.crux.nu/mailman/listinfo/crux

_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
https://lists.crux.nu/mailman/listinfo/crux