Menu
▾
▴
[coLinux-devel] [ colinux-Support Requests-2485983 ] Booting a WUBI image from c:\ drive in CoLinux
|
From: SourceForge.net <no...@so...> - 2011-11-14 04:10:12
|
Support Requests item #2485983, was opened at 2009-01-04 10:17 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=2485983&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Install Problem (example) Group: v1.0 (example) Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Booting a WUBI image from c:\ drive in CoLinux Initial Comment: I am trying to boot an image that was installed by WUBI on my C:\ drive. If someone could help me get this working, then Linux would basically run natively from within Windows without requiring any new partitions. That would be awesome. WUBI puts its linux image in the location C:\ubuntu\disks\root.disk So I modified the example.conf file to say cobd0="C:\ubuntu\disks\root.disk" But alas it does not boot properly. I have included a dump from the screen of what colinux-daemon.exe outputs when it is trying to boot. It just repeats request_module: runaway loop modprobe binfmt-464c a few times and then hangs. I think it is to do with the line ReiserFS: cobd0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on cobd0 that comes up when it is booting. I think this may be because I left the root pointing to root=/dev/cobd0 in the example.conf file when maybe WUBI takes it from somewhere else. Help would be greatly appreciated!! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2011-11-13 20:10 Message: xAQNqp <a href="http://cpbjululitut.com/">cpbjululitut</a>, [url=http://roxysqtlpnnw.com/]roxysqtlpnnw[/url], [link=http://jukzysqzlppt.com/]jukzysqzlppt[/link], http://dafvohvgmwmi.com/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2011-11-12 18:15 Message: C57y6j <a href="http://jkulkomlptml.com/">jkulkomlptml</a>, [url=http://winkpkkpslyi.com/]winkpkkpslyi[/url], [link=http://nzfomcftryvd.com/]nzfomcftryvd[/link], http://lhukpsbummxo.com/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-11 07:30 Message: Thak you again for the explanation of the modules usage. With the X11VNC server instead the vino VNC server the "problems" with the mouse pointer are solved. As I learned, the X11VNC with the xRDP module is the best combination, and the function of the X11VNC server is highly configurable. If the developer of the xRDP module support not only the remote X server function, and also all the other functions as remote audio, clipboard and so on, this will be a easy solution for coLinux under Windows. I'm awaiting the next 0.5(.1) versions of xRDP, which will have more RDP functions. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-10-11 05:06 Message: If you don't missing functionals, then you can leave it so. Typically needs modules for iptables, ipv6, additional linux filesystems or raid/lvm and for NLS (code pages). You can install modules. It is harmless for your dual boot, because coLinux modules resides in a separate directory with "-co-" in the name. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-11 00:55 Message: Henry, many thanks for your support. You are right, I will write a Wiki entry in the next days. I must do some additional tests, because the cursor follows very slow and inacurate the mouse moving. This is a known problem with the vino VNC server and the gnome desktop. But it gives some other VNC servers which can "shadow" a running desktop. The other "problem" is, that the "dummy" video device for the X server under coLinux "steals" the coLinux console output (the console display goes black and comes back, if the Linux will be shutdown). Additional I have one question about the coLinux modules: Therefore are the coLinux modules and must they be installed? I have done all the trials without the installed coLinux modules, because I cannot say what they do at the native dual-booted Linux. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-10-10 13:33 Message: Because this Support Requests are not frequently used as knowledge base from users, it would be nice to have your text in the Wiki, for example as new page "xrdp" ( http://colinux.wikia.com/wiki/Special:CreatePage ) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-10 11:08 Message: .Just I have the WUBI installed Ubuntu 8.04LTS fully functional working with coLinux and xRDP under Windows and as dual-boot Windows/Ubuntu system. I dont know, that this is the right or best way, because I dont have as a Windows user any expirences with Linux. But as I have seen, that the remote desktop solution of Ubuntu with the vino VNC server dont start any new X session and only "shadow" the running Ubuntu system remotly, than I have had the right idea for coLinux with the XRDP connection: As I have say to install the tightvncserver for the RDP connection, this was not the right solution, because the tightvncserver starts a new remote X session. 1. Configure the dual-booted native Ubuntu 8.04LTS for the remote desktop access and without the installation of the tightvncserver (the vino VNC server is installed at Ubuntu 8.04LTS). 2. Configure the auto login. 3. Install the XRDP package. 4. Edit as a root user the /etc//xrdp/startwm.sh file, so that startwm.sh nothing do (outcomment all lines), because we will not start any new X session, e.g.: #!/bin/sh # . /etc/X11/Xsession 5. Edit as a root user the /etc//xrdp/xrdp.ini file, so that the RDP port is not 3389 (e.g. 3390) and the first xrdp section have the right values for the vino VNC server, e.g.: [globals] bitmap_cache=yes bitmap_compression=yes port=3390 crypt_level=low channel_code=1 [xrdp1] name=vino-VNC lib=libvnc.so username=ask password=ask ip=127.0.0.1 port=5900 6. Edit as a root user the /etc/gdm/gdm.conf file, so that the X server will not be started direct, but with the "wrapper" shell script gdm-startx. Do this at the section for the X server definitions and leave the original X server start parameter, e.g.: # X Server Definitions # # Note: Is your X server not listening to TCP requests? Refer to the # security/DisallowTCP setting! [server-Standard] name=Standard server command=/etc/gdm/gdm-startx -br -audit 0 flexible=true 7. Create the right /etc/gdm/gdm-startx shellscipt, e.g.: #!/bin/sh # # start the X server with the "Default" layout # if the system is nativly booted LAYOUT=Default # if the system is started with the coLinux # kernel, than start the X server with the # "coLinux" layout if uname -r | grep -qe "-co-" then LAYOUT=coLinux fi # # run the Xserver with the args that were passed exec X -layout $LAYOUT $* 8. Edit as a root user the /etc/X11/xorg.conf file and rename the original "Default Layout" into the single word identifier "Default", add the "dummy" driver as the "coLinux" device, add a "Generic Monitor" for the use with coLinux, add screen defination for coLinux and last the X server layout for coLinux, e.g.: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "de" Option "XkbOptions" "lv3:ralt_switch" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" EndSection Section "Device" Identifier "Configured Video Device" EndSection Section "Device" Identifier "coLinux Video Device" Driver "dummy" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Monitor" Identifier "Generic Monitor" HorizSync 30 - 85 VertRefresh 50.0 - 160.0 DisplaySize 289 203 EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" EndSection Section "Screen" Identifier "coLinux Screen" Device "coLinux Video Device" Monitor "Generic Monitor" Defaultdepth 24 SubSection "Display" Depth 24 Modes "1600x1200" "1280x1024" "1024x768" "800x600" "720x400" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default" Screen "Default Screen" EndSection Section "ServerLayout" Identifier "coLinux" Screen "coLinux Screen" EndSection With the other adaptions of the configuration files (as at the Wiki for the WUBI with coLinux) you can just (dual-)boot the Windows system and use the same WUBI generated imgage files for the start with coLinux under Windows. The "Remote Desktop Connection" from Windows can be done with the Windows terminal server client, which is included at any Windows installation or can be downloaded from Microsoft. All Ubuntu 8.04LTS functions are working under coLinux (including the administrative tasks, e.g. the Synaptic package manager), as they are working under the native Ubuntu 8.04.LTS. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-10-05 13:13 Message: My idea is, run "xhost +" as the user, than the Xserver should allow the access to current session. Moving or copying the file .Xauthority would not help you, I think. In this file was stored which user was logged in and this exist on the Xserver - on the Windows maybe in your case. Run "xauth -v" and give the commands "info" and "list" to see what 's going on. compaire it with your native Ubuntu. Leave this tool with "quit". Sorry, that I don't know, ho you can add an entry there. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-05 10:13 Message: I have one "little" problem: At the coLinux started WUBI installed Ubuntu system I cannot do any administrative action (run Synaptic etc.), because a Xauthority error: "Cannot copy the .xauthority file" (or so). I have read some tips for that error; "As root copy the root .xauthority file into the users home directory" (but the root have not such file) and so on. The (dual-) booted native WUBI installed Ubuntu is fully functional without any error, and I can use rdesktop to build a (local) XRDP/tightvnc server session, which is fully functional too. This error comes from the GDM login, as I understand it right, but as a Windows user with little Linux knowledge I cannot figure out this problem. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-03 06:02 Message: Just I have the right language at the Gnome-Desktop for the XRDP session: You must export the language variable before the start of the X sessin at the startwm.sh shell-scrip under /etc//xrdp/ so that this would be: #!/bin/sh . /etc/default/locale export LANG . /etc/X11/Xsession ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-02 10:30 Message: The most problems with XRDP sessions comes from the crashing gnome-settings-daemon and this can be solved, if you disables the keyboard and mouse plugins with the gconf-editor startet at the terminal console. The plugins will be found at gconf-editor tree /apps/gnome_settings_daemon/plugins. Deactivate the two plugins keyboard and mouse and then the gnome-settings-daemon dont crashes at XRDP sessions. My German keyboard is then a German keyboard and only the Gnome-Panel language is reverted to English. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-01 11:17 Message: A RDP connection from Windows into running coLinux/Ubuntu is simple: 1. Install under the nativ (dual-)booted Ubuntu with Synaptic xRDP server and the tightvncserver. 2. Change the default RDP port from 3389 into 3390 (e.g.) at the /etc/xrdp/xrdp.ini file. 3. Restart the computer into the dual-booted Windows system. 4. Add at the coLinux start configuration the portforewarding for the 3390 port, e.g. if you use the SLIRP network configuration. 5. Start the coLinux/Ubuntu and then start the Microsoft Terminal Server Client (Remote Desktop Connection). Use as the computer name the connection IP and the right port, e.g. 127.0.0.1:3390 for the SLIRP network connection into coLinux. The port number change must be done for the SLIRP network, because Windows has a own RDP server at port 3389 (the standard RDP port). Just I have some little problems (not installed modules under coLinux/Ubuntu, some error messages at the coLinux/Ubuntu start) and one greater problem: the xRDP session uses not the right keyboard mapping and not the the right language settings (English settings and not the German settings). But these problems with xRDP are known. One note to xRDP with Ubuntu 8.04LTS: This is a older version 0.4.0 of the xRDP server and cannot used with the newer Microsoft RDP clients of Windows Vista or Windows XP with SP3. It gives a newer version of the xRDP server, but not as a DEB package for Ubuntu. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-01 10:05 Message: Just I have the WUBI installed Ubuntu 8.04LTS running with coLinux. I can dual-boot the native Ubuntu, or the native Windows, or the native Windows with coLinux/Ubuntu. The starting X-server with coLinux was the problem! To solve this problem, two things must be done: 1. Edit the /etc/gdm/gdm.conf file as superuser (or root) and start not the X server direct and use for this a shell script gdm-startx (e.g.). Under the server section of the gdm.conf (near the file end) you 'll find this: .... [server-Standard] name=Standard server command=/usr/bin/X -br -audit 0 flexible=true .... Change the command=/usr/bin/X -br -audit 0 into command=/etc/gdm/gdm-startx -br -audit 0 2. Build the shell script gdm-startx at the same directory (/etc/gdm) with the following content: #!/bin/sh # # to skip the Xserver under coLinux boot. if uname -r | grep -qe "-co-" then exit 0 fi # # run the Xserver with the args that were passed exec X $* This is all to stop the start of the X-server only if you start the WUBI installed Ubuntu 8.04LTS under coLinux, but not if the Ubuntu 8.04LTS ist nativly running, thanks the dual-boot WUBI installed Ubuntu. The next try would be for me to get the RDP connection from Windows into the coLinux/Ubuntu running. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-09-30 07:57 Message: The swap file is working at coLinux: As stated at the Wiki for the dual-boot conversion, the fstab file must be edited, but you must not distinguish between nativ/dual-booted and the coLinux system. It is sufficient to append the colinux entries at the fstab file: # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /host/ubuntu/disks/root.disk / ext3 loop,errors=remount-ro 0 1 /host/ubuntu/disks/boot /boot none bind 0 0 /host/ubuntu/disks/swap.disk none swap loop,sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0 /dev/cobd0 / ext3 errors=remount-ro 0 1 /dev/cobd1 none swap sw 0 0 The first lines are the original WUBI entries and the last two lines are the coLinux entries. The nativ Linux kernel of the dual-booted system dont know the coLinux entries and vice versa. The coLinux entries could be appended with a script file, e.g. and this is simpler for the most Windows users. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-09-29 22:38 Message: >But, 8.04 is not installable via WUBI. No download server is available after the start of latest Wubi-8.04.431. You 'll find the the latest Ubuntu LTS version 8.04.3 desktop CD download at http://www.ubuntu.com/getubuntu/download and the functional WUBI installer is included at this CD image. But you are right. newer versions of WUBI cannot install older versions of Ubuntu. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-09-29 11:52 Message: > or from the Radeon driver for the Xserver The Xserver should not load. ;-( If the "text" does not work, then locate (search) for other bootparameters for text mode. Grep for the passage "/proc/cmdline" in all files under /etc/init.d/. Near this line you should find how the text mode was detected. Try to skip /etc/init.d/gdm completely by adding follow line near top of this file: uname -r | grep -qe "-co-" && exit 0 Don't worry about low memory. Text only mode don't need so mutch memory. But, with small tricky you can add the swap for coLinux only: uname -r | grep -qe "-co-" && swapon /dev/cobd1 Add this line some there in any of the early boot scripts, for example into the script what does call "mount -a". Sorry, that I can not help better. But, 8.04 is not installable via WUBI. No download server is available after the start of latest Wubi-8.04.431. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-09-29 10:51 Message: This works in my situation with Ubuntu 8.04LTS: > to stop the GUI (gnome-desktop) at Ubuntu Add the word "single" (without quotes) into coLinux config, This boot parameter got me a Recovery Menu , where I can "Drop to root shell prompt". This I have found for Ubuntu 8.10. And this was/is the only boot parameter, which gives the root shell console. The other boot parameters "nosplash" or/and "text" dont solve the problem. Because I can just "Drop to root shell prompt", I can try somethings to solve the problem with the "core dunp". I found nothings at the LOG files what crashs and I cannot see a displayed crash messages at the FLTK or NT console of colinux. But I think the problem comes from the missing swap file or low RAM for a full Ubuntu (my PC have only 512MB RAM), or from the Radeon driver for the Xserver. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-09-29 05:40 Message: Henry, many thanks for your support and all the suggestions. Sorry for the late answer, but I dont have had the time, but just I'll try to get WUBI installed Ubuntu running with coLinux. By the side, coLinux is a great work! Thank you for the time, that you spend for this project and the support. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-09-26 16:40 Message: Add "text" to the boot parameter in coLinux config. This should skip loading GDM to have a text only system. Add "nosplash". Maybe this produce the error. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-09-26 13:54 Message: > to stop the GUI (gnome-desktop) at Ubuntu Add the word "single" (without quotes) into coLinux config, This boot parameter got me a Recovery Menu , where I can "Drop to root shell prompt". This I have found for Ubuntu 8.10. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-09-24 14:49 Message: First, if you want to boot in DualBoot, then don't change the /etc/fstab!!! coLinux would run with the original too. Perhaps you would have no swap, so you needs to add and script for coLinux bootup and add a line like "swapon /edv/cobd1" The output on FLTK is not normal, I think. This are memory maps for used libraries. Perhaps any binary is faulting and Ubuntu prints a core dump about used libs? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-09-24 09:23 Message: It's not simple to stop the GUI (gnome-desktop) at Ubuntu, because Ubuntu (Debian?) uses the runlevels not in the Linux typically manner. Ubuntu have only the runlevel 1 and 2 at booting, and runlevels 3...5 are all the same as runlevel 2. But thanks the dualboot functionality of the WUBI installed Ubuntu, I can boot into the native Ubuntu and inspect the log files. I have seen at the log files part foir the coLinux boot, that the conet network interface is fully configured, e.g. the ndis-bridged conet interface get the right IPs automatically from the DHCP server at the ADSL router. I think too, that the problem is the start of the Xserver and/or the gnome-desktop (with the activated auto-logon at Ubuntu). I'll try to modify the start-scripts of Ubuntu, as described at the Wiki for the WUBI/Dualboot conversion, at the running native Ubuntu. I hope/think, that than it should be possible to get a working dualboot WUBI installation and with a working coLinux with the same WUBI image. For your informations, this are the last messages at the FLTK console: b7b50000-b7b59000 r-xp 00000000 75:00 58425 /usr/lib/libdrm.so.2.3.0 b7b59000-b7b5a000 rw-p 00008000 75:00 58425 /usr/lib/libdrm.so.2.3.0 b7b65000-b7b6d000 r-xp 00000000 75:00 123412 /usr/lib/xorg/modules/extensions/libdri.so b7b6d000-b7b6e000 rw-p 00007000 75:00 123412 /usr/lib/xorg/modules/extensions/libdri.so b7b6e000-b7b74000 r-xp 00000000 75:00 123415 /usr/lib/xorg/modules/extensions/librecord.so b7b74000-b7b75000 rw-p 00005000 75:00 123415 /usr/lib/xorg/modules/extensions/librecord.so b7b75000-b7bc5000 r-xp 00000000 75:00 123414 /usr/lib/xorg/modules/extensions/libglx.so b7bc5000-b7bc9000 rw-p 0004f000 75:00 123414 /usr/lib/xorg/modules/extensions/libglx.so b7bc9000-b7bca000 rw-p b7bc9000 00:00 0 b7bca000-b7be8000 r-xp 00000000 75:00 123413 /usr/lib/xorg/modules/extensions/libextmod.so b7be8000-b7be9000 rw-p 0001e000 75:00 123413 /usr/lib/xorg/modules/extensions/libextmod.so b7be9000-b7c32000 r-xp 00000000 75:00 123345 /usr/lib/xorg/modules/libpcidata.so b7c32000-b7c50000 rw-p 00049000 75:00 123345 /usr/lib/xorg/modules/libpcidata.so b7c50000-b7c51000 rw-p b7c50000 00:00 0 b7c51000-b7c65000 r-xp 00000000 75:00 212368 /lib/tls/i686/cmov/libpthread-2.7.so b7c65000-b7c67000 rw-p 00013000 75:00 212368 /lib/tls/i686/cmov/libpthread-2.7.so b7c67000-b7c6a000 rw-p b7c67000 00:00 0 b7c6a000-b7c7e000 r-xp 00000000 75:00 59090 /usr/lib/libz.so.1.2.3.3 b7c7e000-b7c7f000 rw-p 00013000 75:00 59090 /usr/lib/libz.so.1.2.3.3 b7c7f000-b7ce9000 r-xp 00000000 75:00 58481 /usr/lib/libfreetype.so.6.3.16 b7ce9000-b7cec000 rw-p 0006a000 75:00 58481 /usr/lib/libfreetype.so.6.3.16 b7cec000-b7e35000 r-xp 00000000 75:00 212354 /lib/tls/i686/cmov/libc-2.7.so b7e35000-b7e36000 r--p 00149000 75:00 212354 /lib/tls/i686/cmov/libc-2.7.so b7e36000-b7e38000 rw-p 0014a000 75:00 212354 /lib/tls/i686/cmov/libc-2.7.so b7e38000-b7e3b000 rw-p b7e38000 00:00 0 b7e3b000-b7e45000 r-xp 00000000 75:00 195136 /lib/libgcc_s.so.1 b7e45000-b7e46000 rw-p 0000a000 75:00 195136 /lib/libgcc_s.so.1 b7e46000-b7e4d000 r-xp 00000000 75:00 212370 /lib/tls/i686/cmov/librt-2.7.so b7e4d000-b7e4f000 rw-p 00006000 75:00 212370 /lib/tls/i686/cmov/librt-2.7.so b7e4f000-b7e72000 r-xp 00000000 75:00 212358 /lib/tls/i686/cmov/libm-2.7.so b7e72000-b7e74000 rw-p 00023000 75:00 212358 /lib/tls/i686/cmov/libm-2.7.so b7e74000-b7e75000 rw-p b7e74000 00:00 0 b7e75000-b7e79000 r-xp 00000000 75:00 58237 /usr/lib/libXdmcp.so.6.0.0 b7e79000-b7e7a000 rw-p 00003000 75:00 58237 /usr/lib/libXdmcp.so.6.0.0 b7e7a000-b7eae000 r-xp 00000000 75:00 58324 /usr/lib/libdbus-1.so.3.4.0 b7eae000-b7eb0000 rw-p 00033000 75:00 58324 /usr/lib/libdbus-1.so.3.4.0 b7eb0000-b7ebf000 r-xp 00000000 75:00 58720 /usr/lib/libhal.so.1.0.0 b7ebf000-b7ec0000 rw-p 0000e000 75:00 58720 /usr/lib/libhal.so.1.0.0 b7ec0000-b7ee8000 r-xp 00000000 75:00 58902 /usr/lib/libpixman-1.so.0.10.0 b7ee8000-b7ee9000 rw-p 00027000 75:00 58902 /usr/lib/libpixman-1.so.0.10.0 b7ee9000-b7eed000 r-xp 00000000 75:00 58475 /usr/lib/libfontenc.so.1.0.0 b7eed000-b7eee000 rw-p 00004000 75:00 58475 /usr/lib/libfontenc.so.1.0.0 b7eee000-b7ef0000 r-xp 00000000 75:00 58226 /usr/lib/libXau.so.6.0.0 b7ef0000-b7ef1000 rw-p 00001000 75:00 58226 /usr/lib/libXau.so.6.0.0 b7ef1000-b7ef2000 rw-p b7ef1000 00:00 0 b7ef2000-b7f4a000 r-xp 00000000 75:00 58245 /usr/lib/libXfont.so.1.4.1 b7f4a000-b7f50000 rw-p 00058000 75:00 58245 /usr/lib/libXfont.so.1.4.1 b7f50000-b7f57000 rw-p b7f50000 00:00 0 b7f57000-b7f59000 r-xp 00000000 75:00 212357 /lib/tls/i686/cmov/libdl-2.7.so b7f59000-b7f5b000 rw-p 00001000 75:00 212357 /lib/tls/i686/cmov/libdl-2.7.so b7f5f000-b7f60000 r-xp 00000000 75:00 123417 /usr/lib/xorg/modules/fonts/libfreetype.so b7f60000-b7f61000 rw-p 00000000 75:00 123417 /usr/lib/xorg/modules/fonts/libfreetype.so b7f61000-b7f65000 r-xp 00000000 75:00 123411 /usr/lib/xorg/modules/extensions/libdbe.so b7f65000-b7f66000 rw-p 00003000 75:00 123411 /usr/lib/xorg/modules/extensions/libdbe.so b7f66000-b7f68000 rw-p b7f66000 00:00 0 b7f68000-b7f82000 r-xp 00000000 75:00 195084 /lib/ld-2.7.so b7f82000-b7f84000 rw-p 00019000 75:00 195084 /lib/ld-2.7.so bf8c1000-bf8d6000 rw-p bf8c1000 00:00 0 [stack] ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso] ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-09-23 15:12 Message: Maybe you tries to boot coLinux with GUI in runlevel 3? Set the default runlevel 2. After it's stopping, please close the FLTK console (right top cross), and run colinux-console-nt.exe, to have copy & paste with left mouse menu. Please post here the last lines from this console. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-09-23 10:06 Message: Many thanks henry for youre response. I have solved the udev-persitent eth0/eth2 renaming, but the problem is the same. I have tried the ndis-bridge network interface, but the problem is the same too. At the FLTK console I see some library loading information, but not other at the stopping end. If the dispayed messages are important, I can post this here. Just I'll try the WUBI converting instruction for Ubuntu 8.10, but this is not a LTS version of Ubuntu and I'm more interrested at the LTS versions. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-09-22 12:11 Message: You need to find a way, that you can see the hanging script name. I don't know exactly how you can do it with Ubuntu. It should be exist a boot parameter or a setting in some of the /etc files to print more verbose about the booting scripts. I see "udev: renamed network interface eth0 to eth2" there, that says, you have not fixed the udev rule script. Add the bypass for coLinux. Check the coLinux boot. If not helps, maybe the network script hangs on non existing interface? What network interface you have on normal boot of wubi? Use the same (eth0 or eth1) under coLinux. If you need a second network, add a network with ndis-bridge (and the name of your real network card) to colinux.conf. Try SSH login: Replace the "eth0=slirp" with "eth0=slirp,,tcp:22:22". Boot Wubi in normal mode and setup a SSH server. Than boot coLinux and try to login via SSH from Windows to "localhost" port 22. (Yes SLiRP is listen on localhost.) Have you a FLTK console and it contains the same kernel messages, you have printed here? Ends FLTK with same message? Maybe Ubuntu has an error console on tty9 or tty10? Try ALT-F9 and ALT-F10 to switch the consoles. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-09-21 23:34 Message: I try this with a Ubuntu Hardy 8.04.3LTS WUBI installation as it would be described at the coLinux Wiki. But I dont get the linux console with the login prompt. The coLinux sart should be stopped at/after the network initialization: C:\Programme\coLinux>colinux-daemon kernel=vmlinux cocon=100x60 cobd0=v:\ubuntu\ disks\root.disk cobd1=v:\ubuntu\disks\swap.disk root=/dev/cobd0 eth0=slirp cofs0 =. cofs1=v:\ubuntu\disks\boot Cooperative Linux Daemon, 0.7.4 Daemon compiled on Wed Apr 15 18:59:08 2009 PID: 2856 colinux: booting Linux version 2.6.22.18-co-0.7.4 (hn@hn-dt) (gcc version 4.2.1 (SUSE Linux)) #1 PREEMPT Wed Apr 15 18:57:39 UTC 2009 128MB LOWMEM available. Entering add_active_range(0, 0, 32768) 0 entries of 256 used Zone PFN ranges: Normal 0 -> 32768 early_node_map[1] active PFN ranges 0: 0 -> 32768 On node 0 totalpages: 32768 Normal zone: 256 pages used for memmap Normal zone: 0 pages reserved Normal zone: 32512 pages, LIFO batch:7 Built 1 zonelists. Total pages: 32512 Kernel command line: root=/dev/cobd0 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: 512 (order: 9, 2048 bytes) Console: colour CoCON 100x60 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 125824k/131072k available (1955k kernel code, 0k reserved, 560k data, 13 6k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffffc000 - 0xfffff000 ( 12 kB) vmalloc : 0xc8800000 - 0xffffa000 ( 887 MB) lowmem : 0xc0000000 - 0xc8000000 ( 128 MB) .init : 0xc0378000 - 0xc039a000 ( 136 kB) .data : 0xc02e8f28 - 0xc0374fe4 ( 560 kB) .text : 0xc0100000 - 0xc02e8f28 (1955 kB) Calibrating delay loop... 24117.24 BogoMIPS (lpj=120586240) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 078bfbff e1d3fbff 00000000 00000000 00000000 00000000 00000001 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU: After all inits, caps: 078bfbff e1d3fbff 00000000 00000410 00000000 0000000 0 00000001 Compat vDSO mapped to ffffe000. CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 00 Checking 'hlt' instruction... OK. NET: Registered protocol family 16 SCSI subsystem initialized PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) NET: Registered protocol family 2 conet-slirp-daemon: running IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered audit: initializing netlink socket (disabled) audit(1253600152.750: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) io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize cobd: loaded (max 32 devices) loop: module loaded conet0: irq 10, HWAddr 00:ff:81:f3:46:20 serio: cokbd at irq 1 mice: PS/2 mouse device common for all mice input: Cooperative Mouse as /class/input/input0 comouse: initialized. TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI Shortcut mode input: AT Translated Set 2 keyboard as /class/input/input1 kjournald starting. Commit interval 5 seconds EXT3 FS on cobd0, internal journal EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem). Freeing unused kernel memory: 136k freed udev: renamed network interface eth0 to eth2 fuse init (API version 7.8) EXT3 FS on cobd0, internal journal ip_tables: (C) 2000-2006 Netfilter Core Team NET: Registered protocol family 10 lo: Disabled Privacy Extensions eth2: no IPv6 routers present What can I do? The WUBI installed Ubuntu runs without any problems, and I have installed the XRDP package at Ubuntu, I can get the RDP connection from Windows into the Ubuntu. My intention is to use the Windows RDP client to get the Ubuntu desktop from the running coLinux/Ubuntu system. I have made the same with the Thinstuff LX Server a long time ago, and it was fully functional in the combination with a coLinux/Ubuntu 6.06 system, but the Thinstuff LX Server is a dicontinued product and dont be fully functional after the Ubuntu upgrade to Ubuntu 8.04. It would be nice, to get a RDP connection with the Ubuntu 8.04 system, because a RDP client hase all Windows versions since Windows 2000, and you dont install some other programs (VNCviewer, Cygwin, Xming ...) to get a Linux desktop at the Windows machine. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-06-27 14:30 Message: Complete howto exist at Wiki now: http://colinux.wikia.com/wiki/Wubi ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-04-19 11:42 Message: Hi, did anything else transpired on this effort? I am willing to help move this idea forward as I believe it has value. I have about ten different PCs I can use to test this if I can make it work. So before I start I would like to know if there was any progress since January when this was initially posted. Thanks! Sergio. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-04 11:22 Message: Oh, sorry, have not seen your attchement. Please forget the scsi stuff. cobd is ok, the filesystem ext2 was mounted correctly. But you need to prepere some thing before you can run it. I don't know all. First, install please the modules manualy. The modules are in the file vmlinux-modules.tar.gz in your coLinux directory. Run WUBI and unpack the modules file as root with this command: tar xzf vmlinux-modules.tar.gz -C / Check, on what mount point is your file mounted. It is something like sda1 or hda1. WUBI does not know "cobd0". Use the mount you found from running WUBI and replace the cobd0 in the colinux config with this. Remove initrd from colinux config. For the first boot, bypass the normal runlevel to have a simple shell. Add this to your boot parameters: init 1 or init=/bin/bash I think there needs more work to bypass the loop mount. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-01-04 11:09 Message: I'm afraid, that WOBI does not use a raw single partition in the file. If WUBI use whole disk with partitions and it is only one file, You can try to replace this lines: cobd0="C:\ubuntu\disks\root.disk" root=/dev/cobd0 with scsi0=disk,"C:\ubuntu\disks\root.disk" root=/dev/sda1 The scsi0 is usable only in the devel version, you can get it from http://www.colinux.org/snapshots/ For more help, I need to kwon how WUBI store the data in the file. Please post the the output from 'mount' running under WUBI here. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=2485983&group_id=98788 |
