Bug 392666

Summary:	kiwi: LiveCD of openSUSE 11.0 has trouble with multiple CD-drives.
Product:	[openSUSE] openSUSE 11.0	Reporter:	Martin Møller <martin>
Component:	Bootloader	Assignee:	Marcus Schaefer <ms>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Factory
Target Milestone:	---
Hardware:	i686
OS:	openSUSE 11.0
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Martin Møller 2008-05-20 15:25:29 UTC

When I first tried installing/booting the KDE LiveCD of openSUSE 11.0 rc1 a few days ago it got stuck trying to find the CD and eventually gave up.

Since I've seen similar things before, I ejected the CD and put it in my other DVD drive (top one a DVD burner, lower one just a DVD drive).

This made Kiwi find it just fine and boot up as it should.

My guess is that Kiwi never tries anything beyond the first CD/DVD drive it finds, which is a shame and should be fixed.

It shouldn't take much extra effort to enumerate all CD/DVD drives available (possibly USB sticks and the like as well?) rather than what is happening now.

I can get past this issue as described above, but I can imagine many not even trying just thinking the product is defective.

/Martin.

Comment 1 Jiri Srain 2008-05-21 06:45:25 UTC

Marcus, how does the Kiwi boot system handle multiple CD/DVD drives?

Comment 2 Marcus Schaefer 2008-05-21 13:10:04 UTC

> My guess is that Kiwi never tries anything beyond the first CD/DVD drive it
> finds, which is a shame and should be fixed

your guess is wrong. kiwi detects all drives it can find by calling
hwinfo --cdrom. See the function CDDevice from KIWILinuxRC.sh. it collects
all devices from hwinfo and stores them into a variable named $cddev.
After that it tries to mount all devices in the order of their detection
To identify the correct media it searches for the file config.isoclient.
The first device which provides this file is used.

I think there is no proper reason to shame for it and I can't understand
the rude report

To be able to find the reason why it hasn't worked one can do the
following:

   - revert to the situation were it has failed
   - boot with the kernel parameter kiwidebug=1
   - when it can't find a suitable device it will stop and run a shell
   - from this shell try to investigate why it failed:

     a) hwinfo --cdrom
     b) take a look at /var/log/boot.kiwi

Thanks

Comment 3 Martin Møller 2008-05-21 13:38:26 UTC

Okay, it may have come out harsher than I though. Sorry about that.
I'll do a few more tests, but I will probably need to know how to get kiwi to load usb-hid in the start-phase or I will have no keyboard and can do no interaction.

I'll try insmod=usb-hid and hope that will do it.

I didn't mean to be rude, I just found the problem very odd.

I'll try it on my other 2 CD/DVD drive machines if I get the chance.

I'll be back with whatever data I am able to get.

Comment 4 Martin Møller 2008-05-21 13:58:35 UTC

Okay, insmod=usb-hid is apparently not the way to go.
I tried searching through kiwi.pdf, but didn't find any mention of how to load a specific module at boot.

The machine in question has no PS/2 ports so I only have USB for input.

I get 6 lines of 'Drive not ready... waiting' and then it gives up.

Even with kiwidebug=1, there was no extra information on console 1 and without USB keyboard support I have no way of seeing what is on the other consoles...

Tried 'kiwimodule=usb-hid' (just an off chance). Didn't get keyboard support here either.

Help!

I can provide you the output of hwinfo --cdrom from inside the 11.0 system I got running by booting from the other drive if it will be helpful to you.

Comment 5 Marcus Schaefer 2008-05-26 15:44:28 UTC


*** This bug has been marked as a duplicate of bug 390934 ***