[Xenomai-help] CAN driver

[Xenomai-help] CAN driver

[Roland Tollenaar]

Hi list,

does anyone have, or can anyone direct met to a project or code-snippet 
that shows how the CAN driver in the xenomai patch is used in an 
application? If not that any documentation that gives and explains what 
calls it responds to.

Would help a lot.

Thanks in advance.

Roland

Re: [Xenomai-help] CAN driver

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

Roland Tollenaar wrote:
> Hi list,
> 
> does anyone have, or can anyone direct met to a project or code-snippet
> that shows how the CAN driver in the xenomai patch is used in an
> application? If not that any documentation that gives and explains what
> calls it responds to.

Check src/utils/can/ on some tools that can also serve as nice examples.
But maybe we should also add even simpler demo code to the examples
repository. Just takes someone to write them...

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

Jan Kiszka wrote:
> Roland Tollenaar wrote:
>> Hi list,
>>
>> does anyone have, or can anyone direct met to a project or code-snippet
>> that shows how the CAN driver in the xenomai patch is used in an
>> application? If not that any documentation that gives and explains what
>> calls it responds to.
> 
> Check src/utils/can/ on some tools that can also serve as nice examples.
> But maybe we should also add even simpler demo code to the examples
> repository. Just takes someone to write them...

The utility programs rtcanconfig, rtcansend and rtcanrcv in 
src/utils/can already demonstrate most of RT-Socket-CAN's functionality 
including filter definition and error handling. I do not see a need for 
simpler examples. I have attached a patch for a nice program to measure 
the round trip time of CAN messages. It contrast to the other CAN 
utility programs, it uses the POSIX-API and works as-is for Socket-CAN 
as well. Jan, any objections to include it? If yes, I'm going to provide 
a README.

BTW: some time ago I provided a patch to make the CAN utility programs 
part of the Doxygen documentation. IIRC, we said it's nice to have 
hyperlinked examples in general.

Wolfgang.


[-- Attachment #2: xenomai-rtcan-rtt.patch --]
[-- Type: text/x-patch, Size: 13646 bytes --]

+ diff -u xenomai/examples/rtdm/profiles/can/Makefile.RTT xenomai/examples/rtdm/profiles/can/Makefile
--- xenomai/examples/rtdm/profiles/can/Makefile.RTT	2007-02-21 13:10:34.000000000 +0100
+++ xenomai/examples/rtdm/profiles/can/Makefile	2007-02-21 13:06:19.000000000 +0100
@@ -0,0 +1,82 @@
+###### CONFIGURATION ######
+
+### List of applications to be build
+APPLICATIONS = rtcan_rtt
+
+### Note: to override the search path for the xeno-config script, use "make XENO=..."
+
+
+### List of modules to be build
+MODULES =
+
+### Default to sources of currently running kernel
+KSRC ?= /lib/modules/$(shell uname -r)/build
+
+### Note: to override the kernel source path, use "make KSRC=..."
+
+
+
+###### USER SPACE BUILD (no change required normally) ######
+ifneq ($(APPLICATIONS),)
+
+XENOCONFIG=$(shell PATH=$(XENO):$(XENO)/bin:$(PATH) which xeno-config 2>/dev/null)
+
+### Sanity check
+ifeq ($(XENOCONFIG),)
+all::
+	@echo ">>> Invoke make like this: \"make XENO=/path/to/xeno-config\" <<<"
+	@echo
+endif
+
+
+CC=$(shell $(XENOCONFIG) --cc)
+
+CFLAGS=$(shell $(XENOCONFIG) --posix-cflags) $(MY_CFLAGS)
+
+LDFLAGS=$(shell $(XENOCONFIG) --posix-ldflags) $(MY_LDFLAGS) -lrtdm
+
+all:: $(APPLICATIONS)
+
+clean::
+	$(RM) $(APPLICATIONS) *.o
+
+endif
+
+
+
+###### KERNEL MODULE BUILD (no change required normally) ######
+ifneq ($(MODULES),)
+
+OBJS     := ${patsubst %, %.o, $(MODULES)}
+CLEANMOD := ${patsubst %, .%*, $(MODULES)}
+PWD      := $(shell if [ "$$PWD" != "" ]; then echo $$PWD; else pwd; fi)
+
+### Kernel 2.6
+ifeq ($(findstring 2.6,$(KSRC)),2.6)
+
+obj-m        := $(OBJS)
+EXTRA_CFLAGS := -I$(KSRC)/include/xenomai -I$(KSRC)/include/xenomai/posix $(ADD_CFLAGS)
+
+all::
+	$(MAKE) -C $(KSRC) SUBDIRS=$(PWD) modules
+
+### Kernel 2.4
+else
+
+ARCH    ?= $(shell uname -i)
+INCLUDE := -I$(KSRC)/include/xenomai -I$(KSRC)/include/xenomai/compat -I$(KSRC)/include/xenomai/posix
+CFLAGS  += $(shell $(MAKE) -s -C $(KSRC) CC=$(CC) ARCH=$(ARCH) SUBDIRS=$(PWD) modules) $(INCLUDE)
+
+all:: $(OBJS)
+
+endif
+
+## Target for capturing 2.4 module CFLAGS
+modules:
+	@echo "$(CFLAGS)"
+
+clean::
+	$(RM) $(CLEANMOD) *.cmd *.o *.ko *.mod.c Module*.symvers
+	$(RM) -R .tmp*
+
+endif
+ diff -u xenomai/examples/rtdm/profiles/can/rtcan_rtt.c.RTT xenomai/examples/rtdm/profiles/can/rtcan_rtt.c
--- xenomai/examples/rtdm/profiles/can/rtcan_rtt.c.RTT	2007-02-21 13:10:43.000000000 +0100
+++ xenomai/examples/rtdm/profiles/can/rtcan_rtt.c	2007-02-21 13:04:44.000000000 +0100
@@ -0,0 +1,402 @@
+/*
+ * Round-Trip-Time Test - sends and receives messages and measures the
+ *                        time in between.
+ *
+ * Copyright (C) 2006 Wolfgang Grandegger <wg@domain.hid>
+ *
+ * Based on RTnet's examples/xenomai/posix/rtt-sender.c.
+ *
+ * Copyright (C) 2002 Ulrich Marx <marx@domain.hid>
+ *               2002 Marc Kleine-Budde <kleine-budde@domain.hid>
+ *               2006 Jan Kiszka <jan.kiszka@domain.hid>
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either version 2 of the License, or
+ * (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+ */
+
+#include <errno.h>
+#include <mqueue.h>
+#include <signal.h>
+#include <pthread.h>
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#include <unistd.h>
+#include <limits.h>
+#include <getopt.h>
+#include <netinet/in.h>
+#include <sys/mman.h>
+
+#include <rtdm/rtcan.h>
+
+static unsigned int cycle = 10000; /* 10 ms */
+static can_id_t can_id = 0x1;
+
+static pthread_t txthread, rxthread;
+static int txsock, rxsock;
+static mqd_t mq;
+static int txcount, rxcount;
+static int overruns;
+static int repeater;
+
+struct rtt_stat {
+    long long rtt;
+    long long rtt_min;
+    long long rtt_max;
+    long long rtt_sum;
+    long long rtt_sum_last;
+    int counts_per_sec;
+};
+
+static void print_usage(char *prg)
+{
+    fprintf(stderr,
+	    "Usage: %s  [Options] <tx-can-interface> <rx-can-interface>\n"
+	    "Options:\n"
+	    " -h, --help     This help\n"
+	    " -r, --repeater Repeater, send back received messages\n"
+	    " -i, --id=ID    CAN Identifier (default = 0x1)\n"
+	    " -c, --cycle    Cycle time in us (default = 10000us)\n",
+	    prg);
+}
+
+void *transmitter(void *arg)
+{
+    struct sched_param  param = { .sched_priority = 80 };
+    struct timespec next_period;
+    struct timespec time;
+    struct can_frame frame;
+    long long *rtt_time = (long long *)&frame.data;
+
+    /* Pre-fill CAN frame */
+    frame.can_id = can_id;
+    frame.can_dlc = sizeof(*rtt_time);
+
+    pthread_setschedparam(pthread_self(), SCHED_FIFO, &param);
+
+    clock_gettime(CLOCK_MONOTONIC, &next_period);
+
+    while(1) {
+        next_period.tv_nsec += cycle * 1000;
+        if (next_period.tv_nsec >= 1000000000) {
+            next_period.tv_nsec = 0;
+            next_period.tv_sec++;
+        }
+
+        clock_nanosleep(CLOCK_MONOTONIC, TIMER_ABSTIME, &next_period, NULL);
+
+	if (rxcount != txcount) {
+	    overruns++;
+	    continue;
+	}
+
+        clock_gettime(CLOCK_MONOTONIC, &time);
+	*rtt_time = time.tv_sec * 1000000000LL + time.tv_nsec;
+
+        /* Transmit the message containing the local time */
+	if (send(txsock, (void *)&frame, sizeof(can_frame_t), 0) < 0) {
+            if (errno == EBADF)
+                printf("terminating transmitter thread\n");
+            else
+                perror("send failed");
+            return NULL;
+        }
+	txcount++;
+    }
+}
+
+
+void *receiver(void *arg)
+{
+    struct sched_param param = { .sched_priority = 82 };
+    struct timespec time;
+    struct can_frame frame;
+    long long *rtt_time = (long long *)frame.data;
+    struct rtt_stat rtt_stat = {0, 1000000000000000000LL, -1000000000000000000LL,
+				0, 0, 0};
+    pthread_setschedparam(pthread_self(), SCHED_FIFO, &param);
+
+    rtt_stat.counts_per_sec = 1000000 / cycle;
+
+    while (1) {
+	if (recv(rxsock, (void *)&frame, sizeof(can_frame_t), 0) < 0) {
+	    if (errno == EBADF)
+                printf("terminating receiver thread\n");
+            else
+                perror("recv failed");
+            return NULL;
+        }
+	if (repeater) {
+	    /* Transmit the message back as is */
+	    if (send(txsock, (void *)&frame, sizeof(can_frame_t), 0) < 0) {
+		if (errno == EBADF)
+		    printf("terminating transmitter thread\n");
+		else
+		    perror("send failed");
+		return NULL;
+	    }
+	    txcount++;
+	} else {
+	    clock_gettime(CLOCK_MONOTONIC, &time);
+	    if (rxcount > 0) {
+		rtt_stat.rtt = (time.tv_sec * 1000000000LL +
+				time.tv_nsec - *rtt_time);
+		rtt_stat.rtt_sum += rtt_stat.rtt;
+		if (rtt_stat.rtt <  rtt_stat.rtt_min)
+		    rtt_stat.rtt_min = rtt_stat.rtt;
+		if (rtt_stat.rtt > rtt_stat.rtt_max)
+		    rtt_stat.rtt_max = rtt_stat.rtt;
+	    }
+	}
+	rxcount++;
+
+	if ((rxcount % rtt_stat.counts_per_sec) == 0) {
+	    mq_send(mq, (char *)&rtt_stat, sizeof(rtt_stat), 0);
+	    rtt_stat.rtt_sum_last = rtt_stat.rtt_sum;
+	}
+    }
+}
+
+void catch_signal(int sig)
+{
+    mq_close(mq);
+}
+
+
+int main(int argc, char *argv[])
+{
+    struct sched_param param = { .sched_priority = 1 };
+    pthread_attr_t thattr;
+    struct mq_attr mqattr;
+    struct sockaddr_can rxaddr, txaddr;
+    struct can_filter rxfilter[1];
+    struct rtt_stat rtt_stat;
+    char mqname[32];
+    char *txdev, *rxdev;
+    struct ifreq ifr;
+    int ret, opt;
+
+    struct option long_options[] = {
+	{ "id", required_argument, 0, 'i'},
+	{ "cycle", required_argument, 0, 'c'},
+	{ "repeater", required_argument, 0, 'r'},
+	{ "help", no_argument, 0, 'h'},
+	{ 0, 0, 0, 0},
+    };
+
+    while ((opt = getopt_long(argc, argv, "hri:c:",
+			      long_options, NULL)) != -1) {
+	switch (opt) {
+	case 'c':
+	    cycle = atoi(optarg);
+	    break;
+
+	case 'i':
+	    can_id = strtoul(optarg, NULL, 0);
+	    break;
+
+	case 'r':
+	    repeater = 1;
+	    break;
+
+	default:
+	    fprintf(stderr, "Unknown option %c\n", opt);
+	case 'h':
+	    print_usage(argv[0]);
+	    exit(-1);
+	}
+    }
+
+    printf("%d %d\n", optind, argc);
+    if (optind + 2 != argc) {
+	print_usage(argv[0]);
+	exit(0);
+    }
+
+    txdev = argv[optind];
+    rxdev = argv[optind + 1];
+
+    /* Create and configure RX socket */
+    if ((rxsock = socket(PF_CAN, SOCK_RAW, 0)) < 0) {
+	perror("RX socket failed");
+	return -1;
+    }
+
+    strncpy(ifr.ifr_name, rxdev, IFNAMSIZ);
+    printf("RX rxsock=%d, ifr_name=%s\n", rxsock, ifr.ifr_name);
+
+    if (ioctl(rxsock, SIOCGIFINDEX, &ifr) < 0) {
+	perror("RX ioctl SIOCGIFINDEX failed");
+	goto failure1;
+    }
+
+    /* We only want to receive our own messages */
+    rxfilter[0].can_id = can_id;
+    rxfilter[0].can_mask = 0x3ff;
+    if (setsockopt(rxsock, SOL_CAN_RAW, CAN_RAW_FILTER,
+		   &rxfilter, sizeof(struct can_filter)) < 0) {
+	perror("RX setsockopt CAN_RAW_FILTER failed");
+	goto failure1;
+    }
+    memset(&rxaddr, 0, sizeof(rxaddr));
+    rxaddr.can_ifindex = ifr.ifr_ifindex;
+    rxaddr.can_family = AF_CAN;
+    if (bind(rxsock, (struct sockaddr *)&rxaddr, sizeof(rxaddr)) < 0) {
+	perror("RX bind failed\n");
+	goto failure1;
+    }
+
+    /* Create and configure TX socket */
+
+    if (strcmp(rxdev, txdev) == 0) {
+	txsock = rxsock;
+    } else {
+	if ((txsock = socket(PF_CAN, SOCK_RAW, 0)) < 0) {
+	    perror("TX socket failed");
+	    goto failure1;
+	}
+
+	strncpy(ifr.ifr_name, txdev, IFNAMSIZ);
+	printf("TX txsock=%d, ifr_name=%s\n", txsock, ifr.ifr_name);
+
+	if (ioctl(txsock, SIOCGIFINDEX, &ifr) < 0) {
+	    perror("TX ioctl SIOCGIFINDEX failed");
+	    goto failure2;
+	}
+
+	/* Suppress definiton of a default receive filter list */
+	if (setsockopt(txsock, SOL_CAN_RAW, CAN_RAW_FILTER, NULL, 0) < 0) {
+	    perror("TX setsockopt CAN_RAW_FILTER failed");
+	    goto failure2;
+	}
+
+	memset(&txaddr, 0, sizeof(txaddr));
+	txaddr.can_ifindex = ifr.ifr_ifindex;
+	txaddr.can_family = AF_CAN;
+
+	if (bind(txsock, (struct sockaddr *)&txaddr, sizeof(txaddr)) < 0) {
+		perror("TX bind failed\n");
+		goto failure2;
+	}
+    }
+
+    signal(SIGTERM, catch_signal);
+    signal(SIGINT, catch_signal);
+    signal(SIGHUP, catch_signal);
+    mlockall(MCL_CURRENT|MCL_FUTURE);
+
+    printf("Round-Trip-Time test %s -> %s with CAN ID 0x%x\n",
+	   argv[optind], argv[optind + 1], can_id);
+    printf("Cycle time: %d us\n", cycle);
+    printf("All RTT timing figures are in us.\n");
+
+    /* Create statistics message queue */
+    snprintf(mqname, sizeof(mqname), "/rtcan_rtt-%d", getpid());
+    mqattr.mq_flags   = 0;
+    mqattr.mq_maxmsg  = 100;
+    mqattr.mq_msgsize = sizeof(struct rtt_stat);
+    mq = mq_open(mqname, O_RDWR | O_CREAT | O_EXCL, 0600, &mqattr);
+    if (mq == (mqd_t)-1) {
+        perror("opening mqueue failed");
+        goto failure2;
+    }
+
+    /* Create receiver RT-thread */
+    pthread_attr_init(&thattr);
+    pthread_attr_setdetachstate(&thattr, PTHREAD_CREATE_JOINABLE);
+    pthread_attr_setstacksize(&thattr, PTHREAD_STACK_MIN);
+    ret = pthread_create(&rxthread, &thattr, &receiver, NULL);
+    if (ret) {
+	fprintf(stderr, "%s: pthread_create(receiver) failed\n",
+		strerror(-ret));
+        goto failure3;
+    }
+
+    if (!repeater) {
+	/* Create transitter RT-thread */
+	ret = pthread_create(&txthread, &thattr, &transmitter, NULL);
+	if (ret) {
+	    fprintf(stderr, "%s: pthread_create(transmitter) failed\n",
+		    strerror(-ret));
+	    goto failure4;
+	}
+    }
+
+    pthread_setschedparam(pthread_self(), SCHED_FIFO, &param);
+
+    if (repeater)
+	printf("Messages\n");
+    else
+	printf("Messages RTTlast RTT_avg RTT_min RTT_max Overruns\n");
+
+    while (1) {
+	long long rtt_avg;
+
+        ret = mq_receive(mq, (char *)&rtt_stat, sizeof(rtt_stat), NULL);
+        if (ret != sizeof(rtt_stat)) {
+	    if (ret < 0) {
+		if (errno == EBADF)
+		    printf("terminating mq_receive\n");
+		else
+		    perror("mq_receive failed");
+	    } else
+		fprintf(stderr,
+			"mq_receive returned invalid length %d\n", ret);
+            break;
+	}
+
+	if (repeater) {
+	    printf("%8d\n", rxcount);
+	} else {
+	    rtt_avg = ((rtt_stat.rtt_sum - rtt_stat.rtt_sum_last) /
+		       rtt_stat.counts_per_sec);
+	    printf("%8d %7ld %7ld %7ld %7ld %8d\n", rxcount,
+		   (long)(rtt_stat.rtt / 1000), (long)(rtt_avg / 1000),
+		   (long)(rtt_stat.rtt_min / 1000),
+		   (long)(rtt_stat.rtt_max / 1000),
+		   overruns);
+	}
+    }
+
+    /* This call also leaves primary mode, required for socket cleanup. */
+    printf("shutting down\n");
+
+    /* Important: First close the sockets! */
+    while ((close(rxsock) < 0) && (errno == EAGAIN)) {
+        printf("RX socket busy - waiting...\n");
+        sleep(1);
+    }
+    while ((close(txsock) < 0) && (errno == EAGAIN)) {
+        printf("TX socket busy - waiting...\n");
+        sleep(1);
+    }
+
+    pthread_join(txthread, NULL);
+    pthread_kill(rxthread, SIGHUP);
+    pthread_join(rxthread, NULL);
+
+    return 0;
+
+ failure4:
+    pthread_kill(rxthread, SIGHUP);
+    pthread_join(rxthread, NULL);
+ failure3:
+    mq_close(mq);
+ failure2:
+    close(txsock);
+ failure1:
+    close(rxsock);
+
+    return 1;
+}

Re: [Xenomai-help] CAN driver

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]

Wolfgang Grandegger wrote:
> Jan Kiszka wrote:
>> Roland Tollenaar wrote:
>>> Hi list,
>>>
>>> does anyone have, or can anyone direct met to a project or code-snippet
>>> that shows how the CAN driver in the xenomai patch is used in an
>>> application? If not that any documentation that gives and explains what
>>> calls it responds to.
>>
>> Check src/utils/can/ on some tools that can also serve as nice examples.
>> But maybe we should also add even simpler demo code to the examples
>> repository. Just takes someone to write them...
> 
> The utility programs rtcanconfig, rtcansend and rtcanrcv in
> src/utils/can already demonstrate most of RT-Socket-CAN's functionality
> including filter definition and error handling. I do not see a need for
> simpler examples.

Yeah, maybe already a link (README) from the examples repos would be
enough to point beginners to them. Or maybe we should ask some beginners
what they expect, what they didn't understand... (Roland?)

> I have attached a patch for a nice program to measure
> the round trip time of CAN messages. It contrast to the other CAN
> utility programs, it uses the POSIX-API and works as-is for Socket-CAN
> as well. Jan, any objections to include it? If yes, I'm going to provide
> a README.

On first glance, nope, looks nice and clean.

> 
> BTW: some time ago I provided a patch to make the CAN utility programs
> part of the Doxygen documentation. IIRC, we said it's nice to have
> hyperlinked examples in general.

Some link at hand? Does it still apply? Sounds like something worth to
apply.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

Jan Kiszka wrote:
> Wolfgang Grandegger wrote:
>> Jan Kiszka wrote:
>>> Roland Tollenaar wrote:
>>>> Hi list,
>>>>
>>>> does anyone have, or can anyone direct met to a project or code-snippet
>>>> that shows how the CAN driver in the xenomai patch is used in an
>>>> application? If not that any documentation that gives and explains what
>>>> calls it responds to.
>>> Check src/utils/can/ on some tools that can also serve as nice examples.
>>> But maybe we should also add even simpler demo code to the examples
>>> repository. Just takes someone to write them...
>> The utility programs rtcanconfig, rtcansend and rtcanrcv in
>> src/utils/can already demonstrate most of RT-Socket-CAN's functionality
>> including filter definition and error handling. I do not see a need for
>> simpler examples.
> 
> Yeah, maybe already a link (README) from the examples repos would be
> enough to point beginners to them. Or maybe we should ask some beginners
> what they expect, what they didn't understand... (Roland?)

Forgot to mention, that there is a README in src/utils/can and 
ksrc/drivers/can.

>> I have attached a patch for a nice program to measure
>> the round trip time of CAN messages. It contrast to the other CAN
>> utility programs, it uses the POSIX-API and works as-is for Socket-CAN
>> as well. Jan, any objections to include it? If yes, I'm going to provide
>> a README.
> 
> On first glance, nope, looks nice and clean.

OK, a revised patch will follow. And shouldn't we have separate sub-dirs 
for each skin in examples/rtdm/profiles/can and serial as well. The 
Makefile is currently valid only for one skin, at least.

> 
>> BTW: some time ago I provided a patch to make the CAN utility programs
>> part of the Doxygen documentation. IIRC, we said it's nice to have
>> hyperlinked examples in general.
> 
> Some link at hand? Does it still apply? Sounds like something worth to
> apply.

See https://mail.gna.org/public/xenomai-core/2006-11/msg00033.html.
My patch was for the CAN utilities only. The idea was to have a more 
general implementation including code snippets and now examples as well.

Wolfgang.

Re: [Xenomai-help] CAN driver

[Roland Tollenaar]

Hi,

depending on advice on my email on the tsc problem I am having I will 
now try and find out how the user-space side of xenomai is to be used. 
Make a simple structure as a Qt thread (in which I intend to write the 
application) and then dig into the CAN stuff.

So in regard to this:
>> Yeah, maybe already a link (README) from the examples repos would be
>> enough to point beginners to them. Or maybe we should ask some beginners
>> what they expect, what they didn't understand... (Roland?)
I will comment on as soon as I have enough insight in xenomai's typical 
usage. Before then my opinion will probably not be worth much.

Besides we are only now going to order the PEAKCAN dongle so I will only 
be able to test something next week.

Thanks.

Roland.


> 
> Forgot to mention, that there is a README in src/utils/can and 
> ksrc/drivers/can.
> 
>>> I have attached a patch for a nice program to measure
>>> the round trip time of CAN messages. It contrast to the other CAN
>>> utility programs, it uses the POSIX-API and works as-is for Socket-CAN
>>> as well. Jan, any objections to include it? If yes, I'm going to provide
>>> a README.
>>
>> On first glance, nope, looks nice and clean.
> 
> OK, a revised patch will follow. And shouldn't we have separate sub-dirs 
> for each skin in examples/rtdm/profiles/can and serial as well. The 
> Makefile is currently valid only for one skin, at least.
> 
>>
>>> BTW: some time ago I provided a patch to make the CAN utility programs
>>> part of the Doxygen documentation. IIRC, we said it's nice to have
>>> hyperlinked examples in general.
>>
>> Some link at hand? Does it still apply? Sounds like something worth to
>> apply.
> 
> See https://mail.gna.org/public/xenomai-core/2006-11/msg00033.html.
> My patch was for the CAN utilities only. The idea was to have a more 
> general implementation including code snippets and now examples as well.
> 
> Wolfgang.
> 
> 

Re: [Xenomai-help] CAN driver

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

Roland Tollenaar wrote:
> Hi,
> 
> depending on advice on my email on the tsc problem I am having I will
> now try and find out how the user-space side of xenomai is to be used.
> Make a simple structure as a Qt thread (in which I intend to write the
> application) and then dig into the CAN stuff.
> 
> So in regard to this:
>>> Yeah, maybe already a link (README) from the examples repos would be
>>> enough to point beginners to them. Or maybe we should ask some beginners
>>> what they expect, what they didn't understand... (Roland?)
> I will comment on as soon as I have enough insight in xenomai's typical
> usage. Before then my opinion will probably not be worth much.
> 
> Besides we are only now going to order the PEAKCAN dongle so I will only
> be able to test something next week.

xeno_can_virt may help to do some testing even without hardware. It
emulates a local virtual CAN bus between 2 or more nodes.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

[Xenomai-core] (was: [Xenomai-help] CAN driver)

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 707 bytes --]

Wolfgang Grandegger wrote:
>>> BTW: some time ago I provided a patch to make the CAN utility programs
>>> part of the Doxygen documentation. IIRC, we said it's nice to have
>>> hyperlinked examples in general.
>>
>> Some link at hand? Does it still apply? Sounds like something worth to
>> apply.
> 
> See https://mail.gna.org/public/xenomai-core/2006-11/msg00033.html.
> My patch was for the CAN utilities only. The idea was to have a more
> general implementation including code snippets and now examples as well.
> 
> Wolfgang.
> 

Gilles, as you are planning to regenerate the docs for trunk anyway,
would you merge this patch (or better the corrected version) at that chance?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

[Xenomai-core] Re: (was: [Xenomai-help] CAN driver)

[Gilles Chanteperdrix]

Jan Kiszka wrote:
 > Wolfgang Grandegger wrote:
 > >>> BTW: some time ago I provided a patch to make the CAN utility programs
 > >>> part of the Doxygen documentation. IIRC, we said it's nice to have
 > >>> hyperlinked examples in general.
 > >>
 > >> Some link at hand? Does it still apply? Sounds like something worth to
 > >> apply.
 > > 
 > > See https://mail.gna.org/public/xenomai-core/2006-11/msg00033.html.
 > > My patch was for the CAN utilities only. The idea was to have a more
 > > general implementation including code snippets and now examples as well.
 > > 
 > > Wolfgang.
 > > 
 > 
 > Gilles, as you are planning to regenerate the docs for trunk anyway,
 > would you merge this patch (or better the corrected version) at that chance?

I compiled doxygen 1.4.6 and generated the documentation with it, but I
do not get the nice tabs at the top of the page, so the next step is to
ask Philippe: where did you get the version of doxygen 1.4.6 that
generates such a nice output ?

-- 


					    Gilles Chanteperdrix.

Re: [Xenomai-core] Re: (was: [Xenomai-help] CAN driver)

[Philippe Gerum]

On Wed, 2007-02-21 at 22:02 +0100, Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>  > Wolfgang Grandegger wrote:
>  > >>> BTW: some time ago I provided a patch to make the CAN utility programs
>  > >>> part of the Doxygen documentation. IIRC, we said it's nice to have
>  > >>> hyperlinked examples in general.
>  > >>
>  > >> Some link at hand? Does it still apply? Sounds like something worth to
>  > >> apply.
>  > > 
>  > > See https://mail.gna.org/public/xenomai-core/2006-11/msg00033.html.
>  > > My patch was for the CAN utilities only. The idea was to have a more
>  > > general implementation including code snippets and now examples as well.
>  > > 
>  > > Wolfgang.
>  > > 
>  > 
>  > Gilles, as you are planning to regenerate the docs for trunk anyway,
>  > would you merge this patch (or better the corrected version) at that chance?
> 
> I compiled doxygen 1.4.6 and generated the documentation with it, but I
> do not get the nice tabs at the top of the page, so the next step is to
> ask Philippe: where did you get the version of doxygen 1.4.6 that
> generates such a nice output ?
> 

Well, I started having those tabs generated after I switched to Ubuntu
(Dapper).

-- 
Philippe.

[Xenomai-core] Re: (was: [Xenomai-help] CAN driver)

[Wolfgang Grandegger]

[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]

Hi Gilles and Jan,

Jan Kiszka wrote:
> Wolfgang Grandegger wrote:
>>>> BTW: some time ago I provided a patch to make the CAN utility programs
>>>> part of the Doxygen documentation. IIRC, we said it's nice to have
>>>> hyperlinked examples in general.
>>> Some link at hand? Does it still apply? Sounds like something worth to
>>> apply.
>> See https://mail.gna.org/public/xenomai-core/2006-11/msg00033.html.
>> My patch was for the CAN utilities only. The idea was to have a more
>> general implementation including code snippets and now examples as well.
>>
>> Wolfgang.
>>
> 
> Gilles, as you are planning to regenerate the docs for trunk anyway,
> would you merge this patch (or better the corrected version) at that chance?

Attached is a revised patch for hyper-linking with example and utility 
programs. Apart from the CAN utilities, I have also added cross-link.c 
for RTserial and the code snippets of the native skin by adding 
"@example" tags to the appropriate source files. For the "demos" of the 
skins it was not obvious for me where to put them. The examples are then 
also part of the PDF documentation. Please have a look, hope you like 
it. I personally find the hyper-linking very useful.

Wolfgang.

[-- Attachment #2: xenomai-doc.patch --]
[-- Type: text/x-patch, Size: 5880 bytes --]

Index: include/rtdm/rtserial.h
===================================================================
--- include/rtdm/rtserial.h	(revision 2221)
+++ include/rtdm/rtserial.h	(working copy)
@@ -459,6 +459,12 @@ typedef struct rtser_event {
     _IOR(RTIOC_TYPE_SERIAL, 0x05, struct rtser_event)
 /** @} */
 
+/*!
+ * @anchor RTSERutils @name RT Serial example and utility programs
+ * @{ */
+/** @example cross-link.c */
+/** @} */
+
 /** @} */
 
 #endif /* _RTSERIAL_H */
Index: include/rtdm/rtcan.h
===================================================================
--- include/rtdm/rtcan.h	(revision 2221)
+++ include/rtdm/rtcan.h	(working copy)
@@ -1163,6 +1163,15 @@ typedef struct can_frame {
 
 /** @} */
 
+/*!
+ * @anchor CANutils @name CAN example and utility programs
+ * @{ */
+/** @example rtcanconfig.c */
+/** @example rtcansend.c */
+/** @example rtcanrecv.c */
+/** @example rtcan_rtt.c */
+/** @} */
+
 /** @} */
 
 
Index: ksrc/skins/native/mutex.c
===================================================================
--- ksrc/skins/native/mutex.c	(revision 2221)
+++ ksrc/skins/native/mutex.c	(working copy)
@@ -42,6 +42,8 @@
  *
  *@{*/
 
+/** @example mutex.c */
+
 #include <nucleus/pod.h>
 #include <nucleus/registry.h>
 #include <native/task.h>
Index: ksrc/skins/native/task.c
===================================================================
--- ksrc/skins/native/task.c	(revision 2221)
+++ ksrc/skins/native/task.c	(working copy)
@@ -38,6 +38,11 @@
  *
  *@{*/
 
+/** @example user_task.c */
+/** @example kernel_task.c */
+/** @example bound_task.c */
+/** @example sigxcpu.c */
+
 #include <nucleus/pod.h>
 #include <nucleus/heap.h>
 #include <nucleus/registry.h>
Index: ksrc/skins/native/intr.c
===================================================================
--- ksrc/skins/native/intr.c	(revision 2221)
+++ ksrc/skins/native/intr.c	(working copy)
@@ -27,6 +27,8 @@
  *
  *@{*/
 
+/** @example user_irq.c */
+
 #include <nucleus/pod.h>
 #include <nucleus/registry.h>
 #include <native/task.h>
Index: ksrc/skins/native/heap.c
===================================================================
--- ksrc/skins/native/heap.c	(revision 2221)
+++ ksrc/skins/native/heap.c	(working copy)
@@ -41,6 +41,9 @@
  *
  *@{*/
 
+/** @example local_heap.c */
+/** @example shared_mem.c */
+
 #include <nucleus/pod.h>
 #include <nucleus/registry.h>
 #include <native/task.h>
Index: ksrc/skins/native/event.c
===================================================================
--- ksrc/skins/native/event.c	(revision 2221)
+++ ksrc/skins/native/event.c	(working copy)
@@ -37,6 +37,8 @@
  *
  *@{*/
 
+/** @example event_flags.c */
+
 #include <nucleus/pod.h>
 #include <nucleus/registry.h>
 #include <native/task.h>
Index: ksrc/skins/native/cond.c
===================================================================
--- ksrc/skins/native/cond.c	(revision 2221)
+++ ksrc/skins/native/cond.c	(working copy)
@@ -39,6 +39,8 @@
  *
  *@{*/
 
+/** @example cond_var.c */
+
 #include <nucleus/pod.h>
 #include <nucleus/registry.h>
 #include <native/task.h>
Index: ksrc/skins/native/sem.c
===================================================================
--- ksrc/skins/native/sem.c	(revision 2221)
+++ ksrc/skins/native/sem.c	(working copy)
@@ -40,6 +40,8 @@
  *
  *@{*/
 
+/** @example semaphore.c */
+
 #include <nucleus/pod.h>
 #include <nucleus/registry.h>
 #include <native/task.h>
Index: ksrc/skins/native/queue.c
===================================================================
--- ksrc/skins/native/queue.c	(revision 2221)
+++ ksrc/skins/native/queue.c	(working copy)
@@ -40,6 +40,8 @@
  *
  *@{*/
 
+/** @example msg_queue.c */
+
 #include <nucleus/pod.h>
 #include <nucleus/registry.h>
 #include <native/task.h>
Index: ksrc/skins/native/alarm.c
===================================================================
--- ksrc/skins/native/alarm.c	(revision 2221)
+++ ksrc/skins/native/alarm.c	(working copy)
@@ -34,6 +34,8 @@
  *
  *@{*/
 
+/** @example user_alarm.c */
+
 #include <nucleus/pod.h>
 #include <nucleus/registry.h>
 #include <native/task.h>
Index: ksrc/skins/native/pipe.c
===================================================================
--- ksrc/skins/native/pipe.c	(revision 2221)
+++ ksrc/skins/native/pipe.c	(working copy)
@@ -45,6 +45,8 @@
  *
  *@{*/
 
+/** @example pipe.c */
+
 #include <nucleus/pod.h>
 #include <nucleus/heap.h>
 #include <nucleus/registry.h>
Index: doc/doxygen/Doxyfile-common.in
===================================================================
--- doc/doxygen/Doxyfile-common.in	(revision 2221)
+++ doc/doxygen/Doxyfile-common.in	(working copy)
@@ -389,21 +389,27 @@ EXCLUDE_PATTERNS       = 
 # directories that contain example code fragments that are included (see 
 # the \include command).
 
-EXAMPLE_PATH           = 
+EXAMPLE_PATH           = ../../ksrc/skins/native/snippets \
+		         ../../ksrc/skins/native/demos \
+		         ../../ksrc/skins/posix/demos \
+		         ../../ksrc/skins/psos+/demos \
+		         ../../ksrc/skins/vxworks/demos \
+		         ../../src/utils \
+			 ../../examples
 
 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 
 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
 # and *.h) to filter out the source-files in the directories. If left 
 # blank all files are included.
 
-EXAMPLE_PATTERNS       = 
+EXAMPLE_PATTERNS       = *.c
 
 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
 # searched for input files to be used with the \include or \dontinclude 
 # commands irrespective of the value of the RECURSIVE tag. 
 # Possible values are YES and NO. If left blank NO is used.
 
-EXAMPLE_RECURSIVE      = NO
+EXAMPLE_RECURSIVE      = YES
 
 # The IMAGE_PATH tag can be used to specify one or more files or 
 # directories that contain image that are included in the documentation (see 

[Xenomai-core] Re: (was: [Xenomai-help] CAN driver)

[Gilles Chanteperdrix]

Wolfgang Grandegger wrote:
> Hi Gilles and Jan,
> 
> Jan Kiszka wrote:
> 
>>Wolfgang Grandegger wrote:
>>
>>>>>BTW: some time ago I provided a patch to make the CAN utility programs
>>>>>part of the Doxygen documentation. IIRC, we said it's nice to have
>>>>>hyperlinked examples in general.
>>>>
>>>>Some link at hand? Does it still apply? Sounds like something worth to
>>>>apply.
>>>
>>>See https://mail.gna.org/public/xenomai-core/2006-11/msg00033.html.
>>>My patch was for the CAN utilities only. The idea was to have a more
>>>general implementation including code snippets and now examples as well.
>>>
>>>Wolfgang.
>>>
>>
>>Gilles, as you are planning to regenerate the docs for trunk anyway,
>>would you merge this patch (or better the corrected version) at that chance?
> 
> 
> Attached is a revised patch for hyper-linking with example and utility 
> programs. Apart from the CAN utilities, I have also added cross-link.c 
> for RTserial and the code snippets of the native skin by adding 
> "@example" tags to the appropriate source files. For the "demos" of the 
> skins it was not obvious for me where to put them. The examples are then 
> also part of the PDF documentation. Please have a look, hope you like 
> it. I personally find the hyper-linking very useful.

Ok. I finally got doxygen 1.4.6 tabs (the problem was the filesystem
rights of the tabs.css file), I will include your patch tonight.

-- 
                                                 Gilles Chanteperdrix

[Xenomai-core] Re: (was: [Xenomai-help] CAN driver)

[Gilles Chanteperdrix]

Wolfgang Grandegger wrote:
 > Hi Gilles and Jan,
 > 
 > Jan Kiszka wrote:
 > > Wolfgang Grandegger wrote:
 > >>>> BTW: some time ago I provided a patch to make the CAN utility programs
 > >>>> part of the Doxygen documentation. IIRC, we said it's nice to have
 > >>>> hyperlinked examples in general.
 > >>> Some link at hand? Does it still apply? Sounds like something worth to
 > >>> apply.
 > >> See https://mail.gna.org/public/xenomai-core/2006-11/msg00033.html.
 > >> My patch was for the CAN utilities only. The idea was to have a more
 > >> general implementation including code snippets and now examples as well.
 > >>
 > >> Wolfgang.
 > >>
 > > 
 > > Gilles, as you are planning to regenerate the docs for trunk anyway,
 > > would you merge this patch (or better the corrected version) at that chance?
 > 
 > Attached is a revised patch for hyper-linking with example and utility 
 > programs. Apart from the CAN utilities, I have also added cross-link.c 
 > for RTserial and the code snippets of the native skin by adding 
 > "@example" tags to the appropriate source files. For the "demos" of the 
 > skins it was not obvious for me where to put them. The examples are then 
 > also part of the PDF documentation. Please have a look, hope you like 
 > it. I personally find the hyper-linking very useful.

Hi, I have included your patch, but there is again some doxygen magic
that I do not understand, there are only a few links to the examples in
the documented files. For example in native condition variables
documentation page, there is no link to the cond.c example, but the
example is included (whereas examples sources that are not mentioned in
the source are not included at all). Any idea what could be the cause ?
-- 


					    Gilles Chanteperdrix.

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

Jan Kiszka wrote:
> Wolfgang Grandegger wrote:
[...]
>> I have attached a patch for a nice program to measure
>> the round trip time of CAN messages. It contrast to the other CAN
>> utility programs, it uses the POSIX-API and works as-is for Socket-CAN
>> as well. Jan, any objections to include it? If yes, I'm going to provide
>> a README.
> 
> On first glance, nope, looks nice and clean.

I have just commited the example program "rtcan_rtt" to the trunk.

Wolfgang.

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

Hi,

The first thing I notice is that I do not seem to find the devices
rtcan0, rtcan1 etc.

They are mentioned in the documentation and I presume they must be nodes in
/dev or so. But I cannot find them. rt-can is statically built into my
kernel so I don;t need to load any modules. I have selected the SJA
chip and the PEAK CAN Dongle.

I am reading the README in /src/can and the one in ksrc/drivers/can.

/proc/rtcan is present but no devices rtcan0, rtcan1 etc under it.

What have I missed?

Regards,

Roland


On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> Jan Kiszka wrote:
> > Wolfgang Grandegger wrote:
> [...]
> >> I have attached a patch for a nice program to measure
> >> the round trip time of CAN messages. It contrast to the other CAN
> >> utility programs, it uses the POSIX-API and works as-is for Socket-CAN
> >> as well. Jan, any objections to include it? If yes, I'm going to provide
> >> a README.
> >
> > On first glance, nope, looks nice and clean.
>
> I have just commited the example program "rtcan_rtt" to the trunk.
>
> Wolfgang.
>

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

Hi,

hope I'm not overloading the list. :)

The second thing I notice is that the code in the /src/utils/can
applications very low level. Admirable to be sure but for lesser
programming fundi's such as myself higher
level calls are more useful. What I was kind of hoping for was the typical

can_init(fd)
can_write(fd,can_mesg)
can_read(...
etc

API calls.

do they exist? If yes how can I incorporate them in my program?

Continuing my browsing......

Regards,

Roland


On 2/22/07, roland Tollenaar <rolandtollenaar@domain.hid> wrote:
> Hi,
>
> The first thing I notice is that I do not seem to find the devices
> rtcan0, rtcan1 etc.
>
> They are mentioned in the documentation and I presume they must be nodes in
> /dev or so. But I cannot find them. rt-can is statically built into my
> kernel so I don;t need to load any modules. I have selected the SJA
> chip and the PEAK CAN Dongle.
>
> I am reading the README in /src/can and the one in ksrc/drivers/can.
>
> /proc/rtcan is present but no devices rtcan0, rtcan1 etc under it.
>
> What have I missed?
>
> Regards,
>
> Roland
>
>
> On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> > Jan Kiszka wrote:
> > > Wolfgang Grandegger wrote:
> > [...]
> > >> I have attached a patch for a nice program to measure
> > >> the round trip time of CAN messages. It contrast to the other CAN
> > >> utility programs, it uses the POSIX-API and works as-is for Socket-CAN
> > >> as well. Jan, any objections to include it? If yes, I'm going to provide
> > >> a README.
> > >
> > > On first glance, nope, looks nice and clean.
> >
> > I have just commited the example program "rtcan_rtt" to the trunk.
> >
> > Wolfgang.
> >
>

Re: [Xenomai-help] CAN driver

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

roland Tollenaar wrote:
> Hi,
> 
> hope I'm not overloading the list. :)
> 
> The second thing I notice is that the code in the /src/utils/can
> applications very low level. Admirable to be sure but for lesser
> programming fundi's such as myself higher
> level calls are more useful. What I was kind of hoping for was the typical
> 
> can_init(fd)
> can_write(fd,can_mesg)
> can_read(...
> etc
> 
> API calls.
> 
> do they exist? If yes how can I incorporate them in my program?

Nope, RT-CAN is incorporating the latest shiny Socket-CAN model which
is, well, socket-based. It's not the n-th specific, incompatible CAN
character device implementation.

> 
> Continuing my browsing......

Start here regarding the API:

http://www.xenomai.org/documentation/branches/v2.3.x/html/api/group__rtcan.html

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] CAN driver

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

roland Tollenaar wrote:
> Hi,
> 
> The first thing I notice is that I do not seem to find the devices
> rtcan0, rtcan1 etc.
> 
> They are mentioned in the documentation and I presume they must be nodes in
> /dev or so. But I cannot find them. rt-can is statically built into my
> kernel so I don;t need to load any modules. I have selected the SJA
> chip and the PEAK CAN Dongle.
> 
> I am reading the README in /src/can and the one in ksrc/drivers/can.
> 
> /proc/rtcan is present but no devices rtcan0, rtcan1 etc under it.
> 
> What have I missed?
> 

rtcanX are networking devices, but only visible in the context of
RTDM/AF_CAN. To enable them, use rtcanconfig as explained in the README.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

Hi Jan,

>
> rtcanX are networking devices, but only visible in the context of
> RTDM/AF_CAN.
What is this?

 To enable them, use rtcanconfig as explained in the README.
Which README are you referring to? The only one I know of that says
something about rtcanconfig is in /src/utils/can and it does not
explain how to use ctrlmode and bittime. There is an example in it

rtcanconfig rtcan0 --baudrate=125000 start.

If I try

rtcanconfig rtcan0 --baudrate=125000 start

I get:

"Can't get interface index for rtcan0, code=-19"

Any idea what is wrong?

Regards,

Roland.



>
> Jan
>
>
>

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

roland Tollenaar wrote:
> Hi Jan,
> 
>>
>> rtcanX are networking devices, but only visible in the context of
>> RTDM/AF_CAN.
> What is this?
> 
> To enable them, use rtcanconfig as explained in the README.
> Which README are you referring to? The only one I know of that says
> something about rtcanconfig is in /src/utils/can and it does not
> explain how to use ctrlmode and bittime. There is an example in it
> 
> rtcanconfig rtcan0 --baudrate=125000 start.
> 
> If I try
> 
> rtcanconfig rtcan0 --baudrate=125000 start
> 
> I get:
> 
> "Can't get interface index for rtcan0, code=-19"
> 
> Any idea what is wrong?

Your devices have not yet show up on your system. I guess there is no 
entry in /proc/rtcan/devices. Check your boot log.

Wolfgang.

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

Hi Jan, Wolfgang,

> Your devices have not yet show up on your system. I guess there is no
> entry in /proc/rtcan/devices. Check your boot log.

There are no entries in /prc/rtcan/deices.

dmesg | grep "rtcan" or
dmesg | grep "rtcan*"

yields nothing.

I have checked the .config for the kernel build and CAN is statically
built into it.

I would prefer to statically build these things into the kernel due to
unwieldiness of my ditribution. If this is not possible I will make
modules. But is this the cause of problem I am having?

I have no device hooked to my system (PEAK dongle on its way) and the
virtual driver and TX loopback ability  has been excluded from the
kernel build. Is this possibly why i have no devices listed in
proc/rtcan/devices?


Roland.



On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> roland Tollenaar wrote:
> > Hi Jan,
> >
> >>
> >> rtcanX are networking devices, but only visible in the context of
> >> RTDM/AF_CAN.
> > What is this?
> >
> > To enable them, use rtcanconfig as explained in the README.
> > Which README are you referring to? The only one I know of that says
> > something about rtcanconfig is in /src/utils/can and it does not
> > explain how to use ctrlmode and bittime. There is an example in it
> >
> > rtcanconfig rtcan0 --baudrate=125000 start.
> >
> > If I try
> >
> > rtcanconfig rtcan0 --baudrate=125000 start
> >
> > I get:
> >
> > "Can't get interface index for rtcan0, code=-19"
> >
> > Any idea what is wrong?
>
> Your devices have not yet show up on your system. I guess there is no
> entry in /proc/rtcan/devices. Check your boot log.
>
> Wolfgang.
>
>

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

roland Tollenaar wrote:
> Hi Jan, Wolfgang,
> 
>> Your devices have not yet show up on your system. I guess there is no
>> entry in /proc/rtcan/devices. Check your boot log.
> 
> There are no entries in /prc/rtcan/deices.
> 
> dmesg | grep "rtcan" or
> dmesg | grep "rtcan*"
> 
> yields nothing.

Can you post the compete dmesg output?

> I have checked the .config for the kernel build and CAN is statically
> built into it.
> 
> I would prefer to statically build these things into the kernel due to
> unwieldiness of my ditribution. If this is not possible I will make
> modules. But is this the cause of problem I am having?

The driver for the dongle will not start properly when statically linked 
into the kernel. There should be a log message, though.

> I have no device hooked to my system (PEAK dongle on its way) and the
> virtual driver and TX loopback ability  has been excluded from the
> kernel build. Is this possibly why i have no devices listed in
> proc/rtcan/devices?

Without device it will not register anyhow and see above.

Wolfgang.

> On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> roland Tollenaar wrote:
>> > Hi Jan,
>> >
>> >>
>> >> rtcanX are networking devices, but only visible in the context of
>> >> RTDM/AF_CAN.
>> > What is this?
>> >
>> > To enable them, use rtcanconfig as explained in the README.
>> > Which README are you referring to? The only one I know of that says
>> > something about rtcanconfig is in /src/utils/can and it does not
>> > explain how to use ctrlmode and bittime. There is an example in it
>> >
>> > rtcanconfig rtcan0 --baudrate=125000 start.
>> >
>> > If I try
>> >
>> > rtcanconfig rtcan0 --baudrate=125000 start
>> >
>> > I get:
>> >
>> > "Can't get interface index for rtcan0, code=-19"
>> >
>> > Any idea what is wrong?
>>
>> Your devices have not yet show up on your system. I guess there is no
>> entry in /proc/rtcan/devices. Check your boot log.
>>
>> Wolfgang.
>>
>>
> 
> 

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]

Hi,

>
> Without device it will not register anyhow and see above.
>

I have now built the kernel with the virtual driver statically built
into it. No difference still no devices.


>
> The driver for the dongle will not start properly when statically linked
> into the kernel. There should be a log message, though.
>
No log message unless I am missing something. What is the module
called? After the
make modules in the kernel building process I will have to find it and
store it somewhere I will try loading it manually when the new kernel
is booted.

The virtual driver I can build in statically?


>
> Can you post the compete dmesg output?
>

 It is attached as a txt file. The errors regarding ehci, ohci, uhci
and mass_storage are results of trying to load modules that I have
statically built into the kernel.


Regards,

Roland





> > I have checked the .config for the kernel build and CAN is statically
> > built into it.
> >
> > I would prefer to statically build these things into the kernel due to
> > unwieldiness of my ditribution. If this is not possible I will make
> > modules. But is this the cause of problem I am having?
> > I have no device hooked to my system (PEAK dongle on its way) and the
> > virtual driver and TX loopback ability  has been excluded from the
> > kernel build. Is this possibly why i have no devices listed in
> > proc/rtcan/devices?
> Wolfgang.
>
> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> roland Tollenaar wrote:
> >> > Hi Jan,
> >> >
> >> >>
> >> >> rtcanX are networking devices, but only visible in the context of
> >> >> RTDM/AF_CAN.
> >> > What is this?
> >> >
> >> > To enable them, use rtcanconfig as explained in the README.
> >> > Which README are you referring to? The only one I know of that says
> >> > something about rtcanconfig is in /src/utils/can and it does not
> >> > explain how to use ctrlmode and bittime. There is an example in it
> >> >
> >> > rtcanconfig rtcan0 --baudrate=125000 start.
> >> >
> >> > If I try
> >> >
> >> > rtcanconfig rtcan0 --baudrate=125000 start
> >> >
> >> > I get:
> >> >
> >> > "Can't get interface index for rtcan0, code=-19"
> >> >
> >> > Any idea what is wrong?
> >>
> >> Your devices have not yet show up on your system. I guess there is no
> >> entry in /proc/rtcan/devices. Check your boot log.
> >>
> >> Wolfgang.
> >>
> >>
> >
> >
>
>

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 15289 bytes --]

veReady SeekComplete Error }
hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
ide: failed opcode was: unknown
UDF-fs: No partition found (1)
XFS: bad magic number
XFS: SB validate failed
NTFS volume version 3.1.
spurious 8259A interrupt: IRQ7.
UDF-fs: No partition found (1)
XFS: bad magic number
XFS: SB validate failed
Linux agpgart interface v0.101 (c) Dave Jones
fuse init (API version 7.6)
NTFS volume version 3.1.
input: PS/2 Synaptics TouchPad as /class/input/input1
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
PCI: Found IRQ 4 for device 0000:02:03.0
PCI: Sharing IRQ 4 with 0000:00:1f.3
PCI: Sharing IRQ 4 with 0000:00:1f.5
PCI: Sharing IRQ 4 with 0000:00:1f.6
IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
Yenta: CardBus bridge found at 0000:02:03.0 [1584:3000]
Yenta: adjusting diagnostic: 40 -> 60
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:03.0, mfunc 0x005c1d22, devctl 0x44
Yenta TI: socket 0000:02:03.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:02:03.0 no PCI interrupts. Fish. Please report.
Yenta: no PCI IRQ, CardBus support disabled for this socket.
Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
Yenta: ISA IRQ mask 0x02c0, PCI irq 0
Socket status: 30000006
pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff
cs: IO port probe 0xc000-0xcfff: clean.
pcmcia: parent PCI bridge Memory window: 0xffd00000 - 0xffdfffff
pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x89ffffff
pcmcia: Detected deprecated PCMCIA ioctl usage.
pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
cs: IO port probe 0xc00-0xcff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0x800-0x80f: clean.
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
cs: IO port probe 0xa00-0xaff: clean.
8139too Fast Ethernet driver 0.9.27
PCI: Found IRQ 3 for device 0000:02:0b.0
PCI: Sharing IRQ 3 with 0000:00:1d.1
eth0: RealTek RTL8139 at 0xc800, 00:03:0d:14:95:c4, IRQ 3
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
ieee1394: Initialized config rom entry `ip1394'
PCI: Found IRQ 5 for device 0000:02:0a.0
PCI: Sharing IRQ 5 with 0000:00:1d.2
PCI: Sharing IRQ 5 with 0000:00:1f.1
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5]  MMIO=[ffdff800-ffdfffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
PCI: Found IRQ 4 for device 0000:00:1f.5
PCI: Sharing IRQ 4 with 0000:00:1f.3
PCI: Sharing IRQ 4 with 0000:00:1f.6
IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 55427 usecs
intel8x0: clocking to 48000
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00030d4975701d84]
i8xx TCO timer: initialized (0x0860). heartbeat=30 sec (nowayout=0)
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
agpgart: Detected an Intel 865 Chipset.
agpgart: AGP aperture is 64M @ 0xf8000000
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
shpchp: Unknown symbol acpi_get_name
shpchp: Unknown symbol acpi_evaluate_object
kobject_register failed for ehci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
kobject_register failed for ohci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c032636c>] bus_add_driver+0x5c/0xa0
 [<c0326e37>] driver_register+0x57/0x90
 [<c02ea732>] __pci_register_driver+0x52/0x80
 [<f8ecf02e>] ohci_hcd_pci_init+0x2e/0x35 [ohci_hcd]
 [<c012e6e2>] sys_init_module+0x102/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for uhci_hcd (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
kobject_register failed for usb_storage (-17)
 [<c02ddf56>] kobject_register+0x36/0x50
 [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
 [<c012e4c9>] load_module+0x909/0x9f0
 [<c012e623>] sys_init_module+0x43/0x190
 [<c01029c8>] syscall_call+0x7/0xb
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
eth0: no IPv6 routers present

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

roland Tollenaar wrote:
> Hi,
> 
>>
>> Without device it will not register anyhow and see above.
>>
> 
> I have now built the kernel with the virtual driver statically built
> into it. No difference still no devices.
> 
>>
>> The driver for the dongle will not start properly when statically linked
>> into the kernel. There should be a log message, though.
>>
> No log message unless I am missing something. What is the module
> called? After the
> make modules in the kernel building process I will have to find it and
> store it somewhere I will try loading it manually when the new kernel
> is booted.
> 
> The virtual driver I can build in statically?
> 
> 
>>
>> Can you post the compete dmesg output?
>>
> 
> It is attached as a txt file. The errors regarding ehci, ohci, uhci
> and mass_storage are results of trying to load modules that I have
> statically built into the kernel.

I'm missing Xenomai related messages? Could you send the complete boot 
log please.

Wolfgang.

> 
> Regards,
> 
> Roland
> 
> 
> 
> 
> 
>> > I have checked the .config for the kernel build and CAN is statically
>> > built into it.
>> >
>> > I would prefer to statically build these things into the kernel due to
>> > unwieldiness of my ditribution. If this is not possible I will make
>> > modules. But is this the cause of problem I am having?
>> > I have no device hooked to my system (PEAK dongle on its way) and the
>> > virtual driver and TX loopback ability  has been excluded from the
>> > kernel build. Is this possibly why i have no devices listed in
>> > proc/rtcan/devices?
>> Wolfgang.
>>
>> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> >> roland Tollenaar wrote:
>> >> > Hi Jan,
>> >> >
>> >> >>
>> >> >> rtcanX are networking devices, but only visible in the context of
>> >> >> RTDM/AF_CAN.
>> >> > What is this?
>> >> >
>> >> > To enable them, use rtcanconfig as explained in the README.
>> >> > Which README are you referring to? The only one I know of that says
>> >> > something about rtcanconfig is in /src/utils/can and it does not
>> >> > explain how to use ctrlmode and bittime. There is an example in it
>> >> >
>> >> > rtcanconfig rtcan0 --baudrate=125000 start.
>> >> >
>> >> > If I try
>> >> >
>> >> > rtcanconfig rtcan0 --baudrate=125000 start
>> >> >
>> >> > I get:
>> >> >
>> >> > "Can't get interface index for rtcan0, code=-19"
>> >> >
>> >> > Any idea what is wrong?
>> >>
>> >> Your devices have not yet show up on your system. I guess there is no
>> >> entry in /proc/rtcan/devices. Check your boot log.
>> >>
>> >> Wolfgang.
>> >>
>> >>
>> >
>> >
>>
>>
> 
> ------------------------------------------------------------------------
> 
> veReady SeekComplete Error }
> hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
> ide: failed opcode was: unknown
> hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
> ide: failed opcode was: unknown
> hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
> ide: failed opcode was: unknown
> hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
> ide: failed opcode was: unknown
> UDF-fs: No partition found (1)
> XFS: bad magic number
> XFS: SB validate failed
> NTFS volume version 3.1.
> spurious 8259A interrupt: IRQ7.
> UDF-fs: No partition found (1)
> XFS: bad magic number
> XFS: SB validate failed
> Linux agpgart interface v0.101 (c) Dave Jones
> fuse init (API version 7.6)
> NTFS volume version 3.1.
> input: PS/2 Synaptics TouchPad as /class/input/input1
> Intel ISA PCIC probe: not found.
> Databook TCIC-2 PCMCIA probe: not found.
> PCI: Found IRQ 4 for device 0000:02:03.0
> PCI: Sharing IRQ 4 with 0000:00:1f.3
> PCI: Sharing IRQ 4 with 0000:00:1f.5
> PCI: Sharing IRQ 4 with 0000:00:1f.6
> IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
> Yenta: CardBus bridge found at 0000:02:03.0 [1584:3000]
> Yenta: adjusting diagnostic: 40 -> 60
> Yenta: Enabling burst memory read transactions
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: socket 0000:02:03.0, mfunc 0x005c1d22, devctl 0x44
> Yenta TI: socket 0000:02:03.0 probing PCI interrupt failed, trying to fix
> Yenta TI: socket 0000:02:03.0 no PCI interrupts. Fish. Please report.
> Yenta: no PCI IRQ, CardBus support disabled for this socket.
> Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
> Yenta: ISA IRQ mask 0x02c0, PCI irq 0
> Socket status: 30000006
> pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff
> cs: IO port probe 0xc000-0xcfff: clean.
> pcmcia: parent PCI bridge Memory window: 0xffd00000 - 0xffdfffff
> pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x89ffffff
> pcmcia: Detected deprecated PCMCIA ioctl usage.
> pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
> pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
> cs: IO port probe 0xc00-0xcff: clean.
> cs: IO port probe 0x820-0x8ff: clean.
> cs: IO port probe 0x800-0x80f: clean.
> cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
> cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
> cs: IO port probe 0xa00-0xaff: clean.
> 8139too Fast Ethernet driver 0.9.27
> PCI: Found IRQ 3 for device 0000:02:0b.0
> PCI: Sharing IRQ 3 with 0000:00:1d.1
> eth0: RealTek RTL8139 at 0xc800, 00:03:0d:14:95:c4, IRQ 3
> eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
> ieee1394: Initialized config rom entry `ip1394'
> PCI: Found IRQ 5 for device 0000:02:0a.0
> PCI: Sharing IRQ 5 with 0000:00:1d.2
> PCI: Sharing IRQ 5 with 0000:00:1f.1
> ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5]  MMIO=[ffdff800-ffdfffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
> PCI: Found IRQ 4 for device 0000:00:1f.5
> PCI: Sharing IRQ 4 with 0000:00:1f.3
> PCI: Sharing IRQ 4 with 0000:00:1f.6
> IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
> PCI: Setting latency timer of device 0000:00:1f.5 to 64
> intel8x0_measure_ac97_clock: measured 55427 usecs
> intel8x0: clocking to 48000
> ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00030d4975701d84]
> i8xx TCO timer: initialized (0x0860). heartbeat=30 sec (nowayout=0)
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> agpgart: Detected an Intel 865 Chipset.
> agpgart: AGP aperture is 64M @ 0xf8000000
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> shpchp: Unknown symbol acpi_get_name
> shpchp: Unknown symbol acpi_evaluate_object
> kobject_register failed for ehci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
> kobject_register failed for ohci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c032636c>] bus_add_driver+0x5c/0xa0
>  [<c0326e37>] driver_register+0x57/0x90
>  [<c02ea732>] __pci_register_driver+0x52/0x80
>  [<f8ecf02e>] ohci_hcd_pci_init+0x2e/0x35 [ohci_hcd]
>  [<c012e6e2>] sys_init_module+0x102/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for uhci_hcd (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> kobject_register failed for usb_storage (-17)
>  [<c02ddf56>] kobject_register+0x36/0x50
>  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>  [<c012e4c9>] load_module+0x909/0x9f0
>  [<c012e623>] sys_init_module+0x43/0x190
>  [<c01029c8>] syscall_call+0x7/0xb
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> NET: Registered protocol family 10
> lo: Disabled Privacy Extensions
> IPv6 over IPv4 tunneling driver
> eth0: no IPv6 routers present

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

Hi Wolfgang,

sorry to ask a stupid question here but where would I find the complete boot log

I am checking /var/log/

but am not sure which one you would want?

Xenomai itself must be running because the the programs in the
testsuite seem to be working.

Roland

On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> roland Tollenaar wrote:
> > Hi,
> >
> >>
> >> Without device it will not register anyhow and see above.
> >>
> >
> > I have now built the kernel with the virtual driver statically built
> > into it. No difference still no devices.
> >
> >>
> >> The driver for the dongle will not start properly when statically linked
> >> into the kernel. There should be a log message, though.
> >>
> > No log message unless I am missing something. What is the module
> > called? After the
> > make modules in the kernel building process I will have to find it and
> > store it somewhere I will try loading it manually when the new kernel
> > is booted.
> >
> > The virtual driver I can build in statically?
> >
> >
> >>
> >> Can you post the compete dmesg output?
> >>
> >
> > It is attached as a txt file. The errors regarding ehci, ohci, uhci
> > and mass_storage are results of trying to load modules that I have
> > statically built into the kernel.
>
> I'm missing Xenomai related messages? Could you send the complete boot
> log please.
>
> Wolfgang.
>
> >
> > Regards,
> >
> > Roland
> >
> >
> >
> >
> >
> >> > I have checked the .config for the kernel build and CAN is statically
> >> > built into it.
> >> >
> >> > I would prefer to statically build these things into the kernel due to
> >> > unwieldiness of my ditribution. If this is not possible I will make
> >> > modules. But is this the cause of problem I am having?
> >> > I have no device hooked to my system (PEAK dongle on its way) and the
> >> > virtual driver and TX loopback ability  has been excluded from the
> >> > kernel build. Is this possibly why i have no devices listed in
> >> > proc/rtcan/devices?
> >> Wolfgang.
> >>
> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> >> roland Tollenaar wrote:
> >> >> > Hi Jan,
> >> >> >
> >> >> >>
> >> >> >> rtcanX are networking devices, but only visible in the context of
> >> >> >> RTDM/AF_CAN.
> >> >> > What is this?
> >> >> >
> >> >> > To enable them, use rtcanconfig as explained in the README.
> >> >> > Which README are you referring to? The only one I know of that says
> >> >> > something about rtcanconfig is in /src/utils/can and it does not
> >> >> > explain how to use ctrlmode and bittime. There is an example in it
> >> >> >
> >> >> > rtcanconfig rtcan0 --baudrate=125000 start.
> >> >> >
> >> >> > If I try
> >> >> >
> >> >> > rtcanconfig rtcan0 --baudrate=125000 start
> >> >> >
> >> >> > I get:
> >> >> >
> >> >> > "Can't get interface index for rtcan0, code=-19"
> >> >> >
> >> >> > Any idea what is wrong?
> >> >>
> >> >> Your devices have not yet show up on your system. I guess there is no
> >> >> entry in /proc/rtcan/devices. Check your boot log.
> >> >>
> >> >> Wolfgang.
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> > ------------------------------------------------------------------------
> >
> > veReady SeekComplete Error }
> > hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
> > ide: failed opcode was: unknown
> > hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> > hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
> > ide: failed opcode was: unknown
> > hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> > hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
> > ide: failed opcode was: unknown
> > hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> > hdc: packet command error: error=0x54 { AbortedCommand LastFailedSense=0x05 }
> > ide: failed opcode was: unknown
> > UDF-fs: No partition found (1)
> > XFS: bad magic number
> > XFS: SB validate failed
> > NTFS volume version 3.1.
> > spurious 8259A interrupt: IRQ7.
> > UDF-fs: No partition found (1)
> > XFS: bad magic number
> > XFS: SB validate failed
> > Linux agpgart interface v0.101 (c) Dave Jones
> > fuse init (API version 7.6)
> > NTFS volume version 3.1.
> > input: PS/2 Synaptics TouchPad as /class/input/input1
> > Intel ISA PCIC probe: not found.
> > Databook TCIC-2 PCMCIA probe: not found.
> > PCI: Found IRQ 4 for device 0000:02:03.0
> > PCI: Sharing IRQ 4 with 0000:00:1f.3
> > PCI: Sharing IRQ 4 with 0000:00:1f.5
> > PCI: Sharing IRQ 4 with 0000:00:1f.6
> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
> > Yenta: CardBus bridge found at 0000:02:03.0 [1584:3000]
> > Yenta: adjusting diagnostic: 40 -> 60
> > Yenta: Enabling burst memory read transactions
> > Yenta: Using CSCINT to route CSC interrupts to PCI
> > Yenta: Routing CardBus interrupts to PCI
> > Yenta TI: socket 0000:02:03.0, mfunc 0x005c1d22, devctl 0x44
> > Yenta TI: socket 0000:02:03.0 probing PCI interrupt failed, trying to fix
> > Yenta TI: socket 0000:02:03.0 no PCI interrupts. Fish. Please report.
> > Yenta: no PCI IRQ, CardBus support disabled for this socket.
> > Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
> > Yenta: ISA IRQ mask 0x02c0, PCI irq 0
> > Socket status: 30000006
> > pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff
> > cs: IO port probe 0xc000-0xcfff: clean.
> > pcmcia: parent PCI bridge Memory window: 0xffd00000 - 0xffdfffff
> > pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x89ffffff
> > pcmcia: Detected deprecated PCMCIA ioctl usage.
> > pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools.
> > pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details.
> > cs: IO port probe 0xc00-0xcff: clean.
> > cs: IO port probe 0x820-0x8ff: clean.
> > cs: IO port probe 0x800-0x80f: clean.
> > cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
> > cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
> > cs: IO port probe 0xa00-0xaff: clean.
> > 8139too Fast Ethernet driver 0.9.27
> > PCI: Found IRQ 3 for device 0000:02:0b.0
> > PCI: Sharing IRQ 3 with 0000:00:1d.1
> > eth0: RealTek RTL8139 at 0xc800, 00:03:0d:14:95:c4, IRQ 3
> > eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
> > ieee1394: Initialized config rom entry `ip1394'
> > PCI: Found IRQ 5 for device 0000:02:0a.0
> > PCI: Sharing IRQ 5 with 0000:00:1d.2
> > PCI: Sharing IRQ 5 with 0000:00:1f.1
> > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5]  MMIO=[ffdff800-ffdfffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
> > PCI: Found IRQ 4 for device 0000:00:1f.5
> > PCI: Sharing IRQ 4 with 0000:00:1f.3
> > PCI: Sharing IRQ 4 with 0000:00:1f.6
> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
> > PCI: Setting latency timer of device 0000:00:1f.5 to 64
> > intel8x0_measure_ac97_clock: measured 55427 usecs
> > intel8x0: clocking to 48000
> > ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00030d4975701d84]
> > i8xx TCO timer: initialized (0x0860). heartbeat=30 sec (nowayout=0)
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > agpgart: Detected an Intel 865 Chipset.
> > agpgart: AGP aperture is 64M @ 0xf8000000
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > shpchp: Unknown symbol acpi_get_name
> > shpchp: Unknown symbol acpi_evaluate_object
> > kobject_register failed for ehci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
> > kobject_register failed for ohci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c032636c>] bus_add_driver+0x5c/0xa0
> >  [<c0326e37>] driver_register+0x57/0x90
> >  [<c02ea732>] __pci_register_driver+0x52/0x80
> >  [<f8ecf02e>] ohci_hcd_pci_init+0x2e/0x35 [ohci_hcd]
> >  [<c012e6e2>] sys_init_module+0x102/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for uhci_hcd (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > kobject_register failed for usb_storage (-17)
> >  [<c02ddf56>] kobject_register+0x36/0x50
> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >  [<c012e4c9>] load_module+0x909/0x9f0
> >  [<c012e623>] sys_init_module+0x43/0x190
> >  [<c01029c8>] syscall_call+0x7/0xb
> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> > NET: Registered protocol family 10
> > lo: Disabled Privacy Extensions
> > IPv6 over IPv4 tunneling driver
> > eth0: no IPv6 routers present
>
>

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

roland Tollenaar wrote:
> Hi Wolfgang,
> 
> sorry to ask a stupid question here but where would I find the complete 
> boot log
> 
> I am checking /var/log/
> 
> but am not sure which one you would want?

Output of "dmesg" please or the log of your console output. You should 
find lines similar to the following:

I-pipe: Domain Xenomai registered.
Xenomai: hal/powerpc started.
Xenomai: real-time nucleus v2.4-devel (Bells Of Lal) loaded.
Xenomai: starting native API services.
Xenomai: starting POSIX services.
Xenomai: starting RTDM services.
RT-Socket-CAN 0.20.2 - (C) 2006 RT-Socket-CAN Development Team
rtcan: registered rtcan0
rtcan0: VIRT driver loaded
rtcan: registered rtcan1
rtcan1: VIRT driver loaded

> 
> Xenomai itself must be running because the the programs in the
> testsuite seem to be working.
> 
> Roland
> 
> On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> roland Tollenaar wrote:
>> > Hi,
>> >
>> >>
>> >> Without device it will not register anyhow and see above.
>> >>
>> >
>> > I have now built the kernel with the virtual driver statically built
>> > into it. No difference still no devices.
>> >
>> >>
>> >> The driver for the dongle will not start properly when statically 
>> linked
>> >> into the kernel. There should be a log message, though.
>> >>
>> > No log message unless I am missing something. What is the module
>> > called? After the
>> > make modules in the kernel building process I will have to find it and
>> > store it somewhere I will try loading it manually when the new kernel
>> > is booted.
>> >
>> > The virtual driver I can build in statically?
>> >
>> >
>> >>
>> >> Can you post the compete dmesg output?
>> >>
>> >
>> > It is attached as a txt file. The errors regarding ehci, ohci, uhci
>> > and mass_storage are results of trying to load modules that I have
>> > statically built into the kernel.
>>
>> I'm missing Xenomai related messages? Could you send the complete boot
>> log please.
>>
>> Wolfgang.
>>
>> >
>> > Regards,
>> >
>> > Roland
>> >
>> >
>> >
>> >
>> >
>> >> > I have checked the .config for the kernel build and CAN is 
>> statically
>> >> > built into it.
>> >> >
>> >> > I would prefer to statically build these things into the kernel 
>> due to
>> >> > unwieldiness of my ditribution. If this is not possible I will make
>> >> > modules. But is this the cause of problem I am having?
>> >> > I have no device hooked to my system (PEAK dongle on its way) and 
>> the
>> >> > virtual driver and TX loopback ability  has been excluded from the
>> >> > kernel build. Is this possibly why i have no devices listed in
>> >> > proc/rtcan/devices?
>> >> Wolfgang.
>> >>
>> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> >> >> roland Tollenaar wrote:
>> >> >> > Hi Jan,
>> >> >> >
>> >> >> >>
>> >> >> >> rtcanX are networking devices, but only visible in the 
>> context of
>> >> >> >> RTDM/AF_CAN.
>> >> >> > What is this?
>> >> >> >
>> >> >> > To enable them, use rtcanconfig as explained in the README.
>> >> >> > Which README are you referring to? The only one I know of that 
>> says
>> >> >> > something about rtcanconfig is in /src/utils/can and it does not
>> >> >> > explain how to use ctrlmode and bittime. There is an example 
>> in it
>> >> >> >
>> >> >> > rtcanconfig rtcan0 --baudrate=125000 start.
>> >> >> >
>> >> >> > If I try
>> >> >> >
>> >> >> > rtcanconfig rtcan0 --baudrate=125000 start
>> >> >> >
>> >> >> > I get:
>> >> >> >
>> >> >> > "Can't get interface index for rtcan0, code=-19"
>> >> >> >
>> >> >> > Any idea what is wrong?
>> >> >>
>> >> >> Your devices have not yet show up on your system. I guess there 
>> is no
>> >> >> entry in /proc/rtcan/devices. Check your boot log.
>> >> >>
>> >> >> Wolfgang.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> > 
>> ------------------------------------------------------------------------
>> >
>> > veReady SeekComplete Error }
>> > hdc: packet command error: error=0x54 { AbortedCommand 
>> LastFailedSense=0x05 }
>> > ide: failed opcode was: unknown
>> > hdc: packet command error: status=0x51 { DriveReady SeekComplete 
>> Error }
>> > hdc: packet command error: error=0x54 { AbortedCommand 
>> LastFailedSense=0x05 }
>> > ide: failed opcode was: unknown
>> > hdc: packet command error: status=0x51 { DriveReady SeekComplete 
>> Error }
>> > hdc: packet command error: error=0x54 { AbortedCommand 
>> LastFailedSense=0x05 }
>> > ide: failed opcode was: unknown
>> > hdc: packet command error: status=0x51 { DriveReady SeekComplete 
>> Error }
>> > hdc: packet command error: error=0x54 { AbortedCommand 
>> LastFailedSense=0x05 }
>> > ide: failed opcode was: unknown
>> > UDF-fs: No partition found (1)
>> > XFS: bad magic number
>> > XFS: SB validate failed
>> > NTFS volume version 3.1.
>> > spurious 8259A interrupt: IRQ7.
>> > UDF-fs: No partition found (1)
>> > XFS: bad magic number
>> > XFS: SB validate failed
>> > Linux agpgart interface v0.101 (c) Dave Jones
>> > fuse init (API version 7.6)
>> > NTFS volume version 3.1.
>> > input: PS/2 Synaptics TouchPad as /class/input/input1
>> > Intel ISA PCIC probe: not found.
>> > Databook TCIC-2 PCMCIA probe: not found.
>> > PCI: Found IRQ 4 for device 0000:02:03.0
>> > PCI: Sharing IRQ 4 with 0000:00:1f.3
>> > PCI: Sharing IRQ 4 with 0000:00:1f.5
>> > PCI: Sharing IRQ 4 with 0000:00:1f.6
>> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
>> > Yenta: CardBus bridge found at 0000:02:03.0 [1584:3000]
>> > Yenta: adjusting diagnostic: 40 -> 60
>> > Yenta: Enabling burst memory read transactions
>> > Yenta: Using CSCINT to route CSC interrupts to PCI
>> > Yenta: Routing CardBus interrupts to PCI
>> > Yenta TI: socket 0000:02:03.0, mfunc 0x005c1d22, devctl 0x44
>> > Yenta TI: socket 0000:02:03.0 probing PCI interrupt failed, trying 
>> to fix
>> > Yenta TI: socket 0000:02:03.0 no PCI interrupts. Fish. Please report.
>> > Yenta: no PCI IRQ, CardBus support disabled for this socket.
>> > Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
>> > Yenta: ISA IRQ mask 0x02c0, PCI irq 0
>> > Socket status: 30000006
>> > pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff
>> > cs: IO port probe 0xc000-0xcfff: clean.
>> > pcmcia: parent PCI bridge Memory window: 0xffd00000 - 0xffdfffff
>> > pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x89ffffff
>> > pcmcia: Detected deprecated PCMCIA ioctl usage.
>> > pcmcia: This interface will soon be removed from the kernel; please 
>> expect breakage unless you upgrade to new tools.
>> > pcmcia: see 
>> http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for 
>> details.
>> > cs: IO port probe 0xc00-0xcff: clean.
>> > cs: IO port probe 0x820-0x8ff: clean.
>> > cs: IO port probe 0x800-0x80f: clean.
>> > cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
>> > cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
>> > cs: IO port probe 0xa00-0xaff: clean.
>> > 8139too Fast Ethernet driver 0.9.27
>> > PCI: Found IRQ 3 for device 0000:02:0b.0
>> > PCI: Sharing IRQ 3 with 0000:00:1d.1
>> > eth0: RealTek RTL8139 at 0xc800, 00:03:0d:14:95:c4, IRQ 3
>> > eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
>> > ieee1394: Initialized config rom entry `ip1394'
>> > PCI: Found IRQ 5 for device 0000:02:0a.0
>> > PCI: Sharing IRQ 5 with 0000:00:1d.2
>> > PCI: Sharing IRQ 5 with 0000:00:1f.1
>> > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5]  
>> MMIO=[ffdff800-ffdfffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
>> > PCI: Found IRQ 4 for device 0000:00:1f.5
>> > PCI: Sharing IRQ 4 with 0000:00:1f.3
>> > PCI: Sharing IRQ 4 with 0000:00:1f.6
>> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
>> > PCI: Setting latency timer of device 0000:00:1f.5 to 64
>> > intel8x0_measure_ac97_clock: measured 55427 usecs
>> > intel8x0: clocking to 48000
>> > ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00030d4975701d84]
>> > i8xx TCO timer: initialized (0x0860). heartbeat=30 sec (nowayout=0)
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > agpgart: Detected an Intel 865 Chipset.
>> > agpgart: AGP aperture is 64M @ 0xf8000000
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > shpchp: Unknown symbol acpi_get_name
>> > shpchp: Unknown symbol acpi_evaluate_object
>> > kobject_register failed for ehci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver 
>> (PCI)
>> > kobject_register failed for ohci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c032636c>] bus_add_driver+0x5c/0xa0
>> >  [<c0326e37>] driver_register+0x57/0x90
>> >  [<c02ea732>] __pci_register_driver+0x52/0x80
>> >  [<f8ecf02e>] ohci_hcd_pci_init+0x2e/0x35 [ohci_hcd]
>> >  [<c012e6e2>] sys_init_module+0x102/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for uhci_hcd (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > kobject_register failed for usb_storage (-17)
>> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >  [<c012e623>] sys_init_module+0x43/0x190
>> >  [<c01029c8>] syscall_call+0x7/0xb
>> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
>> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
>> > NET: Registered protocol family 10
>> > lo: Disabled Privacy Extensions
>> > IPv6 over IPv4 tunneling driver
>> > eth0: no IPv6 routers present
>>
>>
> 
> 

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

[-- Attachment #1: Type: text/plain, Size: 23243 bytes --]

Hi Wolfgang,

I did this

#/var> grep -r "Xenomai" ./  >> dmesg.txt

I found what you are looking for you will find it in the message attached.

I did the same for rtcan which should yield the last 4 lines

and found this:

./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan0
./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan0: VIRT driver loaded
./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan1
./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan1: VIRT driver loaded
./log/dmesg:rtcan: registered rtcan0
./log/dmesg:rtcan0: VIRT driver loaded
./log/dmesg:rtcan: registered rtcan1
./log/dmesg:rtcan1: VIRT driver loaded
./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan0
./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan0: VIRT driver loaded
./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan1
./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan1: VIRT driver loaded
./adm/dmesg:rtcan: registered rtcan0
./adm/dmesg:rtcan0: VIRT driver loaded
./adm/dmesg:rtcan: registered rtcan1
./adm/dmesg:rtcan1: VIRT driver loaded


Hope this helps us?

Regards,

Roland


On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> roland Tollenaar wrote:
> > Hi Wolfgang,
> >
> > sorry to ask a stupid question here but where would I find the complete
> > boot log
> >
> > I am checking /var/log/
> >
> > but am not sure which one you would want?
>
> Output of "dmesg" please or the log of your console output. You should
> find lines similar to the following:
>
> I-pipe: Domain Xenomai registered.
> Xenomai: hal/powerpc started.
> Xenomai: real-time nucleus v2.4-devel (Bells Of Lal) loaded.
> Xenomai: starting native API services.
> Xenomai: starting POSIX services.
> Xenomai: starting RTDM services.
> RT-Socket-CAN 0.20.2 - (C) 2006 RT-Socket-CAN Development Team
> rtcan: registered rtcan0
> rtcan0: VIRT driver loaded
> rtcan: registered rtcan1
> rtcan1: VIRT driver loaded
>
> >
> > Xenomai itself must be running because the the programs in the
> > testsuite seem to be working.
> >
> > Roland
> >
> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> roland Tollenaar wrote:
> >> > Hi,
> >> >
> >> >>
> >> >> Without device it will not register anyhow and see above.
> >> >>
> >> >
> >> > I have now built the kernel with the virtual driver statically built
> >> > into it. No difference still no devices.
> >> >
> >> >>
> >> >> The driver for the dongle will not start properly when statically
> >> linked
> >> >> into the kernel. There should be a log message, though.
> >> >>
> >> > No log message unless I am missing something. What is the module
> >> > called? After the
> >> > make modules in the kernel building process I will have to find it and
> >> > store it somewhere I will try loading it manually when the new kernel
> >> > is booted.
> >> >
> >> > The virtual driver I can build in statically?
> >> >
> >> >
> >> >>
> >> >> Can you post the compete dmesg output?
> >> >>
> >> >
> >> > It is attached as a txt file. The errors regarding ehci, ohci, uhci
> >> > and mass_storage are results of trying to load modules that I have
> >> > statically built into the kernel.
> >>
> >> I'm missing Xenomai related messages? Could you send the complete boot
> >> log please.
> >>
> >> Wolfgang.
> >>
> >> >
> >> > Regards,
> >> >
> >> > Roland
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >> > I have checked the .config for the kernel build and CAN is
> >> statically
> >> >> > built into it.
> >> >> >
> >> >> > I would prefer to statically build these things into the kernel
> >> due to
> >> >> > unwieldiness of my ditribution. If this is not possible I will make
> >> >> > modules. But is this the cause of problem I am having?
> >> >> > I have no device hooked to my system (PEAK dongle on its way) and
> >> the
> >> >> > virtual driver and TX loopback ability  has been excluded from the
> >> >> > kernel build. Is this possibly why i have no devices listed in
> >> >> > proc/rtcan/devices?
> >> >> Wolfgang.
> >> >>
> >> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> >> >> roland Tollenaar wrote:
> >> >> >> > Hi Jan,
> >> >> >> >
> >> >> >> >>
> >> >> >> >> rtcanX are networking devices, but only visible in the
> >> context of
> >> >> >> >> RTDM/AF_CAN.
> >> >> >> > What is this?
> >> >> >> >
> >> >> >> > To enable them, use rtcanconfig as explained in the README.
> >> >> >> > Which README are you referring to? The only one I know of that
> >> says
> >> >> >> > something about rtcanconfig is in /src/utils/can and it does not
> >> >> >> > explain how to use ctrlmode and bittime. There is an example
> >> in it
> >> >> >> >
> >> >> >> > rtcanconfig rtcan0 --baudrate=125000 start.
> >> >> >> >
> >> >> >> > If I try
> >> >> >> >
> >> >> >> > rtcanconfig rtcan0 --baudrate=125000 start
> >> >> >> >
> >> >> >> > I get:
> >> >> >> >
> >> >> >> > "Can't get interface index for rtcan0, code=-19"
> >> >> >> >
> >> >> >> > Any idea what is wrong?
> >> >> >>
> >> >> >> Your devices have not yet show up on your system. I guess there
> >> is no
> >> >> >> entry in /proc/rtcan/devices. Check your boot log.
> >> >> >>
> >> >> >> Wolfgang.
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >> ------------------------------------------------------------------------
> >> >
> >> > veReady SeekComplete Error }
> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> LastFailedSense=0x05 }
> >> > ide: failed opcode was: unknown
> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
> >> Error }
> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> LastFailedSense=0x05 }
> >> > ide: failed opcode was: unknown
> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
> >> Error }
> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> LastFailedSense=0x05 }
> >> > ide: failed opcode was: unknown
> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
> >> Error }
> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> LastFailedSense=0x05 }
> >> > ide: failed opcode was: unknown
> >> > UDF-fs: No partition found (1)
> >> > XFS: bad magic number
> >> > XFS: SB validate failed
> >> > NTFS volume version 3.1.
> >> > spurious 8259A interrupt: IRQ7.
> >> > UDF-fs: No partition found (1)
> >> > XFS: bad magic number
> >> > XFS: SB validate failed
> >> > Linux agpgart interface v0.101 (c) Dave Jones
> >> > fuse init (API version 7.6)
> >> > NTFS volume version 3.1.
> >> > input: PS/2 Synaptics TouchPad as /class/input/input1
> >> > Intel ISA PCIC probe: not found.
> >> > Databook TCIC-2 PCMCIA probe: not found.
> >> > PCI: Found IRQ 4 for device 0000:02:03.0
> >> > PCI: Sharing IRQ 4 with 0000:00:1f.3
> >> > PCI: Sharing IRQ 4 with 0000:00:1f.5
> >> > PCI: Sharing IRQ 4 with 0000:00:1f.6
> >> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
> >> > Yenta: CardBus bridge found at 0000:02:03.0 [1584:3000]
> >> > Yenta: adjusting diagnostic: 40 -> 60
> >> > Yenta: Enabling burst memory read transactions
> >> > Yenta: Using CSCINT to route CSC interrupts to PCI
> >> > Yenta: Routing CardBus interrupts to PCI
> >> > Yenta TI: socket 0000:02:03.0, mfunc 0x005c1d22, devctl 0x44
> >> > Yenta TI: socket 0000:02:03.0 probing PCI interrupt failed, trying
> >> to fix
> >> > Yenta TI: socket 0000:02:03.0 no PCI interrupts. Fish. Please report.
> >> > Yenta: no PCI IRQ, CardBus support disabled for this socket.
> >> > Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
> >> > Yenta: ISA IRQ mask 0x02c0, PCI irq 0
> >> > Socket status: 30000006
> >> > pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff
> >> > cs: IO port probe 0xc000-0xcfff: clean.
> >> > pcmcia: parent PCI bridge Memory window: 0xffd00000 - 0xffdfffff
> >> > pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x89ffffff
> >> > pcmcia: Detected deprecated PCMCIA ioctl usage.
> >> > pcmcia: This interface will soon be removed from the kernel; please
> >> expect breakage unless you upgrade to new tools.
> >> > pcmcia: see
> >> http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for
> >> details.
> >> > cs: IO port probe 0xc00-0xcff: clean.
> >> > cs: IO port probe 0x820-0x8ff: clean.
> >> > cs: IO port probe 0x800-0x80f: clean.
> >> > cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
> >> > cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
> >> > cs: IO port probe 0xa00-0xaff: clean.
> >> > 8139too Fast Ethernet driver 0.9.27
> >> > PCI: Found IRQ 3 for device 0000:02:0b.0
> >> > PCI: Sharing IRQ 3 with 0000:00:1d.1
> >> > eth0: RealTek RTL8139 at 0xc800, 00:03:0d:14:95:c4, IRQ 3
> >> > eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
> >> > ieee1394: Initialized config rom entry `ip1394'
> >> > PCI: Found IRQ 5 for device 0000:02:0a.0
> >> > PCI: Sharing IRQ 5 with 0000:00:1d.2
> >> > PCI: Sharing IRQ 5 with 0000:00:1f.1
> >> > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5]
> >> MMIO=[ffdff800-ffdfffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
> >> > PCI: Found IRQ 4 for device 0000:00:1f.5
> >> > PCI: Sharing IRQ 4 with 0000:00:1f.3
> >> > PCI: Sharing IRQ 4 with 0000:00:1f.6
> >> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
> >> > PCI: Setting latency timer of device 0000:00:1f.5 to 64
> >> > intel8x0_measure_ac97_clock: measured 55427 usecs
> >> > intel8x0: clocking to 48000
> >> > ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00030d4975701d84]
> >> > i8xx TCO timer: initialized (0x0860). heartbeat=30 sec (nowayout=0)
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > agpgart: Detected an Intel 865 Chipset.
> >> > agpgart: AGP aperture is 64M @ 0xf8000000
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > shpchp: Unknown symbol acpi_get_name
> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> > kobject_register failed for ehci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver
> >> (PCI)
> >> > kobject_register failed for ohci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c032636c>] bus_add_driver+0x5c/0xa0
> >> >  [<c0326e37>] driver_register+0x57/0x90
> >> >  [<c02ea732>] __pci_register_driver+0x52/0x80
> >> >  [<f8ecf02e>] ohci_hcd_pci_init+0x2e/0x35 [ohci_hcd]
> >> >  [<c012e6e2>] sys_init_module+0x102/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for uhci_hcd (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > kobject_register failed for usb_storage (-17)
> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> >> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> >> > NET: Registered protocol family 10
> >> > lo: Disabled Privacy Extensions
> >> > IPv6 over IPv4 tunneling driver
> >> > eth0: no IPv6 routers present
> >>
> >>
> >
> >
>
>

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 3712 bytes --]

./log/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -nq xeno_nucleus
./log/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_native
./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_rtdm
./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_timerbench
./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/usr/xenomai/bin/latency
./adm/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -nq xeno_nucleus
./adm/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_native
./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_rtdm
./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_timerbench
./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/usr/xenomai/bin/latency
./log/syslog:Feb 22 13:21:38 (none) kernel: I-pipe: Domain Xenomai registered.
./log/syslog:Feb 22 13:21:38 (none) kernel: Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: hal/x86 started.
./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: real-time nucleus v2.3 (Baroque) loaded.
./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting native API services.
./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting POSIX services.
./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting RTDM services.
./log/dmesg:I-pipe: Domain Xenomai registered.
./log/dmesg:Xenomai: hal/x86 started.
./log/dmesg:Xenomai: real-time nucleus v2.3 (Baroque) loaded.
./log/dmesg:Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
./log/dmesg:Xenomai: starting native API services.
./log/dmesg:Xenomai: starting POSIX services.
./log/dmesg:Xenomai: starting RTDM services.
./adm/syslog:Feb 22 13:21:38 (none) kernel: I-pipe: Domain Xenomai registered.
./adm/syslog:Feb 22 13:21:38 (none) kernel: Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: hal/x86 started.
./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: real-time nucleus v2.3 (Baroque) loaded.
./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting native API services.
./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting POSIX services.
./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting RTDM services.
./adm/dmesg:I-pipe: Domain Xenomai registered.
./adm/dmesg:Xenomai: hal/x86 started.
./adm/dmesg:Xenomai: real-time nucleus v2.3 (Baroque) loaded.
./adm/dmesg:Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
./adm/dmesg:Xenomai: starting native API services.
./adm/dmesg:Xenomai: starting POSIX services.
./adm/dmesg:Xenomai: starting RTDM services.

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

roland Tollenaar wrote:
> Hi Wolfgang,
> 
> I did this
> 
> #/var> grep -r "Xenomai" ./  >> dmesg.txt
> 
> I found what you are looking for you will find it in the message attached.
> 
> I did the same for rtcan which should yield the last 4 lines
> 
> and found this:
> 
> ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan0
> ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan0: VIRT driver loaded
> ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan1
> ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan1: VIRT driver loaded
> ./log/dmesg:rtcan: registered rtcan0
> ./log/dmesg:rtcan0: VIRT driver loaded
> ./log/dmesg:rtcan: registered rtcan1
> ./log/dmesg:rtcan1: VIRT driver loaded
> ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan0
> ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan0: VIRT driver loaded
> ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan1
> ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan1: VIRT driver loaded
> ./adm/dmesg:rtcan: registered rtcan0
> ./adm/dmesg:rtcan0: VIRT driver loaded
> ./adm/dmesg:rtcan: registered rtcan1
> ./adm/dmesg:rtcan1: VIRT driver loaded
> 
> 
> Hope this helps us?

OK, now, what is the output of /proc/rtcan?

> 
> Regards,
> 
> Roland
> 
> 
> On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> roland Tollenaar wrote:
>> > Hi Wolfgang,
>> >
>> > sorry to ask a stupid question here but where would I find the complete
>> > boot log
>> >
>> > I am checking /var/log/
>> >
>> > but am not sure which one you would want?
>>
>> Output of "dmesg" please or the log of your console output. You should
>> find lines similar to the following:
>>
>> I-pipe: Domain Xenomai registered.
>> Xenomai: hal/powerpc started.
>> Xenomai: real-time nucleus v2.4-devel (Bells Of Lal) loaded.
>> Xenomai: starting native API services.
>> Xenomai: starting POSIX services.
>> Xenomai: starting RTDM services.
>> RT-Socket-CAN 0.20.2 - (C) 2006 RT-Socket-CAN Development Team
>> rtcan: registered rtcan0
>> rtcan0: VIRT driver loaded
>> rtcan: registered rtcan1
>> rtcan1: VIRT driver loaded
>>
>> >
>> > Xenomai itself must be running because the the programs in the
>> > testsuite seem to be working.
>> >
>> > Roland
>> >
>> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> >> roland Tollenaar wrote:
>> >> > Hi,
>> >> >
>> >> >>
>> >> >> Without device it will not register anyhow and see above.
>> >> >>
>> >> >
>> >> > I have now built the kernel with the virtual driver statically built
>> >> > into it. No difference still no devices.
>> >> >
>> >> >>
>> >> >> The driver for the dongle will not start properly when statically
>> >> linked
>> >> >> into the kernel. There should be a log message, though.
>> >> >>
>> >> > No log message unless I am missing something. What is the module
>> >> > called? After the
>> >> > make modules in the kernel building process I will have to find 
>> it and
>> >> > store it somewhere I will try loading it manually when the new 
>> kernel
>> >> > is booted.
>> >> >
>> >> > The virtual driver I can build in statically?
>> >> >
>> >> >
>> >> >>
>> >> >> Can you post the compete dmesg output?
>> >> >>
>> >> >
>> >> > It is attached as a txt file. The errors regarding ehci, ohci, uhci
>> >> > and mass_storage are results of trying to load modules that I have
>> >> > statically built into the kernel.
>> >>
>> >> I'm missing Xenomai related messages? Could you send the complete boot
>> >> log please.
>> >>
>> >> Wolfgang.
>> >>
>> >> >
>> >> > Regards,
>> >> >
>> >> > Roland
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >> > I have checked the .config for the kernel build and CAN is
>> >> statically
>> >> >> > built into it.
>> >> >> >
>> >> >> > I would prefer to statically build these things into the kernel
>> >> due to
>> >> >> > unwieldiness of my ditribution. If this is not possible I will 
>> make
>> >> >> > modules. But is this the cause of problem I am having?
>> >> >> > I have no device hooked to my system (PEAK dongle on its way) and
>> >> the
>> >> >> > virtual driver and TX loopback ability  has been excluded from 
>> the
>> >> >> > kernel build. Is this possibly why i have no devices listed in
>> >> >> > proc/rtcan/devices?
>> >> >> Wolfgang.
>> >> >>
>> >> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> >> >> >> roland Tollenaar wrote:
>> >> >> >> > Hi Jan,
>> >> >> >> >
>> >> >> >> >>
>> >> >> >> >> rtcanX are networking devices, but only visible in the
>> >> context of
>> >> >> >> >> RTDM/AF_CAN.
>> >> >> >> > What is this?
>> >> >> >> >
>> >> >> >> > To enable them, use rtcanconfig as explained in the README.
>> >> >> >> > Which README are you referring to? The only one I know of that
>> >> says
>> >> >> >> > something about rtcanconfig is in /src/utils/can and it 
>> does not
>> >> >> >> > explain how to use ctrlmode and bittime. There is an example
>> >> in it
>> >> >> >> >
>> >> >> >> > rtcanconfig rtcan0 --baudrate=125000 start.
>> >> >> >> >
>> >> >> >> > If I try
>> >> >> >> >
>> >> >> >> > rtcanconfig rtcan0 --baudrate=125000 start
>> >> >> >> >
>> >> >> >> > I get:
>> >> >> >> >
>> >> >> >> > "Can't get interface index for rtcan0, code=-19"
>> >> >> >> >
>> >> >> >> > Any idea what is wrong?
>> >> >> >>
>> >> >> >> Your devices have not yet show up on your system. I guess there
>> >> is no
>> >> >> >> entry in /proc/rtcan/devices. Check your boot log.
>> >> >> >>
>> >> >> >> Wolfgang.
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> 
>> ------------------------------------------------------------------------
>> >> >
>> >> > veReady SeekComplete Error }
>> >> > hdc: packet command error: error=0x54 { AbortedCommand
>> >> LastFailedSense=0x05 }
>> >> > ide: failed opcode was: unknown
>> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
>> >> Error }
>> >> > hdc: packet command error: error=0x54 { AbortedCommand
>> >> LastFailedSense=0x05 }
>> >> > ide: failed opcode was: unknown
>> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
>> >> Error }
>> >> > hdc: packet command error: error=0x54 { AbortedCommand
>> >> LastFailedSense=0x05 }
>> >> > ide: failed opcode was: unknown
>> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
>> >> Error }
>> >> > hdc: packet command error: error=0x54 { AbortedCommand
>> >> LastFailedSense=0x05 }
>> >> > ide: failed opcode was: unknown
>> >> > UDF-fs: No partition found (1)
>> >> > XFS: bad magic number
>> >> > XFS: SB validate failed
>> >> > NTFS volume version 3.1.
>> >> > spurious 8259A interrupt: IRQ7.
>> >> > UDF-fs: No partition found (1)
>> >> > XFS: bad magic number
>> >> > XFS: SB validate failed
>> >> > Linux agpgart interface v0.101 (c) Dave Jones
>> >> > fuse init (API version 7.6)
>> >> > NTFS volume version 3.1.
>> >> > input: PS/2 Synaptics TouchPad as /class/input/input1
>> >> > Intel ISA PCIC probe: not found.
>> >> > Databook TCIC-2 PCMCIA probe: not found.
>> >> > PCI: Found IRQ 4 for device 0000:02:03.0
>> >> > PCI: Sharing IRQ 4 with 0000:00:1f.3
>> >> > PCI: Sharing IRQ 4 with 0000:00:1f.5
>> >> > PCI: Sharing IRQ 4 with 0000:00:1f.6
>> >> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
>> >> > Yenta: CardBus bridge found at 0000:02:03.0 [1584:3000]
>> >> > Yenta: adjusting diagnostic: 40 -> 60
>> >> > Yenta: Enabling burst memory read transactions
>> >> > Yenta: Using CSCINT to route CSC interrupts to PCI
>> >> > Yenta: Routing CardBus interrupts to PCI
>> >> > Yenta TI: socket 0000:02:03.0, mfunc 0x005c1d22, devctl 0x44
>> >> > Yenta TI: socket 0000:02:03.0 probing PCI interrupt failed, trying
>> >> to fix
>> >> > Yenta TI: socket 0000:02:03.0 no PCI interrupts. Fish. Please 
>> report.
>> >> > Yenta: no PCI IRQ, CardBus support disabled for this socket.
>> >> > Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
>> >> > Yenta: ISA IRQ mask 0x02c0, PCI irq 0
>> >> > Socket status: 30000006
>> >> > pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff
>> >> > cs: IO port probe 0xc000-0xcfff: clean.
>> >> > pcmcia: parent PCI bridge Memory window: 0xffd00000 - 0xffdfffff
>> >> > pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x89ffffff
>> >> > pcmcia: Detected deprecated PCMCIA ioctl usage.
>> >> > pcmcia: This interface will soon be removed from the kernel; please
>> >> expect breakage unless you upgrade to new tools.
>> >> > pcmcia: see
>> >> http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for
>> >> details.
>> >> > cs: IO port probe 0xc00-0xcff: clean.
>> >> > cs: IO port probe 0x820-0x8ff: clean.
>> >> > cs: IO port probe 0x800-0x80f: clean.
>> >> > cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
>> >> > cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
>> >> > cs: IO port probe 0xa00-0xaff: clean.
>> >> > 8139too Fast Ethernet driver 0.9.27
>> >> > PCI: Found IRQ 3 for device 0000:02:0b.0
>> >> > PCI: Sharing IRQ 3 with 0000:00:1d.1
>> >> > eth0: RealTek RTL8139 at 0xc800, 00:03:0d:14:95:c4, IRQ 3
>> >> > eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
>> >> > ieee1394: Initialized config rom entry `ip1394'
>> >> > PCI: Found IRQ 5 for device 0000:02:0a.0
>> >> > PCI: Sharing IRQ 5 with 0000:00:1d.2
>> >> > PCI: Sharing IRQ 5 with 0000:00:1f.1
>> >> > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5]
>> >> MMIO=[ffdff800-ffdfffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
>> >> > PCI: Found IRQ 4 for device 0000:00:1f.5
>> >> > PCI: Sharing IRQ 4 with 0000:00:1f.3
>> >> > PCI: Sharing IRQ 4 with 0000:00:1f.6
>> >> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
>> >> > PCI: Setting latency timer of device 0000:00:1f.5 to 64
>> >> > intel8x0_measure_ac97_clock: measured 55427 usecs
>> >> > intel8x0: clocking to 48000
>> >> > ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00030d4975701d84]
>> >> > i8xx TCO timer: initialized (0x0860). heartbeat=30 sec (nowayout=0)
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > agpgart: Detected an Intel 865 Chipset.
>> >> > agpgart: AGP aperture is 64M @ 0xf8000000
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > shpchp: Unknown symbol acpi_get_name
>> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> > kobject_register failed for ehci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver
>> >> (PCI)
>> >> > kobject_register failed for ohci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c032636c>] bus_add_driver+0x5c/0xa0
>> >> >  [<c0326e37>] driver_register+0x57/0x90
>> >> >  [<c02ea732>] __pci_register_driver+0x52/0x80
>> >> >  [<f8ecf02e>] ohci_hcd_pci_init+0x2e/0x35 [ohci_hcd]
>> >> >  [<c012e6e2>] sys_init_module+0x102/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for uhci_hcd (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > kobject_register failed for usb_storage (-17)
>> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
>> >> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
>> >> > NET: Registered protocol family 10
>> >> > lo: Disabled Privacy Extensions
>> >> > IPv6 over IPv4 tunneling driver
>> >> > eth0: no IPv6 routers present
>> >>
>> >>
>> >
>> >
>>
>>
> 
> ------------------------------------------------------------------------
> 
> ./log/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -nq xeno_nucleus
> ./log/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_native
> ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_rtdm
> ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_timerbench
> ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/usr/xenomai/bin/latency
> ./adm/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -nq xeno_nucleus
> ./adm/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_native
> ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_rtdm
> ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_timerbench
> ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/usr/xenomai/bin/latency
> ./log/syslog:Feb 22 13:21:38 (none) kernel: I-pipe: Domain Xenomai registered.
> ./log/syslog:Feb 22 13:21:38 (none) kernel: Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
> ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: hal/x86 started.
> ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: real-time nucleus v2.3 (Baroque) loaded.
> ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting native API services.
> ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting POSIX services.
> ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting RTDM services.
> ./log/dmesg:I-pipe: Domain Xenomai registered.
> ./log/dmesg:Xenomai: hal/x86 started.
> ./log/dmesg:Xenomai: real-time nucleus v2.3 (Baroque) loaded.
> ./log/dmesg:Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
> ./log/dmesg:Xenomai: starting native API services.
> ./log/dmesg:Xenomai: starting POSIX services.
> ./log/dmesg:Xenomai: starting RTDM services.
> ./adm/syslog:Feb 22 13:21:38 (none) kernel: I-pipe: Domain Xenomai registered.
> ./adm/syslog:Feb 22 13:21:38 (none) kernel: Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
> ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: hal/x86 started.
> ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: real-time nucleus v2.3 (Baroque) loaded.
> ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting native API services.
> ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting POSIX services.
> ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting RTDM services.
> ./adm/dmesg:I-pipe: Domain Xenomai registered.
> ./adm/dmesg:Xenomai: hal/x86 started.
> ./adm/dmesg:Xenomai: real-time nucleus v2.3 (Baroque) loaded.
> ./adm/dmesg:Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
> ./adm/dmesg:Xenomai: starting native API services.
> ./adm/dmesg:Xenomai: starting POSIX services.
> ./adm/dmesg:Xenomai: starting RTDM services.

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

Hi,

This is a bit better.

/proc/rtcan/rtcan0/info


Device     rtcan0
Controller <virtual>
Board      <virtual>
Clock-Hz   0
Baudrate   undefined
Bit-time   brp=0 prop_seg=0 phase_seg1=0 phase_seg2=0 sjw=0 sam=0
Ctrl-Mode
State      stopped
TX-Counter 0
RX-Counter 0
Errors     0
Refcount   0

for rtcan1

Device     rtcan1
Controller <virtual>
Board      <virtual>
Clock-Hz   0
Baudrate   undefined
Bit-time   brp=0 prop_seg=0 phase_seg1=0 phase_seg2=0 sjw=0 sam=0
Ctrl-Mode
State      stopped
TX-Counter 0
RX-Counter 0
Errors     0
Refcount   0


And after ./rtcanconfig rtcan0 --baudrate=500000 start

Device     rtcan0
Controller <virtual>
Board      <virtual>
Clock-Hz   0
Baudrate   undefined
Bit-time   brp=0 prop_seg=0 phase_seg1=0 phase_seg2=0 sjw=0 sam=0
Ctrl-Mode
State      active
TX-Counter 0
RX-Counter 0
Errors     0
Refcount   0

Why is the Baudrate undefined? I thought rtconfig should set this to 500000 ?

Is this all fine now? I oculd have sworn that I checked proc/rtcan
after I had recompiled the kernel with the virtual driver.

Anyhow. Is there a small program that I can compile to test the
virtual can with? I presume i can send it messages with rtcansend and
read the messages with rtcanrecieve?

I still have the outstanding question of what the module will be
called for the PEAK CAN dongle. I have to find it after make modules
to squirrle it away so i can load it after booting due to the
complications with my live distribution.  You said that I cannot build
that into the kernel statically correct? Can it be loaded without the
actual device being connected?

Maybe a small suggestion. Would it not be better to have the virtual
can driver built into the kernel by default. As a new user I did not
select it, saw no reason to.


Thanks.

Roland.


On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> roland Tollenaar wrote:
> > Hi Wolfgang,
> >
> > I did this
> >
> > #/var> grep -r "Xenomai" ./  >> dmesg.txt
> >
> > I found what you are looking for you will find it in the message attached.
> >
> > I did the same for rtcan which should yield the last 4 lines
> >
> > and found this:
> >
> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan0
> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan0: VIRT driver loaded
> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan1
> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan1: VIRT driver loaded
> > ./log/dmesg:rtcan: registered rtcan0
> > ./log/dmesg:rtcan0: VIRT driver loaded
> > ./log/dmesg:rtcan: registered rtcan1
> > ./log/dmesg:rtcan1: VIRT driver loaded
> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan0
> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan0: VIRT driver loaded
> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan1
> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan1: VIRT driver loaded
> > ./adm/dmesg:rtcan: registered rtcan0
> > ./adm/dmesg:rtcan0: VIRT driver loaded
> > ./adm/dmesg:rtcan: registered rtcan1
> > ./adm/dmesg:rtcan1: VIRT driver loaded
> >
> >
> > Hope this helps us?
>
> OK, now, what is the output of /proc/rtcan?
>
> >
> > Regards,
> >
> > Roland
> >
> >
> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> roland Tollenaar wrote:
> >> > Hi Wolfgang,
> >> >
> >> > sorry to ask a stupid question here but where would I find the complete
> >> > boot log
> >> >
> >> > I am checking /var/log/
> >> >
> >> > but am not sure which one you would want?
> >>
> >> Output of "dmesg" please or the log of your console output. You should
> >> find lines similar to the following:
> >>
> >> I-pipe: Domain Xenomai registered.
> >> Xenomai: hal/powerpc started.
> >> Xenomai: real-time nucleus v2.4-devel (Bells Of Lal) loaded.
> >> Xenomai: starting native API services.
> >> Xenomai: starting POSIX services.
> >> Xenomai: starting RTDM services.
> >> RT-Socket-CAN 0.20.2 - (C) 2006 RT-Socket-CAN Development Team
> >> rtcan: registered rtcan0
> >> rtcan0: VIRT driver loaded
> >> rtcan: registered rtcan1
> >> rtcan1: VIRT driver loaded
> >>
> >> >
> >> > Xenomai itself must be running because the the programs in the
> >> > testsuite seem to be working.
> >> >
> >> > Roland
> >> >
> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> >> roland Tollenaar wrote:
> >> >> > Hi,
> >> >> >
> >> >> >>
> >> >> >> Without device it will not register anyhow and see above.
> >> >> >>
> >> >> >
> >> >> > I have now built the kernel with the virtual driver statically built
> >> >> > into it. No difference still no devices.
> >> >> >
> >> >> >>
> >> >> >> The driver for the dongle will not start properly when statically
> >> >> linked
> >> >> >> into the kernel. There should be a log message, though.
> >> >> >>
> >> >> > No log message unless I am missing something. What is the module
> >> >> > called? After the
> >> >> > make modules in the kernel building process I will have to find
> >> it and
> >> >> > store it somewhere I will try loading it manually when the new
> >> kernel
> >> >> > is booted.
> >> >> >
> >> >> > The virtual driver I can build in statically?
> >> >> >
> >> >> >
> >> >> >>
> >> >> >> Can you post the compete dmesg output?
> >> >> >>
> >> >> >
> >> >> > It is attached as a txt file. The errors regarding ehci, ohci, uhci
> >> >> > and mass_storage are results of trying to load modules that I have
> >> >> > statically built into the kernel.
> >> >>
> >> >> I'm missing Xenomai related messages? Could you send the complete boot
> >> >> log please.
> >> >>
> >> >> Wolfgang.
> >> >>
> >> >> >
> >> >> > Regards,
> >> >> >
> >> >> > Roland
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >> > I have checked the .config for the kernel build and CAN is
> >> >> statically
> >> >> >> > built into it.
> >> >> >> >
> >> >> >> > I would prefer to statically build these things into the kernel
> >> >> due to
> >> >> >> > unwieldiness of my ditribution. If this is not possible I will
> >> make
> >> >> >> > modules. But is this the cause of problem I am having?
> >> >> >> > I have no device hooked to my system (PEAK dongle on its way) and
> >> >> the
> >> >> >> > virtual driver and TX loopback ability  has been excluded from
> >> the
> >> >> >> > kernel build. Is this possibly why i have no devices listed in
> >> >> >> > proc/rtcan/devices?
> >> >> >> Wolfgang.
> >> >> >>
> >> >> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> >> >> >> roland Tollenaar wrote:
> >> >> >> >> > Hi Jan,
> >> >> >> >> >
> >> >> >> >> >>
> >> >> >> >> >> rtcanX are networking devices, but only visible in the
> >> >> context of
> >> >> >> >> >> RTDM/AF_CAN.
> >> >> >> >> > What is this?
> >> >> >> >> >
> >> >> >> >> > To enable them, use rtcanconfig as explained in the README.
> >> >> >> >> > Which README are you referring to? The only one I know of that
> >> >> says
> >> >> >> >> > something about rtcanconfig is in /src/utils/can and it
> >> does not
> >> >> >> >> > explain how to use ctrlmode and bittime. There is an example
> >> >> in it
> >> >> >> >> >
> >> >> >> >> > rtcanconfig rtcan0 --baudrate=125000 start.
> >> >> >> >> >
> >> >> >> >> > If I try
> >> >> >> >> >
> >> >> >> >> > rtcanconfig rtcan0 --baudrate=125000 start
> >> >> >> >> >
> >> >> >> >> > I get:
> >> >> >> >> >
> >> >> >> >> > "Can't get interface index for rtcan0, code=-19"
> >> >> >> >> >
> >> >> >> >> > Any idea what is wrong?
> >> >> >> >>
> >> >> >> >> Your devices have not yet show up on your system. I guess there
> >> >> is no
> >> >> >> >> entry in /proc/rtcan/devices. Check your boot log.
> >> >> >> >>
> >> >> >> >> Wolfgang.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >> ------------------------------------------------------------------------
> >> >> >
> >> >> > veReady SeekComplete Error }
> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> >> LastFailedSense=0x05 }
> >> >> > ide: failed opcode was: unknown
> >> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
> >> >> Error }
> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> >> LastFailedSense=0x05 }
> >> >> > ide: failed opcode was: unknown
> >> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
> >> >> Error }
> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> >> LastFailedSense=0x05 }
> >> >> > ide: failed opcode was: unknown
> >> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
> >> >> Error }
> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> >> LastFailedSense=0x05 }
> >> >> > ide: failed opcode was: unknown
> >> >> > UDF-fs: No partition found (1)
> >> >> > XFS: bad magic number
> >> >> > XFS: SB validate failed
> >> >> > NTFS volume version 3.1.
> >> >> > spurious 8259A interrupt: IRQ7.
> >> >> > UDF-fs: No partition found (1)
> >> >> > XFS: bad magic number
> >> >> > XFS: SB validate failed
> >> >> > Linux agpgart interface v0.101 (c) Dave Jones
> >> >> > fuse init (API version 7.6)
> >> >> > NTFS volume version 3.1.
> >> >> > input: PS/2 Synaptics TouchPad as /class/input/input1
> >> >> > Intel ISA PCIC probe: not found.
> >> >> > Databook TCIC-2 PCMCIA probe: not found.
> >> >> > PCI: Found IRQ 4 for device 0000:02:03.0
> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.3
> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.5
> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.6
> >> >> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
> >> >> > Yenta: CardBus bridge found at 0000:02:03.0 [1584:3000]
> >> >> > Yenta: adjusting diagnostic: 40 -> 60
> >> >> > Yenta: Enabling burst memory read transactions
> >> >> > Yenta: Using CSCINT to route CSC interrupts to PCI
> >> >> > Yenta: Routing CardBus interrupts to PCI
> >> >> > Yenta TI: socket 0000:02:03.0, mfunc 0x005c1d22, devctl 0x44
> >> >> > Yenta TI: socket 0000:02:03.0 probing PCI interrupt failed, trying
> >> >> to fix
> >> >> > Yenta TI: socket 0000:02:03.0 no PCI interrupts. Fish. Please
> >> report.
> >> >> > Yenta: no PCI IRQ, CardBus support disabled for this socket.
> >> >> > Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
> >> >> > Yenta: ISA IRQ mask 0x02c0, PCI irq 0
> >> >> > Socket status: 30000006
> >> >> > pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff
> >> >> > cs: IO port probe 0xc000-0xcfff: clean.
> >> >> > pcmcia: parent PCI bridge Memory window: 0xffd00000 - 0xffdfffff
> >> >> > pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x89ffffff
> >> >> > pcmcia: Detected deprecated PCMCIA ioctl usage.
> >> >> > pcmcia: This interface will soon be removed from the kernel; please
> >> >> expect breakage unless you upgrade to new tools.
> >> >> > pcmcia: see
> >> >> http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for
> >> >> details.
> >> >> > cs: IO port probe 0xc00-0xcff: clean.
> >> >> > cs: IO port probe 0x820-0x8ff: clean.
> >> >> > cs: IO port probe 0x800-0x80f: clean.
> >> >> > cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
> >> >> > cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
> >> >> > cs: IO port probe 0xa00-0xaff: clean.
> >> >> > 8139too Fast Ethernet driver 0.9.27
> >> >> > PCI: Found IRQ 3 for device 0000:02:0b.0
> >> >> > PCI: Sharing IRQ 3 with 0000:00:1d.1
> >> >> > eth0: RealTek RTL8139 at 0xc800, 00:03:0d:14:95:c4, IRQ 3
> >> >> > eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
> >> >> > ieee1394: Initialized config rom entry `ip1394'
> >> >> > PCI: Found IRQ 5 for device 0000:02:0a.0
> >> >> > PCI: Sharing IRQ 5 with 0000:00:1d.2
> >> >> > PCI: Sharing IRQ 5 with 0000:00:1f.1
> >> >> > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5]
> >> >> MMIO=[ffdff800-ffdfffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
> >> >> > PCI: Found IRQ 4 for device 0000:00:1f.5
> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.3
> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.6
> >> >> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
> >> >> > PCI: Setting latency timer of device 0000:00:1f.5 to 64
> >> >> > intel8x0_measure_ac97_clock: measured 55427 usecs
> >> >> > intel8x0: clocking to 48000
> >> >> > ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00030d4975701d84]
> >> >> > i8xx TCO timer: initialized (0x0860). heartbeat=30 sec (nowayout=0)
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > agpgart: Detected an Intel 865 Chipset.
> >> >> > agpgart: AGP aperture is 64M @ 0xf8000000
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver
> >> >> (PCI)
> >> >> > kobject_register failed for ohci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c032636c>] bus_add_driver+0x5c/0xa0
> >> >> >  [<c0326e37>] driver_register+0x57/0x90
> >> >> >  [<c02ea732>] __pci_register_driver+0x52/0x80
> >> >> >  [<f8ecf02e>] ohci_hcd_pci_init+0x2e/0x35 [ohci_hcd]
> >> >> >  [<c012e6e2>] sys_init_module+0x102/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > kobject_register failed for usb_storage (-17)
> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> >> >> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> >> >> > NET: Registered protocol family 10
> >> >> > lo: Disabled Privacy Extensions
> >> >> > IPv6 over IPv4 tunneling driver
> >> >> > eth0: no IPv6 routers present
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> > ------------------------------------------------------------------------
> >
> > ./log/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -nq xeno_nucleus
> > ./log/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_native
> > ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_rtdm
> > ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_timerbench
> > ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/usr/xenomai/bin/latency
> > ./adm/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -nq xeno_nucleus
> > ./adm/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_native
> > ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_rtdm
> > ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/sbin/modprobe -n xeno_timerbench
> > ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; COMMAND=/usr/xenomai/bin/latency
> > ./log/syslog:Feb 22 13:21:38 (none) kernel: I-pipe: Domain Xenomai registered.
> > ./log/syslog:Feb 22 13:21:38 (none) kernel: Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: hal/x86 started.
> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: real-time nucleus v2.3 (Baroque) loaded.
> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting native API services.
> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting POSIX services.
> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting RTDM services.
> > ./log/dmesg:I-pipe: Domain Xenomai registered.
> > ./log/dmesg:Xenomai: hal/x86 started.
> > ./log/dmesg:Xenomai: real-time nucleus v2.3 (Baroque) loaded.
> > ./log/dmesg:Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
> > ./log/dmesg:Xenomai: starting native API services.
> > ./log/dmesg:Xenomai: starting POSIX services.
> > ./log/dmesg:Xenomai: starting RTDM services.
> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: I-pipe: Domain Xenomai registered.
> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: hal/x86 started.
> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: real-time nucleus v2.3 (Baroque) loaded.
> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting native API services.
> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting POSIX services.
> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting RTDM services.
> > ./adm/dmesg:I-pipe: Domain Xenomai registered.
> > ./adm/dmesg:Xenomai: hal/x86 started.
> > ./adm/dmesg:Xenomai: real-time nucleus v2.3 (Baroque) loaded.
> > ./adm/dmesg:Xenomai: SMI-enabled chipset found but SMI workaround not enabled (check
> > ./adm/dmesg:Xenomai: starting native API services.
> > ./adm/dmesg:Xenomai: starting POSIX services.
> > ./adm/dmesg:Xenomai: starting RTDM services.
>
>
>

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

roland Tollenaar wrote:
> Hi,
> 
> This is a bit better.
> 
> /proc/rtcan/rtcan0/info
> 
> 
> Device     rtcan0
> Controller <virtual>
> Board      <virtual>
> Clock-Hz   0
> Baudrate   undefined
> Bit-time   brp=0 prop_seg=0 phase_seg1=0 phase_seg2=0 sjw=0 sam=0
> Ctrl-Mode
> State      stopped
> TX-Counter 0
> RX-Counter 0
> Errors     0
> Refcount   0
> 
> for rtcan1
> 
> Device     rtcan1
> Controller <virtual>
> Board      <virtual>
> Clock-Hz   0
> Baudrate   undefined
> Bit-time   brp=0 prop_seg=0 phase_seg1=0 phase_seg2=0 sjw=0 sam=0
> Ctrl-Mode
> State      stopped
> TX-Counter 0
> RX-Counter 0
> Errors     0
> Refcount   0

And /proc/rtcan/devices is also useful.

> And after ./rtcanconfig rtcan0 --baudrate=500000 start
> 
> Device     rtcan0
> Controller <virtual>
> Board      <virtual>
> Clock-Hz   0
> Baudrate   undefined
> Bit-time   brp=0 prop_seg=0 phase_seg1=0 phase_seg2=0 sjw=0 sam=0
> Ctrl-Mode
> State      active
> TX-Counter 0
> RX-Counter 0
> Errors     0
> Refcount   0
> 
> Why is the Baudrate undefined? I thought rtconfig should set this to 
> 500000 ?

Because it's a virtual devices just routing the messages to the other
virtual devices.

> Is this all fine now? I oculd have sworn that I checked proc/rtcan
> after I had recompiled the kernel with the virtual driver.

Looks good.

> 
> Anyhow. Is there a small program that I can compile to test the
> virtual can with? I presume i can send it messages with rtcansend and
> read the messages with rtcanrecieve?

src/utils/can/README?

> I still have the outstanding question of what the module will be
> called for the PEAK CAN dongle. I have to find it after make modules
> to squirrle it away so i can load it after booting due to the
> complications with my live distribution.  You said that I cannot build
> that into the kernel statically correct? Can it be loaded without the
> actual device being connected?

I said, it can be statically linked into the kernel but it will not work 
(without modification, we can discuss this issue when you have a PCAN 
dongle). What should a driver without hardware be good for?

> Maybe a small suggestion. Would it not be better to have the virtual
> can driver built into the kernel by default. As a new user I did not
> select it, saw no reason to.

Might be useful, indeed. BTW: there is a help available for each 
configuration option?

Wolfgang.

> Thanks.
> 
> Roland.
> 
> 
> On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> roland Tollenaar wrote:
>> > Hi Wolfgang,
>> >
>> > I did this
>> >
>> > #/var> grep -r "Xenomai" ./  >> dmesg.txt
>> >
>> > I found what you are looking for you will find it in the message 
>> attached.
>> >
>> > I did the same for rtcan which should yield the last 4 lines
>> >
>> > and found this:
>> >
>> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan0
>> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan0: VIRT driver loaded
>> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan1
>> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan1: VIRT driver loaded
>> > ./log/dmesg:rtcan: registered rtcan0
>> > ./log/dmesg:rtcan0: VIRT driver loaded
>> > ./log/dmesg:rtcan: registered rtcan1
>> > ./log/dmesg:rtcan1: VIRT driver loaded
>> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan0
>> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan0: VIRT driver loaded
>> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan1
>> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan1: VIRT driver loaded
>> > ./adm/dmesg:rtcan: registered rtcan0
>> > ./adm/dmesg:rtcan0: VIRT driver loaded
>> > ./adm/dmesg:rtcan: registered rtcan1
>> > ./adm/dmesg:rtcan1: VIRT driver loaded
>> >
>> >
>> > Hope this helps us?
>>
>> OK, now, what is the output of /proc/rtcan?
>>
>> >
>> > Regards,
>> >
>> > Roland
>> >
>> >
>> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> >> roland Tollenaar wrote:
>> >> > Hi Wolfgang,
>> >> >
>> >> > sorry to ask a stupid question here but where would I find the 
>> complete
>> >> > boot log
>> >> >
>> >> > I am checking /var/log/
>> >> >
>> >> > but am not sure which one you would want?
>> >>
>> >> Output of "dmesg" please or the log of your console output. You should
>> >> find lines similar to the following:
>> >>
>> >> I-pipe: Domain Xenomai registered.
>> >> Xenomai: hal/powerpc started.
>> >> Xenomai: real-time nucleus v2.4-devel (Bells Of Lal) loaded.
>> >> Xenomai: starting native API services.
>> >> Xenomai: starting POSIX services.
>> >> Xenomai: starting RTDM services.
>> >> RT-Socket-CAN 0.20.2 - (C) 2006 RT-Socket-CAN Development Team
>> >> rtcan: registered rtcan0
>> >> rtcan0: VIRT driver loaded
>> >> rtcan: registered rtcan1
>> >> rtcan1: VIRT driver loaded
>> >>
>> >> >
>> >> > Xenomai itself must be running because the the programs in the
>> >> > testsuite seem to be working.
>> >> >
>> >> > Roland
>> >> >
>> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> >> >> roland Tollenaar wrote:
>> >> >> > Hi,
>> >> >> >
>> >> >> >>
>> >> >> >> Without device it will not register anyhow and see above.
>> >> >> >>
>> >> >> >
>> >> >> > I have now built the kernel with the virtual driver statically 
>> built
>> >> >> > into it. No difference still no devices.
>> >> >> >
>> >> >> >>
>> >> >> >> The driver for the dongle will not start properly when 
>> statically
>> >> >> linked
>> >> >> >> into the kernel. There should be a log message, though.
>> >> >> >>
>> >> >> > No log message unless I am missing something. What is the module
>> >> >> > called? After the
>> >> >> > make modules in the kernel building process I will have to find
>> >> it and
>> >> >> > store it somewhere I will try loading it manually when the new
>> >> kernel
>> >> >> > is booted.
>> >> >> >
>> >> >> > The virtual driver I can build in statically?
>> >> >> >
>> >> >> >
>> >> >> >>
>> >> >> >> Can you post the compete dmesg output?
>> >> >> >>
>> >> >> >
>> >> >> > It is attached as a txt file. The errors regarding ehci, ohci, 
>> uhci
>> >> >> > and mass_storage are results of trying to load modules that I 
>> have
>> >> >> > statically built into the kernel.
>> >> >>
>> >> >> I'm missing Xenomai related messages? Could you send the 
>> complete boot
>> >> >> log please.
>> >> >>
>> >> >> Wolfgang.
>> >> >>
>> >> >> >
>> >> >> > Regards,
>> >> >> >
>> >> >> > Roland
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >> > I have checked the .config for the kernel build and CAN is
>> >> >> statically
>> >> >> >> > built into it.
>> >> >> >> >
>> >> >> >> > I would prefer to statically build these things into the 
>> kernel
>> >> >> due to
>> >> >> >> > unwieldiness of my ditribution. If this is not possible I will
>> >> make
>> >> >> >> > modules. But is this the cause of problem I am having?
>> >> >> >> > I have no device hooked to my system (PEAK dongle on its 
>> way) and
>> >> >> the
>> >> >> >> > virtual driver and TX loopback ability  has been excluded from
>> >> the
>> >> >> >> > kernel build. Is this possibly why i have no devices listed in
>> >> >> >> > proc/rtcan/devices?
>> >> >> >> Wolfgang.
>> >> >> >>
>> >> >> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> >> >> >> >> roland Tollenaar wrote:
>> >> >> >> >> > Hi Jan,
>> >> >> >> >> >
>> >> >> >> >> >>
>> >> >> >> >> >> rtcanX are networking devices, but only visible in the
>> >> >> context of
>> >> >> >> >> >> RTDM/AF_CAN.
>> >> >> >> >> > What is this?
>> >> >> >> >> >
>> >> >> >> >> > To enable them, use rtcanconfig as explained in the README.
>> >> >> >> >> > Which README are you referring to? The only one I know 
>> of that
>> >> >> says
>> >> >> >> >> > something about rtcanconfig is in /src/utils/can and it
>> >> does not
>> >> >> >> >> > explain how to use ctrlmode and bittime. There is an 
>> example
>> >> >> in it
>> >> >> >> >> >
>> >> >> >> >> > rtcanconfig rtcan0 --baudrate=125000 start.
>> >> >> >> >> >
>> >> >> >> >> > If I try
>> >> >> >> >> >
>> >> >> >> >> > rtcanconfig rtcan0 --baudrate=125000 start
>> >> >> >> >> >
>> >> >> >> >> > I get:
>> >> >> >> >> >
>> >> >> >> >> > "Can't get interface index for rtcan0, code=-19"
>> >> >> >> >> >
>> >> >> >> >> > Any idea what is wrong?
>> >> >> >> >>
>> >> >> >> >> Your devices have not yet show up on your system. I guess 
>> there
>> >> >> is no
>> >> >> >> >> entry in /proc/rtcan/devices. Check your boot log.
>> >> >> >> >>
>> >> >> >> >> Wolfgang.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >>
>> >> 
>> ------------------------------------------------------------------------
>> >> >> >
>> >> >> > veReady SeekComplete Error }
>> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
>> >> >> LastFailedSense=0x05 }
>> >> >> > ide: failed opcode was: unknown
>> >> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
>> >> >> Error }
>> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
>> >> >> LastFailedSense=0x05 }
>> >> >> > ide: failed opcode was: unknown
>> >> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
>> >> >> Error }
>> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
>> >> >> LastFailedSense=0x05 }
>> >> >> > ide: failed opcode was: unknown
>> >> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
>> >> >> Error }
>> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
>> >> >> LastFailedSense=0x05 }
>> >> >> > ide: failed opcode was: unknown
>> >> >> > UDF-fs: No partition found (1)
>> >> >> > XFS: bad magic number
>> >> >> > XFS: SB validate failed
>> >> >> > NTFS volume version 3.1.
>> >> >> > spurious 8259A interrupt: IRQ7.
>> >> >> > UDF-fs: No partition found (1)
>> >> >> > XFS: bad magic number
>> >> >> > XFS: SB validate failed
>> >> >> > Linux agpgart interface v0.101 (c) Dave Jones
>> >> >> > fuse init (API version 7.6)
>> >> >> > NTFS volume version 3.1.
>> >> >> > input: PS/2 Synaptics TouchPad as /class/input/input1
>> >> >> > Intel ISA PCIC probe: not found.
>> >> >> > Databook TCIC-2 PCMCIA probe: not found.
>> >> >> > PCI: Found IRQ 4 for device 0000:02:03.0
>> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.3
>> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.5
>> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.6
>> >> >> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
>> >> >> > Yenta: CardBus bridge found at 0000:02:03.0 [1584:3000]
>> >> >> > Yenta: adjusting diagnostic: 40 -> 60
>> >> >> > Yenta: Enabling burst memory read transactions
>> >> >> > Yenta: Using CSCINT to route CSC interrupts to PCI
>> >> >> > Yenta: Routing CardBus interrupts to PCI
>> >> >> > Yenta TI: socket 0000:02:03.0, mfunc 0x005c1d22, devctl 0x44
>> >> >> > Yenta TI: socket 0000:02:03.0 probing PCI interrupt failed, 
>> trying
>> >> >> to fix
>> >> >> > Yenta TI: socket 0000:02:03.0 no PCI interrupts. Fish. Please
>> >> report.
>> >> >> > Yenta: no PCI IRQ, CardBus support disabled for this socket.
>> >> >> > Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
>> >> >> > Yenta: ISA IRQ mask 0x02c0, PCI irq 0
>> >> >> > Socket status: 30000006
>> >> >> > pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff
>> >> >> > cs: IO port probe 0xc000-0xcfff: clean.
>> >> >> > pcmcia: parent PCI bridge Memory window: 0xffd00000 - 0xffdfffff
>> >> >> > pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x89ffffff
>> >> >> > pcmcia: Detected deprecated PCMCIA ioctl usage.
>> >> >> > pcmcia: This interface will soon be removed from the kernel; 
>> please
>> >> >> expect breakage unless you upgrade to new tools.
>> >> >> > pcmcia: see
>> >> >> http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for
>> >> >> details.
>> >> >> > cs: IO port probe 0xc00-0xcff: clean.
>> >> >> > cs: IO port probe 0x820-0x8ff: clean.
>> >> >> > cs: IO port probe 0x800-0x80f: clean.
>> >> >> > cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
>> >> >> > cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
>> >> >> > cs: IO port probe 0xa00-0xaff: clean.
>> >> >> > 8139too Fast Ethernet driver 0.9.27
>> >> >> > PCI: Found IRQ 3 for device 0000:02:0b.0
>> >> >> > PCI: Sharing IRQ 3 with 0000:00:1d.1
>> >> >> > eth0: RealTek RTL8139 at 0xc800, 00:03:0d:14:95:c4, IRQ 3
>> >> >> > eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
>> >> >> > ieee1394: Initialized config rom entry `ip1394'
>> >> >> > PCI: Found IRQ 5 for device 0000:02:0a.0
>> >> >> > PCI: Sharing IRQ 5 with 0000:00:1d.2
>> >> >> > PCI: Sharing IRQ 5 with 0000:00:1f.1
>> >> >> > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5]
>> >> >> MMIO=[ffdff800-ffdfffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
>> >> >> > PCI: Found IRQ 4 for device 0000:00:1f.5
>> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.3
>> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.6
>> >> >> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
>> >> >> > PCI: Setting latency timer of device 0000:00:1f.5 to 64
>> >> >> > intel8x0_measure_ac97_clock: measured 55427 usecs
>> >> >> > intel8x0: clocking to 48000
>> >> >> > ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00030d4975701d84]
>> >> >> > i8xx TCO timer: initialized (0x0860). heartbeat=30 sec 
>> (nowayout=0)
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > agpgart: Detected an Intel 865 Chipset.
>> >> >> > agpgart: AGP aperture is 64M @ 0xf8000000
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > shpchp: Unknown symbol acpi_get_name
>> >> >> > shpchp: Unknown symbol acpi_evaluate_object
>> >> >> > kobject_register failed for ehci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) 
>> Driver
>> >> >> (PCI)
>> >> >> > kobject_register failed for ohci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c032636c>] bus_add_driver+0x5c/0xa0
>> >> >> >  [<c0326e37>] driver_register+0x57/0x90
>> >> >> >  [<c02ea732>] __pci_register_driver+0x52/0x80
>> >> >> >  [<f8ecf02e>] ohci_hcd_pci_init+0x2e/0x35 [ohci_hcd]
>> >> >> >  [<c012e6e2>] sys_init_module+0x102/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for uhci_hcd (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > kobject_register failed for usb_storage (-17)
>> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
>> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
>> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
>> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
>> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
>> >> >> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
>> >> >> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
>> >> >> > NET: Registered protocol family 10
>> >> >> > lo: Disabled Privacy Extensions
>> >> >> > IPv6 over IPv4 tunneling driver
>> >> >> > eth0: no IPv6 routers present
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> > 
>> ------------------------------------------------------------------------
>> >
>> > ./log/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; 
>> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; 
>> COMMAND=/sbin/modprobe -nq xeno_nucleus
>> > ./log/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; 
>> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; 
>> COMMAND=/sbin/modprobe -n xeno_native
>> > ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; 
>> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; 
>> COMMAND=/sbin/modprobe -n xeno_rtdm
>> > ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; 
>> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; 
>> COMMAND=/sbin/modprobe -n xeno_timerbench
>> > ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; 
>> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; 
>> COMMAND=/usr/xenomai/bin/latency
>> > ./adm/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; 
>> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; 
>> COMMAND=/sbin/modprobe -nq xeno_nucleus
>> > ./adm/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ; 
>> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; 
>> COMMAND=/sbin/modprobe -n xeno_native
>> > ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; 
>> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; 
>> COMMAND=/sbin/modprobe -n xeno_rtdm
>> > ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; 
>> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; 
>> COMMAND=/sbin/modprobe -n xeno_timerbench
>> > ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ; 
>> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ; 
>> COMMAND=/usr/xenomai/bin/latency
>> > ./log/syslog:Feb 22 13:21:38 (none) kernel: I-pipe: Domain Xenomai 
>> registered.
>> > ./log/syslog:Feb 22 13:21:38 (none) kernel: Xenomai: SMI-enabled 
>> chipset found but SMI workaround not enabled (check
>> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: hal/x86 started.
>> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: real-time 
>> nucleus v2.3 (Baroque) loaded.
>> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting 
>> native API services.
>> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting 
>> POSIX services.
>> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting RTDM 
>> services.
>> > ./log/dmesg:I-pipe: Domain Xenomai registered.
>> > ./log/dmesg:Xenomai: hal/x86 started.
>> > ./log/dmesg:Xenomai: real-time nucleus v2.3 (Baroque) loaded.
>> > ./log/dmesg:Xenomai: SMI-enabled chipset found but SMI workaround 
>> not enabled (check
>> > ./log/dmesg:Xenomai: starting native API services.
>> > ./log/dmesg:Xenomai: starting POSIX services.
>> > ./log/dmesg:Xenomai: starting RTDM services.
>> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: I-pipe: Domain Xenomai 
>> registered.
>> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: Xenomai: SMI-enabled 
>> chipset found but SMI workaround not enabled (check
>> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: hal/x86 started.
>> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: real-time 
>> nucleus v2.3 (Baroque) loaded.
>> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting 
>> native API services.
>> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting 
>> POSIX services.
>> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting RTDM 
>> services.
>> > ./adm/dmesg:I-pipe: Domain Xenomai registered.
>> > ./adm/dmesg:Xenomai: hal/x86 started.
>> > ./adm/dmesg:Xenomai: real-time nucleus v2.3 (Baroque) loaded.
>> > ./adm/dmesg:Xenomai: SMI-enabled chipset found but SMI workaround 
>> not enabled (check
>> > ./adm/dmesg:Xenomai: starting native API services.
>> > ./adm/dmesg:Xenomai: starting POSIX services.
>> > ./adm/dmesg:Xenomai: starting RTDM services.
>>
>>
>>
> 
> 

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

Hi Wolfgang,

> And /proc/rtcan/devices is also useful.

Device rtcan0 Baudrate undefined State active TXCounter 7 RXCounter 5 Errors 0
Device rtcan1 Baudrate undefined State stopped TXCounter 0 RXCounter 0 Errors 0

> > virtual can with? I presume i can send it messages with rtcansend and
> > read the messages with rtcanrecieve?
> src/utils/can/README?
Works. Can send and recieve messages on it. Interesting may be this:
If i send with rtcansend then in another console recieve the messages
will not display. I would have expected the messages to be in the
stack and display (depending how many messages the stack can hold).
Why is that expectation incorrect?

> > I still have the outstanding question of what the module will be
> > called for the PEAK CAN dongle. I have to find it after make modules
> > to squirrle it away so i can load it after booting due to the
> > complications with my live distribution.  You said that I cannot build
> > that into the kernel statically correct? Can it be loaded without the
> > actual device being connected?
>
> I said, it can be statically linked into the kernel but it will not work
> (without modification, we can discuss this issue when you have a PCAN
> dongle). What should a driver without hardware be good for?
Good question. On the other hand it would be useful to know which
module I have to
pick out and load. Then I can compile the kernel for that so long and
make a structure that loads it after booting. But that can be done
later too.

> > Maybe a small suggestion. Would it not be better to have the virtual
> > can driver built into the kernel by default. As a new user I did not
> > select it, saw no reason to.
>
> Might be useful, indeed. BTW: there is a help available for each
> configuration option?
There should be. I think I used the help. Will check again for you
when I change the configuration to load the PEAK driver as a module.

Roland.


>
> Wolfgang.
>
> > Thanks.
> >
> > Roland.
> >
> >
> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> roland Tollenaar wrote:
> >> > Hi Wolfgang,
> >> >
> >> > I did this
> >> >
> >> > #/var> grep -r "Xenomai" ./  >> dmesg.txt
> >> >
> >> > I found what you are looking for you will find it in the message
> >> attached.
> >> >
> >> > I did the same for rtcan which should yield the last 4 lines
> >> >
> >> > and found this:
> >> >
> >> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan0
> >> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan0: VIRT driver loaded
> >> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan1
> >> > ./log/syslog:Feb 22 13:21:38 (none) kernel: rtcan1: VIRT driver loaded
> >> > ./log/dmesg:rtcan: registered rtcan0
> >> > ./log/dmesg:rtcan0: VIRT driver loaded
> >> > ./log/dmesg:rtcan: registered rtcan1
> >> > ./log/dmesg:rtcan1: VIRT driver loaded
> >> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan0
> >> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan0: VIRT driver loaded
> >> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan: registered rtcan1
> >> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: rtcan1: VIRT driver loaded
> >> > ./adm/dmesg:rtcan: registered rtcan0
> >> > ./adm/dmesg:rtcan0: VIRT driver loaded
> >> > ./adm/dmesg:rtcan: registered rtcan1
> >> > ./adm/dmesg:rtcan1: VIRT driver loaded
> >> >
> >> >
> >> > Hope this helps us?
> >>
> >> OK, now, what is the output of /proc/rtcan?
> >>
> >> >
> >> > Regards,
> >> >
> >> > Roland
> >> >
> >> >
> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> >> roland Tollenaar wrote:
> >> >> > Hi Wolfgang,
> >> >> >
> >> >> > sorry to ask a stupid question here but where would I find the
> >> complete
> >> >> > boot log
> >> >> >
> >> >> > I am checking /var/log/
> >> >> >
> >> >> > but am not sure which one you would want?
> >> >>
> >> >> Output of "dmesg" please or the log of your console output. You should
> >> >> find lines similar to the following:
> >> >>
> >> >> I-pipe: Domain Xenomai registered.
> >> >> Xenomai: hal/powerpc started.
> >> >> Xenomai: real-time nucleus v2.4-devel (Bells Of Lal) loaded.
> >> >> Xenomai: starting native API services.
> >> >> Xenomai: starting POSIX services.
> >> >> Xenomai: starting RTDM services.
> >> >> RT-Socket-CAN 0.20.2 - (C) 2006 RT-Socket-CAN Development Team
> >> >> rtcan: registered rtcan0
> >> >> rtcan0: VIRT driver loaded
> >> >> rtcan: registered rtcan1
> >> >> rtcan1: VIRT driver loaded
> >> >>
> >> >> >
> >> >> > Xenomai itself must be running because the the programs in the
> >> >> > testsuite seem to be working.
> >> >> >
> >> >> > Roland
> >> >> >
> >> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> >> >> roland Tollenaar wrote:
> >> >> >> > Hi,
> >> >> >> >
> >> >> >> >>
> >> >> >> >> Without device it will not register anyhow and see above.
> >> >> >> >>
> >> >> >> >
> >> >> >> > I have now built the kernel with the virtual driver statically
> >> built
> >> >> >> > into it. No difference still no devices.
> >> >> >> >
> >> >> >> >>
> >> >> >> >> The driver for the dongle will not start properly when
> >> statically
> >> >> >> linked
> >> >> >> >> into the kernel. There should be a log message, though.
> >> >> >> >>
> >> >> >> > No log message unless I am missing something. What is the module
> >> >> >> > called? After the
> >> >> >> > make modules in the kernel building process I will have to find
> >> >> it and
> >> >> >> > store it somewhere I will try loading it manually when the new
> >> >> kernel
> >> >> >> > is booted.
> >> >> >> >
> >> >> >> > The virtual driver I can build in statically?
> >> >> >> >
> >> >> >> >
> >> >> >> >>
> >> >> >> >> Can you post the compete dmesg output?
> >> >> >> >>
> >> >> >> >
> >> >> >> > It is attached as a txt file. The errors regarding ehci, ohci,
> >> uhci
> >> >> >> > and mass_storage are results of trying to load modules that I
> >> have
> >> >> >> > statically built into the kernel.
> >> >> >>
> >> >> >> I'm missing Xenomai related messages? Could you send the
> >> complete boot
> >> >> >> log please.
> >> >> >>
> >> >> >> Wolfgang.
> >> >> >>
> >> >> >> >
> >> >> >> > Regards,
> >> >> >> >
> >> >> >> > Roland
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >
> >> >> >> >> > I have checked the .config for the kernel build and CAN is
> >> >> >> statically
> >> >> >> >> > built into it.
> >> >> >> >> >
> >> >> >> >> > I would prefer to statically build these things into the
> >> kernel
> >> >> >> due to
> >> >> >> >> > unwieldiness of my ditribution. If this is not possible I will
> >> >> make
> >> >> >> >> > modules. But is this the cause of problem I am having?
> >> >> >> >> > I have no device hooked to my system (PEAK dongle on its
> >> way) and
> >> >> >> the
> >> >> >> >> > virtual driver and TX loopback ability  has been excluded from
> >> >> the
> >> >> >> >> > kernel build. Is this possibly why i have no devices listed in
> >> >> >> >> > proc/rtcan/devices?
> >> >> >> >> Wolfgang.
> >> >> >> >>
> >> >> >> >> > On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
> >> >> >> >> >> roland Tollenaar wrote:
> >> >> >> >> >> > Hi Jan,
> >> >> >> >> >> >
> >> >> >> >> >> >>
> >> >> >> >> >> >> rtcanX are networking devices, but only visible in the
> >> >> >> context of
> >> >> >> >> >> >> RTDM/AF_CAN.
> >> >> >> >> >> > What is this?
> >> >> >> >> >> >
> >> >> >> >> >> > To enable them, use rtcanconfig as explained in the README.
> >> >> >> >> >> > Which README are you referring to? The only one I know
> >> of that
> >> >> >> says
> >> >> >> >> >> > something about rtcanconfig is in /src/utils/can and it
> >> >> does not
> >> >> >> >> >> > explain how to use ctrlmode and bittime. There is an
> >> example
> >> >> >> in it
> >> >> >> >> >> >
> >> >> >> >> >> > rtcanconfig rtcan0 --baudrate=125000 start.
> >> >> >> >> >> >
> >> >> >> >> >> > If I try
> >> >> >> >> >> >
> >> >> >> >> >> > rtcanconfig rtcan0 --baudrate=125000 start
> >> >> >> >> >> >
> >> >> >> >> >> > I get:
> >> >> >> >> >> >
> >> >> >> >> >> > "Can't get interface index for rtcan0, code=-19"
> >> >> >> >> >> >
> >> >> >> >> >> > Any idea what is wrong?
> >> >> >> >> >>
> >> >> >> >> >> Your devices have not yet show up on your system. I guess
> >> there
> >> >> >> is no
> >> >> >> >> >> entry in /proc/rtcan/devices. Check your boot log.
> >> >> >> >> >>
> >> >> >> >> >> Wolfgang.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >>
> >> >> >> >>
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >>
> >> ------------------------------------------------------------------------
> >> >> >> >
> >> >> >> > veReady SeekComplete Error }
> >> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> >> >> LastFailedSense=0x05 }
> >> >> >> > ide: failed opcode was: unknown
> >> >> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
> >> >> >> Error }
> >> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> >> >> LastFailedSense=0x05 }
> >> >> >> > ide: failed opcode was: unknown
> >> >> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
> >> >> >> Error }
> >> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> >> >> LastFailedSense=0x05 }
> >> >> >> > ide: failed opcode was: unknown
> >> >> >> > hdc: packet command error: status=0x51 { DriveReady SeekComplete
> >> >> >> Error }
> >> >> >> > hdc: packet command error: error=0x54 { AbortedCommand
> >> >> >> LastFailedSense=0x05 }
> >> >> >> > ide: failed opcode was: unknown
> >> >> >> > UDF-fs: No partition found (1)
> >> >> >> > XFS: bad magic number
> >> >> >> > XFS: SB validate failed
> >> >> >> > NTFS volume version 3.1.
> >> >> >> > spurious 8259A interrupt: IRQ7.
> >> >> >> > UDF-fs: No partition found (1)
> >> >> >> > XFS: bad magic number
> >> >> >> > XFS: SB validate failed
> >> >> >> > Linux agpgart interface v0.101 (c) Dave Jones
> >> >> >> > fuse init (API version 7.6)
> >> >> >> > NTFS volume version 3.1.
> >> >> >> > input: PS/2 Synaptics TouchPad as /class/input/input1
> >> >> >> > Intel ISA PCIC probe: not found.
> >> >> >> > Databook TCIC-2 PCMCIA probe: not found.
> >> >> >> > PCI: Found IRQ 4 for device 0000:02:03.0
> >> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.3
> >> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.5
> >> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.6
> >> >> >> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
> >> >> >> > Yenta: CardBus bridge found at 0000:02:03.0 [1584:3000]
> >> >> >> > Yenta: adjusting diagnostic: 40 -> 60
> >> >> >> > Yenta: Enabling burst memory read transactions
> >> >> >> > Yenta: Using CSCINT to route CSC interrupts to PCI
> >> >> >> > Yenta: Routing CardBus interrupts to PCI
> >> >> >> > Yenta TI: socket 0000:02:03.0, mfunc 0x005c1d22, devctl 0x44
> >> >> >> > Yenta TI: socket 0000:02:03.0 probing PCI interrupt failed,
> >> trying
> >> >> >> to fix
> >> >> >> > Yenta TI: socket 0000:02:03.0 no PCI interrupts. Fish. Please
> >> >> report.
> >> >> >> > Yenta: no PCI IRQ, CardBus support disabled for this socket.
> >> >> >> > Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
> >> >> >> > Yenta: ISA IRQ mask 0x02c0, PCI irq 0
> >> >> >> > Socket status: 30000006
> >> >> >> > pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff
> >> >> >> > cs: IO port probe 0xc000-0xcfff: clean.
> >> >> >> > pcmcia: parent PCI bridge Memory window: 0xffd00000 - 0xffdfffff
> >> >> >> > pcmcia: parent PCI bridge Memory window: 0x88000000 - 0x89ffffff
> >> >> >> > pcmcia: Detected deprecated PCMCIA ioctl usage.
> >> >> >> > pcmcia: This interface will soon be removed from the kernel;
> >> please
> >> >> >> expect breakage unless you upgrade to new tools.
> >> >> >> > pcmcia: see
> >> >> >> http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for
> >> >> >> details.
> >> >> >> > cs: IO port probe 0xc00-0xcff: clean.
> >> >> >> > cs: IO port probe 0x820-0x8ff: clean.
> >> >> >> > cs: IO port probe 0x800-0x80f: clean.
> >> >> >> > cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
> >> >> >> > cs: IO port probe 0x100-0x3af: excluding 0x378-0x37f
> >> >> >> > cs: IO port probe 0xa00-0xaff: clean.
> >> >> >> > 8139too Fast Ethernet driver 0.9.27
> >> >> >> > PCI: Found IRQ 3 for device 0000:02:0b.0
> >> >> >> > PCI: Sharing IRQ 3 with 0000:00:1d.1
> >> >> >> > eth0: RealTek RTL8139 at 0xc800, 00:03:0d:14:95:c4, IRQ 3
> >> >> >> > eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
> >> >> >> > ieee1394: Initialized config rom entry `ip1394'
> >> >> >> > PCI: Found IRQ 5 for device 0000:02:0a.0
> >> >> >> > PCI: Sharing IRQ 5 with 0000:00:1d.2
> >> >> >> > PCI: Sharing IRQ 5 with 0000:00:1f.1
> >> >> >> > ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[5]
> >> >> >> MMIO=[ffdff800-ffdfffff]  Max Packet=[2048]  IR/IT contexts=[4/8]
> >> >> >> > PCI: Found IRQ 4 for device 0000:00:1f.5
> >> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.3
> >> >> >> > PCI: Sharing IRQ 4 with 0000:00:1f.6
> >> >> >> > IRQ routing conflict for 0000:02:03.0, have irq 11, want irq 4
> >> >> >> > PCI: Setting latency timer of device 0000:00:1f.5 to 64
> >> >> >> > intel8x0_measure_ac97_clock: measured 55427 usecs
> >> >> >> > intel8x0: clocking to 48000
> >> >> >> > ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00030d4975701d84]
> >> >> >> > i8xx TCO timer: initialized (0x0860). heartbeat=30 sec
> >> (nowayout=0)
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > agpgart: Detected an Intel 865 Chipset.
> >> >> >> > agpgart: AGP aperture is 64M @ 0xf8000000
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > shpchp: Unknown symbol acpi_get_name
> >> >> >> > shpchp: Unknown symbol acpi_evaluate_object
> >> >> >> > kobject_register failed for ehci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI)
> >> Driver
> >> >> >> (PCI)
> >> >> >> > kobject_register failed for ohci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c032636c>] bus_add_driver+0x5c/0xa0
> >> >> >> >  [<c0326e37>] driver_register+0x57/0x90
> >> >> >> >  [<c02ea732>] __pci_register_driver+0x52/0x80
> >> >> >> >  [<f8ecf02e>] ohci_hcd_pci_init+0x2e/0x35 [ohci_hcd]
> >> >> >> >  [<c012e6e2>] sys_init_module+0x102/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for uhci_hcd (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > kobject_register failed for usb_storage (-17)
> >> >> >> >  [<c02ddf56>] kobject_register+0x36/0x50
> >> >> >> >  [<c012d0ed>] mod_sysfs_setup+0x3d/0xb0
> >> >> >> >  [<c012e4c9>] load_module+0x909/0x9f0
> >> >> >> >  [<c012e623>] sys_init_module+0x43/0x190
> >> >> >> >  [<c01029c8>] syscall_call+0x7/0xb
> >> >> >> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> >> >> >> > eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
> >> >> >> > NET: Registered protocol family 10
> >> >> >> > lo: Disabled Privacy Extensions
> >> >> >> > IPv6 over IPv4 tunneling driver
> >> >> >> > eth0: no IPv6 routers present
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >> ------------------------------------------------------------------------
> >> >
> >> > ./log/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ;
> >> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ;
> >> COMMAND=/sbin/modprobe -nq xeno_nucleus
> >> > ./log/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ;
> >> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ;
> >> COMMAND=/sbin/modprobe -n xeno_native
> >> > ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ;
> >> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ;
> >> COMMAND=/sbin/modprobe -n xeno_rtdm
> >> > ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ;
> >> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ;
> >> COMMAND=/sbin/modprobe -n xeno_timerbench
> >> > ./log/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ;
> >> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ;
> >> COMMAND=/usr/xenomai/bin/latency
> >> > ./adm/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ;
> >> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ;
> >> COMMAND=/sbin/modprobe -nq xeno_nucleus
> >> > ./adm/messages:Feb 22 14:00:59 (none) sudo:     root : TTY=pts/4 ;
> >> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ;
> >> COMMAND=/sbin/modprobe -n xeno_native
> >> > ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ;
> >> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ;
> >> COMMAND=/sbin/modprobe -n xeno_rtdm
> >> > ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ;
> >> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ;
> >> COMMAND=/sbin/modprobe -n xeno_timerbench
> >> > ./adm/messages:Feb 22 14:01:00 (none) sudo:     root : TTY=pts/4 ;
> >> PWD=/mnt/appusb/xenomai/share/xenomai/testsuite/latency ; USER=root ;
> >> COMMAND=/usr/xenomai/bin/latency
> >> > ./log/syslog:Feb 22 13:21:38 (none) kernel: I-pipe: Domain Xenomai
> >> registered.
> >> > ./log/syslog:Feb 22 13:21:38 (none) kernel: Xenomai: SMI-enabled
> >> chipset found but SMI workaround not enabled (check
> >> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: hal/x86 started.
> >> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: real-time
> >> nucleus v2.3 (Baroque) loaded.
> >> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting
> >> native API services.
> >> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting
> >> POSIX services.
> >> > ./log/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting RTDM
> >> services.
> >> > ./log/dmesg:I-pipe: Domain Xenomai registered.
> >> > ./log/dmesg:Xenomai: hal/x86 started.
> >> > ./log/dmesg:Xenomai: real-time nucleus v2.3 (Baroque) loaded.
> >> > ./log/dmesg:Xenomai: SMI-enabled chipset found but SMI workaround
> >> not enabled (check
> >> > ./log/dmesg:Xenomai: starting native API services.
> >> > ./log/dmesg:Xenomai: starting POSIX services.
> >> > ./log/dmesg:Xenomai: starting RTDM services.
> >> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: I-pipe: Domain Xenomai
> >> registered.
> >> > ./adm/syslog:Feb 22 13:21:38 (none) kernel: Xenomai: SMI-enabled
> >> chipset found but SMI workaround not enabled (check
> >> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: hal/x86 started.
> >> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: real-time
> >> nucleus v2.3 (Baroque) loaded.
> >> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting
> >> native API services.
> >> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting
> >> POSIX services.
> >> > ./adm/messages:Feb 22 13:21:38 (none) kernel: Xenomai: starting RTDM
> >> services.
> >> > ./adm/dmesg:I-pipe: Domain Xenomai registered.
> >> > ./adm/dmesg:Xenomai: hal/x86 started.
> >> > ./adm/dmesg:Xenomai: real-time nucleus v2.3 (Baroque) loaded.
> >> > ./adm/dmesg:Xenomai: SMI-enabled chipset found but SMI workaround
> >> not enabled (check
> >> > ./adm/dmesg:Xenomai: starting native API services.
> >> > ./adm/dmesg:Xenomai: starting POSIX services.
> >> > ./adm/dmesg:Xenomai: starting RTDM services.
> >>
> >>
> >>
> >
> >
>
>

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

roland Tollenaar wrote:
> Hi Wolfgang,
> 
>> And /proc/rtcan/devices is also useful.
> 
> Device rtcan0 Baudrate undefined State active TXCounter 7 RXCounter 5 
> Errors 0
> Device rtcan1 Baudrate undefined State stopped TXCounter 0 RXCounter 0 
> Errors 0
> 
>> > virtual can with? I presume i can send it messages with rtcansend and
>> > read the messages with rtcanrecieve?
>> src/utils/can/README?
> Works. Can send and recieve messages on it. Interesting may be this:
> If i send with rtcansend then in another console recieve the messages
> will not display. I would have expected the messages to be in the
> stack and display (depending how many messages the stack can hold).
> Why is that expectation incorrect?

There is no per device stack. The messages will be delivered directly to 
  the sockets receive buffer if it is listening and the filter does match.

> 
>> > I still have the outstanding question of what the module will be
>> > called for the PEAK CAN dongle. I have to find it after make modules
>> > to squirrle it away so i can load it after booting due to the
>> > complications with my live distribution.  You said that I cannot build
>> > that into the kernel statically correct? Can it be loaded without the
>> > actual device being connected?
>>
>> I said, it can be statically linked into the kernel but it will not work
>> (without modification, we can discuss this issue when you have a PCAN
>> dongle). What should a driver without hardware be good for?
> Good question. On the other hand it would be useful to know which
> module I have to
> pick out and load. Then I can compile the kernel for that so long and
> make a structure that loads it after booting. But that can be done
> later too.

You can do it now, just try and then ask questions.

> 
>> > Maybe a small suggestion. Would it not be better to have the virtual
>> > can driver built into the kernel by default. As a new user I did not
>> > select it, saw no reason to.
>>
>> Might be useful, indeed. BTW: there is a help available for each
>> configuration option?
> There should be. I think I used the help. Will check again for you
> when I change the configuration to load the PEAK driver as a module.
> 
> Roland.

Re: [Xenomai-help] CAN driver

[Roland Tollenaar]

Hi Wolfgang,

>>> I said, it can be statically linked into the kernel but it will not work
>>> (without modification, we can discuss this issue when you have a PCAN
>>> dongle). What should a driver without hardware be good for?
>> Good question. On the other hand it would be useful to know which
>> module I have to
>> pick out and load. Then I can compile the kernel for that so long and
>> make a structure that loads it after booting. But that can be done
>> later too.
> 
> You can do it now, just try and then ask questions.

Did it now, now there are questions. :)

The README says something about loading modules only it talks about

insmod xeno_can.o
and some others I cannot recall now (on windows now haven't got linux 
handy).

If I do the make modules and make modules_install I end up with a 
rtcan_peak_dngl.ko (again only the extension is accurate). modprobing 
that does not work so I insmod it. I get a message that invalid 
parameters were supplied or somethign like that.

In a flash I did see something mentioned about loading the modules with 
parameters (maybe you mentioned it?) but I cannot find the documentation 
that says something about this. Where must I look?

Regards,

Roland.

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

Roland Tollenaar wrote:
> Hi Wolfgang,
> 
>>>> I said, it can be statically linked into the kernel but it will not 
>>>> work
>>>> (without modification, we can discuss this issue when you have a PCAN
>>>> dongle). What should a driver without hardware be good for?
>>> Good question. On the other hand it would be useful to know which
>>> module I have to
>>> pick out and load. Then I can compile the kernel for that so long and
>>> make a structure that loads it after booting. But that can be done
>>> later too.
>>
>> You can do it now, just try and then ask questions.
> 
> Did it now, now there are questions. :)

OK.

> The README says something about loading modules only it talks about
> 
> insmod xeno_can.o
> and some others I cannot recall now (on windows now haven't got linux 
> handy).
> 
> If I do the make modules and make modules_install I end up with a 
> rtcan_peak_dngl.ko (again only the extension is accurate). modprobing 
> that does not work so I insmod it. I get a message that invalid 
> parameters were supplied or somethign like that.

Well, the modules name is xeno_can_peak_dng.ko as listed when doing:

   $ make modules
   ...
   LD [M]  drivers/xenomai/can/sja1000/xeno_can_peak_dng.ko
                                       ^^^^^^^^^^^^^^^^^^^^


> In a flash I did see something mentioned about loading the modules with 
> parameters (maybe you mentioned it?) but I cannot find the documentation 
> that says something about this. Where must I look?

And I load the modules with the following command:

   $ modprobe xeno_can_peak_dng type=epp io=0x378 irq=7

Wolfgang.

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

Hi Wolfgang,

> Well, the modules name is xeno_can_peak_dng.ko as listed when doing:
>
>    $ make modules
>    ...
>    LD [M]  drivers/xenomai/can/sja1000/xeno_can_peak_dng.ko
Yes I have this.

>                                        ^^^^^^^^^^^^^^^^^^^^
> And I load the modules with the following command:
>
>    $ modprobe xeno_can_peak_dng type=epp io=0x378 irq=7
I am having trouble here. The above line returns:
FATAL Module xeno_can_peak_dng not found

even when I call it from the directory the driver is in.

insmod from the directory I have the driver in returns:

insmod: error inserting 'xeno_can_peak_dng.ko': -1 no such device.

Any idea what may be wrong?

Regards,

Roland



>
> Wolfgang.
>
>

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

Hi

Just a quick update on the situation.

> > And I load the modules with the following command:
> >
> >    $ modprobe xeno_can_peak_dng type=epp io=0x378 irq=7
I had to sort out the module.conf matter but this now also responds with:

"No such device"

Which I presume is correct if the device is not attached?

What would be nice is a brief explantion of the paramters

io=0x378 looks like the hardware address of the parallel port. ?
irq the interrupt request number. Why 7? Is that specific to the
parallel port or would that be the same for all the CAN devices?
type=epp ? What does this mean?

Regards,

Roland.



>
> >
> > Wolfgang.
> >
> >
>

Re: [Xenomai-help] CAN driver

[Gilles Chanteperdrix]

roland Tollenaar wrote:
> Hi
> 
> Just a quick update on the situation.
> 
> 
>>>And I load the modules with the following command:
>>>
>>>   $ modprobe xeno_can_peak_dng type=epp io=0x378 irq=7
> 
> I had to sort out the module.conf matter but this now also responds with:
> 
> "No such device"
> 
> Which I presume is correct if the device is not attached?
> 
> What would be nice is a brief explantion of the paramters
> 
> io=0x378 looks like the hardware address of the parallel port. ?
> irq the interrupt request number. Why 7? Is that specific to the
> parallel port or would that be the same for all the CAN devices?
> type=epp ? What does this mean?

Maybe running modinfo xeno_can_peak_dng would help ?

-- 
                                                 Gilles Chanteperdrix

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

Hi Gilles,

Thanks
>
> Maybe running modinfo xeno_can_peak_dng would help ?
>

filename:       xeno_can_peak_dng.ko
author:         Wolfgang Grandegger <wg@domain.hid>
description:    RTCAN board driver for PEAK-Dongle
license:        GPL
vermagic:       2.6.16 486 gcc-3.4
depends:
parm:           irq:The interrupt number (array of byte)
parm:           io:The io-port address (array of ushort)
parm:           type:The type of interface (sp, epp) (array of charp)


This is the output. This is probably a beginners question but why irq
7 must be supplied and what sp or epp means is not answered by this
info.

Any idea?

Regards,

Roland.


> --
>                                                  Gilles Chanteperdrix
>

Re: [Xenomai-help] CAN driver

[Paul]

Hi Roland

On Friday 23 February 2007 12:04, roland Tollenaar wrote:
> parm:           irq:The interrupt number (array of byte)
> parm:           io:The io-port address (array of ushort)
> parm:           type:The type of interface (sp, epp) (array of charp)
>
>
> This is the output. This is probably a beginners question but why irq
> 7 must be supplied and what sp or epp means is not answered by this
> info.

This link should help to answer most of your parallel port questions: 
http://www.beyondlogic.org/epp/epp.htm

And for kernel calls to control the parallel port, see: 
http://people.redhat.com/twaugh/parport/html/parportguide.html - The 
information is relevant to vintage 2.2.x as well as for the latest 2.6.xx 
kernels.


Regards, Paul.

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

hi Paul,

Thanks for the urls. They are very helpful.

Does anyone know what the future of the parallel port is going to be?
Will it be disappearing from the PC,s in the near future or will it
still be around on new machines for a while?

Roland

On 2/23/07, Paul <paul_c@domain.hid> wrote:
>
> Hi Roland
>
> On Friday 23 February 2007 12:04, roland Tollenaar wrote:
> > parm: irq:The interrupt number (array of byte)
> > parm: io:The io-port address (array of ushort)
> > parm: type:The type of interface (sp, epp) (array of charp)
> >
> >
> > This is the output. This is probably a beginners question but why irq
> > 7 must be supplied and what sp or epp means is not answered by this
> > info.
>
> This link should help to answer most of your parallel port questions:
> http://www.beyondlogic.org/epp/epp.htm
>
> And for kernel calls to control the parallel port, see:
> http://people.redhat.com/twaugh/parport/html/parportguide.html - The
> information is relevant to vintage 2.2.x as well as for the latest 2.6.xx
> kernels.
>
>
> Regards, Paul.
>
>

Re: [Xenomai-help] CAN driver

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]

roland Tollenaar wrote:
> hi Paul,
> 
> Thanks for the urls. They are very helpful.
> 
> Does anyone know what the future of the parallel port is going to be?
> Will it be disappearing from the PC,s in the near future or will it
> still be around on new machines for a while?

Already vanished from laptops, will probably disappear from commodity
desktop hardware in the next years as well. But I guess industrial
boards will stick to it a bit longer.

USB has reached up, at least for lab scenarios (and your CAN dongle it
surely intended for such a use case). RT and USB is still an engineering
task to be finished. First approaches are there for Xenomai, but they
need stabilisation and interface standardisation.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] CAN driver

[roland Tollenaar]

> USB has reached up, at least for lab scenarios (and your CAN dongle it
> surely intended for such a use case). RT and USB is still an engineering
> task to be finished. First approaches are there for Xenomai, but they
> need stabilisation and interface standardisation.

How long is the development of RT-USB-CAN expected to take still.
Months or years?

Roland


>
> Jan
>
>
>

Re: [Xenomai-help] CAN driver

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

roland Tollenaar wrote:
>> USB has reached up, at least for lab scenarios (and your CAN dongle it
>> surely intended for such a use case). RT and USB is still an engineering
>> task to be finished. First approaches are there for Xenomai, but they
>> need stabilisation and interface standardisation.
> 
> How long is the development of RT-USB-CAN expected to take still.
> Months or years?

Until our pain with current special PC104 RS-422 cards gets too huge and
we start working on USB dongle integration again - or someone considers
an RT-USB stack worth to work on or to sponsor. There is no automatism
when relying on pure "open source magic".

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

Re: [Xenomai-help] CAN driver

[Paul]

Hi Roland

On Friday 23 February 2007 13:25, roland Tollenaar wrote:
> Does anyone know what the future of the parallel port is going to be?
> Will it be disappearing from the PC,s in the near future or will it
> still be around on new machines for a while?

I think you'll find many commodity manufacturers already label the parallel 
port as "legacy".. In fact, a number of laptops are shipped without one!

 I don't think we will see the parallel port disappear for a few years, but 
the time will come - The alternatives are PCI cards (worth fitting one if 
only to take advantage of the faster IO read/writes), or using one of the low 
cost fpga cards with custom firmware. It has been muted in some quarters that 
the PCI bus will also disappear, so the fpga option may not sound as daft as 
it might first appear.


Regards, Paul.

Re: [Xenomai-help] CAN driver

[Roland Tollenaar]

> Ethernet must surely be here for the long term - Many people have predicted 
> USB usurping ethernet, but it lacks the abilty to drive long cables.. For 
> industrial environments, one crucial part missing from most (all ?) USB - 
> That of electrical isolation. One accident with a floating earth, or one 
> device that is "hot", and the whole system ends up being toasted.

I do believe that PEAK USB CAN adapters come optically isolated for just
this reason. I know because its and option and more expensive than the
ones we purchased. At that stage we were only using them for testing bus's.



>> AFAIK there is no obvious successor for USB? Firewire made some noise
>> for a while but the way I understand it, not really that beneficial?
> 
> It really depends on what you need to interface, and also how deterministic 
> the communications needs to be - For most users, the USB "sometime today" 
> model is sufficient, for others who need a "now DAMIT" time frame, there are 
> alternatives.
Besides firewire (1394 was it not?) what else are the options? Become
vendor driven things, ProfiBus, Devicenet (variant of CAN), anything else?

By the way, what is CANOpen going to do long term. Stick around or is it
already being driven out by other protocols?

Regards,

Roland.




> 
> 
> Regards, Paul.
> 

Re: [Xenomai-help] CAN driver

[Wolfgang Grandegger]

roland Tollenaar wrote:
> Hi,
> 
> The first thing I notice is that I do not seem to find the devices
> rtcan0, rtcan1 etc.

The devices will be available when after the driver have properly 
loaded. You can find corresponding messages in the system log (type 
dmesg to list them. Here is the output from my Laptop:

RT-Socket-CAN 0.20.2 - (C) 2006 RT-Socket-CAN Development Team
rtcan: registered rtcan0
rtcan0: VIRT driver loaded
rtcan: registered rtcan1
rtcan1: VIRT driver loaded
RTCAN SJA1000 driver initialized
rtcan: registered rtcan2

> They are mentioned in the documentation and I presume they must be nodes in
> /dev or so. But I cannot find them. rt-can is statically built into my

No, see above.

> kernel so I don;t need to load any modules. I have selected the SJA
> chip and the PEAK CAN Dongle.

You must build the driver for the PEAK CAN Dongle as module and specify
the port type, I/O port and IRQ number when you load it. But as Jan 
already pointed out, you can use the virtual CAN driver for getting started.

> I am reading the README in /src/can and the one in ksrc/drivers/can.
> 
> /proc/rtcan is present but no devices rtcan0, rtcan1 etc under it.
> 
> What have I missed?

What have you selected? Check your boot log!

Wolfgang.


> On 2/22/07, Wolfgang Grandegger <wg@domain.hid> wrote:
>> Jan Kiszka wrote:
>> > Wolfgang Grandegger wrote:
>> [...]
>> >> I have attached a patch for a nice program to measure
>> >> the round trip time of CAN messages. It contrast to the other CAN
>> >> utility programs, it uses the POSIX-API and works as-is for Socket-CAN
>> >> as well. Jan, any objections to include it? If yes, I'm going to 
>> provide
>> >> a README.
>> >
>> > On first glance, nope, looks nice and clean.
>>
>> I have just commited the example program "rtcan_rtt" to the trunk.
>>
>> Wolfgang.
>>
> 
> 

[Xenomai-core] Re: (was: [Xenomai-help] CAN driver)

[Wolfgang Grandegger]

> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> 
> Wolfgang Grandegger wrote:
> >>> BTW: some time ago I provided a patch to make the CAN utility programs
> >>> part of the Doxygen documentation. IIRC, we said it's nice to have
> >>> hyperlinked examples in general.
> >>
> >> Some link at hand? Does it still apply? Sounds like something worth to
> >> apply.
> > 
> > See https://mail.gna.org/public/xenomai-core/2006-11/msg00033.html.
> > My patch was for the CAN utilities only. The idea was to have a more
> > general implementation including code snippets and now examples as well.
> > 
> > Wolfgang.
> > 
> 
> Gilles, as you are planning to regenerate the docs for trunk anyway,
> would you merge this patch (or better the corrected version) at that
chance?

I'm going to provide a revised patch tomorrow. Today I also playing with
other solutions but didn't found a better yet.

Wolfgang.