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!

kjoeLast edited by kjoe on Sat 10 Oct 2009, 07:30; edited 1 time in total

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?

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 :

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:

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

pmodemdiag-1.0.pet

Description

Gathers diagnostic information for troubleshooting dialup/wireless modem problems.To run, in a console type: ./pmodemdiagFind the pmodemdiag-20....tar.gz in /root and send it for analysis.

I successfully compiled and tested the latest Lucent (kernel-resident) modem driver, but withheld it because it supports the same hardware IDs as the "user-space" Lucent-Agere driver, dev_martian. However, for cases where the martian_dev driver fails to support a Lucent modem, ltmodem could be a fallback. I attach separate dotpets for the firmware update and for the driver itself.

I feel that the firmware update should be included in the bugfix, since the existing firmware would not work with the now-current (ltmodem) driver. The device name has changed to ttySV0 and the old ltserial module no longer exists, necessitating changes to the firmware and files firmware.dep.2.6.30.6, MODULESCONFIG, and 60-dialup-modem.rules. (See the pinstall.sh script.)

I also feel that the driver should NOT be included in Puppy 4.3.1, but should be added to the repository, for users to install as a "last resort" to getting a Lucent/Agere modem working.
Richard

NOTE: As it stands, the firmware dotpet retains the old blacklisting of ltserial-now-ltmodem. That was done to allow the preferred driver, martian_dev, to be loaded, since both drivers were present in Puppy. This is appropriate if Barry were to include ltmodem in 4.3. But for users installing the dotpet, they also must un-blacklist ltmodem in BootManager, as well as then "probe-Erasing" the ttySM0 device selection (in PupDial) and rebooting. If Barry leaves the driver dotpet for the user to install from the repository, I would suggest that the blacklisting be removed (from MODULESCONFIG). That way, the driver dotpet would "just work" when installed.

UPDATE 10/10/09: I have now attached a better version of the firmware update (-2) that eliminates the need to un-blacklist the driver. This is consistent with my recommendation to provide the driver only as a downloadable package and to not build the driver into the Puppy distros.
Richard

ltmodem_firmware_update_to_P430-2.pet

Description

Ltmodem firmware replacement for puppy 4.3.1+.This version omits the blacklisting of ltmodem, so that user merely installs it,then erases the ttySM0 device and reboots to see new device, ttySV0.Appropriate if driver is provided only as installable pack

I have set up an issue tracker on google code for versions 4.4+ and am looking for some volunteers who follows this thread and the bugs forum in general to enter issues into the tracker. (also has project hosting if you are working on any puppy projects or if you would like to be a package maintainer for your favorite programs and keep them up to date)_________________Web Programming - Pet Packaging 100 & 101

When you added a word in the spell check in previous versions, that word would be OK in the spell check when the document was next opened. This is not happening in 4.3.
The file that held the added words in 4.2 was /root/.config/enchant/.en_AU.dic (or en_US.dic). Does any one know what file is applicable (if any) in puppy 4.3?

Regarding he Lucent driver: EZ4arabs reports too me that his Thinkpad R22 with that driver finds the Lucent modem as ttyS4! That is interesting news and is probably related to the new standard driver, martian_dev's, inability to support it correctly. This is a new development, to me. My Lucent PCI modem gets ttySV0, which is what I expect from what I have read. So, be prepared for this surprise, if you need the driver.
Richard

Further thoughts about this development: My guess is that the Lucent driver refused to support EZ4arabs' modem, but blocked martian_dev from loading. Probing in pupdial then finds the serial modem. I would think we would get the same effect by leaving out the Lucent driver and blacklisting martian_dev (in BootManager). If that works, I can probably make a rule to disable martian_dev for this particular modem.

EZ4arabs, could you test this idea? Simply boot a fresh puppy (pfix=ram), Go into BootManager and blacklist martian_dev, "probe-ERASE" in pupdial, reboot. I would expect no modem to be detected. Then probe for the modem in pupdial. If this works, it will lead to an elegant solution to your problem. Thanks.
RichardLast edited by rerwin on Sat 10 Oct 2009, 10:14; edited 1 time in total

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum