On 7/31/07, Gabriel C <[email protected]> wrote:
> Sasa Ostrouska wrote:
> > On 7/30/07, Avuton Olrich <[email protected]> wrote:
> >> On 7/30/07, Sasa Ostrouska <[email protected]> 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 ?
>
> >
> > Rgds
> > Sasa
>
> Gabriel
>
Gabriel, hmm, shouldnt udev be able to autoconfigure that ? But I need
to check that, thx for the tip.
Rgds
Sasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
