[ltp] G40 Series Internal Ethernet Adapter

[linux-thinkpad@linux-thinkpad.org]

This is a multi-part message in MIME format.

--bound1059363202
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

I was able to get the driver to work, but I had to change the base address to correspond to the hardware in the G40.  I discovered the need to do that by looking at the /proc/pci file to see where the hardware was, and then looked at the driver source.  The driver files I downloaded did not have addresses corresponding to the G40's hardware.  Once I did that, the driver loaded and worked.

Fred

Pam Huntley <phuntley@us.ibm.com> wrote ..
> 
> 
> 
> 
> Hi Fred,
> 
> Sorry it's taken me so long to get back to you.   Have you had any success
> since the last email?  I went and installed Red Hat 9 from scratch (no
> updates) and then downloaded broadcom's driver, but I wasn't able to
> reproduce your problem.  Everything seemd to work flawlessly.
> 
> Here are the step I took, just in case...
> mkdir
> unzip driver into dir
> untar, etc
> make
> insmod bcm5700.o
> checked dmesg to make sure it was happy - it does find the driver
> rmmod bcm5700
> make install
> used neat (System Settings -> network) to configure eth0
> success
> 
> I'm assuming you did almost exactly those same steps?
> 
> I will try it with the updated Red Hat 9 kernel next, that could very well
> be part of the problem...
> 
> Thanks,
> 
> Pam
> 
> 
> Pam Huntley wrote:
> >
> >>I built the driver using the tarball.  Is there anything else that I
> >>should have done?
> >>
> >>
> >
> >I don't think so...  did you get any messages when you were building it?
> I
> >take it the message you posted was all that dmesg or /var/log/messages
> had
> >to say?  Red Hat doesn't ship the bcm5700 driver, so you don't have to
> >worry about getting the right version...  The only think that's different
> >when I was looking at it was the kernel version...  I think I'll have
> to
> >take another look at it when I get the hardware back on Monday...
> >
> >Pam
> >
> >
> >
> >
> >
> There is nothing in either dmsg nor messages for the desive.  The build
> appeared to do OK, and the driver does respond to modinfo -p.   That got
> me:
> 
> root@moby dev]# modinfo -p bcm5700
> debug int
> line_speed int array (min = 1, max = 16)
> auto_speed int array (min = 1, max = 16)
> full_duplex int array (min = 1, max = 16)
> rx_flow_control int array (min = 1, max = 16)
> tx_flow_control int array (min = 1, max = 16)
> auto_flow_control int array (min = 1, max = 16)
> mtu int array (min = 1, max = 16)
> tx_checksum int array (min = 1, max = 16)
> rx_checksum int array (min = 1, max = 16)
> scatter_gather int array (min = 1, max = 16)
> tx_pkt_desc_cnt int array (min = 1, max = 16)
> rx_std_desc_cnt int array (min = 1, max = 16)
> rx_jumbo_desc_cnt int array (min = 1, max = 16)
> adaptive_coalesce int array (min = 1, max = 16)
> rx_coalesce_ticks int array (min = 1, max = 16)
> rx_max_coalesce_frames int array (min = 1, max = 16)
> tx_coalesce_ticks int array (min = 1, max = 16)
> tx_max_coalesce_frames int array (min = 1, max = 16)
> stats_coalesce_ticks int array (min = 1, max = 16)
> enable_wol int array (min = 1, max = 16)
> enable_tso int array (min = 1, max = 16)
> 
> 
>  I also did a lspci -vvv and got the following for the hardware:
> 
> 02:00.0 Ethernet controller: Broadcom Corporation: Unknown device 170d
> (rev 01)
>         Subsystem: IBM: Unknown device 0545
>         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B-
>         Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (16000ns min), cache line size 08
>         Interrupt: pin A routed to IRQ 11
>         Region 0: Memory at d0200000 (64-bit, non-prefetchable) [size=64K]
>         Capabilities: [48] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot+,D3cold+)
>                 Status: D0 PME-Enable+ DSel=0 DScale=1 PME-
>         Capabilities: [50] Vital Product Data
>         Capabilities: [58] Message Signalled Interrupts: 64bit+
> Queue=0/3 Enable-
>                 Address: 00000000009e56e8  Data: f0f0
> 
> Is there some kind of configuration required to make the driver look at
> the hardware?  Do I need to create or map the driver to an entry in /dev
> ?
> 
> Fred
> 
> 
> --
> The linux-thinkpad mailing list home page is at:
> http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
> 
> 
> 
> -- 
> The linux-thinkpad mailing list home page is at:
> http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad

--bound1059363202--