Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 161005 - No wake-on-lan line for Marvell Controller
Summary: No wake-on-lan line for Marvell Controller
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-08 21:34 UTC by juggler885
Modified: 2007-01-08 21:41 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
My .config file (config,37.33 KB, text/plain)
2007-01-08 21:34 UTC, juggler885
Details

Note You need to log in before you can comment on or make changes to this bug.
Description juggler885 2007-01-08 21:34:12 UTC
There is no wake-on-lan line for Marvell Controller when I use ethtool. I know this card supports it because I have used the wake-on-lan feature in Windows. 

03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 22)
        Subsystem: Giga-byte Technology Marvell 88E8053 Gigabit Ethernet Controller (Gigabyte)
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at c9000000 (64-bit, non-prefetchable) [size=16K]
        I/O ports at 9000 [size=256]
        [virtual] Expansion ROM at 80000000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 2
        Capabilities: [50] Vital Product Data
        Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/1 Enable-
        Capabilities: [e0] Express Legacy Endpoint IRQ 0
        Capabilities: [100] Advanced Error Reporting

Linux jbdesk 2.6.18-gentoo-r6 #2 SMP Sun Jan 7 16:34:41 EST 2007 i686 Intel(R) Pentium(R) D CPU 3.60GHz GNU/Linux

Using gentoo-sources
Comment 1 juggler885 2007-01-08 21:34:47 UTC
Created attachment 106115 [details]
My .config file
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2007-01-08 21:41:06 UTC
If you can reproduce this w/ latest vanilla-sources, then report this upstream. If you can't; then attach your kernel .config, relevant dmesg output, post emerge --info output and reopen then.