Fatdog64-510
Fatdog64-510
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.
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.
tronkel, capoverde,
Unzip the attached file and put it in /etc, then try dhcpcd again.
Billtoo,
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.
Unzip the attached file and put it in /etc, then try dhcpcd again.
Billtoo,
Try xorgwizard-oldIf I exit to the prompt in any of the above and enter "xorgwizard" it won't start the xorgwizard.
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.
- Attachments
-
- dhcpcd.conf.gz
- (497 Bytes) Downloaded 450 times
Fatdog64-510
Booted "fatdog pfix=ram"kirk wrote:
Billtoo,
Try xorgwizard-oldIf I exit to the prompt in any of the above and enter "xorgwizard" it won't start the xorgwizard.
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
SAMBA PET built for 64bit FATDOG works fine! No issues
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.
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.
@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?
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?
Life is too short to spend it in front of a computer
Fatdog64-510
Sage wrote: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...once installed it's super
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.
SeaMonkey Browser
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.
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.
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.
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.
- Attachments
-
- dhcpcd-3.2.3-x86_64.pet
- (31.71 KiB) Downloaded 455 times
Full-install test
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)
Report what you see.
cheers!
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
cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Fatdog64-510
I tried it on 3 computers, it got online using wlan0 on two of them and eth0 on the other.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.