My setup : HP Pavilion DV6 laptop, openSUSE Tumbleweed.
After I do a complete shutdown, the computer wouldn’t even POST to the boot screen, it’d just light up and give me a blank screen(Absolutely blank, not even the usual backlight). What I do is remove the power cable and battery, put them back and then do a start and then it boots. If I do a forced shutdown, it’ll come back up fine. Any ideas?
A bad move! IMO one should be familiar with any problems re one’s hardware support on standard 11.4, before doing Tumbleweed. You should consider going back to standard 11.4 and doing just that.
On 09/02/2011 09:56 PM, consused wrote:
>
> consider going back to standard 11.4 and doing just that.
+1…imo there ought to be a big, bold, flashing, red lettered, notice
that must be read (and ‘accepted’ with a button saying "I have been
warned)…notice reads something like:
Tumbleweed (at this stage of its development) is not a good fit for
folks with little or no experience with Linux, or openSUSE.
If you can’t troubleshoot routine problems, fix your system, and post
rational bug reports, please stick to openSUSE.
It’s not like I have absolutely no clue when it comes to Linux and I had been using Tumbleweed without much problems for a while, but this one stumped me as I tried everything I could find. Regardless, I’ve downgraded to 11.4 and will let know if I encounter this problem.
If this is not when using a kernel version < 3.0 then it is due to the wonderful new reboot quirks (acpi?) kernel developers copied from Microsoft. If these quirks broke your system it is worth a famous new bug report on kernel.org. But try an older kernel before reporting!
Your linux experience will be useful again, when you revisit Tumbleweed :). If you have enough disk space, you could do that on another partition and multiboot for testing. That’s what I have done with Tumbleweed from the start, but have been fortunate with my hardware and no real puzzles. Testing everything with 11.4 will give you a good base for further adventure and investigation. It may well turn out to be a combination of your hardware and kernel version 3.0.x…