ISO from gumanzoy's liveusb-doglinux-debian-12-2024.10.08

[fredx181]

*** ISO made from gumanzoy's liveusb-doglinux-debian-12-2024.10.08 ***

Updated 2024-10-08, ISO replaced.

For who prefer an ISO of @gumanzoy's share https://forum.puppylinux.com/viewtopic. ... 473#p88473 , see info and download:
https://github.com/doglinux/book-worm/releases/tag/v1.2

gumanzoy's post 2024.10.05 about it : https://forum.puppylinux.com/viewtopic. ... 93#p132393

Tested (and works for me) with Legacy boot and UEFI boot:
- using Ventoy for direct ISO booting (select grub2 mode, not normal mode)
- writing the iso to USB with dd e.g. dd bs=1M if=gumanzoy-doglinux-debian-12-2024.10.08.iso of=/dev/sdX status=progress oflag=sync
(replace sdX for what it should be for you, e.g. sdb)

The ISO contains all from gumanzoy's share (LiveUSB tree), I've added files e.g. grub.cfg, menu.lst, isolinux/live.cfg containing all the different boot choices.

P.S. Added stanza: "DebianDog 64bit Linux changes to folder /deb__dog" for when booted ISO directly (e.g. from Ventoy), to make changes saved in that case, create a folder "deb__dog" on some Linux partition (e.g. ext4) and it should be found.

2024-10-07_21-59-59.png (22.09 KiB) Viewed 1323 times

[fredx181]

Will refresh the ISO later after @gumanzoy fixed a problem: viewtopic.php?p=132524#p132524

[gumanzoy]

@fredx181

Done. New version 2024.10.08 uploaded. Files changed:

Code: Select all

live/dk5/initrd1.xz
live/dk5/k-5.10.0-32-amd64.squashfs
live/dk5/vmlinuz1
live/optional/dkms.squashfs
live/optional/headers-5.10.0-32-amd64.squashfs
live/optional/headers-6.10.12-amd64.squashfs
live/optional/nv340.108-k5.10.0-32-amd64.squashfs
live/optional/nv340.108-k6.10.12-amd64.squashfs
live/optional/nv390.157-k5.10.0-32-amd64.squashfs
live/optional/nv390.157-k6.10.12-amd64.squashfs
live/optional/nvidia-550.120-k6.10.12-amd64.squashfs
live/initrd1.xz
live/k-6.10.12-amd64.squashfs
live/vmlinuz1

Annother way for create iso from liveusb tree described in iso_doglinux/iso_doglinux_readme_en.txt
Provided iso_doglinux/boot/grub/grub.cfg

Code: Select all

mv live* ./iso_doglinux
grub-mkrescue --locales= -volid DogLinux -o doglinux.iso ./iso_doglinux

Only grub2 without isolinux.
Can boot with Ventoy in normal mode. But need to enable VTOY_LINUX_REMOUNT option.

---

And for Ventoy i have better way to installation described in install_en.txt
By custom grub2 menu ventoy/ventoy_grub.cfg

Copy folders live live32 and ventoy to drive.
When boot Ventoy menu appears - press F6 to show DebianDog menu.

[fredx181]

@fredx181

Done. New version 2024.10.08 uploaded. Files changed:

Code: Select all

live/dk5/initrd1.xz
live/dk5/k-5.10.0-32-amd64.squashfs
live/dk5/vmlinuz1
live/optional/dkms.squashfs
live/optional/headers-5.10.0-32-amd64.squashfs
live/optional/headers-6.10.12-amd64.squashfs
live/optional/nv340.108-k5.10.0-32-amd64.squashfs
live/optional/nv340.108-k6.10.12-amd64.squashfs
live/optional/nv390.157-k5.10.0-32-amd64.squashfs
live/optional/nv390.157-k6.10.12-amd64.squashfs
live/optional/nvidia-550.120-k6.10.12-amd64.squashfs
live/initrd1.xz
live/k-6.10.12-amd64.squashfs
live/vmlinuz1

....

Thanks, ISO now updated to v2024-10-08, see first post.

[Clarity]

Hello @gumanzoy AND @fredx181

I have begun preliminary testing of this distro by booting and running it "live" as I do with all of the forum distros. Nothing new in my testing...except today, it occurs to me that I have NOT done a QEMU VM test with a "Persistence" labeled disk containing a folder named "Sessions". This is the approach I have tested and documented in all other forum distros from KLs to WoofCEs to the Derivatives and to FATDOGs as well as the distro from the Project area of the forum over the past 5 years.

I would like some guidance on this and other DOGs that exist in Fred's subarea. I view this as minimal as I am sure you understand from your work.

Question
Would you recommend a boot stanza where it will find/save its persistent save session on a disk labeled "Persistence" contained in a folder named "Sessions", please?

I ask this as I want to build a boot stanza that matches the kind of direction in KL to that folder.

Thansk for any guidance and I will test and report back here.

BTW: I have booted this ISO within a VM using this following QEMU VM definition to desktop without issue upon its arrival.

Code: Select all

qemu-system-x86_64 -name "ISO booting for DOGs" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -cdrom gumanzoy-doglinux-debian-12-2024.10.08.iso

My KVM that would accompany a disk for storage appropriately setup for sessions looks like this

Code: Select all

qemu-system-x86_64 -name "ISO booting for DOGs" -enable-kvm -vga std -m 2G -smp 2 -device AC97 -net nic -net user -rtc base=localtime -cdrom gumanzoy-doglinux-debian-12-2024.10.08.iso -hdb /mnt/sdd3/Persisitence/PERSISTENCE.qcow2

Repeating my request I would like a recommendation for a menu item of this distro which would direct save-session to be found/placed on Persistence drive in its Session folder...exactly the same as is defined by boot menu of KL distros.

DOG ISO's boot menu.jpg (37.93 KiB) Viewed 1125 times

.

Another idea: would be to implement a strategy in boot menu of future DOGs, if reasonable, for a consistent location with KLs for saving a session to a persistence disk.

[fredx181]

Hi @Clarity

Would you recommend a boot stanza where it will find/save its persistent save session on a disk labeled "Persistence" contained in a folder named "Sessions", please?

If you modify changes=... at the second entry to changes=LABEL:Persistence/Sessions it should work, a folder "changes" will be automatically created in Sessions then.
Also just changes=/Sessions will do if there's no "Sessions" folder on some other partition than your Persistence labeled partition.
(for to save changes only at shutdown or on demand, make it: changes=EXIT:LABEL:Persistence/Sessions)

But the easiest (as I mentioned in first post too, without any need for modification) is to create a folder deb__dog on your Persistence partition and just run the second entry (again, then no other partition should contain "deb__dog").

EDIT: FYI, if you also boot other "dog" based distros, with the same changes=LABEL:Persistence/Sessions then it will conflict (as /Sessions/changes is the same), so to avoid that it's best to create a new folder with a unique name in Sessions named after the distro, e.g. in this case "gumanzoy-iso" and modify to changes=LABEL:Persistence/Sessions/gumanzoy-iso

[Clarity]

@fredx181, Thanks

Also, as you explain, I could, merely, modify the "deb__dog" stanza to be "Sessions" and saves would be placed within the Sessions folder on the Persistence labeled partition...Correct?

This would be excellent as the DOG sessions will be saved within the same folder that my KLs are saved. This is simple housekeeping.

If so, I will test and report back later today.

[fredx181]

@fredx181, Thanks

Also, as you explain, I could, merely, modify the "deb__dog" stanza to be "Sessions" and saves would be placed within the Sessions folder on the Persistence labeled partition...Correct?
...

Yes, just changes=/Sessions will work too (it will be found, but if there's also Sessions folder existing on some other partition, then better use LABEL or UUID).
See btw, EDIT at my previous post too.

[Clarity]

Thanks @fredx181

On each PC I've ever setup or used, there is ONLY 1 partition named Persistence; on that partition is Sessions folder for keep ALL forum distros within. I do not have a Sessions folder on any other storage attached to PCs.

I am about to set a new PC that has NO OS or distro installed. That PC will exist containing a Persistence partition for persistence sessions and a DATA partition ONLY for user data. There will be NO bootable internal drives on this PC.

With the forum distro technologies, there is ZERO need to have or install an OS/distro physically on any PC. All forum distro ISO files can be booted directly and each distro has technologies to find its save-session within Sessions folder on the Persistence partition. Thus NO installations are ever required. This has been proven over the past 3 years with KLs (aka @wiak, @gyrog and @rockedge) being the inspiration to this end along with WoofCE PUPs.

KLs support persistence with a 'standard' supported Boot Menu setup while PUPs do it via a SAVESPEC file within the USB folder containing the ISO files.

Since no installations are needed, the systems all start from a common USB that is used to launch any ISO file it contains. This remove all chances for user errors and reduces ALL distro efforts to a mere download and boot.

Puppy Forum has given users, who are aware of this, a new degree of simplicity.

"Imagine a PC with NO distro or OS installed capable to boot and operate for use from any of this forum's distros (except 1)."

[fredx181]

@Clarity Rather off-topic your above reply IMHO, as it's mostly about ISO booting in general and not about the contents of this project from gumanzoy.
(but that's okay, just saying )

edit: the reason I posted this in the first place is for some convenience (for who prefer an ISO from gumanzoy's live-usb setup for some reason).

[Clarity]

Testing gumanzoy-doglinux-debian-12-2024.10.08.iso

Been delayed, but trying to catch up.

Todays test are within a KVM from a USB start. The KVM machine is as follows where /dev/sdd is the USB stick:

Code: Select all

qemu-system-x86_64 -enable-kvm -m 2G -vga std -smp 2 -device AC97 -net nic -net user -rtc base=localtime -name "DOG test" -hda /dev/sdd -hdb /mnt/sdd3/Persisitence/PERSISTENCE.qcow2

There are 2 results screens below: 1st pic is ISO file boot failure when launched from Ventoy... the other pic is ISO file boot success when launched from SG2D The SG2D results are exactly the same as booting the distro in KVM directly from its ISO file,

The COPY2RAM boot menu option is taken in ALL tests.

Ventoy launch of ISO fails

DOG test(1).jpg (53.17 KiB) Viewed 848 times

SG2D launch of ISO SUCCESSFUL

DOG test(2).jpg (55.4 KiB) Viewed 848 times

[rcrsn51]

It also boots fine off an ISObooter3 USB drive.

[Clarity]

Testing on bare-metal. Booted via Ventoy to a desktop

Looked for couple familiar (within most forum distros, today) admin tools, OOTB; namely TLDR, BTOP, NEOFETCH/FASTFETCH and HARDINFO.

Open PM only to discover this PC did not get IP credential from the DHCP host on the network. So PM cannot be updated or used to add needed admin tools. Rebooted to use the 64bit version using the 'other' kernel. Stiill no credentials.

Checked for familiar network admin tools, but ...

Am aborting all of my testing

[fredx181]

Testing on bare-metal. Booted via Ventoy to a desktop.
...
Open PM only to discover this PC did not get IP credential from the DHCP host on the network. So PM cannot be updated or used to add needed admin tools. Rebooted to use the 64bit version using the 'other' kernel. Stiill no credentials.
...

Can you explain a bit more about that problem ? I don't understand what you mean exactly.

[rcrsn51]

I tested this with an ISObooter boot on a machine with wired Ethernet. It grabbed an IP address right away.

[Clarity]

Bare-Metal test of Ventoy launching the ISO file on a AMD AIO PC. Boots and finds hardware resources without issue. This includes wired ethernet with LAN active upon boot.

The prior problem is on a 2012 Intel with a nVidia video card. If no one else is reporting such, I'd consider this platform independent problem.

Further, KVM boots the ISO file direct with ethernet active as well

It would me a 'nice' if the admin tools, mentioned earlier, are included should a new release is planned.

[gumanzoy]

The prior problem is on a 2012 Intel with a nVidia video card. If no one else is reporting such, I'd consider this platform independent problem.

Hi.

Problem with ethernet connection? Can you show lspci -v and ifconfig output?

I suspect Broadcom chip with tg3 kernel module. If so - try to run rmmod tg3 && modprobe tg3

[Clarity]

Hello @gumanzoy and @fredx181

Just completed a bare-metal test on a different nVidia test PC I have. Everything is working, as expected. Some PC details:

Screenshot_2024-10-19_04-51-03.png (163.31 KiB) Viewed 598 times

Screenshot_HardInfo2-1.jpg (116.2 KiB) Viewed 598 times

Screenshot_HardInfo2-2.jpg (134.68 KiB) Viewed 598 times

[Clarity]

The REALLY neat thing about your distro is its boot time ability to discover and bring in my nVidia-HDMI OOTB connection without any need for extra steps to activate use of nvidia driver.

BUT: I cannot seem to find the steps to move the audio from the PC's internal speaker to the TV over HDMI. HELP!

Screenshot_neofetch.png (111 KiB) Viewed 597 times

Screenshot_Sound is not outputting to TV - ONLY to PC internal speaker.jpg (17.26 KiB) Viewed 597 times

When the audio server is upgraded and admin tool qpwgraph is available the task to discovery may be a bit easier to visualize what is happening with system-application audio.

[Clarity]

Yes, the problem is isolated to that single platform. Next time it is restarted, i will collect the info that @gumanzoy has requessed.

Can you show lspci -v and ifconfig output?

Further this is the only ISO file that fails in getting the adapter on this particular PC.

[gumanzoy]

@Clarity

The REALLY neat thing about your distro is its boot time ability to discover and bring in my nVidia-HDMI OOTB connection without any need for extra steps to activate use of nvidia driver.

Yes. OOTB support of nvidia proprietary drivers is killer feature.

BUT: I cannot seem to find the steps to move the audio from the PC's internal speaker to the TV over HDMI. HELP!

When the audio server is upgraded and admin tool qpwgraph is available the task to discovery may be a bit easier to visualize what is happening with system-application audio.

Sorry i don't use PipeWire. I use sound in my build only to check notebooks stereo speakers is working.
For this case ALSA only is enough.

But included sound-card-selector tool to help with create config .asoundrc

sound-card-selector.png (67.6 KiB) Viewed 584 times

[Clarity]

Code: Select all

root@live:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever

lspci-v command.txt

(15.53 KiB) Downloaded 5 times

[Clarity]

Screenshot_SoundcardSelelctor2.png (69.13 KiB) Viewed 559 times

No matter what I do to change audio from PC to the HDMI, no go here.

[gumanzoy]

@Clarity @fredx181

lspci-v command.txt

Yes Broadcom tg3

Code: Select all

05:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
	Subsystem: Dell NetLink BCM57780 Gigabit Ethernet PCIe
	Flags: fast devsel, IRQ 17
	Memory at fbff0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [48] Power Management version 3
	Capabilities: [60] Vendor Specific Information: Len=6c <?>
	Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [cc] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Virtual Channel
	Capabilities: [160] Device Serial Number 00-25-64-ff-fe-e4-40-8f
	Capabilities: [16c] Power Budgeting <?>
	Kernel modules: tg3

Try to run rmmod tg3 && modprobe tg3

I know about this problem. If kernel module tg3 loaded in initrd by linuxrc - it is not work. Until rmmod and modprobe again.
I suspect lack of firmware or it may have softdep on some other module (from kernel/drivers/net/phy/ maybe).
This problem also prevent to boot from PXE by this card.
I don't have this hardware to check. It is really rare now. Almost all is realtek and intel.

To fix function in runtime but not PXE. Remove tg3 from /usr/local/cr-initrd/initramfs/modlist
Then run /usr/local/cr-initrd/mkinitrd to create new initrd1.xz for kernel you use.
But i don't know how you can update it in .iso file. I recommend to boot from live folder makes easy to update some modules.

If you use 5.10 kernel - before run /usr/local/cr-initrd/mkinitrd need comment out
line 55 #cp /usr/share/nvidia/nvidia.ids $INITRAMFS/usr/share/nvidia/ and uncomment
line 57 cp /usr/share/nvidia/nvidia-legacy-340xx.ids $INITRAMFS/usr/share/nvidia/

To make nvidia_detect works correct.
Because i don't build current version nvidia-550.120 modules for 5.10 kernel.

[Clarity]

Out of time. I can follow the steps when the PC is free again.

[gumanzoy]

@Clarity

Screenshot_SoundcardSelelctor2.png
No matter what I do to change audio from PC to the HDMI, no go here.

Screenshot_2024-10-19_09-32-17.png (81.83 KiB) Viewed 550 times

Select HDMI card, press Select button and then copy lines from window to /root/.asoundrc
Then restart application you use to play sound.

Out of time. I can follow the steps when the PC is free again.

In is not very important. I think rare hardware because only 2 person for 3 years report about problem with it.

[rcrsn51]

Regarding HDMI audio: In alsamixer, check that the SPDIF control is UNmuted. Also test the other HDMI device numbers. It's often higher than 3.

Regarding tg3. It's either missing firmware or a timing problem. The network manager in this OS is not waiting long enough for the hardware to initialize, so the request for a DHCP address fails.

This may require a startup script that unloads/reloads the tg3 driver, then makes another DHCP request.

[gumanzoy]

Regarding tg3. It's either missing firmware or a timing problem. The network manager in this OS is not waiting long enough for the hardware to initialize, so the request for a DHCP address fails.

This may require a startup script that unloads/reloads the tg3 driver, then makes another DHCP request.

It is not network manager problem.
ip addr not show eth0

I check it earlier (2.5 years ago) when i have limited time access to some Acer laptop with same broadcom tg3 adapter.

Better to not load it in initrd. But for PXE network boot support need to fix initrd problem.

As i remember (but i am not 100% sure) i try to copy /usr/lib/firmware/tigon/ to initrd and it is not change anything.
And, i think, i try to rm -rf /usr/lib/firmware/tigon/ after boot and then run rmmod tg3 && modprobe tg3 and it is working without any firmware.

[fredx181]

For what it's worth, booted this on my old HP laptop, lspci gives:
18:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
It's using tg3 too, and no problems, eth0 connected instantly.

[gumanzoy]

@fredx181

For what it's worth, booted this on my old HP laptop, lspci gives:
18:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
It's using tg3 too, and no problems, eth0 connected instantly.

Interesting. Boot this .iso or another build? With porteus initrd or debian live-boot?

@rcrsn51

Regarding HDMI audio: In alsamixer, check that the SPDIF control is UNmuted. Also test the other HDMI device numbers. It's often higher than 3.

Yes. Thanks. UNmute is important!
I boot my PC with GTX 1070, edit .asoundrc as sound-card-selector suggests, then unmute all S/PDIF in alsamixer
And then i have sound on my DP monitor and my HDMI TV.
As usual i not use it. Use my soundcard and analog speakers.

@Clarity

I check sound DP/HDMI is working.

Screenshot_2024-10-19_14-42-377.jpeg (107.33 KiB) Viewed 489 times