Puppy Linux Discussion Forum

Hello Everyone!

Can someone help me to fix my screen size / resolution ?

I tried different options but the only one that works is 1920x1200 but is too big and I cant see parts of the screen ( low bar )

I had to minimize the windows to work. Not impossible but better if we can solve it.

Also when a I play a video in full screen , is not working in big size, just stay in one size or sometimes duplicates.

In this same hardware when I used to have MacPup, Wary, or Race everything in the screen worked perfectly.

manual says (LCD 14.1" WXGA 1280x800 TFT LCD Accelerator Sis M672 ( says in the manual compatible with DirectX 9.0 ))

But I just want to use the last OS possible. Internet is running fine with Chromium or Firefox .SFS . Just Feeling that the laptop is going to fly as an helicopter.... hahahaha, but the rest is working perfectly.

So I preffer to put all the possible information...

Please just sendme the code!!! I dont understand to much about this ... yet!!!!

Thanks!!!!

Pablo

VIDEO REPORT: JammyPup32, version 22.04
Processor: Intel(R) Core(TM) Duo CPU T2450 @ 2.00GHz

X.Org X Server 1.20.11
X Protocol Version 11, Revision 0

Chip description:

01:00.0 VGA compatible controller [0300]: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] [1106:3371] (rev 01)
Subsystem: CLEVO/KAPOK Computer Device [1558:5408]
Kernel modules: viafb

Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: glx
Drivers requested to be loaded: vesa

Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): vesa
Loaded modules: ddc fb glx int10 libinput shadow synaptics vbe

Actual rendering on monitor:
Resolution: 1920x1200 pixels (508x318 millimeters)
Depth: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Mesa/X.org
OpenGL renderer string: llvmpipe (LLVM 11.0.1, 128 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 20.3.5

...the above also recorded in /tmp/report-video

***********

-Computer-
Processor : 2x Intel(R) Core(TM) Duo CPU T2450 @ 2.00GHz
Memory : 1921MB (307MB used)
Machine Type : Physical machine
Operating System : JammyPup32 - 22.04
User Name : root (root)
Date/Time : Tue Jun 7 10:48:00 2022
-Display-
Resolution : 1920x1200 pixels
OpenGL Renderer : llvmpipe (LLVM 11.0.1, 128 bits)
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA VIA VT82xx
Audio Adapter : PC-Speaker - pcsp
-Input Devices-
AT Translated Set 2 keyboard
USB OPTICAL MOUSE
Power Button
Sleep Button
Lid Switch
Power Button
Video Bus
PC Speaker
HDA VIA VT82xx Rear Mic
HDA VIA VT82xx Front Mic
HDA VIA VT82xx Line
HDA VIA VT82xx Line Out
HDA VIA VT82xx Front Headphone
SynPS/2 Synaptics TouchPad
-Printers (CUPS)-
CUPS-PDF : <i>Default</i>

*****************************************

# lscpu
Architecture: i686
CPU op-mode(s): 32-bit
Address sizes: 32 bits physical, 32 bits virtual
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Vendor ID: GenuineIntel
BIOS Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM) Duo CPU T2450 @ 2.00GHz
BIOS Model name: Intel(R) Core(TM) Duo CPU T2
CPU family: 6
Model: 14
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
Stepping: 12
CPU max MHz: 2000.0000
CPU min MHz: 800.0000
BogoMIPS: 3990.08
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov clflush dts acpi mmx fxsr sse sse2 ht tm pbe nx co
nstant_tsc arch_perfmon bts cpuid aperfmperf pni monitor
est tm2 xtpr pdcm pti dtherm
Caches (sum of all):
L1d: 64 KiB (2 instances)
L1i: 64 KiB (2 instances)
L2: 2 MiB (1 instance)
Vulnerabilities:
Itlb multihit: KVM: Mitigation: VMX unsupported
L1tf: Mitigation; PTE Inversion
Mds: Vulnerable: Clear CPU buffers attempted, no microcode; S
MT disabled
Meltdown: Mitigation; PTI
Spec store bypass: Not affected
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer
sanitization
Spectre v2: Mitigation; Retpolines, STIBP disabled, RSB filling
Srbds: Not affected
Tsx async abort: Not affected
#

***********

up-SysInfo Hardware Report (Complete), Tue 7 Jun 2022

Current Time: 10:49:34
System Uptime: 0d 0h 39m
Load Average: 0.46 0.40 0.37
Processes: 139 total, 2 running

▶—— BASE SYSTEM ——◀

PC Manufacturer: Positivo
Product Name: Positivo Mobile
Serial Number: 2163608
UUID: 0090f55c-4a5d-0000-0000-000000000000

Motherboard Vendor: CLEVO Co.
Product Name: M550SE/M660SE
Version: VT6363A
Serial Number: 1234567890

Kernel Release: 5.10.113 (i686)
Build Date: #1 SMP Mon May 9 05:56:45 UTC 2022
Build GCC: 10.2.1-6
PAE Enabled: Yes

Kernel Command Line:
initrd=/ubninit ntldr=/boot/grub/grldr BOOT_IMAGE=/ubnkern

Distro: JammyPup32 22.04
Window Manager: JWM v2.3.7
Desktop Start: xwin jwm

Development:
Bash: 5.1.16
Geany: 1.29
Gtkdialog: 0.8.5 (GTK2)
Perl: 5.34.0
Yad: 0.42.1 (GTK+ 2.24.33)
--
busybox: 1.35.0
dhcpcd: 6.7.1
Glibc: 2.35
OpenSSL: 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022), built on: Wed Mar 16 08:35:51 2022 UTC
wpa_supplicant: 2.9

Username: root
Language: en_US.UTF-8
Keyboard: br-abnt
Timezone: America/Sao_Paulo

Firewall: On (ip_tables active)
Network Interface: wlan0
Wireless Network: CLARO_2GC127A2
Bit Rate=54 Mb/s Tx-Power=20 dBm
Link Quality=65/70 Signal=-45 dBm
Wireless strength: 92%
Session Data: Received 3.2 MB, Sent 265.0 KB
Monthly Data: Received 43 MB, Sent 2 MB

Hostname: puppypc10846
Network IP Address: 192.168.0.34
Domain Name Server (DNS): 181.213.132.4
181.213.132.5
Hardware Address (MAC): 00:15:AF:1C:CA:37

Boot Partition: sdb1 (Size 3.8G, Free 2.8G)
Boot File System: vfat

PUPMODE=13
PUPSFS=sdb1,vfat,/puppy_upupjj+d_22.04.sfs
PUPSAVE=sdb1,vfat,/upupjj+dsave-PabloJammy2022June.2fs

▶—— BIOS ——◀

Vendor: Phoenix Technologies LTD
Version: 6.00
Release Date: 02/27/2007
Runtime Size: 98144 bytes
ROM Size: 64 kB

▶—— CENTRAL PROCESSOR ——◀

Intel(R) Core(TM) Duo CPU T2450 @ 2.00GHz
Socket Designation: mPGA 479m
Manufacturer: GenuineIntel
Voltage: 3.3 V
External Clock: 200 MHz
Min/Max Speed: 800/2000 MHz
Current Speed of Core 0:2000 MHz, 1:1067 MHz
Core Count: 2
64-bit capable: No

Frequency governor : ondemand
Freq. scaling driver : acpi-cpufreq

CPU Vulnerabilities:
itlb_multihit:KVM: Mitigation: VMX unsupported
l1tf:Mitigation: PTE Inversion
mds:Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
meltdown:Mitigation: PTI
spec_store_bypass:Not affected
spectre_v1:Mitigation: usercopy/swapgs barriers and __user pointer sanitization
spectre_v2:Mitigation: Retpolines, STIBP: disabled, RSB filling
srbds:Not affected
tsx_async_abort:Not affected

Core 0 (coretemp) : +50.0 C (high = +NA.0 C, crit = +85.0 C)
Core 1 (coretemp) : +52.0 C (high = +NA.0 C, crit = +85.0 C)
thermal () : +NA.0 C (high = +NA.0 C, crit = +NA.0 C)

▶—— COMPUTER MEMORY ——◀

Personal Storage File:
Name: /upupjj+dsave-PabloJammy2022June.2fs
Total Size: 512 MB
Free Space: 481 MB
Location: partition sdb1

Memory Allocation:
Total RAM: 1876 MB
Used RAM: 1274 MB
Free RAM: 602 MB
Buffers: 12 MB
Cached: 960 MB
Total Swap: 998 MB
Free Swap: 998 MB

Actual Used RAM: 302 MB Used - (buffers + cached)
Actual Free RAM: 1574 MB Free + (buffers + cached)

Memory Statistics:
MemTotal: 1921760 kB
MemFree: 612604 kB
MemAvailable: 1068560 kB
Buffers: 12548 kB
Cached: 983836 kB
SwapCached: 0 kB
Active: 217712 kB
Inactive: 984740 kB
Active(anon): 121788 kB
Inactive(anon): 440040 kB
Active(file): 95924 kB
Inactive(file): 544700 kB
Unevictable: 0 kB
Mlocked: 0 kB
HighTotal: 1063432 kB
HighFree: 13600 kB
LowTotal: 858328 kB
LowFree: 599004 kB
SwapTotal: 1022972 kB
SwapFree: 1022972 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 206080 kB
Mapped: 147516 kB
Shmem: 355760 kB
KReclaimable: 27224 kB
Slab: 69320 kB
SReclaimable: 27224 kB
SUnreclaim: 42096 kB
KernelStack: 1536 kB
PageTables: 5652 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 1983852 kB
Committed_AS: 1305168 kB
VmallocTotal: 122880 kB
VmallocUsed: 10492 kB
VmallocChunk: 0 kB
Percpu: 416 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
Hugetlb: 0 kB
DirectMap4k: 18424 kB
DirectMap2M: 882688 kB

—— Physical Memory ——

Installed Memory: 2 GB
Maximum Memory: 4 GB
Number Of Slots: 3

Memory Module 1
Data Width: 64 bits
Size: 2 GB
Form Factor: DIMM
Locator: M1
Type: DRAM
Type Detail: Synchronous
Speed: Unknown
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified

Memory Module 2
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Locator: M2
Type: DRAM
Type Detail: Synchronous
Speed: Unknown
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified

Memory Module 3
Data Width: Unknown
Size: No Module Installed
Form Factor: DIMM
Locator: M3
Type: DRAM
Type Detail: Synchronous
Speed: Unknown
Manufacturer: Not Specified
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified

Internal Cache
Configuration: Enabled, Socketed, Level 1
Installed Size: 16 kB

External Cache
Configuration: Enabled, Socketed, Level 2
Installed Size: 2 MB

Cache Information
Configuration: Enabled, Socketed, Level 3
Installed Size: 2 MB

▶—— COMPUTER RESOURCES ——◀

MEMORY REGISTERS USED BY
================ =======
00000000-00000fff : Reserved
00001000-0009dbff : System RAM
0009dc00-0009ffff : Reserved
000a0000-000bffff : Video RAM area
000c0000-000cffff : Video ROM
000d0000-000d1fff : Adapter ROM
000e0000-000fffff : Reserved
000f0000-000fffff : System ROM
00100000-77e7ffff : System RAM
19000000-19e1dc54 : Kernel code
19e1e000-1a24cfff : Kernel rodata
1a24e000-1a40143f : Kernel data
1a52c000-1a5b5fff : Kernel bss
77e80000-77e91fff : ACPI Tables
77e92000-77efffff : ACPI Non-volatile Storage
77f00000-7fffffff : Reserved
a0000000-bfffffff : PCI Bus 0000:01
a0000000-bfffffff : 0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01)
c0000000-c7ffffff : 0000:00:00.0 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
c8000000-c87fffff : PCI Bus 0000:02
c8800000-c8ffffff : PCI Bus 0000:04
c9000000-c9ffffff : PCI Bus 0000:01
c9000000-c9ffffff : 0000:01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01)
ca000000-ca7fffff : PCI Bus 0000:02
ca800000-caffffff : PCI Bus 0000:04
cb000000-cb0fffff : PCI Bus 0000:06
cb000000-cb003fff : 0000:06:01.0 Audio device: VIA Technologies, Inc. VX900/VT8xxx High Definition Audio Controller (rev 10)
cb000000-cb003fff : ICH HD audio
cb100000-cb1fffff : PCI Bus 0000:07
cb100000-cb1000ff : 0000:07:04.1 SD Host controller: ENE Technology Inc ENE PCI SmartMedia / xD Card Reader Controller
cb100000-cb1000ff : mmc0
cb100100-cb1001ff : 0000:07:04.3 FLASH memory: ENE Technology Inc ENE PCI Secure Digital / MMC Card Reader Controller
cb100100-cb1001ff : mmc1
cb100200-cb10027f : 0000:07:04.0 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller
cb400000-cb4000ff : 0000:00:10.4 USB controller: VIA Technologies, Inc. USB 2.0 EHCI-Compliant Host-Controller (rev 86)
cb400000-cb4000ff : ehci_hcd
cb400400-cb4004ff : 0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102/VT6103 [Rhine-II] (rev 7c)
cb400400-cb4004ff : via-rhine
e0000000-efffffff : Reserved
e0000000-efffffff : pnp 00:00
e0000000-e06fffff : PCI MMCONFIG 0000 [bus 00-06]
f0012000-f0012fff : pnp 00:00
f0013000-f0013fff : pnp 00:00
fec00000-fec0ffff : Reserved
fec00000-fec003ff : IOAPIC 0
fecc0000-fecc03ff : IOAPIC 1
fee00000-fee00fff : Local APIC
fee00000-fee00fff : Reserved
ffee0000-ffefffff : pnp 00:02
fff00000-ffffffff : Reserved
fff00000-ffffffff : pnp 00:02

COM PORTS USED BY
========= =======
0000-001f : dma1
0020-0021 : pic1
0022-0022 : ACPI PM2_CNT_BLK
0040-0043 : timer0
0050-0053 : timer1
0060-0060 : keyboard
0061-0061 : PNP0800:00
0062-0062 : PNP0C09:00
0062-0062 : EC data
0064-0064 : keyboard
0066-0066 : PNP0C09:00
0066-0066 : EC cmd
0070-0075 : rtc0
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : PNP0C04:00
00f0-00ff : fpu
0170-0177 : 0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
0170-0177 : pata_via
01f0-01f7 : 0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
01f0-01f7 : pata_via
0376-0376 : 0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
0376-0376 : pata_via
03c0-03df : vga+
03f6-03f6 : 0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
03f6-03f6 : pata_via
04d0-04d1 : pnp 00:03
0cf8-0cff : PCI conf1
4000-407f : pnp 00:03
4000-4003 : ACPI PM1a_EVT_BLK
4004-4005 : ACPI PM1a_CNT_BLK
4008-400b : ACPI PM_TMR
4020-4023 : ACPI GPE0_BLK
4050-4053 : ACPI GPE1_BLK
4100-411f : pnp 00:03
4100-4107 : vt596_smbus
4400-44ff : 0000:00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80)
4400-44ff : sata_via
4800-48ff : 0000:00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102/VT6103 [Rhine-II] (rev 7c)
4800-48ff : via-rhine
4c00-4c1f : 0000:00:10.0 USB controller: VIA Technologies, Inc. VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller (rev a0)
4c00-4c1f : uhci_hcd
4c20-4c3f : 0000:00:10.1 USB controller: VIA Technologies, Inc. VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller (rev a0)
4c20-4c3f : uhci_hcd
4c40-4c5f : 0000:00:10.2 USB controller: VIA Technologies, Inc. VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller (rev a0)
4c40-4c5f : uhci_hcd
4c60-4c7f : 0000:00:10.3 USB controller: VIA Technologies, Inc. VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller (rev a0)
4c60-4c7f : uhci_hcd
4c80-4c8f : 0000:00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80)
4c80-4c8f : sata_via
4c90-4c9f : 0000:00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
4c90-4c9f : pata_via
4ca0-4ca3 : 0000:00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80)
4ca0-4ca3 : sata_via
4ca4-4ca7 : 0000:00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80)
4ca4-4ca7 : sata_via
4ca8-4caf : 0000:00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80)
4ca8-4caf : sata_via
4cb0-4cb7 : 0000:00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80)
4cb0-4cb7 : sata_via
5000-6fff : PCI Bus 0000:02
7000-8fff : PCI Bus 0000:04
fe00-fe00 : pnp 00:03
fe10-fe11 : pnp 00:03

▶—— NETWORK (SAMBA) SHARED RESOURCES ——◀

smbclient Version 4.7.0 smbd Version 4.7.0
nmblookup Version 4.7.0
nmbd Version 4.7.0

▸testparm -s

# Global parameters
[global]
server string = Puppy Samba Server
printcap name = cups
map to guest = Bad Password
security = USER
idmap config * : backend = tdb

[puppyshare]
path = /mnt/home
read only = No

[printers]
comment = All Printers
path = /var/spool/samba
browseable = No
printable = Yes
guest ok = Yes

▶—— DEVICES: INPUT ——◀

Bus=0011 Vendor=0001 Product=0001 Version=ab41
Name="AT Translated Set 2 keyboard"
Connected to: isa0060/serio0/input0

Bus=0003 Vendor=0000 Product=3825 Version=0111
Name=" USB OPTICAL MOUSE"
Connected to: usb-0000:00:10.1-1/input0

Bus=0019 Vendor=0000 Product=0001 Version=0000
Name="Power Button"
Connected to: PNP0C0C/button/input0

Bus=0019 Vendor=0000 Product=0003 Version=0000
Name="Sleep Button"
Connected to: PNP0C0E/button/input0

Bus=0019 Vendor=0000 Product=0005 Version=0000
Name="Lid Switch"
Connected to: PNP0C0D/button/input0

Bus=0019 Vendor=0000 Product=0001 Version=0000
Name="Power Button"
Connected to: LNXPWRBN/button/input0

Bus=0019 Vendor=0000 Product=0006 Version=0000
Name="Video Bus"
Connected to: LNXVIDEO/video/input0

Bus=0010 Vendor=001f Product=0001 Version=0100
Name="PC Speaker"
Connected to: isa0061/input0

Bus=0000 Vendor=0000 Product=0000 Version=0000
Name="HDA VIA VT82xx Rear Mic"
Connected to: ALSA

Bus=0000 Vendor=0000 Product=0000 Version=0000
Name="HDA VIA VT82xx Front Mic"
Connected to: ALSA

Bus=0000 Vendor=0000 Product=0000 Version=0000
Name="HDA VIA VT82xx Line"
Connected to: ALSA

Bus=0000 Vendor=0000 Product=0000 Version=0000
Name="HDA VIA VT82xx Line Out"
Connected to: ALSA

Bus=0000 Vendor=0000 Product=0000 Version=0000
Name="HDA VIA VT82xx Front Headphone"
Connected to: ALSA

Bus=0011 Vendor=0002 Product=0007 Version=81b1
Name="SynPS/2 Synaptics TouchPad"
Connected to: isa0060/serio4/input0

▶—— DEVICES: MONITOR/VIDEO ——◀

Display Specifications:
• Screen Name: default
• Screen VertRefresh: 0.00 times/s
• Screen Resolution: 1920x1200 pixels (508x318 millimeters)
• Screen Depth: 24 bits (planes)

Xorg Startup Log (/var/log/Xorg.0.log):
• Xorg Driver in use: vesa
• Loaded Modules: ddc fb glx int10 libinput shadow synaptics vbe
• X.Org version: 1.20.11

OpenGL 2D/3D Rendering:
• Direct Rendering: Yes
• Vendor: Mesa/X.org
• Renderer: llvmpipe (LLVM 11.0.1, 128 bits)
• Version: 3.1 Mesa 20.3.5

VGA compatible controller:
• VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01)
• Video RAM: 1876M total, 512M prefetchable

▶—— DEVICES: MULTIMEDIA/SOUND ——◀

Audio device [0403]: VIA Technologies, Inc. VX900/VT8xxx High Definition Audio Controller [1106:3288] (rev 10)
• Kernel Driver: snd_hda_intel
• Memory Used: 36.00 KB
• Path: /lib/modules/5.10.113/kernel/sound/pci/hda/snd-hda-intel.ko
• Description: Intel HDA driver

▶—— DEVICES: NETWORK ——◀

Ethernet controller [0200]: VIA Technologies, Inc. VT6102/VT6103 [Rhine-II] [1106:3065] (rev 7c)
• Kernel Driver: via-rhine

▶—— DEVICES: NOTEBOOK BATTERY (BAT0) ——◀

Specifications:
NAME=BAT0
STATUS=Full
TECHNOLOGY=Li-ion
MODEL_NAME=BAT1
MANUFACTURER=NOTEBOOK

Capacity Summary:
Remaining capacity: 64665 mAh, 100.0% of last full capacity
Design capacity: 4000 mAh
Last full capacity: 64665 mAh, 1616.6% of design capacity
Capacity loss: -1516.6%

▶—— DEVICES: PCI INTERFACES ——◀

Host bridge
• VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
• VendorID=1106 DeviceID=0364
• Kernel Driver=agpgart-via

Host bridge
• VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
• VendorID=1106 DeviceID=1364

Host bridge
• VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
• VendorID=1106 DeviceID=2364

Host bridge
• VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
• VendorID=1106 DeviceID=3364

Host bridge
• VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
• VendorID=1106 DeviceID=4364

PIC
• VIA Technologies, Inc. CN896/VN896/P4M900 I/O APIC Interrupt Controller
• VendorID=1106 DeviceID=5364

Host bridge
• VIA Technologies, Inc. CN896/VN896/P4M900 Security Device
• VendorID=1106 DeviceID=6364

Host bridge
• VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
• VendorID=1106 DeviceID=7364

PCI bridge
• VIA Technologies, Inc. VT8237/CX700/VX700-Series PCI to PCI Bridge
• VendorID=1106 DeviceID=b198

PCI bridge
• VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller
• VendorID=1106 DeviceID=a364 Rev=80
• Kernel Driver=pcieport

PCI bridge
• VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller
• VendorID=1106 DeviceID=c364 Rev=80
• Kernel Driver=pcieport

IDE interface
• VIA Technologies, Inc. VT8237A SATA 2-Port Controller
• VendorID=1106 DeviceID=0591 Rev=80
• Kernel Driver=sata_via

IDE interface
• VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE
• VendorID=1106 DeviceID=0571 Rev=07
• Kernel Driver=pata_via

USB controller
• VIA Technologies, Inc. VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller
• VendorID=1106 DeviceID=3038 Rev=a0
• Kernel Driver=uhci_hcd

USB controller
• VIA Technologies, Inc. VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller
• VendorID=1106 DeviceID=3038 Rev=a0
• Kernel Driver=uhci_hcd

USB controller
• VIA Technologies, Inc. VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller
• VendorID=1106 DeviceID=3038 Rev=a0
• Kernel Driver=uhci_hcd

USB controller
• VIA Technologies, Inc. VT82xx/62xx/VX700/8x0/900 UHCI USB 1.1 Controller
• VendorID=1106 DeviceID=3038 Rev=a0
• Kernel Driver=uhci_hcd

USB controller
• VIA Technologies, Inc. USB 2.0 EHCI-Compliant Host-Controller
• VendorID=1106 DeviceID=3104 Rev=86
• Kernel Driver=ehci-pci

ISA bridge
• VIA Technologies, Inc. VT8237A PCI to ISA Bridge
• VendorID=1106 DeviceID=3337
• Kernel Module=i2c_viapro

Host bridge
• VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller
• VendorID=1106 DeviceID=287e

Ethernet controller
• VIA Technologies, Inc. VT6102/VT6103
• VendorID=Rhine-II
• VendorID=1106 DeviceID=3065 Rev=7c
• Kernel Driver=via-rhine
• Kernel Module=via_rhine

PCI bridge
• VIA Technologies, Inc. VT8237A Host Bridge
• VendorID=1106 DeviceID=337b

PCI bridge
• VIA Technologies, Inc. VT8237A PCI to PCI Bridge
• VendorID=1106 DeviceID=337a

VGA compatible controller
• VIA Technologies, Inc. CN896/VN896/P4M900
• VendorID=Chrome 9 HC
• VendorID=1106 DeviceID=3371 Rev=01
• Kernel Module=viafb

Audio device
• VIA Technologies, Inc. VX900/VT8xxx High Definition Audio Controller
• VendorID=1106 DeviceID=3288 Rev=10
• Kernel Driver=snd_hda_intel
• Kernel Module=snd_hda_intel

FLASH memory
• ENE Technology Inc ENE PCI Memory Stick Card Reader Controller
• VendorID=1524 DeviceID=0730

SD Host controller
• ENE Technology Inc ENE PCI SmartMedia / xD Card Reader Controller
• VendorID=1524 DeviceID=0750
• Kernel Driver=sdhci-pci

FLASH memory
• ENE Technology Inc ENE PCI Secure Digital / MMC Card Reader Controller
• VendorID=1524 DeviceID=0751
• Kernel Driver=sdhci-pci

▶—— DEVICES: PRINTERS ——◀

DefaultPrinter CUPS-PDF

▶—— DEVICES: USB ——◀

VendorID=1d6b ProductID=0002 Rev=05.10
Manufacturer=Linux 5.10.113 ehci_hcd
Product=EHCI Host Controller
SerialNumber=0000:00:10.4
Driver=hub

VendorID=058f ProductID=6387 Rev=01.03
Manufacturer=Generic
Product=Mass Storage
SerialNumber=39646992
Driver=usb-storage

VendorID=1d6b ProductID=0001 Rev=05.10
Manufacturer=Linux 5.10.113 uhci_hcd
Product=UHCI Host Controller
SerialNumber=0000:00:10.0
Driver=hub

VendorID=1d6b ProductID=0001 Rev=05.10
Manufacturer=Linux 5.10.113 uhci_hcd
Product=UHCI Host Controller
SerialNumber=0000:00:10.1
Driver=hub

VendorID=0000 ProductID=3825 Rev=01.00
Product= USB OPTICAL MOUSE
Driver=usbhid

VendorID=1d6b ProductID=0001 Rev=05.10
Manufacturer=Linux 5.10.113 uhci_hcd
Product=UHCI Host Controller
SerialNumber=0000:00:10.2
Driver=hub

VendorID=1d6b ProductID=0001 Rev=05.10
Manufacturer=Linux 5.10.113 uhci_hcd
Product=UHCI Host Controller
SerialNumber=0000:00:10.3
Driver=hub

--

Bus 001 Device 004: ID 0bda:8187 Manufacturer_Realtek_RTL8187_ RTL8187_Wireless
Bus 001 Device 002: ID 058f:6387 Generic Mass Storage
Bus 001 Device 001: ID 1d6b:0002 Linux 5.10.113 ehci_hcd EHCI Host Controller
Bus 005 Device 001: ID 1d6b:0001 Linux 5.10.113 uhci_hcd UHCI Host Controller
Bus 004 Device 001: ID 1d6b:0001 Linux 5.10.113 uhci_hcd UHCI Host Controller
Bus 003 Device 002: ID 0000:3825 USB OPTICAL MOUSE
Bus 003 Device 001: ID 1d6b:0001 Linux 5.10.113 uhci_hcd UHCI Host Controller
Bus 002 Device 001: ID 1d6b:0001 Linux 5.10.113 uhci_hcd UHCI Host Controller

▶—— DRIVES: CD/DVD ——◀

sr0:
====

Model=Optiarc CD-RW CRX880A , FwRev=KX07 , SerialNo=
Read/Write speed:
Maximum read speed: 4234 kB/s (CD 24x, DVD 3x, BD 0x)
Maximum write speed: 4234 kB/s (CD 24x, DVD 3x, BD 0x)

▶—— DRIVES: HDD ——◀

Device Name: sda:
Model Number: ST960813AS
Serial Number: 5LY2P5BN
Firmware Revision: 3.ALC
device size with M = 1024*1024: 57231 MBytes
device size with M = 1000*1000: 60011 MBytes (60 GB)

▶—— DRIVES: HDD-RAID ——◀

No active RAID drives are detected in /proc/mdstat.

▶—— DRIVES: PARTITIONS (HDD & USB) ——◀

▶ Active/Mounted Partitions (df -h):

Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 3.8G 1004M 2.8G 27% /initrd/mnt/dev_save

▶ All Partitions (probepart):

Part Type Size(MB)
==== ==== ====
sda1 ext2 41170
sda2 swap 999
sda3 ext2 5061
sda4 ext2 10000
sdb1 vfat 3849

▶ All Partitions (/root/.pup_event):

Part Type Size
==== ==== ====
sda1 ext2 40.2G [ATA ST960813AS]
sda3 ext2 4.9G [ATA ST960813AS]
sda4 ext2 9.7G [ATA ST960813AS]
sdb1 vfat 3.7G [Generic Flash Disk]

▶ Partition Attributes (blkid):

sda1: LABEL="ppal" UUID="05d05c6b-3103-44f6-b8e1-868a1e245f8d" BLOCK_SIZE="4096" TYPE="ext2" PARTUUID="000c15c9-01"
sda2: LABEL="lx" UUID="199f7124-7378-4a51-87f3-1efe61deafed" TYPE="swap" PARTUUID="000c15c9-02"
sda3: LABEL="MACPUP" UUID="589da31a-2153-4517-9a36-89e9aebf3df1" BLOCK_SIZE="4096" TYPE="ext2" PARTUUID="000c15c9-03"
sda4: UUID="452bf830-6b16-406e-b470-70871b954674" BLOCK_SIZE="4096" TYPE="ext2" PARTUUID="000c15c9-04"
sdb1: LABEL="NO NAME" UUID="58B9-1F18" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="61b644a5-01"

▶ Partition Specifications (parted):

ALERT: parted probe disabled in Preferences

▶ Partition Tables (fdisk 1):
•Disk /dev/loop0: 224.49 MiB, 235393024 bytes, 459752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


•Disk /dev/loop1: 19.38 MiB, 20320256 bytes, 39688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


•Disk /dev/loop2: 38.73 MiB, 40607744 bytes, 79312 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


•Disk /dev/loop3: 20.71 MiB, 21721088 bytes, 42424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


•Disk /dev/loop4: 512 MiB, 536870912 bytes, 1048576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


•Disk /dev/loop5: 90.39 MiB, 94781440 bytes, 185120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


•Disk /dev/sda: 55.89 GiB, 60011642880 bytes, 117210240 sectors
Disk model: ST960813AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000c15c9

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 84318207 84316160 40.2G 83 Linux
/dev/sda2 115163136 117209087 2045952 999M 82 Linux swap / Solaris
/dev/sda3 104798208 115163135 10364928 4.9G 83 Linux
/dev/sda4 84318208 104798207 20480000 9.8G 83 Linux



•Disk /dev/sdb: 3.76 GiB, 4037017600 bytes, 7884800 sectors
Disk model: Flash Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x61b644a5

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 7884799 7882752 3.8G b W95 FAT32

▶—— FILESYSTEMS ——◀

Filesystem Size Used Avail Use% Mounted on
shmfs 303M 0 303M 0% /dev/shm
tmpfs 1.8G 324M 1.4G 19% /initrd/mnt/tmpfs
unionfs 1.8G 324M 1.4G 19% /
/dev/loop4 504M 24M 481M 5% /initrd/pup_ro1
/dev/sdb1 3.8G 1004M 2.8G 27% /initrd/mnt/dev_save

=== END OF HARDWARE REPORT ===

This report is also available in
/tmp/root/PSI-HW-COMPLETE-220607.

Section "Device"
Identifier "Card0"
Driver "vesa" #card0driver
EndSection

Section "Screen"
Identifier "Screen0"
# Device "Card0"
Monitor "Monitor0"
# DefaultDepth 24
#Option "metamodes" "1280x800_60 +0+0" #METAMODES_0
Subsection "Display"
Depth 24 #screen0depth
# Modes "1024x768" #screen0modes
EndSubsection
EndSection

=== END OF ACTIVITY REPORT ===

This report is also available in
/tmp/root/PSI-SYS-SUMMARY-220607.

***************

HARDWARE REPORT: /tmp/root/PSI-HW-COMPLETE-220607
SYSTEM ACTIVITY: /tmp/root/PSI-SYS-SUMMARY-220607
COMPLETE REPORT: /tmp/root/PSI-SYS-COMPLETE-220607

4e192d6c6671ecafde479f24d1a80096 JammyPup32-22.04+4.iso

Just Ubuntu & Woof-CE updates

see post #1

jwm > lxde / lxqt / xfce

Clarity wrote: ↑Mon Apr 25, 2022 8:47 am

Although JammyPUP32 is much better as it is a fully featured PUP, just tested VoidPUP32 booting it, as well, via its ISO file on this eeePC.

Performs without issues, same as JammyPUP32.

Personally, I like the better featured JammyPUP32 if I needed to continue use of this PC. (I am returning it back to its moth-balled state. Just wanted to test the ISO file boot process on this ancient PC; it works and performs an one should expect any PUP to perform.)

Hope this info is insightful for use of the ISO file boot methods posted in the forum.

do I understand you can boot up a puppy from iso file/folder without first copying to HD or USB?

fc224abc69c6b32e90dbcb33aa34af7b JammyPup32-22.04+5.iso

Just Ubuntu & Woof-CE updates

see post #1

gychang wrote: ↑Thu Aug 04, 2022 11:35 pm

do I understand you can boot up a puppy from iso file/folder without first copying to HD or USB?

YES

@peebee has all of his WoofCE designs built such that a USB can contain his ISO files and be booted with no more effort than a mere download and boot. This is true for all modern WoofCE PUPs except one, for all the DOGs, and for KLV, as well.

I have been booting such for several years and since its initial discovery, I have never copied or installed a PUP-DOG in years while having ALL the benefits of a Frugal use. Repeating, PUPs/DOGs operates with ALL of its subsystems including persistence.

Anyone can boot any PUP-DOG within 1 minute after download with NO other action except to download the ISO file and boot.

ITs a user/developer's dream come true. It is not only foolproof, but a 'productivity' gain for all.

Other forum members have done so as well.

Clarity wrote: ↑Sat Aug 06, 2022 12:04 am

gychang wrote: ↑Thu Aug 04, 2022 11:35 pm

do I understand you can boot up a puppy from iso file/folder without first copying to HD or USB?

YES

@peebee has all of his WoofCE designs built such that a USB can contain his ISO files and be booted with no more effort than a mere download and boot. This is true for all modern WoofCE PUPs except one, for all the DOGs, and for KLV, as well.

I have been booting such for several years and since its initial discovery, I have never copied or installed a PUP-DOG in years while having ALL the benefits of a Frugal use. Repeating, PUPs/DOGs operates with ALL of its subsystems including persistence.

Anyone can boot any PUP-DOG within 1 minute after download with NO other action except to download the ISO file and boot.

ITs a user/developer's dream come true. It is not only foolproof, but a 'productivity' gain for all.

Other forum members have done so as well.

I should clarify first...
Is it possible while booted into FP64, I can download e.g. BP64(bionicpup64).iso and now I can boot into BP64? I thought one has to copy vmlinz, linuz, *.sfs to HD or USB first followed by grub2dos... then boot into BP64 but directly from iso?? If one can boot directly from *.iso I would like more details on this.

peebee wrote: ↑Fri Aug 05, 2022 4:11 pm

fc224abc69c6b32e90dbcb33aa34af7b JammyPup32-22.04+5.iso

Just Ubuntu & Woof-CE updates

see post #1

Hi! I installed the latest version of Jammypup32 (UPUPJJ+D-22.04+5) in an Acer Aspire4332 notebook. I was attracted by the phrase "Ubuntu Support for Jammy Jellyfish Continues Until April 2027". A great incentive! Working very well, in an overlayfs system, kernel 5.10.135. Using Seamonkey 2.53.13 as a browser. Great job Peebee!
Initially, I tested it more conventionally, installing on a flash drive through the Balenaetcher, made the boot through the flash drive and created Savefile.
I resurrected the old notebook! It was very fast!

HI @gychang, there is a better way asn note of th work you outlined. Merely download and boot the ISO file directly method.

If interested to try, send me a PM and I will guide you to the forum sites prescribing how.

This is neither a new or anything that modifies your systems disk nor how you use PUPS-DOGs from this forum.

None of what the PUP-DOGs do changes including save your session-work (persistence)

It is a significant productivity change for you if you value that. All you do is download the ISO files (yes many) and boot (any you downloaded) with NO ADDITIONAL EFFORT.

PM me and I will try to make its initial use a "5 minute to done" effort; afterwhich you just keep adding ISO files from the forum you choose.

Duprate wrote: ↑Sun Aug 07, 2022 1:14 am

peebee wrote: ↑Fri Aug 05, 2022 4:11 pm

fc224abc69c6b32e90dbcb33aa34af7b JammyPup32-22.04+5.iso

Just Ubuntu & Woof-CE updates

see post #1

Hi! I installed the latest version of Jammypup32 (UPUPJJ+D-22.04+5) in an Acer Aspire4332 notebook. I was attracted by the phrase "Ubuntu Support for Jammy Jellyfish Continues Until April 2027". A great incentive! Working very well, in an overlayfs system, kernel 5.10.135. Using Seamonkey 2.53.13 as a browser. Great job Peebee!
Initially, I tested it more conventionally, installing on a flash drive through the Balenaetcher, made the boot through the flash drive and created Savefile.
I resurrected the old notebook! It was very fast!

Hi @gychang, I think you are looking for grub4dos options as, in:

https://dev.to/suntong/grub4dos-to-boot ... image-57ho

Or

Regards

Pika

Hi! I installed the 32-bit version of Firefox, provided on the first page. It was perfect and accepted the customization I use in the 64bit version! Feels like home... Thank you Peebee!

Hi! Lots of possibilities, customizations, for this 32-bit system! All to increase the self-esteem of an old notebook....
Right now using the system on my 64bit PC....

Hello,

I'm having a little trouble booting this one up. I have no issues booting xenialpup64, bionicpup64 or fossapup64 - I use grub4dos to load any of these from a folder in the hard drive (pupmode 5). But no success with jammypup32...the kernel boots OK, but then the init says the sfs is not found. Have read in some posts that it works if you put the sfs files in root...while I would prefer to avoid that, even that doesn't work. From the looks of it, it's not mounting sda1, and hence it can't find any sfs. I can mount it manually after init exits, but only if I pass -t ntfs (don't have to pass that argument in the other pups after they boot, not sure if that's where the problem is).

The entry is this:

title Puppy jammypup32 (sda1/jammypup32)
  uuid 635465BF546GC5E1
  kernel /jammypup32/vmlinuz  pmedia=atahd psubdir=jammypup32 pfix=ram
  initrd /jammypup32/initrd.gz

Any ideas on how I can sort this one out? Last resort I'll have to try to edit init to make it as similar as possible to the other pups.

Also, when booting jammypup32 from USB (for which I used Rufus), it complains ISO9660 is not found...although in this instance it eventually does boot, after a 60 second wait. I guess I could also try to look into and remove this line from init, but any ideas why it's doing that? Doesn't happen with the other pups.

This is the grub4dos entry I use for ntfs boot:

title ntfs-boot
uuid 46BF84C01FAF29CE
kernel /ntfs-boot/vmlinuz pdrv=sda1 psubdir=/ntfs-boot pmedia=atahd pfix=fsck
initrd /ntfs-boot/initrd.gz

I notice you have psubdir=jammypup32 i.e. no /

You do need to give more details of your setup - e.g. how is the disk installed, formatted, partitioned etc. and what kind of "disk" is it?

Thanks peebee!
It was the / that was missing. For some reason, the 64 pups boot OK without it, glad it was that easy...thanks for an amazing distro

Hi,
so I download JammyPup32-22.04+5 , JammyPup32-22.04+4, and 0 as ISOs
put them all on my ventoy usb stick, selected them, and after a second of flashing screen with presumably text, I am greeted by a blinking cursor.

Now what?
loaded BionicPup32 from the USB Stick, and deletet the whole partition where I put the full install of BionicPup, reboot and .... still a blinking cursor.

Laptop is a Dell Inspiron Mini 10 which has a now shrunken windows 7 C partition and a shrunken down D partition, with ~200GB of unallocated space where BionicPup was, till I heard earlier today that I should fire up JammyPup.

So, yeah, a bit of assistance is very much welcome.

Cheers
Julian

@argonaut459 This is a KNOWN problem that is 'INDIRECTLY' alluded to on the forum.

There is a simple solution (depending if you choose to follow) to this problem: If you want some simple instructions I will comply.

Post back here if you want my instructions.

Sure I'm all ears

Hi @argonaut459

AS you are a Ventoy user, this is going to be VERY easy. I hae found that some PUPs have problems booting from the Ventoy Menu. But I have had no WoofCE PUPs have problems booting from SuperGrub2Disk (SG2D). They all boot including KLV Airdale with no issues. This can be done via any/every Ventoy USB and its simple with NO modifications to anything Ventoy. In summary you will boot the same Ventoy USB and do what you always do ... except for a single additional step that assure PUPs boot.

Steps

1. You're going to keep your Ventoy USB.

   

   Ventoy disk 1.jpg (6.69 KiB) Viewed 4364 times

   But, I want you to create a folder on the Ventoy USB named BOOTISOS and move ALL of your ISO files into that folder. Don't worry, Ventoy knows to find them

   

   Ventoy disk 2.jpg (18.9 KiB) Viewed 4364 times

2. Next, go here and copy the SuperGrub2Disk ISO file to that folder too.

3. REBOOT your Ventoy USB

4. Select the SG2D ISO file

5. When SG2D Menu emerges, merely/ONLY hit the Enter-key and wait a few moments for the next Menu

6. Scroll to the bottom and Select any one of the PUPs ISO files you see .

Any of your PUPs/DOGs ISO files will boot to desktop without any medications. Enjoy

There's nothing more to it and the Ventoy USB should boot forever servicing ALL of your ISO files you add.

Any problems, post here or on the aforementioned thread

P.S. Every WoofCE PUP works ... but Bionic and olders were created before WoofCE was built, thus they are missing the 'easy-to-boot' feature in those old ISO files.

Thank you, will try this ASAP

EDIT:
I got this one, is this correct?

Download supergrub2-2.06s1-beta2-multiarch-CD.iso
i386, x86_64, i386-efi and x86_64-efi Modern UEFI 64-bit and 32-bit systems and also old BIOS systems.

EDIT 2:
after going through the very convoluted menu of this supergrub
Jammy booted up

Now, where can I report my impressions about it?

f7c5d5015d7b05697b4f439b114086d4 JammyPup32-22.04+6.iso

see post #1

kernel updated to 5.10.142

Hi! As always, appreciating your good work!

Hi @peebee.

there is an error when updating PPM ...
(JammyPup32 +6)

peace

one wrote: ↑Thu Sep 29, 2022 10:09 am

Hi @peebee.

there is an error when updating PPM ...
(JammyPup32 +6)

peace

Apologies - there is a mangled 0setup file........

this ydrv corrects until the next release.

Thank you @peebee,

btw: your updated kernel 5.10.142 now boots fine on my ext. SSD

peace

Peebee, thanks for the last update! Much appreciated ....

JammyPup32 (UPupJJ+D-22.04+7 - (JammyJellyfish+Debian Woof-CE build 08-Oct-2022)

http://distro.ibiblio.org/puppylinux/pu ... -22.04.htm

I use UPup BionicBeaver 32 bit on Atom D525 with 4Gb RAM onboard. It is quite comfortable (only PaleMoon is not so fast as I wish). I boot it with old kernel 3.18.138-32-nopae.
If I will install this JammyPup32 instead BB, will it significantly reduce performance of my poor old monoblock?) Should I change kernel to older?
Or it will be faster and better to use more old system, like Tahr etc.?

Zedward wrote: ↑Sun Oct 09, 2022 10:21 pm

I use UPup BionicBeaver 32 bit on Atom D525 with 4Gb RAM onboard. It is quite comfortable (only PaleMoon is not so fast as I wish). I boot it with old kernel 3.18.138-32-nopae.
If I will install this JammyPup32 instead BB, will it significantly reduce performance of my poor old monoblock?) Should I change kernel to older?
Or it will be faster and better to use more old system, like Tahr etc.?

Hi! I use this system on an Acer Aspire 4332 notebook (Oct/2009), Intel Celeron 900 mobile processor, 2 GB of DDR2 667 MHz, Graphics Mobile Intel GL40 Express Chipset. Came with Windows 7. I got it as a "gift", to throw away! I didn't even look at what was inside. I immediately formatted the disk and sparingly installed JammyPup32 (UPupJJ+D-22.04), now updated +7. Initially I used Seamonkey 32bits and now I use Firefox 32, provided by Peebee. Both work very well and update in conventional mode. I also use LibreOffice, Clamav, Wine and PortableApps (some light games and PhotoShop7). It's not even such an old notebook but the configuration is rotten! But with new life!
It's a ZoombieNoteBook.......

Duprate wrote: ↑Mon Oct 10, 2022 7:56 pm

now I use Firefox 32, provided by Peebee

Is it faster than PaleMoon?

I need programs to teach students: any file manager, any browser, Office, Logo, bitmap and vector painters, any video editor, any site constructor, Geogebra.
So I use the lightest: Double Commander, PaleMoon and Vivaldi (in SFS when PaleMoon don't open site), Abiword/Gnumeric/Presentations from FreeOffice and Kexi, GImageReader on Tesseract, KTurtle with millions of dependencies (no alternatives), Dia in Wine (because I can't run Dia in Linux), standard mtPaint and Inkscape, OpenShot (it doesn't run from SFS), Kompozer (in SFS) and Geogebra (in SFS) (no alternatives).
But all these programs pull a lot of libraries and dependencies with them, including severak variations of gtk, qt4, qt5 etc. And it seems that this set is not the best and loads the system in the background heavily. The initial lightness from first frugal setup disappears. Please advise what is the best way to replace this programs we use for studying with more light without large number of dependencies.
Maybe I should replace Abiword/Gnumeric/Presentations from FreeOffice and Kexi with LibreOffice?

Zedward: I don't think you can expect much from an old notebook with a weak configuration. I don't use PaleMoon. Firefox works fine, but for your educational interests, Seamonkey with its built-in tools (browser, addressbook, composer-html-editor and mail) might be better suited. For me, the old notebook is useful but it shouldn't have big compromises. I don't leave the poor guy abandoned somewhere. In order to be thrown in the trash, it will first have to burn some vital component......