----------------------------------------------------------------------------------
@MSGID: <slrnuekq8g.h6j.lars@deadbadger.twente.arpa>
c570d8a2
@REPLY: <slrnuek6q5.eeq.maus@deb2.org> 09e526f0
@REPLYADDR Lars van Maanen
<lars@deadbadger.twente.arpa>
@REPLYTO 2:5075/128 Lars van Maanen
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-Id:
<slrnuekq8g.h6j.lars@deadbadger.twente.arpa>
@RFC-References: 2@dont-email.me>
<slrnuek6q5.eeq.maus@deb2.org>
@TZUTC: 0000
@PID: slrn/1.0.3 (Linux)
@TID: FIDOGATE-5.12-ge4e8b94
On 2023-08-26, maus <
maus@deb2.org> wrote:
> On 2023-07-27, CBM64 <
amiga1000@commodore.com> wrote:
>>
>> Good morning. i have a hp elitebook 104 g1 and i would like to install
>> slack 15. i succeed, but then the boot does not work. I have to choose
>> "f9" at startup and point to the file located in the /efi/ directory ....
>> in this way I start the system. Is there a way to by_pass this hassle?
>> ultimately how do you install slack 15 on hp elitebook 104 g1 ?
>> Thank you
> trying to install slack this evening, mounting the disk that the
> slackware64 is on resulted in "Out of memory"
Regarding CBM64`s problem, I might have a solution, or at least a
workaround:
First, you should try to manually create the boot entry using
`efibootmgr`. If this fails (I had this habitually happen to me on
an HP Elitebook 2560p), then you should rename the bootloader efi
file to "bootx64.efi" and place it in a directory named "BOOT" (I
am not sure if the capitalization matters) on the root of the EFI
partition. This is a fallback option that should always work (it
does for me), even when the UEFI system`s NVRAM is unwritable.
Regarding maus`s problem, I don`t have a clue.
--- slrn/1.0.3 (Linux)
* Origin: Usenet.Farm (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441