Try booting the machine...or power down.
then click the "dash" the button upper left in the launcher
then type in..terminal...that should give you a terminal choice.
Try booting the machine...or power down.
then click the "dash" the button upper left in the launcher
then type in..terminal...that should give you a terminal choice.
Craving anchovy, herring and squid pizza.....with clam sauce
Come to #ubuntuforums! We have cookies! | Basic Ubuntu Security Guide
Tomorrow's an illusion and yesterday's a dream, today is a solution...
Got my terminal back, I switched to another theme, and uninstalled the theme I was usingCode:charles@Raspberry:~$ sudo ifconfig eth0 down [sudo] password for charles: charles@Raspberry:~$ sudo ifconfig eth0 up charles@Raspberry:~$ sudo modprobe -v tg3 charles@Raspberry:~$ sudo cat /var/log/syslog | grep -e tg3 -e etwork | tail -n25 May 23 22:00:18 Raspberry NetworkManager[1211]: <info> address 192.168.8.101 May 23 22:00:18 Raspberry NetworkManager[1211]: <info> prefix 24 (255.255.255.0) May 23 22:00:18 Raspberry NetworkManager[1211]: <info> gateway 192.168.8.1 May 23 22:00:18 Raspberry NetworkManager[1211]: <info> nameserver '198.88.216.2' May 23 22:00:18 Raspberry NetworkManager[1211]: <info> nameserver '198.88.216.3' May 23 22:00:18 Raspberry NetworkManager[1211]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... May 23 22:00:18 Raspberry NetworkManager[1211]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started... May 23 22:00:19 Raspberry NetworkManager[1211]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0] May 23 22:00:19 Raspberry NetworkManager[1211]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete. May 23 22:00:19 Raspberry NetworkManager[1211]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0] May 23 22:00:19 Raspberry NetworkManager[1211]: <info> Policy set 'Saluki' (wlan0) as default for IPv4 routing and DNS. May 23 22:00:19 Raspberry NetworkManager[1211]: <info> DNS: starting dnsmasq... May 23 22:00:19 Raspberry NetworkManager[1211]: <warn> dnsmasq not available on the bus, can't update servers. May 23 22:00:19 Raspberry NetworkManager[1211]: <error> [1369364419.935950] [nm-dns-dnsmasq.c:402] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name May 23 22:00:19 Raspberry NetworkManager[1211]: <warn> DNS: plugin dnsmasq update failed May 23 22:00:19 Raspberry NetworkManager[1211]: <info> Writing DNS information to /sbin/resolvconf May 23 22:00:20 Raspberry NetworkManager[1211]: <info> Activation (wlan0) successful, device activated. May 23 22:00:20 Raspberry NetworkManager[1211]: <warn> dnsmasq appeared on DBus: :1.51 May 23 22:00:20 Raspberry NetworkManager[1211]: <info> Writing DNS information to /sbin/resolvconf May 23 22:00:39 Raspberry NetworkManager[1211]: <info> (wlan0): IP6 addrconf timed out or failed. May 23 22:00:39 Raspberry NetworkManager[1211]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... May 23 22:00:39 Raspberry NetworkManager[1211]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started... May 23 22:00:39 Raspberry NetworkManager[1211]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete. May 23 22:04:29 Raspberry NetworkManager[1211]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted May 23 22:11:28 Raspberry kernel: [ 726.736209] tg3 0000:09:00.0: irq 45 for MSI/MSI-X charles@Raspberry:~$
Screenshot from 2013-05-23 22:23:34.pngThis is odd, I used to have a "wired network 1" listed here...now I don't anymore. Do you think that is the problem?
I downloaded the messed-up code for your 'base-64' image before CharlesA removed it. I fixed the code, and what I see WAS a terminal (see attachment). It could have been stuck. Wondering what theme it was
PS:
For Mods : copy code after 'base64,' as text > cat inputfile | base64 --decode > outputfile ; reference : http://ubuntuforums.org/showthread.php?t=2097846
Although what CharlesA did was a better solution - teaching users the correct use to avoid such bugs
Nothing still,Code:charles@Raspberry:~$ sudo modprobe -v tg3 [sudo] password for charles: charles@Raspberry:~$ sudo ifconfig eth0 down charles@Raspberry:~$ sudo ifconfig eth0 up charles@Raspberry:~$ sudo ifconfig eth0 down charles@Raspberry:~$ sudo ifconfig eth0 192.168.8.110 charles@Raspberry:~$ ping -c4 192.168.8.1 PING 192.168.8.1 (192.168.8.1) 56(84) bytes of data. From 192.168.8.110 icmp_seq=1 Destination Host Unreachable From 192.168.8.110 icmp_seq=2 Destination Host Unreachable From 192.168.8.110 icmp_seq=3 Destination Host Unreachable --- 192.168.8.1 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms pipe 4 charles@Raspberry:~$ ping -c4 192.168.8.1 PING 192.168.8.1 (192.168.8.1) 56(84) bytes of data. From 192.168.8.110 icmp_seq=1 Destination Host Unreachable From 192.168.8.110 icmp_seq=2 Destination Host Unreachable From 192.168.8.110 icmp_seq=3 Destination Host Unreachable From 192.168.8.110 icmp_seq=4 Destination Host Unreachable --- 192.168.8.1 ping statistics --- 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3016ms pipe 3 charles@Raspberry:~$
Reseting the BIOS scares me...I had the problem of the machine not shutting down for the longest time because it would freeze on the Ubuntu splash screen. I finially got it working by using my "Boot Repair" .iso image. Can we try something else before I mess around with the BIOS?
Here's the theme pack which my machine did not likeCode:sudo add-apt-repository ppa:noobslab/themes sudo apt-get update sudo apt-get install zoncolor-themes
are you using network mgr...or wcid?
*If you are using network mrg, then do.
thanksCode:sudo service network-manager restart
Last edited by Hadaka; May 24th, 2013 at 04:50 AM.
Craving anchovy, herring and squid pizza.....with clam sauce
Like mentioned in the launchpad answer page I linked to, see if the IRQ (Interrupts) are set to be "Set by the system" (or "Auto" or something similar) in your BIOS.
Something important - if your system is UEFI based and this is an EFI based installation, it may not be a good idea to reset the BIOS. I should have mentioned that earlier, I forgot, sorry. Besides, this is only one of a few possibilities, not necessarily the actual reason for the problem. So too much risk may not be worth unless everything else is ruled out.
Just see if there is an "auto" or "set by system" type setting for IRQs or not in the BIOS. Let us know if all the settings are manual.
Also, please install ethtool -
..then run it and post back its output -Code:sudo apt-get install ethtool
It may give us more hints about what is going on.Code:sudo ethtool eth0
I tried this, and I still had no network manager. So I then Added "Ethernet Connection 1" and made sure the tabs were correct in your earlier reply (4 attachments) and I do have wired connection by hooking up directly to the modem, this is what was always available to me. So I do have that...just not a wired connection through the routerScreenshot from 2013-05-24 19:14:13.pngCode:charles@Raspberry:~$ sudo service network-manager restart [sudo] password for charles: network-manager stop/waiting network-manager start/running, process 3369 charles@Raspberry:~$
Bookmarks