Raspberry Pi Forums

Posted: **Thu Aug 24, 2017 8:00 am**

I'm new to the community and I just started using my Raspberry Pi (1) Model B. I installed the latest jessie with Pixel desktop, but Chromium is timing out for every website, even Google. I'm connected by ethernet cable and the cable works; I've was able to get Chromium to work on a Pi 3 Model B with same connection.

I'm very new to Linux and really don't know much about it. What can I do to get the browser working on my older Pi? I'd like to download the updates and install files from the internet using Chromium. Any help is welcome.

Posted: **Thu Aug 24, 2017 12:30 pm**

do you have the RPi1 with 256MB or the RPi1 with 512MB?
i am currently flashing Raspbian Stretch to my RPi1 256MB... if it is done, i can tell you if chromium is working there.

EDIT: actually i installed 2017-08-16-raspbian-stretch.img to a 16GB SD card and plugged it into my PRi1 (rev.1) with 256MB.
just without any modification of the configuration, Chromium works more or less.

it is able to download webpages and render them. but extremly slow.

open "https://duckduckgo.com", page takes ~3 minutes to begin render its content. after total time of 9 minutes, the page was fully loaded and the CPU goes from 100% down to ~15%.

open "https://google.com", page takes ~3 minutes to begin render its content. after total time of 12 minutes, the page was fully loaded and the CPU goes from 100% down to ~68%.

so, from my side, there is internet working out of the box - chromium is working on a RPi1 rev.1 256MB at 700MHz CPU.
but to me it is not usable, because it is that extremely slow.
(normally i have only the lite version installed on my old RPi1 - that makes more sense to me)

i did not over clock the CPU!
i did not changed the memory split!
i did not update or upgrade anything for that test!
i did not run raspi-config nor rc-gui!
i just flashed the SD and boot (and auto resize).

you can over clock the CPU up to 1000MHz, that makes some things working faster, but maybe also a bit more unstable.
you can increase the memory split but on a RPi1 rev.1 with only 256MB, there is not much left when you increase the split.

Posted: **Thu Aug 24, 2017 5:21 pm**

do you have the RPi1 with 256MB or the RPi1 with 512MB?

I have the RPi1-B with 512MB, no over clocking, just straight out the box with a 16GB SD card and the Raspbian image.

When I use Chromium, and try to go to Google.com, chromium gives a timeout message, and does not load the page. Every web page I try to view using Chromium always times out, and Chromium displays the timed [Retry] page.

Again, I'm completely new to Linux, and the Pi, so I have no idea how to trouble shoot this.

Any help is appreciated.

Posted: **Thu Aug 24, 2017 7:41 pm**

is only chromium affected from that time out?
i am not familiar with chromium, so i don't know, what will let chronuim run into time out.

you can successfully ping to google?

Code: Select all

pi@raspberry:~$ ping google.com
PING google.com (172.217.18.14) 56(84) bytes of data.
64 bytes from google.com (172.217.18.14): icmp_seq=1 ttl=55 time=23.5 ms
64 bytes from google.com (172.217.18.14): icmp_seq=2 ttl=55 time=23.2 ms
64 bytes from google.com (172.217.18.14): icmp_seq=3 ttl=55 time=23.1 ms
64 bytes from google.com (172.217.18.14): icmp_seq=4 ttl=55 time=23.1 ms
64 bytes from google.com (172.217.18.14): icmp_seq=5 ttl=55 time=23.1 ms
^C
--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 23.123/23.245/23.506/0.170 ms

you say you use the latest raspbian jessie image. but the current image is raspbian stretch now from 2017-08-16.
will this make a different?

Posted: **Thu Aug 24, 2017 8:40 pm**

I've tried ping 8.8.8.8 which gives results, but some tries have errors. for example:

Code: Select all

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq-1 ttl=57 time-2.19 ms
64 bytes from 8.8.8.8: icmp_seq-2 ttl=57 time-2.19 ms
. . .
64 bytes from 8.8.8.8: icmp_seq-32 ttl=57 time-2.19 ms
wrong data byte #33 should bo 0x21 but was 0x29
. . . 
64 bytes from 8.8.8.8: icmp_seq=116 ttl=57 time=2.19 ms
64 bytes from 8.8.8.8: icmp_seq=117 ttl=57 time=2.19 ms

I didn't realize there was an update for jessie image on 2017-08-16. I'll have to download that and try it, that may help. Also, I'll try and ping google.com, later tonight, and post the results.

Posted: **Fri Aug 25, 2017 8:25 am**

So I updated to latest Jessie Release (2017-08-16). I'm able to ping google:

Code: Select all

ping google.com
PING google.com (172.217.9.174) 56(84) bytes of data.
64 bytes from dfw25s27-in-f14.1e100.net (172.217.9.174): icmp_seq2 ttl=51 time=64.0 ms
64 bytes from dfw25s27-in-f14.1e100.net (172.217.9.174): icmp_seq3 ttl=51 time=64.2 ms
wrong data byte #49 should be 0x31 but was 0x39
#8      8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27
#40     28 29 2a 2b 2c 2d 2e 2f 30 39 32 33 34 35 36 37
64 bytes from dfw25s27-in-f14.1e100.net (172.217.9.174): icmp_seq4 ttl=51 time=64.8 ms
64 bytes from dfw25s27-in-f14.1e100.net (172.217.9.174): icmp_seq5 ttl=51 time=63.6 ms
64 bytes from dfw25s27-in-f14.1e100.net (172.217.9.174): icmp_seq6 ttl=51 time=64.7 ms
64 bytes from dfw25s27-in-f14.1e100.net (172.217.9.174): icmp_seq7 ttl=51 time=63.3 ms
^C
--- google.com ping statistics ---
7 packets transmitted, 6 received, 14% packet loss, time 6060ms
rtt min/avg/max/mdev = 63.335/64.163/64.878/0.618 ms

However, when I use Chromium, every website does not display and gives an ERR_TIMED_OUT message.

Code: Select all

pi@raspberrypi:~ $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
        valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
2: enxb827eb8d7b75: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:8d:7b:75 brd ff:ff:ff:ff:ff:ff
    inet 172.168.1.114/24 brd 172.168.1.255 scope global enxb827eb8d7b75
        valid_lft forever preferred_lft forever
    inet6 fe80::fa1c:aa31:4350:20aa/64 scope link
        valid_lft forever preferred_lft forever
pi@raspberrypi:~ $

again I'm connected using an ethernet cable.

Any help is appreciated greatly.

Raspberry Pi Forums

Pi (1st generation) Model B internet connection trouble

Pi (1st generation) Model B internet connection trouble

Re: Pi (1st generation) Model B internet connection trouble

Re: Pi (1st generation) Model B internet connection trouble

Re: Pi (1st generation) Model B internet connection trouble

Re: Pi (1st generation) Model B internet connection trouble

Re: Pi (1st generation) Model B internet connection trouble