(old)Puppy Linux Discussion Forum

Bug found in fatdog 610:

When I made my extract_rpm-fatdog-1.0.pet and extract_rpm-1.0.pet
I originally made the pet package while using fatdog.

To my surprise I couldn't install them on a regular puppy distro.
I would get error messages. I was able to extract the packages.

Could it be that the lack of a desktop file is the problem??

_______________________________________________________

A script I have written using gtkdialog3 won't launch
in fatdog 610 ---> an image request fails because
the image isn't installed . It will launch if I modify and use fatdog's
gtkdialog4.

Other puppies don't have this problem. Images don't have to present.

____________________________________

Fishy wrote:I appreciate all the effort in making Fatdog a multi-user system but I would prefer to use it as root only. Is there a simple way to change all applications to run as root or do I have to edit all exec files manually?

You don't have to do anything. By default Fatdog runs as root, except for certain network programs.
If you want them to run as root too, look at all files that ends with "-spot" in /usr/bin, and edit them to launch the application directly.

don570 wrote: When I made my extract_rpm-fatdog-1.0.pet and extract_rpm-1.0.pet
I originally made the pet package while using fatdog.

To my surprise I couldn't install them on a regular puppy distro.
I would get error messages. I was able to extract the packages.

Could it be that the lack of a desktop file is the problem??

No, it's because Fatdog's dir2pet uses XZ compression (instead of GZ compression).
Fatdog's pet is actually .tar.xz files (as opposed to puppy's pet which is tar.gz).

A script I have written using gtkdialog3 won't launch
in fatdog 610 ---> an image request fails because
the image isn't installed . It will launch if I modify and use fatdog's
gtkdialog4.

For new scripts, please use gtkdialog4. gtkdialog3 (gtkdialog 0.7.2) is old and no longer maintained. All puppies are also moving towards gtkdialog4 (the one in fatdog is gtkdialog 0.8.0), zigbert is already moving to gtkdialog5? (anything newer than 0.8.2 is gtkdialog5 ). The reason gtkdialog3 is still there is because there are about 120 scripts in Fatdog that still depend on it.

Thanks fellas, more HDMI advice from G and an .rpm installer from don, v.004 lina-lite from el. - truly Xmas has arrived early! {I know! the date is wrong anyway, Xmas should be in July or somewhere else thanks to Gregory, Victorian 10-day adjustments, odd-second adjustments as well as poor record-keeping. Some of us are still celebrating old Norse pagan festivals with fir trees, lights and co. anyway - glad the old sun hasn't changed its time-keeping habits much this last 4.3bn years}.

In Fatdog, how do we check graphics driver in use? I am asking this because Fatdog 610 flash video is not as crisp as Fatdog 600.Sorry if it has been answered already.

To make it come back I had to unplug the HDMI cable from the socket and plug it again into the same port , and then it worked fine .

'Fraid it didn't work!

spandey, try Menu / Control Panel / Desktop / Display Properties , maybe it works in your case ...
If you haven't installed a propietary driver ( intel , nvidia , ati-catalyst ) then it should be Mesa-9.0-x86_64 , the default driver installed by fatdog . If you did , check Menu / System / ...
It should also be a command line which I would like to find out too ...

Sorry to hear that Sage ...

In Fatdog, how do we check graphics driver in use?

Look at /var/log/Xorg.0.log. You can also run glxinfo from a terminal and make sure you see direct rendering: Yes.

Also, if you use ATI graphics, the included open source drivers provide better 2D acceleration than the proprietary fglrx driver.

Thank's kirk Good to know ...

I compiled mhwaveedit in fatdog 610 to make sure
that mhwaveedit opened up retrovol when I clicked
on the mixer button . It's stripped to reduce size.

It includes a new configuration file to make sure that an old one
with a different entry for audiomixer won't confuse mhwaveedit.

____________________________________________________

I checked direct rendering enabled is both versions. The vendor name for driver in 600 is tungsten where as for 610 it's Intel Opensource . I am not sure if both are same company or different.

Other difference I noticed was under about:plugins, firefox lists the plugins twice in 610. One refers to /usr/lib where as other to /usr/lib64. But it 600 it refers to only /usr/lib64.

FatDog is noticeably faster than Saluki 23 . I just received my used PC this afternoon. Saluki was helpful for about an hour then I booted into FatDog. NICE

I honestly think people don't know how outdated & unnecessary old PC's are. I'm not selling anything... but maybe you know what I mean... Bottom line, for under $75 it's like a NEW WORLD getting away from my P4 (yikes why did I wait)...

My eBay ideas for those wishing to investigate the round world...
http://www.murga-linux.com/puppy/viewtopic.php?t=82280

UPDATE: I'll try to get some junkers off my site and concentrate more on puppy's. I guess the variety has become counter-productive, but I'm not fully agreeing w/your sage of wisdom, yet.

Sending you a set of go-faster stripes in the post. You'll need to speak to your President or your shrink about your lemming-itis and your sense of public duty towards landfill, lack of spirit of ingenuity, &co. Hope you're not in need of a humour transplant, too!

not in need of a humour transplant

- a misapprehension, evidently. Should show more Ab Fab, Fawlty Towers and Office over there! Can't win 'em all.

Managed to free up an HD for an FD610 FULL. Went like clockwork yielding a very nice result, thanks, kirk & jb. Presently got it chained with a Nadia install so I could test the GRUB4DOS re-write for both - no problems there, either.
So far the only niggle is that too short time-out for searching wifi. On second thoughts, can't distinguish whether it's too short or just failing on first ask?
Not important, probably my misunderstanding, pfix=ram, nox prior to installing yields the prompt but xorgwizard not available (somebody say that already?) so only X option is xwin. Gives correct video detection on several machines so not an issue.
This control Panel is the best of the lot; should suit the 'doze refugees.

Just ran a test of 610 again on another machine, while I was browsing this topic, to make sure I was right about something others were missing.

On a machine with an fd64save.ext4 file in the base directory of the file system "pfix=ram" does not prevent the save file from being loaded. Sage avoids this only by not having a save file, not because the pfix flag stops loading. "savefile=none" does prevent loading.
--

On the subject of video graphics, please, don't load the KMS module until it is clear that you need it. Leave a route people can use to install a proprietary nVidia driver if there are no acceptable open source drivers.

When I was working with Gentoo there were always open source wrappers for nVidia proprietary drivers we could compile even as kernels evolved. Has this changed?

I would prefer complete open source drivers, but I'm not going to pretend these are keeping pace with changes nVidia introduces. ATI provides enough information for developers. nVidia may not.

There may also be problems with Matrox drivers, though it has been a while since I've fooled with these.

On the subject of video graphics, please, don't load the KMS module until it is clear that you need it. Leave a route people can use to install a proprietary nVidia driver if there are no acceptable open source drivers.

When I was working with Gentoo there were always open source wrappers for nVidia proprietary drivers we could compile even as kernels evolved. Has this changed?

KMS is required for most Intel graphics. With Nvidia, Fatdog64's Xorg will use:

PCID 0x008-0x009 --- vesa (No acceleration)
PCID 0x0018-0x0019 --- nv (2d acceleration)
All other PCIDs --- nouveau (2d and 3d acceleration)

Unfortunately this isn't always the best choice. Sometime's nouveau may give you problems and you'll want to try the nv driver. James' new xorgwizard should make this easier. And to switch to the nv driver, if the nouveau kernel module claims your card's PCID, you should delete/blacklist the nouveau module.

For Matrox the vesa driver is the only option included.

Fatdog64-611 is uploaded. See the first post for details.

For Matrox the vesa driver is the only option included.

Many (most?) boards refuse to show the BIOS screen with my Matrox cards so booting into VESA would be an innovation!
Thanks for 611, kirk. Mirrors, including the Dutch, are not showing up yet. Could be a long haul.

Will you be offering deltas, please?

Hello Kirk

I have just done a new install of fd611.

There is this error on bootup, but it seems not fatal. I think it has been mentioned before, but fd610 does not have it.
Apart from that everything seems normal.

I can confirm the same error on bootup.