Hi Joel, |--==> joel silvestre writes:
js> Hi Free, js> works very well in a 32bits core-duo laptop. Get's only very occasionnal js> Xruns with internal sound chip and 0.7ms ([EMAIL PROTECTED]) buffer frame! js> But Freebob doesn't work anymore: js> Freebob using Firewire port 0, node -1 js> Ieee1394Service::initialize: Could not get 1394 handle: No such file or js> directory js> Is ieee1394 and raw1394 driver loaded? js> [31mFatal (devicemanager.cpp)[68] initialize: Could not initialize js> Ieee1349Service object js> [0m[31mFatal (freebob.cpp)[69] freebob_new_handle: Could not js> initialize device manager js> FreeBoB ERR: FREEBOB: Error creating virtual device js> :~$ gscanbus js> couldn't get handle: No such file or directory js> This probably means that you don't have raw1394 support in the kernel or js> that js> you haven't loaded the raw1394 module. js> So I have a look in the .config file, Firewire seem's to be disabled. js> :~$ cat /boot/config-2.6.23-1-multimedia-686 | grep 1394 js> # IEEE 1394 (FireWire) support js> # CONFIG_IEEE1394 is not set Thanks a lot for the report, it seems that since kernel 2.6.22 the Debian default configuration is using the "Juju" FireWire stack: CONFIG_FIREWIRE: # # This is the "Juju" FireWire stack, a new alternative implementation # designed for robustness and simplicity. You can build either this # stack, or the classic stack (the ieee1394 driver, ohci1394 etc.) # or both. Please read http://wiki.linux1394.org/JujuMigration before # you enable the new stack. # # To compile this driver as a module, say M here: the module will be # called firewire-core. It functionally replaces ieee1394, raw1394, # and video1394. # Would check if firewire-core helps? If so, I would keep this stack, in order to keep us as much similar as possible to the standard Debian kernel. Ciao! Free _______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel
