[Bug 858319] New: OpenSuse13.1 Installation, Rescue System, Check Media do not boot on Toshiba Qosmio X70, get to Starting udev.
https://bugzilla.novell.com/show_bug.cgi?id=858319 https://bugzilla.novell.com/show_bug.cgi?id=858319#c0 Summary: OpenSuse13.1 Installation, Rescue System, Check Media do not boot on Toshiba Qosmio X70, get to Starting udev. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers@suse.de ReportedBy: woa46@yahoo.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 I have a Toshiba Qosmio X70 and the OpenSuse 13.1 Installation disk will not boot either the Installation, the Rescue System, or the Check Installation Media options. It gets to the point where it prints out "Starting udev" and then the screen blanks and nothing happens. I was able to install OpenSuse 12.3 on the system. I had some problems with the EFI boot and the Intel Dual Band WI-FI AC 7260. I was able to go to www.kernel.org and get the source for the 3.12.6-1.1-desktop kernel, build it, install the iwlwifi firmware and get my wifi working. I don't know whether the EFI boot or the wi-fi driver caused the problem, but it appears that this is something that should be corrected in the next release. The OpenSuse 13.1 system installed correctly on my Toshiba Qosmio X505-Q898. My question is this: is there some way I can run the 13.1 Installation program from my working kernel? I would still like to install 13.1 on the X70 since it has some features I like. Thank you for any help in this matter. Reproducible: Always Steps to Reproduce: 1. Install OpenSuse13.1 boot DVD-ROM on Toshiba Qosmio X70. 2. Boot it. 3. Select "Installation", "Rescue System", or "Check Installation Media". 4. Hit Enter or Return. Actual Results: Gets to Starting udev, blanks the screen, and then does nothing. Expected Results: System should continue on, install the devices and continue on into the installation program. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858319 https://bugzilla.novell.com/show_bug.cgi?id=858319#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858319 https://bugzilla.novell.com/show_bug.cgi?id=858319#c2 David Webb <djw@soton.ac.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |djw@soton.ac.uk --- Comment #2 from David Webb <djw@soton.ac.uk> 2014-02-20 17:44:24 UTC --- I seem to have a similar bug - but there may be more than one. Comments below relate to my attempts to use the Install option. The other DVD options which involve booting a version of Linux appear to behave in the same way. Note this may be related to the full 13.1 freeze bug. That seems to freeze in a similar way. openSUSE 13.1 DVD. System freezes at start of installation. =========================================================== Mainboard: ASUS A8N-SLI CPU: AMD Athlon 62 X2 Dual Core processor 3800+ Keyboard: PS2 USB: mouse, printer, scanner IDE Bus: Main system disk + DVD read/write SATA Bus: Two disks - one data, one spare/other OS Graphics: GeForce 6600 I tried to install openSUSE 13.1 from the DVD. There were 'problems' in reaching the first install screen, but eventually I succeeded by removing all USB devices and the two SATA disks. I could then install 13.1 by using just the keyboard. 13.1 has similar problems (another bug report) but it gets to the login screen and the linux tty shells with both the PS2 mouse and the SATA disks installed. The bug or bugs may be related to the 13.1 freeze bug reported elsewhere. Test runs --------- 1. IDE Disks only, no USB devices: Fail at "Starting udev ..." 2. Add: Kernel: Safe Settings Success: Yast Welcome page I could continue using only the keyboard. 3. Add USB mouse: Starting usb... ok Then the green bands (of wasted time) carry on in their infinite way but DVD disk reads soon stop. ALT-F3: fcoe_check: 0 insmod /modules/af_packet.ko ALT-F4: ... Startup... (sometimes more insmod lines) 3a. Add USB mouse - occasional behaviour Seems to reach green line success point, with DVD reads, then nothing or message >usb 2: usb (I find it difficult to reproduce this error) ALT-F3:... unknown keysym 'compose' <stdin>:691: syntax error syntax error in map file key bindings not changed starting setctsid 'showconsole' inst_setup yast ALT-F4: ... Startup... [53.6....] usb-2-3: new low-speed USB device number 2 using ohci-pci [53.7....] firewire_core 0000:05:0b.0: created device fw0: GUID 0011d800007686ae, S400 4. Remove USB mouse, add SATA disk Starting usb... ok Then green bands but again only DVD reads for a short time. ALT-F3:..... more insmod lines insmod /modules/powernow-k8.ko ALT-F4: ... Startup Previous versions of openSUSE ============================= I tried the openSUSE 12.1, 12.2 and 12.3 DVDs. 12.1 installed without problem. 12.2 and 12.3 seemed to give similar errors to those above but I have not checked in the same detail. Further Comments ================ I found out about the ALT-F3 and ALT-F4 options only by accident. I have not seen any help in debugging the install sequence on any of the openSUSE pages. I would welcome comments about raising this as an additional bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858319 https://bugzilla.novell.com/show_bug.cgi?id=858319#c3 --- Comment #3 from David Webb <djw@soton.ac.uk> 2014-02-20 17:47:06 UTC --- Comment above about PS2 mouse should efer to my USB mouse. I tried an old PS2 mouse but could not get it to work - the mouse may be faulty. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858319 https://bugzilla.novell.com/show_bug.cgi?id=858319#c4 --- Comment #4 from David Webb <djw@soton.ac.uk> 2014-03-03 10:18:56 UTC --- Solution? ========= I found in my case adding the kernel parameters: nomodeset acpi_osi="Linux" solved the problem. Using "noacpi" instead of "acpi_osi..." also works. Neither was sufficient by itself. The effect should be the same as the two startup options "No KMS" under F3 (Video mode) and "No ACPI" under the F5 (Kernel) key. (I would have thought that "Safe Settings" should also include "No ACPI"). However these options (or nomodeset plus either "No ACPI" or Safe Settings" under F5) lead to a freeze at message "Loading basic drivers... OK". Background After trying different possibilities and using google I came across the following article which discusses these two options: http://ubuntuforums.org/showthread.php?t=1613132 "nomodeset" I am used to because I have a NVIDIA GeForce 6600 graphics card which does not live comfortably with the nouveau driver. In the past I've also come across acpi (Advanced Configuration and Power Interface). The article explains that by default Linux pretends to the bios that it is one or more versions of windows and "Unfortunately, some bioses contain fixes to fix problems with specific windows versions (notably vista) that arent needed or dont work for other OS's." The author argues that using "noacpi" may be too harsh and generate its own problems. Instead he recommends using acpi_osi="Linux" on the command line or " acpi_osi=\"Linux\" " inside scripts such as the one used when making the grub2 menus. I realize that the above may not solve Walter Augenstein's problem but for the record my startup screen gives the BIOS as: Phoenix AwardBIOS v6.00PG ASUS A8N-SLI Premium ACPI BIOS 1303 Also why the combination of the graphics card, the bios acpi system and either a sata disk or a usb mouse caused problems - whereas removing the last two didn't is beyond me. However, especially given that SuSE 13.1 will eventually feed into one of the SuSE SLED products: Suggestions: 1) It looks as if there is a bug in adding the "No KMS", "No ACPI" and "Safe Settings" to the kernel command. 2) I would like to see a more detailed discussion of potential startup problems with solutions and pointers to additional openSuSE help documents, either in the release notes or in a closely associated document. 3) A movement back to a more tolerant (knoppix like?) kernel for the installation phase. 4) At the kernel level, isn't it time for an intelligence option, which if compiled into a kernel will add code that knows about and can allow for bios quirks. On the last point, even allowing for linux phones etc., - there must be fewer bios manufacturers than printer manufacturers - and the printing system can deal with most of the special printer quirks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858319 https://bugzilla.novell.com/show_bug.cgi?id=858319#c5 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai@suse.com Resolution| |FIXED --- Comment #5 from Takashi Iwai <tiwai@suse.com> 2014-03-17 10:34:38 UTC --- Unfortunately, it's almost impossible to cover all BIOS bugs. BIOS writers also do something wrong, and there are even more different BIOSen than printers. (It's not only about vendor, but each particular BIOS *version* or *revision* triggers bugs.) Sorry for that, but it's a reality... In anyway, it'd good that you found a workaround. Maybe it'd be good to have a boot option to add acpi_osi=Linux, too. OTOH, we don't want to have too many boot options, which is also confusing. If you really want to add acpi_osi boot option, feel free to request it in openFATE. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com