#39 Booting a WUBI image from c:\ drive in CoLinux

v1.0 (example)
open
nobody
5
2009-01-04
2009-01-04
Anonymous
No

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!!

Discussion

<< < 1 2 3 (Page 3 of 3)
  • 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.

     
  • 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

     
  • 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.

     
  • Henry N.
    Henry N.
    2009-10-05

    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.

     
  • .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.

     
  • Henry N.
    Henry N.
    2009-10-10

    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 )

     
  • 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.

     
  • Henry N.
    Henry N.
    2009-10-11

    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.

     
  • 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.

     
<< < 1 2 3 (Page 3 of 3)