coLinux
Agoeb (talk | contribs)
(→‎Kernel Version: - updated to reflect 0.7.8 should work)
 
(10 intermediate revisions by 5 users not shown)
Line 2: Line 2:
   
 
== Kernel Version ==
 
== Kernel Version ==
The ''mountall ''program used in Ubuntu Karmic uses ''/proc/self/mountinfo'' to ensure partitions are mounted properly. This file has been [http://kernelnewbies.org/Linux_2_6_26 introduced] by the linux kernel version 2.6.26. However, even the coLinux 0.80 development branch uses version 2.6.25 and therefore not provides this file, which causes ''mountall ''to report the following error and to stop the boot process:
+
The ''mountall ''program used in Ubuntu Karmic uses ''/proc/self/mountinfo'' to ensure partitions are mounted properly. This file has been [http://kernelnewbies.org/Linux_2_6_26 introduced] by the linux kernel version 2.6.26. Therefore Ubuntu Karmic is not compatible with coLinux versions prior to 0.7.8.
mountall:/proc: unable to mount: Device or resource busy
 
mountall:/proc/self/mountinfo: No such file or directory
 
mountall start/spawned, process 787
 
mountall: root filesystem isn't mounted
 
init: mountall main process (787) terminated with status 1
 
General error mounting filesystems.
 
A maintenance shell will now be started.
 
CONTROL-D will terminate this shell and re-try.
 
So far I guess there is no solution but to wait for a coLinux kernel refresh. Just in case I'm wrong, I [https://answers.launchpad.net/ubuntu/+source/mountall/+question/89645 asked ]the ''mountall ''maintainers for an alternative solution.
 
   
=== Experimental coLinux kernel 2.6.26.8 ===
+
=== coLinux kernel 2.6.26.8 ===
Thanks to the coLinux mailing list I discovered that there is an [http://www.henrynestler.com/colinux/testing/kernel-2.6.26.8/ experimental coLinux kernel] for download. According to the author, this kernel is widely untested, but seems to run quite well. In my case, the above error message disappeared, the new modules were installed into the Karmic file system, but then the boot process hang:
+
Thanks to the coLinux mailing list I discovered that there is an experimental coLinux kernel for download. According to the author, this kernel is widely untested, but seems to run quite well. The mountinfo issue disappears, the new modules are installed into the Karmic file system, but then the boot process hangs. This issue seems to be missing ''squashfs ''support in the kernel binaries (although ''squashfs ''is provided as a module), which is essential to access the initial ramdisk of Ubuntu Karmic.
  +
* coLinux version 0.7.7 with kernel 2.6.26.8 is released and available on [http://sourceforge.net/projects/colinux/files SourceForge] now
Cooperative Linux Daemon, 0.8.0
 
Daemon compiled on Mon Nov 9 00:35:05 2009
 
 
PID: 4896
 
colinux: booting
 
conet-slirp-daemon: running
 
Linux version 2.6.26.8-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE Linux)) #2 P
 
REEMPT Sun Nov 15 20:34:49 UTC 2009
 
768MB LOWMEM available.
 
Entering add_active_range(0, 0, 196608) 0 entries of 256 used
 
Zone PFN ranges:
 
Normal 0 -> 196608
 
Movable zone start PFN for each node
 
early_node_map[1] active PFN ranges
 
0: 0 -> 196608
 
On node 0 totalpages: 196608
 
Normal zone: 1536 pages used for memmap
 
Normal zone: 0 pages reserved
 
Normal zone: 195072 pages, LIFO batch:31
 
Movable zone: 0 pages used for memmap
 
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 195072
 
Kernel command line: root=/dev/cobd0 ro
 
Enabling fast FPU save and restore... done.
 
Enabling unmasked SIMD FPU exception support... done.
 
Initializing CPU#0
 
Setting proxy interrupt vectors
 
PID hash table entries: 4096 (order: 12, 16384 bytes)
 
Console: colour CoCON 80x25
 
console [tty0] enabled
 
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
 
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
 
Memory: 775040k/786432k available (2079k kernel code, 0k reserved, 628k data, 14
 
8k init, 0k highmem)
 
virtual kernel memory layout:
 
fixmap  : 0xffffa000 - 0xfffff000 ( 20 kB)
 
colinux : 0xfe800000 - 0xffc00000 ( 20 MB)
 
vmalloc : 0xf0800000 - 0xfe7fe000 ( 223 MB)
 
lowmem  : 0xcCPA: page pool initialized 1 of 1 pages preallocated
 
Calibrating delay loop... 3761.76 BogoMIPS (lpj=18808832)
 
Security Framework initialized
 
SELinux: Disabled at boot.
 
Capability LSM initialized
 
Mount-cache hash table entries: 512
 
CPU: L1 I cache: 32K, L1 D cache: 32K
 
CPU: L2 cache: 4096K
 
using mwait in idle threads.
 
CPU: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz stepping 0b
 
Checking 'hlt' instruction... OK.
 
Freeing SMP alternatives: 0k freed
 
net_namespace: 640 bytes
 
NET: Registered protocol family 16
 
SCSI subsystem initialized
 
PCI: Probing PCI hardware
 
PCI: Probing PCI hardware (bus 00)
 
NetLabel: Initializing
 
NetLabel: domain hash size = 128
 
NetLabel: protocols = UNLABELED CIPSOv4
 
NetLabel: unlabeled traffic allowed by default
 
NET: Registered protocol family 2
 
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
 
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
 
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
 
TCP: Hash tables configured (established 131072 bind 65536)
 
TCP reno registered
 
NET: Registered protocol family 1
 
audit: initializing netlink socket (disabled)
 
type=2000 audit(1258357001.470:1): initialized
 
VFS: Disk quotas dquot_6.5.1
 
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
 
cofuse init 0.1 (API version 2.2)
 
msgmni has been set to 1514
 
io scheduler noop registered
 
io scheduler anticipatory registered (default)
 
io scheduler deadline registered
 
io scheduler cfq registered
 
brd: module loaded
 
cobd: loaded (max 32 devices)
 
loop: module loaded
 
conet0: irq 10, HWAddr 00:ff:b2:9d:26:00
 
Driver 'sd' needs updating - please use bus_type methods
 
Driver 'sr' needs updating - please use bus_type methods
 
serio: cokbd at irq 1
 
mice: PS/2 mouse device common for all mice
 
TCP cubic registered
 
NET: Registered protocol family 17
 
Using IPI Shortcut mode
 
input: AT Translated Set 2 keyboard as /devices/serio0/input/input0
 
kjournald starting. Commit interval 5 seconds
 
EXT3-fs: mounted filesystem with ordered data mode.
 
VFS: Mounted root (ext3 filesystem) readonly.
 
Freeing unused kernel memory: 148k freed
 
If anybody has suggestions on this issue, just update this page. Thank you!
 
   
  +
=== coLinux kernel 2.6.33 ===
--
 
  +
* coLinux 0.7.8 containing kernel 2.6.33.5 should be able to run Karmic
* Those binaries don't have SQUASHFS, which is used to create a ram disk with initrd.gz. This ram disk is essential to the boot process.
 
  +
* You can build your own disk image using the instructions from[[Cobootstrap| Cobootstrap]].
/Carlos
 
--
 
 
[[Category:Ubuntu]]
 
[[Category:Ubuntu]]
 
[[Category:Distributions]]
 
[[Category:Distributions]]

Latest revision as of 15:10, 22 February 2011

This page should be used to collect information on how to use the current Ubuntu version 9.10 Karmic Koala with coLinux.

Kernel Version[]

The mountall program used in Ubuntu Karmic uses /proc/self/mountinfo to ensure partitions are mounted properly. This file has been introduced by the linux kernel version 2.6.26. Therefore Ubuntu Karmic is not compatible with coLinux versions prior to 0.7.8.

coLinux kernel 2.6.26.8[]

Thanks to the coLinux mailing list I discovered that there is an experimental coLinux kernel for download. According to the author, this kernel is widely untested, but seems to run quite well. The mountinfo issue disappears, the new modules are installed into the Karmic file system, but then the boot process hangs. This issue seems to be missing squashfs support in the kernel binaries (although squashfs is provided as a module), which is essential to access the initial ramdisk of Ubuntu Karmic.

  • coLinux version 0.7.7 with kernel 2.6.26.8 is released and available on SourceForge now

coLinux kernel 2.6.33[]

  • coLinux 0.7.8 containing kernel 2.6.33.5 should be able to run Karmic
  • You can build your own disk image using the instructions from Cobootstrap.