I still can’t use my system though, because systemd fails to boot up and booting with system v leaves me without any working X and also without an integrated Intel NIC. Lucky I still have an old PS/2 keyboard so I can at least try to do smth here, because USB devices don’t work with either one.
When I try booting with systemd, I get these messages:
Doing fast boot
FATAL: Module ata_piix not found.
FATAL: Error running install command for ata_piix
FATAL: Module ata_generic not found.
FATAL: Module aic79xx not found.
FATAL: Module mptsas not found.
FATAL: Module sata_sil24 not found.
FATAL: Module pata_it821x not found.
FATAL: Module piix not found.
FATAL: Module it821x not found.
FATAL: Module ide_pci_generic not found.
FATAL: Module processor not found.
FATAL: Module fan not found.
Creating device nodes with udev
udevd[184]: failed to execure: `/etc/sysconfig/network/scripts/ifup-sysctl` `/etc/sysconfig/network/scripts/ifup-sysctl lo -o hotplug`: No such file or directory
Trying manual resume from /dev/disk/by-id/ata-ST3250824NS_5ND0TQEP-part2
Invoking userspace resume from /dev/disk/by-id/ata-ST3250824NS_5ND0TQEP-part2
Resume: libgcrypt version: 1.5.0
Trying manual resume from /dev/disk/by-id/ata-ST3250824NS_5ND0TQEP-part2
Invoking userspace resume from /dev/disk/by-id/ata-ST3250824NS_5ND0TQEP-part2
Waiting for device /dev/sda3 to appear: ok
fsck from util-linux 2.20.1
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a -C0 /dev/sda3
/dev/sda3: clean, 750284/14548992 files, 54206945/58163970 blocks
fsck succeeded. Mounting root device read-write
Mounting root /dev/sda3
mount -o rw,acl,user_xattr -t ext4 /dev/sda3 /root
5.949557] systemd[1]: [/etc/init.d/cups:19] Failed to add LSB Provides name cupsd.service, ignoring: File exists
6.076781] systemd[1]: Failed to open /dev/autofs: No such file or directory
6.076805] systemd[1]: Failed to initialize automounter: No such file or directory
Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode.
Give root password for login:
Any ideas what’s going on here? Why can’t the kernel modules be loaded?
atroxix, if this was me AND I had a separate /home partition, is to do a clean installation. Basically, select custom partitioning, not based on anything AND mount your same root / and elect to format, mount your /home but don’t format, keep your old SWAP and elect to mount but not format any other existing partitions and supply where they should be mounted, like /windows/c for Windows if you had such a partition. If you use a nVIDIA or AMD video chipset, you may need to select (F5) VESA mode and add in the kernel load option nomodeset later, to be placed in your grub menu.lst file. openSUSE 12.1 uses systemd for system file startup and is a big change over how openSUSE 11.4 worked, causing some upgrade issues. Once the install is complete, just reinstall any other missing applications and all of your old settings in /home will be reused, even including your desktop background.
Well, I’ve installed and configured my system quite a bit during the years and I’d very strongly prefer fixing the now-broken system to finding out all the customizations etc. And unfortunately I don’t have separate /home partition.
I’ve now tried updating the system again from the DVD (and during that, including also online repositories), setting all the packages to be updated unconditionally. When different kernels (default, pae, desktop) were installed, all the installations gave errors that the above-mentioned kernel modules were not found. What does it mean? It does not seem like it’s related to systemd anymore. Or is it still?
Not having the kernel load option nomodeset is most common problem but you could try adding in the options in one at a time from this list: apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off processor.max_cstate=1 and try to find the one that is helping you startup. The fewer the better as each one can have a penalty of some sort.
Specify maximum number of processors that a SMP (Symmetric multi processing) kernel should make use of. For example if you have four cpus and would like to use 2 CPU then pass 2 as a number to maxcpus (useful to test different software performances and configurations). [FONT=Verdana][size=2] Using “maxcpus=0” will disable SMP entirely[/size][/FONT].
Now consider that there can be an interaction with these parameters and it might be best to try them one at a time and see what you might get.
On 11/26/2011 03:16 PM, atroxix wrote:
>
> I tried to increase the “maxcpus” number. The system is booting OK with
> “maxcpus=1”, but not with “maxcpus=2”. My CPU:
>
>
> Code:
> --------------------
>
> # cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 15
> model : 2
> model name : Intel(R) Pentium(R) 4 CPU 2.60GHz
> stepping : 9
> cpu MHz : 2593.312
> cache size : 512 KB
> physical id : 0
> siblings : 1
> core id : 0
> cpu cores : 1
> apicid : 0
> initial apicid : 0
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 2
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe up pebs bts cid xtpr
> bogomips : 5186.62
> clflush size : 64
> cache_alignment : 128
> address sizes : 36 bits physical, 32 bits virtual
> power management:
>
> --------------------
>
>
> So “maxcpus=1” should be good enough for me, shouldn’t it?
Yes. If your P4 is one with hyperthreading, maxcpus=1 will disable it. For most
Linux cases, that extra pseudo-processor is not worth much, and disabling it is
the correct thing to do.
maxcpus=0 will disable SMP (as written above). I doubt Pentium4 is a SMP processor…
I think atroxix has a wrotten initrd as stated in output of first message: essential modules not found
