=== CyberBurn is now known as OICU812 | ||
xu-dana | Just an observation of xubuntu.org - There is no link to xubuntu Documentation in the site menu. | 02:29 |
---|---|---|
xu-dana | Mainly I just wanted to know a bit more about installing a minimal xubuntu from ubuntu server, using "sudo apt install", is "xubuntu-core" still a valid option for 20.10? I just want the basics | 02:33 |
Bashing-om | xu-dana: Yes still valid >> roovy (20.10) (metapackages): Xubuntu core system [universe] .233: amd64 arm64 armhf ppc64el s390x. See to ' apt show xubuntu-core ' from terminal. | 02:38 |
=== vlm_ is now known as vlm | ||
aradesh | hi all. i'm having some issues booting up my operating system... wonder if anyone could help me debug what's going on | 12:26 |
aradesh | for a while i was able to get xubuntu to load in recovery mode, but now i just get as far as a blinking _ | 12:26 |
aradesh | though i can access the other tty's | 12:27 |
diogenes_ | aradesh, and where is the plot? | 12:32 |
aradesh | what's that? | 12:33 |
diogenes_ | aradesh, you told us the final result but how did you get there to end up with blinking cursor? (usually something like: i installed some PPAs, i installed some drivers, i removed something, i upgraded etc.) | 12:34 |
aradesh | oh, to my knowledge i didn't do anything. it was all working fine yesterday, and today when i started the laptop it just froze on a black screen. then after forcefully shutting down and getting the grub boot choice menu, i was able to boot up via recovery mode | 12:38 |
aradesh | but now having done that a few times, run diagnostics, etc, now when i try the same process from the grub menu it only gets as far as blinking cursor | 12:38 |
diogenes_ | aradesh, do you happen to dual boot with windows? | 12:39 |
aradesh | nope | 12:41 |
aradesh | just xubuntu | 12:41 |
diogenes_ | how old is the HDD/SSD? | 12:42 |
aradesh | maybe 2 years | 12:42 |
diogenes_ | try in recovery mde to boot up the first kernel (afaik it's 5.4 for 20.04) | 12:43 |
diogenes_ | mode* | 12:44 |
=== rud0lf is now known as Flowergirl42 | ||
=== Flowergirl42 is now known as rud0lf | ||
aradesh | my last kernel is 5.4.0-54-generic, and i get the recovery menu | 12:47 |
aradesh | though i suspect if i 'resume' it will get stuck at the blinking cursor | 12:47 |
diogenes_ | wait so you're talking about resuming? which means you can't wake it from sleep mode? | 12:49 |
Maik | that kernel should be 5.4.0-62 by now | 12:51 |
aradesh | well that's my oldest one | 12:52 |
aradesh | diogenes_: the first option on recovery options is resume normal boot | 12:53 |
diogenes_ | aradesh, try the oldest kernel if it doesn't boot then as soon as you reach grub menu press e and tell me when you're there. | 12:54 |
aradesh | press 'e' on which option? | 12:55 |
aradesh | the main ubuntu one, or the recovery option? | 12:55 |
aradesh | ok | 12:55 |
diogenes_ | the main default one | 12:56 |
aradesh | diogenes_: https://pastebin.com/raw/vCFVTka7 might be typos as i copied it off the screen by hand | 13:02 |
aradesh | only thing i didn't copy verbatim was some id string | 13:02 |
diogenes_ | aradesh, so i suspect it's an encrypted filesystem? | 13:02 |
aradesh | yep | 13:03 |
aradesh | it gets as far as the echoing of "Loading initial ramdisk ..." | 13:03 |
aradesh | though on recovery mode it gets further and i'm able to enter the password | 13:04 |
diogenes_ | try this, after pressing 'e', navigate to the line 'linux' and remove the following agruments: ro quiet splash $vt_handoff | 13:06 |
diogenes_ | and add the following one: nomodeset | 13:06 |
diogenes_ | after that hit ctrl+x | 13:06 |
aradesh | just nomodeset instead of all four? | 13:06 |
diogenes_ | the line should look like this: | 13:06 |
diogenes_ | linux /vmlinuz-5.4.0-56-generic root=/dev/mapper/xubuntu--vg-root nomodeset | 13:06 |
diogenes_ | that's all. | 13:06 |
aradesh | okay. | 13:06 |
aradesh | got to Loading initial ramdisk ... but stuck on a solid _ | 13:09 |
aradesh | either being very slow, or stuck | 13:09 |
aradesh | poor broken computer | 13:10 |
diogenes_ | i suspect something with your encrypted filesystem has gone wrong. | 13:10 |
diogenes_ | let's try one more thing. | 13:11 |
aradesh | but i am able to when in recovery mode have it accept my encryption password | 13:11 |
aradesh | and access the hard drive via tty terminal | 13:12 |
diogenes_ | so you either can access your system via terminal or it's just stuc at _ and you cannot do anything? (i'm confused now). | 13:12 |
aradesh | it depends what method i go through | 13:13 |
aradesh | so if i select a 'recovery' option, it asks "please unlock disk sda3_crypt" and i can enter the pw | 13:13 |
aradesh | then i get 'recovery menu' | 13:14 |
diogenes_ | and what happens next? | 13:14 |
aradesh | andn i can choose 'resume normal boot' | 13:14 |
aradesh | then i have blinking cursor, and i can say do windows key + f2 to change tty | 13:14 |
aradesh | +f1 | 13:14 |
aradesh | and log in | 13:14 |
aradesh | but... if i don't have 'recovery' selected, i don't even get as far as being able to enter my pw | 13:15 |
diogenes_ | ok get to the login at least, login and then trype: startxfce4 | 13:16 |
aradesh | printed out a bunch of stuff - and i got "Fatal server error:" "(EE) no screens found(EE)" | 13:17 |
aradesh | and eventually xinit gave up and quit | 13:19 |
diogenes_ | ok now let's try this: sudo apt reinstall lightdm xorg | 13:19 |
aradesh | it didn't like that command so i did: sudo apt-get --reinstall install lightdm xorg | 13:20 |
aradesh | ok. shall i startxfce4 again? | 13:20 |
aradesh | oo | 13:21 |
aradesh | it's doing something different | 13:21 |
diogenes_ | hmm? | 13:21 |
aradesh | it booted up this time | 13:21 |
aradesh | shall i see if i can do a normal boot now? | 13:21 |
diogenes_ | so it booted up ok? | 13:22 |
aradesh | yeah in a recovery mode way | 13:22 |
aradesh | with none of my extra monitors on | 13:23 |
diogenes_ | ok now in terminal run: systemctl poweroff | 13:23 |
diogenes_ | and after it shuts dwn completely, fire it up in normal mode. | 13:23 |
=== rud0lf is now known as rudolf | ||
aradesh | starting in normal mode doesn't seem to be working | 13:24 |
aradesh | but the reinstalling of lightdm and xorg seemed to get it to work in recovery mode at least | 13:24 |
=== rudolf is now known as rud0l | ||
=== rud0l is now known as rud0lf | ||
diogenes_ | so you still didn't get any progress at all in normal mode? | 13:26 |
aradesh | correct | 13:26 |
aradesh | very strange | 13:26 |
diogenes_ | then in recovery more try: sudo dpkg-reconfigure xorg | 13:27 |
diogenes_ | after that: sudo apt install -f | 13:27 |
aradesh | another thing - i don't know if this is related, but i've noticed that the battery doesn't seem to be working. if i pull out the power cable, it just goes off | 13:28 |
aradesh | ok, i ran those commands, though they didn't seem to do much. | 13:30 |
aradesh | nothing got newly installed | 13:30 |
diogenes_ | they weren't supposed to install anything. | 13:31 |
aradesh | okay | 13:31 |
aradesh | still something not quite right with the graphics though. i guess that's because recovery mode uses nomodeset? can't chaneg the resolution of the screen for example | 13:35 |
diogenes_ | yep it disables the drivers what GPU btw? | 13:36 |
aradesh | hmm | 13:37 |
aradesh | lshw -C display tells me: *-display UNCLAIMED and says its just "Intel Corporation" | 13:37 |
diogenes_ | try in normal mode press 'e' and add nomodeset | 13:37 |
aradesh | ok | 13:37 |
aradesh | is there any command i can type to start it up in the kernel select mode? | 13:38 |
aradesh | trying nomodeset now | 13:40 |
aradesh | nope... still hangs | 13:42 |
diogenes_ | sorry i'm a bit busy now, maybe someone could help you further on or come back later. | 13:44 |
aradesh | no problem. thanks for your help. | 13:44 |
aradesh | i'll stick around. | 13:44 |
aradesh | hmmm... managed to get it to boot up normally once. but then it didnt work again. i ran it with: ro nomodeset dis_ucode_ldr and then when it got to the login as user screen, i asked it to 'restart' and then it booted up like normal... | 13:54 |
aradesh | same method worked again - asked it to 'restart' from recovery mode login, and then it booted up as normal | 13:57 |
aradesh | very odd. | 13:57 |
diogenes_ | aradesh, ok try to boot it up normally and we'll be able to get some more info. | 13:59 |
aradesh | well i currently have it booted up normally now | 14:00 |
diogenes_ | connected to internet? | 14:00 |
aradesh | yep | 14:00 |
diogenes_ | then go to IRC on the PC | 14:01 |
aradesh | what's wrong with being on IRC here? | 14:02 |
aradesh | easier to copy info? | 14:03 |
aradesh | i'll just email it to myself or something, not convenient to set IRC up on it rn | 14:03 |
diogenes_ | aradesh, in terminal run: sudo apt install hexchat | 14:04 |
aradesh | xD | 14:06 |
aradesh | alright alright | 14:06 |
diogenes_ | now when you start hexchat, it asks you to join a channel, there you type: #xubuntu | 14:14 |
aradesh | diogenes_: ok i'm on the pc | 14:15 |
diogenes_ | aradesh, first make sure your system is fully update: sudo apt update && sudo apt upgrade | 14:16 |
aradesh | okay. | 14:17 |
aradesh | ok that's done | 14:31 |
diogenes_ | so it upgraded some packages right? | 14:31 |
aradesh | yes it took all that time | 14:32 |
diogenes_ | ok reboot now and fingers crossed. | 14:32 |
aradesh | ok | 14:32 |
aradesh | unfortunately i can't get my previous strategy to get it to boot up normally to work again | 14:54 |
aradesh | still no luck | 15:23 |
=== tomreyn_ is now known as tomreyn | ||
aradesh | diogenes_: hiya. i didn't have any luck. and my strategy for getting it back to boot up normally, i can't get it to work again. | 16:11 |
aradesh | maybe the computer is just broken | 16:11 |
diogenes_ | aradesh, but can you get to the TTY as before? | 16:15 |
aradesh | yeah yeah i can boot up with recovery mode too, and run terminals from there | 16:17 |
aradesh | i think it's when nomodeset isn't on that it doesn't work. | 16:20 |
diogenes_ | aradesh, ok boot with recovery and connect to internet and get to IRC. | 16:32 |
aradesh | yep. i am | 16:32 |
diogenes_ | aradesh, ok in terminal run: sudo apt install inxi | 16:43 |
diogenes_ | and btw ping me because im multitasking | 16:44 |
aradesh | diogenes_: done | 16:44 |
diogenes_ | inxi -Fc0 | nc termbin.com 9999 | 16:45 |
diogenes_ | share the url | 16:45 |
aradesh | https://termbin.com/6cj1 | 16:46 |
aradesh | diogenes_: ^ | 16:47 |
diogenes_ | aradesh, so when did you install the system? | 16:51 |
aradesh | i think around sep 2020 | 16:51 |
aradesh | diogenes_: ^ | 16:51 |
aradesh | no... | 16:51 |
aradesh | sep 2019 | 16:51 |
diogenes_ | yes i thought it was 20.04 but it's 18.04, run: ls /usr/share/xsessions/ | nc termbin.com 9999 | 16:55 |
aradesh | diogenes_: https://termbin.com/6cj1 | 16:56 |
diogenes_ | it's the previous one | 16:57 |
aradesh | oh, sorry | 16:58 |
aradesh | diogenes_: https://termbin.com/u4pm | 16:58 |
diogenes_ | so why do you have awesome installed? | 16:58 |
aradesh | i just chose to use it | 16:59 |
aradesh | no special reason | 17:00 |
diogenes_ | maybe this has something to do with your issue, sorry i know nothing about other window managers. | 17:02 |
aradesh | no problem. thanks for taking the time to help me investigate. | 17:05 |
Stan123 | Hi, I wish to replace my old Xubuntu 18, i386 with Xubuntu 20, amd64. I use a DVD and try to preserve other systems installed on my computer and, as far as possible, programs under Xubuntu. I stopped the instalation at option 3 (modify existing partitions) before saving boot loader on my disk without assertion it won't affect GRUB. Unfortunately, | 18:17 |
Stan123 | there is no strait option to upgrade or replace old system preserving mounting points etc. So, can I safely proceed to replace old version of the system without loosing anything? | 18:17 |
=== coconut_ is now known as coconut |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!