pon., 21 paź 2024 o 01:44 Evan Jobling via openwrt-devel
<openwrt-devel@lists.openwrt.org> napisał(a):
>
> The sender domain has a DMARC Reject/Quarantine policy which disallows
> sending mailing list messages using the original "From" header.
>
> To mitigate this problem, the original message has been wrapped
> automatically by the mailing list software.
>
>
> ---------- Forwarded message ----------
> From: Evan Jobling <evan.jobl...@mslsc.com.au>
> To: Janusz Dziedzic <janusz.dzied...@gmail.com>, OpenWrt Development List
> <openwrt-devel@lists.openwrt.org>
> Cc:
> Bcc:
> Date: Mon, 21 Oct 2024 10:42:48 +1100
> Subject: Re: HPE 1920-8G-PoE+ 180W (JG922A) PoE problems - after cold boot
> Hi there!
>
> Great to see another JG922A user!
>
> I'll be able to get you an answer eventually on
> snapshot as I'm still working on fixing default
> fan behaviour for JG922A.
>
> >
> > Seems, don't deliver power - does it ever works before?
> Let's start with confirming your PoE config?
>
> It "worked for me" back around august.
> Given this is a reboot issue I could have missed
> it though?
>
> Also have a look at joining the forum, there's a
> thread which is quite active regarding realtek target
> support in the developer section.
>
> Please note the layout is reversed?
> I think it also outlined how to configure PoE in
> the git commit.
>
> There are also notes I added to the wiki.
> i.e. what I have as my /etc/config/poe configuration.
>
> https://openwrt.org/toh/hpe/1920-8g_jg922a
>
Great, Thanks Evan.
Default config/poe is wrong for this switch - set id 1 for lan1 -
after change to 8:
root@OpenWrt:~# ubus call poe info
{
"firmware": "v20.3",
"mcu": "Nuvoton M05xx LAN Microcontroller",
"budget": 170.000000,
"consumption": 5.800000,
"ports": {
"lan1": {
"priority": 2,
"mode": "PoE+",
"status": "Delivering power",
"consumption": 5.800000
}
}
}
This is my OpenWrt One - after id change works correctly.
Seems we start with wrong default conf - and PoE disabled.
BTW, seems community config this using ethtool:
Enable kernel CONFIG_PSE_CONTROLLER =y
# ethtool --show-pse eth0
PSE attributes for eth0:
Clause 33 PSE Admin State: disabled
Clause 33 PSE Power Detection Status: disabled
# ethtool --set-pse eth0 c33-pse-admin-control enable
# ethtool --show-pse eth0
PSE attributes for eth0:
Clause 33 PSE Admin State: enabled
Clause 33 PSE Power Detection Status: delivering power
And fill:
static const struct pse_controller_ops pd692x0_ops = {
.setup_pi_matrix = pd692x0_setup_pi_matrix,
.ethtool_get_status = pd692x0_ethtool_get_status,
.pi_enable = pd692x0_pi_enable,
.pi_disable = pd692x0_pi_disable,
.pi_is_enabled = pd692x0_pi_is_enabled,
.pi_get_voltage = pd692x0_pi_get_voltage,
.pi_get_current_limit = pd692x0_pi_get_current_limit,
.pi_set_current_limit = pd692x0_pi_set_current_limit,
};
So, far I see two PSE controllers backends:
janusz@e850:~/github/linux-next/drivers/net/pse-pd$ ls
Kconfig Makefile pd692x0.c pse_core.c pse_regulator.c tps23881.c
janusz@e850:~/github/linux-next/drivers/net/pse-pd$
Seems, we can skip realtek-poe package in the future and use ethtool :)
Anyway, thanks for help.
BR
Janusz
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
