Bug 230698

Summary:	skge network driver is unable to perform wol
Product:	[Fedora] Fedora	Reporter:	ohad Levy <ohadlevy>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6	CC:	jonstanley, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-08 04:28:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	427887

Description ohad Levy 2007-03-02 10:59:58 UTC

using skge on my 3com Corp 3c940 10/100/1000Base-T [Marvell] (rev 12) on board
LAN, (ASUS p4p800) I'm unable to wol.

I've set the correct ethtool wol g entries, and also removed the ifdown from the
initscripts, with no luck.

using the same hardware with winxp, the machine starts up without a problem.

I'm using the kernel-smp 2.6.19 with skge as a module (standard rpm version).

any help would be appreciated.

Thanks

Comment 1 Jon Stanley 2008-01-08 01:49:54 UTC

(This is a mass-update to all current FC6 kernel bugs in NEW state)

Hello,

I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!

Comment 2 Jon Stanley 2008-02-08 04:28:08 UTC

Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA,
since no information has been lodged for over 30 days.

Please re-open this bug or file a new one if you can provide the requested data,
and thanks for filing the original report!