Re: CEPC doesn't find network card

What kind of network card are you using? What registry keys have you set.

It sounds like you are a little bit confused about how the KITL networking stuff works.

There are two kinds of network drivers for CE: NDIS and EDBG.

EDBG drivers are tiny static libraries that are linked into eboot.exe (the boot loader) and either kitl.dll (for CE 6.0) or nkkitl.exe (for earlier versions). These are used for very basic network operations when the full CE OS (scheduler, memory manager) is not available. These use no OS services so that they will work when there is no OS (bootloader) or when the OS is stopped at a breakpoint (KITL). These cannot be directly used for normal ("Product") networking. They are very simple, but fairly inefficient.

NDIS drivers are DLLs that are loaded by the OS for normal ("Product") networking. They only work when the full OS is running. They are full-featured and efficient. They make use of the scheduler and the memory manager, so they can only work when the OS is running. These cannot be used for download or debugging.

There is an NDIS driver named "VMINI" that works by sending packets to KITL, therefore providing "Product" ethernet via the EDBG driver. This is inefficient, but it works ok if you have only one network card or if you don't yet have a working NDIS driver.

It sounds like you have a working EDBG driver available for your network card (though you need to figure out why you aren't getting a DHCP reply message when booting). To find out why your NDIS driver is not loading, you need to explain the kind of network card you are using and the registry keys you are trying to set.

--
// StdDisclaimer.h
// This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Andrew Schweitzer" <a.schweitzer.grps@xxxxxxxxx> wrote in message news:1171211829.053265.38550@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello. I'm trying to set up a CEPC, and I'm having trouble getting it
to use the network correctly.

I managed to get it to successfully download an image over the network
from platform builder, but when CE comes up it can't find the network
adapter. Ipconfig reports no network adapter. Booting with VMINI
(connection sharing) allows it to find the card, sort of. It issues a
DHCP discover to which my router does not respond (router does respond
to the DHCP discover from bootloader). Then it gives up and gives
itself a 169 address.

The registry keys for the card are present. By adding prints to serial
port I can see 3Com1 and 3Com2 ("3Com" is how I named the keys)
drivers being loaded.

Any suggestions on a strategy to debug this? Have I maybe got the
registry keys only partly correct? I made them point at NE2000. Any
suggestions on figuring out where in the chain the ball is getting
dropped? Any idea how to figure out why, if driver is loaded, NDIS
doesn't set up a network stack associated with card? Should I play
with registry settings? Maybe my IRQs aren't correct? Could I figure
out what's going on by dumping the entire registry to the serial
port?

Thanks

Andy


.

Relevant Pages

  • RE: Missing Registry Entries, network connection and Driver file p
    ... corruption since the registry is also not complete. ... with the onboard Intel 10/100 network. ... I find 7 registry keys under that one. ... simple driver issue, but did try treating it as that to start anyway. ...
    (microsoft.public.windows.server.networking)
  • Re: Network Configuration
    ... > network card did not work. ... > Then I try to add the second network driver eepro100. ... > Do you Yahoo!? ...
    (RedHat)
  • Re: Finally getting DSL
    ... one set of pages talking about a 3Com 10/100 network card apparently being ... I'll try the other D-Link driver in the other post. ... Click Uninstall and then click OK to confirm you want to uninstall ...
    (rec.games.computer.ultima.dragons)
  • Re: Averatec 5500 Trying to set up SuSe 9.2
    ... >> trouble getting a network connection on it. ... > new to Linux, because weird hardware abounds on laptops. ... I did the default install. ... The Windows Network Connections says there is a 1394 network card. ...
    (comp.os.linux.portable)
  • Re: Start again on the newbies networking problem. Re: Need help (of course) setting up network
    ... >Did starting a new thread help? ... You should make all the Windows machines go *through* the Linux machine to ... computer from the network. ... one network card, but it is so insecure that it's not worth the effort. ...
    (Fedora)