On Fri, Sep 04, 2009 at 07:44:05AM -0600, Sebastian Kuzminsky wrote:
> 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?
Gave up on that GUI "Applications->CNC->EMC2->5i20" thingo [1], and fired up
halrun, to load the modules manually. dmesg now has 3 or 4 [halrun|emc]
starts in it, and as 1 a.m. approaches, it's a bit late to reboot to
absolutely confirm that emc is just using the manually loaded modules.
Tomorrow I'll try "$ emc explicit_inifile", rather than just
mouse-clicky-click, to see if manually nominating an inifile obviates
the need to poke about with halrun.
If beavers can gnaw down trees with their bare teeth, a commandline
dinosaur ought to be able to get emc to fire up, given a few prods in the
right direction.
[1] OK, I've finally woken up to the fact that that's the same as
running "emc" on the commandline.
Erik
------------------------------------------------------------------------------
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
