Puppy Linux Discussion Forum

fixedfury505 wrote: ↑Thu Feb 24, 2022 2:22 am

help! i cant get rid of the LICK bootup and cant install! i am really in a panic hoping i didnt just trash my computer. when i try to boot into linux (i did "install" with lick) its a black screen with a line (like the line in cmd) but it dosent blink and freezes my computer. im really worried for my computer i dont want to destroy it. ive tried 5 times but i can boot into windows like i did just now. please reply fast

fixedfury505 wrote: ↑Sat Feb 26, 2022 1:09 pm

what do you mean boot into windows? i could use it this whole time

Oh, I see. You saying you were "in a panic hoping i didn't just trash my computer... and im really worrried for my computer i dont want to destroy it" was misunderstood by me. If you can still boot into Windows with no issues then there is nothing to panic about at all. As mikeslr says it is just a matter of finding alternative mechanism for installing and booting the fossapup files (to see if fossapup works on your computer).

You already have grub loading and working successfully so the work remaining to be done isn't big at all and various Puppy experts will be able to set your install sorted out I'm sure.

Just to eliminate one possible cause of not booting with the Lick install.

Find the folder fossapup64-9.5 on C drive.

See if it has these files in it:
initrd.gz
vmlinuz
puppy_fossapup64_9.5.sfs
adrv_fossapup64_9.5.sfs
fdrv_fossapup64_9.5.sfs
zdrv_fossapup64_9.5.sfs.

bigpup wrote: ↑Sun Feb 27, 2022 3:32 am

Just to eliminate one possible cause of not booting with the Lick install.

Find the folder fossapup64-9.5 on C drive.

See if it has these files in it:
initrd.gz
vmlinuz
puppy_fossapup64_9.5.sfs
adrv_fossapup64_9.5.sfs
fdrv_fossapup64_9.5.sfs
zdrv_fossapup64_9.5.sfs.

Just to add..if you cannot find the folder on C: drive named fossapup64-9.5, look for whatever folder you named it when you ran lick.
Whenever I deal with MS Windows, I try NOT to put periods in "folder" names, but that's just me. So, for example, let's say you ran lick,
and chose to install to C:\fossapup64 , then look inside this folder for the files bigpup mentioned. The next step should be simple if you
can find the folder installed to. All you really need to do is open the file menu.lst in Notepad, or text editor of choice,
change references from whatever folder is there (probably fossapup64_9.5) to the name of the folder that matches your install folder!
Then grub can "find" the files to boot Fossapup.
Wiz

Wiz57 wrote: ↑Sun Feb 27, 2022 1:04 pm

The next step should be simple if you
can find the folder installed to. All you really need to do is open the file menu.lst in Notepad, or text editor of choice,
change references from whatever folder is there (probably fossapup64_9.5) to the name of the folder that matches your install folder!
Then grub can "find" the files to boot Fossapup.
Wiz

It will be simple in that case, though I'm pretty sure it is grub2 that is being used so the config file to edit will be grub.cfg

wiak wrote: ↑Sun Feb 27, 2022 1:40 pm

Wiz57 wrote: ↑Sun Feb 27, 2022 1:04 pm

The next step should be simple if you
can find the folder installed to. All you really need to do is open the file menu.lst in Notepad, or text editor of choice,
change references from whatever folder is there (probably fossapup64_9.5) to the name of the folder that matches your install folder!
Then grub can "find" the files to boot Fossapup.
Wiz

It will be simple in that case, though I'm pretty sure it is grub2 that is being used so the config file to edit will be grub.cfg

You're correct, I had forgotten about grub.cfg being used with grub2..my Pups are all on an old MBR based, non-UEFI system,
and uses grub4dos with menu.lst. Guess I was stricken with "tunnel vision", lol, my "installation" routine consists of extracting
a downloaded ISO file, usually with 7Zip, into a new directory (folder in Windows), then editing menu.lst to include the newly
installed Puppy...I normally "copy and paste" the boot stanzas for a known working Pup to a blank area of menu.lst, then
change the name, the folder name, etc. of the copied Pup to match the "new installation" Pup.
Wiz

I posted a issue topic on Github Lick about this problem.
https://github.com/noryb009/lick/issues

noryb009 is the person that built/coded Lick.
He should be able to help you.

Any help he can give should be what is needed.

Something I noticed when I followed bigpups github link to Lick, seems Lick might create a tad different named config file
as well as grldr file name...if so, then look for a file named lickgrub.cfg, and pupldr in the top (root) directory of your C:
drive. Edit lickgrub as detailed above for grub.cfg. Make sure pupldr is there and is in use instead of grldr.
I realize that people who work on these types of installer programs can feel proud of their work, perhaps it would be
best if they continued to utilize the original grub2 file structures? I ran into a similar situation a long time ago with a
Windows program for installing the old Slax 6.0, the creator used grub4dos, but renamed the files. I didn't realize it
until I went to do an update of grub4dos...which gave me additional config files and loader file. I had to sort through
those files and the menu.lst to choose the bootloader I wanted.
Wiz

bigpup wrote: ↑Sun Feb 27, 2022 3:32 am

Just to eliminate one possible cause of not booting with the Lick install.

Find the folder fossapup64-9.5 on C drive.

See if it has these files in it:
initrd.gz
vmlinuz
puppy_fossapup64_9.5.sfs
adrv_fossapup64_9.5.sfs
fdrv_fossapup64_9.5.sfs
zdrv_fossapup64_9.5.sfs.

yes, it has all 4 files

I was just looking through the files to find errors and i think this will help! (in the vmlinuz file)

i went to install another iso and check if its the downloader, i got the same error in the not intalled vmlinuz file. so i think there is something wrong with the downloader itself

fixedfury505 wrote: ↑Mon Feb 28, 2022 1:21 am

bigpup wrote: ↑Sun Feb 27, 2022 3:32 am

Just to eliminate one possible cause of not booting with the Lick install.

Find the folder fossapup64-9.5 on C drive.

See if it has these files in it:
initrd.gz
vmlinuz
puppy_fossapup64_9.5.sfs
adrv_fossapup64_9.5.sfs
fdrv_fossapup64_9.5.sfs
zdrv_fossapup64_9.5.sfs.

yes, it has all 4 files

Should be 6 files.
So again, does it have all of them?

bigpup wrote: ↑Mon Feb 28, 2022 1:41 am

fixedfury505 wrote: ↑Mon Feb 28, 2022 1:21 am

bigpup wrote: ↑Sun Feb 27, 2022 3:32 am

Just to eliminate one possible cause of not booting with the Lick install.

Find the folder fossapup64-9.5 on C drive.

See if it has these files in it:
initrd.gz
vmlinuz
puppy_fossapup64_9.5.sfs
adrv_fossapup64_9.5.sfs
fdrv_fossapup64_9.5.sfs
zdrv_fossapup64_9.5.sfs.

yes, it has all 4 files

Should be 6 files.
So again, does it have all of them?

oh sorry, yes it does, but look at the picture i sent i think that will help a lot

i went to install another iso and check if its the downloader, i got the same error in the not intalled vmlinuz file. so i think there is something wrong with the downloader itself

Best if you download the Fossapup64 9.5 ISO by doing it in a Internet browser.
http://distro.ibiblio.org/puppylinux/pu ... 64-9.5.iso
Download to location you can find it.
Open a file manager to the ISO download location.
Tell Lick to use that ISO by doing the drag and drop into lick main window input slot.

bigpup wrote: ↑Mon Feb 28, 2022 1:53 am

i went to install another iso and check if its the downloader, i got the same error in the not intalled vmlinuz file. so i think there is something wrong with the downloader itself

Best if you download the Fossapup64 9.5 ISO by doing it in a Internet browser.
http://distro.ibiblio.org/puppylinux/pu ... 64-9.5.iso
Download to location you can find it.
Open a file manager to the ISO download location.
Tell Lick to use that ISO by doing the drag and drop into lick main window input slot.

it still has the same error in the code that my download did. i think something is wrong with the downloader

Thanks for sticking with trying to figure out what is wrong and how to fix it!

I would wait and see if noryb009 gives us a reply.

He is still active on the Lick on Github, so he should respond to my issue post I made there.

fixedfury505 wrote: ↑Mon Feb 28, 2022 1:26 am

I was just looking through the files to find errors and i think this will help! (in the vmlinuz file)

That is just what the kernel stores as information to send if an error occurs. That wouldn't really help as all you're receiving is a blank terminal screen from booting. As well I'm not entirely certain why it says 'pfix=fsck dofsck' which might not even be a valid one. Try cutting out dofsck then pressing F10 to boot.
As well, someone suggested you burn the ISO to a usb and see what happens if you boot off that usb. (The ISO of course needs to be intact and not corrupted)

I assume you have secure boot enabled in the computer UEFI setup.

You say you did this, which is suppose to let it boot with secure boot enabled:

LICK supports secure boot, but requires a manual step during the first reboot.

On the first reboot, if you see a blue screen with writing, press enter to select OK.
Press enter again to select Enroll Hash.
Use the up and down arrow keys to highlight loader.efi, and press enter.
Press the down arrow to select Yes, then press enter.
Use the down arrow to highlight Exit, then press enter.

On subsequent reboots, these steps will not need to be taken.

Secure boot is just a big bunch of crap for non Windows OS's.

Could see if secure boot is causing the problem.
If you are willing to try it.
Go into the computers UEFI setup.
Find the setting for secure boot and disable it.
Exit UEFI setup saving changes.
Now try to boot Fossapup64.

Are we having fun yet?

bigpup wrote: ↑Mon Feb 28, 2022 2:34 am

Are we having fun yet?

nope, it didnt work

Secure boot only checks the boot loader, and if the boot loader was configured or programmed it will then check the files to be booted.

Regarding the suggestion of burning fossapup to a USB then trying to boot off the USB, any luck?

That suggestion also advised to use rufus so as to eliminate the possibility that the problem you're having relates to a flaw in LICK. The instructions I provided regarding rufus are only necessary if you want to actually run fossapup64 from the Stick, creating and using 'persistence' to the stick. rockedge's instructions here are sufficient if you only intend to use fossapup64 on the stick to install it to your hard drive, viewtopic.php?t=5192. That is:

Install rufus or use its portable version https://rufus.ie/en/ under Windows. Run it. Select your USB-Stick and your Fossapup64.ISO. Click OK. Wait for rufus to finish. That's it.

Phoenix wrote: ↑Mon Feb 28, 2022 3:46 pm

Secure boot only checks the boot loader, and if the boot loader was configured or programmed it will then check the files to be booted.

Regarding the suggestion of burning fossapup to a USB then trying to boot off the USB, any luck?

sprry i havent gotten to try that i havent been able to find any usbs

i went through stuff i could do with grub and foind i cant boot a command line so maybe it is grub?

Its not a matter of entering things manually to make it work, if those lines in the configuration didn't work so.

After you have confirmed burning the ISO to usb didn't fix it (you can use Rufus to do this on Windows), try removing 'dofsck' when you edit the menu entry in GRUB(2). Then boot via F10 or whatever GRUB(2) says is the key.

Phoenix wrote: ↑Tue Mar 01, 2022 2:31 am

Its not a matter of entering things manually to make it work, if those lines in the configuration didn't work so.

After you have confirmed burning the ISO to usb didn't fix it (you can use Rufus to do this on Windows), try removing 'dofsck' when you edit the menu entry in GRUB(2). Then boot via F10 or whatever GRUB(2) says is the key.

i havent booted it yet but it looked like it was lick because it looks like more was extracted i think youve done it

I GOT IT WORKING

HOW DO I COMNECT WIFI

Nice to see your persistence pay off. You could explain what you did to get it working, so the next guy that is researching similar problems can see your fix.

As for Wifi, the best is to open a new topic in the beginner section and explain which wifi tool you are having problems with and what you have tried already.

williwaw wrote: ↑Tue Mar 01, 2022 7:16 am

Nice to see your persistence pay off. You could explain what you did to get it working, so the next guy that is researching similar problems can see your fix.

As for Wifi, the best is to open a new topic in the beginner section and explain which wifi tool you are having problems with and what you have tried already.

out of all things, it was the installer. it was not extracted properly. to the people who need help reading this. please to save a few days on this forum use a usb and rufus. look back and you will see the link.

This is you saying Lick did a bad install.

The problem with that statement, many people report using Lick to do installs, and they have no problem with the Puppy version they install, booting.

So we are not sure if you did something wrong or there is a bug in Lick's latest version.

Hopefully the developer of Lick (noryb009) will look at this topic.

If Fossapup64 9.5 is booting OK from a USB.
We know it is not something in Fossapup64 9.5 keeping it from booting.

Again noryb009 needs to answer on this topic!

@fixedfury505 Can you clarify what you mean by "it was not extracted properly"? Were there files that had the wrong checksum? Or were there files that were not extracted at all?

> I realize that people who work on these types of installer programs can feel proud of their work, perhaps it would be best if they continued to utilize the original grub2 file structures?

For normal cases, I agree having the regular names makes things easier. But doing this introduces a lot more edge cases. For example, someone might already have grub2 installed when they install LICK - LICK then needs to hook into that boot loader and `grub.cfg` (and the grub.cfg might not be in the location it expects). It can also have another Linux distribution come along and rewrite the `grub.cfg` to what it wants, which loses the LICK configuration. When LICK is uninstalled, it needs to know whether it should delete the bootloader (and some users will not expect that the `grub.cfg` they edited came from LICK).