Fatdog64 700 alpha1
@neeraj:
Thanks for the opera sfs. Please help to make a post under "Fatdog64 Contribution thread" too (the link is in my sig) so that it will be long lasting.
As for the pupx, yeah it's annoying. It has been fixed for next release (which is coming soon), but for now, please detach the attached file, gunzip it, and put it to /usr/share/pupx/locale (create the directory if it doesn't exist).
Abdurrahman/Pavan: boot with boot parameter "blacklist=nouveau"
Thanks for the opera sfs. Please help to make a post under "Fatdog64 Contribution thread" too (the link is in my sig) so that it will be long lasting.
As for the pupx, yeah it's annoying. It has been fixed for next release (which is coming soon), but for now, please detach the attached file, gunzip it, and put it to /usr/share/pupx/locale (create the directory if it doesn't exist).
Abdurrahman/Pavan: boot with boot parameter "blacklist=nouveau"
- Attachments
-
- english.po.gz
- gunzip to /usr/share/pupx/locale
- (694 Bytes) Downloaded 413 times
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]
- neerajkolte
- Posts: 516
- Joined: Mon 10 Feb 2014, 07:05
- Location: Pune, India.
Hi,
@jamesbond,
Thanks for the english.po file.
For the Opera sfs, all the thanks goes to @wognath.
I thought of posting in contribution thread, but I have to upload it first.
My work network blocks many cloud storages like google drive etc.
My home networks data pack has ended. So I will try to upload it asap.
Edit: Here you go.
Download it.
md5: eac12b7a120699a93c12fdd0de95c6b3.
sha1: 2cd84a402ca9374fcf3a4f7177bc780d8b031bec.
Thanks.
- Neeraj.
@jamesbond,
Thanks for the english.po file.
For the Opera sfs, all the thanks goes to @wognath.
I thought of posting in contribution thread, but I have to upload it first.
My work network blocks many cloud storages like google drive etc.
My home networks data pack has ended. So I will try to upload it asap.
Edit: Here you go.
Download it.
md5: eac12b7a120699a93c12fdd0de95c6b3.
sha1: 2cd84a402ca9374fcf3a4f7177bc780d8b031bec.
Thanks.
- Neeraj.
Last edited by neerajkolte on Fri 12 Sep 2014, 08:44, edited 2 times in total.
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson
“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€
- Amara’s Law.
- Ken Thompson
“We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.â€
- Amara’s Law.
-
- Posts: 15
- Joined: Mon 16 Jun 2014, 07:24
Abdulrahman wrote:Can someone post up a basic idiots install guide for the Nvidia proprietary drivers as i searched google and it said something about blacklisting the previous drivers and i got a bit lost ?
So that is all you need too do to install the Nvidia proprietary drivers?jamesbond wrote:Abdurrahman/Pavan: boot with boot parameter "blacklist=nouveau"
-
- Posts: 361
- Joined: Fri 27 May 2011, 17:21
- Location: Reading UK
Radeon UVD/VDPAU
Hello jamesbond & kirk
I've been following the saga of Radeon UVD/VDPAU support for a long time and it finally looks as though everything should be ready for my RS880G to do the job. It's taken so long that I expect you have traded in your AMD laptop for something better, by now.
Question: Is VLC in fatdog 700 built with VDPAU support?
I couldn't see any sign of it. Grigori Goronzy, who did the mesa patches to make radeon/VDPAU work with VLC, said that there should be a setting in preferences to choose either the default "readback method" or to "enable VDPAU for output", but I can't find it.
The Kernel need 6 patches from Christian König, and I saw a post from someone who had successfully applied them to 3.16. Now that you have built kernel 3.16.2, I'll have a go at patching the source to see what happens... I've never done this before, but it doesn't matter if I break it. I guess it just produces a new radeon.ko.
Mesa needs a couple of patches that are included in 10.3, which will be released any day. You keep the fatdog repo quite up-to-date with mesa versions, so I can wait for that to come when it's convenient.
Thanks for you work on fatdog
EDIT:
The patches applied OK
I've now made a new radeon.ko for 3.16.2
I've downloaded the new firmware.
When your next fatdog ISO is released, I should be ready to give UVD a tryout.
EDIT 2:
I've found the setting to enable VDPAU, in preferences. It's well hidden. In VLC 2.1 it only supports decode. The feature that I was talking about is probably in VLC 2.2.
I've been following the saga of Radeon UVD/VDPAU support for a long time and it finally looks as though everything should be ready for my RS880G to do the job. It's taken so long that I expect you have traded in your AMD laptop for something better, by now.
Question: Is VLC in fatdog 700 built with VDPAU support?
I couldn't see any sign of it. Grigori Goronzy, who did the mesa patches to make radeon/VDPAU work with VLC, said that there should be a setting in preferences to choose either the default "readback method" or to "enable VDPAU for output", but I can't find it.
The Kernel need 6 patches from Christian König, and I saw a post from someone who had successfully applied them to 3.16. Now that you have built kernel 3.16.2, I'll have a go at patching the source to see what happens... I've never done this before, but it doesn't matter if I break it. I guess it just produces a new radeon.ko.
Mesa needs a couple of patches that are included in 10.3, which will be released any day. You keep the fatdog repo quite up-to-date with mesa versions, so I can wait for that to come when it's convenient.
Thanks for you work on fatdog
EDIT:
The patches applied OK
I've now made a new radeon.ko for 3.16.2
I've downloaded the new firmware.
When your next fatdog ISO is released, I should be ready to give UVD a tryout.
EDIT 2:
I've found the setting to enable VDPAU, in preferences. It's well hidden. In VLC 2.1 it only supports decode. The feature that I was talking about is probably in VLC 2.2.
Last edited by LateAdopter on Sun 14 Sep 2014, 21:07, edited 1 time in total.
Camera Support - FatDog64
I noticed that gPhoto is not in the package installer, is there any other way to connect my camera to FatDog?
Thanks,
Dan
Thanks,
Dan
do not see Gtkam or go-mtpfs in the repository.
Here is the output of my dmesg, looks like the camera is recognized by the system
Here is the output of my dmesg, looks like the camera is recognized by the system
Code: Select all
[58218.067922] usb 1-4.1.1: new high-speed USB device number 7 using ehci-pci
[58218.162562] usb 1-4.1.1: New USB device found, idVendor=04a9, idProduct=3136
[58218.162571] usb 1-4.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[58218.162577] usb 1-4.1.1: Product: Canon Digital Camera
[58218.162582] usb 1-4.1.1: Manufacturer: Canon Inc.
[58218.162587] usb 1-4.1.1: SerialNumber: BC8153D3E5FD402E99F45B23C607E233
[58277.790719] usb 1-4.1.1: USB disconnect, device number 7
[58340.691217] usb 1-4.1.1: new high-speed USB device number 8 using ehci-pci
[58340.785846] usb 1-4.1.1: New USB device found, idVendor=04a9, idProduct=3136
[58340.785855] usb 1-4.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[58340.785861] usb 1-4.1.1: Product: Canon Digital Camera
[58340.785866] usb 1-4.1.1: Manufacturer: Canon Inc.
[58340.785871] usb 1-4.1.1: SerialNumber: BC8153D3E5FD402E99F45B23C607E233
[58381.470754] usb 1-4.1.1: USB disconnect, device number 8
[58423.377886] usb 1-4.1.1: new high-speed USB device number 9 using ehci-pci
[58423.472384] usb 1-4.1.1: New USB device found, idVendor=04a9, idProduct=3136
[58423.472393] usb 1-4.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[58423.472399] usb 1-4.1.1: Product: Canon Digital Camera
[58423.472404] usb 1-4.1.1: Manufacturer: Canon Inc.
[58423.472409] usb 1-4.1.1: SerialNumber: BC8153D3E5FD402E99F45B23C607E233
[58450.846755] usb 1-4.1.1: USB disconnect, device number 9
[58515.284518] usb 1-4.1.1: new high-speed USB device number 10 using ehci-pci
[58515.382510] usb 1-4.1.1: New USB device found, idVendor=04a9, idProduct=3136
[58515.382516] usb 1-4.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[58515.382520] usb 1-4.1.1: Product: Canon Digital Camera
[58515.382524] usb 1-4.1.1: Manufacturer: Canon Inc.
[58515.382527] usb 1-4.1.1: SerialNumber: BC8153D3E5FD402E99F45B23C607E233
The only package source in glapt is:
http://distro.ibiblio.org/fatdog/packages/700/
Kernel Version: 3.15.5
Although inexperienced I'm really good at following directions, been using Vector for about 7 years for my home desktop.
Appreciate any help.
Dan
http://distro.ibiblio.org/fatdog/packages/700/
Kernel Version: 3.15.5
Although inexperienced I'm really good at following directions, been using Vector for about 7 years for my home desktop.
Appreciate any help.
Dan
Well, I don't know much about FD700, nothing beyond what's available on the forum here. Heck, I don't even know if FD allows a frugal installation. If on the other hand that's what you're running there, and you're adventurous, I'd say grab a few Slack pkgs and check compatibility. Or, you could follow along here and build your own pkg.
This, Gnomad2 (more deps), or go-mtpfs should allow you to mount and access your device with FD's file manager.
If you go with Slack binaries <testing mode of course> you'll have to use "ldd" to sort dependencies.
This way you could make a backup, be reckless and get somewhere.
I wanna know whether that's a frugal install you've got there..
This, Gnomad2 (more deps), or go-mtpfs should allow you to mount and access your device with FD's file manager.
If you go with Slack binaries <testing mode of course> you'll have to use "ldd" to sort dependencies.
This way you could make a backup, be reckless and get somewhere.
I wanna know whether that's a frugal install you've got there..
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
Frugal was not an option when I did the local install. This distribution has just about everything I've ever needed, but suspect that it is by default a frugal distribution to start with.
I had also installed Puppy 5.7.0 on a T42 at the same time and it has similar software.
A few things I noticed about 700
I could not use a save file that was specified as a directory, FD was never aware of the directory.
I had to manually set my swap partition, but manually updating fstab, the create swapfile wants to create it on the boot partition
I will try to compile the latest libgphoto2-2.5.5.1, after I gslapt-get gcc.
I had also installed Puppy 5.7.0 on a T42 at the same time and it has similar software.
A few things I noticed about 700
I could not use a save file that was specified as a directory, FD was never aware of the directory.
I had to manually set my swap partition, but manually updating fstab, the create swapfile wants to create it on the boot partition
I will try to compile the latest libgphoto2-2.5.5.1, after I gslapt-get gcc.
GCC's in the devx here >> http://ftp.nluug.nl/ftp/pub/os/Linux/di ... g/sfs/700/
The fd64-devx_xxx.sfs file contains the GCC compiler, python, headers, etc.. Everything you need to compile stuff.
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<
The above is for blacklisting the nouveau driver. You need to do this before installing the nvidia driver. The next step would be to:Abdulrahman wrote:Abdulrahman wrote:Can someone post up a basic idiots install guide for the Nvidia proprietary drivers as i searched google and it said something about blacklisting the previous drivers and i got a bit lost ?
So that is all you need too do to install the Nvidia proprietary drivers?jamesbond wrote:Abdurrahman/Pavan: boot with boot parameter "blacklist=nouveau"
- load devx SFS, and
- load kernel-source SFS,
- followed by downloading the correct driver from nvidia website,
- chmod +x the said driver
- and run it.
@LateAdopter, beta1 has been released but it still features the same VLC as alpha1.
It comes with updated mesa (10.2.7) but not 10.3 yet. Let us know how your VDPAU experiment goes. From my previous observation, Flash player seems to make use of vdpau in my radeon, but I'm not sure whether this is a universal truth.
@solex, gphoto is now in the repo.
@Semme thanks for helping.
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]
-
- Posts: 15
- Joined: Mon 16 Jun 2014, 07:24
I am posting from a fatdog 700 sfsdirect-remaster so it seems justifiable to post it to this thread as well as others.
SFSdirect-remaster is now working. It is probably the fastest possible remaster method.
Remaster in ram from ram or on device from ram.
Works with both fatdog and standard pups.
Only replacing the fd64.sfs in initrd is not automatic must be done manually until someone supplies the needed code!! Also maybe some tweaking is needed with regard to -e 'excluded' files and directories!
Please try it as a beta release ie use at your own risk. (back up your original initrd before replacing the fd64.sfs)
SFSdirect-remaster is now working. It is probably the fastest possible remaster method.
Remaster in ram from ram or on device from ram.
Works with both fatdog and standard pups.
Only replacing the fd64.sfs in initrd is not automatic must be done manually until someone supplies the needed code!! Also maybe some tweaking is needed with regard to -e 'excluded' files and directories!
Please try it as a beta release ie use at your own risk. (back up your original initrd before replacing the fd64.sfs)
Code: Select all
#!/bin/sh
#sfsdirect remastering suite by stemsee copyright Marcos Contant 2014
. /etc/DISTRO_SPECS
if [ -d /aufs ]; then
name=$DISTRO_FILE_PREFIX
else
name=$DISTRO_NAME
fi
echo "SfS direct is a live remaster system which works in either ram or device.
Make sure that your system has enough ram or uses a swap for the remaster, or
specify path and drive. e.g. mnt sda2.
Do you want to work in ram? y or n"
read ram
case $ram in
y) if [ -d /tmp/quaddirs ]; then
rm -r /tmp/quaddirs
rm /tmp/*.sfs
mkdir -p /tmp/quaddirs/{mnt,tmp,sys,proc}
else
mkdir -p /tmp/quaddirs/{mnt,tmp,sys,proc}
fi
mksquashfs /* /tmp/quaddirs/* /tmp/$name.sfs -e /proc /tmp /mnt /initrd /proc /sys /aufs /archive /root/.cache /root/.Trash /root/spot/Downloads/* /root/Downloads/* /root/.history /root/.bash_history /root/.Skype /etc/resolv.conf /root/.XLOADED /etc/.XLOADED /lib/modules /lib/firmware -keep-as-directory -noappend -comp xz
echo "'$name'.sfs has been created in /tmp. Where do you want to save it to?
Enter the path e.g. /mnt/sda2/"
read savepart
mv -f /tmp/$name.sfs $savepart
echo "All done!" && exit;;
n) if [ -d /tmp/quaddirs ]; then
rm -r /tmp/quaddirs
mkdir -p /tmp/quaddirs/{mnt,tmp,sys,proc}
else
mkdir -p /tmp/quaddirs/{mnt,tmp,sys,proc}
fi
echo "Input path and drive e.g. mnt sda2"
read path drive
mount /dev/$drive /$path/$drive
mksquashfs /* /tmp/quaddirs/* /$path/$drive/$name.sfs -e /proc /tmp /mnt /initrd /proc /sys /aufs /archive /root/.cache /root/.Trash /root/spot/Downloads/* /root/Downloads/* /root/.history /root/.bash_history /root/.Skype /etc/resolv.conf /root/.XLOADED /etc/.XLOADED /lib/modules /lib/firmware -keep-as-directory -noappend -comp xz
echo "All done!" && exit;;
*) echo "You didn't enter anything relevant! Exiting script." && exit;;
esac