Related topics

Realtek 8139 WiFi Cardbus Adapter
Doug Rabson d...@nlsystems.com lucky freebsd current On Sat, 2003-11-15 at 22:32, Philippe Charnier wrote: Hello, I have a Compaq armada 7800 with a noname pccard ethernet adapter which used to be detected as: rl0: <RealTek 8139 10/100BaseTX> port 0x1100-0x11ff mem 0x88000000-0x880001ff irq 11 at device 0.0 on

Realtek 8139 WiFi Cardbus Adapter
Martijn van Buul marti...@atlas.ipv6.stack.nl mailing netbsd help It occurred to me that Jeff_W wrote in gmane.os.netbsd.help: Hi All, I recently acquired a Linksys 802.11b WiFi adapter (model WPC11-VN v.4) and am trying to figure out why it doesn't get configured using NetBSD 3.0.1_STABLE (GENERIC_LAPTOP).

OpenBSD 2.7 install problem (network adapter ?)
That is, a vendor may sell a card labeled as an EtherGronk EG100 which will in fact be a RealTek 8139-based adapter, and then a few months later they'll have a new revision of the EtherGronk EG100 in the same box with the same picture on the front, only now it's a Macronix PMAC adapter. This doesn't bother them of

hardware recommendations
I didn't know they didn't support the NE2000 chipset...get a cheap Realtek 8139 card, they work very well in WinXP. Anyway when I go to manually install a driver all I get listed is "Microsoft Loopback Adapter". Why is there no Novell / Anthem ne2000 driver on the CD as with previous windows versions?

Network adapter....
But going to the netconf I just can find the 'realtek 8139 10/100' but not the realtek 8029 ... Or am I doing something wrong here .... There is dhcp on the LAN I am trying to connect to, evertyhing works fine from my Win98. Please help me out. Greetings The NIC mentioned is using "tulip.o" module.

misc/40192: PCI devices can not used with an nVidia nForce chipset
... charset=us-ascii Content-Disposition: inline I have an Ovislink LFS-PCM-32 10/100 CardBus ethernet adapter working under 5.0-CURRENT with the rl driver. .... ff ff ff ff ff rl0: <RealTek 8139 10/100BaseTX> port 0x3000-0x30ff mem 0x18022000-0x180221ff irq 11 at device 0.0 on cardbus0 rl0: Realtek 8139B detected.

Realtek 8139 WiFi Cardbus Adapter
... on their product boxes even when it is completely different (eg PCNet-PCI or RealTek 8139). If in doubt check the main chip number against this document. On Mon, 7 Aug 2000 22:56:58 -0400, "Ben Garvey" <bengar...@purrfectsoul.com> wrote: Ok, I'm sick of trying to get an unrecognized network adapter to work.

Network very slow... what have I done wrong ???
Network: Network Adapter VIA Compatable Fast Ethernet Adapter (169.254.21.116) Network Adapter WAN (PPP/SLIP) Interface (66.72.81.50) Hmm. Perhaps look into getting a cheap Realtek 8139 chipset NIC, sometime in the future. Modem US Robotics 56K Fax PCI ... fingers crossed on this one. Linux/Mandrake and Kppp might

Again..VIA Problem with RealTek EtherCard.
EJ ed...@yahoo.com linux redhat install Look at your manual and the box of the realtek 8139 to see if it compatible to a network card, such as ne2000. In my case, I use dhcpcd to bring up the dhcp client # dhcpcd charlie...@my-deja.com wrote: How do I install my network adapter ? Do I have to build th RTL8139

PPP Adapter. in winipcfg
You should use the same netcard: Realtek 8139 or Realtec 8029. Then you can do this step. You should install network card and TCP/IP protocol first. and you can AdapterName: Select the type of Adapter of the diskless workstation. Adapter Driver: the driver of adapter: *.DOS. If the netcard used in diskless

Realtek 8139 WiFi Cardbus Adapter
Juergen Pfann Juergen.pf...@t-online.de comp os linux hardware Jim vh wrote: Very frustrating trying to get this adapter to work. Realtek RTL8139(A) PCI Fast Ethernet Adapter I can't believe this. My RTL8139s (as well the 8029s before) work for >3 years now. Yes, they're maybe not the fastest NIC's, but stable most

Netconf -> LAN adapter -> Realtek 8029
I'm thinking about NIC incompatibility - is a realtek 8139 - but the driver are new and for win2k. I just outed a realtek 8029(?) from another win2k machine that was causing horrendous collisions. The 3-com replacement worked fine. X-No-Archive: Yes Lexx typed: One possible cause is if the adapter is not installed

Gwenview for WINDOWS + Possible Setup/Hardware Compatability ...
I don't ever recall seeing a software problem on RealTek 8139 cards. Nick. Thierry Montigneaux wrote: Hi, I have a problem installing 2.7 via FTP. Everything runs well when booting the install floppy, except that I occasionally get the message: " de0: autosense failed, cable problem ? " The Network adapter I have

Realtek 8139 adapter under RedHat 5.1
Mixed NetBIOS Scope ID. . . . . . : IP Routing Enabled. . . . . : No WINS Proxy Enabled. . . . . : No NetBIOS Resolution Uses DNS : No 0 Ethernet adapter : Description . . . . . . . . : Realtek 8139-series PCI NIC Physical Address. . . . . . : 00-48-54-6E-75-51 DHCP Enabled. . . . . . . . : Yes IP Address.

Microsoft MN-130 PCI ethernet adapter with Linux???
... "AJ Budge-Reid" <ajbu...@attglobal.net> wrote: Dear Chuck, Well after a bit of a learning process things seem to be working with the Realtek 8139 driver. above section you can change the Title to whatever you wish, this is what will be displayed in the MPTS (network adapter & protocol services) card list.

Intel PRO/100 (i82557) Server Adapter not seen by fxp.
(manufacturer 0x0, product 0x0) Realtek Semiconductor 8180 802.11b (ethernet network, revision 0x20) at cardbus0 dev 0 function 0 not configured Hm, next time, I don't know :) Personally, I'ma bit weary about realtek stuff. But I wouldn't be overly surprised if this turns out to be an issue with the laptop,

XP Home and Win98SE Network Problem
My adapter is a Realtek 8139-series PCI NIC. I next went to Control Panel | Network, and was surprised to see that on the server only, the RealTek TCP/IP was missing from the list. So I installed a new TCP/IP instance, and it came up correctly with the Realtek adapter name. I gave it the address 192.168.1.1 (the

Netconf -> LAN adapter -> Realtek 8029
Add support for another RealTek device. If you have a RealTek 8139 or 8129, please download and test the code from: http://www.freebsd.org/~wpaul/RealTek/3.0 FreeBSD 3.0 source code http://www.freebsd.org/~wpaul/RealTek/2.2 FreeBSD 2.2.x source code Note that I only have an 8139 adapter so I don't know for sure

Ovislink Ethernet Adapter hangs kernel on eject
So, try another NIC before fighting with other things too hard. The cheap card that everyone laughs at, but seems to work darned well are the Realtek 8139-based cards. Not a great performer, but they work well on many platforms and they are cheap. I don't ever recall seeing a software problem on RealTek 8139 cards.

HELP!!! HELP!!! HELP!!! Question about Realtek 8139 Ethernet ...
Then I run winipcfg and see that there are 3 entries: PPP Adapter., Microsoft TV/Video Connection and Realtek 8139-series PCI NIC. PPP adapter is for dialup connection and Realtek is the network card for broadband. The technical support girl said win98se will sometimes switch from the network card to PPP adapter,