Re: Salix Xfce 15.0alpha2
Posted: 17. Apr 2022, 09:15
https://people.salixos.org/djemos/salix ... ilo.gr.pnggapan wrote: I just tried it and can't see the problem.
https://people.salixos.org/djemos/salix ... ilo.gr.pnggapan wrote: I just tried it and can't see the problem.
Thanks ibka. I'm not really sure what's different in my systems here and it works.ibka wrote: ↑17. Apr 2022, 07:31Installation on a 64-bit computer
CPU: Intel Core i7-4770 @ 3.40GHz x 8
RAM: 7,6 GiB
GPU: Intel HD Graphics 4600 (1,5GiB)
* 64-bit ISO
* Bios
* Swedish
* Full installation
I have installed all updates that exists.
I have installed Swedish language for libreoffice
I have installed the Whisker menu
I haven't used the command line tool, it was the gtkhostsetup i used
I don't know what more information i can give you that could help, if you have any idea of what information you need let me know.
Code: Select all
sudo hostname newhostname
Code: Select all
sudo hostname oldhostname
I confirm. After change the hostname on gtkhostsetup cannot run any application.ibka wrote:I haven't used the command line tool, it was the gtkhostsetup i used
This is true and prove the worth of salix. From my experience all these years and from users i have contacted by email all over the world, you cannot imagine how useful is salix xfce for people who have old laptop and for their own reasons do not want to take a new one.gapan wrote:Sidenote: 15.0alpha2 runs amazingly well on this old netbook with its extremely underpowered by todays standards Atom N270 CPU, 1GB RAM and 4GB system partition. I'm posting this from it using netsurf. Everything is snappy and RAM consumption is about 200M right now. I made a few tweeks to the iso before installing though, by removing some huge packages like firefox, llvm, vulkan_sdk and gcc, otherwise even Basic mode wouldn't fit in 4GB. I even removed all the locales I don't need after installation and now it's sitting at a comfortable 1GB free drive.
I believe that this means that efibootmgr was unable to install a boot menu item in the EFI nvm. This was confirmed when you found that there was no entry for refinding when booting. The refind install script tries to do two things using efibootmgr. The first is to install a boot menu entry for refind and the second is to make the refind boot entry the first boot option. In your case, it doesn't appear to be able to install the boot menu entry.mimosa wrote: ↑17. Apr 2022, 07:45Installing it!
ALERT: There were problems running the efibootmgr program! You may need to
rename the refind_x64.efi binary to the default name (EFI/BOOT/bootx64.efi
on x86-64 systems, EFI/BOOT/bootia32.efi on x86 systems, or
EFI/BOOT/bootaa64.efi on ARM64 systems) to have it run!
Code: Select all
$ sudo efibootmgr -c -d /dev/sd<disk> -p <partition> -L rEFInd Boot Manager -l \EFI\refind\refind_x64.efi
Renaming the refind binary, in this case, will not help since there is no boot menu entry that points to the /EFI/refind/ directory. The EFI/BOOT/bootx64.efi is a fallback. When booting if all the boot menu entries fail to boot, the EFI boot manager tries to boot EFI/BOOT/bootx64.efi binary as the last gasp. However, since you already have working boot options it will never default to this unless you make it the first boot option.mimosa wrote: ↑17. Apr 2022, 07:45 I tried renaming /boot/efi/EFI/refind/refind_x64.efi both as suggested, and also as elilo.efi, which is what's in the other directories.The only thing I haven't tried is that path EFI/BOOT which has got to be wrong!Code: Select all
mimosa[~]$ ls /boot/efi/EFI/refind/ boot64.efi drivers_x64 elilo.efi icons keys refind.conf refind_x64.efi tools_x64 mimosa[~]$ ls /boot/efi/EFI/Salix-Xfce-15.0/ elilo.conf elilo.efi vmlinuz
Code: Select all
#/bin/bash
CURRENT=`hostname`
gtkhostsetup
hostname $CURRENT
Code: Select all
sudo chmod +x myscript
Code: Select all
sudo ./myscript
Code: Select all
(gtkhostsetup:12043): dbind-WARNING **: 17:33:42.470: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-Etv6ye89dK: No such file or directory
Thanks laprjns, that did it!laprjns wrote: ↑17. Apr 2022, 13:07
You could try manually installing a boot entry item using efibootmgr in a terminal.If successful, then the refind boot menu entry will be added as the first boot option.Code: Select all
$ sudo efibootmgr -c -d /dev/sd<disk> -p <partition> -L rEFInd Boot Manager -l \EFI\refind\refind_x64.efi
Code: Select all
mimosa[~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
[....]
nvme0n1 259:0 0 232.9G 0 disk
├─nvme0n1p1 259:1 0 954M 0 part /boot/efi
├─nvme0n1p2 259:2 0 36.6G 0 part
├─nvme0n1p3 259:3 0 46.5G 0 part
├─nvme0n1p4 259:4 0 44.9G 0 part /
└─nvme0n1p5 259:5 0 102.2G 0 part
Code: Select all
sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -L rEFInd Boot Manager -l \EFI/refind/refind_x64.efi