Mailinglist Archive: opensuse (1196 mails)
| < Previous | Next > |
Re: [opensuse] Why is root device hardcoded in initrd and how could it be prevented?
- From: Tejas Guruswamy <masterpatricko@xxxxxxxxx>
- Date: Mon, 18 Jan 2010 15:15:03 +0000
- Message-id: <4B547AF7.2030007@xxxxxxxxx>
On 18/01/10 14:52, Istvan Gabor wrote:
8 mkinitrd.
Regards,
Tejas
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
Yes, I tried it. I have two problems with this solution:Boot off a rescue system, chroot into the drive, mkinitrd should work.
1. I don't know how to make an initrd image to the system if it is not
running.
Do you know how to create initrd image for a system which is not running?
2. I used the install DVD to boot the copied system and ran mkinitrd. Thistry mkinitrd -s 1024x768 (or whatever resolution you want) - look at man
solution worked but the new initrd can boot only in text mode, graphical boot
mode is lost. There is a graphical message window but after that step booting
always continues in text mode.
How can I make an initrd image that allows graphical boot?
8 mkinitrd.
Regards,
Tejas
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |