Mailinglist Archive: opensuse-autoinstall (46 mails)
| < Previous | Next > |
Re: [opensuse-autoinstall] Re: "EDD information not available" messages during v11.1 autoyast install?
- From: PGNet <pgnet.trash+osyast@xxxxxxxxx>
- Date: Thu, 8 Jan 2009 08:25:26 -0800
- Message-id: <dbd51810901080825s6b790be2m5a286ca7fbe9d353@xxxxxxxxxxxxxx>
Hi,
On Thu, Jan 8, 2009 at 8:02 AM, Bernhard Walle <bwalle@xxxxxxx> wrote:
2nd boot? Hm. More reading-up on the process required ...
Currently, testing in Xen, I'm creating the DomU with,
xm create test.cfg
where,
vi test.cfg
...
extra = 'textmode=1 xencons=tty edd=off
autoyast=nfs://192.168.1.130/home/xen/os11_1/autoyast.xml
install=http://suse.mirrors.tds.net/pub/opensuse/distribution/11.1/repo/oss?device=eth0
hostip=192.160.1.2/24 gateway=192.168.1.1 nameserver=192.168.1.1'
...
Is that the "first boot" location that I need to address in this case?
I suspect it's this:
https://bugzilla.novell.com/show_bug.cgi?id=463406
where Jan suggests removing the edd.ko module from the DomU.
If that *is* the right solution here, how do I correctly *remove* the
module from the autoyast startup? Currently, my .xml includes only,
<bootloader>
<loader_type>grub</loader_type>
<initrd_modules config:type="list">
<initrd_module><module>xenblk</module> </initrd_module>
<initrd_module><module>xennet</module> </initrd_module>
<initrd_module><module>processor</module></initrd_module>
<initrd_module><module>thermal</module> </initrd_module>
<initrd_module><module>fan</module> </initrd_module>
<initrd_module><module>jbd</module> </initrd_module>
<initrd_module><module>ext3</module> </initrd_module>
<initrd_module><module>dm_mod</module> </initrd_module>
</initrd_modules>
I.e, I'm not specifically *installing* the module ...
IIUC, either an "edd=off" -- in the right place, of course -- or some
module-remove directive is needed?
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx
On Thu, Jan 8, 2009 at 8:02 AM, Bernhard Walle <bwalle@xxxxxxx> wrote:
But that's only for the 2nd boot.
2nd boot? Hm. More reading-up on the process required ...
For the installation you need to
provide that in the installation command line (when you boot the media
or in the PXE configuration, we don't know how you boot).
Currently, testing in Xen, I'm creating the DomU with,
xm create test.cfg
where,
vi test.cfg
...
extra = 'textmode=1 xencons=tty edd=off
autoyast=nfs://192.168.1.130/home/xen/os11_1/autoyast.xml
install=http://suse.mirrors.tds.net/pub/opensuse/distribution/11.1/repo/oss?device=eth0
hostip=192.160.1.2/24 gateway=192.168.1.1 nameserver=192.168.1.1'
...
Is that the "first boot" location that I need to address in this case?
I suspect it's this:
https://bugzilla.novell.com/show_bug.cgi?id=463406
where Jan suggests removing the edd.ko module from the DomU.
If that *is* the right solution here, how do I correctly *remove* the
module from the autoyast startup? Currently, my .xml includes only,
<bootloader>
<loader_type>grub</loader_type>
<initrd_modules config:type="list">
<initrd_module><module>xenblk</module> </initrd_module>
<initrd_module><module>xennet</module> </initrd_module>
<initrd_module><module>processor</module></initrd_module>
<initrd_module><module>thermal</module> </initrd_module>
<initrd_module><module>fan</module> </initrd_module>
<initrd_module><module>jbd</module> </initrd_module>
<initrd_module><module>ext3</module> </initrd_module>
<initrd_module><module>dm_mod</module> </initrd_module>
</initrd_modules>
I.e, I'm not specifically *installing* the module ...
IIUC, either an "edd=off" -- in the right place, of course -- or some
module-remove directive is needed?
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx
| < Previous | Next > |