Fossapup64-9.0.3 RC

[666philb]

When I'm typing into the terminal

Code: Select all

jwm -p

it returns

Code: Select all

root# jwm -p
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
root#

I searched the JWM files, but only timidity has

++

in its name.

Removing them from the content of timidity's .desktop file doesn't change anything. The above warning still appears unchanged.

What's the problem?

hi O.F.I.N.S.I.S.

not sure what that error means. you could check
/root/.jwmrc
/root/.jwmrc-tray
/root/.jwm/jwmrc-personal
for any clues. but if everything is working i wouldn't worry.

[TiredPup]

System:
Host: puppypc31035 Kernel: 5.4.47 x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: JWM 2.4.0 Distro: Puppy 9.0.3
Machine:
Type: Laptop System: Dell product: OptiPlex 760 v: N/A serial: N/A
Mobo: Dell model: 0G919G v: A01 serial: ..CN7082196FO0U5. BIOS: Dell
v: A06 date: 12/23/2009
CPU:
Topology: Dual Core model: Intel Core2 Duo E8400 bits: 64 type: MCP
arch: Penryn rev: A L2 cache: 6144 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 11970
Speed: 2938 MHz min/max: N/A Core speeds (MHz): 1: 2938 2: 2982
Graphics:
Device-1: Intel 4 Series Integrated Graphics vendor: Dell driver: i915
v: kernel bus ID: 00:02.0
Display: server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa
resolution: 1280x1024~60Hz
OpenGL: renderer: Mesa DRI Intel Q45/Q43 (ELK) v: 2.1 Mesa 20.0.4
direct render: Yes
Audio:
Device-1: Intel 82801JD/DO HD Audio vendor: Dell driver: snd_hda_intel
v: kernel bus ID: 00:1b.0
Sound Server: ALSA v: k5.4.47
Network:
Device-1: Intel 82567LM-3 Gigabit Network vendor: Dell driver: e1000e
v: 3.2.6-k port: ece0 bus ID: 00:19.0
IF: eth0 state: down mac: 00:24:e8:34:fd:e9
Device-2: D-Link System DWA-140 RangeBooster N Adapter(rev.B2) [Ralink
RT3072]
type: USB driver: rt2800usb bus ID: 1-1.4:3
IF: wlan0 state: up mac: 78:54:2e:27:7f:c5
Drives:
Local Storage: total: 465.76 GiB used: 12.09 GiB (2.6%)
ID-1: /dev/sda vendor: Western Digital model: WD5000AAKX-08U6AA0
size: 465.76 GiB
Partition:
ID-1: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
Message: No sensors data was found. Is sensors configured?
Info:
Processes: 126 Uptime: 19m Memory: 3.69 GiB used: 249.6 MiB (6.6%)
Init: SysVinit runlevel: 35 Compilers: gcc: N/A Shell: bash v: 5.0.16
inxi: 3.0.38

I installed inxi from the Ubuntu repo. It would not start. It made a complaint about perl. I noted that perl is already installed. I did reinstall it and inxi started without complaint after that.

[O.F.I.N.S.I.S.]

hi O.F.I.N.S.I.S.

not sure what that error means. you could check
/root/.jwmrc
/root/.jwmrc-tray
/root/.jwm/jwmrc-personal
for any clues. but if everything is working i wouldn't worry.

I checked all files already including my additional JWM modification files (I have three menus, left-click, right-click & middle-click), but I had overseen /root/.jwm/jwmrc-personal.

Inside of /root/.jwm/jwmrc-personal there's some "+" characters that I need to have some functions working for JWM.

E.g:

Code: Select all

<Key mask="C+S" keycode="35">exec:amixer sset Master 1+,1+</Key>
<Key mask="C+S" keycode="61">exec:amixer sset Master 1-,1-</Key>

<!-- Switch Desktop Icons on/off (VarioMenu Group 1, Administrator) -->
<Key mask="C+S" key="1">exec: /root/Choices/ROX-Filer/restore_to_PuppyPin</Key>
<Key mask="C+S" key="2">exec: /root/Choices/ROX-Filer/remove_from_PuppyPin</Key>
<Key mask="C+S" key="3">exec: /usr/local/Clean_Desk/clean_desk</Key>

No problems so far. I was just curious about those warnings.

Thanks.

[davids45]

G'day,

Ran "jwm -p" in a terminal and quickly got a new # blank line. I assume this means no problems in jwm as this is what I saw in a well-running Pup.

So I deleted the Fossa-9.0.3 iso and files from the frugal subfolder and re-downloaded the iso - again, the new iso has the right md5sum.

Copied the usual files to the empty frugal subfolder and re-booted to Fossa64-9.0.3.

But now watching more closely the startup process .........
Quick setup - I set language, location, keyboard (numlockon) and hostname to 'puppydesktop' as per normal ....... on reset, the taskbar was gone and the right-click menu incomplete again (even less showing on a right-click than before).

Assuming it is the Qucksetup creating my problems, I rebooted, but did not change the Quicksetup settings. and saw a normal Menu and could better place and space the drive icons (screenshot).

Rebooted, making a save-folder as normal during shutdown.

But now the application icons on the pinboard are gone, while the Menu and drive icons are still good (screenshot).
Terminal 'jwm -p' still nothing reported.

Although frdv seems loaded (/lib/firmware has lots of files), I cannot get my usb wifi dongle to work.

So having to post this from another Pup (a 64LxPupSc).

David S.

[666philb]

G'day,

Ran "jwm -p" in a terminal and quickly got a new # blank line. I assume this means no problems in jwm as this is what I saw in a well-running Pup.

So I deleted the Fossa-9.0.3 iso and files from the frugal subfolder and re-downloaded the iso - again, the new iso has the right md5sum.

Copied the usual files to the empty frugal subfolder and re-booted to Fossa64-9.0.3.

But now watching more closely the startup process .........
Quick setup - I set language, location, keyboard (numlockon) and hostname to 'puppydesktop' as per normal ....... on reset, the taskbar was gone and the right-click menu incomplete again (even less showing on a right-click than before).

Assuming it is the Qucksetup creating my problems, I rebooted, but did not change the Quicksetup settings. and saw a normal Menu and could better place and space the drive icons (screenshot).

Rebooted, making a save-folder as normal during shutdown.

But now the application icons on the pinboard are gone, while the Menu and drive icons are still good (screenshot).
Terminal 'jwm -p' still nothing reported.

Although frdv seems loaded (/lib/firmware has lots of files), I cannot get my usb wifi dongle to work.

So having to post this from another Pup (a 64LxPupSc).

David S.

hi davids45,

on a fresh boot (no save) can you try closing the welcome window and then editing /usr/sbin/quicksetup

at the end of the file line 1601 can you try increasing the sleep value. and then running /usr/sbin/quicksetup again.

Code: Select all

  exec pupcheck &
  sleep 1
  exec restartwm

also will need more info on your dongle

cheers

[ETP]

Hi davids45,

There are not many people who run with multiple partitions as we both do and I can confirm multiple display
problems if things are not done in a certain sequence. In addition certain field values seem to have upper limits.

In addition to what you have described it is all too easy to have icons piled up on top of each other.
Here are my tips for avoiding such problems:

1. Having completed first run do not attempt to change drive icon parameters until the next boot having
created a save file or folder.

2. Do NOT edit /etc/eventmanager directly always use the window below within JWM desk.

3. DO NOT make any changes to the desktop icons until you have the partitions/drives displaying
correctly and have rebooted again & saved the session.

4. In the shot below "Start gap" stick with the default 32 or change to 64 (Do NOT exceed 64)
(I normally use 64 even when not dealing with long nvme names)

5. The "Edge gap" (from the bottom of the screen) is not limited in any way other than it needs to
start above the height of the task bar. In the shot below I used 160 to place the first row above
the FOSSAPUP logo.

6. If you make any change to any one or all of the values you MUST tick refresh before clicking OK.
If the refresh does not give the desired result restart X before tweaking any value.
Do NOT get tempted to adjust a value again without both the refresh and restart of X.

7. For "Spacing" use a value of 64 to 128 (Do NOT exceed 128)

ROX Icons is a very sensitive wee beastie, easily upset.
Good luck.

[bigpup]

re-downloaded the iso - again, the new iso has the right md5sum.

Copied the usual files to the empty frugal subfolder and re-booted to Fossa64-9.0.3.

Exactly what files are you manually copying to the frugal folder(directory)?
Tell us exactly what you put in the frugal install???

[O.F.I.N.S.I.S.]

Hi.

Just to find out, if those warnings do appear caused by the "+" used inside /root/.jwm/jwmrc-personal, I changed two commands from

Code: Select all

<Key mask="C+S" keycode="35">exec:amixer sset Master 1+,1+</Key>
<Key mask="C+S" keycode="61">exec:amixer sset Master 1-,1-</Key>

to

Code: Select all

<Key mask="C-S" keycode="35">exec:amixer sset Master 1+,1+</Key>
<Key mask="C-S" keycode="61">exec:amixer sset Master 1-,1-</Key>

This is the warnings that returned by entering jwm -p into the terminal

Code: Select all

root# jwm -p
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "-"
JWM: warning: invalid modifier: "-"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
root#

After changing

Code: Select all

<Key mask="C-S" keycode="35">exec:amixer sset Master 1+,1+</Key>
<Key mask="C-S" keycode="61">exec:amixer sset Master 1-,1-</Key>

to

Code: Select all

<Key mask="CS" keycode="35">exec:amixer sset Master 1+,1+</Key>
<Key mask="CS" keycode="61">exec:amixer sset Master 1-,1-</Key>

the two warnings with "-" disappeared from that list.

Code: Select all

root# jwm -p
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
JWM: warning: invalid modifier: "+"
root#

Though, the related command, to increase/decrease Master Audio Volume is still working.

Resume: to mask e.g. Strg/Shift or Control/Shift for a keyboard shortcut, adding the "+" in between doesn't seem to be necessary at all.

Thanks for mentioning the jwm -p command, which I never used, as I didn't know the meaning of parse. Now I understand this term.

Edit:

After changing all those commands all warnings disappeared.

[bigpup]

V9.0.3 latest Quickpet updates.
Quickpet->Drivers
Lists the Nvidia 440 driver
Clicked on it and get error message it is not found.

Looked in http://distro.ibiblio.org/puppylinux/pe ... s-fossa64/
No pet for nvidia 440 driver package.

[davids45]

G'day 666philb, ETP & bigpup,

Thanks for your feedback on my Fossa difficulties.

Firstly, bigpup, I've attached my subdirectory for Fossa-9.0.3 showing the files I'd copied from the mounted iso. There's a savefile and backup of a 'good' savefile (to go back to if a test goes badly). I've done over forty Pups this way on this desktop so would be surprised (well, a little bit) if this is the basis of my problem with this new Fossa.

Secondly, ETP,
I have had some of the issues you listed in some earlier Pups but generally all previous Pups have been user-friendly in aligning the drive icons to fit my monitor (one closely packed row across the bottom). Fossa has been odd in comparison so your step-by-step approach looks a fix for a new problem?

I'm putting these problems down (at least partly) to 666philb's new approach to modularising a Puppy and having an 'old dog' like me trying to learn something new.

Thirdly, 666philb,
My usb wifi dongle is a TP-Link TL-WN821N and this one uses the ath9k firmware/drivers. Here's the PSI report (running 64BionicPup8.0-k5.6.18 now) :

VendorID=0cf3 ProductID=7015 Rev=02.02
Manufacturer=ATHEROS
Product=USB WLAN
SerialNumber=12345
Driver=ath9k_htc

I think it's been OK in earlier FossaPups but I do have occasional firmware issues with fdrvs (in other Pups that won't load an fdrv?) so I copy the ath9k firmware directory to /lib/firmware and then things are good.

I'll soon try 666philb's request to edit quicksetup in /usr/sbin/, and ETP's slower desktop setup process when I re-boot into Fossa.

Thanks again,

David S.

[bigpup]

Firstly, bigpup, I've attached my subdirectory for Fossa-9.0.3 showing the files I'd copied from the mounted iso. There's a savefile and backup of a 'good' savefile (to go back to if a test goes badly). I've done over forty Pups this way on this desktop so would be surprised (well, a little bit) if this is the basis of my problem with this new Fossa.

Well had to ask.
It is easy to do something manually and miss something.
I know I have!

[davids45]

G'day,

I am now posting from 64Fossapup-9.0.3, after a few changes.

I followed ETP's slow guide to doing the set-up and having made a 1 to 5 seconds change to /usr/sbin/quicksetup (666philb's suggestion).
I stopped picom (seemed to be a memory hog?) which sped up things back to about normal with nothing untoward happening.

FossaPup now had a desktop with all icons present (drive & applications) and the taskbar as usual.

However, I still could not get a network connection for my USB dongle, so no printing, scanning or browsing.

So I deleted the supplied fdrv and replaced it with one having just my dongle's firmware (made from ozsouth's fdrive sfs).
I also replaced zdrv and vmlinuz with a 5.6.18 kernel's (again from ozsouth).

I did these changes together so don't know if one or the other, or both, did the trick, but now I have a network connection and can print, scan and browse, albeit with a 5.6.18 kernel FossaPup-9.0.3 (screenshots).

Still at issue are a few applications not running - some portables, some 32-bitters, and wine (also 32-bit) - which are likely needing some lib file fixes. A typical situation for 64-bit Pups with their mixed libs conventions.

I hope some of all this may be of use to 666philb in developing FossaPup.

Thanks,

David S.

[bigpup]

Still at issue are a few applications not running - some portables, some 32-bitters, and wine (also 32-bit)

need to load the 32bit compatibility sfs to have support for 32bit software.
Quickpet->Useful->

This being a release candidate of Fossapup64.
Released for testing and bug fixing.
It would really help if you kept Fossapup as it is released and let us figure out what is needed to be added to Fossapup or bug fixed.

Example:
I needed a kernel module driver for my WIFI adapter.
666philb made a pet for it.
Installed the pet, adding the driver, and it now works.
Another time during testing. I needed support added for the wired network device.
Fossapup64 6.0.2 did not have it.
Fossapup64 6.0.3 does have support and my wired etho works in it.

[Gnimmelf]

please hold on to the full install option and quickpet!
I have been running bionicpup64 8.0 since it came.
the full install is by far the fastest option - if you look at ram, run hardinfo test and browser speedtest, its far faster than the frugall install and i prefer it by far.
And of course quickpet is a gem!!! only thing i need is that brave browser is in quickpet, so that could be a wish too. the portable Brave and Opera found elsewhere here on the forum, i think by mike walsh, is faster and more low ram than anything else i tried, and testes bether on browsertest -speedbatle, at least on my HP Pavilion g6 laptop.

kind regards Gnimmelf

Ps is the full install option gone? cannot seem to find it? i have bionic pup running at about 136mb ram - the frugal of fossapup uses 196 mb ram and the browsers are slower than on the bionic full install (using speedbattle - and the eyes!) ...... please keep the full install option!!!!

Kindly Gnimmelf

[666philb]

please hold on to the full install option and quickpet!
I have been running bionicpup64 8.0 since it came.
the full install is by far the fastest option - if you look at ram, run hardinfo test and browser speedtest, its far faster than the frugall install and i prefer it by far.
And of course quickpet is a gem!!! only thing i need is that brave browser is in quickpet, so that could be a wish too. the portable Brave and Opera found elsewhere here on the forum, i think by mike walsh, is faster and more low ram than anything else i tried, and testes bether on browsertest -speedbatle, at least on my HP Pavilion g6 laptop.

kind regards Gnimmelf

Ps is the full install option gone? cannot seem to find it? i have bionic pup running at about 136mb ram - the frugal of fossapup uses 196 mb ram and the browsers are slower than on the bionic full install (using speedbattle - and the eyes!) ...... please keep the full install option!!!!

Kindly Gnimmelf

hi Gnimmelf,

i had a look at woofce and the full install option is still there just hidden. I presume it has been hidden to stop new users choosing a full install which they are likely to do as default, where as puppy should really be frugal as a default.

anyway in a terminal

Code: Select all

export ENABLE_FULLINSTALL=1
puppyinstaller

[taersh]

Hi.

Just to let you know. Testing pgprs-2.0.4-beta.pet.

Currently I'm online and posting with FossaPup64 and pgprs-2.0.4-beta.pet installed. Though, I'm running FossaPup64 with Kernel 5.0.21-rt15. Using the original kernel of FossaPup64 the modem is not detected.

So testings of pgprs with original kernel is not possible.

[bigpup]

Using the original kernel of FossaPup64 the modem is not detected.

So, what exactly is the modem?

Is this when running Foassapup64 9.0.3?

[taersh]

It's a wireless USB modem and it's 9.0.3.

[bigpup]

What exact device is it?

From the working Fossapup.
menu->System->Pup-Sysinfo->Devices->Network

Please post the info given.

[linux28]

vivaldi pet Do you have? Install with install-vivaldi-0.4-noarch is too slow