Fatdog2 64bit alpha1
I've been out of town and had some other things going on, so I haven't been around for a month or so. I do have some plans:
1) Quit using LZMA compression for the main SFS, might still use it for the devx file. LZMA slows things down too much and 64bit machines should have enough RAM.
2) Incorporate Pizzasgood's multi-user stuff. I think I'll just wait and steal it from Woof once Barry gets it in there.
3) Might include QT4. The gui that comes with wpa-supplicant looks good. Maybe I kind find some other good/small QT4 apps.
4) Upgrade firefox to the latest or maybe replace it with Opera if I have QT4. Though I probably should stick with Firefox since it's so popular.
5) Upgrade Flash
6) Get the Latest Kernel
7) Improve the handbrake GUI, Id like it to choose the main title instead of the longest one, don't know if lsdvd can determine that. I think there is a QT GUI for handbrake, but it's big.
8.) Might try Xorg 7.5, but that would be a lot of work. If I did that it might be better to do another T2 build.
Then again, setting on my butt and watching football is pretty appealing too.
1) Quit using LZMA compression for the main SFS, might still use it for the devx file. LZMA slows things down too much and 64bit machines should have enough RAM.
2) Incorporate Pizzasgood's multi-user stuff. I think I'll just wait and steal it from Woof once Barry gets it in there.
3) Might include QT4. The gui that comes with wpa-supplicant looks good. Maybe I kind find some other good/small QT4 apps.
4) Upgrade firefox to the latest or maybe replace it with Opera if I have QT4. Though I probably should stick with Firefox since it's so popular.
5) Upgrade Flash
6) Get the Latest Kernel
7) Improve the handbrake GUI, Id like it to choose the main title instead of the longest one, don't know if lsdvd can determine that. I think there is a QT GUI for handbrake, but it's big.
8.) Might try Xorg 7.5, but that would be a lot of work. If I did that it might be better to do another T2 build.
Then again, setting on my butt and watching football is pretty appealing too.
The devx file contains the patched kernel source with .config.Please, could you post the DotConfig used to compile the Kernel with 64Bit option and also the patches applied.
I used the scripts from from Woof, (/etc/rc.d etc. ) but I didn't use the woof build system for the 64bit version. Woof uses many 32 bit pet packages and it doesn't know how to handle /lib64. So this was put together by hand.How did you generated the pet used by Woof?
P.S. If/when I get around to the next update, I'll be going back to zlib compression. The lzma just slows things down too much and 64bit systems should have plenty of RAM. If you want to re-squash your sfs file without lzma compression, give mksquashfs the -nolzma option.
Kirk, I have upgraded my mobo and when booting from CD, fatdog gets the DSOD after choosing a xorg resolution. I have tried an older puppy (.sfs3) to open up fd200.sfs but it gives a error message about some sort of block mode. I was going to unpet the ATI .pet and copy the .pet into fd200.sfs and burn a new cd. How can I open up fd200.sfs. Aung
Hey Kirk, Fatdog 64 is back online.
In all I was able to take ATI-radeon from Bongo drums X11/xorg/drivers and splice them into Kirks fatdog and now I have fatdog64 running on my newish (its not the latest ATI chipset) mobo.
Now, how do I get pmount to work, and, playing video, or trying to, in Kino kills Gxine, needs a reboot to bring back gxine. Aung
# ./pmount
./pmount: line 35: yaf-splash: command not found
./pmount: line 290: kill: (5135) - No such process
#
In all I was able to take ATI-radeon from Bongo drums X11/xorg/drivers and splice them into Kirks fatdog and now I have fatdog64 running on my newish (its not the latest ATI chipset) mobo.
Now, how do I get pmount to work, and, playing video, or trying to, in Kino kills Gxine, needs a reboot to bring back gxine. Aung
# ./pmount
./pmount: line 35: yaf-splash: command not found
./pmount: line 290: kill: (5135) - No such process
#
fd-200 rebuilt 3speed bike-pup
rebuilt fd 200 compiled the 2.6.30.5 kernel added squashfs-4 to it. the pmount problem is missing some links to the theme. icons. not sure working on it . right now I am trouble shooting the init for the boot cd.
also rebuilding the scripts for the remaster. I am using t-2 lib and some of slackware 64 current source.
Any way I rarely post it hade been so long I had to create an new acount.
But the bike season is slow right now so I just wanted play on my 64 bit system. the rebuild is extremely fast.
took 9 minutes to compile the kernel.
3speed
one gear at a time
things todo
upgrade it to 4.3.1 standards.
also rebuilding the scripts for the remaster. I am using t-2 lib and some of slackware 64 current source.
Any way I rarely post it hade been so long I had to create an new acount.
But the bike season is slow right now so I just wanted play on my 64 bit system. the rebuild is extremely fast.
took 9 minutes to compile the kernel.
3speed
one gear at a time
things todo
upgrade it to 4.3.1 standards.
lxpanel request?
I've finally tried my hand on FD64.
Amazing stuff, my 4G machine's available memory increases from 2.8G on 32-bit OS, to 3.8G on FD64 !!!
Through the process, I met the same problem as archwndas, but fortunately I can solve it. No kernel replacement etc is required, just the devx.
1. Got devx working (you need at least 512MB save file for this)
2. go to /usr/src, then make menuconfig
3. in the drivers --> networking --> wireless --> iwlwifi, in the section for iwlagn, Intel 5000 and 4965 are currently unchecked. Check them, and check all options (except the debugging options)
4. quit and save changes.
5. do a "make modules".
6. Get the new iwlwifi modules (./drivers/net/wireless/iwlwifi) and copy them over the to the correct place, overwriting the existing modules (/lib/modules/2.6.28.10/kernel/drivers/net/wireless/iwlwifi).
7. depmod -a
8. get iwlwifi-5000-1.ucode (many places have this - I got mine from intelwireless.org). Don't use the iwlwifi-5000-2.ucode, use the -1 version as the -2 version is not compatible with driver in 2.6.28.10 kernel.
9. modprobe iwlagn - voila! You've got wifi !!
(I tested these steps in both FD 112 and FD2-64).
Thank you kirk for giving us this!
I only have a simple request, kirk, if you're not too busy, could you please compile 64-bit version of lxpanel? Thank you !
EDIT: I mean openbox+lxpanel thanks.
cheers!
Amazing stuff, my 4G machine's available memory increases from 2.8G on 32-bit OS, to 3.8G on FD64 !!!
Through the process, I met the same problem as archwndas, but fortunately I can solve it. No kernel replacement etc is required, just the devx.
1. Got devx working (you need at least 512MB save file for this)
2. go to /usr/src, then make menuconfig
3. in the drivers --> networking --> wireless --> iwlwifi, in the section for iwlagn, Intel 5000 and 4965 are currently unchecked. Check them, and check all options (except the debugging options)
4. quit and save changes.
5. do a "make modules".
6. Get the new iwlwifi modules (./drivers/net/wireless/iwlwifi) and copy them over the to the correct place, overwriting the existing modules (/lib/modules/2.6.28.10/kernel/drivers/net/wireless/iwlwifi).
7. depmod -a
8. get iwlwifi-5000-1.ucode (many places have this - I got mine from intelwireless.org). Don't use the iwlwifi-5000-2.ucode, use the -1 version as the -2 version is not compatible with driver in 2.6.28.10 kernel.
9. modprobe iwlagn - voila! You've got wifi !!
(I tested these steps in both FD 112 and FD2-64).
Thank you kirk for giving us this!
I only have a simple request, kirk, if you're not too busy, could you please compile 64-bit version of lxpanel? Thank you !
EDIT: I mean openbox+lxpanel thanks.
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]
Thanks !
Nevermind, I got both of them compiled (I found your patched source 0.3.8.1 of lxpanel and that seems to be the easiest one to compile --- and most stable). Some of the newer versions segfault upon starting.
Anyway, I found the source of yaf-splash --- so here it is, and the compiled version.
cheers!
Anyway, I found the source of yaf-splash --- so here it is, and the compiled version.
cheers!
- Attachments
-
- yaf-splash.tar.gz
- the yaf-splash source file, I pulled it out from the CVS at Savannah http://savannah.nongnu.org/projects/yaf-splash/
- (80.68 KiB) Downloaded 938 times
-
- yaf-splash.gz
- compiled yaf-splash, just download and the gunzip the file.
- (13.87 KiB) Downloaded 928 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]
Thanks james bond and kirk.
Now I know what a yaf-splash is. The font in the orange box is tiny.
It sort of wants to work! The orange box is gone in a splash!
# pmount
yaf-splash: couldn't load font "8x16"
ln: creating symbolic link `/tmp/gtkdialog_pmount': File exists
/usr/sbin/pmount: line 295: 18429 Terminated
yaf-splash -font "8x16" -outline 0 -margin 4
-bg orange -text "Puppy Drive Mounter
Please wait, probing hardware..."
#
All the drive icons on the desktop work OK. Aung
Now I know what a yaf-splash is. The font in the orange box is tiny.
It sort of wants to work! The orange box is gone in a splash!
# pmount
yaf-splash: couldn't load font "8x16"
ln: creating symbolic link `/tmp/gtkdialog_pmount': File exists
/usr/sbin/pmount: line 295: 18429 Terminated
yaf-splash -font "8x16" -outline 0 -margin 4
-bg orange -text "Puppy Drive Mounter
Please wait, probing hardware..."
#
All the drive icons on the desktop work OK. Aung
Aung, here's how to fix it: create a symlink from /usr/bin/gtkdialog3 to /usr/sbin/gtkdialog3. In console, do:
pmount should work after that.
Code: Select all
ln -s /usr/bin/gtkdialog3 /usr/sbin/gtkdialog3
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]
Hey James Bond!! You should be on the silver screen, that worked. Now can you sort this one, When I try to play a DV (raw DV) clip in Kino, the Edit window crashes, Black SOD, and then Xine goes out in synpathy and wont play any video. I have to reboot to play anything in Xine. And after this I have a gkrellm (thermal.ko) to sort. Aung
initrd.gz
after compiling the new kernel and setting up the squashfs4 build the intrd.gz and the init has taken me for a set back.
On a full install I built the kernel with squashfs 4 it reads the and mounts them. but after many trys of rebuilding the initrd. I have fell short.
it either fails or fails to mount the the squasfs4.
I have tried tweaking the init.
Made sure all the modules are being loaded.
theses things happened from a setup frugal install.
no sync kernel panic. LOL
unable to find fd-200.sfs lol not sure why looking at the init and
the modules being loads
another build did not even look in the psubdir=fatdog
it just booted right to my sda6 drive.
You figure that when grub was pointed at psubdir on another drive.
weird stuff. and the (hd0,x) pointed to a complete different drive.
any way my full install rebuild and the the old full install.
both load run fine but the drive it is installed on is still being shown.
and if you mount it you have to umount to reboot.
this is even after adjusting the fstab I am looking in to the init.d
and puppy functions.
This pup is much faster then the other pups way fast with a newer kernel and new aufs squashfs 4.
Any input on building the new intrid.gz for the newer kernel would help.
I have been studying Barry's init and have become LOST in space.
3speed
On a full install I built the kernel with squashfs 4 it reads the and mounts them. but after many trys of rebuilding the initrd. I have fell short.
it either fails or fails to mount the the squasfs4.
I have tried tweaking the init.
Made sure all the modules are being loaded.
theses things happened from a setup frugal install.
no sync kernel panic. LOL
unable to find fd-200.sfs lol not sure why looking at the init and
the modules being loads
another build did not even look in the psubdir=fatdog
it just booted right to my sda6 drive.
You figure that when grub was pointed at psubdir on another drive.
weird stuff. and the (hd0,x) pointed to a complete different drive.
any way my full install rebuild and the the old full install.
both load run fine but the drive it is installed on is still being shown.
and if you mount it you have to umount to reboot.
this is even after adjusting the fstab I am looking in to the init.d
and puppy functions.
This pup is much faster then the other pups way fast with a newer kernel and new aufs squashfs 4.
Any input on building the new intrid.gz for the newer kernel would help.
I have been studying Barry's init and have become LOST in space.
3speed
Just changing the kernel isn't too hard. You have to swap out the modules in the initrd.gz and depmod it. Running depmod on your initrd if your currently running an older kernel can be tricky. If you have a full install running your new kernel it's easy. Do this:
1) gunzip initrd.gz
2) mkdir puppy-init
3) cd puppy-init
4) cat ../initrd | cpio -d -i
5) replace all modules
6) depmod -b ./ (path to the root of your initrd)
7) find . | cpio -o -H newc | gzip -9 > ../initrd.gz (from the root of your initrd)
If you want you can remove these two lines from init:
modprobe sqlzma #fatdog
modprobe unlzma #fatdog
You don't have to, it just won't find them since your new kernel won't have lzma compression unless you patched it in.
1) gunzip initrd.gz
2) mkdir puppy-init
3) cd puppy-init
4) cat ../initrd | cpio -d -i
5) replace all modules
6) depmod -b ./ (path to the root of your initrd)
7) find . | cpio -o -H newc | gzip -9 > ../initrd.gz (from the root of your initrd)
If you want you can remove these two lines from init:
modprobe sqlzma #fatdog
modprobe unlzma #fatdog
You don't have to, it just won't find them since your new kernel won't have lzma compression unless you patched it in.
Thanks ... but the rest of the questions are too difficult to me (jamesbond uses gadgets, and while he can jerry-rig some nifty little things, for most of his gadgets he calls on Q instead )Aung wrote:Hey James Bond!! You should be on the silver screen, that worked. Now can you sort this one, When I try to play a DV (raw DV) clip in Kino, the Edit window crashes, Black SOD, and then Xine goes out in synpathy and wont play any video. I have to reboot to play anything in Xine. And after this I have a gkrellm (thermal.ko) to sort. Aung
I don't use Kino since my camcorder produces MPEG2 files (which can't be edited in Kino), and I don't use gkrellm (I use lxpanel) ... so I really can't help there.
I can only guess Kino doesn't really die when it goes out, and somehow it retains an exclusive lock on the graphics card acceleration hardware, so that no other program (including Xine) can use it to play video afterwards. Try the Pprocess (Puppy Process Manager) and see if it's still there, and try to end the process.
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]
fat 64
the new kernel is patched for aufs. like you said I did rebuild the initrd. change out the modules.
the new kernels are a little more udev dependent. I think it may be in the sbin scripts in the image. beacause after rebuilding the sfs files. with the new kernel it only reads the aufs squashfs4. it fails to to unsquasfs the fd-200.sfs
Now I understand why theses things would happen. But it has to do with the new patched kernel.
I see Barry tweaked his intrid scripts some for layrs=aufs on he newer patched kernel. What gets me is the kernel boot intrid is read. but the new kernel seems to ignore the scripts. in the intrid.image I think in the sbin folder. the busy box is not loading the modules.
I believe they are being by passed do the kernel is way different.
this may not be part of fat dogs goal but I am trying to make it run like the 432 pup coming out. make it a 64 bit mirror.
so like you after pulling your hair out building the -rap t2 build.
then rebuilding the Dog with a new kernel then building new sfs files I have been dealing with new road blocks.
everything is the same except the kernel and a rebuilt initrd.
added gyachi, amsn .v4L -compat for old cams. opera .QT4 and the old spcagui for making videos so I can edit them on kino.
your xorg problems is some of your libraries are missing do to the -rap t2 build environment.
this Fat Dog is a Grey hound ready to run.
Thanks Kirk for your feed back and effort .
3speed bike being chased by the fat dog.
the new kernels are a little more udev dependent. I think it may be in the sbin scripts in the image. beacause after rebuilding the sfs files. with the new kernel it only reads the aufs squashfs4. it fails to to unsquasfs the fd-200.sfs
Now I understand why theses things would happen. But it has to do with the new patched kernel.
I see Barry tweaked his intrid scripts some for layrs=aufs on he newer patched kernel. What gets me is the kernel boot intrid is read. but the new kernel seems to ignore the scripts. in the intrid.image I think in the sbin folder. the busy box is not loading the modules.
I believe they are being by passed do the kernel is way different.
this may not be part of fat dogs goal but I am trying to make it run like the 432 pup coming out. make it a 64 bit mirror.
so like you after pulling your hair out building the -rap t2 build.
then rebuilding the Dog with a new kernel then building new sfs files I have been dealing with new road blocks.
everything is the same except the kernel and a rebuilt initrd.
added gyachi, amsn .v4L -compat for old cams. opera .QT4 and the old spcagui for making videos so I can edit them on kino.
your xorg problems is some of your libraries are missing do to the -rap t2 build environment.
this Fat Dog is a Grey hound ready to run.
Thanks Kirk for your feed back and effort .
3speed bike being chased by the fat dog.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
After thinking I might compile a 64Bit kernel, soon realising I was well out of my depth - had another go at Fatdog
Reading all the posts
This time I had the horizontal and vertical hz for my monitor
and tried the 'vesa' setting by editing the config file during initial
boot up
Nope. The crash is quite severe (I can not get back to the command line
with ctrl alt backspace - even ctrl alt - del - have to turn off machine)
Will have a go with Alpha 2
Reading all the posts
This time I had the horizontal and vertical hz for my monitor
and tried the 'vesa' setting by editing the config file during initial
boot up
Nope. The crash is quite severe (I can not get back to the command line
with ctrl alt backspace - even ctrl alt - del - have to turn off machine)
Will have a go with Alpha 2