Precise Puppy 5.4 and 5.4.2

[gerry]

This is not really a bug, just something different from previous puppies. My printer is a Canon i965 connected to an XP computer, which always gives me some fun and games to get working. I've got a Canon driver for it, which has been installed on Puppies ever since cups came as a dotpup. And it has always worked. This time.... a filter named pstocanonbj crashes with error 22, "incorrect argument".

I really can't see any prospect of finding what that is- so I'm afraid Precise Puppy is not for me. Pity really- apart from that it is superb. Running frugal on Thinkpad T60p, it automatically gets the right wifi setup and ATI Radeon video driver. Boohoo!

(Also, I found that Gutenprint has, at last, a driver for my printer. B/W ok, colour screwed up.)

[rcrsn51]

I've got a Canon driver for it, which has been installed on Puppies ever since cups came as a dotpup. And it has always worked. This time.... a filter named pstocanonbj crashes with error 22, "incorrect argument".

I'm not surprised. The Linux printing system has changed considerably since that driver was created.

Is the file "pstocanonbj" a script or a binary? ie. can you open it in a text editor?

BTW, I found a link where someone got this printer working as a Gutenprint ip8500.

[Edit] Precise has Gutenprint 5.2.8pre1, which only lists an i960. However Slacko 5.4 [beta2] has Gutenprint 5.2.9, which also lists an i965.

Try your printer in the new Slacko. If it works there, you could look at upgrading Gutenprint in Precise.

[gerry]

@rcrsn51- yes, I have used BJC8500, but black comes out dark grey rather than black.

EDIT: pstocanonbj is a binary.

EDIT: saves ink, I 'spose.

[puppyluvr]

Hello,

ERROR **: gtkdialog: Error in line 5, near token '</label>': syntax error

I`ve gotten this with the precise woofs I`ve been building, regarding networking, and think it is gtkdialog related, rather than an error in the executing script... The same scripts run fine in other pups.. Tried relinking gtkdialog to 3/2/etc to no avail..

[BarryK]

Before we get to an all out relegion, freedom of speech/choice etc debate ...
Did anyone tried to boot from an SDcard and then save to the entire SDcard partition?
I can see the files there after reboot but puppy keeps booting to pupmode 5, as for the first time.
It would appear that the issue is with the rc.shutdown but before I start digging would be good to know if is not something specific to my card/hardware.
Besides is getting late tonight

Did you format the SDcard in a Linux format?
I think that is required when saving to entire partition.

Yes of course!
I did try another card and is the same thing. So is not the card
Actually one card had Luci saved to the entire partition before and still failed with precise (and yes I also removed the whiteouts). Putted back Luci and works fine.
Saving to a file in Precise-5.4 on the same SDcards, works fine.
So looks like a bug.

Luci was the last puppy I installed saving to an entire SDcard partition and since then many things changed in puppy's init/rc.sysinit/rc.shutdown that could cause this
So again,
Did anybody booted Precise (or any recent woof-based puppy) from an (ext2/3/4 formatted) SDcard and saved to the entire SDcard partition succesfully?
Thx


Latter: This IS a bug! I replaced the precise initrd/init with the one from Lucid 5.1 (last entry: "#100520 pkeys boot param wasn't working for 'uk', 'dvorak'."). Sure enough the saved partitione was recognized the layered file system set and everything was OK.!!!
Putting back the original precise initrd/init in the already set and working (with the luci init) system, fails again and boots to pupmode 5.
From the little that I checked with the failing init the SDcard partitions are detected and logged OK in initrd, so it probably has to do with the logic of determining that the entire mmcblk[0-9]p[0-9], sd[a-z][1-9] is used.
Unfortunately there is a 1700 lines of code difference between the two init files and a massive "find files" rewrite. So I guess is up to Barry.

Latter Later: Turns out that precise also fails to find the files when saving to an entire USB stick partition, not just an SDcard.!

Com'n guys and gals ... Did anybody booted Precise (or any recent woof-based puppy) from an (ext2/3/4 formatted) SDcard or USB stick and "saved to the entire partition" succesfully? ie on reboot the and saved data was recognized and used by puppy.

Fixed, see:
http://bkhome.org/blog2/?viewDetailed=00006

[gcmartin]

Hope @BarryK sees this

I have posted this before, but, the FirstRUN that is used has a logic BUG.

And htere is no explanationanywhere explaning why it behaves as it does.

If a PC has a LAN card (this includes WiFi) the Network section of FirstRUN should be present for new system setup. This is a very important function of initial system setup.

Current, if the PC does NOT have an IP address on its very first LAN adapter, the Network Section does not appear.

We should be able to see the Network section as an initial use of FirstRUN, no matter what.

Currently ONLY Shinobar's FirstRUN "Personalize Settings" version addresses this as it should. But, Shinobar's version is NOT available in WOOF as of yet...or is it? This makes for extra steps by those developers who recognize this problem and address it with Shinobar's version. Could his version be made an option in Woof or could the logic bug be fixed?

Precise is a fine and speedy distro overall.

Here to help

[01micko]

Barry,

Just a note on Pnethood failing to work.

It fails in the latest Slacko too. It doesn't find windows7 shares. I have tackled it with kirk's roxapp from fatdog64.

I started a thread here.

Note down the page there is the source hacked by kirk to speed up mpscan, it works well. The binary included is compiled in Slacko, but I have noticed bins seem a lot more sensitive these days so YMMV in Precise.

@shinobar, you may want to consider changing Pnethood as nbtscan is failing in these newer pups.

Slacko will ship with the roxapp and YASSM by rcrsn51.

[colorpurple21859]

In reference to earlier post about distorted display, was able to get the display working by unsquashing the puppy_precise_5.4.sfs file and changing /etc/modprobe.d/radeon.conf to modeset=0 and resquashing file

[puppyluvr]

Hello,
gcmartin,
Could this be related to this?
http://www.murga-linux.com/puppy/viewto ... 777#661777

[BarryK]

Problems with loading savefile light-encrypted ext2: no backdrop-image, the same error of slacko 5.3.1. I tried the same console command:

gdk-pixbuf-query-loaders --update-cache

but I lost all the installations. Is it recoverable?

Solved with new save file ext2 light-encrypted with no backdrop-image problem. I think that in the first installation something went wrong with the installation of the package z_mesa-8.0.3-up.pet. I renounced to install that package and all went well.

Precise 5.4 already has mesa installed.

[rerwin]

Barry and testers,
I have been working to integrate Frisbee as a normal alternative network manager. The attached packages make minor changes to architecture scripts to accommodate Frisbee and its companion, an enhanced version of dhcpcd that should handle weak signals better. I assume it is the reason Frisbee seems more tolerant of intermittent connections. The mods utilize the feature if that version is installed, but do not require it to be.

The changes may not work with the Frisbee versions now deployed, but require my modified version, which I named "3.0", to avoid conflict with 01micko's set of betas. The 3.0 version needs testing by wireless users, because I have no wireless setup.

I plan to attach Frisbee 3.0 in another message, as well as details of the dhcpcd modification.

The changes are summarized as follows:

• - A network-tray selector script is added to /root/Startup. to replace the network_tray executable there, and to use the Frisbee tray (moved to /usr/sbin) if appropriate.
  - The network_tray executable is moved from /root/startup to /usr/sbin.
  - SNS and networkwizard/net_setup use the new (default 15-second) delay value if specified (in /etc/dhcpcd_dropwait_secs) and the enhanced dhcpcd is present.
  - The wag-profiles.sh script is moved into its own package so that net_setup and Frisbee can use it as a dependency.
  - If present, Frisbee 3.0 is run from the wizard instead of the installation of a pet package to add it, since it is to be built into puppy as a package. (The older, beta Frisbees will overlay the script that runs Frisbee, so might still work, but would confound verification/troubleshooting.)

Richard

UPDATE 11/9/2012: Modified the woof-update package to switch network trays back to normal in case changed by Frisbee. Please use the newer version of that package.

UPDATE 11/11/2012: Updated woof-updates package to match the frisbee-3.0 20121111 package internally. Required when installing that (or later) Frisbee package.

UPDATE 11/12/2012: Updated woof-updates package again to correct tray swapping and restore Frisbee to the default-selection radio-button list.

UPDATE 11/15/2012: Updated woof-updates and wag-profilies packages to correct use of the "dropwait" option (thanks to 01micko's PM). This should reduce the frequency of lost wireless connections.

UPDATE 12/6/2012: Updated woof-updates to 20121204 for new interfaces to Frisbee. Use it with frisbee_integrated-20121206 and later.

UPDATE 12/11/2012: Updated the dhcpcd-dropwait package to add files and links to make it a complete replacement for the puppy dhcpcd pet package - after download 48. Thanks to pemasu for reporting those omissions.

UPDATE 01/16/2013: Updated the woof_updates and network_tray packages to match the released version of "integrated frisbee". They are required for support of the new "frisbee-1.0" package, below, and are incompatible with the previous versions of them. The complete set is also available as a tarball in the Frisbee beta2 thread:
http://www.murga-linux.com/puppy/viewto ... 292#678292

UPDATE 01/30/2013: Uploaded renamed dhcpcd-dropwait package, which is an optional replacement for the dhcpcd package, not a separate/supplemental program - after download 110. Uploaded the latest version of the wag_profiles package, to match that being tested in the "kit" in the "Frisbee beta2" thread - after download 90.

UPDATE 2/6/2013: Uploaded the network_tray package, now with installation/uninstallation scripts to restart the replacing program afterward.

Barry,
UPDATE 2/7/2013: Uploaded a duplicate of network_tray-2.6 renamed as "2.5-frisbee", to represent it as an alternative to 2.5, not an upgrade to it. If you have another way to identify alternates, please adjust the names of the network_tray and dhcpcd...dropwait packages accordingly. Or have me do it.

UPDATE 2/17/2013: Removed the 2.5--frisbee alternative, since 2.6 adopted for woof. Uploaded release version of network_tray. Added alternate net_setup package that includes the content of wag_profiles, because wag-profiles.sh is used only by net_setup.

[BarryK]

I noticed one line without gettext in /usr/sbin/filemnt. It's line 93 and it should be something like this:

Code: Select all

pupmessage -bg '#FF8080' "`eval_gettext "Sorry \\\$imgFile is already mounted and in-use by Puppy
on \\\$MNTDIMG_MNT_PT from \\\$MNTDIMG"`"    #120220

Thanks, done.

[rerwin]

Attached is Frisbee modified to be part of puppy. As I do not have a wifi setup for testing, please try it with the above set of architecture packages.

My actions have been to reconfigure some of the parts, avoiding modification of the logic. The main change is to run it as any other network manager would run from the "connect" wizard, without an intermediate installation of a pet package.

The other significant change is to rely on the existing (Precise) version of defaults_chooser (which includes reference to Frisbee), instead of the older one included in the 2.x-betas. Please verify any activity that uses that function.
Richard

EDIT 11/4/2012: Re-uploaded package to correct the text for label "Wpa_cli" in the Frisbee dialog window, after download number 3.

EDIT 11/5/2012: Peebee informs me that the Frisbee wireless tab-panel is greyed out (disabled) and that he does not see the popup messages. The messages and the Frisbee tray icon should appear after Frisbee is set as the current manager and a reboot is done. The grey-out issue is what I am working on, so no need for further reports of that.

EDIT 11/6/2012: I have corrected the "grey-out" problem in the replacement package. Note, however, that Frisbee must be made the default network manager for the wireless tab to be accessible, but only after a reboot. I hope to improve that situation, but provide frisbee as is for further testing. The steps for testing it are here:
http://www.murga-linux.com/puppy/viewto ... 938#662938

EDIT 11/7/2012: I have corrected the pink pop-up message, "(interface) is down", to display at the top of the screen instead of in the center and never timing out. It is easily fixed by editing /lib/dhcpcd/99-down, line 12, to move " top" to follow "-placement". I also changed the version file content to "3.0". So, reinstalling is not necessary for this. Peebee reports that Frisbee works except for this minor issue.

EDIT 11/9/2012: I have made improvements to the frisbee package (20121108) regarding the popup messages and setting of the appropriate network-tray version (Frisbee vs. the other). Details on page 22 of this thread:
http://www.murga-linux.com/puppy/viewto ... 753#663753

UPDATE 11/10/2012: Oops! The 20121108 Frisbee package still had the greyed out wireless tab. I thought I had solved that but was testing in a contaminated environment. Please install the corrected package, 20121110.

UPDATE 11/11/2012: Uploaded Corrections and internal cleanup in response to peebee's reports from running via the connect wizard. Frisbee now seems to behave as I intend. It should run as it has when selected as the "default tool". But you have to select it. From the connect wizard, it may be delayed a few seconds while it get set up; Subsequent runs that way will start faster unless another tool is selected between Frisbee runs. The pop-ups will start only after Frisbee starts, but will continue until another tool is selected. Now the challenge is to verify that the connections work as expected. NOTE: Be sure to also install the package, woof_updates-20121111 (or later)! It synchronizes with internal modifications.

UPDATE 11/12/2012: Uploaded with corrections to allow Frisbee-3.0 to run in slacko and later-kernel puppies. The wpa_* files are in different locations in those puppies. Also made several small corrections to avoid unnecessary error messages.

UPDATE 12/6/2012: Uploaded New version derived from Frisbee-beta-4 from saluki/carolina projects, with some added bug fixes. Improves robustness when switching between network managers. Package name changed to "frisbee_integrated", to differentiate it from the original Frisbee packages. Dropped the presumptuous "3.0" part of the name.

UPDATE 12/10/2012: Uploaded version with thunor's gtkdialog recommendations and some typo corrections, in an attempt to resolve the sometime abort-exits. But they still occur, although they do not appear to cause trouble. Please report any other issues. Note that the old option to specify a preferred access-point MAC address has been removed from Frisbee (by Jemimah, I assume). If anyone depends on its being there, please tell me, as I am inclined to accept Jemimah's decision on that removal.

UPDATE 1/16/2013: Uploaded released version of integrated frisbee, now to be known as frisbee-1.0. Please replace the older version with this, as well as the updated supporting packages, above. There are significant, incompatible differences since the version originally posted here. The complete set is also available as a tarball in the Frisbee beta2 thread:
http://www.murga-linux.com/puppy/viewto ... 292#678292
Please provide feedback to that thread. To generate diagnostic information, please install and use the "pdiag" pet package, available here:
http://www.murga-linux.com/puppy/viewto ... 751#671751

UPDATE 1/16/2013: Uploaded internationalized and civilized version that does not kill the standard network_tray connectivity icon.

UPDATE 2/17/2013: Uploaded release version.

UPDATE 2/21/2013: Uploaded release version with internationalization correction.

UPDATE 2/27/2013: Uploaded version 20130227, with wpa_supplicant debug-level logging turned off by default.
EDIT: Replaced with 20130228 after download #4 to improve a test that does not change the functionality, just removes a vulnerability.

[rerwin]

Attached are the difference listings for the puppy changes posted above, as well as the source tarball for the enhanced version of dhcpcd.

EDIT: added the difference listing between frisbee 2.4beta and 3.0 which was derived from it.
Richard

[puppyluvr]

Hello,
rerwin,
D/L directly into my Precise woof tree.. Will get back to you.. Thx.....

[otropogo]

Have just spent several hours trying to configure the display in Puppy 5.4. Although I've had some problems with Quirky-120 in the last two days, and with Puppy 528 in the past, I've never been completely stumped before.

My adapter is a ATI X1550 w/256MB of RAM, in an Intel D865GLC motherboard. I've got two monitors attached via a Maxtor DualHead2Go adapter. One is a 21" Sun CRT converted to PC use, the other is a 17" LG Flatron L1710B LCD.

In Lupupluslibre 005-2, I'm able to run both monitors at 1600x1200@60Hz, or at 1280x1024@75Hz.

In Quirky, I can run both at 1600x1200, 1280x1024@60 (and 1024x768@75, if I can trust my notes). The CRT is getting old and dim, so I like to have it available, but prefer to use the LCD most of the time.

There's often a problem installing Linux, not just Puppy, initially with this setup as the probe generally wants to spread the display across the two monitors. In Puppy 528 this is fairly easy to fix, especially when the special Radeon driver is installed. In Quirky it was quite a bit of work to get it right, because xorgwizard keeps insisting on making the display 2560x1024x60 , and when I choose 1280x1024 insists on making it 85Hz, which the LG can't handle.

However, eventually I can get both monitors to display at the same time in at least two resolutions that fit in both Quirky and 528.

But in 5.4, I haven't been able to find anything except 2048x768@60 (spread across both monitors) that fits. With other configuration tried, the LG give an error message: "dsub input signal out of range". And some settings that work on both monitors elsewhere wont display on either in 5.4.

Right now I'm running Puppy 5.4 at 1600x1200 on the CRT, and I can't change it down to 1280x1024@60, xorgwizard just ignores the input.

I've also tried choosing the "Radeon" option in Xorgwizard, and that blacks out both monitors.

Very frustrating. Any suggestions?

Update: according to report-video, I'm only running in 1280x768 under lupu528, whereas the resolution changer reports 1280x1024

Under Puppy 5.4, report-video doesn't report any resolution, only the colour depth, whereas resolution changer reports 1600x1200 as being in effect (*).

[otropogo]

Have gone another hour or two trying in vain to get a usable xorg configuration for my monitors in Puppy 5.4. I've got two choices, 2048x768 @ 60Hz, spread over two monitors (hideous and unwieldly), or the LCD monitor is disabled, and the 21' CRT displays at 1600x1200@60Hz - very uncomfortable for my viewing, plus I'm stumped if my CRT gives out.

So unless someone can talk me through another way of configuring, I'm stumped.

Meanwhile, I can't find any means of adding a new wallpaper to the selection provided. I've never had this issue before either.

[James C]

Another quick test of Precise 5.40 with a different Nvidia card. Sound,internet and display all correct on boot.

# report-video
VIDEO REPORT: Precise Puppy, version 5.4

Chip description:
oem: NVIDIA
product: nv44 Board - p382h1 Chip Rev

Driver used by Xorg:
vesa

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

Actually using "nouveau".


-Computer-
Processor : Intel(R) Pentium(R) 4 CPU 2.00GHz
Memory : 1554MB (194MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Mon 05 Nov 2012 01:54:53 AM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Gallium 0.4 on NV4A
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : ICH - Intel 82801BA-ICH2
Audio Adapter : MPU-401 UART - MPU-401 UART


Multimedia audio controller : Intel Corporation 82801BA/BAM AC'97 Audio Controller (rev 05)
VGA compatible controller : NVIDIA Corporation NV44A [GeForce 6200] (rev a1) (prog-if 00 [VGA controller])
Ethernet controller : D-Link System Inc Gigabit Ethernet Adapter (rev 11


...the above also recorded in /tmp/report-video
# glxgears
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
2194 frames in 5.0 seconds = 438.672 FPS
3353 frames in 5.0 seconds = 670.486 FPS
3800 frames in 5.0 seconds = 759.843 FPS
3804 frames in 5.0 seconds = 760.669 FPS
3764 frames in 5.0 seconds = 752.799 FPS

[666philb]

Meanwhile, I can't find any means of adding a new wallpaper to the selection provided. I've never had this issue before either.

put your new background in /usr/share/backgrounds

or you could use don570's pet, which gives you an option to send a picture to the backgrounds folder by right clicking http://www.murga-linux.com/puppy/viewtopic.php?t=67013

[BarryK]

[*] One of the most frequent questions in the forum is why the modem doesn't connect. I have a G3 ZTE MF636 USB modem, of the type that looks like a memory stick, and also contains memory, and it is a couple of years old by now. It does not connect.

Have you tried first installing:

http://distro.ibiblio.org/quirky/pet_pa ... 2.4-up.pet

and

http://distro.ibiblio.org/quirky/pet_pa ... 120815.pet

?

Please don't do that. Precise Puppy 5.4 already has usb-modeswitch and usb-modeswitch-data. Every Puppy will have them.

If you are having problems with a USB 3G modem, do not blame Puppy. Go to the usb-modeswitch forum/mail-list and discuss it there, as it is a problem with that application.