1 |
On Thu, 2007-07-05 at 11:36 +0200, Galevsky wrote: |
2 |
> Many thanks for you suggestion. I tried a boot with no fall back, but |
3 |
> nothing added neither to boot.log nor to dmesg. I am sure to target |
4 |
> the right kernel image with no typo into grub.conf . This new kernel |
5 |
> is a =xen-sources-2.6.16.49, and I configured it making an oldconfig |
6 |
> based on current =gentoo-sources-2.6.20 running kernel. So, errors |
7 |
> cannot come from drivers or such things, but specific xen options. |
8 |
> Does anyone know any xen option able to prevent the kernel to boot up |
9 |
> ? |
10 |
|
11 |
I guess I (still) don't understand what your issue is. So I went back |
12 |
and read your original post. Maybe I misunderstood it. |
13 |
|
14 |
* What do you mean by "remote host"? |
15 |
* If your box "does not boot" how would you expect to see a |
16 |
boot.log or dmesg? They don't exist if the system has not |
17 |
booted. In fact "does not boot" implies that you can't even log |
18 |
in to check for dmesg or boot logs. Perhaps you can explain |
19 |
what it is exactly you mean by "does not boot". |
20 |
* Usually there is an error message on the console if there is a |
21 |
boot loader/kernel issue with booting. |
22 |
* Also you never posted your grub.conf. |
23 |
|
24 |
So hopefully you can come up with a specific explanation of "does not |
25 |
boot" as well as your config and any console messages you get. Else |
26 |
this becomes a "blind leading the blind" issue. |
27 |
|
28 |
|
29 |
|
30 |
-- |
31 |
Albert W. Hopkins |
32 |
|
33 |
-- |
34 |
gentoo-user@g.o mailing list |