WakePup2 for Puppy 2.x and greater (NOW WITH more SUPPORT)

Using applications, configuring, problems
Message
Author
PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#31 Post by PaulBx1 »

I posted a candidate fix for my hang issue on the 217B thread, but was not able to test it because of other issues I don't understand. Maybe the old edit-initrd script I have is out of date. John, how do you edit an initrd.gz?

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#32 Post by John Doe »

Here give this one a try with RC1

*edit- deleted attachment, nevermind my initrd.gz didn't work.

BK is going to have to do it.

he could just post the new initrd.gz for you to test since you are using USB and Floppy.

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#33 Post by John Doe »

John Doe wrote:BK is going to have to do it.
actually, now that unleashed 2.17 is out i can do it.

give this one a test (it's 2.17 final).
Last edited by John Doe on Sat 21 Jul 2007, 05:19, edited 1 time in total.

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#34 Post by John Doe »

just wanted to mention i checked with that code and was able to boot in all manners i've previous attempted over here.

no adverse effects to current function.

if it works over there, it's golden.

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#35 Post by PaulBx1 »

I booted with it, and it worked no differently. I then looked at /initrd/sbin/init and found that usbstoragecompletionfunc was the standard one, not the one that I modified. So it looks like this is the same initrd.gz as the standard one. :)

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#36 Post by John Doe »

I edited the wrong init in initrd-tree. There used to be a symlink in the root and now it's a file. I thought they moved it and edited the wrong one (it didn't even make it into the image, but the bakup i made did).

I edited the attachment above, please try again.

I'll have to redo my testing now also :roll:

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#37 Post by PaulBx1 »

OK, with the new initrd.gz it does timeout properly in 50 sec (printing out 1 2 3 4... as it goes). Of course shortly afterward it dumps me at the command promt, saying something about gurus being able to troubleshoot. It also said it found no usb devices.

So anyway, I think that rearrangement of usbstoragecompletionfunc is correct.

As to what's wrong with the wakepup2? I think it needs also the boot parameter "pfix=usbcard". When I boot from CD and use "puppy pfix=usbcard pmedia=usbflash", it does boot up properly (that's how I'm booted now). Wakepup2 does detect the device when it is out on the pcmcia card. Is there a way for it to know that the USB where the device is, is generated from a pcmcia card?

Another thing you could do, if the above is not possible, is just allow the user to tack on a parameter manually. Another menu entry would do it. That's not as user-friendly, of course.

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#38 Post by John Doe »

update is here:

http://www.murga-linux.com/puppy/viewto ... 924#122924
PaulBx1 wrote:So anyway, I think that rearrangement of usbstoragecompletionfunc is correct.
cool. did a couple tests here and all looks well so far.
PaulBx1 wrote:As to what's wrong with the wakepup2? I think it needs also the boot parameter "pfix=usbcard".
JD: *slaps self on forehead*!

i've only seen that on the screen about 40000 times in the past year, thanks for making the connection...

i added an item under custom at the end after the first pfix dialog to turn that on. it plays nice with the previous dialog.

thanks for rounding this off with me for everyone.

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#39 Post by PaulBx1 »

John, your md5sum there is wrong.

I take it, from the way you described the implementation, that there is no way for the program to automatically put that boot parameter in if the device is on a pcmcia card. Too bad...

For what it's worth, that rearrangement of the usbstoragecompletionfunc has the effect of reducing the timeout by one second. No big deal when invoked with a 50-sec timeout, but when called with smaller timeouts the reduction may become significant. So, the calls of this routine should be examined to see if you want to boost the timeout parameter.

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#40 Post by PaulBx1 »

John, any update on this?

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#41 Post by John Doe »

thanks for the bump, sorry on the delay.
PaulBx1 wrote:John, your md5sum there is wrong.
thanks. try again (it's updated). i got burnt out and frustrated on it so i went out and picked some mushrooms and got a fishing license to clear my head.
PaulBx1 wrote:For what it's worth, that rearrangement of the usbstoragecompletionfunc...
thanks (i'll have to actually look at it sometime). i just tested for problems on my machine configurations and didnt' find any.

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#42 Post by John Doe »

PaulBx1 wrote:I take it, from the way you described the implementation, that there is no way for the program to automatically put that boot parameter in if the device is on a pcmcia card. Too bad...
perhaps i explained wrong or didn't understand my options at the time.

it should work now for anyone...

one must use "Custom" under 'boot mode'. assuming that usbflash is chosen for the user as "Boot Media". one may need to select 6 first to change the "Boot Media" and then choose "Custom" under 'boot mode'.

let me know how it goes.

PaulBx1
Posts: 2312
Joined: Sat 17 Jun 2006, 03:11
Location: Wyoming, USA

#43 Post by PaulBx1 »

Didn't work.

My flash boots fine on the 1.1 port using "Normal". When I plug it into the 2.0 port on the card, it doesn't matter if I use "Normal", or "Custom" with the usbcard parameter; the result is the same. It prints out "Kernel command line:", prints out the line it's going to use, then hangs there with the flash drive being accessed forever (flashing LED). Adding all the debug switches doesn't add any more info.

The md5sum checks out now, for what it's worth.

Sorry John.

BTW if I were you I'd put the question about the usbcard earlier than the debug questions, so it is in line with all those other questions such as apic. In fact I wonder if it can be combined with the "nopcmcia" question? I.e., "1=Normal (load pcmcia drivers, no pfix=usbcard switch", "2=nopcmcia (load no pcmcia drivers, no pfix=usbcard switch", "3=usbcard (load pcmcia drivers, pfix=usbcard" with a note explaining the distinction between the two (which to be honest, I don't understand either!) Just a suggestion...

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#44 Post by John Doe »

i'm going to try and wrap this up tomorrow afternoon.

i think i need to dig up a new floppy and start over, as it seems i corrupted a driver along the way with a bad read or something.

Philh
Posts: 150
Joined: Wed 17 May 2006, 13:26
Location: England

#45 Post by Philh »

Some more info
I just tried out a usbhd (usb to ide) on a usb1 port, and it hangs
loading Adaptec v4.01b ASPI disk driver.
But if I comment out the device=A:\driver\usb\USBASPI.SYS /v
leaving aspiuhci.sys in
then it boots up ok.

User avatar
Crash
Posts: 453
Joined: Fri 09 Dec 2005, 06:34
Location: Melbourne, FL

#46 Post by Crash »

First, let me state that I really like this version of Wakepup2. It offers a nice set of options.

I made a couple of additions to the opening menu of the AUTOEXEC.BAT file, adding options 7 and 8:

...

echo * 7. Floppy File: Executes last saved boot config from floppy *
echo * *
echo * 8. Target File: Executes last saved boot config from target media*
echo * *

...

choice /C:12345678 Please choose :

...

if "%errorlevel%"=="7" goto load
if "%errorlevel%"=="8" goto load2

...

:load2
LINLD.COM image=%drv%\vmlinuz initrd=%drv%\initrd.gz cl=@%drv%\linld\puppy.lin

goto end

...

If you have a particular setup that you tried that works good, you don't have to remember it. Just type option 7 and it runs your last saved configuration.

You can copy the a:\linld directory to the target device and run it from there when you use option 8.

Ulterior motive: Option 8 works on a floppy image burned to a CD. I can experiment with the best configuration on floppy, copy it to the USB stick, and carry it around along with the boot CD for the poor souls who won't retrofit their computer with a floppy drive.

---

P.S. (Edited August 1):

Philh: Like you, one of the computers I tried would lock up on the USBASPI.SYS driver but work OK with aspiuhci.sys. Another computer that locked up on the USBASPI.SYS driver didn't work with aspiuhci.sys but worked OK with version 2.06 of USBASPI.SYS. Unfortunately, there doesn't seem to be a combination that works on all computers. I consider this a DOS USB support issue rather than a Puppy issue, but it is an issue none the less.

I attached my edits to the autoexec.bat file here since I don't know if my excerpts above are very clear.

---

(Edited August 3): The writeup and attachment was revised to reflect the current new Wakepup2 configuration.
Attachments
autoexec.bat.gz
(3.01 KiB) Downloaded 668 times
Last edited by Crash on Fri 03 Aug 2007, 12:58, edited 2 times in total.

jonyo

#47 Post by jonyo »

Thought I might ask this question here. Have an ibm 380 ed lap P150 32 megs a ram that I'm playing with to run pup. 'Cording to the lenovo site it is non cd bootable.

Stumbled on that it booted a win 98 cd. Ended up trying out gparted that booted. Tried out a bunch a pup vers & no luck. Tried out a wake floppy with a buncha pup vers & no luck with that. Thought at first it wasn't recognizing the cd drive or something..

All of a sudden the wake floppy (outa 2.17) booted pup vers 2.01. So wonderin why it booted 2.01 & not the other 2x variants?

Also didn't boot micro muppy(based on 2.12 i think).
Last edited by jonyo on Wed 08 Aug 2007, 10:15, edited 1 time in total.

j-impossiblix
Posts: 7
Joined: Fri 27 Jul 2007, 22:02

#48 Post by j-impossiblix »

wake pup works for me. it's great for those times that my intermittant cd drive is down, or overheated....

works for 2.17, not sure wake pup version...@ work...

wondering how it works, and how come this is the only distro that can use a floppy to help boot.

others say that since kernel 2.6.... is over 1.44 mb it won't work on a boot floppy, but i think that even tho pup is using 2.4.... and is less than 1.44, am i right that the kernel isn't on the disk anyway?

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#49 Post by John Doe »

Thanks Crash, jonyo, and j-impossiblix for jumping in.

really dig 7 and 8, great ideas (8 I will have to look at a bit, but I think I get it). will implement that this week and fix up the main image.

going to add "pfix=noswap" also (if Barry likes it and plans on inclusion for 2.18). <- that's an eight if you have smiley's enabled (stupid regex).

http://www.murga-linux.com/puppy/viewto ... 583#133583

John Doe
Posts: 1681
Joined: Mon 01 Aug 2005, 04:46
Location: Michigan, US

#50 Post by John Doe »

j-impossiblix wrote:wondering how it works...
i'll try to give an quick run down.

the mbr on the floppy gets hit and the bios boots it.
config.sys is loaded and all DOS drivers are loaded in there.
autoexec.bat is next. it has the logic to find puppy and decide what is pasted to linld.
linld is a dos app that will boot a kernel image from DOS.
we use the menu system in order to write the config file for overcomeing the commandline limitations in freedos (we are using freedos not MS-DOS).
j-impossiblix wrote:...and how come this is the only distro that can use a floppy to help boot.
is it really? i'm ignorant, so i must defer this back the group.

@all
is puppy really the only disto (or liveCD) that can use a floppy (GRUP floppy excluded, that wouldn't be any fun)?

Post Reply