From: kingler <ki...@gm...> - 2005-11-17 06:50:19
|
I tried using "manually edit the partition table", but I just cannot go pas= t this step. Adding alias for hda1 for the disk image didn't work either. The installer just couldn't find any physical disk and refuses to go beyond the partition step. I am really stuck. :( I also have a native Ubuntu partition which I tried to boot using coLinux. = I got past the booting process and had a kernel panic after loading many drivers including the network adapters. I guess it might be the X-window, and I have tried changing the login mode to text only, but still no luck. |
From: Liang J. <ki...@gm...> - 2005-11-17 23:08:59
|
I got the native Ubuntu partition working, using the guide on Ubuntu forum: http://ubuntuforums.org/showthread.php?p=439988 Thanks for all the advice I got here. Additionally, Henry mentioned to me that the installer may not work at all, but I don't have time to try that yet. The following is the email he sent to me: > I tried using "manually edit the partition table", but I just cannot go > past > this step. > > Adding alias for hda1 for the disk image didn't work either. You know? If you use hda1, then the image file behind should also a image from such partion /dev/hda1, not from the whole disk /dev/hda. That is not only a label naming hda and hda1. > The installer > just couldn't find any physical disk and refuses to go beyond the partition > step. I am really stuck. :( Mostly installers needs a partion table. You can copy the first block of your real harddisk to a file dd if=/dev/hda of=file.img bs=512 count=1 Give this file as image for hda (here hda, and not hda1) so the installer see you partions. For every partion create a separate image file (for hda1, hda2 and so) But mostly, the installer can't run under colinux. The installer search the hardware by some exensive scans. And this mostly not works, hangs or crash colinux. > > I also have a native Ubuntu partition which I tried to boot using coLinux. > I > got past the booting process and had a kernel panic after loading many > drivers including the network adapters. I guess it might be the X-window, > and I have tried changing the login mode to text only, but still no luck. > 1. run colinux first with "root=/dev/hda1 ro init=/bin/sh" (or hda2, your rootfs) This give you a simple console and you can see your image is ok. 2. boot with "root=/dev/hda1 ro init 1" or "init S" for runlevel without loading any drivers and without X. 3. edit the main file for boot proces (/etc/rc.S I think). This is a loop for all other init process in /ect/rc1.d and rc2.d and ... Put a "#!/bin/sh -x" on top of this script for debugging output and perhaps a "sleep 1" in the inner loop. So, you can see all calling task and the stopping process. If you find the problem in one of these sub scripts: Edit this script to, and add also the "-x" to the top line for tracing. That are some of my ideas, I used long time to runs my SuSE 9.3 as partion under colinux. |
From: Kris V. <Kri...@ks...> - 2005-11-18 12:59:42
|
> I was able to enter the installation interface, but I just couldn't go = past > the "partition hard drive" step. I have the preformated 2GB image file > mounted as /target but I don't know how to tell the installer where to > install the files I had exactly the same problem when trying to install Kubuntu 5.10 from=20 scratch under coLinux a few days ago. I managed to continue the installat= ion,=20 by switching to a second console (Alt+F2) and killing the partman (not=20 entirely sure about the name) process. Back in console 1, the installer=20 complained that an error had occurred and that for the installation to=20 continue, the root file system had to be mounted on /target. So I switche= d=20 back to console 2, mounted the root file system there, and then hit Enter= in=20 console 1. After this intervention, I could continue the installation pro= cess=20 as normal... > I also have a native Ubuntu partition which I tried to boot using coLin= ux. > I > got past the booting process and had a kernel panic after loading many > drivers including the network adapters. I guess it might be the X-windo= w, > and I have tried changing the login mode to text only, but still no luc= k. This also happened with my coLinux install. When the base ubuntu distribu= tion=20 was installed, i tried: apt-get install kubuntu-desktop which made coLinux suddenly disappear during the package configuration, a= s=20 well as on subsequent booting, except in single-user mode. A similar prob= lem=20 is mentioned on the XCoLinux page in the Wiki, where it is suggested to u= se=20 coLinux 0.6.3-rc2 (http://firechief.dyndns.org/colinux/binaries/). This=20 indeed made it possible to boot my kubuntu image again (at least most of = the=20 time). > I got the native Ubuntu partition working, using the guide on Ubuntu fo= rum: >=09http://ubuntuforums.org/showthread.php?p=3D439988 I will try to disable the offending services as described in this guide. = That=20 should resolve my remaining problems. Kris --=20 |
From: danny s. <ori...@gm...> - 2005-11-19 14:30:28
|
Okay what we need to do, to get ubuntu and colinux together is the followin= g: Do a minimal install of Ubuntu in a small 2Gb partition. Tune it so it wont break in colinux, test load it, then DD it to an img, compress it and add it to the site. Then add pages to the colinux wiki using this thread, and referencing/using the thread on the ubuntu forums to get a good start going. Now what is worth knowing is how much of a minimal install can be made, which will support a tap connection out of the box, and how configurable it will be in the "ubuntu" user friendly way post install. If I find time in my task list following other projects, I may even attempt some of this stuff myself - it would be good to add another distro to the colinux fold. Should the colinux community be starting to approach Dist guys and getting them to build colinux friendly installers? Is colinux mature enough and got the uptake for it? I would certainly like the installers to cope with colinux without as much faffing about. If we could boot the disk with a parameter, or have an advanced box with questions like "will this be installed for a colinux (or other VM/Nested Native Execution modules)" - which will ensure that hardware probes are skipped, disk partitioning is optionally swapped for building a disk image, and potentially harmful modules (stuff that will definately crash colinux) are not installed by default. Its just a small thought - but to at least start to approach these guys may go a long way to making colinux a more accessible and recognised approach in multi-OS solutions. Please dont flame me on this stuff - its all just suggestions, and I will come clean to say I have little time or are too lazy to actually do this stuff myself right now... Danny On 18/11/05, Kris Vanneste <Kri...@ks...> wrote: > > > I was able to enter the installation interface, but I just couldn't go = past > > the "partition hard drive" step. I have the preformated 2GB image file > > mounted as /target but I don't know how to tell the installer where to > > install the files > > I had exactly the same problem when trying to install Kubuntu 5.10 from > scratch under coLinux a few days ago. I managed to continue the installat= ion, > by switching to a second console (Alt+F2) and killing the partman (not > entirely sure about the name) process. Back in console 1, the installer > complained that an error had occurred and that for the installation to > continue, the root file system had to be mounted on /target. So I switche= d > back to console 2, mounted the root file system there, and then hit Enter= in > console 1. After this intervention, I could continue the installation pro= cess > as normal... > > > I also have a native Ubuntu partition which I tried to boot using coLin= ux. > > I > > got past the booting process and had a kernel panic after loading many > > drivers including the network adapters. I guess it might be the X-windo= w, > > and I have tried changing the login mode to text only, but still no luc= k. > > This also happened with my coLinux install. When the base ubuntu distribu= tion > was installed, i tried: > apt-get install kubuntu-desktop > which made coLinux suddenly disappear during the package configuration, a= s > well as on subsequent booting, except in single-user mode. A similar prob= lem > is mentioned on the XCoLinux page in the Wiki, where it is suggested to u= se > coLinux 0.6.3-rc2 (http://firechief.dyndns.org/colinux/binaries/). This > indeed made it possible to boot my kubuntu image again (at least most of = the > time). > > > I got the native Ubuntu partition working, using the guide on Ubuntu fo= rum: > > http://ubuntuforums.org/showthread.php?p=3D439988 > > I will try to disable the offending services as described in this guide. = That > should resolve my remaining problems. > > Kris > -- > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > Register for a JBoss Training Course. Free Certification Exam > for All Training Attendees Through End of 2005. For more info visit: > http://ads.osdn.com/?ad_idv28&alloc_id=16845&opclick > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > -- Danny Staple MBCS OrionRobots http://orionrobots.co.uk (Full contact details available through website) |
From: Eric S. J. <es...@ha...> - 2005-11-19 16:16:56
|
danny staple wrote: > Okay what we need to do, to get ubuntu and colinux together is the following: > Do a minimal install of Ubuntu in a small 2Gb partition. Tune it so it > wont break in colinux, test load it, then DD it to an img, compress it > and add it to the site. actually, I think we would be better off if we had a reproducible method of creating disk images. It shouldn't be any more complicated than necessary and by that I mean in order of magnitude less complicated than the documented mechanisms on the wiki site today. My experimentation with qemu show that it's very very easy (but very slow) to create a boot image (something like five additional steps over the basic install) but the problem is at the end of the day you have a partitioned file which qemu is not happy about. Apparently from someone else's experience, there are also a few processes it should be stopped. That can be handled with a simple script file in order to make it repeatable and reliable. So now we are up to eight or nine steps additional. *if* someone contributed partition table handling, you would be one step closer to finding out the rest of the production level problems. I'd really like to solve this problem of building new images once and do it as a real product rather than a science club project. life is too short to screw around with things that could be fixed once. I have very little time left for open source work right now but making colinux work for me is very important. I will commit to building one production model based on qemu for the initial disk image and documenting it on the wiki if I can get a partition aware environment. By partition aware, I mean being capable of handling all the normal partitions including swap. although, if there are some advantages to swap in a different partitioned disk image, I can do that too. Just tell me. --- eric |
From: George P B. <geo...@gm...> - 2005-11-22 15:29:39
|
We probably need to replace the cobd block device with one that can handle partitions. QEMU, VMWare, and even UML now support this...=20 Doing this should allow the partition step in installer to work.=20 After that, the X problem is the only other significant problem, and it appears to mostly be fixed in 0.6.3 George On 11/19/05, danny staple <ori...@gm...> wrote: > Should the colinux community be starting to approach Dist guys and > getting them to build colinux friendly installers? Is colinux mature > enough and got the uptake for it? I would certainly like the > installers to cope with colinux without as much faffing about. If we > could boot the disk with a parameter, or have an advanced box with > questions like "will this be installed for a colinux (or other > VM/Nested Native Execution modules)" - which will ensure that hardware > probes are skipped, disk partitioning is optionally swapped for > building a disk image, and potentially harmful modules (stuff that > will definately crash colinux) are not installed by default. Its just > a small thought - but to at least start to approach these guys may go > a long way to making colinux a more accessible and recognised approach > in multi-OS solutions. -- George |
From: peter g. <plugwash@P10Link.net> - 2005-11-22 17:08:42
|
> We probably need to replace the cobd block device with one that can > handle partitions. QEMU, VMWare, and even UML now support this... > Doing this should allow the partition step in installer to work. > After that, the X problem is the only other significant problem, and > it appears to mostly be fixed in 0.6.3 how much impact would this have on existing images? in particular those that use static device nodes. |
From: George P B. <geo...@gm...> - 2005-11-22 21:39:55
|
On 11/22/05, peter green <plu...@p1...> wrote: > > > We probably need to replace the cobd block device with one that can > > handle partitions. QEMU, VMWare, and even UML now support this... > > Doing this should allow the partition step in installer to work. > > After that, the X problem is the only other significant problem, and > > it appears to mostly be fixed in 0.6.3 > how much impact would this have on existing images? in particular those t= hat > use static device nodes. > If my memory serves me correctly the way that it's done in UML detects if partitions exists and does the right thing, else does what it's always done. I maybe wrong, but if not that would be the way to go.=20 If that isn't doable, then it would be a case of getting partitions added to existing images, or perhaps some loopback device trickiness. -- George |
From: kingler <ki...@gm...> - 2005-11-18 16:48:23
|
A slap on the forehead! Kill the partman process?! I should have tried that. Actually I already have the root file system mounted as /target using the second console. So close... Thanks for the advice. I think it definitely worths putting in the wiki pages. -Liang >I had exactly the same problem when trying to install Kubuntu 5.10 from >scratch under coLinux a few days ago. I managed to continue the installation, >by switching to a second console (Alt+F2) and killing the partman (not >entirely sure about the name) process. Back in console 1, the installer >complained that an error had occurred and that for the installation to >continue, the root file system had to be mounted on /target. So I switched >back to console 2, mounted the root file system there, and then hit Enter in >console 1. After this intervention, I could continue the installation process >as normal... > >Kris |