1 |
On Tue, May 31, 2011 at 3:14 AM, Pandu Poluan <pandu@××××××.info> wrote: |
2 |
> Meh, I clicked 'Send' too fast. |
3 |
> |
4 |
> *My* suggested solution: |
5 |
> |
6 |
> Generate an initramfs containing udev. The hands-down easiest way is |
7 |
> using genkernel's 'only create an initramfs' switch (sorry I forgot |
8 |
> what exactly). |
9 |
|
10 |
good god no, please, anything but genkernel. |
11 |
|
12 |
That thing is an attempt to emulate binary distros which require an |
13 |
initramfs to work properly (for any sane definition of "work") as the |
14 |
person building the installer has no idea what hardware the user will |
15 |
have. In Gentoo the user knows exactly what they have so there's no |
16 |
need for a gigantic hardware-detecting workaround at boot time. |
17 |
|
18 |
> This needs to be done exactly once throughout the life of your VM. |
19 |
> |
20 |
> (To the herd of Gentoo graybeards, feel free to CMIIW) |
21 |
|
22 |
Or wait a few days for vapier's (posting under his other name of |
23 |
spanky) sane advice to be implemented. His proposal is the sole voice |
24 |
of reason in that bug thread.... |
25 |
|
26 |
|
27 |
> |
28 |
> Another alternative would be to mknod all required devices for |
29 |
> booting. But, as evidenced in the bug I've linked to earlier, you |
30 |
> might have to create more than 20 devs. Not a good use of time, if you |
31 |
> ask me. Except if you're one of the guys doing the bug exorcising :) |
32 |
> |
33 |
> Oh, and please forgive my top-postings. Gmail's Java mobile client sucks. |
34 |
> |
35 |
> Rgds, |
36 |
> |
37 |
> |
38 |
> On 2011-05-31, walt <w41ter@×××××.com> wrote: |
39 |
>> In preparation for the upcoming "upgrade" to gnome3, I've installed |
40 |
>> the latest gentoo snapshot to a new virtualbox machine. (So I can |
41 |
>> trash my virtual gentoo machine instead of my real gentoo machine :) |
42 |
>> |
43 |
>> The virtual install went perfectly AFAICT, except for building a new |
44 |
>> customized kernel for the gentoo virtualbox machine. |
45 |
>> |
46 |
>> Here's what I did to configure my new customized gentoo kernel: |
47 |
>> |
48 |
>> I booted the gentoo install iso image in virtualbox and did lspci -k |
49 |
>> and wrote down all the drivers it displayed. |
50 |
>> |
51 |
>> I also booted my virtualbox ubuntu machine and did lspci -k and again |
52 |
>> wrote down all the listed drivers. (Only one extra driver showed up |
53 |
>> in ubuntu and I included it in my list of drivers to-be-installed.) |
54 |
>> |
55 |
>> I configured my new gentoo custom kernel to use all of the drivers I'd |
56 |
>> gathered from the steps above, and compiled and installed it without |
57 |
>> any problems. |
58 |
>> |
59 |
>> However, when I reboot the virtual gentoo guest machine with my new |
60 |
>> customized kernel, the boot hangs forever after discovering devices |
61 |
>> and mounting the root partition.ro. |
62 |
>> |
63 |
>> Obviously I've configured my custom kernel incorrectly, but how? |
64 |
>> |
65 |
>> If any of you have virtualbox guest gentoo machines running with a |
66 |
>> custom kernel, would you please post your guest .config file for my |
67 |
>> edification? |
68 |
>> |
69 |
>> Many thanks! |
70 |
>> |
71 |
>> |
72 |
>> |
73 |
> |
74 |
> |
75 |
> -- |
76 |
> -- |
77 |
> Pandu E Poluan - IT Optimizer |
78 |
> My website: http://pandu.poluan.info/ |
79 |
> |
80 |
> |
81 |
|
82 |
|
83 |
|
84 |
-- |
85 |
Alan McKinnon |
86 |
alan dot mckinnon at gmail dot com |