European digital sovereignty – but no adequate financial support for students in Germany?

Present discussions about European Digital Sovereignty underline the fact of an almost complete dependence of Europe and in particular of Germany on US technology – regarding

  • shear computational power (supercomputers, data centers),
  • classic IT, office and ERP applications (dominated by Microsoft, Google, Meta, …)
  • as well as AI models and related computational capacities
  • and, last but not least, the combination of robotics and defense systems with AI.

The standard recipe is a call for money to build more computation centers on European soil.

Actually, most of such centers presently under construction are planned to be eventually used by US companies. This is a sign of schizophrenia of European and German politicians or – even worse – a total lack of understanding of what happens in the fields of IT/AI and of what digital sovereignty really requires. Certainly not more data centers of Google, Microsoft or Meta in Germany. At least, this should not be a top priority item on an agenda for European independence of US monopolists.

Related concerns of European experts working in the fields of IT and AI culminated last week in the publication “https://europe2031.ai/“. The paper and the scenario described in it was triggered by the present failure of European governments to take and scale counter-measures against a coming US-dominance in the little remaining interval of time – if there is any at all. Visitors of this blog have probably read the paper, already.

From my perspective as a former IT consultant, I want to add three points which the scenario in the “Europe31.ai” paper does not cover to the extent these points deserve.

The first point is “education“:

AI is predominantly the result of certain types of SW, the development of artificial neural networks, the theory of artificial neural networks and advanced ideas about learning and learning algorithms. But, and this is sometimes totally underestimated, AI is also based on a lot of mathematics (in particular regarding Linear Algebra, analysis of data distributions in multiple dimensions, differential geometry, theory of graphs, optimization problems and advanced statistics). If you do not believe it, take a regular look at the papers published by American and Chines universities.

Top hardware is also an important aspect, but as China has shown with its recent CPU-based supercomputer LineShine and “DeepSeek” not a predominant factor. You can build sufficient supercomputer power also based on previous generations of hardware. What is much more important is the bundling and focusing of efforts in the field of AI – as well as the support of administrative institutions of solution oriented thinking and start-ups. Regarding these points we have, unfortunately, a lot to learn from China and investment companies in the US.

And: As in any high-tech field, real progress in the field of Machine Learning and LLM-based AI was and is achieved by clever ideas.

Proof: Consider the impact of transformer based neural networks on the development of present LLM systems. One idea, enormous consequences. And new emerging tech giants.

However and naturally: Clever ideas in turn require educated people.
Consequence: European AI Sovereignty requires at least as much investment in the education of people as in hardware.

Now, compare this with the fact that the present conservative government of Germany plans NOT to rise the state’s budget for supporting and helping students (Bafög) who do not have rich parents or parents with academic background.

A rise in support for extremely high costs for student apartments in German cities and a general increase of the support sum according to the inflation rate has been declined by a minister who – according to the press – made a paid career in their party and jobs in attached organizations already during their years as students; for related criticism see e.g. here, here and here and many more press articles. Its a shame – and I find no other word for it.

The decline came, although the level of financial support for students had and has already for several years been below minimum social standards guaranteed to other groups of citizens in Germany.

The obvious stupidity of such a budget planning remembers strongly of the Kohl era when theoretical physicists were told that Germany did not need theoretical researchers, but application oriented engineers. As if this had ever been a contradiction … My first diploma exam (in astrophysics) started with such a statement of the examining professors – uttered with a grain of pity for my generation. 15 years later the very same economy (not science) advisors, who once had told Kohl their “wisdom” about German engineering, suddenly found out that Germany did not receive enough Nobel prizes and that the best educated academic people had left Germany to work abroad. And advised chancellor Merkel to start initiatives on theoretical education and research. Well done …

Well, as a relatively old person with a PhD in physics, who can look back on more than 35 professional years in IT, you automatically think of the 5 apes in action, which unfortunately have become so characteristic of conservative German governments during the last 3 decades:

(1) Don’t hear and listen (to warnings of scientists), (2) don’t see (but ignore obvious developments in high tech realms), (3) don’t speak (about problems and long term strategy or e.g. about the self-inflicted dependency on Russian gas during the Merkel period and avoid any discussion about not having invested e.g. in digitization and AI), (4) don’t understand (because a substantial lack of MINT scientists among politicians), (5) don’t pick up ideas beyond a conservative ideology of the last century (let the market alone do its job).

As an elderly, rather conservative person, I do not utter this criticism lightheartedly. But the politicians of my generation (Merkel era) have totally failed to make my country, Germany, fit for the challenges of the time once called “future” – which now is the present time. Not to speak of today’s future …

Continue reading

Orthogonal projections of MVNs and of their ellipsoidal contour surfaces

Some readers may remember a post series I have written in this blog about the reconstruction of human faces with a CNN-based Autoencoder. I could show that the information in the latent space of the Autoencoder is given in form of a core of a Multivariate Normal Distribution [MVN].

This did not surprise too much as there are good reasons to assume that facial features on average, but in particular across rather symmetric celebrity faces follow Gaussian distributions. Hundreds of encoded features together form a MVN-distribution in a latent space of hundreds of dimensions. The Encoder part of a CNN-based Autoencoder is a pattern extraction machine – and there is no simpler pattern in multiple dimensions than a (off-center) MVN! A MVN’s multidimensional and concentric contour surfaces are ellipsoids, which have an algebraic description in form of quadratic forms. In case of the MVN defined by the inverse of the covariance matrix.

During the named series, I have extensively used that fact that the projections of a multidimensional MVN down to a coordinate planes result in 2-dimensional bivariate MVNs. The elements of the (2×2)-covariance matrix of the various 2-dimensional projected distributions could simply be picked from (nxn) covariance matrix of the original MVN – by a simple selection process. I had taken this procedure as granted, as it had been claimed in some publications. And it worked very well … See e.g.

and links therein to other posts. The projection of course affects the (n-1)-dimensional ellipsoidal and concentric contour surfaces of a MVN and maps them onto (p-1)-dimensional contour ellipses of the projected 2-dimensional MVNs. For respective images see this post:

Last weeks I looked a bit deeper into the mathematics of orthogonal projections of multidimensional ellipsoids onto sub-spaces of the ℝn. It came a bit of a surprise to me that the math behind the projections of figures controlled by quadratic forms is relatively complicated. In the general case of the projection to a p-dimensional sub-space, the quadratic form matrix for the ellipsoidal hull of the projection image is a so called Schur complement of the original ellipsoid’s quadratic form matrix.

Fortunately, the relation between the inverse matrices of the quadratic forms for the ellipsoids could be established in a way that is fully consistent with the mapping of covariance matrices of MVNs and and related matrices of their projection images. However and in contrast to other publications, I found that a solid proof requires some Linear Algebra around Schur complements.

Readers interested in MVNs and their mathematical properties for statistical analysis e.g. in Machine Learning contexts may find detailed information in the following articles of mine:

Orthogonal projections of multidimensional ellipsoids

However, basic Linear Algebra knowledge is required! The articles should also be interesting for physicists.
 

New year – new operative system for desktops and laptops?

Some readers have noticed that I seldom write in this blog – at least compared to certain periods before 2023. One reason for this has been and is: Linux – in my case Opensuse Leap 15.x – has just worked well for me up to this very day. Small glitches, but on average Leap 15 and its subversions have always fulfilled my needs and requirements. (Another reason is that after retirement, I got more interested in math, physics, ML and politics.)

However, I also have to say that my private needs have become very limited. Significantly fewer server components due to a removal of LAMP/Postgre-SQL/JS/JQuery and Kolab stacks and keeping only a minimum of LDAP services. Only some virtualization for server-based mail services. Actually, I have become a desktop user, sometimes using a Python/CUDA stack for local Machine Learning experiments. Aside of mail services, my own servers have become simple data containers. And the few requirements some remaining customers of my wife have with respect to their web-installations do not require full-fledged development stacks.

Now, as a pure desktop user, I am approaching a point (EOL of Leap 15.6) at which I seriously have to decide whether I should turn to Opensuse Leap 16 or move to a completely different distribution as Debian.

The reason is that Leap 16 comes with a lot of fundamental changes and a significant reduction of supported application packages. A new installer (Agama), no Yast any longer, the container-based ALP-system mixed with RPMs, confusion about immutability and BTRFS, Myrlyn as an interface to package management, SE-Linux instead of Apparmor, no support for older Nvidia cards, Agama installer (according to some users) not fully working with Luks and LVM, … Well, what I read smells like a bunch of potential problems.

Regarding ALP and containers, I have used some applications like Blender for a long while now with Snap and/or Flatpak – and was always shocked about the additional disk space requirements. So, I am very skeptical regarding this aspect. It may be suited for Cloud based services – but for local installations in an environment with a mixture of desktop systems and small servers? The question is whether and in which form ALP affects small file server installations.

Aside of ALP, what is my present strategy regarding my desktops and laptops?

I will give Leap 16 a chance. As a fist step, I will install it freshly on an external USB disks for my various systems and see what the installation leads to. I will start with a mutable version for desktop usage. One objective is to install Leap 16 with multiple partitions, all encrypted with LUKS and, of course, using LVM. For desktop systems with relatively new Nvidia cards I expect full support (including CUDA).

As for an old Optimus laptop which has an Nvidia card that requires the version 470 Nvidia drivers, I will probably have to accept that its card is no longer supported. So, I will have to see how far one gets on such a system with the Nouveau driver and a Noveau-adapted version of prime-select. I hope that Blender runs with reasonable performance even on these systems. If everything works as expected, I will start with an upgrade of the existing 15.6 installations on desktops and laptops.

If I, however, run into serious trouble, I will definitely switch to Debian. Debian is my preferred alternative, based on very good experiences with Debian on servers and Kali Linux on KVM virtualized desktops.

The decision to keep Leap or not may depend on the kind of system and their age.

I will report about my experiences during February. So, stay tuned …

Leap 15.6, Nvidia driver 580 – resume from S3 deep sleep state after suspend to RAM?

Some months ago I wrote a post about a Nvidia option, which at that time helped to overcome a specific problem with a suspend-to-RAM [leading to a deep S3 sleep state] action and a following incomplete resume operation from the S3 state to the original desktop session. The setting “nvidia_modeset vblank_sem_control=0” at least remedied a result which had been described by many users of different Linux flavors: The resume process ended up in a black screen with only a mouse cursor being visible. This situation was difficult to control – and typically one had to reboot the system.

In my experience things have changed a bit since the named post. Therefore, I give a brief summary of other settings below. These settings appear to support relatively stable suspend-to-ram and resume operations on my Leap 15.6 system with my X11-based KDE Plasma a newer Nvidia driver of version 580. However, though not leading to black screens any more, the resume process will not always restore the interrupted KDE/Plasma session. Notably, after a series of extended tests the suspend/resume processes seem to work significantly more stable with Wayland than with X11.

Note, 11/08/25: I had to change this post after some more systematic tests. While I could confirm my general impression that driver Nvidia 580.105 has brought more stability to resume processes from deep S3 sleep, on a X11 based KDE/Plasma desktop, resume processes do fail sometimes – in 20%-30% of the cases. Probably due to race conditions during the restoration of the interrupted KDE/Plasma-session (see below). This did not happen in a series of tests with different sleep time intervals for a Plasma desktop based on Wayland.

Card, driver, services, grub_cmdline

I describe the settings for just one of my systems. The board is an older ASRock Z170 extreme+. The Nvidia card is a 4060 TI. My present Nvidia driver is the proprietary Nvidia driver of version 580.105.08. It was installed from the usual repository. In particular the The RPM “nvidia-driver-G06-kmp-default” is installed. KDE is of version 5.115, Plasma of version 5.27, t5 of version 5.15.12.

Note: I have not checked whether things work on other systems or with Gnome based desktops, yet.

The default grub cmdline contains the parameter setting

nvidia-drm.modeset=1

The services

  • nvidia-suspend.service
  • nvidia-hibernate.service
  • nvidia-resume.service
  • nvidia-persistenced.service
  • nvidia-powerd.service

are all enabled.

Nvidia configuration settings

In the directory “/etc/modprobe.d”, I have a file 50-nvidia.conf”, which contains the following option

blacklist nouveau
options nouveau modeset=0

options nvidia NVreg_DeviceFileUID=0
options nvidia NVreg_DeviceFileGID=33
options nvidia NVreg_DeviceFileMode=0660
options nvidia NVreg_TemporaryFilePath=/var/tmp
options nvidia NVreg_EnableS0ixPowerManagement=1
options nvidia NVreg_PreserveVideoMemoryAllocations=1
options nvidia-drm modeset=1
#
options nvidia_modeset vblank_sem_control=0

Resume-buttons

I usually start suspending to RAM by options offered on the KDE Plasma desktop. But things work also from the command line or with automatic invocation after some idle time of the desktop. My ASRock-board shows that (video) memory contents is written to the system’s root filesystem (see option ) by indicating a respective storage-activity ahead of reaching the S3 state. When the deep suspend state S3 is reached the power button starts blinking.

The default keyboard-button for triggering a resume from sleep is the “blank” key. I can also use the power button on my PC case to start the resume process. If the resume process leads to the old KDE/Plasma session – which it does in more than 60% of the cases with X11 – this session is restored in the state before the suspend-process, with all interrupted processes running again. Independent of the duration of the sleep time. Logs show that a time jump is recognized and that the system adapts to it.

Results after a series of tests on X11 and Wayland based KDE Plasma desktop

In contrast to previous versions of this post, I have now investigated the behavior of the resume processes a bit more systematically, both for X11 and Wayland. For each of the platforms, I have tested the success of suspend/resume processes 15 to 20 times – with growing duration of the sleep interval between 5 minutes up to 40 minutes. The tests also varied with respect to the triggering of the suspend action, regarding both direct user action or, alternatively, an automatic start of a suspend process after some defined idle time. In the latter case a lock/login screen was invoked some minutes before suspend started. (You find respective options in KDE-5’s “systemsettings5”.)

X11-based KDE/Plasma
In the case of X11 a return to the interrupted KDE Plasma session fails in around 30% of the cases. In such cases the resume process ends up in a SDDM login-screen for a new KDE Plasma session. The logs then show that the old Plasma session could not be restored due to some error (see below). The system then obviously turns into a workaround: It forgets the old KDE-session, restarts into the default graphical target and starts SDDM for a new graphical user session. So, the problem with a blank screen and only the mouse cursor blinking appears to have gone (maybe due to the settings “nvidia_modeset vblank_sem_control=0” or due to other improvements; this still has to be checked).

Note, 11/08/25: A previously assumed dependency of the resume success on using the power button or, alternatively, the keyboard to start the resume operation has disappeared after a larger number of tests. There still seems to be a dependency on the duration of the sleep time.

This result means that users of KDE/Plasma should take care of saving all their work before leaving their KDE/plasma desktop unattended with settings that automatically trigger suspend after a defined idle time.

Wayland-based KDE/Plasma
Let me first mention that Wayland meanwhile works really well for the wide range of applications I regularly use. For all the 20 times I tested suspend/resume on Wayland, each trial ended in a successful and complete restoration of the interrupted KDE/Plasma session (which could be entered via login to my KDE session lock-screen).

Race conditions during resume for X11-based KDE/Plasma desktop?

Afterwards, I have checked the logs for X11 and found that the failed resume processes have led to a situation were the X11-session appeared to be broken for certain starting applications as pulseaudio and gkrellm. This may be the result of race conditions between X11-restoration and processes requiring an X11-connection already during resume. In such a case the restart of the default graphical target happened.

Conclusion

The suspend/resume behavior on Leap-systems obviously changes depending on kernel and Nvidia’s driver versions. Presently and on Leap 15.6 systems, we have only reached a relatively stable status regarding suspend-to-RAM and resume for KDE Plasma on a X11-basis: In more than 60% of the cases, the interrupted KDE/Plasma session is fully restored. In other cases I, at least, did not experience blank screens, but a return to the SDDM login-screen for a new desktop session. X11 users should therefore save all their work before leaving the desktop.

The good news is that suspend/resume appears to work flawlessly with Wayland (at least on my conservative Leap system).

I hope this post helps some readers who experience instability problems with suspend/resume on Leap systems with Nvidia graphics cards.

 

Leap 15.6, Nvidia-driver – problems due to dependency on original kernel-default-devel package

After some updates of Opensuse’s Leap 15.6 systems via a variety of repositories (including the SLES 15.6 repo as the main and leading repository), one of my installed packages was removed. I am talking about a very central one, namely “kernel-default-devel version 6.4.0-160600.21.3-x86_64”. (It can be found in the main repository of the 15.6 distribution.) This was in so far reasonable as I have no longer any respective kernel installed. All used kernels are of version “6.4.0-156000.23.xxx”.

However, the removal of the old kernel-default-devel package caused difficulties with the Nvidia drivers in Opensuse’s respective repositories. The installation and compilation of the required diver module delivered by package “nvidia-driver-G06-kmp-default” would fail. It requires the original kernel-default-devel version 6.4.0-150600.21. As a consequence on the affected systems the Nvidia driver could no longer be loaded.

A supplemental installation of the original kernel-default-devel package (coming with the distribution) remedied the problems. Hope this helps others who experience similar problems during system updates.