Bug#596390: Log messages from 2.6.30 and 2.6.32

To: 596390-quiet@bugs.debian.org
Cc: Ben Hutchings <ben@decadent.org.uk>, 596390-submitter@bugs.debian.org, 596390@bugs.debian.org
Subject: Bug#596390: Log messages from 2.6.30 and 2.6.32
From: Shawn Heisey <elyograg@elyograg.org>
Date: Sat, 20 Nov 2010 10:43:31 -0700
Message-id: <[🔎] 4CE808C3.60400@elyograg.org>
Reply-to: Shawn Heisey <elyograg@elyograg.org>, 596390@bugs.debian.org
In-reply-to: <[🔎] 4CE80340.4010102@elyograg.org>
References: <4C8AB1A8.8020701@elyograg.org> <1284159429.5323.610.camel@localhost> <4C8B29CC.1020808@elyograg.org> <1284223574.5323.621.camel@localhost> <4C8BFC62.2070105@elyograg.org> <1284257751.5323.649.camel@localhost> <[🔎] 4CE80340.4010102@elyograg.org>

On 11/20/2010 10:20 AM, Shawn Heisey wrote:

Unknown RealTek chip (mask: 0x28000000)

I found what looks like a bug report and resolution for this same chipand problem in FreeBSD.


http://www.pubbs.net/200904/netbsd/15177-50rc3-messed-up-rtl8111dl-onboard-nic.html

I know there are licensing issues between BSD and Linux that prevent youfrom copying the code directly, but perhaps this can nudge you in theright direction.


Thanks,
Shawn

Reply to:

References:
- Bug#596390: Log messages from 2.6.30 and 2.6.32
  - From: Shawn Heisey <debian@elyograg.org>

Prev by Date: Bug#596390: Log messages from 2.6.30 and 2.6.32
Next by Date: Bug#596390: Log messages from 2.6.30 and 2.6.32
Previous by thread: Bug#596390: Log messages from 2.6.30 and 2.6.32
Next by thread: Bug#596390: Log messages from 2.6.30 and 2.6.32
Index(es):
- Date
- Thread