firewire init monopolizes UI after boot

[donn]

At the end of the bootstrap, after the UI, Terminal etc. have been drawn on screen but before the Desktop contents, the firewire device initialization keeps the system too busy to respond to user inputs for the first two or three seconds.

hrev26947, MSI K8N Neo4 motherboard, NForce4 chipset. Firewire on or off in the BIOS, makes no difference. No firewire devices.

[donn]

tail end of syslog, including firewire init

[korli]

The firewire bus modules are loaded when the media_server starts up.

[absabs]

IMO, it does not relate with firewire, although there are so many memory allocations during booting in syslog.

[jackburton]

Ping...

[donn]

Thanks for the reminder! Have had no problem with the alpha, evidently because it doesn't have firewire, but I just installed a recent image (hrev35849) and the firewire initialization is still disabled? This one has a bus_managers/firewire, 68227 bytes, but is looking for a bus_managers/firewire/v1.

KERN: module: Search for bus_managers/firewire/v1 failed.

KERN: fw_raw: couldn't load bus_managers/firewire/v1

[donn]

I'm sorry! I'm confused (/Haiku1/var/log from old install with browser and vi, is not the same /var/log when booted from /Haiku1 partition ...)

hrev35849 firewire is alive and apparently well - I can't verify that it works, but at least its initialization completes in a timely fashion, on my computer.

[jackburton]

Let's close this, then.