I installed openSUSE 11.1 in an extended partition.
All I had to install after the installation was the nVidia drivers, the rest is all working nice and shinny.
Still, the issues are the following:
First, when I pick openSUSE in grub, the loading screen shows but it won’t work, it gets stuck there and the only way to make it progress is to push ESC and ENTER, ENTER, ENTER or any other key. I am not sure why this is happening, I tried disabling the wireless at startup, touchpad, everything, but nothing. I’ve also looked for people having this same problem but I found nothing.
Second, when I make openSUSE to load, a huge nVidia logo is displayed (Kinda sexy huh?) and after that, I am asked to log in as root, I do it, and 2 seconds after I log in, the screen goes black! I thought and I said: “Maybe it changed the screen to screen 2”, so I pushed [FN] + F4 and voila! Video is back… I tried the nVidia settings but nothing, I couldn’t find anything to solve this. I even tried to look into the xorg file, to see if there is some errors, but nope.
Apart of these issues, openSUSE is running perfect, but you know… these are annoying so… if I hear solutions, I’d be more than glad and motivated to start using this wonderful distro.
Please, help? Any question about my system or anything, are welcome. I’d be tracking down this thread.
And yes, you are right, I should not be logging in as root, but aparantly I am not because if the system keeps asking me permssion to do certain things or if I have to use sudo everytime I use the console…
anyway, I’ll try what you said and be back here with the test results.
I tryed booting failsafe mode, and everything worked perfectly, I didn’t have to push any key to make suse load, and the right screen was selected. But… the video driver didn’t seem to be installed. No compiz, no big reso.
I feel like we’re in the same situation here, no progress.
Hey, you were right about the boot command: apci=off. this indeed solve my loading problem at startup but I wanna know why? why setting acpi to ‘off’ will let suse load good?
But this is just the start… cause yaeh, it loaded super fast, then when I got to the desktop I had to face with my second problem, I log in and then this silly nVidia changes the Screen X to the next one, BUUUT, for some reason, even if I try pushing [FN] + F4 to enable the screen again, it won’t work… Maybe setting acpi=off affected the shortcut fn keys?
The reason will be that the BIOS ACPI code has something in it that the ACPI interpreter in the kernel can’t parse, perhaps an MS extension created by their tool chain, that only Windows knows about because it’s not in the ACPI standard (or something has been interpreted differently, as the standard is not 100% unambiguous). Things are not getting set up in a way the kernel can use them.
There may be a BIOS update which solves the problem. In past some ppl have gone to such lengths as disassemble the ACPI code in BIOS, hack it, then re-flash. Not something for the faint hearted!
Thanks for your explaination, but the fact [fn] shortcuts keys are not working is an effect by setting acpi=off?
I think there’s something wrong in the xorg.conf file, that’s why my screen becomes black right after I log in, like the video adapter changes to video output to the Screen 2. So to fix this, I just use the {fn} + f4, which swap the video output between the external video output and the laptop’s screen. but this time, when I set acpi=off, {fn} + f4 did not work. :o
I installed the nVidia drivers with the 1-click install… perhaps If i try again…?
As a note my wife’s dv6000 also have this same
press-enter-a-dozen-times-to-boot issue, and often to shutdown. Seems
to happen first regularly (if not consistently) when loading USB
components. I’ll have her try the acpi=off bit.
Good luck.
mirux wrote:
> Hello robopensuse,
>
> Thanks for your explaination, but the fact [fn] shortcuts keys are not
> working is an effect by setting acpi=off?
>
> I think there’s something wrong in the xorg.conf file, that’s why my
> screen becomes black right after I log in, like the video adapter
> changes to video output to the Screen 2. So to fix this, I just use the
> {fn} + f4, which swap the video output between the external video output
> and the laptop’s screen. but this time, when I set acpi=off, {fn} + f4
> did not work. :o
>
> I installed the nVidia drivers with the 1-click install… perhaps If i
> try again…?
>
> Thanks for your reply.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
I finally fixed my second issue, with the blackout after the signingn in.
It was compiz, I disabled compiz on startup, and rebooted to see if the blackout happens! but no, everything perfect so now I am gonna find out what is causing the balckout then I post back with the final solution to this.
And yeah, acpi=off seems to be the solution, I’ll do some more research on what features I may lose if I disable acpi tho.
Verified… acpi=off fixed my boot. Looking at my boot line for
Failsafe (which I never tried, btw) I have apm=off. Would that be
better perhaps? Anyway, whatever. Also she is not running compiz so I
don’t know how that will affect things should she implement it at some
point.
Good luck.
mirux wrote:
> BINGO!
>
> I finally fixed my second issue, with the blackout after the signingn
> in.
>
> It was compiz, I disabled compiz on startup, and rebooted to see if the
> blackout happens! but no, everything perfect so now I am gonna find out
> what is causing the balckout then I post back with the final solution to
> this.
>
> And yeah, acpi=off seems to be the solution, I’ll do some more research
> on what features I may lose if I disable acpi tho.
>
> Regards.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
I don’t know if I am retarded, which I doubt but… I tried fixing my boot, adding the acpi=off to the boot menu option, so It will solve my problem, and then grub never started again… just black screen, cursor blinking.
I even had to reinstal Windows Vista because my win partition was erased.
I don’t know what I did wrong, I just went to:
yast -> system -> boot loader and did the obvious thing, add the thing to the optinoal parameter of the current menu item.
Your Vista Partition was not erased. In fact everything was there just as it should be - except: You just installed grub incorrectly. Many have fallen prey of this strange behavior.
Well, I am definitely not happy right now, I reinstalled vista and during the installation I had to decide… If I drop linux or not by erasing the ext3 partitions…
I finally decided I will give it a chance, it was not my fault i didn’t know the boot loader was buggy… I’ll maybe try some other distro (Fedora 10 maybe), and this time, won’t use grub, only the win grub version. Since I can’t migrate from windows for now… I want it to manage the startup.
But hey, thanks for the replies! It really helped! Who knows… maybe I won’t even like fedora and then i come back to suse.
Maybe setting acpi=off affected the shortcut fn keys?