From: Stephen Hemminger <shemminger@osdl.org>
To: Stephen.Clark@seclark.us
Cc: Francois Romieu <romieu@fr.zoreil.com>,
Jiri Slaby <jirislaby@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>,
netdev@vger.kernel.org
Subject: Re: New laptop - problems with linux
Date: Wed, 8 Nov 2006 12:26:49 -0800 [thread overview]
Message-ID: <20061108122649.2f79ec1f@freekitty> (raw)
In-Reply-To: <45523289.2010002@seclark.us>
On Wed, 08 Nov 2006 14:39:53 -0500
Stephen Clark <Stephen.Clark@seclark.us> wrote:
> Francois Romieu wrote:
>
> >Stephen Clark <Stephen.Clark@seclark.us> :
> >[...]
> >
> >
> >>No it is not loaded - i did a modprobe on it and it loaded but still no
> >>ethx device.
> >>
> >>
> >
> >Send complete 'dmesg' and 'lspci -vvx' (please Cc: netdev@vger.kernel.org)
> >
> >
> >
> lspci and dmesg attached below:
> Thanks, anything else I can do please let me know.
> 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG
> Network Connection (rev 02)
> Subsystem: Intel Corporation Unknown device 1000
>
Use the ipw3945 driver and binary regulatory daemon from:
http://ipw3945.sourceforge.net/#downloads
> 05:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169SC
> Gigabit Ethernet (rev 10)
> Subsystem: ASUSTeK Computer Inc. Unknown device 1345
> 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 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 11
> Region 0: I/O ports at d800 [size=256]
> Region 1: Memory at fe8ffc00 (32-bit, non-prefetchable) [size=256]
> Expansion ROM at 80000000 [disabled] [size=128K]
> Capabilities: [dc] Power Management version 2
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0-,D1+,D2+,D3hot+,D3cold+)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 00: ec 10 67 81 17 00 b0 02 10 00 00 02 08 40 00 00
> 10: 01 d8 00 00 00 fc 8f fe 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 45 13
> 30: 00 00 8c fe dc 00 00 00 00 00 00 00 0b 01 20 40
>
This PCI ID was added to 2.6.19. You should run 2.6.19-rc5 or backport the changes.
next prev parent reply other threads:[~2006-11-08 20:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4551EC86.5010600@seclark.us>
[not found] ` <4551F3A6.8040807@gmail.com>
[not found] ` <4551F5B7.1050709@seclark.us>
[not found] ` <20061108182658.GA21154@electric-eye.fr.zoreil.com>
2006-11-08 19:39 ` New laptop - problems with linux Stephen Clark
2006-11-08 20:26 ` Stephen Hemminger [this message]
2006-11-08 20:34 ` Stephen Clark
2006-11-08 20:53 ` Jesper Juhl
2006-11-08 21:21 ` Stephen Clark
2006-11-09 4:38 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061108122649.2f79ec1f@freekitty \
--to=shemminger@osdl.org \
--cc=Stephen.Clark@seclark.us \
--cc=davej@redhat.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).