Hi!
It's not easy to determine where your problem lies form your description,
but I'll try anyway.
If you are using the irda-utils you might find the program findchip.
If you type: findchip -v
it will tell you what chip your computer is using to utilize IR. At least
that worked with my notebook, and the FIR chip I have.
Otherwise you need to find another way to find out which IR device you are
using.
You must try to load the modules for your device with:
modprobe smc-ircc (where smc-ircc is the module for MY
chip, which might be different for you)
To find out if SuSE provides modules for your chip, you can change to:
/lib/modules/`uname -r`/kernel/drivers/net/irda
that's where the modules for irda devices reside.
If you have successfully loaded a module for your device you then need to
do this:
echo 1 > /proc/sys/net/irda/discovery
then:
ifconfig irda0
and: irattach irda0
then you can check your traffic on the irda interface with: irdadump irda0
I hope this helps.
I spent almost a week trying to get mine to work, so don't give up, it may
still work yet.
Good luck,
.peter
On Fri, 4 Jan 2002, Ruedi Hofer wrote:
>
> Hi
>
> I have a problem sync'ing my palm m505 with linux 2.4.14 kernel.
> From previous answers to this list it seems as if I was missing the
> irobex kernel module. Where can I get that from?
> Since it's not included in the 2.4.14 kernel, do I have to change to
> a later kernel?
>
> I'm using irda-0.9.13-42 from Suse 7.2.
>
> --
>
> Cheers, Ruedi Hofer (http://ruedihofer.come.to)
>
> _______________________________________________
> Linux-IrDA mailing list - [EMAIL PROTECTED]
> http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
>
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
