Technology news and Jobs arrow Our Blogs arrow Open Sauce arrow Further adventures with Feisty Fawn
Further adventures with Feisty Fawn E-mail
by Sam Varghese   
Tuesday, 24 April 2007
(If you missed the first part of this saga, please read this.)

It's difficult to walk away from an experiment with software - especially when you know that most of the problems are resolvable. It's probably something to do with one's ego. But never mind.

I returned to my experiments with Feisty Fawn early this morning. To recap a bit, after installing it on my PC yesterday, I got a message saying ""GRUB loading, please wait... Error 18."

This time, before beginning the installation, I changed the BIOS setting for the hard drive from LBA to auto, this being one of the suggestions I saw on a mailing list.  This did no good, so the next time I partitioned the hard drive manually, allocating a small boot partition as the first slice. I left it to install while I went to bed.

After I woke up, I rebooted the PC and found I had a working installation. But my rejoicing was shortlived.

Given the problems I had with DHCP earlier (see this article for details), I had opted to set up the network interface manually for this installation.

There is a small icon on the right-hand-side of the Ubuntu desktop which allows one to disable and enable networking. However, after I had entered the network details manually, I could not bring it up using this icon. Logically, this should run the ifup and ifdown scripts which will take down a network interface and bring it up again with any changes incorporated.

I checked the interfaces configuration file which resides in /etc/network. The settings looked fine; everything I had entered in the graphical utility for network configuration (which you can find under System) had been accepted. But running ifconfig showed that the network card did not have these settings.

I tried logging in and out but nothing changed. Then I tried something which no Linux user should ever have to do (unless you install a new kernel) - rebooting. Once again, there was no change.

Finally, I ran ifdown and ifup from a terminal; after that I had internet connectivity



 
< Next story in category   Previous story in the category >
iTWire user statistics Visitors last 30 days
694,279
Subscribers 15,210
#1 independent technology news advertise here
  •   *  
  • Search
  • AdvSeach
  • Login
  • Events
  • FreeStuff

- Advertisement -

Featured Whitepapers

Open Sauce - A GNU perspective Subscribe to the RSS
Open Sauce focuses on the wonderful, wacky world of free and open source software where people write great applications and actually allow others to use them without payment.
Follow iTWire on Twitter

About iTWire

iTWire is all about technology news, information, jobs and community for the IT and telecommunications industry professional. Subscribe to our free ICT daily newsletter