Hi,

Remember the special modes. You could configure the "loopback" mode of the device using "rtcanconfig -c loopback rtcan0".

But the virtual device installs on rtcan0 Where will I find the loaded dongle? rtcan1?

Then I presume I will send a message on 1 and then see it appear on the rtcanrecv rtcan1 ?

If things are a bit slow on my side its because I am rushing around doing other mandatory things. Only reason I am busy with this as well at the moment is because I don;t want to lose the opportunity of having you all at your desks :)

Thanks, "ich melde mich" soon. :)


Roland.


Wolfgang.


Roland



On 3/2/07, roland Tollenaar <[EMAIL PROTECTED]> wrote:
Hi,

My situation is slightly different. The modules don;t get loaded for
some or other reason (not sure why because I do have parport support
<M> selected in the kernel config.

My BIOS settings said ECP instead of EPP ( I still don;t know the
difference) I set it to EPP and the driver seems to load with modprobe
now.

Interestingly enough before I changed the BIOS I did try

modprobe xeno_can_peak_dng type=ecp io=0x378 irq=7

but it tells me that ecp is an invalid argument? Why is that?


Kind regards,

Roland


On 3/2/07, Markus Franke <[EMAIL PROTECTED]> wrote:
> roland Tollenaar wrote:
> > You mean this must be run as a boot option? Sorry I am not familiar
> > with the term kernel commandline.
>
> Yes, I mean boot option.
>
> >
> > Sounds like its worth a try.
> >
> > Lp and parport_pc are not loaded.
>
> In my case it was the problem that parport_pc and lp were loaded during
> system boot. When I removed these modules in order to load my parport
> module, the parallelport was always switched off by linux and it was not
> possible to activate it again.
>
> >
> > Thanks
> >
> > Roland
> >
> >> the kernel commandline.
> >> Maybe this can also help you.
> >>
> >> Regards,
> >> Markus Franke
> >>
> >> roland Tollenaar wrote:
> >> >> >
> >> >> > FATAL: Error inserting xeno_can_peak_dng (xeno_can_peak_dng.ko): No
> >> >> such
> >> >> > device
> >> >>
> >> >> Is there som additional kernel output visible via "dmesg"?
> >> >
> >> >
> >> > Yes:
> >> >
> >> > SCSI device sdb: 3963904 512-byte hdwr sectors (2030 MB)
> >> > sdb: Write Protect is off
> >> > sdb: Mode Sense: 43 00 00 00
> >> > sdb: assuming drive cache: write through
> >> > SCSI device sdb: 3963904 512-byte hdwr sectors (2030 MB)
> >> > sdb: Write Protect is off
> >> > sdb: Mode Sense: 43 00 00 00
> >> > sdb: assuming drive cache: write through
> >> > sdb: sdb1
> >> > sd 3:0:0:0: Attached scsi removable disk sdb
> >> > usb-storage: device scan complete
> >> > ERROR! No SJA1000 device found!
> >> > ERROR while trying to register SJA1000 device -19!
> >> > Init failed with -19
> >> >
> >> > are the final lines.
> >> >
> >> >
> >> >>
> >> >> How do you have configured the parport in the kernel? Are there
> >> modules
> >> >> loaded (check /proc/modules)? Retry after removing lp and parport_pc:
> >> >
> >> >
> >> > Have looked can't see any. Have attached the output of /proc/modules
> >> >
> >> >
> >> >>
> >> >>    $ rmmod lp
> >> >>    $ rmmod parport_pc
> >> >
> >> >
> >> > I get a message that it cannot find these modules in /proc/modules
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >>
> >> >> Wolfgang.
> >> >>
> >> >
> >> >
> >> ------------------------------------------------------------------------
> >> >
> >> > _______________________________________________
> >> > Xenomai-help mailing list
> >> > Xenomai-help@gna.org
> >> > https://mail.gna.org/listinfo/xenomai-help
> >>
> >> --
> >> Nichts ist so praktisch wie eine gute Theorie!
> >>
> >
>
> --
> Nichts ist so praktisch wie eine gute Theorie!
>
>


_______________________________________________
Xenomai-help mailing list
Xenomai-help@gna.org
https://mail.gna.org/listinfo/xenomai-help





_______________________________________________
Xenomai-help mailing list
Xenomai-help@gna.org
https://mail.gna.org/listinfo/xenomai-help

Reply via email to