Discussion:
[wish-info] 2.6.14?
Shawn Rutledge
2005-11-11 07:20:58 UTC
Permalink
Is anybody running a USB powerlinc on Linux 2.6.14 yet? Mine is
working fine with 2.6.9, but now that I have tried to upgrade, and
also upgraded to x10dev-2.1.3, for a while it hangs when I try to send
commands to a device; and later it's like this:

[nucleus][12:18:37 AM] echo 1 > /dev/x10/g6
bash: /dev/x10/g6: Bad address
Scott Hiles
2005-11-11 12:40:48 UTC
Permalink
I haven't gotten a 2.6.14 kernel yet. As soon as I get one going I will see
if I can reproduce the problem. I am running it on a 2.6.13 kernel with no
problems.

One thing to check is that you have the right hiddev for the device. Look
in your /var/log/messages when you start plusbd and see if you are making a
connection to the device driver. Also type "lsmod | grep x10" to make sure
that the x10 driver is loaded. When I went to 2.6.12 the name and location
of hiddev changed so my startup scripts had to change.

Scott
-----Original Message-----
Shawn Rutledge
Sent: Friday, November 11, 2005 2:21 AM
Subject: [wish-info] 2.6.14?
Is anybody running a USB powerlinc on Linux 2.6.14 yet? Mine
is working fine with 2.6.9, but now that I have tried to
upgrade, and also upgraded to x10dev-2.1.3, for a while it
hangs when I try to send commands to a device; and later it's
[nucleus][12:18:37 AM] echo 1 > /dev/x10/g6
bash: /dev/x10/g6: Bad address
-------------------------------------------------------
Tame your development challenges with Apache's Geronimo App
Server. Download it for free - -and be entered to win a 42"
http://sourceforge.net/geronimo.php
_______________________________________________
wish-info mailing list
https://lists.sourceforge.net/lists/listinfo/wish-info
wsh
2005-11-11 16:17:36 UTC
Permalink
I am running Fedora Core 4 on a 4 processor system running 2.6.13-1.1532_FC4
without any problems. But, when I went to 2.6.12 for FC4, I found that the
devices changed. The latest version of the scripts for starting up the
drivers (on sourceforge) have an added step to look through the dmesg file
to find the hiddev associated with the PLUSB and then automatically select
it. Once I put that change in, my system has worked flawlessly.

And, one other little thing that I found is that 2.6.12 introduced something
into the USB stack that caused plusbd to sometimes not find the device so I
added the "-delay" flag. 2.6.13 fixed that problem and I no longer have to
use the -delay on 2.6.13.

Hope this helps,
Scott

----- Original Message -----
From: "John Liss" <***@lissproductions.com>
To: <wish-info-***@lists.sourceforge.net>
Sent: Friday, November 11, 2005 10:12 AM
Subject: RE: [wish-info] 2.6.14?
I rolled back to 2.6.12-1.1456_FC4 over halloween just for that very
reason.
Did a yum update | upgrade and it installed 2.6.13-1.1532_FC4 which has
that
problem also.
I thought ok... I'll reconfig re make but it didn't work.
In /var/log/messages it didn't see the powerlink usb that I use. :/
-----Original Message-----
Date: Fri, 11 Nov 2005 07:40:48 -0500
Subject: RE: [wish-info] 2.6.14?
Post by Scott Hiles
I haven't gotten a 2.6.14 kernel yet. As soon as I get one going I will see
if I can reproduce the problem. I am running it on a 2.6.13 kernel with no
problems.
One thing to check is that you have the right hiddev for the device.
Look
in your /var/log/messages when you start plusbd and see if you are making a
connection to the device driver. Also type "lsmod | grep x10" to make sure
that the x10 driver is loaded. When I went to 2.6.12 the name and location
of hiddev changed so my startup scripts had to change.
Scott
-----Original Message-----
Shawn Rutledge
Sent: Friday, November 11, 2005 2:21 AM
Subject: [wish-info] 2.6.14?
Is anybody running a USB powerlinc on Linux 2.6.14 yet? Mine
is working fine with 2.6.9, but now that I have tried to
upgrade, and also upgraded to x10dev-2.1.3, for a while it
hangs when I try to send commands to a device; and later it's
[nucleus][12:18:37 AM] echo 1 > /dev/x10/g6
bash: /dev/x10/g6: Bad address
-------------------------------------------------------
Tame your development challenges with Apache's Geronimo App
Server. Download it for free - -and be entered to win a 42"
http://sourceforge.net/geronimo.php
_______________________________________________
wish-info mailing list
https://lists.sourceforge.net/lists/listinfo/wish-info
-------------------------------------------------------
Tame your development challenges with Apache's Geronimo App Server.
Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
wish-info mailing list
https://lists.sourceforge.net/lists/listinfo/wish-info
Shawn Rutledge
2005-11-12 04:57:08 UTC
Permalink
Post by wsh
I am running Fedora Core 4 on a 4 processor system running 2.6.13-1.1532_FC4
without any problems. But, when I went to 2.6.12 for FC4, I found that the
devices changed. The latest version of the scripts for starting up the
drivers (on sourceforge) have an added step to look through the dmesg file
to find the hiddev associated with the PLUSB and then automatically select
it. Once I put that change in, my system has worked flawlessly.
Yes that fixed it for me too, thanks.

It does seem a bit awkward that you have to grep dmesg though.
Ideally there would be a /proc or /sys file which maps the usb ID to
the appopriate device in /dev.

Loading...