Puppy 4.3 Final -- bug reports and suggestions

[hiveman]

Thanks for the advice on how to clean my mouse. Unfortunately that doesn't apply to my situation. The Dell Inspiron 8200 is a laptop - one of the older laptops that offer both a touchpad and and eraser-style pointer. Just for grins I did pull out a ps/2 external mouse, but that doesn't make any difference. The pointer still disappears every few minutes.

To make sure that this was really a 4.3 issue I rebooted off a CD with 4.2.5 on it. I've been using it for 30 minutes or so with no problems. All three interfaces work - external ps/2 mouse, touchpad and eraser. The pointer has not drifted or disappeared. I guess I'll fall back to 4.2.5 and try to upgrade again with the next release, unless anyone has any suggestions to try.

[aarf]

ps2 connected mouse is no good, u need to try a mouse that is connected via a usb port even if it has a ps2 plug and usb adapter it is ok but it must be connected into the usb port.

[rerwin]

The kernel 2.6.25.16 version of Puppy 4.3 does not detect these modems, because the modem-rules file and firmware tarball are the incorrect versions. I obtained the appropriate versions from puppy 4.1.5. The attached dotpet applies ONLY to the k2.6.25.16 puppy installations. The two files should be added to the bugfix release 4.3.1-k2.6.25.16.
Richard

[Kenny-M]

Aarf,

Is that a problem particular to Dell? This is no BIOS setting?

hiveman,

Back when I used to do IT ending around 2005 I though Dell had a patch for the eraser mouse. Those things were always an issue. Well, If you could find the patch that would only help you using M$iscrosoft.

All I know is those touch pads and eraser mice used to be a big problem with Windows NT & 2000 Pro.

[aarf]

Aarf,

Is that a problem particular to Dell? This is no BIOS setting?

hiveman,

Back when I used to do IT ending around 2005 I though Dell had a patch for the eraser mouse. Those things were always an issue. Well, If you could find the patch that would only help you using M$iscrosoft.

All I know is those touch pads and eraser mice used to be a big problem with Windows NT & 2000 Pro.

ps2 mouse is a problem with linux and/or old hardware.
may have been another of those issues fixed in 421 but missed in 430 but i dont know about that.

[rjbrewer]

I'm using 430 small, new kernel.

My old Inspiron 4000 has bios options for ps2+mouse pad,
ps2, or serial.

With ps2+mouse pad both the pad and eraserhead pointer
work using a ps2 or usb mouse.

The left click has been messed up since I got it, so I just use
a usb mouse with the bios set to serial.

Apart from the left clicker, it will work with touchpad, pointer,
ps2 mouse and multiple usb mice, at the same time.

[dogone]

Hiveman, perhaps it will reassure you to hear that the touch pad and external USB mouse on my Dell 8200 laptop work perfectly well under 4.3 "small". No disappearing pointer or intermittent behavior.

You might check to determine if your 8200 has the last BIOS release. Mine does. A BIOS reset would be the my next step.

The good news is that everything can work. The 8200 is actually my most Puppy friendly computer!

[Kenny-M]

I must say I have never had a problem with a desktop system using standard P/S-2 Mice and Keyboards.

When using USB Mice and Keyboards for example on my Dell 745 Optiplex Desktop when Puppies first prompt comes up to press F2 nothing happens. The devices don't wakeup until the GUI comes up. That's a problem.

One thing that impressed my about this budget system:

http://www.newegg.com/Product/Product.a ... -_-Product

was it had standard P/S-2 connectors and 15 pin VGA port. Looks like a nice experimental machine. No floppy drive. No floppy connector on the Motherboard.

[charlie6]

Hi,
on 4.3 k2.6.30.5 frugal install
with xorg_xorg_full_dri-7.3.1.pet installed
I get the message:
EDITED: extract of comment code repaced by full comments code

Code: Select all

## glxinfo
name of display: :0.0
display: :0  screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, 
    GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe, 
    GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, 
    GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, 
    GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, 
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
    GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, 
    GLX_SGIX_fbconfig, GLX_EXT_texture_from_pixmap
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.4 (1.5 Mesa 6.5.2)
OpenGL extensions:
    GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program, 
    GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, 
    GL_ARB_occlusion_query, GL_ARB_point_parameters, GL_ARB_point_sprite, 
    GL_ARB_shadow, GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp, 
    GL_ARB_texture_compression, GL_ARB_texture_cube_map, 
    GL_ARB_texture_env_add, GL_ARB_texture_env_combine, 
    GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, 
    GL_ARB_texture_mirrored_repeat, GL_ARB_texture_non_power_of_two, 
    GL_ARB_texture_rectangle, GL_ARB_transpose_matrix, GL_ARB_vertex_program, 
    GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, 
    GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, 
    GL_EXT_blend_logic_op, GL_EXT_blend_minmax, GL_EXT_blend_subtract, 
    GL_EXT_clip_volume_hint, GL_EXT_copy_texture, GL_EXT_draw_range_elements, 
    GL_EXT_fog_coord, GL_EXT_framebuffer_object, GL_EXT_multi_draw_arrays, 
    GL_EXT_packed_pixels, GL_EXT_paletted_texture, GL_EXT_point_parameters, 
    GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color, 
    GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, 
    GL_EXT_shared_texture_palette, GL_EXT_stencil_wrap, GL_EXT_subtexture, 
    GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp, 
    GL_EXT_texture_env_add, GL_EXT_texture_env_combine, 
    GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias, 
    GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, 
    GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels, 
    GL_ATI_draw_buffers, GL_ATI_texture_env_combine3, 
    GL_ATI_texture_mirror_once, GL_ATIX_texture_env_combine3, 
    GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, 
    GL_MESA_pack_invert, GL_MESA_ycbcr_texture, GL_NV_blend_square, 
    GL_NV_fragment_program, GL_NV_light_max_exponent, GL_NV_point_sprite, 
    GL_NV_texgen_reflection, GL_NV_texture_rectangle, GL_NV_vertex_program, 
    GL_NV_vertex_program1_1, GL_SGI_color_matrix, GL_SGI_color_table, 
    GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, 
    GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SGIX_depth_texture, 
    GL_SGIX_shadow, GL_SGIX_shadow_ambient, GL_SUN_multi_draw_arrays

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x23 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x24 16 tc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 None
0x25 16 tc  0 24  0 r  y  .  5  6  5  8  0 16  8 16 16 16 16  0 0 None
0x26 16 tc  0 24  0 r  .  .  5  6  5  8  0 16  8 16 16 16 16  0 0 None
0x27 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x28 16 dc  0 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 None
0x29 16 dc  0 24  0 r  y  .  5  6  5  8  0 16  8 16 16 16 16  0 0 None
0x2a 16 dc  0 24  0 r  .  .  5  6  5  8  0 16  8 16 16 16 16  0 0 None
# 

whereas it tells "Yes" on pup4.3 k2.6.25.16

then how to get OpenGL working on 4.3 k2.6.30.5 using xorg_xorg_full_dri-7.3.1.pet ?

thanks for any idea
cheers

see also more details on page 5 of
http://murga-linux.com/puppy/viewtopic. ... 4&start=60
charlie

[gray]

The new puppy package manager has an anoying problem when installing .pet packages with menu entries. It changes the category to BUILDINGBLOCK for any .desktop category that it does not recognise (like any of the Xfce specific ones such as X-Xfce-Toplevel).

[magerlab]

still have strange svg files behavior
some of them are seen in rox and fbpanel
but some do not display
i want to use svg mime icons and icons in fbpanel

is it a gtk bug?

[FrankA]

4.3 is cool.

conexant hsfi pci modem & wvdial work out of the box. excellent.

[jrb]

Pardon if this has been mentioned before.

The thesaurus (aiksaurus) in Abiword did not show up anywhere I could find.

I took libAbiAikSaurus.so from abiword-plugins-2.6.3.pet and placed it in /usr/lib/abiword-2.6/plugins/. Now the thesaurus is available on the tools menu and when you right click on a word.

[yorkiesnorkie]

Issues:

• Full Install of Puppy 4.3 with kernel ".30" does not poweroff computer
  Next boot of the computer X does not start and Puppy drops out to the command line you have to type xwin or xorgwizard and then xwin to get X to start.
  Attempting to boot the computer from the live cd then results in either a drop out to a flashing prompt ISO Linux..., or the pup sfs file is not found. The live cd will not boot, tried kernels ".30" and ".25"

Quote from another of my posts

Ok, I'm less cross than I was last night. What follows is a bit of a digression but I return to the main issue:

So, what's the difference between Puppy 3 and the 4 series? I know Puppy 3 will boot from the CD without any issues however I've been getting issues with 4.

I've got an IBM 380 XD with 96 mb of ram, a pentium II with MMX, and I typically do a full install on an ext2 partition with an additional Linux Swap.

Typically with one of the 4 series CDs 4 Dingo (with Sylpheed for Mail), Puppy 4.1.2, Puppy 4.2.1, Puppy 4.3 my pc will come back with the error XXX-sfs not found, XXX being the version. In these cases there is already a previous version of a puppy full install on the pc.

If I enter one or more of the variations of the boot then "sometimes" the live cd will boot the computer:

puppy pfix=ram
puppy pfix=ram,no5
puppy pfix=purge

That's great and I can usually complete the upgrades.

However on occasion all I get is an ISO linux message and a flashing prompt "_" or I get the sfs not found message. Powering off and trying a reboot does nothing to improve the situation.

If I go back and boot from the Puppy 3 CD, and delete the swap and ext2 partition, and re-create empty partitions "sometimes" then the 4 Dingo series CD will start without a hitch, i.e. I get past the ISO Linux message and the sfs is found, the live CD boots.

This has nothing to do with the present issue, but I note that I'm not the only one to have issues with the sfs not found error. It does have bearing in the sense that when I tried to mount the Puppy 4.3 with the kernel K2.6.30... I got no farther than the ISO Linux message.

That can make you think you've got a FUBAR CD, but they are actually good. I check mine for a good burn.

I'm going to try the version of the live CD with the earlier kernel http://ftp.nluug.nl/ftp/pub/os/Linux/di ... 6.21.7.iso and the small version http://ftp.nluug.nl/ftp/pub/os/Linux/di ... -small.iso and see what happens. However, I expect that I'll likely get the same issue with the live CD.

I wonder if Barry's notes about previous sfs have any bearing:

A word of advice
if you try more than one .iso file, be sure to delete all traces of the previous one before testing the next. When you shutdown the first time and save the session to hard drive (to what we call the "pupsave" file), one or two files off the CD are also copied to the hard drive: pup-430.sfs (and maybe zp430305.sfs). The easiest way to cleanup is to boot the next live-CD with the boot parameter "puppy pfix=ram" (which starts up with Puppy running totally in RAM) and after bootup take a look on the hard drive and delete those previous files.

However, if you shutdown without saving a session, then the above problem will not occur. Thus, for quick evaluation of these live-CDs, run each one without saving the session, so nothing gets left behind on the hard drive.

This should apply only to the live cd. If the live cds continue to fail I might try first backing up any sfs I find on the full install and moving it to another non-linux partition and then try booting from the live cd just to see what happens.

- - - -

Returning to the original shut down and boot issue where x does not start - I would still like to run 4.3, but I'll have to try an earlier kernel. It would be nice to have shutdowns and restarts on the full install work properly but that means I have to get a live cd to work.

The source of the quoted post http://www.murga-linux.com/puppy/viewtopic.php?t=47079

Yorkiesnorkie

[yorkiesnorkie]

Notes

• I tried the live CDs with the later kernels but they woudn't boot the computer.
  4.1.2s live cd wouldn't boot.
  Puppy 3's live cd will boot, no issues.
  I confirmed the burns of the CD as good.
  All CDs were burned within Puppy 4 Dingo, using Pburn, on our Compaq Presario Desktop.

Deleting the contents of EXT2:

While 3's live CD was running I deleted the contents of ext2 (in order to test whether something in the full install was affecting the live CD) then tried a reboot using several of the 4.3 cds with various alternative kernels. However, it still wouldn't boot. I got stuck at vmlinuz each time.

The version of 4.3 I didn't try was the "small" version. I did download it though for a later try. This ol' geezer needed some shut-eye. My spouse is starting to look at me funny too.

Since the ".30" kernel worked before but I had problems with shutting down and starting I decided to give 4.1.2 another try since I know that one did work a while back. True to form I tried 4.1.2 and bingo, it booted the live cd.

Intermediate Conclusion:

Basically on this particular PC the live CDs after 4.1.2 won't boot the PC. I'm not exactly sure what the conditions that contribute to that are. Could there be something in Linux Swap? I deleted what was in EXT2 but this may or may not have contributed to 4.1.2 booting. Clearly whatever the issue is it doesn't affect Puppy 3 at all. Maybe 96 mb of ram is not enough even with the swap to successfully run 4.3

What has worked on this PC, Proper shut downs and startups:

• Puppy 2.15 CE
  Puppy 3
  Puppy 4 Dingo
  Puppy 4.1.2 Retro
  Puppy 4.2.1 Retro (slow)

For the time being I'll be using 4.1.2 since its clearly the most stable version of Puppy on this particular PC. I'll probably create a separate partition for 4.3, if i can get one of the live cds to boot so I can test it further. I'm going to try the various live CDs I've made on our ol' Compaq Presario desktop to confirm they work/don't work.

Yorkiesnorkie

[Lobster]

Yesterday connected a friends Dell to his new modem router by wireless
That is lap dog one
Lap dog 2 is my Dell Inspiron 3500 pentium II
also connected wirelessly without too much trouble

Thanks to Tempestuous and others who work tirelessly for
us Wi-fi enabled Puppys.
.
Thanks Guys

[kjoe]

Hello,
This is a bug reminder with regard to the next release but also a request to anybody who can help me fix the bug causing remasterpup2 script to stop in Puppy 4.30, which I've described here

Thanks

kjoe

Edited Oct 10, 2009: Barry K. has just announced in his blog that he has found the bug that caused the Remaster CD script to crash if there are two optical drives. So this will be fixed in the 4.31 release. Thank you Barry!

kjoe

[Ledster]

First of all - a great guide to building puppy with woof from Iguleder!
Ran through it using puppy 4.3 (2.6.30.5 kernel) and built one with the 2.6.29.6
kernel, and it worked first time.
Now for why I did it. I have an Acer Aspire One on which I run upup alpha 9 from a usb stick
and it works fine. Had to put pciehp:pciehp_force=1 into the addlist section of
/etc/rc.d/modulesconfig to make the sd card slots work, and I can now boot up and
insert cards as and when required. Try the same with puppy 4.3 and the card(s)
must be in the slot(s) whenever I boot or they are not recognised (once booted you
can take them out and put them in at any time). So I wondered if this was anything
to do with the kernel version and built puppy with the same version as upup
(almost! 2.6.29.6 instead of upup's 2.6.29.4).
Made no difference.
So my question is, what difference is there between upup and puppy 4.x causing this?
If it is a simple config change I could probably cope (I am fairly new to linux, though).
It's one of those really annoying little things that I would love to fix.
Anyone any ideas?

Ledster

[gersen]

Can't get puppy 4.3 to recognise my usb joystick. Tried modprobe joydev which fixed it on lighthouse puppy, but doesn't work here.
Strange thing is games running under wine see the joystick just fine, but X-plane which runs natively cant see it.
Running jstest /dev/input/js0 just returns "no such device"
The system is seeing it though, unplugging and replugging the joystick gives me this in /var/log :

Oct 8 22:39:19 (none) user.info kernel: usb 2-6.3: new full speed USB device using ehci_hcd and address 7
Oct 8 22:39:19 (none) user.info kernel: usb 2-6.3: configuration #1 chosen from 1 choice
Oct 8 22:39:19 (none) user.info kernel: input: Saitek Saitek X52 Flight Control System as /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6.3/2-6.3:1.0/input/input8
Oct 8 22:39:19 (none) user.info kernel: generic-usb 0003:06A3:075C.0005: input: USB HID v1.11 Joystick [Saitek Saitek X52 Flight Control System] on usb-0000:00:1d.7-6.3/input0

Is this a bug or am I missing something, advice appreciated ?

Regards

[rerwin]

Puppy 4.3's expanded dialup and wireless modem coverage may generate many requests for assistance for particular cases. Rather than repeat the various instructions to send several files, compressed into a tarball (which is all a mystery to n00bs) I have created a script to collect everything I can think of that I might need to understand their situations.

This tool requires a small modification to PupScan, to run it "silently" to create the PCI and USB hardware-and-driver files and exit without presenting the dialog. Here are the differences in the pupscan script:

Code: Select all

6a7
> #v431 rerwin: Add --silent option to only generate files, without display.
7a9
> [ "`echo $@ | grep ' *--silent *'`" != "" ] && SILENT=true || SILENT=false #v431
24c26
< [ ! -f /lib/modules/$KERNVER/modules.pcimap ] && load_zdrv #func in functions4puppy4
---
> #[ ! -f /lib/modules/$KERNVER/modules.pcimap ] && load_zdrv #func in functions4puppy4
272c274
< RETSTRING="`echo "$MAINDIALOG" | gtkdialog2 --stdin`"
---
> [ $SILENT != true ] && RETSTRING="`echo "$MAINDIALOG" | gtkdialog2 --stdin`" #v431

Barry, please accept the updated pupscan for 4.3.1, but the utility, pmodemdiag, could merely be added to the repository for user download as needed. (Or maybe it belongs somewhere else.) The dotpet places the script in the home (/root) directory, similar to where scanModem would go. It is intended to be run from a console, so the user gets feedback, but I find that clicking its icon also runs the tool silently; the user has to know where the tarball ends up (/root).

The instruction to a user would be to install the dotpet, in a console type:
./pmodemdiag
and attach the tarball to a posting or PM to the helper.

BTW: The saved version of the wvdial.conf file has the usernames, passwords, and PIN codes replaced by "X"es, to protect privacy.

UPDATE 10/13/09: Changed version to more standard format and added collection of a pgprs-option file, for comparison to what wvdial produces. Added prevention of overwriting an earlier tarball with same name as new one. (This would be "-3" under the old versioning numbers.)
Richard