Fatdog64 beta2

[jamesbond]

emil,

Thanks for your mathematical software thread. Although I ended up not using sage (I'm not at the level that require that much sophistication) - the collections of math thread you started introduced me to the wealth of open source math software, some of which I do use now.

I suppose once Fatdog has stabilised (ie got into Final status), we can look at trimming some of its fat. Mind you, however, it is unlikely to be as slim as standard puppy.

Wuwei,
I will upload the nvidia driver pet tomorrow.

Kirk,
Minor stuff - for whatever reason, the xterm terminfo file (located in /usr/share/terminfo/) is the old file - which prevents color usage in rxvt. What I did to fix it is to rename the original xterm to xterm-old, then create a symlink to xterm-new.

EDIT:
Lobster, no easy solution for the keyboard layout. You can open terminal and type

Code: Select all

setxkbmap -layout gb

.

cheers!

[tozers]

Hello Kirk,

Please could you describe the basic steps you performed to create FatDog64bit. After compiling the kernel and t2 packages, how have you put everything together and how have you generated the development sfs?

I would like to create a similar distribution. I would like to have a very basic system to run VirtualBox (gcc, kernel headers, etc) with its hard disk image (or iso file) totally on ram. I have been using FatDogA1 and it does the job very well. I have tried to use beta2, but the ram footprint is larger and I was unable to compile the nvidia modules. Thanks in advance.

[oui]

Hi

as didiwiki is not yet available, it is possible to install it directly from a debian depository

http://packages.debian.org/sid/amd64/didiwiki/download

only click and install it as proposed with the puppy package manager

then start it in Rxvt

after the start you can use it in the browser at

http://localhost:8000/

you can of course try to install more from the debian bin packages as you can see in above site the dependencies...

the puppy package manager installs and uninstall deb's and integrate links into the start menu if needed

zim would be more efficient as didiwiki but has terrible dependencies

salut

[jamesbond]

Very bad: the xorg.conf can't be saved and is helpless after start

Yes, that's broke. I've attached a file, unzip it and replace the file in /usr/X11R7/bin.

This replacement xwin doesn't work on my system. Causes the famous blank screen .... there's something inside that kills

EDIT: The package manager doesn't seem to work .... it doesn't detect the new pet ... need to take a look at it (or perhaps get the latest one from woof).

Wuwei, you can get the nvidia pet from the ibiblio site. It will disable the xorgwizard - after you install it, you have to use nvidia-settings or nvidia-xconfig to configure your X. (It comes with a default, working xorg.conf so that should be all right).

[playdayz]

Hey kirk, It's a drag that I am working so hard on Lucid Puppy because I would enjoy playing with Fatdog64. After they are released I'll have the time. You know,when all the different innovations start getting combined that is going to make for some fast Puppy evolution. Thanks.

[kirk]

I've updated xf86-video-ati to the latest, added pppoe and fixed ayttm. I'm going to see if I can fix dialog so that it displays colors, I'm thinking maybe there's some configure option that needs to be enabled.


tozers,

That's a lot of steps . You'd probably be better off just cutting out the stuff you don't like. The sfs file is made using mksquashfs. Fatdog64a1 used lzma compression not zlib compression as now, this accounts for most of the size increase.


jamesbond,

I updated /usr/share/terminfo/, I had not updated it from alpha1. Cut it down in size too. Hopefully this takes care of the problem.

This replacement xwin doesn't work on my system. Causes the famous blank screen

Did you try that booting up ram only, installing the new xwin, exit X and type xwin? This new xwin has the old xvesa stuff removed and the roaming xorg.conf stuff removed that was causing xorgwizard to run every time. If it still hangs let me know what kind of video hardware your using. Now that I think about it, I might have changed xwin since I posted it here, I'll check tonight.

playdayz,

Yep, this is taking all of my free computer time as well.

[jamesbond]

Did you try that booting up ram only, installing the new xwin, exit X and type xwin?

Nope, I did it in with FD already installed with save file. Hardware is Intel Graphics (Integrated Graphics Chipset: Intel(R) Mobile Intel® GM45 Express Chipset). I installed it just to test how it's supposed to work, my system currently works fine without it.

This new xwin has the old xvesa stuff removed and the roaming xorg.conf stuff removed that was causing xorgwizard to run every time.

I know everytime xwin is executed, it will call xorgwizard and re-write xorg.conf (that's why I disabled xorgwizard on my nvidia.pet as the workaround ...).
The trick that prevents xwin to call xorgwizard is to append the (convoluted) output of ddcprobe into a comment near the end of xorg.conf #PuppyHardwareProfile.

If it still hangs let me know what kind of video hardware your using. Now that I think about it, I might have changed xwin since I posted it here, I'll check tonight.

I will try booting with pfix=ram and see how it goes. I'll edit this post later. Yeah a lot of "legacy" code here ...

EDIT:
I tried it both ways (with pfix=ram and without) - and this time, it works ... I have to eat my words back, I can't remember what I did last night that caused the thing to stop working ...

[jamesbond]

I've attached an updated_init which incorporates pfix=noram from pizzasgood's post here http://www.murga-linux.com/puppy/viewtopic.php?t=24899. I think as Fatdog grows, this will become more and more important ...

[kirk]

I've attached an updated_init which incorporates pfix=noram from pizzasgood's post here

Got it, thanks.

I know everytime xwin is executed, it will call xorgwizard and re-write xorg.conf (that's why I disabled xorgwizard on my nvidia.pet as the workaround ...).
The trick that prevents xwin to call xorgwizard is to append the (convoluted) output of ddcprobe into a comment near the end of xorg.conf #PuppyHardwareProfile.

Yep, we don't really need it with the auto video configuration, though I guess if you switch between a laptop and a desktop on some usb installation you might want to put xorgwizard in rc.local. If xorg-server 1.8 had came out a few months ago I'd probably be using that and it uses udev for input setup instead of hal.

I've fixed the package manager again, hopefully got it right this time. Recompiled dialog, still no color but the button all display correctly. There's only one thing that's still bugging me, every now and then on this desktop, the boot will hang near the end of rc.init, It showed up after upgrading the kernel from 2.6.33. No messages with loglevel=7, I had put some debugging stuff in rc.init, when it does happen it doesn't always stop at the same place in rc.init, so it's something in the background. Maybe it's my hardware. I'll upload beta3 in a few days.

[jamesbond]

I've got dialog working with color as long as /usr/share/terminfo/xterm is symlinked to xterm-new (beware - the new xterm-new is not 100% compatible with urxvt -- perhaps we should take it from old puppies).

No clue on the hang, my guess could be due to firmware problem (that's your TV computer you're testing on, right? Perhaps try to blacklist the DVB module and see if the hang is gone?).

[emil]

Hi kirk,

I downloaded beta2 and run it and overall good impression - only thing was, that I couldn't change my keyboard configuration with the Desktop>Chooselocal localization menu.

I clicked the radio button for de_AT: German, Austria but still I had the us configuration.
changing the textfile
/etc/keymap

from "us" to "de" and then restarting the X server did it for me.

thanks for fatdog, I'll try to compile something
kind regards
emil

[kirk]

I couldn't change my keyboard configuration with the Desktop>Chooselocal localization menu.

You need to use setup - Mouse/keyboard wizard. There was some other stuff broke in beta2 that would have caused problems changing keyboards as well. I think it's fixed in beta3.


Beta 3 is uploaded:

http://www.murga-linux.com/puppy/viewtopic.php?t=54774

[eugeniak1]

Hi, have a silly question - is it possible to include LVM support?
A propos - have the same problem - change my keyboard configuration. "Desktop>Chooselocal localization menu" and "Mouse/keyboard wizard" - the result is the same - desktop freezed.