Sorry to hear the Trisquel 6 to 7 upgrade didn't work so well. Me, I would
either start over by reinstalling the good working Trisquel 6, or burn a
Trisquel 7 'mini' install to a dvd and try installing from that directly.
But
You might try this regarding Internet connection
(you can do 'ipconfig \all' in Windows to learn what ip is working in Windows
and repeat that with the gateway most likely being xxx.xxx.xxx.1 whereas your
ip is xxx.xxx.xxx.not 1. My example below uses a fairly standard default home
network - 192.168.0.0 but others certainly exist.)
In terminal:
$ ip link
---just to make sure what eth0 is called,
Mine is called enp2s0 but ifconfig -a shows that also so since ifconfig -a in
yours shows eth0 I will assume it's safe to assume dev name is eth0.
$ ip link show dev eth0
---just to make sure it's UP,
---if it's not, try
$ ip link eth0 set up
$ ip addr 192.168.0.100/24 broadcast 192.168.0.255 dev eth0
---Guessing about your network. .255 is usually the broadcast address
---Also guessing that no other device already using .100.
$ ip route add default via 192.168.0.1
---in the above example, the router/gateway's ip would usually be 192.168.0.1
Then you need to add nameservers to /etc/resolv.conf, I use openNIC name
servers but you might work to use your gateway as nameserver also. Additions
made to /etc/resolv.conf may only be temporary as it says in mine at the top
of the file:
"# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN"
if all that worked, a '$ ping -c 1 google.com' should resolve to google's ip
address more or less instantly.
( I did an install recently that needed for me to perform these steps and I
am reading from the notes I made, three other commands I noted I will pass on
just in case they would be needed: $ ip addr flush dev eth0 - $ ip route
flush dev eth0 - $ ip link set eth0 down - these will erase what you've done
so you can start over)
Seems like some daemon that is supposed to set up your Internet connection
isn't starting. NetworkManager maybe. If the above works you might have to do
it every time you reboot because the service that is supposed to take care of
it isn't running.
