Yes, was the first I looked at, and also the stretch-i486.sgn.dancytron wrote:Do you have the stretch-x86_64.sgn file in your .../live directory?
Create Debian 9 (Stretch) minimal ISO similar to DebianDog
Not really, can you test if "live-boot" method works ?Galbi wrote:I've been fighting with this the last days and, no way I can't boot any Stretch Dog64 in this machine.
....
....
Any idea?
Code: Select all
title Stretch Dog 64 live-boot
root (hd0,0)
kernel /stretch64/live/vmlinuz1 boot=live live-media-path=/stretch64/live/ union=aufs
initrd /stretch64/live/initrd.img
Yes, it can, but only save-file and it's a bit more complicated (see below).Galbi wrote:Yes it does, quick and fine.fredx181 wrote:Not really, can you test if "live-boot" method works ?
Can I have persistence?
But can you please first test for me a modified initrd1.xz (perhaps porteus-boot works with this for you):
https://fredx181.github.io/StretchDog/a ... initrd1.xz
(just replace in the "live" directory)
For kernel 4.0.9-6
Ok, persistence with live-boot:
- Download zipped persistence 1GB here:
http://www.smokey01.com/saintless/1Gb-p ... ive-rw.zip
- Extract at the root of the same partition where your stretch64 folder is located.
(it will be found only if it's at the root of the partition)
- Menu.lst entry:
Code: Select all
title Stretch Dog 64 live-boot with persistence
root (hd0,0)
kernel /stretch64/live/vmlinuz1 boot=live persistence live-media-path=/stretch64/live/ union=aufs
initrd /stretch64/live/initrd.img
I know this is a bit weird, but it's the only way I could make it work properly with persistence.
The official "live-boot" way would be to place a "filesystem.module" file in the "live" directory with inside the module names that define the order of loading, but somehow that doesn't work for me.
Well.. now I remember again why I prefer the porteus boot method
Fred
Sorry, the modified version did not work.fredx181 wrote:But can you please first test for me a modified initrd1.xz (perhaps porteus-boot works with this for you):
https://fredx181.github.io/StretchDog/a ... initrd1.xz
(just replace in the "live" directory)
For kernel 4.0.9-6
But with the original version, I've noticed something. If I boot with initrd.img in the grub line, boots fine. But if I change it for initrd1.xz does not boot and says it can't find Porteus file etc.
Is initrd1.xz a compressed version of initrd.img?
Remember: [b][i]"pecunia pecuniam parere non potest"[/i][/b]
@Galbi: I have experienced this myself. Here are two possible solutions.
1. Use UUIDs instead of paths in your grub entry. The stretch-live-frugal-install tool in the Starter Kit can do this.
2. Switch to a newer kernel. For your 64bit Stretch, try one from Fatdog.
a. Get the kernel-modules file and rename it with a .squashfs extension.
b. Get the matching vmlinuz file and rename it as vmlinuz1.
1. Use UUIDs instead of paths in your grub entry. The stretch-live-frugal-install tool in the Starter Kit can do this.
2. Switch to a newer kernel. For your 64bit Stretch, try one from Fatdog.
a. Get the kernel-modules file and rename it with a .squashfs extension.
b. Get the matching vmlinuz file and rename it as vmlinuz1.
Ok, thanks anyway for testing.Galbi wrote:Sorry, the modified version did not work.
I assume you did test it with the "porteus-boot" menu.lst entry ?
Code: Select all
title Stretch Dog 64
root (hd0,0)
kernel /stretch64/live/vmlinuz1 noauto from=/stretch64 changes=/stretch64/live/
initrd /stretch64/live/initrd1.xz
No, booting with initrd1.xz is "porteus" boot style very different from 'live-boot" (with initrd.img) which is the official Debian style.But with the original version, I've noticed something. If I boot with initrd.img in the grub line, boots fine. But if I change it for initrd1.xz does not boot and says it can't find Porteus file etc.
Is initrd1.xz a compressed version of initrd.img?
Fred
This worked!fredx181 wrote:Ok, persistence with live-boot:
- Download zipped persistence 1GB here:
http://www.smokey01.com/saintless/1Gb-p ... ive-rw.zip
- Extract at the root of the same partition where your stretch64 folder is located.
(it will be found only if it's at the root of the partition)
- Menu.lst entry:Code: Select all
title Stretch Dog 64 live-boot with persistence root (hd0,0) kernel /stretch64/live/vmlinuz1 boot=live persistence live-media-path=/stretch64/live/ union=aufs initrd /stretch64/live/initrd.img
===
No joy with this.rcrsn51 wrote:1. Use UUIDs instead of paths in your grub entry.
I want to try this, but not sure what to do in point a.
Thanks again boys.2. Switch to a newer kernel. For your 64bit Stretch, try one from Fatdog.
a. Get the kernel-modules file and rename it with a .squashfs extension.
b. Get the matching vmlinuz file and rename it as vmlinuz1.
Remember: [b][i]"pecunia pecuniam parere non potest"[/i][/b]
Switch your install back to Porteus boot.Galbi wrote:I want to try this, but not sure what to do in point a.2. Switch to a newer kernel. For your 64bit Stretch, try one from Fatdog.
a. Get the kernel-modules file and rename it with a .squashfs extension.
b. Get the matching vmlinuz file and rename it as vmlinuz1.
I gave you the link to Fatdog's kernel page.
1. Download the file kernel-modules.sfs-4.12.10
2. Rename it as kernel-modules.sfs-4.12.10.squashfs
3. Download the file vmlinuz-4.12.10
4. Rename it as vmlinuz1
5. Copy the two files into your /live frugal install folder.
6. Reboot.
Success !!!rcrsn51 wrote:Switch your install back to Porteus boot.Galbi wrote:I want to try this, but not sure what to do in point a.2. Switch to a newer kernel. For your 64bit Stretch, try one from Fatdog.
a. Get the kernel-modules file and rename it with a .squashfs extension.
b. Get the matching vmlinuz file and rename it as vmlinuz1.
I gave you the link to Fatdog's kernel page.
1. Download the file kernel-modules.sfs-4.12.10
2. Rename it as kernel-modules.sfs-4.12.10.squashfs
3. Download the file vmlinuz-4.12.10
4. Rename it as vmlinuz1
5. Copy the two files into your /live frugal install folder.
6. Reboot.
with Porteus Boot and keeps changes.
Thanks.
Remember: [b][i]"pecunia pecuniam parere non potest"[/i][/b]
That's great, thanks for trying and reporting back !Galbi wrote:Success !!!rcrsn51 wrote:Switch your install back to Porteus boot.Galbi wrote:I want to try this, but not sure what to do in point a.
I gave you the link to Fatdog's kernel page.
1. Download the file kernel-modules.sfs-4.12.10
2. Rename it as kernel-modules.sfs-4.12.10.squashfs
3. Download the file vmlinuz-4.12.10
4. Rename it as vmlinuz1
5. Copy the two files into your /live frugal install folder.
6. Reboot.
with Porteus Boot and keeps changes.
Thanks.
@rcrsn51
Do you have any idea why this 4.12 kernel boots with porteus-boot and not the 4.9 kernel (well, in Galbi's case, works for me).
(and , as you might have noticed above, for Galbi the 4.9 kernel does boot with "live-boot").
Fred
I have seen this several times, on newer machines. It is some kind of conflict between the stock 4.9.0 kernel and the Porteus boot method.
If you run the bootup in "debug" mode you can see how Porteus is failing to detect the hard drive. But I don't know what causes the problem.
Almost any Puppy or Fatdog kernel will fix it. But I am surprised that 32bit worked for Galbi while 64bit did not.
If you run the bootup in "debug" mode you can see how Porteus is failing to detect the hard drive. But I don't know what causes the problem.
Almost any Puppy or Fatdog kernel will fix it. But I am surprised that 32bit worked for Galbi while 64bit did not.
For the record, I've used the 4.14.12 kernel version.
The problem with the 4.9.0 kernel happens only in this machine, which has two hard disks, one of them a bit old, perhaps thats why?
In another PC (one Intel i3), newer than this, boots fine.
===
Another question: Which are the libs necesary to have compatibility with 32bit software?
Saludos.
The problem with the 4.9.0 kernel happens only in this machine, which has two hard disks, one of them a bit old, perhaps thats why?
In another PC (one Intel i3), newer than this, boots fine.
===
Another question: Which are the libs necesary to have compatibility with 32bit software?
Saludos.
Remember: [b][i]"pecunia pecuniam parere non potest"[/i][/b]
It depends on what you want. After doing:Galbi wrote:Which are the libs necesary to have compatibility with 32bit software?
Code: Select all
dpkg --add-architecture i386
apt-get update
mv -f /etc/apt/preferences /etc/apt/preferences.bak # must do this, otherwise possibly errors
Code: Select all
apt-get install <package>:i386
Code: Select all
dpkg -i <package>_i386.deb
apt-get -f install
Code: Select all
dpkg --add-architecture i386
apt-get update
mv -f /etc/apt/preferences /etc/apt/preferences.bak # must do this, otherwise errors
apt-get install libc6:i386 libatk1.0-0:i386 libcairo2:i386 libfontconfig1:i386 libfreetype6:i386 libgdk-pixbuf2.0-0:i386 libglib2.0-0:i386 libgtk2.0-0:i386 libgtk-3-0:i386 libpango1.0-0:i386 libsm6:i386 libxext6:i386 libxrender1:i386 libxt6:i386 libasound2:i386 libdbus-glib-1-2:i386
Note: will take a lot of space.
Fred
Thanks again Fred, I'll try that, but now something more urgent appeared.
I need the kernel sources for this new kernel (4.14.12) and there are not in the usual repositories. They are necesary to build the VirtualBox kernel module. I must run Vbox to run Win7 for work.
My idea is to migrate from 32bit to 64bit.
Sorry for so many questions.
I need the kernel sources for this new kernel (4.14.12) and there are not in the usual repositories. They are necesary to build the VirtualBox kernel module. I must run Vbox to run Win7 for work.
My idea is to migrate from 32bit to 64bit.
Sorry for so many questions.
Remember: [b][i]"pecunia pecuniam parere non potest"[/i][/b]
That I don't know, maybe best then to switch to "live-boot" again, as you did earlier.Galbi wrote:I need the kernel sources for this new kernel (4.14.12) and there are not in the usual repositories. They are necesary to build the VirtualBox kernel module. I must run Vbox to run Win7 for work.
Then you can install "linux-headers" package and build the VirtualBox kernel module.
Fred
Hi Galbi, just curious, did this work for you to build the VirtualBox kernel module ?rcrsn51 wrote:What about here.Galbi wrote:I need the kernel sources for this new kernel (4.14.12) and there are not in the usual repositories.
Fred