SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having a problem getting Suse to work. The installation goes fine, but I get the "Attention out of range message" before I can login into KDE environment. I was able to search the forum and find out how to solve that problem.
What's stopping me now is when I go into failsafe mode the system seems to be hanging or locking up at the "PCI: Probing PCI Hardware (BUS00)" and the line before that is just "PCI: Probing PCI Hardware". The login prompt doesn't come up and it's been at this line for over an hour now. Does anyone have an idea of what's wrong and how to solve it?
I really appreciate the help I've already found and any that might be offered.
You mean 'Failsafe' fails and normal boot works, but ends at a black screen?
Can you switch to text console with Ctrl+Alt+F1? In this case, login as root and type init 3, then sax2, configure graphics, save and exit, type init 5 and hope that it works now.
If Ctrl+Alt+F1 doesn't work, try the following: instead of failsafe boot, press (I think) F3 to get a grub command-line. Type '3' and continue normal booting. This should bring you into runlevel 3. Try again like above.
but i've been starring at a pitch black console for a few days,
only to discover that when simply hitting the Enter key once it jumped to Log in:
just a long shot but for me it was the screen setting.
You mean 'Failsafe' fails and normal boot works, but ends at a black screen?
Can you switch to text console with Ctrl+Alt+F1? In this case, login as root and type init 3, then sax2, configure graphics, save and exit, type init 5 and hope that it works now.
If Ctrl+Alt+F1 doesn't work, try the following: instead of failsafe boot, press (I think) F3 to get a grub command-line. Type '3' and continue normal booting. This should bring you into runlevel 3. Try again like above.
Thanks I had it backwards With your advise I was able to login and get to SaX2, but the screen goes to about half size and displays two garbled version of Linux start up. The mouse icon also becomes a fuzzy square. Is there a way to enter Sax2 into a pure text mode or am I doing something else wrong?
Thanks I had it backwards With your advise I was able to login and get to SaX2, but the screen goes to about half size and displays two garbled version of Linux start up. The mouse icon also becomes a fuzzy square. Is there a way to enter Sax2 into a pure text mode or am I doing something else wrong?
You could try sax2 in a vesa mode. ... ie either sax2 -m 0=vesa or sax2 -m 1=vesa. The 0 or 1 correspond to your graphic chipset. You can find out that by typing sax2 -p.
You could try sax2 in a vesa mode. ... ie either sax2 -m 0=vesa or sax2 -m 1=vesa. The 0 or 1 correspond to your graphic chipset. You can find out that by typing sax2 -p.
Thanks for the advice void_linux and Nabisco00 . I was able to find the "-m 1=vesa" command and it solved my video card problem. Been using SUSE 10 and happily windows free for close to a week now. This is a great community and I hope to be able to help other out the more I learn.
Last edited by rogue emissary; 02-03-2006 at 10:36 PM.
the "-m 1=vesa" command and it solved my video card problem.
C O N G R A T U L A T I O N S on finding the command arguments, and getting it to work. Apologies for the slow response. I've been sick for the past few weeks, and haven't been on this forum for a long time. Thanks for sharing your solution.
I don't want to dampen your enthusiasm here, but using the vesa driver will not give the full capability of the graphics card, e.g. 3D acceleration. But anyway, first goal is to get the system going.
Once you are more familiar with the system, you should try to get the NVIDIA drivers going.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.