John, thanks for your help. I put inpu_001.sfs, intrd.gz, and vmlinuz in partition /dev/sda1. Then in /dev/sda1/boot/grub I created menu.lst as follows:
title Puppy Linux Insidious 001
rootnoverify (hd0,0)
kernel (hd0,0)/vmlinuz root=/dev/ram0 pmedia=atahd
initrd (hd0,0)/initrd.gz
But when I boot, I never even make it into grub, just a flashing line cursor in the upper left of the screen. No more. I'm a terrible linux nooby of course...
Are there any drawbacks or disadvantages of a FRUGAL install rather than a FULL install?
-Steve D
Insidious Puppy 001
I don't know how often John check if there are comments here?
So in case he is away for the Holiday Season I would start a new thread in the Beginners section
Then more people get aware of your question.
Re if Frugal install has drawbacks. Well the pupsavfile can be limited.
But a work around is to place .sfs outside of the pupsave in the mnt/home part.
have the menu.lst and the grldr file in the mnt/home part and maybe that helps booting?
Not sure. It booted also when the menu-lst was way deep down in Jolicloud/boot/grub/ menu.lst so as long as you have grldr on a partition that BIOS? accept that would allow it to boot.
Maybe people that knows more than what I know which is almost nothing wants you to tell more about your set up there. Did you have a windows installation and then wiped it clean and did a frugal install? Did you do that from within some Puppy on a CD and which Puppy and did you format to what? Can you see if the boot flag is set as bootable.
I failed booting an USB due to not setting the boot flag. So such has nothing to do with frugal or puppy. All booting need proper set up of BIOS and how the HDD looks like for the grldr?
I could be wrong though. I am a very newbie kind of noob.
So in case he is away for the Holiday Season I would start a new thread in the Beginners section
Then more people get aware of your question.
Re if Frugal install has drawbacks. Well the pupsavfile can be limited.
But a work around is to place .sfs outside of the pupsave in the mnt/home part.
have the menu.lst and the grldr file in the mnt/home part and maybe that helps booting?
Not sure. It booted also when the menu-lst was way deep down in Jolicloud/boot/grub/ menu.lst so as long as you have grldr on a partition that BIOS? accept that would allow it to boot.
Maybe people that knows more than what I know which is almost nothing wants you to tell more about your set up there. Did you have a windows installation and then wiped it clean and did a frugal install? Did you do that from within some Puppy on a CD and which Puppy and did you format to what? Can you see if the boot flag is set as bootable.
I failed booting an USB due to not setting the boot flag. So such has nothing to do with frugal or puppy. All booting need proper set up of BIOS and how the HDD looks like for the grldr?
I could be wrong though. I am a very newbie kind of noob.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
I must be noobier that you are. I don't know what a grldr file is?have the menu.lst and the grldr file in the mnt/home part and maybe that helps booting?
I had a full install of Puppy 5.2 beta on the hard drive before, but used my Ubuntu Lucid 10.04 live-cd to run GParted to format and create 2 partitions: 99GB ext3; and a 1GB linux-swap. The boot flag is set on the main partition.Did you have a windows installation and then wiped it clean and did a frugal install? Did you do that from within some Puppy on a CD and which Puppy and did you format to what? Can you see if the boot flag is set as bootable.
Like I mentioned in an earlier post, the PUI on my Puppy 5.2 CD works fine to perform a full install, but not with the Insidious PUI. But INPU itself runs fine off the CD in live mode.
Maybe there's a different puppy derivative that would be better suited to use on a 5 year old laptop?
-Steve D
Wish those that know more than me would jump in and help you but suppose all of them are traveling to their Holiday families so I try my best.
I would make use of Shinobar's grub4dosconfig and let that one do the set up.
Look for it using this search machine
http://www.wellminded.com/puppy/pupsearch.html
put in this
Shinobar grub4dosconfig
and looks for threads where he describe how to use it.
that one should be able to set things going so all of it boots.
If it does not start a new thread and tell your story there. Hope that helps.
http://murga-linux.com/puppy/viewtopic.php?t=51697
My gut feeling is that ext3 maybe is part of your problem but I know too little.
I remember that I had a HP/Compaq and that one I tried out ext3 and it failed to boot and then I tried another formatting and it booted but that was maybe a year ago so I fail to remember and I could ahve done something else wrong too.
Waht grldr is? I have no idea either. But it may mean Grub Loader
but I only wild guess. Look for it and see if it is on a partition that allow it to be used when booting? But you have to ask somebody else, I know too little.
I would make use of Shinobar's grub4dosconfig and let that one do the set up.
Look for it using this search machine
http://www.wellminded.com/puppy/pupsearch.html
put in this
Shinobar grub4dosconfig
and looks for threads where he describe how to use it.
that one should be able to set things going so all of it boots.
If it does not start a new thread and tell your story there. Hope that helps.
http://murga-linux.com/puppy/viewtopic.php?t=51697
My gut feeling is that ext3 maybe is part of your problem but I know too little.
I remember that I had a HP/Compaq and that one I tried out ext3 and it failed to boot and then I tried another formatting and it booted but that was maybe a year ago so I fail to remember and I could ahve done something else wrong too.
Waht grldr is? I have no idea either. But it may mean Grub Loader
but I only wild guess. Look for it and see if it is on a partition that allow it to be used when booting? But you have to ask somebody else, I know too little.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
As far as I know there is a problem with the installer in Insidious in regard to full installs. See here.......
http://www.murga-linux.com/puppy/viewto ... 042#473042
and
http://www.murga-linux.com/puppy/viewto ... 276#473276
I've performed about 5 different frugal installs,booting with regular grub,on ext3 and no problems.
HTH.
http://www.murga-linux.com/puppy/viewto ... 042#473042
and
http://www.murga-linux.com/puppy/viewto ... 276#473276
I've performed about 5 different frugal installs,booting with regular grub,on ext3 and no problems.
HTH.
Thanks for the pointers, nooby. I know most normal folks are away on holiday this time of year. I will read up on shinobar's grub4dos utility and give that a shot. If I still have no joy after doing that I will start a new thread regarding this specific issue. I might give Puppy 412 a try as I have read that runs well (cooler too) on older laptops. Happy holiday to all!
-Steve D
-Steve D
Sid seems to have a promblem with the GTK main libs and executables.
Any app that depends on input 2>File is getting a lot of warning messages into the FILE.
Xdialog is one of them.
Apps that relay on clean FILE to perform `cut -f X -d Y` don't find the needed info in that field anymore. It is not -f 2 anymore but -f 120 or such.
Sid still is testing and experimental.
The puppyinstaller is getting his infos that way too. But also bootmanager, jwmconfig will suffer and everything in /usr/local has to be concidered to work only with problems.
For the Kernel experience : There is 2.6.37* out and the aufs patches that worked ok on 30.5, 34.7, 35.7 and 36 seems not to work there ATM ...
I tried it also on 6.27.57 but the syntax is different : fs/notify uses some SYM_inode_BOL there while the patches are using SYM_path_BOL. They applied anyway but led to error-halt. I seems that the puppy 2.6.25 kernel doesn't use aufs.
There had been 2.4.37.10 out but it needed some modutils that I couldn't download anywhere and the modutils source from kernel.org for compiling 2.4 kernels had been full of compile errors.
Any app that depends on input 2>File is getting a lot of warning messages into the FILE.
Xdialog is one of them.
Apps that relay on clean FILE to perform `cut -f X -d Y` don't find the needed info in that field anymore. It is not -f 2 anymore but -f 120 or such.
Sid still is testing and experimental.
The puppyinstaller is getting his infos that way too. But also bootmanager, jwmconfig will suffer and everything in /usr/local has to be concidered to work only with problems.
For the Kernel experience : There is 2.6.37* out and the aufs patches that worked ok on 30.5, 34.7, 35.7 and 36 seems not to work there ATM ...
I tried it also on 6.27.57 but the syntax is different : fs/notify uses some SYM_inode_BOL there while the patches are using SYM_path_BOL. They applied anyway but led to error-halt. I seems that the puppy 2.6.25 kernel doesn't use aufs.
There had been 2.4.37.10 out but it needed some modutils that I couldn't download anywhere and the modutils source from kernel.org for compiling 2.4 kernels had been full of compile errors.
Hi All
Happy Christmas from downunder.
Valinote - Sorry my instructions were assuming you already had a working linux distro on another partition complete with it's own already functioning grub - then to add the entry that I listed to boot your insidious puppy - usng the grub installed by your other distro. From the fact you get nothing at all when you boot up I assume the original grub set up for Ubuntu is no longer working.
What I would try would be repair Ubuntu first to give a working grub setup for that a working grub and then add the puppy grub entry [4 lines] to the /boot/grub/menu.lst file of your Ubuntu [you'll need to be root to do this or do sudo gedit /boot/grub/menu.lst]
OR if you have a knoppix live cd handy try installing grub from scratch with that - details see Kyle Rankin's book 'Knoppix Hacks' #66 p203. BUT I don't know if that will work directly with a frugal puppy install - you should be able to repair your Ubuntu grub setup with Knoppix and then add the puppy entry afterwards.
Or use the grub installer of the Puppy Insidious live cd - go Menu-System-Grub bootloader config - see if you can repair grub that way . or if you still have Ubuntu live cd/dvd boot it and use its initial option to boot linux from first hard drive - to get your Ubuntu booted.
then perhaps Ubuntu has it's own grub-install or grub-update commands - I don't know it well enough to know - but you have to boot it first.
Or better still someone who knows what they're doing will come up with a better solution.
Best wishes, John
Happy Christmas from downunder.
Valinote - Sorry my instructions were assuming you already had a working linux distro on another partition complete with it's own already functioning grub - then to add the entry that I listed to boot your insidious puppy - usng the grub installed by your other distro. From the fact you get nothing at all when you boot up I assume the original grub set up for Ubuntu is no longer working.
What I would try would be repair Ubuntu first to give a working grub setup for that a working grub and then add the puppy grub entry [4 lines] to the /boot/grub/menu.lst file of your Ubuntu [you'll need to be root to do this or do sudo gedit /boot/grub/menu.lst]
OR if you have a knoppix live cd handy try installing grub from scratch with that - details see Kyle Rankin's book 'Knoppix Hacks' #66 p203. BUT I don't know if that will work directly with a frugal puppy install - you should be able to repair your Ubuntu grub setup with Knoppix and then add the puppy entry afterwards.
Or use the grub installer of the Puppy Insidious live cd - go Menu-System-Grub bootloader config - see if you can repair grub that way . or if you still have Ubuntu live cd/dvd boot it and use its initial option to boot linux from first hard drive - to get your Ubuntu booted.
then perhaps Ubuntu has it's own grub-install or grub-update commands - I don't know it well enough to know - but you have to boot it first.
Or better still someone who knows what they're doing will come up with a better solution.
Best wishes, John
AUFS already patched source
Finally it seems that I have found a solution for the aufs :
http://git.c3sl.ufpr.br/gitweb?p=aufs/a ... ;a=summary
HEADS > lists kernels with already aufs insinde !
4 months ago aufs2-35 shortlog | log | tree
click TREE for
http://git.c3sl.ufpr.br/gitweb?p=aufs/a ... b=aufs2-35
At the TOP PART of that page click SNAPSHOT to download the 90 Mb source .
Evacuate it from the pupsave and gunzip and tar -xf it from the terminal ... Xarchive takes awfully long ... after felt several minutes I clicked cancel ....
I had a short look into it : fs/aufs is inside .
At the moment there is running make modules on another machine :
While concentrating on the Language part ( found at filesystems ) , the <*> Serial ATA and Parallel ATA drivers ---> , Graphics support ---> and <M> Sound card support ,
I forgot a lot of USB and similar drivers ( flash, CF and so on ).
Kernel 2.6.37-7-i486 became 4.3 Mb and was filling 170-180 Mb Ram on a full install after bootup ...
The LoadAverage is also a little more than slightly higher as on normal Puppies : 0.3 to 0.7 against 0.01 to 0.5 . While doing hard work like compiling large source it is normal : 1.4
The old Serial Mouse is working and Sound is Ok.
It really appears to me that 2.6.34 has got sound card problems.
Best wishes for the new part of the longering of the days (New Year) and a best health besides the fortunate "illnesses" that lead to stay away from difficult situations .
http://git.c3sl.ufpr.br/gitweb?p=aufs/a ... ;a=summary
HEADS > lists kernels with already aufs insinde !
4 months ago aufs2-35 shortlog | log | tree
click TREE for
http://git.c3sl.ufpr.br/gitweb?p=aufs/a ... b=aufs2-35
At the TOP PART of that page click SNAPSHOT to download the 90 Mb source .
Evacuate it from the pupsave and gunzip and tar -xf it from the terminal ... Xarchive takes awfully long ... after felt several minutes I clicked cancel ....
I had a short look into it : fs/aufs is inside .
At the moment there is running make modules on another machine :
While concentrating on the Language part ( found at filesystems ) , the <*> Serial ATA and Parallel ATA drivers ---> , Graphics support ---> and <M> Sound card support ,
I forgot a lot of USB and similar drivers ( flash, CF and so on ).
Kernel 2.6.37-7-i486 became 4.3 Mb and was filling 170-180 Mb Ram on a full install after bootup ...
The LoadAverage is also a little more than slightly higher as on normal Puppies : 0.3 to 0.7 against 0.01 to 0.5 . While doing hard work like compiling large source it is normal : 1.4
The old Serial Mouse is working and Sound is Ok.
It really appears to me that 2.6.34 has got sound card problems.
Best wishes for the new part of the longering of the days (New Year) and a best health besides the fortunate "illnesses" that lead to stay away from difficult situations .
Repairing grub
Valinote,
You can repair the Ubuntu grub using the puppy live cd. Just follow the instructions here:
http://roshan18.wordpress.com/2008/02/0 ... ot-loader/
You can repair the Ubuntu grub using the puppy live cd. Just follow the instructions here:
http://roshan18.wordpress.com/2008/02/0 ... ot-loader/
-
Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
Back home after two weeks of training, my chest feels harder 
I don't have any time to work on Insidious or Puppy, at least for now. If everything goes according to my plan A, the basic training will end in two weeks. Maybe I'll have some spare time by then.
Sorry!
I don't have any time to work on Insidious or Puppy, at least for now. If everything goes according to my plan A, the basic training will end in two weeks. Maybe I'll have some spare time by then.
Sorry!
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
NOPE : /aufs2-2.6-refs_heads_aufs2-35.tar
the git source has got a
config AUFS_FS
bool "Aufs (Advanced multi layered unification filesystem) support"
while it should be
config AUFS_FS
tristate "Aufs (Advanced multi layered unification filesystem) support"
to get AUFS as module ... otherwise with bool you have only the choice between implemented into the kernel or not.
after I changed bool to tristate I got these errors&halt after a long time ( +1 hour ( sata , 2.2 GHz , 1G ram ))
the git source has got a
config AUFS_FS
bool "Aufs (Advanced multi layered unification filesystem) support"
while it should be
config AUFS_FS
tristate "Aufs (Advanced multi layered unification filesystem) support"
to get AUFS as module ... otherwise with bool you have only the choice between implemented into the kernel or not.
after I changed bool to tristate I got these errors&halt after a long time ( +1 hour ( sata , 2.2 GHz , 1G ram ))
OBJCOPY arch/x86/boot/vmlinux.bin
HOSTCC arch/x86/boot/tools/build
BUILD arch/x86/boot/bzImage
Root device is (0, 12)
Setup is 13724 bytes (padded to 13824 bytes).
System is 6795 kB
CRC 66a7b4e
Kernel: arch/x86/boot/bzImage is ready (#1)
Building modules, stage 2.
MODPOST 2806 modules
ERROR: "security_path_chmod" [fs/aufs/aufs.ko] undefined!
ERROR: "fsnotify_add_mark" [fs/aufs/aufs.ko] undefined!
ERROR: "security_inode_readlink" [fs/aufs/aufs.ko] undefined!
ERROR: "security_path_rename" [fs/aufs/aufs.ko] undefined!
ERROR: "deny_write_access" [fs/aufs/aufs.ko] undefined!
ERROR: "security_file_permission" [fs/aufs/aufs.ko] undefined!
ERROR: "security_path_symlink" [fs/aufs/aufs.ko] undefined!
ERROR: "do_truncate" [fs/aufs/aufs.ko] undefined!
ERROR: "do_splice_from" [fs/aufs/aufs.ko] undefined!
ERROR: "security_path_unlink" [fs/aufs/aufs.ko] undefined!
ERROR: "fsnotify_put_group" [fs/aufs/aufs.ko] undefined!
ERROR: "lookup_hash" [fs/aufs/aufs.ko] undefined!
ERROR: "fsnotify_find_mark_entry" [fs/aufs/aufs.ko] undefined!
ERROR: "security_path_mkdir" [fs/aufs/aufs.ko] undefined!
ERROR: "fsnotify_init_mark" [fs/aufs/aufs.ko] undefined!
ERROR: "fsnotify_obtain_group" [fs/aufs/aufs.ko] undefined!
ERROR: "security_path_truncate" [fs/aufs/aufs.ko] undefined!
ERROR: "security_file_mmap" [fs/aufs/aufs.ko] undefined!
ERROR: "security_inode_permission" [fs/aufs/aufs.ko] undefined!
ERROR: "do_splice_to" [fs/aufs/aufs.ko] undefined!
ERROR: "fsnotify_destroy_mark_by_entry" [fs/aufs/aufs.ko] undefined!
ERROR: "__lookup_one_len" [fs/aufs/aufs.ko] undefined!
ERROR: "fsnotify_put_mark" [fs/aufs/aufs.ko] undefined!
ERROR: "security_path_link" [fs/aufs/aufs.ko] undefined!
ERROR: "security_path_chown" [fs/aufs/aufs.ko] undefined!
ERROR: "security_path_rmdir" [fs/aufs/aufs.ko] undefined!
WARNING: modpost: Found 108 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
Re: Insidious Puppy 001
Iguleder wrote:Insidious Puppy 001
Credit for the name goes to pemas and the credit for the logo goes to its original creator; I just modified it.
Hey man, your puplet looks good. I like your fangy logo too.
Glad someone was able to take the fangy idea I had for Attackpup V1 back in May and use it for their own ideas. You know who made the original round puppy logo?
I finally gave up trying to get inpu installed. Rather did a full install of lupu-242. Had to use my Ubuntu live cd to get the grub setup and working though. But all is well now. Runs great on this laptop. Cools temps and reasonable battery life. Thanks to everyone for their patience and kind advice.
-Steve D
-Steve D
I made woof build using latest woof and Iguleders specs of Insidious 002. It uses kernel 2.6.35.7 which I have compiled. I just added for better laptop behavior my made frisbee-001.pet and jemimah_acpi-001.pet so that wireless and laptop behavior is handled better with Jemimah`s latest wireless tool and laptop working is better. And I added rox_right_clicks pet also.
Alsaconf still does not find devices. Audio works though. There are duplicate icons in menu which I track how they are there. Maybe easiest solution is to do zz_squuze-001.pet and just remove them during building.
But hey, it works and uses mostly debian sid packages.
Alsaconf still does not find devices. Audio works though. There are duplicate icons in menu which I track how they are there. Maybe easiest solution is to do zz_squuze-001.pet and just remove them during building.
But hey, it works and uses mostly debian sid packages.
pemasu when you say "I made ..." then you refer to this download?
Insidious Puppy 001, released November 28, built with the November 28 Woof (the one used with Luci 240 and Quirky 1.4, with the zzz PET) -
ISO: inpu-001.iso
Or do you refer to what you have done at home and not uploaded for us to test?
Insidious Puppy 001, released November 28, built with the November 28 Woof (the one used with Luci 240 and Quirky 1.4, with the zzz PET) -
ISO: inpu-001.iso
Or do you refer to what you have done at home and not uploaded for us to test?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though