FedoraThis forum is for the discussion of the Fedora Project.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Two days ago, my Internet connection stopped working under Fed 12. It works under Win, and Ubuntu, so there is no hardware failure. Maybe the result of an update?
How can I fix this? Anyone else had this problem. It simply won't connect to the connection 'Zuhause'. I haven't had the opportunity to try another connection. Monday at work I can see if it will connect to a different connection.
How are you trying to connect? What sort of network?
In fedora, I remember having to remove the connection settings completely then reinstating them when something went wrong.
Not sure what you mean. I see no button 'reset' I have the nm applet running, and like I said, up to 2 days ago, it worked fine. This must be related to an update. I check everyday for updates. I have Debian on an external HD. I installed WICD there. But it doesn't seem to have a rubric 'dsl', just 'wired network'. But I'm writing this in Ubuntu, and everything works.
I deleted the connection and re-wrote it, but that didn't help! I felt a bit silly when the technician came. He started Windows and there was nothing wrong!
I was so happy with Fed 12, everything seemed to work! Knew it was too good to be true!
Dual boot no. I only use Win for AutoCAD. I use the same nm in Ubuntu, the Gnome nm. I just set the username and password. nm says I have a connection Home, but it never connects. I get a white x on a red background next to the double monitor icon, then it switches to syseth0, which goes nowhere. This is a dsl connection working now under Ubuntu, and previously under Fed 12
That is to say: Win is on the same hard disc, but never had this problem before. I don't know if you can boot both at once. A friend runs win under a VM inside Linux, if that's what you mean by dual boot
A computer with two operating systems. At startup, a boot manager program lets the user choose which one to load.
... so, yes, you have a multi-boot computer. All the operating systems are running on the same hardware from the same HDD (but not simultaniously).
On some systems, windows will put the nic to sleep when it shuts down - then, when you boot the same computer to another OS, the nic stays asleep and the OS cannot use it.
However - looking at your description, I need you to check something else.
Quote:
nm says I have a connection Home, but it never connects. I get a white x on a red background next to the double monitor icon, then it switches to syseth0, which goes nowhere.
This sounds contradictory to me.
The X on the nm applet means there is no connection. Our object is to get rid of that little red X. If the red x goes away when it "switches to syseth0", then you have a connection - but you may just get a timer animation that keeps going - is that what you mean?
If you left-click on the applet, you should see the available networks. I get a wired connection called "auto eth0" and my network setup uses a router/adsl-modem with dhcp. If I right-click on it I see a checkbox next to "enable networking": this has to be ticked.
There is also an option to edit connections - you should compare the settings with those in Ubuntu - which you know works.
When the little red x goes away, then you have a connection.
After you've got back to me with the result of these checks, I'll see if I need to give you some commandline stuff to do. I have to work slowly because you are very new to this and I want to be sure I'm getting it right. If I was right there it would take about 10mins.
Ok.
A right click on the nm icon brings up a menu with check boxes 'enable networking' some other stuff and 'edit connections'
The check boxes are automatically checked on boot. But I unchecked them and then rechecked them. I made a new dsl connection, 'homeagain' with my username and password. It won't connect, lil x shows up. Then Fed goes to system eth0, and it says I have a connection. This is a wired connection with no ip, going nowhere. I have a static ip in the library here. I will walk over there later, and see if Fed lets me connect to the wired network there.
If I had a net connection under Fed, I would re-install nm. Must be a bug in it, I think. It was working up to 3 days ago. But I will wait and heed your advice. As I said, I like Fed 12, so I'd like to keep it.
Under the tab dsl in the nm gui there is no option 'enable dhcp', just username, service (I leave this blank, don't know what it is, works without it)and password. There is a checkbox 'allow other users to use this connection' which I've checked. Apart from that there is nothing. Well, at the top I can give the connection a name.
Well, I'm in the library, and the wired network here (fixed ip) worked first time under Fed 12. My update manager is telling me there is a new release of NetworkManager. It is installing the update now. I will walk home again after that and see if it can connect to the dsl connection.
Keep your hair on Pete! I have a dsl connection again at home! Must have been a glitch in a previous update! Thanks for your advice! Don't s'pose I'll ever know what it was!
Well done - it is also possible that there was a rogue setting someplace that got cleared in the update. It can clean things up like that, as well as break them.
One of the things I suspected was that you may have had your browser etc in offline mode. So nmapplet would say you are connected but you cannot do anything. Making a new network connection could also have reset everything.
Should you see this again, you'll want to look at the commandline method of getting a connection through ifconfig and dhpcd. The advantage of this is that you get more detailed error messages as well as exact information about your potential and actual connections.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.