[opensuse-autoinstall] "EDD information not available" messages during v11.1 autoyast install?
I'm building/booting a Xen DomU using an Autoyast template. Under opensuse v11.0 (as Dom0 & DomU) all's well. Under v11.1, I see a bunch of 'new', EDD-related messsages @ console -- & I'm not clear if they're just new diagnostic, or a new problem: ... >>> openSUSE installation program v3.3.22 (c) 1996-2008 SUSE Linux Products GmbH <<< Starting udev... udevd version 128 started rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 netfront: Initialising virtual ethernet driver. xen-vbd: registered block device major 202 blkfront: xvda: barriers enabled xvda: unknown partition table ok GGLoading basic drivers...Uniform Multi-Platform E-IDE driver SCSI subsystem initialized st: Version 20080504, fixed bufsize 32768, s/g segs 256 BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. NET: Registered protocol family 17 BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. NET: Registered protocol family 10 lo: Disabled Privacy Extensions BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. RPC: Registered udp transport module. RPC: Registered tcp transport module. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. loop: module loaded BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. ok BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. Starting hardware detection... ok (If a driver is not working for you, try booting with brokenmodules=driver_name.) Xen Virtual Storage 0 ... My autoyast template starts with, <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <initrd_module><module>edd</module></initrd_module> <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> ... Something's changed from v11.0 -> v11.1. Is there something I need to do differently to avoid/fix these messages? Or, are they not a problem, just 'noisy' reporting? Thanks. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Saturday 03 January 2009 PGNet wrote:
I'm building/booting a Xen DomU using an Autoyast template.
Under opensuse v11.0 (as Dom0 & DomU) all's well. Under v11.1, I see a bunch of 'new', EDD-related messsages @ console -- & I'm not clear if they're just new diagnostic, or a new problem:
have you tried to add "edd=off" to the linuxrc parameter list? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Burn Down Heaven" by Straftanz -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi Uwe, On Thu, Jan 8, 2009 at 3:04 AM, Uwe Gansert <ug@suse.de> wrote:
have you tried to add "edd=off" to the linuxrc parameter list?
I'm not clear exactly where you mean ... I *have* added in my autoyast.xml, ... <bootloader> <loader_type>grub</loader_type> ... <sections config:type="list"> <section> <original_name>linux</original_name> <name>title openSUSE 11.1 - Xen DomU (default)</name> <kernel>(hd0,0)/boot/vmlinuz-xen</kernel> <image>(hd0,0)/boot/vmlinuz-xen</image> <initrd>(hd0,0)/boot/initrd-xen</initrd> <append>resume=resume=/dev/system/swap kbdtype=us headless text quiet nofb selinux=0 edd=off splash=silent noshell showopts</append> <initial>1</initial> <lines_cache_id>0</lines_cache_id> <root>/dev/system/root</root> <type>image</type> <vga>0x317</vga> <vgamode>0x317</vgamode> </section> </sections> </bootloader> ... But that has no effect. Did you mean somewhere else, perhaps? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
* PGNet [2009-01-08 07:49]:
Hi Uwe,
On Thu, Jan 8, 2009 at 3:04 AM, Uwe Gansert <ug@suse.de> wrote:
have you tried to add "edd=off" to the linuxrc parameter list?
I'm not clear exactly where you mean ...
I *have* added in my autoyast.xml,
But that's only for the 2nd boot. 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). Bernhard -- Bernhard Walle, SUSE Linux Products GmbH, Architecture Development -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Hi, On Thu, Jan 8, 2009 at 8:02 AM, Bernhard Walle <bwalle@suse.de> 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=e... 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@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
Bernhard Walle -
PGNet -
Uwe Gansert