This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Pau Espin Pedrol pespin at sysmocom.deHi, I have the feeling the connection between osmo-trx and osmo-bts-trx is good. The problem is that your BTS<->BSC<->... is failing. BTs shows these messages at startup because osmo-trx is not yet running: """" > osmo-bts-trx[23221]: <000b> trx_if.c:1174 phy0.0: Open transceiver > osmo-bts-trx[23221]: <000b> trx_if.c:185 phy0.0: No satisfactory > response from transceiver(CMD POWEROFF) """ Then at some point osmo-trx answers: """ > ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DTRXCTRL <0002> Transceiver.cpp:778 [tid=140554180474624][chan=0] command is 'POWEROFF' > ubuntu-HP-EliteBook-8470p osmo-trx-uhd[8282]: Thu Apr 9 11:22:24 2020 DTRXCTRL <0002> Transceiver.cpp:923 [tid=140554180474624][chan=0] response is 'RSP POWEROFF 0' """ But it's already too late, the BTS is already exiting due to some issue in Abis: """ > osmo-bts-trx[23221]: <000d> abis.c:142 Signalling link down > osmo-bts-trx[23221]: <0001> bts.c:292 Shutting down BTS 0, Reason Abis close """ Regards, Pau -- - Pau Espin Pedrol <pespin at sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte