Hi
I've noticed that, with Fedora Core 2 test 2, I get an error at each system boot:
Initializing firewire controler (ohci1394): FATAL: Module ohci1394 not found
Does it mean the kernel doesn't support FireWire ? I have nothing to test FireWire currently but I plan to buy an external FireWire hard driver. Does it have any chance to work ? If not, why isn't the ohci1394 module included in the Fedora's kernel ?
Thanks for your help.
On Thu, 2004-04-29 at 04:51, Julien Olivier wrote:
Hi
I've noticed that, with Fedora Core 2 test 2, I get an error at each system boot:
Initializing firewire controler (ohci1394): FATAL: Module ohci1394 not found
Does it mean the kernel doesn't support FireWire ? I have nothing to test FireWire currently but I plan to buy an external FireWire hard driver. Does it have any chance to work ? If not, why isn't the ohci1394 module included in the Fedora's kernel ?
Thanks for your help.
Julien Olivier julo@altern.org
FireWire is currently busted in the latest kernel trees. IIRC it compiles but explodes wonderfully on insertion, taking the whole system and half the of the South East USA seacoast with it into oblivion. It will likely be turned on again when it works.
FireWire is currently busted in the latest kernel trees. IIRC it compiles but explodes wonderfully on insertion, taking the whole system and half the of the South East USA seacoast with it into oblivion. It will likely be turned on again when it works.
Thanks for your answer. I'll test it when it's turned on again then.
PS: I've just noticed that I sent this email to fedora-devel-list whil I meant to send it to fedora-test-list... All my apologies for this rather off-topic email.
On Apr 28, 2004, Chris Kloiber ckloiber@ckloiber.com wrote:
FireWire is currently busted in the latest kernel trees. IIRC it compiles but explodes wonderfully on insertion, taking the whole system and half the of the South East USA seacoast with it into oblivion. It will likely be turned on again when it works.
Which probably means it won't make it to FC2 final. I plan on offering some work-arounds for Firewire users, sort of like I did for FC1. My plan is to take the Firewire code that shipped with kernel 2.6.3, since that has worked quite reliably for me.
On Sat, 2004-05-01 at 23:56 -0300, Alexandre Oliva wrote:
On Apr 28, 2004, Chris Kloiber ckloiber@ckloiber.com wrote:
FireWire is currently busted in the latest kernel trees. IIRC it compiles but explodes wonderfully on insertion, taking the whole system and half the of the South East USA seacoast with it into oblivion. It will likely be turned on again when it works.
Which probably means it won't make it to FC2 final. I plan on offering some work-arounds for Firewire users, sort of like I did for FC1. My plan is to take the Firewire code that shipped with kernel 2.6.3, since that has worked quite reliably for me.
For what it's worth, I was able to build and load the firewire modules against 2.6.5-1.347. I used the latest ieee1394 branch from subversion using the attached Makefile. I have not actually tested connecting any firewire devices but my experience with other recent kernels was that loading ohci1394 spewed out a bunch of stack dumps.
David T Hollis wrote:
For what it's worth, I was able to build and load the firewire modules against 2.6.5-1.347. I used the latest ieee1394 branch from subversion using the attached Makefile. I have not actually tested connecting any firewire devices but my experience with other recent kernels was that loading ohci1394 spewed out a bunch of stack dumps.
The ieee1394 branch from subversion was merged into one of the recent mainline kernels (I think it was between 2.6.6-rc2 and 2.6.6-rc3). I have been using vanilla 2.6.6-rc3 with firewire enabled and I have had no problems whatsoever. My maxtor external hard drive works as well as my internal one.
So I guess that for people that really require firewire capability, compiling their own kernels might be necessary (as it is for people who want Nvidia binary drivers or NTFS to work - I happen to need the three of them ;)).
Cheers, Ismael
On Tue, May 04, 2004 at 11:36:00AM +0100, Ismael Juma wrote:
The ieee1394 branch from subversion was merged into one of the recent mainline kernels (I think it was between 2.6.6-rc2 and 2.6.6-rc3). I have been using vanilla 2.6.6-rc3 with firewire enabled and I have had no problems whatsoever. My maxtor external hard drive works as well as my internal one.
FWIW, I'm running 2.6.5-rc3-bk5 on a Mandrake 10 system and FireWire is working perfectly with two DVD+RW drives. In contrast, 2.6.5's FireWire completely explodes (it doesn't take the whole system down, but it spews tons of messages and is completely useless.) Both of those are mainline, BTW.
Since the latest posted arjanv kernel (2.6.5-1.349) is based on 2.6.6-rc3-bk, it should have the ieee1394 update and I would expect it to work again. I don't know if I will have time to test this in the next few days, however.
-Barry K. Nathan barryn@pobox.com
Barry K. Nathan wrote:
FWIW, I'm running 2.6.5-rc3-bk5 on a Mandrake 10 system and FireWire is working perfectly with two DVD+RW drives. In contrast, 2.6.5's FireWire completely explodes (it doesn't take the whole system down, but it spews tons of messages and is completely useless.) Both of those are mainline, BTW.
Since the latest posted arjanv kernel (2.6.5-1.349) is based on 2.6.6-rc3-bk, it should have the ieee1394 update and I would expect it to work again. I don't know if I will have time to test this in the next few days, however.
You're running 2.6.5-rc3-bk5? Or do you mean 2.6.6-rc3-bk5?
Cheers, Ismael
On Tue, May 04, 2004 at 01:50:51PM +0100, Ismael Juma wrote:
You're running 2.6.5-rc3-bk5? Or do you mean 2.6.6-rc3-bk5?
Yes, I meant 2.6.6-rc3-bk5, sorry about that!!
-Barry K. Nathan barryn@pobox.com
On May 4, 2004, Ismael Juma ijuma82@f2s.com wrote:
I have been using vanilla 2.6.6-rc3 with firewire enabled and I have had no problems whatsoever.
I have tested the linux1394 SVN tree regularly with my LVM on RAID1 on two external Firewire Maxtor hard drives, and every now and then I get the whole firewire subsystem to die under high load. Last I tried was -r1206, which appears to still be the latest. Problem is still the same as the one I last (?) re-reported to the linux1394-devel list about a month ago. Unfortunately the archives at sf.net seem to only go up to Apr 3 (?!?), so here's a link to an earlier version of the same report: http://sourceforge.net/mailarchive/message.php?msg_id=7605681
FWIW, some people have run into the problem with a single disk, without LVM or RAID, so it's not that. It's just more difficult to trigger the problem then.
Alexandre Oliva wrote :
On Apr 28, 2004, Chris Kloiber ckloiber@ckloiber.com wrote:
FireWire is currently busted in the latest kernel trees. IIRC it compiles but explodes wonderfully on insertion, taking the whole system and half the of the South East USA seacoast with it into oblivion. It will likely be turned on again when it works.
Which probably means it won't make it to FC2 final. I plan on offering some work-arounds for Firewire users, sort of like I did for FC1. My plan is to take the Firewire code that shipped with kernel 2.6.3, since that has worked quite reliably for me.
Eeek!!! Disable FireWire in the final release!? I hope you were joking, and that whatever working version that existed last will be forward ported since FireWire seems nearly vital to me.
I personally use it _very_ often to connect an external hard drive, as well as my MiniDV camcorder with dvgrab/kino, and I'm pretty sure I'm not the only one.
Matthias
Matthias Saou wrote:
Eeek!!! Disable FireWire in the final release!? I hope you were joking, and that whatever working version that existed last will be forward ported since FireWire seems nearly vital to me.
I personally use it _very_ often to connect an external hard drive, as well as my MiniDV camcorder with dvgrab/kino, and I'm pretty sure I'm not the only one.
You aren't alone! Without firewire support FC2 becomes useless for many users.
Lorenzo
Matthias
On Tue, May 04, 2004 at 11:53:15AM +0200, Matthias Saou wrote:
Eeek!!! Disable FireWire in the final release!? I hope you were joking, and that whatever working version that existed last will be forward ported since FireWire seems nearly vital to me.
The "working version" doesnt exist yet - thats much of the problem.
I personally use it _very_ often to connect an external hard drive, as well as my MiniDV camcorder with dvgrab/kino, and I'm pretty sure I'm not the only one.
And there will be errata kernels in time
devel@lists.stg.fedoraproject.org
-
Alan Cox -
Alexandre Oliva -
Barry K. Nathan -
Chris Kloiber -
David Hollis -
Ismael Juma -
Julien Olivier -
Lorenzo Luconi Trombacchi -
Matthias Saou