Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 22 Dec 2014, 13:17
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
Fatdog2 64bit alpha1
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 6 of 7 [93 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Author Message
3speed

Joined: 28 Jan 2010
Posts: 7

PostPosted: Sun 07 Feb 2010, 21:33    Post subject: 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
Back to top
View user's profile Send private message 
kirk

Joined: 11 Nov 2005
Posts: 1437
Location: florida

PostPosted: Sun 07 Feb 2010, 22:42    Post subject:  

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.
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 2232
Location: The Blue Marble

PostPosted: Mon 08 Feb 2010, 06:32    Post subject:  

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


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 Very Happy )
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, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread
Back to top
View user's profile Send private message 
3speed

Joined: 28 Jan 2010
Posts: 7

PostPosted: Mon 08 Feb 2010, 23:59    Post subject: fat 64
Subject description: initrd
 

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.
Back to top
View user's profile Send private message 
Lobster
Official Crustacean


Joined: 04 May 2005
Posts: 15122
Location: Paradox Realm

PostPosted: Thu 11 Feb 2010, 06:23    Post subject:  

After thinking I might compile a 64Bit kernel, soon realising I was well out of my depth Embarassed - 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 Smile

_________________
Puppy WIKI
Back to top
View user's profile Send private message Visit poster's website 
kirk

Joined: 11 Nov 2005
Posts: 1437
Location: florida

PostPosted: Sat 13 Feb 2010, 00:50    Post subject:  

3speed,

Yes, the new kernel would use squashfs4, you will need the squashfs tools to make a squashfs4 file system. The tools included in Fatdog are for squashfs3. They are not compatible.

My wife got a new laptop, real nice, CoreI5, 4GB of DDR3, Blu-Ray drive $499, but with crappy intel graphics. Anyway, Xorg 7.3 is too old and doesn't support this new Intel graphics chip, so I just rebuilt everything with T2. I got it running, but I've got a to-do list:

* grab the latest kernel and try to patch it for squashfs-lzma, I've got patches for 2.6.32rc2 (I still want to use lzma compression for the devx file)

* rebuild ghostscript to be smaller, way to big right now.

* Include openbox-lxpanel. With JWM, the menu icons have a black background. Going to keep JWM too.

* Get Abiword from CVS and see if it will build with the new gcc. The last version doesn't.

Probably lots of other bugs to find and things to make smaller.
Back to top
View user's profile Send private message 
3speed

Joined: 28 Jan 2010
Posts: 7

PostPosted: Sun 14 Feb 2010, 09:18    Post subject: fat dog  

well this has to do with the sqaushfs but I am way ahead of that problem.
It has to do with the kernel patch also.
still working on it.
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 2232
Location: The Blue Marble

PostPosted: Sun 14 Feb 2010, 23:03    Post subject:  

Hi kirk,
kirk wrote:
* Include openbox-lxpanel. With JWM, the menu icons have a black background. Going to keep JWM too.


If you're sticking to 0.3.8.1P of lxpanel, I've got 2 patches for you:
1. in src/plugins/netstat/devproc.c, include #include <arpa/inet.h> as one of the include headers. Otherwise, this will cause the netstat plugin to crash upon start.
2. in src/plugins/launchbar.c, delete line 517 g_object_unref(filter). If this is not deleted, when you try to add items to launchbar, it will crash.

cheers!

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread
Back to top
View user's profile Send private message 
Aung

Joined: 19 Jan 2007
Posts: 119
Location: Hervey Bay

PostPosted: Mon 15 Feb 2010, 10:42    Post subject:  

Kirk, with a full HD install I am getting this problem and cant setup my DV camera in Kino. I cant find any /etc/modprobe.d/. !! (the new ATI driver sorted the Gxine dieing problem) Aung
# modprobe raw1394
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
# modprobe dv1394
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
Back to top
View user's profile Send private message 
kirk

Joined: 11 Nov 2005
Posts: 1437
Location: florida

PostPosted: Mon 15 Feb 2010, 15:42    Post subject:  

Aung,

The "WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. " does seem to be just that, a warning. I've seen it a few times, but I have not saw it cause a problem. Probably something else going on there. I've never setup a camera with Kino before, I've only used it to import files and edit them.


Mr Bond,

Yes I'm sticking with the 0.3.8.1P version of lxpanel. I tried the latest one but it seems to unstable. That's one nice thing about JWM. I'll apply your patches. Thanks again!

The squashfs-lzma patches I had against 2.6.32rc2 won't work with 2.6.32.8, it gets a weird problem when installing the modules. Makes me too scared to try and use it. The current patches are in linux-next (which I probably should be scared of too), so I'll try 2.6.33rc8 with the linux-next patch and see how that goes. I'm having probems with Rox not rendering all the thumb nails, it only seems to render the ones that are associated with a .desktop file. I saw where Barry was having a problem with ROX focus and rcrsn51 had a solution:

export GDK_NATIVE_WINDOWS=true

I'm having that problem too, So I'll try that and cross my fingers. If not I'll try the old GTK. Also, I can't find the source for ob-xdgmenu. I found something similar, but I think it will need some patching. I don't really use the openbox menu, so it's kind of low on the list.
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 2232
Location: The Blue Marble

PostPosted: Tue 16 Feb 2010, 10:24    Post subject:  

kirk wrote:

Mr Bond,

Yes I'm sticking with the 0.3.8.1P version of lxpanel. I tried the latest one but it seems to unstable. That's one nice thing about JWM. I'll apply your patches. Thanks again!

No worries. Yeah I tried the latest lxpanel as well, it was devastating - lots of warning on startup before crashing. I tried the one before, and the one before ... Not to mention that after 0.3.8.1 they used menu-cached which kinda complicate the issues.

kirk wrote:

... If not I'll try the old GTK.

FD2-64 doesn't come with Gimp, but FD2-32 does, and Gimp there crashes like crazy Confused Some guys said it was caused GTK_DISABLE_DEPRECATED thingy, but I've downloaded Gimp 2.6.8, hacked its configure script to remove all those "DISABLE" defines, and recompiled (for FD2-32, haven't done it for FD-64). Still the same crash. So now I suspect either Glib or GTK is the one causing the problem. I'm not sure whether you plan to roll-out Gimp, but if you do, then watch out, some GTK versions seems to be bad.

kirk wrote:

Also, I can't find the source for ob-xdgmenu.
I found something similar, but I think it will need some patching. I don't really use the openbox menu, so it's kind of low on the list.

I compiled the openbox 3.4.10 (the latest at time I compiled it, now they have 3.4.11). That openbox is now capable of dynamic menu just like lxpanel. I have handcrafted a menu.xml (based on your obmenu-refresh script) which will produce an openbox dynamic menu identical to lxpanel's version. I don't have it with me now, I will attach it later.

cheers!

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread
Back to top
View user's profile Send private message 
kirk

Joined: 11 Nov 2005
Posts: 1437
Location: florida

PostPosted: Tue 16 Feb 2010, 12:13    Post subject:  

I'm not sure if I'm going to include gimp or not. If it seems too unstable I'll dump it. It's really overkill for what I do. I'll be sticking with GTK 2.18.(6?) My problem with Rox was a missing file, /usr/lib64/gconv/gconv-modules. Don't know how I managed to lose it, took a while to find, no errors logged anywhere. Yes, I'd like to get your openbox menu script, Thanks!
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 2232
Location: The Blue Marble

PostPosted: Tue 16 Feb 2010, 20:29    Post subject:  

gimp will crash with segfault if you access its menu too often. File open and file save/save as are especially prone - you can crash it simply by starting gimp and trying to open a file if you're not careful. Very irritating, they claim to fix this post 2.6.5, but even in 2.6.8 this still happens. I guess leave it out first ... if I've got the time again I will try to compile it on FD-64 and see how stable it is, and let you know.

Anyway, attached is the menu.xml ... oh btw it uses ob-xdgmenu Smile and the ob-xdgmenu comes as part of openbox, so don't worry about it, when you compile openbox you'll get it.

cheers!

EDIT: didn't realise the forum didn't allow xml file attachments. This is the gzipped version.
menu.xml.gz
Description  menu.xml for dynamic menu generation in openbox. uses ob-xdgmenu.
gz

 Download 
Filename  menu.xml.gz 
Filesize  718 Bytes 
Downloaded  232 Time(s) 

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread
Back to top
View user's profile Send private message 
tozers

Joined: 08 Oct 2009
Posts: 5

PostPosted: Fri 19 Feb 2010, 15:39    Post subject: If possible, please, update the FatDog64  

Hello Kirk,

I have been following this topic and I have been using FatDog64 for a wile and it is very cool! Thanks!

I have notice some new activities on it, so, if possible, Please, update the FatDog64 at http://puppylinux.asia/tpp/kirk/Fatdog2-64bit/
Back to top
View user's profile Send private message 
jamesbond

Joined: 26 Feb 2007
Posts: 2232
Location: The Blue Marble

PostPosted: Sat 20 Feb 2010, 05:46    Post subject:  

kirk wrote:
I'm not sure if I'm going to include gimp or not. If it seems too unstable I'll dump it. It's really overkill for what I do. I'll be sticking with GTK 2.18.(6?) My problem with Rox was a missing file, /usr/lib64/gconv/gconv-modules. Don't know how I managed to lose it, took a while to find, no errors logged anywhere. Yes, I'd like to get your openbox menu script, Thanks!


jamesbond wrote:

gimp will crash with segfault if you access its menu too often. File open and file save/save as are especially prone - you can crash it simply by starting gimp and trying to open a file if you're not careful. Very irritating, they claim to fix this post 2.6.5, but even in 2.6.8 this still happens. I guess leave it out first ... if I've got the time again I will try to compile it on FD-64 and see how stable it is, and let you know.


I compiled GTK 2.18.7 and overwrite the GTK 2.16.2 which was in FD-32 (and FD-64). The original Gimp that comes with it (2.6.5) suddenly works fine. I did this in FD-32, not in FD-64, but I would extrapolate that your choice of GTK 2.18.6 will be fine for Gimp.

EDIT: must also update glib from 2.20 to 2.22 otherwise the crash still happen. (Glib update alone is not enough, it has to be both glib and gtk).

cheers!

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 6 of 7 [93 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1032s ][ Queries: 13 (0.0057s) ][ GZIP on ]