On 9/25/10 1:23 AM, Tim wrote:
> On Fri, 2010-09-24 at 19:53 -0700, James McKenzie wrote:
>> Well, I finally made it to the site. There is "Free" and "NonFree",
>> which I had interpreted to mean "Pay", the opposite of "Free".
> "Freedom," in this case, from various restrictions, or not quite so
On 09/25/2010 08:47 AM, Patrick O'Callaghan wrote:
> On Sat, 2010-09-25 at 18:37 +1000, Roger wrote:
I use upstream virtual box + dkms - and I have not had 1 problem with
any kernel update.
just another data point ..
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or chan
On Sat, 2010-09-25 at 18:37 +1000, Roger wrote:
> On 25/09/10 18:23, Tim wrote:
> > On Fri, 2010-09-24 at 19:53 -0700, James McKenzie wrote:
> >> Well, I finally made it to the site. There is "Free" and "NonFree",
> >> which I had interpreted to mean "Pay", the opposite of "Free".
> > "Freedom," i
On 25/09/10 18:23, Tim wrote:
> On Fri, 2010-09-24 at 19:53 -0700, James McKenzie wrote:
>> Well, I finally made it to the site. There is "Free" and "NonFree",
>> which I had interpreted to mean "Pay", the opposite of "Free".
> "Freedom," in this case, from various restrictions, or not quite so
On Fri, 2010-09-24 at 19:53 -0700, James McKenzie wrote:
> Well, I finally made it to the site. There is "Free" and "NonFree",
> which I had interpreted to mean "Pay", the opposite of "Free".
"Freedom," in this case, from various restrictions, or not quite so free
from them.
--
[...@localhost
On 9/22/10 2:03 PM, Michael Cronenworth wrote:
> James Mckenzie wrote:
>> However, a kernel update should not necessarily break its functionality.
>> This update did with obvious results.
> Fedora is not responsible for out-of-distribution software.
>
>> I don't think that RPMFusion provides th
Dear Gabriel,
On Thu, 23 Sep 2010, Gabriel Ramirez wrote:
seems which your machine don't have installed the kmod metapackage for
VirtualBox-OSE:
kmod-VirtualBox-OSE-3.2.6-1.fc13.8.x86_64
try the following 2 steps:
yum reinstall kmod-VirtualBox-OSE
yum update
you perfectly got the sign, kmo
On Wed, 22 Sep 2010, Patrick Bartek wrote:
Do you have the dkms package installed on your system? With it a new
vbox kernel module should automatically be rebuilt when the kernel is
updated. I have it installed on my Fedora 12 64-bit system and it
works just fine. Of course, you'll need to ha
On 09/22/2010 11:01 AM, Walter Cazzola wrote:
> Dear Fedorians,
> I'm a new user of fedora 13 and I use a virtualbox installation on it.
>
> Unfortunately the last two kernel upgrades (2.6.34.6-54 and 2.6.34.7-56)
> didn't correspond to an upgrade of the kernel modules necessary by
> virtualbox (vb
--- On Wed, 9/22/10, Walter Cazzola wrote:
> On Wed, 22 Sep 2010, Greg Woods
> wrote:
>
> > On Wed, 2010-09-22 at 18:01 +0200, Walter Cazzola
> wrote:
>
> >> Unfortunately the last two kernel upgrades
> (2.6.34.6-54 and 2.6.34.7-56)
> >> didn't correspond to an upgrade of the kernel
> modules n
On 09/22/2010 03:47 PM, James Mckenzie wrote:
> Michael Cronenworth wrote:
>> Sent: Sep 22, 2010 11:58 AM
>> To: users@lists.fedoraproject.org
>> Subject: Re: kernel update breaks virtualbox
>>
>> Walter Cazzola wrote:
>>> I'm a new user of fedo
Michael Cronenworth wrote:
>Sent: Sep 22, 2010 2:03 PM
>To: users@lists.fedoraproject.org
>Subject: Re: kernel update breaks virtualbox
>
>James Mckenzie wrote:
>> However, a kernel update should not necessarily break its functionality.
>> This update did with obviou
On Wed, Sep 22, 2010 at 01:47:51PM -0700, James Mckenzie wrote:
> You state the obvious. Virtualbox is produced by Oracle.
> However, a kernel update should not necessarily break its functionality.
> This update did with obvious results.
That'd be a reasonable expectation for user-space level fun
James Mckenzie wrote:
> However, a kernel update should not necessarily break its functionality.
> This update did with obvious results.
Fedora is not responsible for out-of-distribution software.
>
> I don't think that RPMFusion provides this, but I've not been able to get to
> the 'pay' side
Michael Cronenworth wrote:
>Sent: Sep 22, 2010 11:58 AM
>To: users@lists.fedoraproject.org
>Subject: Re: kernel update breaks virtualbox
>
>Walter Cazzola wrote:
>> I'm a new user of fedora 13 and I use a virtualbox installation on it.
>
>VirtualBox is not Fedora s
Walter Cazzola wrote:
> I'm a new user of fedora 13 and I use a virtualbox installation on it.
VirtualBox is not Fedora software.
Please post your message on the RPMFusion mailing list[1].
Off-topic: The problem is because you are using a kmod, which does not
automatically update when you updat
On 09/22/2010 01:13 PM, Walter Cazzola wrote:
> On Wed, 22 Sep 2010, Steven Stern wrote:
>
Did you try running "service vboxdrv setup"? That should cause it to
build kernel modules for the running kernel. I have to do this every
time I do a kernel update.
>
>>> unfortunately I can'
On Wed, 22 Sep 2010, Steven Stern wrote:
Did you try running "service vboxdrv setup"? That should cause it to
build kernel modules for the running kernel. I have to do this every
time I do a kernel update.
unfortunately I can't do, when I try I get:
>service vboxdrv setup
vboxdrv: unrec
On 09/22/2010 01:03 PM, Walter Cazzola wrote:
> On Wed, 22 Sep 2010, Genes MailLists wrote:
>
>> On 09/22/2010 12:01 PM, Walter Cazzola wrote:
>>> Dear Fedorians,
>>> I'm a new user of fedora 13 and I use a virtualbox installation on it.
>
>> For what its worth, I'm running 2.6.34.7-56.fc13.x86
On 09/22/2010 01:04 PM, Walter Cazzola wrote:
> On Wed, 22 Sep 2010, Greg Woods wrote:
>
>> On Wed, 2010-09-22 at 18:01 +0200, Walter Cazzola wrote:
>
>>> Unfortunately the last two kernel upgrades (2.6.34.6-54 and 2.6.34.7-56)
>>> didn't correspond to an upgrade of the kernel modules necessary b
On Wed, 22 Sep 2010, Greg Woods wrote:
On Wed, 2010-09-22 at 18:01 +0200, Walter Cazzola wrote:
Unfortunately the last two kernel upgrades (2.6.34.6-54 and 2.6.34.7-56)
didn't correspond to an upgrade of the kernel modules necessary by
virtualbox (vboxdrv, vboxnetflt, and vboxnetadp); this im
On Wed, 22 Sep 2010, Genes MailLists wrote:
On 09/22/2010 12:01 PM, Walter Cazzola wrote:
Dear Fedorians,
I'm a new user of fedora 13 and I use a virtualbox installation on it.
For what its worth, I'm running 2.6.34.7-56.fc13.x86_64 with upstream
(i.e. cisco repository, not the OSE version
On Wed, 2010-09-22 at 18:01 +0200, Walter Cazzola wrote:
> Unfortunately the last two kernel upgrades (2.6.34.6-54 and 2.6.34.7-56)
> didn't correspond to an upgrade of the kernel modules necessary by
> virtualbox (vboxdrv, vboxnetflt, and vboxnetadp); this impedes the
> normal behavior of virtual
On 09/22/2010 12:01 PM, Walter Cazzola wrote:
> Dear Fedorians,
> I'm a new user of fedora 13 and I use a virtualbox installation on it.
>
For what its worth, I'm running 2.6.34.7-56.fc13.x86_64 with upstream
(i.e. cisco repository, not the OSE version) virtualbox with dkms - and
have no probl
Dear Fedorians,
I'm a new user of fedora 13 and I use a virtualbox installation on it.
Unfortunately the last two kernel upgrades (2.6.34.6-54 and 2.6.34.7-56)
didn't correspond to an upgrade of the kernel modules necessary by
virtualbox (vboxdrv, vboxnetflt, and vboxnetadp); this impedes the
nor
25 matches
Mail list logo
