I've had problems with my ThinkPad T61 Freezing on me (wouldn't respond
to keyboard, mouse, nothing). So I reinstalled Debian without the tlp or
sensors stuff. I was back to the old IRQ problems (which turned into
FIFO overrun errors if I put irqpoll in GRUB). It was just a constant
cycle of pr
ginal post below:]
To: debian-user@lists.debian.org
Subject: How To Fix: Firewire IRQ Errors on Reboot
From: RavenLX
Date: Wed, 7 Jun 2017 09:25:52 -0400
Message-id: <[?] 5abcce6c-1786-f85c-5ffe-4f9821aac...@sitesplace.net>
I would like to share another discovery. This one fixed my firewire I
I would like to share another discovery. This one fixed my firewire IRQ
errors when rebooting my ThinkPad T61.
(Not-So-Obligatory) Disclaimer:
---
While, I do not notice any change in overall functionality of the laptop
as a result of this fix, I also do not know
* From: peasth...@shaw.ca
* Date: Wed, 31 Dec 2003 18:07:42 -0800
http:/carnot.yi.org/UnityDigitalCF.Firewire.jpg
Should be
http://carnot.yi.org/UnityDigitalCF.Firewire.jpg
Sorry, ... Peter E.
--
123456789 123456789 123456789 123456789 123456789 123456789 123456
are good.
(CF-Firewire adapter) = (enclosure). It is everything in the photo
except for the CF card; and only the edge of the CF is visible. The
CF-Firewire adapter plugs into a socket on a Firewire-PCI adapter.
I should have put a ruler in the photo for scale. This computer has
wheezy by the
From: David Guntner
Date: Wed, 16 Oct 2013 16:33:01 -0700
> You *seriously* need to take a look at your system clock :-)
Thanks. This afternoon the machine was down for cleaning for the first time
in years. When it was running again, I forgot to reset the clock. Should be
within less
On Wed, Dec 31, 2003 at 06:07:42PM -0800, peasth...@shaw.ca wrote:
> A photo of a CF-Firewire adapter here.
> http:/carnot.yi.org/UnityDigitalCF.Firewire.jpg
> I removed the cover in case anyone is interested. The two largest chips
> are marked LSI SYM13FW501 and Winbond W27E010P-7
On 12/31/2003 09:07 PM, peasth...@shaw.ca wrote:
> A photo of a CF-Firewire adapter here.
> http:/carnot.yi.org/UnityDigitalCF.Firewire.jpg
> I removed the cover in case anyone is interested. The two largest chips
> are marked LSI SYM13FW501 and Winbond W27E010P-70.
>
> When
A photo of a CF-Firewire adapter here.
http:/carnot.yi.org/UnityDigitalCF.Firewire.jpg
I removed the cover in case anyone is interested. The two largest chips
are marked LSI SYM13FW501 and Winbond W27E010P-70.
When the firewire plug is connected, dmesg gives the following.
fdisk -l yields
On 9/10/13, Rick Valenzuela wrote:
> I'm going to need an ExpressCard FireWire port to use with an older
> video camera and a Toshiba R930 laptop. Does anyone have any
> recommendations for FW ExpressCards?
When I search on *bay, eg for USB3 card, esata devices etc, I often
add
Hi all,
I'm going to need an ExpressCard FireWire port to use with an older
video camera and a Toshiba R930 laptop. Does anyone have any
recommendations for FW ExpressCards?
I don't know if there a lot of variation or troubleshooting involved
with Linux and FireWire, or with Express
xpanded since
> then; my understanding has improved little.
>
> https://ieee1394.wiki.kernel.org/index.php/Juju_Migration
>
> It states,
> # /etc/udev/rules.d/example-firewire.rules # IIDC devices: industrial
> cameras and some webcams SUBSYSTEM=="firewire",
> ATTR{units}==&q
el.org/index.php/Juju_Migration
It states,
# /etc/udev/rules.d/example-firewire.rules
# IIDC devices: industrial cameras and some webcams
SUBSYSTEM=="firewire", ATTR{units}=="*0x00a02d:0x00010*", GROUP="video"
Whereas Squeeze has no such rules.
peter@joule:~$ ls /etc/
On Mon, 11 Jun 2012 09:40:00 -0700, peasthope wrote:
> Does anyone use a firewire camera? Does anyone use Coriander?
>
> The Coriander manual has no mention of JuJu or udev and I wonder which
> of the instructions apply to my Debian Squeeze system.
(...)
We already discused this t
Does anyone use a firewire camera? Does anyone use Coriander?
The Coriander manual has no mention of JuJu or udev and I wonder
which of the instructions apply to my Debian Squeeze system.
peter@joule:/dev$ uname -rv
2.6.32-5-686 #1 SMP Sat May 5 01:33:08 UTC 2012
http://damien.douxchamps.net
o be done with some applications, like Skype, to
get video working, but dunno why, though.
> Some information for that connection method:
(...)
Looks good. The camera is detected and configured as UVC device.
> Concerning FireWire connection, the Firewire port itself is working.
>
&
b
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Concerning FireWire connection, the Firewire port itself is working.
root@pips04:/home/matpro# ls -l /lib/modules/$(uname
-r)/kernel/drivers/ieee1394/raw1394.ko
ls: Zugriff auf
/lib/modules/2.6.32-5-amd64/kernel/drivers/ieee1394/raw13
El 2011-09-10 a las 15:43 +0200, matpro_fhkoeln escribió:
(resending to the list)
> Am 10.09.2011 14:01, schrieb Camaleón:
> > On Sat, 10 Sep 2011 03:29:10 +0200, matpro_fhkoeln wrote:
> >
> >> I try to connect the Panasonic NV-GS500 over Firewire on Debian Squeeze
On Sat, 10 Sep 2011 03:29:10 +0200, matpro_fhkoeln wrote:
> I try to connect the Panasonic NV-GS500 over Firewire on Debian Squeeze,
> but it seems that Debian doesn't identify the camera correctly.
(...)
Are you sure the camera allows to be put in DV mode (live video
recording)
Hello Ladies and Gentlemen,
I try to connect the Panasonic NV-GS500 over Firewire on Debian Squeeze,
but it seems that Debian doesn't identify the camera correctly.
root@pips04:/home/matpro# uname -a
Linux pips04.gm.fh-koeln.de 2.6.32-5-amd64 #1 SMP Wed Aug 31 16:50:35
UTC 2011 x86_64 GNU/
Hello Ladies and Gentlemen,
I try to connect the Panasonic NV-GS500 over Firewire on Debian Squeeze,
but it seems that Debian doesn't identify the camera correctly.
root@pips04:/home/matpro# uname -a
Linux pips04.gm.fh-koeln.de 2.6.32-5-amd64 #1 SMP Wed Aug 31 16:50:35
UTC 2011 x86_64 GNU/
with GUID 0x85000110863c
Waiting for DV...
Capture Started
send oops
~ snip, deleted a whole bunch of 'send oops'
send oops
The size of the file varies each time I download from the Camcorder.
$ dmesg|grep firewire
[2.495874] firewire_ohci :02:00.0: PCI INT A -> GSI 19
Started
send oops
~ snip, deleted a whole bunch of 'send oops'
send oops
The size of the file varies each time I download from the Camcorder.
$ dmesg|grep firewire
[2.495874] firewire_ohci :02:00.0: PCI INT A -> GSI 19 (level,
low) -> IRQ 19
[2.495879] firewire_o
Ops, I forgot the kernel version:
$ uname -r
2.6.32-5-amd64
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4da36a03.8040...@brudeseth.name
, deleted a whole bunch of 'send oops'
send oops
The size of the file varies each time I download from the Camcorder.
$ dmesg|grep firewire
[2.495874] firewire_ohci :02:00.0: PCI INT A -> GSI 19 (level,
low) -> IRQ 19
[2.495879] firewire_ohci :02:00.0: setting lat
On Lu, 18 oct 10, 14:06:08, Rodolfo Medina wrote:
> Camaleón writes:
>
> > On Sun, 17 Oct 2010 15:56:08 +0200, Rodolfo Medina wrote:
> >
> >> Camaleón writes:
> >
> >>> Please, type "lspci" and put here the output, just to be sure.
> >>
> >>
> >> I had already posted it:
> >>
> >> # lspci | gr
s [SiS] USB 1.0 Controller
(rev 0f)
00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast
Ethernet (rev 91)
00:06.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000
Controller (PHY/Link)
On Sun, 17 Oct 2010 15:56:08 +0200, Rodolfo Medina wrote:
> Camaleón writes:
>> Please, type "lspci" and put here the output, just to be sure.
>
>
> I had already posted it:
>
> # lspci | grep -i ethernet
> eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
Yep, but do not "grep" it,
Camaleón writes:
> On Sun, 17 Oct 2010 13:47:22 +0200, Rodolfo Medina wrote:
>
>> , so eth0 has always been a firewire device. But the device I'm using
>> as an ethernet port is eth1, which now is not detected by the command
>> ifconfig, nor dmesg, nor lspci.
>
On Sun, 17 Oct 2010 13:47:22 +0200, Rodolfo Medina wrote:
> , so eth0 has always been a firewire device. But the device I'm using
> as an ethernet port is eth1, which now is not detected by the command
> ifconfig, nor dmesg, nor lspci.
Please, type "lspci" and put her
Camaleón writes:
>>> But... what kind of device is that? Are you using an adapter (firewire
>>> to ethernet)? :-?
> It's like Rodolfo's ethernet device got messed in some way and the system
> now detects his ethernet connection as Firewire.
Well, the fil
On Sat, 16 Oct 2010 12:25:40 -0600, Morgan Gangwere wrote:
> On Sat, 16 Oct 2010 16:15:12 + (UTC) Camaleón <> wrote:
>
>> But... what kind of device is that? Are you using an adapter (firewire
>> to ethernet)? :-?
>
> the 1394 standard says that a computer
6 Oct 2010 16:15:12 + (UTC) Camaleón <> wrote:
> >> But... what kind of device is that? Are you using an adapter
> >> (firewire to ethernet)? :-?
> >
> > the 1394 standard says that a computer which supports 1394 must also
> > support "1394 networking&
of device is that? Are you using an adapter
>> (firewire to ethernet)? :-?
>
> the 1394 standard says that a computer which supports 1394 must also
> support "1394 networking". Short end of it, if you need to move some
> data between two 1394 capable computers, you use that. Th
On Sat, 16 Oct 2010 16:15:12 + (UTC) Camaleón <> wrote:
> But... what kind of device is that? Are you using an adapter
> (firewire to ethernet)? :-?
the 1394 standard says that a computer which supports 1394 must also
support "1394 networking". Short end of it, if you
On 2010-07-15 03:35 +0200, bri...@aracnet.com wrote:
> Looks like the latest kernel is -5, is that correct ?
Yes.
Sven
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.o
On Wed, 14 Jul 2010 09:09:10 +0200
Sven Joachim wrote:
> On 2010-07-14 04:31 +0200, bri...@aracnet.com wrote:
>
> > The question is , submit to Debian or to LKML ?
>
> Report a bug in Debian, they will likely instruct how to report
> upstream. But first of all, boot a newer kernel because your
On 2010-07-14 04:31 +0200, bri...@aracnet.com wrote:
> The question is , submit to Debian or to LKML ?
Report a bug in Debian, they will likely instruct how to report
upstream. But first of all, boot a newer kernel because your current
one…
> [24128.816259] Pid: 716, comm: scsi_eh_10 Tainted: P
information
to do anything, but I thought I'd ask. If there's a chance then I'll
go ahead and submit a bug report and do what I can to help figure out
the problem.
I think it has something to do with firewire as I'm getting lots of
messages of all sorts of things being b
s root and has proposed a solution.
>
> So it is only fair to clarify that this is not a problem in Debian per
> say, but has been discovered as (i) a regression in the kernel and (ii)
> due to a bug in the camcorder's firmware (Sony DCR TRV25). I am sure we
> can expect a so
686.
>
> I see that firewire is now handled differently in the kernel and that
> /dev/fw? devices are formed instead of /dev/raw1394. Since Kino demands
> the latter, I have created a symbolic link /dev/raw1394 to /dev/fw0 (or
> fw1, as the case may be).
>
> I have these mo
Stefano Rivera wrote:
> Hi H.S. (2010.05.29_03:37:19_+0200)
>> In today's Debian Testing, is there anyone here who has successfully
>> grabbed dv video from a MiniDV camcorder at all using the newer
>> firewire stack?
>
> Yes. I have had some trouble with it (dvgr
Hi H.S. (2010.05.29_03:37:19_+0200)
> In today's Debian Testing, is there anyone here who has successfully
> grabbed dv video from a MiniDV camcorder at all using the newer
> firewire stack?
Yes. I have had some trouble with it (dvgrab refusing to find the
camera), but I blamed that
Ron Johnson wrote:
> On 05/28/2010 01:43 PM, H.S. wrote:
>> Ron Johnson wrote:
>>>
>>> I think that the "old" Firewire stack is still in the kernel.
>>>
>>> Googling "linux howto use old firewire stack", I found this link
On 05/28/2010 01:43 PM, H.S. wrote:
Ron Johnson wrote:
I think that the "old" Firewire stack is still in the kernel.
Googling "linux howto use old firewire stack", I found this link which
might help:
http://www.kdenlive.org/user-manual/troubleshooting-and-common-prob
Ron Johnson wrote:
>
> I think that the "old" Firewire stack is still in the kernel.
>
> Googling "linux howto use old firewire stack", I found this link which
> might help:
>
> http://www.kdenlive.org/user-manual/troubleshooting-and-common-problems/tr
t;
>> I am now using Debian Testing, KDE and kernel 2.6.32-trunk-686.
>>
>> I see that firewire is now handled differently in the kernel and that
>> /dev/fw? devices are formed instead of /dev/raw1394. Since Kino demands
>> the latter, I have created a symbolic link /dev/raw
-686.
I see that firewire is now handled differently in the kernel and that
/dev/fw? devices are formed instead of /dev/raw1394. Since Kino demands
the latter, I have created a symbolic link /dev/raw1394 to /dev/fw0 (or
fw1, as the case may be).
I have these modules loaded:
$> lsmod | grep f
I used to grab video from my DCR TVR25 MiniDV camcorder without any
problems in the past on Debian Testing using Kino or dvgrab. Since some
kernel version and up, this has not been possible anymore.
I am now using Debian Testing, KDE and kernel 2.6.32-trunk-686.
I see that firewire is now
So I'm trying to get video of my DCR-HC1000E...
Using Kino I get the following output:
>> Left Editor
>> Starting Capture
>> AV/C Aktiverad
>>> Using iec61883 capture
rom1394_0 warning: read failed: 0xf414
>>> iec61883Reader::StartThread on port 0
>>> AVC enabled
>> Constr
Alex Samad a écrit :
> On Thu, Mar 19, 2009 at 10:49:00PM +, thveillon.debian wrote:
>> Peter Krefting a écrit :
>>> Hi!
>>>
>>> Do I need to do something special to get firewire up and running on a
>>> Debian (unstable) install?
>>>
>
On Thu, Mar 19, 2009 at 10:49:00PM +, thveillon.debian wrote:
> Peter Krefting a écrit :
> > Hi!
> >
> > Do I need to do something special to get firewire up and running on a
> > Debian (unstable) install?
> >
[snip]
> > The camera works fine, I have
Peter Krefting a écrit :
> Hi!
>
> Do I need to do something special to get firewire up and running on a
> Debian (unstable) install?
>
> I am trying to get kdenlive working with my Canon HV20 camera. It is a
> HDV camera, and I connect it via Firewire. I am not able to get
Hi!
Do I need to do something special to get firewire up and running on a Debian
(unstable) install?
I am trying to get kdenlive working with my Canon HV20 camera. It is a HDV
camera, and I connect it via Firewire. I am not able to get kdenlive to see
the camera, though. Is there something
> currently experiencing a heavy performance regression in 2.6.26. Until
> 2.6.26, my external firewire disk (Maxtor OneTouch 4 Plus / 1TB) was
> reading with 38MB/s and writing with 26MB/s. When I do writing tests wi=
th
> dd from /dev/zero to disk, I get 26MBs but when I read with
Hi,
I'm running Debian testing in my home machine and after a long break I've
dist-upgraded it. During the update, I've upgraded my kernel from
2.6.25-2-686-bigmem to 2.6.26-1-686-bigmem.
While this upgrade fixed some problems with my firewire disk (firewire
disks are detected / m
On Sat, Dec 01, 2007 at 07:21:26PM +0100, Andrew Henry wrote:
> Sorry Andrew for double post...when I hit reply it goes to you and not the
> list, so I have now resent the mail to the list... for the second time!
The proper thing to do is Reply-to-List. I read the list and don't
need a copy sent t
this belongs on the list...
On Sat, Dec 01, 2007 at 12:47:05PM +0100, Andrew Henry wrote:
> Andrew Sackville-West wrote:
> > nice guide. it was definitely part of my list of open tabs when I was
> > setting up my encrypted laptop. He's got some other good ones there as
> > well.
> >
> > A
> >
Andrew Sackville-West wrote:
> nice guide. it was definitely part of my list of open tabs when I was
> setting up my encrypted laptop. He's got some other good ones there as
> well.
>
> A
>
Somethings broken :(
I followed the guide to the letter, and it all seemed to work
wonderfully. Then t
On Fri, Nov 30, 2007 at 11:37:52AM +0100, Andrew Henry wrote:
> Andrew Sackville-West wrote:
> > It comes down to this. Backups -- if its something you don't want to
> > have to go through the work to replace, then you should back it
> > up. Even if it's something that can't be "lost" because you h
Andrew Sackville-West wrote:
> It comes down to this. Backups -- if its something you don't want to
> have to go through the work to replace, then you should back it
> up. Even if it's something that can't be "lost" because you have
> original cds lying around, is the *effort* to re-rip it all some
On Wed, Nov 28, 2007 at 09:30:10PM +0100, Andrew Henry wrote:
> I have a big disk that I cannot backup due to space constraints and want
> to encrypt it. It is an ext3 external WD MyBook drive. I keep movies
> music and backups on there so its nothing I cannot lose, but I would
> hate to spend ti
I have a big disk that I cannot backup due to space constraints and want
to encrypt it. It is an ext3 external WD MyBook drive. I keep movies
music and backups on there so its nothing I cannot lose, but I would
hate to spend time ripping all my CDs and DVDs again.
I run Debian Etch on the laptop
On Thursday 10 May 2007 03:03, Douglas Allan Tutty wrote:
> With the system up, type:
> $ dmesg | grep eth
>
> You will see eth0 listed as firewire, and you should see your
> davicom (or something) listed as eth? Assuming its eth1:
>
> vi /etc/network/interfaces
ler: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
> compatible 10/100 Ethernet (rev 31)
> ----
> 01:09.0 FireWire (IEEE 1394): Texas Instruments TS
Pete Clarke wrote:
> Hi there,
>
> What is the current state of support for firewire attached drives within
> Linux ..
In konqueror...
gg:ieee1394 linux hard drive
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
to fit
a firewire card to it and run either the duo, or a couple of the Western
Digital 500GB MyBook Premium USB/Firewire drives (2 x 500GB mirrored).
It currently has 9 machines backing up to it, a combination of Linux (sarge
on 386 hardware) and Solaris (9 and 10), speed is not a huge issue
On Thu, Mar 01, 2007 at 07:03:46PM -, Pete Clarke wrote:
> Hi there,
>
> What is the current state of support for firewire attached drives within
> Linux ..
> I would like to use Sarge, standard PC - and attach something like the WD
> My Book Pro 1TB drive, ideally via fir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/01/07 13:03, Pete Clarke wrote:
> Hi there,
>
> What is the current state of support for firewire attached drives within
> Linux ..
> I would like to use Sarge, standard PC - and attach something like the
> WD My Book Pro 1TB
> Hi there,
>
> What is the current state of support for firewire attached drives within
> Linux ..
> I would like to use Sarge, standard PC - and attach something like the WD
> My
> Book Pro 1TB drive, ideally via firewire...
I'm using individual drives in external
Hi there,
What is the current state of support for firewire attached drives within
Linux ..
I would like to use Sarge, standard PC - and attach something like the WD My
Book Pro 1TB drive, ideally via firewire...
Cheers,
Pete.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuckk Hubbard wrote:
> On 7/16/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
>>
>> Chuckk Hubbard wrote:
>> > through, I'm kinda strapped. Also, what I was saying about ethernet
>> > is that each comp only has one port. So even if I had a router, I'd
>
On 7/16/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuckk Hubbard wrote:
> through, I'm kinda strapped. Also, what I was saying about ethernet
> is that each comp only has one port. So even if I had a router, I'd
> need an extra port for each machi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuckk Hubbard wrote:
> On 7/14/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> >> Think I'd be better off buying a PCI card with two ethernet jac
On 7/14/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> Think I'd be better off buying a PCI card with two ethernet jacks and
>> a hub? A FireWire cable is $30.
Well, that's iffy. On a good day, Fast Ethernet can reach 9
e:
On 7/14/06, Kenward Vaughan <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 13, 2006 at 08:27:32PM -0400, Chuckk Hubbard wrote:
> > AGNULA/DeMudi 2.6.12
> > It doesn't offer me any sort of option to use firewire in the
> > Networking panel. Modem, Ethernet, Wir
On 7/14/06, Kenward Vaughan <[EMAIL PROTECTED]> wrote:
On Thu, Jul 13, 2006 at 08:27:32PM -0400, Chuckk Hubbard wrote:
> AGNULA/DeMudi 2.6.12
> It doesn't offer me any sort of option to use firewire in the
> Networking panel. Modem, Ethernet, Wireless, Parallel Line, and
On Fri, Jul 14, 2006 at 12:10:58PM -0400, Chuckk Hubbard wrote:
> On 7/13/06, Kenward Vaughan <[EMAIL PROTECTED]> wrote:
...
> >Try it sometime. :)
> >
> >
> >Kenward
>
> I find it all interesting, and I would like to, but my major is
> composition, and I deal with lots of deadlines as a musician
ut I thought I had
>> it figured out.
>> I'd rather not have an extra piece of hardware lying around (hub) or
>> pay for it, if IP-over-FireWire is faster anyway. It works great for
>> XP<->OSX, and I can leave my ethernet DSL connected. If I used
>> et
t.
> I'd rather not have an extra piece of hardware lying around (hub) or
> pay for it, if IP-over-FireWire is faster anyway. It works great for
> XP<->OSX, and I can leave my ethernet DSL connected. If I used
> ethernet, I'd have to buy a hub, and either buy a new card
lying around (hub) or
> pay for it, if IP-over-FireWire is faster anyway. It works great for
> XP<->OSX, and I can leave my ethernet DSL connected. If I used
> ethernet, I'd have to buy a hub, and either buy a new card or reach
> back and switch cables when I go from internet
Oops, sorry, I thought I replied to the list. Gmail has a funny way
of misleading you about where your reply is going, but I thought I had
it figured out.
I'd rather not have an extra piece of hardware lying around (hub) or
pay for it, if IP-over-FireWire is faster anyway. It works great f
on-programmer.
>> > I read that IP-over-FireWire can only be done in Linux by recompiling
>> > the kernel. Maybe this was wrong.
>>
>> What work has to be done depends on whether your dist. has it compiled
>> in for the stock kernels. Apparently Debian's have
On 7/13/06, Kenward Vaughan <[EMAIL PROTECTED]> wrote:
On Thu, Jul 13, 2006 at 12:54:39PM -0400, Chuckk Hubbard wrote:
> On 7/13/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
> A non-programmer.
> I read that IP-over-FireWire can only be done in Linux by recompiling
> the
E1394_DV1394=m
>>> CONFIG_IEEE1394_RAWIO=m
>> I'm truly stunned that SBP2 is not "m".
>>
>> - --
>> Ron Johnson, Jr.
>
> Well, careful what you do 'till you recover. ;-)
>
> I don't know what option that is, Ron. IIRC, I follo
On Fri, Jul 14, 2006 at 02:21:11AM -0500, Ron Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Kenward Vaughan wrote:
...
> > Try searching the kernel config file under boot for IEEE1394 options:
> >
> > ==
> >
> > kvaughan:~# grep IEEE1394 /boot/config-2.6.16
> > CON
t;> Chuckk Hubbard wrote:
>>>>> A non-programmer. I read that IP-over-FireWire can only be done
>>>>> in Linux by recompiling the kernel. Maybe this was wrong.
>>> Compiling a kernel is *not* "programming". It does, though, take a
>>> bi
On Thu, Jul 13, 2006 at 08:27:32PM -0400, Chuckk Hubbard wrote:
> On 7/13/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >Chuckk Hubbard wrote:
> >>> A non-programmer. I read that IP-over-FireWire c
e a bit of time
> and energy if you are not familiar with Linux administration and/or
> programming."
> Daunting, but I don't have much choice.
>
> -Chuckk
...
Hmm. I use Kino with my videocam via Firewire. Works wonderfully, and
it's all packaged. Seems to me that th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuckk Hubbard wrote:
> On 7/13/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
> Chuckk Hubbard wrote:
>>> A non-programmer. I read that IP-over-FireWire can only be done
>>> in Linux by recompiling the kernel. Maybe th
On 7/13/06, Kenward Vaughan <[EMAIL PROTECTED]> wrote:
On Thu, Jul 13, 2006 at 12:54:39PM -0400, Chuckk Hubbard wrote:
> On 7/13/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
What work has to be done depends on whether your dist. has it compiled
in for the stock kernels. Apparently Debian's have i
On 7/13/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuckk Hubbard wrote:
>> A non-programmer. I read that IP-over-FireWire can only be done
>> in Linux by recompiling the kernel. Maybe this was wrong.
Compiling a kernel is *not*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuckk Hubbard wrote:
> On 7/13/06, Ron Johnson <[EMAIL PROTECTED]> wrote: Chuckk
> Hubbard wrote:
>> So do I understand correctly, that FireWire support in Linux
>> comes only with compiling the kernel with specific add-ons
On Thursday 13 July 2006 07:26, Chuckk Hubbard wrote:
> So do I understand correctly, that FireWire support in Linux comes
> only with compiling the kernel with specific add-ons?
That's one way. The other is to use a Debian kernel which already has this
done for you.
> Can s
On Thu, Jul 13, 2006 at 12:54:39PM -0400, Chuckk Hubbard wrote:
> On 7/13/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >Chuckk Hubbard wrote:
> >> So do I understand correctly, that FireWire support i
On 7/13/06, Ron Johnson <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuckk Hubbard wrote:
> So do I understand correctly, that FireWire support in Linux comes
> only with compiling the kernel with specific add-ons? Can someone
> with no desire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuckk Hubbard wrote:
> So do I understand correctly, that FireWire support in Linux comes
> only with compiling the kernel with specific add-ons? Can someone
> with no desire to program use FireWire?
So you think/say that *everyone* who
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 13, 2006 at 10:26:56AM -0400, Chuckk Hubbard wrote:
> So do I understand correctly, that FireWire support in Linux comes
> only with compiling the kernel with specific add-ons? Can someone
> with no desire to program use Fire
So do I understand correctly, that FireWire support in Linux comes
only with compiling the kernel with specific add-ons? Can someone
with no desire to program use FireWire?
I'm also having the "no sound" problem, but I'll browse through some
of the other thousands of pos
Direct-AccessANSI SCSI revision: 05
>
>
> The only reference I see is to "scsi0".
>
> What am I missing?
I'm sorry, but I know very little about SCSI, and SCSI printing even
less so. I suggest you ask on cups.general.
It may be a missi
1 - 100 of 261 matches
Mail list logo
