Media Disconnected State after FBA

  • Thread starter Thread starter Santiago Allen
  • Start date Start date
S

Santiago Allen

Hi All,

I was wondering if anyone could give me some insigts on this. I have
a MB with an onboard Marvell Yukon 88E8052 ethernet adapter. I
componetized the driver directly from the inf file and know it worked
because I can ping 127.0.0.1. When I ipconfig I see that my media
state is "Media Disconnected". I am installing Core Networking (minus
the Firewall) DHCP Client service, and Client for Microsoft Networks.
I have made similar images with different network cards before and
this is all they ever needed to get an ip address and connect to
windows network shares using the net command.

The big difference I notice between this MB and netowrk card and
others I have worked with is that WinPE also is incapable of
initializing the card. I dont know how meaningfull it is.

Did some research and found out that there is a Media Sense feature
that can detect media states and make DHCP ask for a new IP address.
How can I use this? Or am I already using it? What I cannot do is
use a static IP address.

Any suggestions?

Thanks,

Santiago
 
Ok some more information,

I figured out how to disable Media Sense. Now when I use the renew
command on ipconfig I get "Unable to Contact DHCP Server" so either I
am missing a component or I failed to componetize the Marvell Yukon
ethernet card correctly even though I can ping myself.

Any thoughts?
 
Santiago,

I've seen number of issues with Marvell Yukon adapters. Quite frankly, I don't like them as the driver(s) are always complicated and
none of them are in XPe database (nor in XP Pro install). This means you always have to deal with the adapter/driver bugs by
yourself.

Anyway, I do not think the MediaSense feature has anything to do with your problems. In fact, it serves a different purpose. Also,
by default, the MediaSense is on so it should not make your adapter say "Media disconnected" unless you are really disconnected. You
can always force to renew and get a new IP address by doing ipconfig /renew.

My suggestions:
- First of all, please check if you really have a good physical NIC connection to the network. Check all cables used, etc.
- Please look into the \windows\setupapi.log file to see if there was any IRQ or similar conflicts while installing or
initializing the NIC driver.
- Try to play with some older versions of the Yukon driver. There have been some rumors they broke things in some builds
released.
- Check out how things are working with the same driver on XP Pro and XP Pro Emulation image (www.xpefiles.com).
 
Hi KM,

Thanks for the reply, here is what I can tell you.

....Installed XP Pro...installed the yukon driver by Device
Manager...Update Driver...and using the same inf I componetized.
....In Xp pro the media state is connected
....I used the same wires/routers in XP pro as I did in XPE so the
wires should be ok.
....Without turning off media sense, I cant ipconfig /renew because the
feature is disabled.

I am looking at XP pro emulation now...the problem is it wont fit on
the flash drive so I will have to use a normal HDD.

My hunch is towards a missing component so I think I will try XP
emulation and if it works, remove components until it stops working.
Its not a very time-efficient way of doing this but it should work.

Thanks,

Santiago
 
Santiago,
I am looking at XP pro emulation now...the problem is it wont fit on
the flash drive so I will have to use a normal HDD.
Click to expand...

You can safely remove big features there like .Net 2.0 and such. Those are irrelevant to your driver testing.
You will have to leave with some build errors though.
My hunch is towards a missing component so I think I will try XP
emulation and if it works, remove components until it stops working.
Its not a very time-efficient way of doing this but it should work.
Click to expand...

Well, this is going to be a huge effort if you plan to deploy and test the image every time you remove a component or even a group
of components.
I'd rather spend a little bit of time on XPPRoEmulation, test the driver there. If works, it is going to prove the concept - the
driver can work on XPe without major registry modificaitons.
Then I'd move towards your own (small) image and explore the problem there with tools like DependencyWalker, Regmon/Filemon/Process
Monitor and etc.

Regards,
KM
 
Back
Top