Ethernet problems on new motherboard.

[Bill_Bright]

Haven't had an issue with realtek drivers or AMD chipset drivers directly from the site.

Good to know.

Manufacture,s supply a Drivers disk ( with working Drivers) for initall install.

I agree, there is nothing wrong with using them. They will get you going. I am just saying what often happens is the disk is made well in advance (weeks, maybe months) of the motherboards so they can be ready for inclusion in the motherboard box during packaging. Then they may sit in a warehouse/distribution center for weeks, maybe months until Amazon, Newegg, BestBuy etc. place their order. Then they sit on the shelves or in the retailer's distribution center until the consumer buys it.

In the meantime, updated drivers (and BIOS firmware updates too) come out and are made available on-line.

Now I am not one to automatically update drivers just because a new one is out there. But on new builds, I do make sure the latest are installed. From then on, I update (or recommend updating) drivers only if they address an issue that affects me. The exception might be graphics drivers (depending on user) and I tend to keep them up to the latest.

 

[eidairaman1]

Good to know.

I agree, there is nothing wrong with using them. They will get you going. I am just saying what often happens is the disk is made well in advance (weeks, maybe months) of the motherboards so they can be ready for inclusion in the motherboard box during packaging. Then they may sit in a warehouse/distribution center for weeks, maybe months until Amazon, Newegg, BestBuy etc. place their order. Then they sit on the shelves or in the retailer's distribution center until the consumer buys it.

In the meantime, updated drivers (and BIOS firmware updates too) come out and are made available on-line.

Now I am not one to automatically update drivers just because a new one is out there. But on new builds, I do make sure the latest are installed. From then on, I update (or recommend updating) drivers only if they address an issue that affects me. The exception might be graphics drivers (depending on user) and I tend to keep them up to the latest.

I hate automatic updates, drives me nuts

 

[John Naylor]

Would suggest this route ,,,,

1. Prepare for Windows installation with USB tool or use available media
https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool

2. Connect boot drive data cable to lowest numbered SATA port .... but don't connect:
-Ethernet cable
-SATA Data Cable for any other drives

3. Install Windows to boot drive

4. Turn off Windows ability to install Hardware drivers
https://www.tenforums.com/tutorials...iver-updates-windows-update-windows-10-a.html

5. Install all hardware drivers from original media in boxes. See Item 7 below. Do NOT install WiFi drivers **.

6. Connect ethernet cable and run Windows Update till it stops doing anything

7. Install latest drivers for ALL hardware from manufacturers web sites. The reason we didn't do this in step 5 is 3 fold:
-Sometimes MoBo CD comes with licensed utilities with product key embedded and these are not on web site versions
-Its advisable to establish a working out of box conditions
-Sometimes newer drivers require latest Windows Updates

If you have a 2nd drive ....

8. Shut down and connect HD data cable to 2nd lowest numbered SATA port.

9. Boot to BIOS and make sure that SSD is the 1st boot device, if not fix it

10. Boot to Windows

According to Asus Tech Support, their MoBos are not designed to have both ethernet and WiFi drivers installed concurrently. Ran into this in my own box when built on workbench had used WiFi to get all new drivers. Moved box into office, ethernet would not work. Fiddled and tweaked for 2 days, called TS and they said "no can do... pick one". I didn't believe them, but been there done that w/ Asus before. Wasn't going to get an TS from them and given one or the other, obviously would rather have ethernet. Uninstalled WiFi driver and all was right w/ the world.

Might not be your issue, but worth giving it a try,

 

[Bill_Bright]

I hate automatic updates, drives me nuts

I was referring to people who automatically update drivers just because a new driver is out there. I don't do that. My generally philosophy is, if it ain't broke, don't fix it.

Again, except for a brand new build, I don't update drivers unless the new driver (1) addresses a problem I am having, (2) addresses a security issues (rare), or (3) current driver is corrupt (also rare).

Most chipset driver updates, for example, typically just add support for new CPUs and other hardware that came out after the motherboard left the factory. If I am not adding that new hardware, I don't need the update.

Bottom line: read the change log.

 

[R-T-B]

Sorry but that is not true. If it were, how can a computer boot into "Safe Mode with networking"?

By loading a select set of drivers bill?

Safe mode has some drivers.

Here, if you don't believe me:

EDIT: It appears I am late to this thread, appologies, getting over a cold.

 

[Bill_Bright]

By loading a select set of drivers bill?

Safe mode has some drivers.

Exactly my point. Those are native drivers already built into Windows. Note who the Digital Signer is.

 

[R-T-B]

Exactly my point. Those are native drivers already built into Windows. Note who the Digital Signer is.

I guess my point is those are still drivers. But whatever, semantics at this point.

 

[Deleted member 67555]

I've had this happen...
There is an order to things and sometimes that order just doesn't go like it usually does...
When this happened to me I did as I normally do and tried to install the lan drivers but still had no connection....
Long story short I had to install the chipset drivers because for some reason the generic windows driver didn't work... After that it was all good.

 

[eidairaman1]

I've had this happen...
There is an order to things and sometimes that order just doesn't go like it usually does...
When this happened to me I did as I normally do and tried to install the lan drivers but still had no connection....
Long story short I had to install the chipset drivers because for some reason the generic windows driver didn't work... After that it was all good.

Yup some tie in to each other. I think it could be because it's not a full dedicated lan chip, sort of like how a Soft/Winmodem worked.

https://en.m.wikipedia.org/wiki/Softmodem

 

[Bill_Bright]

I guess my point is those are still drivers.

Sure, hardware needs drivers. But many classes of hardware just need generic drivers to be fully operational. Ethernet, USB, EIDE, SATA, and more all just need generic drivers.

Even for graphics, Windows and the hardware (graphics solutions and monitors) support the common protocols and resolutions. If not, you could not see what you doing in the BIOS Setup Menu or to install an OS in the first place.

 

[R-T-B]

Sure, hardware needs drivers. But many classes of hardware just need generic drivers to be fully operational. Ethernet, USB, EIDE, SATA, and more all just need generic drivers.

But these drivers are native to the Intel ethernet chipset in question and far from generic...

 

[Bill_Bright]

But these drivers are native to the Intel ethernet chipset in question and far from generic...

LOL You think so? Look at mine.

 

[R-T-B]

LOL You think so? Look at mine.

View attachment 96021

Yeah, that's native to Realtek, bill. You're furthering my point.

 

[Bill_Bright]

Yeah, that's native to Realtek, bill. You're furthering my point.

Oh? So you are saying both Intel and Realtek use the exact same file name for their driver (rt640x64.sys)?

Really?

 

[R-T-B]

Oh? So you are saying both Intel and Realtek use the exact same file name for their driver (rt640x64.sys)?

Really?

Link me an Intel controller using rt640x64.sys, and you'll probably have a patent infringement case Bill. I'm seriously doubting you can do that.

I'm really not just talking out of my ass here. I used to do freelance development work for the remains of IBM OS/2, known as ecomstation. If there really was a generic way to write ethernet drivers, they would've been the first to know, given they were fighting an uphill battle to keep a dying operating system that was still deployed in many ATMs at the time network ready.

The closest solution we came up with was a process known as GENMAC, which was really just an NDIS2 wrapper for far more modern windows drivers, wifi cards and such, that worked rather poorly. But it worked well enough for the time.

 

[Bill_Bright]

This is going OT. If you are convinced different manufacturers of Ethernet controllers use proprietary protocols to communicate over Ethernet, then I am just wasting my time trying to show you otherwise.

 

[R-T-B]

This is going OT. If you are convinced different manufacturers of Ethernet controllers use proprietary protocols to communicate over Ethernet, then I am just wasting my time trying to show you otherwise.

I'm simply referring to the drivers that drive the chipsets. I didn't say anything about the media layer. Of course that's a standard. Ethernet can be roughly simulated by people it's so simple. Doesn't mean the parts that implement it load the same drivers, believe me I wish they did.

It is OT, so I'll let it die.