TNAP-7 Image Discussion
- Thread starter el bandido
- Start date
el bandido
TNAP-Images
Get rid of the static ip and set it to DHCP. Save, exit, reboot.
No improvement !
el bandido
TNAP-Images
As for the Network Manager itself, I cannot find anything that is broken in it. Everything I have tried works as advertised. Several things were added in the Network Manager to modernize it. If you do not update something like the Network Manager, then some will ask: "Why?" If you do update then some will say: "It is broken." Cannot win either way, so I choose the updated version.
I spent like 8 hours looking at the Network part of the image, and while I did not find anything that was broken, several things were improved. For example, The image backups did not contain wpa_supplicant.wlan0.conf. This means the settings for the Network were not being restored or partially restored. On image reboot after image install, my NIC was assigned 192.168.1.161, but my wifi is set to 192.168.1.4. So the receiver opened with 192.168.1.161, assigned 192.168.1.4 to the wifi and stopped there with the receiver showing the wifi address as valid, but in reality, the receiver was still on 192.168.1.161 until a reboot took place.
We have made some changes. And in the process I mean right in the middle of the network edits, here comes a large image update. Which I guess now is as good of time as any other. When the new images come up, Flash them. Online update will not be suggested. Python and other things are upgraded:
Image updates:
This works for me without issue. The wifi adapter being used is Ancient.
I spent like 8 hours looking at the Network part of the image, and while I did not find anything that was broken, several things were improved. For example, The image backups did not contain wpa_supplicant.wlan0.conf. This means the settings for the Network were not being restored or partially restored. On image reboot after image install, my NIC was assigned 192.168.1.161, but my wifi is set to 192.168.1.4. So the receiver opened with 192.168.1.161, assigned 192.168.1.4 to the wifi and stopped there with the receiver showing the wifi address as valid, but in reality, the receiver was still on 192.168.1.161 until a reboot took place.
We have made some changes. And in the process I mean right in the middle of the network edits, here comes a large image update. Which I guess now is as good of time as any other. When the new images come up, Flash them. Online update will not be suggested. Python and other things are upgraded:
Image updates:
This works for me without issue. The wifi adapter being used is Ancient.
Megatron817
Administrator
I did that too, but no joy.
el bandido
TNAP-Images
el bandido
TNAP-Images
Excellent!
Please test new driver: ustym4kpro-20261024 multiboot
Cool. Sometimes easy to overlook. Sometimes ambiguous too. Especially when paired up with, like you saw.....'if i use wpa2 on the router, 2 & 3????? must be the hot ticket'. Then the cussing starts.
Were you not also having problems with the Ethernet port?
I was curious because my wifi connection to router from the osmio has been rock solid. On ViX anyways....
Dug into /lib/modules/5.15.0/extra. Then opened wlan.ko in notepad++
Around line 28787 started seeing text that looks like debugging info. Queried? Blurted out to the os? Don't know.
/usr/src/debug/wlan-qcacld-20/4.5.25.55....bla-bla-bla like it points to a directory not present in ViX (at least).
There's some pretty verbose crap present. After that my vision got blurry.
Wouldn't it have been nice to see an in-your-face 'dumbass is using the wrong encryption scheme'? lol!
el bandido
TNAP-Images
Correct, and that’s expected. A LAN connection has no encryption setting on any device, because a cable doesn’t need one. WPA2/WPA3 only protect the wireless link between a Wi-Fi device and the router. Your router’s “WPA3-Personal” setting has no effect on its LAN ports. So nothing is missing on your Zero4K, and the image isn’t restricting anything. Plug it in and it’s done.
stephan94
Legit VIP
Unfortunately, the blind scan does not work at all; it is still searching using the blind scan settings for the SF 8008 (Octagon), which is incorrect.
Many menus still refer to the 8008 (for example, the signal finder), even though this is an Ustym 4K PRO.
Attachments
el bandido
TNAP-Images
Excellent! Thanks for testing. If the blindscan binary in /usr/bin was changed to octagon-blindscan it would work. I will give instructions if you want to do that. Or you may install the 1023 image.
el bandido
TNAP-Images
Unzip the attached file. Place octagon-blindscan into /usr/bin of the ustym4kpro receiver.
Then using Telnet or Terminal:
chmod +x /usr/bin/octagon-blindscan
reboot
Satellite Blindscan will work.
Megatron817
Administrator
Been using the VU+zero4k today. I set up multiboot on it using openatv so what can be done is have two versions of TNAP 7. One with the Radio fix (10/24 image) and one without and when we want to use the AAC radio just boot in that slot. Normal everyday TV use another slot. That audio sync issue is seen on Satellite timeshift and recordings on all services ATSC. Multiboot and TNAP7 has really made this zero4k great again. Thanks.