Quirky 1.2rc feedback

Please post any bugs you have found
Message
Author
User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

Re: Laptop running hot.

#211 Post by rjbrewer »

aarf wrote:
rjbrewer wrote:
aarf wrote: PWIDGETS TEMPERATURE WIDGET HAS BOTH TEMPERATURE aND FAN SPEED</caps lock>
Mr. Widget says I don't have any fans! :lol:
speak with micko he fixes awol fans
Never mind;
Found something that controls fan speed much better.

http://www.youtube.com/watch?v=SjxfAjAy ... re=related

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

jpeps
Posts: 3179
Joined: Sat 31 May 2008, 19:00

Re: Laptop running hot.

#212 Post by jpeps »

aarf wrote: speak with micko he fixes awol fans
The temp widget tries to read /proc/eee or /proc/acpi/fan. If there's nothing in either (like for my laptop), eliminating line 51 in .pwidgets/widget/Temp_cpu gets rid of the annoying message.

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

Re: Laptop running hot.

#213 Post by nooby »

jpeps wrote:
aarf wrote: speak with micko he fixes awol fans
The temp widget tries to read /proc/eee or /proc/acpi/fan. If there's nothing in either (like for my laptop), eliminating line 51 in .pwidgets/widget/Temp_cpu gets rid of the annoying message.
If the annoying message refers to a real rise of temperature then it is a very important message. if it is a bug or failure to measure correctly then that is important to sort out which is which.

So how can one find out if the temp is high or not without taking the thing apart and putting a mechanical sensor there?
I use Google Search on Puppy Forum
not an ideal solution though

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#214 Post by BarryK »

I posted here about possible problem with jerky Flash playing when using the on-demand frequency governor:

http://bkhome.org/blog/?viewDetailed=01637

Bèèm,
You asked about /root/Startup/start_cpu_freq -- the above link has a script that has been reported to fix the heat problem.
[url]https://bkhome.org/news/[/url]

nooby
Posts: 10369
Joined: Sun 29 Jun 2008, 19:05
Location: SwedenEurope

#215 Post by nooby »

BarryK, can I take your words to mean that it is not an annoying message then.

It is a true message that the real physical temperature is really that high?
Can one trust that measurement or is it still 40 but reporting over the recommended limit?
I use Google Search on Puppy Forum
not an ideal solution though

jpeps
Posts: 3179
Joined: Sat 31 May 2008, 19:00

Re: Laptop running hot.

#216 Post by jpeps »

nooby wrote:
jpeps wrote:
aarf wrote: speak with micko he fixes awol fans
The temp widget tries to read /proc/eee or /proc/acpi/fan. If there's nothing in either (like for my laptop), eliminating line 51 in .pwidgets/widget/Temp_cpu gets rid of the annoying message.
If the annoying message refers to a real rise of temperature then it is a very important message. if it is a bug or failure to measure correctly then that is important to sort out which is which.
The temperature reading still displays. There's a fan module (/sys/module/fan) loaded...the widget just doesn't read it.

User avatar
Béèm
Posts: 11763
Joined: Wed 22 Nov 2006, 00:47
Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win

Re: Laptop running hot.

#217 Post by Béèm »

rjbrewer wrote:
aarf wrote:
rjbrewer wrote: Mr. Widget says I don't have any fans! :lol:
speak with micko he fixes awol fans
Never mind;
Found something that controls fan speed much better.

http://www.youtube.com/watch?v=SjxfAjAy ... re=related
And for a good price. :wink:
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]

jpeps
Posts: 3179
Joined: Sat 31 May 2008, 19:00

#218 Post by jpeps »

BarryK wrote:I posted here about possible problem with jerky Flash playing when using the on-demand frequency governor:

http://bkhome.org/blog/?viewDetailed=01637
I'm running an Intel(R) Pentium(R) M processor 1600MHz with a 1024 kb cache on my Dell Latitude D600. The cpufreq_ondemand module is not loaded by default, and loading it doesn't alter the flash problem.

User avatar
lstandish
Posts: 126
Joined: Fri 06 Jun 2008, 13:22

snap2 update fixes non-working menu entry

#219 Post by lstandish »

I just realized that snap2's "snapshot backup now!" menu entry is not working in v 4.13 (and below). This escaped my attention because I develop the program (and run it daily) in Debian. I'm sorry for the confusion and inconvenience this may have caused.

This is fixed in version 4.14 (pet download: http://files.lstandish.com/

The "snapshot backup now!" menu entry is included to allow one-click backup (no GUI). I could remove it from the Puppy snap2 distribution if users prefer.
--
Lloyd
snap2 rotating snapshot backups for Puppy/Debian Lenny/Ubuntu
The convenience of full backups with the speed and disk economy of incremental backups
[url]http://standish.home3.org/snap2[/url]

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#220 Post by rjbrewer »

jpeps wrote:
BarryK wrote:I posted here about possible problem with jerky Flash playing when using the on-demand frequency governor:

http://bkhome.org/blog/?viewDetailed=01637
I'm running an Intel(R) Pentium(R) M processor 1600MHz with a 1024 kb cache on my Dell Latitude D600. The cpufreq_ondemand module is not loaded by default, and loading it doesn't alter the flash problem.
Strange: your D600 has identical parts and specs as my 700m, and I
don't have any "jerky" streaming problems; with or without cpu
scaling.

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

jpeps
Posts: 3179
Joined: Sat 31 May 2008, 19:00

#221 Post by jpeps »

rjbrewer wrote:
Strange: your D600 has identical parts and specs as my 700m, and I
don't have any "jerky" streaming problems; with or without cpu
scaling.
It works with VESA and only get's jerky with X24. (1024X768). X16 is "recommended" after probe, although the screen shows up with a dimly lit green hue.

I noticed 4.4. uses x.org ver 1.3.0, where quirky is using ver 1.7.1. I use X24 with all other distros incl 4.4.

gcmartin

Quirky 1.2rc feedback

#222 Post by gcmartin »

Ran into a problem trying to boot Quirky 1.2.rc on a IBM rack mount with 2 P-III CPUs
1.5GB memory
2 18GB SCSI 15000K
Quirky Retro version 1.2rc

Error is on boot-u failure

Code: Select all

[b]Allow boot without keyboarding. Taking the defaults[/b]
Loading  vmlinux....................
Loading initrd.gz..............
Loading drivers needed to access disk drives..	done
Searching for Puppy files in computer disk drives...	done
Loading the ‘gret-112.sfs’ main file ... copying to ram	done
setting up the flayered filesystem...	done
Performing a ‘switch_root’ to the layered filesystem...Kernel panic - not syncing: Attempted to kill init!
Hope this helps resolve
[/code]

User avatar
jemimah
Posts: 4307
Joined: Wed 26 Aug 2009, 19:56
Location: Tampa, FL
Contact:

#223 Post by jemimah »

Here is a patched xorgwizard for Quirky with support for the Elantech touchpads found on EeePCs and other netbooks.

This will enable scrolling and other features you can activate with Flsynclient.
Attachments
xorgwizard.gz
(21.15 KiB) Downloaded 593 times

aarf

#224 Post by aarf »

q112 still cant see more than one and 1/8 installed pets in package manager, so if you want to remove the 5th installed package you must first delete the 2nd, 3rd, and 4th installed packages.

jpeps
Posts: 3179
Joined: Sat 31 May 2008, 19:00

#225 Post by jpeps »

I took a shot at compiling xorg intel video drivers, but there's a missing header, gl.h.

Code: Select all

/usr/X11R7/include/GL/glxint.h:36:19: error: GL/gl.h: No such file or directory
In file included from i810.h:60,
                 from i810_accel.c:41:
/usr/X11R7/include/GL/glxint.h:103: error: expected specifier-qualifier-list before 'GLboolean' 

User avatar
Abnormalter
Posts: 95
Joined: Sun 31 Jan 2010, 10:56
Location: Russia

Common mind about problems of it

#226 Post by Abnormalter »

Oh! It's duplicated post! :(
Last edited by Abnormalter on Thu 03 Jun 2010, 18:07, edited 1 time in total.

User avatar
Abnormalter
Posts: 95
Joined: Sun 31 Jan 2010, 10:56
Location: Russia

Common mind about problems of it

#227 Post by Abnormalter »

Hello, dear Barry! Hello, people!
Thanks for your Puppy releases developing.

Alas, my new test for this release robbed me of hope and confidence to fate of the Puppy now...
And excuse me generously for this unpleasant truth.

I have an informed opinion based on my experience of two decades in the IT practice and my long life; in general, that this sad event occurs as phenomenon that has long been familiar to an older generation of people who dedicate their lives to engineering practice. Many things has been fixed... but, in alas, the current generation of IT "successfully" forgotten them, including those expressed in the famous Parkinson's and Murphy's Law/Rules...
But I have no intention here to argue for a long time on this topic, especially with the even generally and as philosophical reasons. However, I allow myself to simply highlight here my two or three points...
It's main components, which must be led to provides it as "unexpected" result of the development project, which is not too happy and do not inspire hope...

One reason is difficult to unjustified balanced judgments of the use to the Puppy' release this newest OS kernel, which has fully not sufficient testing practices, and who is passed not on the kernel developers from any bugs. Includes errors with drivers communicative problems. Any problems, which is more than eloquent was be confirmed of the monthly beta testing for Lupu 5.0x.
It's life truth after applied the kernel developers is identification of the release as 2.6.33.2 (Note to the last digit!)
Note. An oldest programming practice and impartial monitoring of the set of specialists on the Programmer's World, clearly shown fact: every software product and operating system and components like kernel, which in its minor digit not gone far from zero, they release of the software it's are potentially relevant not stable. This is fact of life.
These mind would seem that this is a fairly well-known fact, but the stupid fact and unthinking adherence the "Zeitgeist", and reckless aspirations of young people in the project to all "newest" develop -- on the external form only, not on facts, not on the merits... and this is precisely unjustified passes of wisdom aspirations must be lead to the similar occurring now. And it's main cause of.
But programmers forgotten now many of this basic things...
Meanwhile, the developers of the project Ubuntu Lucid 10.04 LTS can be develop it very much wiser and weighted. They used quite a stable kernel, since passed true debugging process, with the number of this kernel is 2.6.32.20/22. And this fact eloquently shows the reasons for the success of this release. And the Ubuntu uses people not noticed any bugs and incompatibilities with the equipment of most PCs under current and stable the Ubuntu release.
Alas, this can not boast a team of Lucid Puppy 5... :(

The second important cause of numerous OS' errors and hardware bugs in this project is desire of the developers to apply for this newest release too many innovations at one time. This is bad developers mind and very bad practice!
Many developers, who have great experience, those people, who is know and understand this reasons, known the fact: disproportionate amount of changes made in the current project immediately and without progressive experimental testing process, they developers lead to an avalanche of bugs and provides to many programming mistakes! And it's poor way to condemn the developers for painful and unproductive process of debugging it.
Both users and beta testers too, they get frustrate for it; they have reasonable causes to confusion in the process of probing this newest releases.
This is true, because it's so many bugs and abnormal behavior of user PCs has this Puppy' release...

And it's I says as last reason. It is prefer if the Puppy' projects would be divided (on a fork, but as common subprojects) to successfully processed studies of many directions to development of the newest Puppy. (It would seem that it was done...)
The first program line and first way is development of direction to maximum usability the OS for most attractive destination users, for so-called "end users"; they prefer it for any OSs. And as second way is improvement to provide and evolution the maintainer's technology, including technology to provide for simply building any software packages.
The second way and task is direction by Barry and that is very successfully develops himself by Barry.
But the first direction way on the community Puppy is now essentially natural chaos... What is not good, IMHO...

I wish many for the people participating in the project, and Barry personally, and many every success! And especially -- lot of courage and patience to overcome the failures of this way.

P.S. Excuse me for my poor English.

User avatar
Sit Heel Speak
Posts: 2595
Joined: Fri 31 Mar 2006, 03:22
Location: downwind

Suggestion: better labelling of the grub menu entries

#228 Post by Sit Heel Speak »

It might be a frustration-saver (good) idea to explicitly label each of the two grub-install menu entries with which filesystems it pertains to, like this:

Grub Legacy bootloader config (not for FAT32, NTFS)
Grub4DOS bootloader config (*eh, OK on FAT32, does it work on all filesystems?*)

Also I am curious if anyone can enlighten me, when did Grub4DOS (when installed to the MBR, the menu's default) start placing menu.lst and grldr in the top directory of the chosen install partition? Didn't these used to go in /boot/grub?

User avatar
Sit Heel Speak
Posts: 2595
Joined: Fri 31 Mar 2006, 03:22
Location: downwind

Remaster script needs updating to say "112" not "110"

#229 Post by Sit Heel Speak »

(***EDITED the following sentence is not true***)

Simple CD Remaster prompts do not reflect the change from version 110 to 112.

(*bad words*)!!!,

when I install Grub4DOS from the live CD of Quirky 112, I *expect* menu.lst to contain Quirky 112 as the top (default) entry, not the Quirky 110 I earlier placed on the drive...
Last edited by Sit Heel Speak on Thu 03 Jun 2010, 19:30, edited 2 times in total.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#230 Post by rcrsn51 »

For netbook users who are having wifi problems with the Broadcom BCM4312 driver, I have posted a howto here based on ndiswrapper.

Post Reply