The “maxcpus=1” would directly affect the boot from DVD for installing. That option is possibly also added to the grub menu for future booting. But you can edit that later.
Note that I had a similar problem (stops at udev) on booting the DVD. I think it was the 64 bit DVD, but I’m not sure on that… It worked on the third try. I am not having that problem with the installed system. I suspect that the problem is only with the particular setup used on the DVD.
I do believe that the key point here is “Brand New”. The statement that … Slackware boots and installs … is that your experience or someone else’s?? It was noticed in the Slackware Report that was submitted that not all items are working. Could be that SuSE is not as lenient on the missing drivers as Slackware. I really don’t see the maxcpus doing anything -unless you are using an SMP kernel. By the way, are you using a LiveCD or was the openSuSE installed on the Laptop??
What you just said makes absolutely no sense. It’s not a report. Yes, Slackware64 13.37 installs and works almost entirely. Yes, that was written by me. As for “missing drivers”, what the heck are you talking about? USB 3.0 xhci_hcd gets loaded, just that kernel 188.8.131.52 may be why. Yes, “brand new” laptop may have something to do with it. I am using the OpenSuSE installer DVD, not a live CD. The USB 3.0 is more tied (i believe) to age of kernel and being brand new, but I’m not worried about USB 3.0 working here. This isn’t just “USB 3.0 don’t work but USB 2.0 port works” like with Slackware: this is “Installer DVD will not even get past boot so that I can install it.”
My point is not to compare Slackware to OpenSuSE but to point out that a different linux distribution works on this laptop, hence it’s no the laptop. And much less I could say here “well Slackware configures udev properly, why can’t you?” but I’m not using that logic so much as pointing out that now is the wrong time to try and use that logic as you did in your post. While I appreciate your attempt to help, please refrain from replying again. I’ll try the other guy’s maxcpus thing and get back with you.
(By the way 11.4 opensuse is installed on my netbook and so far works fine, but that’s the fun of asus eee pc )
I got stuck at udev whilst installing RC2. However, I did not have a USB
thumb inserted. May have been the timing problem but I didn’t wait 10
minutes to find out. I merely hit reset and install went through OK -
apart from the usual mid-install freeze at 1st reboot.
Graham Davis, Bracknell, Berks.
openSUSE 11.4 (64-bit); KDE 4.7.3; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nVidia driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
Harshness was not intended nor expected in return. I apologize for any offense taken -but- that I did not really send. That is the problem with textual conversations -especially if the two parties are not familiar with each other. I was perhaps to short in mine -but- nothing was meant to cause any hard feelings… nor to insinuate anything bad about you. It was a report, to me … made by you as it turns out … but it was a report. A war was not meant to be started just asking questions to get more verification on the problem. I still do not see how the number of CPUs fixes the problem -but- that is something to learn. Thanks for asking and thanks to interele for the info about the maxcpus. I’ll keep that one in mind.
My HP Compac nc6400 failed to install 12.2 and now fails to install 12.3 at udev. I have it set to single core, and all attachable devices turned off and nothing plugged into the computer.
It works well with 12.1 (when I re-enable things in the BIOS).
12.2 final will the installation procedure, but has another problem later. It does give me a quick flash of an error message just before it goes to graphics mode. Those error messages need to be visible until they can be read, even after switching out of text mode. Otherwise they get missed (who watches the screen constantly?)
12.3 stays at Starting udev until the system powers down due to over temperature CPU.
If the problem was know for 12.2 RC1, how did it get to 12.3 final?
12.3 works fine with my desktop system (with an AMD 3 core).