new GBQUAD4K no longer responding to its remote control handset

[piran]

I've had the same problem. Hold down TV and 0 to reset R/C. R/C will flash once, then a pause and 3 more flashes. After that all should be OK.

Noted, with thanks. Think I'm running 'OK' now.

Style-over-substance choosing to write GIGA in dark red on a tiny black button that virtually disables the entire system with no warning markers... just saying from the POV of one of the ancients with fading eye-sight.

Fiddling about with the network settings, locked up the box, got logging command line and an imposed reboot. It's happened several times.

I also managed to seize everything up SOLIDLY - apparently just going through some of its menus. That's unreasonable, traversing menus should be buffered. I'm not using a sledgehammer or chainsaw. Nothing budged until I (had to) hit the power (again).

FWIW all my stuff is on multiple UPSs. This box and its OS is a little worrying, it's more unstable than anything that I have recently used. I'm from back in the days of early DOS, dial-up modems with data throughput 'measured' in bauds not Xbps ...well before the arrival of the internet. Sorry but us oldies expect more stability and reliability with our shiny new toys:-)

The system has already asked me to file several logs somewhere but I didn't catch quite where before it ran the enforced reboot. I'd like to help get this stuff developed to be more robust ...with more built-in resilience. My regular LINUX server runs (headlessly) for weeks, hell, months and more without attention other than remotely implementing the occasional upstream patch. The previous hardware I built wasn't opened for years (plural) running 24/7 autonomously.

Sincerely hope the developers are still beavering away on the code. I may have bugs for them.

PostEdit: typo

[adm]

The system has already asked me to file several logs somewhere but I didn't catch quite where before it ran the enforced reboot.

The box produces crash and debug logs that can be posted to these forums.

To enable debug logs.
Menu -> settings -> system -> logs -> settings -> enable debug logs

you can also see your crash and debig logs at
Menu -> settings -> system -> logs -> settings -> log manager (pressing red toggles between the two type of logs)


In case you haven't found it yet
Menu -> setup -> system -> customise -> setup mode = expert (this gives more menu options)

[piran]

The box produces crash and debug logs that can be posted to these forums.
To enable debug logs.
Menu -> settings -> system -> logs -> settings -> enable debug logs

Will do so ...probably tomorrow (busy with family birthday today).

The box produces crash and debug logs that can be posted to these forums.
you can also see your crash and debig logs at
Menu -> settings -> system -> logs -> settings -> log manager (pressing red toggles between the two type of logs)

Noted.

The box produces crash and debug logs that can be posted to these forums.

Is that on public view (ref: spiders and search engines, scrapers, skimmers, bad actors etc)? Also stuff 'calling-home' tends to trip alarms all over the place (by my design) so I may have to dig deep to appropriately whitelist. Tomorrow ...as above

In case you haven't found it yet
Menu -> setup -> system -> customise -> setup mode = expert (this gives more menu options)

Ummm... yes, I was actually in 'expert mode' already. Whilst not an 'expert', with my experience of general satellite receivers being less than a week - starting from nothing at all, I tend to learn 'tech' surprisingly quickly - for my advanced age :-) You'll see.

[ccs]

Noted, with thanks. Think I'm running 'OK' now.

Style-over-substance choosing to write GIGA in dark red on a tiny black button that virtually disables the entire system with no warning markers... just saying from the POV of one of the ancients with fading eye-sight.

Fiddling about with the network settings, locked up the box, got logging command line and an imposed reboot. It's happened several times.

I also managed to seize everything up SOLIDLY - apparently just going through some of its menus. That's unreasonable, traversing menus should be buffered. I'm not using a sledgehammer or chainsaw. Nothing budged until I (had to) hit the power (again).

FWIW all my stuff is on multiple UPSs. This box and its OS is a little worrying, it's more unstable than anything that I have recently used. I'm from back in the days of early DOS, dial-up modems with data throughput 'measured' in bauds not Xbps ...well before the arrival of the internet. Sorry but us oldies expect more stability and reliability with our shiny new toys:-)

The system has already asked me to file several logs somewhere but I didn't catch quite where before it ran the enforced reboot. I'd like to help get this stuff developed to be more robust ...with more built-in resilience. My regular LINUX server runs (headlessly) for weeks, hell, months and more without attention other than remotely implementing the occasional upstream patch. The previous hardware I built wasn't opened for years (plural) running 24/7 autonomously.

Sincerely hope the developers are still beavering away on the code. I may have bugs for them.

PostEdit: typo

I don't know what you're doing, but crash logs are needed.

These boxes really are 100% reliable, I couldn't crash mine if I tried, with one possible exception when setting up a NAS password, a problem fixed in the next release.

[twol]

I don't know what you're doing, but crash logs are needed.

These boxes really are 100% reliable, I couldn't crash mine if I tried, with one possible exception when setting up a NAS password, a problem fixed in the next release.

Agree completely, but unfortunately my in laws have taught me that if the receiver can be placed in a state that it appears to be not operational then some people are quite capable of doing so by an unusual combination of remote buttons!

[piran]

Agree completely, but unfortunately my in laws have taught me that if the receiver can be placed in a state that it appears to be not operational then some people are quite capable of doing so by an unusual combination of remote buttons!

Agreed. Prime case of QED;-)

[piran]

I don't know what you're doing, but crash logs are needed.

See my earlier reply.

These boxes really are 100% reliable

Mmmm... we'll see...

I couldn't crash mine if I tried, with one possible exception when setting up a NAS password, a problem fixed in the next release.

Noted. I seem to have a knack (curse) of readily falling over bugs and any code weakness... I've effectively been alpha/beta testing for four decades and have generally found that stuff needs to be pretty bomb-proof to get by. This box needs more armouring:-)