How to use GRUB menu and/or LICK?

[fixedfury505]

Hello! Back on this site again after a few years. Promise not to be as much of a mess as 12 y/o me was on this site last time haha..

As of recent ive decided to try and get linux on my laptop again now that ive had plenty more practice with software. I decided rather than fossapup i went with S15Pup64 22.12. Last time I did manage to get it working via rufus on a usb but this time my laptop DID NOT cooperate with another bootable device. So, I went with LICK. Everything seemed to work properly, I installed the boot loader, then puppy in the same session.. which may have been a mistake but idk. I restart my computer to be greeted with the GRUB menu with a prompt. Heres the problem, there were no instructions on what to do for a GRUB prompt.. and im not the most savvy with GRUB myself. Im trying to get into whatever menu to first of all, enroll hash and all that for LICK, and successfully install linux on my computer. Anything helps!

[bigpup]

Welcome Back

Lick is an installer specifically for installing Puppy along side a version of Windows OS.

This is the topic on it, with more information.
viewtopic.php?t=336

You did use the latest version of Lick? v1.3.4?

Is Windows OS the only other operating system on the computer internal drive?

What Windows version is on the computer?

When Windows is shutdown.

Do a complete full shutdown.

Do not do any other type shutdown of Windows.

Hibernation mode will for sure mess up trying to boot something else.
It does not fully release control of the computer.

What is the laptop?
Make and model?
Specs if you know them?

[bigpup]

I installed the boot loader, then puppy in the same session..

Lick should have installed S15Pup64 first and then installed the boot loader.

Could just try doing the install again with Lick making sure to be using the latest version v1.3.4

[cobaka]

@fixedfury505
Your return to the Puppy forum is very welcome. You are in the process of installing Puppy Linux (Slack Puppy) and had some trouble. Well, I decided to write a note about the first steps. You may know everything I write here - in that case - skip it. I thoroughly recommend the link your see (further down this posting). It's a reference to a note from Rockedge, where he describes using gParted. His work assumes a background that doesn't come from using Windows; Windows is a 'hand-holding' OS. You get C: You get a disk with the OS. You don't format the HDD. In this respect Windows is great - until something goes wrong. Then you're in a barb-wire canoe, up a difficult creek without a paddle. When you are familiar with 'the Puppy' you'll find yourself in a solid canoe where lots of people will hand you a good paddle. Hang in there; we'll get Puppy installed and running.

Now here is my intro to formatting.

Formatting - an introduction.
When the first rotating drives were pioneered by IBM in 1957, the surface of the disk platter was unmagnetised; in that state it could not store any data from the computer/mainframe. Today, at first, the much smaller mechanical drives are similarly unmagnetised. Before a drive can be used, then, the surface must magnetised in some way. The manufacturer "writes" a series of magnetic concentric rings (the tracks) and subdivsions within each track (the sectors) onto the disk surface. By analogy, this process is somewhat akin to moving empty shelves in a new library. Space is available to put books; but at this stage there is no catalog showing where various "books" (i.e. files) are found. This process is called "low level" formatting.

The second stage of formatting a drive - "high level" formatting - is to determing some logical arrangement of storing information to each track and sector, creating some form of catalog (i.e. a directory) giving the location of where each file can be found the disk platter. The Microsoft operating system adopts the office/document/file analogy by substituting the word "folder" for the Unix/Linux "directory". The directory, then is nothing more than a catalog of the location of each file on the disk (or by extension thumb-drive or FDD).

Many different "high level" formats (file systems) are used to arrange the information on a storage device. Abbreviations such as FAT32 (a system using a file allocation table), NTFS (a 'new technology' filing system), ext2, ext3, ext4 (extension to earlier filing systems) hint at the underlying structure for the format used on some particular storage device.

Our interest is the filing system used to install Puppy Linux to a hard drive.
Various pieces of software can write one of the high level formats to the drive. The command line can be used for this:
mkfs.ext3 /dev/sdb1
"mkfs" will "make" (i.e. write) a file system to a storage device. The file format will be "file extension #3" for a drive known (to the system) as storage device b1.

Using the command line is tedious; in Puppy Linux the graphical partition editor "gPartEd" is more convenient. This note will come to that shortly; first we must deal with "partition". In our example from IBM and 1957 the surface of a disk platter was a single entity. As disk capacity increased a process - partitioning - sub-divided the storage space of the disk platter into smaller, apparently independent segments or partitions. Thus sda may be partitioned as sda1, sda2 ... and so on. A table - the partition table - records the beginning and ending location of each partition on the drive. In our analogy of libraries, this would be locating several libraries in one building with a guide at the entrance indicating: Library #1, to level 4. Library #2 at levels 5 .. 8 and so on.

Here I re-introduce gPartEd, the partition editor.
This is shown in the forum topic below:
https://www.forum.puppylinux.com/viewto ... 184&t=5241

In that forum posting @rockedge assumes you will install the Puppy Operating System to a legacy internal drive, but you can easily extend his instructions to formatting a thumb drive (or a Solid-State Drive).

Well, Rockedge's instructions are quite detailed; you can easily follow them. My only comment is this: he begins the process by deleting a partition.
I begin the process by Device -> Create a partition table.

I have no idea whether deleting a table blanks the partition table, whereas creating a partition table certain initializes the info in the table for sure. You can ask Rock about that. He knows much more about this than I do.

This is a long posting; the second of two.
I'll write the first now.

[cobaka]

@fixedfury505

This is the first posting of 2. My second posting is just background info about formatting and partitioning a drive.
You may know everything I wrote; it's common knowledge, but not everyone knows about gParted and the result of each process.
In the posting below I give a link to a posting by Rockedge. This is a very useful page; I recommend it.

Later today I'll try to install S15 using the software your mention. (In the past I installed Puppy by a completely different process)
When I'm familiar with Lick I'll check your result against my experience.
I'm very confident you can install the Puppy using Lick. I'm also confident you'll like it.

@bigpup asked for some specific info. Yes, we need to know this.

собака

[fixedfury505]

I installed the boot loader, then puppy in the same session..

Lick should have installed S15Pup64 first and then installed the boot loader.

Could just try doing the install again with Lick making sure to be using the latest version v1.3.4

I think a restart would help. But I cant get back into windows without going through GRUB, which im not quite sure how to do.

[rockedge]

I think it might be possible to use chain +1 or a variant of the chain command to hand over the boot to the Windows boot loader.

I have examples in Grub4Dos but not Grub2, though the syntax can be adapted.

[bigpup]

If your computer is UEFI bios.

during boot, press the F12 or Delete key to open up the UEFI control center.
There you should find a specific setting where the boot hierarchy is laid out.
You should find GRUB or Lick boot manager on top, followed by Windows Boot Manager.

Have it selected to use the Windows Boot Manger

That should get it to directly boot Windows.

The computer may have a direct access to the boot selection option.
Just as it starts up press and hold a specific key.
On my computer it is F-11 key. Yours could be that or some other key.
A screen opens with selections of what to boot from.

[fixedfury505]

If your computer is UEFI bios.

during boot, press the F12 or Delete key to open up the UEFI control center.
There you should find a specific setting where the boot hierarchy is laid out.
You should find GRUB or Lick boot manager on top, followed by Windows Boot Manager.

Have it selected to use the Windows Boot Manger

That should get it to directly boot Windows.

The computer may have a direct access to the boot selection option.
Just as it starts up press and hold a specific key.
On my computer it is F-11 key. Yours could be that or some other key.
A screen opens with selections of what to boot from.

Ok.. I got back into windows and reinstalled the bootloader which was definitely needed, but now puppy itself wont load. When my computer boots I see the bootloader asking me to select my operating system. I have 3 options: windows 10, S15Pup64 22.12, and S15Pup64 22.12 *no save file. If i select windows windows loads as normal but both puppy options lead to a blank screen with a dash in the corner like a command prompt; but no buttons are responsive aside the power button. I gave both blank screens a few minutes to see if anything happens, both showing no progress. I redownloaded the iso hoping it was simply a bad download only to have the same results. Maybe I should try another method? im not sure about usb again since it straight up just didnt boot at all when I tried that.

[bigpup]

I suggest you try using BookwormPup64 10.0.6
viewtopic.php?t=8690

S15Pup64 seems to have some booting issues with some computers.

No one Puppy version will work on all possible computers!
That is why there are several to try.

There is one thing that could be causing these issues.

But need to know exactly what the computer is.
Make?
Model?

[fixedfury505]

I suggest you try using BookwormPup64 10.0.6
viewtopic.php?t=8690

S15Pup64 seems to have some booting issues with some computers.

No one Puppy version will work on all possible computers!
That is why there are several to try.

There is one thing that could be causing these issues.

But need to know exactly what the computer is.
Make?
Model?

i use a dell inspiron 13 7300 2in1

Core i7 10510U / 1.8 GHz
16 GB RAM
512 GB SSD (32 GB SSD cache)
13.3" touchscreen 3840 x 2160 Ultra HD 4K (with some goofy display issues)
Intel UHD Graphics
and i primarily use windows 10.

Cant quite think of a reason it wouldnt work though.. its not the best computer specs nowdays but more than enough to boot any puppy operating system.

[Wiz57]

If you can, post the contents of your grub.cfg if using grub2 or if using grub4dos the contents of menu.lst. I've noticed that my frugal install of
S15Pup32 requires the "pdrv" parameter on the kernel line in order to boot. Older Pups didn''t need this, a simple "find root" was enough.
Wiz

[fixedfury505]

If you can, post the contents of your grub.cfg if using grub2 or if using grub4dos the contents of menu.lst. I've noticed that my frugal install of
S15Pup32 requires the "pdrv" parameter on the kernel line in order to boot. Older Pups didn''t need this, a simple "find root" was enough.
Wiz

I am running on grub 2. I didnt quite see a grub.cfg but there was a lickgrub. cfg. These are the following contents of that file:

## start header
insmod part_gpt
insmod part_msdos
insmod ntfs

set timeout=5
set default=0

insmod all_video
if loadfont /grub/fonts/unicode.pf2 ; then
set gfxmode=auto
set gfxpayload=keep
terminal_output gfxterm
fi

menuentry "Windows" {
insmod chain
search --set=root --file /EFI/Microsoft/boot/bootmgfw.efi
chainloader /EFI/Microsoft/boot/bootmgfw.efi
}
## end header

[bigpup]

You are doing a normal complete shutdown of Windows 10?

Did you try using BookwormPup64 10.0.6?

Not all computers are supported by all Puppy versions.

[bigpup]

Is this a computer with UEFI bios?
If yes.
If secure boot is enabled in the bios setup.

Did this happen when you first tried to boot with Lick?

UEFI Systems with Secure Boot

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.

[fixedfury505]

Is this a computer with UEFI bios?
If yes.
If secure boot is enabled in the bios setup.

Did this happen when you first tried to boot with Lick?

UEFI Systems with Secure Boot

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.

No, which i find odd considering that happened when i installed lick a few years ago with the same laptop.

[bigpup]

That should be installing the Puppy security key on the computer, with the others that are already there for Windows.
If you did this at another time in the past.
It is already there and no need to install it.

Well that eliminates one possible issue.

[bigpup]

Did you try using BookwormPup64 10.0.6?

[fixedfury505]

That should be installing the Puppy security key on the computer, with the others that are already there for Windows.
If you did this at another time in the past.
It is already there and no need to install it.

Well that eliminates one possible issue.

You sure? This laptop has been formatted at least once since I last installed puppy.