All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@domain.hid>
To: roland Tollenaar <rolandtollenaar@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] problems installing peak CAN dongle
Date: Fri, 02 Mar 2007 10:36:29 +0100	[thread overview]
Message-ID: <45E7F01D.2080304@domain.hid> (raw)
In-Reply-To: <bc4264770703020123s28450a37n60bb1e49798f32b8@domain.hid>

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.

OK ==> the device cannot be accessed. Either the I/O address "0x378" and 
partport type "epp" is incorrect (you did not answer my question on 
that) or the parallel port is not operational (power off, etc.).
Please check what is actually selected in the BIOS of your system.

>> 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

Try "modporbe parport". If the module does not exists, configure and 
rebuild your kernel with parport support.

In the meantime I'm going to apply the fix Jan mentioned.

Wolfgang.



  reply	other threads:[~2007-03-02  9:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02  8:23 [Xenomai-help] problems installing peak CAN dongle roland Tollenaar
2007-03-02  8:40 ` Jan Kiszka
2007-03-02  8:54   ` Wolfgang Grandegger
2007-03-02  8:55   ` Roland Tollenaar
2007-03-04 10:01   ` Paul
2007-03-02  8:47 ` Wolfgang Grandegger
2007-03-02  9:23   ` roland Tollenaar
2007-03-02  9:36     ` Wolfgang Grandegger [this message]
2007-03-02  9:54       ` roland Tollenaar
2007-03-02  9:54     ` Markus Franke
2007-03-02 10:22       ` Wolfgang Grandegger
2007-03-02 10:27         ` Markus Franke
2007-03-02 10:33           ` roland Tollenaar
2007-03-02 10:31         ` roland Tollenaar
2007-03-02 10:28       ` roland Tollenaar
2007-03-02 10:42         ` Markus Franke
2007-03-02 10:50           ` roland Tollenaar
2007-03-02 10:52             ` roland Tollenaar
2007-03-02 11:21               ` Wolfgang Grandegger
2007-03-02 11:39                 ` Roland Tollenaar
2007-03-02 13:19                   ` Wolfgang Grandegger
2007-03-02 13:37                     ` Roland Tollenaar
2007-03-02 14:41                       ` Wolfgang Grandegger
2007-03-02 14:46                         ` Wolfgang Grandegger
2007-03-02 14:06                     ` Roland Tollenaar
2007-03-02 11:17             ` Wolfgang Grandegger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45E7F01D.2080304@domain.hid \
    --to=wg@domain.hid \
    --cc=rolandtollenaar@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.