30 replies to this topic

[nerron]

Hello

i'm having a problem with the wifi connection on my mutant (openpli 9.0)

it doesn't connect automatically when I start the mutant (start from deep standby) I can't activate it manually from the menu I have to reboot and then it connects normally

from standby or on restart the wifi connects the problem occurs only from deep standby

does anyone have an idea how to solve the problem? 

thanks in advance

 

 

[WanWizard]

Can you boot the box from deep standby, then get /var/log/messages from the box, and post it here as attachment (as a zip)?

[nerron]

Can you boot the box from deep standby, then get /var/log/messages from the box, and post it here as attachment (as a zip)?

Hello WanWizard

thank you for your interest in my problem

I was able to copy it with dreamexplorer I also looked at the one after the reboot and indeed they are different even if I do not understand what that means

I put both in a .zip

 message.rar   15.45KB   4 downloads

[Dimitrij]

messages_after_reboot is 15 lines wlan0

messages_deep-standby not lines wlan0

Edited by Dimitrij, 10 December 2024 - 16:40.

[WanWizard]

I see two issues: there is no detection of the USB wifi chipset on cold boot, and there is a wifi driver crash on reboot. It is not clear from this log if the crashed driver is caused by hardware issues.

 

I know I tossed my HD66SE into a corner quite some time ago because it drove me up the wall, but I can't remember why exactly I was so fed up with it.

 

edit: I remember, I had tuner issues, randomly and intermittently sudden reception loss and/or lots of BERs.

[nerron]

no tuner problems on mine 

I was quite happy with it as long as it had a wired connection, but since I've had to switch to wifi, much less so.

 

it's become very slow to start up since the deep standby, certainly because of the wifi since that's the only thing I've changed

if I want to use it in less than 15 minutes, the only solution seems to be to leave it in standby mode, but that bothers me.

 

in any case, thank you for taking the time to try to help me

[WanWizard]

It takes 15 minutes to start up? I can't imagine that. Your log file show an OS load time of about 17 seconds.

 

I have no idea how the wifi module is connected to the internal USB bus. Is it integrated on the mainboard? Or is it a seperate module with possibly a poor connection?

[nerron]

15 minutes I exaggerate but it is very long it remains blocked on “boot” long minutes and it is since the switch to wifi.

 

I've just opened it to check it's soldered to the motherboard the problem doesn't come from there 

 

I think it's more of a software problem as it only happens in deep standby.

[WanWizard]

It can't be software, as the USB hardware isn't detected / enumerated on cold boot. If there is no hardware, software has nothing to access.

 

In the log you can see udev loading, and immediately loading the driver on reboot, and that is missing from the cold boot log.

 

Can you compare the output of "lsusb", between cold boot and reboot?

 

I'll see if my hd66se is still in the corner, and see what mine does.

[nerron]

Can you compare the output of "lsusb", between cold boot and reboot?

 

 

I don't know how to do this, but if you tell me where to look, yes.

Edited by nerron, 10 December 2024 - 21:02.

[WanWizard]

You have to login to the box with telnet, lsusb is a commandline command you need to type in, and it gives you the USB ID's of all devices it sees.

 

And no worries, that's an anti-spam measure, not applicable to you.

[nerron]

unable to connect via telnet after cold boot 

 

after reboot i have this 

 

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

[WanWizard]

You'll need a wired connection, as your wifi doesn't work after cold boot .

 

usb id 0bda:c820 is the ID of the wifi device. If that is not present after a cold boot, there's nothing much we can do.

[Dorfkind]

Or, for a few bucks, sth like https://www.tp-link....uter/tl-wr702n/

[nerron]

with wired connexion I have this 

 

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

 

it's the wifi that slows down my boot, with wired i get my boot back as fast as before.

 

 

Or, for a few bucks, sth like https://www.tp-link....uter/tl-wr702n/

It could be a solution, but I'd hate to have to add another device when I'm supposed to already have wifi.

[WanWizard]

It does show there, so that's odd. Is that a cold boot, after the box has been switched off?

 

Just to double check, do a cold boot with a wired connection, and issue the commands "ifconfig" and "lsmod".

[nerron]

yes, it was a startup after a deep standby but without cutting the power with the switch behind it. 

now I've done it again, cutting off the switch too 

here are the results of the commands

 

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, 16:15.

[nerron]

then strangely enough, if I start up with the button = no wifi and no possibility of configuring it, I only have the lan option, even if nothing is connected.

but if I turn it off and on with the switch behind it, I've got wifi and the lan and wlan setting options. 

 

  

Attached Files

•  IMG_20241211_162630.jpg   41.16KB   0 downloads
•  IMG_20241211_16223.jpg   45.92KB   0 downloads

[Dimitrij]

WanWizard

 

maybe....

linux fix issue with close wifi drivers rework bss patch

[Dimitrij]

nerron

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