Puppy Linux Discussion Forum

Pizzasgood · Posted: Fri 12 Dec 2008, 00:50 Post subject:

You don't have to burn a CD just to get at the files inside. In the old days, I would have told you to run this and then look inside /mnt/data:
mount -o loop puppy.iso /mnt/data

But nowadays it's even easier: just click the iso. When you're done, click it again and Puppy will unmount it.

The same techniques also work for accessing the stuff inside .sfs files. It works on the save file too, but there's a catch: clicking it to mount will fail if the save file is the one you're booted from, or if it has the same name. Renaming it should fix that, or run the command by hand.

Pizzasgood · Posted: Fri 12 Dec 2008, 01:10 Post subject:

/usr/sbin/petget has issues with spaces in the path to the file it's installing. Should be fixable by putting quotation marks around the $ALIENFILE variable at lines 971 and 981. I attached a working version and a diff.

Dougal · Posted: Sun 14 Dec 2008, 07:11 Post subject:

aragon · Joined: 15 Oct 2007 Posts: 1698 Location: Germany

petget-fix by Pizzasgood tested => works!

cheers
aragon

Botanic · Joined: 05 Sep 2007 Posts: 241 Location: Toulouse, France

Botanic · Joined: 05 Sep 2007 Posts: 241 Location: Toulouse, France

i removed everything related to the second screen using mp and executed xwin.
Now it works...
But i have the feeling that i'm still in vesa mode

rerwin · Joined: 24 Aug 2005 Posts: 1883 Location: Maine, USA

Autodetection of Intel, mwave, and certain Agere modems disappeared from Puppy 4.1 after working (except agrserial) in 4.0. To compensate, I provided some workaround instructions for 4.1.2. Now I have restored the autodetection of all these PCI devices.
EDIT 2/15/09: For the ISA version of mwave modems, I corrected the forced-loading logic to bypass loading of the mwave module (as done, but differently, pre-4.1). The details are here:
http://www.murga-linux.com/puppy/viewtopic.php?p=270523#270523
/EDIT

The fix uses new udev rules to trigger loading of the driver modules by augmenting the /sbin/pup_event_backend_modprobe script to accept as an optional argument a module name to be used if another module is not found using the normal method (so it could not override another module). In addition, /sbin/pup_event_backend_modprobe is corrected to restore the module override function that substitutes module dmfe for tulip for a particular NIC.
EDIT 2/15/09: Also, /etc/rc.d/rc.sysinit is corrected to skip modprobing mwave after extracting its firmware, so that the initialization script can perform the modprobe. /EDIT

The fix is attached as a dotpet, so users can apply it to 4.1.2. It contains only the following 3 files:
- /etc/udev/rules.d/60-udev-modem.rules
- /etc/rc.d/rc.sysinit
- /sbin/pup_event_backend_modprobe

I have tested with my Intel536-supported modem. However, the same implementation technique is used for all of the affected modems.
EDIT 2/15/09: Except for rc.sysinit, this dotpet is ready for 4.2; however, rc.sysinit has changed in 4.2, so that update should be applied manually, as described in the above-referenced posting about it. /EDIT
Richard

UPDATE 2/11: I have updated the above information and attached an updated version of the of this fix, to remove the no-longer-needed O2 Micro cardbus controller fix and restoring the "override" capability dropped from 4.1. The bugfix should resolve the dmfe-module issue described here:
http://www.murga-linux.com/puppy/viewtopic.php?p=264943&search_id=1610028076#264943

UPDATE 5/2: I have replaced the dotpet. It improves the udev rule and modem test, and makes the Intel536/7 drivers use device names created when they load (e.g., 535ep0). Would someone with an Intel 537 modem please tell me by PM whether it uses 5370 or some other name, since I do not have any such modem for testing? Do not use this dotpet on puppy 4.2, because the rc.sysinit file is wrong for it.

Update 6/21: I have upgraded the dotpet to support a second (and more generic) Intel537 modem. I have acquired a "537" modem for testing. This new version uses devices /dev/5360 and /dev/Intel5370, which appear when their driver is first loaded. If your connect wizard and pupdial still show either /dev/536 or /dev537, please use pupdial to "probe > ERASE" that setting and reboot to pick up the new device names.

UPDATE 8/22/09: Upgraded to "-5" for compatibility with the 3G-wireless (-12) support, to avoid regressing it if this package is installed with it.

Remember, this is only for 4.1.2. For 4.2.1, use the similar dotpet posted here: http://www.murga-linux.com/puppy/viewtopic.php?p=318272#318272
Richard

edoc · Posted: Mon 19 Jan 2009, 01:07 Post subject:

I am suffering serious problems with 4.12 on a laptop where prior versions have done quite well.

CUPS
gxine
serial
etc.

Is it possible that 4.12-Retro might resolve them or are these not the kind of things Retro usually fixes?

vtpup · Posted: Mon 26 Jan 2009, 00:28 Post subject:

edoc, you don't say which laptop, but I use the following and ALL require 4.1.2 retro:

Thinkpad 600e Pentium II 400 mhz
Thinkpad 600e Pentium III (hack) 810 mhz
Thinkpad T30 Pentium IV 1.8 ghz

The last laptop, seemed to work well for a few weeks with 4.1.2 new kernel, but eventually I discovered it was unable to handle DVD writing, and sometimes reading as well. A change to 4.1.2 retro cleared this problem up.

I still have some problems with even 4.1.2 retro when shutting down the T30 laptop. I get kernel panics (after personal save file is checked) but before final blank screen powerdown. I haven't lost anything, but it is still a pain in the butt, and requires holding down the power button for 30 seconds to kill it. It is also an intermittent occurence.

Disabling ACPI seems to help, but hasn't totally eliminated it from happening on occasion. You might try diabling ACPI with the new kernel first before trying the retro version.

edoc · Posted: Mon 26 Jan 2009, 01:05 Post subject:

On the Z500 I was having the gxine & vlc video display problem - turns out it was a bug in xorg where the setup misreads the drivers and assigns an incorrect value.

Merely changing a 16 to a 24 in two locations of xorg.comf solved that problem.

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1024x768"
EndSubsection
EndSection

I am hoping that the solution to CUPS is a similarly simple problem in a setup script.

I am also hoping that these bug fixes are useful in preventing these same problems in 4.2

Were you having CUPS-specific problems in 4.12-Normal and they resolved in 4.12-Retro?

I did observe a DVD writing problem with my Z500 under 4.11 but not 4.12

WB7ODYFred · Last edited by WB7ODYFred on Tue 27 Jan 2009, 01:37; edited 2 times in total

This updated petget is only related to finding resources on alternative mirrors Before repairing it would only download from ibiblior.org and ftp.nluug.nl The button "gatech.edu" was broken and would not download a pet package file using the "wget" ftp command.

Now, wherever in the world you are running puppylinux you can download from a realatively nearby puppylinux mirror.

The file /usr/sbin/petget is updated for downloading from the "www.gtlib.gatech.edu" puppylinux mirror site and also added
Austria, Australia, South Africa, Portugal, Thailand puppylinux mirrors.

Bosnian, Chec, and German puppylinux mirrors were also available that could be edited into the "petget" file. Someone living in that part of the world could customize to select their favorite puppylinux mirror.

This petget file has Pizzasgood's changes incorporated, to add quote marks around the variable "$ALIENFILE" mentioned above.

Report back any problems via private message to WB7ODYFred

I would like to add an Indian puppy linux mirror to file petget. You may edit in a new mirror website to match button value 18.
Edit lines 1622 - 1705 to add another mirror webisite in the return value 18 position.

Yes, the buttons are crowded, but PuppyLinux is headed for World Domination and needs the added mirror websites to succeed, Yeah!! Wink

save original petget file by executing this command first before installing petget-4.1.2

cp /usr/sbin/petget /usr/sbin/petget_original

to undo changes

mv /usr/sbin/petget /usr/sbin/petget-4.1.2
cp /usr/sbin/petget_original /usr/sbin/petget

See the differences between the two files using "diff" command
diff -b /usr/sbin/petget /usr/sbin/petget_original

26-January-2009 Fred edited to make clear. Bugs fixed, mirrors added.

edoc · Posted: Mon 26 Jan 2009, 12:55 Post subject:

Fred - I am confused s this thread jumps all over the place and it is often difficult to be certain which posts apply to which sub-discussions within the thread. Rolling Eyes

Does your petget modification apply to the xorg or CUPS problems which may both occur during installation or is it only related to finding resources on alternative mirrors?

rjbrewer · Joined: 22 Jan 2008 Posts: 4421 Location: merriam, kansas

Edoc

This thread is about pet packaging bugs.

Your printer problem would probably be better addressed
in the hardware section of forum.

rjb

edoc · Posted: Mon 26 Jan 2009, 13:23 Post subject:

It was just that the video problem (gxine & vlc) was software problem created by an error in xorg during setup so I wondered if the CUPS problem - which did not exist in prior releases - may be the same.

The same printer and the same laptop suddenly will not communicate - the printer works fine elsewhere - the laptop will not address any printer.

As a result of all of that it seems to be that it is 99% probable that this is a bug in 4.12-Normal that is related to a software script error during setup rather than a hardware issue.

WDYT?

Patriot · Joined: 15 Jan 2009 Posts: 734

Hmmm .....

Recently I have the need to test internally made packages on fresh puppys and QEMU enables me to make those tests on different fresh puppy 4.x versions rapidly ...

I've read about how xorg does work on QEMU from here :
http://www.murga-linux.com/puppy/viewtopic.php?t=35469

After like the umph'teen times doing the same on fresh puppy boots, I figured it's good enough time to attempt a fix on this.

I've made a quick patch to xorgwizard to make a simple detection of QEMU. If puppy is running in QEMU then xorgwizard will copy a preconfigured-for-Qemu xorg.conf.new to /root ... this allows it to proceed on the next text screen for resolution selection. Testing of the selected resolution also will now work as intended.

A much more elegant solution would be to write a util to check for all VMs.