colinux-users

[coLinux-users] installing distro that uses cramfs for initrd

[Luis L. <lui...@gm...>]

Hello List,

I found coLinux several days back and start playing with it, using
Ubuntu 7.04 that was available at the site.

For several reasons, i want to install GoboLinux, which is a different
kind of distro that don't follow standard FHS.

The thing is that following some of the instructions in the wiki page,
I cannot get the initrd to boot since is generated using cramfs.

http://colinux.wikia.com/wiki/Full_CD-based%28iso%29_distro_install_and_config_steb-by-step_HOWTO_%28based_on_Xubuntu-7.10%29

But was impossible for me mount the initrd that came from the CD image:

(-v 3):

Cooperative Linux Daemon, 0.7.3
Daemon compiled on Wed Apr 16 19:00:33 2008
...
Linux version 2.6.22.18-co-0.7.3 (hn@hn-lt) (gcc version 4.1.2) #1
PREEMPT Wed Apr 16 18:50:10 UTC 2008
...
VFS: Mounted root (ext2 filesystem).
ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find
reiserfs on cobd3
VFS: Can't find ext3 filesystem on dev cobd3.
VFS: Can't find an ext2 filesystem on dev cobd3.
Unable to identify CD-ROM format.
List of all partitions:
7503        744 cobd3 (driver?)
No filesystem could mount root, tried:  reiserfs ext3 ext2 iso9660
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(117,3)

and this is my configuration file:

kernel=vmlinux
mem=128
initrd=initrd.gz

cobd0=data\gobo\gobo_014_root.ext3.fs
cobd1=data\gobo\swap_256mb.fs
cobd2=D:\Downloads\Tools\GoboLinux\GoboLinux-014.01-i686.iso
cobd3=data\gobo\gobo-initrd
root=/dev/cobd3

eth0=slirp,02:00:00:00:00:01,tcp:8922:8922

Can anyone point me what I'm doing wrong?

Thank you in advance for your time.

-- 
Luis Lavena
Multimedia systems
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Jason A. <ja...@co...>]

Luis Lavena said the following on 26/04/2008 11:20 PM:
> But was impossible for me mount the initrd that came from the CD image:
>   

coLinux uses a specially compiled kernel and modules. Standard distro's 
don't use it. In general, it's still possible to use any distro you 
want, but it's easiest to "inject" the kernel that comes with coLinux 
into your distro.

Jason

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Luis L. <lui...@gm...>]

On Sun, Apr 27, 2008 at 4:29 AM, Jason Ahrens <ja...@co...> wrote:
> Luis Lavena said the following on 26/04/2008 11:20 PM:
>
> > But was impossible for me mount the initrd that came from the CD image:
>  >
>
>  coLinux uses a specially compiled kernel and modules. Standard distro's
>  don't use it. In general, it's still possible to use any distro you
>  want, but it's easiest to "inject" the kernel that comes with coLinux
>  into your distro.
>

Thank you Jason for your answer, but the thing is that the kernel that
cames with coLinux is not possible to mount cromfs/cramfs, even on a
pre-installed distro like ubuntu using a loop device to extract the
initrd contents of the CD.

If you look at my configuration file, you will see that I'm not trying
to boot from that, but just using as root, which seems not to work.

In any case, I'll try a full boot with that distro and maybe convert
it to another format.

Regards,
-- 
Luis Lavena
Multimedia systems
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Henry N. <Hen...@Ar...>]

Luis Lavena wrote:
> Thank you Jason for your answer, but the thing is that the kernel that
> cames with coLinux is not possible to mount cromfs/cramfs, even on a
> pre-installed distro like ubuntu using a loop device to extract the
> initrd contents of the CD.
> 
> If you look at my configuration file, you will see that I'm not trying
> to boot from that, but just using as root, which seems not to work.
> 
> In any case, I'll try a full boot with that distro and maybe convert
> it to another format.

Try this, there crams is enabled:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080428-cramfs/

If that not work, then please detect the right type of filesystem of the
file "data\gobo\gobo-initrd", for example by booting a Knoppix and than
run "file gobo-initrd".

Should give such output:
initrd: Linux rev 1.0 ext2 filesystem data
----------------------^^^^
But with other filesystem as "ext2" from my initrd.

-- 
Henry N.

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Luis L. <lui...@gm...>]

On Mon, Apr 28, 2008 at 7:28 PM, Henry Nestler <Hen...@ar...> wrote:
> Luis Lavena wrote:
>  > Thank you Jason for your answer, but the thing is that the kernel that
>  > cames with coLinux is not possible to mount cromfs/cramfs, even on a
>  > pre-installed distro like ubuntu using a loop device to extract the
>  > initrd contents of the CD.
>  >
>  > If you look at my configuration file, you will see that I'm not trying
>  > to boot from that, but just using as root, which seems not to work.
>  >
>  > In any case, I'll try a full boot with that distro and maybe convert
>  > it to another format.
>
>  Try this, there crams is enabled:
>  http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080428-cramfs/
>

Thank you Henry, that actually made me get one step further...

Now I'm getting something like this, since it appears the file system
of the initrd is readonly and coLinux initrd is not able to create the
lib directory. into defined root...

Installing modules for coLinux 2.6.22.18-co-0.8.0-SVN1038
Mounting cofs for vmlinux-modules.tar.gz
tar: Cannot create directory `lib/': Read-only file system
tar: Cannot create directory `lib/': Read-only file system
tar: Cannot create directory `lib/': Read-only file system
tar: Cannot create directory `lib/': Read-only file system
tar: Cannot create directory `lib/': Read-only file system
tar: Cannot create directory `lib/': Read-only file system
tar: lib/modules/2.6.22.18-co-0.8.0/kernel/arch/i386/crypto/aes-i586.ko: No such
 file or directory
Closing /
VFS: Mounted root (cramfs filesystem) readonly.
Trying to move old root to /initrd ... /initrd does not exist. Ignored.
Unmounting old root
Trying to free ramdisk memory ... okay
Freeing unused kernel memory: 140k freed

That was from the colinux console, this is from -v 3:

RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on
 cobd3
VFS: Can't find ext3 filesystem on dev cobd3.
VFS: Can't find an ext2 filesystem on dev cobd3.
VFS: Mounted root (cramfs filesystem) readonly.


>  If that not work, then please detect the right type of filesystem of the
>  file "data\gobo\gobo-initrd", for example by booting a Knoppix and than
>  run "file gobo-initrd".
>
>  Should give such output:
>  initrd: Linux rev 1.0 ext2 filesystem data
>  ----------------------^^^^
>  But with other filesystem as "ext2" from my initrd.
>

Results from file:

/opt/gobo-initrd: Linux Compressed ROM File System data, little endian
size 761856 version #2 sorted_dirs CRC 0x14ec9052, edition 0, 441
blocks, 283 files

It seems is quite a challenge get GoboLinux (which doesn't follow FHS)
to work under coLinux... too bad :-(

Thank you for your time and helpful assistance.

-- 
Luis Lavena
Multimedia systems
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Henry N. <Hen...@Ar...>]

Luis Lavena wrote:
> On Mon, Apr 28, 2008 at 7:28 PM, Henry Nestler <Hen...@ar...> wrote:
>> Luis Lavena wrote:
>>  > Thank you Jason for your answer, but the thing is that the kernel that
>>  > cames with coLinux is not possible to mount cromfs/cramfs, even on a
>>  > pre-installed distro like ubuntu using a loop device to extract the
>>  > initrd contents of the CD.
>>  >
>>  > If you look at my configuration file, you will see that I'm not trying
>>  > to boot from that, but just using as root, which seems not to work.
>>  >
>>  > In any case, I'll try a full boot with that distro and maybe convert
>>  > it to another format.
>>
>>  Try this, there crams is enabled:
>>  http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080428-cramfs/
>>
> 
> Thank you Henry, that actually made me get one step further...
> 
> Now I'm getting something like this, since it appears the file system
> of the initrd is readonly and coLinux initrd is not able to create the
> lib directory. into defined root...
> 
> Installing modules for coLinux 2.6.22.18-co-0.8.0-SVN1038

Oh, sorry. I putted some wrong. Kernel and modules are not from same
build. But, does no matter for your problem, the kernel file was ok.
File uploaded as "modules-2.6.22.18-co-0.8.0-SVN1038-20080428.tgz" now.

> Mounting cofs for vmlinux-modules.tar.gz
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: lib/modules/2.6.22.18-co-0.8.0/kernel/arch/i386/crypto/aes-i586.ko: No such
>  file or directory
> Closing /

The messages above are from coLinux "initrd=intrd.gz", that is normal
for cramfs.

> VFS: Mounted root (cramfs filesystem) readonly.
> Trying to move old root to /initrd ... /initrd does not exist. Ignored.
> Unmounting old root
> Trying to free ramdisk memory ... okay
> Freeing unused kernel memory: 140k freed
> 
> That was from the colinux console, this is from -v 3:
> 
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on
>  cobd3
> VFS: Can't find ext3 filesystem on dev cobd3.
> VFS: Can't find an ext2 filesystem on dev cobd3.
> VFS: Mounted root (cramfs filesystem) readonly.

Don't use the initrd.gz from coLinux. This tries to intstall modules in
your cramfs. Cramfs is read only all times.
If you needs modules at some install point later, then install it
manualy with a mount over "cofs0".

You should use only the initrd from Distry for installing. I don't know
how you can stop from installing the distro kernel. For installing the
coLinux kernel you properly needs some hacks in the initrd, look arround
the coLinux-Knoppix boot...

-- 
Henry N.

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Luis L. <lui...@gm...>]

On Tue, Apr 29, 2008 at 5:36 AM, Henry Nestler <Hen...@ar...> wrote:
> Luis Lavena wrote:
>  >
>  > Now I'm getting something like this, since it appears the file system
>  > of the initrd is readonly and coLinux initrd is not able to create the
>  > lib directory. into defined root...
>  >
>  > Installing modules for coLinux 2.6.22.18-co-0.8.0-SVN1038
>
>  Oh, sorry. I putted some wrong. Kernel and modules are not from same
>  build. But, does no matter for your problem, the kernel file was ok.
>  File uploaded as "modules-2.6.22.18-co-0.8.0-SVN1038-20080428.tgz" now.
>

Thank you, downloaded and will check back later.

>
>  > Mounting cofs for vmlinux-modules.tar.gz
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: lib/modules/2.6.22.18-co-0.8.0/kernel/arch/i386/crypto/aes-i586.ko: No such
>  >  file or directory
>  > Closing /
>
>  The messages above are from coLinux "initrd=intrd.gz", that is normal
>  for cramfs.
>
>
>  > VFS: Mounted root (cramfs filesystem) readonly.
>  > Trying to move old root to /initrd ... /initrd does not exist. Ignored.
>  > Unmounting old root
>  > Trying to free ramdisk memory ... okay
>  > Freeing unused kernel memory: 140k freed
>  >
>  > That was from the colinux console, this is from -v 3:
>  >
>  > RAMDISK: Compressed image found at block 0
>  > VFS: Mounted root (ext2 filesystem).
>  > ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on
>  >  cobd3
>  > VFS: Can't find ext3 filesystem on dev cobd3.
>  > VFS: Can't find an ext2 filesystem on dev cobd3.
>  > VFS: Mounted root (cramfs filesystem) readonly.
>
>  Don't use the initrd.gz from coLinux. This tries to intstall modules in
>  your cramfs. Cramfs is read only all times.
>  If you needs modules at some install point later, then install it
>  manualy with a mount over "cofs0".
>
>  You should use only the initrd from Distry for installing. I don't know
>  how you can stop from installing the distro kernel. For installing the
>  coLinux kernel you properly needs some hacks in the initrd, look arround
>  the coLinux-Knoppix boot...
>

Hmn, I got the impression that I needed to use initrd *from* coLinux
with any distro I want t install, but instead setting the root device
to the initrd supplied by my distro from this part of the wiki:

http://colinux.wikia.com/wiki/Full_CD-based%28iso%29_distro_install_and_config_steb-by-step_HOWTO_%28based_on_Xubuntu-7.10%29#THE_CLUE

I'll try again and see how it ends :-P

Thank you for your help.

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams