Fatdog64-510

[jamesbond]

I asked this question earlier and not answered, yet. So, I'm bumping it>

Anyone care to comment on why terminal sessions (Ctrl-Alt-F2, etc.) hang when you try to login? (System is LIveCD)

thanks in advance

gcmartin, most likely it doesn't hang (if you can switch back to X by using ctrl-alt-f7, it means the system doesn't hang), but the text video is garbled. Unfortunately I don't have any solution for this, other than trying to switch back and forth between X and the text console (ctrl-alt-f7 and ctrl-alt-f1 or f2).

[rcrsn51]

A while back, there was some discussion about running Samba-TNG in Fatdog64. We successfully compiled a 64-bit version but it would never run correctly.

However, I have now tried fd64-510 with the fd64-32bit-libs-3.sfs. Under this combination, the original samba-tng-rcrsn 32-bit package works fine.

[gcmartin]

@Kirk, I haven't installed the nVidia support in liveCD mode. So the problem I am experiencing is in my use of what I get natively when LiveCD boots.

This system has a PCIe nvidia 250 (single card) on a SLI motherboard with multiple LAN and sound onboard. The processor is an X2 witn 4GB RAM.

Desktop seems stable excepting for lack of ability to get to Terminal sessions in Crtl-Alt-F2 to F6. When login ID, them password is entered, there is no further communications from that session. I can go back to the Desktop without problems and I can continue an work necessary. The FATDOG desktop seems stable no matter which workload I throw at it.

Up until this point, I have NOT installed 2 obvious packages for the use of your distro I have requirements for; namely full SAMBA to guide newbies (and non-newbies) in using FATDOG in a LAN with Windows PCs, Linux PCs, and multimedia devices. As reported earlier, the 64bit Full-SAMBA you made available and all of its tools work fine on FATDOG's earlier versions.

If you or anyone feel that by installing the nVidia ...260...PET will fix this dilemma, I will follow any recommendations and report back here with findings for others who may have similar configurations..

[tronkel]

@kirk

Thanks for the guidance on the DHCP problem.

ping google.com didn't work.
ping 208.67.222.22 did work.

I then added this to /etc/resolv.conf without restarting dhcp. This enabled browsing to google but not to other sites such as puppylinux.com and leo.com.

I then copied the IP address lines from /etc/resolv.conf.old back to /etc/resolv.conf and this then enabled me to browse all sites.

If I run dhcpcd again , this seems to erase the contents of /etc/resolv.conf - so the problem then reappears.

Seems then that there is a bug of some sort that affects dhcp.

Will keep an eye on it and see how it goes.

Thanks for the great 64 bit system. Runs very fast for me on this 3 year old AMD system.

tronkel

[tronkel]

@kirk

A system reboot blanks /etc/resolv.conf necessitating the DNS info to be re-copied back to /etc/resolv.conf from /etc/resolv.conf.old

[tronkel]

@kirk

Problems with ALSA

The sound icon has disappeared from the taskbar tray.
This occurred when I ran the ALSA sound wizard in order to try to get the microphone to work in Skype. The ALSA wizard didn't succeed in finding my sound card at all.

[Prospere]

@ kirk

I do not wish to use FGLR since powerplay work well on other distribs with 2.6.35 kernel

about the power play
h-online said

The rudimentary support of the power management functions of Radeon graphics chips already introduced in Linux 2.6.34 has been extended and optimised considerably in 2.6.35. How aggressive the driver's power saving efforts will be can be determined via /sys/class/drm/card0/device/power_method. For instance, writing "dynpm" to this file activates the fully automatic dynamic power management. Alternatively, by writing "profile" to the file, users can enable one of four profiles in the file /sys/class/drm/card0/device/power_profile: "default" enables the standard GPU and memory clocks, "low" activates a power-saving mode, "high" a performance mode, and "auto" automatically switches between "low" and "high" depending on the power supply.

and this worked on slax remix, fedora, Ubuntu, Arch... since the 2.6.35.1

and on radeon IRC, they said it can work only if we use echo.
but this distrib is the first with 2.6.35 whitch do not have these file.

and since 10.7, fglrx do not support anymore powerplay for card officially full supported by 2.6.35

[Sage]

Have been using this one solely as a liveCD so far.
Tonight, some old HDs became available so tried a FULL install. Complete dog's dinner, I'm afraid. Installation seem to go well, but boot came up with KP almost from the off. Shame. I overwrote it with Wary1.0.2 which worked outa-da-box at first asking. Clearly a SW issue.

[davids45]

G'day jamesbond,

Thanks for replying to my wine for Fatdog query.
I'd downloaded the wine version from the Fatdog collection at:

http://distro.ibiblio.org/pub/linux/dis ... g/sfs/500/

so was hoping it was a 64-bit version.

I've now got your recommended 32-bit libs sfs from the same place and will see how I go.

And I've just read the read-me from there as well which explains what does what - "better late than never" is often my excuse.

David S.

[gcmartin]

@kirk

....
ping google.com didn't work.
ping ... did work.
....

If anyone should have a similar problem where their FATDOG goes onto the local LAN but it cannot get outside of your network to the internet, then, your problem is your internal network or the way your router is setup (if it came from your ISP). FATDOG is probably OK.

This feedback from Tronkel is indicative of a DNS problem. That's what you will want to focus on.
Hope this helps anyone

[anAF]

Ok, this must be the right place to post this question.
I downloaded the new iso and tried to make a full install on virtualbox, but after the installation process and the reboot, I've got a "kernel panic - no init found" after the grub screen.
What can I do?
The RC4 worked fine.
Thanks


Davide

[Sage]

I've got a "kernel panic - no init found

I just said that!

[Billtoo]

I've installed fatdog 510 to an 8 gb flash drive using bootflash (in
luci 245).
The first boot came up with a garbled screen on my acer desktop with
an Nvidia 8600 gt graphics card and forced me to hit
ctrl-alt-backspace and then poweroff.
I booted again from the live cd with the "fatdog nomodeset
pfix=vesa,ram" parameter and once at the desktop and after setting up
the wired network I downloaded the nvidia.pet and installed
it,restarted x, then quit and had the save file go to my 8gb
bootflash drive.
Next bootup from the flash drive works:

# glxgears
52146 frames in 5.0 seconds = 10429.166 FPS
52163 frames in 5.0 seconds = 10432.497 FPS
52180 frames in 5.0 seconds = 10435.877 FPS
52195 frames in 5.0 seconds = 10438.974 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 8600 GT/PCI/SSE2
Version 3.3.0 NVIDIA 260.19.21
Direct Rendering Yes

It's working well

[jamesbond]

tronkel,
internet fails because dhcpcd isn't getting DNS entries. I've given the fix to try on earlier post. You can also try this manually (after killing all the dhcpcd process) without creating /etc/dhcpcd.conf, from terminal:

Code: Select all

dhcpcd -Q 006 eth0

assuming that your interface is eth0. If it works, you can create the dhcpcd.conf to make the fix permanent.

Sage etc,
Universal installer has a bug. You can either use the attached installer (gunzip to /usr/sbin), or you can fix it yourself - use geany and edit /usr/sbin/puppyinstaller, go to line 1280, and add the following line:

Code: Select all

cp -a -u --remove-destination $DESTMNTPT/srcmntpt/lib64 $DESTMNTPT/ 

Then you can go and do full install. It should work.

Good luck.

[Sage]

Too kind, jb. Have an extra slice of turkey on me!

Whilst you were abed, I did:

use geany and edit /usr/sbin/puppyinstaller

and got KP exactly as before. Sorry.
Good grief, man - What time is it over there?! I see you're still awake.

[jamesbond]

Thanks billtoo, gcmartin.

<rant mode on>
This nvidia thing is apparently a stuff of magic, caused by closed proprietary interface. I really hope that they learn a page or two from broadcomm - and open-source their specs.
</rant mode off>

There are 3 nvidia drivers available:
a) nv - the old, stable, non KMS open source driver
b) nouveau - the "new", KMS open source driver
c) nvidia proprietary driver
And of course, Fatdog64 has a fallback to vesa (activated by pfix=vesa and nomodeset).

Let's forget about option "c" for the moment because kirk wants to know how this magical stuff works out of the livecd, before installing any proprietary driver (you need to get to X before you can install the nvidia pet).

Between option a) and b), the problem is not all cards with all drivers. Some works with "nv", some works with "nouveau", some doesn't work either (this is where the fail-safe option "vesa nomodeset" comes handy - but on some systems, like mine, the fallback doesn't work!).

Earlier RCs had only "nv" driver, the newer and Final has both "nv" and nouveau. By default nouveau is given preference. If you want to try your luck and use "nv" driver, this is how to do it (you need to have a save file):
a) exit to text console (if possible - if not, skip to step e)
b) run xorgwizard-old
c) after completion, edit /etc/X11/xorg.conf and look for the words

Code: Select all

driver "nouveau"

and change "nouveau" to "nv"
d) restart x (run xwin from terminal)
e) if this one fails, remove all the nouveau stuff

Code: Select all

find / -name "nouveau*" -delete

and then reboot. Repeat step b,c,d.
If it works, then it works. If it still doesn't work --- then we'll have to live with the fallback.

We need to do a quick count of which driver serves the majority better - is it the "nv" driver or the "nouveau" driver. Most problems can be solved by installing "nvidia" driver (option c) - but the problem is, you can't install it if you can't get into the X screen in the first place.

So the idea is to figure out which driver will bring up X for the majority. For the minority - well, they'll have to go with the fallback option, and for the very small minority like me where even the fallback option doesn't work - we just have to figure out things.

In order of priority:
a) must be able to bring up X on nvidia systems
b) if we can't bring up X, then at least text console must be working so that we can troubleshoot X
c) it's ideal that both X and text console works (gcmartin problem) but as long as X works, then text console is of secondary importance.

So far the count is - for nouveau
a) works for myself, gcmartin (boots to X)
b) doesn't work for billtoo (X screen garbled)

For nv
a) doesn't work for me
b) for gcmartin, billtoo = ?

[Sage]

Edit supra.

[capoverde]

Same problem as described by tronkel and ghead - my eth0 connection was found, configured normally with DHCP but then couldn't go online. Tried Tronkel's solution -- went to /etc/resolv.conf and found nothing but three commented lines (!?), opened /etc/resolf.conf.old and copied the line "nameserver 208.67.222.222" found there to /etc/resolv.conf then saved: Magic! Could browse normally.
Don't think it's a problem with my connection: all other Puppies from 1.08 on could go online with no further fuss.

Also: trying to switch over to JWM didn't work from the "flying" menu (right-click on the desktop) but did work from the fixed one (left-click on the bottom left "menu" tab). With JWM working, some settings aren't accepted (changing no. of virtual desktops, changing tray height) while changing theme or background works regularly.

Overall, the system seems quite a bit faster and more responsive than any other Puppy version I've ever tried. Thank you Kirk for a fine job!

*** Edited: Bad news!
The /etc/resolv.conf file gets overwritten every five mins or so with a new commented three-line one:

# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line

and the connection is lost... All to be done over again -- quite unpleasant...

[Billtoo]

For nv
a) doesn't work for me
b) for gcmartin, billtoo = ?

I booted the live cd with "fatdog nomodeset pfix=nv,ram"

# glxgears
1719 frames in 5.0 seconds = 343.650 FPS
1724 frames in 5.0 seconds = 344.727 FPS
1723 frames in 5.0 seconds = 344.567 FPS
1720 frames in 5.0 seconds = 343.861 FPS
#
Display
Resolution 1440x900 pixels
Vendor The X.Org Foundation
Version 1.9.0
Monitors
Monitor 0 1440x900 pixels

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

-------------------------------------------------------------------------------
Rebooted and didn't create save file.
-------------------------------------------------------------------------------

Booted live cd with "fatdog nomodeset pfix=nouveau,ram"

# glxgears
1716 frames in 5.0 seconds = 343.019 FPS
1720 frames in 5.0 seconds = 343.890 FPS
1718 frames in 5.0 seconds = 343.575 FPS
1720 frames in 5.0 seconds = 343.930 FPS
#
Display
Resolution 1440x900 pixels
Vendor The X.Org Foundation
Version 1.9.0
Monitors
Monitor 0 1440x900 pixels

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

-------------------------------------------------------------------------------
Rebooted and didn't create save file
-------------------------------------------------------------------------------

Booted live cd with "fatdog nomodeset pfix=vesa,ram"

# glxgears
1685 frames in 5.0 seconds = 336.821 FPS
1694 frames in 5.0 seconds = 338.738 FPS
1693 frames in 5.0 seconds = 338.496 FPS
1691 frames in 5.0 seconds = 338.008 FPS
#
Display
Resolution 1440x900 pixels
Vendor The X.Org Foundation
Version 1.9.0
Monitors
Monitor 0 1440x900 pixels

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

-------------------------------------------------------------------------------
Rebooted and didn't create save file
-------------------------------------------------------------------------------

Booted live cd with "fatdog nomodeset pfix=whatsup,ram"

# glxgears
1715 frames in 5.0 seconds = 342.917 FPS
1717 frames in 5.0 seconds = 343.333 FPS
1720 frames in 5.0 seconds = 343.893 FPS
1719 frames in 5.0 seconds = 343.604 FPS
#
Display
Resolution 1440x900 pixels
Vendor The X.Org Foundation
Version 1.9.0
Monitors
Monitor 0 1440x900 pixels

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

-------------------------------------------------------------------------------

Seems that you can put whatever you want in the "fatdog nomodeset pfix="
line.

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

If I boot the live cd with "fatdog pfix=ram" the screen is garbled,
ctrl-alt-backspace gets to the prompt but xorgwizard won't run.

-------------------------------------------------------------------------------
Rebooted with "fatdog pfix=ram"
-------------------------------------------------------------------------------

Screen is garbled, hit ctrl-atl-backspace and reboot creating savefile
"nouveau"
Reboot and load "nouveau" save file
X won't start.
do ctrl-alt-backspace.
do xorgwizard-old.
edited xorg.conf and changed line "DRIVER "nouveau" #card0driver"
to "DRIVER "nv" #card0driver"

Reboot and x won't start.
Edited xorg.conf and changed to "DRIVER "vesa" #card0driver"
Reboot and get garbled screen, it's a different color garbled than
pfix=ram bootup.

Rebooted with "fatdog nomodeset pfix=expletive,ram"
and here I am.

The other day I made a bootflash install and used it on my acer revo
nettop computer which has the nvidia ion chip, it got to the desktop
so the nouveau driver works on the that chip, I installed the nvidia
pet to that too, (message a couple of pages back).

The revo install has been running for 3 days, 20:45:55 hours.

[gcmartin]

@Jamesbond, I want to insure I am on the same page with you.

1. If I understand you to say, nouveau is "standard" for LiveCD on systems with a nVidia card...correct?
2. And, If I can get to a Terminal session, running "xorgwizard-old" will allow the system to change to the nv driver....correct?

On the following, this is what I have in an "unmodified LiveDVD"(fatdog pfix=ram) system after boot for /etc/X11/xorg.conf ,,,

Code: Select all

#Special base config file used in Puppy Linux. 

Section "ServerFlags" 
Option "AllowMouseOpenFail"  "true"
Option "AutoAddDevices" "False" # No HAL 
Option "DontZap" "false"
EndSection 

Section "Device" 
Identifier "Configured Video Device" 
#Driver     "vesa"
EndSection 

Section "Monitor" 
Identifier "Configured Monitor" 
EndSection 

Section "Screen" 
Identifier "Default Screen" 
Monitor "Configured Monitor" 
Device "Configured Video Device" 
EndSection 

Section "InputDevice" 
Identifier "Keyboard0" 
Driver "kbd" 
Option "XkbRules" "xorg" 
Option "XkbModel" "pc102" 
Option "XkbLayout" "us"
EndSection 

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2" #mouse0protocol
	Option	    "Device" "/dev/mouse"
	#Option      "Emulate3Buttons"
	#Option      "Emulate3Timeout" "50"
	Option      "ZAxisMapping" "4 5" #scrollwheel
EndSection

From your post, IF I can get to a Terminal and run "xorgwizard-old", I will see an entry in this file showing what?

Lastly, how can I tell what driver is currently being used (The "System Information program" doesn't seem to help ID the video driver in curremt use)?