Debian on TBS2921 MOI+

full inet access, but the same unsepressed echo if ehternet cable plugged

root@debian:~# [ 158.112629][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[ 158.565586][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[ 158.572269][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[ 159.605495][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[ 159.612540][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled

eth0 is fully functionable, but because of unsupressable echo on it im mostly
using wlan,

It looks decent.

SATA, RTC, USB, Wifi all working OK. The miniPCI slots should work also if there is anything attached.

Try

ethtool eth0

And then do 2 tests.

1. Unplug the Ethernet cable (if it is plugged in), and replug. And

ethtool eth0

2. Keep the Ethernet cable attached, and plug the other end to different switch/router. And

ethtool eth0

====

I've attached the MOI+ DTS here in this post.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

eth0 full inet, but endless echo

1. ethtool after boot
2. ethtool after plug-replug
3. ethtool on other switch(router, not bound to the rest of nework)

Alex,

> eth0 full inet

Yes.

So your router is 10.0.1.1 ?

2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    inet 10.0.1.112/24 brd 10.0.1.255 scope global eth0

3: wlx00e04d930a34: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet 10.0.1.113/24 brd 10.0.1.255 scope global wlx00e04d930a34

But some paparemeters are missing.

root@debian:~# ethtool eth0
Settings for eth0:
	Supported ports: [ TP	 MII	 FIBRE ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: Unknown!
	Duplex: Unknown! (255)
	Auto-negotiation: on
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: external
	MDI-X: Unknown
	Supports Wake-on: pg
	Wake-on: d
	Link detected: no

Should look like this:

Settings for eth0:
	Supported ports: [ TP	 MII ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Supported pause frame use: Symmetric Receive-only
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	                        1000baseT/Full
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Link partner advertised link modes:  10baseT/Half 10baseT/Full
	                                     100baseT/Half 100baseT/Full
	                                     1000baseT/Full
	Link partner advertised pause frame use: Symmetric
	Link partner advertised auto-negotiation: Yes
	Link partner advertised FEC modes: Not reported
	Speed: 1000Mb/s
	Duplex: Full
	Auto-negotiation: on
	Port: Twisted Pair
	PHYAD: 0
	Transceiver: external
	MDI-X: Unknown
	Supports Wake-on: pg
	Wake-on: g
	Link detected: yes

Looks like the auto-negotiation failed. Can you use ethtool to set them manually? (man ethtool). See if it helps.

===

Perhaps it's time to look at the GPL source to find any Linux patch regarding the Ethernet driver. Or I'll have to create a temprary version for NSA325 u-boot to try bringing the network up in u-boot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

>So your router is 10.0.1.1 ?

i use 10.0.1.179 for wifi (RTL usb dongle)
and 10.0.1.138 for eth0
sorry, may be the thing was, because
i'm starting wifi as default

lets'see how it looks like if eth0 is default;

the same procedure
1. immidiatly after boot with eth0 plugged
2. plug out/plug in
3. plug out/plugin on another router

there is also onboard wifi RTL 8188 EUS ,
but it is obviously old NSA325 uboot not knowing it


root@debian:~# lspci -vvnn

00:01.0 PCI bridge [0604]: Marvell Technology Group Ltd. Device [11ab:6282] (rev 01) (prog-if 00 [Normal decode])
	Subsystem: Marvell Technology Group Ltd. Device [11ab:11ab]
	Device tree node: /sys/firmware/devicetree/base/mbus@f1000000/pcie@82000000/pcie@1,0
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: e0000000-e00fffff [size=1M] [32-bit]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity+ SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Subsystem: Marvell Technology Group Ltd. Device [11ab:11ab]
	Capabilities: [60] Express (v1) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <256ns, L1 unlimited
			ClockPM- Surprise- LLActRep+ BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 128 bytes, Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1
			TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #1, PowerLimit 0W; Interlock- NoCompl-
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 4a000001 01000004 01080000 00010000
		RootCmd: CERptEn- NFERptEn- FERptEn-
		RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
			 FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
		ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000

01:00.0 Multimedia controller [0480]: Philips Semiconductors SAA7160 [1131:7160] (rev 03)
	Subsystem: Device [6925:0001]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 0
	Region 0: Memory at e0000000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [40] MSI: Enable- Count=1/32 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [50] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <1us
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- SlotPowerLimit 0W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		LnkCap:	Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
		LnkCtl:	ASPM Disabled; RCB 128 bytes, Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1
			TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
	Capabilities: [74] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] Vendor Specific Information: Len=50 <?>

====
moderator: please use code tags (formatted code button on the far right) to post log.



Edited 1 time(s). Last edit at 11/02/2024 02:11PM by bodhi.

Alex,

> i use 10.0.1.179 for wifi (RTL usb dongle)
> and 10.0.1.138 for eth0
> sorry, may be the thing was, because
> i'm starting wifi as default

It's OK. I just wanted to be sure that's what you want.

>
> lets'see how it looks like if eth0 is default;
>
> the same procedure
> 1. immidiatly after boot with eth0 plugged
> 2. plug out/plug in
> 3. plug out/plugin on another router
>
> there is also onboard wifi RTL 8188 EUS ,
> but it is obviously old NSA325 uboot not knowing
> it

Not because it's old. Each u-boot is different. The NSA325 does not have Wifi. The RTL 8188 EUS wifi driver must be explicitly included in a u-boot build.

> root@debian:~# lspci -vvnn
>

PCI looks pretty good.

=====

The kernel GPL source they provided at website is practically useless. The patch is basically the whole new architecture (size 1.2 MB) added to kernel 2.6.35. There is no documentation or comment that indicate what are patches for the MOI+.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Alex,

Please test kwboot this new u-boot (run it with -p). It's a bit rough (I spent < 2 hrs to roll this). Assuming it boots, interrupt count down and

dm tree
setenv ipaddr <some valid ip address in your network environment)
ping <your router>
dm tree

And check envs, see if they are all there (they should, becaus you've flashed the NSA325 u-boot).

printenv

And then boot like you did previously.

Please post the entire serial console log.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/02/2024 06:22PM by bodhi.

bodhi,

10.0.1.137 is alive!
uboot, starting place for a spaceship, toward the sky full of stars..
travellling through the space slowly ,jet with a speed of light..

i also found after compiling of their old source
a system.dtb, the only dtb to be found in the compile tree,
but it was of no use, if attaching it to the debian kernel image

Regards,
Alex

Alex,

> 10.0.1.137 is alive!
> uboot, starting place for a spaceship, toward the
> sky full of stars..
> travellling through the space slowly ,jet with a
> speed of light..

:)) Nice!

I forgot the configure the dm command in. Will make another build.

The fact that Ethernet works OK in the new u-boot tell me that the driver in Linux might be lacking something. This is a rare case where the SoC is 88F6282, but with the Alaska chip 88E1516. This 88E1516 is mostly used in newer Marvell boxes with Armada 37x/38x/XP. So it seems like nobody has tested this combo before.

But I think more network test is needed in u-boot.

> i also found after compiling of their old source
> a system.dtb, the only dtb to be found in the
> compile tree,
> but it was of no use, if attaching it to the
> debian kernel image

That's interesting. Please attach that system.dtb here in your next post.

=====

In the mean time, see if you can get an internet connection to Google server (or some other server).

Assuming 10.0.1.137 is your router IP addr. Your IP addr already set to 10.0.1.222.

setenv gatewayip 10.0.1.137
setenv netmask 255.255.255.0
ping 8.8.8.8

And this time boot Debian with initrd to make sure you have all needed kernel modules loaded.

setenv load_initrd_addr 0x02100000
setenv bootcmd_linux 'setenv bootargs $bootargs_linux; mw.l f1010100 0020c000; sata init; ext2load sata 0:4 $load_uimage_addr  /boot/uImage; ext2load sata 0:4 $load_initrd_addr  /boot/uInitrd; bootm $load_uimage_addr $load_initrd_addr'
boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Here is the new u-boot.

uboot.2025.01-rc1-tld-1.moi_plus.kwb
sha256:
8eb6f4e2b1d83bd14356eb3c9b3d0063490b81c68b04d14fa62703d200b30eda

Run the 3 commands twice, before and after you test the network connection as described the my previous post.

dm tree
mii info
mdio list

setenv gatewayip 10.0.1.137
setenv netmask 255.255.255.0
ping 8.8.8.8

dm tree
mii info
mdio list

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

first ethtool eth0 on boot
on another router
2 other ethtool eth0 on a
gateway router directly (well,
a dumb switch in between)

system.dtb -> there is a link
in sources on a microblaze.dts

Regards,
Alex

Alex,

> system.dtb -> there is a link
> in sources on a microblaze.dts

Right! it looks like garbage left over in their source tree.

MOI+> mii info
PHY 0x00: OUI = 0x5043, Model = 0x1D, Rev = 0x01, 100baseT, FDX

MOI+> mdio list
ethernet-controller@72000:
0 - Marvell 88E151x <--> ethernet-controller@72000

Too bad. The right chip was detected but it looks like the auto negotiation is not working, just like in the kernel. The speed is only 100Mbs.

Try this test to see if the link is consistently up, or it will flipflop up/down in between.

for pingstat in 1 2 3 4 5 6 7 8 9; do; ping 10.0.1.137; sleep 1; done

Or use tftp to load a large file of a few MBs such the uImage. If the link stays up all the time, then you won't see T's.

=======

I have a bad feeling that a bit more works will be needed :) I need to look at the u-boot driver code.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Looks stable:

when in u-boot, there is no echo

Alex,

That tftp test looks great. Meaning even though it's 100 Mbs, but it stable and usable.

Here is another build.

uboot.2025.01-rc1-tld-1.moi_plus.kwb
sha256:
6b55fbedcbdc4eb8b4534fa0591ffa7e9f4ae1a7efd87fd86eed94ab0e7704c5  uboot.2025.01-rc1-tld-1.moi_plus.kwb

Please run the test similar to above (dm, mmi, mdio commands before and after)

https://forum.doozan.com/read.php?3,138227,138363#msg-138363

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

U-Boot:
regardless, if warm or cold restart,
eth LED switches on/off easily on replugging before
ping was issued,
with no effect on pluggin/replugging thereafter

Debian:
after a ping being issued in u-boot,
not link in debian, regardless
ifdown -ifup eth0, or /etc/init.d/networking restart

without a ping issued,
link is on, also afrer replugging,

- interestingly, LED on the
beginig of kernel booting swaps OFF,
and not swapping ON again, with no effect on plug/replug
.non withstanding the eth0 link goes always on on plug/replug

Regards,
Alex

Alex,

OK. That was bad :) Let's go back to the previous version on Nov 04.

https://forum.doozan.com/read.php?3,138227,138363#msg-138363

I'll do some more reading.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Alex,

Use the Nov 4th version. kwboot like you did. Boot into Debian. And

ethtool eth0
mii-tool -vv eth0

and then
ping the router (and cancel after about 20 pings).

Please post the log as usual.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Regards,
alex

Alex,

# ethtool eth0

Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full

Link partner advertised link modes:  
10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full

# mii-tool -vv eth0

advertising:  1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control

This is a bit fishy. Is your switch/router really is 1Gbs? is there a way that you can verify you can get 1Gbs, using a different Linux box and the same cable plugged in the same switch?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

yes, Sir!
that is what it is all about!
streaming with100mbit makes no sense..
(or make nonsense;-)
i was sitting behind a 100mbit and < switches,
misleading you.
Yes; now on 1GB switch, first suprise(to me)

MOI+> ping 8.8.8.8
ethernet-controller@72000 Waiting for PHY auto negotiation to complete....... done
Using ethernet-controller@72000 device
ping failed; host 8.8.8.8 is not alive
MOI+> sntp
ethernet-controller@72000 Waiting for PHY auto negotiation to complete....... done
Date: 2024-11-08 Time: 20:04:32
MOI+> printenv ntpserverip
ntpserverip=81.169.204.195
MOI+> ping 81.169.204.195
ethernet-controller@72000 Waiting for PHY auto negotiation to complete....... done
Using ethernet-controller@72000 device
host 81.169.204.195 is alive
MOI+> ping 8.8.8.8
ethernet-controller@72000 Waiting for PHY auto negotiation to complete....... done
Using ethernet-controller@72000 device
host 8.8.8.8 is alive
MOI+>
it can't be sntp that wakes it, really?
good,
first i send you the whole log
Regards, alex

Alex,

> yes, Sir!
> that is what it is all about!
> streaming with100mbit makes no sense..
> (or make nonsense;-)
> i was sitting behind a 100mbit and < switches,
> misleading you.
> Yes; now on 1GB switch, first suprise(to me)

Cool! so at least we know the speed is correct.

> MOI+> ping 8.8.8.8
> ethernet-controller@72000 Waiting for PHY auto
> negotiation to complete....... done
> Using ethernet-controller@72000 device
> ping failed; host 8.8.8.8 is not alive

> MOI+> sntp
> ethernet-controller@72000 Waiting for PHY auto
> negotiation to complete....... done
> Date: 2024-11-08 Time: 20:04:32

Nicely done! Making a round trip with SNTP.

> ethernet-controller@72000 Waiting for PHY auto
> negotiation to complete....... done
> Using ethernet-controller@72000 device
> host 8.8.8.8 is alive.
> MOI+>
> it can't be sntp that wakes it, really?

Not really. Usually when you ping in u-boot, you'll need to ping at least a couple time to be sure. It's been like that in mainline u-boot, but I have not tried to look for the real cause.

Now it's better. But we still don't know why the link goes down/up like that. My 1st guess is the Auto-negotiation does not works correctly, and or the cable is faulty.

1. Have you tried another CAT 5e or 6 cable? (whatever rating that gives you 1 Gbs).

2. Let's see if you can turn off Auto Negotiation with ethtool after the network has been up for several seconds (seeing that it has achieved 1Gbs). If the problem is with Auto-negotiation then it should stop the up/down behavior.

ethtool -s eth0 autoneg off

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

Worked like a charm!

Regards.alex

Alex,

> Worked like a charm!

Cool! we can declare victory :)

Now it's time to flash. But let me upload the final version with some instruction in one post.

In the mean time, add this to your /etc/network/interface (If you use dynamic IP)

auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
        pre-up ethtool -s eth0 autoneg off

See if 1Gbs is up from the kernell starts and no up/down flipping.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

iface eth0 inet static
pre-up ethtool -s eth0 autoneg off
address 10.0.1.112
netmask 255.255.255.0
network 10.0.1.0
#gateway 10.0.1.138
gateway 10.0.1.179
dns-nameservers 10.0.1.179

Doesn't work for static address; but, a
minor issue; either i'll change to dynamic
or do autoneg off manually

Regards,alex

Alex,

> Doesn't work for static address; but, a
> minor issue; either i'll change to dynamic
> or do autoneg off manually

I would do this in /etc/rc.local if static IP is preferred.

/usr/sbin/ethtool -s eth0 autoneg off

To make it perfect, I think it could be done automatically in the kernel. But that is a rainy day project!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Please change your 1st post Subject to Debian on TBS2921 MOI+. It will help people looking for it.

I will move this thread to Debian section.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Alex,

Please test this final version.

The default envs image will be uploaded in the new installation thread. For now, test with the envs you have been using.

uboot.2024.10-tld-1.moi_plus.kwb

sha256:
f76bd75f27b1ee08d960a67a451b7ee55ab8ce9f6fe8e473a859a2c5ab9c7051

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/10/2024 01:27PM by bodhi.