Hi all,
Just wondering, in the supplied *i?86*.config files for the kernel src RPM, why is CONFIG_IEEE1394 unset?
Also wondering why 4KSTACKS is turned on?
Thanks, Martin
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.
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.
On Thu, Apr 08, 2004 at 11:11:48AM -0400, Martin Stone wrote:
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.
it's perfectly safe if you use good kernel code....
On Thu, 2004-04-08 at 23:11, Martin Stone wrote:
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.
Well it might be more accurate to say that the nVidia module is unsafe, or only partially safe. Of course I use it myself in several places, so... :)
Does this mean that firewire won't be supported in Fedora Core 2?
FWIW, I read that most of the issues with firewire were fixed in the latest subversion tree of http://www.linux1394.org/ (I've been using the code from there for the past month and I have had absolutely no problems with an external HD even under heavy usage). According to the following post by Ben Collins, he intended to sync the code with Linux on 06-Apr-2004:
http://article.gmane.org/gmane.linux.kernel/195749/match=ieee1394
Regards, Ismael
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.
On Thu, 2004-04-08 at 07:49, 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)
All my flac files are sitting on a hard drive I intend to attach via firewire - so in linux right now, I'm without my tunes :(
Of course - I'm not really sure it matters anyway - last I checked, nforce2 IEEE1394 wasn't working anyway (even though ohci module loaded)
devel@lists.stg.fedoraproject.org
-
Arjan van de Ven -
Chris Kloiber -
Ismael Juma -
Martin Stone -
Michael A. Peters