Quirky 1.2 feedback

[Béèm]

re: "jerky video"

Try this:
1. Install nvidia-195.36.15-k2.6.33.2-1-q from the PPM
2. exit to prompt. Rerun xorgwizard, and "probe"

This worked for me; the radeon driver used the extra libs supplied with nvidia, and flash now works.

Thanks for the info.
But it's a 72MB install to get a few libs for the radeon driving.
It would be nice to know which libs it are and only install those as the rest of the package is not needed for a ATI/Radeon video controller.

[rcrsn51]

Printing to a ps-file via CUPS-PDF still has no upper-left margin.

Can you give an example? What application are you printing from? This appears to work for me. Instead of using the CUPS-PDF driver, have you tried using "Print to File"? Most applications have this print option.

A shell script !#bin/sh does not start on booting despite link form executable in path to /root/Startup.

Can you give an example? This also works for me. Have you declared the script file executable?

[Kal]

rcrsn51 wrote:

Here is a better short-term solution.

Locate the file /usr/local/cpu-freq/cpu_func and open it in a text editor.

Line 15 currently says
Code:
if [ ! "`cat /tmp/modprobe_module.tmp`" ] ; then

Change it to
Code:
if [ $? -eq 0 ] ; then

Oh well, that didn’t work, but, thanks for trying. Back to deleting modprobe.conf after the fact in rc.sysinit.

Thanks again, Kal

[jpeps]

re: "jerky video"

Try this:
1. Install nvidia-195.36.15-k2.6.33.2-1-q from the PPM
2. exit to prompt. Rerun xorgwizard, and "probe"

This worked for me; the radeon driver used the extra libs supplied with nvidia, and flash now works.

Thanks for the info.
But it's a 72MB install to get a few libs for the radeon driving.
It would be nice to know which libs it are and only install those as the rest of the package is not needed for a ATI/Radeon video controller.

I think you just need it for the setup, and can then uninstall it.

[01micko]

Hi

qrky-120, quick test.

2 bugs and a nuisance per sé

Installed Firefox 3.6.4beta from the repo, only Ibiblio seems to work (nuisance)

Bug1
Firefox failed to run

Code: Select all

mozilla: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: _Z20js_NextActiveContextP9JSRuntimeP9JSContext

Bug2
Seamonkey now fails to run from the menu, both FF and SM run from "mozilla" command which I guess picks up the first one alphabetically.

Cheers

[BarryK]

Here's why some users were reporting problems with the CPU Frequency Scaling Tool. Quirky 1.1 has modprobe v3.3-pre11 but Quirky 1.2 has 3.11.1. This new version always produces a warning message "Deprecated config file /etc/modprobe.conf...."

When the CPU Frequency Scaling Tool program tries to activate any power module, it interprets this warning message as a failure, even if you have made the correct selection.

But manually loading the correct module from /root/Startup/start_cpu_freq works properly in spite of the warning.

[Edit] The solution to the problem appears to be:

1. Make a folder /etc/modprobe.d
2. Move the file /etc/modprobe.conf into this new folder.

Code: Select all

mkdir /etc/modprobe.d
mv /etc/modprobe.conf /etc/modprobe.d

We will have to fix some scripts. I think that the ALSA sound Wizard writes to /etc/modprobe.conf.

[BarryK]

Hi rcrsn51:
When you reboot it’s back. Because it makes a new modprobe.conf back in /etc.

Here is a better short-term solution.

Locate the file /usr/local/cpu-freq/cpu_func and open it in a text editor.

Line 15 currently says

Code: Select all

if [ ! "`cat /tmp/modprobe_module.tmp`" ] ; then

Change it to

Code: Select all

if [ $? -eq 0 ] ; then

Make sure you leave spaces on either side of the [ ] characters.

Thanks for that. I have fixed the PET and uploaded it, see here:
http://bkhome.org/blog/?viewDetailed=01649

[BarryK]

Downloaded and installed Quirky 1.2 along with my save file from 1.2rc. The save file was updated quickly and sound, flash video, ethernet network and local LAN worked right out of the box.

I had to delete and reinstall my HP 6P laserjet to enable printing via samba, but this was no problem.

Unfortunately, the problems reported here: http://murga-linux.com/puppy/viewtopic. ... 085#422085 have not been resolved in the new version. Just to summarize:

1. Geany is still not able to open files on an smb mounted drive. Geany 0.19 has not resolved this - the problem did not appear with Puppy 4.31 and Geany 0.18.

2. Printing to a ps-file via CUPS-PDF still has no upper-left margin.

3. A shell script !#bin/sh does not start on booting despite link form executable in path to /root/Startup. (Say . . . this folder contains traytemp and start_cpu_freq as well. Do you suppose this might have something to do with the temperature problems?)

Interesting that we are getting conflicting reports about Samba. Some people are reporting it doesn't work in Quirky 1.2rc/1.2.

I don't understand your point 3.

[BarryK]

Regarding so-called temperature problems in Quirky. Two points:

1. Earlier puppies did not have a tray temp guage.
2. Are we sure that 'traytemp' is reporting true CPU temp?

So, even if the temp did spike temporarily in earlier puppies, you would not have known.

If you did have a temp guage installed in earlier puppies, and temp did not spike too high, it would be good to install that and compare its reading with 'traytemp'.

Maybe if I take out 'traytemp' the problem will "go away"

[aarf]

Exactly which part of the PPM did you find those drivers in?

Quirky repo.....desktop section.

i am surprised your ppm looks like that.
my q100 (ok) and q120 (not ok) ppm are included.
there is no way to view the bottom of ppm in q120. edge dragging does no more.
it causes problems as detailed in q112 bugs.

[broomdodger]

Regarding so-called temperature problems in Quirky. Two points:
...
Maybe if I take out 'traytemp' the problem will "go away"

This Acer TravelMate 4670 notebook palm rests are getting HOT.
I do not think removing the 'traytemp' will help.
Also hardinfo agrees with traytemp.
Where does traytemp get the temp value?

[rjbrewer]

Regarding so-called temperature problems in Quirky. Two points:

1. Earlier puppies did not have a tray temp guage.
2. Are we sure that 'traytemp' is reporting true CPU temp?

So, even if the temp did spike temporarily in earlier puppies, you would not have known.

If you did have a temp guage installed in earlier puppies, and temp did not spike too high, it would be good to install that and compare its reading with 'traytemp'.

Maybe if I take out 'traytemp' the problem will "go away"

Earlier Puppies had hardinfo>sensors, and those of us with hot
running dell laptops have been watching that closely for a long
time.

edit;

Maybe if it wasn't for that high temp warning pop up (that didn't
exist in earlier versions) the problem wouldn't have been noticed.

[efiguy]

Hi Group,
Might suggest an automotive air conditioning thermometer to check the air outlet.

Is it possible for a kernel to cycle some process('s), triggering a large percentage of gates on the chip at too high a rate or not properly set priority?

My troubleshooting would suggest using Pprocess to kill all unnecessary tasks. With any luck, you will find that the temp will drop, and the culprit might be the tray gadget, energizing co-processor logic.
It could also be the graphic chip also heating the board from some setup register tweak for ultra gaming.

Install Ms for a cross check on air exit temperature.

just some ideas,
Jay

[DaveS]

Regarding so-called temperature problems in Quirky. Two points:

1. Earlier puppies did not have a tray temp guage.
2. Are we sure that 'traytemp' is reporting true CPU temp?

So, even if the temp did spike temporarily in earlier puppies, you would not have known.

If you did have a temp guage installed in earlier puppies, and temp did not spike too high, it would be good to install that and compare its reading with 'traytemp'.

Maybe if I take out 'traytemp' the problem will "go away"

Barry, interesting to note that I have had problems with my laptop getting hot in Quirky, and I mean hot to touch, not hot as in the reported temp, though that too was way up. Also the fan WAS running, so it is not just a case of being freaked out by the warning messages. Ultimately I shut Quirky down as it was approaching a reported 80 deg and getting a bit smelly . Putting in a working script into startup from 4.3.1 corrected it.
See Next Post..........

[DaveS]

I tried Quirky 1.2, but again could not get my touchpad to function properly, so tried Qret 1.2. So far, this is BRILLIANT.
It seemed to boot with a cpu frequency scaling script loaded correctly by default. My touchpad now works perfectly again though it can only be configured via FISnclient, changes to xorg.conf have no effect. The filechooser dialogue opens in the middle of the screen instead of somewhere down near Paris and my screen dimmer keys work (Quirky variants are a first for this in Puppy). Run temperatures have yet to exceed 50 deg, though it is cool here just now. Battery life seems better. No bugs so far, but installation of Easytag now needs libid3-3.8.so.3 which was present by default in 4.3.1
So far........Brilliant. Big thanks from me

[DaveS]

If I understand it correctly, Qret has a huge number of modem drivers which I dont need. Can I delete them prior to re-mastering, and where will I find them please?

[jpeps]

Earlier Puppies had hardinfo>sensors, and those of us with hot
running dell laptops have been watching that closely for a long
time.

I keep my Dell sitting on top of a cooling stand, where it stays at about 45C. I think they last longer that way.

[chrismt]

Quirky is very nice on my system compared with other Puppies but I have to say that 1.2 isn't fast and stable like 1.1

Maybe what I am feeling it just a placebo effect or maybe I am right

I have a suggestion

There should be a utility in Quirky that will help any newbies change their DNS servers like changing them to Google DNS or OpenDns easily.

And maybe the coming 1.3 will be more speedy

Thanks a lot

[rcrsn51]

Interesting that we are getting conflicting reports about Samba. Some people are reporting it doesn't work in Quirky 1.2rc/1.2.

There has been some recent discussion about Samba vis-a-vis setting up a fileserver and how Puppy compares to other distros.

The last time I checked, the Samba client functions for connecting to a Windows shared printer are working correctly in Quirky.

Of course, Puppy has never contained the full Samba server functionality. I don't know if anyone has successfully tested the Samba fileserver PET from the PPM with Quirky.

[rcrsn51]

Are we sure that 'traytemp' is reporting true CPU temp?

On all my machines, the traytemp reading matches the one in System > Hardinfo > Sensors.

So, even if the temp did spike temporarily in earlier puppies, you would not have known.

Definitely true. I have an old machine that runs close to traytemp's default threshold of 70C. I'm sure on a hot day, I could get it to trigger a warning. With other Puppies, I never would have known.

The outstanding question is whether there is something in Quirky (like the new video drivers or ACPI) that makes it run hotter. Why is it that Quirky apparently needs ondemand CPU scaling to run cool on some machines when other Puppies did not?

[Edit] I actually found a machine that runs a little hotter under 4.3.1 than with Quirky.

FYI, there have been several reports (including me) of traytemp segfaulting and never launching. I got jemimah's source code and compiled it on an offending machine, but it didn't help.