peebee wrote: Sat Jul 01, 2023 3:04 pmLunarPup32-23.06+1 is now available - see post #1.
Kernel 5.15.119 is fixed for usb boots (thanks @one )
This fixes USB booting with ISObooter but I still cannot get Ventoy to work. Is anyone else trying this?
Moderator: Forum moderators
peebee wrote: Sat Jul 01, 2023 3:04 pmLunarPup32-23.06+1 is now available - see post #1.
Kernel 5.15.119 is fixed for usb boots (thanks @one )
This fixes USB booting with ISObooter but I still cannot get Ventoy to work. Is anyone else trying this?
Thanks. I checked some other recent Puppy releases and Ventoy didn't work there either.
Luckily, ISObooter is working properly again after some patches in woof.
Seems bionicpups and fossapup64 seem to work with ventoy but other pups may not work.
rcrsn51 wrote: Wed Jul 05, 2023 12:22 pmThanks. I checked some other recent Puppy releases and Ventoy didn't work there either.
Luckily, ISObooter is working properly again after some patches in woof.
Hi @rcrsn51,
the only recent puppys I found to work with ventoy (v1.0.89) are FP96_CE4 (incl. fusilli), quickpup64_23.01 and upup-22.04-jrb-D1 - others are not "ventoy-compatible" ...
I like your isobooter, it is much more reliable than ventoy and much quicker.
peace
PS: sorry to dilute your thread @peebee
Latest LunarPup always boots into a black screen. Frugal install on HDD.
Main: Debian + Mageia + Windows 10 on a AMD Ryzen 7 machine.
bert07 wrote: Wed Jul 19, 2023 8:43 pmLatest LunarPup always boots into a black screen. Frugal install on HDD.
Thanks @bert07
There does seem to be a config problem with the 5.15 kernel with respect to Intel graphics....
I have raised a GitHub Issue: https://github.com/puppylinux-woof-CE/w ... ssues/4120
A workaround is to boot to the console with PFIX=nox
and then type: xwin
Kernel 5.10 does not have the problem - attached are the INTEL configs for 5.10 and 5.15 - can anybody see where the problem might be??
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
522d81b200690c8a309d65cc8bec8813 LunarPup32-23.06+2.iso
see post #1
still a CUPS problem
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
This appears to be a Ghostscript problem. I dropped in a very old GS package and got some printing to work. But that's not a solution.
Looks like it's looking for default_gray.icc form libgs-common. This package is missing, but installing it doesn't make the problem go away.
dimkr wrote: Sun Aug 13, 2023 7:53 amLooks like it's looking for default_gray.icc form libgs-common. This package is missing, but installing it doesn't make the problem go away.
Added that package and also printer-driver-cups-pdf via a ydrv - some progress as printing to pdf now occurs but only in monochrome - no colour - so something else is missing......
Bookworm64Pup is also only printing in monochrome. As is JammyPup32.....
Looking at what Bookworm64Pup has from it's /var/packages/DISTRO_PKGS_SPECS:
Code: Select all
# after dependency resolution by resolvedeps.sh
PKGS_SPECS_TABLE='
yes|cups|cups,cups-bsd,printer-driver-cups-pdf,foomatic-db-compressed-ppds,libcups2-dev,cups-client,cups-common,cups-core-drivers,cups-daemon,cups-filters,cups-ppdc,cups-server-common,ghostscript,poppler-utils,libpaper-utils,dpkg-dev,libcupsimage2-dev,cups-filters-core-drivers,ssl-cert,libpaper1,libcupsfilters1,libfontembed1,libqpdf29,libgs10,libpoppler126,libdpkg-perl,libcupsimage2,cups-ipp-utils,libpoppler-cpp0v5,libgs10-common,poppler-data,libidn12,libijs-0.35,libjbig2dec0,libopenjp2-7,libnspr4,libnss3,fonts-urw-base35,libgs-common|exe,dev,doc,nls||deps:yes
as compared to in LunarPup32:
Code: Select all
yes|cups|cups-bsd,cups,cups-common,cups-core-drivers,cups-server-common,cups-client,cups-ppdc,libcups2,libcups2-dev,libcupsimage2,libcupsimage2-dev,cups-daemon,libsnapd-glib-2-1|exe,dev,doc>exe,nls|compat:plus
yes|cups-filters|cups-filters,cups-filters-core-drivers,printer-driver-cups-pdf,libcupsfilters1,libcupsfilters-dev,libfontembed1,libfontembed-dev|exe,dev,doc,nls|compat:plus
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
peebee wrote: Mon Aug 14, 2023 3:29 pmsome progress as printing to pdf now occurs but only in monochrome - no colour - so something else is missing......
Bookworm64Pup is also only printing in monochrome. As is JammyPup32.....
Looks like this is a Debian 12 Bookworm problem:
viewtopic.php?p=96421#p96421
which can be "fixed" with a line in /root/Startup
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
94304620e28aab405c080a6e410f3b81 LunarPup32-23.06+3.iso
CUPS-PDF printing is better but not perfect.....
Colour printing now works but some text printing doesn't - e.g.
Cups printer maintenance - Print test page works but Print Self Test Page doesn't
Printing from web browsers - images are printed but text isn't.....????
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
Hi @peebee,
Thank you for this latest version of LunarLobser.
Printing works well (tested from evince, abiword, gnumeric and mtpaint) with brother laser monochrome.
Don't tested from browser.
That's wonderful.
It seems that the Pupradio/PupTelly entry in Multimedia does not find pupradio.
By the way, I couldn't find the pupradio binary with the "find / -iname *pupradio*" command. Only the pupRadio.desktop file is found.
I "made" an adrv... with Firefox-ESR and Links : it's ok.
Thank you again for your 32bit distributions.
Bests regards.
hi folks we was bug fix "us" (default) keyboard layout in lunarpup32 with Slalom (AntonioPt).
The problem description:
Slalom was try to start pup with pkeys=pt boot parameter , sys was made the xorg.conf with xorg-autoconf, but woof-ce code still include the /root/.xkbrc file with "us" XBDLAYOUT value , and when sys is load the desktop , quicksetup show us default keyboard layout (as in woof-ce code)... this happen when have no /etc/X11/xorg.conf and sys start the xorgwizard-automatic. This script told to xorg-autoconf script to make the xorg.conf file (its ok) , but xorgwizard not change the /root/.xkbrc content ... so i edit the xorgwizard script to chage the file content with the fallowing code:
Code: Select all
#============================================================
# xorgwizard-automatic
#============================================================
if [ "$AUTOMATIC" = "1" ] ; then
if [ -x /usr/sbin/xorg-autoconf ] ; then
/usr/sbin/xorg-autoconf > /etc/X11/xorg.conf
sleep 0.1
XKB_LAYOUT="$(grep XkbLayout /etc/X11/xorg.conf | cut -f4 -d'"' | cut -c-2)"
sed -i "s%^XKB_DEFAULT_LAYOUT=.*%XKB_DEFAULT_LAYOUT=$XKB_LAYOUT%" ~/.xkbrc
THE_END=1
else
(about line 125)
Slalom was made remaster with this xorgwizard script , and evrything ok with pt (portuguese) keyboard layout ...
@KuLuSz
thank you for help to solve this problem.
I had the impression nobody is interested to find a solution.
For info only
Here my solution I am using since years.
its not correct cos Slalom has pt-latin1.gz keymap file like source in /lib/keymaps dir and if its set it in the .xkbrc file as pt-latin1, is not work , just with the pt value (i dont know why)
anyway may have problems with azerty dvorak and other keymaps too ... there is not fix the problem with my idea...
beacause xkb modes only support 2 char names as example portuguese:
Code: Select all
grep -i "\!\|portuguese" /etc/X11/xkb/rules/base.lst
! model
yahoo Yahoo! Internet Keyboard
! layout
br Portuguese (Brazil)
pt Portuguese
! variant
nodeadkeys br: Portuguese (Brazil, eliminate dead keys)
dvorak br: Portuguese (Brazil, Dvorak)
nativo br: Portuguese (Brazil, Nativo)
nativo-us br: Portuguese (Brazil, Nativo for US keyboards)
nodeadkeys pt: Portuguese (eliminate dead keys)
sundeadkeys pt: Portuguese (Sun dead keys)
mac pt: Portuguese (Macintosh)
mac_nodeadkeys pt: Portuguese (Macintosh, eliminate dead keys)
mac_sundeadkeys pt: Portuguese (Macintosh, Sun dead keys)
nativo pt: Portuguese (Nativo)
nativo-us pt: Portuguese (Nativo for US keyboards)
! option
hey @KuLuSz as you can see the layout is pt or br pt for Portugues and br for Brazil so what ever script that is geting pt-latin1 is doing some wrong but with our fix problem solve but if we can figure out what who is writing to keymap file pt-latin1 and fix issue there better all so
Thx for all
Why astronauts use Linux
Because you can't open windows in space
hello all i need it poedit to start making Portugues translation and so i download poedit-1.4.2-3-i686.pt but since one lib that crash hexchat i made a new pet for lunnarpup
Hope it helps http://patinsemlinhaslalom.altervista.o ... 2-i686.pet
Why astronauts use Linux
Because you can't open windows in space
Hello @peebee how are you hope all good
i was trying to fix Grafic issues in my old machine with @KuLuSz and the some amout drivers that HunPup are all so in lunarPup but im not able to run LunarPup
i have to use pfix=nox and run xorgwizard and set to fbdev any solutions ideas ?
Intel GMA 950
Machine is this one if helps https://pt.wikipedia.org/wiki/Port%C3%A ... lh%C3%A3es
Thxx in Advance
Why astronauts use Linux
Because you can't open windows in space
AntonioPt wrote: Fri Jan 12, 2024 5:12 pmHello @peebee how are you hope all good
i was trying to fix Grafic issues in my old machine with @KuLuSz and the some amout drivers that HunPup are all so in lunarPup but im not able to run LunarPup
i have to use pfix=nox and run xorgwizard and set to fbdev any solutions ideas ?
Intel GMA 950
Machine is this one if helps https://pt.wikipedia.org/wiki/Port%C3%A ... lh%C3%A3esThxx in Advance
Try:
i915.modeset=0
see: viewtopic.php?t=6598
or maybe select intel driver when you run xorgwizard ...........
Builder of LxPups, SPups, UPup32s, VoidPups; LXDE, LXQt, Xfce addons; Chromium, Firefox etc. sfs; & Kernels
hi @peebee Thxx gonna check all and test it and let it know if works meanwhile i put it Kernel Kernel 5.10.135-oz-pea that did work 100% kernel 5.10.198 didnt give no sound or networks lolol
Screen size issue me and @KuLuSz are going to analyze some scripts that are making this problem one of them is xorg-autoconf that im working allready the othwe is xorgwizard
Why astronauts use Linux
Because you can't open windows in space
Hi everyone,
So in order to fix my issue since my old my machine the size aint correct as you guys can see it and i get crop on left and right side of screnn every time i load my OS "since i don't use a save folder/file", so i add this peace of code in to xwin script
Code: Select all
MAX_RES=$(xrandr -q | grep " " | awk '{ print $1 }' | sort --unique --field-separator "x" -h -r | head -1)
xrandr -s $MAX_RES
since this next command give me a complete different value from xrandr
Ex: xrandr will give me 2034x1208 and kernel i got 3034x2033
Code: Select all
MAX_RES="$(cat $(grep -H ^c $(realpath $(ls -1 /s*/c*/drm/*/status)) | sed 's/st.*/modes/') | sort -n -k1 | tail -1)"es'
i all so notice when i add this code "Kernel" in xorg-autoconf to add size in it i never have value when OS is loading all so
Hope it helps in any way
A big thxx to @KuLuSz for the time he spend with me and all of you as well
Why astronauts use Linux
Because you can't open windows in space
This show xrandr preferable resolutions:
Code: Select all
MAX_RES="$(xrandr -q | grep "^ " | awk '{ print $1 }' | sort --unique --field-separator "x" -h -r | head -1)"
This show the connected video outputs kernel-drm preferable resolutions:
Code: Select all
MAX_RES="$(cat $(grep -H ^c $(realpath $(ls -1 /s*/c*/drm/*/status)) | sed 's/st.*/modes/') | sort -n -k1 | tail -1)"
This show the connected video outputs kernel-drm-edid(binaryfile) parsed monitor description:
Code: Select all
cat $(grep -H ^c $(realpath $(ls -1 /s*/c*/drm/*/status)) | sed 's/st.*/edid/') | parse-edid
Checksum Correct
Section "Monitor"
Identifier "hp 7550"
ModelName "hp 7550"
VendorName "HWP"
# Monitor Manufactured week 47 of 2003
# EDID version 1.3
# Analog Display
DisplaySize 320 240
Gamma 2.80
Option "DPMS" "true"
Horizsync 30-86
VertRefresh 50-140
# Maximum pixel clock is 180MHz
#Not giving standard mode: 640x480, 85Hz
#Not giving standard mode: 800x600, 85Hz
#Not giving standard mode: 1024x768, 85Hz
#Not giving standard mode: 1600x1200, 65Hz
Modeline "Mode 0" 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
EndSection
Last command getting from barryk blog.
Note: in some new puppy system need to use realpath cos parse-edid command cannot read the simple path edid file like : /sys/class/drm/card*/edid
Hello all i got a small issue,
So if i change the layout of the desktop icons the defaultfilemanager Home icon never display what may be the file that is missing ? any one got a clue ?
Thxx in Advance
Why astronauts use Linux
Because you can't open windows in space
Hello all,
in LunarPup and HunPup globicons in /root/.config/rox.sourceforce.net/ROX-Filer need to be update it in order every time we change icons display the icons we chose
Why astronauts use Linux
Because you can't open windows in space
need small help @peebee ,
so my LunarPup i dont have no safe folder,... but still says it mount in /initrd/mnt/dev_save any idea why this is happen ?
thxx in advange
Why astronauts use Linux
Because you can't open windows in space