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