|
Bugzilla – Full Text Bug Listing |
Created attachment 209132 [details]
2
Marcus, any idea what to try? it seems the CD/DVD drive wasn't found. I use hwinfo to detect it. Several reasons are possible especially because we change so much in 11.0. More information is on the error console Alt-F3 I suggest the following: - boot with: kiwidebug=1 - switch to the error console as soon as possible - watch out for errors - the system will provide a shell: try to call /usr/sbin/hwinfo --cdrom what is displayed ? I have installed openSUSE 10.3 on the same machine. If entering error console wouldn't be possible, would it be enough to send an output of /usr/sbin/hwinfo --cdrom from 10.3 installation or is it necessary to boot with kiwidebug=1? 10.3 is completely different than 11.0 I need 11.0 information because on 10.3 it works :-) thanks for your time and effort After kiwidebug=1 i obtained again: could not find kernel image: kiwidebug=1 But, i have two dvd-rom. LG GSA 4163B (/dev/sr0) and LG GSA 4167B (/dev/sr1). So that i tried to boot from /dev/sr1. I obtained also could not find kernel image: Live-System but system started automatically booting (after aprox. 10 sec) and it was booted sucssesfully. attached output /usr/sbin/hwinfo --cdrom Created attachment 209430 [details]
output /usr/sbin/ --cdrom
sorry I don't understand your comment #6. Could you explain that more detailed ? - if you insert the CD do you see a graphical boot screen j/n - if there is such a boot screen did you enter kiwidebug=1 in the entry field at the bottom j/n - if you hit enter what happens ? and when does this "could not find kernel image" message appear sorry for asking such questions but I don't get the picture the graphical boot is broken - another bug. So you only get a text prompt (In reply to comment #9 from Stephan Kulow) > the graphical boot is broken - another bug. So you only get a text prompt Yes, excatly. (In reply to comment #8 from Marcus Schaefer) > sorry I don't understand your comment #6. Could you explain that more > detailed ? > > - if you insert the CD do you see a graphical boot screen j/n No, i don´t see a graphical boot screen. I see only what is on the first snapshot. > - if there is such a boot screen did you enter kiwidebug=1 in > the entry field at the bottom j/n I entered kiwidebug=1 instead of "Live-System" boot: kiwidebug=1 Could not find kernel image: kiwidebug=1 boot: Hm, but i´ve just realized that i did it wrong probably:-) > - if you hit enter what happens ? and when does this > "could not find kernel image" message appear > sorry for asking such questions but I don't get the picture > I´ll take a picture and i´ll attach, just to be sure. ah now I understand. So this is a duplicate of #381152. if you can't see the graphical boot screen no options neither kernel nor initrd information is provided to the default prompt of the isolinux bootloader. That's the reason why it can't find any kernel image All this should be fixed with the fix in #381152 but I need to test that with the latest 11.0 source first *** This bug has been marked as a duplicate of bug 381152 *** back to the original problem with beta2 :) *** Bug 386465 has been marked as a duplicate of this bug. *** I have a similar problem with Beta2 KDE Live CD. I see the graphical boot screen. But booting from CDROM stops with above error message : Couldn´t find CD image configuration file Booting from my second CDROM drive runs without problems. I have similar problem submited here (and judged duplicate): https://bugzilla.novell.com/show_bug.cgi?id=382807 However, in my case kernel seem to have no knowledge about any CD ROMs at all I tried kiwidebug=1 and than when I typed: /usr/sbin/hwinfo --cdrom nothing was shown - like there were no CD drives attached/found. the regular /usr/sbin/hwinfo shows lots of info - I am just nor sure how to copy the output from debug shell? Could any body give a pointer how to mount USB stick or something? Thanks *** Bug 386558 has been marked as a duplicate of this bug. *** if hwinfo can't find any device it looks like the required kernel
modules were not loaded. Steffen compared to 10.3 are you aware of
any changes in the CD/DVD kernel support ?
Andrew: what kind of CD/DVD is attached to this computer, internal, external
USB , etc... ?
Andrew: could you check if there are any block devices registered
ls -l /sys/block
thanks
No idea. 'hwinfo --storage' would be interesting; to see which modules are involved. I don't know enough Linux command line Voodoo in order to successfully try to get additional information, but after going through this original bug report, I made the following observation: Trying to boot the 11.0 Beta2 KDE CD from the master CD-burner on the secondary IDE channel of my nForce2 based Athlon-XP system fails as described in Bug 386558. However, if I put the CD into the slave drive on the same channel, booting-up from it succeeds w/o obvious further problems. Hope this helps to narrow things further down. I have now attached two DVD RW drivers both SATA (tried either one as well) there are two hard drives SATA as well - the board doesnt have PATA connectors ls -l /sys/block shows only USB FLASH DRIVE which I find strange - since kernel in kiwidebug fails to detect/use my USB keyboard (i had to connect PS/2 keyboard) hwinfo --storage displays some information since I do not know how to copy it onto PEN DRIVE - I had to take screenshots (sorry if they are not that clear...) Created attachment 212446 [details]
screenshot of hwinfo -- storage
Created attachment 212447 [details]
screenshot of ls -l /sys/block
Does loading pata_acpi ('modprobe pata_acpi') help?
In any case this looks like something for our kernel people.
I'm having the same problem on openSuse 11.0 beta2. 10.1-10.3 and various alphas/betas worked fine on a Samsung Q10 laptop. I'm using the std CD-Rom drive that comes with the laptop. A Laptop might not be the best test plattform but I'll attach the logs that I've got so far, let me know if you need anything else. Created attachment 212841 [details]
dmesg of 11.0beta2
Created attachment 212843 [details]
almost full output of hwinfo (beta2)
It looks like the module loaded ok but still no block devices were detected (unless I have to do something to force redetection?) Created attachment 212881 [details]
after loading modprobe pata_acpi
Steffen can this work if the other ata modules were loaded before ? I also think this is not a kiwi problem From the logs Daniel sent, I'd say it's a driver (ata_piix) problem. ok, I will assign this to the screening team in order to find the right people to have a look on this one. I'm pretty sure the kernel people will request additional information *** Bug 382807 has been marked as a duplicate of this bug. *** I have also had problem with this bug on beta2 KDE4 LiveCD. I have 1 PATA connected DVD-RW drive and 1 SATA (/dev/sr0) connected DVD-RW drive. If I try to run it with both drives connected (or just with SATA connected) it just stops with this bug (regardless of the drive in which CD is). If I try to run it with SATA drive physically disconnected and CD in PATA drive it runs without problems. After running into the bug (running with CD in SATA drive) I was able to mount it (so it seems that it really is not a driver problem) on console (Alt-F2) by using following command: mount /dev/sr0 /mnt/path -t iso9660 Hope this helps, let me know if you need me to try something else. Daniel, how is the cdrom connected to the laptop? Can you please post boot log from 10.3 w/ the cdrom attached? Andrew, ata_piix is detected fine but for some reason it failed to detect attached devices. Please do the followings. - switch to command console. - plug in a usb stick and mount it under /mnt. "mount /dev/sda1 /mnt" should do it. Depending on what filesystem the usb stick is formatted for, you might need to load ext3 or other fs module. - Execute "cp /var/log/boot.msg /mnt; dmesg > /mnt/dmesg.out; lspci -nn /mnt/lspci-out". - "cd /; umount /mnt" and post the files on the usb stick here. Jaromir, are you saying that the SATA cdrom was accessible from command shell? Can you also please do the above and post the logs? (In reply to comment #34 from Tejun Heo) > Daniel, how is the cdrom connected to the laptop? I'd like to know this one. I'm not sure if it is firewire, even though it says scsi. All I know is, the CD-ROM is located in that detachable thingy that holds additional connectors. This Laptop is a, I guess, so called sub-notebook. Afraid I don't know the answer to that one, but will attach dmesg and hwinfo of a working 10.3. Created attachment 215036 [details]
dmesg of 10.3
Created attachment 215039 [details]
almost full output of hwinfo of 10.3
Yeap, it's a firewire. <6>ieee1394: sbp2: Logged into SBP-2 device <6>ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048] <5>scsi 3:0:0:0: CD-ROM TOSHIBA DVD-ROM SD-R2102 1715 PQ: 0 ANSI: 0 <5>scsi 3:0:0:0: Attached scsi generic sg2 type 5 <4>sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray <6>Uniform CD-ROM driver Revision: 3.20 <7>sr 3:0:0:0: Attached scsi CD-ROM sr0 /me dunno anything about firewire. Asking for re-assignment. Maybe the kiwi initrd isn't containing modules for firewire? Greg, what modules would that be? that would be sbp2 see Steffen's response. If this is firewire, reassigning... in my case this has nothing to do with firewire all drives and dvds are connected to internal sata connectors perhaps this bug should be split into two afterall? i will attach now dmesg Created attachment 215321 [details]
hwinfo from 10.3
In my case too, I guess it's not firewire and I have the same problem.
I attach hwinfo from 10.3 for your record
Strange! Bottom line is: I was unable to mount USB stick The long story: 1) on previous load attempts the kiwi message was "Failed to detect CD drive!", this time the message was "cannot find CD image configuration file" 2) this time when booting i had USB flash stick connected - after kiwidebug - I noticed entries CDROM and CDROM1 in my /dev directory (I have two DVDs not attached) - I thought this were my CD ROMs so I I mounted /dev/cdrom to /mnt partition (even without specifying file system) and I was able to see three files LOCATED ON USB STICK! unfortunately the stick mounted as read only and I was unable to write to it 3) I disconnected the stick and connected another (or reconnected the original one) this time no /dev/cdrom entries - but as expexted /dev/sda however I has unable to mount it because it claimed it had wrong file system (both sticks are FAT and work fine under windows and linux) dmesg - showed proper recognition of device, but than it had info about mounting: FAT: invalid media value (0xb9) cannot find a valid FAT file system Created attachment 215339 [details]
usb flash stick incorrectly mounted read only from /dev/cdrom
Created attachment 215340 [details]
output of hwinfo --cdrom - after incorrect mounting of usb flash mem
Created attachment 215341 [details]
output of dmesg after inserting another usb stick and attempted mount
Tejun, one more thing: since I cannot copy the output you requested perhaps you can speculate what should I look for in those places? and I will try to look myself or I will try to take screenshots of some (highlighted) sections ? Tejun, I did try as requested. Indeed my SATA drive was accessible from command shell without any modprobe etc. commands, only simple mount was required and I saw contents of LiveCD disk. When I tried to run the commands you requested I had to use my iRiver T60 instead of USB stick (but works as mass storage). I had it connected and started all the time since boot up and was unable to connect to it (/dev/sda1 seems to be first partition of my SATA disk and other files in /dev didnt seem to be of usb stick relevancy .. only some called usb storage something (might have some - or similar characters in them) and they wouldnt mount). I had to repeat steps several times (countdown to 120s till reboot is quite short, it would be really useful if the countdown could be stopped somehow) and i think that on 4th reboot I tried to type df on console (I was going to try mount my disk partition and use it to store requested info), then maybe just mount command without arguments (not sure though) and it (very surprisingly) resumed loading liveCD (while it has on tty0 screen already written that "drive not ready" and maybe also "Couldn´t find CD image configuration file" (not sure if it managed to get to this point as I was on tty1 at that time)). So after successful start of KDE, I simply mounted usb stick and copied requested information, they will follow in next 3 messages (isn't there a way to insert them in only 1 post?). I also tried to repeat the steps involved (df and successful loading of KDE) but to no avail, so I am kinda puzzled what actually happened and if df had any relevance to what happened. I'll try what happens with beta3 once I download it today/tomorrow. If you need anything else, just say, I'd be glad to help. Created attachment 215791 [details]
boot.msg of 11.0beta2
Created attachment 215792 [details]
dmesg of 11.0beta2
Created attachment 215793 [details]
lspci -nn of 11.0b2
Live-CD Beta3 Gnome behaves still the same as described in #19 for the Beta2 KDE version. Successful boot only works from slave drive on (secondary) PATA channel, but not the master one. Same problem on my machine with beta3. If you need more feedback I'll post more logs. Marcus, please check what all those systems have in common. I assume everything is working with your own hardware. I dont have kiwi capable hardware *** This bug has been marked as a duplicate of bug 390934 *** I just wanted to give feedback, that with RC1, booting from my optical master drive on the secondary IDE channel now works as expected :-) |
Created attachment 209131 [details] 1 I´m not able to start live system from KDE4-LiveCD. If i enter Live-System from available boot options, I´ll obtain error: could not find kernel image: Live-System After aprox 10 seconds live system tries to boot automatically, but it is finished with: Drive not ready yet.....waiting -----> Couldn´t find CD image configuration file -----> rebootException: error consoles at Alt F3/F4 -----> rebootException: reboot in 120 sec memtest works fine from boot options. i attached snapshots just to be sure.