CUSI-M on Board LAN Question

  • Thread starter Thread starter Dave Manning
  • Start date Start date
D

Dave Manning

This MB has a wake-on-lan connector but also has a built in lan. Is there a
way to use the wake-on-lan feature using the built in LAN controller?

Thanks,

Dave Manning
 
Dave said:
This MB has a wake-on-lan connector but also has a built in lan. Is there a
way to use the wake-on-lan feature using the built in LAN controller?

Thanks,

Dave Manning
Click to expand...

The WOL header (input-header) is typically there for add-in PCI cards
with a similar output-header. The onboard LAN also typically doesn't
interface with this WOL circuitry. In some cases an onboard LAN solution
could also have the same 3-pin WOL output-header to connect to the
motherboard's WOL input-header, but I don't think this is the case with
the CUSI-M (or nearly all boards with chipset-based LAN, for that matter).
So you will have to rely on the self-contained wake-up capabilities of
the onboard LAN (if any). I think this motherboard is PCI 2.2 compliant
(which supports wake up via a PCI signal) but I don't know if the
onboard LAN is suitably wired. You could also check for relevant options
in the device manager settings for the onboard LAN.

Regards
Nikos
 
The WOL header (input-header) is typically there for add-in PCI cards
with a similar output-header. The onboard LAN also typically doesn't
interface with this WOL circuitry. In some cases an onboard LAN
solution could also have the same 3-pin WOL output-header to connect
to the motherboard's WOL input-header, but I don't think this is the
case with the CUSI-M (or nearly all boards with chipset-based LAN, for
that matter). So you will have to rely on the self-contained wake-up
capabilities of the onboard LAN (if any). I think this motherboard is
PCI 2.2 compliant (which supports wake up via a PCI signal) but I
don't know if the onboard LAN is suitably wired. You could also check
for relevant options in the device manager settings for the onboard
LAN.

Regards
Nikos
Click to expand...

Thanks for the info. I checked the device manager and that is were my
problem was.

Again Thank you

Dave
 
Back
Top