From: Philip P. <phi...@re...> - 2010-08-10 05:29:14
|
I've tried both the canned soloscli sources in the tarball and the latest SVN version (r26), and both get the same result: # soloscli -s 0 SupportedAnnexes T1.413A Error. No response from modem # anyone else seeing anything similar? At boot I was seeing: Solos PCI Driver Version 0.11 svn-25 solos 0000:00:0e.0: Solos FPGA Version 0.03 svn-37 solos 0000:00:0e.0: Registered ATM device 0 solos 0000:00:0e.0: Registered ATM device 1 solos 0000:00:0e.0: Received packet for unknown VCI.VPI 0.0 on port 0 Error. No response from modem Error. No response from modem Sequence incorrect. Expected x1499, buffer was: o data. Error. No response from modem Thanks. |
From: Guy E. <gu...@tr...> - 2010-08-11 21:35:07
|
Hi Philip, What version does soloscli report? - Guy. On 10/08/2010 3:28 PM, Philip Prindeville wrote: > I've tried both the canned soloscli sources in the tarball and the latest SVN version (r26), and both get the same result: > > # soloscli -s 0 SupportedAnnexes T1.413A > Error. No response from modem > # > > anyone else seeing anything similar? > > At boot I was seeing: > > Solos PCI Driver Version 0.11 svn-25 > solos 0000:00:0e.0: Solos FPGA Version 0.03 svn-37 > solos 0000:00:0e.0: Registered ATM device 0 > solos 0000:00:0e.0: Registered ATM device 1 > solos 0000:00:0e.0: Received packet for unknown VCI.VPI 0.0 on port 0 > Error. No response from modem > Error. No response from modem > Sequence incorrect. > Expected x1499, buffer was: > > o data. > > Error. No response from modem > > > Thanks. > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Linux-atm-general mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-atm-general > > -- Guy Ellis gu...@tr... http://www.traverse.com.au Skype: guy.ellis1 Tel: +613 9386 4430 Fax: +613 9386 4435 |
From: Nathan W. <na...@tr...> - 2010-08-12 00:04:08
|
On Thu, 2010-08-12 at 07:05 +1000, Guy Ellis wrote: > Hi Philip, > > What version does soloscli report? > > - Guy. > > On 10/08/2010 3:28 PM, Philip Prindeville wrote: > > I've tried both the canned soloscli sources in the tarball and the latest SVN version (r26), and both get the same result: > > > > # soloscli -s 0 SupportedAnnexes T1.413A > > Error. No response from modem > > # Try increasing TIMEOUT in soloscli.h to 300. |
From: Mike W. <we...@cs...> - 2010-08-12 01:32:01
|
Increasing timeout values is a sometimes effective way to recover from various errors in broken drivers (or firmware!) :-( For relatively high performance (OC-3 +) systems, the cost is often severe performance hurts. For DSL speed stuff it's ugly but typically not noticeable performance-wise. Been there, done that. Mike |
From: Philip P. <phi...@re...> - 2010-08-12 15:40:37
|
On 8/11/10 5:03 PM, Nathan Williams wrote: > On Thu, 2010-08-12 at 07:05 +1000, Guy Ellis wrote: >> Hi Philip, >> >> What version does soloscli report? >> >> - Guy. >> >> On 10/08/2010 3:28 PM, Philip Prindeville wrote: >>> I've tried both the canned soloscli sources in the tarball and the latest SVN version (r26), and both get the same result: >>> >>> # soloscli -s 0 SupportedAnnexes T1.413A >>> Error. No response from modem >>> # > Try increasing TIMEOUT in soloscli.h to 300. No joy: pbx ~ # soloscli -s 0 SupportedAnnexes T1413A Sequence incorrect. Expected x3803, buffer was: o data. pbx ~ # soloscli -s 0 SupportedAnnexes T1413A Error. No response from modem pbx ~ # soloscli -s 0 SupportedAnnexes T1413A Error. No response from modem pbx ~ # |
From: Nathan W. <na...@tr...> - 2010-08-13 00:47:38
|
On Thu, 2010-08-12 at 08:40 -0700, Philip Prindeville wrote: > No joy: > > pbx ~ # soloscli -s 0 SupportedAnnexes T1413A > Sequence incorrect. > Expected x3803, buffer was: > > o data. > > pbx ~ # soloscli -s 0 SupportedAnnexes T1413A > Error. No response from modem > pbx ~ # soloscli -s 0 SupportedAnnexes T1413A > Error. No response from modem > pbx ~ # Hi Philip, I noticed that your FPGA version is 0.03-37, not 0.03-38. Some timing issues between the FPGA and Solos ADSL chipset were fixed in 0.03-38. I have emailed a binary and upgrade instructions for you off list. Regards, Nathan |
From: Philip P. <phi...@re...> - 2010-08-16 23:59:15
|
On 8/12/10 5:47 PM, Nathan Williams wrote: > On Thu, 2010-08-12 at 08:40 -0700, Philip Prindeville wrote: >> No joy: >> >> pbx ~ # soloscli -s 0 SupportedAnnexes T1413A >> Sequence incorrect. >> Expected x3803, buffer was: >> >> o data. >> >> pbx ~ # soloscli -s 0 SupportedAnnexes T1413A >> Error. No response from modem >> pbx ~ # soloscli -s 0 SupportedAnnexes T1413A >> Error. No response from modem >> pbx ~ # > Hi Philip, > > I noticed that your FPGA version is 0.03-37, not 0.03-38. > Some timing issues between the FPGA and Solos ADSL chipset were fixed in > 0.03-38. > > I have emailed a binary and upgrade instructions for you off list. > > Regards, > Nathan > I must be braindead... Aug 16 16:39:14 pbx user.info kernel: solos 0000:00:0e.0: Unregistering ATM device 0 Aug 16 16:39:14 pbx user.info kernel: solos 0000:00:0e.0: Unregistering ATM device 1 Aug 16 16:39:14 pbx user.info kernel: Solos PCI Driver 0.11 svn-25 Unloaded Aug 16 16:39:14 pbx user.info kernel: NET: Unregistered protocol family 20 Aug 16 16:39:14 pbx user.info kernel: NET: Unregistered protocol family 8 Aug 16 16:39:28 pbx user.info kernel: NET: Registered protocol family 8 Aug 16 16:39:28 pbx user.info kernel: NET: Registered protocol family 20 Aug 16 16:39:28 pbx user.info kernel: Solos PCI Driver Version 0.11 svn-25 Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Solos FPGA Version 0.03 svn-37 Aug 16 16:39:28 pbx user.info kernel: firmware: requesting solos-FPGA.bin Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Flash upgrade starting Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Firmware size: 152064 Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Number of blocks: 36 Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Changing FPGA to Update mode Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Set FPGA Flash mode to FPGA Chip Erase Aug 16 16:40:49 pbx user.info kernel: solos 0000:00:0e.0: Returning FPGA to Data mode Aug 16 16:40:49 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM device 0 Aug 16 16:40:49 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM device 1 Aug 16 16:41:39 pbx user.warn kernel: solos 0000:00:0e.0: Received packet for unknown VCI.VPI 0.0 on port 0 Aug 16 16:54:40 pbx user.info kernel: solos 0000:00:0e.0: Unregistering ATM device 0 Aug 16 16:54:40 pbx user.info kernel: solos 0000:00:0e.0: Unregistering ATM device 1 Aug 16 16:54:40 pbx user.info kernel: Solos PCI Driver 0.11 svn-25 Unloaded Aug 16 16:54:40 pbx user.info kernel: NET: Unregistered protocol family 20 Aug 16 16:54:40 pbx user.info kernel: NET: Unregistered protocol family 8 Aug 16 16:55:10 pbx user.info kernel: NET: Registered protocol family 8 Aug 16 16:55:10 pbx user.info kernel: NET: Registered protocol family 20 Aug 16 16:55:10 pbx user.info kernel: Solos PCI Driver Version 0.11 svn-25 Aug 16 16:55:10 pbx user.info kernel: solos 0000:00:0e.0: Solos FPGA Version 0.03 svn-37 Aug 16 16:55:10 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM device 0 Aug 16 16:55:11 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM device 1 pbx ~ # pbx ~ # soloscli -s 0 SupportedAnnexes T1413A Error. No response from modem pbx ~ # |
From: Nathan W. <na...@tr...> - 2010-08-17 01:18:32
|
On 17/08/2010 9:59 AM, Philip Prindeville wrote: > Aug 16 16:39:28 pbx user.info kernel: Solos PCI Driver Version 0.11 svn-25 > Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Solos FPGA > Version 0.03 svn-37 > Aug 16 16:39:28 pbx user.info kernel: firmware: requesting solos-FPGA.bin > Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Flash upgrade > starting > Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Firmware size: > 152064 > Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Number of > blocks: 36 > Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Changing FPGA > to Update mode > Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Set FPGA Flash > mode to FPGA Chip Erase > Aug 16 16:40:49 pbx user.info kernel: solos 0000:00:0e.0: Returning FPGA > to Data mode > Aug 16 16:40:49 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM > device 0 > Aug 16 16:40:49 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM > device 1 > Aug 16 16:41:39 pbx user.warn kernel: solos 0000:00:0e.0: Received > packet for unknown VCI.VPI 0.0 on port 0 > Aug 16 16:54:40 pbx user.info kernel: solos 0000:00:0e.0: Unregistering > ATM device 0 > Aug 16 16:54:40 pbx user.info kernel: solos 0000:00:0e.0: Unregistering > ATM device 1 > Aug 16 16:54:40 pbx user.info kernel: Solos PCI Driver 0.11 svn-25 Unloaded > Aug 16 16:54:40 pbx user.info kernel: NET: Unregistered protocol family 20 > Aug 16 16:54:40 pbx user.info kernel: NET: Unregistered protocol family 8 > Aug 16 16:55:10 pbx user.info kernel: NET: Registered protocol family 8 > Aug 16 16:55:10 pbx user.info kernel: NET: Registered protocol family 20 > Aug 16 16:55:10 pbx user.info kernel: Solos PCI Driver Version 0.11 svn-25 > Aug 16 16:55:10 pbx user.info kernel: solos 0000:00:0e.0: Solos FPGA > Version 0.03 svn-37 > Aug 16 16:55:10 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM > device 0 > Aug 16 16:55:11 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM > device 1 > pbx ~ # > pbx ~ # soloscli -s 0 SupportedAnnexes T1413A > Error. No response from modem > pbx ~ # > > Hi Philip, You will need to power-cycle the PC to force the FPGA to reload its configuration. Then you should see Solos FPGA Version 0.03 svn-38. Regards, Nathan |
From: Philip P. <phi...@re...> - 2010-08-23 17:50:54
|
On 8/16/10 6:18 PM, Nathan Williams wrote: > On 17/08/2010 9:59 AM, Philip Prindeville wrote: >> Aug 16 16:39:28 pbx user.info kernel: Solos PCI Driver Version 0.11 svn-25 >> Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Solos FPGA >> Version 0.03 svn-37 >> Aug 16 16:39:28 pbx user.info kernel: firmware: requesting solos-FPGA.bin >> Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Flash upgrade >> starting >> Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Firmware size: >> 152064 >> Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Number of >> blocks: 36 >> Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Changing FPGA >> to Update mode >> Aug 16 16:39:28 pbx user.info kernel: solos 0000:00:0e.0: Set FPGA Flash >> mode to FPGA Chip Erase >> Aug 16 16:40:49 pbx user.info kernel: solos 0000:00:0e.0: Returning FPGA >> to Data mode >> Aug 16 16:40:49 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM >> device 0 >> Aug 16 16:40:49 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM >> device 1 >> Aug 16 16:41:39 pbx user.warn kernel: solos 0000:00:0e.0: Received >> packet for unknown VCI.VPI 0.0 on port 0 >> Aug 16 16:54:40 pbx user.info kernel: solos 0000:00:0e.0: Unregistering >> ATM device 0 >> Aug 16 16:54:40 pbx user.info kernel: solos 0000:00:0e.0: Unregistering >> ATM device 1 >> Aug 16 16:54:40 pbx user.info kernel: Solos PCI Driver 0.11 svn-25 Unloaded >> Aug 16 16:54:40 pbx user.info kernel: NET: Unregistered protocol family 20 >> Aug 16 16:54:40 pbx user.info kernel: NET: Unregistered protocol family 8 >> Aug 16 16:55:10 pbx user.info kernel: NET: Registered protocol family 8 >> Aug 16 16:55:10 pbx user.info kernel: NET: Registered protocol family 20 >> Aug 16 16:55:10 pbx user.info kernel: Solos PCI Driver Version 0.11 svn-25 >> Aug 16 16:55:10 pbx user.info kernel: solos 0000:00:0e.0: Solos FPGA >> Version 0.03 svn-37 >> Aug 16 16:55:10 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM >> device 0 >> Aug 16 16:55:11 pbx user.info kernel: solos 0000:00:0e.0: Registered ATM >> device 1 >> pbx ~ # >> pbx ~ # soloscli -s 0 SupportedAnnexes T1413A >> Error. No response from modem >> pbx ~ # >> >> > > Hi Philip, > > You will need to power-cycle the PC to force the FPGA to reload its configuration. Then you should see Solos FPGA Version 0.03 svn-38. > > Regards, > Nathan Nathan did indeed send me a new FPGA image out-of-band, and I installed it. That seems to have resolved the issues. -Philip |