I've no idea what I've done recently to provoke it, but every time I power on my machine, it tells me there's no configured network interface. All I have to do to fix it, is give the root password, and then click ok several times until I get to 'finish'. It remembers all the static ip details but I can't persuade it to remember to start.
All I can recall doing recently is trying to persuade the box to talk to my Nokia phone but I'm not sure if that's the cause. I mention it just in case.
I've tried googling for the solution but got nowhere. Anybody any ideas?
On 28 Jul 17:37, Chris Walker wrote:
I've no idea what I've done recently to provoke it, but every time I power on my machine, it tells me there's no configured network interface. All I have to do to fix it, is give the root password, and then click ok several times until I get to 'finish'. It remembers all the static ip details but I can't persuade it to remember to start.
click?! Ahh - is this after you've logged in? Is the network managed by "network manager"? Also - what distribution, because it appears that Fedora do things different to the rest of the world too...
Maybe you need to go in to network manager, tell it the config and that it's the defaults and to bring it up on boot... but that's a guess... I'm still very much a user of /etc/network/interfaces in debian - even for my wifi (which then uses a mapping script and a bunch of psuedo interfaces to get the card up and working).
Cheers,
Chris Walker wrote:
I've no idea what I've done recently to provoke it, but every time I power on my machine, it tells me there's no configured network interface. All I have to do to fix it, is give the root password, and then click ok several times until I get to 'finish'. It remembers all the static ip details but I can't persuade it to remember to start.
All I can recall doing recently is trying to persuade the box to talk to my Nokia phone but I'm not sure if that's the cause. I mention it just in case.
I've tried googling for the solution but got nowhere. Anybody any ideas?
More by luck than judgement, I've fixed this.
It stopped happening when I switched off fastboot. I've no idea what it is - I can guess what it does! - but courtesy of a google suggestion, I made the change and for the past couple of days, it's worked.
-
Brett Parker -
Chris Walker