Re: Preview Release & NetworkManager

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Saturday 26 April 2008 15:47, Anne Wilson wrote:
> On Saturday 26 April 2008 15:32, Anne Wilson wrote:
> > On Saturday 26 April 2008 13:49, Patrick O'Callaghan wrote:
> > > Don't see anything relevant (which doesn't mean it's not there). The
> > > other places to look would be /boot/config* ("grep PCMCIA" and compare
> > > the results), or maybe 'lspci' and/or 'lsusb'. Also /etc/udev/rules.d/*
> >
> > They are identical.  One possible breakthrough, though.  On the Live
> > system I managed to get the info screen on the connection.  It said it
> > was using pcnet_cs.  This isn't the device name, I guess, but probably a
> > driver or chipset?  Either way, that should, surely, be traceable to our
> > solution.
>
> I've just found this -
>
> Pcnet_cs is a driver for all NS8390-based PCMCIA ethernet cards. It can use
> either polled IO or a shared memory window to exchange data with the card.
> The driver first tests for a shared memory buffer, falling back on polled
> IO if the memory test fails. When this driver is bound to a card, it
> allocates the next available ethernet device (eth0..eth#). This device name
> will be reported in the kernel log file, and passed on to cardmgr(8).
>
> So - does anyone know which device from the list belongs to the NS8390
> group?
>
According to http://www.mikrotik.com/documentation/manual_2.7/DriverList.html 
the 3Com 3c590 driver should work.  Unfortunately I'm still getting 'Device 
eth0 doesn't seem to be present' :-(

Anne

-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux