A note on /dev/raw1394's security implications:
1. You cannot access local memory through raw1394, except for ROMs and
CSRs that are exposed to other nodes any way.
2. It is extremely hard to manipulate data on attached SBP-2 devices
(FireWire storage devices).
3. You can disturb operation of
This may have been fixed upstream, e.g. in Linux 2.6.16.2. Could you try
the newest kernel that you are confident you can get installed without
trouble?
--
sbp2 hot plug causes hard crashes
https://launchpad.net/bugs/28647
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This was certainly fixed in a later kernel version. There were a number
of related fixes getting in into almost each subsequent upstream
release, so it's hard to tell which one you would need.
--
amd64 kernel locks on firewire ipod unplugging
https://launchpad.net/bugs/28691
--
ubuntu-bugs
Yes, you are right. Actually, a cheap setup to achieve #1 by #4 is to
have two FireWire controllers in the PC and connect them.
--
use /dev/video1394, not /dev/raw1394
https://launchpad.net/bugs/6290
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The PL3507 is widely known for a weak FireWire implementation and
sometimes extremely bad firmware. USB is supposed to work better on this
though.
As far as sbp2 is concerned, failures to connect are perhaps fixed
upstream. There was a regression in sbp2 concerning some PL3507 in Linux
This looks like http://bugzilla.kernel.org/show_bug.cgi?id=6356 which
was fixed upstream in Linux 2.6.16.20 and 2.6.17. But I don't know if
2.6.15-20-powerpc actually has this bug in the first place.
--
External Firewire DVD-RW not working.
https://launchpad.net/bugs/39257
--
ubuntu-bugs
*** This bug is a duplicate of bug 48317 ***
This is a duplicate of bug #48317.
** This bug has been marked a duplicate of bug 48317
firewire not detected on resume from suspend
--
ohci1394 module does not work after resume from suspend or hibernate
https://launchpad.net/bugs/51052
--
This is tracked as an upstream bug at
http://bugzilla.kernel.org/show_bug.cgi?id=7072 . You could add your
e-mail address there if you are interested in latest news. Don't expect
a fix soon.
As a workaround, mark ohci1394 (and perhaps the other IEEE 1394 drivers)
to be unloaded before suspend. I
PS: Of course you should unmount any FireWire storage devices before
unloading ohci1394.
** Bug 51052 has been marked a duplicate of this bug
--
firewire not detected on resume from suspend
https://launchpad.net/bugs/48317
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The very first comment looks like bug #39257. (Failure of the very first
SCSI command, i.e. INQUIRY, device is perhaps based on the Prolific
PL3507 USB 2.0 + FireWire 400 chip whose FireWire part is substandard.
Aplle iPods are of course not based on PL3507.)
Please provide the full syslog
In case anybody is still using Linux 2.6.12, there is a chance that
sbp2's module parameter serialize_io=1 helps with this sort of problem.
--
external hard disk disconnects (firewire ieee1394 over SCSI) during file copy
'Read-only file system' 'Device offlined'
https://launchpad.net/bugs/27659
Does the problem still exist? If yes, do you know what bridge chip the
device is based on?
--
/dev/scd0, often, doesn't come up
https://launchpad.net/bugs/33039
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Dapper may still be affected, or actually newly affected. See patch
sbp2: fix spinlock recursion in upstream 2.6.16.2 and 2.6.17.
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=24c7cd0630f76f0eb081d539c53893d9f15787e8
--
amd64 kernel locks on firewire
I read your report via Babelfish. It looks like bug #28691, although
that one was reported for Breezy Badger.
--
Disque externe connecté en IEEE1394
https://launchpad.net/bugs/46868
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I agree; it is a kernel driver problem or/and a firmware problem. Did
you change anything else besides pmount?
--
after upgrading default version of pmount, firewire drive will not automount
anymore
https://launchpad.net/bugs/46991
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Except if you don't load ohci1394 or load ohci1394 with the parameter
phys_dma=0. Switching physical DMA off will work fine with raw1394,
dv1394, video1394... It will just break sbp2 until I get
http://bugzilla.kernel.org/show_bug.cgi?id=6393 fixed. (It's not high on
my list, and it is a nuisance
As I understood it, address based filtering could/would have been done
with the multiple files approach too. However the capabilities based
approach sounds really good. AFAICS it achieves basically the same in a
simpler way. Simpler = more secure.
I think the multi-file approach would allow to
So it is the infamous PL3507. These are sold with bugs in various
flavours. I don't know about a particular solution for an early failure
like this Error parsing configrom.
If you have access to a Windows PC, try update the PL3507's firmware.
(Prolific's firmware uploader runs under Windows.) Not
Does the pmount package come with postinstall scripts that run some
lowlevel reconfiguration?
(I am not a Ubuntu user, just lurking here as an sbp2 kernel driver
maintainer.)
--
after upgrading default version of pmount, firewire drive will not automount
anymore
Yes, this is what I am looking for.
The information is not entirely conclusive though, especially the fact
that the first few SCSI commands succeed (Inquiry, Read Capacity, Mode
Sense) while the first or one of the first SCSI read commands fails.
What can be seen though is that this device
Some SBP-2 chips can be fixed by firmware upload.
For some PL-3507 variants:
http://www.prolific.com.tw/eng/downloads.asp?ID=44
(Windows required)
For INIC-1430:
http://www.initio.com/support/1430/1430support.htm
(Windows or OS X required)
--
Firewire connection not being correctly mounted in
The firmware upload utility should show it. It may also be possible to
read version information with Linux utilities, but exact specifications
from the firmware maker would be required.
If you can open up the enclosure easily and without voiding warranty,
check what chip is in there before trying
I meant the disk enclosure. The firmware of the usually biggest chip on
the PCB in the disk enclosure a.k.a. the SBP-2 bridge is what I referred
to in comment #9. Some enclosures cannot be opened without special tools
though.
--
Firewire connection not being correctly mounted in 6.06
Re comment #7: If the enclosure overheats, I/O errors may happen but the
PC should not hang. I believe these hard lockups were fixed in upstream
Linux 2.6.17 + 2.6.16.2 by
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=24c7cd0630f76f0eb081d539c53893d9f15787e8
--
See bug #28647.
--
amd64 kernel locks on firewire ipod unplugging
https://launchpad.net/bugs/28691
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The regression I referred to in comment 4 went into Ubuntu Dapper too, as part
of a bugfix for other devices. Ubuntu Edgy has the regression fixed:
http://www.kernel.org/git/?p=linux/kernel/git/bcollins/ubuntu-2.6.git;a=commitdiff;h=a54c9d30dbb06391ec4422aaf0e1dc2c8c53bd3e
--
usb-mass storage
[ 432.935107] ieee1394: sbp2: scsi_add_device failed (-19)
This _may_ indeed be the bug which I referred to in my previous comment.
Ubuntu's 2.6.15-20 has a regression of upstream 2.6.16, which is partly
my fault. Ubuntu Edgy has the regression fixed. See bug #36619.
[ 432.937341] scsi1 : SCSI
Jose,
check if sbp2 was loaded with serialize_io=1. This is loggeded in a file under
/var/log/. It should be (and it is the default) as it is currently required for
some devices and setups.
Also, check if there are messages from sbp2 about reconnect attempts
during normal I/O. This may be
Sorry, I'm really stressed at the moment ;-)
Today I reported this bug to GNOME. You can find it here:
http://bugzilla.gnome.org/show_bug.cgi?id=559388
I tested this bug again and it still appears in Ubuntu 8.04 (Hardy
Heron). But this bug does not appear in Ubuntu 8.10 (Intrepid Ibex)
Live-CD!
The dmesg shows that this problem is very likely in the sbp2 + ieee1394
+ ohci1394 kernel driver stack and possibly an upstream problem. Alas a
quick look at the IEEE 1394 kernel subsystem changelog after 2.6.24
(which I presume was the major version number of the reporter's last
known working
dvgrab can capture MPEG2-TS too.
--
[needs-packaging] mpg1394grab - DV Video (HD) Capture IEC 61883-4 from dv
ieee1394 firewire port
https://bugs.launchpad.net/bugs/274814
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
About the suggested workarounds:
serialize_io=1 is on by default anyway, hence specifying this option does
nothing. (serialize_io=0 is too buggy hence not used by default.) Please
check if sbp2 is loaded in serialized mode even if you don't provide this
option explicitly:
# cat
As a workaround, the commands
# modprobe -r sbp2
# modprobe sbp2
may help.
It would indeed be good to know if kernels 2.6.27 works (ideally without
any workaround).
--
Error message after plugging firewire hard disk
https://bugs.launchpad.net/bugs/186333
You received this bug notification
It's an upstream bug on which nobody is working on. The problem is
between the controller and how our drivers update its DMA program.
Have a look at http://marc.info/?l=linux1394-userm=116463661930992
though. Would that be applicable to your setup?
--
fw-host0: Iso Xmit 0 Context died
Is there anything suspicious in dmesg? (I suppose not, otherwise you
would probably already posted it here.) I think you should ask at the
ffado-user mailinglist whether there are ways to gather helpful
diagnostics.
PS, I am entirely unexperienced with both ffado and Ubuntu; I'm only
involved
The problem could be with
- k3b and the libraries it uses (unlikely though since it works over USB),
- the kernel (try a newer Ubuntu kernel/ Ubuntu release if you can),
- the FireWire bus (full output of dmesg from when the 1394 drivers are
loaded till the failure occurred would be
dvgrab 2.x and 3.x are definitely not affected anymore.
--
dvgrab uses unsupported isochronous request types
https://bugs.launchpad.net/bugs/129974
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The log from kernel 2.6.20 in comment 1 alas lacks info about SCSI/
SBP-2/ IEEE 1394 errors before and after the oops, if there were any.
Chances are that this issue is no longer present in newer kernels.
--
adding FW harddrive causes this oops
https://bugs.launchpad.net/bugs/39792
You received
The initial bug description shows that the kernel rediscovers the disk
and its partition just fine. So it is obviously a bug in the userspace
infrastructure.
--
Ipod won't re-mount
https://bugs.launchpad.net/bugs/37898
You received this bug notification because you are a member of Ubuntu
Bugs,
I wrote:
dvgrab can capture MPEG2-TS too
...(i.e. HDV) and can divert it into files or into stdout and hence to a pipe
by using a - as trailing command line parameter. I.e. it can do everything
which mpg1394grab can do and much more than that, is practically as simple to
use, and is still
HDV (MPEG2-TS) support was added in dvgrab 3.0, released in August 2007.
Before that, mpg1394grab or test-mpeg2 had to be used for HDV.
Information about mpeg1394grab's kernel interface issue is somewhat
obscure, but would show itself at runtime on a new kernel or at compile
time with libraw1394
Does dvgrab work with previous version of Ubuntu before 8.04 or before
kernel 2.6.23 ?
Yes, dvgrab v2.x and dvgbrab v3.x (latest version is recommended) work
with old kernels and new kernels alike. Ditto regarding libraw1394
version compatibility.
--
[needs-packaging] mpg1394grab - DV Video
It seems that I have the PL3507A
My condolences. It's junk. All bets are off.
For whatever reason the disk is working reliable with my current
intrepid again with 2.6.27-7.14 altough I see no firewire or sbp related
changes in the linux-image changelog between 2.6.27-4 and 2.6.27-7.
Maybe
The test with different OSs would serve to find out whether the problem
is influenced by the kernel or by the hardware (or both). The different
types of failures that your logs show point towards flaky hardware. If
so, then it could be the card, the cable, or the combination of PC (with
all its
Public bug reported:
Binary package hint: enigmail
Normally you need to type your passphrase after writing signed or encrypted
mails in thunderbird.
But I don't get an input box! I only get the message wrong passphrase.
After installing the package pinentry-gtk2 it works.
So perhabs this
This bug occurs in Ubuntu Gutsy!
--
thunderbird enigmail does not work with passphrases
https://bugs.launchpad.net/bugs/172336
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
So you have one machine with a 2.6.16 based kernel where it works and
one with a 2.6.20 based kernel where it is unstable.
What does cat /sys/module/sbp2/parameters/serialize_io say? If it is
1, then it's OK.
Do you use a long cable or a front panel connector or something like
that on the
As a side note:
The ext2 and ext3 filesystems have an option to count the number of how
often a partition was mounted and when it was last checked with fsck,
and to enforce an fsck after it was mounted a certain times or checked
more than a certain time ago. This option is configured per
Could you post the output of uname -a, and the messages from dmesg which
belong to the following events:
1.) when ohci1394 is present in the kernel and you plug the disk in,
2.) when you do the rmmod/modprobe workaround to get the disk recognized.
--
Firewire drive not detected
Sorry, I was absent ;-)
I try to describe this problem a second time.
Scenario 1: Ubuntu Gutsy 7.10
1. open nautilus
2. press the edit button so that you can type a location (e.g.
/home/user/Desktop)
3. type the following address: smb://[EMAIL PROTECTED] and press return
4. now you have to log
Public bug reported:
Binary package hint: nautilus
I think that this bug occurs in Ubuntu hardy and not in Ubuntu Gutsy.
if I log in a samba server in nautilus (smb://[EMAIL PROTECTED]) I will not be
able to log in the same server with another account (smb://[EMAIL PROTECTED]).
Instead of
Security enhanced replacement drivers are being worked on since last
year, but not yet ready for prime time. It is possible with these
drivers to let scripts assign different device file permissions based on
the type of FireWire device ( - finer grained device security). These
drivers also
The OXFW911+ is quite a good chip. It is responsible for the FireWire
interface. The Cypress chip is for the USB2 side. Both are AFAIK fully
independent of each other.
During the past few years I heard of only a single report of an 911 or
911+ with bad firmware, which is negligible compared to
I wrote:
The unsupported isochronous request types in raw1394 that
dvgrab 1.x can use alternatively to dvgrab1394
should read ...to dv1394
dvgrab-2.1.tgz
should read dvgrab-2.1.tar.gz
--
use /dev/video1394, not /dev/raw1394
https://bugs.launchpad.net/bugs/6290
You received this bug
Jeff, that's evidently a very old version of dvgrab. File a bug for the
dvgrab package --- it should be updated to version 2.1.
Yes, the dv1394 driver will eventually vanish. But there is no date set
for its removal yet; it depends on how fast the new alternative FireWire
stack which was merged
Public bug reported:
Binary package hint: apache2-mpm-itk
Ubuntu feisty (7.04)
While updating apache2.2-common the package apache2-mpm-itk have to
be removed because after this update it has unmet dependencies.
So the dependencies in apache2-mpm-itk should be updated.
** Affects:
The new alternative experimental drivers (CONFIG_FIREWIRE) are not ready
for production yet, unless distributors know exactly what they are
doing. Support by userspace libraries and applications is still
lacking, and there are some hardware incompatibilities. See
If you still have this hardware: Compare the contents of
/proc/interrupts right before and after you plugged the drive in.
--
Firewire drive not detected
https://bugs.launchpad.net/bugs/105317
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Regarding FireWire disks, there are a few open bugs in the new driver
stack (devices not recognized, errors during heavy I/O, and other
issues). I estimate that most of them can be resolved before upstream
kernel 2.6.24 will be released.
The difficult part is handling of FireWire camcorders,
PS: Those /dev/disk/by-id/* symlinks are automatically created by
'udevd'. If Ubuntu's udevd and the udev scripts are reasonably close to
mainline udev, then it works out-of-the box with firewire-sbp2 just like
with sbp2.
--
firewire hard disk only detected at boot process
I'm not sure what is required to have it show up on the desktop.
Perhaps an update to 'hald' to adapt it to the new drivers. (But then,
firewire-sbp2 simply adds and removes SCSI devices like sbp2 and any
other SCSI driver for hotpluggable SCSI devices does. It would
moderately surprise me if
This was the fix in 2.6.21 relative to 2.6.20:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=3360177c62e86f476c4f1a057e13163383652f7b
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=3360177c62e86f476c4f1a057e13163383652f7b
I'm
PS: Even after the fix, the sbp2 driver may still have problems to
transparently reconnect to the disk after resume. It could happen that
the SCSI device is destroyed (during suspend or right after resume) and
then re-created as a different SCSI device. It may even be necessary to
unplug and
Oliver:
I could not reproduce the problem with a brand-new LaCie Little Disk 500 GB on
a few different controllers. But I found a little oddness of that disk in the
process: http://marc.info/?l=linux1394-develt=12334064382
However, at least I have got an older CD-RW which shows the same
[raw1394 not loaded automatically]
Could you post the output of modinfo raw1394? I'd like to check
whether all device identifiers are in there as they should be. May be
necessary to run it as root or to run it as /sbin/modinfo raw1394.
Also, if you have the camcorder around, please plug it in/
Well, unmounting a read-only filesystem may very well go through without
any SCSI request...
Anyway. Maybe the WD My Book does not handle the SCSI START STOP UNIT command
like the Linux SCSI core expects. You could try adding a device quirks
workaround which influences the parameters for this
Is it sufficient to remove only sbp2 but leave ohci1394 (and ieee1394 of
course) loaded during suspend, with the disk attached?
--
Ubuntu becomes unrepsonsive on resume with external firewire disk attached
https://bugs.launchpad.net/bugs/320099
You received this bug notification because you are
How does lspci -v show the controller? The PCI IDs look like from the
Texas Instruments TSB43AB** family.
The messages
ohci1394: fw-host0: Get PHY Reg timeout [0x/0x/100]
indicate that the drivers were unable to perform the last steps of
initialization. For now I don't
PeterNSteinmetz, this is different from the other reporters' issues.
Yours is likely bad hardware, perhaps bad firmware. The drivers can't
do anything about it. It could perhaps be caused by old revisions of
1394b physical interface chips (TI TSB81BA3 erratum without software
workaround). If
The patch from comment 16 has been merged in upstream released kernels
2.6.29-rc4, 2.6.28.5, and 2.6.27.16.
--
Firewire IPOD does not work since upgrade to 8.10
https://bugs.launchpad.net/bugs/294391
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
454abp ,
if you use workaround 9 (i.e. 1 and 8 as in the patch) and the file manager
freezes during iPod access, what do you get from dmesg? (If the UI becomes
very unresponsive, try [Ctrl][Alt][F1] to get a text console.)
--
Firewire IPOD does not work since upgrade to 8.10
Why does Ubuntu (or only your two test boxes?) not load raw1394
automatically when a DV device is plugged in?
Are the module aliases somehow missing in Ubuntu's raw1394? (Run
modinfo raw1394.)
Or does Ubuntu have a blacklist raw1394 directive somewhere in /etc?
(Run grep -r 'blacklist raw1394'
OK, this is how it should be; raw1394 _should_ be automatically loaded
with that when a DV device appears. Could be that the drivers have a
special problem with your particular camera.
Your local change to the udev rules does not influence autoloading, only
how device file ownership is set up
Yes, there would be some benefits to provide the new drivers as an opt-in
alternative, i.e. enabled in the build configuration but blacklisted to prevent
automatic loading:
- Asynchronous performance of 1394a buses (a.k.a. FireWire 400) is indeed
considerably higher in the new firewire
Comment 3 still shows the taint due to machine check exception. Comment
4 doesn't have that anymore, so that's out of the way.
Gentoo tracks a different forcedeth related bug: https://bugs.gentoo.org/188767
The first attachment of this bug contains test code (a server and a client).
Maybe you
If workaround 8 does not help, try the same with
# echo 1 /sys/module/sbp2/parameters/workarounds
--
Firewire IPOD does not work since upgrade to 8.10
https://bugs.launchpad.net/bugs/294391
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Please try the following command as root user:
# echo 8 /sys/module/sbp2/parameters/workarounds
Then plug in the iPod. If it works, post the contents of dmesg, beginning with
the Node added message from when the iPod was plugged in.
--
Firewire IPOD does not work since upgrade to 8.10
I just remembered another old issue with FireWire iPods which was never
addressed in the drivers. (Can't process more than one page table
element.) It seems that performance enhancements in the block layer of
newer kernels changed that problem from a theoretical one into an actual
one.
Alas it
454abp: Sounds good.
- Is reading (and writing...) of small and large files stable with
workarounds=8?
- Which iPod model is this? (http://en.wikipedia.org/wiki/IPod#Models)
--
Firewire IPOD does not work since upgrade to 8.10
https://bugs.launchpad.net/bugs/294391
You received this bug
Thanks for the information. We can add the firmware_revision and
model_id to a quirks list in the sbp2 driver so that the workaround will
activated automatically by upcoming releases of the kernel.
Until this made its way into the kernel, you can enable this workaround
permantly by adding the
Report at upstream dvgrab:
https://sourceforge.net/tracker/index.php?func=detailaid=2492640group_id=14103atid=114103
Status so far:
linux-image-2.6.18-6-686_2.6.18.dfsg.1-23etch1_i386.deb works while Ubuntu
2.6.27-9.19-generic doesn't.
--
dvgrab Error:no DV with Panasonic NV-MX500EG
Kevin,
is it also OK to specify both workarounds combined, i.e.
# echo 9 /sys/module/sbp2/parameters/workarounds
The trouble is that 2nd generation iPods and 3rd generation iPods have
the same firmware_revision, vendor_id, model_id. So we can only add one
driver-internal quirks list entry for
I agree with mbeili.
FYI, the patch is currently staged in kernel.org's linux1394-2.6.git's
fixes branch. I will push this for 2.6.29-rc circa in a week or so
together with some unrelated updates, and after that propose it for
inclusion into kernel.org's 2.6.28.y and 2.6.27.y. You may want to
Kevin,
what hardware platform do you have? Intel or AMD or...? Do you know on which
chipset (nortbridge, southbridge) your maiboard is based on?
--
Firewire IPOD does not work since upgrade to 8.10
https://bugs.launchpad.net/bugs/294391
You received this bug notification because you are a
454abp and Kevin,
please also post the result of ls /sys/bus/ieee1394/devices/*/model_id from
when the iPod is connected.
--
Firewire IPOD does not work since upgrade to 8.10
https://bugs.launchpad.net/bugs/294391
You received this bug notification because you are a member of Ubuntu
Bugs, which
test patch posted at http://lkml.org/lkml/2009/1/24/83
--
Firewire IPOD does not work since upgrade to 8.10
https://bugs.launchpad.net/bugs/294391
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
diefans,
is this the LaCie Little Disk, USB 2.0 + FireWire 400, with shortcut button?
--
External ieee1394 drive not recognized 2.6.27-5
https://bugs.launchpad.net/bugs/279342
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I suspect they will fix it in a future Ubuntu release by replacing the
kernel drivers ohci1394 + ieee1394 + raw1394 by the kernel drivers
firewire-ohci + firewire-core. Presently, those newer drivers are
already shipped in Ubuntu's kernel packages in parallel with the older
drivers. The older
Robert Petersen wrote:
I am running Ubunto 9.10, and Kino 1.3.3
[...]
the biggest problem is actually that I have to plugin the camera to
use the program. So when i have copied all the scenes to the computer,
you can work and edit the scenes without having the camera installed.
But when you
Re comment 56...59:
So when i have copied all the scenes to the computer,
you can work and edit the scenes without having the camera installed.
But when you want to export it to example mpeg or what ever, you cant
the following error Error setting the IEEE 1394 port (host adaptor)
I tested
I don't see anything related to 1394 in david's comments. Wrong bug
number?
-
Those who still have sbp2 login failures should please try the following:
- Make sure to have a somewhat recent kernel package which has
firewire-ohci.ko installed in parallel with ohci1394.ko.
-
Does the fact that this bug has not been touched in 3 months mean
there is no desire to fix it?
I more likely means that nobody is here who knows the driver well enough
to suggest a fix. You could report to upstream: net...@vger.kernel.org,
Cc: Ayaz Abdulla aabdu...@nvidia.com (forcedeth
Does the fact that this bug has not been touched in 3 months mean
there is no desire to fix it?
It more likely means that nobody is here who knows the driver well
enough to suggest a fix. You could report to upstream:
net...@vger.kernel.org, Cc: Ayaz Abdulla aabdu...@nvidia.com
(forcedeth
I read in another bug though that ubuntu devs don't want bugs filed
upstream and instead want them filed with LP:
...
This inconsistency makes it difficult to know when to file upstream and
when not to.
I'm not speaking for Canonical, I'm not even using Ubuntu. I'm only
watching this bug
There are still some very visible regressions of the new vs. the old
stack, see ieee1394.wiki.kernel.org. Alas, upstream work on these
issues slowed down again during the last few months due to lack of
developer manhours.
--
Enable new Firewire stack in default kernel config
Duncan Lithgow wrote:
Reopening this bug.
In Ubuntu 8.10 (Alpha 6) importing dv over firewire does not just work with
Kino 1.3.0
I'm back at the familiar message: WARNING: raw1394 kernel module not loaded
or failure to read/write /dev/raw1394
My first guess is that this is because
*** This bug is a duplicate of bug 6290 ***
https://bugs.launchpad.net/bugs/6290
Scott James Remnant wrote on 2008-04-24:
...
The statements about IEEE 1394 and about what the linux1394 stack does
are... somewhat inaccurate. I won't comment further.
Failing that, an interim solution
*** This bug is a duplicate of bug 6290 ***
https://bugs.launchpad.net/bugs/6290
Scott James Remnant wrote on 2008-06-09:
dv1394 is going away in the kernel :-(
Nowadays I think that dv1394 will remain in the mainline as long as the
ieee1394 driver stack remains in there. However, it is
Duncan:
With the camcorder attached and switched on, please save the output of dmesg
into a file and attach it. Also, post the output of
ls /sys/bus/ieee1394/devices/
and
grep . /sys/bus/ieee1394/devices/fw-host0/*
Furthermore, does Ubuntu's libraw1394 package maintainer listen
Tim, run modprobe ohci1394 as root and see if there is anything added
to the dmesg output.
--
Firewire drive not detected
https://bugs.launchpad.net/bugs/105317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
1 - 100 of 186 matches
Mail list logo
