Fatdog64-520RC2
To remove nouveau (other than deleting the folder as kirk already said earlier) with a single reboot, assuming you boot for the first time:
- first boot
- choose System --> Boot Manager --> Blacklist and add nouveau
- reboot and create a save file
After reboot nouveau will no longer be loaded.
There is a way to remove nouveau without rebooting, but not for 520 (because it requires yet another kernel recompilation...) --> this http://cateee.net/lkddb/web-lkddb/VT_HW ... NDING.html to be enabled. And you need vbetool.
gcmartin,
samba-3.5.6 moved to the main PPM area and should be accessible through PPM now.
- first boot
- choose System --> Boot Manager --> Blacklist and add nouveau
- reboot and create a save file
After reboot nouveau will no longer be loaded.
There is a way to remove nouveau without rebooting, but not for 520 (because it requires yet another kernel recompilation...) --> this http://cateee.net/lkddb/web-lkddb/VT_HW ... NDING.html to be enabled. And you need vbetool.
gcmartin,
samba-3.5.6 moved to the main PPM area and should be accessible through PPM now.
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]
Ray, assuming you still have windows on it (since you have ntfs) - boot Windows and do chkdsk on that partition. Then try again.
I just tried on my ntfs partition and it works ok, no errors. I didn't put my savefile there though, that ntfs partition is on a usb stick. If you put the savefile on ntfs partition, once a while you will get some corruption (which is okay), all you need to do is to boot windows and run chkdsk on it. Then everything will be good again (for a while). All my fat dogs are unleashed and they run with either ext3 or ext4, but I still have Wary that runs on ntfs and my record so far is about 4 months - every 4 months things start to rot, I need to go to windows to chkdsk the disk and make it happy.
cheers!
I just tried on my ntfs partition and it works ok, no errors. I didn't put my savefile there though, that ntfs partition is on a usb stick. If you put the savefile on ntfs partition, once a while you will get some corruption (which is okay), all you need to do is to boot windows and run chkdsk on it. Then everything will be good again (for a while). All my fat dogs are unleashed and they run with either ext3 or ext4, but I still have Wary that runs on ntfs and my record so far is about 4 months - every 4 months things start to rot, I need to go to windows to chkdsk the disk and make it happy.
Even betterkirk wrote:You might be able to unload nouveau and delete it on the first boot if you boot with nomodeset pfix=vesa.
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]
More tests with Fusion E-350
(Testing Fusion E-350)kirk wrote:.. boot with nomodeset pfix=vesa.
Thanks for that tip! I did that with 520RC2 and it ran OK from cold-boot, but not OK thereafter. It simply hangs.
I tried the parameters with 511 (my first use of Fatdog 64!) and I got a screen with working Mesa/direct rendering. The xorg.conf looks like the pristine xorg.conf. Subsequent boots of 511 are OK even without the added kernel parameters. xorg.conf was unchanged.
I tested xorgwizard from the menu of 511 and it created the vesa xorg.conf files (see example files here) but hung at xwin time. Rebooting and using CLI, I restored the xorg.conf from its bak copy and was able to get back to X.
I encounter a similar problem in 520RC2 - I could not use xorgwizard from X (when X is working). All I see is a blank screen.
Therefore, the question: is there another way to test/tweak xorg before X, or is simply adding "pfix=vesa" the recommended solution for X problems?
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
HARDINFO Reports do not balance
System appears to running stably. Only issue I have found in shown in the attached reports. This is a low priority issue since it does NOT impact system operation(s). But, it is misleading to someone trying to ID information about their PC.
Please look at the hardcopy report and compare its information with the on-screen report page.
My finding is that the hardcopy shows RAM and MB information while the screen does NOT.
My question is two-fold. Can others post similar info? and who should the issue be addressed by?
Hope this helps
Please look at the hardcopy report and compare its information with the on-screen report page.
My finding is that the hardcopy shows RAM and MB information while the screen does NOT.
My question is two-fold. Can others post similar info? and who should the issue be addressed by?
Hope this helps
- Attachments
-
- report-video-glx.txt.bz2
- Hardcopy report on video, Memory, and Hardinfo results
- (10.46 KiB) Downloaded 417 times
-
- HardINFO Cumputer on-screen is not reporting information found in the report hardcopy.png
- Missing Information contained on this Hardinfo screen
- (127.96 KiB) Downloaded 1961 times
Raffy,I tested xorgwizard from the menu of 511 and it created the vesa xorg.conf files (see example files here) but hung at xwin time. Rebooting and using CLI, I restored the xorg.conf from its bak copy and was able to get back to X.
I encounter a similar problem in 520RC2 - I could not use xorgwizard from X (when X is working). All I see is a blank screen.
Therefore, the question: is there another way to test/tweak xorg before X, or is simply adding "pfix=vesa" the recommended solution for X problems?
What kind of graphics card do you have? In the thread you linked to, the xorg.conf was using the vesa driver also.
When you try the Xorg Video Wizard from the Setup menu, you said you got a blank screen. Was that before you where asked to choose a resolution or after?
Some info that may help:
nomodeset --- This is a kernel boot option that tells the kernel not to enable kernel mode setting (KMS). Video support is usually a combination of a drm kernel driver and a Xorg driver working together. KMS is used with Intel, Nouveau, and Radeon kernel modules. KMS is required for Intel and Nouveau, and optional for Radeon (although, with different features).
If you want to use the vesa Xorg driver, and you have hardware that uses the Intel, Nouveau, or Radeon kernel modules, you may need to boot with nomodeset, or blacklist the matching module, or just delete the module. The modules will be found in /lib/modules/3.0.3/kernel/drivers/gpu/drm/.
pfix=vesa --- This boot option tells the boot scripts to delete any existing xorg.conf and create a new bare-bones xorg.conf that specifies the vesa driver. The vesa driver should support just about everything, but you'll have no 2d or 3d acceleration and no special features (dual head, hdmi ...). You should only have to do this once, Xorg will use the vesa driver on subsequent boots. You may still need to specify nomodeset if you have hardware that uses the Intel, Nouveau, or Radeon kernel modules. If you use the Xorg Video Wizard from the Setup menu (xorgwizard-old if you exit X) it will create a detailed xorg.conf, and will probably not choose the vesa driver. So if you use the Xorg Video Wizard and you need to you the vesa driver, you'll need to edit the xorg.conf file. This can be done within the Xorg Video Wizard. After choosing your resolution, you will need to click "Test". After that you can click "Tweek" and then edit the xorg.conf. You'll want to change the line that has the driver from this:
Code: Select all
Driver "intel" #card0driver
Code: Select all
Driver "vesa" #card0driver
Edit: I've modified the Xorg Video Wizard, if you boot pfix=vesa, it will use the vesa driver for the xorg.conf it creates.
gcmartin,
That's a Hardinfo problem. This is a developmental version, but it seems better than the old one.
vesa as boot parameter
Thanks for that.kirk wrote:Edit: I've modified the Xorg Video Wizard, if you boot pfix=vesa, it will use the vesa driver for the xorg.conf it creates.
What I've tried in the Fusion E-350 (with Radeon 6310 graphics), was to test xorgwizard from the menu, but can't, so a boot-time parameter will be a big help.
As to when hanging occurs while tweaking the screen resolution, it is after choosing the resolution in 511 and after choosing the wizard (from the menu) in 520RC2 (the screen immediately goes blank).
Am happily running the 511, although it baffles me no end that a pristine xorg.conf will get me direct graphics rendering, but this is the AMD Fusion, with (impressive) integrated graphics in the CPU. AMD calls it APU ("accelerated" is the word).
These are the other specs of the Fusion family:
9w TDP: C-30 (1 core, 1Ghz), C-50 (2 cores, 1.2 Ghz) - Radeon 6250
18w TDP: E-240 (1 core, 1.5Ghz), E-350 (2 cores, 1.6 Ghz) - Radeon 6310
(These are fantastic 64-bit processors, so expect them to be all over the portables such as laptops, tablets and net-tops. Mini-ITX combo boards with these processors are now in stores.)
Puppy user since Oct 2004. Want FreeOffice? [url=http://puppylinux.info/topic/freeoffice-2012-sfs]Get the sfs (English only)[/url].
Don't know if this helps on Hardinfo, but notice compilation line from FATDOG64-RC2Hope this helps
Code: Select all
# hardinfo -v
HardInfo version 0.5.2pre
Copyright (C) 2003-2009 Leandro A. F. Pereira. See COPYING for details.
Compile-time options:
Release version: Yes (ARCH_x86)
BinReloc enabled: Yes
Data prefix: /usr/share/hardinfo
Library prefix: /usr/lib/hardinfo
Compiled on: linux-ARCH_x86 2.6.39.4 ()
Modules:
File Name Name Version
libcomputer.so Computer 0.5.2pre
libdevices.so Devices 0.5.2pre
libnetwork.so Network 0.5.2pre
libbenchmark.so Benchmarks 0.5.2pre
#
Reviewing the video shortcomings reported above, it seems that a text panel pop-up would help to assist neophytes. As far as black-screening is concerned, is it possible to intercept these in SW, even if only to display said panel with options and instructions about which drivers to load/unload, boot codes, etc? This approach has been used successfully for eg network connecting.
There may be a short intermission whilst kirk dodges Irene?!
There may be a short intermission whilst kirk dodges Irene?!
Looks like Irene has set her sites on Northern parts of US and Canada. Florida, except for some rain, is spared...I think.Sage wrote: ... There may be a short intermission whilst kirk dodges Irene?!
Question;
I offered this for review, before, but does Shinobar's Personalize Settings allow a simple tool that might help a couple of the issues we still have in FATDOG.
It would be nice to have the OS figure out everything automagically. But in light of the several problems i am aware of, seems that tool JUST MIGHT provide a helping hand for the immediate future.
Just a thought that might help. Not looking for a debate nor need a response.
-
- Posts: 156
- Joined: Fri 21 Nov 2008, 17:20
I've just decided to try Fatdog and wanted to say whats good and what I've found not quite so good, most comments are comparing with Puppy 4.3.1.
A quick system outline.
Pentium D930
Intel M/B with integrated audio and network
ATi X1600 graphics
2GB RAM
I've done a "manual frugal" install to an ntfs partition for now.
Boot up - it "just works" everything is ready to use without setting loads of options for KB, testing video etc.
Network - it finds my wired Ethernet and gets an IP straight off.
Video card - magic I have open GL and DRI on my ATi without any fiddling. I spent ages finding a combination of 4 series kernel and some beta drivers that managed that.
Items:
Browser and e-mail
The Firefox icons both on the desktop and the menu open Aurora the same as the "default browser" menu entry does.
Same as above with Thunderbird, the icons open Miramar.
As a test, "firefox" in a terminal also starts Aurora
Window Manager changing
The option in the menu to change window manager seems "clunky" compared to the rest.
At one point I lost the "taskbar" altogether trying to change to JWM. I resorted to Ctrl+Alt+Backsp then "xwin" + options and got it back without a reboot and haven't managed to reproduce the quirk since.
Apart from these points this seems a great distro and I like it a lot, thanks.
Will
EDIT
Have just realized I think I am using Fatdog 520 RC from this thread http://www.murga-linux.com/puppy/viewtopic.php?t=70771. I hadn't noticed Kirk has a new RCout so we'd better ignore these notes till I've had chance to try the latest release.
Will
A quick system outline.
Pentium D930
Intel M/B with integrated audio and network
ATi X1600 graphics
2GB RAM
I've done a "manual frugal" install to an ntfs partition for now.
Boot up - it "just works" everything is ready to use without setting loads of options for KB, testing video etc.
Network - it finds my wired Ethernet and gets an IP straight off.
Video card - magic I have open GL and DRI on my ATi without any fiddling. I spent ages finding a combination of 4 series kernel and some beta drivers that managed that.
Items:
Browser and e-mail
The Firefox icons both on the desktop and the menu open Aurora the same as the "default browser" menu entry does.
Same as above with Thunderbird, the icons open Miramar.
As a test, "firefox" in a terminal also starts Aurora
Window Manager changing
The option in the menu to change window manager seems "clunky" compared to the rest.
At one point I lost the "taskbar" altogether trying to change to JWM. I resorted to Ctrl+Alt+Backsp then "xwin" + options and got it back without a reboot and haven't managed to reproduce the quirk since.
Apart from these points this seems a great distro and I like it a lot, thanks.
Will
EDIT
Have just realized I think I am using Fatdog 520 RC from this thread http://www.murga-linux.com/puppy/viewtopic.php?t=70771. I hadn't noticed Kirk has a new RCout so we'd better ignore these notes till I've had chance to try the latest release.
Will
In addition, from wikipedia:kirk wrote:Those are the code names Mozilla uses for these releases.The Firefox icons both on the desktop and the menu open Aurora the same as the "default browser" menu entry does.
Same as above with Thunderbird, the icons open Miramar.
Tony,To allow distributions of the code without using the official branding, the Firefox source code contains a "branding switch". This switch allows the code to be compiled without the official logo and name, for example to produce a derivative work unencumbered by restrictions on the Firefox trademark (this is also often used for alphas of future Firefox versions). In the unbranded compilation the trademarked logo and name are replaced with a freely distributable generic globe logo and the name of the release series from which the modified version was derived. The name "Deer Park" is used for derivatives of Firefox 1.5, "Bon Echo" for derivatives of Firefox 2.0, "Gran Paradiso" for derivatives of Firefox 3.0 and "Shiretoko" is used for derivatives of Firefox 3.5. Derivatives of Firefox 3.6 are referred to as "Namoroka". The codename Minefield and a modified version of the generic logo stylized to look like a bomb is used for unofficial builds of version 3.0 and later, and for nightly builds of the trunk.
Distributing modified versions of Firefox under the "Firefox" name requires explicit approval from Mozilla for the changes made to the underlying code, and requires the use of all of the official branding. For example, it is not permissible to use the name "Firefox" without also using the official logo. When the Debian project decided to stop using the official Firefox logo in 2006 (because of copyright restrictions on its use incompatible with the project's guidelines), they were told by a representative of the Mozilla Foundation that this was not acceptable, and were asked either to comply with the published trademark guidelines or cease using the "Firefox" name in their distribution.[155] Ultimately, Debian switched to branding their modified version of Firefox "Iceweasel", along with other Mozilla software.
Kernel version shouldn't affect compatibility. Compatibility is more affected by shared libraries dependencies. I've never tried mixing with Slackware packages - but I've tried with some Debian packages (the "lenny" branches) and they worked fine. Why don't you give it a try and let us know?
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]
Well I took your advice. I loaded flightgear 64 on slacko and moved it
across onto fatdog 64.
Tested it out with ldd -v and got it down to :-
libdbus-1.so.3 => not found
libhal.so.1 => not found
libsvn_client-1.so.0 => not found
libsvn_ra-1.so.0 => not found
libsvn_subr-1.so.0 => not found
libstdc++.so.6 (GLIBCXX_3.4.14) => not found
libstdc++.so.6 (GLIBCXX_3.4.14) => not found
libstdc++.so.6 (GLIBCXX_3.4.14) => not found
After that I crashed the system playing with versions of libstdc++.so.6.
Will do a bit more googling and try again.
Regards Tony
across onto fatdog 64.
Tested it out with ldd -v and got it down to :-
libdbus-1.so.3 => not found
libhal.so.1 => not found
libsvn_client-1.so.0 => not found
libsvn_ra-1.so.0 => not found
libsvn_subr-1.so.0 => not found
libstdc++.so.6 (GLIBCXX_3.4.14) => not found
libstdc++.so.6 (GLIBCXX_3.4.14) => not found
libstdc++.so.6 (GLIBCXX_3.4.14) => not found
After that I crashed the system playing with versions of libstdc++.so.6.
Will do a bit more googling and try again.
Regards Tony
Haha, you choose a difficult one. I've never gotten flightgear64 to work so far.
I can only add one thing: libdbus is available as a pet in the PPM.
Others you must get elsewhere. Fatdog's libstdc++ is one version older that requested - if you get a newer libtsdc++, don't replace the original version, instead put it somewhere else and use LD_LIBRARY_PATH.
cheer!
I can only add one thing: libdbus is available as a pet in the PPM.
Others you must get elsewhere. Fatdog's libstdc++ is one version older that requested - if you get a newer libtsdc++, don't replace the original version, instead put it somewhere else and use LD_LIBRARY_PATH.
cheer!
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]
Desktop Recorder help
Hi All
I have the RC2 build installed to a usb stick and would like to use GTK-Recordmydesktop or Xvidcap to make some videos about the o/s, however cant find either of them anywhere, the .pets on these forums dont work any help would really be appreciated.
I have the RC2 build installed to a usb stick and would like to use GTK-Recordmydesktop or Xvidcap to make some videos about the o/s, however cant find either of them anywhere, the .pets on these forums dont work any help would really be appreciated.