I run many different puppies and other distros on my laptop, but FD601 just hangs - it finds and identifies the vmlinuz file, but just hangs on initrd. I downloaded Fatdog64-601-Firefox.iso from the Greek mirror and checked the md5sum (OK).
I have tried all sorts of parameters like waitdev and various pci parms but nothing happens and there are no error messages. Has anyone else encountered this?
I think it' could be a kernel problem but I have never had any kernel issues with this machine.
Through Grub I run Windows 7, Lighthouse64, Mint 11, Mint Debian, Macpup 528v2, Saluki 021, Racy puppy, which covers many kernels.
I have set up and run with no problems FD600 on my regular 64 bit desktop..
I'm stumped on this one. Any suggestions?

I use grub to boot everything, and my preferred method for adding a new distro is:
- download the .iso, check md5sum
- open the iso and copy the required files to a directory.
- Add an entry for the new distro to menu.lst
- reboot and test

I have JWM working fairly well on Fatdog 601, I like using xcompmgr (for shadowing). The last JWM snapshot that works with it for me is 523. I had to compile it myself.

I have also modified the /usr/bin/jwm_menu_create, first I removed the corner tags (line #353 and #359) and then corrected one line about #391 for the pager styles foreground (This fixes the color tag error).

Reads.

Code:

<Foreground>'${PAGERG}'</Foreground>

Should be.

Code:

<Foreground>'${PAGERFG}'</Foreground>

This fixes the errors listed with “jwm -p” in terminal.
Of coarse, you have to do a “fixmenus” in terminal and restart JWM to see changes.

I than added retrovol for a tray volume control and blinky for network monitor. Don’t start them from the Startup file. You have to start both from a Startup Command in /root/.jwm/jwmrc-personal, like so.

Starting them from there, causes no problems for Openbox, when you use it.

Of coarse, I made other personal changes to jwm_menu_create, always keeping a backup as I’d go. I also repaired some xxxx.desktop files (Categories) and renamed some, to get them to go alphabetical with the name inside.

but FD601 just hangs - it finds and identifies the vmlinuz file, but just hangs on initrd..

Since you use grub, do you ever get to see the message of initrd being loaded? If not, then like rcrsn51 said it's probably because of your laptop doesn't support big initrd.

rcrsn51 wrote:

I don't know if there is a small-initrd release for 601.

There isn't one yet, but I'll make one for the seamonkey iso.

EDIT: 601-small-initrd is now available in the mirrors:
- http://puppy-linux.org/fatdog64/ (thanks to Q5sys)
- http://www.smokey01.com/jamesbond/fatdog64/ (thanks to smokey01).

duke93535 wrote:

corrected one line about #391 for the pager styles foreground

Thank you, fixed.

duke93535 wrote:

blinky_tray-0.8.1 is from here: http://ftp.nluug.nl/ftp/pub/os/Linux/distr/fatdog/source/b/

You can also get blinky from jwm_applets pet.

smokey01 wrote:

Has anyone managed to compile the latest Filezilla for Fatdog-601?

It needs xwWidgets to be installed. So when I try to compile that I get more problems.

I haven't tried that. Did you use the wxWidgets from the package repo, or did you roll up your own?_________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.Last edited by jamesbond on Sat 28 Jul 2012, 09:42; edited 1 time in total

I then tried the ones in the repo but had no luck either. When compiling filezilla during the ./configure process the xwwidgets could not be found after both pets were installed.

Ah, I see. That's because FileZilla requires that wxWidgets is compiled with unicode, the one in the repo isn't.

DC wrote:

Whilst testing DVB with my old twinhan I found the file "dvb-usb-dibusb-5.0.0.11.fw" was missing. I'd just like to know was it left out / old /not required etc.

Not sure. Linux-firmware doesn't seem to have a copy of that file anymore. Does your DVB work without it? If not, I'll try to find that in my old copy of 511, or better yet, send me that file and I'll put it in. If you do, tell me which directory I need to put it in, too. Thanks.

rcrsn51 wrote:

I wonder if memdisk is less demanding. I believe that this is a fairly new feature in syslinux.

Yes, because when it loads stuff to memory it can assure that they are all contiguous. Glad to see it work.

Fishy wrote:

Wondering if there is an up-dated transmission compatible with the over-sized dog?

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