Puppy 4.1beta (2.6.25.16 kernel)

[Béèm]

I was making a reply here where a picture had to be uploaded.
As soon as I did hit the browse button, SeaMonkey quited abruptly.
Don't know if it matters, but I always migrate from version to version.

Other people having this issue?
Is there a cure?

[Béèm]

When migrating from 406 to 408 (frugal lin'n'win type of install) I saw the pup_408.sfs was copied to HDD and a little while later after the version change phase I got a kernel panic message.
(P.S. I don't use a devx_xxx.sfs)

I power off-on and redid the operation and all went well now.

The thing that annoyed me is the for the last couple of version the pup_xxx.sfs is copied to HDD again.
Why is this?
Why is there this change now?
Can it be avoided to do this copying?

[Béèm]

For a couple of versions now I discovered that attaching 3 sfs files with boot manager only results in having 2 active at next boot.
Very annoying, as regularly I use 3.
In initrd I see that ro4 and ro5 contain two of the sfs files and ro2 seems to contain the pup_xxx.sfs

Why this ro2 issue and what is the need?

Is there a solution for this issue?

[Béèm]

Retry to upload an image with SeaMonkey with puppy 302, the 408 not functioning.

I think I started to have this with puppy403. (see picture for the 408)
It's kinda annoying and I think it shouldn't occur.
When running with pfix=ram the icons seem ok. No extra hda etc...
So I suspect something weird in the pup_save file, which migrates from version to version.

Any idea where to look?

[Stingray]

set timezone from GUI impossible

in the actual 4.1 beta the tzselect in /usr/bin is missing, so no timezone setting is available, only set on the shell via "date foo CEST" for example.

[DesertPuppy]

@stingray

in puppy 4.1 the script /usr/sbin/timezone-set is used to set the timezone. that is what the menu item is pointing to. It has worked for me.

[paulh177]

a picture had to be uploaded ... SeaMonkey quit abruptly ... Other people having this issue?

similar in that I was trying to upload to photobucket.com and had the same thing happen (ironically it was a screenshot of a Puppy bug).
I can reproduce this consistently

[liberomureddu]

Hi,
I'm almost new to this forum, after a short visit during the summer, trying to get puppy 4.0 installed on my quad core.
After many days of trial and errors, I found out that this beta installs on my computer (puppy 4.0 didn't).
I'm so happy about this linux distribution, and I installed on a usb pen drive and testing (and considering to change my ubuntu to Puppy). Quite amazing, I found out that almost all the software I need (included VOIP) is included by default. Amazing!

However, I have a little problem: with Xorg, I cannot get a screen resolution bigger than 800x600, using Xvesa I can.
Xvesa could be fine, but then, if I use skype video with xvesa, skype crashes.

Any hint to get a bigger screen resolution?
My system is:

Intel DQ35JOE with embedded Audio and Video.
http://www.intel.com/Products/Desktop/M ... erview.htm
Intel Core2 Quad Processor Q6600 2.40GHz
2GB Ram
Puppy beta installed on USB pen drive.
The monitor (temporarily), is an old Fujitsu 15''

Best regards and thanks for any help.

Libero Mureddu

[Sage]

The monitor (temporarily), is an old Fujitsu 15''

Please edit your profile to let us know where you live. That double 'd' suggests Cornwall or Wales? If the latter, I can drop off a 17" monitor for you in a few weeks, gratis.
Otherwise, you could try increasing your video ram allocation (not recommended) or, better, switching it off in BIOS and adding a PCI-E video card. That should solve all your problems.
Of course, like so many, you've have got the wrong combination of HW for Puppy. Sell your Intelx2 cr*p on Ebay, beg-borrow-or-buy a decent monitor with the proceeds and pick out an old SktA box from a roadside skip to run The Pup.

[liberomureddu]

I updated my profile information, I live in Italy and spend some months in Finland during the year. But thanks for the offer anyway!

Otherwise, you could try increasing your video ram allocation (not recommended) or, better, switching it off in BIOS and adding a PCI-E video card. That should solve all your problems.

How to add ram allocation, from BIOS?
Unfortunately that's my main audio workstation, and it has been designed in order to be silent as possible and with minimal video features, so I wouldn't add a separate video card.

Of course, like so many, you've have got the wrong combination of HW for Puppy. Sell your Intelx2 cr*p on Ebay, beg-borrow-or-buy a decent monitor with the proceeds and pick out an old SktA box from a roadside skip to run The Pup.

Later I'll try with a different monitor, and see if it works better. BTW, what's a SktA box? Didn't get the jargon
Thanks for your help.
libero

[Sage]

Ah yes, the Finnish language - lots of double vowels, too. What a shame (about the monitor!).

A Socket A (SktA) Duron or Athlon single core is going to give you a lot less trouble than those multi-cores, which seem to be a kludge for the worthless bloat of M$Vista and useless Intel technology which never got anything right. Subjectively, you'll not detect much difference in use for Puppy between a Duron1200 and a quad core i2.4 ! No harm in running two machines especially if one is a resurrected junkheap that cost nowt.

If you're not familiar with BIOS tweaking, best read Wim's BIOS website followed by Adrian's Rojak Pot. Everything you ever needed to know!

However, those proprietary combo boards often have Phoenix (Award) BIOSes which are dreadful. If that's the case, you can dig around on the Net to find out who really made the board and what is it's real designation/number then use the Award flasher /F switch to force it to flash to it's proper state. Alternatively, you can twiddle the BIOS with a suitable utility. Most of them run in a DOS window under a DOS-based Windows OS like W9x, so you may need to swap your HD temporarily. These utilities can be dangerous if you haven't thoroughly read and digested all the nuances.

[Stingray]

@desertpuppy

probably my fault... i only restarted the jwm and the xwindows system from the start menue. this leaves the settings untouched. if i had restartet to shell and then restartet X, it would had worked.

but in my opinion better think about an probable issue before fix it after release

[HairyWill]

Any hint to get a bigger screen resolution?
My system is:

Intel DQ35JOE with embedded Audio and Video.
http://www.intel.com/Products/Desktop/M ... erview.htm

This board uses the intel gma3100 video card.
The contents of /tmp/xerrs.log may reveal the problem.

[tempestuous]

My system is: Intel DQ35JOE with embedded Audio and Video.

This board uses the intel gma3100 video card.

For the GMA3100 you need an updated version of the 915resolution utility -
http://puppylinux.com/blog/?viewDetailed=00314

[liberomureddu]

@ Sage
Thanks again for your answer. I'm Italian (from Sardinia, that explains the "u" in the last name, double "d" is quite common), not Finnish
In my BIOS there's the possibility to give more memory to the video card, I tried setting it to 256Mb and then Max with no result.
BTW, isn't 4.1 Beta supposed to have a multi core kernel? Well, anyway it runs soo fast...!

[liberomureddu]

The contents of /tmp/xerrs.log may reveal the problem.

Hi, here it is:

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: UNKNOWN
Current Operating System: Linux puppypc 2.6.25.16 #1 Tue Aug 26 10:45:53 GMT-8 2008 i686
Build Date: 28 November 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 24 17:29:49 2008
(==) Using config file: "/etc/X11/xorg.conf"

(EE) Failed to load module "glx" (module does not exist, 0)
(EE) Failed to load module "dri" (module does not exist, 0)
(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(II) Module already built-in
(II) Module already built-in
(II) Module already built-in
(EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
usage: absvolume -bg is no longer supported, ignoring.
Try restarting X to pickup new gtk background colour.
/usr/X11R7/bin/jwm
JWM: warning: no icon or label for TrayButton
JWM: warning: color depth is 16, disabling icon alpha channel
asapm: open_apm_device_file: The file does not exist.
asapm: Neither ACPI nor APM are available!
kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l [sigspec]
Setting up watches.
Watches established.
/usr/sbin/delayedrun: line 87: 5489 Terminated yaf-splash -font "8x16" -outline 0 -margin 4 -bg yellow -text "WARNING! Do not unplug USB Flash drive!"
Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8
Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8
/tmp/pup_event_sizefreem
Setting up watches.
Watches established.
Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8
/usr/lib/seamonkey-1.1.11/run-mozilla.sh: line 131: 6033 Segmentation fault "$prog" ${1+"$@"}

[liberomureddu]

For the GMA3100 you need an updated version of the 915resolution utility -
http://puppylinux.com/blog/?viewDetailed=00314

Hi, I followed the link, but it says that this patched version will be included in Puppy 4.1 Beta that I'm already using. Should I install this file or not?

Following the link in this page I ended up in this thread http://murga-linux.com/puppy/viewtopic.php?t=32462 and ran 915resolution -l.
Here's the output:

Intel chipset detected. However, 915resolution was unable to determine the chipset type.
Chipset Id: 29b08086
Please report this problem to stomljen etc...

[liberomureddu]

@ rerwin
here is my ddcprobe.txt

vbe: VESA 3.0 detected.
oem: Intel(r)Q33/Q35/G33 Graphics Chip Accelerated VGA BIOS
vendor: Intel Corporation
product: Intel(r)Q33/Q35/G33 Graphics Controller Hardware Version 0.0
memory: 8128kb
mode: 1280x1024x256
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 1024x768x256
mode: 1024x768x64k
mode: 1024x768x16m
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 640x480x256
mode: 800x600x256
mode: 640x480x64k
edid: ÿÿÿÿÿÿ
edid: 1 74
id: 4961
eisa: SME4961
serial: 002640f8
manufacture: 27 2000
input: sync on green, analog signal.
screensize: 26 52
gamma: 2.250000
dpms: RGB, active off, suspend, standby
timing: 640x480@60 Hz (VGA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@75 Hz (VESA)
ctiming: 720x450@84
ctiming: 752x470@70
ctiming: 640x480@78
ctiming: 640x480@75
ctiming: 1216x912@85
ctiming: 800x600@107
ctiming: 800x600@87
ctiming: 1024x768@60
dtiming: 800x600@106
dtiming: 0x1115@0
dtiming: 2048x306@83
dtiming: 1024x835@325

[Sage]

Didn't know that Italian uses 'dd' - I only speak Italian Menu! Don't we all?

Anyway, looks as if HW and tempie are going to sort out your problems. They know all about the SW, besides which, I try to avoid Intel products.

Best of luck.

[HairyWill]

For the GMA3100 you need an updated version of the 915resolution utility -
http://puppylinux.com/blog/?viewDetailed=00314

Hi, I followed the link, but it says that this patched version will be included in Puppy 4.1 Beta that I'm already using. Should I install this file or not?

I'm guessing tempestuous is asleep so I will answer.
My initial understanding of Barry's blog post was the same as yours. However, reading it more carefully it looks like tempestuous applied additional patches to the ones Barry used. I would install tempestuous's update to try and get 915resolution to recognise your chipset.