More info seems to lead to more questions. Apparently this has something to do with systemd. I guess this is a new (to me) thing and it changes the way stuff is named. So, what used to be eth0 is now enp3s0. But, trying the usual network commands with that don't work either.
Michael On Sun, May 14, 2017 at 10:04 PM, wes <[email protected]> wrote: > my first step is usually to find the model number in the lspci output, and > the google that number along with ubuntu 16.04 and see if anyone's posted a > guide. > > -wes > > On Sun, May 14, 2017 at 9:28 PM, Michael Barnes <[email protected]> > wrote: > > > Installed 16.04 LTS via flash drive to new hard drive. Only took a few > > minutes! Previous DVD installs took much, much longer. Anyhow, so far, no > > network. Sadly, my Linux memory has become very foggy, so please forgive > > the noobie type questions. I don't seem to be finding eth0. Using lspci, > I > > find the info for the onboard Broadcom Ethernet adapter, but under > > 'Capabilities' it says "<access denied>. Running ifconfig does not show > > eth0, but it does show enp3s0. If I try "sudo ifup eth0" I get "Unknown > > interface eth0." > > > > I'm kind of surprised at the minimum of questions and the speed of the > > install. I wonder what else will not be working? > > > > Thanks for your comments, > > > > Michael > > > > > > On Sun, May 14, 2017 at 8:42 PM, Michael Barnes <[email protected]> > > wrote: > > > > > I figured the quickest and easiest was probably to start all over. It > > > looks like all my files, pictures, documents, etc. are still intact. > I'll > > > just stick in a new hard drive, install 16.04 LTS from scratch, then > copy > > > what I need from the old drive to the new one. Thanks for everyone's > > > comments. > > > > > > Michael > > > > > > > > > On Sat, May 13, 2017 at 12:51 AM, Nat Taylor <[email protected]> > wrote: > > > > > >> instead of comparing xorg files, I'd want to get it to try to > > >> automagically > > >> configure stuff fresh, maybe with a *sudo dpkg-reconfigure xorg* and a > > >> *sudo > > >> apt update && sudo apt upgrade && sudo apt dist-upgrade* > > >> Maybe try dpkg-reconfiguring your window manager (unity?) > > >> -- did it disable the universe or multiverse for the upgrade and do > you > > >> need to reenable it? > > >> Check your /etc/apt/sources.list and /etc/apt/sources.list.d/ > > >> > > >> Did you do the upgrade to 16.04 by manually editing the sources, or > did > > >> you > > >> use the tool in the Software Center, or did you do-release-upgrade > from > > >> the > > >> command line? > > >> > > >> On Fri, May 12, 2017 at 3:20 PM, Michael Barnes < > [email protected]> > > >> wrote: > > >> > > >> > Yeah, I got to thinking after I started I shouldn't have done that. > > >> > Everything has been packed away for almost a year. It seems I've > > >> forgotten > > >> > more than I remember. A new hard drive is probably in order. I'll > have > > >> to > > >> > compare Xorg files and look at drivers loaded between the two > > versions. > > >> > Just have to remember how to do all that. > > >> > > > >> > Michael > > >> > > > >> > > > >> > On Fri, May 12, 2017 at 1:44 PM, Edward Koenig < > [email protected] > > > > > >> > wrote: > > >> > > > >> > > Michael > > >> > > If the new version boots and you can ssh to log in, then most > likely > > >> > > either X.org or a GPU driver did not update fully or correctly. > This > > >> is > > >> > > very typical for proprietary nvidia drivers, or any proprietary > > >> hardware > > >> > > drivers that install a kernel module. You might try using the > > command > > >> > line > > >> > > tools to reinstall the GPU and X bits. I'm not sure it Ubuntu > > >> switched > > >> > to > > >> > > wayland with this release so perhaps check on that. Remember to > > read > > >> the > > >> > > release notes etc before clicking "upgrade" > > >> > > > > >> > > Nuking from orbit, as Dick suggests after backup, will certainly > > work. > > >> > > Personally run a Linux distribution to avoid such "windowesque" > > fixes. > > >> > > > > >> > > Ed > > >> > > > > >> > > > > >> > > > On May 12, 2017, at 11:36 AM, Dick Steffens < > > [email protected]> > > >> > > wrote: > > >> > > > > > >> > > >> On 05/12/2017 11:24 AM, Michael Barnes wrote: > > >> > > >> I rebooted again and at the grub screen chose 14.04LTS. > > Everything > > >> > came > > >> > > up > > >> > > >> normally. After login, I get a pop-up window that says 14.04 is > > out > > >> > > dated > > >> > > >> and no longer supported. Anyhow, display and everything works, > > so I > > >> > > know at > > >> > > >> least the hardware is okay. Shutdown and restart, let grub > screen > > >> > choose > > >> > > >> default and back to blank screens. I can ssh in and shutdown > from > > >> > remote > > >> > > >> session. Screens give Ubuntu shutdown splash just before power > > off. > > >> > > > > > >> > > > Having been on this list a fairly long time, I've followed the > > >> advice > > >> > of > > >> > > > others who say one should not use the "upgrade" path to move > from > > >> one > > >> > > > Ubuntu release to another, but should start with a fresh > install. > > I > > >> > have > > >> > > > gone from Ubuntu 10 to 12 to 14, and am slowly moving to 16. > Each > > >> time > > >> > I > > >> > > > had the luxury of being able to at least put in a fresh hard > drive > > >> for > > >> > > > the new version, and then mount the old hard drive to be able to > > >> copy > > >> > > > files as needed. I don't think any of the episodes has been > > >> painless, > > >> > > > since it seems there's always something big that changes so that > > it > > >> > > > doesn't work the way it did in the previous version, but I have > > >> always > > >> > > > been able to get past it, often with the help of folks on this > > list. > > >> > > > > > >> > > > So, in your case, I'd recommend using Grub to boot to your > > previous > > >> > > > version, find a way to back up all your important files, and > > >> install 16 > > >> > > > from scratch. Better would be to have two machines, but not > > everyone > > >> > has > > >> > > > that luxury. I'm happy that I do have that option this time, > > because > > >> > > > there are a handful of things I have yet to be able to figure > out > > >> how > > >> > to > > >> > > > do in 16 that I need on at least a weekly basis, if not a daily > > one. > > >> > > > > > >> > > > -- > > >> > > > Regards, > > >> > > > > > >> > > > Dick Steffens > > >> > > > > > >> > > > _______________________________________________ > > >> > > > PLUG mailing list > > >> > > > [email protected] > > >> > > > http://lists.pdxlinux.org/mailman/listinfo/plug > > >> > > _______________________________________________ > > >> > > PLUG mailing list > > >> > > [email protected] > > >> > > http://lists.pdxlinux.org/mailman/listinfo/plug > > >> > > > > >> > _______________________________________________ > > >> > PLUG mailing list > > >> > [email protected] > > >> > http://lists.pdxlinux.org/mailman/listinfo/plug > > >> > > > >> _______________________________________________ > > >> PLUG mailing list > > >> [email protected] > > >> http://lists.pdxlinux.org/mailman/listinfo/plug > > >> > > > > > > > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
