I posted the question accidentally into another forum but there wasn't a delete option! Sorry about that, I am posting it here as well.
We manage to install the GXSM for a new computer and once we started it we saw an error we haven't seen before. I just wanted to make sure it is not a critical issue on our side.
I posted the question accidentally into another forum but there wasn't a delete option! Sorry about that, I am posting it here as well.
We manage to install the GXSM for a new computer and once we started it we saw an error we haven't seen before. I just wanted to make sure it is not a critical issue on our side.
Eventually we were left with the following line of error. Only the time part is increasing and it is appearing multiple times as we start the GXSM. Is it something to be concerned about?
After the errors, we also see the lines below but I suppose they were regular information lines but can be about an issue. We just wanted to make sure not to encounter any problems while using the system.
** Message: 14:11:07.836: HWI-DEV-MK2/3: Initialization and DSP verification.
** Message: 14:11:07.836: HWI-DEV-MK3-I** HwI SR-MK3: verifying MK3 FB_SPM software details.
** Message: 14:11:22.981: HWI-DEV-MK2/3: auto probing succeeded: MK3 DSP identified and ready.
** Message: 14:11:23.007: GVP-VP restore to memo LM_set_last
** (gxsm3:695135): WARNING **: 14:11:23.007: DSP SIGNAL TABLE finding: Sig[60] 'WaveCh': ptr=10f054c4 is identical with Sig[59] 'Wave X': ptr=10f054c4
** (gxsm3:695135): WARNING **: 14:11:23.711: WHILE GXSM3 STARTUP: Valid Range: for [dsp-fbs-mx0-current-gain]: -0.5 ... 0.5
requested: 1 --> auto continue.
** Message: 14:11:24.195: Checking Z Polarity, Signal found: Z Servo Neg
** Message: 14:11:24.206: Checking Z Polarity (config=negative): OK
** (gxsm3:695135): WARNING **: 14:11:26.705: WHILE GXSM3 STARTUP: Valid Range: for [rp-pacpll-RP-VERBOSE-LEVEL]: 1 ... 10
requested: 0 --> auto continue.
** Message: 14:11:27.317: UPDATE SigSrc DSP: [0] >In 0< in (nA) x 4.65675e-08 x se=65536 {10}
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry, I have no good idea what is causing those issues. Not normal.
A few hints:
If you have any uncommon "local" (language) -- try to stay with "C" or English.
No not start gxsm fron any folder not within the current users's home folder with all default permission. Never start gxsm as root -- this could create a Ev-log as root for example and next time you start as non root you will get write access issues.
Make sure gxsm is installed properly and ONLY in one way -- no multiple version or installs in potentially different locations i.e. /usr/local/... when installed and build from source -- and also installed via repository/apt in /usr/bin/... what will conflict plugins/preferences/etc...
-P
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Percy,
I posted the question accidentally into another forum but there wasn't a delete option! Sorry about that, I am posting it here as well.
We manage to install the GXSM for a new computer and once we started it we saw an error we haven't seen before. I just wanted to make sure it is not a critical issue on our side.
Do you know why we got this error?
From what path or location did you started it? Looks there is no write permission.
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: discussion@gxsm.p.re.sourceforge.net discussion@gxsm.p.re.sourceforge.net on behalf of bugrahan guner bugrahanguner@users.sourceforge.net
Sent: Tuesday, September 26, 2023 10:25:44 PM
To: [gxsm:discussion] 40919@discussion.gxsm.p.re.sourceforge.net
Subject: [gxsm:discussion] Error encountered after starting GXSM
Hi Percy,
I posted the question accidentally into another forum but there wasn't a delete option! Sorry about that, I am posting it here as well.
We manage to install the GXSM for a new computer and once we started it we saw an error we haven't seen before. I just wanted to make sure it is not a critical issue on our side.
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
** Message: 10:15:13.315: HWI-DEV-MK3-I** HwI SR-MK3: verifying MK3 FB_SPM software details.
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
** Message: 10:15:18.306: HWI-DEV-MK2/3: auto probing succeeded: MK3 DSP identified and ready.
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
** Message: 10:15:18.335: GVP-VP restore to memo LM_set_last
** (gxsm3:206859): WARNING **: 10:15:18.335: DSP SIGNAL TABLE finding: Sig[60] 'WaveCh': ptr=10f054c4 is identical with Sig[59] 'Wave X': ptr=10f054c4
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
** (gxsm3:206859): WARNING **: 10:15:19.022: WHILE GXSM3 STARTUP: Valid Range: for [dsp-fbs-mx0-current-gain]: -0.5 ... 0.5
requested: 1 --> auto continue.
** Message: 10:15:19.550: Checking Z Polarity, Signal found: Z Servo Neg
** Message: 10:15:19.561: Checking Z Polarity (config=negative): OK
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
** (gxsm3:206859): WARNING **: 10:15:21.862: WHILE GXSM3 STARTUP: Valid Range: for [rp-pacpll-RP-VERBOSE-LEVEL]: 1 ... 10
requested: 0 --> auto continue.
** Message: 10:15:22.439: UPDATE SigSrc DSP: [0] >In 0< in (nA) x 4.65675e-08 x se=65536 {10}
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Sorry !
Can't write File !: Ev_Sep2023.log
Do you know why we got this error?
Error encountered after starting GXSMhttps://urldefense.com/v3/__https://sourceforge.net/p/gxsm/discussion/40919/thread/65354dbb24/?limit=25*7b6a__;Iw!!P4SdNyxKAPE!CYn71nOnMh2a4uS2GCqNreROt3V40JMMvzzT2rTcdjXyfTdk0L7_XnomBRxVGPv7q5L0JXxLaDfT5O1hv2kgorwzahsVmrU$
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/gxsm/discussion/40919/https://urldefense.com/v3/__https://sourceforge.net/p/gxsm/discussion/40919/__;!!P4SdNyxKAPE!CYn71nOnMh2a4uS2GCqNreROt3V40JMMvzzT2rTcdjXyfTdk0L7_XnomBRxVGPv7q5L0JXxLaDfT5O1hv2kgorwzYHnuqxM$
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/https://urldefense.com/v3/__https://sourceforge.net/auth/subscriptions/__;!!P4SdNyxKAPE!CYn71nOnMh2a4uS2GCqNreROt3V40JMMvzzT2rTcdjXyfTdk0L7_XnomBRxVGPv7q5L0JXxLaDfT5O1hv2kgorwzC3m512w$
Hi Percy,
Eventually we were left with the following line of error. Only the time part is increasing and it is appearing multiple times as we start the GXSM. Is it something to be concerned about?
(gxsm3:695135): Gtk-CRITICAL **: 14:11:07.772: gtk_combo_box_text_insert: assertion 'text != NULL' failed
Last edit: bugrahan guner 2023-09-28
After the errors, we also see the lines below but I suppose they were regular information lines but can be about an issue. We just wanted to make sure not to encounter any problems while using the system.
** Message: 14:11:07.836: HWI-DEV-MK2/3: Initialization and DSP verification.
** Message: 14:11:07.836: HWI-DEV-MK3-I** HwI SR-MK3: verifying MK3 FB_SPM software details.
** Message: 14:11:22.981: HWI-DEV-MK2/3: auto probing succeeded: MK3 DSP identified and ready.
** Message: 14:11:23.007: GVP-VP restore to memo LM_set_last
** (gxsm3:695135): WARNING **: 14:11:23.007: DSP SIGNAL TABLE finding: Sig[60] 'WaveCh': ptr=10f054c4 is identical with Sig[59] 'Wave X': ptr=10f054c4
** (gxsm3:695135): WARNING **: 14:11:23.711: WHILE GXSM3 STARTUP: Valid Range: for [dsp-fbs-mx0-current-gain]: -0.5 ... 0.5
requested: 1 --> auto continue.
** Message: 14:11:24.195: Checking Z Polarity, Signal found: Z Servo Neg
** Message: 14:11:24.206: Checking Z Polarity (config=negative): OK
** (gxsm3:695135): WARNING **: 14:11:26.705: WHILE GXSM3 STARTUP: Valid Range: for [rp-pacpll-RP-VERBOSE-LEVEL]: 1 ... 10
requested: 0 --> auto continue.
** Message: 14:11:27.317: UPDATE SigSrc DSP: [0] >In 0< in (nA) x 4.65675e-08 x se=65536 {10}
Sorry, I have no good idea what is causing those issues. Not normal.
A few hints:
If you have any uncommon "local" (language) -- try to stay with "C" or English.
No not start gxsm fron any folder not within the current users's home folder with all default permission. Never start gxsm as root -- this could create a Ev-log as root for example and next time you start as non root you will get write access issues.
Make sure gxsm is installed properly and ONLY in one way -- no multiple version or installs in potentially different locations i.e. /usr/local/... when installed and build from source -- and also installed via repository/apt in /usr/bin/... what will conflict plugins/preferences/etc...
-P