I too am having problems getting a D-Link DFE-530TX+ network card to work in my system. I have seen several previous threads describing this problem, and I hope you can make some suggestions for me. The card is labeled as DFE-530TX+ Rev. Results 241 - 288 of 359 - Genuine D-Link DFE-530TX Rev D2 + Fast Ethernet 10/100 PCI. Not responsible for compatibility issues with your system or software. Writers concentrated on contents. It was SGML like. Writing and reference software for mac. End users who bought the product could produce documents that looked exactly liek the DIgital manuals since those styles were there by default. It was used by Digital to write their extensive documentation, so it was able to efficiently generate books with index, table of contents etc etc. (I have found information regarding Rev. A, B, C, D1 and D2, but E1 must be so new I can find no info on it yet.) The main chip on the card is labeled DL10038D. My distribution is RedHat 7.2, with kernel 2.4.7-10. (I have SuSe 8.1 available but prefer not to upgrade yet if I can avoid it.) I have checked the BIOS and Plug-N-Play is set to No. I have tried the card in two different PCI slots, wih no apparent differences. I believe you nailed the problem in your original post- The DL10038 D chip used on the Rev. E cards is newer than the DL10038 C chip used on the previous 530TX+ rev, and as such might not be supported by the current rtl8139.o or 8139too.o modules. One of the most irritating things about the 530TX/TX+ line of cards is that every sucessive revision seems to either use an entirely different chipset than previous models, or a newer rev of chipset which isn't supported by the current drivers. You could try to contact the author/maintainer of the rtl8139 driver and see if he has any advice: Donald Becker. I am a newbie but have trried to follow all guides and instructions for this also. I put a DFE-530TX+ Rev.D2 in a Celeron box with a partition drive. I have W98 on part of it and just intsalled RH8.0 on the other. The driver for Windows loaded no problem but I could not compile the rtl8139.c file from D-Link download. It has the 8139too.o file in the /lib/modules/2.4.18-14/kernal/drivers/net folder but it does not recognize it as appropriate. I try to insmod the file and get the following errors: unresolved symbol mii_ethtool_gset_Raeb9c2b4 unresolved symbol mii_nway_restart_R9d437993 unresolved symbol mii_link_ok_R633bd7b9 unresolved symbol mii_ethtool_sset_Rc366493c # Can anyone guide me on this, it feels like I am sooo close. Originally posted by rlyonmckay I could not compile the rtl8139.c file from D-Link download.What errors did you receive? In order to compile from source, you need to install the gcc compiler, kernel sources, and kernel headers. None of these packages are installed by default, so you need to install them (via RPM) from your installation CDs. They are all (I believe) part of the 'Development' packages. So you've now put in an older (rev D) version of the NIC, and the Redhat 8.0 installer didn't detect it all during the install, right? Does the NIC appear in Redhat's Hardware Browser utility at all? Let's see what modules you actually are loading right now; post the output of the following command (the ' l ' is a lower-case 'L'): lsmod Also- this probably won't work, but it won't hurt anything either, so let's give it a try. Execute the following two commands (in order): depmod -ae modprobe 8139too If you get no errors, run 'lsmod' again and see if the driver is now in the list of loaded modules. Do/answer all of the above (please be complete and precise in your response) and we'll take it from there. Great, glad I could help. And yes, the output of lsmod is correct. Apparently you had an unresolved module dependency issue, because mii needs to be loaded before 8139too in order for 8139too to function correctly. That's what the cryptic 'mii 2156 0 (8139too)' entry is telling you. The 'unresolved symbol' errors came from the fact that the 8139too module's code was looking for information from mii, but since mii wasn't loaded the calls failed. Vgn fz4000 driver for mac. Installation programs usually sort that out and ensure that modules are loaded in the required order, but sometimes you need to do it manually, and that's what the 'depmod' command does. The 'modprobe' command actually consults the database created by depmod to see if the module you are trying to load requires that other modules be loaded first; if so, it loads those modules in the necessary order. The (older) 'insmod' command isn't as intelligent; it's unaware of dependencies and will just blindly try to load the module you specify regardless of dependencies. • 72 Answers SOURCE: D-Link's support site shows that this product was discontinued in 2001. The operating systems supported by the driver only show up to Windows XP and not Vista or Windows 7. Windows XP has the driver in the operating system so you should be able to use the Add/Remove hardware wizard to install the driver within Windows or try from the CD that came with the card. If you are using a later operating system, there is a good possibility that the product is not supported. Posted on Nov 19, 2010.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |