From: Avery Fay <avery@ravencode.com>
To: linux-kernel@vger.kernel.org
Subject: Re: via-rhine broken in 2.6.12-rc6 and 2.6.11 stable
Date: Wed, 15 Jun 2005 13:20:16 -0400 [thread overview]
Message-ID: <1118856017.2987.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1118854779.3107.7.camel@localhost.localdomain>
Nevermind about the stable kernel part. For some reason, my symbolic
links were not getting updated right. But it definitely doesn't work on
2.6.12-rc6 and it's definitely related to vmware. Is this something that
vmware needs to fix?
On Wed, 2005-06-15 at 12:59 -0400, Avery Fay wrote:
> Hello,
>
> I just upgraded to the latest Debian release of 2.6.11. via-rhine
> breaks. I also tried 2.6.12-rc6 and it's broken too. A few notes:
>
> 1.) this is an Averatec 3225hs laptop
> 2.) I'm using vmware too w/vmnet module
> 3.) Worked on previous 2.6.11 debian releases
> 4.) when i bring this interface up, i'm also enabling nat
--
Avery Fay <avery@ravencode.com>
next prev parent reply other threads:[~2005-06-15 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 16:59 via-rhine broken in 2.6.12-rc6 and 2.6.11 stable Avery Fay
2005-06-15 17:20 ` Avery Fay [this message]
2005-06-15 18:00 ` Jesper Juhl
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=1118856017.2987.1.camel@localhost.localdomain \
--to=avery@ravencode.com \
--cc=linux-kernel@vger.kernel.org \
/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