>> there are no initrd= lines in my lilo.conf. At first boot I get a
>kernel> panic.

>is it an upgrade? or an install on a non-formatted /boot ?

>(more precisely occured when the initrd existed prior to DrakX)

>i've fixed a bug that way today, will upload this evening (< 6 hours)

clean install, format reiser prior to install, I need to ckeck the
log...
here:

* starting step `formatPartitions'
* formatting device hda8 (type Journalised FS: ReiserFS)
* running: mkreiserfs -ff /dev/hda8
mkreiserfs, 2002 - reiserfsprogs 3.6.2mkreiserfs: Guessing about desired
format.
.
mkreiserfs: Kernel 2.4.18-23mdkBOOT is running.
Initializing journal - 0%....20%....40%....60%....80%....100%
failed to genetate UUID
Format 3.6 with standard journal
Count of blocks on the device: 1102452
Number of blocks consumed by mkreiserfs formatting process: 8245
Blocksize: 4096
Hash function used to sort names: "r5"
Journal Size 8193 blocks (first block 18)
Journal Max transaction length 1024
inode generation number: 0
UUID: 00000000-0000-0000-0000-000000000000
Syncing..ok



the initrd is there and the symlink to it is there too

I'll put in some more logging to bootloader.pm, must be a reason why
there's no value of {initrd}

- Mark


Reply via email to