[Bug 1062] wrote:
https://qa.mandrakesoft.com/show_bug.cgi?id=1062Firewire support is still being finalized, as is USB 2.0 which is being also finalized as far as things ever are in the Linux world. Kernel developers are working on this still, it is not fully and completely a part of any stock distro exept as one might consider LFS or Gentoo a stock thing (you compile from source and tweak right now to get ieee1394 support going right if you also have USB or especially USB 2.0 also, among other things). This is a linux-wide issue, not just a Mandrake one. I do not think that even a USB 2.0 direct-connect cable works in Linux commonly yet. At a guess, we will need to wait for things from 2.5 development branch of kernel to be back-ported(patched back into the 2.4 branch) if that is feasible, or for 2.6 to come out in late 2003 to early 2004. Software driver support for classes of things tends to take longer than for pinpoint drivers-- and for what the other operating system you use has, the base support is already there. For Linux, sorry to say not yet. Linux was first designed for servers and older boxes, those tend to use NICs instead of direct-connects, and for that reason Linux has supported a bunch of NICs for a very long time. The consumer variants of things have been not heavily worked on compared to LAN and server technology classes of devices. For now, the following direct connects are feasible and fairly easily accomplished:
Product: drakxtools
Component: DrakConnect
Summary: No ip over 1394
Version: 9.1-0.13mdk
Platform: PC
URL: [EMAIL PROTECTED]
OS/Version: All
Status: UNCONFIRMED
Severity: major
Priority: P1
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
DrakConnect doesn't list eth1394 as a driver, and expert mode crashes when I try it. This is after I have done insmod eth1394.o.gz and re booted. Actually, this option should be offered during the install, automatically, so those of us who are relying on our firewire cards to connect two windows machines will be able to network our new Linux install to, say, our winxp machine. (My case).
Even though my Linux bootup screen says eth0 is "OK", my winxp machine can't tell it's there. xp says "1394 Connection A network cable is unplugged." The Linux machine is dual booted with winme which does work with ip over 1394, Internet and everything. Linux needs to do ip over 1394 "out of the box", firewire has been around for some time now. And I can't find ANY documentation on the eth1394 module anywhere. Any ideas?
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
1. Null modem serial port connects, with or without modems involved (modem to modem and serial port to serial port with special cabling are both possible);
2. NIC to NIC connects with a crossover cable between them, and;
3. Parallel (ieee1284 type, two way Parallel) cable connects.
Of those three, Gigabit NIC to NIC would be fastest and would be faster than firewire also in terms of what you could do with data that also needs to be stored even in a caching way when transferred. Next fastest would be about as fast as actual USB 1.1, and that would still be a NIC-to-NIC connection (Intel eepro100s work, as do some 3COMs, VERY well, for this and for LAN use).
Cheapest is a tossup between 1 and 2, for Linux.
John.
