Re: [gentoo-user] Re: Is my machine too old for virtualbox?

2009-09-27 Thread Volker Armin Hemmann 
On Sonntag 27 September 2009, David Relson wrote:
> On Sun, 27 Sep 2009 14:01:02 -0400
> 
> Walter Dnes wrote:
> > On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote
> >
> > > I'm using the vbox svn repository from Sun, so I haven't tried
> > > building the portage version.
> >
> >   As I mentioned, I'm using Sun's install because the portage install
> > dies.
> >
> > > What problem do you see?
> >
> >   At bootup I get...
> >  * Starting VirtualBox kernel module ...
> >  * modprobe vboxdrv failed. Please use 'dmesg' to find out why
> >
> >   I'm attaching dmesg output in the hope that someone can figure this
> > out.
> 
> Do you have vboxdrv in your kernel?  My kernel has the module build,
> as evidenced by command 'locate vboxdrv' displaying:
> 
> /lib64/modules/2.6.28-gentoo-r5-xfs/misc/vboxdrv.ko
> 
> I'm don't know which kernel option creates vboxdrv, but google surely
> knows :->
> 
> HTH,
> 
> David
> 

none does. You have to emerge the vbox driver.

Re: [gentoo-user] Re: Is my machine too old for virtualbox?

2009-09-27 Thread David Relson 
On Sun, 27 Sep 2009 14:01:02 -0400
Walter Dnes wrote:

> On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote
> 
> > I'm using the vbox svn repository from Sun, so I haven't tried
> > building the portage version.
> 
>   As I mentioned, I'm using Sun's install because the portage install
> dies.
> 
> > What problem do you see?
> 
>   At bootup I get...
>  * Starting VirtualBox kernel module ...
>  * modprobe vboxdrv failed. Please use 'dmesg' to find out why
> 
>   I'm attaching dmesg output in the hope that someone can figure this
> out.
> 
> -- 
> Walter Dnes 

Do you have vboxdrv in your kernel?  My kernel has the module build,
as evidenced by command 'locate vboxdrv' displaying:

/lib64/modules/2.6.28-gentoo-r5-xfs/misc/vboxdrv.ko

I'm don't know which kernel option creates vboxdrv, but google surely
knows :->

HTH,

David

Re: [gentoo-user] Re: Is my machine too old for virtualbox?

2009-09-27 Thread Jesús Guerrero 
On Sun, 27 Sep 2009 14:01:02 -0400, "Walter Dnes" 
wrote:
> On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote
> 
>> I'm using the vbox svn repository from Sun, so I haven't tried building
>> the portage version.
> 
>   As I mentioned, I'm using Sun's install because the portage install
> dies.
> 
>> What problem do you see?
> 
>   At bootup I get...
>  * Starting VirtualBox kernel module ...
>  * modprobe vboxdrv failed. Please use 'dmesg' to find out why
> 
>   I'm attaching dmesg output in the hope that someone can figure this
> out.

The attached output doesn't seem to have anything related to vboxdrv at
all. 

In any case, did you check that you are compiling the driver against the
right kernel? Look at the output of uname -r, and make sure that the
symlink /usr/src/linux points to the current kernel version, then recompile
the drivers package.
-- 
Jesús Guerrero

Re: [gentoo-user] Re: Is my machine too old for virtualbox?

2009-09-27 Thread Volker Armin Hemmann 
On Sonntag 27 September 2009, Walter Dnes wrote:
> On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote
> 
> > I'm using the vbox svn repository from Sun, so I haven't tried building
> > the portage version.
> 
>   As I mentioned, I'm using Sun's install because the portage install
> dies.
> 
> > What problem do you see?
> 
>   At bootup I get...
>  * Starting VirtualBox kernel module ...
>  * modprobe vboxdrv failed. Please use 'dmesg' to find out why
> 
>   I'm attaching dmesg output in the hope that someone can figure this
> out.
> 

how about dmesg after you tried to load vboxdrv?

Re: [gentoo-user] Re: Is my machine too old for virtualbox?

2009-09-27 Thread Walter Dnes 
On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote

> I'm using the vbox svn repository from Sun, so I haven't tried building
> the portage version.

  As I mentioned, I'm using Sun's install because the portage install
dies.

> What problem do you see?

  At bootup I get...
 * Starting VirtualBox kernel module ...
 * modprobe vboxdrv failed. Please use 'dmesg' to find out why

  I'm attaching dmesg output in the hope that someone can figure this
out.

-- 
Walter Dnes 
Linux version 2.6.29-gentoo-r5 (r...@d530) (gcc version 4.3.2 (Gentoo 4.3.2-r3 
p1.6, pie-10.1.5) ) #1 SMP Fri Jul 10 23:46:49 EDT 2009
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  NSC Geode by NSC
  Cyrix CyrixInstead
  Centaur CentaurHauls
  Transmeta GenuineTMx86
  Transmeta TransmetaCPU
  UMC UMC UMC UMC
BIOS-provided physical RAM map:
 BIOS-e820:  - 00099c00 (usable)
 BIOS-e820: 00099c00 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - 7f59 (usable)
 BIOS-e820: 7f59 - 7f5e3000 (ACPI NVS)
 BIOS-e820: 7f5e3000 - 7f5f (ACPI data)
 BIOS-e820: 7f5f - 7f60 (reserved)
 BIOS-e820: e000 - f000 (reserved)
 BIOS-e820: fec0 - 0001 (reserved)
DMI 2.5 present.
last_pfn = 0x7f590 max_arch_pfn = 0x10
kernel direct mapping tables up to 377fe000 @ 7000-c000
ACPI: RSDP 000F96C0, 0024 (r2 DELL  )
ACPI: XSDT 7F5E3080, 005C (r1 DELLFX0942302E31 AWRD0)
ACPI: FACP 7F5E7200, 00F4 (r3 DELLFX0942302E31 AWRD0)
ACPI Warning (tbfadt-0568): 32/64X length mismatch in Pm1aEventBlock: 32/8 
[20081204]
ACPI Warning (tbfadt-0568): 32/64X length mismatch in Pm1aControlBlock: 16/8 
[20081204]
ACPI Warning (tbfadt-0568): 32/64X length mismatch in PmTimerBlock: 32/8 
[20081204]
ACPI Warning (tbfadt-0568): 32/64X length mismatch in Gpe0Block: 128/8 
[20081204]
ACPI Warning (tbfadt-0412): Invalid length for Pm1aEventBlock: 8, using default 
32 [20081204]
ACPI Warning (tbfadt-0412): Invalid length for Pm1aControlBlock: 8, using 
default 16 [20081204]
ACPI Warning (tbfadt-0412): Invalid length for PmTimerBlock: 8, using default 
32 [20081204]
FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
ACPI: DSDT 7F5E3200, 3FFC (r1 DELL   AWRDACPI 1000 MSFT  300)
ACPI: FACS 7F59, 0040
ACPI: HPET 7F5E73C0, 0038 (r1 DELLFX0942302E31 AWRD   98)
ACPI: MCFG 7F5E7400, 003C (r1 DELLFX0942302E31 AWRD0)
ACPI: SLIC 7F5E7440, 0176 (r1 DELLFX0942302E31 AWRD0)
ACPI: DMY2 7F5E75C0, 0080 (r1 DELLFX0942302E31 AWRD0)
ACPI: APIC 7F5E7300, 0084 (r1 DELLFX0942302E31 AWRD0)
ACPI: SSDT 7F5E7CA0, 0380 (r1  PmRefCpuPm 3000 INTL 20041203)
ACPI: Local APIC address 0xfee0
1149MB HIGHMEM available.
887MB LOWMEM available.
  mapped low ram: 0 - 377fe000
  low ram:  - 377fe000
  bootmap 8000 - ef00
(8 early reservations) ==> bootmem [00 - 00377fe000]
  #0 [00 - 001000]   BIOS data page ==> [00 - 001000]
  #1 [001000 - 002000]EX TRAMPOLINE ==> [001000 - 002000]
  #2 [006000 - 007000]   TRAMPOLINE ==> [006000 - 007000]
  #3 [10 - 705d54]TEXT DATA BSS ==> [10 - 705d54]
  #4 [706000 - 709000]INIT_PG_TABLE ==> [706000 - 709000]
  #5 [099c00 - 10]BIOS reserved ==> [099c00 - 10]
  #6 [007000 - 008000]  PGTABLE ==> [007000 - 008000]
  #7 [008000 - 00f000]  BOOTMAP ==> [008000 - 00f000]
found SMP MP-table at [c00f3e30] 000f3e30
Zone PFN ranges:
  DMA  0x -> 0x1000
  Normal   0x1000 -> 0x000377fe
  HighMem  0x000377fe -> 0x0007f590
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x -> 0x0099
0: 0x0100 -> 0x0007f590
On node 0 totalpages: 521513
free_area_init_node: node 0, pgdat c06264c0, node_mem_map c100
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 3961 pages, LIFO batch:0
  Normal zone: 1744 pages used for memmap
  Normal zone: 221486 pages, LIFO batch:31
  HighMem zone: 2300 pages used for memmap
  HighMem zone: 291990 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee0
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: IOAPIC (id[0x04] address[0xfec0] gsi_base[0])
IOAPIC[0]: apic_id 4, version 32, address 0xfec0,