Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!
Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.
Strony: 1
Usilowalem dzisiaj skutecznie zainstalowac oporne Google Earth ktore do tej pory ciagle crash. https://forum.dug.net.pl/viewtopic.php?id=29324
Po boot messages zamiast ekranu logowania zaliczylem bialy ekran, ktory mowi ze cos poszlo zle i zeby ponownie probowac.
Niestety to nieskuteczna rada.
Wszedlem w opcje zaawansowane gdzie komenda:
"journalctl -xb"
pokazala log z taka trescia:
Failed at step EXEC spawning /bin/plymuth. No such file or directory
Jak uratowac system, bo mam na nim wiele waznych ustawien?
Ostatnio edytowany przez Novi-cjusz (2017-06-04 19:19:05)
Offline
Coś mi się zdaje że nie odróżniasz botowania od startu gnome.
Zobacz na nowym użytkowniku czy wszystko odpali.
Offline
Jak to zrobic, majac tylko dostep do shella ?
Offline
Offline
Zobacz na nowym użytkowniku czy wszystko odpali.
Nie moge, bo konsola narzuca logowanie, ja nie mam wyboru.
Utworzylem uzytkownika "Jan"
Zeby bylo weselej to przegladarka na Centosie bedacym na sasiedniej partycji fiksuje: http://imgur.com/a/TNSvv
Tak na logike to nie powinno miec zwiazku, albo moze miec zwiazek jezeli cos w opragramowaniu hardware jest uwalone.
Doczytalem:
Plymouth presents a graphic animation (also known as bootsplash) while the boot process is occurring in the background. It is designed to be used with the Direct Rendering Manager (DRM) modesetting drivers
Wykonalem:
advanced options, recovery mode, password, useradd -m Jan
Nie pomoglo.
Ustalilem remount error:
# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda2 during installation UUID=c9f2f7f2-fdf3-4cb2-8b04-db6bb478f774 / ext4 errors=remount-ro 0 1 /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
Tylko nie wiem jak to naprawic?
Moze problem jest w sterownikach?
andrew@andrew-desktop:~$ lspci -k 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) (rev 02) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B) 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) Kernel driver in use: pcieport 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D) Kernel driver in use: pcieport 00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port E) Kernel driver in use: pcieport 00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port F) Kernel driver in use: pcieport 00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port G) Kernel driver in use: pcieport 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40) Subsystem: ASUSTeK Computer Inc. Device 84dd Kernel driver in use: ahci 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Kernel driver in use: ohci-pci 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Kernel driver in use: ehci-pci 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Kernel driver in use: ohci-pci 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Kernel driver in use: ehci-pci 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller Kernel driver in use: piix4_smbus 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller (rev 40) Subsystem: ASUSTeK Computer Inc. Device 84de Kernel driver in use: pata_atiixp 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40) Subsystem: ASUSTeK Computer Inc. Device 84fb Kernel driver in use: snd_hda_intel 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller Kernel driver in use: ohci-pci 00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Kernel driver in use: ohci-pci 00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Kernel driver in use: ehci-pci 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 Kernel driver in use: k10temp 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 Kernel driver in use: fam15h_power 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 01:00.0 VGA compatible controller: NVIDIA Corporation NV42GL [Quadro FX 3450/4000 SDI] (rev a2) Subsystem: NVIDIA Corporation Device 029b Kernel driver in use: nouveau 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09) Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard Kernel driver in use: r8169 03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller Subsystem: ASUSTeK Computer Inc. P8B WS Motherboard Kernel driver in use: xhci_hcd 04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) Subsystem: ASUSTeK Computer Inc. Device 84b7 Kernel driver in use: ahci 05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller Subsystem: ASUSTeK Computer Inc. P8B WS Motherboard Kernel driver in use: xhci_hcd 06:05.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a) Subsystem: Creative Labs CT4780 SBLive! Value Kernel driver in use: snd_emu10k1 06:05.1 Input device controller: Creative Labs SB Live! Game Port (rev 0a) Subsystem: Creative Labs Gameport Joystick Kernel driver in use: Emu10k1_gameport andrew@andrew-desktop:~$
*-display description: VGA compatible controller product: NV42GL [Quadro FX 3450/4000 SDI] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:90 memory:fd000000-fdffffff memory:c0000000-cfffffff memory:fc000000-fcffffff memory:fe000000-fe01ffff
andrew@andrew-desktop:~$ lspci | grep -i vga 01:00.0 VGA compatible controller: NVIDIA Corporation NV42GL [Quadro FX 3450/4000 SDI] (rev a2)
Wszystko ATI tylko VGA - NVIDIA.
Chyba jestem coraz blizej rozwiazania.
Komenda
journalctl -xn
mowi ze
gdm service inactive
ale
systemctl start gdm.service
zamiast poprawy wywoluje czarny niereaktywny ekran zamiast ekranu logowania.
Dodatkowe info:
- http://imgur.com/a/DYPQf
- http://imgur.com/a/DO1Gg
Przeinstalowalem gdm3 - nie pomoglo, zamiast demonstrowac okno logowania, demonstruje bialy ekran.
Reinstalowalem gnome - core https://packages.debian.org/jessie/gnome-core i wszystko znowu gra, nawet nie stracilem zakladek w FF.
Ostatnio edytowany przez Novi-cjusz (2017-06-04 19:18:26)
Offline
Strony: 1