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.
hey guys, I've been having this problem for a little while now and it's starting to piss me off. I have downloaded 10.3 9 times now and nothing is working. The closest I have gotten to it working is this. The installation welcome screen comes up, I tell it to install, I get the loading kernel dialog then the computer goes into stand-by/hibernate, then my only option from there is to shut it off. I am lost, I don't know what to do. I can seem to get a CD or DVD to work. Is there a way to get it to install from a network source or something? Cuz I can put my 10.3 iso on my roommates computer and run it off of that if I need to, but I don't know exactly how to do that. Or is there anything else I can do? I'm in dire need of help on this one and I don't like 10.2 and I don't have my 10.1 discs on me. Can anyone help me pls? Also, the md5 checksums all add up, so I know my copy of the iso is good.
Are you dead-set on Suse? I've never run it myself other than just fired up a free set I got in a give away years ago once: I'm a Slackware
person myself.
The reason I say this is that the problem you describe is almost certainly an ACPI problem of some sort. Your message isn't clear: does this
happen after the kernel is running and is spitting out various messages? If so, does it happen after the hard drive(s) get mounted or does it
die while the kernel is still running by itself in memory? If the former, you can use another computer to look at the logs, assuming you got far
enough that syslogd was brought up and had time to write to the disk.
One way around this is to turn off ACPI support at boot time. Some computers allow you to do it in the BIOS, while on others you must do it at boot time by passing "noacpi" (or something like that) to the kernel off the GRUB/LILO command line; there should be some instructions from Suse
on how to do this.
Are you dead-set on Suse? I've never run it myself other than just fired up a free set I got in a give away years ago once: I'm a Slackware
person myself.
The reason I say this is that the problem you describe is almost certainly an ACPI problem of some sort. Your message isn't clear: does this
happen after the kernel is running and is spitting out various messages? If so, does it happen after the hard drive(s) get mounted or does it
die while the kernel is still running by itself in memory? If the former, you can use another computer to look at the logs, assuming you got far
enough that syslogd was brought up and had time to write to the disk.
One way around this is to turn off ACPI support at boot time. Some computers allow you to do it in the BIOS, while on others you must do it at boot time by passing "noacpi" (or something like that) to the kernel off the GRUB/LILO command line; there should be some instructions from Suse
on how to do this.
Mike
I'm pretty set on SuSE. I've tried a few other Distros and Like SuSE the best. As for the kernel errors, it is still in memory when it happens. I get no logs, I don't even get to where I can tell it to do anything. It just gives me the welcome screen and that's it. I'll see what I can do about turning off the ACPI settings on it and see if it will install that way. I'll definately keep you guys updated. Thanks for the reply man.
What *might* be hapenning is that - particularly on a laptop some of the Wireless modules just cause the whole system to freeze on installation.
When you boot up press ESC as soon as possible (after you see the splash screen). This should bring you into CONSOLE mode where you can see what's happening.
You'll get to probably a message which says something like this
Loading modules xxxxx and then you get a hang.
To get round this supply in the boot options
brokenmodules=xxxxx where xxxx is the name of the module you can see on the console at the time of the system freeze.
I never understand why the system doesn't start up in Console mode by default - especially during install time as it's impossible to diagnose errors if you are stuck in the splash screen. After you've got a running (bootable) system you can change runlevel to 3 so you have to manually start X --but IMO this should be the default option until you've got a working system where you can (IMO not a good idea) change the runlevel again to 5 which starts X automatically.
Re-downloading the DVD again won't solve the problem -- in 99.99999% of the cases the DVD obtained from official mirrors will be OK.
If you want to try something easier without installing download the livecd -- you'll probably get the same freeze but apply the solution outlined above (brokenmodules=xxxxx).
This will save you from attempting to install a system which is incomaptable with your motherboard. If you can get the livecd to work then you'll be able to install the full system.
Alrighty so here's what I got. I finally got the program to work. I had a bad DVD iso burn. I reburned it and it went right in and worked just fine. I don't know what caused the bad burn, but it's really odd. Everything worked fine, even the ACPI settings worked fine. Now I just have to get my sound and display to work fine. (Sound is easy, but display is a PITA, especially since my card isn't supported at all. ) Thanks for the help guys! I'm already liking 10.3 much better.
Also, I can't configure my screensaver. Everytime I click on the setup for it, it goes back to the init3, then comes back to the login screen. Kinda weird, any thoughts?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.