(Correction: Title should read "Must hit enter 8-10 times to boot…)
My computer loads the BIOS, goes to grub, and then displays the graphical boot progress bar. (This is the progress bar prior to KDE displaying it’s progress bar)
Eventually, I have to hit “esc” and repeatedly hit “enter” in order to make the boot continue…otherwise it will just sit and do nothing, no matter how long I wait.
I dont even know where to start in diagnosing the source of this…what kind of information do, those of you who are smarter than me, need in order to help find the cause of this issue…and hopefully, a resolution.
I’m not sure its related to rpm distros per se but it happens to show on them.
I’m inclined to think it maybe a question of kernel modules or patching that is done. Might be worth taking it to the bugzilla.
Only thing I can think off, is to see if lsmod is blatantly showing something different or the kernel config.
Perhaps have a little look and compare,
zcat /proc/config.gz on both and run a diff.
But if it is kernel and you have confirmed it isn’t just something like a gremlin install, bad install media etc… I’m out of my depth hopefully one of the kernel hackers may have an idea.
AFAIC ata2: SATA link down (SStatus 0 SControl 300) means the drive is down, as for why it comes back up by hitting return lost me sorry.
Really sorry I haven’t got anything to add. If I’m honest I’m not really sure whether old IDE’s come up as sata, but you seem to be using an ata module. So I no longer even understand whether this is a sata drive or not.
Would be intrigued to know if it is the same in a working linux distro.
smccuan wrote:
> Andy Sipowicz;1973696 Wrote:
>> did this condition just start happening one day, after having run
>> smoothly prior? that is, is this the way this machine has booted ever
>> since the first install of openSUSE???
>
> It’s done this since the first install.
did you check the md5sum before burning the disk, and then then media
check prior to install?
did the install go ok?? anything strange happen?
>> does a Linux Live CD boot up normally/quickly?
> Debian based distro’s work fine, rpm based distro’s exhibit the same
> behavior.
how about a live SUSE disk?
>> have you in anyway customized the BIOS settings?
> No.
>> try booting with acpi off
>
> I haven’t tried this yet, however, I’d like to keep ACPI on if at all
> possible. But, I’ll test it out.
when i first saw your Q i entered
“ata2: SATA link down (SStatus 0 SControl 300)” [with quotes] into a
google search…and, found too much for ME to read to help YOU…but
what i did read (if i remember correctly now) was that someone solved
their similar problem by turning off power savings stuff in their BIOS…
since it is YOUR problem, perhaps you have the patience to wade
through all the nouns and verbs pointed to by that google search…
Could you compare kernels from a working distro and a non-working one.
I’m sure it’s related to kernel just not sure how. Why I would look at kernel config and lsmod comparisons.
It may be as simple as removing a module and replacing it,or upgrading/downgrading a kernel. but at the moment it is impossible to tell what or even if that is the difference. Last time I looked Ubuntu’s kernel was older than Suse’s.
It really does shout kernel it seems to be happening quite early on in the boot sequence, and all distro’s do there little things to the kernel.
Did this issue ever get solved? I have the exact same thing happening, and I’ve experienced this before as well (I think I ended up wiping the HD the previous installation was on).
I Always check the CD prior to install. Nothing strange.