7.04 Dell Optiplex 320 Install

apjone · 01:03 PM

Ok, I have installed 7.04 on a dell optiplex 320, installed and configured lilo and updated to latest kernel by using chroot from the install cd.

It boots past lilo then says

Code:

cant find /root/etc/fstab

and some dev's & files. Then drops in to the ash shell. Before you can do anything it just locks up and prints

Code:

(interamfs)

on a new line. Any idea's?

mfa81

Same problem to me... install lilo from alternate cd

mfa81 · 02:58 PM

I think that this issue is related to this bug https://bugs.launchpad.net/ubuntu/fe...adm/+bug/75681

unfortunately i must to give up to use feisty and install etch on my workstation optiplex 320, at least for now !

Staceman · 03:07 PM

After trying multiple things from various places, I finally managed to get the Feisty beta to boot on my Optiplex 320.

I'll outline the entire procedure step-by-step, in the case that someone more inexperienced with Linux comes across this thread with the same problem. Keep in mind that my system is a dual-booting system with WindowsXP, and thus, the device names (/dev/sda3, for example) may be different. Also, you will need an active, preferably fast, internet connection.

First, download and install the Feisty Fawn beta, of course.

Next, instead of booting the new system (it won't work), boot back into the Live CD environment.

Open a terminal (Applications -> Accessories -> Terminal) and type the following, step by step (pressing Enter after each line of course):

Code:

sudo mkdir /media/ubuntu

sudo mount /dev/sda3 /media/ubuntu

sudo mount -t proc none /media/ubuntu/proc

sudo mount -o bind /dev/ /media/ubuntu/dev

sudo chroot /media/ubuntu /bin/bash

You are now chroot'ed into your installed system.

Now we install LILO:

Code:

sudo apt-get install lilo

It will tell you that you have to do a few things after the installation of LILO is complete. But first, we need to backup, then fix up, our fstab file:

Code:

sudo cp /etc/fstab /etc/fstab.backup
sudo vim /etc/fstab

...it may look something like this:

Code:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/sda3
UUID=18f2c772-d63f-4b71-a560-4146d0a4f298 /               ext3    defaults,errors=remount-ro 0       1
# /dev/sda5
UUID=6ffc9530-c9e4-4657-ac3c-5772716ae51c none            swap    sw              0       0
/dev/hda        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/hdb        /media/cdrom1   udf,iso9660 user,noauto     0       0
/dev/scd0       /media/cdrom2   udf,iso9660 user,noauto     0       0

What we need to do, is get rid of the "UUID=fded2ced-53ea-4dfa-bdb3-e4fd0b7a4fd3" entries, and replace them with the more traditional mount point syntax, since liloconfig can't handle the UUID stuff yet. If your fstab is similar to the one above, then the correct "traditional" mount points for your system should be directly above the UUID lines, commented out. After changing things around, it should look like this:

Code:

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/sda3
/dev/sda3       /               ext3    defaults,errors=remount-ro 0       1
# /dev/sda5
/dev/sda5       none            swap    sw              0       0
/dev/hda        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/hdb        /media/cdrom1   udf,iso9660 user,noauto     0       0
/dev/scd0       /media/cdrom2   udf,iso9660 user,noauto     0       0

After the above changes have been made, you can then run:

Code:

liloconfig

If you're dual booting with Windows on a single hard drive, you may get a warning about LILO needing to assign the drive an ID number, and that this may cause a fatal error in your Windows install, and it will ask you if you have a Windows 2K or XP system. If you answer 'yes', liloconfig will quit, and no changes are made. We need these changes to be made. Myself, I bit the bullet, answered 'no', and my Windows install booted up just fine. As for anyone else, I suggest you backup your Windows partition before proceeding, since your Windows install may get hosed, and it certainly won't be *my* fault!

Anyway, liloconfig will ask a few questions, default answers should be fine in most cases, you even get to choose your LILO theme at one point. Ignore any errors about your video adaptor. The very last question will be about your master boot record (MBR), and if your setup isn't anything fancy, you should answer 'Yes' here. (in other words, if you don't know what this all means, you should probably just answer 'yes'.)

If liloconfig ran without any errors, we now need to open up lilo.conf and make a few changes:

Code:

sudo vim /etc/lilo.conf

Scroll all the way to the bottom to this section:

Code:

image=/boot/vmlinuz-2.6.20-12-generic
        label="Lin 2.6.20img0"
        initrd=/boot/initrd.img-2.6.20-12-generic
        read-only
        append="pci=nomsi"

...and add the 'append="pci=nomsi"' directly below the "read-only" part. I feel it's only fair to mention, that this may not be necessary, and I don't have the time to test it at the moment. If you want to be safe, add it. If you're feeling adventurous, don't add it, see if your system boots, and post the result here.

Anyway, next we want to enable the Windows boot option, if you're dual-booting:

Code:

# If you have another OS on this machine (say DOS),
# you can boot if by uncommenting the following lines
# (Of course, change /dev/hda2 to wherever your DOS partition is.)
other=/dev/sda2 
label="Windows"

You'll need to uncomment the 'other' and 'label' lines, as above, and change the 'other' to the location of your Windows partition.

Now, simply run:

Code:

lilo

and if there's no errors, we're ready for the next step.

Now we update:

Code:

sudo apt-get update

sudo apt-get upgrade

Depending on your internet connection speed, and the speed of the mirrors you're using, this could take a while, as it will be updating a lot of things. If it stops at any time and complains about not being able to download all the packages, just repeat the 'sudo apt-get upgrade" step again, and things should be fine. Once everything is downloaded and apt begins the installation process, you may see a few things hang, such as daemon restarts and the like. This is normal, since it's working with the chroot'ed environment, and the installation process should continue shortly.

After the upgrade is complete, you should be able to reboot, and have a working install!

One thing to note though, you won't have the pretty Ubuntu loading boot screen when you use LILO. There's probably a way to enable it, and if anyone knows how, feel free to post it here, along with any other improvements to this method you may find.

Also please note that this most likely will only apply to the beta of Feisty Fawn. I would assume that the bug will be fixed by the time the final release rolls around.

Special thanks to the LILO guide found here: http://users.bigpond.net.au/hermanzone/

mfa81

Works fine to me !

Quote:

Originally Posted by Staceman

One thing to note though, you won't have the pretty Ubuntu loading boot screen when you use LILO. There's probably a way to enable it, and if anyone knows how, feel free to post it here, along with any other improvements to this method you may find.

Just add "splash" to the append line into lilo.conf, but I still see some text messages

Code:

        append="pci=nomsi splash"

zgoda

Any better situation with 7.04 final?

Staceman

I wasn't expecting the final release to be out so soon!

I've got my machine running pretty smoothly, not sure if I want to take the chance and experiment and hose it again!

Given the fact it's the final release, there will be more people trying it out, and thus I'm sure we'll hear something from someone sooner or later, if there's still an issue with these machines.

studerby

I just tried an install with the new Feisty Fawn live CD; with a standard install, GRUB still hangs on boot (assuming I added the "pci=nomsi" correctly for GRUB...).

Looks like we're going to have to continue switching to LILO, as described above.

doctorock

Hi

I am currently trying to install ubuntu 7.04 on an Optiplex 320 with dual booting and have had the problems described here and elsewhere.

Thanks for the adicve regarding the lilo loader. However, I can't get it to work for me. After following the steps described above, whenI reboot "MBR" breifly appears in the top left corner of the otherwise blank screen and then windows loads. I have installed both a partition boot record and a master boot record, and have tried with and without the lines in the lilo.conf file about the windows operating system commented out.

many thanks

doctorock

doctorock

I worked out what my problem was. The linux partition with the boot loader (sda3) was not set to active, even though I requested that it be so in liloconfig. Instead the windows partition was. I fixed the problem with the gparted tool and now I have Ubuntu up and running.

Thanks again for the instructions. I would have been lost without them.

April 14th, 2007	#1
apjone Dipped in Ubuntu Join Date: Nov 2005 Location: Wales Beans: 628 Ubuntu 9.04 Jaunty Jackalope	7.04 Dell Optiplex 320 Install Ok, I have installed 7.04 on a dell optiplex 320, installed and configured lilo and updated to latest kernel by using chroot from the install cd. It boots past lilo then says Code: cant find /root/etc/fstab and some dev's & files. Then drops in to the ash shell. Before you can do anything it just locks up and prints Code: (interamfs) on a new line. Any idea's? __________________ Tony J Unanswered Posts Team: A team for handling unanswered posts. \| The Blog: http://apjone.com \| Hardware Team:A team for handling hardware forums Last edited by apjone; April 14th, 2007 at 01:03 PM..

April 16th, 2007	#2
mfa81 5 Cups of Ubuntu Join Date: Feb 2006 Beans: 18	Re: 7.04 Dell Optiplex 320 Install Same problem to me... install lilo from alternate cd

April 16th, 2007	#3
mfa81 5 Cups of Ubuntu Join Date: Feb 2006 Beans: 18	Re: 7.04 Dell Optiplex 320 Install I think that this issue is related to this bug https://bugs.launchpad.net/ubuntu/fe...adm/+bug/75681 unfortunately i must to give up to use feisty and install etch on my workstation optiplex 320, at least for now ! Last edited by mfa81; April 16th, 2007 at 02:58 PM..

April 16th, 2007	#4
Staceman 5 Cups of Ubuntu Join Date: Mar 2006 Beans: 14 Ubuntu 6.10 Edgy	Re: 7.04 Dell Optiplex 320 Install After trying multiple things from various places, I finally managed to get the Feisty beta to boot on my Optiplex 320. I'll outline the entire procedure step-by-step, in the case that someone more inexperienced with Linux comes across this thread with the same problem. Keep in mind that my system is a dual-booting system with WindowsXP, and thus, the device names (/dev/sda3, for example) may be different. Also, you will need an active, preferably fast, internet connection. First, download and install the Feisty Fawn beta, of course. Next, instead of booting the new system (it won't work), boot back into the Live CD environment. Open a terminal (Applications -> Accessories -> Terminal) and type the following, step by step (pressing Enter after each line of course): Code: sudo mkdir /media/ubuntu sudo mount /dev/sda3 /media/ubuntu sudo mount -t proc none /media/ubuntu/proc sudo mount -o bind /dev/ /media/ubuntu/dev sudo chroot /media/ubuntu /bin/bash You are now chroot'ed into your installed system. Now we install LILO: Code: sudo apt-get install lilo It will tell you that you have to do a few things after the installation of LILO is complete. But first, we need to backup, then fix up, our fstab file: Code: sudo cp /etc/fstab /etc/fstab.backup sudo vim /etc/fstab ...it may look something like this: Code: # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # /dev/sda3 UUID=18f2c772-d63f-4b71-a560-4146d0a4f298 / ext3 defaults,errors=remount-ro 0 1 # /dev/sda5 UUID=6ffc9530-c9e4-4657-ac3c-5772716ae51c none swap sw 0 0 /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/hdb /media/cdrom1 udf,iso9660 user,noauto 0 0 /dev/scd0 /media/cdrom2 udf,iso9660 user,noauto 0 0 What we need to do, is get rid of the "UUID=fded2ced-53ea-4dfa-bdb3-e4fd0b7a4fd3" entries, and replace them with the more traditional mount point syntax, since liloconfig can't handle the UUID stuff yet. If your fstab is similar to the one above, then the correct "traditional" mount points for your system should be directly above the UUID lines, commented out. After changing things around, it should look like this: Code: # /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # /dev/sda3 /dev/sda3 / ext3 defaults,errors=remount-ro 0 1 # /dev/sda5 /dev/sda5 none swap sw 0 0 /dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/hdb /media/cdrom1 udf,iso9660 user,noauto 0 0 /dev/scd0 /media/cdrom2 udf,iso9660 user,noauto 0 0 After the above changes have been made, you can then run: Code: liloconfig If you're dual booting with Windows on a single hard drive, you may get a warning about LILO needing to assign the drive an ID number, and that this may cause a fatal error in your Windows install, and it will ask you if you have a Windows 2K or XP system. If you answer 'yes', liloconfig will quit, and no changes are made. We need these changes to be made. Myself, I bit the bullet, answered 'no', and my Windows install booted up just fine. As for anyone else, I suggest you backup your Windows partition before proceeding, since your Windows install may get hosed, and it certainly won't be my fault! Anyway, liloconfig will ask a few questions, default answers should be fine in most cases, you even get to choose your LILO theme at one point. Ignore any errors about your video adaptor. The very last question will be about your master boot record (MBR), and if your setup isn't anything fancy, you should answer 'Yes' here. (in other words, if you don't know what this all means, you should probably just answer 'yes'.) If liloconfig ran without any errors, we now need to open up lilo.conf and make a few changes: Code: sudo vim /etc/lilo.conf Scroll all the way to the bottom to this section: Code: image=/boot/vmlinuz-2.6.20-12-generic label="Lin 2.6.20img0" initrd=/boot/initrd.img-2.6.20-12-generic read-only append="pci=nomsi" ...and add the 'append="pci=nomsi"' directly below the "read-only" part. I feel it's only fair to mention, that this may not be necessary, and I don't have the time to test it at the moment. If you want to be safe, add it. If you're feeling adventurous, don't add it, see if your system boots, and post the result here. Anyway, next we want to enable the Windows boot option, if you're dual-booting: Code: # If you have another OS on this machine (say DOS), # you can boot if by uncommenting the following lines # (Of course, change /dev/hda2 to wherever your DOS partition is.) other=/dev/sda2 label="Windows" You'll need to uncomment the 'other' and 'label' lines, as above, and change the 'other' to the location of your Windows partition. Now, simply run: Code: lilo and if there's no errors, we're ready for the next step. Now we update: Code: sudo apt-get update sudo apt-get upgrade Depending on your internet connection speed, and the speed of the mirrors you're using, this could take a while, as it will be updating a lot of things. If it stops at any time and complains about not being able to download all the packages, just repeat the 'sudo apt-get upgrade" step again, and things should be fine. Once everything is downloaded and apt begins the installation process, you may see a few things hang, such as daemon restarts and the like. This is normal, since it's working with the chroot'ed environment, and the installation process should continue shortly. After the upgrade is complete, you should be able to reboot, and have a working install! One thing to note though, you won't have the pretty Ubuntu loading boot screen when you use LILO. There's probably a way to enable it, and if anyone knows how, feel free to post it here, along with any other improvements to this method you may find. Also please note that this most likely will only apply to the beta of Feisty Fawn. I would assume that the bug will be fixed by the time the final release rolls around. Special thanks to the LILO guide found here: http://users.bigpond.net.au/hermanzone/ Last edited by Staceman; April 16th, 2007 at 03:07 PM..

April 20th, 2007	#6
zgoda 5 Cups of Ubuntu Join Date: Aug 2005 Location: Wolomin, Poland Beans: 44 Ubuntu 7.10 Gutsy Gibbon	Re: 7.04 Dell Optiplex 320 Install Any better situation with 7.04 final? __________________ We read Knuth so you don't have to.

April 20th, 2007	#8
studerby First Cup of Ubuntu Join Date: Dec 2006 Beans: 4	Re: 7.04 Dell Optiplex 320 Install I just tried an install with the new Feisty Fawn live CD; with a standard install, GRUB still hangs on boot (assuming I added the "pci=nomsi" correctly for GRUB...). Looks like we're going to have to continue switching to LILO, as described above.

April 24th, 2007	#9
doctorock First Cup of Ubuntu Join Date: Apr 2007 Beans: 2	Re: 7.04 Dell Optiplex 320 Install Hi I am currently trying to install ubuntu 7.04 on an Optiplex 320 with dual booting and have had the problems described here and elsewhere. Thanks for the adicve regarding the lilo loader. However, I can't get it to work for me. After following the steps described above, whenI reboot "MBR" breifly appears in the top left corner of the otherwise blank screen and then windows loads. I have installed both a partition boot record and a master boot record, and have tried with and without the lines in the lilo.conf file about the windows operating system commented out. many thanks doctorock

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode