Re: x86_64_RC1 full install CD not booting
by Sanjay Mysore
Attached screen shots...bounced back
On Sun, 24 May 2020, 8:09 pm Sanjay Mysore, <sanjmys(a)gmail.com> wrote:
> Pl. see the attached file. Libreboot options shown..Adelie Rc1 or beta4
> cannot be booted by any of these options...
> Since AdelieLinux is about free software, pl. make it work with libreboot
>
> On Sat, 23 May 2020 at 23:22, Sanjay Mysore <sanjmys(a)gmail.com> wrote:
>
>> Mr. Reeves
>> You are right in that it was not booting only on libreboot. On my friends
>> machine with BIOS, it booted. Sorry....
>> Yet, after booting, it asks if you want to install or play around, i.e
>> live. When I select live, it falls into a zsh shell.
>> I am familiar with bash...not used zsh till now
>> As a blind shot, typed startx...nothing happened
>>
>> On Sat, 23 May 2020, 9:46 pm Max Rees, <maxcrees(a)me.com> wrote:
>>
>>> On Sat May 23 11:58 AM, Sanjay Mysore wrote:
>>> > Thanks for replying..
>>> > I did not mean to be pointing fingers at any body, but I am frustrated
>>> > that after having downloaded 2 .iso, both do not work I do not think
>>> > it has anything to do with Libreboot as such....
>>>
>>> I think it has everything to do with Libreboot.
>>>
>>> The docs for it are kind of sparse so I'm shooting in the dark here. I
>>> tried using the GRUB payload ROMs they provide for QEMU but it causes an
>>> internal KVM error as soon as it's loaded.
>>>
>>> Looking back to your original email and referencing the Libreboot docs,
>>> it seems you were trying to boot the ISO as if it were an ISOLINUX
>>> image. This is not the case - our ISOs have not been ISOLINUX based
>>> since before BETA1; they all use GRUB now. This explains why it would
>>> just return to the original menu without having done anything - it was
>>> looking for a file to parse that does not exist on our images.
>>>
>>> I guess Libreboot does not have GRUB set up to similarly parse other
>>> GRUB configurations. You can try running some commands at the GRUB
>>> command line (press "c" at the menu) to try to manually boot the ISO
>>> (this is based on boot/grub.cfg from the x86_64 RC1 ISO):
>>>
>>> 1. linux (cd)/bzImage-x86_64 squashroot=x86_64.squashfs
>>> 2. initrd (cd)/initrd-x86_64
>>> 3. boot
>>>
>>> Max
>>>
>>
>
> --
> With Best Regards
> Sanjay. M.R
>
11 months, 3 weeks
x86_64_RC1 full install CD not booting
by Sanjay Mysore
Hello
contents of the CD (.ISO image burned) are
1. Boot folder (grub)
2. system folder
3. bzimage_x86_64 (is this the one that should boot)
4. efi.img
5. initrd_x86_64 zip file
6. x86_64squash.fs
This CD does not boot. Kindly clarify if the contents listed above on this
Cd is correct or something is missing
--
With Best Regards
Sanjay. M.R
11 months, 3 weeks
Verifying hashes and signatures
by Cláudio Vieira
Hello all,
Having discovered Adélie Linux very recently I became keen on exploring it and joining the party!
I was not able to find anywhere instructions on how to verify the hashes and signatures of distribution files made available for download.
Verifying the SHA hashes is no problem at all.
Verifying the PGP signatures requires the public key used for signing. Which key is it (fingerprint)? Where to get it from?
I know how to do these verifications and will contribute to the documentation by writing a section on this topic.
Regards,
Cláudio Vieira
12 months
Re: TLP
by Didier BOUSSARD
Hello
My version should be 1.2.2 because my file is in etc/default/tlp
You told me to execute apk fetch --stdout tlp | tar -xOf - etc/default/tlp > myfile
System respond :
sudo apk fetch --stdout tlp | tar -xOf - ~/.tlp > myfile
bash: myfile: Permission denied
sudo: apk: command not found
I try with apt :
sudo apt fetch --stdout tlp | tar -xOf - ~/.tlp > myfile
bash: myfile: Permission denied
E: Command line option --stdout is not understood in combination with the other options
I have overwrite the file and i have no files in the same location but with the suffix ".apk-new"
help please
Le vendredi 15 mai 2020 à 09:41:12 UTC+2, Max Rees <maxcrees(a)me.com> a écrit :
On Fri May 15 07:27 AM, Didier BOUSSARD wrote:
> Hello
> I discard by inadvertance the default configuration file. I can make
> one by tlp-stat > myfile but there is no more comment inside. How can
> i get it back? (uninstall then install tlp did not resolve my problem)
>
> thanks
Is this on an Adélie system? It seems odd that uninstalling and
reinstalling it would not restore the default configuration if you have
deleted the file entirely. Usually it will place the default
configuration files in the same location but with the suffix ".apk-new"
if you have overridden things (but not if you deleted the file entirely
- it should just appear as the normal name).
There is also the problem of our current version spread of TLP - the
instructions depend on which version of TLP you have (`apk info -ev tlp`
will tell you - make sure your system is up-to-date though).
For tlp-1.2.2-r0, the configuration file is /etc/default/tlp. You can
get it from the package like this:
apk fetch --stdout tlp | tar -xOf - etc/default/tlp > myfile
For tlp-1.3.1-r0, it's /etc/tlp.conf:
apk fetch --stdout tlp | tar -xOf - etc/tlp.conf > myfile
In the future you may want to email the
adelie-users(a)lists.adelielinux.org mailing list instead of the package
maintainer directly, then everyone can help. :)
Max
12 months
