From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S969513AbXG3WYe (ORCPT ); Mon, 30 Jul 2007 18:24:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S968930AbXG3WYQ (ORCPT ); Mon, 30 Jul 2007 18:24:16 -0400 Received: from nf-out-0910.google.com ([64.233.182.190]:52068 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S968872AbXG3WYN (ORCPT ); Mon, 30 Jul 2007 18:24:13 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Dh8ePeTe5z+xLvuf5ZohcIRsYAQlPx5qdaeD2As4G0VZzsoA11/6ONGkvMGpMMou7ElqTEnGN6VyoFHUeczy76j6cK3c8NFaVAFJ/qWhP6KYUdYFN8S6GQAVcY0Z8TuWotSu5pSWk2DMFd1r60Kznsm+G1WGCNl219vDMIqcLYE= Message-ID: <46AE63F6.9060108@googlemail.com> Date: Tue, 31 Jul 2007 00:19:34 +0200 From: Gabriel C User-Agent: Thunderbird 2.0.0.5 (X11/20070721) MIME-Version: 1.0 To: Kay Sievers CC: Sasa Ostrouska , Avuton Olrich , linux-kernel@vger.kernel.org Subject: Re: forcedeth ? References: <3aa654a40707301337w52bbe246o99db15b9f8e7a2c4@mail.gmail.com> <46AE6029.60308@googlemail.com> <3ae72650707301522r4241353ld1be5dd7a2322233@mail.gmail.com> In-Reply-To: <3ae72650707301522r4241353ld1be5dd7a2322233@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Kay Sievers wrote: > On 7/31/07, Sasa Ostrouska wrote: >> On 7/31/07, Gabriel C wrote: >>> Sasa Ostrouska wrote: >>>> On 7/30/07, Avuton Olrich wrote: >>>>> On 7/30/07, Sasa Ostrouska wrote: >>>>>> Hi people, >>>>>> >>>>>> I'm using this on a x86-64 amd machine. During boot of the last >>>>>> 2.6.22.1 kernel I get this error: >>>>> Somewhat unrelated, but I had a similar forcedeth problem, I took the >>>>> latest git forcedeth.c and put it into 2.6.22.1 and it worked for me. >>>>> >>>>> Good luck! >>>>> -- >>>>> avuton >>>> Ok, maybe I can try that. In any case I noticed another strange thing. >>>> I have 2 nics in that machine. >>>> One is a nvidia MPC61 using the forcedeth.c the other one is a Realtec >>>> RTL8029 using the >>>> ne2k_pci. >>>> Now, whenever I compile them both as modules each reboot the cards get >>>> inversed eth assignement. Suppose first boot, the forcedeth is eth0 , >>>> the next boot it is eth1 , this is very anoying as one cant make only >>>> one boot, probably this is someway related to the bios. >>>> Now I configured them one in the kernel and the other as a module so >>>> they get each time assigned the same name. But when powerloss happens >>>> (unplug the cable) the next boot they do not work. I see them assigned >>>> the correct name, ifconfig shows the IP's but ping results in a >>>> destination unreachable. >>>> >>>> Any ideas ? >>> Udev rules ? >>> >> Gabriel, hmm, shouldnt udev be able to autoconfigure that ? But I need >> to check that, thx for the tip. > > Udev does that already, it automatically creates rules and assigns > persistent names to newly discovered network hardware. The names will > be stable across reboots, regardless of module loading order or > anything else. But sure, that's only on distros who take these issues > serious. :) Yes but the rules are based on the MAC address no ? > > Kay > Gabriel