Re: Dell XPS 1530 - Network card issue - Marvell 88E8040
On Thu, Jan 24, 2008 at 03:08:57PM +0100, Chris Stromblad wrote: > > On Thu, 2008-01-24 at 19:58 +0900, Pyun YongHyeon wrote: > > On Thu, Jan 24, 2008 at 11:02:05AM +0100, Chris Stromblad wrote: > > > Sorry, here is the correct output, now also run as root! > > > > > > Again I've included the Wireless, because perhaps someone else would > > > like to have a look at the data to understand why it's not detected. To > > > my understanding there should be support as I seem to recall that Intel > > > even put out the drivers themselves, or at least some hardware > > > specifications. > > > > > > > I've checked wpi(4) probe routine and your device id is listed there. > > So wpi(4) does serve your hardware, if not post your issues to > > appropriate mailing list. > > Thanks for looking into this for me, I'll give 7.0-RC1 another go and > see if I can get it to work. > > Let me know how you get along with the Marvell driver. > Try the patch at the following URL. Not sure whether it also needs patch for PHY.(You know I don't have the hardware.) If msk(4) attach to the hardware, please show me the output of verbosed boot message. http://people.freebsd.org/~yongari/msk/msk.88E8040.patch -- Regards, Pyun YongHyeon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell XPS 1530 - Network card issue - Marvell 88E8040
On Thu, 2008-01-24 at 19:58 +0900, Pyun YongHyeon wrote: > On Thu, Jan 24, 2008 at 11:02:05AM +0100, Chris Stromblad wrote: > > Sorry, here is the correct output, now also run as root! > > > > Again I've included the Wireless, because perhaps someone else would > > like to have a look at the data to understand why it's not detected. To > > my understanding there should be support as I seem to recall that Intel > > even put out the drivers themselves, or at least some hardware > > specifications. > > > > I've checked wpi(4) probe routine and your device id is listed there. > So wpi(4) does serve your hardware, if not post your issues to > appropriate mailing list. Thanks for looking into this for me, I'll give 7.0-RC1 another go and see if I can get it to work. Let me know how you get along with the Marvell driver. > Btw, I think you may have to use 7.0-RC1 to get wpi(4). > > > 09:00.0 0200: 11ab:4354 (rev 12) > > Subsystem: 1028:022e > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > > ParErr- Stepping- SERR+ FastB2B- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast > > >TAbort- SERR- > Latency: 0, Cache Line Size: 64 bytes > > Interrupt: pin A routed to IRQ 16 > > Region 0: Memory at f9ffc000 (64-bit, non-prefetchable) > > [size=16K] > > Region 2: I/O ports at de00 [size=256] > > Capabilities: [48] Power Management version 3 > > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > > PME(D0+,D1+,D2+,D3hot+,D3cold+) > > Status: D0 PME-Enable- DSel=0 DScale=1 PME- > > Capabilities: [5c] Message Signalled Interrupts: Mask- > > 64bit+ Queue=0/0 Enable- > > Address: Data: > > Capabilities: [c0] Express Legacy Endpoint IRQ 0 > > Device: Supported: MaxPayload 128 bytes, PhantFunc > > 0, ExtTag- > > Device: Latency L0s unlimited, L1 unlimited > > Device: AtnBtn- AtnInd- PwrInd- > > Device: Errors: Correctable- Non-Fatal- Fatal- > > Unsupported- > > Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- > > Device: MaxPayload 128 bytes, MaxReadReq 512 bytes > > Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s > > L1, Port 0 > > Link: Latency L0s <256ns, L1 unlimited > > Link: ASPM L0s Enabled RCB 128 bytes CommClk+ > > ExtSynch- > > Link: Speed 2.5Gb/s, Width x1 > > > > 0b:00.0 0280: 8086:4222 (rev 02) > > Subsystem: 8086:1021 > > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > > ParErr- Stepping- SERR+ FastB2B- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast > > >TAbort- SERR- > Latency: 0, Cache Line Size: 64 bytes > > Interrupt: pin A routed to IRQ 17 > > Region 0: Memory at f9eff000 (32-bit, non-prefetchable) > > [size=4K] > > Capabilities: [c8] Power Management version 2 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > > PME(D0+,D1-,D2-,D3hot+,D3cold+) > > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > > Capabilities: [d0] Message Signalled Interrupts: Mask- > > 64bit+ Queue=0/0 Enable- > > Address: Data: > > Capabilities: [e0] Express Legacy Endpoint IRQ 0 > > Device: Supported: MaxPayload 128 bytes, PhantFunc > > 0, ExtTag- > > Device: Latency L0s <512ns, L1 unlimited > > Device: AtnBtn- AtnInd- PwrInd- > > Device: Errors: Correctable- Non-Fatal- Fatal- > > Unsupported- > > Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ > > Device: MaxPayload 128 bytes, MaxReadReq 128 bytes > > Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s > > L1, Port 0 > > Link: Latency L0s <128ns, L1 <64us > > Link: ASPM L1 Enabled RCB 64 bytes CommClk+ > > ExtSynch- > > Link: Speed 2.5Gb/s, Width x1 > > > > Thanks for the info. > > > On Thu, 2008-01-24 at 18:46 +0900, Pyun YongHyeon wrote: > > > On Thu, Jan 24, 2008 at 10:27:31AM +0100, Chris Stromblad wrote: > > > > Hi, > > > > > > > > This is the output from lspci -v: > > > > > > 'lspci -nvv' is preferred as I have to check device ids. > > > > > > > 09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 > > > > PCI-E Fast Ethernet Controller (rev 12) > > > > Subsystem: Dell Unknown device 022e > > > > Flags: bus master, fast devsel, latency 0, IRQ 16 > > > > Memory at f9ffc000 (64-bit, non-prefetchable) [size=16K] > > > > I/O ports at de00 [size=256] > > > > Capabilities: > > > > > > > > 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG > > > > N
Re: Dell XPS 1530 - Network card issue - Marvell 88E8040
On Thu, Jan 24, 2008 at 11:02:05AM +0100, Chris Stromblad wrote: > Sorry, here is the correct output, now also run as root! > > Again I've included the Wireless, because perhaps someone else would > like to have a look at the data to understand why it's not detected. To > my understanding there should be support as I seem to recall that Intel > even put out the drivers themselves, or at least some hardware > specifications. > I've checked wpi(4) probe routine and your device id is listed there. So wpi(4) does serve your hardware, if not post your issues to appropriate mailing list. Btw, I think you may have to use 7.0-RC1 to get wpi(4). > 09:00.0 0200: 11ab:4354 (rev 12) > Subsystem: 1028:022e > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR+ FastB2B- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast > >TAbort- SERR- Latency: 0, Cache Line Size: 64 bytes > Interrupt: pin A routed to IRQ 16 > Region 0: Memory at f9ffc000 (64-bit, non-prefetchable) > [size=16K] > Region 2: I/O ports at de00 [size=256] > Capabilities: [48] Power Management version 3 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA > PME(D0+,D1+,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=1 PME- > Capabilities: [5c] Message Signalled Interrupts: Mask- > 64bit+ Queue=0/0 Enable- > Address: Data: > Capabilities: [c0] Express Legacy Endpoint IRQ 0 > Device: Supported: MaxPayload 128 bytes, PhantFunc > 0, ExtTag- > Device: Latency L0s unlimited, L1 unlimited > Device: AtnBtn- AtnInd- PwrInd- > Device: Errors: Correctable- Non-Fatal- Fatal- > Unsupported- > Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- > Device: MaxPayload 128 bytes, MaxReadReq 512 bytes > Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s > L1, Port 0 > Link: Latency L0s <256ns, L1 unlimited > Link: ASPM L0s Enabled RCB 128 bytes CommClk+ > ExtSynch- > Link: Speed 2.5Gb/s, Width x1 > > 0b:00.0 0280: 8086:4222 (rev 02) > Subsystem: 8086:1021 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR+ FastB2B- > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast > >TAbort- SERR- Latency: 0, Cache Line Size: 64 bytes > Interrupt: pin A routed to IRQ 17 > Region 0: Memory at f9eff000 (32-bit, non-prefetchable) > [size=4K] > Capabilities: [c8] Power Management version 2 > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [d0] Message Signalled Interrupts: Mask- > 64bit+ Queue=0/0 Enable- > Address: Data: > Capabilities: [e0] Express Legacy Endpoint IRQ 0 > Device: Supported: MaxPayload 128 bytes, PhantFunc > 0, ExtTag- > Device: Latency L0s <512ns, L1 unlimited > Device: AtnBtn- AtnInd- PwrInd- > Device: Errors: Correctable- Non-Fatal- Fatal- > Unsupported- > Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ > Device: MaxPayload 128 bytes, MaxReadReq 128 bytes > Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s > L1, Port 0 > Link: Latency L0s <128ns, L1 <64us > Link: ASPM L1 Enabled RCB 64 bytes CommClk+ > ExtSynch- > Link: Speed 2.5Gb/s, Width x1 > Thanks for the info. > On Thu, 2008-01-24 at 18:46 +0900, Pyun YongHyeon wrote: > > On Thu, Jan 24, 2008 at 10:27:31AM +0100, Chris Stromblad wrote: > > > Hi, > > > > > > This is the output from lspci -v: > > > > 'lspci -nvv' is preferred as I have to check device ids. > > > > > 09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 > > > PCI-E Fast Ethernet Controller (rev 12) > > > Subsystem: Dell Unknown device 022e > > > Flags: bus master, fast devsel, latency 0, IRQ 16 > > > Memory at f9ffc000 (64-bit, non-prefetchable) [size=16K] > > > I/O ports at de00 [size=256] > > > Capabilities: > > > > > > 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG > > > Network Connection (rev 02) > > > Subsystem: Intel Corporation Unknown device 1021 > > > Flags: bus master, fast devsel, latency 0, IRQ 17 > > > Memory at f9eff000 (32-bit, non-prefetchable) [size=4K] > > > Capabilities: > > > > > > I included the wireless data as well because I wanted to ask if you know > > > whether or not this has support from ports? It doesn't get detec
Re: Dell XPS 1530 - Network card issue - Marvell 88E8040
Sorry, here is the correct output, now also run as root! Again I've included the Wireless, because perhaps someone else would like to have a look at the data to understand why it's not detected. To my understanding there should be support as I seem to recall that Intel even put out the drivers themselves, or at least some hardware specifications. 09:00.0 0200: 11ab:4354 (rev 12) Subsystem: 1028:022e Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- On Thu, Jan 24, 2008 at 10:27:31AM +0100, Chris Stromblad wrote: > > Hi, > > > > This is the output from lspci -v: > > 'lspci -nvv' is preferred as I have to check device ids. > > > 09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 > > PCI-E Fast Ethernet Controller (rev 12) > > Subsystem: Dell Unknown device 022e > > Flags: bus master, fast devsel, latency 0, IRQ 16 > > Memory at f9ffc000 (64-bit, non-prefetchable) [size=16K] > > I/O ports at de00 [size=256] > > Capabilities: > > > > 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG > > Network Connection (rev 02) > > Subsystem: Intel Corporation Unknown device 1021 > > Flags: bus master, fast devsel, latency 0, IRQ 17 > > Memory at f9eff000 (32-bit, non-prefetchable) [size=4K] > > Capabilities: > > > > I included the wireless data as well because I wanted to ask if you know > > whether or not this has support from ports? It doesn't get detected when > > booting FreeBSD so I assume that either it needs a binary blob, or that > > perhaps there are some drivers in ports that can be installed once I > > have the wired network functioning properly. > > > > Didn't wpi(4) detect your wireless network hardware? > > > Once again thank you very much for your help, and if there is anything > > else I can do or get you, please let me know! > > > > - Chris > > > -- Chris Stromblad Security Engineer WASP UK Regent Street London, WC2 Dir: +44 207 043 5190 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell XPS 1530 - Network card issue - Marvell 88E8040
Hi, This is the output from lspci -v: 09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 12) Subsystem: Dell Unknown device 022e Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f9ffc000 (64-bit, non-prefetchable) [size=16K] I/O ports at de00 [size=256] Capabilities: 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) Subsystem: Intel Corporation Unknown device 1021 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at f9eff000 (32-bit, non-prefetchable) [size=4K] Capabilities: I included the wireless data as well because I wanted to ask if you know whether or not this has support from ports? It doesn't get detected when booting FreeBSD so I assume that either it needs a binary blob, or that perhaps there are some drivers in ports that can be installed once I have the wired network functioning properly. Once again thank you very much for your help, and if there is anything else I can do or get you, please let me know! - Chris On Thu, 2008-01-24 at 10:29 +0900, Pyun YongHyeon wrote: > On Wed, Jan 23, 2008 at 02:50:13PM +0100, Chris Stromblad wrote: > > > > > > Pyun YongHyeon wrote: > > >On Wed, Jan 23, 2008 at 12:25:17PM +0100, Chris Stromblad wrote: > > > > (I originally addressed this to the freebsd-hardware, but got no > > > response, > so please forgive me for reposting this here!) > > > > > > > > Hi, > > > > > > > > It appears as if the Marvell 88E8040 is not yet supported by FreeBSD > and > > > > specifically the msk(4) driver. I would just like to know if there are > > > any > > > > plans on adding support for the above mentioned NIC. > > > > > > > > > >I'd like to add support 88E8040(Yukon2 FE+ PCIe Fast ethernet > > >controller). I don't think just adding a PCI id is sufficient > > >to make it work but it would be even better if you can send me > > >the 'pciconf -lcv' output to me. > > > > Will I have to download and install FreeBSD in order to provide this > > data, or is there a simpler way of doing it? > > > > Ether Linux or FreeBSD can do that. > If you have to run Linux due to lack of driver on FreeBSD, > send me the output of lspci. > As you said, you have to install FreeBSD first in order to > run "pciconf -lcv". > > If you didn't install FreeBSD yet, just use FreeBSD or Linux > LiveCD to boot the OS and use lspci or pciconf. > > > > > > >I think one of the serious issue of Yukon2 FE+ is introduction > > >of new descriptor format and additional bugs for the chip/phy > > >as other variants. Since there are no documentation for > > >controller/phy hardware, it may take longer than you would > > >expect to see a working/stable driver. I guess disabling TSO and > > >checksum offload may make it possible to write a minimal driver > > >for the hardware. I'll let you know when I have code to test. > > >I cannot say the code written by me would work as I don't have > > >that hardware. > > > > > > > Normally I wouldn't even bother asking, and just shrug and say, tough > > > luck > > > > they don't support it... next distribution. Thing is, I really, really > > > > like FreeBSD. I'm kind of a GNU/Linux guy, but I've never managed to > > > > settle for a distribution and have moved from one to another, never > > > quite > > > > finding something that works with me, and not against me. > > > > > > > > Then I tried FreeBSD, actually I just read much of the available > > > > documentation and I was "converted". _THIS_ is how documentation > should > > > be > > > > written; clear, concise, to the point and most of all, USEFUL! Thank > > > you! > > > > > > > > So, my point is that I really want this to work out. I'm willing to > give > > > > as much time as necessary to get this driver working. Whether it's > just > > > a > > > > little Device_ID change in the source, I don't know. However, if > anyone > > > is > > > > up for helping me getting this to work, I'll provide whatever > > > information > > > > I can. > > > > > > > > Many thanks, and keep up the fantastic work on the FreeBSD operating > > > system. > > > > > > > > Regards, > > > > Christoffer Str?mblad > > > > > > > > PS: I've tried 8.0-CURRENT (snapshot from 27122007), 7.0-RC1 and > > > FreeBSD > 6.3, no luck. > > > > -- Chris Stromblad Security Engineer WASP UK Regent Street London, WC2 Dir: +44 207 043 5190 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell XPS 1530 - Network card issue - Marvell 88E8040
On Thu, Jan 24, 2008 at 10:27:31AM +0100, Chris Stromblad wrote: > Hi, > > This is the output from lspci -v: 'lspci -nvv' is preferred as I have to check device ids. > 09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 > PCI-E Fast Ethernet Controller (rev 12) > Subsystem: Dell Unknown device 022e > Flags: bus master, fast devsel, latency 0, IRQ 16 > Memory at f9ffc000 (64-bit, non-prefetchable) [size=16K] > I/O ports at de00 [size=256] > Capabilities: > > 0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG > Network Connection (rev 02) > Subsystem: Intel Corporation Unknown device 1021 > Flags: bus master, fast devsel, latency 0, IRQ 17 > Memory at f9eff000 (32-bit, non-prefetchable) [size=4K] > Capabilities: > > I included the wireless data as well because I wanted to ask if you know > whether or not this has support from ports? It doesn't get detected when > booting FreeBSD so I assume that either it needs a binary blob, or that > perhaps there are some drivers in ports that can be installed once I > have the wired network functioning properly. > Didn't wpi(4) detect your wireless network hardware? > Once again thank you very much for your help, and if there is anything > else I can do or get you, please let me know! > > - Chris > -- Regards, Pyun YongHyeon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell XPS 1530 - Network card issue - Marvell 88E8040
On Wed, Jan 23, 2008 at 12:25:17PM +0100, Chris Stromblad wrote: > (I originally addressed this to the freebsd-hardware, but got no response, > so please forgive me for reposting this here!) > > Hi, > > It appears as if the Marvell 88E8040 is not yet supported by FreeBSD and > specifically the msk(4) driver. I would just like to know if there are any > plans on adding support for the above mentioned NIC. > I'd like to add support 88E8040(Yukon2 FE+ PCIe Fast ethernet controller). I don't think just adding a PCI id is sufficient to make it work but it would be even better if you can send me the 'pciconf -lcv' output to me. I think one of the serious issue of Yukon2 FE+ is introduction of new descriptor format and additional bugs for the chip/phy as other variants. Since there are no documentation for controller/phy hardware, it may take longer than you would expect to see a working/stable driver. I guess disabling TSO and checksum offload may make it possible to write a minimal driver for the hardware. I'll let you know when I have code to test. I cannot say the code written by me would work as I don't have that hardware. > Normally I wouldn't even bother asking, and just shrug and say, tough luck > they don't support it... next distribution. Thing is, I really, really > like FreeBSD. I'm kind of a GNU/Linux guy, but I've never managed to > settle for a distribution and have moved from one to another, never quite > finding something that works with me, and not against me. > > Then I tried FreeBSD, actually I just read much of the available > documentation and I was "converted". _THIS_ is how documentation should be > written; clear, concise, to the point and most of all, USEFUL! Thank you! > > So, my point is that I really want this to work out. I'm willing to give > as much time as necessary to get this driver working. Whether it's just a > little Device_ID change in the source, I don't know. However, if anyone is > up for helping me getting this to work, I'll provide whatever information > I can. > > Many thanks, and keep up the fantastic work on the FreeBSD operating system. > > Regards, > Christoffer Str?mblad > > PS: I've tried 8.0-CURRENT (snapshot from 27122007), 7.0-RC1 and FreeBSD > 6.3, no luck. -- Regards, Pyun YongHyeon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
