Anunţ

Caută printre mesajele de pe forum înainte de a scrie unul nou!
Formulează corect întrebarea sau problema pe care o ai.
Respectă regulile forumului și Codul de Conduită!

#1 10 Apr 2020 12:24:30

qew00
Membru nou
Înregistrat: 10 Apr 2020
Mesaje: 6

Problema dual boot Windows10/Ubuntu 18.04

Bun. Pe vremuri am mai instalat Ubuntu acu 5-6-7 ani nu am avut problema. Dar acum am.

Am un Laptop cu Windows 10 original si vreau sa fac dual boot.

Am luat 18.04 , am facut un stick bootabil si m-am pus pe instalat.
Bootez de pe stick imi apare meniul de instalare cu alesul limbii si nu apuc sa dau click ca freezuie, si ramane asa. Dau power off de la buton. Reincerc de data asta merge si se instaleaza.
Si Ubuntu instalat imi apare fereastra cu what is new si chestii si freezuie iar la fel nimic. Sting laptopul tot de la buton. Intru de data asta in windows. Totul normal, doar ca e ora decalata. Nicio problema, intru in setari in windows is ii dau resync la date.time windows si isi revine. Dau restart, imi apare meniul de ales de pe unde sa imi booteze si e freezuit, nu se intampla nimic nu pto selecta nimic ,tastatura nu functioneaza(am testat cu caps look). Din nou turn of, il reaprind merge de data asta , aleg ubuntu. Intru in in ubuntu , si merge 2 ore nu se freezuie. Il sting normal si se opreste.

Dupa 2 ore deschid laptopul, intru pe windows, iar ora e decalata. Repet procedura. Stau pe windows cateva ore nu e problema. Ii dau restart sa intru in Ubuntu. Iar freezuie meniul de ales pe ce sa booteze. Din nou turn off de la buton repornit , merge meniul intru in ubuntu , dupa 2 minute freezuie. Iar turn off turn on, intru iar in ubuntu, 2 ore nu mai freezuie. Dau sa il sting: si incepe sa ruleze ceva comenzi pe fundal , si ramane asa 10 mintue nu se mai intampla nimic. Il sting iar de la buton. Restart , intru iar in Ubuntu, il pornesc, stau 5 minute il opresc iar  normal, iar se blocheaza si nu se inchide.

De ce face asa si e asa instabil? Windowsul se misca bine si in afara de faza cu ora nu am vazut nimic dubios.

Laptopul este suficient de bun, nu asta e problema. Inainte de instalare am scos din partitia C din windows(avea o singura partitie) niste memorie, cam 200 de gb pentru linux. si 200_ gb a ramas pt windows. Laptopul are un SSD de 512 GB. Alte detalii nu stiu ce sa mai dau.

Multumesc. Daca este nevoie de mai multe detalii pentru a rezolva problema va rog sa imi spuneti.

M-am gandit sa dezinstalez ubuntu si sa incerc din nou desi nu vad sa fi gresit la instalare. La fel eventual sa refac stickul bootabil, desi nici acolo nu vad sa fi gresit cu ceva, nu e prima data cand fac stickuri bootabile.

Offline

 

#2 10 Apr 2020 17:15:44

zBANG
Membru
Locaţie: Neamt
Înregistrat: 07 May 2015
Mesaje: 91

Re: Problema dual boot Windows10/Ubuntu 18.04

pai fa stick-ul bootabil cu rufus si acolo la ubuntu selecteaza gpt ... o sa faca stick-u uefi si in principiu o sa mearga


Gaming is fun...banggin' is funnier !!

Offline

 

#3 10 Apr 2020 18:58:04

gbagape
Membru
Locaţie: Constanta
Înregistrat: 10 Aug 2011
Mesaje: 901

Re: Problema dual boot Windows10/Ubuntu 18.04

Încearcă să faci un stick cu lubuntu 18.04 LTS poate e ceva necompatibil în Ubuntu.

Editat ultima oară de gbagape (10 Apr 2020 18:58:39)


Degeaba porți capul pe umeri dacă nu știi când să'l folosești.
Skype: gbagapegb1
Yahoo:gbagape
Ubuntu User # 34906,http://linuxcounter.net/user/551248.html

Offline

 

#4 10 Apr 2020 19:26:38

qew00
Membru nou
Înregistrat: 10 Apr 2020
Mesaje: 6

Re: Problema dual boot Windows10/Ubuntu 18.04

Updates

Am mai utilizat astazi laptopul.
Veste buna, nu mai freezuie nici la alegerea de pe ce sa booteze si nici in Ubuntu.

La oprire, daca stau pe ubuntu putin gen pana in 5 minute se stinge cum trebuie (sau se reseteaza cum trebuie) si atunci daca reintru in windows ora nu se modifica. Cand reintru din windows in ubuntu se modifica ora in 2 secunde in ora buna in ubuntu.

Problema e urmatoarea, daca stau in ubuntu mai mult, nu se mai stinge si apare urmatoarea poza si ramane asa:
Your text to link here...
Si daca il inchid de la buton, si reintru in windows, ora este modificata(cu 3 ore) si iar trbuie sa ii dau resync.

Voi incerca varianta cu rufus sa vedem. Pot reface stickul bootabil si reinstala deasupra ubuntului? sau trebuie cumva sa il scot si sa instalez pe curat? Da laptopul are UEFI, e destul de nou, Asus Zenbook 2019.

Multumesc.

Editat ultima oară de qew00 (10 Apr 2020 19:26:56)

Offline

 

#5 11 Apr 2020 14:04:52

qew00
Membru nou
Înregistrat: 10 Apr 2020
Mesaje: 6

Re: Problema dual boot Windows10/Ubuntu 18.04

Noutati.

Am refacut stickul cu Ubuntu 18.04 LTS, L-am facut tot cu rufus ca data trecuta dar am pus gpt si uefi. A mers instalarea mai bine ca data trecuta.

Dar au ramas aceleasi probleme care apar cand si cand, nu tot timpul dar apar, dar si unele noi:
- cateodata cand intru in ubuntu nu imi vede wi-fi module, deci trebuie restart. Dau restart si cand reintru apare. Nu tot timpul am problema asta dar apare
- Daca conectez un cablu HDMI de la un monitor la laptop in timp ce este aprins in ubuntu , frezeuie si se blocheaza. La fel si daca il scot(adica bag hdmi-ul cand este stins, aprind in ubuntu pot utliza ubuntu is pe monitor perfect, dar daca trebuie sa il deconectez, freezuie). Efectiv se blocheaza nu mai merge nimic si trebuie restart.

Probleme foarte enervante pe carea acu 5-6 ani nu le-am avut cu linux(atat ubuntu cat si alte distributii).

Windowsul merge bine mersi in afara de problema cu ora care tot apare cand si cand dupa utilizarea Ubuntu.

Offline

 

#6 12 Apr 2020 07:24:56

CockoX
Membru nou
Locaţie: Bucharest
Înregistrat: 29 Jul 2018
Mesaje: 9

Re: Problema dual boot Windows10/Ubuntu 18.04

Problema cu ora apare pentru ca ubuntu, by default, salvaza in bios/hwclock ora raportat la UTC iar Windows se raporteaza la Local Time (de aici si diferenta de 3 ore);
Ruleaza asta intr-un terminal: timedatectl set-local-rtc 1 --adjust-system-clock

Legat de problema cu freeze, te rog sa verifici ce erori iti apar in loguri (/var/logs: debug, kern.log, syslog)

Editat ultima oară de CockoX (12 Apr 2020 07:30:40)

Offline

 

#7 12 Apr 2020 12:33:41

qew00
Membru nou
Înregistrat: 10 Apr 2020
Mesaje: 6

Re: Problema dual boot Windows10/Ubuntu 18.04

Sa le luam pe rand:

Problema cu ceasul rezolvat. Multumesc.
Problema cu freeze cand conectam un monitor sau deconectam(in timpul functionarii) pana acum vad ca s-a rezolvat dupa ce am instalat driverele de la placa grafica dedicata(am si placa grafica dedicata si integrata). Din 10 icnercari de conectare si deconectare nu a mai dat freeze.

Problema cu Wi-fi nu a mai aparut astazi dupa 10 intrari in Ubuntu inca nu a mai aparut.

Acum problema la Shut Down sau restart - o data s-a inchis greu ,a durat 30 de secunde(la un restart) si dupa aceea cand mi-a aparut meniul de ales ce sa bootez, a freezuit acolo in meniu(unde aleg daca ubuntu sau windows)- si a trebuit iar s apas pe power button si dupa 3 secunde l-am reaprins is nu a mai freezuit.

12:15:58 pornire Ubuntu
12:17:52 - cred ca atunci am dat restart
12:20:49 - a doua pornire Ubuntu dupa toata povestea explicata cu restartul si freezul in meniul de alegere de OS cu care sa porneasca

In log apare asa:

Kernel:
Apr 12 12:15:58 alex-ZenBook kernel: [    3.963884] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Apr 12 12:15:58 alex-ZenBook kernel: [    3.963886] Bluetooth: BNEP filters: protocol multicast
Apr 12 12:15:58 alex-ZenBook kernel: [    3.963889] Bluetooth: BNEP socket layer initialized
Apr 12 12:15:58 alex-ZenBook kernel: [    4.176229] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
Apr 12 12:15:58 alex-ZenBook kernel: [    4.291384] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
Apr 12 12:15:58 alex-ZenBook kernel: [    4.356545] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
Apr 12 12:15:59 alex-ZenBook kernel: [    4.853830] Lockdown: Xorg: ioperm is restricted; see man kernel_lockdown.7
Apr 12 12:16:04 alex-ZenBook kernel: [   10.081943] wlo1: authenticate with 30:d1:7e:dd:5b:7c
Apr 12 12:16:04 alex-ZenBook kernel: [   10.083654] wlo1: send auth to 30:d1:7e:dd:5b:7c (try 1/3)
Apr 12 12:16:04 alex-ZenBook kernel: [   10.192916] Bluetooth: RFCOMM TTY layer initialized
Apr 12 12:16:04 alex-ZenBook kernel: [   10.192926] Bluetooth: RFCOMM socket layer initialized
Apr 12 12:16:04 alex-ZenBook kernel: [   10.192934] Bluetooth: RFCOMM ver 1.11
Apr 12 12:16:04 alex-ZenBook kernel: [   10.195279] wlo1: authenticated
Apr 12 12:16:04 alex-ZenBook kernel: [   10.197311] wlo1: associate with 30:d1:7e:dd:5b:7c (try 1/3)
Apr 12 12:16:04 alex-ZenBook kernel: [   10.202669] wlo1: RX AssocResp from 30:d1:7e:dd:5b:7c (capab=0x1411 status=0 aid=3)
Apr 12 12:16:04 alex-ZenBook kernel: [   10.204667] wlo1: associated
Apr 12 12:16:04 alex-ZenBook kernel: [   10.240795] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
Apr 12 12:16:04 alex-ZenBook kernel: [   10.271506] wlo1: Limiting TX power to 30 (30 - 0) dBm as advertised by 30:d1:7e:dd:5b:7c
Apr 12 12:16:05 alex-ZenBook kernel: [   10.958004] rfkill: input handler disabled
Apr 12 12:17:52 alex-ZenBook kernel: [  118.101711] rfkill: input handler enabled
Apr 12 12:20:49 alex-ZenBook kernel: [    0.000000] microcode: microcode updated early to revision 0xca, date = 2019-10-03
Apr 12 12:20:49 alex-ZenBook kernel: [    0.000000] Linux version 5.3.0-46-generic (buildd@lcy01-amd64-013) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 (Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18)
Apr 12 12:20:49 alex-ZenBook kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=bdae51de-bad9-498b-93a8-2520b933d0b9 ro quiet splash vt.handoff=1
Apr 12 12:20:49 alex-ZenBook kernel: [    0.000000] KERNEL supported cpus:
Apr 12 12:20:49 alex-ZenBook kernel: [    0.000000]   Intel GenuineIntel
Apr 12 12:20:49 alex-ZenBook kernel: [    0.000000]   AMD AuthenticAMD
Apr 12 12:20:49 alex-ZenBook kernel: [    0.000000]   Hygon HygonGenuine
Apr 12 12:20:49 alex-ZenBook kernel: [    0.000000]   Centaur CentaurHauls
Apr 12 12:20:49 alex-ZenBook kernel: [    0.000000]   zhaoxin   Shanghai 
Apr 12 12:20:49 alex-ZenBook kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'


syslog1:

Apr 12 12:17:13 alex-ZenBook gnome-software[2155]: Failed to load snap icon: local snap has no icon
Apr 12 12:17:13 alex-ZenBook gnome-software[2155]: Failed to load snap icon: local snap has no icon
Apr 12 12:17:52 alex-ZenBook systemd[1028]: Stopping D-Bus User Message Bus...
Apr 12 12:17:52 alex-ZenBook gsd-print-notif[1506]: Source ID 2 was not found when attempting to remove it
Apr 12 12:17:52 alex-ZenBook kernel: [  118.101711] rfkill: input handler enabled
Apr 12 12:17:52 alex-ZenBook gnome-session[1162]: gnome-session-binary[1162]: WARNING: Lost name on bus: org.gnome.SessionManager
Apr 12 12:17:52 alex-ZenBook gnome-session[1162]: gnome-session-binary[1162]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Apr 12 12:17:52 alex-ZenBook gnome-session-binary[1162]: WARNING: Lost name on bus: org.gnome.SessionManager
Apr 12 12:17:52 alex-ZenBook gnome-session-binary[1162]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Apr 12 12:17:52 alex-ZenBook gvfsd[1308]: A connection to the bus can't be made
Apr 12 12:17:52 alex-ZenBook systemd[1028]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 12:17:52 alex-ZenBook systemd[1028]: xdg-permission-store.service: Failed with result 'exit-code'.
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: [1739:1777:0412/121752.292568:FATAL:bus.cc(1220)] D-Bus connection was disconnected. Aborting.
Apr 12 12:17:52 alex-ZenBook gsd-media-keys[1560]: Error releasing name org.gnome.SettingsDaemon: The connection is closed
Apr 12 12:17:52 alex-ZenBook gnome-software[2155]: lost session service
Apr 12 12:17:52 alex-ZenBook systemd[1028]: Stopped D-Bus User Message Bus.
Apr 12 12:17:52 alex-ZenBook systemd[1028]: Started D-Bus User Message Bus.
Apr 12 12:17:52 alex-ZenBook dbus-daemon[2347]: [session uid=1000 pid=2347] AppArmor D-Bus mediation is enabled
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: [1771:1771:0412/121752.317524:ERROR:x11_util.cc(109)] X IO error received (X server probably went away)
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "41"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event2  - Power Button: device removed
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "44"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event12 - Video Bus: device removed
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "45"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event13 - Video Bus: device removed
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "46"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event1  - Power Button: device removed
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "47"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event4  - MOSART Semi. 2.4G Wireless Mouse: device removed
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "48"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event6  - USB2.0 HD IR UVC WebCam: USB2.0: device removed
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "49"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event7  - USB2.0 HD IR UVC WebCam: USB2.0: device removed
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "50"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event18 - ELAN1401:00 04F3:30DC Touchpad: device removed
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "51"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event19 - ELAN1401:00 04F3:30DC Keyboard: device removed
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "52"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event8  - Asus WMI hotkeys: device removed
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (**) Option "fd" "53"
Apr 12 12:17:52 alex-ZenBook /usr/lib/gdm3/gdm-x-session[1048]: (II) event3  - AT Translated Set 2 keyboard: device removed
Apr 12 12:17:52 alex-ZenBook gnome-shell[1283]: [AppIndicatorSupport-DEBUG] Lost nameorg.kde.StatusNotifierWatcher
Apr 12 12:17:52 alex-ZenBook gnome-shell[1283]: Object .Gjs_AppIndicatorIconActor__1 (0x564a63cd5040), has been already finalized. Impossible to set any property to it.
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: == Stack trace for context 0x564a6198c330 ==
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #0 0x7ffef78a3270 I   resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7fc8c00b5de0 @ 87)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #1 0x564a61e23df0 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/indicatorStatusIcon.js:93 (0x7fc8736c5340 @ 58)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #2 0x7ffef78a3e50 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fc8c00b5de0 @ 71)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #3 0x7ffef78a3f10 b   self-hosted:916 (0x7fc8c00f12b8 @ 367)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #4 0x7ffef78a3f90 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7fc8c00d2230 @ 386)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #5 0x564a61e23d68 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:190 (0x7fc8736b0f78 @ 22)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #6 0x7ffef78a4b70 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fc8c00b5de0 @ 71)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #7 0x564a61e23cc0 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:176 (0x7fc8736b02b8 @ 26)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #8 0x7ffef78a5750 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fc8c00b5de0 @ 71)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #9 0x564a61e23c20 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:170 (0x7fc8736b0230 @ 68)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #10 0x7ffef78a6340 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fc8c00b5de0 @ 71)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #11 0x7ffef78a6410 b   self-hosted:918 (0x7fc8c00f12b8 @ 394)
Apr 12 12:17:52 alex-ZenBook gnome-shell[1283]: Object .Gjs_AppIndicatorIconActor__1 (0x564a6400afd0), has been already finalized. Impossible to set any property to it.
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: == Stack trace for context 0x564a6198c330 ==
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #0 0x7ffef78a3270 I   resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7fc8c00b5de0 @ 87)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #1 0x564a61e23df0 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/indicatorStatusIcon.js:93 (0x7fc8736c5340 @ 58)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #2 0x7ffef78a3e50 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fc8c00b5de0 @ 71)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #3 0x7ffef78a3f10 b   self-hosted:916 (0x7fc8c00f12b8 @ 367)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #4 0x7ffef78a3f90 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7fc8c00d2230 @ 386)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #5 0x564a61e23d68 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:190 (0x7fc8736b0f78 @ 22)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #6 0x7ffef78a4b70 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fc8c00b5de0 @ 71)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #7 0x564a61e23cc0 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:176 (0x7fc8736b02b8 @ 26)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #8 0x7ffef78a5750 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fc8c00b5de0 @ 71)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #9 0x564a61e23c20 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:170 (0x7fc8736b0230 @ 68)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #10 0x7ffef78a6340 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fc8c00b5de0 @ 71)
Apr 12 12:17:52 alex-ZenBook org.gnome.Shell.desktop[1283]: #11 0x7ffef78a6410 b   self-hosted:918 (0x7fc8c00f12b8 @ 394)
Apr 12 12:17:52 alex-ZenBook gnome-shell[1283]: gnome-shell: Fatal IO error 0 (Success) on X server :0.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Unmounted /run/user/1000/gvfs.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopped Unattended Upgrades Shutdown.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopping Thunderbolt system service...
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopping Session 1 of user alex.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopped target Sound Card.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopped target Timers.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopped Discard unused blocks once a week.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopping ACPI event daemon...
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopped target Graphical Interface.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopping GNOME Display Manager...
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopped Message of the Day.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Removed slice system-getty.slice.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopping User Manager for UID 1000...
Apr 12 12:17:52 alex-ZenBook systemd[1]: Stopping Daemon for power management...
Apr 12 12:20:49 alex-ZenBook systemd-modules-load[355]: Inserted module 'lp'
Apr 12 12:20:49 alex-ZenBook systemd-modules-load[355]: Inserted module 'ppdev'

Offline

 

#8 12 Apr 2020 12:37:16

obivankenobi
Membru
Locaţie: Sulina
Înregistrat: 13 Sep 2007
Mesaje: 813

Re: Problema dual boot Windows10/Ubuntu 18.04

Dai in fereastra de comenzi:
sudo shutdown (restart) now


Nu fura! Guvernul uraste concurenta!

Offline

 

#9 12 Apr 2020 14:17:53

CockoX
Membru nou
Locaţie: Bucharest
Înregistrat: 29 Jul 2018
Mesaje: 9

Re: Problema dual boot Windows10/Ubuntu 18.04

qew00, spune-mi modelul exact al laptop-ului! cumva ZenBook UX433xx / UX533xx?
ce CPU are?

Daca laptop-ul nu mai booteaza incat sa te poti loga pe el atunci in meniul de boot (GRUB) selecteaza Ubuntu..., apasa tasta e si adauaga la final:
dis_ucode_ldr
si apoi F10 ca sa boot-ezi.
Butoneaza ceva timp laptop-ul si vezi cum se comporta.

Daca este OK atunci poti face permanenta setarea de mai sus editand:
sudo nano /etc/default/grub
si actulizand linia GRUB_CMDLINE_LINUX_DEFAULT="" cu
GRUB_CMDLINE_LINUX_DEFAULT="dis_ucode_ldr"
+
sudo update-grub2
reboot

sau renunti la optiunea de mai sus si rulezi comenzile:
sudo apt install intel-microcode=3.20180312.0~ubuntu18.04.1
sudo apt-mark hold intel-microcode=3.20180312.0~ubuntu18.04.1

Editat ultima oară de CockoX (12 Apr 2020 14:37:29)

Offline

 

#10 12 Apr 2020 22:41:57

qew00
Membru nou
Înregistrat: 10 Apr 2020
Mesaje: 6

Re: Problema dual boot Windows10/Ubuntu 18.04

UX433FA sau FD ceva de genul.

Am descoperit solutia sa nu mi se mai freezuie in meniul de ales boot-ul. Daca e activ monitorul legat la HDMI atunci freezuie(in cazul unui restart). Dar daca monitorul este in sleep mode nu e problema.

Astazi cu inchisul nu a mai facut probleme, s-a stins. Si am stat pe el 8 ore non stop(programare, filme, net) si nu a freezuit.
O sa urmaresc sa vad daca l-am stabilizat cu masurile de pana acum.


Multumesc pentru ajutor pana acum.

Editat ultima oară de qew00 (05 May 2020 13:56:11)

Offline

 

#11 05 May 2020 17:04:04

qew00
Membru nou
Înregistrat: 10 Apr 2020
Mesaje: 6

Re: Problema dual boot Windows10/Ubuntu 18.04

A trecut aproape o luna de la trecerea pe Ubuntu. SI nu am mai avut niciun fel de problema, si nici nevoie de windows chiar daca il am in dual boot. Asa ca voi continua cu linux ca si OS principal.

Acum problema e ca: Linuxul are ca spatiu 150 de gbb si windowsul are 300 de gb. Si vreau sa transfer?

Ma gandesc la 2 solutii:
- renunt la windows de tot
- micsorez spatiul pentru windows si il mut la linux

Ma tenteaza prima varianta.
Care is pasii pentru a face asta? Pentru prima varianta pot cred merge in Disks in linux si formata , dar nu stiu cum sa partitionez dupa accea spatiul ramas, sa las o singura partitie de linux e ok? Acum tot una singura am.

Multumesc

Offline

 

#12 06 May 2020 06:47:02

CockoX
Membru nou
Locaţie: Bucharest
Înregistrat: 29 Jul 2018
Mesaje: 9

Re: Problema dual boot Windows10/Ubuntu 18.04

Salut.
Daca vrei sa renunti de tot la Windows poti formata partitia cu ntfs ca ext4 si o poti folosi ca atare sau o poti sterge complet si dai resize la partitia cu ubuntu.
Oricare ar varianta aleasa iti recomand sa instalezi GParted pentru ca este mai usor si mai intuitiv in utilizare.
... si atentie la ce stergi si formatezi, verifica de doua ori inainte sa dai Apply smile

Offline

 
Feed

Antet forum

Powered by FluxBB