Quirky 1.2rc feedback

[sinc]

pdvd rsab did not function correctly. I believe it was built to use Xine and it looks like Quirky has mplayer. It ripped okay but I couldn't shrink a file and a had a few other glitches I did not record. but just a quick (not very helpful) note that pdvdrsab did not function properly.

[rcrsn51]

More on the scanner issue later. It's a Canon i-SENSYS MF4010 and xsane and sane-find-scanner did not detect it. Even after updating to the latest sane-backend/xsane.

I can't find a Linux driver for your scanner anywhere.

http://software.canon-europe.com/softwa ... asp?model=

There's .rpm and .deb packages in the archive as well as source code. Didn't take a look at it yet since I have no compiler on my quirky.

That driver is for printers only, not scanners.

[Firewave]

That driver is for printers only, not scanners.

I found this

http://www.canon-europe.com/Support/Sof ... UPPORT.asp

Code: Select all

Please note that there is no support for scanning or PC Faxing on Linux for i-SENSYS products.

So it seems I am screwed. Although I saw some scanners of the MF series listed on sane-backends being supported by using the pixma driver.

[alec78]

Hi all,
@BarryK
Did my usual type of install with qrky-112, that is save the sfs and save files to an USB dongle, and boot from the CD.
On the second boot up every thing went O.K. quirky recognised the .3fs save file this time, except touchpad tapping is still not working. I had set one finger to left click in flSyclient prior to the first shut down.
flSynclient did open up with no complaints of missing files this time, but when I pressed the save button it highlighted but did not close the window, I had to hit the small x button to close the window, this might indicate the setting has not been saved.
This is with the Samsung X05 which as I reported previously touchpad tapping works under lupu 5.

VIDEO REPORT: Quirky, version 112

Chip description:
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)

Driver used by Xorg:
vesa

Video mode used by Xorg:
Resolution: Depth 24 Depth: "Display"

Cheers

[Firewave]

Seems like I need sane-pixma to get my scanner working. Gonna look into it.

[BarryK]

Hello, There is a thread started outside of this one about high CPU Temps.

http://www.murga-linux.com/puppy/viewtopic.php?t=55417

I just thought it would be appropriate to include a link into this thread. At 1st blush, I don't think the acpi is working with the fan correctly.

OverDrive

Yes, the info there describes pretty much what happens on my system (intel dual core T23330) Its fine in 4.3, runs around 40-45 deg, but in Q1.2 just goes up steadily till I shut down at around 70deg. Would probably go higher if I let it.

Hmmm, could you please try this:

1.
In /root/Startup, change 'acpi' to not-executable (right click on it and choose Properties).
2.
In /etc/init.d, change 'rc.acpi' to not-executable.
3.
Reboot.

[OverDrive]

Barry, I went ahead and tried that. The temp stayed at 63c idling or under good load. It never popped up a temp warning dialog box.

Without your tweak it would issue a warning in just a few minutes with temp 71c or more.

Just to let you know if you haven't caught up on the other thread, I copied the contents of start_cpu_freq over from my known good 4.31 setup and the temp went down to 48c idling and 55/63c when under good load.

It seems to me the CPU Frequency Scaling Tool needs some tweaking for Quirky as it failed in loading *any* module for my laptop whereas there was no problem in 4.31. I can't remember who maintains that one.

So in summary I don't think there is a problem with anything kernel / ACPI module wise. Just the tool needs a tweak.

Overdrive

[rjbrewer]

I tried it with a full Quirky install and clicking refresh after
"de-executableizing" the 2 files, the cpu scaling was automatically
enabled to the same settings as the 3 other puppies I have
installed.

I still get the high temp warning on video streams, but the 70c
setting is about 4c low for full fan turn on with this laptop.

Edit;
I had no problem using the net with sns; even though the little
blue globe in tray was saying I didn't have an active interface.

[DaveS]

Now that I have the temp under control, this seems the best Puppy EVER. It can finally allow me to control the brightness of my screen using the FN key on my lappy. No other Puppy has ever been able to do that . Odd little things here and there, but hey, its Quirky, right?
Now here is interesting: with the temp control working, this is actually chewing through my laptop battery about 25% SLOWER than 4.3.1! 25% more run time...Yay! AND the filechooser dialogue is wholly visible.

[aarf]

Edit;
I had no problem using the net with sns; even though the little
blue globe in tray was saying I didn't have an active interface.

my impression is that the update pets for sns are not in this quirky. i haven't been able to hold connection with my wifi in q112 sometime cant connect at all, then on switch to puppeeerc3.5 using pwireless2 it holds for hours even when not in use. consequently only minimal testing of q112.

[Firewave]

Apparently the pixma backend comes with sane-backends. Investigating.

Something else came up:

# man test
find: `/usr/share/doc/puppylogo96.png/': Not a directory
find: `/usr/share/doc/puppylogo48.png/': Not a directory
find: `/usr/share/doc/release-Quirky-1.1.htm/': Not a directory
find: `/usr/share/doc/release-Quirky-100.htm/': Not a directory
find: `/usr/share/doc/hiawatha.htm/': Not a directory
find: `/usr/share/doc/release-Quirky-1.0.htm/': Not a directory
find: `/usr/share/doc/puppylogo96.png/': Not a directory
find: `/usr/share/doc/puppylogo48.png/': Not a directory
find: `/usr/share/doc/release-Quirky-1.1.htm/': Not a directory
find: `/usr/share/doc/release-Quirky-100.htm/': Not a directory
find: `/usr/share/doc/hiawatha.htm/': Not a directory
find: `/usr/share/doc/release-Quirky-1.0.htm/': Not a directory

Happens on every man call.

[Béèm]

I applied Barry's advice, but my laptop is still running hot.
I looked at the start_cpu_freq, but it's no code in the script file.
I looked at the one of the 4.3.1, but it's the same.
What is the use of a script file without code?

I tried to see at what speed the fan is running, but apparently I only have the indication 0 rpm.
Do I have to activate some mod?
Do you guys see at what speed the fan is running?

[aarf]

I tried to see at what speed the fan is running, but apparently I only have the indication 0 rpm.
Do I have to activate some mod?
Do you guys see at what speed the fan is running?

PWIDGETS TEMPERATURE WIDGET HAS BOTH TEMPERATURE aND FAN SPEED</caps lock>

[rjbrewer]

I tried to see at what speed the fan is running, but apparently I only have the indication 0 rpm.
Do I have to activate some mod?
Do you guys see at what speed the fan is running?

PWIDGETS TEMPERATURE WIDGET HAS BOTH TEMPERATURE aND FAN SPEED</caps lock>

Mr. Widget says I don't have any fans!

[aarf]

I tried to see at what speed the fan is running, but apparently I only have the indication 0 rpm.
Do I have to activate some mod?
Do you guys see at what speed the fan is running?

PWIDGETS TEMPERATURE WIDGET HAS BOTH TEMPERATURE aND FAN SPEED</caps lock>

Mr. Widget says I don't have any fans!

speak with micko he fixes awol fans

[rjbrewer]

PWIDGETS TEMPERATURE WIDGET HAS BOTH TEMPERATURE aND FAN SPEED</caps lock>

Mr. Widget says I don't have any fans!

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

[jpeps]

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]

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?

[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.

[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?