Re: [gentoo-user] getnoo system freeze at boot on - mounting misc binary format filesystem

2021-01-24 Thread thelma
On 1/24/21 4:11 PM, the...@sys-concept.com wrote:
> New installation.
> When I boot system freeze after:
> mounting misc binary format filesystem   . [OK]
> 
> I run fsck.ext4 on all partitions.  I can login to the system via ssh 
> 
> dmesg doesn't show any errors:
> 
> [2.361518] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
> UNIX platforms  455.45.01  Thu Nov  5 22:55:44 UTC 2020
> [2.364037] [drm] [nvidia-drm] [GPU ID 0x0800] Loading driver
> [2.364038] [drm] Initialized nvidia-drm 0.0.0 20160202 for :08:00.0 
> on minor 0
> [2.455612] nvidia-smi (787) used greatest stack depth: 12592 bytes left
> [2.546763] EXT4-fs (nvme0n1p4): re-mounted. Opts: (null)
> [2.583028] Adding 524284k swap on /dev/nvme0n1p3.  Priority:-2 extents:1 
> across:524284k SS
> [2.605406] EXT4-fs (nvme0n1p5): mounted filesystem with ordered data 
> mode. Opts: (null)
> [2.672221] elogind-daemon[1307]: New seat seat0.
> [2.672613] elogind-daemon[1307]: Watching system buttons on 
> /dev/input/event1 (Power Button)
> [2.672639] elogind-daemon[1307]: Watching system buttons on 
> /dev/input/event0 (Power Button)
> [2.728216] ip (1443) used greatest stack depth: 12320 bytes left
> [2.735102] elogind-daemon[1307]: Watching system buttons on 
> /dev/input/event13 (Logitech USB Keyboard)
> [2.735154] elogind-daemon[1307]: Watching system buttons on 
> /dev/input/event14 (Logitech USB Keyboard)
> [2.931612] ip (1734) used greatest stack depth: 12264 bytes left
> [5.916664] igb :04:00.0 enp4s0: igb: enp4s0 NIC Link is Up 1000 Mbps 
> Full Duplex, Flow Control: RX/TX
> [6.018743] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
> [   13.654042] random: crng init done
> [   13.654044] random: 7 urandom warning(s) missed due to ratelimiting
> [   37.712659] elogind-daemon[1307]: New session 1 of user root.


It has something to do with EFI.  
I did not configure the system to use EFI with grub.  When the system boots the 
fonts on the screen are large.  It display on the screen everything up the 
point:
...
mounting misc binary format filesystem   . [OK]

at this point the fonts are changed and the screen is not not displaying 
anything it looks like it is frozen and the is no "login" prompt.
When I enable XDM the boot login shows up and I can long-in via "slim" login 
manager.

In make.conf:
...
INPUT_DEVICES="evdev"
VIDEO_CARDS="nvidia"
 
Does it have something to do with "x11-base/xorg-server"  or "nvidia" driver?
How to configure the system so it will display/switch the fonts during boot on 
the screen?



[gentoo-user] getnoo system freeze at boot on - mounting misc binary format filesystem

2021-01-24 Thread thelma
New installation.
When I boot system freeze after:
mounting misc binary format filesystem   . [OK]

I run fsck.ext4 on all partitions.  I can login to the system via ssh 

dmesg doesn't show any errors:

[2.361518] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  455.45.01  Thu Nov  5 22:55:44 UTC 2020
[2.364037] [drm] [nvidia-drm] [GPU ID 0x0800] Loading driver
[2.364038] [drm] Initialized nvidia-drm 0.0.0 20160202 for :08:00.0 on 
minor 0
[2.455612] nvidia-smi (787) used greatest stack depth: 12592 bytes left
[2.546763] EXT4-fs (nvme0n1p4): re-mounted. Opts: (null)
[2.583028] Adding 524284k swap on /dev/nvme0n1p3.  Priority:-2 extents:1 
across:524284k SS
[2.605406] EXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. 
Opts: (null)
[2.672221] elogind-daemon[1307]: New seat seat0.
[2.672613] elogind-daemon[1307]: Watching system buttons on 
/dev/input/event1 (Power Button)
[2.672639] elogind-daemon[1307]: Watching system buttons on 
/dev/input/event0 (Power Button)
[2.728216] ip (1443) used greatest stack depth: 12320 bytes left
[2.735102] elogind-daemon[1307]: Watching system buttons on 
/dev/input/event13 (Logitech USB Keyboard)
[2.735154] elogind-daemon[1307]: Watching system buttons on 
/dev/input/event14 (Logitech USB Keyboard)
[2.931612] ip (1734) used greatest stack depth: 12264 bytes left
[5.916664] igb :04:00.0 enp4s0: igb: enp4s0 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX/TX
[6.018743] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
[   13.654042] random: crng init done
[   13.654044] random: 7 urandom warning(s) missed due to ratelimiting
[   37.712659] elogind-daemon[1307]: New session 1 of user root.




Re: [gentoo-user] BIOS can not find boot partition

2021-01-24 Thread thelma
On 1/24/21 5:03 AM, Michael wrote:
> On Sunday, 24 January 2021 05:49:28 GMT the...@sys-concept.com wrote:
>> I'm missing something as system can not find boot device
>>
>> fdisk /dev/nvme0n1
>> Disklabel type: gpt
>>
>> Device StartEndSectors   Size Type
>> /dev/nvme0n1p1  2048   6143   4096 2M BIOS boot
>> /dev/nvme0n1p2  6144 268287 262144   128M EFI System
>> /dev/nvme0n1p326828813168631048576   512M Linux swap
>> /dev/nvme0n1p4   1316864  315889663  314572800   150G Linux filesystem
>>
>> I don't want to use EFI.
> 
> If you do NOT want to use EFI why have you set up /dev/nvme0n1p2 as an ESP 
> type partition?
> 
> With just 4 partitions in total there's also the question of your choice to 
> use GPT instead of the legacy MBR partition table.  :-/

I have 5-partitions, all together, and use 
fdisk  -t gpt  /dev//dev/nvme0n1
 
> 
>> /boot = dev/nvme0n1p2  (ext4) file system
>>
>> When I run:
>> grub-install /dev/nvme0n1p2
>> Installing for x86_64-efi platform.
>> grub-install: error: cannot find EFI directory.
> 
> First, the handbook clearly directs to install GRUB to a disk not a partition:
> 
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader
> 
> However, you *can* install GRUB's boot code in a partition instead of a disk, 
> if you wish to chainload the partition's GRUB from another boot loader, e.g. 
> MSWindows, rEFInd, another GRUB, etc.  I don't see you want to do this, from 
> what you have shared.

You are correct here, this was my mistake, it should be (it was late at night 
didn't notice it) :
grub-install /dev/nvme0n1   (now it works)

not:
grub-install /dev/nvme0n1p2

> Second, I think the error you get is caused because you have created ESP type 
> partition, but there is no EFI/ directory in it, which the UEFI boot protocol 
> requires.
> 
> 
>> but there is /boot/grub
> 
> Yes, the error you got does not complain about /boot/grub missing, but about 
> the absence of an "... EFI directory".
> 
> 
>> Running: grub-mkconfig -o /boot/grub/grub.cfg  is OK (no errors)
>>
>> fstab:
>> /dev/nvme0n1p2   /boot   ext4
> noauto,noatime1 2
>>
>> The BIOS has CSM compatibly mode enable.
>> When I try to boot, system can not find bootable partition.
>>
>> Am I suppose to put any file system on /dev/nvme0n1p1 (2Mb partition) the
>> installation manual did not mention anything.
> 
> No filesystem formatting is required for the small /dev/nvme0n1p1 BIOS boot 
> partition - GRUB will install its 2nd stage core image in there.
> 
> I'd question if your boot partition should be set as ESP type in the first 
> place.  Set it as a Linux partition, reformat it with ext2, or if you want as 
> ext4, mount it as /boot and then install GRUB on the disk as the handbook 
> instructs.

Yah, I change this partition to "Linux filesystem" 
/dev/nvme0n1p2  6144 268287 262144   128M Linux filesystem

Without reinstalling anything, it works (it was ext4).



Re: [gentoo-user] BIOS can not find boot partition

2021-01-24 Thread Andrea Conti

Hello,


I don't want to use EFI.


Then you probably should not be attempting to boot off an NVMe drive, as that 
is only possible if the drive has an onboard BIOS-mode boot ROM; AFAIK those 
are only found on some of the earliest NVMe drives.

Moreover...


grub-install /dev/nvme0n1p2
Installing for x86_64-efi platform.


You are installing GRUB in EFI mode. My guess is that it's because you're 
running the command from a system that was booted in EFI mode, so grub-install 
picks EFI by default.
For BIOS you want the 'i386-pc' platform, and you _must_ install GRUB to the 
block device itself (/dev/nvme0n1)

And once again, whether or not you'll be able to boot from that is very much 
open to debate.


Am I suppose to put any file system on /dev/nvme0n1p1 (2Mb partition) the 
installation manual did not mention anything.


That partition is only there to reserve space for the initial stages of GRUB 
when BIOS-booting from a GPT disk. It does not need to be formatted or mounted, 
and as long as it has the proper flags grub-install should be able to pick it 
up on its own.

andrea




Re: [gentoo-user] BIOS can not find boot partition

2021-01-24 Thread Michael
On Sunday, 24 January 2021 05:49:28 GMT the...@sys-concept.com wrote:
> I'm missing something as system can not find boot device
> 
> fdisk /dev/nvme0n1
> Disklabel type: gpt
> 
> Device StartEndSectors   Size Type
> /dev/nvme0n1p1  2048   6143   4096 2M BIOS boot
> /dev/nvme0n1p2  6144 268287 262144   128M EFI System
> /dev/nvme0n1p326828813168631048576   512M Linux swap
> /dev/nvme0n1p4   1316864  315889663  314572800   150G Linux filesystem
> 
> I don't want to use EFI.

If you do NOT want to use EFI why have you set up /dev/nvme0n1p2 as an ESP 
type partition?

With just 4 partitions in total there's also the question of your choice to 
use GPT instead of the legacy MBR partition table.  :-/


> /boot = dev/nvme0n1p2  (ext4) file system
> 
> When I run:
> grub-install /dev/nvme0n1p2
> Installing for x86_64-efi platform.
> grub-install: error: cannot find EFI directory.

First, the handbook clearly directs to install GRUB to a disk not a partition:

https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader

However, you *can* install GRUB's boot code in a partition instead of a disk, 
if you wish to chainload the partition's GRUB from another boot loader, e.g. 
MSWindows, rEFInd, another GRUB, etc.  I don't see you want to do this, from 
what you have shared.

Second, I think the error you get is caused because you have created ESP type 
partition, but there is no EFI/ directory in it, which the UEFI boot protocol 
requires.


> but there is /boot/grub

Yes, the error you got does not complain about /boot/grub missing, but about 
the absence of an "... EFI directory".


> Running: grub-mkconfig -o /boot/grub/grub.cfg  is OK (no errors)
> 
> fstab:
> /dev/nvme0n1p2/boot   ext4
noauto,noatime  1 2
> 
> The BIOS has CSM compatibly mode enable.
> When I try to boot, system can not find bootable partition.
> 
> Am I suppose to put any file system on /dev/nvme0n1p1 (2Mb partition) the
> installation manual did not mention anything.

No filesystem formatting is required for the small /dev/nvme0n1p1 BIOS boot 
partition - GRUB will install its 2nd stage core image in there.

I'd question if your boot partition should be set as ESP type in the first 
place.  Set it as a Linux partition, reformat it with ext2, or if you want as 
ext4, mount it as /boot and then install GRUB on the disk as the handbook 
instructs.

signature.asc
Description: This is a digitally signed message part.


[gentoo-user] Re: pycharm-community crashed on the first start

2021-01-24 Thread gevisz
ср, 23 дек. 2020 г. в 22:33, gevisz :
>
> I have just installed pycharm-community 2020.1.3 (marked stable) with
> its default settings (that is with +bundled-jdk use flag) on my newly
> installed Gentoo system and tried to start it using the following
> command:
> /opt/pycharm-community/bin/pycharm.sh
>
> Unfortunately, pycharm crashed on the start reporting the following error:
>
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x, pid=26676, tid=26725
> #
> # JRE version: OpenJDK Runtime Environment (11.0.7+10) (build 
> 11.0.7+10-b765.64)
> # Java VM: OpenJDK 64-Bit Server VM (11.0.7+10-b765.64, mixed mode,
> tiered, compressed oops, concurrent mark sweep gc, linux-amd64)
> # Problematic frame:
> # C  0x
> #
> # Core dump will be written. Default location: /home/gevis/core
> #
> # If you would like to submit a bug report, please visit:
> #   http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
>
> A longer error report from /home/gevis/java_error_in_PYCHARM_26676.log
> tells me nothing meaningful. :(
>
> I have no other Java JDK installed on my system.
>
> Is it a known problem? Shall I try to install pycharm with
> -bundled-jdk use flag?

I have just compiled pycharm-community without bundled-jdk use flag
and found out that now it can start (after setting
export PYCHARM_JDK=`java-config -O`

Moreover, I have found out that, in
https://wiki.gentoo.org/wiki/PyCharm_Community_Edition, it is stated
that "There are currently no USE flags available for
dev-util/pycharm-community" which is definitely not true.

So, I have filed the following bug about all this:
https://bugs.gentoo.org/764926