installed 12.2 with Grub as 12.3 can not use my raid0 array.
installed all updates 12.2
installed kde4 10.2
installed latest kernel 3.5.8.x
installed nvidia driver 319.12
installed printing
installed libre office latest
installed vlc from download.videolan.org/pub/pub/pub/videolan/vlc/SuSe/12.2
then changed every entry in Yast configured Software Repositories from 12.2 to 12.3
then you have a form of control that the changed repositories exists
Then the update to 12.3
in Yast Software Manager view - repositories @System that is all what is installed
do a update All in the list / update if newer version available
this took 1/3 of the time to download the 12.3 iso
Then the moment of truth
REBOOT
12.3 is up and running
2 problems for changing runlevels in yast that depends on boot.localfs and boot.rootfsck which are not in init.d
I found them on internet with google search
make them with editor cut and paste from internet page
put them in /etc/init.d reboot
now you can change runlevels
that are the problems i found.
Exept the black outlook from Plymouth every thing is running the same way as 12.2
12.3 is a fraction slower in changing from boot to starting kde4
in 12.2 kde4 was started as boot was not finished so to speak
in 12.3 the boot proces has to be ended to start kde4 that is the delay i think
So in my view of things 12.3 is a minor upgrade to 12.2
from sysinfo:/
OS Information
OS: Linux 3.8.8-1-desktop x86_64
Current user: @@@@@@@@linux-ssd.site
System: openSUSE 12.3 (x86_64)
KDE: 4.10.2 "release 556"
Display Info
Vendor: nVidia Corporation
Model: GT520
2D driver: nvidia
3D driver: NVIDIA 319.12
CPU Information
Processor (CPU): AMD FX(tm)-8120 Eight-Core Processor
Speed: 3,600.00 MHz
Cores: 8
Memory Information
Total memory (RAM): 15.5 GiB
Free memory: 12.4 GiB (+ 1.4 GiB Caches)
Free swap: 2.0 GiB
On 2013-04-19 21:16, susegebr wrote:
>
> installed 12.2 with Grub as 12.3 can not use my raid0 array.
> installed all updates 12.2
> installed kde4 10.2
> installed latest kernel 3.5.8.x
> installed nvidia driver 319.12
> installed printing
> installed libre office latest
> installed vlc from
> download.videolan.org/pub/pub/pub/videolan/vlc/SuSe/12.2
>
>
> then changed every entry in Yast configured Software Repositories
> from 12.2 to 12.3
> then you have a form of control that the changed repositories exists
>
> Then the update to 12.3
> in Yast Software Manager view - repositories @System that is all
> what is installed
> do a update All in the list / update if newer version available
> this took 1/3 of the time to download the 12.3 iso
>
> Then the moment of truth
> REBOOT
> 12.3 is up and running
Advice to any reader: don’t do any of this.
> 2 problems for changing runlevels in yast that depends on
> boot.localfs and boot.rootfsck which are not in init.d
> I found them on internet with google search
> make them with editor cut and paste from internet page
> put them in /etc/init.d reboot
> now you can change runlevels
Oh my!
12.3 does not have those files, and that is intentional. You are
breaking your system. That it runs at all is merest luck.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2013-04-20 05:06, vazhavandan wrote:
>
>> 12.3 is a fraction slower
> On a clean install 12.3 is faster than 12.2;)
Not in heavy math, code is known to run even 7 times slower (libm fault).
However, if his system behaves badly after the upgrade, compared to a
clean install, it is because he did not do the upgrade in the documented
and recommended manner. 3 docs, two methods:
Am 20.04.2013 13:38, schrieb Carlos E. R.:
> Not in heavy math, code is known to run even 7 times slower (libm fault).
Only for some edge cases, in general that affects only software which
needs to calculate excessive amounts of sines, cosines, exp’s. This is a
very rare case, usually that part of programs is a microscopic fraction
of the arithmetic done and general arithmetic and its optimizations are
not affected.
I do a lot of numeric calculations and in general the difference between
12.2 and 12.3 is exactly zero (of course since that only depends on the
optimization capabilities of the compiler and how optimized the fft,
blas and son libraries are which you use and not on glibc functions).
–
PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.0 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500
On 2013-04-20 14:06, vazhavandan wrote:
>
> robin_listas;2549351 Wrote:
>> Not in heavy math, code is known to run even 7 times slower (libm
>> fault).
>>
> Saw that thread. Do all s/w on standard installation use these
> libraries? I thought they were talking about some specific
> maths/scientific usage.
It seems to be some specific functions, yes. I have not seen a list of
affected functions, and how much each of them.
Yes, libm can be used by any standard application, but not many do those
operations in such a number as to be noticed.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
libm4 is not installed
on this system akonadi is not running nepomuk is not runing
this system is more like a chromebook
none of the bloated akonadi nepomuk kde programs is used
most programs i use run within the google browser so less overhead
gkrellm to check the inner working of the system and sensors
dit not install pulse audio thats good for gnome users
printing through HPLIB and google drive ( 2 tablets)
only 5 widgets cwp cpufreqdisplay clock network monitor Py Chasew
and to boot.localfs an boot.rootfsck have both chmod a+x
and are set B in runlevels
Why is there no tool to manage sytemd systemctl is funny to see but if you have no idea what systemd is then systemctl is one big questionmark
even systemadm does not do the job
thats why i say 12.3 is a minor upgrade
the real work has to be done before 13.1
so as a upgrade 12.3 can be a testbed
found 2 scripts nearbij systemd that enable a few services if i dont need them then how to get rid of them
It’s about libm, i.e. the system’s math library, not libm4…
Why is there no tool to manage sytemd systemctl is funny to see but if you have no idea what systemd is then systemctl is one big questionmark
even systemadm does not do the job
Well, enabling/disabling services in YaST Runlevel does still work.
And to be able to see the runlevel controls you need to have an /etc/inittab which isn’t there by default (you can copy it over from 12.2, f.e.).
I’m not sure how much effect the runlevel selection has, though…
I wouldn’t exactly call it “madness”. I guess it’s ignored by systemd anyway. (can’t check right now, though)
YaST’s runlevel control will magically appear if you copy it over.
But I didn’t want to suggest this **should **be done.
It is installed for sure! Otherwise your system wouldn’t even boot.
Hint: It’s in the glibc package and installed in /lib (or /lib64 if you’re on 64bit)…
I wouldn't exactly call it "madness". I guess it's ignored by systemd anyway. (can't check right now, though)
YaST's runlevel control will magically appear if you copy it over.
without them you cannot change runlevels yast is complaining localfs is not there
put boot.localfs in then its complaining rootfsk is not there
thats why i put them in and everything works as it should
RAID set "pdc_hgfehahg" was activated
RAID set "pdc_hgfehahg" was not activated
Trying manual resume from /dev/disk/by-id/raid-pdc_hgfehahg-part2
Invoking userspace resume from /dev/disk/by-id/raid-pdc_hgfehahg-part2
resume: libgcrypt version: 1.5.0
Trying manual resume from /dev/disk/by-id/raid-pdc_hgfehahg-part2
Invoking in-kernel resume from /dev/disk/by-id/raid-pdc_hgfehahg-part2
Waiting for device /dev/disk/by-id/raid-pdc_hgfehahg-part3 to appear: ok
fsck from util-linux 2.21.2
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/mapper/pdc_hgfehahg-part3
/dev/mapper/pdc_hgfehahg-part3: clean, 392009/14385152 files, 6086075/57539072 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/disk/by-id/raid-pdc_hgfehahg-part3
mount -o rw,noatime,nodiratime,discard,acl,user_xattr -t ext4 /dev/disk/by-id/raid-pdc_hgfehahg-part3 /root
Welcome to e[0;32mopenSUSE 12.3 (Dartmouth) (x86_64)e[0m!
Starting Collect Read-Ahead Data...
Starting Replay Read-Ahead Data...
[e[1;32m OK e[0m] Reached target Remote File Systems.
e[1;32m OK e[0m] Listening on Syslog Socket.
e[1;32m OK e[0m] Listening on udev Control Socket.
e[1;32m OK e[0m] Listening on udev Kernel Socket.
e[1;32m OK e[0m] Listening on Delayed Shutdown Socket.
e[1;32m OK e[0m] Listening on /dev/initctl Compatibility Named Pipe.
e[1;32m OK e[0m] Listening on udev Kernel Socket.
e[1;32m OK e[0m] Listening on udev Control Socket.
e[1;32m OK e[0m] Reached target Encrypted Volumes.
e[1;32m OK e[0m] Set up automount Arbitrary Executable File Formats File System Automount Point.
Expecting device dev-disk-by\x2did-raid\x2dpdc_hgfehahg\x2dpart2.device...
Expecting device dev-disk-by\x2did-ata\x2dST1000DM003\x2d1CH162_S1D3J8GP\x2dpart1.device...
Expecting device dev-disk-by\x2did-raid\x2dpdc_hgfehahg\x2dpart1.device...
e[1;32m OK e[0m] Listening on Journal Socket.
Starting LSB: Set default boot entry if called...
Starting Create dynamic rule for /dev/root link...
Starting create /dev/root symlink with dynamic rule...
Mounting Huge Pages File System...
Mounting POSIX Message Queue File System...
Starting udev Coldplug all Devices...
Starting Journal Service...
e[1;32m OK e[0m] Started Journal Service.
e[1;32m OK e[0m] Started Collect Read-Ahead Data.
e[1;32m OK e[0m] Started Replay Read-Ahead Data.
e[1;32m OK e[0m] Started Create dynamic rule for /dev/root link.
e[1;32m OK e[0m] Started LSB: Set default boot entry if called.
e[1;32m OK e[0m] Started create /dev/root symlink with dynamic rule.
e[1;32m OK e[0m] Mounted Huge Pages File System.
e[1;32m OK e[0m] Mounted POSIX Message Queue File System.
Starting udev Kernel Device Manager...
Starting Setup Virtual Console...
Starting Load Kernel Modules...
Starting Remount Root and Kernel File Systems...
e[1;32m OK e[0m] Started udev Kernel Device Manager.
Starting LSB: start dmraid...
e[1;32m OK e[0m] Started udev Coldplug all Devices.
e[1;32m OK e[0m] Started Load Kernel Modules.
e[1;32m OK e[0m] Started Remount Root and Kernel File Systems.
Starting Load Random Seed...
Starting Apply Kernel Variables...
e[1;32m OK e[0m] Started Load Random Seed.
e[1;32m OK e[0m] Started Apply Kernel Variables.
Starting Load Random Seed...
e%Ge[1;32m OK e[0m] Started Load Random Seed.
e[1;32m OK e[0m] Started Setup Virtual Console.
Starting udev Coldplug all Devices...
e[1;32m OK e[0m] Found device /dev/disk/by-id/raid-pdc_hgfehahg-part2.
Activating swap /dev/disk/by-id/raid-pdc_hgfehahg-part2...
e[1;32m OK e[0m] Found device /dev/disk/by-id/raid-pdc_hgfehahg-part1.
e[1;32m OK e[0m] Started udev Coldplug all Devices.
e[1;32m OK e[0m] Activated swap /dev/disk/by-id/raid-pdc_hgfehahg-part2.
e[1;32m OK e[0m] Reached target Swap.
Starting Show Plymouth Boot Screen...
e[1;32m OK e[0m] Reached target Sound Card.
e[1;32m OK e[0m] Found device ST1000DM003-1CH162.
e[1;32m OK e[0m] Started Show Plymouth Boot Screen.
e[1;32m OK e[0m] Started LSB: start dmraid.
Starting File System Check on /dev/disk/by-id/ata-ST1000DM003-1CH162_S1D3J8GP-part1...
Starting File System Check on /dev/disk/by-id/raid-pdc_hgfehahg-part1...
e[1;32m OK e[0m] Reached target Local File Systems (Pre).
Mounting Lock Directory...
Mounting /sys/kernel/debug...
Mounting Runtime Directory...
e[1;32m OK e[0m] Mounted Lock Directory.
e[1;32m OK e[0m] Mounted /sys/kernel/debug.
systemd-fsck[739]: /dev/mapper/pdc_hgfehahg-part1: clean, 368/40000 files, 116131/159744 blocks
e[1;32m OK e[0m] Mounted Runtime Directory.
e[1;32m OK e[0m] Started File System Check on /dev/disk/by-id/raid-pdc_hgfehahg-part1.
Mounting /boot...
e[1;32m OK e[0m] Mounted /boot.
e[1;32m OK e[0m] Reached target Local File Systems.
Starting Tell Plymouth To Write Out Runtime Data...
Starting Recreate Volatile Files and Directories...
Starting Trigger Flushing of Journal to Persistent Storage...
systemd-fsck[738]: /dev/sdc1: clean, 9541/61054976 files, 5918433/244190208 blocks
e[1;32m OK e[0m] Started Tell Plymouth To Write Out Runtime Data.
e[1;32m OK e[0m] Started Recreate Volatile Files and Directories.
e[1;32m OK e[0m] Reached target System Initialization.
Starting Restore Sound Card State...
Starting Console System Startup Logging...
e[1;32m OK e[0m] Listening on PC/SC Smart Card Daemon Activation Socket.
e[1;32m OK e[0m] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
e[1;32m OK e[0m] Listening on CUPS Printing Service Sockets.
e[1;32m OK e[0m] Listening on D-Bus System Message Bus Socket.
e[1;32m OK e[0m] Reached target Sockets.
e[1;32m OK e[0m] Reached target Basic System.
Starting Configure Plugged-In Printer...
e[1;32m OK e[0m] Started Configure Plugged-In Printer.
Starting LSB: Framebuffer setup...
Starting CUPS Printing Service...
e[1;32m OK e[0m] Started CUPS Printing Service.
e[1;32m OK e[0m] Reached target Printer.
Starting Haveged Entropy Gathering Daemon...
e[1;32m OK e[0m] Started Haveged Entropy Gathering Daemon.
Starting LSB: Script infrastructure to enable/disable certain power management functions...
Starting Avahi mDNS/DNS-SD Stack...
Starting LSB: Configure network interfaces and set up routing...
Starting System Logging Service...
Starting Login Service...
e[1;32m OK e[0m] Started File System Check on /dev/disk/by-id/ata-ST1000DM003-1CH162_S1D3J8GP-part1.
e[1;32m OK e[0m] Started Restore Sound Card State.
e[1;32m OK e[0m] Started Console System Startup Logging.
e[1;32m OK e[0m] Started LSB: Framebuffer setup.
e[1;32m OK e[0m] Started LSB: Script infrastructure to enable/disable certain power management functions.
e[1;32m OK e[0m] Started System Logging Service.
e[1;32m OK e[0m] Reached target Syslog.
Starting D-Bus System Message Bus...
e[1;32m OK e[0m] Started D-Bus System Message Bus.
Starting Initialize hardware monitoring sensors...
Starting ACPI Event Daemon...
e[1;32m OK e[0m] Started ACPI Event Daemon.
Mounting /usr/local...
e[1;32m OK e[0m] Started Initialize hardware monitoring sensors.
e[1;32m OK e[0m] Started Login Service.
e[1;32m OK e[0m] Started Avahi mDNS/DNS-SD Stack.
e[1;32m OK e[0m] Started Trigger Flushing of Journal to Persistent Storage.
Starting Permit User Sessions...
e[1;32m OK e[0m] Started Permit User Sessions.
Starting Getty on tty1...
e[1;32m OK e[0m] Started Getty on tty1.
e[1;32m OK e[0m] Reached target Login Prompts.
e[1;32m OK e[0m] Mounted /usr/local.
e[1;32m OK e[0m] Started LSB: Configure network interfaces and set up routing.
e[1;32m OK e[0m] Reached target Network.
Starting Command Scheduler...
e[1;32m OK e[0m] Started Command Scheduler.
e[1;32m OK e[0m] Reached target Host and Network Name Lookups.
e[1;32m OK e[0m] Reached target Remote File Systems (Pre).
Starting LSB: Network time protocol daemon (ntpd)...
Starting LSB: Sound daemon with network support...
Starting /etc/init.d/boot.local Compatibility...
e[1;32m OK e[0m] Started /etc/init.d/boot.local Compatibility.
e[1;32m OK e[0m] Started LSB: Network time protocol daemon (ntpd).
e[1;32m OK e[0m] Reached target Multi-User.
Starting LSB: X Display Manager...
e[1;32m OK e[0m] Started LSB: X Display Manager.
/CODE]
it seems that systemd LSB and plain boot
are competing to start the raid array
is this the slow boot???
is this normal ?????????
RAID set "pdc_hgfehahg" was activated
RAID set "pdc_hgfehahg" was not activated
Trying manual resume from /dev/disk/by-id/raid-pdc_hgfehahg-part2
Invoking userspace resume from /dev/disk/by-id/raid-pdc_hgfehahg-part2
resume: libgcrypt version: 1.5.0
Trying manual resume from /dev/disk/by-id/raid-pdc_hgfehahg-part2
Invoking in-kernel resume from /dev/disk/by-id/raid-pdc_hgfehahg-part2
Waiting for device /dev/disk/by-id/raid-pdc_hgfehahg-part3 to appear: ok
fsck from util-linux 2.21.2
[/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/mapper/pdc_hgfehahg-part3
/dev/mapper/pdc_hgfehahg-part3: clean, 392009/14385152 files, 6086075/57539072 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/disk/by-id/raid-pdc_hgfehahg-part3
mount -o rw,noatime,nodiratime,discard,acl,user_xattr -t ext4 /dev/disk/by-id/raid-pdc_hgfehahg-part3 /root
i boot from masterboot record with grub
[1;32m OK [0m] Set up automount Arbitrary Executable File Formats File System Automount Point.
Expecting device dev-disk-by\x2did-raid\x2dpdc_hgfehahg\x2dpart2.device...
Expecting device dev-disk-by\x2did-ata\x2dST1000DM003\x2d1CH162_S1D3J8GP\x2dpart1.device...
Expecting device dev-disk-by\x2did-raid\x2dpdc_hgfehahg\x2dpart1.device...
this is just a few lines futher in boot.log
The raid array was made in 12.2 and fstab is also from 12.2
12.3 cant handle it so to see
so what has to be altered to boot without these messages?
The names the raid array has are as named in the top half
what systemd expects is not the same
And that is also the trouble installing 12.3 on this mobo
what you define is not the same as he uses so format goes beyond the end of patition
error -3030