Raspberry Pi Forums

- I wonder if anyone could offer some clues about what might be preventing my "sudo apt-get update" from running correctly.
- I have also tried to install Geany after installing Synaptic. I think the Synaptic install went ok but I am not sure.
- I have put some of the Terminal output below. The wireless network is working correctly as far as I know.

Regards,
Rob H.

Unable to update correctly
------------------------------------

pi@raspberrypi ~ $ sudo apt-get update
Hit http://archive.raspberrypi.org wheezy Release.gpg
Get:1 http://mirrordirector.raspbian.org wheezy Release.gpg [490 B]
Hit http://raspberrypi.collabora.com wheezy Release.gpg

... mass of blurb ... then

Err http://mirrordirector.raspbian.org wheezy/main armhf Packages
Cannot initiate the connection to mirrordirector.raspbian.org:80 (5.153.225.207). - connect (101: Network is unreachable)
Err http://mirrordirector.raspbian.org wheezy/contrib armhf Packages

.. repeated many times ...

... then ...
W: Failed to fetch http://mirrordirector.raspbian.org/rasp ... f/Packages Cannot initiate the connection to mirrordirector.raspbian.org:80 (5.153.225.207). - connect (101: Network is unreachable)

... then ...
E: Some index files failed to download. They have been ignored, or old ones used instead.
pi@raspberrypi ~ $

Unable to install Geany
-----------------------

pi@raspberrypi ~ $ sudo apt-get install geany
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
geany-common
Suggested packages:
doc-base
The following NEW packages will be installed:
geany geany-common
0 upgraded, 2 newly installed, 0 to remove and 17 not upgraded.
Need to get 3,401 kB of archives.
After this operation, 8,682 kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Err http://mirrordirector.raspbian.org/raspbian/ wheezy/main geany-common all 1.22+dfsg-2
Could not resolve 'mirrordirector.raspbian.org'
Err http://mirrordirector.raspbian.org/raspbian/ wheezy/main geany armhf 1.22+dfsg-2
Could not resolve 'mirrordirector.raspbian.org'
Failed to fetch http://mirrordirector.raspbian.org/rasp ... -2_all.deb Could not resolve 'mirrordirector.raspbian.org'
Failed to fetch http://mirrordirector.raspbian.org/rasp ... _armhf.deb Could not resolve 'mirrordirector.raspbian.org'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
pi@raspberrypi ~ $

It looks like network/internet errors. "Network unreachable" and "Could not resolve..." are typical network errors.

What is the result of:

- On my Raspberry Pi it is ===> "bash: nslookup: command not found"

- Trying the same command on my Linux laptop gives:-
" ~$ nslookup mirrordirector.raspian.org
Server: 127.0.0.1
Address: 127.0.0.1#53

Non-authoritative answer:
Name: mirrordirector.raspian.org
Address: 92.242.132.15

Regards,
Rob H.

Regards,
Rob H.

On the RPi try:

Could we try to stick to giving the Enquirer advice that will work 'out of the box' on Raspbian?

@heatonrb - you originally said "The wireless network is working correctly as far as I know." I think the errors you have posted indicate otherwise. If you can fix it that your RPi has working access to the Internet I am pretty sure the installation procedures you have tried will work correctly.

Aren't nslookup and host 'out of the box' commands? I believe they are, at least on my recently installed raspbian image.

If not available on the on the OP's RPi, he can try to put the following line in his 'out of the box' /etc/resolv.conf
And comment out the other nameserver entries.

ripat wrote:Aren't nslookup and host 'out of the box' commands? I believe they are, at least on my recently installed raspbian image.

Not for me -

- Thanks for your assistance. Replacing the SD card with another has solved the problem. I have been able to update correctly and install Geany.

- I suspect that on the faulty SD card the WiFi dongle was incorrectly configured

- Thanks for your suggestions

Rob H.

Hi,
I had the same problem with a diffent package.
Solved by setting the gateway to the default route.
If your ip is something like this....98.99.100.200
rasp@berry:~# route add default gw 98.99.100.1

Greets, raf_qpsk