Wakepup2 Aug 2008 - floppy image for booting from USB

[Crash]

do you put wakepuppy on a boot floppy, or does putting it on the floppy make it bootable? Some of the posts in this thread seem to imply that wakepuppy does everything you need to boot, but nobody ever says so.

Wakepup2 is a bootable floppy disk image using FreeDOS. It is meant to work stand-alone without need for any other pre-prepared disk.

What does Autoexec.bat does not contain label 'writeoption' mean anyway!?!?

Interesting bug. Which version of Wakepup2 are you using? There is a label in the autoexec.bat file called "writeoptions" with an "s" at the end. The error you see indicates there is a problem with the code in that area.

I was planning to install Puppy on a thumb drive and have a floppy with wakepuppy for PCs that can't boot off a USB drive, but it looks like that won't work.

It should work OK. I have booted USB flash drives in about a dozen computers using Wakepup2 with excellent results. It also works fine booting to SD cards or CF cards when they are inserted into a USB media adapter.

///

The latest version of Wakepup2, dated Sept. 16 2008, is at:

http://www.murga-linux.com/puppy/viewtopic.php?t=33551

This is the version that I prefer people to download and give feedback on.

///

[pistoi0]

I am the one who successfully booted a frugal install off a USB key, using a PCMCIA device(s). Both are USB 2.0s, an Adaptec 1440 USB card and a generic USB card bus.

I did retract the anouncement of success because I couldn't reboot after making successful boots on a series of Pups, including 2, 3, and 4 series -- and on several different USB drives.

Well, lo and behold. I tried both the August effort and the most recent Sept. 14 edition by the persevering Crash. They, too, booted successfully, including (MU's latest Minissys 84F). However, I had the same result when I attempted a reboot with a .2fs save file. My conclusion is that Wakepup2 will boot from a PCMCIA device. --BUT it will not reboot with a pup_save.2fs. That is when I get the error pup_save xxx.2fs not found, just as Otropogo and others have reported. Go figure.

Meanwhile, I have been booting a USB drive in the native USB port using Wakepup2 since this past June.

I should mention again that I am using Wakepup2 on an AST Asentia M, 166mmx, 128 RAM, no HD or CDROM.

[otropogo]

I am the one who successfully booted a frugal install off a USB key, using a PCMCIA device(s). Both are USB 2.0s, an Adaptec 1440 USB card and a generic USB card bus.

I'm a bit confused by your report. and I'm not familar with the Adaptec 1440 Card. Are you using a USB key in a USB adapter in a cardbus pcmcia socket, or what, where, exactly?

When you say cardbus, do you mean a 32-bit pcmcia socket?

...My conclusion is that Wakepup2 will boot from a PCMCIA device. --BUT it will not reboot with a pup_save.2fs. That is when I get the error pup_save xxx.2fs not found, just as Otropogo and others have reported. Go figure.

No, that's not quite right. You say you can consistently load and run the Puppy sfs file from a pcmcia socket.

I've never been able to load Puppy from pcmcia or pcmcia_scsi. And I've never gotten beyond the message saying the the "...sfs" file (NOT the 2fs) could not be found

I've booted every Wakepup since v. 1.1 with a CF card loaded with Puppy in my laptop's pcmcia slot. Puppy has never even been detected in my pcmcia slots by Wakepup , never mind loading it.

Either the difference is due to your having 32-bit cardbus, as opposed to my 16-bit pcmcia sockets, or you have a superior technique for using wakepup.

[otropogo]

@ Crash

Have a look at this new thread.

http://www.murga-linux.com/puppy/postin ... e&p=233245

Apparently, here is someone with a BOOTABLE pcmcia slot, which gets him to exactly to the same spot that I arrive at on a bootable SCSI drive or, with the help of Wakepup, on the Parallel Zip and the LiveCd on pcmcia_scsi:

Code: Select all

Pup_400.sfs not found

Which makes Pistoi0's success in loading Puppy from pcmcia with Wakepup all the more remarkable.

[cromabianca]

Interesting bug. Which version of Wakepup2 are you using? There is a label in the autoexec.bat file called "writeoptions" with an "s" at the end. The error you see indicates there is a problem with the code in that area.

The latest version of Wakepup2, dated Sept. 16 2008, is at:

http://www.murga-linux.com/puppy/viewtopic.php?t=33551

This is the version that I prefer people to download and give feedback on.

Sure.

My version of Wakepup2 is the 16 sept. one.

Here's the procedure I follow.

1) Bot from Wakepup2 from floppy

2) At first choice menu I chose: 4. Addonics (or similar)...

3) My PCMCIA CD-ROM starts spinning (it's a Toshiba, it came with the laptop, an od 7020ct portege)

4) Freedos says: ...file found on idecd, drive W: (that's my Puppy Linux 4.0 "Dingo" live CD)

5) At second choice menu, i chose: 1. Normal Boot

6) Here I have the problem, freedos answers: Batchfile 'A:/AUTOEXEC.BAT' does not contain label 'writeoptions' (I dont't know where to find the backslash on my Mac... In my last post I did a typo: IT SAYS infact writeoptions, with an 's' )

7) The prompt A:> apperas (from there I can actually access my CD-ROM, by typing W:)

Very same thing happens when I try to boot from USB Pen (in first menu I make choice 1, instead of 4)

Here's excerpts from my autoexec.bat...

Code: Select all

@echo off
rem September 16, 2008
rem wakepup2 0.2 (C) 2006, Paul Akterstam ('pakt' on Puppy Linux Forum)
...
...
...

echo ...file found on %media%, drive %drv%
echo.
echo *********************************************************************
echo *                     Select Puppy2 Boot Mode                       *
echo *********************************************************************
echo *  1. Normal       Normal Boot                                      *
echo *                                                                   *
echo *  2. Ram/NoX      Normal Boot with pfix=ram,nox                    *
echo *                                                                   *
echo *  3. Custom       Set custom boot options
...
...
...

echo.
choice /C:123456789 Please choose :
if "%errorlevel%"=="1" goto writeoptions
if "%errorlevel%"=="2" set pfix=pfix=ram,nox
...
...
...


:writeoptions

del linld\puppy.lin

echo root=/dev/ram0 >> linld\puppy.lin
echo PMEDIA=%media% >>  linld\puppy.lin
if not "%acpi%"=="" echo %acpi% >> linld\puppy.lin
if not "%pfix%"=="" echo %pfix% >> linld\puppy.lin
if not "%vga%"=="" echo %vga% >> linld\puppy.lin
if not "%apm%"=="" echo %apm% >> linld\puppy.lin
if not "%noapic%"=="" echo %noapic% >> linld\puppy.lin
if not "%ide%"=="" echo %ide% >> linld\puppy.lin
if not "%nopcmcia%"=="" echo %nopcmcia% >> linld\puppy.lin
if not "%loglevel%"=="" echo %loglevel% >> linld\puppy.lin
if not "%usrinput2%"=="" echo psubdir=%usrinput2% >> linld\puppy.lin
if not "%nosmp%"=="" echo %nosmp% >> linld\puppy.lin

:load
LINLD.COM image...... ... ... 
...
...

[Keef]

@ otropogo
I'm not sure of the kernels, but the current Pup I have on the USB stick is MeanPup, based on 2.02. I've also succeeded with 2.14R, Fatfree 3.01, and several variants of the 4 series - SkinnyPup 4.0 is ok for instance. Can't think of any particular problems. Muppy-mini also boots but is a tad slow on a 366mhz CPU and 192mb RAM. Might be easier to find the ones that don't boot , so I'll experiment with a spare memory stick.

@Crash
I tried the latest version of Wakepup2 and unfortunately it would not work with my existing setup (see above) that is known to succeed with previous versions (original and August revisions are ok).
For some reason it seems to be reading the USBFLASH marker as USBCD, and tells me the (usdcd) device cannot be found. Weird. Tried it again with older version of WakePup and it worked, so the setup is not corrupted.

[Crash]

cromabianca:

Indeed puzzling, and the first person to report results of testing on the Addonics path. The autoexec.bat code doesn't look corrupted. Have previous versions of Wakepup worked for you? Also, have you gotten the message "file found on idecd, drive W:" with any previous versions?

It is good that you can access the CD ROM. Possibly you can get it to boot by typing something like this from the A: drive:

Code: Select all

LINLD.COM image=W:\vmlinuz initrd=W:\initrd.gz "cl=root=/dev/ram0 PMEDIA=idecd"

................

I tried the latest version of Wakepup2 and unfortunately it would not work with my existing setup (see above) that is known to succeed with previous versions (original and August revisions are ok).

There is a test file on page 2 of this post that has an image called "wp2test1.img". Does it work? This will tell whether the problem is in modifications to config.sys/autoexec.bat or if the problem is with with other files that I changed. Also, have you tried both option 1 and 2 with the September 16 version?

///

oops... wrong person quoted. Sorry. Got it right now...

///

[cromabianca]

cromabianca:

Indeed puzzling, and the first person to report results of testing on the Addonics path. The autoexec.bat code doesn't look corrupted. Have previous versions of Wakepup worked for you? Also, have you gotten the message "file found on idecd, drive W:" with any previous versions?

It is good that you can access the CD ROM. Possibly you can get it to boot by typing something like this from the A: drive:

Code: Select all

LINLD.COM image=W:\vmlinuz initrd=W:\initrd.gz "cl=root=/dev/ram0 PMEDIA=idecd"

No, I didn't try any of the previuos version... I'll do it, though.

I did try loading using loadlin.com ad this is what hapened.

I inserted the code and loaded the kernel, then...


Loading kernel drivers needed to access disk drives... done
Searching for Puppy files in computer disk drives...pup_400.sfs not found. Dropping out to initial-ramdisk console...
/din/sh: can't access tty; job control turned off
#


That's it.

Now I'm gonna try the older versions of wakepup....

[cromabianca]

IT WORKED, IT WORKED, IT WORKED!!!!!!

Puppy Linux 4.0 "Dingo" running on my Toshiba Portege 7020ct (2001) Laptop!

I just needed the loader to find pup_400.sfs file, so I inserted my pendrive in USB ad that did the trick!!!

man, that WAS something!!!



I'm happier than a tornado in a trailer park!!!!

[Keef]

I'll try and make my last post a bit more useful....
The USB stick boots successfully with previous WakePups, using the Iomega drivers (option 6, or option 2)

The error using the most recent version is as follows:

Registering unionfs 20060503-0400
fuse init (API version 7.6)
ERROR, cannot find Puppy on usbcd boot media
PUPMODE=1 PDEV=
Exited to initial ramdisk command line...

After trying this again a few times, I have noticed that
'Kernel command line' contains:
PMEDIA=usbcd pfix=nox,usbcard apm=on log level 7
(This just flashes by, so I'm relying on memory and dodgy handwriting)

Using the older WakePups it has PMEDIA=usbflash, and none of the other stuff, I think.

@Crash
Sorry, missed your reply above, what with not being sideburns!!. I will try your suggestions.

***
wp2test1.img - yes this works. Used option 6, so I assume Option 2 works (got summoned away before I could try).
I haven't had much success with option 1 in any version

[Crash]

wp2test1.img - yes this works. Used option 6, so I assume Option 2 works

Thanks. That narrows the problem down considerably. It will still take a while for me to find out what is going on. I was hoping the Sept 16 version would be good to go, but such is life. I'll probably post something like a "wp2test2" image on this thread after I figure things out.

I've just received a cheapo PCMCIA CF card adapter, and I'm going to see if I can get any joy from that (seems highly unlikely, going by what's been said so far...)

If you try PCMCIA with a CF card adapter, you might try the Puppy 4.1 Beta version. I had my first CF/PCMCIA success today using it. I posted the description in the Bugs - Puppy 4.1 Beta thread. The particular laptop computer I used is pretty stubborn and never has worked with PCMCIA and Wakepup/DOS, so I had to do a brute force floppy boot method. Maybe Wakepup will work for yours. I like the idea of just pushing a CF card into a $10 PCMCIA adapter.

/// Edited Sep 21

Update: After a closer look at the September 16 wakepup2.img file, the probable culprit is that autoexec.bat resides at the far end of the floppy. Floppies are notoriously unreliable in that area. I need to break out my old Norton Utilities disk to verify, but I think some physical cleanup of the files in the image will fix things. I welcome others to play with the image and give feedback. It's a great learning experience.

///

[Jesse]

...
From your fully working setup you can use the steps below to figure out what drivers are needed.
This mut2 command (below) will get mut to tell you what is on the PCI bus, and what drivers are loaded there, here you should see your PCMCIA device (probably not the plug in cards themselves). It'll advise what it reckons the drivers and driver dependancies are.

Code: Select all

/usr/sbin/mut probepci --list -d -b

Afraid not.

This command opens the MUT Window but returns no information in the console. In fact, the console hangs...

Oh dear, sounds like its the older 0.1.1 version of mut that you have. Here is the download link for version 2.
http://www.murga-linux.com/puppy/viewtopic.php?t=32028

I don't think any drivers are needed to support the CF adapter and card other than those enabling pcmcia support itself.

My understanding of PCMCIA is that each PCMCIA device driver is its own entity, meaning that if you don't have the precise driver loaded for that PCMCIA port, you cannot determine anything about what is plugged in other than a chip id, so even your CF adapter needs a specific driver. Possibly you need the yenta_socket kernel driver (and its dependancy). But hopefully mut2 will be able to let you know what is needed.

Jesse

[otropogo]

...sounds like its the older 0.1.1 version of mut that you have. Here is the download link for version 2.
http://www.murga-linux.com/puppy/viewtopic.php?t=32028
...
Jesse

Thanks. I've downloaded it, but how do I install it? And will it work in Puppy 3.01 Retro?

Update: I ran the command again today, and this time I got a response:

bash: /usr/bin/mut: no such file or directory

There is however a program called Mtools, so I substituted that for mut, and got a list of "supported commands"

[Jesse]

...sounds like its the older 0.1.1 version of mut that you have. Here is the download link for version 2.
http://www.murga-linux.com/puppy/viewtopic.php?t=32028
...
Jesse

Thanks. I've downloaded it, but how do I install it?

It is a program that breaks a few Linux notions, it doesn't really install anywhere, or if you like, it installs into memory, it is a disk info service daemon, and that is accessed via command line from the mut binary, which can go anywhere you like, /temp if you just want to try it out. It has had a traditional location of /usr/bin/mut/ in Puppy Linux.
The mut binary is designed to be helpful by letting you know about the command line options when passing --help as a command line option.

And will it work in Puppy 3.01 Retro?

A good question! Um, it may crash if the glibc is version 2.4 or earlier, and I think that is all puppy editions earlier than 4.0. However if it is statically linked with a good glibc it can run fine in almost any Linux. Its just that the static link adds about 600-700Kb to the mut executable. That potential to crash is on the fork() call, and I don't think that is invoked for the probepci command that I reccomended, but it will be for virtually any other command to mut2.
I can whip up a static build for you if you like?

Update: I ran the command again today, and this time I got a response:

bash: /usr/bin/mut: no such file or directory

There is however a program called Mtools, so I substituted that for mut, and got a list of "supported commands"

From memory mtools is a dos/fat/fat32 utilities program, its nothing to do with mut.
Jesse

[otropogo]

...sounds like its the older 0.1.1 version of mut that you have. Here is the download link for version 2.
http://www.murga-linux.com/puppy/viewtopic.php?t=32028
...
Jesse

Thanks. I've downloaded it, but how do I install it?

...
It is a program that breaks a few Linux notions, it doesn't really install anywhere, or if you like, it installs into memory, it is a disk info service daemon, and that is accessed via command line from the mut binary, which can go anywhere you like, /temp if you just want to try it out. It has had a traditional location of /usr/bin/mut/ in Puppy Linux.

....

Jesse

OK. So, should I just create the folder "mut" in /usr/bin/ and extract the archive into that folder, then run the command?

[Jesse]

OK. So, should I just create the folder "mut" in /usr/bin/ and extract the archive into that folder, then run the command?

Personally I'd just use /temp and see if mut can be of use so that you will then see if you want to keep it around in a permanent directory. If there is something already in /usr/bin/mut it'll be the older version and you may not want to overwrite that just yet, if there is nothing at /usr/bin/mut then feel free to install it there.

Jesse

[otropogo]

... I'd just use /temp and see if mut can be of use so that you will then see if you want to keep it around in a permanent directory. If there is something already in /usr/bin/mut it'll be the older version and you may not want to overwrite that just yet, if there is nothing at /usr/bin/mut then feel free to install it there.

Jesse

There's no mut in /usr/bin, but Mut 1.1 is on the system. I decided to run it from a flash card first, and it seems to work. Here's the output:

# /mnt/hdc1/mut probepci --list -d -b
# module_dir=/lib/modules/2.6.18.1/
# proc_dir=/proc
# filter=*.*
# -d=1 -i=0 -b=1 -l=1
00:13.1 060700 1180:0476 BRIDGE.CARDBUS <yenta_cardbus> (yenta_socket)
00:13.0 060700 1180:0476 BRIDGE.CARDBUS <yenta_cardbus> (yenta_socket)
00:02.0 030000 10C8:0003 DISPLAY.VGA <> ()
00:01.3 068000 8086:7113 BRIDGE.OTHER <piix4_smbus> (i2c-piix4)
00:01.2 0C0300 8086:7112 SERIAL.USB <> (uhci-hcd)
00:01.1 010180 8086:7111 STORAGE.EIDE <PIIX_IDE> ()
00:01.0 060100 8086:7110 BRIDGE.ISA <> ()
00:00.0 060000 8086:7100 BRIDGE.HOST <> ()
# driver is loaded yenta_cardbus
# driver is loaded yenta_cardbus
# driver is loaded piix4_smbus
# driver is loaded PIIX_IDE
# driver uhci-hcd
#already loaded driver: uhci-hcd

[Jesse]

Hi otropogo,

Here mut2 shows your pcmcia port(s), each has an entry on the PCI bus.

00:13.1 060700 1180:0476 BRIDGE.CARDBUS <yenta_cardbus> (yenta_socket)
00:13.0 060700 1180:0476 BRIDGE.CARDBUS <yenta_cardbus> (yenta_socket)

The driver name in the angle brackets <yenta_cardbus> is the name of the driver (that the driver itself reports) that has attached itself to the PCI bus. The list of drivers that also might work is the last item (yenta_socket), the list is generated from /lib/modules/(kernel version)/modules.pcimap

I had a look and I don't see a driver called "yenta_cardbus", but it looks like the driver is called "yenta_socket".

The yenta_socket has one dependancy, rsrc_nonstatic.

/lib/modules/2.6.25.16/modules.dep:/lib/modules/2.6.25.16/initrd/kernel/drivers/pcmcia/yenta_socket.ko.gz: /lib/modules/2.6.25.16/initrd/kernel/drivers/pcmcia/rsrc_nonstatic.ko.gz


Actually this is ringing some bells.
yenta_socket and rsrc_nonstatic can be loaded in the initrd, and have been for quite a few puppy editions, I think there is some boot option to get it going, um... pfix=pcmcia or pfix=cardbus something like that from memory.

Heres some people with similar problem and potential fixes fix:
http://www.murga-linux.com/puppy/viewtopic.php?p=213637

There are a lot of results to this google search:
pfix pcmcia site:www.murga-linux.com/
And its a lot faster than using the forum search function.

Regards
Jesse

[otropogo]

Hi otropogo,

Here mut2 shows your pcmcia port(s), each has an entry on the PCI bus.

00:13.1 060700 1180:0476 BRIDGE.CARDBUS <yenta_cardbus> (yenta_socket)
00:13.0 060700 1180:0476 BRIDGE.CARDBUS <yenta_cardbus> (yenta_socket)

The driver name in the angle brackets <yenta_cardbus> is the name of the driver (that the driver itself reports) that has attached itself to the PCI bus. The list of drivers that also might work is the last item (yenta_socket), the list is generated from /lib/modules/(kernel version)/modules.pcimap

I had a look and I don't see a driver called "yenta_cardbus", but it looks like the driver is called "yenta_socket".

The yenta_socket has one dependancy, rsrc_nonstatic.

/lib/modules/2.6.25.16/modules.dep:/lib/modules/2.6.25.16/initrd/kernel/drivers/pcmcia/yenta_socket.ko.gz: /lib/modules/2.6.25.16/initrd/kernel/drivers/pcmcia/rsrc_nonstatic.ko.gz

Jesse, while I appreciate your effort, I'm very much afraid this information requires more than my very limited understanding of Linux to apply.

I would note, however, that the Puppy 3.01 Retro, which generated my probe results, runs with Linux Kernel 2.6.18, whereras the modules you cite above are for Kernel 2.6.25.

Heres some people with similar problem and potential fixes fix:
http://www.murga-linux.com/puppy/viewtopic.php?p=213637

Had a look, but not obviously related to my situation, since they're working on USB, while I'm stuck with 16-bit pcmcia. There's also only been one post since July...

There are a lot of results to this google search:
pfix pcmcia site:www.murga-linux.com/

Thanks for the tip, will have a look later,.

[Jesse]

Jesse, while I appreciate your effort, I'm very much afraid this information requires more than my very limited understanding of Linux to apply.

I would note, however, that the Puppy 3.01 Retro, which generated my probe results, runs with Linux Kernel 2.6.18, whereras the modules you cite above are for Kernel 2.6.25.

Hi otropogo,
Ok, actually that makes things a bit simpler. I have Puppy (2.13) as my main system, which is using a 2.6.18.1 Kernel. The driver names and dependancies havn't changed for yenta_socket and rsrc_nonstatic.
I had a look at the Puppy Linux boot hints (more /initrd/sbin/init) and the Puppy Linux boot hint 'pfix' has this option for booting, relevant to pcmcia:

usbcard) USBCARD="yes";; #boot from pcmcia drive.

So all you really need to do is use a text editor and add "pfix=usbcard" into your kernel boot parameters.

I know that it says 'usb', but your card might have usb internally and just not advertise that fact.

Ok, so, how to setup your kernel boot parameters?

If you've got a file called syslinux.cfg in the root directory.
The contents may be:
default vmlinuz initrd=initrd.gz pmedia=usbflash
Change to:
default vmlinuz initrd=initrd.gz pmedia=usbflash pfix=usbcard

If you're using GRUB, open up the (HD)/boot/grub/menu.lst file:
You may have an entry like this:

title Puppy-4.1 beta (408) pfix=ram (NEW)
rootnoverify (hd0,2)
kernel /408/vmlinuz root=/dev/ram0 ro vga=normal pfix=ram psubdir=408
initrd /408/initrd.gz

Change to:

title Puppy-4.1 beta (408) pfix=ram (NEW)
rootnoverify (hd0,2)
kernel /408/vmlinuz root=/dev/ram0 ro vga=normal pfix=usbcard,ram psubdir=408
initrd /408/initrd.gz

The basic idea is to find the boot config file and the kernel load line and add in pfix=usbcard. Its usually a small file, less than 1000 bytes or so. The kernel file is usually called 'vmlinuz' with Puppy Linux.

Okies, best of luck in getting it going.

Regards
Jesse