2:08 p.m.
Hi everybody, I'm running fc3 quite successful and am very happy with
it. However, shortly after the fresh install firewire hotplugging
started working, and I can't even mount my disks by hand because there
is no /dev/sda<n> created. So I finally came around to look after it but
without success so far, and this is what I get in my system log:
Jan 25 21:03:06 localhost kernel: ieee1394: Error parsing configrom
for node 0-01:1023
Jan 25 21:03:07 localhost kernel: ieee1394: Error parsing configrom for node 0-00:1023
Any help much appreciated, Florian
3:21 p.m.
tir, 25.01.2005 kl. 21.08 skrev Florian Idelberger:
Hi everybody, I'm running fc3 quite successful and am very happy
with
it. However, shortly after the fresh install firewire hotplugging
started working, and I can't even mount my disks by hand because there
is no /dev/sda<n> created. So I finally came around to look after it but
without success so far, and this is what I get in my system log:
> Jan 25 21:03:06 localhost kernel: ieee1394: Error parsing configrom for node
0-01:1023
> Jan 25 21:03:07 localhost kernel: ieee1394: Error parsing configrom for node
0-00:1023
Any help much appreciated, Florian
Does it work for the original on-cd kernel, but dosn't with one from
fedora-updates? Which kernel is the latest which has this working?
3:32 a.m.
On Tue, 2005-01-25 at 22:21 +0100, Kyrre Ness Sjobak wrote:
tir, 25.01.2005 kl. 21.08 skrev Florian Idelberger:
> Hi everybody, I'm running fc3 quite successful and am very happy with
> it. However, shortly after the fresh install firewire hotplugging
> started working, and I can't even mount my disks by hand because there
> is no /dev/sda<n> created. So I finally came around to look after it but
> without success so far, and this is what I get in my system log:
>
> > Jan 25 21:03:06 localhost kernel: ieee1394: Error parsing configrom for node
0-01:1023
> > Jan 25 21:03:07 localhost kernel: ieee1394: Error parsing configrom for node
0-00:1023
>
> Any help much appreciated, Florian
Does it work for the original on-cd kernel, but dosn't with one from
fedora-updates? Which kernel is the latest which has this working?
At the beginning it worked, with the on-cd kernel, now it doesn't matter
if I boot the original one or the latest (2.6.10). Normally I'm running
2.6.10 (build 447 i think)
7:55 a.m.
On Wed, 2005-01-26 at 10:32 +0100, Florian Idelberger wrote:
On Tue, 2005-01-25 at 22:21 +0100, Kyrre Ness Sjobak wrote:
> tir, 25.01.2005 kl. 21.08 skrev Florian Idelberger:
> > Hi everybody, I'm running fc3 quite successful and am very happy with
> > it. However, shortly after the fresh install firewire hotplugging
> > started working, and I can't even mount my disks by hand because there
> > is no /dev/sda<n> created. So I finally came around to look after it but
> > without success so far, and this is what I get in my system log:
> >
> > > Jan 25 21:03:06 localhost kernel: ieee1394: Error parsing configrom for
node 0-01:1023
> > > Jan 25 21:03:07 localhost kernel: ieee1394: Error parsing configrom for
node 0-00:1023
> >
> > Any help much appreciated, Florian
>
> Does it work for the original on-cd kernel, but dosn't with one from
> fedora-updates? Which kernel is the latest which has this working?
>
At the beginning it worked, with the on-cd kernel, now it doesn't matter
if I boot the original one or the latest (2.6.10). Normally I'm running
2.6.10 (build 447 i think)
O.k., this is so strange.
fstab-sync gives me a lovely segfault if I do "fstab-sync --clean", and
nothing but.
reloading of sbp2 didn't help either.
10:42 a.m.
On Thu, 2005-01-27 at 14:55 +0100, Florian Idelberger wrote:
On Wed, 2005-01-26 at 10:32 +0100, Florian Idelberger wrote:
> On Tue, 2005-01-25 at 22:21 +0100, Kyrre Ness Sjobak wrote:
> > tir, 25.01.2005 kl. 21.08 skrev Florian Idelberger:
> > > Hi everybody, I'm running fc3 quite successful and am very happy with
> > > it. However, shortly after the fresh install firewire hotplugging
> > > started working, and I can't even mount my disks by hand because
there
> > > is no /dev/sda<n> created. So I finally came around to look after it
but
> > > without success so far, and this is what I get in my system log:
> > >
> > > > Jan 25 21:03:06 localhost kernel: ieee1394: Error parsing configrom
for node 0-01:1023
> > > > Jan 25 21:03:07 localhost kernel: ieee1394: Error parsing configrom
for node 0-00:1023
> > >
> > > Any help much appreciated, Florian
> >
> > Does it work for the original on-cd kernel, but dosn't with one from
> > fedora-updates? Which kernel is the latest which has this working?
> >
>
> At the beginning it worked, with the on-cd kernel, now it doesn't matter
> if I boot the original one or the latest (2.6.10). Normally I'm running
> 2.6.10 (build 447 i think)
>
O.k., this is so strange.
fstab-sync gives me a lovely segfault if I do "fstab-sync --clean", and
nothing but.
reloading of sbp2 didn't help either.
Downgrading udev from 039-10 to 039-8, didn't help.
But after removing the whole firewire controller on runtime, and
reinserting it (with nothing mounted, because there was nothing
recognized, I got some interesting new kernel output which I don't like
if it means what I think. Plus, this just can't be, because sometimes it
works, and it works especially well with other distros, like debian or
knoppix.
So here's the output:
Jan 27 17:36:55 localhost kernel: ohci1394: fw-host0: Set PHY Reg
timeout [0xffffffff/0x00004000/100]
[root@localhost dev]# tail /var/log/messages
Jan 27 17:37:19 localhost wait_for_sysfs[5060]: either wait_for_sysfs
(udev 039) needs an update to handle the device
'/devices/pci0000:00/0000:00:11.1/0000:06:00.0/fw-
host0/01ac9120000002e7' properly (unknown bus) or the sysfs-support of
your device's driver needs to be fixed, please report to <linux-hotplug-
devel(a)lists.sourceforge.net>
Jan 27 17:37:19 localhost ieee1394.agent[5076]: ... no drivers for
IEEE1394 product 0x/0x/0x
Jan 27 17:37:19 localhost ieee1394.agent[5091]: ... no drivers for
IEEE1394 product 0x/0x/0x
Jan 27 17:37:19 localhost kernel: ieee1394: Error parsing configrom for
node 0-02:1023
Jan 27 17:37:19 localhost wait_for_sysfs[5109]: error: unknown bus,
please report to <linux-hotplug-devel(a)lists.sourceforge.net> 'ieee1394'
Jan 27 17:37:19 localhost wait_for_sysfs[5109]: either wait_for_sysfs
(udev 039) needs an update to handle the device
'/devices/pci0000:00/0000:00:11.1/0000:06:00.0/fw-
host0/400401012800c037' properly (unknown bus) or the sysfs-support of
your device's driver needs to be fixed, please report to <linux-hotplug-
devel(a)lists.sourceforge.net>
Jan 27 17:37:19 localhost ieee1394.agent[5114]: ... no drivers for
IEEE1394 product 0x/0x/0x
Jan 27 17:37:21 localhost wait_for_sysfs[5133]: error: unknown bus,
please report to <linux-hotplug-devel(a)lists.sourceforge.net> 'ieee1394'
Jan 27 17:37:21 localhost wait_for_sysfs[5133]: either wait_for_sysfs
(udev 039) needs an update to handle the device
'/devices/pci0000:00/0000:00:11.1/0000:06:00.0/fw-
host0/400401012800c037/400401012800c037-0' properly (unknown bus) or the
sysfs-support of your device's driver needs to be fixed, please report
to <linux-hotplug-devel(a)lists.sourceforge.net>
Jan 27 17:37:21 localhost ieee1394.agent[5137]: ... no drivers for
IEEE1394 product 0x/0x/0x
12:26 p.m.
tor, 27.01.2005 kl. 14.55 skrev Florian Idelberger:
On Wed, 2005-01-26 at 10:32 +0100, Florian Idelberger wrote:
> On Tue, 2005-01-25 at 22:21 +0100, Kyrre Ness Sjobak wrote:
> > tir, 25.01.2005 kl. 21.08 skrev Florian Idelberger:
> > > Hi everybody, I'm running fc3 quite successful and am very happy with
> > > it. However, shortly after the fresh install firewire hotplugging
> > > started working, and I can't even mount my disks by hand because
there
> > > is no /dev/sda<n> created. So I finally came around to look after it
but
> > > without success so far, and this is what I get in my system log:
> > >
> > > > Jan 25 21:03:06 localhost kernel: ieee1394: Error parsing configrom
for node 0-01:1023
> > > > Jan 25 21:03:07 localhost kernel: ieee1394: Error parsing configrom
for node 0-00:1023
> > >
> > > Any help much appreciated, Florian
> >
> > Does it work for the original on-cd kernel, but dosn't with one from
> > fedora-updates? Which kernel is the latest which has this working?
> >
>
> At the beginning it worked, with the on-cd kernel, now it doesn't matter
> if I boot the original one or the latest (2.6.10). Normally I'm running
> 2.6.10 (build 447 i think)
>
O.k., this is so strange.
fstab-sync gives me a lovely segfault if I do "fstab-sync --clean", and
nothing but.
reloading of sbp2 didn't help either.
Somehow i have a thought that this belongs in bugzilla!
1:13 p.m.
On Tue, 2005-01-25 at 21:08 +0100, Florian Idelberger wrote:
Hi everybody, I'm running fc3 quite successful and am very happy
with
it. However, shortly after the fresh install firewire hotplugging
started working, and I can't even mount my disks by hand because there
is no /dev/sda<n> created. So I finally came around to look after it but
without success so far, and this is what I get in my system log:
> Jan 25 21:03:06 localhost kernel: ieee1394: Error parsing configrom for node
0-01:1023
> Jan 25 21:03:07 localhost kernel: ieee1394: Error parsing configrom for node
0-00:1023
These messages might be harmless (at least, I'm also seeing them and
firewire works mostly fine here).
Check if the sbp2 module is loaded:
$ lsmod | grep sbp2
If not, load it manually (keep an eye on /var/log/messages):
$ sudo modprobe sbp2
The recent kernels are very picky about module options, so if you have
any set in /etc/modprobe.conf ("serialize_io=1" is very common), make
sure they're spelled out correctly and without any trailing spaces.
Also, you might try experimenting with when the disk is turned on (prior
to or after the system is brought up).
Hope that helps,
--
Ziga
1:23 p.m.
Ziga Mahkovec wrote:
On Tue, 2005-01-25 at 21:08 +0100, Florian Idelberger wrote:
>Hi everybody, I'm running fc3 quite successful and am very happy with
>it. However, shortly after the fresh install firewire hotplugging
>started working, and I can't even mount my disks by hand because there
>is no /dev/sda<n> created. So I finally came around to look after it but
>without success so far, and this is what I get in my system log:
>
>
>
>>Jan 25 21:03:06 localhost kernel: ieee1394: Error parsing configrom for node
0-01:1023
>>Jan 25 21:03:07 localhost kernel: ieee1394: Error parsing configrom for node
0-00:1023
>>
>>
These messages might be harmless (at least, I'm also seeing them and
firewire works mostly fine here).
Check if the sbp2 module is loaded:
$ lsmod | grep sbp2
If not, load it manually (keep an eye on /var/log/messages):
$ sudo modprobe sbp2
The recent kernels are very picky about module options, so if you have
any set in /etc/modprobe.conf ("serialize_io=1" is very common), make
sure they're spelled out correctly and without any trailing spaces.
Also, you might try experimenting with when the disk is turned on (prior
to or after the system is brought up).
Hope that helps,
1) all modules are loaded, and as I said, it works --sometimes-- (rare),
although I have to mount manually
2) no I have not specified any options, afaik there shouldn't be any
necessary
3) at sometime this evening I'll downgrade udev, as Kyrre proposed
but nonetheless, thx for your post
1:43 p.m.
On Wed, 2005-01-26 at 20:23 +0100, Florian Idelberger wrote:
>Check if the sbp2 module is loaded:
>$ lsmod | grep sbp2
>
1) all modules are loaded, and as I said, it works --sometimes-- (rare),
although I have to mount manually
I see, it wasn't clear from your email that it does work on occasion.
Also, "no /dev/sda<n> created" in my case usually meant sbp2 didn't
get
loaded.
Having to mount manually on the other hand meant fstab-sync wasn't
picking up the partitions. Usually I worked around this with:
$ rmdir /media/firewire*
$ fstab-sync --clean
$ sudo rmmod sbp2; sudo modprobe sbp2
But I guess it could be udev as well.
--
Ziga
7022
days inactive
7024
days old
desktop@lists.fedoraproject.org
8 comments
3 participants
participants (3)
-
Florian Idelberger -
Kyrre Ness Sjobak -
Ziga Mahkovec