Just in case you didn't see: that code has 'persistence' as boot parameter which is, as you know, for live-boot v3.Just tested the same code and I can't make it boot
Fred
Ah, okay, I misunderstood. I'm relieved it is that way. It is good to have both options in the one iso, when there is no huge size penalty, of course.saintless wrote: Hi, William.
The iso size will stay the same. Only if using Fat flash drive it will copy the main module two times on the flash drive.
Hi Toni, maybe nothing to do with it, but good if you could test on newer machine than your old 128MB grunter. I do most of my testing on my own old machine here, which doesn't boot from usb. However, my installations are all on usb flash because the hard disk is failing on this machine. I manage that because I have grub4dos/menu.list/grldr on hard drive and the menu.lst instructed to find kernel etc on the usb flash (doesn't need a bootable flash of course). However, I do have weird issues 'sometimes' and very unpredicatable where I sometimes on the same usb flash get 'file not found boot message'. Usually after deleting and installing some new stuff. The other thing is I currently can boot debiandog from current usb but no longer Puppy guydog (file not found boot message for that one). I have come to the conclusion that my old machine has these BIOS/ATA limitations (no of heads, cylinders, usb size etc) such that BIOS can sometimes luckily find vmlinuz etc if it happens to be on earlier enough cylinder and low down in the GB. Once vmlinuz etc is booting it takes over from the BIOS so the rest of the system works fine thereafter - that's my intuitive suspicion anyway (I've been messing around with fdisk expert mode to try and prove it one way or the other, but nothing conclusive so far...). There are certainly many limits that could come into play - these old machines are not expecting large hard drives and usb flash view of the chs situation probably even worse for them:saintless wrote: Just tested the same code and I can't make it boot. I get file not found boot message. The strange thing is I can't make it boot now even with live-media-path=/debian-wheezy/live/ and I'm sure I have it working this way before.
Thanks, I also suspect this could be the cause of my troubles or the version of Grub I have. I will use grub4dos test on another computer today. I need to be sure it is not a problem caused from the remount /live/image line and one squeeze path_id file added in initrd.imgmcewanw wrote:Hi Toni, maybe nothing to do with it, but good if you could test on newer machine than your old 128MB grunter.
My intuition seems to have proved correct Toni. I now have Debiandog booting from my tricky 4GB usb.mcewanw wrote:I have come to the conclusion that my old machine has these BIOS/ATA limitations (no of heads, cylinders, usb size etc) such that BIOS can sometimes luckily find vmlinuz etc if it happens to be on earlier enough cylinder and low down in the GB. Once vmlinuz etc is booting it takes over from the BIOS so the rest of the system works fine thereafter - that's my intuitive suspicion anyway
Renaming vmlinuz is not possible in iso install option I think.mcewanw wrote:This could have important implications for debdog-install, if what I have found proves correct, if we want it to work on old machines - should arrange for vmlinuz to be copied first and then a sync before the rest.
... simply renaming it to say 'avmlinuz' would copy it early during installation...
Hi Toni, fair enough, and I wanted to test the mechanism further before even modifying my own copy of debdog-install. Turns out my original 'solution' was wrong anyway (it is complex testing these things so easy to be in error...:-) so I have removed most of the txt from my earlier post above about this (so as not to confuse anyone or give them false hope..!). I have been testing all day to try and find out what is going on.saintless wrote: There is no need to make debdog-install so complicated since the problems you have on your old hardware are not the same on mine much older hardware. I even doubt someone else will use DebianDog on old hardware like mine.
I have no problem to boot 512Mb and 8Gb flash drive using debdog-install latest version.
I wonder where the fdisk included in DebianDog comes from.William wrote:However, unlike on Lubuntu, debiandog's fdisk wasn't automatically changing the CHS values automatically.
Maybe I should try with gnu-fdisk package installed then in case gparted partitioning problem somehow stems from that?fredx181 wrote:I wonder where the fdisk included in DebianDog comes from.William wrote:However, unlike on Lubuntu, debiandog's fdisk wasn't automatically changing the CHS values automatically.
Officially it's part of the gnu-fdisk package but it's not installed.
Looking at the size of fdisk from gnu-fdisk (extracted the .deb) it's different from the included one.
Fred
Don't think standard fdisk can create filesystems etcDescription-en: Linux fdisk replacement based on libparted
GNU fdisk is a replacement to the old Linux fdisk. It provides the same
features as the original fdisk provides plus some interesting ones like:
* partition resizing
* creating filesystem on newly created partitions
* partition integrity checking
* copying/moving partition
Same place where DebianDog comes from, Fred:fredx181 wrote:I wonder where the fdisk included in DebianDog comes from.
Ok, but I ment from which package.Toni wrote:Same place where DebianDog comes from, Fred:
http://live.debian.net/cdimage/release/ ... andard.iso
Code: Select all
echo "16384,,L,*" | sfdisk -f -H 16 -uS /dev/sdc
mkfs.ext4 -O ^has_journal /dev/sdc1
Forgot also previously to add the modules, optional and rootcopy folders in /live to the archive.EDIT2:New revision of DebianDog-PorteusDog-new-setup.tar.gz uploaded:
The base_only boot option didn't work previously, now it does.
Thank you, Fred!fredx181 wrote:What you need only in fact is the edited linuxrc so attached here.
Code: Select all
find | cpio -H newc -o | xz --check=crc32 --x86 --lzma2 > ../initrd.xz
Hi, William.mcewanw wrote:Though you say your machine won't boot usb with 8MiB offset Toni (and that may well be the case), I would still be grateful if you could try the above method with 8MiB offset just to be sure gparted isn't the culprit really
I use this:Toni wrote:BTW what is yours compress initrd.xz command?
Code: Select all
find . -print | cpio -o -H newc 2>/dev/null | xz -f --extreme --check=crc32 > ../initrd.xz