Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Could some kind person help me with this problem, please?
I recently upgraded Ubuntu 8.10 on my old desktop and also on a USB memory stick to Ubuntu 9.04 alpha 1. I realise that this is not the final release and that there could be problems, but I was curious to see what it is like.
My computer boots into Ubuntu 9.04 quite happily from the memory stick and Update Manager notifies me of any updates, so now it has alpha 4
However although my desktop (it is an old one that I use for this type of thing) boots quite normally and update manager notified me of updates it will not now connect to the internet. When it boots a green thing rotates for a while in the notification area and then there is the message "The network has been disconnected". I was able to connect to the internet until after upgrading to alpha 4
Clicking on the Network Manager icon shows that Ubuntu 'knows' that it should use 'eth0' but everything related to it is greyed out so that I can't edit it (even if I knew what to do)
It seems very strange that two identical versions of Ubuntu 9.04 behave differently in the same machine
The machine that I am using is a dual boot Windows XP/Ubuntu, with Ubuntu and Windows on separate drives, which normally defaults to Windows if I don't tell it otherwise and in order to save time I edited 'menu.lst' on the computer so that it would default to Ubuntu. I checked the 'menu.lst' on the memory stick to make sure that what I had edited was correct and found that on the memory stick 'menu.lst' referred to Ubuntu 9.04 but on the computer 'menu.lst' only referred to Ubuntu 8.10. I tried importing the lines relevant to Ubuntu 9.04 from the memory stick to the computer but now the computer won't boot properly. Fortunately I left the lines relating to Ubuntu 8.10 so I was able to boot it and remove my editing from 'menu.lst'
Is there any way out of this 'impasse'or is it a case for reformatting the hard disc? A corrupt file, perhaps?
You might also disclose how you are connected to the Internet - Wifi, what network card, and compare /etc/host.conf and /etc/resolv.conf in both systems. you may need to install a kernel module if everything is gray.
Hi john test, doing ifup eth0 produced "ignoring unknown interface eth0=eth0"
/etc/init.d/networking restart produced "reconfiguring network interfaces" followed by [OK]
but I still can't connect.
I connect via an NVIDIA (built in) ethernet card and cable connected to an ADSL modem. /etc/resolv.conf appears to be empty. It just says "# Generated by NetworkManager". The files are the same in both systems.
At some stage I tried to boot in recovery mode and at the end got this message "ALERT! /dev/desk/by-uuid/dec5558c-1a28-4c78-b59a-4ce00abbbfba does not exist. Dropping to a shell"
Booting stopped after that.
How can I find out if a module is missing and more importantly where to find it and how to install it.
I had thought of making an alternative install disc but it looks as if this will erase everything even though I read that it can be used as an updater.
Hi farslayer, thanks for your suggestion. I did 'cat /var/log/dmesg' etc. and it identified the ethernet card as a RealTek RTL 8139 and as eth0. It also mentioned that 'sd' and'sr' need updating but I don't know what these are, how to update them or how to use the 'bus type method' that it said to use.
It looks to me that the card is OK (?) and that the problem lies somewhere else
I am not sure whether I understand the output from 'diff -u thisfile thatfile.
The modules from the system that works properly had a - in front of them and those from the one that won't connect to the internet have a + in front of them. I copied it to a file but I am doing this in Windows so as to leave the other machine free for Ubuntu and transferred the file to Windows but it is unreadable. I could shut down windows and send the file if you have the patience to look at it.
The output from ifconfig is very similar to yours but the interrupt is 18 and the base address is 0xec00 and the TX and RX packets were 57 and 47 in the system that works and 8 and 2 in the system that doesn't
If you could look at the file I could send it tomorrow as I am being nagged to "shut that b****y computer down asap"
Hi farslayer, thanks for getting back to me. I did lsmod | grep -i 8139* as you suggested, on the system that connects (i.e the one booted with the USB stick) and the one that won't (i.e. the same computer booting from its HD) and the output was identical on both occasions:-
Computer that connects using USB stick :
8139too 32128 0
8139cp 27776 0
mi i 13312 2 8139too, 8139cp
Same computer but booting from its HD exactly the same
The computer has two HDs; C: is devoted entirely to Windows XP SP2 and D: is devoted entirely to Ubuntu. I did it like that partly because I had a spare HD and partly because, not knowing much about partitions, I thought that there was less chance of losing data than if Ubuntu were installed on the C: drive.
I had a look at the link that you gave and found that "Wake on LAN after shutdown" was already enabled. I have had no problems like this with Ubuntu 8.10 or Ubuntu 9.04 alpha 1 to alpha 3. The problem only arose with alpha 4. I have downloaded the alternative install image for alpha 5 and burned it to a CD thinking that if it were installed it would correct any broken files but it won't install. It says that the system is already up to date. I don't know if it can be made to install in spite of that.
Sometimes it occurs that the card is detected as 8139 but there are different version of the 8139 available.
The 8139cp driver is for RealTek RTL-8139C+ series 10/100 PCI Ethernet driver
The 8139too driver is for RealTek RTL-8139 Fast Ethernet driver
So the proper module would depend on Which actual card you have.. if the system is trying to load both modules it could be causing a conflict.. lspci should help you determine which module is actually correct.
Ethernet controller: RealTek Semiconductor Co. Ltd RTL-8139/8139C/8139C+ rev 10 and having done the commands (rmmod etc.), doing 'ifup eth0' returned "Ignoring unknown interface eth0=eth0". I tried 'ifup eth0' a couple of days ago and got the same answer
I have just done 'lsmod' on the system that connects to the internet and both 8139too and 8139cp are listed and 'mii' has 8139too,8139cp beside it; that is the same as the system that wont connect
It looks to me as though I am going to have to reinstall Ubuntu
Last edited by Chriscrof; 03-04-2009 at 11:56 AM.
Reason: New information
lspci was a great help - we know you have a Realtek card now!
I concur with farslayer.
8139cp is for Realtek 9139C+ Fast Ethernet cards and is recommended
8130too is for older cards, (8129/8130/early 8139)and they conflict.
If your card is ancient then this might be the one for you. I suspect 8139too may get in the way.
I had this bug a while back. try
There are saved interrupt settings in those realtek cards, and my nic wanted irq 11. But some halfassed via chipset M/b had a broken interrupt controller and gave it irq 22 or summat. So the System Couldn't See It.
Check what irq works for it. You can assign an irq with ifconfig. Bring it down, then up.
ifconfig eth0 down
ifconfig eth0 irq (your irq) up
then run dhclient eth0 (or pppoe with it's options if appropriate.)