From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfgang Grandegger Subject: Re: Configuration CAN sja1000_isa Date: Thu, 26 Apr 2012 13:32:23 +0200 Message-ID: <4F993247.30704@grandegger.com> References: <4F99015A.2050606@grandegger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from ngcobalt02.manitu.net ([217.11.48.102]:39640 "EHLO ngcobalt02.manitu.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756099Ab2DZLc1 (ORCPT ); Thu, 26 Apr 2012 07:32:27 -0400 In-Reply-To: Sender: linux-can-owner@vger.kernel.org List-ID: To: cedric koch-hofer Cc: linux-can@vger.kernel.org On 04/26/2012 10:17 AM, cedric koch-hofer wrote: > On Thu, Apr 26, 2012 at 10:03 AM, Wolfgang Grandegger wrote: >> > On 04/26/2012 09:35 AM, cedric koch-hofer wrote: >>> >> Hello all, >>> >> >>> >> I am currently trying to use the CAN output of an Aaeon embedded >>> >> system using sja1000 CAN chipset controler. >>> >> I am using an Ubuntu with a kernel 3.0 and I do not succeed to change >>> >> the state of my can device from down to up. >>> >> As you can see in the following trace, all seems to work untill I try >>> >> to activate my CAN network interface. >>> >> After that, the interface is in state "UNKNOWN" and I can not use it >>> >> with the socketcan tools: cansend, candump, cansniffer... >>> >> >>> >> Any idea will be welcome, >> > >> > That's wired. Does it work with "ifconfig can0 up"? OK. it's the same with ifconfig. Hm, I have no idea. Looks like some mismatch between the tools and the kernel. Some questions: - What UBUNTU and kernel version do you use? - Do you use the CAN drivers from that kernel? - Could you try a more recent kernel? Wolfgang.