Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] boot stop before login, cant startx (Read 355 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] boot stop before login, cant startx

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

kernel.log
Code: [Select]
Sep  4 19:38:04 juan-pc kernel: snd_hda_intel 0000:00:09.2: Too big adjustment 256
Sep  4 19:43:55 juan-pc kernel: EXT4-fs (sdb7): mounted filesystem with ordered data mode. Opts: (null)
Sep  4 19:51:49 juan-pc kernel: r8169 0000:03:00.0 enp3s0: link up
Sep  4 19:51:49 juan-pc kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
Sep  4 19:51:52 juan-pc kernel: fuse init (API version 7.27)
Sep  4 19:53:31 juan-pc kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Sep  4 19:55:48 juan-pc kernel: r8169 0000:03:00.0 enp3s0: link up
Sep  4 19:55:48 juan-pc kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
Sep  4 19:56:00 juan-pc kernel: fuse init (API version 7.27)
Sep  4 20:04:52 juan-pc kernel: raid6: sse2x1   gen()  7482 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: sse2x1   xor()  5619 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: sse2x2   gen() 10258 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: sse2x2   xor()  7797 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: sse2x4   gen() 12553 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: sse2x4   xor()  5131 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: avx2x1   gen() 12112 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: avx2x1   xor()  7841 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: avx2x2   gen() 14351 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: avx2x2   xor()  8562 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: avx2x4   gen() 15902 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: avx2x4   xor()  7223 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: using algorithm avx2x4 gen() 15902 MB/s
Sep  4 20:04:52 juan-pc kernel: raid6: .... xor() 7223 MB/s, rmw enabled
Sep  4 20:04:52 juan-pc kernel: raid6: using avx2x2 recovery algorithm
Sep  4 20:04:52 juan-pc kernel: xor: automatically using best checksumming function   avx      
Sep  4 20:04:52 juan-pc kernel: Btrfs loaded, crc32c=crc32c-intel
Sep  4 20:04:52 juan-pc kernel: JFS: nTxBlock = 8192, nTxLock = 65536
Sep  4 20:06:14 juan-pc kernel: EXT4-fs (sdb7): mounted filesystem with ordered data mode. Opts: (null)
Sep  4 20:52:13 juan-pc kernel: SUPR0GipMap: fGetGipCpu=0xb
Sep  4 20:56:28 juan-pc kernel: vboxdrv: 000000004db29b10 VMMR0.r0
Sep  4 20:56:28 juan-pc kernel: vboxdrv: 000000003a91291f VBoxDDR0.r0
Sep  4 20:56:29 juan-pc kernel: VBoxNetFlt: attached to 'enp3s0' / 88:d7:f6:3e:a0:9a
Sep  4 20:56:29 juan-pc kernel: vboxpci: created IOMMU domain 00000000eca8893c
Sep  4 20:56:29 juan-pc kernel: device enp3s0 entered promiscuous mode
Sep  4 21:39:55 juan-pc kernel: PM: suspend entry (deep)
Sep  4 21:48:59 juan-pc kernel: PM: Syncing filesystems ... done.
Sep  4 21:48:59 juan-pc kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Sep  4 21:48:59 juan-pc kernel: OOM killer disabled.
Sep  4 21:48:59 juan-pc kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Sep  4 21:48:59 juan-pc kernel: Suspending console(s) (use no_console_suspend to debug)
Sep  4 21:48:59 juan-pc kernel: serial 00:06: disabled
Sep  4 21:48:59 juan-pc kernel: sd 6:0:0:0: [sdb] Synchronizing SCSI cache
Sep  4 21

syslog.log
Code: [Select]
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:*([email protected]: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
[  

Re: boot stop before login, cant startx

Reply #1
The most obvious reason would be that indicated by syslogd:
Code: [Select]
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.

Re: boot stop before login, cant startx

Reply #2
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

you can see it in this extract of everything.log
Code: [Select]
Sep  4 19:55:45 juan-pc syslog-ng[2069]: syslog-ng starting up; version='3.15.1'
Sep  4 19:55:45 juan-pc crond[2129]: (CRON) STARTUP (1.5.2)
Sep  4 19:55:45 juan-pc crond[2129]: (CRON) INFO (Syslog will be used instead of sendmail.)
Sep  4 19:55:45 juan-pc crond[2129]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 58% if used.)
Sep  4 19:55:45 juan-pc crond[2129]: (CRON) INFO (running with inotify support)
Sep  4 19:55:45 juan-pc /etc/init.d/netmount[2136]: WARNING: netmount will start when NetworkManager has started
Sep  4 19:55:45 juan-pc acpid[2101]: starting up with netlink and the input layer
Sep  4 19:55:45 juan-pc acpid[2101]: 1 rule loaded
Sep  4 19:55:45 juan-pc acpid[2101]: waiting for events: event logging is off
Sep  4 19:55:45 juan-pc supervise-daemon[2265]: Supervisor command line: supervise-daemon agetty.tty1 --start --pidfile /run/agetty.tty1.pid /sbin/agetty -- tty1 38400 linux
Sep  4 19:55:45 juan-pc supervise-daemon[2267]: Child command line: /sbin/agetty tty1 38400 linux
Sep  4 19:55:45 juan-pc acpid[2101]: client connected from 2247[0:0]
Sep  4 19:55:45 juan-pc acpid[2101]: 1 client rule loaded
Sep  4 19:55:45 juan-pc supervise-daemon[2293]: Supervisor command line: supervise-daemon agetty.tty2 --start --pidfile /run/agetty.tty2.pid /sbin/agetty -- tty2 38400 linux
Sep  4 19:55:45 juan-pc supervise-daemon[2295]: Child command line: /sbin/agetty tty2 38400 linux
Sep  4 19:55:45 juan-pc supervise-daemon[2321]: Supervisor command line: supervise-daemon agetty.tty3 --start --pidfile /run/agetty.tty3.pid /sbin/agetty -- tty3 38400 linux
Sep  4 19:55:45 juan-pc supervise-daemon[2323]: Child command line: /sbin/agetty tty3 38400 linux
Sep  4 19:55:46 juan-pc supervise-daemon[2349]: Supervisor command line: supervise-daemon agetty.tty4 --start --pidfile /run/agetty.tty4.pid /sbin/agetty -- tty4 38400 linux
Sep  4 19:55:46 juan-pc supervise-daemon[2351]: Child command line: /sbin/agetty tty4 38400 linux
Sep  4 19:55:46 juan-pc supervise-daemon[2377]: Supervisor command line: supervise-daemon agetty.tty5 --start --pidfile /run/agetty.tty5.pid /sbin/agetty -- tty5 38400 linux
Sep  4 19:55:46 juan-pc supervise-daemon[2379]: Child command line: /sbin/agetty tty5 38400 linux
Sep  4 19:55:46 juan-pc supervise-daemon[2405]: Supervisor command line: supervise-daemon agetty.tty6 --start --pidfile /run/agetty.tty6.pid /sbin/agetty -- tty6 38400 linux
Sep  4 19:55:46 juan-pc supervise-daemon[2407]: Child command line: /sbin/agetty tty6 38400 linux
Sep  4 19:55:47 juan-pc ModemManager[2001]: <info>  Couldn't 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
Sep  4 19:55:48 juan-pc NetworkManager[1958]: <info>  [1536101748.1933] device (enp3s0): carrier: link connected
Sep  4 19:55:48 juan-pc NetworkManager[1958]: <info>  [1536101748.1941] device (enp3s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Sep  4 19:55:48 juan-pc kernel: r8169 0000:03:00.0 enp3s0: link up
Sep  4 19:55:48 juan-pc kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
Sep  4 19:55:48 juan-pc NetworkManager[1958]: <info>  [1536101748.1955] policy: auto-activating connection 'Wired connection 1' (73baa458-2973-3819-9331-3132738b5d2f)
Sep  4 19:55:48 juan-pc NetworkManager[1958]: <info>  [1536101748.1975] device (enp3s0): Activation: starting connection 'Wired connection 1' (73baa458-2973-3819-9331-3132738b5d2f)
Sep  4 19:55:48 juan-pc NetworkManager[1958]: <info>  [1536101748.1978] device (enp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep  4 19:55:48 juan-pc NetworkManager[1958]: <info>  [1536101748.1987] manager: NetworkManager state is now CONNECTING
Sep  4 19:55:48 juan-pc NetworkManager[1958]: <info>  [1536101748.1992] device (enp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep  4 19:55:48 juan-pc NetworkManager[1958]: <info>  [1536101748.2001] device (enp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep  4 19:55:48 juan-pc NetworkManager[1958]: <info>  [1536101748.2010] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)

lspci -nnk
Code: [Select]
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576]
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) I/O Memory Management Unit [1022:1577]
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev e2)
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio [1002:9840]
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge [1022:157b]
00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port [1022:157c]
Kernel driver in use: pcieport
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge [1022:157b]
00:08.0 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Device [1022:1578]
Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1578]
00:09.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:157d]
00:09.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Audio Controller [1022:157a]
Subsystem: ASUSTeK Computer Inc. Device [1043:86c7]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller [1022:7914] (rev 20)
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 49)
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
Kernel driver in use: ahci
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 4a)
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 11)
Subsystem: ASUSTeK Computer Inc. Device [1043:8719]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 0 [1022:1570]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 1 [1022:1571]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 2 [1022:1572]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 3 [1022:1573]
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 4 [1022:1574]
Kernel driver in use: fam15h_power
Kernel modules: fam15h_power
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 5 [1022:1575]
01:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset USB 3.1 xHCI Controller [1022:43bb] (rev 02)
Subsystem: ASMedia Technology Inc. Device [1b21:1142]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
01:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset SATA Controller [1022:43b7] (rev 02)
Subsystem: ASMedia Technology Inc. Device [1b21:1062]
Kernel driver in use: ahci
01:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43b2] (rev 02)
Kernel driver in use: pcieport
02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)
Kernel driver in use: pcieport
02:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)
Kernel driver in use: pcieport
02:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port [1022:43b4] (rev 02)
Kernel driver in use: pcieport
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: ASUSTeK Computer Inc. Device [1043:8677]
Kernel driver in use: r8169
Kernel modules: r8169
04:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 04)

here an exctract of rc.log, when booting is loading virtual box modules that is normal?
Code: [Select]
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
:'(

Re: boot stop before login, cant startx

Reply #3
The virtualbox modules and modemmanager aren't the show stoppers.
Code: [Select]
[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?

Re: boot stop before login, cant startx

Reply #4
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

Re: boot stop before login, cant startx

Reply #5
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.)
Code: [Select]
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.

Re: boot stop before login, cant startx

Reply #6
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!!

 

Re: boot stop before login, cant startx

Reply #7
Great! Please edit your first post and add a [SOLVED] tag to the subject.