Bionicpup64 8.0 CE

[artsown]

Fresh frugal on hard drive of 7.9.6
Test computer is a dell desktop Dimension E510. This machine does not
provide cpu temp sensors, yet pmcputemp displays a constant 32 degrees
in the bottom tray.

Psync is working well.

Memory usage is still relatively high compared to Fatdog 721, Xenialpup64
7.5 and Tahrpup64 6.0.6 My tests on this computer using only one gig
ram plus one gig swap suggested that more than 1 gig ram is required,
especially with "heavy" browsers instead of "light".

Art

[zigbert]

Test 7.9.6 on Lenovo yoga 530
AMD Ryzen 5 2500u
Pristine frugal install

Thanks for the included Realtek RTL8821CE wifi kernel module. Sorry to say, the device was not detected. Is there anything I can test/do?

I thought the newer kernel would have positive effect on the graphical experience... But it hasn't... It sometimes loads into X, sometimes not. When reaching X, the system freezes after minutes (sometimes seconds).
It uses the ati driver, and I wonder if I should try the AMD proprietary driver? The problem is that I can't connect to the web, so I have to somehow include it into my usb-pendrive that I boot from. Secondly, I have to force Puppy to use it during boot. Can I do that in xorgwizard?

Neither the touchpad nor the touchscreen works.

Thanks for any help

[Terry H]

@Terry H - your AMD cpu probably just a bit old for the k10temp module. If you edit /usr/bin/pmcpucurt.sh, replacing all (3) k10temp with k8temp, then restart window manager, will probably work. Would love you to test that, as I don't have many machines to test with.

Changed as requested. Initially it appeared OK when checked against PupSysInfo it was displaying what was the same as pmcputemp.sh had previously shown, which was temp1 it8772 reading, however over time the reading in PupsysInfo increased and fluctuates when checked, but the CPU Temp in the Tray has remained static at the initial value of 32.

[torgo]

I had done some testing of Ubuntu Mate 18.4.1, so I had it installed all by itself on a SSD drive. With no other hard drives on the system, I tried a frugal install of 7.9.5 on this same drive.
The screen shows:

wee 0> find --set-root /grldr
(0x80,0)
wee 0> /grldr
wee 13>

This is a bug in Grub4dos not being able to handle ext4 64bit format.
Ubuntu Mate 18.4.1 probably formatted the SSD drive partition ext4 64bit.
Ext4 64bit is used now by a lot of newer Linux OS's.

Here is more info and some info on ways to get around this:
http://murga-linux.com/puppy/viewtopic.php?t=111376
If you change the format of the drive partition to ext4 32bit, Grub4dos should work.
The Gparted in Puppy only makes ext4 32bit format.

Thanks, bigpup!

I guess the easiest approach is just to go with the GRUB2 used by Ubuntu and add various Frugal Pups to the 40_custom file in the grub.d folder. Probably also best to make a separate partition for Pups and other stuff, keeping them out of the Ubuntu partition.

[znekk]

Hello all,

This is just a quick report to say that everything works as expected basically on a frugal install to a usb drive.
I noticed some sound distortions with the first iso, but now this seems to be resolved for me, it might have been the kernel?
I also updated palemoon to the latest, no problems with that. Running with an I3-2140 and 8GB of ram the pup is flying!

Thank you very much for the hard work, to all the Puppy community.

[zigbert]

7.9.6
It seems the charset is limited in cli.
Can't remember this from earlier versions.

[ozsouth]

@Terry H - thankyou for testing cpu temperature. No k8temp in the output. Just running sensors in a terminal should give the same output. Need to determine which sensor is actively monitoring temp & use it. Mick's original didn't do that either. Could read it, apply a burst to CPU & read again, to pick up changes, but don't like to do that to folks CPU's. That means several different possibilities. I've worked on 2 angles - sensor & path. There are 2 main paths so a changed pmcpucurt.sh, checking those paths would do for now.
Here's a pet to test. For other folk, ONLY try this if current pmcpucurt NOT working.

[bigpup]

Memory usage is still relatively high compared to Fatdog 721, Xenialpup64
7.5 and Tahrpup64 6.0.6 My tests on this computer using only one gig
ram plus one gig swap suggested that more than 1 gig ram is required,
especially with "heavy" browsers instead of "light".

Art

What are you using to measure ram usage?
Pup-Sysinfo>Devices>Memory gives the best information.
Actual Used RAM:
Actual Free RAM:

RAM set aside for buffers and cached is not actually in use, until something needs it.

[Terry H]

@Terry H - thankyou for testing cpu temperature. No k8temp in the output. Just running sensors in a terminal should give the same output. Need to determine which sensor is actively monitoring temp & use it. Mick's original didn't do that either. Could read it, apply a burst to CPU & read again, to pick up changes, but don't like to do that to folks CPU's. That means several different possibilities. I've worked on 2 angles - sensor & path. There are 2 main paths so a changed pmcpucurt.sh, checking those paths would do for now.
Here's a pet to test. For other folk, ONLY try this if current pmcpucurt NOT working.

At present I'll have to wait to run this tomorrow.

[ozsouth]

Update 1 for pmcpucurt - not essential, but expands options & simplifies amendments. Some still may need 2path pet instead.
See: http://murga-linux.com/puppy/viewtopic. ... 96#1008196

[davids45]

G'day,

I'm not sure if this new problem for my computer has the same origin as recent temperature reporting issues but.....

..... I cannot get my required hwmon module to work in this Pup. I need it for my Temp-CPU widget.
Boot Manager reports the module to be loaded but sensors in a terminal says no modules are loaded.

I switched kernels in 64Bionic796 to an older kernel but still nothing reported for system temperatures.

This non-module-working situation was also in 64Bionic795 and now I see it in the most recent 32-bit Pup (CosmicCuttlefish).

All my other 64-bit Pups and 32-bit Pups are fine with this smsc47b397 module loaded either via the Boot Manager or editing MODULESCONFIG.

Should I suspect a problem with Boot Manager Modules section in the latest woof failing to actually load hwmon modules??

David S.

[artsown]

@bigpup
The problem of determining physical ram demand in Linux is a difficult
one. I'm not entirely clear on the HTOP method, but I still have the
sense that it seems to yield a realistic estimate. For example, HTOP
sort of predicted that I would experience crashes under certain
conditions using a mere one gig ram when testing version 7.9.5,
and I did. As soon as HTOP showed ram useage crawling up to the
one gig area, I saw crashes. The simple formula method you suggest
gives too small of a estimate.

Art

[Terry H]

@Terry H - thankyou for testing cpu temperature. No k8temp in the output. Just running sensors in a terminal should give the same output. Need to determine which sensor is actively monitoring temp & use it. Mick's original didn't do that either. Could read it, apply a burst to CPU & read again, to pick up changes, but don't like to do that to folks CPU's. That means several different possibilities. I've worked on 2 angles - sensor & path. There are 2 main paths so a changed pmcpucurt.sh, checking those paths would do for now.
Here's a pet to test. For other folk, ONLY try this if current pmcpucurt NOT working.

At present I'll have to wait to run this tomorrow.

I installed the path pet and it still appears as constant 32 (probably displaying the icon from the pmcpucurt .config file. I ran the script in terminal

Code: Select all

cat: /sys/devices/virtual/thermal/thermal_zone0/temp: No such file or directory
/usr/bin/pmcpucurt.sh: line 25: /1000 : syntax error: operand expected (error token is "/1000 ")
Script completed hit RETURN to close window.

I ran the old pmcputemp.sh script from the previous .iso to check the path. The AMD processor used the third option from the old script. This produced this output:

Code: Select all

/sys/devices/platform/it87.2608/hwmon/hwmon3/temp1_input is written to /root/.config/pmcputemp
Script completed hit RETURN to close window.

I changed the AMD path in the pccpucurt.sh to match the file shown above. The Tray icon now shows a variable CPU temp.

[ozsouth]

@Terry - thankyou for extensively testing. That explodes my path theory for AMD. At least, as per your last line, it's easy to amend the path - one of my objectives. Newer Intel and newer AMD seems OK (80+% of users???), but back to the drawing board for older AMD.
Any Intel users out there having issues with pmcpucurt?

[sheldonisaac]

.. Newer Intel and newer AMD seems OK (80+% of users???), but back to the drawing board for older AMD.
Any Intel users out there having issues with pmcpucurt?

Hello, ozsouth. I have Bionicpup64 on this PC only, a Dell laptop E6410. Whatever cpu temp measurer it came with seems to work.
I'll download pmcpucurt and boot Bionicpup64, and hope to report back.
-----------
Oh, I seem to have it already. Is this it?
-rwxr-xr-x 1 root root 23144 Oct 24 13:51 /usr/bin/pmcpucurt
Tray icon is 56, 55, 57,..
I guess that's normal?

[Revolverve]

666philb
thanks for .6
Frugal freshness,
-touch, wacom ootb now.
-bravo for xvkbd 3.9 and fonts fix,look,hmmm..bigger,thumbs up.
- fw for intel 7260wifi and probably more.good
-taskbar diplay cpu temp and all...intel here
-did i miss that on .5,but think i tried ; could not get get full screen with different screen resolution ,working now.
Check an try,
-remove buildin packages....libjack....
warning may break bla-bla...proceed,yes,
it removed libjackserver.so.0.1.0+(jack2 lib)
*it does not remove usr/lib/libjackserver.so.0.0.28+(jack1)*
wiki:There are two JACK implementations, see this comparison for the difference between the two. In short, Jack 1 and Jack 2 are equivalent implementations of the same protocol. Programs compiled against Jack 1 will work with Jack 2 without recompile (and vice versa).
..but by experience jack server refuse to start if both libs are there ,of course if all you need are libs and do not use jackd you wont have any problem.. suggest removing libjack.so.0.0.28 and libjackserver.so.0.0.28 .
Else,
Days on 7.9.5,hours on .6 no problem ,did not tried every buildin prg ...
platform;motion r12 r001

If someone know how,any link/hints appreciate .:
??
Made that simple script for correcting finger touch not reaching one screen border:
#!/bin/bash
xinput set-prop "Wacom ISDv4 4004 Finger touch" --type=float "Coordinate Transformation Matrix" 1, 0, 0, 0, 1, 0, -0.019, 0, 1

.....from root/Startup ,boot or restartx is all good,
it only just wont survive sleep/resume.

[Terry H]

Oh, I seem to have it already. Is this it?
-rwxr-xr-x 1 root root 23144 Oct 24 13:51 /usr/bin/pmcpucurt
Tray icon is 56, 55, 57,..
I guess that's normal?

Yes, it is the default in 7.9.6.

[ozsouth]

Seems the old pmcputemp program, using the 'platform' path will work on most machines - does on my Intel N3060 & AMD E450.
Have updated pet - see http://www.murga-linux.com/puppy/viewto ... 76#1008276

[artsown]

@ozsouth
Installed your version 0.63a of pmcputemp on a computer which has no
cpu temp sensors. Every bootup the old "does not work here" window
pops up and a phoney temp is displayed in the bottom tray. When
I close the window, the phoney temp display disappears.

Why not automatically close the window after three seconds or so? Or
maybe it does close eventually and I've not waited long enough to
see it auto-close?

I'm using this particular "no cpu sensors" computer daily for the time
being, and I should be available to check possible future versions.

Art

[ozsouth]

@Art - this is where a C programmer is needed - I hacked the code in an earlier attempt to fix the display, but I could easily see what to delete & drop to a shell. Other stuff not so easy. Sadly some machines just won't display temp.