Page 1 of 3
WH is not starting after installation
Posted: Sun Dec 04, 2022 1:38 pm
by DG8KD
Hi,
I used 4 different SD cards (all 16GB different vendors), used the old legacy Buster with Desktop image from April 2022 and still failing to get WH running.
After the installation of WH via those three lines of commands the Rasperberry reboots, but I am getting always only this screen:
(I had to rebuild my SD as it fails after the latest RPi update...)
Any ideas / hints / clues?
vy 73
Rainer
Re: WH is not starting after installation
Posted: Sun Dec 04, 2022 2:17 pm
by G4EWJ
First check the supply voltages at the jumpers.
I assume that it booted OK before doing the WH installation?
Can you ssh into it and start htop to see if any WH processes are running.
If you are using a keyboard, try this to get past the frozen screen and log in. Run htop.
https://forums.raspberrypi.com/viewtopic.php?t=246236
If no WH processes are running, try starting WH manually in AnyHub mode:
cd /home/pi/winterhill/RPi-3v20
sudo ./winterhill-3v20 0 9900 0 0 0 0 0
Brian
Re: WH is not starting after installation
Posted: Sun Dec 04, 2022 3:11 pm
by DG8KD
Thanks Brian.
All voltages checked: 5,12V , 3,2 V and 1,1V, seems to be ok.
htop does not show anything related to WH.
The mentioned commands are not stopping the rc-local process.
After starting WH in Anyhub mode it shows the receiving of the DATV beacon.
Re: WH is not starting after installation
Posted: Sun Dec 04, 2022 4:31 pm
by G4EWJ
That part seems to be working, but the beacon is not being received on RX3. Do you have an antenna connected to NIM_B?
To see if the local display works, reboot and run ./whlaunch-local-3v20.sh and see if the beacon is displayed.
Brian
Re: WH is not starting after installation
Posted: Mon Dec 05, 2022 2:58 pm
by DG8KD
Hi Brian,
Local decoding is not working, comes back with errors...
Today I opened a new sealed MicroSD card and build a new card, but still the same behavior...
73
Rainer
Re: WH is not starting after installation
Posted: Mon Dec 05, 2022 5:26 pm
by G4EWJ
Were you using the attached keyboard rather than an SSH login? You need to be using the keyboard to start the launch files.
If you were using the keyboard, then it looks like you have no graphical display.
So to summarise the situation:
When you first boot up after making an SD card, you see the normal desktop display?
After installing WH and rebooting, it is stuck at rc-local.service?
If you start ./winterhill-3v20 0 9900 0 0 0 0 0 manually, it works correctly from a PC in AnyHub mode?
Brian
Re: WH is not starting after installation
Posted: Mon Dec 05, 2022 6:36 pm
by DG8KD
Were you using the attached keyboard rather than an SSH login? You need to be using the keyboard to start the launch files.
Code: Select all
[b]No command line, no input possible, so only remote keyboard via ssh[/b]
If you were using the keyboard, then it looks like you have no graphical display.
So to summarise the situation:
When you first boot up after making an SD card, you see the normal desktop display?
After installing WH and rebooting, it is stuck at rc-local.service?
]
If you start ./winterhill-3v20 0 9900 0 0 0 0 0 manually, it works correctly from a PC in AnyHub mode?
[/b]
Re: WH is not starting after installation
Posted: Mon Dec 05, 2022 7:56 pm
by G4EWJ
I'll do a new SD card and installation, to check that nothing has changed.
Brian
Re: WH is not starting after installation
Posted: Tue Dec 06, 2022 12:29 am
by G4EWJ
The install worked OK. I've re-wired my WH to do some tests, so it can't display any video with the standard WH version, but it did display the 4 VLC windows and it didn't hang up at rc-local.service. Maybe G8GKQ will have some ideas.
Can you post your /etc/rc.local and /boot/config.txt files please. They may contain a clue.
Brian
Re: WH is not starting after installation
Posted: Tue Dec 06, 2022 9:16 am
by g0mjw
DG8KD wrote: ↑Mon Dec 05, 2022 6:36 pm
Were you using the attached keyboard rather than an SSH login? You need to be using the keyboard to start the launch files.
Code: Select all
[b]No command line, no input possible, so only remote keyboard via ssh[/b]
Surely this is the problem - using an attached screen but a remote keyboard?