On Fri, Nov 28, 2014 at 8:56 PM, Jack Chastain <[email protected]> wrote:
> A thought struck me after I sent my last reply - can I boot the DVD > (LiveCD mode) and then mount my original partition and run "sudo apt-get > update" on that? Or even the fix that was mentioned? Is that too much a > Solaris thing to work on Linux? > > Reading man page on it, probably just a little too much to hope for. OK - Reinstall coming up after maybe a bit more reading and searching. If I can stand it, I may even wait until Saturday just in case there are other ideas. JC JC > > On Fri, Nov 28, 2014 at 8:54 PM, Jack Chastain <[email protected]> > wrote: > >> >> On Fri, Nov 28, 2014 at 8:40 PM, Sean Dague <[email protected]> wrote: >> >>> On 11/28/2014 08:33 PM, Jack Chastain wrote: >>> >>> On Fri, Nov 28, 2014 at 8:21 PM, Sean Dague <[email protected]> wrote: >>> >>>> 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. >>>> >>>> >>> Yep - that's a habit I have - and when NOT on DVD, it only has lo >>> (booted on LiveCD - much more normal, though no address on eth0) >>> >>> >>> >>>> I also don't know what a Logitech Unity is, so I'm not sure what kind >>>> of device is expected there. >>>> >>>> >>> On LIveCD it "just works" - even the keyboard! Yay! Maybe I don't need >>> Solaar anymore! >>> >>> >>>> >>>> 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) >>>> >>>> >>> Yeah - absolutely nothing like this when on normal boot. No eth >>> anything (I grepped before) >>> >>> >>> >>>> 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 >>>> >>>> >>> nothing returns. I dropped off the "-dist" and get some results, so I >>> am presuming the answer to this is "there aren't any". >>> >>> >>> >>>> 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. >>>> >>>> >>> Totally understand and appreciate the attempts. Original question >>> stands - is it possible to do a "recovery" from the DVD I now have, or am I >>> just going to commit to a rebuild? I can do that - probably easier - I >>> backed up my entire home dir before, so no loss anticipated (though I have >>> to reload all the "stuff". Too clueless to use all the nice reconstruction >>> things ;-) >>> >>> There is not really such a thing as a recovery mode, because what that >>> would be is trying to clear out a bunch of common state and reboot, most of >>> which would be in /etc. >>> >>> >> Well - I expected that, but was kind of hoping... >> >> >> >>> Did you try removing the persistence rules file with a restart? That's >>> the most common state wedge for something like "my adapter didn't show up". >>> >>> >> Did nothing (that I was aware of?) with rules. Are we talking about >> /etc/udev? (Only got that from Google - keep in mind - I am pretty minimal >> in Linux!) I'm looking at search results for that now - nothing good yet. >> >> I will probably just go for a re-install, given that everything works >> fine with the DVD in. >> >> >> >>> The other "in the future" tool to install and use is 'etckeeper', which >>> keeps all of /etc in a git repo, so you can see all changes that package >>> upgrades do, which helps on a debug like this. >>> >>> >> I will do that first :) >> >> >>> -Sean >>> >>> >> >> JC >> >>> >> -- >> 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. >> > > > > -- > 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. > -- 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.
