From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4603F45D.7060007@domain.hid> Date: Fri, 23 Mar 2007 16:38:05 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 Subject: Re: [Xenomai-help] New install of Xenomai 2.3 for 2.6.17 kernel.... Various problems References: <032320071533.27467.4603F3590000E5E600006B4B2216557996070E0301020A98@domain.hid> In-Reply-To: <032320071533.27467.4603F3590000E5E600006B4B2216557996070E0301020A98@domain.hid> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenomai@domain.hid Cc: xenomai@xenomai.org xenomai@domain.hid wrote: >>Btw, make sure 100% that all your modules issued from the kernel >>compilation in question have been properly installed under /lib/modules. >> >>Additionally, it has been reported (and I recently experienced this >>myself) than under some specific circumstances, only running a "make >>clean" in an old Xenomai-enabled kernel tree before upgrading the >>Xenomai support with prepare-kernel.sh, then compiling anew, is _not_ >>enough. This may introduce some funky issues, likely due to missed >>dependencies in the kernel tree. > > > > I did originally build the kernel form fresh source and have only patched > once. I am however rebuilding after a make mrproper just for kicks. > Since building the nucleus as a module, It appears that things are being > scheduled on both processors for linux. I still however can't get my > network connection to work properly. It is a Broadcom NetExtreme GigE > card. It successfully get's a DHCP address as if it is working fine. > No messages in any of the log files. I however can not get out at all. > When trying to get in from the outside with ssh it supplies me the host > key but then hangs for about 1 minute then prompts me for a password and > works fine from there. From inside, even pings dont work. Do you have the same behaviour of your network card when the SMI workaround is disabled ? Did you try to disable CONFIG_PCI_MSI ? -- Gilles Chanteperdrix