Drivers for Pavillion p6 2026?

I installed a fresh W7 Ultimate on this HP Pavillion P6 2026.
Right off the bat I see in Device Manager that I need a Realtek
ethernet controller. But even after I downloaded and installed all
the drivers offered by HP at

http://support.hp.com/us-en/drivers/.../model/5180011

I still lack the driver.

Need help.

Thanks
Alan

wrote:
I installed a fresh W7 Ultimate on this HP Pavillion P6 2026.
Right off the bat I see in Device Manager that I need a Realtek
ethernet controller.

What (exactly) does the device manager say/show? Which realtek?

Do you have something else to boot that has network function; a linux,
an AV disk/usb/.iso, Hiren's, etc.

Can Win7 find a MS/win driver for it on its own?



--
Mike Easter

On Mon, 26 Sep 2016 14:01:22 -0700, Mike Easter
wrote:

wrote:
I installed a fresh W7 Ultimate on this HP Pavillion P6 2026.
Right off the bat I see in Device Manager that I need a Realtek
ethernet controller.

What (exactly) does the device manager say/show? Which realtek?

It simply says 'Ethernet Controller'.


Do you have something else to boot that has network function; a linux,
an AV disk/usb/.iso, Hiren's, etc.

I have a Hirens Boot CD V 9.5 from 2008, that used to boot okay on
other machines. I haven't tried it on this Pavillion.

Can Win7 find a MS/win driver for it on its own?

Not sure what you mean, but I think not.

Thanks for response.

Alan

wrote:
I installed a fresh W7 Ultimate on this HP Pavillion P6 2026.
Right off the bat I see in Device Manager that I need a Realtek
ethernet controller. But even after I downloaded and installed all
the drivers offered by HP at

http://support.hp.com/us-en/drivers/.../model/5180011

I still lack the driver.

Need help.

Thanks
Alan

Did that specific driver download?

écrivait :

I installed a fresh W7 Ultimate on this HP Pavillion P6 2026.
Right off the bat I see in Device Manager that I need a Realtek
ethernet controller. But even after I downloaded and installed all
the drivers offered by HP at

http://support.hp.com/us-en/drivers/...on-p6-Desktop-
PC-series/5151865/model/5180011

I still lack the driver.

Need help.

Thanks
Alan

The driver is the page you post. Select your OS and Windows version, click
the button "Change" and all drivers will appear.

wrote:
Mike Easter wrote:

What (exactly) does the device manager say/show? Which realtek?

It simply says 'Ethernet Controller'.

My Win7 device manager specifically id/s the network devices, ethernet
or wireless by brand name and model with additional info in the
Properties about the driver.

It also says/displays what is 'going on' with the device.

Can Win7 find a MS/win driver for it on its own?

If Win knows what it is, which is apparently some kind of problem in
this case, you can help it find a driver in its own driver resources.
Realteks are very common, but 'variable' as to id.


--
Mike Easter

wrote:
I installed a fresh W7 Ultimate on this HP Pavillion P6 2026.
Right off the bat I see in Device Manager that I need a Realtek
ethernet controller. But even after I downloaded and installed all
the drivers offered by HP at

http://support.hp.com/us-en/drivers/.../model/5180011

I still lack the driver.

Need help.

Thanks
Alan

RealTek has the drivers on their site as well.
So you have HP and RealTek as driver sources.

http://www.realtek.com.tw/downloads/...vel=3 &Conn=2

Here you can see my new install, with no
driver for my Ethernet chip. VEN=0x8086
(the code for Intel), and DEV=0x1503
(some Intel chip).

http://s9.postimg.org/yeni0no4f/hardwareid.gif

Then, I look them up here.

http://pciids.sourceforge.net/pci.ids

1503 82579V Gigabit Network Connection

So now I have a name for my NIC.

Yours might be in the RealTek section...
The RealTek section starts with this line.

10ec Realtek Semiconductor Co., Ltd.

RealTek is a bit tricky, because for some
reason, some of the chip numbers are explicitly acknowledged
right on their download page. Whereas some of the
other codes, I don't know if they're OEM or what
the excuse is, they're harder to track down.
I sometimes resort to checking INF files if
I want to understand what's going on there.

My guess is, yours is a tricky one, and I'll be
downloading the HP driver and burrowing into
the INF using 7ZIP. This driver covers a number
of RealTek NICs.

http://whp-aus2.cold.extweb.hp.com/p...00/sp54416.exe

.\src\hp64win7.inf

%RTL8168.DeviceDesc% = RTL8168.ndi, PCI\VEN_10EC&DEV_8168&REV_01

That might be an example of a more obscure one, an 8168.
If the entry in the INF (there are many to choose from)
matches your chip, then you'd try installing the driver.

Most of the time, the filter rules in the INF prevent
catastrophes. On occasion, some idiot company makes
a "polymorphic" driver, which just about any
computer will accept, and then all sorts of strange
stuff can happen. That might happen with touchpad
drivers or the like (a filter driver). NICs will
normally be pretty good, and if you install the
wrong one, it'll just tell you that the driver
is not applicable. But in general, if you installed
a thousand drivers just downloaded at random off the
Internet, sooner or later you'll run into one that
installs when it isn't supposed to. And it's because
it is not checking Plug and Play information properly.

Paul

Turing wrote:

I installed a fresh W7 Ultimate on this HP Pavillion P6 2026.
Right off the bat I see in Device Manager that I need a Realtek
ethernet controller. But even after I downloaded and installed all
the drivers offered by HP at

http://support.hp.com/us-en/drivers/.../model/5180011

I still lack the driver.

Many laptop/notebook/tablet makers design their hardware product for a
specific OS version. The hardware is bundled with software specific for
one OS and a single version of that OS. There are no older drivers for
older OS versions and no newer drivers for newer OS versions. Cost
margin is often very tight for these products so the maker cannot afford
the resources to develop drivers for out-of-band setup scenarios. You
get the product with a particular OS and version and that is all the
maker supports. If you change to a different setup and one not
supported for the product then it is up to you to find all the required
drivers for that out-of-band OS. Just because you can do it doesn't
mean you should do it.

Have you tried getting the driver from Realtek? If you know the chip
model number on the mobo then you can probably find Realtek's own driver
for various OSes and versions of them. However, that will be a
"reference" driver. It will not have any additional functions the OEMer
may add to the driver. The chip may have additional connections (pins)
to support added functionality provided the mobo includes additional
circuitry to support those added functions; however, the OEMer would
have to modify the reference driver to accomodate any added functions in
the hardware. A reference driver might work okay but you might end up
with limited functions (none of the hardware-assisted extra features).

According to the hyperlink you provided on HP's page for that product,
you need to get the "Driver-Original" bundle. That includes the NIC
driver. The description of that driver bundle includes:

Original Realtek Network Controller Driver
7.44.421.2011 Rev. A 1.7 MB Apr 17, 2016

Did you try to install that driver bundle? What do you see when you go
into Device Manager (devmgmt.msc) and look at the properties of the NIC
on the mobo? Is there a yellow question mark for that device? If you
look at the properties for that device and go under the Driver tab, does
it show the above regarding version and date for the installed driver?

I don't know when this product first got released for sale. If it is
old enough, the appropriate driver(s) may already be bundled (embedded)
in Windows and you use those. You go through the hardware wizard to
install the driver and select the one already available within Windows.
If not, use the NIC driver included in the Driver-Original bundle.

If you did install that driver bundle, have you rebooted yet? Drivers
are kernel-mode software that must get loaded when Windows loads. So
you have to start Windows to load the drivers. That means restarting
Windows so it loads again and also loads the drivers. Sometimes
installs don't complete correctly and you have to reboot Windows into
its safe mode and then reboot again to go into Windows normal mode. I'm
not talking about going into sleep or hibernate mode. I'm talking about
a warm or cold reboot of Windows. It has to actually start anew for it
to load new kernel-mode drivers.