Results 1 to 1 of 1
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Dec 2004
Help with 32bit environment in Ubuntu 64 (Hoary)
Hi, I am trying to install a 32bit environment in my ubuntu 64 system. Mainly for the use of wine. I followed the directions from this site http://www.nerdarium.com/archives/20...it-chroot-fun/. When I do the "dchroot -d" command I get this:
dchroot: chdir: No such file or directory dchroot: Child exited non-zero. dchroot: Operation failed.
chroot /var/32 dpkg-reconfigure locales
Reading package lists... Done Building dependency tree... Done You might want to run `apt-get -f install' to correct these: The following packages have unmet dependencies: linux-restricted-modules-188.8.131.52-3-386: Depends: linux-image-184.108.40.206-3-386 but it is not going to be installed wine: Depends: libwine (= 0.0.20040615-1ubuntu1) but it is not going to be installed Depends: xbase-clients (>= 4.0) but it is not going to be installed or xcontrib E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
Reading package lists... Done Building dependency tree... Done Correcting dependencies... Done The following extra packages will be installed: linux-image-220.127.116.11-3-386 Suggested packages: lilo grub linux-doc-18.104.22.168 linux-source-22.214.171.124 The following NEW packages will be installed: linux-image-126.96.36.199-3-386 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 10 not fully installed or removed. Need to get 0B/15.5MB of archives. After unpacking 45.6MB of additional disk space will be used. Do you want to continue [Y/n]? y Preconfiguring packages ... (Reading database ... 11792 files and directories currently installed.) Unpacking linux-image-188.8.131.52-3-386 (from .../linux-image-184.108.40.206-3-386_220.127.116.11-16.1_i386.deb) ... You are attempting to install an initrd kernel image (version 18.104.22.168-3-386) 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'll continue to see this message whenever you install a kernel image using initrd. Do you want to stop now? [Y/n]
You are attempting to install a kernel image (version 22.214.171.124-3-386) However, the directory /lib/modules/126.96.36.199-3-386 still exists. If this directory belongs to a previous linux-image-188.8.131.52-3-386 package, and if you have deselected some modules, or installed standalone modules packages, this could be bad. However, if this directory exists because you are also installing some stand alone modules right now, and they got unpacked before I did, then this is pretty benign. Unfortunately, I can't tell the difference. If /lib/modules/184.108.40.206-3-386 belongs to a old install of linux-image-220.127.116.11-3-386, then this is your last chance to abort the installation of this kernel image (nothing has been changed yet). If this directory is because of stand alone modules being installed right now, or if it does belong to an older linux-image-18.104.22.168-3-386 package but you know what you are doing, and if you feel that this image should be installed despite this anomaly, Please answer n to the question. Otherwise, I suggest you move /lib/modules/22.214.171.124-3-386 out of the way, perhaps to /lib/modules/126.96.36.199-3-386.old or something, and then try re-installing this image. Do you want to stop now? [Y/n]