kernel RPM: Why is CONFIG_IEEE1394 unset?

Martin Stone martin.stone at db.com
Thu Apr 8 15:11:48 UTC 2004


Thanks!  This is very good to know.  I guess I shouldn't even attempt to use 
firewire under 2.6.x then.

4KSTACKS was causing my nVidia display to freeze my whole box, so I was under 
the (perhaps mistaken) impression that it was unsafe or only partially safe.

Arjan van de Ven wrote:
> On Thu, 2004-04-08 at 16:29, Martin Stone wrote:
> 
>>Hi all,
>>
>>Just wondering, in the supplied *i?86*.config files for the kernel src RPM, why 
>>is CONFIG_IEEE1394 unset?
> 
> 
> because it breaks and blows up at boot, even for people who only have a
> firewire controller and no firewire devices (which seems to be the
> majority)
> 
> 
>>Also wondering why 4KSTACKS is turned on?
> 
> 
> because it's good for performance and reduces memory usage, both server
> and desktop.
> 
> 






More information about the fedora-devel-list mailing list