Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 23 Oct 2017, 23:45
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
LxPupSc - Woof-CE, Slackware-Current, LXDE experiment
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 46 of 56 [839 Posts]   Goto page: Previous 1, 2, 3, ..., 44, 45, 46, 47, 48, ..., 54, 55, 56 Next
Author Message
peebee


Joined: 21 Sep 2008
Posts: 2947
Location: Worcestershire, UK

PostPosted: Sun 09 Apr 2017, 07:22    Post subject: Re: pmcputemp  

Rodney Byne wrote:
Could you please investigate & test much more
deeply this problem.

Hi RB

There is no "problem"....

The pet is made by 01micko and is not constructed to meet your expectations...

Don't use urxvt - use LXTerminal....

Restart WM is a button on the Session Control menu....

Attached is a modified .pet which should meet your expectations Wink
pmcputemp-0.50-i686_lx.pet
Description 
pet

 Download 
Filename  pmcputemp-0.50-i686_lx.pet 
Filesize  7.99 KB 
Downloaded  44 Time(s) 

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
Rodney Byne

Joined: 31 Jan 2014
Posts: 147

PostPosted: Sun 09 Apr 2017, 11:56    Post subject: Re pmcputemp  

PB,

The .pet runs, but when the green box appears, the laptop
fan speeds up and then the green box turns red.
The laptop top plate gets unnaturally hotter.

So I have decided to stand down on this issue
and have uninstalled the .pet to status quo.
The pc fan now just ticks over normally.

My original expectation was led by BK's earlier
xenial xerus 7.0.1 which temp indicator works normally.

One thing I have noticed when trying out distros, if the OS
has two alternative window managers, such that the
unselected WM & vice-versa still runs in the background,
the fan screams fast enough to threaten tearing out its bearings.

This situation is totally unacceptable as the dual-core processors
are obviously heat-overloaded.
Cheers.
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 2947
Location: Worcestershire, UK

PostPosted: Mon 10 Apr 2017, 04:21    Post subject: Re: Re pmcputemp  

Rodney Byne wrote:
...the laptop fan speeds up and then the green box turns red.

.....if the OS has two alternative window managers, such that the
unselected WM & vice-versa still runs in the background,

Hi RB

My laptop does not exhibit that behaviour.....

There is no other window manager running in LxPup - use the Task Manager - you will see no sign of jwm running.....

_________________
LxPup = Puppy + LXDE

Last edited by peebee on Mon 10 Apr 2017, 04:26; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
peebee


Joined: 21 Sep 2008
Posts: 2947
Location: Worcestershire, UK

PostPosted: Mon 10 Apr 2017, 04:25    Post subject:  

There is a new version of libbluray been added to Slackware which I would like to switch to but have no way of testing.

Can anybody check if bluray discs play in mplayer when the attached ydrv sfs (false .gz) is installed please?

Ta.
ydrv_LxPupSc_17.04.21.sfs.gz
Description  remove false .gz and rename appropriately if required
gz

 Download 
Filename  ydrv_LxPupSc_17.04.21.sfs.gz 
Filesize  172 KB 
Downloaded  33 Time(s) 

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
mistfire

Joined: 04 Nov 2008
Posts: 624
Location: PH

PostPosted: Mon 10 Apr 2017, 18:15    Post subject:  

Hi @peebee does your lxpup kernel supports "forcepae" option? If yes how to use this option on grub or syslinux?
Back to top
View user's profile Send private message 
Marv


Joined: 04 May 2005
Posts: 901
Location: SW Wisconsin

PostPosted: Mon 10 Apr 2017, 18:57    Post subject:  

mistfire wrote:
Hi @peebee does your lxpup kernel supports "forcepae" option? If yes how to use this option on grub or syslinux?


@mistfire - Both the current 4.10.x kernels and the 'alternative' 4.4.x kernels fully support forcepae, as IIRC do all kernels since 4.x.x or so. I routinely run the 'alternative' kernels and test the 'regular' ones in LxPupSc and LxPupXenial on my Pentium M laptops which require forcepae. I use Grub4Dos only and pass forcepae as a kernel parameter in the menu.lst entry there so I can't help with the exact parameter placement in a grub or syslinux install.

My reasons for using the 'alternative' kernels in the forcepae Pentium Ms are twofold. One, they lock up on suspend with any of the 4.10.x kernels and the other is that the video FPS is 3x lower with the 4.10 series than with the 4.4 series. The 4.9.x kernel in LxPupXenial is intermediate in that it suspends correctly but still has the poorer video performance.

_________________
Pups currently in kennel Very Happy X-slacko 4.4 and X-tahr 2.0 for my users; LxPupSc,LxPupXenial & XFCE_XenialPup64 for me. All good pups indeed, and all running browsers, office etc. solely from SFS.
Back to top
View user's profile Send private message 
belham2

Joined: 15 Aug 2016
Posts: 1190

PostPosted: Tue 11 Apr 2017, 12:58    Post subject:  

Hi PeeBee,

Just wanted to give you a heads up, on the latest LxPupSc release, that even with the alt-Xorg and alt-kernel, once again I lost my dual monitors, redshift abilities and few other things (as we had talked about a few months ago). To rectify the situation, since the alt kernel and Xorg provided did not work, I again went to a recent Slacko32 build I did (a woof-CE build I did a couple of weeks ago) and grabbed it's vmlinuz and kernel. I then put them into this latest LxPupSc (always frugal installed) and..... sure enough.........everything worked as it should again.

What I find strange is out of all pup iterations here on murga----which I sample (and use) a lot of---these problems (losing dual monitors, xorg, redshift, etc) only appears with two distros: LxPupSc and now mistfire's X-Slacko-Slim. I've had to let Mistfire's go, as I don't have time to keep trouble shooting it. But for yours, I'll keep at it, flopping in the whatever the latest vmlinuz & kernel is in Micko's Slacko32 latest builds, and everything should be good. As always, thanks so much for keeping LxPupSc always fresh and up-to-date! Wink
Back to top
View user's profile Send private message 
norgo


Joined: 13 Nov 2015
Posts: 150
Location: Germany

PostPosted: Tue 11 Apr 2017, 17:41    Post subject: libbluray 2.0.0  

Hello @peebee,

removed old libbluray ( 1.4.0 ) package,
converted your SFS to a PET and tested this under use of LxPup-Sc 17.03.2 and Mplayer 1.3.0

worked without problems,
thank you very much.
Back to top
View user's profile Send private message Visit poster's website 
peebee


Joined: 21 Sep 2008
Posts: 2947
Location: Worcestershire, UK

PostPosted: Wed 12 Apr 2017, 02:02    Post subject: Re: libbluray 2.0.0  

norgo wrote:
Hello @peebee,

removed old libbluray ( 1.4.0 ) package,
converted your SFS to a PET and tested this under use of LxPup-Sc 17.03.2 and Mplayer 1.3.0

worked without problems,
thank you very much.

Hi norgo

Great - thanks for testing - will go into the next build....

_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
Marv


Joined: 04 May 2005
Posts: 901
Location: SW Wisconsin

PostPosted: Wed 12 Apr 2017, 15:19    Post subject:  

@belham2 - Just for information purposes if it's not too much trouble could you swap in the 4.9.13 kernel from the most recent LxPupXenial and see if it passes or fails your 'redshift etc.' test? The last couple of versions of mistfires X-slacko Slim have been using the LxPupSc 4.10.x kernel so it's not surprising they act similarly wrt that.

Thanks,

_________________
Pups currently in kennel Very Happy X-slacko 4.4 and X-tahr 2.0 for my users; LxPupSc,LxPupXenial & XFCE_XenialPup64 for me. All good pups indeed, and all running browsers, office etc. solely from SFS.
Back to top
View user's profile Send private message 
Sailor Enceladus

Joined: 22 Feb 2016
Posts: 1258

PostPosted: Thu 13 Apr 2017, 10:24    Post subject:  

Marv wrote:
The last couple of versions of mistfires X-slacko Slim have been using the LxPupSc 4.10.x kernel so it's not surprising they act similarly wrt that.

Interesting, I didn't know that. That one I tried a few months ago came with 3.14.56 (not as a zdrv) I think.
Back to top
View user's profile Send private message 
belham2

Joined: 15 Aug 2016
Posts: 1190

PostPosted: Thu 13 Apr 2017, 13:29    Post subject:  

Marv wrote:
@belham2 - Just for information purposes if it's not too much trouble could you swap in the 4.9.13 kernel from the most recent LxPupXenial and see if it passes or fails your 'redshift etc.' test? The last couple of versions of mistfires X-slacko Slim have been using the LxPupSc 4.10.x kernel so it's not surprising they act similarly wrt that.

Thanks,



@Marv,

Downloaded the 4.9.13 kernel from ibiblio----thanks to peebee, as I wasn't sure what you were referring to since LxPupXenial latest kernel is 4.1.31 in the latest -16-Sept-2016-release of LxPupXenial.

Anyhow, putting the 4.9.13 kernel in (with its vmlinuz) into LxPupSc-17.04.1 (with no savefile, and a frugal boot) was/is a disaster. Wireless Mouse stopped working upon hitting the desktop, had to go grab a wired (which worked), tried to set up an internet connection, and no LAN connection can be seen---no active network adapters can be seen, which, lol, is a very first for any pup I've tried over the past several years using my systems. Tried even loading the module for the gigabyte board, but it wouldn't work.

So, i stopped right here since no functioning network interface ability puts a kabosh on doing anything else.

If it helps you to know, I've done XenialPup64 build with the 4.9.15 kernel (in fact, use it a lot of my chess playing), and have no problems with it whatsoever. So if I can do builds with the 4.9.15 kernel in it, have full dual screens, redshift, and no xorg problems, then what is going on in LxPup (and Mistfire's X-Slacko) that I can continually have to resort back to using whatever Micko puts in his latest Slacko32 builds.....which as I noted, is exactly what I did and then LxPup-17.04.1 (and all iterations) run fine. Heck, I even run Micko's latest Slacko32 and 64 builds, and have zero problems with the latest kernels he puts in.

Something is screwy here....but I've no time at the present to hunt this down, so i just trashed-can Mistfire's creation and for Peebee's, I just grab the last kernel & vmlinuz from a slacko32 build, and I am good to go in LxPup any-version. (The latest Slacko32 build I did, just some days ago, I chose the old battle-proven 3.14.78 huge kernel specifically because I knew it had to do double-duty in subbing in for what I am getting with LxPupSc).

I don't think Peebee (or you) should waste any time on this. I guess I must be an outlier with my 5-6 year old 3 Gigabyte AMD motherboards, 7 year old 2 Biostar AMD motherboards and 2 ASUS AMD 3-4 years motherboards. Quite honestly, even the crazy dpup builds I have done, I never have any problems like this that I do with LxPupSc. I continue with LxPupSc only for one reason: how Peebee integrates PCManFM....once I figure out how to do that in my own builds, and/or Phil (or others) start doing it to the degree that Peebee does it so well, only then will I leave LxPupSc and the headache of always having to revert back to older kernels and xorg servers.
Back to top
View user's profile Send private message 
peebee


Joined: 21 Sep 2008
Posts: 2947
Location: Worcestershire, UK

PostPosted: Fri 14 Apr 2017, 09:32    Post subject:  

belham2 wrote:
I've done XenialPup64 build with the 4.9.15 kernel (in fact, use it a lot of my chess playing), and have no problems with it whatsoever. So if I can do builds with the 4.9.15 kernel in it, have full dual screens, redshift, and no xorg problems, then what is going on in LxPup

Hi @Belham2 & @Marv

I have just tested LxPupSc-17.04.x (32-bit) with kernel huge-4.9.15-xenialpup64 (64-bit) and it works just fine.....(apart from strange tunl0 device....)

Keep the LxPupSc fdrv even though firmware is in the zdrv as it adds some firmware like b43.

Please test.
Thanks
peebee
Screenshot(1).png
 Description   
 Filesize   38.44 KB
 Viewed   172 Time(s)

Screenshot(1).png

Screenshot.png
 Description   
 Filesize   8.69 KB
 Viewed   171 Time(s)

Screenshot.png


_________________
LxPup = Puppy + LXDE
Back to top
View user's profile Send private message Visit poster's website 
belham2

Joined: 15 Aug 2016
Posts: 1190

PostPosted: Fri 14 Apr 2017, 12:05    Post subject:  

Hi Peebee,

I'll give the 64bit 4.9.15 kernel a go tonight or early tomorrow morning, Just for my own curiousity, I just did (today) a Slacko32 build using the 4.1.11 kernel. Had never tried this one. I also inserted radky's FbBox-4.0 in the build, and then let it all rip. Sure enough, the result was great and everything works immediately-----dual monitors was even recognized on the initial boot (which is nice, as I had to do nothing), same for redshift (which I had inserted too in the build). Here's a screenshot, realize it might be hard to read so here's what "PupSysInfo" shows:

▶—— Linux Kernel ——◀

Kernel Release: 4.1.11
Build Date: Mon Oct 26 21:32:35 AEST 2015
OS Support: GNU/Linux
Architecture: i686
SMP Enabled: Yes
PAE Enabled: Yes


....and the terminal showing both screens (hdmi and vga, each 1280x1024).

I can't get any of the above in either LxPupSc (or Mistfire's) Slacko....unless I do the switcheroo with kernels and the Xorg. Note, the Xorg in this 4.1.1 I believe is not that problematic 1.19, but the 1.11. Either way, I just don't understand what is going on with this relentless push to constantly upgrade kernels (and such) when it is causing a lot of problems operationally and these kernels are not ready? I did some Google searches and murga-searches, is anyone aware of the number of problems over the past 4-5 months being reported that are directly related to this kernel upgrade madness?? I am not trying to be ungrateful, please don't take this that way. I am just saying "slow down", maybe even "stop", until you have the major issues solved. There is NO way in any linux universe (puppy included) that my 5-7 year old Gigabyte, Asus and Biostar motherboards (7 in all) should ALL---all 7 of them---be having problems with the new kernel releases from puppy----and I am talking about the canyon jump of the kernels up to the 4.10.9/4.10.10, the 4.9.21 and the 4.4.60.

I now understand what DryFalls (Just Lighthouse 64) was referring to when last year he wrote this in the 2nd msg of his JL-64 release:

"Finally, I personally use the 4.1.11 kernel. It just doesn't seem wise to have so many demons running amok. If the kernel folks don't slow down on their continual "upgrades", there may never be a stable Slackware 14.2. That is, unless they at slackware revert to the earlier approach of sticking with one kernel till the bugs are worked out. "


In sum, imho, somebody needs to say something to the woof-CE gang. They have let this kernel canyon-jumping madness go amok. Additionally, I get tired of people posting (testing) saying how wonderful the new kernels are with a build they've done, yet they don't use that build much at all, don't fully put them through their paces, then incredibly a few days later they go on to do other builds and once again trumpet how great the new kernels are, yet they don't put those builds thru the ringer either. It is folly! The new kernels, in their present form, are NOT great. Please, woof-CE gang, when it comes to Slacko and Tahrs, slow down and stop making huge jumps like this with kernels & such...and then expecting us users to act like Microsoft-bludgeoned customers who are forced to work out the bugs and make switches & patches ourselves to get things to work. This is the surefire way to drive people from puppy Confused




P.S. Peebee, thanks for all your help.....I saw your message in the other thread....seriously, this isn't your war and/or battle, and it shouldn't be. You already put something great out. The fact that this huge jumping in kernels, xorgs, etc is going on has nothing to do with you.
Fri-14-APR-2017-woof-CE-Slacko32-build-with-4.1.11-kernel-everything-working.png
 Description   
 Filesize   99.5 KB
 Viewed   1954 Time(s)

Fri-14-APR-2017-woof-CE-Slacko32-build-with-4.1.11-kernel-everything-working.png

Back to top
View user's profile Send private message 
Marv


Joined: 04 May 2005
Posts: 901
Location: SW Wisconsin

PostPosted: Fri 14 Apr 2017, 19:35    Post subject:  

64 bit 4.9.15 kernel run sucessfully in LxPupSc 17.04.1 on the all intel core 2 duo laptop. No extraneous IO ports on this hardware. As it is 64 bit, the Pentium M machines will not run it.

As usual looking at kernels, Swapping is fast, I have a little cleaner script that scrubs a savefile before updating or changing kernels which speeds that aspect up and renaming isn't much. Then I look for a clean boot sequence and WM and panel load post X; reasonable time from X start to desktop display, correct video resolution and driver use, at CPU and memory use at idle, check that services and boot processes I normally run have started cleanly and have a look for stray processes... delayedrun is the chief offender lately. Then check the IO ports and drivers and connect wirelessly and wired to see that the kernel drivers and firmware are ok. glxgears is not perfect but for comparison purposes quickly shows up any glaring problems with kernel video drivers and Xorg. My browsers/office suite/ video player, etc. are all SFS so that loading is checked. redshift and zarfy also in the mix recently. If in doubt about any prog in particular, start it from terminal and check for error messages. Suspend, both from button and lid and shutdown checked. My background is hardware and drivers, not look'n'feel so that gets shorted a bit. What I value is solidity. Same boot same responses to the operator every time over a long time. Reboots optional.

All in all it's clearly a compromise between timelyness and thoroughness for a first look, then I use it as a daily.

That said, I've run the 4.9.15 above, the 4.1.11, 4.1.30 and 31, 4.4.45, 4.4.52, 4.9.13, 4.10.3-8 recently on my stable of intel machines circa 2003 through 2015. Lots more kernels over time. For a while now I have not used the 3 series kernels as forcepae support may or may not be present there and it wastes a boot to find out.

Starting with the 2003 era Pentium Ms. The 64 bit 4.9.15 will of course not run on them. Anything 4.9.13 and newer has a pretty severe FPS hit on them though all the software including redshift and zarfy is ok. The 4.10.6 or so and newer lock up solid on suspend there. 4.1.11, 4.4.45 and 4.4.52 all run perfectly in all respects on them. 4.1.11 has a slight edge on idle CPU and memory use and 4.4.52 an edge on FPS. Suspend is normal on these three. Fan and power management pretty much irrelevant on these machines as the CPU has about a 9 watt TDW. On this hardware I favor (and run) 4.4.52 on LxPupSc and 4.1.30/31 on other older pups.

Next the 2007 era core 2 duos. Absolutely everything above runs perfectly on them. Redshift, zarfy, slimjet, chromium, printing, scanning, office suites, some CAD, basically everything I do. From a standpoint of video FPS the 64 bit 4.9.15 and the 32 bit 4.10.8 are equal and great. CPU and memory use are a bit lower with 4.10.8. Fan and power management seem about equal between the two. No real reason to drop back to older kernels here though the 4.4.52 is a close second, suffering only a bit in video FPS.

The 2015 era BayTrail desktops just burp and say the newer the better wrt kernels - at least so far -. They need at least a 4.x.x for USB support so I bump the older pups to 4.1.30/31 but LxPupSc (all the 4.10.x series) just works. I haven't run the 64 bit kernel on them yet as one is the main workhorse where it lives and the other is my NAS box...

@belham2, I heartily second the motion of sticking to a kernel for longer so fighting the kernel doesn't swamp other things that need ironing out. Problem as I see it is where to stick as it is so very hardware dependent. I've learned what I need for the various vintages but for a random box, random hardware, random age and new user what is best Question

Edited once for grammar.

_________________
Pups currently in kennel Very Happy X-slacko 4.4 and X-tahr 2.0 for my users; LxPupSc,LxPupXenial & XFCE_XenialPup64 for me. All good pups indeed, and all running browsers, office etc. solely from SFS.

Last edited by Marv on Sat 15 Apr 2017, 22:28; edited 1 time in total
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 46 of 56 [839 Posts]   Goto page: Previous 1, 2, 3, ..., 44, 45, 46, 47, 48, ..., 54, 55, 56 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0873s ][ Queries: 14 (0.0195s) ][ GZIP on ]