Fatdog64-510

[Sage]

Thanks jb. Maybe I should stick to watching the cricket? On the other hand...

[jamesbond]

Thanks jb. Maybe I should stick to watching the cricket? On the other hand...

Sorry Sage, there isn't much I can do. If you don't mind, and if you have any spare harddisk, do you mind trying this:
a) Boot with 510 LiveCD
b) Use Gparted and wipe off everything
c) Inside Gparted, create a new disk label (type=msdos)
d) Create a new partition - single partition, say with ext3. Remember to turn on the boot flags
e) Install Fatdog full install with the original unmodified installer
f) After installation, run and Grub4dos installer. No modification of menu.lst is necessary.
g) just before you shutdown, do this - mount the newly installed partition (it should be in /mnt/sda1)
h) the in terminal do this:

Code: Select all

cd /mnt/sda1 
ln -s lib lib64

The last line is "LN -S LIB LIB64" all in small case.
i) Then do the chroot test:

Code: Select all

chroot /mnt/sda1 /bin/busybox

j) If it's successful (ie no error message), try booting from the harddisk. If you still get the same error during chroot test, then forget it.
Sorry this is the same steps you would probably have done a couple of hundred times already, but let's just start again from blank slate to in case one of us miss anything.
If you decide to do this instead of watching cricket, let me know. If you feel this is pointless, well, you'll probably be right.

cheers!

[Sage]

Sorry, jb, I just sent you a tar file of the HD I used to successfully install a FRUGAL ! Ignore it ! I will process your further suggestions after a chicken masala lunch break. I may be gone some time....

UPDATE:
Refreshed and refuelled, I have some excellent news for you, jb.
Strange as it is to use an M$-anything, your ploy worked. I got the full busybox read-out and a complete boot up.

Looks as if the fault lies somewhere in the regular fs/legacyGRUB/install routine?

Over to you, with grateful thanks.

[tommy]

Today I have given a try to this Fatdog 510 on a bootable usb stick and got success on my Toshiba Satellite L350d - Amd X2 dual core 2.1GHz 64bit with Ati graphics. It booted in 20 seconds, it automagically recognised the video card using native 1280x800 resolution (Puppy 4.1 - 4.2 - 4.3 never succeeded in this , falling at 1024x768 pixel). Everything works, from audio to dual core, to Atheros wifi (ath5k module). Even the inbuilt webcam (Chicony ) works well. The only problem is the touchpad, it works but the mouse cursor speed is really below normal, going from a corner of the video to the opposite one takes about one minute and a lot of rubbing. I tried to setup - mouse - speed and threshold, restarted X but no go.

I will test the video application further, to see how speedy is converting video formats etc on a 64bit system he he.

I hope to find in future more 64bit .pets to feed this fat dog a lot more.

Nice job!!

[kirk]

Is this PET to be added to my running system?

Boot pfix=ram and try it.

Just a note: When adding the updated Seamonkey browser to the PPM, INSURE that you get the 64bit version (available as a stable or the beta versions).

I'll compile it from source whenever I get around to it.

The only problem is the touchpad, it works but the mouse cursor speed is really below normal, going from a corner of the video to the opposite one takes about one minute and a lot of rubbing

You've got a newer Synaptics touch pad. The new Synaptics pads where identifying themselves as Alps, which has a different acceleration coefficient. But now they've went back just identifying themselves as Synaptics. So I don't know how to tell them apart anymore. Anyway the fix is easy.

Click on /etc/X11/Xorg.conf, it should open in the text editor. Then change this line:

Option "AccelFactor" "0.0030"

to

Option "AccelFactor" "0.030"

Save and then restart X.

BTW this along with lots of other good stuff is in the FAQs link on the home page.

[kirk]

Uploaded Seamonkey-2.0.11.pet.

[Sage]

Anything that can be done to persuade users to avoid SM would be worthwhile.

Gradually getting to grips with this strange installation but lack of suppositories(sic) is hampering progress. Couldn't get the 64bit Opera11final to install, either. Some sort of error reported; used the Debian (other) which works on Wary/Quirky/etc.
Let's hope kirk gets plenty of free time over the holidays!

[gcmartin]

@Sage. Respectfully, I don't understand your ANGER! Why do you have such a bias toward a stable, "worthwhile", all inclusive browser to the point you want to deprive others of its services. There are several other forum threads about SeaMonkey (even some by me). Please articulate your bias there so that everyone including the Mozilla community can understand your bias.

My interpretation is that Kirk has updated the "repository". I see NO REFERENCE that he suggest that you or anyone must/should use this.

Personally, Seamonkey has been stable since I first became a fan of BarryK's Pups.

Thanks in advance, if you will let us know in "those threads that are already elsewhere in the forum" why you feel the way you do about SeaMonkey.

P.S. Thanks everyone for ALL of the contributions. This truly is an great effort. Especial Congratulations to Kirk. He has been religiously devoted to insuring we have a stable platform to work from. THANKS!!!
Edited: @Sage, this is NOT a personal attack. Nor should anyone view it as that. It IS a request for understanding....merely.

[capoverde]

Sorry for late reply Kirk - was stuck in bed for two days with a cold (or flu or whatever it was).

Well, booted Fatdog 510 with pfix=ram and immediately installed dhcpcd-3.2.3-x86_64.pet, then ran the Net-wizard: connection worked normally - posting this right after.
_______________________________________________________
Admittedly off-topic:

"Anything that can be done to persuade users to avoid SM would be worthwhile."

The browser of choice is mainly a matter of personal preference. Guess most forum members have tried at least three or four; I've tried Opera, Firefox, Iron, Chrome, Midori and more in Puppy, plus K-meleon and Opera with Wine+Puppy, wasting lots of time at duly configuring 'em. Each has its own pros and cons, but finally my preference stays with SeaMonkey and, when I have Wine at boot, K-meleon.

Surely there's something around that suits my needs/taste even better; but is the time lost in that search justified?...

[Sage]

You are welcome to SM. Many folks consider I've already said too much about it. I hear the clamour already. Personally, I hate it's antiquated style, even Dillo and Netsurf are 'better'. My preference is Opera, as everyone around here knows, but tux has done a great job on FF and the regular FF is entirely acceptable.
Survey after survey has shown that FF is most favour amongst this Forum's members with Opera a close second.
So, I'll now duck out and let the FF & Opera fans speak for themselves. Everyone's entitled to their own opinion.Seasons Greetings.
PS for the Brits - the pure driven snow goes well with a single malt...

[tronkel]

This argument over which is the best browser for Puppy Linux has been running ever since Puppy was born. To date is has never been settled!

Advantages of Seamonkey:
All-in-one package for ease of installation and compact size - so good match for Puppy.
Simplistic but efficient interface.
Good page rendering and mostly HTML standards-compatible.
Later versions have improved Firefox extensions compatibility.
Good email component similar to Thunderbird.

Disadvantages of Seamonkey
Standard theme looks a bit plain-jane
Less then perfect Firefox extensions compatibility - could be a deal-breaker for a lot of users.
Not lightning-fast.
Puppy compiled versions have sometimes been unstable.
Poor choice of theming options.
Recent versions have given serious grief with installing Enigmail, Lightning and Google Calendar Provider.

So Sage is right up to a point, but others are also right up to a point.

Solution to this quandary?

Since Firefox and Thunderbird as separate entities don't appear to exhibit the above-mentioned disadvantages, why not create a pet or sfs that contains both Firefox and Thunderbird? In fact, in Puppy days of yore (about 3 years ago), I made such a package out of Firefox and Thunderbird - called Thunderfox- using the Mozilla binaries. Maybe a bit on the bloated side though.

How about someone compiling Firefox and TB and then merging them into a single pet/sfs?

Mathematically:

Thunderfox = Firefox + Thunderbird >= Seamonkey

@sage single malt + play with latest Android mobile toy in front of log fire?

[gcmartin]

Hey everyone. @Sage must be wallowing in his laughter as he has gotten all of you (us) talking about browsers....INSTEAD OF FATDOG issues and development.

Let me try to say this again...if SAGE want Opera then let him start a forum thread to address Opera. Let's not get into the pro/cons of browser and any base browser that is offered across the Puppies distros that we see.

No offense. But THIS THREAD IS ABOUT FATDOG.....not Sage or anyone's browser emotions.

Just my 2 cents worth. Again, let do what we can, to make FATDOG easy to operate and stable. (And lets ignore those that want to laugh at our reactions to what they start. Thanks.

This forum has threads already available to discuss browsers. This thread is.... "read the title, above"....FATDOG (not browser preferences) So, let's not get distracted by the distractors (I'm including myself in this group). And let's help each other everywhere we can.

And Sage, please don't post Browser hated or love in this thread. Please post in a thread that already exist for Opera or if you choose, SeaMonkey or open your own devoted to your browser issue(s), but this Thread is about FATDOG...not browser hatred. I not repeating myself as I am trying to "make sense" to ...

[capoverde]

OK gcmartin, so here's an odd thing with Fatdog:

as already stated in my post at page 5, I couldn't save-to-file (running Live-CD) upon exiting with Xvesa -- I could with Xorg.

BUT... at the next boot the system loads (apparently) regularly, then everything freezes: "NO SIGNAL" claimed by the monitor, neither Ctrl+Alt+Bksp nor anything else clears things up, no error messages before freezing to give a hint about the problem.

In order to get things to work I must cold-reset & reboot with "pfix=vesa". Everything seems to work then, but the trick must be repeated at every boot.

As always, I suspect the embedded Intel graphic card may be involved. If time permits, I'll try on a different box.

[gcmartin]

@JamesBond Thanks for the Pdiag Utility. I took a look at it and you've done a pretty thorough job this utility's capture.

Thanks for such a thoughtful piece of creation.

OK gcmartin, so here's an odd thing with Fatdog: ...
as already stated in my post at page 5, I couldn't save-to-file (running ... .

I not the right person to answer this, but I would do 1 of the following and post back here.

1. Boot LiveDVD/CD with loglevel=7 to get a system capture of the boot problem.
2. Run JamesBonds "new tool" (Pdiag.sh Posted: Fri Dec 17, 2010 4:01 am Post subject: Diagnostic script )

Post either of these in this thread with the description you just gave me of your problem. I'm sure someone should reply with a resolution. It seems to me that there are several current incarnations of Puppies that are struggling to get a firm handle on this specific problem that I too have reported elsewhere.

[capoverde]

Just tried twice to download Pdiag, which seemed a promising tool to keep at hand, but after being asked where I'd save it (as per my Namoroka preferences setting) nothing was saved.

Tried again after setting my prefs back to default, found Pdiag normally saved to /root/spot/Downloads. Oh well... Why can't that be changed?

[Caneri]

Hi Kirk,JB,

Has anyone had problems with internet connections on 64-510?

My install works well and the wifi (ath9k) module loads but no connections to the net via FF....sorry if this had been posted but it's a LONG thread...TIA

Eric

[gcmartin]

Just tried twice to download Pdiag, which seemed a promising tool to keep at hand, but after being asked where I'd save it (as per my Namoroka preferences setting) nothing was saved.

Tried again after setting my prefs back to default, found Pdiag normally saved to /root/spot/Downloads. Oh well... Why can't that be changed?

Don't know if I'm late to the table here, but,using the default browser I click Edit >> Preferences >> Always ask me... (on the General Tab). After that, you can tell the browser where to store your downloads.

• Then after download, open ROX to the downloaded file, doubleclick the downloaded file to have it saved as PDiag.sh.
• Then right-click on the PDiag.sh file, click Permissions >> Yes (so that it becomes an executable program in Linux).
• Finally open a 2nd ROX window. In this 2nd window, Click "my-applications" icon >> "bin" icon. Now, drag the Pdiag.sh from the other ROX window to this ROX window.

Whenever you either click this icon or type Pdiag.sh in a terminal window, it could run the Diagnostic Collection Tool.

Hope this helps

[kirk]

I uploaded a Opera-11 pet package and Billtoo's pets.

Caneri,

Yes, we've had some problems with dhcpcd. The pet package attached to the first post in this thread has a fix for the version of dhcpcd included in 510, or you can use the other version of dhcpcd I posted on page 6 of this thread.

[Sage]

Many thanks, kirk!
Did that - got the same "Error, package opera-11.pet failed to install." as I got when I tried to use .deb(other).
Interesting, as a check, tried to install nano & encfs from your repo - got exactly the same error messages.
Also, had to re-install my hard-wired NIC (SiS190) this morning???

[jamesbond]

UPDATE:
Refreshed and refuelled, I have some excellent news for you, jb.
Strange as it is to use an M$-anything, your ploy worked. I got the full busybox read-out and a complete boot up.

Looks as if the fault lies somewhere in the regular fs/legacyGRUB/install routine?

Over to you, with grateful thanks.

Glad that it worked.

I actually tested both Grub4DOS and Grub legacy, both works for me ... but Grub is more touchy, because when you install it you need to install it to both MBR (or superblock), and to the filesystem (the files in /boot/grub - the so-called stage 2). Grub4Dos on the other hand just install everything into hidden sectors ... it's cleaner that way.