Puppy Linux Discussion Forum

Hi

Laptop:
Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz
Core Count: 2
64-bit capable: Yes
RAM: 3 GB
Chipset: SiS

I can't find way to overcome booting bootleneck with fossapup64-9.5 on this laptop - on other one there are no problems. Regardless used media (CD, Flash, HDD) and boot mode booting hangs on "Waiting for modules to complete loading..." - laptop is frozen.

Help me please
Adam Li

Adam Li wrote: ↑Sun Jun 13, 2021 4:40 pm

Hi

Laptop:
Intel(R) Core(TM)2 Duo CPU T6400 @ 2.00GHz
Core Count: 2
64-bit capable: Yes
RAM: 3 GB
Chipset: SiS

I can't find way to overcome booting bootleneck with fossapup64-9.5 on this laptop - on other one there are no problems. Regardless used media (CD, Flash, HDD) and boot mode booting hangs on "Waiting for modules to complete loading..." - laptop is frozen.

Help me please
Adam Li

Hello Adam,
Please try these one by one ...
1. Take out the internal HDD from this laptop, then try to boot from the USB again
2. If still no go, try to isolate the laptop RAM stick by applying it one by one and on different socket each boot
3. If still no go, try to use a different RAM stick
4. The last resort, flash the ISO to the internal HDD, not USB media

What you used to do the different installs could be the issue.
What install way would you like best to use?
CD/DVD, USB drive, internal hard drive?

Pick one and we will guid you to get it booting.

If you have Windows on this computer.
Make sure Windows is completely shutdown normally.
Do not shutdown in hibernate or sleep.

If you can get Fossapup64 to start booting.
I will assume you have the UEFI setup set with secure boot disabled, legacy boot enabled, or CSM enabled.
If not.
Need to do this.
Depends on the UEFI firmware version, as to what settings it has, but it will have one or more of them.

Thanks sonny
It's i no way hardware problem, I use this laptop daily: main system is BionicPup32-8 19.03 (I'm writing this post from this), second Precise 5.7.1 - both frugal instal on HDD, and third WindowsXP.
Thanks once more.

Thanks bigpup
1. It's old classic BIOS, not UEFI.
2. I tried some others 64-bit Linux using Ventoy:
- clonezilla-live-2.6.7-28-amd64.iso
- clonezilla-live-2.7.1-22-amd64.iso
- linuxmint-20.1-cinnamon-64bit.iso
- MX-19.3_x64.iso
- Zorin-OS-15.3-Core-64-bit.iso
with success.
3. I'm interested in frugal instal on HDD, booting through grldr.

I'm waiting with interest ...

Fossapup64 9.5 installed on a USB.
Only have this USB drive plugged in when booting.
No other USB drives.

First I would try getting a fresh new download of the Fossapup64 9.5.iso
There is a chance you got a bad download. It happens.

Try to download to a location that is a Linux format.
If you download to a location windows XP uses.
There is a chance it is fragmented.
That can cause the Fossapup iso to be fragmented and not work well.
Running Windows defrag program, on that location, can fix it.

Ok, Fossapup as a frugal install, on internal HDD, with other Puppy versions as frugal installs.
How are you trying to do the frugal install?
Manually?
Using some program?

Is the Fossapup frugal install in same location as the other Puppy versions frugal installs?

What boot loader are you using?

How are you updating the boot loader after you install Fossapup?

Can you post the boot menu entry you are using to boot Fossapup?
Do you understand what I am asking and how to find it?
Maybe something is wrong in this entry.

Hi bigpup, a plenty of thanks for You!

bigpup wrote:

First I would try getting a fresh new download of the Fossapup64 9.5.iso
There is a chance you got a bad download. It happens.

sha256 checked

bigpup wrote:

Try to download to a location that is a Linux format.
If you download to a location windows XP uses.
There is a chance it is fragmented.
That can cause the Fossapup iso to be fragmented and not work well.
Running Windows defrag program, on that location, can fix it.

Disk defragmented.

bigpup wrote:

Ok, Fossapup as a frugal install, on internal HDD, with other Puppy versions as frugal installs.
How are you trying to do the frugal install?
Manually?
Using some program?

ISO unpacked to /mnt/home/fossapup64

bigpup wrote:

Is the Fossapup frugal install in same location as the other Puppy versions frugal installs?
What boot loader are you using?
How are you updating the boot loader after you install Fossapup?

In sequence:
- yes
- grldr
- manually

menu.lst

######################################################
# GvR Sept 30th 2004
	color black/cyan yellow/cyan
	timeout=5
	default=0

title Bionicpup32 Puppy 8.0
kernel (hd0,0)/bionicpup32/vmlinuz PMEDIA=satahd pfix=nocopy PDEV1=sda1 psubdir=bionicpup32 video=640x480
initrd (hd0,0)/bionicpup32/initrd.gz
boot

title Precise Puppy Linux 5.7.1
kernel (hd0,0)/precise/vmlinuz PMEDIA=satahd pfix=nocopy PDEV1=sda1 psubdir=precise video=640x480
initrd (hd0,0)/precise/initrd.gz
boot

title Fossapup64 9.5
kernel (hd0,0)/fossapup64/vmlinuz PMEDIA=satahd pfix=nocopy PDEV1=sda1 psubdir=fossapup64 video=640x480
initrd (hd0,0)/fossapup64/initrd.gz
boot

title Windows XP
	rootnoverify (hd0,0)
	chainloader +1
	boot



######################################################

Some earlier experiments:

- booting with alone puppy_fossapup64_9.5.sfs
- saved fossapup64save-corrino.3fs
- restart
- added fdrv_fossapup64_9.5.sfs
- restart
- added zdrv_fossapup64_9.5.sfs
- restart
- added adrv_fossapup64_9.5.sfs
- restart

Working, but not recognized sound card and WiFi.

Have a nice day
Adam

Adam Li wrote: ↑Mon Jun 14, 2021 1:31 pm

Working,

So how is that last test different from your original problem?

Hi rcrsn51

I just don't like not knowing - the sfs append routine is some sort of workaround, but the cause of the hang is still unclear. I suppose the problem is due to the lack of drivers, but that's just a guess. BIOS Phoenix v6.00 dated 06/07/2011 - laptop is over 10 years old, GeForce 9300M GS with 256 MB RAM is old too. An unusual combination is the Intel (R) Core (TM) 2 Duo CPU T6400 @ 2.00GHz with the SIS 671MX / SiS968 / SiS 5513 chipset and the SiS Azalia Audio Controller audio controller. In short: something in (my) hope for a 64 bit puppy is wrong and I don't know what or why.

Have a nice day
Adam

I am still unclear. Does "working" mean that you still had the hangup?

Or does loading the .sfs modules in stages somehow avoid the hangup?

Hi rcrsn51, thanks for interesting in

I had to check it out so as not to write nonsense. If there is fossapup64save-corrino.3fs in the fossapup64 folder saved with alone puppy_fossapup64_9.5.sfs, fossa boot-up, but in any other case - for example with pfix = ram - it hangs on.

Have a nice days and nights
Adam

So is omitting the zdrv_fossapup64_9.5.sfs enough to make it boot?

Bingo rcrsn51, You Are Great!

Renamed zdrv_fossapup64_9.5.sfs, pfix=ram >> no booting problem.

But what to do with booting from ISO - is remastering the only way?

Have a nice days and nights
Adam

Adam Li wrote: ↑Mon Jun 14, 2021 6:12 pm

Renamed zdrv_fossapup64_9.5.sfs, pfix=ram >> no booting problem.
But what to do with booting from ISO - is remastering the only way?

It sounds like some new driver in the zdrv conflicts with your old hardware, particularly the SiS stuff or maybe the Geforce video.

Try booting from the ISO. When it hangs up, press Ctrl-C several times and see if you can break out.

Hi rcrsn51

rcrsn51 wrote:

Try booting from the ISO. When it hangs up, press Ctrl-C several times and see if you can break out.

Tested options:
- Safe mode, no x
- RAM only
Ctrl-C several times with no effect - laptop frozen like Emmerich's "The Day After Tomorrow".

Thanks very much and I go sleep - it's 23:09 my local time.
See you morning!
Adam

If you really want to run fossapup64_9.5, you should look at switching the kernel to an older version that works with your hardware.

Fossapup64 9.5 is developed to provide support for very new hardware.
It tries to support older stuff, but it is using one of the newest Linux kernels.
the kernels are dropping support for very old hardware.

Do you know how to change the kernel?

Have you tried Bionicpup64 8.0?

hi bigpup

bigpup wrote:

Do you know how to change the kernel?

No, never needed.

bigpup wrote:

Have you tried Bionicpup64 8.0?

Yes, about 2 yers ago, along with Bionicpup32 (and 8 others in Puppy Gang )

Regards!
Adam

You probably want to try a kernel series 4 one.
I do not think you need a series 3 one ,but maybe, maybe not.

If you can get Fossapup to a working desktop.
To change kernel

you can change the kernel to any type you would like with this tool
In a terminal enter

change_kernels

Here are all the normal Puppy kernel packages that can be used:
http://distro.ibiblio.org/puppylinux/huge_kernels/
64 bit kernels have 64 in the package name.

Download a huge kernel tar.bz2 package and extract the files in it to a directory.
open the change_kernels program
open in rox file manager the directory holding the extracted huge kernel components
drag and drop the correct vmlinuz and kernel-modules.sfs or zdrv.sfs paths to the program input slots.
answer prompt yes
The program makes all the needed name changes.
reboot
Should now be using the new kernel.

Just to better understand the change_kernels program.

The info for the input slots is a little miss leading.
(Use nothing from the running Puppy)

What goes into the slots is stuff from the new kernel.
Top slot -->the vmlinuz file
Bottom slot -->the zdrv sfs or the kernel-modules sfs

There is a kernels button bottom right that will take you to the repository of all the regular Puppy versions kernels.
You can use any of them, however get too old a kernel and newer hardware may not be supported.

If you cannot run change_kernels program.
after you extract the new kernel package files.
Change the name of the zdrv.sfs to the exact name it is in Fossapup.
Delete the vmlinuz and the zdrv sfs files from the Fossapup install.
Replace them with the new ones from the new kernel package.
Reboot.

"bigpup" You did it again! Great post on "change_kernels", worked perfectly. My HP-G60 la[top cira 2008 seemed sluggish on fossa/kernel 5, partitions were slow to open with rox (5 seconds or so), Now since loading kernel 4.19.23 from bionic partitions load instantly and everything seems much faster, and the rox freezes opening root/proc is also gone.
thanks
pete

Hi bigpup - YOU ARE BIGPUP!

I'm writing from Fossapup64, kernel 4.9.249 from huge-4.9.249-slacko.tar.bz2, manually unpacked and renamed files.

WiFi working, sound also. I write more after some test

Great thanks and see you later
Adam

BTW
huge-3.14.56-tahr_PAE.tar.bz2 do not pass MD5 check - four independed mirrors tested.

Well, thank rcrsn51 for bringing up the idea

Great to see it worked for you!

I'm writing from Fossapup64, kernel 4.9.249 from huge-4.9.249-slacko.tar.bz2, manually unpacked and renamed files.

specific info is important.
huge-4.9.249-slacko.tar.bz2 is the 32bit Slacko kernel.
I hope you actually used the 64 bit one.
http://distro.ibiblio.org/puppylinux/hu ... 64.tar.bz2

If 64 is not in the name of the kernel package.
It is compiled for 32bit operations and will not have everything configured for full 64bit operations.

Hi bigpup

You are right, I checked it and do some correction:

huge-4.9.249-slacko64.tar.bz2:
------------------------------
fdrv-4.9.249-slacko64.sfs		--> fdrv_fossapup64_9.5.sfs
kernel-modules-4.9.249-slacko64.sfs	--> zdrv_fossapup64_9.5.sfs
vmlinuz-4.9.249-slacko64		--> vmlinuz

All working OK, booting with pfix=ram OK, the only an annoying defect is I can not call a wifi right click menu, net is immediately disconnected.

Thanks and have a nice day
Adam

the only an annoying defect is I can not call a wifi right click menu, net is immediately disconnected.

If you are talking about right clicking on the tray network icon.
Right click and keep the right mouse button held down.
Move over the menu to highlight what you want selected.
Release the right button.
It should select what you had highlighted.
This is a little bug in Fossapup64 9.5, how to get a selection on that menu.

booting with pfix=ram OK

Why are you booting that way?
That tells Puppy to not use the save, if you made one.

Do not think that affects how Puppy loads into ram.
A normal boot of a frugal or full install, always loads into ram.

Hi bigpup

I am not surprised - you are involved in many threads - that some kind of mental shortcut has confused you.
I wrote

Adam Li wrote:

Some earlier experiments:
.
.
- booting with alone puppy_fossapup64_9.5.sfs
- saved fossapup64save-corrino.3fs
- restart
- added fdrv_fossapup64_9.5.sfs
- restart
- added zdrv_fossapup64_9.5.sfs
- restart
- added adrv_fossapup64_9.5.sfs
- restart

and I wrote

Adam Li wrote:

I had to check it out so as not to write nonsense. If there is fossapup64save-corrino.3fs in the fossapup64 folder saved with alone puppy_fossapup64_9.5.sfs, fossa boot-up, but in any other case - for example with pfix = ram - it hangs on.

Finally I wrote in short:

Adam Li wrote:

All working OK, booting with pfix=ram OK...

and the trap came out

bigpup wrote:

Why are you booting that way?

It was only booting test with "new old kernel".

Normal boot options are as follow:

title Fossapup64 9.5
kernel (hd0,0)/fossapup64/vmlinuz PMEDIA=satahd pfix=nocopy PDEV1=sda1 psubdir=fossapup64 video=640x480
initrd (hd0,0)/fossapup64/initrd.gz
boot

Sorry!
Have a nice day
Adam Li

bigpup wrote: ↑Wed Jun 16, 2021 11:50 am

the only an annoying defect is I can not call a wifi right click menu, net is immediately disconnected.

If you are talking about right clicking on the tray network icon.
Right click and keep the right mouse button held down.
Move over the menu to highlight what you want selected.
Release the right button.
It should select what you had highlighted.
This is a little bug in Fossapup64 9.5, how to get a selection on that menu.

It's more than just a "little bug" in Fossapup, bigpup. Bionicpup does it; Xenialpup does it; even BK's older Quirkies have the same behaviour. I'm in Quirky64 April 7.0.1 right now, and it's just the same here. Seems to be endemic to all Woof-CE built Pups; I'm a bit surprised the issue hasn't been addressed yet....

Most of us regulars will be used to this by now, but.....has anybody ever mentioned this over at Github? The only Woof-CE Pup I can remember that didn't do this was the very first release of Tahrpup, 6.0 CE......and that was very early days for Woof-CE, too.

Mike.

mikewalsh wrote:

It's more than just a "little bug" in Fossapup, bigpup. Bionicpup does it; Xenialpup does it; even BK's older Quirkies have the same behaviour. I'm in Quirky64 April 7.0.1 right now, and it's just the same here. Seems to be endemic to all Woof-CE built Pups; I'm a bit surprised the issue hasn't been addressed yet....

It's like to be 64-bit "special add-on". I don't remember more, but Bionicpup32 8.0 and Precise 5.7.1 are free of this.

Regards

OK.
It is a feature not a bug!

Well, like everything in Puppy Linux.
Someone has to volunteer to fix it, for it to get fixed!