Artix Linux => System => Topic started by: tefenet on 05 September 2018, 18:48:01
Title: [SOLVED] boot stop before login, cant startx
Post by: tefenet on 05 September 2018, 18:48:01
hi, Yesterday I installed virtualbox, as needed to deploy a 30 Gb system and did not have space in / home, I made a new directory: "/ virtual" I also made a partition of 60 Gb in the hdd. I added a line in the fstab to automatically mount said partition in / virtual. copy the .ova file in / virtual and start the process of importing disk, with virtualbox. in the process he asked me something about the network adapter, I gave him ok. the virtual system was going. I think the system was deployed in my root and not in the new partition generating some kind of conflict with my system, I do not know how to find out or how to solve it. now the startup stops before login, then I give "enter" and I can login. here is when I run startx, and it responds, unsupported high keycode 372 for name i372 ignored
Sep 4 16:09:20 juan-pc syslog-ng[2024]: syslog-ng starting up; version='3.15.1' Sep 4 19:51:20 juan-pc syslog-ng[2024]: syslog-ng shutting down; version='3.15.1' Sep 4 19:51:46 juan-pc syslog-ng[2072]: syslog-ng starting up; version='3.15.1' Sep 4 19:55:17 juan-pc syslog-ng[2072]: syslog-ng shutting down; version='3.15.1' Sep 4 19:55:45 juan-pc syslog-ng[2069]: syslog-ng starting up; version='3.15.1' Sep 4 20:55:45 juan-pc syslog-ng[2069]: I/O error occurred while writing; fd='18', error='No space left on device (28)' Sep 4 20:55:45 juan-pc syslog-ng[2069]: I/O error occurred while writing; fd='17', error='No space left on device (28)' Sep 4 20:55:45 juan-pc syslog-ng[2069]: Suspending write operation because of an I/O error; fd='18', time_reopen='10' Sep 4 20:55:45 juan-pc syslog-ng[2069]: Suspending write operation because of an I/O error; fd='17', time_reopen='10' Sep 4 20:55:55 juan-pc syslog-ng[2069]: Error suspend timeout has elapsed, attempting to write again; fd='18' Sep 4 20:55:55 juan-pc syslog-ng[2069]: Error suspend timeout has elapsed, attempting to write again; fd='17' Sep 4 20:55:55 juan-pc syslog-ng[2069]: I/O error occurred while writing; fd='18', error='No space left on device (28)' Sep 4 20:55:55 juan-pc syslog-ng[2069]: I/O error occurred while writing; fd='17', error='No space left on device (28)' Sep 4 20:55:55 juan-pc syslog-ng[2069]: Suspending write operation because of an I/O error; fd='17', time_reopen='10' Sep 4 20:55:55 juan-pc syslog-ng[2069]: Suspending write operation because of an I/O error; fd='18', time_reopen='10' Sep 4 20:56:05 juan-pc syslog-ng[2069]: Error suspend timeout has elapsed, attempting to write again; fd='17' Sep 4 20:56:05 juan-pc syslog-ng[2069]: Error suspend timeout has elapsed, attempting to write again; fd='18' Sep 4 20:56:05 juan-pc syslog-ng[2069]: I/O error occurred while writing; fd='17', error='No space left on device (28)' Sep 4 20:56:05 juan-pc syslog-ng[2069]: I/O error occurred while writing; fd='18', error='No space left on device (28)' Sep 4 20:56:05 juan-pc syslog-ng[2069]: Suspending write operation because of an I/O error; fd='17', time_reopen='10' Sep 4 20:56:05 juan-pc syslog-ng[2069]: Su
Xorg.0.log
Quote
[ 9.964] (--) Log file renamed from "/var/log/Xorg.pid-2241.log" to "/var/log/Xorg.0.log" [ 9.966] X.Org X Server 1.20.1 X Protocol Version 11, Revision 0 [ 9.966] Build Operating System: Linux Artix Linux [ 9.966] Current Operating System: Linux juan-pc 4.18.4-artix1-1-ARTIX #1 SMP PREEMPT Wed Aug 22 11:50:18 UTC 2018 x86_64 [ 9.966] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=a98d7c6c-5548-4635-b5a6-9d3ff5030943 rw quiet resume=UUID=b7c8def7-cb0c-4e93-b3d0-7158a96cd7ed [ 9.966] Build Date: 09 August 2018 07:08:35PM [ 9.966] [ 9.966] Current version of pixman: 0.34.0 [ 9.966] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 9.966] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 9.966] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 5 08:32:11 2018 [ 9.967] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 9.967] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 9.968] (==) No Layout section. Using the first Screen section. [ 9.968] (==) No screen section available. Using defaults. [ 9.968] (**) |-->Screen "Default Screen Section" (0) [ 9.968] (**) | |-->Monitor "<default monitor>" [ 9.969] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 9.969] (==) Automatically adding devices [ 9.969] (==) Automatically enabling devices [ 9.969] (==) Automatically adding GPU devices [ 9.969] (==) Automatically binding GPU devices [ 9.969] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 9.972] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF". [ 9.972] Entry deleted from font path. [ 9.972] (Run 'mkfontdir' on "/usr/share/fonts/OTF"). [ 9.972] (WW) The directory "/usr/share/fonts/Type1" does not exist. [ 9.972] Entry deleted from font path. [ 9.972] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi". [ 9.972] Entry deleted from font path. [ 9.972] (Run 'mkfontdir' on "/usr/share/fonts/100dpi"). [ 9.972] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi". [ 9.972] Entry deleted from font path. [ 9.972] (Run 'mkfontdir' on "/usr/share/fonts/75dpi"). [ 9.972] (==) FontPath set to: /usr/share/fonts/misc, /usr/share/fonts/TTF [ 9.972] (==) ModulePath set to "/usr/lib/xorg/modules" [ 9.972] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 9.972] (II) Module ABI versions: [ 9.972] X.Org ANSI C Emulation: 0.4 [ 9.972] X.Org Video Driver: 24.0 [ 9.972] X.Org XInput driver : 24.1 [ 9.972] X.Org Server Extension : 10.0 [ 9.973] (++) using VT number 7
[ 9.973] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 9.973] (II) xfree86: Adding drm device (/dev/dri/card0) [ 9.989] (--) PCI:*(0@0:1:0) 1002:9874:1043:8719 rev 226, Mem @ 0xe0000000/268435456, 0xf0000000/8388608, 0xfe900000/262144, I/O @ 0x0000f000/256, BIOS @ 0x????????/131072 [ 9.989] (II) Open ACPI successful (/var/run/acpid.socket) [ 9.989] (II) LoadModule: "glx" [ 9.990] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 10.004] (II) Module glx: vendor="X.Org Foundation" [ 10.004] compiled for 1.20.1, module version = 1.0.0 [ 10.004] ABI class: X.Org Server Extension, version 10.0 [ 10.004] (II) Applying OutputClass "AMDgpu" to /dev/dri/card0 [ 10.004] loading driver: amdgpu [ 10.004] (==) Matched amdgpu as autoconfigured driver 0 [ 10.004] (==) Matched ati as autoconfigured driver 1 [ 10.004] (==) Matched modesetting as autoconfigured driver 2 [ 10.004] (==) Matched fbdev as autoconfigured driver 3 [ 10.004] (==) Matched vesa as autoconfigured driver 4 [ 10.004] (==) Assigned the driver to the xf86ConfigLayout [ 10.004] (II) LoadModule: "amdgpu" [ 10.004] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so [ 10.008] (II) Module amdgpu: vendor="X.Org Foundation" [ 10.008] compiled for 1.20.0, module version = 18.0.1 [ 10.008] Module class: X.Org Video Driver [ 10.008] ABI class: X.Org Video Driver, version 24.0 [ 10.008] (II) LoadModule: "ati" [ 10.008] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [ 10.008] (II) Module ati: vendor="X.Org Foundation" [ 10.008] compiled for 1.20.0, module version = 18.0.1 [ 10.008] Module class: X.Org Video Driver [ 10.008] ABI class: X.Org Video Driver, version 24.0 [ 10.037] (II) LoadModule: "modesetting" [ 10.037] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 10.038] (II) Module modesetting: vendor="X.Org Foundation" [ 10.038] compiled for 1.20.1, module version = 1.20.1 [ 10.038] Module class: X.Org Video Driver [ 10.038] ABI class: X.Org Video Driver, version 24.0 [ 10.038] (II) LoadModule: "fbdev" [ 10.038] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 10.039] (II) Module fbdev: vendor="X.Org Foundation" [ 10.039] compiled for 1.20.0, module version = 0.5.0 [ 10.039] Module class: X.Org Video Driver [ 10.039] ABI class: X.Org Video Driver, version 24.0 [ 10.039] (II) LoadModule: "vesa" [ 10.039] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 10.040] (II) Module vesa: vendor="X.Org Foundation" [ 10.040] compiled for 1.20.0, module version = 2.4.0 [ 10.040] Module class: X.Org Video Driver [ 10.040] ABI class: X.Org Video Driver, version 24.0 [ 10.040] (II) AMDGPU: Driver for AMD Radeon: All GPUs supported by the amdgpu kernel driver [ 10.040] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 10.040] (II) FBDEV: driver for framebuffer: fbdev [ 10.040] (II) VESA: driver for VESA chipsets: vesa [ 10.056] (II) [KMS] Kernel modesetting enabled. [ 10.071] (WW) Falling back to old probe method for modesetting [ 10.071] (WW) Falling back to old probe method for fbdev [ 10.071] (II) Loading sub module "fbdevhw" [ 10.071] (II) LoadModule: "fbdevhw" [ 10.071] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 10.072] (II) Module fbdevhw: vendor="X.Org Foundation" [ 10.072] compiled for 1.20.1, module version = 0.0.2 [ 10.072] ABI class: X.Org Video Driver, version 24.0 [ 10.072] (II) AMDGPU(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 10.072] (==) AMDGPU(0): Depth 24, (--) framebuffer bpp 32 [ 10.072] (II) AMDGPU(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 10.072] (==) AMDGPU(0): Default visual is TrueColor [ 10.072] (==) AMDGPU(0): RGB weight 888 [ 10.072] (II) AMDGPU(0): Using 8 bits per RGB (8 bit DAC) [ 10.072] (--) AMDGPU(0): Chipset: "Unknown AMD Radeon GPU" (ChipID = 0x9874) [ 10.072] (II) Loading sub module "fb" [ 10.072] (II) LoadModule: "fb" [ 10.072] (II) Loading /usr/lib/xorg/modules/libfb.so [ 10.073] (II) Module fb: vendor="X.Org Foundation" [ 10.073] compiled for 1.20.1, module version = 1.0.0 [ 10.073] ABI class: X.Org ANSI C Emulation, version 0.4 [ 10.073] (II) Loading sub module "dri2" [ 10.073] (II) LoadModule: "dri2" [ 10.073] (II) Module "dri2" already built-in [ 10.308] (II) Loading sub module "glamoregl" [ 10.308] (II) LoadModule: "glamoregl" [ 10.308] (II) Loading /usr/lib/xorg/modules/libglamoregl.so [ 10.317] (II) Module glamoregl: vendor="X.Org Foundation" [ 10.317] compiled for 1.20.1, module version = 1.0.1 [ 10.317] ABI class: X.Org ANSI C Emulation, version 0.4 [ 10.343] (II) AMDGPU(0): glamor X acceleration enabled on AMD CARRIZO (DRM 3.26.0, 4.18.4-artix1-1-ARTIX, LLVM 6.0.1) [ 10.343] (II) AMDGPU(0): glamor detected, initialising EGL layer. [ 10.343] (==) AMDGPU(0): TearFree property default: auto [
Title: Re: boot stop before login, cant startx
Post by: nous on 06 September 2018, 14:31:45
The most obvious reason would be that indicated by syslogd:
I/O error occurred while writing; fd='17', error='No space left on device (28)'
Since you can at least login, try freeing up some disk space.
Title: Re: boot stop before login, cant startx
Post by: tefenet on 06 September 2018, 22:58:47
yesterday I deleted the disk of the virtual machine and I already have enough space, the error persists. the first error message before logging in is: ModemManager [2001]: <info> Could not check support for device '/sys/devices/pci0000:00/0000:00:02.4/0000:01:00.2/0000: 02: 00.0 / 0000: 03: 00.0 ': not supported by any plugin
rc boot logging started at Wed Sep 5 07:49:31 2018
* Loading module vboxdrv ... [ ok ] * Loading module vboxpci ... [ ok ] * Loading module vboxnetadp ... [ ok ] * Loading module vboxnetflt ... [ ok ] * Setting system clock using the hardware clock [UTC] ... [ ok ] * Mounting misc binary rc default logging started at Wed Sep 5 08:02:11 2018
* Starting NetworkManager ... [ ok ] Connecting... 1sConnecting.... 1sConnecting..... 1sConnecting...... 1sConnecting....... 1sConnecting........ 1sConnecting......... 1sConnecting.......... 1sConnecting........... 1sConnecting............ 1sConnecting............. 1sConnecting.............. 1sConnecting............... 1sConnecting............... 0s [offline] * Marking NetworkManager as inactive. It will automatically be marked * as started after a network connection has been established. * WARNING: NetworkManager has started, but is inactive * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ... [2018-09-05T08:02:12.614109] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.15 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file.; [ ok ] * Starting syslog-ng ... [2018-09-05T08:02:12.789828] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.15 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file.; [2018-09-05T08:02:12.818810] Can't grow the persist file; old_size='0', new_size='16384', error='No space left on device' * start-stop-daemon: failed to start `/usr/bin/syslog-ng' * Failed to start syslog-ng [ !! ] * ERROR: syslog-ng failed to start * Starting acpid ... [ ok ] * Starting cronie ... [ ok ] * WARNING: netmount will start when NetworkManager has started * Setting up sddm ... [ ok ] * Starting local ... [ ok ]
rc default logging stopped at Wed Sep 5 08:02:13 2018
thanks for answering
edit: I deleted virtualbox, and now when it starts it just leaves the screen black. I can access another tty console and log in, but startx gives the same error. I tried to reinstall xorg-server and it tells me that there is no space, I lost patience and an important file. I think I'm going to reinstall and reconfigure :'(
Title: Re: boot stop before login, cant startx
Post by: nous on 07 September 2018, 02:10:12
The virtualbox modules and modemmanager aren't the show stoppers.
[2018-09-05T08:02:12.818810] Can't grow the persist file; old_size='0', new_size='16384', error='No space left on device'
This however is. Importing a real disk into virtualbox isn't such a good idea sometimes. Does sddm start OK or only user-invoked startx fails?
Title: Re: boot stop before login, cant startx
Post by: tefenet on 07 September 2018, 03:58:34
I try to start sddm in tty1, and it tells me that it is already started in ty7 then it aborts. ty7 only has a black screen
Title: Re: boot stop before login, cant startx
Post by: ####### on 07 September 2018, 04:31:35
If you can get a shell, perhaps even from a bootable iso if needed, then you can see how big partitions are, mount them, and check how much space has been used. du might not be perfectly accurate or give the result in GB not GiB but it usually gives an idea which partition is full or nearly full. (If a partition is already mounted then you can cd straight to it's top level directory.)
fdisk -l lsblk mount -o ro /dev/sdaX /mnt cd /mnt du -hs umount /mnt ...etc...
Perhaps this isn't a real no space error and is something else, but when I accidentally tried to copy a large file to a too small partition, even though the copy failed on a no space left on device error, I think I remember it left a partial file in place that filled the partition, which I had to manually delete.
Title: Re: boot stop before login, cant startx
Post by: tefenet on 07 September 2018, 04:42:34
good news! it was a space problem like my friend nous said . next time I will have to allocate more space to the system. now I'm going to open another thread to ask how to use virtualbox correctly you answered me soon, im on artix again :) thanks to all!!
Title: Re: boot stop before login, cant startx
Post by: nous on 07 September 2018, 15:33:21
Great! Please edit your first post and add a [SOLVED] tag to the subject.