On 11/28/2014 08:03 PM, Jack Chastain wrote: > It was "whatever the system wanted" - based on upgrade notices > normally given... so not something I did "intentionally" - just the > flow of things. I only know that it is not stating 14.04 LTE (note - I > don't see 14.04.1 - though that is what I am downloading to DVD at the > moment.) > > ifconfig looks ... short to me - but I don't look at it often enough > to know on the laptop. If I am reading it correctly, only "lo" is > showing up.Loopback isn't going to do me any good (not at all sure why > no wireless either but I suspect it is related). ifconfig -a (the -a is important) as that will display all interfaces known to the system even if they don't have addresses, which yours don't.
I also don't know what a Logitech Unity is, so I'm not sure what kind of
device is expected there.
>
> BTW: I also changed wires and physical ports - and went directly to my
> main router as well - all nothing.
>
> I did try "sudo restart network-manager" and it just comes back the
> same way. Tells me I am offline.
Right, network manager is just reading other configs / kernel exported
resources. Restarting it without a config change won't impact anything.
>
> Looking in dmesg for net-based items (anything specific I need to look
> for? "et.." data? This is why I never really was successful on the
> Linux side - my Unix is pretty damn good - but Linux still confuses me
> ;-) - I find these few things...
>
> NET: Registered protocol family 16
> ...
> NET: Registered protocol family 2
> [several TCP and UDP lines - nothing like errors or anything I recognise]
> NET: Registered protocol family 1 (others later as well)
> ...
> nothing else obvious - however the last line in dmesg reads
> (paraphrased here, will try to copy the entire thing if necessary to
> here):
>
> systemd-hostname[2887]: Warning: nss-myhostname is not installed.
> Changing the local hostname might make it unresolvable. Please install
> nss-myhostname.
That's pretty innocuous. I saw that on my 14.04 all the time.
>
> No clue if that is imporatant.
>
> Should I try to drop you the entire dmesg?
>
> [add: I just ran "dmesg | grep -i net" - see this mongst a few other
> things: "audit: initializing netlink socket (disabled)"]
>
> Thanks!
What you are looking for is reference for your network adapters
initializing for instance:
[ 8.991276] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: Rx/Tx
(from my desktop)
or
[496871.229602] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
[496871.236602] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
[500301.873312] iwlwifi 0000:03:00.0: no hotplug settings from platform
[501462.791896] iwlwifi 0000:03:00.0: no hotplug settings from platform
(from my laptop)
The other thing to figure out is figure out if some config file wanted
to be updated during upgrade and didn't get:
sudo find /etc | grep dpkg-dist
That will be the etc files which there was a new distro config file, but
either you or the system decided not to apply it. That can be the cause
for configuration issues like this as well.
But, that being said, there is a lot of shooting in the dark here.
-Sean
>
> Jack
>
> On Fri, Nov 28, 2014 at 7:38 PM, Sean Dague <[email protected]
> <mailto:[email protected]>> wrote:
>
> What did you upgrade to? was it just a minor update to 14.04 LTS,
> or was it the upgrade to 14.10?
>
> On the networking front:
>
> Does `ifconfig -a` return a set of interfaces that you would expect?
>
> Does `dmesg` list your device getting loaded and registered (which
> might just mean a device mapping issue).
>
> I recently did the 14.10 update and because of the switch to
> systemd needed to:
>
> rm -f /etc/udev/rules.d/70-persistent-net.rules because the device
> that was living as eth1 for the last year was now being mapped to
> eth0, but it took a delete of the persistence rules to get
> everything to reset.
>
> -Sean
>
>
> On 11/28/2014 06:17 PM, Jack Chastain wrote:
>> HI folks.
>>
>> Ubuntu had a bad upgrade - or maybe I just had an upgrade failure
>> - and one of the effects appears to have been to take out my
>> network - so I can't do any of the "apt-get" fixes I am finding
>> on my ancient Windows station to actually fix it.
>>
>> the system boots fine, looks mostly normal save that networking
>> is gone and my Logitech Unity adapter is n[t seen any longer as
>> well (one possibility was to disable third party stuff - which I
>> could do but without network, I don't really see the point ... yet. )
>>
>> If I pull down a new copy of Ubuntu, can I repair from that
>> without completely erasing what I have on my laptop? I am going
>> to do some backing up just in case I am stuck with a wipe and
>> reinstall - but would love to not have to do that.
>>
>> And yeah - I know all this happens just before the Backup
>> Solutions meeting. Karma.
>>
>> Jack
>>
>> --
>> Google Voice: (914) 468-4552 <tel:%28914%29%20468-4552>
>> ----------------------------------------
>> Prov. 12:15
>>
>> Eschew obfuscation and pompous prolixity.
>>
>> Light a man a fire, he is warm for the night.
>> Light a man afire, he is warm for the rest of his life.
>>
>>
>> _______________________________________________
>> Mid-Hudson Valley Linux Users Group http://mhvlug.org
>> https://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
>>
>> Upcoming Meetings (6pm - 8pm) Vassar College *
>> Dec 3 - Home Disaster Recovery
>> Jan 7 - When Will Then Be Now? Soon.
>
>
> --
> Sean Dague
> http://dague.net
>
>
> _______________________________________________
> Mid-Hudson Valley Linux Users Group http://mhvlug.org
> https://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
>
> Upcoming Meetings (6pm - 8pm) Vassar College *
> Dec 3 - Home Disaster Recovery
> Jan 7 - When Will Then Be Now? Soon.
>
>
>
>
> --
> Google Voice: (914) 468-4552
> ----------------------------------------
> Prov. 12:15
>
> Eschew obfuscation and pompous prolixity.
>
> Light a man a fire, he is warm for the night.
> Light a man afire, he is warm for the rest of his life.
>
>
> _______________________________________________
> Mid-Hudson Valley Linux Users Group http://mhvlug.org
> https://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
>
> Upcoming Meetings (6pm - 8pm) Vassar College *
> Dec 3 - Home Disaster Recovery
> Jan 7 - When Will Then Be Now? Soon.
--
Sean Dague
http://dague.net
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org https://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) Vassar College * Dec 3 - Home Disaster Recovery Jan 7 - When Will Then Be Now? Soon.
