From vmoutoussamy at suse.com Mon Mar 2 06:48:12 2020 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Mon, 2 Mar 2020 13:48:12 +0000 Subject: [sle-beta] =?utf-8?q?SLE_15_SP2_Public_Beta_=E2=80=93_Snapshot_Up?= =?utf-8?b?ZGF0ZXMgKDUsNiw3KQ==?= Message-ID: <94220261-EE05-452A-B9AF-6F4C29AFCBEB@suse.com> Hi, [You can also read the HTML version of this email in the public blog post: https://www.suse.com/c/sle-15-sp2-public-beta-snapshot-updates-567/ ] As you might know from our SLE 15 SP2 Public Beta announcement, we are now releasing fewer Public Beta ISOs but we are releasing weekly updates, called Snapshot, in our Beta Online Channels! So let?s see what notable changes did we make 3 weeks after the Public Beta release. = Beta Registration Code = It?s important to note that, to benefit from having the freshest updates on your SLE 15 SP2 Beta system, you need to register it with a Beta Registration Code. This will give you access to our Beta Online Channels thus allowing you to check and install all updates. Please request your Beta Registration Codes at beta-programs at lists.suse.com. = Notable Changes = == MariaDB == We have recently update MariaDB to version 10.4.12. We are aware that some parts of the distribution may need further adaptations to the new version, so it?s important to read the following notes: === Changes & Improvements === ? MariaDB 10.4 ? MariaDB 10.3 === How to upgrade === ? 10.2 -> 10.3 ? 10.3 -> 10.4 === Important packaging changes and news === ? Provide mariadb variants of mysql binaries (e.g. mariadb-dumpslow is a symlink to mysqldumpslow and the like), ? Add rcmariadb compat link, ? Rename libmysqld subpackage (embedded library) to libmariadbd since libmysqld.so was renamed to libmariadbd.so, ? remove sql_mode from my.cnf since NO_ENGINE_SUBSTITUTION and STRICT_TRANS_TABLES are already set by default from version 10.2.4, ? enhance mariadb.service and mariadb at .service with various options (Documentation=, User=, Group=, KillSignal=, SendSIGKILL=, Restart=, RestartSec=, CapabilityBoundingSet=, ProtectSystem=, ProtectHome=, PermissionsStartOnly= and UMask=), ? Remove ?innodb_file_format? option from my.cnf file that was removed in MariaDB 10.3.1. Also remove ?innodb_file_per_table=ON? option that is ON by default and it?s redundant now. We will appreciate feedback on how other subsystems work with updated MariaDB. == Packages Added == ? libblockdev2: 2.22-1.1 ? libbytesize1: 1.4-1.1 ? libyui-ncurses-rest-api11: 0.1.1-1.1 ? libyui-qt-rest-api11: 0.1.1-1.1 ? libyui-rest-api11: 0.3.0-1.1 ? llvm9: 9.0.1-1.3 ? prometheus-ha_cluster_exporter: 1.0.0beta6-1.1 ? prometheus-hanadb_exporter: 0.7.0+git.1581952699.a346b55-bp152.1.2 ? python-prometheus_client (renaming and replacing python-prometheus-client): 0.7.1-1.1 == Packages Updated== ? 389-ds: 1.4.2.8~git0.3aaa3e820-1.3 ? autoyast2: 4.2.27-1.9 ? bcm43xx-firmware: 20180314-12.1 ? ceph-common: 15.1.0.818+g5f8ed0e957-1.7 ? crmsh: 4.2.0 ? gcc7: 7.5.0+r278197-4.16.2 ? grub2: 2.04-3.1 ? intel-vaapi-driver: 2.4.0-1.2 ? ipmitool: 1.8.18+git20200204.7ccea28-1.3 ? kernel: 5.3.18-7.3 ? libstorage-ng: 4.2.65-1.1 ? libvirt: 6.0.0-3.11 ? libyui: 3.9.3-1.3 ? lshw: B.02.18+git.20190613-3.2 ? mariadb: 10.4.12-1.1 ? Mesa: 19.3.4-44.2 ? MozillaFirefox: 68.5.0-3.72.1 ? MozillaThunderbird: 68.5.0-3.71.1 ? nodejs12: 12.15.0-1.5 ? npm12: 12.15.0-1.5 ? openssl-1_1: 1.1.1d-6.2 ? ovmf: 201911-3.6 ? permissions: 20200127-14.8 ? pesign-obs-integration: 10.1-3.6.1 ? postgresql: 10-8.6.1 ? powerpc-utils: 1.3.7.1-3.9.1 ? protobuf: 3.9.2-2.1 ? qemu: 4.2.0-5.3 ? rmt-server: 2.5.4-1.4 ? s390-tools: 2.11.0-4.3 ? salt: 2019.2.3-2.6 ? slurm: 20.02.0-bp152.1.1 ? systemd: 234-31.7 ? u-boot-tools: 2020.01-3.1 ? udisks2: 2.8.1-1.1 ? valgrind: 3.15.0-15.2 ? vm-install: 0.10.08-1.7 ? yast2: 4.2.67-1.3 ? zypper: 1.14.34-1.2 Your SUSE Linux Enterprise Team. Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager From malcolmlewis at cableone.net Mon Mar 2 15:56:33 2020 From: malcolmlewis at cableone.net (Malcolm) Date: Mon, 2 Mar 2020 16:56:33 -0600 Subject: [sle-beta] SLE 15 SP2 - Add serial console access to RPi JeOS In-Reply-To: References: <20200223125935.4c7abb2b@grover.homelinux.org> Message-ID: <20200302165633.0607ae19@grover.homelinux.org> On Mon, 2 Mar 2020 19:18:41 +0000 Andreas Faerber wrote: > Hi Malcolm, > > Am Sonntag, den 23.02.2020, 12:59 -0600 schrieb Malcolm: > > Console access seems to be missing from the grub options at boot; > > > > cat /etc/default/grub | grep GRUB_CMDLINE_LINUX_DEFAULT > > > > GRUB_CMDLINE_LINUX_DEFAULT="plymouth.enable=0 console=tty quiet > > root=UUID=f7bb2dae-ab02-4f1f-8dd5-dd615a1ef946 rw " > > > > Added console=ttyS0,115200n8 and grub2-mkconfig -o > > /boot/grub2/grub.cfg > > > > Image: SLES15-SP2-JeOS.aarch64-15.2-RaspberryPi-PublicBeta.raw.xz > > Thanks for reporting this. It should be the same behavior as SLE15 > SP1. In our experience most customers did not have a serial adapter > attached and used HDMI for initial evaluation. I'd be happy to extend > that to cover serial console by default, but I fear either way it > will require editing the GRUB command line in menu and/or config. > > What we can offer is to use "console=ttyS0,115200n8 console=tty", > which would then by default give you the kernel log on serial only by > default (like openSUSE Tumbleweed does), but I assume you would also > want to run the jeos-firstboot setup on serial, which would still > require editing the command line to drop trailing "console=tty". > Users with HDMI monitor only would then need to remove > "console=ttyS0,115200n8". > > Also note that the name of the serial device varies between ttyS0, > ttyAMA0, ttyAMA1 and theoretically more, depending on your Device Tree > aliases and [extra]config.txt settings. When someone tweaks > *config.txt or loads DT Overlays, they may need to edit the command > line, too, if we hardcode it there. > > The Compute Modules on base boards such as MyPi are another scenario > we need to consider. I think we should be okay there in most cases. > > U-Boot always emits on serial console, so people wanting to use the > serial pins for HATs (e.g., GPS, modem) may need to take steps such as > resetting the external devices via GPIO later from userspace or > disabling serial output in the DT and re-enabling it from U-Boot, so > they would not suffer much extra from needing to disable kernel output > on serial, too. > > Would the above order of serial followed by graphical work for you? > In GRUB you would still need to press 't' for boot menu on serial. Hi Andreas Thank you for the detailed explanation and offer to modify which would work for me :) In saying that, perhaps an alternative option would be in the Release Notes to advise users what to change for different boot scenarios? As long as I can press 't' to get to the grub menu and modify for first boot it's not an issue. -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20200229 | GNOME Shell 3.34.4 | 5.5.6-1-default Intel DQ77MK MB | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/Nvidia up 1 day 5:27, 2 users, load average: 0.22, 0.89, 1.55 From vmoutoussamy at suse.com Tue Mar 3 01:55:25 2020 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Tue, 3 Mar 2020 08:55:25 +0000 Subject: [sle-beta] SLE 15 SP2 - Add serial console access to RPi JeOS In-Reply-To: <20200302165633.0607ae19@grover.homelinux.org> References: <20200223125935.4c7abb2b@grover.homelinux.org> <20200302165633.0607ae19@grover.homelinux.org> Message-ID: <176783DA-647A-4981-8559-AC850630E699@suse.com> Hi, > On 2 Mar 2020, at 23:56, Malcolm wrote: > Hi Andreas > Thank you for the detailed explanation and offer to modify which would > work for me :) In saying that, perhaps an alternative option would be > in the Release Notes to advise users what to change for different boot > scenarios? > > As long as I can press 't' to get to the grub menu and modify for first > boot it's not an issue. If the solution is just to document possible configuration for various scenario, I guess the RPi QuickStart Guide could be updated: https://documentation.suse.com/sles/15-SP1/single-html/SLES-rpi-quick/#art-rpiquick Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager From malcolmlewis at cableone.net Tue Mar 3 05:21:12 2020 From: malcolmlewis at cableone.net (Malcolm) Date: Tue, 3 Mar 2020 06:21:12 -0600 Subject: [sle-beta] SLE 15 SP2 - Add serial console access to RPi JeOS In-Reply-To: <176783DA-647A-4981-8559-AC850630E699@suse.com> References: <20200223125935.4c7abb2b@grover.homelinux.org> <20200302165633.0607ae19@grover.homelinux.org> <176783DA-647A-4981-8559-AC850630E699@suse.com> Message-ID: <20200303062112.3469661c@grover.homelinux.org> On Tue, 3 Mar 2020 08:55:25 +0000 Vincent Moutoussamy wrote: > Hi, > > > On 2 Mar 2020, at 23:56, Malcolm wrote: > > > > > Hi Andreas > > Thank you for the detailed explanation and offer to modify which > > would work for me :) In saying that, perhaps an alternative option > > would be in the Release Notes to advise users what to change for > > different boot scenarios? > > > > As long as I can press 't' to get to the grub menu and modify for > > first boot it's not an issue. > > If the solution is just to document possible configuration for > various scenario, I guess the RPi QuickStart Guide could be updated: > https://documentation.suse.com/sles/15-SP1/single-html/SLES-rpi-quick/#art-rpiquick > Hi Some notes in section 3 'Booting for the First Time' would seem appropriate? -- Cheers Malcolm ??? SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20200229 | GNOME Shell 3.34.4 | 5.5.6-1-default Intel DQ77MK MB | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/Nvidia up 1 day 19:07, 2 users, load average: 2.67, 2.06, 1.77 From suresh.sandur at thalesesecurity.com Thu Mar 5 02:53:27 2020 From: suresh.sandur at thalesesecurity.com (Sandur, Suresh) Date: Thu, 5 Mar 2020 09:53:27 +0000 Subject: [sle-beta] missing sources in 5.3.18-7 kernel-source Message-ID: Hello, I updated SLES15 SP2 from 5.3.18-4-default to 5.3.18-7-default. I also updated kernel-default-devel. After that, all the *[ch] files in /usr/src/linux-5.3.18-7/fs are gone. What happened to these files? regards, Suresh -------------- next part -------------- An HTML attachment was scrubbed... URL: From beta-programs at lists.suse.com Mon Mar 9 05:06:07 2020 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Mon, 09 Mar 2020 12:06:07 +0100 Subject: [sle-beta] [ANNOUNCE] SUSE Linux Enterprise 15 Service Pack 2 Weekly Update Message-ID: <5e66231f7f9e3_30022ac2ae5965f0382d6@zourite.lab.gb.mail> Our Weekly Update for SUSE Linux Enterprise 15 Service Pack 2 is available. - SUSE Linux Enterprise Server (SLES), - SUSE Linux Enterprise Server for SAP (SLES for SAP), - SUSE Linux Enterprise Just Enough Operating System (JeOS), - SUSE Linux Enterprise High Availability (SLEHA and SLEHA GEO), - SUSE Linux Enterprise Desktop (SLED), - SUSE Linux Enterprise Workstation Extension (SLEWE), - SUSE Linux Enterprise for High Performance Computing (SLEHPC). State Update We would like to inform you about the current state of SLE 15 SP2. We are not satisfied with the current quality of our builds in regard of the approaching Release Candidate phase. Many of the known issues are being tackle but our recent changes to some of our packages - details further down below - need extra care. Due to those changes we require a specific test cycle to ensure the quality of future RC milestone. We will inform you about further milestones releases later on. Download and Apply Updates Please note that to be able to test the changes announced in this email, you need to register your system with a Beta Registration Code! To request Beta Registration Code, you need to follow this[1]. We will then send you your codes along with a complete FAQ, on how to proceed. Notable Changes PostgreSQL 12 PostgreSQL 12 has been added to SLE 15 SP2! Please note that PostgreSQL 10 is still available. We highly recommend to read the available upstream documentation for changes and upgrades: - PostgreSQL 11[2] - PostgreSQL 12[3] We have the following two changes to the layout of subpackages that come out with PostgreSQL 12: - The former postgresql10-devel package will be split into postgresql12-devel (containing everything that's needed to build database clients that link against libpq and libecpg) and postgresql12-server-devel (containing everything that's needed to build server extensions). - There is a new optional subpackage called postgresql12-llvmjit. All new packages of course also have a noarch companion without a version number in the name, i.e. postgresql-server-devel and postgresql-llvmjit . Others - MariaDB 10.4[4] - Media Changes[5], - SCSI Devices[6], - Tech Preview: Maven in version 3.6.3 has been added to SLES 15 SP2 as a Tech Preview, Added Packages - container-diff: 0.15.0-1.4.2 - erlang: 22.2.7-1.4 - glibmm2: 2.61.1-1.1 - glslang: 8.13.3559+git20-1.1 - libsigc++3: 3_0-0-3.0.2-1.1 - lifecycle-data-sle-module-development-tools: 1-1.2 - postgresql12: 12.2-1.1 - python3-xattr: 0.9.1-7.2 - python-cfn-lint: 0.21.4-3.3.9 - python-zc.lockfile: 2.0-1.2 - rabbitmq-server: 3.8.2-1.4 - shaderc: 2019.1-1.1 - spirv-cross: 20200116-1.1 - terraform: 0.12.19-3.6.1 - terraform-provider-susepubliccloud: 0.0.1-3.3.1 - vulkan (+ tools) 1.2.133-1.3 Updated Packages - updated GNOME stack to 3.34.4 (including applications like evolution, baobab, gdm, NetworkManager, ModemManager, seahorse, vino...) - updated maven stack - updated yast2 stack - apache2: 2.4.41-4.13 => 2.4.41-5.3 - baobab: 3.26.1-1.47 => 3.34.0-1.3 - cifs-utils: 6.8-3.18 => 6.9-5.3.1 - flatpak: 1.6.1-1.13 => 1.6.2-1.1 - flatpak-builder: 1.0.3-1.29 => 1.0.9-1.1 - gdb: 8.3.1-8.8.1 => 8.3.1-8.11.1 - gtk3: 3.24.13+0-1.30 => 3.24.14-1.1 - glib2: 2.62.3-1.22 => 2.62.5-1.1 - glibc: 5.3-1.35 => 5.3-1.38 - java-1_8_0-ibm: 1.8.0_sr6.0-3.30.1 => 1.8.0_sr6.5-3.33.2 - meson: 0.51.2-1.20 => 0.53.1-1.2 - ninja: 1.8.2-1.22 => 1.10.0-1.2 - nodejs10: 10.18.0-1.15.1 => 10.19.0-1.18.1 - openssh: 8.1p1-1.6 => 8.1p1-2.2 - ovmf: 201911-3.6 => 201911-4.4 - pdsh: 2.33-5.32 => 2.33-7.6.1 - perl: 5.26.1-7.6.1 => 5.26.1-7.9.1 - postgresql10: 10.10-8.6.1 => 10.12-1.1 - postgresql: 10-8.6.1 => 12-1.1 - python3: 3.6.10-3.42.2 => 3.6.10-3.47.2 - raspberry-firmware: 2020.02.20-1.1 => 2020.02.20-1.2 - saptune: 2.0.2-8.8.1 => 2.0.3-1.2 - spirv-tools: 2017.0.g103-2.17 => 2020.1~git24-1.3 - tomcat: 9.0.30-10.14 => 9.0.31-1.5 - wayland-devel: 1.16.0-5.16 => 1.18.0-1.2 - wicked: 0.6.61-1.26 => 0.6.62-1.2 - zypper-migration-plugin: 0.12.1529570802.4a668e3-4.35 => 0.12.1580220831.7102be8-6.4.1 Removed Packages - cfn-lint - python-xattr (but python3-xattr has been added) SLE Beta Page ?[7] If you have _ANY_ concerns, doubts, inquiry, etc please contact beta-programs at lists.suse.com. Your SUSE Linux Enterprise Team Do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. Click here to unsubscribe.[8] [1]:https://www.suse.com/betaprogram/sle-beta/#faq-reg [2]:https://www.postgresql.org/docs/11/release-11.html [3]:https://www.postgresql.org/docs/12/release-12.html [4]:https://www.suse.com/betaprogram/sle-beta/#notable [5]:https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP2 /#_changes_in_15sp2 [6]:https://www.suse.com/betaprogram/sle15sp2-changes-for-scs i-devices/ [7]:https://www.suse.com/betaprogram/sle-beta/ [8]:mailto:beta-programs at lists.suse.com?subject=Unsubscribe%2 0from%20SLE%20Beta&body=Unsubscribe%20from%20SLE%20Beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Thu Mar 12 09:08:59 2020 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 12 Mar 2020 15:08:59 +0000 Subject: [sle-beta] missing sources in 5.3.18-7 kernel-source In-Reply-To: References: Message-ID: <4C12A58D-4D76-4992-873A-AB961FCCE5D9@suse.com> Hi, Sorry for the late response, I thought we were having an issue on our side but could it just be that you didn?t install the package kernel-source for 5.3.18-7? It?s available in the Development Tools Modules both in the media and online channels. Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager > On 5 Mar 2020, at 10:53, Sandur, Suresh wrote: > > Hello, > > I updated SLES15 SP2 from 5.3.18-4-default to 5.3.18-7-default. I also updated kernel-default-devel. After that, all the *[ch] files in /usr/src/linux-5.3.18-7/fs are gone. > > What happened to these files? > > regards, > Suresh > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/sle-beta From suresh.sandur at thalesesecurity.com Thu Mar 12 10:28:12 2020 From: suresh.sandur at thalesesecurity.com (Sandur, Suresh) Date: Thu, 12 Mar 2020 16:28:12 +0000 Subject: [sle-beta] [EXTERNAL] Re: missing sources in 5.3.18-7 kernel-source In-Reply-To: <4C12A58D-4D76-4992-873A-AB961FCCE5D9@suse.com> References: , <4C12A58D-4D76-4992-873A-AB961FCCE5D9@suse.com> Message-ID: Thank you Vincent. I had not enabled the Development Tools Module when registering and hence I was not seeing the updated sources. Now that I did, I can see the new sources. Apologies for the trouble. regards, Suresh ________________________________ From: Vincent Moutoussamy Sent: Thursday, March 12, 2020 8:38 PM To: Sandur, Suresh Cc: sle-beta at lists.suse.com Subject: [EXTERNAL] Re: [sle-beta] missing sources in 5.3.18-7 kernel-source Hi, Sorry for the late response, I thought we were having an issue on our side but could it just be that you didn?t install the package kernel-source for 5.3.18-7? It?s available in the Development Tools Modules both in the media and online channels. Regards, -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager > On 5 Mar 2020, at 10:53, Sandur, Suresh wrote: > > Hello, > > I updated SLES15 SP2 from 5.3.18-4-default to 5.3.18-7-default. I also updated kernel-default-devel. After that, all the *[ch] files in /usr/src/linux-5.3.18-7/fs are gone. > > What happened to these files? > > regards, > Suresh > _______________________________________________ > sle-beta mailing list > sle-beta at lists.suse.com > Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/sle-beta -------------- next part -------------- An HTML attachment was scrubbed... URL: From vmoutoussamy at suse.com Thu Mar 12 10:49:15 2020 From: vmoutoussamy at suse.com (Vincent Moutoussamy) Date: Thu, 12 Mar 2020 16:49:15 +0000 Subject: [sle-beta] [EXTERNAL] missing sources in 5.3.18-7 kernel-source In-Reply-To: References: <4C12A58D-4D76-4992-873A-AB961FCCE5D9@suse.com> Message-ID: <360465B2-504F-4D87-AD62-649878C4BEA9@suse.com> No trouble ; ) Apologies for not responding earlier. Have a nice day! -- Vincent Moutoussamy SUSE Beta Program, JeOS and SDK Project Manager Paris, France > On 12 Mar 2020, at 17:28, Sandur, Suresh wrote: > > Thank you Vincent. I had not enabled the Development Tools Module when registering and hence I was not seeing the updated sources. Now that I did, I can see the new sources. > > Apologies for the trouble. > > regards, > Suresh > > > From: Vincent Moutoussamy > Sent: Thursday, March 12, 2020 8:38 PM > To: Sandur, Suresh > Cc: sle-beta at lists.suse.com > Subject: [EXTERNAL] Re: [sle-beta] missing sources in 5.3.18-7 kernel-source > > Hi, > > Sorry for the late response, I thought we were having an issue on our side but could > it just be that you didn?t install the package kernel-source for 5.3.18-7? > > It?s available in the Development Tools Modules both in the media and online channels. > > Regards, > -- > Vincent Moutoussamy > SUSE Beta Program, JeOS and SDK Project Manager > > > On 5 Mar 2020, at 10:53, Sandur, Suresh wrote: > > > > Hello, > > > > I updated SLES15 SP2 from 5.3.18-4-default to 5.3.18-7-default. I also updated kernel-default-devel. After that, all the *[ch] files in /usr/src/linux-5.3.18-7/fs are gone. > > > > What happened to these files? > > > > regards, > > Suresh > > _______________________________________________ > > sle-beta mailing list > > sle-beta at lists.suse.com > > Check the mailing list archives or Unsubscribe at http://lists.suse.com/mailman/listinfo/sle-beta From mail at marekpasnikowski.name Fri Mar 13 15:28:31 2020 From: mail at marekpasnikowski.name (Marek =?utf-8?B?UGHFm25pa293c2tp?=) Date: Fri, 13 Mar 2020 22:28:31 +0100 Subject: [sle-beta] Pinebook Pro Server Message-ID: <3073595.5fSG56mABF@obikawa17> Greetings I am a new SUSE beta tester and I would like to report my first finding. I believe, that with the current software stack, it should be possible to run a CLI SUSE Server on a Pinebook Pro, which is an ARM, Rockchip based laptop. However, the screen never lights up when booting from the SD card. I wonder, if SUSE could get in touch with the Pine64 company to exchange information about what is required to boot the system? They seem to be very open to collaboration with software providers. Please forgive me, if I am stepping out of line. This is my first interaction on a serious mailing list, and I don't really have the experience to know what are good or bad topics. From afaerber at suse.de Tue Mar 17 02:46:22 2020 From: afaerber at suse.de (=?UTF-8?Q?Andreas_F=c3=a4rber?=) Date: Tue, 17 Mar 2020 09:46:22 +0100 Subject: [sle-beta] Pinebook Pro Server In-Reply-To: <3073595.5fSG56mABF@obikawa17> References: <3073595.5fSG56mABF@obikawa17> Message-ID: <65dbf022-5e90-4811-17d7-de73b6b514f1@suse.de> Hello Marek, Am 13.03.20 um 22:28 schrieb Marek Pa?nikowski: > I am a new SUSE beta tester and I would like to report my first finding. > > I believe, that with the current software stack, it should be possible to run > a CLI SUSE Server on a Pinebook Pro, which is an ARM, Rockchip based laptop. For reference: https://www.pine64.org/pinebook-pro/ > However, the screen never lights up when booting from the SD card. Thank you for taking the time to report this. Unfortunately a black screen can have several different causes: * Bootloader firmware might not be EBBR compliant yet (too old) * System might boot into Linux but lacking drivers for e.g. eDP bridges * Unified Installer initrd might be lacking some display-related module * Drivers might have bugs It would help if you can access a serial console to obtain further information on boot progress. Also please let us know exactly what you're testing - I assume attaching our Unified Installer .iso on USB? Please always mention the milestone/filename to avoid ambiguities. > I wonder, if SUSE could get in touch with the Pine64 company to exchange > information about what is required to boot the system? They seem to be very > open to collaboration with software providers. > > Please forgive me, if I am stepping out of line. This is my first interaction > on a serious mailing list, and I don't really have the experience to know what > are good or bad topics. Thanks for taking the time to beta-test on this non-server system. We do not have access to a Pinebook Pro for testing ourselves. While our Release Notes list the RK3399 as one enabled SoC, that does not guarantee that all available devices will boot or fully work. https://www.suse.com/releasenotes/aarch64/SUSE-SLES/15-SP2/#aarch64 I should probably add a sentence similar to the product page: https://www.suse.com/products/arm/ "Note: Please check with the specific hardware vendor for SUSE YES certification for the Arm processor in your solution. Due to the rapidly evolving availability of Arm System-on-a-Chip hardware, not all platforms have undergone the same degree of hardware testing." Normally IHVs would work with SUSE months in advance of our Beta program to ensure that all necessary driver enablement gets requested. By now we're already headed into the Release Candidate phase, so time is getting short for major changes... @TL: Does the Pinebook Pro contain a SPI flash with recent U-Boot, so that from your perspective our Linux should be able to boot? Or might Marek need to perform a firmware upgrade first? Please compare: https://www.suse.com/media/article/UEFI_on_Top_of_U-Boot.pdf Note that at this time neither SUSE Linux Enterprise Desktop nor SUSE Linux Enterprise Workstation Extension products are available for Arm, i.e. Desktop Productivity Module packages are unavailable for aarch64. However, that does not limit you to CLI - both minimal X11 (IceWM) and GNOME desktops are available for convenient system administration. HMI or Digital Signage are valid use cases for SUSE Linux Enterprise Server in the context of Edge Computing. Arm Mali 3D acceleration has been missing in previous releases and is still under evaluation for 15 SP2. It would need to be described in the bootloader's Flat Device Tree in order to be testable. However, Mali acceleration is independent of 2D graphics output. Could you explain what the context of your test report is: Are you interested in deploying SUSE Linux Enterprise Server for Arm on this device as a partner/customer, or are you an ISV trying to test your software on an Arm based device that you happened to have around? Thanks, Andreas F?rber Project Manager arm64 SUSE Labs -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Felix Imend?rffer HRB 36809 (AG N?rnberg) From beta-programs at lists.suse.com Wed Mar 25 10:26:08 2020 From: beta-programs at lists.suse.com (SUSE Beta Program) Date: Wed, 25 Mar 2020 17:26:08 +0100 Subject: [sle-beta] =?utf-8?q?=5BANNOUNCE=5D_SLE_15_SP2_Public_Beta_?= =?utf-8?b?4oCTIFNuYXBzaG90IFVwZGF0ZXMgKDgscmMxKSE=?= Message-ID: <5e7b862034a6f_5cf62ae05bdde5f81073@zourite.lab.gb.mail> As you might know from our SLE 15 SP2 Public Beta announcement[1], we are now releasing fewer Public Beta ISOs but we are releasing weekly updates, called Snapshot, in our Beta Online Channels! Our Snapshot Updates for SUSE Linux Enterprise 15 Service Pack 2 are available. - SUSE Linux Enterprise Server (SLES), - SUSE Linux Enterprise Server for SAP (SLES for SAP), - SUSE Linux Enterprise Just Enough Operating System span> (JeOS), - SUSE Linux Enterprise High Availability strong> (SLEHA and SLEHA GEO), - SUSE Linux Enterprise Desktop (SLED), - SUSE Linux Enterprise Workstation Extension strong> (SLEWE), - SUSE Linux Enterprise for High Performance Computing (SLEHPC). ? Schedule changes Due to recent inclusion of important fixes (kernel, PostgreSQL, MariaDB, etc) we had to adapt our schedule. These schedule changes give us time to perform additional testing to ensure the best quality of the release. In short, the Public RC release initially scheduled for April 3th is replaced by a regular snapshot update, Public RC is then postponed to April 24th which was initially the Public GMC release date. Last but not least, the dates for Gold Master Candidate and Gold Master are under revision and we will give you an update about these dates as soon as possible, too. Please find below the new date : - Public Release Candidate ? April 24, 2020 - Public Gold Master Candidate ? TBD ? Download and Apply Updates Please note that to be able to test the changes announced here, you need to register your system with a Beta Registration Code! To request Beta Registration Code, you need to follow this[2]. We will then send you your codes along with a complete FAQ, on how to proceed. Notable Changes ? As a side note, did you know that kernel fixes submitted to SLE 15 SP2 are reflected in openSUSE Kernel Of The Day (KOTD)? for more information please check https://en.opensuse.org/openSUSE:Kernel_of_the_day[3] or contact us. Others - PostgreSQL 12[4], - MariaDB 10.4,[5] - Media Changes[5], - SCSI Devices[6], - Tech Preview: Maven in version 3.6.3 has been added to SLES 15 SP2 as a Tech Preview, Added Packages (selection) - cmake-full 3.16.2-1.6 - python-xattr: 0.9.7-1.1 - yubikey-manager-qt: 1.1.1-1.12 Updated Packages (selection) - a-certificates-mozilla: 2.40-4.18.8 - checkpolicy: 3.0-1.1 - cmake: 3.16.2-1.4 - drbd-utils: 9.12.0-1.3 - ipmctl: 02.00.00.3733-1.3 - kernel: 5.3.18-10.1 - libselinux: 3.0-1.5 - lsb-release: 3.1-1.3 - mariadb: 10.4.12-2.4 - MozillaFirefox: 68.6.0-3.75.1 - openssh 8.1p1-3.6 - openssl-1_1 1.1.1d-7.4 - open-vm-tools: 11.0.5-1.3 - osc: 0.167.2-3.12.1 - perl-DBD-Pg: 3.10.4-1.3 - php7: 7.3.15-1.7 - policycoreutils: 3.0-1.1 - powerpc-utils: 1.3.7.1-3.12.1 - restorecond: 3.0-1.1 - s390-tools: 2.11.0-5.6 - suse-build-key: 12.0-8.6.1 - wicked: 0.6.63-1.5 - wireshark: 3.2.2-3.35.2 - yast2 stack More information SLE Beta Page ?[7] If you have _ANY_ concerns, doubts, inquiry, etc please contact beta-programs at lists.suse.com. Your SUSE Linux Enterprise Team Do not hesitate to contact us at beta-programs at lists.suse.com if you have any questions. Click here to unsubscribe.[8] [1]:https://www.suse.com/c/suse-linux-enterprise-15-service-% 20%20%20pack-2-public-beta/ [2]:https://www.suse.com/%20%20%20%20%20%20%20%20%20%20%20bet aprogram/sle-beta/#faq-reg [3]:https://en.opensuse.org/openSUSE:%20Kernel_of_the_day [4]:https://www.suse.com/betaprogram/sle-beta/#notable [5]:https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP2 /%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 %20%20%20%20#_changes_in_15sp2 [6]:https://www.suse.com/betaprogram/sle15sp2-changes-for-scs i-devices/ [7]:https://www.suse.com/betaprogram/sle-beta [8]:mailto:beta-programs at lists.suse.com?subject=Unsubscribe%2 0from%20SLE%20Beta&body=Unsubscribe%20from%20SLE%20Beta -------------- next part -------------- An HTML attachment was scrubbed... URL: