March 2020 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Problem with booting a migrated machine.
by Carlos E. R. 21 Mar '20

21 Mar '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm migrating an old computer to a new computer. First thing I did, was install openSUSE 15.1 on the new computer. Partition called "Auxiliary". Boots fine. Then, using this system, I cloned the old machine to the new machine. Well, only two partitions, "/" and "/boot" (not the others). Old machine (traditional BIOS, with GPT partitions): SSD disk. Two partitions to cope with, for the moment (*): /boot / sde sde 512 0 0 232.9G disk ├─sde1 sde1 512 0 0 24G part swap ssd-swap ssd-swap [SWAP] 4feaa6f5-38c4-4674-ae54-8e22389731a1 ├─sde2 sde2 512 0 0 15M part primary ├─sde3 sde3 512 0 0 15G part ext4 ssd-test primary / 32392d31-6b40-4f90-badd-9153370daba7 ├─sde4 * sde4 512 0 0 1G part ext2 ssd-boot primary /other/main/boot a977c5c3-259f-4df6-80e4-9f21a1ae96f5 └─sde5 * sde5 512 0 0 150G part ext4 ssd-main primary /other/main ac173013-18ad-4c4e-921e-fd2ecfb56495 New machine (UEFI): nvme disk. nvme0n1 nvme0n1 465,8G disk 0 0 ├─nvme0n1p1 nvme0n1p1 500M part 0 0 EFI EFI /boot/efi 1726-BDB2 ├─nvme0n1p2 nvme0n1p2 100G part 0 0 Swap Swap [SWAP] 7f9467db-113f-4ca5-867c-85113ce94da9 ├─nvme0n1p3 nvme0n1p3 30G part 0 0 Auxiliary Auxiliary / f0b68654-4d7f-4ff8-b68c-117e85bb5e7f ├─nvme0n1p4 nvme0n1p4 1G part 0 0 ssd-boot /other/main/boot a977c5c3-259f-4df6-80e4-9f21a1ae96f5 └─nvme0n1p5 nvme0n1p5 150G part 0 0 ssd-main /other/main ac173013-18ad-4c4e-921e-fd2ecfb56495 Partitions 4 and 5 of the old machine were cloned to the new machine, thus same uuid. I used this command: time dd bs=16M if=/dev/sde4 status=progress | ssh root(a)192.168.1.134 "dd bs=16M of=/dev/nvme0n1p4" time dd bs=16M if=/dev/sde5 status=progress | ssh root(a)192.168.1.134 "dd bs=16M of=/dev/nvme0n1p5" No errors. Now, the problem is getting that migrated system to boot, or for the moment, to at least start booting (it will not finish the booting, because it lacks the /home and data partitions, but those will be done later). I used mount bind sys, proc, dev and chrooted procedure to run yast in text mode and reinstall the boot loader in the cloned system. I then changed it to grub efi mode. It installed mokutil-0.3.0-lp151.5.1.x86_64.rpm. On the "auxiliary" system I used yast boot manager to probe for other systems. When booting, it does detect the cloned system but fails to boot it. The current error is (hand copied): error: file boot/vmlinuz-4-12-14-lp151...default` not found error: you need to load the kernel first. press any key to continue (but of course the file does exist, it must be looking at the wrong partition or something) I have this info: Andor:~ # efibootmgr -v BootCurrent: 0000 Timeout: 1 seconds BootOrder: 0000,0003,0001 Boot0000* opensuse-secureboot HD(1,GPT,800b649f-a2e3-4dad-b2bf-b7ecc5ef11d8,0x800,0xfa000)/File(\EFI\OPENSUSE\SHIM.EFI) Boot0001* auxiliary-secureboot HD(1,GPT,800b649f-a2e3-4dad-b2bf-b7ecc5ef11d8,0x800,0xfa000)/File(\EFI\AUXILIARY\SHIM.EFI) Boot0003* opensuse HD(1,GPT,800b649f-a2e3-4dad-b2bf-b7ecc5ef11d8,0x800,0xfa000)/File(\EFI\OPENSUSE\GRUBX64.EFI)..BO Andor:~ Booting directly from the UEFI menu fails. Press F11 when booting, then I get first a prompt to the UEFI password, then the menu. I select "opensuse-secureboot", it flashes something, and then goes to the grub menu of "Auxiliary" instead, so fast I can not see an error message. I also tried another method, that works on my BIOS+GPT machines (but not here). I create a "/boot/grub2/custom.cfg", with these two entries: menuentry '--> Auxiliary (por uuid)' --id cer-aux-001 { insmod part_gpt insmod ext2 set root='hd0,gpt2' if search --no-floppy --fs-uuid --set=root f0b68654-4d7f-4ff8-b68c-117e85bb5e7f ; then echo Going in sleep 3 chainloader +1 echo going out sleep 3 else echo Could not find this OS instance, will not boot (1) sleep 1 fi } menuentry '--> ssd-main (ssd-boot por uuid)' --id cer-nvme-002 { insmod part_gpt insmod ext4 set root='hd0,gpt3' if search --no-floppy --fs-uuid --set=root a977c5c3-259f-4df6-80e4-9f21a1ae96f5 ; then chainloader +1 else echo Could not find this OS instance, will not boot (2) sleep 1 fi } The entries do run but fail. I get "invalid EFI file path" just when "chainload" would be executed. Thus I gather that it doesn't work that way with UEFI. The entry created by os-prober in grub.cfg is this one (and it failed with this error: error: file boot/vmlinuz-4-12-14-lp151...default` not found error: you need to load the kernel first. press any key to continue ): ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'openSUSE Leap 15.1 (on /dev/nvme0n1p5)' --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-ac173013-18ad-4c4e-921e-fd2ecfb56495' { insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root ac173013-18ad-4c4e-921e-fd2ecfb56495 else search --no-floppy --fs-uuid --set=root ac173013-18ad-4c4e-921e-fd2ecfb56495 fi linuxefi /boot/vmlinuz-4.12.14-lp151.28.36-default root=/dev/nvme0n1p5 initrdefi /boot/initrd-4.12.14-lp151.28.36-default } I don't know where this is wrong. The uuid for root is correct, but there is a separate boot partition. On the original (Bios) system, the entry was: menuentry 'Main_openSUSE' --class main_opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-ac173013-18ad-4c4e-921e-fd2ecfb56495' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod ext2 set root='hd0,gpt4' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd4,gpt4 --hint-efi=hd4,gpt4 --hint-baremetal=ahci4,gpt4 --hint='hd0,gpt4' a977c5c3-259f-4df6-80e4-9f21a1ae96f5 else search --no-floppy --fs-uuid --set=root a977c5c3-259f-4df6-80e4-9f21a1ae96f5 fi echo 'Loading Linux 4.12.14-lp151.28.40-default ...' linux /vmlinuz-4.12.14-lp151.28.40-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 resume=/dev/disk/by-label/ssd-swap splash=verbose echo 'Loading initial ramdisk ...' initrd /initrd-4.12.14-lp151.28.40-default } Notice that the ancient version does: --set=root a977c5c3-259f-4df6-80e4-9f21a1ae96f5 (which is the /boot partition) while the new probed version does --set=root ac173013-18ad-4c4e-921e-fd2ecfb56495 (which is the root partition. This must be wrong). That must be the error (bug?) of os-prober. I'll add a manual entry in custom.cfg: menuentry '==> nvme-MAIN' --id cer-probe { insmod part_gpt insmod ext2 if search --no-floppy --fs-uuid --set=root a977c5c3-259f-4df6-80e4-9f21a1ae96f5 ; then linuxefi /boot/vmlinuz-4.12.14-lp151.28.36-default root=UUID=f0b68654-4d7f-4ff8-b68c-117e85bb5e7f splash=verbose resume=/dev/disk/by-label/Swap mitigations=auto initrdefi /boot/initrd-4.12.14-lp151.28.36-default else echo Could not find this OS instance, will not boot (3) sleep 1 fi } Yes, this entry does boot. Well, it starts to, till it finds (not) the missing disks, as expected. Progress! It remains to find why chainload does not work, and why directly from UEFI menu doesn't work either. I suspect YaST failed to enter the correct entry. Andor:/boot/grub2 # efibootmgr BootCurrent: 0000 Timeout: 1 seconds BootOrder: 0000,0003,0001,0004,0005 Boot0000* opensuse-secureboot <--- The correct name is "Main_openSUSE" Boot0001* auxiliary-secureboot Boot0003* opensuse Boot0004* UEFI: VerbatimSTORE N GO Boot0005* UEFI: VerbatimSTORE N GO, Partition 2 Andor:/boot/grub2 # - -- Cheers Carlos E. R. (from 15.1 x86_64 at Legolas) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXnWGYRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVNooAnirM4WvkCQ2ZbNXH2Mj+ LMf38PaEAJ98jJLsTbyxb5KEuz8tkq960oHt9Q== =p6bp -----END PGP SIGNATURE-----

1 0

Re: [opensuse] steam -> lost ember
by Simon Becherer 20 Mar '20

20 Mar '20

Am 20.03.20 um 19:17 schrieb Mike Henry: > Yes, either steam will do it automatically or you will need to check > the box. Steam will also give you a refund if you have less than 2 > hours of playtime so you can test it risk free. > Thanks mike, and sorry, i have hit the wrong reply button..... -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] steam -> lost ember
by Simon Becherer 20 Mar '20

20 Mar '20

Hi, is anybody here running "lost ember" on tumbleweed? my son like to play it and i have never installed steam before so before i try and buy, would be nice if somebody could confirm that it is running. https://software.opensuse.org/package/steam searching the net i found only that steam could be installed, but i still did not know if "lost ember" will run. simoN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Display resolution
by John Perry 19 Mar '20

19 Mar '20

After a couple of years in Windows only, I finally tried Hyper-V to get linux back (VirtualBox wouldn't give me a clean opensuse with guest additions, etc.). Hyper-V built me a really nice VM except that suse will only come up in an 1152X864 screen. I managed to fix this in VBox, but I can't find the setting to reconfigure the display to 1924X1080. All the display settings restrict me to the default so I get a box in the middle of my screen. Where's the display resolution setting? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 9

[opensuse] New 15.1 install on new computer: recover from hibernation fails silently.
by Carlos E. R. 19 Mar '20

19 Mar '20

Hi, I tried to hibernate my new machine, and it failed. On recovery, it simply did a full boot. The text goes so fast that I can not read anything (m2 ssd). hwinfo: <https://susepaste.org/72687508> verbose hwinfo: <https://susepaste.org/67176305> Log excerpt: 2020-03-17T04:49:30.045232+01:00 linux-pto8 xfce4-session[3120]: IA__gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed 2020-03-17T04:49:38.421691+01:00 linux-pto8 systemd[1]: Reached target Sleep. 2020-03-17T04:49:38.422283+01:00 linux-pto8 systemd[1]: Starting Hibernate... 2020-03-17T04:49:38.426894+01:00 linux-pto8 systemd-sleep[5108]: INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate 2020-03-17T04:49:38.427001+01:00 linux-pto8 systemd-sleep[5108]: INFO: Running prepare-grub .. 2020-03-17T04:49:38.427705+01:00 linux-pto8 kernel: [ 5399.930782] PM: Hibernation mode set to 'platform' 2020-03-17T04:49:38.492859+01:00 linux-pto8 systemd-sleep[5108]: running kernel is grub menu entry openSUSE Leap 15.1 (vmlinuz-4.12.14-lp151.28.40-default) 2020-03-17T04:49:38.493007+01:00 linux-pto8 systemd-sleep[5108]: preparing boot-loader: selecting entry openSUSE Leap 15.1, kernel /boot/4.12.14-lp151.28.40-default 2020-03-17T04:49:38.498483+01:00 linux-pto8 systemd-sleep[5108]: running /usr/sbin/grub2-once "openSUSE Leap 15.1" 2020-03-17T04:49:38.558637+01:00 linux-pto8 systemd-sleep[5108]: time needed for sync: 0.0 seconds, time needed for grub: 0.0 seconds. 2020-03-17T04:49:38.558733+01:00 linux-pto8 systemd-sleep[5108]: INFO: Done. 2020-03-17T04:49:38.558845+01:00 linux-pto8 systemd-sleep[5108]: Suspending system... 2020-03-17T10:56:31.083131+01:00 linux-pto8 systemd[1]: systemd 234 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hybrid) 2020-03-17T10:56:31.083169+01:00 linux-pto8 systemd[1]: Detected architecture x86-64. 2020-03-17T10:56:31.083172+01:00 linux-pto8 systemd[1]: Set hostname to <linux-pto8>. 2020-03-17T10:56:31.083173+01:00 linux-pto8 systemd-tmpfiles[466]: [/usr/lib/tmpfiles.d/net-snmp.conf:1] Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordingly. 2020-03-17T10:56:31.083177+01:00 linux-pto8 apparmor.systemd[465]: Restarting AppArmor 2020-03-17T10:56:31.083178+01:00 linux-pto8 apparmor.systemd[465]: Reloading AppArmor profiles 2020-03-17T10:56:31.083180+01:00 linux-pto8 systemd-tmpfiles[466]: [/usr/lib/tmpfiles.d/samba.conf:1] Line references path below legacy directory /var/run/, updating /var/run/samba → /run/samba; please update the tmpfiles.d/ drop-in file accordingly. 2020-03-17T10:56:31.083183+01:00 linux-pto8 systemd-tmpfiles[466]: [/usr/lib/tmpfiles.d/vpnc.conf:1] Line references path below legacy directory /var/run/, updating /var/run/vpnc → /run/vpnc; please update the tmpfiles.d/ drop-in file accordingly. 2020-03-17T10:56:31.083185+01:00 linux-pto8 systemd[1]: Started Load/Save Random Seed. 2020-03-17T10:56:31.083187+01:00 linux-pto8 systemd[1]: Started Create Static Device Nodes in /dev. 2020-03-17T10:56:31.083189+01:00 linux-pto8 systemd[1]: Started Apply Kernel Variables. 2020-03-17T10:56:31.083189+01:00 linux-pto8 kernel: [ 0.000000] Linux version 4.12.14-lp151.28.40-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux) ) #1 SMP Fri Mar 6 13:48:15 UTC 2020 (f0f1262) The obvious is correct. The kernel boot line has a resume entry: linux-pto8:~ # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp151.28.40-default root=UUID=f0b68654-4d7f-4ff8-b68c-117e85bb5e7f splash=verbose resume=/dev/disk/by-label/Swap mitigations=auto linux-pto8:~ # linux-pto8:~ # l /dev/disk/by-label/Swap lrwxrwxrwx 1 root root 15 Mar 17 10:56 /dev/disk/by-label/Swap -> ../../nvme0n1p2 linux-pto8:~ # l /dev/nvme0n1p2 brw-rw---- 1 root disk 259, 2 Mar 17 10:56 /dev/nvme0n1p2 linux-pto8:~ # file -s /dev/nvme0n1p2 /dev/nvme0n1p2: Linux/i386 swap file (new style), version 1 (4K pages), size 26214399 pages, LABEL=Swap, UUID=7f9467db-113f-4ca5-867c-85113ce94da9 linux-pto8:~ # Swap is enabled: linux-pto8:~ # swapon --show NAME TYPE SIZE USED PRIO /dev/nvme0n1p2 partition 100G 0B -1 linux-pto8:~ # What else can I look at? Hibernation has not failed for me for some years now, but this is a new machine. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

1 1

Re: [opensuse] New 15.1 install on new computer does not boot.
by Carlos E. R. 17 Mar '20

17 Mar '20

On 17/03/2020 02.03, Felix Miata wrote: > Carlos E. R. composed on 2020-03-17 01:50 (UTC+0100): > >> I'm going to redo the install without encryption. A pain to redo after all the detailed package selection... > > I would have chrooted into the installed system and tried yast2 bootloader first. > I can do that, I have still not done what I intended. It is encrypted, though. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

4 9

[opensuse] quick hardware question
by Carlos E. R. 17 Mar '20

17 Mar '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm assembling a replacement machine, to use with Linux, of course (AMD hardware). I have a problem with the fans. The box (Antec P101 Silent) comes with 3 fans front and 1 rear, all connected to a single switch for fast/normal/slow speed. However, the board has sockets for 1 "pump fan" and 3 "sys fan". All of them are 4 pin. However, the fan cables in the box have all 3 pin plugs. (I did not buy the fans myself, they came with the box) How can I connect those 3 wire fans to the 4 pin sockets? I assume it is possible. If you know a web page that explains, just share the link. Or if you know a google term that produces the results, just share the term, I'm thick today. If you think this is off topic, just reply on the offtopic mail list, or directly (off list). Thank you :-) - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXm2gjhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV7FYAn3ID5E00dwLrbYjSmO3I 8Ur2H03SAJ4y+xNHh8Wp1lHNr1O8bOvdYuKtdQ== =1t65 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 8

[opensuse] TW : todays zypper dup : multikernels
by ellanios82 17 Mar '20

17 Mar '20

just an observation : - i used to have 4 kernel versions - after today's zypper dup , i have 2 kernel versions [ cannot see anything changed in /etc/zypp/zypp.conf ] .... rgds -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 6

[opensuse] New 15.1 install on new computer does not boot.
by Carlos E. R. 17 Mar '20

17 Mar '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.21.2003162330320.6948(a)Telcontar.valinor> Hi, As here we are confined to our homes I had the time to finish the building of my new computer. AMD hardware. I installed 15.1 to it, but it does not boot. No messages at all, the machine takes some time and then goes directly to UEFI setup screen. Apparently grub does not load, I do not see any messages from it. I have booted 15.1 rescue system (XFCE Live) on USB, and there I can run tests. This is the disk layout: NAME KNAME SIZE TYPE RM HOTPLUG LABEL PARTLABEL MOUNTPOINT UUID PARTUUID WWN MODEL PTUUID ALIGNMENT loop0 loop0 540.8M loop 0 0 /run/initramfs/squashfs_container 0 loop1 loop1 3G loop 0 0 /run/rootfsbase 9f5ab536-edf3-4359-931f-3fb8f223d864 0 sda sda 7.5G disk 1 1 openSUSE_Leap_15.1_Rescue_CD 2020-02-11-20-30-27-00 STORE N GO 0 ├─sda1 sda1 633.3M part 1 1 openSUSE_Leap_15.1_Rescue_CD /run/initramfs/live 2020-02-11-20-30-27-00 0 ├─sda2 sda2 15M part 1 1 BOOT A496-B571 0 └─sda3 sda3 6.9G part 1 1 cow /run/overlayfs 41fa859c-ff55-458f-8319-bf17faba49b6 0 nvme0n1 nvme0n1 465.8G disk 0 0 Samsung SSD 970 EVO Plus 500GB 40891e95-9e7d-4326-a9a0-13f86d9cfa26 0 ├─nvme0n1p1 nvme0n1p1 500M part 0 0 BE1E-E116 800b649f-a2e3-4dad-b2bf-b7ecc5ef11d8 0 ├─nvme0n1p2 nvme0n1p2 100G part 0 0 dac90564-26b2-480b-8bb9-5f535685053e 3d186ef5-2041-4a47-9576-9ae9a49d5097 0 └─nvme0n1p3 nvme0n1p3 30G part 0 0 c5e019f8-0929-4116-8c1f-a0c1fcdcccf8 51be098c-35bc-44fa-8899-e78adfacf300 0 The "disk" is an M2 SSD thing. P1 is the EFI, p2 is swap (yes, it is 100GB, intentionally so), and p3 is the system. ext4. The contents of the EFI partition are: test/ └── EFI ├── boot │ ├── bootx64.efi │ └── fallback.efi └── opensuse ├── MokManager.efi ├── boot.csv ├── grub.cfg ├── grub.efi ├── grubx64.efi └── shim.efi 3 directories, 8 files Now, during the install I saw the option to encrypt the root filesystem, and I did that. Maybe that option does not work, needs separate unencrypted /boot. I do not know. Or maybe Grub should know how to decipher it. Maybe not. But I should see some message from grub, right? I also run bootinfoscript. The result file is attached, it should have all the information. Of course, anything related to /dev/sda you can ignore, that's the rescue system on USB stick. So I'm about to retry without encryption, but if you have other ideas I can try them. (I'm not that keen on an encrypted system, it was just a try) About the hardware... hwinfo file is 1.5 megabytes, too much for an email here. I can try to upload to susepaste, but the command "susepaste" in the rescue system hangs. Ah, it exited with "failed". Ah, yet it succeeded, I found it: <https://susepaste.org/67176305> It is the debug output, it does that as soon as I pipe to a file. Ah, got a short version. This one: <https://susepaste.org/72687508> - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXnAGVhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVjtwAn0FRWg6Poj+mEpi+k80l Dpq9y6XZAJ9b5g7Yx03AkmlN+F0R+rOLLMgM1Q== =G8qp -----END PGP SIGNATURE-----

3 4

[opensuse] How to change the console resolution / yast2 bootloader is broken? / how to remove the bouncing button that belongs in an episode of The Prisoner.
by Richmond 16 Mar '20

16 Mar '20

The console resolution is too small to see, so I changed it in grub2 bootloader. But this only worked for the grub2 menu, as soon as the bouncing button appeared, the resolution on the console changed back to tiny (verify by pressing escape). So, I tried different resolutions, then removed the check for graphic console but all to no avail. Then I removed the "quiet" kernet command line parameter and added "nosplash" but no avail. Then I removed the "themes" directory from /boot/grub2 but no avail. The virtual console resolution is always tiny, and the bouncing button won't go away, it is following me everywhere now, even when I go for a walk. Help! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3