Hi,
I’m totally new with Raspberry Pi and have purchased a Pi 4 4Gb and DVB TV HAT.
Following the guide:
[Getting-started-with-the-Raspberry-Pi-TV-HAT.pdf (raspberrypi.org)] to get it to run on the Pi with monitor and keyboard, I get all the way through page 1.
When I put in the IP address to install with the browser - I get an error “address is unreachable” (either on the Pi or another PC).
I’ve updated, uninstalled and re-installed TVHeadend still with no luck.
Can anyone point me in the right direction?
Cheers, Dave
Hi Dave, Welcome to the forum!
Was this the guide you were following?
If so, you’re stuck on this step, right?
Could you send us the output of the ifconfig command? Also a photo of your Pi and HAT?
Keen to get to the bottom of this with you!
Hi James,
Yes that’s what I’m following. Thanks for the offer to help.
ifconfig:
dave327@raspberrypi:~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether [redacted] txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 33 bytes 4119 (4.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 33 bytes 4119 (4.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.8.114 netmask 255.255.255.0 broadcast 192.168.8.255
inet6 [redacted prefixlen 64 scopeid 0x20<link>
inet6 [redacted] prefixlen 64 scopeid 0x0<global>
ether [redacted] txqueuelen 1000 (Ethernet)
RX packets 224 bytes 64374 (62.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 207 bytes 27466 (26.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
1 Like
Hi Dave,
Cheers for posting that info!
Just to confirm, are you replacing raspberrypi.local in the address given in the guide with 192.168.8.114? Most of the time raspberrypi.local will work, but it relies on the Bonjour service, which some machines don’t have installed/enabled.
If you have a desktop environment on your Pi, you could try http://127.0.0.1:9981/extjs.html from the Pi’s browser.
As this doesn’t need any external networking, the lo or loopback interface is what directs the packets back at the Pi.
Alternatively, I like to check that other devices can see my Pis, and that the right ports are open. I personally like the Net Analyser app for Android, but a simple ping command from other devices on your network will work out whether they can reach .
Keen to see how you go with these steps!
1 Like
Hi James,
I had the right address. However, I tried a different network and it now seems to be OK.
I’ll move through the rest of the guide.
Thanks for your help.
Dave
1 Like
