Fatdog64-510

Message

Billtoo · #61 Post by **Billtoo** » Mon 13 Dec 2010, 19:48

I booted the live cd with "fatdog pfix=ram" and when it got to the
desktop the srcreen was garbled.

I booted the live cd with "fatdog nomodeset pfix=vesa,ram"
and got to the desktop (this pc needs the exact pfix=vesa,ram line)

# glxgears
1710 frames in 5.0 seconds = 341.947 FPS
1723 frames in 5.0 seconds = 344.573 FPS
1705 frames in 5.0 seconds = 340.897 FPS
1718 frames in 5.0 seconds = 343.521 FPS
#
Display
Resolution 1280x1024 pixels
Vendor The X.Org Foundation
Version 1.9.0
Monitors
Monitor 0 1280x1024 pixels

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

The resolution should be 1440x900

-------------------------------------------------------------------------------
Download and install nvidia pet, restart x:

# glxgears
7426 frames in 5.0 seconds = 1485.097 FPS
7391 frames in 5.0 seconds = 1478.164 FPS
7429 frames in 5.0 seconds = 1485.720 FPS
7426 frames in 5.0 seconds = 1485.139 FPS
#
Display
Resolution 1440x900 pixels
Vendor The X.Org Foundation
Version 1.9.0
Monitors
Monitor 0 1440x900 pixels

OpenGL
Vendor NVIDIA Corporation
Renderer GeForce 9200/PCI/SSE2
Version 3.3.0 NVIDIA 260.19.21
Direct Rendering Yes

I've got 4 computers with nvidia graphics and the nouveau driver only works on
one of the them, the acer revo.
The nvidia pet in the repo works on all 4 though.

kirk · #62 Post by **kirk** » Mon 13 Dec 2010, 20:14

tronkel, capoverde,

Unzip the attached file and put it in /etc, then try dhcpcd again.

Billtoo,

If I exit to the prompt in any of the above and enter "xorgwizard" it won't start the xorgwizard.

Try xorgwizard-old

gcmartin,

xorgwizard-old will create a detailed /etc/X11/xorg.conf. This detailed xorg.conf will show which driver is to be used. You can also look though /var/log/Xorg.0.log and find which driver was loaded. Nouveau is the default, but nv or vesa will be used as folows:

Device id
0x0008, 0x0009 --- vesa
0x0018, 0x0019 --- nv

You can find your device id by running menu-System-PupScan.

Billtoo · #63 Post by **Billtoo** » Mon 13 Dec 2010, 20:59

kirk wrote:
Billtoo,

If I exit to the prompt in any of the above and enter "xorgwizard" it won't start the xorgwizard.
Try xorgwizard-old

Booted "fatdog pfix=ram"
Screen was garbled, ctrl-alt-backspace,entered xorgwizard-old and a screen asking me to chose resolution came up and once that was done the garbled screen came up again.

I've already tried editing the xorg.conf a couple of messages ago.

This pc, and the others too, work great with the nvidia pet once it's installed, so aside from being a little difficult to get it installed, once installed it's super

Sage · #64 Post by **Sage** » Tue 14 Dec 2010, 06:20

once installed it's super

How did you do it, Bt?! Hope that's not a FRUGAL you're referring to? I'd like to join you folks worrying about your video drivers, etc. but this is very difficult if I'm stuck with a KP on the opening lines...

gcmartin · #65 Post by **gcmartin** » Tue 14 Dec 2010, 09:06

For all who want to have FATDOG share files/folders, the SAMBA 3.5.6 PET for FATDOG works beautifully. You'll want to use this for the increased security fixes (along with added functions) that has been added since 3.0.0 came out several years ago. This is full SAMBA.

The setup and use instructions are the same as those when it was tested on FATDOG 5.10 rc5 several weeks ago.

Thank you Kirk for this effort.
Hope this helps everyone.

P.S. I don't know why, but the file transfer tests I ran using SAMBA 3.0.26 VS 3.5.6 has shown faster transfer using 3.5.6. Don't know why, but it is faster. Now, to get back to testing my video.

Stripe · #66 Post by **Stripe** » Tue 14 Dec 2010, 09:55

Hi all

Downloaded 510 but cannot get it to connect to the internet, it says it has after running net-wizard but firefox cant find anything, tried a ping test in terminal and nothing there, any ideas

Have dropped back to 500 and I am very impressed with it
(no connection problems)

Cheers
Stripe

tronkel · #67 Post by **tronkel** » Tue 14 Dec 2010, 10:38

@kirk

The updated /etc/dhcpcd.conf worked OK after restarting dhcp.

Any further ideas about why the ALSA system borked after running alsamixer? ALSA was OK when the system was pristine. Now there's no sound icon in the system tray. Sound card is now not getting recognised by the ALSA wizard.

Any ideas about reconfiguring ALSA?

capoverde · #68 Post by **capoverde** » Tue 14 Dec 2010, 13:01

Confirmed, thanks Kirk - dhcp works after your /etc/dhcpcd.conf file is copied

. Going on for further testing.

kirk · #69 Post by **kirk** » Tue 14 Dec 2010, 14:17

I've added a pet package to the first post in this thread. It contains the bug fixes posted so far. Since the dhcpcd bug is pretty bad I'll be uploading a 511 in a few days.

kirk · #70 Post by **kirk** » Tue 14 Dec 2010, 14:22

tronkel,

If you ran the alsawizard you're probably hosed. Alsawizard was removed from the menu because it only seemed to mess things up. I left the script in there just in case someone really needed it. If you ran alsawizard from the terminal, it's easiest just to make a new save file.

Sage · #71 Post by **Sage** » Tue 14 Dec 2010, 14:35

I'll be uploading a 511 in a few days

Will that include a PUI FULL install fix?

tronkel · #72 Post by **tronkel** » Tue 14 Dec 2010, 16:16

kirk wrote

If you ran alsawizard from the terminal, it's easiest just to make a new save file

OK I'll hang on for 511 and then start from a clean sheet and see what gives. Thanks for all the work and the support. It'll all pay off in the end.

Billtoo · #73 Post by **Billtoo** » Tue 14 Dec 2010, 16:56

Sage wrote:
once installed it's super
How did you do it, Bt?! Hope that's not a FRUGAL you're referring to? I'd like to join you folks worrying about your video drivers, etc. but this is very difficult if I'm stuck with a KP on the opening lines...

The full install to hard drive gave a kernel panic here too.

But I did do a full install (sort of) to an 8 gb sdhc card.
I used gparted to format the card with ext4 and set the boot flag.
Then used the puppy universal installer to install fd510 to the card.
Then installed grub4dos to the card and used the fatdog nomodeset
pfix=vesa,ram parameter so the screen wouldn't be garbled on first
boot.
After first boot and setting up the network,downloading and installing
the nvidia pet, rebooting gave the option to save to a file or the
whole drive.I installed to the whole drive so it's a full install, I
guess.
It's working nice after a few reboots, I've installed a bunch of pets
and there is still 6.4 gb free on the card, even when the card is
freshly formatted it only shows 7.5 gb free.

I made the change to the puppyinstaller in usr/sbin before I did this
but doing the change didn't help with a full install to hard drive.

Sage · #74 Post by **Sage** » Tue 14 Dec 2010, 18:20

Thanks for that, Bt. Nice piece of lateral thinking. Don't have an SD of that capacity spare at present. Looks like this is a serious issue, so let's hope kirk has got his head down working on it ready for 511.

capoverde · #75 Post by **capoverde** » Tue 14 Dec 2010, 18:27

Could not save to file on exiting from an Xvesa session, tried twice - screen went black and nothing happened, had to reboot or force shutdown.

With Xorg all seemed normal on closing session. Intel video card here, maybe it's that?

Stripe · #76 Post by **Stripe** » Tue 14 Dec 2010, 19:07

Hi all

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

Cheers
Stripe

gcmartin · #77 Post by **gcmartin** » Tue 14 Dec 2010, 22:04

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 · #78 Post by **kirk** » Wed 15 Dec 2010, 02:18

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 · #79 Post by **jamesbond** » Wed 15 Dec 2010, 03:47

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 · #80 Post by **Billtoo** » Wed 15 Dec 2010, 04:33

kirk wrote: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.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fatdog64-510

Fatdog64-510

Fatdog64-510

SAMBA PET built for 64bit FATDOG works fine! No issues

Fatdog64-510

SeaMonkey Browser

Full-install test

Fatdog64-510