Re: Multihead in Debian/Debian-based distro and 64-bits?

[drbista <dr...@ep...>]

On Saturday 08 January 2005 7:55, you wrote:
> --- drbista <dr...@ep...> wrote:
> > On Friday 07 January 2005 7:55, you wrote:
>
> <snip>
>
> > A peculiar question, does the patched kernel
> > (
>
> http://www.c3sl.ufpr.br/multiterminal/kernel-image-2.6.7-ruby.tar.bz2)
>
> > at
> > http://www.c3sl.ufpr.br/fourhead/howto-en.php when
> > installed with dpkg -i
> > command would install in parallel with the existing
> > 2.6.7 kernel or replace
> > the existing one? Any idea?
>
> If /lib/modules now has /2.6.7 then after installing
> what you cite with dpkg -i would probably install
> 2.6.7-ruby. But you can tell beforehand by examining
> the .deb see man deb.
>
> In any case I had better results with 2.6.9 Ruby, but
> that was with a regular 32 bit kernel of course.
>
> In Debian compiling a kernel is trivial with the
> kernel-package package. Perhaps you know. "make-kpkg
> --revision 1 kernel_image" gets you the deb in the
> /usr/src dir. Get the .config file from /boot and
> adjust with make menuconfig in a vc.
>
> With 2.6.9 I was able to use the Debian source of the
> kernel and use Ruby (i.e the 2.6.9 vanilla kernel and
> the Debian patches added) but it will depend on the
> kernel and if it does not fit you will have to use the
> vanilla kernel. Sorry if this has been said already
> and I am duplicating information. Aivils seems to
> think that the main problem is the video cards. If I
> were to do it over again I would first experiment with
> many of those. As it is I only have 2 nVidia cards, so
> funny looking garbage remains a questionmark...
>
>
> HTH
> H
>
> > I wrote to the c3sl but yet to get any response for
> > the last 48 hours! :-(
> >
> > Thanks for help.
> >
> > Dr. Sichendra Bista
>

I tried to install the precompiled kernel 
( http://www.c3sl.ufpr.br/multiterminal/kernel-image-2.6.7-ruby.tar.bz2) and 
it get installed as a parallel kernel, but it gave some errors like below:

<QUOTE>
# dpkg -i kernel-image-2.6.7-ruby_10.00.Custom_i386.deb 
Selecting previously deselected package kernel-image-2.6.7-ruby.
(Reading database ... 115039 files and directories currently installed.)
Unpacking kernel-image-2.6.7-ruby (from 
kernel-image-2.6.7-ruby_10.00.Custom_i386.deb) ...

You are attempting to install an initrd kernel image (version
2.6.7-ruby) but you do not seem to have a mkinitrd command in the
path. This will break the installation, unless initrd-tools are also
being installed right now.


Could not find mkinitrd in path. at /var/lib/dpkg/tmp.ci/preinst line 189.

You are attempting to install an initrd kernel image (version 2.6.7-ruby)
This will not work unless you have configured your boot loader to use
initrd. (An initrd image is a kernel image that expects to use an INITial
Ram Disk to mount a minimal root file system into RAM and use that for
booting).

   As a reminder, in order to configure LILO, you need
   to add an 'initrd=/initrd.img' to the image=/vmlinuz
   stanza of your /etc/lilo.conf

I repeat, You need to configure your boot loader -- please read your
bootloader documentation for details on how to add initrd images.

If you have already done so, and you wish to get rid of this message,
please put
  "do_initrd = Yes"
in /etc/kernel-img.conf. Note that this is optional, but if you do not,
you will continue to see this message whenever you install a kernel
image using initrd.
Do you want to stop now? [Y/n]n

(I tried to continue with the n option and got the following)

Setting up kernel-image-2.6.7-ruby (10.00.Custom) ...
Failed to create initrd image.
dpkg: error processing kernel-image-2.6.7-ruby (--install):
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 kernel-image-2.6.7-ruby

<UNQUOTE>

However, I added the necessary lines with dumbcon=1 (as I had had 2 consoles) 
in /boot/grub/menu.lst as below:

title MEPIS at hda7, kernel 2.6.7-ruby
kernel (hd0,6)/boot/vmlinuz-2.6.7-ruby root=/dev/hda7 nomce psmouse.proto=imps 
quiet splash=verbose vga=791 dumbcon=1 
initrd (hd0,6)/boot/initrd.mepis 

And when trying to boot in the ruby image, it gave me kernel panic error 
saying the kernel could not find the place to mount....

Any idea? Thanking you in anticipation,

Webocratically yours,
Dr. Sichendra Bista, Chief Architect and Secreatary General
eParliament.org: The Pioneering OPERATIONAL Model of Webocracy
Founder and President, Global Initiatives International Secretariat
GPO Box 10422, Kathmandu, Nepal. Web: http://giis.netfirms.com/anupa.htm
Tel: +977 (1) 478 1160/478 2321    Web: http://www.eParliament.org
Fax: +977 (1) 478 2321             Email: dr...@eP...
--------------------------------------------------------------------
  Peace  |  Justice  |  Human Rights  |  Democracy  |  Development
--------------------------------------------------------------------