Fatdog64-510

[Stripe]

Hi all

Thanks for the 510 fixes, I can now connect to the internet like in 500.

Cheers
Stripe

[gcmartin]

The SeaMonkey Browser is quite dated. Current version is 2.0.6 in PPM vhile the industry is at 2.0.11

Don't know if this should be reported here or not, but I notice that the SeaMonkey available in PPM for FATDOG should probably point to the most current version, if possible.

Hope this helps.

[kirk]

tronkel, capoverde, and anyone else for that matter:

Could you try booting up ram only and then only install the attached pet package. Then try to get on-line?

I'm not happy with the current version of dhcpcd. The pet package contains the latest patched version of 3.2.3 maintained by debian.

[jamesbond]

Anyone interested in testing full install - please follow these steps and report.
1) Do a full install with modified puppyinstaller (as indicated in earlier posts)
2) When done, re-boot to LiveCD (or LiveUSB, etc) again
3) Mount the partition where you did the full install earlier (for the following example, I will assume it's /mnt/sda1)
4) Open terminal and type this in terminal (replacing sda1 with the partition where you did the full install)

Code: Select all

chroot /mnt/sda1 /bin/busybox

Report what you see.

cheers!

[Billtoo]

tronkel, capoverde, and anyone else for that matter:

Could you try booting up ram only and then only install the attached pet package. Then try to get on-line?

I'm not happy with the current version of dhcpcd. The pet package contains the latest patched version of 3.2.3 maintained by debian.

I tried it on 3 computers, it got online using wlan0 on two of them and eth0 on the other.

[Sage]

4) Open terminal and type this in terminal (replacing sda1 with the partition where you did the full install)
Code:
chroot /mnt/sda1 /bin/busybox

Did that:
chroot cannot run command /bin/busybox No such file or directory

I presumed you wished the liveCD to be run with pfix=ram

What now?

[anAF]

Hi,
I typed

Code: Select all

chroot /mnt/sda1 /bin/busybox 

The report is attached in the png image

[anAF]

By the way,
if I run the keyboard wizard now, the layouts are all there but when I select the italian layout I've got the graphic error you can see in the attached image: what's the problem now?
Thaks again

Davide

[jamesbond]

Davide, your report means that busybox works ==> init works ==> system should start. You should be able to boot into your full installation.

If you still can't boot, tell me:
a) what's your boot loader (is it grub or grub4dos)
b) how you install it (manually or do you use fatdog64's grub/grub4dos installer)
c) content of your menu.lst file
d) when you boot, please append "loglevel=7" to the kernel command line, and pass me the screen capture when it encounter kernel panic.

I presume you are using VirtualBox to test it - I did the same, and it booted successfully, straight to X desktop. I tested with both grub and grub4dos, using fatdog64's installer (both grub and grub4dos installed to MBR). I didn't even have to change anything in the menu.lst, just accept what grub/grub4dos installer gave me. Unfortunately I can't spare a machine to test full-install on bare metal. Others are welcome to try though.

cheers!

[jamesbond]

By the way,
if I run the keyboard wizard now, the layouts are all there but when I select the italian layout I've got the graphic error you can see in the attached image: what's the problem now?
Thaks again

Davide

That's an interesting art On a more serious note, I'll let others look into this. This is on your frugal install?

[Sage]

jb: although you didn't specifically refer to my HD-install, I decide to append loglevel=7 to my boot parameters. The boot proceeded much further this time until it reached:
autorun DONE
VFS: Mounted root...r-o on device 8:1
Freeing unused k...mem 444k freed
KP!, etc seems to want me to pass an init=option to kernel
followed by six Call Trace o.p.s
Obviously cannot record the whole OP as don't even have a CLI.

[jamesbond]

Sage, have you tried my chroot test above?

[Sage]

Oh yes - see seven items above!
Care to explain purpose in simple terms for a simple guy?

[jamesbond]

Sorry Sage didn't see your post earlier. It means that busybox cannot run ==> thus init cannot be started ==> kernel doesn't know what to do ==> panic!

Now try this:
1) boot with your LiveCD
2) Mount the partition where you did the full install (I'll assume it will be /mnt/sda1)
3) Open terminal
4) In terminal, type this

Code: Select all

cd /mnt/sda1

and then

Code: Select all

ls -l lib64

What do you see? If you get an error message, then type this

Code: Select all

ln -s lib lib64

or else don't do anything - just tell me what you see.

[Sage]

OK.
ls -1(numeric one) lib64 gives :
consolefonts
keymaps
then ls -s lib lib64 gives:
prompt

ls -l(alphabetic) lib64 gives:
lrwxrwxrwx 1(numeric) root root 3 2010-04-23 21:59 lib64-> lib
then ls -s lib lib64 gives:
ln: creating symbolic link 'lib64/lib': File exists

Take your pick, but something seems to be happening.
About time for your cocoa?!!

[Karylon]

Hi folks

this is my first post.
Fatdog64 is that, what I always wanted. Small, running in RAM, 64bit and Openbox to make it responsive. And that together with a few, but high quality applications.
It's my workhorse for everything. Thank's a lot.

For myself ROX is not so convenient for many copy and paste operations, so I have build a package of PcmanFm 0.53 which works well with openbox.Most of the dependencies (libhal, libdbus etc.) were simply taken from debian 64 packages and converted with deb2pet and then funneled into one main package.

The pet is below one Mb.

When someone wants to use this package first you have to tell PcmanFm to use a Gnome icon theme (otherwise You get segfault error).
So copy the "nuoveXT.2.2.tar.bz2" to /usr/share/icons/ and unpack it inside this directory.

Now open the hidden file /root/.gtkrc-2.0 and add after the last line:

gtk-icon-theme-name="nuoveXT.2.2"

Now PcmanFm should work (I hope). You find the in the menu under System.

If possible give me one or two feedbacks, wether it works or not.

If some finds a more beautiful Icontheme please let me know also, because nuove XT is a little bit dull.
P.S.
I have tried several times to upload the (9Mb) nuoveXT.2.2.tar.bz2 but was always thrown out. So please try to find this Icon theme by googling.

Klaus

[gcmartin]

@Kirk
I run a liveDVD and have NOT seen the reported problems others are seeing with DNS resolution on my FATDOG. The problem you are working on, you ask

... try ... dhcpcd-3.2.3-x86_64.pet ...

• Is this PET to be added to my running system?
• And, if so, how will I know what to report to you, if all continues OK and I still am able to route?
• Lastly, if you advise me to test, what steps should I follow for the PET's certification on FATDOG (maybe a 511-rc1 may be in order)?

Hope this helps
P.S. 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).

[James C]

Finally got around to giving 510 a spin..... live pfix=ram.booted to working sound and correct screen resolution but no internet connection. Installed the pet from the first post which solved that little difficulty. Display seems good even with the default driver.

-Computer-
Processor : 4x AMD Athlon(tm) II X4 620 Processor
Memory : 3797MB (219MB used)
Operating System : Puppy Linux 0.50
User Name : root (root)
Date/Time : Wed 15 Dec 2010 04:59:38 PM GMT+5
-Display-
Resolution : 1366x768 pixels
OpenGL Renderer : Software Rasterizer
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA NVidia


-OpenGL-
Vendor : Mesa Project
Renderer : Software Rasterizer
Version : 2.1 Mesa 7.8.2
Direct Rendering : Yes

Think I'll give this a bit of an extended test....looks really good so far.

[James C]

Anyone out there using Nvidia graphics? Just wondering how that's going.

I'm using the onboard Nvidia on this box.......downloaded and installed the 260.19.21 pet and working good.


-OpenGL-
Vendor : NVIDIA Corporation
Renderer : GeForce 7025 / nForce 630a/PCI/SSE2
Version : 2.1.2 NVIDIA 260.19.21
Direct Rendering : Yes


# glxgears
10165 frames in 5.0 seconds = 2032.853 FPS
10183 frames in 5.0 seconds = 2036.480 FPS
10174 frames in 5.0 seconds = 2034.621 FPS
10185 frames in 5.0 seconds = 2036.961 FPS
10170 frames in 5.0 seconds = 2033.841 FPS
11147 frames in 5.0 seconds = 2229.383 FPS
11127 frames in 5.0 seconds = 2225.292 FPS
11418 frames in 5.0 seconds = 2283.442 FPS
11401 frames in 5.0 seconds = 2280.100 FPS
11362 frames in 5.0 seconds = 2272.362 FPS

[jamesbond]

kirk,
The original dhcpcd (without the dhcpcd.conf fix) works fine on my home router, but not on my enterprise router. So the result varies. The problem is the same as others - /etc/resolv.conf was empty. So I quickly figured out that dhcpcd isn't getting DNS information, and I figured it if I forced it to ask for DNS info (by putting "require 006" in dhcpcd.conf), it might work - which it does. It also works with your fuller dhcpcd.conf. I won't be able to test 3.2.3 dhcpcd pet in my problematic environment until tomorrow.

Tested the 3.2.3 dhcpcd in enterprise environment from pfix=ram. It works straight away.

cheers!