30 replies to this topic

[nerron]

nerron

Maybe need re-install openpli-develop-hd66se-20241211_recovery_emmc.zip

 

 

Thanks, I'll give it a try.

I actually have this one

openpli-9.0-release-hd66se-20241104_recovery_emmc.zip/

[WanWizard]

Post #17 clearly shows the wifi hardware is detected on cold boot, the driver is loaded, the interface is created, and the interface having a local LAN IP address.

 

So I'm a bit clueless to what exactly the problem is now, and the original complaint was "no wifi interface after cold boot" ?

[nerron]

Post #17 clearly shows the wifi hardware is detected on cold boot, the driver is loaded, the interface is created, and the interface having a local LAN IP address.

 

So I'm a bit clueless to what exactly the problem is now, and the original complaint was "no wifi interface after cold boot" ?

 

I just redid the commands because the info in post #17 I had done by switching off via the switch and it seems to work but it seems similar to me.

I don't understand this info and I trust you if you say that everything looks good but I don't have wifi. 

 

with restart ok 

with the switch behind ok 

but via button or remote no wifi

I've flashed the recovery suggested by Dimitrij, same problem.

I saw that I could set the wifi configuration to default, same problem (before I hadn't configured the lan, I only had wifi).

 

my mutant must be haunted 

 

root@hd66se:~# lsusb

Bus 001 Device 002: ID 05e3:0610

Bus 001 Device 003: ID 0bda:c820

Bus 001 Device 001: ID 1d6b:0002

Bus 002 Device 001: ID 1d6b:0001

Bus 003 Device 001: ID 1d6b:0002

Bus 004 Device 001: ID 1d6b:0003

Bus 001 Device 004: ID 0930:6544

Bus 001 Device 005: ID 13fe:6300

 

 

ifconfig

eth0      Link encap:Ethernet  HWaddr 00:14:49:37:73:3A

          inet addr:192.168.1.23  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::214:49ff:fe37:733a/64 Scope:Link

          inet6 addr: 2a01:cb18:8a:d400:214:49ff:fe37:733a/64 Scope:Global

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:312 errors:0 dropped:163 overruns:0 frame:0

          TX packets:96 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:37995 (37.1 KiB)  TX bytes:16202 (15.8 KiB)

          Interrupt:32

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:40 errors:0 dropped:0 overruns:0 frame:0

          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1

          RX bytes:5698 (5.5 KiB)  TX bytes:5698 (5.5 KiB)

 

wlan0     Link encap:Ethernet  HWaddr A0:67:20:D4:4A:6E

          inet addr:192.168.1.17  Bcast:0.0.0.0  Mask:255.255.255.0

          inet6 addr: 2a01:cb18:8a:d400:a267:20ff:fed4:4a6e/64 Scope:Global

          inet6 addr: fe80::a267:20ff:fed4:4a6e/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:132 errors:0 dropped:22 overruns:0 frame:0

          TX packets:262 errors:0 dropped:1 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:19886 (19.4 KiB)  TX bytes:43441 (42.4 KiB)

 

 

 lsmod

Module                  Size  Used by

8821cu               2357709  0

cfg80211              435036  1 8821cu

mali                  288900  0

hd66se_4             6605805  52 mali

hd66se_3              430733  23 mali,hd66se_4

hd66se_2               31510  1 hd66se_3

hd66se_1               29576  3 hd66se_2,hd66se_3,hd66se_4

Edited by nerron, Yesterday, 18:29.

[WanWizard]

The issue is that you're not very clear with your "I have no wifi" statement.

 

Because again, this shows that the device is detected, the driver for the device is loaded, the interface (wlan0) is created, and the device has a valid IPv4 and IPv6 address (and as IPv6 is assigned by the router, this also shows your box has an operational connection to your (wifi) router.

 

So, what EXACTLY do you mean, as for me, this is all how it should be. Albeit with quite a few packet drops, so clearly not a very optimal connection.

 

edit: also quite a lot of packet drops on your wired connection, which is weird, perhaps your PC is wirelessly connected too, and that is causing the drops?

Edited by WanWizard, Yesterday, 18:34.

[nerron]

no I'm stupid I didn't look and post the right file

it's not similar in fact 

no wlan0 via cold boot without switch

 

sorry if I'm not always very clear, but I'm French and not comfortable enough with English to do without a translator.

 

root@192.168.1.23's password:

root@hd66se:~# lsmod

Module                  Size  Used by

cfg80211              435036  0

mali                  288900  0

hd66se_4             6605805  51 mali

hd66se_3              430733  23 mali,hd66se_4

hd66se_2               31510  1 hd66se_3

hd66se_1               29576  3 hd66se_2,hd66se_3,hd66se_4

root@hd66se:~# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:14:49:37:73:3A

          inet addr:192.168.1.23  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::214:49ff:fe37:733a/64 Scope:Link

          inet6 addr: 2a01:cb18:8a:d400:214:49ff:fe37:733a/64 Scope:Global

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:356 errors:0 dropped:110 overruns:0 frame:0

          TX packets:214 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:33523 (32.7 KiB)  TX bytes:31336 (30.6 KiB)

          Interrupt:32

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:36 errors:0 dropped:0 overruns:0 frame:0

          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1

          RX bytes:5396 (5.2 KiB)  TX bytes:5396 (5.2 KiB)

 

root@hd66se:~# lsusb

Bus 001 Device 002: ID 05e3:0610

Bus 001 Device 001: ID 1d6b:0002

Bus 002 Device 001: ID 1d6b:0001

Bus 003 Device 001: ID 1d6b:0002

Bus 004 Device 001: ID 1d6b:0003

Bus 001 Device 003: ID 0930:6544

Bus 001 Device 004: ID 13fe:6300

Edited by nerron, Yesterday, 18:36.

[WanWizard]

Ah, that explains .

 

Here,

Bus 001 Device 003: ID 0bda:c820

is not present, meaning the device is not detected, which in the base is a hardware problem.

 

You could try to see if it appears after issuing the command

udevadm trigger

but I doubt it.
 

[WanWizard]

Just connected my HD66SE, no issues with the wireless connection on the first boot in 15 months...

[nerron]

Ah, that explains .

 

Here,

Bus 001 Device 003: ID 0bda:c820

is not present, meaning the device is not detected, which in the base is a hardware problem.

 

You could try to see if it appears after issuing the command

udevadm trigger

but I doubt it.
 

no, the problem remains the same 

at least now I know I can start normally via the switch

it doesn't solve the problem but it allows me to use the mutant more or less normally. 

 

 

Just connected my HD66SE, no issues with the wireless connection on the first boot in 15 months...

so it's my mutant that's the problem, it's no longer guaranteed and I don't have enough knowledge of electronics to do anything about it.

 

thank you very much for taking so much time to help me

[WanWizard]

Tried both the switch and deep standby + on via the remote, in all cases wifi works. So yes, I'm afraid you have a localized hardware issue.

[nerron]

yes 

I'll just start it with the switch and it'll be fine.

[Dimitrij]

Try checking the WiFi module connection cable. Pull out/insert.