Erik Christiansen wrote: > $ halrun > halcmd: loadrt hostmot2 > halcmd: loadrt hm2_pci config="/lib/firmware/hm2/5i20/SVST8_4.BIT \ > num_encoders=3 num_pwmgens=3 num_stepgens=0" > > $ lsmod > Module Size Used by > hm2_pci 9116 0 > hostmot2 56320 1 hm2_pci > hal_lib 36248 2 hm2_pci,hostmot2 > ... > > And in /var/log/syslog, I find: > > hm2_pci: discovered 5i20 at 0000:00:08.0
Wow, you fixed it! What did you change to get the 5i20 to be discovered? > Though it didn't like the SVST8_4.BIT which I offered it: > > hm2/hm2_5i20.0: invalid token in config string: > "/lib/firmware/hm2/5i20/SVST8_4.BIT" > hm2_5i20.0: board fails HM2 registration > hm2_pci: probe of 0000:00:08.0 failed with error -22 > > However, pasting the config pathname from /var/log/syslog to the > commandline, we have: > > $ ls -l /lib/firmware/hm2/5i20/SVST8_4.BIT > -rw-r--r-- 1 root root 167061 2009-07-27 00:06 > /lib/firmware/hm2/5i20/SVST8_4.BIT > > So the "invalid token" is quite inscrutable at this stage. The firmware finder program looks in /lib/firmware, so you need to tell it just "hm2/5i20/SVST8_4.BIT". -- Sebastian Kuzminsky any sufficiently analyzed magic is indistinguishable from science ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
