| 1 |
Hi Jeff, |
| 2 |
|
| 3 |
>J-S, can you give me a pointer to the MILO you are |
| 4 |
>using for your XLT? I've had mine for so long, I don't |
| 5 |
>know where I got it from anymore. |
| 6 |
> |
| 7 |
> |
| 8 |
I can send it to you privately if you want. It'll be following this |
| 9 |
mail. I don't really remember by heart which version I use... So it's |
| 10 |
easier to send it to you. :-) |
| 11 |
|
| 12 |
>Could it be that the MILO I have was built with some |
| 13 |
>version of libz incompatible with current kernels |
| 14 |
>builds? |
| 15 |
> |
| 16 |
> |
| 17 |
I doubt it... One thing to check : I have found that MILO does some name |
| 18 |
mangling when there are more than one period in the filename. For |
| 19 |
example, even though the initrd's filename on the 2005.0 Gentoo LiveCD |
| 20 |
is gentoo_2.4.igz, I have to type 'initrd=gentoo_2_4.igz' in my boot |
| 21 |
command. Maybe something similar is happening to you? At the MILO |
| 22 |
prompt, try doing an 'ls' on your boot partition / directory to see what |
| 23 |
MILO sees the filenames as. |
| 24 |
|
| 25 |
Other than that, I don't have any other ideas... Generally, if you use |
| 26 |
the filename as seen in an 'ls' from the MILO prompt, the kernel should |
| 27 |
start to load, and after that it all depends on the build options and |
| 28 |
other parameters in the boot command. With my MILO image, anyways, I can |
| 29 |
boot my latest kernels without any problems. |
| 30 |
|
| 31 |
Good luck, |
| 32 |
|
| 33 |
J-S |
| 34 |
|
| 35 |
-- |
| 36 |
___________________________________________ |
| 37 |
Jean-Sébastien Guay jean_seb@×××××××××.ca |
| 38 |
http://whitestar02.webhop.org/ |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-alpha@g.o mailing list |
Archives