Discussion:
[wish-info] Re: compile X10 1.6.2 driver on Redhat kernel 2.4.18-3
Hong Hsu
2003-05-13 00:26:15 UTC
Permalink
After following steps,
#make mrproper
#make menuconfig
#make dep
#nohup make bzImage &

#tail -f nohup.out message shows:
......
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o tools/build
tools/build.c -I/usr/src/linux-2.4.18-3/include
objcopy -O binary -R .note -R .comment -S compressed/bvmlinux
compressed/bvmlinux.out
tools/build -b bbootsect bsetup compressed/bvmlinux.out CURRENT > bzImage
Root device is (3, 8)
Boot sector 512 bytes.
Setup is 4772 bytes.
System is 1022 kB
warning: kernel is too big for standalone boot from floppy
make[1]: Leaving directory `/usr/src/linux-2.4.18-3/arch/i386/boot'

May I say building kernel is OK at this point? but install x10 driver
still got same error message at this stage. Is that valid to
install at this point?

Thanks,
-Hong
Hong Hsu
2003-05-13 15:25:08 UTC
Permalink
Scott,

compilation of drivers has no problem. Does order of installing
drivers is matter? Do I need to install all 13 x10_xyz.o drivers as I
only use PowerLincUSB?

I have installed x10_plusb.o and x10_strings.o with no problem.
However, installation of x10_core.o causes Segmentation fault AND
tainted others:
[***@puma root]# lsmod
Module Size Used by Tainted: PF
x10_core 22688 1 (initializing)
x10_ldisc_plusb 8192 0 [x10_core]
x10_xcvr_plusb 7456 0 [x10_core x10_ldisc_plusb]
x10_xcvr_pl 7104 0 (unused)
x10_strings 2688 0 [x10_core]
x10_plusb 38464 0 [x10_ldisc_plusb x10_xcvr_plusb
x10_xcvr_pl]
i810_audio 23008 0 (autoclean)
ac97_codec 11936 0 (autoclean) [i810_audio]
soundcore 6692 2 (autoclean) [i810_audio]
NVdriver 1066272 10
nfsd 76192 8 (autoclean)
lockd 56768 1 (autoclean) [nfsd]
sunrpc 75764 1 (autoclean) [nfsd lockd]
autofs 12132 0 (autoclean) (unused)
nvnet 30240 2
ipchains 43528 14


Now I even can not unload x10_core. Another thing:
[***@puma wish-1.6.2]# insmod -f x10_pl.o
x10_pl.o: init_module: Operation not permitted
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters

Is this version issue you mentioned? How do I fix that?
Many thanks,
-Hong
OK...your kernel will compile so you are getting closer. Make sure that you
have a link from of /usr/src/linux to /usr/src/linux-2.4.18-3.
Now go to the directory that you untarred the source code for the x10
# make clean
# make
You should end up with x10_plusb.o, x10_pl.o, x10_cm11a.o, and x10_cm17a.o.
If you got this far, then your drivers have been compiled. Now, try loading
# insmod -f x10_<device>.o
You may get an error that the versions don't match don't worry about it at
this point. You should be able to test that the drivers work on your
machine by running utils/x10attach if needed.
If you got the error that the versions don't match the problem is in
/usr/src/linux/Makefile and I can tell you how to fix the error.
Scott
-----Original Message-----
Sent: Monday, May 12, 2003 8:26 PM
Subject: [wish-info] Re: compile X10 1.6.2 driver on Redhat
kernel 2.4.18-3
After following steps,
#make mrproper
#make menuconfig
#make dep
#nohup make bzImage &
......
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o tools/build
tools/build.c -I/usr/src/linux-2.4.18-3/include
objcopy -O binary -R .note -R .comment -S compressed/bvmlinux
compressed/bvmlinux.out
tools/build -b bbootsect bsetup compressed/bvmlinux.out
CURRENT > bzImage Root device is (3, 8) Boot sector 512
bytes. Setup is 4772 bytes. System is 1022 kB
warning: kernel is too big for standalone boot from floppy
make[1]: Leaving directory `/usr/src/linux-2.4.18-3/arch/i386/boot'
May I say building kernel is OK at this point? but install
x10 driver
still got same error message at this stage. Is that valid to
install at this point?
Thanks,
-Hong
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003,
Santa Clara The only event dedicated to issues related to
Linux enterprise solutions www.enterpriselinuxforum.com
_______________________________________________
wish-info mailing list
https://lists.sourceforge.net/lists/listinfo/w> ish-info
--
<Linux kernel:>< As a computer I find your faith in technology amusing.
Scott Hiles
2003-05-13 15:33:49 UTC
Permalink
You only install the driver called x10_<device>.o. So, for the PowerLinc
USB, you would only install x10_plusb.o. The rest are compiled into the
device driver.

When you install x10_plusb.o, your var/log/messages should now have a
message indicting that the driver was loaded and the version of the X10
transceiver.

Continue with the instructions to remove hid.o (rmmod hid) so that it won't
interfere with the X10 USB drivers. If you have run the script to make your
devices, you should be all set. You should now be able to send commands to
the X10 devices.

If it all works at this point, you have completed the test. You now just
need to install the drivers into your modules directory (which is what
install.sh should be able to do) and create a startup script in
/etc/rc.d/init.d. Look at the example scripts for startup for a way that I
do it on a RedHat System.

Scott

-----Original Message-----
From: Hong Hsu [mailto:***@bellatlantic.net]
Sent: Tuesday, May 13, 2003 11:25 AM
To: Scott Hiles
Cc: wish-***@lists.sourceforge.net
Subject: Re: [wish-info] Re: compile X10 1.6.2 driver on Redhat kernel
2.4.18-3


Scott,

compilation of drivers has no problem. Does order of installing drivers
is matter? Do I need to install all 13 x10_xyz.o drivers as I only use
PowerLincUSB?

I have installed x10_plusb.o and x10_strings.o with no problem. However,
installation of x10_core.o causes Segmentation fault AND tainted others:
[***@puma root]# lsmod
Module Size Used by Tainted: PF
x10_core 22688 1 (initializing)
x10_ldisc_plusb 8192 0 [x10_core]
x10_xcvr_plusb 7456 0 [x10_core x10_ldisc_plusb]
x10_xcvr_pl 7104 0 (unused)
x10_strings 2688 0 [x10_core]
x10_plusb 38464 0 [x10_ldisc_plusb x10_xcvr_plusb
x10_xcvr_pl]
i810_audio 23008 0 (autoclean)
ac97_codec 11936 0 (autoclean) [i810_audio]
soundcore 6692 2 (autoclean) [i810_audio]
NVdriver 1066272 10
nfsd 76192 8 (autoclean)
lockd 56768 1 (autoclean) [nfsd]
sunrpc 75764 1 (autoclean) [nfsd lockd]
autofs 12132 0 (autoclean) (unused)
nvnet 30240 2
ipchains 43528 14


Now I even can not unload x10_core. Another thing:
[***@puma wish-1.6.2]# insmod -f x10_pl.o
x10_pl.o: init_module: Operation not permitted
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters

Is this version issue you mentioned? How do I fix that?
Many thanks,
-Hong


Scott Hiles wrote:


OK...your kernel will compile so you are getting closer. Make sure that you

have a link from of /usr/src/linux to /usr/src/linux-2.4.18-3.



Now go to the directory that you untarred the source code for the x10

drivers and try the following commands:



# make clean

# make



You should end up with x10_plusb.o, x10_pl.o, x10_cm11a.o, and x10_cm17a.o.

If you got this far, then your drivers have been compiled. Now, try loading

them by hand using:



# insmod -f x10_<device>.o



You may get an error that the versions don't match don't worry about it at

this point. You should be able to test that the drivers work on your

machine by running utils/x10attach if needed.



If you got the error that the versions don't match the problem is in

/usr/src/linux/Makefile and I can tell you how to fix the error.



Scott





-----Original Message-----

From: wish-info-***@lists.sourceforge.net

[mailto:wish-info-***@lists.sourceforge.net] On Behalf Of Hong Hsu

Sent: Monday, May 12, 2003 8:26 PM

To: wish-***@lists.sourceforge.net

Subject: [wish-info] Re: compile X10 1.6.2 driver on Redhat

kernel 2.4.18-3





After following steps,

#make mrproper

#make menuconfig

#make dep

#nohup make bzImage &



#tail -f nohup.out message shows:

......

gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o tools/build

tools/build.c -I/usr/src/linux-2.4.18-3/include

objcopy -O binary -R .note -R .comment -S compressed/bvmlinux

compressed/bvmlinux.out

tools/build -b bbootsect bsetup compressed/bvmlinux.out

CURRENT > bzImage Root device is (3, 8) Boot sector 512

bytes. Setup is 4772 bytes. System is 1022 kB

warning: kernel is too big for standalone boot from floppy

make[1]: Leaving directory `/usr/src/linux-2.4.18-3/arch/i386/boot'



May I say building kernel is OK at this point? but install

x10 driver

still got same error message at this stage. Is that valid to

install at this point?



Thanks,

-Hong









-------------------------------------------------------

Enterprise Linux Forum Conference & Expo, June 4-6, 2003,

Santa Clara The only event dedicated to issues related to

Linux enterprise solutions www.enterpriselinuxforum.com



_______________________________________________

wish-info mailing list

wish-***@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/w> ish-info
--
<Linux kernel:>< As a computer I find your faith in technology amusing.
Hong Hsu
2003-05-15 01:08:25 UTC
Permalink
Scott,

Two questions.
1) What the following error means, and how to fix it?
[x10]#mknod /dev/x10/c3 c 120 3
[***@puma wish-1.6.2]#rmmod hid
[***@puma wish-1.6.2]# insmod x10_plusb
[***@puma wish-1.6.2]# x10logd
Error: Unable to open device /dev/x10/log (No such file or directory)

2) When I run simple test:
#echo 1 >/dev/x10/c3

Got system locked up! The message is:
Kernel panic: Aiee, killing interrupt handlers!

I have to reboot it. Am I missing some thing? (I use PowerLincUSB and
lamp module c3 is the only module)
Thanks,
-Hong
You only install the driver called x10_<device>.o. So, for the PowerLinc USB, you would only install x10_plusb.o.
The rest are compiled into the device driver.
When you install x10_plusb.o, your var/log/messages should now have a
message indicting that the driver was loaded and the version of the
X10 transceiver.
Continue with the instructions to remove hid.o (rmmod hid) so that it
won't interfere with the X10 USB drivers. If you have run the script
to make your devices, you should be all set. You should now be able
to send commands to the X10 devices.
If it all works at this point, you have completed the test. You now
just need to install the drivers into your modules directory (which is
what install.sh should be able to do) and create a startup script in
/etc/rc.d/init.d. Look at the example scripts for startup for a way
that I do it on a RedHat System.
Scott
-----Original Message-----
Sent: Tuesday, May 13, 2003 11:25 AM
To: Scott Hiles
Subject: Re: [wish-info] Re: compile X10 1.6.2 driver on Redhat
kernel 2.4.18-3
Scott,
compilation of drivers has no problem. Does order of
installing drivers is matter? Do I need to install all 13
x10_xyz.o drivers as I only use PowerLincUSB?
I have installed x10_plusb.o and x10_strings.o with no problem.
However, installation of x10_core.o causes Segmentation fault AND
Module Size Used by Tainted: PF
x10_core 22688 1 (initializing)
x10_ldisc_plusb 8192 0 [x10_core]
x10_xcvr_plusb 7456 0 [x10_core x10_ldisc_plusb]
x10_xcvr_pl 7104 0 (unused)
x10_strings 2688 0 [x10_core]
x10_plusb 38464 0 [x10_ldisc_plusb x10_xcvr_plusb
x10_xcvr_pl]
i810_audio 23008 0 (autoclean)
ac97_codec 11936 0 (autoclean) [i810_audio]
soundcore 6692 2 (autoclean) [i810_audio]
NVdriver 1066272 10
nfsd 76192 8 (autoclean)
lockd 56768 1 (autoclean) [nfsd]
sunrpc 75764 1 (autoclean) [nfsd lockd]
autofs 12132 0 (autoclean) (unused)
nvnet 30240 2
ipchains 43528 14
x10_pl.o: init_module: Operation not permitted
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
Is this version issue you mentioned? How do I fix that?
Many thanks,
-Hong
OK...your kernel will compile so you are getting closer. Make sure that you
have a link from of /usr/src/linux to /usr/src/linux-2.4.18-3.
Now go to the directory that you untarred the source code for the x10
# make clean
# make
You should end up with x10_plusb.o, x10_pl.o, x10_cm11a.o, and x10_cm17a.o.
If you got this far, then your drivers have been compiled. Now, try loading
# insmod -f x10_<device>.o
You may get an error that the versions don't match don't worry about it at
this point. You should be able to test that the drivers work on your
machine by running utils/x10attach if needed.
If you got the error that the versions don't match the problem is in
/usr/src/linux/Makefile and I can tell you how to fix the error.
Scott
-----Original Message-----
Sent: Monday, May 12, 2003 8:26 PM
Subject: [wish-info] Re: compile X10 1.6.2 driver on Redhat
kernel 2.4.18-3
After following steps,
#make mrproper
#make menuconfig
#make dep
#nohup make bzImage &
......
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o tools/build
tools/build.c -I/usr/src/linux-2.4.18-3/include
objcopy -O binary -R .note -R .comment -S compressed/bvmlinux
compressed/bvmlinux.out
tools/build -b bbootsect bsetup compressed/bvmlinux.out
CURRENT > bzImage Root device is (3, 8) Boot sector 512
bytes. Setup is 4772 bytes. System is 1022 kB
warning: kernel is too big for standalone boot from floppy
make[1]: Leaving directory `/usr/src/linux-2.4.18-3/arch/i386/boot'
May I say building kernel is OK at this point? but install
x10 driver
still got same error message at this stage. Is that valid to
install at this point?
Thanks,
-Hong
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003,
Santa Clara The only event dedicated to issues related to
Linux enterprise solutions www.enterpriselinuxforum.com
_______________________________________________
wish-info mailing list
https://lists.sourceforge.net/lists/listinfo/w> ish-info
--
<Linux kernel:>< As a computer I find your faith in technology amusing.
--
<Linux kernel:>< As a computer I find your faith in technology amusing.
Scott Hiles
2003-05-15 03:10:12 UTC
Permalink
X10logd needs the /dev/x10/log device. So, until you run the makedev.sh
command, you won't have all of the devices.

Now, the kernel locking up when you try to send to the port is a bad thing.
I don't remember if I tested the USB drivers under 2.4.18-3 so I will need
to boot that kernel and test to see if I can pinpoint the problem. I can't
do that till this coming Sunday so hang on for a bit. I know that they work
under 2.4.18-10, 2.4.18-17, 2.4.18-19, and 2.4.18-24 as I did testing for
those kernels for USB, but I didn't go back as far as 2.4.18-3.

By the way, /dev/x10/c3 should be "mknod /dev/x10/c3 c 120 34". The node
you created is for device A4. But, fixing that won't fix the kernel crash.


Scott



-----Original Message-----
From: Hong Hsu [mailto:***@bellatlantic.net]
Sent: Wednesday, May 14, 2003 9:08 PM
To: Scott Hiles
Cc: wish-***@lists.sourceforge.net
Subject: Re: [wish-info] Re: compile X10 1.6.2 driver on Redhat kernel
2.4.18-3


Scott,

Two questions.
1) What the following error means, and how to fix it?
[x10]#mknod /dev/x10/c3 c 120 3
[***@puma wish-1.6.2]#rmmod hid
[***@puma wish-1.6.2]# insmod x10_plusb
[***@puma wish-1.6.2]# x10logd
Error: Unable to open device /dev/x10/log (No such file or directory)

2) When I run simple test:
#echo 1 >/dev/x10/c3

Got system locked up! The message is:
Kernel panic: Aiee, killing interrupt handlers!

I have to reboot it. Am I missing some thing? (I use PowerLincUSB and lamp
module c3 is the only module)
Thanks,
-Hong



Scott Hiles wrote:


You only install the driver called x10_<device>.o. So, for the PowerLinc
USB, you would only install x10_plusb.o. The rest are compiled into the
device driver.

When you install x10_plusb.o, your var/log/messages should now have a
message indicting that the driver was loaded and the version of the X10
transceiver.

Continue with the instructions to remove hid.o (rmmod hid) so that it won't
interfere with the X10 USB drivers. If you have run the script to make your
devices, you should be all set. You should now be able to send commands to
the X10 devices.

If it all works at this point, you have completed the test. You now just
need to install the drivers into your modules directory (which is what
install.sh should be able to do) and create a startup script in
/etc/rc.d/init.d. Look at the example scripts for startup for a way that I
do it on a RedHat System.

Scott

-----Original Message-----
From: Hong Hsu [mailto:***@bellatlantic.net]
Sent: Tuesday, May 13, 2003 11:25 AM
To: Scott Hiles
Cc: wish-***@lists.sourceforge.net
Subject: Re: [wish-info] Re: compile X10 1.6.2 driver on Redhat kernel
2.4.18-3


Scott,

compilation of drivers has no problem. Does order of installing drivers
is matter? Do I need to install all 13 x10_xyz.o drivers as I only use
PowerLincUSB?

I have installed x10_plusb.o and x10_strings.o with no problem. However,
installation of x10_core.o causes Segmentation fault AND tainted others:
[***@puma root]# lsmod
Module Size Used by Tainted: PF
x10_core 22688 1 (initializing)
x10_ldisc_plusb 8192 0 [x10_core]
x10_xcvr_plusb 7456 0 [x10_core x10_ldisc_plusb]
x10_xcvr_pl 7104 0 (unused)
x10_strings 2688 0 [x10_core]
x10_plusb 38464 0 [x10_ldisc_plusb x10_xcvr_plusb
x10_xcvr_pl]
i810_audio 23008 0 (autoclean)
ac97_codec 11936 0 (autoclean) [i810_audio]
soundcore 6692 2 (autoclean) [i810_audio]
NVdriver 1066272 10
nfsd 76192 8 (autoclean)
lockd 56768 1 (autoclean) [nfsd]
sunrpc 75764 1 (autoclean) [nfsd lockd]
autofs 12132 0 (autoclean) (unused)
nvnet 30240 2
ipchains 43528 14


Now I even can not unload x10_core. Another thing:
[***@puma wish-1.6.2]# insmod -f x10_pl.o
x10_pl.o: init_module: Operation not permitted
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters

Is this version issue you mentioned? How do I fix that?
Many thanks,
-Hong


Scott Hiles wrote:


OK...your kernel will compile so you are getting closer. Make sure that you

have a link from of /usr/src/linux to /usr/src/linux-2.4.18-3.



Now go to the directory that you untarred the source code for the x10

drivers and try the following commands:



# make clean

# make



You should end up with x10_plusb.o, x10_pl.o, x10_cm11a.o, and x10_cm17a.o.

If you got this far, then your drivers have been compiled. Now, try loading

them by hand using:



# insmod -f x10_<device>.o



You may get an error that the versions don't match don't worry about it at

this point. You should be able to test that the drivers work on your

machine by running utils/x10attach if needed.



If you got the error that the versions don't match the problem is in

/usr/src/linux/Makefile and I can tell you how to fix the error.



Scott





-----Original Message-----

From: wish-info-***@lists.sourceforge.net

[mailto:wish-info-***@lists.sourceforge.net] On Behalf Of Hong Hsu

Sent: Monday, May 12, 2003 8:26 PM

To: wish-***@lists.sourceforge.net

Subject: [wish-info] Re: compile X10 1.6.2 driver on Redhat

kernel 2.4.18-3





After following steps,

#make mrproper

#make menuconfig

#make dep

#nohup make bzImage &



#tail -f nohup.out message shows:

......

gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o tools/build

tools/build.c -I/usr/src/linux-2.4.18-3/include

objcopy -O binary -R .note -R .comment -S compressed/bvmlinux

compressed/bvmlinux.out

tools/build -b bbootsect bsetup compressed/bvmlinux.out

CURRENT > bzImage Root device is (3, 8) Boot sector 512

bytes. Setup is 4772 bytes. System is 1022 kB

warning: kernel is too big for standalone boot from floppy

make[1]: Leaving directory `/usr/src/linux-2.4.18-3/arch/i386/boot'



May I say building kernel is OK at this point? but install

x10 driver

still got same error message at this stage. Is that valid to

install at this point?



Thanks,

-Hong









-------------------------------------------------------

Enterprise Linux Forum Conference & Expo, June 4-6, 2003,

Santa Clara The only event dedicated to issues related to

Linux enterprise solutions www.enterpriselinuxforum.com



_______________________________________________

wish-info mailing list

wish-***@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/w> ish-info
--
<Linux kernel:>< As a computer I find your faith in technology amusing.
--
<Linux kernel:>< As a computer I find your faith in technology amusing.
Scott Hiles
2003-05-19 20:18:22 UTC
Permalink
I got 2.4.18-3 up and running and was able to compile the drivers. They
worked just fine on my Redhat system. To make it a bit easier, I put
binaries on sourceforge which have been precompiled. This is my first time
creating an RPM so hopefully I got it all right.

Go to the wish.sourceforge.net page and scroll down to the area for
Installing RPMs. Select the "Yes" for 2.4.18-3 and download the rpm file.
To make it easy for you to see the commands and the output you should
expect, I have performed the commands on my machine and captured them below.

[***@crazy tmp]# tail -f /var/log/messages &
[***@crazy tmp]# rpm -i wish-1.6.2-kernel2.4.18-3-noDEVFS.i386.rpm
[***@crazy root]# insmod x10_plusb
Using /lib/modules/2.4.18-3/kernel/drivers/char/x10/x10_plusb.o
May 19 16:12:00 localhost kernel: x10: X10 Transceiver module v1.6.1
(***@sprintmail.com)
May 19 16:12:00 localhost kernel: x10: $Id: x10_core.c,v 1.39 2003/03/06
17:05:06 whiles Exp whiles $
May 19 16:12:00 localhost kernel: x10: $Id: x10_ldisc_plusb.c,v 1.10
2003/02/10 19:33:05 whiles Exp $
May 19 16:12:00 localhost kernel: x10: $Id: x10_xcvr_plusb.c,v 1.10
2003/02/15 02:46:06 whiles Exp whiles $
May 19 16:12:00 localhost kernel: usb.c: registered new driver PowerLincUSB
May 19 16:12:00 localhost kernel: x10: PowerLinc USB successfully probed and
installed
[***@crazy root]# May 19 16:12:02 localhost kernel: x10: PowerLinc USB
Hardware Rev 1.4 found
May 19 16:12:02 localhost kernel: x10: X10 driver successfully loaded
[***@crazy root]# echo 1 > /dev/x10/e11
[***@crazy root]# echo 0 > /dev/x10/e11

The last two lines turned the light on for e11 and then turned it off.

The direct link for downloading the rpm file is:
http://prdownloads.sourceforge.net/wish/wish-1.6.2-kernel2.4.18-3-noDEVFS.i3
86.rpm?download

Scott

-----Original Message-----
From: Hong Hsu [mailto:***@bellatlantic.net]
Sent: Wednesday, May 14, 2003 9:08 PM
To: Scott Hiles
Cc: wish-***@lists.sourceforge.net
Subject: Re: [wish-info] Re: compile X10 1.6.2 driver on Redhat kernel
2.4.18-3



Scott,

Two questions.
1) What the following error means, and how to fix it?
[x10]#mknod /dev/x10/c3 c 120 3
[***@puma wish-1.6.2]#rmmod hid
[***@puma wish-1.6.2]# insmod x10_plusb
[***@puma wish-1.6.2]# x10logd
Error: Unable to open device /dev/x10/log (No such file or directory)

2) When I run simple test:
#echo 1 >/dev/x10/c3

Got system locked up! The message is:
Kernel panic: Aiee, killing interrupt handlers!

I have to reboot it. Am I missing some thing? (I use PowerLincUSB and lamp
module c3 is the only module)
Thanks,
-Hong



Scott Hiles wrote:


You only install the driver called x10_<device>.o. So, for the PowerLinc
USB, you would only install x10_plusb.o. The rest are compiled into the
device driver.

When you install x10_plusb.o, your var/log/messages should now have a
message indicting that the driver was loaded and the version of the X10
transceiver.

Continue with the instructions to remove hid.o (rmmod hid) so that it won't
interfere with the X10 USB drivers. If you have run the script to make your
devices, you should be all set. You should now be able to send commands to
the X10 devices.

If it all works at this point, you have completed the test. You now just
need to install the drivers into your modules directory (which is what
install.sh should be able to do) and create a startup script in
/etc/rc.d/init.d. Look at the example scripts for startup for a way that I
do it on a RedHat System.

Scott

-----Original Message-----
From: Hong Hsu [mailto:***@bellatlantic.net]
Sent: Tuesday, May 13, 2003 11:25 AM
To: Scott Hiles
Cc: wish-***@lists.sourceforge.net
Subject: Re: [wish-info] Re: compile X10 1.6.2 driver on Redhat kernel
2.4.18-3


Scott,

compilation of drivers has no problem. Does order of installing drivers
is matter? Do I need to install all 13 x10_xyz.o drivers as I only use
PowerLincUSB?

I have installed x10_plusb.o and x10_strings.o with no problem. However,
installation of x10_core.o causes Segmentation fault AND tainted others:
[***@puma root]# lsmod
Module Size Used by Tainted: PF
x10_core 22688 1 (initializing)
x10_ldisc_plusb 8192 0 [x10_core]
x10_xcvr_plusb 7456 0 [x10_core x10_ldisc_plusb]
x10_xcvr_pl 7104 0 (unused)
x10_strings 2688 0 [x10_core]
x10_plusb 38464 0 [x10_ldisc_plusb x10_xcvr_plusb
x10_xcvr_pl]
i810_audio 23008 0 (autoclean)
ac97_codec 11936 0 (autoclean) [i810_audio]
soundcore 6692 2 (autoclean) [i810_audio]
NVdriver 1066272 10
nfsd 76192 8 (autoclean)
lockd 56768 1 (autoclean) [nfsd]
sunrpc 75764 1 (autoclean) [nfsd lockd]
autofs 12132 0 (autoclean) (unused)
nvnet 30240 2
ipchains 43528 14


Now I even can not unload x10_core. Another thing:
[***@puma wish-1.6.2]# insmod -f x10_pl.o
x10_pl.o: init_module: Operation not permitted
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters

Is this version issue you mentioned? How do I fix that?
Many thanks,
-Hong


Scott Hiles wrote:


OK...your kernel will compile so you are getting closer. Make sure that you

have a link from of /usr/src/linux to /usr/src/linux-2.4.18-3.



Now go to the directory that you untarred the source code for the x10

drivers and try the following commands:



# make clean

# make



You should end up with x10_plusb.o, x10_pl.o, x10_cm11a.o, and x10_cm17a.o.

If you got this far, then your drivers have been compiled. Now, try loading

them by hand using:



# insmod -f x10_<device>.o



You may get an error that the versions don't match don't worry about it at

this point. You should be able to test that the drivers work on your

machine by running utils/x10attach if needed.



If you got the error that the versions don't match the problem is in

/usr/src/linux/Makefile and I can tell you how to fix the error.



Scott





-----Original Message-----

From: wish-info-***@lists.sourceforge.net

[mailto:wish-info-***@lists.sourceforge.net] On Behalf Of Hong Hsu

Sent: Monday, May 12, 2003 8:26 PM

To: wish-***@lists.sourceforge.net

Subject: [wish-info] Re: compile X10 1.6.2 driver on Redhat

kernel 2.4.18-3





After following steps,

#make mrproper

#make menuconfig

#make dep

#nohup make bzImage &



#tail -f nohup.out message shows:

......

gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o tools/build

tools/build.c -I/usr/src/linux-2.4.18-3/include

objcopy -O binary -R .note -R .comment -S compressed/bvmlinux

compressed/bvmlinux.out

tools/build -b bbootsect bsetup compressed/bvmlinux.out

CURRENT > bzImage Root device is (3, 8) Boot sector 512

bytes. Setup is 4772 bytes. System is 1022 kB

warning: kernel is too big for standalone boot from floppy

make[1]: Leaving directory `/usr/src/linux-2.4.18-3/arch/i386/boot'



May I say building kernel is OK at this point? but install

x10 driver

still got same error message at this stage. Is that valid to

install at this point?



Thanks,

-Hong









-------------------------------------------------------

Enterprise Linux Forum Conference & Expo, June 4-6, 2003,

Santa Clara The only event dedicated to issues related to

Linux enterprise solutions www.enterpriselinuxforum.com



_______________________________________________

wish-info mailing list

wish-***@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/w> ish-info
--
<Linux kernel:>< As a computer I find your faith in technology amusing.
--
<Linux kernel:>< As a computer I find your faith in technology amusing.
Scott Hiles
2003-05-19 20:23:34 UTC
Permalink
One thing I forgot to mention. I took out hid.o from my module directory so
you need to do an "rmmod hid" before you do the insmod step below. I
modified the transcript to include that step.

Scott

-----Original Message-----
From: Scott Hiles [mailto:***@sprintmail.com]
Sent: Monday, May 19, 2003 4:18 PM
To: 'Hong Hsu'
Cc: 'wish-***@lists.sourceforge.net'
Subject: RE: [wish-info] Re: compile X10 1.6.2 driver on Redhat kernel
2.4.18-3


I got 2.4.18-3 up and running and was able to compile the drivers. They
worked just fine on my Redhat system. To make it a bit easier, I put
binaries on sourceforge which have been precompiled. This is my first time
creating an RPM so hopefully I got it all right.

Go to the wish.sourceforge.net page and scroll down to the area for
Installing RPMs. Select the "Yes" for 2.4.18-3 and download the rpm file.
To make it easy for you to see the commands and the output you should
expect, I have performed the commands on my machine and captured them below.

[***@crazy tmp]# tail -f /var/log/messages &
[***@crazy tmp]# rpm -i wish-1.6.2-kernel2.4.18-3-noDEVFS.i386.rpm
[***@crazy tmp]# rmmod hid
[***@crazy root]# insmod x10_plusb
Using /lib/modules/2.4.18-3/kernel/drivers/char/x10/x10_plusb.o
May 19 16:12:00 localhost kernel: x10: X10 Transceiver module v1.6.1
(***@sprintmail.com)
May 19 16:12:00 localhost kernel: x10: $Id: x10_core.c,v 1.39 2003/03/06
17:05:06 whiles Exp whiles $
May 19 16:12:00 localhost kernel: x10: $Id: x10_ldisc_plusb.c,v 1.10
2003/02/10 19:33:05 whiles Exp $
May 19 16:12:00 localhost kernel: x10: $Id: x10_xcvr_plusb.c,v 1.10
2003/02/15 02:46:06 whiles Exp whiles $
May 19 16:12:00 localhost kernel: usb.c: registered new driver PowerLincUSB
May 19 16:12:00 localhost kernel: x10: PowerLinc USB successfully probed and
installed
[***@crazy root]# May 19 16:12:02 localhost kernel: x10: PowerLinc USB
Hardware Rev 1.4 found
May 19 16:12:02 localhost kernel: x10: X10 driver successfully loaded
[***@crazy root]# echo 1 > /dev/x10/e11
[***@crazy root]# echo 0 > /dev/x10/e11

The last two lines turned the light on for e11 and then turned it off.

The direct link for downloading the rpm file is:
http://prdownloads.sourceforge.net/wish/wish-1.6.2-kernel2.4.18-3-noDEVFS.i3
86.rpm?download

Scott

-----Original Message-----
From: Hong Hsu [mailto:***@bellatlantic.net]
Sent: Wednesday, May 14, 2003 9:08 PM
To: Scott Hiles
Cc: wish-***@lists.sourceforge.net
Subject: Re: [wish-info] Re: compile X10 1.6.2 driver on Redhat kernel
2.4.18-3



Scott,

Two questions.
1) What the following error means, and how to fix it?
[x10]#mknod /dev/x10/c3 c 120 3
[***@puma wish-1.6.2]#rmmod hid
[***@puma wish-1.6.2]# insmod x10_plusb
[***@puma wish-1.6.2]# x10logd
Error: Unable to open device /dev/x10/log (No such file or directory)

2) When I run simple test:
#echo 1 >/dev/x10/c3

Got system locked up! The message is:
Kernel panic: Aiee, killing interrupt handlers!

I have to reboot it. Am I missing some thing? (I use PowerLincUSB and lamp
module c3 is the only module)
Thanks,
-Hong



Scott Hiles wrote:


You only install the driver called x10_<device>.o. So, for the PowerLinc
USB, you would only install x10_plusb.o. The rest are compiled into the
device driver.

When you install x10_plusb.o, your var/log/messages should now have a
message indicting that the driver was loaded and the version of the X10
transceiver.

Continue with the instructions to remove hid.o (rmmod hid) so that it won't
interfere with the X10 USB drivers. If you have run the script to make your
devices, you should be all set. You should now be able to send commands to
the X10 devices.

If it all works at this point, you have completed the test. You now just
need to install the drivers into your modules directory (which is what
install.sh should be able to do) and create a startup script in
/etc/rc.d/init.d. Look at the example scripts for startup for a way that I
do it on a RedHat System.

Scott

-----Original Message-----
From: Hong Hsu [mailto:***@bellatlantic.net]
Sent: Tuesday, May 13, 2003 11:25 AM
To: Scott Hiles
Cc: wish-***@lists.sourceforge.net
Subject: Re: [wish-info] Re: compile X10 1.6.2 driver on Redhat kernel
2.4.18-3


Scott,

compilation of drivers has no problem. Does order of installing drivers
is matter? Do I need to install all 13 x10_xyz.o drivers as I only use
PowerLincUSB?

I have installed x10_plusb.o and x10_strings.o with no problem. However,
installation of x10_core.o causes Segmentation fault AND tainted others:
[***@puma root]# lsmod
Module Size Used by Tainted: PF
x10_core 22688 1 (initializing)
x10_ldisc_plusb 8192 0 [x10_core]
x10_xcvr_plusb 7456 0 [x10_core x10_ldisc_plusb]
x10_xcvr_pl 7104 0 (unused)
x10_strings 2688 0 [x10_core]
x10_plusb 38464 0 [x10_ldisc_plusb x10_xcvr_plusb
x10_xcvr_pl]
i810_audio 23008 0 (autoclean)
ac97_codec 11936 0 (autoclean) [i810_audio]
soundcore 6692 2 (autoclean) [i810_audio]
NVdriver 1066272 10
nfsd 76192 8 (autoclean)
lockd 56768 1 (autoclean) [nfsd]
sunrpc 75764 1 (autoclean) [nfsd lockd]
autofs 12132 0 (autoclean) (unused)
nvnet 30240 2
ipchains 43528 14


Now I even can not unload x10_core. Another thing:
[***@puma wish-1.6.2]# insmod -f x10_pl.o
x10_pl.o: init_module: Operation not permitted
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters

Is this version issue you mentioned? How do I fix that?
Many thanks,
-Hong


Scott Hiles wrote:


OK...your kernel will compile so you are getting closer. Make sure that you

have a link from of /usr/src/linux to /usr/src/linux-2.4.18-3.



Now go to the directory that you untarred the source code for the x10

drivers and try the following commands:



# make clean

# make



You should end up with x10_plusb.o, x10_pl.o, x10_cm11a.o, and x10_cm17a.o.

If you got this far, then your drivers have been compiled. Now, try loading

them by hand using:



# insmod -f x10_<device>.o



You may get an error that the versions don't match don't worry about it at

this point. You should be able to test that the drivers work on your

machine by running utils/x10attach if needed.



If you got the error that the versions don't match the problem is in

/usr/src/linux/Makefile and I can tell you how to fix the error.



Scott





-----Original Message-----

From: wish-info-***@lists.sourceforge.net

[mailto:wish-info-***@lists.sourceforge.net] On Behalf Of Hong Hsu

Sent: Monday, May 12, 2003 8:26 PM

To: wish-***@lists.sourceforge.net

Subject: [wish-info] Re: compile X10 1.6.2 driver on Redhat

kernel 2.4.18-3





After following steps,

#make mrproper

#make menuconfig

#make dep

#nohup make bzImage &



#tail -f nohup.out message shows:

......

gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o tools/build

tools/build.c -I/usr/src/linux-2.4.18-3/include

objcopy -O binary -R .note -R .comment -S compressed/bvmlinux

compressed/bvmlinux.out

tools/build -b bbootsect bsetup compressed/bvmlinux.out

CURRENT > bzImage Root device is (3, 8) Boot sector 512

bytes. Setup is 4772 bytes. System is 1022 kB

warning: kernel is too big for standalone boot from floppy

make[1]: Leaving directory `/usr/src/linux-2.4.18-3/arch/i386/boot'



May I say building kernel is OK at this point? but install

x10 driver

still got same error message at this stage. Is that valid to

install at this point?



Thanks,

-Hong









-------------------------------------------------------

Enterprise Linux Forum Conference & Expo, June 4-6, 2003,

Santa Clara The only event dedicated to issues related to

Linux enterprise solutions www.enterpriselinuxforum.com



_______________________________________________

wish-info mailing list

wish-***@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/w> ish-info
--
<Linux kernel:>< As a computer I find your faith in technology amusing.
--
<Linux kernel:>< As a computer I find your faith in technology amusing.
Hong Hsu
2003-05-20 04:09:35 UTC
Permalink
Scott,

I appreciate all you have done.

Follow you two mails, I also remove
/lib/modules/2.4.18-3/kernel/drivers/usb/hid.o. This time it doesn't
taint my kernel. But my x10 lamp module didn't response to on/off
signal. Here are some logs:

[***@puma root]# tail -f /var/log/messages
May 19 23:30:50 puma insmod: insmod: insmod
/lib/modules/2.4.18-3/kernel/drivers/usb/hid.o failed
May 19 23:30:50 puma insmod: insmod: insmod hid failed
May 19 23:30:50 puma /etc/hotplug/usb.agent: ... can't load module hid
May 19 23:30:50 puma /etc/hotplug/usb.agent: missing kernel or user mode
driver hid
May 19 23:30:50 puma kernel: x10: X10 Transceiver module v1.6.1
(***@sprintmail.com)
May 19 23:30:50 puma kernel: x10: $Id: x10_core.c,v 1.39 2003/03/06
17:05:06 whiles Exp whiles $
May 19 23:30:50 puma kernel: x10: $Id: x10_ldisc_plusb.c,v 1.10
2003/02/10 19:33:05 whiles Exp $
May 19 23:30:50 puma kernel: x10: $Id: x10_xcvr_plusb.c,v 1.10
2003/02/15 02:46:06 whiles Exp whiles $
May 19 23:30:50 puma kernel: usb.c: registered new driver PowerLincUSB
May 19 23:30:50 puma kernel: x10: PowerLinc USB successfully probed and
installed
May 19 23:32:33 puma kernel: x10: PowerLinc USB Hardware error getting
Version number
May 19 23:32:33 puma kernel: x10: X10 driver successfully loaded

parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
May 19 23:34:49 puma kernel: parport0: irq 7 detected


using x10logd, I got following:
May 19 23:43:38 puma T C ON
May 19 23:44:31 puma T C ALL_LIGHTS_ON
May 19 23:45:00 puma T C OFF
May 19 23:45:25 puma T C ALL_LIGHTS_OFF
May 19 23:45:53 puma T C1
May 19 23:45:53 puma T C ON

It seems ok. And #cat /dev/x10/c reports following:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
C: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
C: 100 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000

I also test PowerLincUSB on Windows XP, it works fine without any
problem. The lamp module, X10 LM465, can on/off and dim.

I wish I know how to find a way to solve the issue. Thanks a lot,
-Hong
Post by Scott Hiles
One thing I forgot to mention. I took out hid.o from my module
directory so you need to do an "rmmod hid" before you do the insmod
step below. I modified the transcript to include that step.
Scott
Scott Hiles
2003-05-20 13:46:50 UTC
Permalink
Your problem occurs in these lines:

May 19 23:32:33 puma kernel: x10: PowerLinc USB Hardware error getting
Version number
May 19 23:32:33 puma kernel: x10: X10 driver successfully loaded

This means that the driver loaded but couldn't get a response from the USB
hardware. I had this same problem the first time I loaded the drivers under
2.4.18-3. I unloaded the drivers and reloaded them and it started working
correctly.

So, try booting the system in Linux again, look in the /var/log/messages and
see if you have the error saying it had an error getting the hardware
version. If it does, then type "rmmod x10_plusb". Then type "insmod
x10_plusb". Look in the /var/log/messages again and see if you have the
error. It will successfully load and look similar to what I sent earlier.

You are much closer to getting this going. 2.4.18-3 is a fairly old kernel.
Consider going to Redhat and getting the 2.4.18-24.7.x rpm. You will find
the USB support to be much better.

Scott

-----Original Message-----
From: Hong Hsu [mailto:***@bellatlantic.net]
Sent: Tuesday, May 20, 2003 12:10 AM
To: Scott Hiles
Cc: wish-***@lists.sourceforge.net
Subject: Re: FW: [wish-info] Re: compile X10 1.6.2 driver on Redhat kernel
2.4.18-3


Scott,

I appreciate all you have done.

Follow you two mails, I also remove
/lib/modules/2.4.18-3/kernel/drivers/usb/hid.o. This time it doesn't taint
my kernel. But my x10 lamp module didn't response to on/off signal. Here
are some logs:

[***@puma root]# tail -f /var/log/messages
May 19 23:30:50 puma insmod: insmod: insmod
/lib/modules/2.4.18-3/kernel/drivers/usb/hid.o failed
May 19 23:30:50 puma insmod: insmod: insmod hid failed
May 19 23:30:50 puma /etc/hotplug/usb.agent: ... can't load module hid
May 19 23:30:50 puma /etc/hotplug/usb.agent: missing kernel or user mode
driver hid
May 19 23:30:50 puma kernel: x10: X10 Transceiver module v1.6.1
(***@sprintmail.com)
May 19 23:30:50 puma kernel: x10: $Id: x10_core.c,v 1.39 2003/03/06 17:05:06
whiles Exp whiles $
May 19 23:30:50 puma kernel: x10: $Id: x10_ldisc_plusb.c,v 1.10 2003/02/10
19:33:05 whiles Exp $
May 19 23:30:50 puma kernel: x10: $Id: x10_xcvr_plusb.c,v 1.10 2003/02/15
02:46:06 whiles Exp whiles $
May 19 23:30:50 puma kernel: usb.c: registered new driver PowerLincUSB
May 19 23:30:50 puma kernel: x10: PowerLinc USB successfully probed and
installed
May 19 23:32:33 puma kernel: x10: PowerLinc USB Hardware error getting
Version number
May 19 23:32:33 puma kernel: x10: X10 driver successfully loaded

parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
May 19 23:34:49 puma kernel: parport0: irq 7 detected


using x10logd, I got following:
May 19 23:43:38 puma T C ON
May 19 23:44:31 puma T C ALL_LIGHTS_ON
May 19 23:45:00 puma T C OFF
May 19 23:45:25 puma T C ALL_LIGHTS_OFF
May 19 23:45:53 puma T C1
May 19 23:45:53 puma T C ON

It seems ok. And #cat /dev/x10/c reports following:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
C: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
C: 100 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000

I also test PowerLincUSB on Windows XP, it works fine without any problem.
The lamp module, X10 LM465, can on/off and dim.

I wish I know how to find a way to solve the issue. Thanks a lot,
-Hong



Scott Hiles wrote:


One thing I forgot to mention. I took out hid.o from my module directory so
you need to do an "rmmod hid" before you do the insmod step below. I
modified the transcript to include that step.

Scott
Hong Hsu
2003-05-21 16:08:38 UTC
Permalink
Scott,

I rebooted my system, and got same error as no response from USB
hardware. Reboot again. same error. Then #rmmod and #insmod, that
didn't solve the problem either. I noticed every time the system boot
when PowerLincUSB was plugged in, or plug in the PowerLincUSB when the
system is up, the x10_plusb will be loaded automatically. Is it the
issue or devfs setting causes the problem.

My system uses integrated LAN card and GeForce 2 GPU which do not have
newer version of driver for newer Linux kernel from nVIDIA.com. So I
have to wait for a while.
-Hong
Post by Hong Hsu
May 19 23:32:33 puma kernel: x10: PowerLinc USB Hardware error getting
Version number
May 19 23:32:33 puma kernel: x10: X10 driver successfully loaded
This means that the driver loaded but couldn't get a response from the
USB hardware. I had this same problem the first time I loaded the
drivers under 2.4.18-3. I unloaded the drivers and reloaded them and
it started working correctly.
So, try booting the system in Linux again, look in the
/var/log/messages and see if you have the error saying it had an error
getting the hardware version. If it does, then type "rmmod
x10_plusb". Then type "insmod x10_plusb". Look in the
/var/log/messages again and see if you have the error. It will
successfully load and look similar to what I sent earlier.
Scott Hiles
2003-05-21 18:08:20 UTC
Permalink
No, don't reboot the system each time. This appears to be what is causing
the confusion on my system. When I reboot under 2.4.18-3, the USB bus seems
to have problems recognizing the USB device on the first try. Leave the
system up and running and do the rmmod then the insmod a couple of times.
That cleared up the problem for my system.

Are you running DEVFS? The driver that I put out there for you doesn't have
DEVFS compiled into it. If you are running DEVFS I will need to build a
different set of objects for you.

Scott

-----Original Message-----
From: Hong Hsu [mailto:***@bellatlantic.net]
Sent: Wednesday, May 21, 2003 12:09 PM
To: Scott Hiles
Cc: wish-***@lists.sourceforge.net
Subject: Re: FW: [wish-info] Re: compile X10 1.6.2 driver on Redhat kernel
2.4.18-3


Scott,

I rebooted my system, and got same error as no response from USB
hardware. Reboot again. same error. Then #rmmod and #insmod, that
didn't solve the problem either. I noticed every time the system boot when
PowerLincUSB was plugged in, or plug in the PowerLincUSB when the system is
up, the x10_plusb will be loaded automatically. Is it the issue or devfs
setting causes the problem.

My system uses integrated LAN card and GeForce 2 GPU which do not have newer
version of driver for newer Linux kernel from nVIDIA.com. So I have to wait
for a while.
-Hong


Scott Hiles wrote:


Your problem occurs in these lines:

May 19 23:32:33 puma kernel: x10: PowerLinc USB Hardware error getting
Version number
May 19 23:32:33 puma kernel: x10: X10 driver successfully loaded

This means that the driver loaded but couldn't get a response from the USB
hardware. I had this same problem the first time I loaded the drivers under
2.4.18-3. I unloaded the drivers and reloaded them and it started working
correctly.

So, try booting the system in Linux again, look in the /var/log/messages and
see if you have the error saying it had an error getting the hardware
version. If it does, then type "rmmod x10_plusb". Then type "insmod
x10_plusb". Look in the /var/log/messages again and see if you have the
error. It will successfully load and look similar to what I sent earlier.
Hong Hsu
2003-05-21 19:41:18 UTC
Permalink
My system may be running the DEVFS. Do you know how to verify that?

Plug in the PowerLincUSB when the system is on, /var/log/messages shows
May 21 15:27:43 puma kernel: hub.c: USB new device connect on bus1/2,
assigned device number 4
May 21 15:27:43 puma kernel: x10: PowerLinc USB successfully probed and
installed
May 21 15:27:46 puma /etc/hotplug/usb.agent: Setup hid x10_plusb for USB
product 10bf/1/400
May 21 15:27:46 puma insmod: insmod:
/lib/modules/2.4.18-3/kernel/drivers/usb/hid.o: No such file or directory
May 21 15:27:46 puma insmod: insmod: insmod
/lib/modules/2.4.18-3/kernel/drivers/usb/hid.o failed
May 21 15:27:46 puma insmod: insmod: insmod hid failed
May 21 15:27:46 puma /etc/hotplug/usb.agent: ... can't load module hid
May 21 15:27:46 puma /etc/hotplug/usb.agent: missing kernel or user mode
driver hid
......

-Hong
Post by Scott Hiles
No, don't reboot the system each time. This appears to be what is
causing the confusion on my system. When I reboot under 2.4.18-3, the
USB bus seems to have problems recognizing the USB device on the first
try. Leave the system up and running and do the rmmod then the insmod
a couple of times. That cleared up the problem for my system.
Are you running DEVFS? The driver that I put out there for you
doesn't have DEVFS compiled into it. If you are running DEVFS I will
need to build a different set of objects for you.
Scott
Loading...