I have an issue with normal boot (fail safe boot doesn’t have this problem). The boot process just stops and nothing happens, I just see the green background, the white lizard and no moving progress bar. I’ve given it about 40min without touching it, but nothing happened. If I press escape, the last log print says its mounting/mounted the hard drive. Not until I touch the head pad or press a key, it wakes up and the boot procedure continues.
I once had a similar problem on opensuse 11.1 which could require much tickling before booting up completely. This was never seen on 10.3, 11.0 and 11.2, but now its back in 11.3.
[booting normally up until here]
mount -o rw,acl,user_xattr -t ext4 /dev/disk/by-id/ata-TOSHIBAxxxxx-part1 /root
[gets stuck until tickled]
INIT: version 2.88 booting
[continuing as usual]
Copying static /dev content
[gets stuck until tickled, not once, but twice]
ok
[booting up entirely from here, no errors shown]
Device Boot Start End Blocks Id System
/dev/sda1 * 1 2612 20980858+ 83 Linux
/dev/sda2 2613 3134 4192965 82 Linux swap / Solaris
/dev/sda3 3135 14593 92044417+ 83 Linux
I’m experiencing similar events on openSuSE11.3-32 after updating from 11.2.
The boot sequence is too fast for the root partition, sda2, to be mounted. After about a 20 second pause the sequence stops and asked if I wish to continue. If I’m too fast responding ‘y’ the boot process stops and exits into a $ prompt. If the ‘y’ response is delayed a few seconds booting continues normally. Details given below from the log.
<7> 4.672350] PM: Resume from disk failed.
<6> 41.515303] EXT4-fs (sda2): mounted filesystem with ordered data mode
Boot logging started on /dev/char/…/tty1(/dev/console) at Sun Jul 18 23:15:38 2010
Trying manual resume from /dev/disk/by-id/ata-SAMSUNG_SP0842N_S0DWJ2FL907879-part1
Invoking userspace resume from /dev/disk/by-id/ata-SAMSUNG_SP0842N_S0DWJ2FL907879-part1
resume: libgcrypt version: 1.4.4
Trying manual resume from /dev/disk/by-id/ata-SAMSUNG_SP0842N_S0DWJ2FL907879-part1
Invoking in-kernel resume from /dev/disk/by-id/ata-SAMSUNG_SP0842N_S0DWJ2FL907879-part1
Waiting for device /dev/idev/disk/by-id/ata-SAMSUNG_SP0842N_S0DWJ2FL907879-part2 to appear: …Could not find /dev/idev/disk/by-id/ata-SAMSUNG_SP0842N_S0DWJ2FL907879-part2.
Want me to fall back to /dev/disk/by-id/ata-SAMSUNG_SP0842N_S0DWJ2FL907879-part2? (Y/n)
Waiting for device /dev/disk/by-id/ata-SAMSUNG_SP0842N_S0DWJ2FL907879-part2 to appear: ok
fsck from util-linux-ng 2.17.2
[/sbin/fsck.ext4 (1) – /] fsck.ext4 -a -C0 /dev/sda2
/dev/sda2: clean, 203322/1313280 files, 1385062/5242880 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/disk/by-id/ata-SAMSUNG_SP0842N_S0DWJ2FL907879-part2
mount -o rw,acl,user_xattr -t ext4 /dev/disk/by-id/ata-SAMSUNG_SP0842N_S0DWJ2FL907879-part2 /root
Is there a quick fix? Similar happened in 11.2 but the boot sequence did not demand a user response.
The computer must boot by itself, this is indeed too much. But an observation is that this doesn’t happen exactly every time, it occurs with a frequency of 3-4of5 times. I’ll hang around for a while to see if some update fixes it, meanwhile trying different partition setups.
If anyone has an idea what it can be and need logs for further investigation, don’t hesitate to ask.
I had the exact same problem on my HP Pavilion dv6736nr with 11.1 and 11.3. This time with 11.3 I though it might be related with the nvidia graphics card so I switched off the KMS using the ‘nomodeset’ kernel boot option. Unfortunately, it had no effect and my laptop was still getting stuck on boot. After playing around with different options I realized that it boots ok if I set ‘nosmp’ or ‘maxcpus=0’ kernel boot options. This, however, was not acceptable since I would end up running with only one CPU core.
At this point I was very frustrated since I was not able to find any solution on the web. I was even considering to install the latest kernel snapshot from the
Kernel:HEAD/openSUSE_11.3 repository which is something I was not looking forward to. Then I realized that there are multiple ‘flavors’ of the 2.6.34 kernel available in the oss repository and the one that that was installed by default was ‘kernel-desktop’. Once I installed ‘kernel-default’ and removed ‘kernel-desktop’ everything worked like a charm.
Now, this is exactly the type of stuff that makes me sad. With every new version of openSUSE it feels like 5 step forward and 2 steps back. There is always something very important not working properly which than overshadows all other great improvements. If something like this happened to somebody who was considering to switch to openSUSE (or Linux in general), that person would immediately conclude that openSUSE (or Linux) is a piece of c***.
I’m not a kernel expert and I don’t know what is the exact difference between the ‘kernel-desktop’ and ‘kernel-default’ but ‘kernel-desktop’ was clearly a wrong default in my case. Maybe this problem only affects computers with a specific hardware and I’m unlucky enough to have such hardware. I don’t know. Anyways, I hope this fix will also work for other people with the same problem.
That also solves the problem for me as well, so far everything seems fine with the default kernel. Tried power on-off and reboot several times, no problems at all. Thanks a lot!
I too have a HP pavillion, guess there might be something with this particular hardware and the desktop-kernel then? Also, it seemed to be appear more frequently during reboots in comparision to turning the power off and then and booting up a fresh start.
Fully agree with you on the quality aspects. Additionally, I can imagine that in the long run its also becomes a turnoff for experienced users as well, always experience weird type of problems with a new distribution, most likely because of too much new functionality, too little or too narrow testing and stabilization.
Same problem here with HP dv6815nr laptop. Using kernel-default fixes the problem here too. I started a bug thread before I saw this thread if anyone wants to add to it. https://bugzilla.novell.com/show_bug.cgi?id=581566
I am also running 64 bit and had this same problem on a Compaq laptop. Installing the default kernel and removing the desktop one fixed the problem.
It is very unfortunate that this should occur right off the bat. With each new release, something always seems to be broken. A novice user would have had a hard time figuring this out.
This bug has been assigned, so hopefully a patch will be pushed out soon. It’s hard for me to complain about something I got for free. I discovered this bug in milestone 6, but had to travel, and didn’t get to help the devs solve the problem.
I have the same issue. In my case, I cannot boot the default option. I can only boot the desktop option.
I see the following.
Waiting for device /dev/sda1 to appear: 1.846612] …Could not find /dev/sda1.
Want me to fall back to /dev/disk/by-id/ata-WDC_WD3200AAJS-56B4A0_WD-WCAT1A665301-part1? (Y/n)
64-bit system, upgraded from OpenSUSE 11.1 to 11.3.
On 07/30/2010 12:06 PM, nwe2023 wrote:
>
> I have the same issue. In my case, I cannot boot the -default- option. I
> can only boot the -desktop- option.
>
> I see the following.
>
> Waiting for device /dev/sda1 to appear: 1.846612] …Could not
> find /dev/sda1.
> Want me to fall back to
> /dev/disk/by-id/ata-WDC_WD3200AAJS-56B4A0_WD-WCAT1A665301-part1? (Y/n)
>
> 64-bit system, upgraded from OpenSUSE 11.1 to 11.3.
As that upgrade path is not supported, it may not be possible to fix; however,
it looks like an error in /boot/grub/menu.lst.
In that file, find the stanzas that describe the “desktop” and “default”
options. There must be some difference between the “root=” phrase. Edit the
“default” section to match the other.
You will have to be root to examine or edit this file, but you can use YaST =>
System => Boot Loader. In the main screen, find the pull-down that says “Other”
and select “Edit Configuration Files”. Pull down the “Filename” box to select
/boot/grub/menu.lst.
