(old)Puppy Linux Discussion Forum

photonn wrote:Is a puppy-unleashed-core available for this release?

What about a devx?

It uses the normal devx_214.sfs. I should probably post here a dotpet with the few (minor) updates to it.

No unleashed -- that would probably require changing things on the repository, too.

Dougal wrote:As for the ub module... that's always has a big question mark next to it: it should probably be blacklisted.
ub is supposed to be a newer way of handling usb and Tempestuous said Vector was loading it for him, so I assumed it's safe to leave in...
You can always boot with "blacklist=ub", but I guess I'll blacklist it in the future.

that did the trick thanks

Caneri wrote:Is there any issue with an update from 2.14 to 2.14R that people should be aware of?

It uses 214 as the version, so won't upgrade.
You could boot it with pfix=purge, but there could be problems with some config files: I've moved all the Rox config files to their proper place ($HOME/.config/).

HairyWill wrote:I also like the fact that the default file handler for images is qiv not mtpaint, I look at images more often than I edit them.

When an image is open in qiv, you can press "1" to open it in Gqview or "2" to open it in mtpaint...

Love the revision. Fast and just works!

I have one thing that is confusing me. I'm trying use my usb wifi adapter that is a zd1211 ZyDas chip. The firmware is always under /lib/firmware/zd1211. It's not there. When I look at /lib/modules, there is a text that talks about a post-executable package for the zd1211 firmware, but I can't seem to find it? Seems to indicate I need to install the livecd to get it? Can you help with this?

Thanks for the good work.

This presents me with two dilemmae. Should I dig deep in the junk heap? Should I ask the inevitable question and risk two beautiful friendships? Answers on the proverbial postcard addressed to Father Christmas....

" Should I ask the inevitable question and risk two beautiful friendships? "

So unlike you to tread lightly.
Do what I do and just give no consideration to feelings.
Sure ... this approach is not for the faint hearted.
But as I insist on saying....if I start to be nice at this point in life....my few remaining friends will ask..."why now".

No dear Sage.....just head for the dark side now that Christmas approaches.
With indifference and attitude....we two could lead the world.

Excuse me now...I'm off to write some poisonous emails.

Regards..........Chris.

Congratulations Puppy2.14R !

I boot from CD and,

1: Selected keyboad=jp-106
2: Selected Xorg=800x600x16

and it works very lightly and I enjoy.

But at first time, I reboot/shutdown Puppy from " Menu | Shutdown | Reboot computer or Power-off computer ", no damage done. Only black screen is
there. It seems power-off.

I try again with Selected keyboad=en. The same results.

Mostly after reboot/shutdown script at first time, there will appears "Save to File | Save to CD | Don't Save".

How do I make my personal strage file ?

My PC is;
Epson Endeaver MT-3500
Celeron 533Mhz, 256MBRAM
Display Adaputor: Intel 810 Graphics Controller

Thank you.

pakt & Dougal - thankyou both for devoting some time to putting this together for us puppians..

BUT - as you are aware there are still many of us who are unfortunately still on 56k dialup speeds - so is there any possibility that you could 'package' just the changes/enhancements you incorporated into a smaller tar.bz2 or zip or pup/pet ( much similar to what WhoDo did with Ezypup ) - thus making it easier to do downloads..

I'm sure most of us who would like this "package" can do the install(s) as needed - if we have probs we can always come to this forum with our queries..

Please..

crafty.
.
.

Thanks for these improvements! I awaited them for so long ...
It boots as expected from CD, however, I can't get frugal to work ?!
rc.sysinit never gets executed; after the union thing, it said:
[...]
busybox v 1.6.1 [...]
usage: init
init is the parent of all processes. - and then nothing else happens.

Here is what I did:
- copied all files from the ISO image to /mnt/home/pup214R/
- booted with grub:
kernel (hd0,1)/pup214R/vmlinuz pmedia=idehd pdev1=hda2 psubdir=pup214R
initrd (hd0,1)/pup214R/initrd.gz

I also tried a varity of disk locations for the files but the union thing seems to happen ok anyway.

Any help appreciated!

BTW the file-searching code works amazingly fast (zdrv file in subdir is not found) and gives a very informative choice of files.

twointo1 wrote:I'm trying use my usb wifi adapter that is a zd1211 ZyDas chip. The firmware is always under /lib/firmware/zd1211. It's not there. When I look at /lib/modules, there is a text that talks about a post-executable package for the zd1211 firmware, but I can't seem to find it?

Tempestuous made us an updated zdrv, fixing some firmware problems that existed in 2.14. So the question is if the firmware is missing from the zdrv (and if so, was it missing from 2.14) or if it's just a problem with the module not being loaded.

You could have a look at /tmp/bootsysinit.log and see if there are any error messages.
I'll look into the zdrv and see if I can find something wrong there.

Sage wrote:This presents me with two dilemmae. Should I dig deep in the junk heap? Should I ask the inevitable question and risk two beautiful friendships? Answers on the proverbial postcard addressed to Father Christmas....

Ahh, I was wondering when that would come up.
Sorry to disappoint you, but that subject had to be abandoned. Believe it or not, but it seems like even old Swedes can become violent if you use the word "SCSI" on them...

You asked me to wait a little longer. Was that in 2005? Installed Sidux Lite to scsi the other day - effortless. With the combined talent of yourself and pakt, bated was my breath.....

Hello,

Dougal,

HotPup is a great tool.
I have tried it on puppy 2.17.1 and it runs fine.
On Puppy 3.01 it does not run by me.
Do you know why?

Thank your for your constant work on the Puppy project.

--
gw

Dougal wrote:Tempestuous made us an updated zdrv, fixing some firmware problems that existed in 2.14.

Ah, so the revised zdrv was used in Pup214R.

twointo1 wrote:The firmware is always under /lib/firmware/zd1211. It's not there.

I removed the unreliable zd1211rw driver and replaced it with the zd1211 and zd1211b "Vendor-based community drivers" from
http://zd1211.wiki.sourceforge.net/

These drivers have inbuilt firmware, so they don't don't need to load firmware from userspace via hotplug. Don't worry about missing Zydas firmware, it's not required.

EDIT December 17 2007
zd1211rw driver available as dotpet here http://www.murga-linux.com/puppy/viewto ... 138#161138

Just got 2.14R installed and booting on an old box (Compaq Deskpro 6350, 350 MHz PII w/ 320 MB.). Several recent Puppies didn't finish booting because of trouble with the old IDE CDROM. Two other distros worked: DSL 4.0, TinyFlux 1.0. With a full install of the latter to the hard drive, tried to do a frugal install to a puppy214 directory. The result was something I wouldn't have predicted: puppy214 was made a subdirectory of /boot/grub in hda1, with vmlinuz and initrd.gz inside. I have no idea what happened to zdrv_214R.sfs and pup_214R.sfs. I ended up copying them from the CD manually and put everything in a top level directory (psubdir=puppy214).
There were errors in the text displayed for the menu.lst entry. ex: one place had (hd,0) instead of (hd0,0)

I rewrote the menu entry as
The first time I booted through the grub menu on the hard disk the default location for the pup_save.2fs file was the base of the file system. I booted another system and moved this into /puppy214, after that it booted and saved as expected.

This is a great little system for old machines, and hotpuppy is habit forming. Fix the frugal install and it will go far.

prehistoric

tempestuous-

Thanks for your reply on the zd1211rw driver. While it may be unreliable, it worked flawlessly in the puppy versions I've been using 2.15 through 3.0

I'm using the Airlink 3055 usb adapter and it is simply not recognized in this version. I really wanted to use this version because everything else seems to just work.

Unless someone can provide a pet that will allow my adapter to function, I will miss this version.

Thanks for your time and if there is something I can do (I'm not a programmer, just a happy puppy user), I would like to have someone's help.

I'm sure that going forward, others will have this same issue.

twointo1

I can't find any reference to Airlink 3055. Do you maybe have the Airlink AWLL3025?

Well it's a very simple process to copy over the zd1211rw module plus firmware from Puppy 2.14 (or from 2.12/2.13/2.15CE/2.16)
... but before you do that, why not try the existing driver? Do this EDIT: wrong module. It should be zd1211b.

now run this command to see if a new network interface has been created - If a network interface has been created, just go ahead and use the Network Wizard.

If no success, it would be worth knowing exactly which device you have. Please post the results of this command

Sad to report real problems with FULL install. LiveCD is OK. First issue occurred when PUI tried to install GRUB. Only one choice to root??fs was offered, claiming it was 'usual' - well it isn't and it didn't work, so I used the independent GRUB installer from 3.01 into MBR and that worked. Both XVESA and Xorg caused problems I've never seen before with any version/any distro, various instabilities, black screens. Managed to find a winning combination only to find that the NIC drivers were missing, as happened with 4.0alpha. Copied the entire lib/modules file from 3.01 and that worked OK. There seem to be lots of other issues which need systematising before they merit description.
Later.

tempestuous-

Tried to modprobe zd1211 and got: FATAL no module found

I have a Airlink101 AWLL3055 id 0ace:1215 just to give you the full information.

I added a folder /lib/firmware/zd1211 and added the firmware. It still doesn't work. I don't think that there is a zd1211.ko in the kernel - could be wrong.

Thanks again

twointo1