Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 26 Jul 2014, 13:12
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
Puppy 4.1.2 Bug Fixes
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 3 [44 Posts]   Goto page: Previous 1, 2, 3
Author Message
rerwin


Joined: 24 Aug 2005
Posts: 1503
Location: Maine, USA

PostPosted: Sat 31 Jan 2009, 18:50    Post subject: Mwave modem module loading bug affects old Thinkpads
Subject description: Replaces posting re mwavem module - reveals rc.sysinit omission
 

EDITED 2/15/09 to replace previous posting:
Member vtpup has advocated for several months to repair the mwave modem firmware tgz file so that it contains a non-stripped version of the mwavem executable. However, in working with him I found another problem that is more basic. I discovered an omission in the forced loading of modules that prevents using the mwave driver on the ISA versions of that modem. Automatic detection can be expected only for PCI and USB devices; so drivers must be forced for ISA devices to make them work.

In the normal hardware detection and setup there is logic that skips actually loading the mwave driver module but causes the firmware/init-script to be expanded. That script then modprobes mwave. The fix is an easy edit to /etc/rc.d/rc.sysinit. Change line 298 from:
Code:
  modprobe $MODULE $MPARAMS
to:
Code:
  [ "$MODULE" != "mwave" ] && modprobe $MODULE $MPARAMS
Just copy the "[ "$MODULE" != "mwave" ] && " and paste it before the existing "modprobe $MODULE $MPARAMS". That will run the mwave setup in the correct sequence when forcong loading of the mwave driver (in BootManager). I have added this fix to my earlier posting for restoring modem functionality, here:
http://www.murga-linux.com/puppy/viewtopic.php?p=266797#266797

Because my previous attachment of another "solution" is unproven and unsuitable for inclusion in Puppy, I have withdrawn it; I suspect it hints at an alternative solution, to be worked out after this rc.sysinit fix.

Thanks to vtpup for resuming interest in making mwave modems work in 4.1.. His recent posting about this is:
http://www.murga-linux.com/puppy/viewtopic.php?p=268940#268940

Richard

Last edited by rerwin on Sun 15 Feb 2009, 19:00; edited 4 times in total
Back to top
View user's profile Send private message 
vtpup


Joined: 15 Oct 2008
Posts: 1077
Location: Republic of Vermont

PostPosted: Sat 31 Jan 2009, 21:31    Post subject:  

Hello rerwin,

I've just booted into 412 retro via pfix=ram on a TP600E to make sure everything is "fresh" for the test.

Steps:
1.) booted pfix=ram
2.) ran PupDial Modem ialup
3.) Did Probe (tried auto, tts0 and tts1)
4.) Got "Warning, no Modem Detected"
5.) Installed the new .pet from this post.
Tried again steps 1 through 4 with same result as in 5.

However, a few things should be checked before jumping to any conclusions:

a.) I didn't reboot because I was in pfix-ram. Maybe that would be needed
b.) This laptop just had its BIOS upgraded to the latest version this week and so it may not have its interrupts properly assigned to the internal modem and serial ports. That's half the battle on a Thinkpad,, as I remember it. Everything was reset to default in the BIOS refresh..

So let me work on this a little more, and we'll see if I can give you a more positive result.

Thanks for all your work on this, as well.
Back to top
View user's profile Send private message 
vtpup


Joined: 15 Oct 2008
Posts: 1077
Location: Republic of Vermont

PostPosted: Sat 31 Jan 2009, 21:46    Post subject:  

deleted by request
Last edited by vtpup on Sun 01 Feb 2009, 21:13; edited 1 time in total
Back to top
View user's profile Send private message 
vtpup


Joined: 15 Oct 2008
Posts: 1077
Location: Republic of Vermont

PostPosted: Sat 31 Jan 2009, 22:16    Post subject:  

deleted by request
Last edited by vtpup on Sun 01 Feb 2009, 21:15; edited 1 time in total
Back to top
View user's profile Send private message 
vtpup


Joined: 15 Oct 2008
Posts: 1077
Location: Republic of Vermont

PostPosted: Sat 31 Jan 2009, 22:40    Post subject:  

deleted by request
Last edited by vtpup on Sun 01 Feb 2009, 21:17; edited 1 time in total
Back to top
View user's profile Send private message 
vtpup


Joined: 15 Oct 2008
Posts: 1077
Location: Republic of Vermont

PostPosted: Sun 01 Feb 2009, 15:10    Post subject:  

deleted by request
Last edited by vtpup on Sun 01 Feb 2009, 21:19; edited 1 time in total
Back to top
View user's profile Send private message 
vtpup


Joined: 15 Oct 2008
Posts: 1077
Location: Republic of Vermont

PostPosted: Sun 01 Feb 2009, 16:28    Post subject:  

deleted by request. Prior posts moved to Thinkpad TP600e Mwavemodem discussion at:

http://www.murga-linux.com/puppy/viewtopic.php?p=270879#270879

Last edited by vtpup on Sun 01 Feb 2009, 21:24; edited 1 time in total
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1503
Location: Maine, USA

PostPosted: Sun 01 Feb 2009, 18:55    Post subject:  

vtpup,
Thanks for trying the mwave dotpet. I did not understand that it takes so much customizing to get it to work. But I can explain why you don't see anything happening.

With Puppy 4.1 the module loading technique changed so that simply using modprobe does not activate the firmware that does some of the magic. But there is a way to overcome that. Use the BootManager to force loading of mwaved with all its parameters. That will trigger the modem init script, which should handle the rest -- I think. (If it doesn't, we could make it so.)
Richard

EDIT: I read this last post first, then noticed your previous ones. So I may be addressing the wrong problem.

But first, I think we should go back to your other thread so that we don't hijack this one, which is for offering fixes. Could you move this dialog back there and reduce the size of your above posts? I think everyone would appreciate that.

Anyway, once you reboot after installing the dotpet, mwaved should get loaded automatically. We need to get that far first, maybe without your mods to the BIOS, considering that you have upgraded it. But I yield to your knowledge on that.

A-hah! The driver is not loading because of another change in module loading for 4.1. But I have made a dotpet to correct that, earlier in this thread, here:
http://www.murga-linux.com/puppy/viewtopic.php?p=266797#266797
EDIT: A catch: This dotpet works only jfor the standard kernel. For the retro kernel, the fix is to insert a line into /etc/rc.d/MODULESCONFIG btween lines 10 and 11, so that lines 10-12 are:
Code:
PCI_OVERRIDES='dmfe 0x00001282 0x00009102 #r_hughes reports tulip module not work.
mwave 0x00001014 0x0000007d #not in modinfo.
'
This is needed only in 4.1.2 retro, since 4.1 and 4.1.1 already contain the line (and others).

Richard

Last edited by rerwin on Mon 02 Feb 2009, 12:42; edited 1 time in total
Back to top
View user's profile Send private message 
vtpup


Joined: 15 Oct 2008
Posts: 1077
Location: Republic of Vermont

PostPosted: Sun 01 Feb 2009, 21:59    Post subject:  

Quote:
But first, I think we should go back to your other thread so that we don't hijack this one, which is for offering fixes. Could you move this dialog back there and reduce the size of your above posts? I think everyone would appreciate that.


Apologies, didn't realize it was only for posting solutions since you requested test results here in this thread..

If the thread is reserved for solutions only, then perhaps it would be wise to only post tested software here and test it prior to inclusion. You could request testing results first elsewhere in a thread devoted to testing that package.

Apologies again...and thanks!
Back to top
View user's profile Send private message 
PaulBx1

Joined: 16 Jun 2006
Posts: 2308
Location: Wyoming, USA

PostPosted: Thu 05 Feb 2009, 17:44    Post subject:  

The net-setup.sh script contains this line:

Code:
mv -f /etc/resolv.conf /etc/resolv.conf.$$


Unfortunately, over time that causes /etc to fill up with piles of resolv.conf files. A better way to do it would be this:

Code:
if [ -f /etc/resolv.conf.-2 ]; then mv -f /etc/resolv.conf.-2 /etc/resolv.conf.-3; fi
if [ -f /etc/resolv.conf.-1 ]; then mv -f /etc/resolv.conf.-1 /etc/resolv.conf.-2; fi
if [ -f /etc/resolv.conf    ]; then mv -f /etc/resolv.conf    /etc/resolv.conf.-1; fi


Three backups should be enough.
I will post this in the network wizard thread too.

<later>
I just noticed rc.network has this same bit of code. In other words, when booting, rc.network may create another backup resolv.conf file. This seems to be an error. rc.network should execute the files created by the network wizard, not generate more of them. The comment there said the routine setupStaticIP was a hacked version of the same routine in net-setup.sh, however it appears it was not hacked enough!

Strangely, resolv.conf does not appear to be used anywhere. Not in /etc/rc.d anyway. I wonder why we go to all the trouble of making it and backing it up, if it never gets used. Maybe it's something in the boot process that uses it. Bind?
Back to top
View user's profile Send private message 
viperpiper


Joined: 18 Dec 2008
Posts: 13

PostPosted: Fri 13 Feb 2009, 01:29    Post subject: Temp files not cleaned - causes hang after power loss  

Puppy 4.1.0-->4.1.2
Full install
Puppy will hang after power loss at "Waiting for modules to complete loading". Keyboard unresponsive.

Booting from the live CD and deleting some temp files fixes the problem.

To cope with this in the future (as this is repeatable every time I have a powerloss) I added the following to my /etc/rc.sysini script just after the line:

Code:

ln -s /proc/mounts /etc/mtab




Code:
#If we were not shutdown cleanly, try and recover
if [ -f /tmp/RUNNING ];then
 echo -n "(Cleaning up after unclean shutdown)" >/dev/console
 rm -f /var/log/X*
 rm -rf /tmp/*
 rm -f /var/lock/LCK*
 rm -f /var/run/*.pid
 rm -rf /root/tmp 2> /dev/null
 rm -rf /root/.thumbnails/* 2> /dev/null
fi

#create a file in tmp that should be deleted on a clean shutdown
echo 'this file is deleted during a clean shutdown' > /tmp/RUNNING

Back to top
View user's profile Send private message 
vtpup


Joined: 15 Oct 2008
Posts: 1077
Location: Republic of Vermont

PostPosted: Fri 13 Feb 2009, 18:14    Post subject:  

Xvidtune save bug identified and worked around:
http://www.murga-linux.com/puppy/viewtopic.php?p=274603#274603

hopeful it will translate into a fix in next version of Puppy.
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1503
Location: Maine, USA

PostPosted: Sat 17 Oct 2009, 22:53    Post subject: burniso2cd verify correction from puppy 4.3.1
Subject description: Waits additional 15 seconds before verifying
 

This correction is part of puppy 4.3.1 and is retrofitted for puppys 4.1.2 and 4.2.1. The correction eliminates bad verifies due to starting of verification before the optical drive is ready. Beware that nothing will appear to be happening for perhaps a half minute, then the drive light will indicate reading of the disk. The attached package is for puppys based on 4.1.2 only.
burniso2cd_for_P4.1.2-1.pet
Description  Retrofitted correction to the Verify portion, to delay verification until the drive
has had time to become ready.
pet

 Download 
Filename  burniso2cd_for_P4.1.2-1.pet 
Filesize  2.86 KB 
Downloaded  503 Time(s) 
Back to top
View user's profile Send private message 
rerwin


Joined: 24 Aug 2005
Posts: 1503
Location: Maine, USA

PostPosted: Sun 13 Dec 2009, 22:29    Post subject: Fix for erratic module-loading preference function
Subject description: Preferred module alternative was sometimes not loaded as specified in BootManager
 

Reports of unreliable handling of module preferences, as given in the BootManager Preference option, probably resulted from a bug in the pup_event_backend_modprobe script, which is responsible for the loading of appropriate hardware driver modules. The package, pup_event_backend_modprobe_fix_to_p41x_42x-1.pet, resolves that bug. It should be installed by anyone experiencing a problem with preferred modules not loading (e.g., atl1e instead of atl1c). The package, for both Puppy 4.1.2 and 4.2.1, can be downloaded from the 4.2 thread here:
http://www.murga-linux.com/puppy/viewtopic.php?p=371664#371664
Richard
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 3 of 3 [44 Posts]   Goto page: Previous 1, 2, 3
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Bugs ( Submit bugs )
Jump to:  

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


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0889s ][ Queries: 13 (0.0062s) ][ GZIP on ]