Puppy Linux Discussion Forum

jamesbond wrote: Sat Jul 22, 2023 4:20 am

Duprate wrote: Fri Jul 21, 2023 7:20 pm

Hello! I don't know if I should opine about the kernel....
The fact is that, for me, kernel 5.19.17 and 6.1.39, on startup give the error "kernel panic" and crash. However, for years I use FatDog64 only in Overlayfs mode and compile the Kernel as Monolithic (without modules and firmware). I'm already using 6.1.39 which I compiled on the 19th of July 2023. So my obtained results are probably not of interest to any of the AUFS users.
But, I would also like to know what the result of using the new kernel is with other users.......

Hi Duprate, I'm not sure I understand you. When you said you experienced crash, in what situation did it happen? If it happens you're using your own custom kernel with your own custom config, and your own custom initrd to use overlayfs when it happens ... I'm afraid you're right, it's probably irrelevant to others, as the configuration is very specific to you and it will not be reproducible by others.

Hi jamesbond! You are right. I use overlayfs, my initrd is different and I compile my kernel. From FatDog64, I use the system base (fd64.sfs and fd64-devx.sfs), and that works perfectly for me!
However, I will do a standard installation, aufs, all original, in order to produce valid tests.

Hello! Now, with a new default installation, the same way everyone uses it, the new 6.1.39 kernel provided for FatDog64 is working perfectly, as well as the previously tested packages ( conky-1.7.2-x86_64-1.txz and wine-8.6-i686-1.txz). Using a script to create ZRAM memory. Geany still doesn't work.
Happy and content!

re: wine 8.6
I'll try downloading libvulkan and libvulkan32bit
and repeat

I have a frugal install, a save file and I removed SFS files and deleted hidden wine folder in /root
then installed wine 8.6 txz. That was all. Then CD to bin folder in /opt
Here is terminal output for various commands. The notepad app did work for 2nd command.

# ./wine notepad
./wine: /lib/libc.so.6: version `GLIBC_2.34' not found (required by ./wine)

____________________________________________________
# ./wine64 notepad
wine: created the configuration directory '/root/.wine'
004c:err:vulkan:wine_vk_init Failed to load libvulkan.so.1
/opt/wine-8.6/bin/wine: /lib/libc.so.6: version `GLIBC_2.34' not found (required by /opt/wine-8.6/bin/wine)

___________________________________________________________
# ./wine64 mp3DC236.exe
0050:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
/opt/wine-8.6/bin/wine: /lib/libc.so.6: version `GLIBC_2.34' not found (required by /opt/wine-8.6/bin/wine)
Application could not be started, or no application associated with the specifie
d file.

________________________________________________________
# ./wine64 /root/.wine/drive_c/mp3DC236.exe
0050:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
/opt/wine-8.6/bin/wine: /lib/libc.so.6: version `GLIBC_2.34' not found (required by /opt/wine-8.6/bin/wine)
Application could not be started, or no application associated with the specifie
d file.
________________________________________________

So maybe libvulkan is all that is needed to allow mp3DC286.exe to launch.
..........---------------------------------------------------------------------------

Duprate wrote: Sat Jul 22, 2023 7:08 pm

Hello! Now, with a new default installation, the same way everyone uses it, the new 6.1.39 kernel provided for FatDog64 is working perfectly, as well as the previously tested packages ( conky-1.7.2-x86_64-1.txz and wine-8.6-i686-1.txz). Using a script to create ZRAM memory. Geany still doesn't work.
Happy and content!

Glad you are happy!
How is geany not working?

Hello! I click on Geany and it looks dead! Luckily I don't miss it.... Everything I would do with Geany, I do with Leafpad....... Now, if Geany is working for the rest of the users, which will be great news, that's my problem alone. So sooner or later I sort it out!

@Duprate, please open terminal, and type "geany" and, and report error message you see.

Vulkan was needed to be installed to get rid of complaint
when running windows but I still get ld-linux complaint when attempting to launch a windows exe file

________________________________________________________

When running a pinstall.sh file for install of WINE 5.11
viewtopic.php?p=94671#p94671

I saw two strange messages...

/usr/lib/gtkdialog/box_splash  no such file

/usr/bin/fixmenus  permission denied

I don't know if it is important. Just reporting.
pfind has box_splash file so maybe it's important.
_______________________________________

jamesbond wrote: Sun Jul 23, 2023 3:36 pm

@Duprate, please open terminal, and type "geany" and, and report error message you see.

Hello Jamesbond! Below is a screen from the terminal...

I'm using the default installation (AUFS)

In FatDog-813, it gives the same message however, it works normally.....

don570 wrote: Sun Jul 23, 2023 9:44 pm

but I still get ld-linux complaint when attempting to launch a windows exe file

@don570, I cannot reproduce this. Perhaps because I have already fixed the bug without knowing it. We are already many commits ahead of alpha. Perhaps wait until get to beta release (which should be soon) before we attack the problem again?

When running a pinstall.sh file for install of WINE 5.11
viewtopic.php?p=94671#p94671

I saw two strange messages...

Code: Select all

/usr/lib/gtkdialog/box_splash  no such file

Code: Select all

/usr/bin/fixmenus  permission denied

I don't know if it is important. Just reporting.
pfind has box_splash file so maybe it's important.

Yes we don't use box_splash nor do we use /usr/lib/gtkdialog/box_splash (I think this was meant to replace yaf-splash, which is not working in many Puppies, but in Fatdog we fixed it and it works well so we never went to the box_splash route). It should be harmless, all you miss is a few notices.

____________________________

@Duprate, on your test 900 system where geany is failing, can you tell me what is your hostname? Also what is the value of the TZ environment variable? Also what is the symlink /etc/localtime points to?

# hostname
# echo $TZ
# ls -l /etc/localtime

Dear Fatdog crew
I booted the Fatdog-64-814.iso in a VM (checked the md5 to be correct) and installed it in a vfat formatted usb thumbdrive (next to fatdog 813 and other puppies). I chose the small initrd setup (as I had done in 813) and booted through reFind with identical settings as shown bellow (with or without the savefile parameter)
In all cases I get to a grey desktop with no icons and menubar, any warning windows have no decoration, mouse and keyboard do not work in this laptop and in general looks like the window manager is broken as well as modules ot firmware is missing.
Unfortunately, I can not get a terminal to see any info for the problem and I did not try the standard initrd to boot from the USB
Any suggestions welcome
Thank you

menuentry FatDog-813 {
    icon EFI/BOOT/icons/fatdog.png
    volume FAT
    loader /FatDog813/vmlinuz
    initrd /FatDog813/initrd
    options "pkeys=bbig rootfstype=ramfs waitdev=3 video=displayport:2880x1800 savefile=ram:uuid:NNNN-1DEE:/FatDog813/fd64save.ext4 basesfs=ram:uuid:NNNN-1DEE:/FatDog813/fd64.sfs "
#   disabled
}

menuentry FatDog-814 {
    icon EFI/BOOT/icons/fatdog.png
    volume FAT
    loader /FatDog814/vmlinuz
    initrd /FatDog814/initrd
    options "pkeys=bbig rootfstype=ramfs waitdev=3 video=displayport:2880x1800  savefile=ram:uuid:NNNN-1DEE:/FatDog814/fd64save.ext4   basesfs=ram:uuid:NNNN-1DEE:/FatDog814/fd64.sfs "
#   disabled
}

Are you saying 813 boots and 814 doesn't?
Why is there a space before the closing quotation on the option line.
What happens when the option line is commented out?

retiredt00 wrote: Mon Jul 24, 2023 10:27 am

Dear Fatdog crew
I booted the Fatdog-64-814.iso in a VM (checked the md5 to be correct) and installed it in a vfat formatted usb thumbdrive (next to fatdog 813 and other puppies). I chose the small initrd setup (as I had done in 813) and booted through reFind with identical settings as shown bellow (with or without the savefile parameter)
In all cases I get to a grey desktop with no icons and menubar, any warning windows have no decoration, mouse and keyboard do not work in this laptop and in general looks like the window manager is broken as well as modules ot firmware is missing.
Unfortunately, I can not get a terminal to see any info for the problem and I did not try the standard initrd to boot from the USB
Any suggestions welcome
Thank you

Code: Select all

menuentry FatDog-813 {
    icon EFI/BOOT/icons/fatdog.png
    volume FAT
    loader /FatDog813/vmlinuz
    initrd /FatDog813/initrd
    options "pkeys=bbig rootfstype=ramfs waitdev=3 video=displayport:2880x1800 savefile=ram:uuid:NNNN-1DEE:/FatDog813/fd64save.ext4 basesfs=ram:uuid:NNNN-1DEE:/FatDog813/fd64.sfs "
#   disabled
}

menuentry FatDog-814 {
    icon EFI/BOOT/icons/fatdog.png
    volume FAT
    loader /FatDog814/vmlinuz
    initrd /FatDog814/initrd
    options "pkeys=bbig rootfstype=ramfs waitdev=3 video=displayport:2880x1800  savefile=ram:uuid:NNNN-1DEE:/FatDog814/fd64save.ext4   basesfs=ram:uuid:NNNN-1DEE:/FatDog814/fd64.sfs "
#   disabled
}

Dear Smokey thanks for the interest

smokey01 wrote: Mon Jul 24, 2023 12:31 pm

Are you saying 813 boots and 814 doesn't?

Indeed, this is correct

smokey01 wrote: Mon Jul 24, 2023 12:31 pm

Why is there a space before the closing quotation on the option line.

This is left over from additional options that have been deleted. It does not make any difference (at least in 813)

smokey01 wrote: Mon Jul 24, 2023 12:31 pm

What happens when the option line is commented out?

As I mentioned my setup is using the small initrd. Without kernel options it can not find anything and goes to bulldog, where without a functional keyboard can not do much

Can you (or anyone else) boot Fatdog 814 with the small initrd from a VFAT drive?

jamesbond wrote: Mon Jul 24, 2023 7:46 am

@Duprate, on your test 900 system where geany is failing, can you tell me what is your hostname? Also what is the value of the TZ environment variable? Also what is the symlink /etc/localtime points to?

Code: Select all

# hostname
# echo $TZ
# ls -l /etc/localtime

Hi Jamesbond! Well, "/etc/localtime" in my case is not a link, it's a text file .... (old methods of solving old problems, which I don't even remember anymore)

retiredt00 wrote: Mon Jul 24, 2023 10:27 am

Unfortunately,..... I did not try the standard initrd to boot from the USB

I did try booting from the same USB drive with the big initrd (and no options in the kernel command line) and takes considerable more time but it boots fine.
I did repeat the installation with the small initrd, in case something was wrong in the first one and the problem remains

Just in case is of any use, the md5sum of the files after splitting are

6de7bcfa3fefc3fc23d8f776eccaa00e  fd64.sfs
be6625d917c05c68b80b06f46371ccb8  initrd
70445e7d18318e64a45b8f3f6a190e81  VERSION
61b58f51ec619ca452378a837018d56e  vmlinuz

retiredt00 wrote: Mon Jul 24, 2023 5:11 pm

I did try booting from the same USB drive with the big initrd (and no options in the kernel command line) and takes considerable more time but it boots fine.
I did repeat the installation with the small initrd, in case something was wrong in the first one and the problem remains

1. How did you split the initrd? Please post the command line you used.
2. What's the size of your /tmp? Open terminal and type "df -h /tmp" and please post the result.
3. What's the size of resulting fd64.sfs? It should be either around 580MB or 350MB, depending on which option you use (-mini or -micro).

Duprate wrote: Mon Jul 24, 2023 3:29 pm

Hi Jamesbond! Well, "/etc/localtime" in my case is not a link, it's a text file .... (old methods of solving old problems, which I don't even remember anymore)

OK, here is what's wrong with your installation.

1. hostname cannot contain slashes or dots. "GNU/Linux" is bad, no matter how much you are a fan of GNU "GNU.Linux" is also bad. "GNU-Linux" is acceptable.
2. Your old methods of solving old problem doesn't work anymore. /etc/localtime must be a symlink to one of the REAL timezone files in /usr/share/zoneinfo. I suggest /usr/share/zoneinfo/Brazil/East

Do that, and then trye launch geany it again. Then report back. Thank you.

jamesbond wrote: Mon Jul 24, 2023 11:01 pm

retiredt00 wrote: Mon Jul 24, 2023 5:11 pm

I did try booting from the same USB drive with the big initrd (and no options in the kernel command line) and takes considerable more time but it boots fine.
I did repeat the installation with the small initrd, in case something was wrong in the first one and the problem remains

1. How did you split the initrd? Please post the command line you used.
2. What's the size of your /tmp? Open terminal and type "df -h /tmp" and please post the result.
3. What's the size of resulting fd64.sfs? It should be either around 580MB or 350MB, depending on which option you use (-mini or -micro).

Dear Jamesbon
Regarding your questions,
No command line was used. Just the GUI apps
Fatdog control panel > install> Fatdog64 Installer and click on "use small initrd" check box.

Regarding sizes

$df -h /tmp
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           2.0G  404K  2.0G   1% /tmp

$ ls -lh
total 566M
-rwxr-x--- 1 root root 547M Jul 24 16:36 fd64.sfs
-rwxr-x--- 1 root root  12M Jul 24 16:37 initrd
-rwxr-x--- 1 root root  100 Jul 24 16:36 VERSION
-rwxr-x--- 1 root root 7.7M Jul 24 16:36 vmlinuz

@retiredt00 Ah, okay, I think the problem is that your tmpfs (2GB) is too small to be able to properly split the initrd. Fatdog has grown in size that 2GB is no longer enough to contain the uncompressed SFS + the newly-build SFS (that's what the split-initrd do). This we can see because your fd64.sfs is only 547MB, when it should have been ~580MB.

What you can do, is to split it manually. If you split it manually, you can specify "temporary location" where to contain the uncompressed SFS whlle it is being split. By default this "temporary location" is /tmp, but if you run the command from terminal, manually, you can split it to other location. Note that this "temporary location" must be a proper linux filesystem, like ext3 or ext4 and not VFAT or NTFS.

You can split the initrd from 814 while you're running 813 (the command is the same and hasn't changed between the two versions). You run the command, and tell it to look at the original 814 initrd (which you put somewhere), and it will produce smaller-initrd and fd64.sfs, which you can use to boot 814.

The command is "fatdog-split-initrd.sh" and if you run it without any parameter, it will tell you what to do.

jamesbond wrote: Tue Jul 25, 2023 8:38 am

@retiredt00 Ah, okay, I think the problem is that your tmpfs (2GB) is too small to be able to properly split the initrd. Fatdog has grown in size that 2GB is no longer enough to contain the uncompressed SFS + the newly-build SFS (that's what the split-initrd do). This we can see because your fd64.sfs is only 547MB, when it should have been ~580MB.

Dear Jamesbond
I increased the VM memory so tempfs was 4GB and now fd64.sfs is ~590MB and the system boots fine.
Thank you!
You may want to change the 800MB requirement for the "use small initrd" check box to appear, though or maybe introduce some integrity test.

retiredt00 wrote: Tue Jul 25, 2023 9:12 am

Dear Jamesbond
I increased the VM memory so tempfs was 4GB and now fd64.sfs is ~590MB and the system boots fine.
Thank you!
You may want to change the 800MB requirement for the "use small initrd" check box to appear, though or maybe introduce some integrity test.

Thank you for the confirmation. I have updated the requirement to 3.6GB for Fatdog64 900, just to be on the safe side (uncompressed 900 takes about 2.6GB).

jamesbond wrote: Mon Jul 24, 2023 11:01 pm

Duprate wrote: Mon Jul 24, 2023 3:29 pm

Hi Jamesbond! Well, "/etc/localtime" in my case is not a link, it's a text file .... (old methods of solving old problems, which I don't even remember anymore)

OK, here is what's wrong with your installation.

1. hostname cannot contain slashes or dots. "GNU/Linux" is bad, no matter how much you are a fan of GNU "GNU.Linux" is also bad. "GNU-Linux" is acceptable.
2. Your old methods of solving old problem doesn't work anymore. /etc/localtime must be a symlink to one of the REAL timezone files in /usr/share/zoneinfo. I suggest /usr/share/zoneinfo/Brazil/East

Do that, and then trye launch geany it again. Then report back. Thank you.

Okay, Jamesbond! This was the problem! I followed your instructions and Geany worked correctly.
Thanks!
I promise not to bother you anymore.....

Dear fatdog crew
just to let you know that updating from 813 to 814 (using the same savefile) went smoothly with just one out of tree module that needed update after the kernel change.
Thanks again

Regarding out of tree modules I was wondering how difficult would be to incorporate dkms in fatdog 900. I noticed the LFS does not include dkms so I'm sure is far from simple, but given your expertise one can wish for it.

I. icake language txzes:
I have created 5 half-Chinese language txzes for fatdog64-814:
fcitx Chinese input platform: fcitx64_4.2.7-en-zh-raring-321.0.5.txz (21 mb)
gcin Chinese input platform: gcin64_2.8.5-en-zh-raring-321.0.5.txz (13 mb)
hime Chinese input platform: hime64_0.9.10-en-zh-raring-321.0.5.txz (10 mb)
scim Chinese input platform: scim64_1.4.14-en-zh-raring-321.0.5.txz (14 mb)
yong Chinese input platform: yong64_2.5.0-en-zh-raring-321.0.5.txz (10 mb)

Plus 2 Chinese language txzes each for fatdog64-814:
Simplified Chinese: fatdog64-814-zhcn-321.0.5.txz (4 mb)
Traditional Chinese: fatdog64-814-zhhk-321.0.5.txz (3 mb)

To use:
(a) any 1 of the 5 half-Chinese language pets will enable you to display and input Chinese in fatdog64-814

(b) the 2 name+version number corresponding Chinese language pets will give you Simplified Chinese (zhcn) or Traditional Chinese (zhhk) menus, icon labels, tooltips for fatdog64-814. Please note that all Chinese language pets rely on a suitable half-Chinese language pet already installed to the system to provide Chinese input platform and Chinese fonts. Otherwise the system cannot input Chinese and display Chinese (shown as squares).

II. icake combo txz
I have also created an icake combo txz for fatdog64-814 with all 5 Chinese input platforms above and 3 user interface languages
icake64-fatdog64-813-combo-est-fghsy.txz (70 mb)

III. icake combo live iso
I have also remastered 1 icake combo live iso based on fatdog64-814 with all 5 Chinese input platforms above and 3 user interface languages：
icake64-Fatdog64-814-est-fghsy.iso (709 mb)

so the total number of different systems created by the above icake combo txz and combo live iso is 15:
15 = 5 Chinese input platforms (fcitx, gcin, hime, scim or yong) X 3 user interface languages (English, Simplified Chinese and Traditional Chinese)

more information about the fcitx, gcin, hime, ibus, scim and yong pets

@icake, thank you very much from the fatdog team!

@retiredt00, you're welcome.

As for this:

retiredt00 wrote: Wed Jul 26, 2023 7:11 am

Regarding out of tree modules I was wondering how difficult would be to incorporate dkms in fatdog 900. I noticed the LFS does not include dkms so I'm sure is far from simple, but given your expertise one can wish for it.

dkms is now available in repo, and will be included in future devx.sfs (post-beta releases, it's too late to make it into beta).

jamesbond wrote: Fri Aug 04, 2023 2:56 am

dkms is now available in repo, and will be included in future devx.sfs (post-beta releases, it's too late to make it into beta).

That is nice!
I tried to locate the package(s) it in http://distro.ibiblio.org/fatdog/* to give it a try with 900 beta, but I did not manage.
Where is it? Under what name?
Thank you

Sorry, I built it but forgot to upload it. It's there now: http://distro.ibiblio.org/fatdog/packag ... arch-1.txz
Run the gslapt package manager for easier access instead of downloading manually.

Dear jamesbond
Just to let you know that dkms add, build and install worked fine in building and loading a usable out of tree module.
It requires both the devx and the kernel source SFSs to work of course, which is a lot of extra files but is ok.
Hopefully, will do the update automatically in the next kernel change (if devx and source is loaded at startup)
Thanks a lot.