Date: Thu, 24 Jan 2008 19:58:17 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Chris Stromblad <cs@wa-sp.com> Cc: freebsd-hackers@freebsd.org Subject: Re: Dell XPS 1530 - Network card issue - Marvell 88E8040 Message-ID: <20080124105817.GD18179@cdnetworks.co.kr> In-Reply-To: <1201168925.6667.3.camel@localhost,> References: <4797241D.8080000@wa-sp.com> <20080123123244.GG14495@cdnetworks.co.kr> <47974615.2030901@wa-sp.com> <20080124012957.GB18179@cdnetworks.co.kr> <1201166851.8147.18.camel@localhost, > <20080124094620.GC18179@cdnetworks.co.kr> <1201168925.6667.3.camel@localhost, >
next in thread | previous in thread | raw e-mail | index | archive | help
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- <TAbort- <MAbort- >SERR- <PERR- > 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: 0000000000000000 Data: 0000 > 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- <TAbort- <MAbort- >SERR- <PERR- > 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: 0000000000000000 Data: 0000 > 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: <access denied> > > > > > > 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: <access denied> > > > > > > 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 > -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080124105817.GD18179>