Re: Question about PCI IDs and Drivers

Sorry man, I forgot:

du:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address 10.0.0.38
netmask 255.255.255.0
network 10.0.0.0
broadcast 10.0.0.255
gateway 10.0.0.93
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 200.204.0.138
dns-search minicom


auto eth1
iface eth1 inet static
address 10.0.0.247
netmask 255.255.255.0
network 10.0.0.0
broadcast 10.0.0.255




So, when I try to reload the network interfaces, I got this error :

du:~# /etc/init.d/networking restart
* /etc/network/options is deprecated.
Setting up IP spoofing protection...done (rp_filter).
Reconfiguring network interfaces...ifup: interface lo already configured
SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
Failed to bring up eth1.
done.


The 8139too and 8139cp are already loaded



On 7/19/06, Ron Johnson <ron.l.johnson@xxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Like I asked before:

What's in your /etc/network/interfaces file?

Eduardo wrote:
> I tried first with 8139cp and ran :
>
> du:~# modprobe 8139cp
> du:~# ifconfig eth1 10.0.0.221 255.255.255.0 up
> SIOCSIFADDR: No such device
> eth1: ERROR while getting interface flags: No such device
> SIOCSIFADDR: No such device
> eth1: ERROR while getting interface flags: No such device
> eth1: ERROR while getting interface flags: No such device
>
>
> Doesn't work. Now with 8139too:
>
> du:~# ifconfig eth1 10.0.0.221 255.255.255.0 up
> SIOCSIFADDR: No such device
> eth1: ERROR while getting interface flags: No such device
> SIOCSIFADDR: No such device
> eth1: ERROR while getting interface flags: No such device
> eth1: ERROR while getting interface flags: No such device
>
>
> Nothing!!! Does anybody knows how can I put this NIC to work?
>
>
>
>
> On 7/19/06, Florian Kulzer <florian@xxxxxxxxxxxxxxxxxxxxx> wrote:
>> On Wed, Jul 19, 2006 at 13:14:42 -0500, Ron Johnson wrote:
>> > Eduardo wrote:
>> > > I have a new Network Card, and I found the VENDOR ID and the
>> DEVICE ID.
>> > > I found it in "lspci -nv" and later looking for the given number in
>> > > /var/libs/pciutils/pci.ids, but now, how do I know which driver to
>> > > use? And if Debian has it compiled?
>> > >
>> > > The card is (listed with pci.ids) :
>> > >
>> > > 1904 Hangzhou Silan Microelectronics Co., Ltd.
>> > > 8139 RTL8139D [Realtek] PCI 10/100BaseTX ethernet adaptor
>> > >
>> > > Now, the output of lspci -v :
>> > >
>> > > 0000:00:0b.0 Ethernet controller: Hangzhou Silan Microelectronics
>> Co.,
>> > > Ltd. RTL8139D [Realtek] PCI 10/100BaseTX ethernet adaptor (rev 01)
>> > > Flags: bus master, medium devsel, latency 64, IRQ 11
>> > > Memory at cfff7f00 (32-bit, non-prefetchable) [size=256]
>> > > I/O ports at d000 [size=256]
>> > > Expansion ROM at cffa0000 [disabled] [size=128K]
>> > > Capabilities: [50] Power Management version 2
>> > > Capabilities: [60] Vital Product Data
>> > >
>> > >
>> > > I think is the Driver 8139too, but when I modprobe it, my Network
>> > > Cards still doesnt work.
>> > >
>> > > If I do "ifconfig eth1 10.0.0.221 255.255.255.0 up" it says No
>> Such Device.
>> >
>> > 8139too would also be my guess.
>> >
>> > What's in your /etc/network/interfaces file?
>>
>> There is also 8139cp which according to the comments in the source file
>> supports "8139C+" cards/chipsets from Realtek. I don't know if that
>> includes 8139D, but it might be worth a try.

- --
Ron Johnson, Jr.
Jefferson LA USA

Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEvqRdS9HxQb37XmcRAkzaAJ0QqJfsuxIwFa73gb8LasTojQz/SwCfczbR
9L72PKd5zLhCned7oH3Nkdg=
=jnXc
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx




--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: [SLE] PCMCIA eth problems
    ... configured eth-pcmcia-0 as static with ip ... If I do "ifconfig", only lo interface is present. ... Shutting down network interfaces: ...
    (SuSE)
  • Re: Different IP for different users
    ... user switch is active), has different ip addresses, maybe forcing the ... physical output interface even if it isn't a must. ... I need to guarantee bandwidthto administrator account giving ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Computer names and HD names?
    ... the network interface order, all that changes is the default interface ... If you have two active network interfaces, ... Connected to two of these ports are an Airport Extreme modem and an old ... AppleTalk in the AppleTalk tab of the Airport connection in Network ...
    (comp.sys.mac.system)
  • Re: Different IP for different users
    ... user switch is active), has different ip addresses, maybe forcing the ... physical output interface even if it isn't a must. ... I need to guarantee bandwidthto administrator account giving ...
    (microsoft.public.windowsxp.general)
  • Re: Different IP for different users
    ... physical output interface even if it isn't a must. ... I need to guarantee bandwidthto administrator account giving ... low priorities to other users. ...
    (microsoft.public.windowsxp.help_and_support)