From: Eric <eric@cisu.net>
To: Zoltan NAGY <nagyz@nefty.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: v2.6 in vmware?
Date: Wed, 18 Feb 2004 11:44:14 -0600 [thread overview]
Message-ID: <200402181144.14794.eric@cisu.net> (raw)
In-Reply-To: <634316431.20040218143725@nefty.hu>
On Wednesday 18 February 2004 7:37 am, Zoltan NAGY wrote:
> Hi!
>
> I've been trying to get 2.6.x working in vmware4, but it drops some
> oopses during init... I cannot provide details, but I'm sure that it
> does not just me who are having problems with it..
Right now I am using Vmware 4.something in kernel 2.6.2-rc3 and will upgrade
to 2.6.3 and im pretty sure it will work. Make sure you use the appropriate
install script. Someone has published their own patches to make VMware more
compatible w/ 2.6.
Do a google for vmware-any-any-update49.tar.gz or updateXX where XX might be
a newer version. I have not had any oopses with this package. The only
problem I have is some older versions of the update package wouldnt compile.
Perhaps you are insmodding a module built for 2.4 and crashing the kernel?
> Regards,
>
> --
> Zoltan NAGY,
> Network Administrator
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
-------------------------
Eric Bambach
Eric at cisu dot net
-------------------------
next prev parent reply other threads:[~2004-02-18 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 13:37 v2.6 in vmware? Zoltan NAGY
2004-02-18 17:27 ` Herbert Poetzl
2004-02-18 17:44 ` Eric [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-18 12:53 Petr Vandrovec
2004-02-18 19:23 ` Alexander Hoogerhuis
2004-02-18 20:06 ` Petr Vandrovec
2004-02-18 20:33 ` Zwane Mwaikambo
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=200402181144.14794.eric@cisu.net \
--to=eric@cisu.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nagyz@nefty.hu \
/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