[00:11] Well that was underwhelming... I rebooted and it wasn't broken, it started up normally. Without even running boot-repair or anything. I guess it's because when it asked about where to install the new GRUB I didn't select any drive. Oh well, that's good! Now, how do I undo the mess I created with this huge apt install? [00:12] Melissa_McC: Ok. === bazhang_ is now known as bazhang [00:14] hfp: Maybe Try ; ' sudo apt update ; sudo apt full-upgrade ; sudo apt -f install ' If all comes up clean then see that ' sudo dpkg -C " only returns to prompt . [00:15] hey everyone. this is a first time i'm seeing something like this! I am attempting to revive a friend's very old hard drive NTFS (Windows XP) hard drive. It's an 80GB IDE. I've managed to get the thing mounted but it appears like it's missing files and directories. Someone played with the drive before me, and it took many tries to get it to mount correctly. Anyone have any suggestions for us? [00:15] oh wait should I remove grub-pc and reinstall grub-efi and friends before? [00:16] Bashing-om: full-upgrade will upgrade every package, right? But it won't remove all the ones that my previous apt install <150 packages I don't really all need> did, will it? [00:16] hfp: It booted back up , so grub I expect is fine as is . [00:17] I think GRUB wasn't overwritten, but apt said it uninstalled grub-efi and friends while it installed grub-pc. Isn't that a problem for the future, when a new kernel will be installed/upgraded? [00:18] hfp: "full-upgrade" will install whatever the package manager deems needed for all packages on the current install . where as install -f ( fix broken ) will sure try and fix the system - whatever that may take . [00:18] Unless I'm missing something of course :) [00:19] I see [00:19] Alright, let me try that [00:20] michael_mbp: You can try doing a data recovery on it with Photorec/testdisk . Just make sure you recover the files onto a DIFFERENT drive. [00:20] michael_mbp: run sudo apt-get install testdisk [00:21] michael_mbp: And then run: sudo photorec (It should be fairly easy to use from there.) [00:21] That's what full-upgrade says: http://termbin.com/z0yk -- It's a surpring low number of packages, I would have expected a lot more to be there. Also, copyq? I'm using it but how is it needed by the current install? And no sign of grub-efi [00:23] michael_mbp: Also you will lose the filenames and directory structure but all the files that are physically on the drive will get recovered. Even files that were deleted and moved to the freespace. It will do a very complete recovery. [00:24] hfp: looking . [00:24] Bashing-om: Alright, I followed your instruction. full-upgrade reinstalled a few packages, -f install came back clean, and the dpkg command didn't output anything. [00:24] instructions* [00:26] oops I was talking to the wrong Michael. m1chael Please see message above [00:26] electricmilk: that looks like great advice! i'll try it out! [00:27] hfp what are you recovering from? [00:27] hfp: Good deal :) . as to copyq : Installed from PPA ( add-apt-repository ppa:hluk/copyq ) . // What now ' sudo dpkg -C ' ? [00:28] m1chael: No problem. Photorec works great. It's a freaking lifesaver but PLEASE remember to recover to another drive....VITAL you do this. [00:28] hfp, you may have removed the distro meta package [00:28] m1chael: Here is a little guide www.cgsecurity.org/wiki/PhotoRec_Step_By_Step [00:30] ChogyDan: recovering from installing all these extra packages I don't need. I have the command output here: http://termbin.com/w5l9. Should I apt remove anything that's under "The following NEW packages will be installed:" while reinstalling what's under "The following packages will be REMOVED:"? It seems that "The following additional packages will be installed:" is a subset of "The following NEW packages [00:30] will be installed:" [00:30] Bashing-om: sudo dpkg -C returns nothing and exits with 0 [00:30] hfp, what was the command that you ran that gave that output? [00:31] hfp: Seems then the system is stable and happy as is :) [00:32] ChogyDan: `sudo apt-get remove $(grep -vE "^\s*#" req_pkg | tr "\n" " ")`, req_pkg being this: http://termbin.com/p5e7 [00:33] hfp, omg, I don't understand that command. what are you grepping for? -dev packages? [00:33] ChogyDan: that command takes every line in req_pkg (the file I linked) and removes line returns so apt install has a long list of packages to install [00:33] The list of packages is from the file I linked [00:33] m1chael: what does ls -l at the HHD result out! [00:34] !orphaned [00:34] so it installed a ton of packages I don't need, but I can't just remove that list, because some packages are needed by my base system [00:34] or were already there before [00:34] hfp, ya, there is an orphaned package tool [00:34] Hence my idea to take the list from what apt install said it would do following that command [00:34] hfp, maybe gtkorphan [00:35] hfp, just make sure that you have the kernel and distro meta packages installed [00:37] ChogyDan: deborpan only returns this list: http://termbin.com/opto [00:38] hfp, I don't have ubuntu installed atm, but there was a command to look up a reverse dependency. [00:39] hfp, and gtkorphan has a lot more options... [00:42] Can anyone help me get rid of a perpetual graphics stutter on a fresh install of Ubuntu 16.04? [00:42] That's the thing, I don't think any of these packages are orphaned since I requested them to be installed how can the system tell I don't want them [00:43] hfp, I know how to do it in gtkorphan [00:44] hfp, I forget the option, but you add the packages to some ignore list. I don't have it open in front of me. Maybe right click, maybe in the options [00:44] DanteEdward: just state the issue in details. [00:45] ChogyDan: is it hibernated packages? [00:45] hfp, that rings a bell [00:46] the list is empty [00:47] hfp, well, you have to add packages to the list. You add the packages you want to keep, and then they are removed from the main list [00:47] My whole graphics feed keeps pausing approximately 3/sec, and I'm not even running anything that intense. I've got a GeForce GTX 970 and I'm using the v375.66 official proprietary drivers because the Additional Drivers tab doesn't offer anything else but the nouveau driver, which doesn't work at all for me. [00:48] ChogyDan: I don't understand what this does. I don't remember/know every package I want to keep... [00:48] hfp, right click the package and hibernate them [00:48] ChogyDan: which package though? [00:48] hfp, do you know the main ones you want to keep? Just the programs you installed [00:48] hfp, what distro? [00:49] ChogyDan: well not really, there are tons of packages installed that I need but I don't have a list off the top of my head. ubuntu 17.04 [00:49] I had the same problem on Mint. I formatted my drive and switched to Ubuntu to try and make the problem not a thing. [00:50] hfp, well, you want to hibernate the ones you installed, not any dependencies, if that makes sense. ubuntu-desktop should depend on everything in the main desktop linux-generic should depend on the latest kernel. === RaptorJesus is now known as FapperJesus [00:51] !info nvidia-375 xenial | DanteEdward [00:51] DanteEdward: nvidia-375 (source: nvidia-graphics-drivers-375): NVIDIA binary driver - version 375.66. In component restricted, is optional. Version 375.66-0ubuntu0.16.04.1 (xenial), package size 38895 kB, installed size 160232 kB (Only available for i386; amd64; armhf) === FapperJesus is now known as RaptorJesus [00:52] DanteEdward: do you have the same behaviour using the free nouveau driver! [00:52] DanteEdward: ^^ partners repo enabled on your system ? [00:52] RaptorJesus: I'm pretty sure there's pills that can help you last longer next time. [00:53] ChogyDan: not sure that's what I need though. I passed a long list of things to apt to install so it did install most of them. Now I want to remove antyhing from that list that wasn't installed before it ran. Not necessarily dependencies, some of these packages were directly installed. I have the list apt gave me before installing but I don't know if I should apt remove the list under "The following NEW [00:53] packages will be installed" or under "The following additional packages will be installed" [00:53] sary: I can't tell. My screens won't turn on when I boot with the nouveau driver. [00:54] Bashing-om: I'm VERY new to Linux. I have no idea what a "partners repo" even is. [00:54] hfp, are you sure $(grep -vE "^\s*#" req_pkg | tr "\n" " ") works properly? [00:56] Bashing-om: I have no idea what ChogyDan said just now, and I have no idea whether or not's it' someting advanced or elementary. [00:56] ChogyDan: yes, it basically takes every line in the req_pkg text file and puts it on one long line. So it's the same as doing `sudo apt install ` [00:56] DanteEdward, I was speaking to hfp, a different user [00:57] ChogyDan: but I don't want all these anymore. some of the packages were already installed, others were installed as a result of running this command. I want to remove them. [00:57] hfp, that's what I don't get. It doesn't look like the output of a remove command. It would be nice to see the command [00:57] I know. I was reffering to the terminal string you typed out. I have no idea what any of that could possibly mean. [00:58] ChogyDan: it was the output of an install command, which I'm ont trying to figure out how to undo [00:58] hfp, oh, so you saved that output, and that is what you want to undo [00:58] that's right [00:59] have you installed ubuntu=standard? [00:59] so I'm wondering which list should I take from that output for apt remove, the one under "The following additional packages will be installed" or the one under "The following NEW packages will be installed" [00:59] DanteEdward: how did you install the Nvidia driver! [01:00] DanteEdward: The 375 driver is in the repo. There has to be some reason why "additional Drivers" does not see it . One reason might be that the partner repo is not enabled ( is by default) . what shows the terminal command ' grep "partner" /etc/apt/sources.list ' ? [01:00] hfp, the new list lists all packages, as well as dependencies [01:01] ChogyDan: right, so that's the list I want to use for apt remove, or will it automatically figure out the dependencies from the other list? [01:01] hfp, the dependencies are already there, take a look [01:01] Bashing-om: 375 is in Additional Drivers, though. It's one of only two things there, the other being nouveau. [01:02] sary: I installed it through the Additional Drivers tab in the Synaptic Package Manager [01:03] ChogyDan: what do you mean there? there where? [01:03] DanteEdward: Now I am confused as your 1st post " Additional Drivers tab doesn't offer anything else but the nouveau driver " . [01:04] DanteEdward: Ok. [01:04] hfp, here: http://termbin.com/w5l9 all additional are listed as new [01:05] Bashing-om: For clarification, Mint offered four or five other options. It said that they were open-source Nvidia drivers. [01:05] It offered them in the Additional Drivers tab. [01:06] Ubuntu's only giving me two options: the proprietary NVidia driver and nouveau. [01:07] DanteEdward: ' cat /var/log/gpu-manager.log | nc termbin.com 9999 ' The result is a URL back in terminal, pass that link back here . We find out what is not going on . // ubuntu now only offers the latest nvidia drivers that will work for a given card . [01:08] ChogyDan: hmmm I'm still not sure if I should go with the list under "The following NEW packages will be installed" or the one further up under "The following additional packages will be installed" [01:08] ChogyDan: NEW is packages to insatll + dependencies to upgrade? [01:08] Bashing-om: http://termbin.com/vbsc [01:09] DanteEdward: reading . [01:15] DanteEdward: Looks good . I see no faults reported . What have we got actually installed ? ' dpkg -l | grep -i nvidia | nc termbin.com 9999 ' . [01:16] http://termbin.com/vayq [01:16] The problem was present before I installed anything. [01:16] ChogyDan: yolo, I removed the NEW list, and reinstalled the removed list. nothing blew up. I'm going to try and reboot, see what happens. see you on the other side. [01:17] DanteEdward: Here we go ! a driver conflict " ii nvidia-367 and ii nvidia-375 " . [01:18] I did attempt to install 367, yes [01:18] In an attempt to fix the problem that was already evident. [01:19] alright it seems like it went well. Thanks ChogyDan, Bashing-om, oerheks_, seems like everything is back to normal. [01:20] Next question: what's the recommended way of backing up a 17.04 laptop? [01:20] DanteEdward use normal repo driver [01:20] in case I screw up again I'll have a backup to restore [01:20] card is [01:20] hfp, yay, glad it worked [01:21] Dreaman: I don't know what you mean. If you mean the Nouveau driver, my screens will not turn on when I atempt to use Nouveau. [01:21] GLX Renderer: GeForce 940MX/PCIe/SSE2 [01:21] GLX Version: 4.5.0 NVIDIA 375.66 [01:21] work [01:22] DanteEdward: can be only one ! must remove one prior to installing another . Do ' sudo apt purge nvidia* ; sudo rm /etc/X11/xorg.conf ; sudo ubuntu-drivers autoinstall ' I do not expect xorg.conf to exist but just in case we want it gone . [01:22] I tried dejadup/ubuntu's backup utility but I wasn't impressed. It seems to only backup /home, and you can't even use it to restore on a fresh install. I'd rather make a full snapshop of the drive to another partition or something that I could restore. [01:23] Plus dejadup on 17.04 crashes my machine when it takes backups [01:23] hfp, I wish there was a better back up thing [01:24] ffs [01:24] Bashing-o.: /var/lib/dpkg/ is locked [01:24] And xorg.conf doesn't exist, according to the terminal. [01:26] DanteEdward: Got another instance of package management active at this time ? again there can be only one instance - one reason why ya get the lock advisory . [01:26] Oh, that's what causes that? [01:26] I has Synaptic open [01:26] DanteEdward: you can't have apt and synaptic at the same time , sudo rm /var/lib/dpkg/lock [01:26] had* [01:27] after that , you might need to sudo dpkg --configure -a [01:28] No need. [01:28] I closed Synaptic and the command is processing now. [01:28] Great! [01:28] DanteEdward: :) [01:32] Alright, command processed. [01:32] DanteEdward: reboot to see the effect . [01:32] Before I reboot [01:33] I'm accessing IRC through a browser because Hexchat isn't wanting to play nice [01:33] I put in Freenode's details, and I'm getting remotely d/c'd [01:34] I've got it running now [01:34] DanteEdward: never used hexchat , no experience to advise . sary ?? [01:34] And I'm getting an instant "connection reset by peer" each time it tries to connect [01:35] Yeah that's freenode web-interface , I would report that in #freenode , i use irssi . [01:35] So there's probably no way I can connect to Freenode with Hexchat, then? [01:36] DanteEdward, sure there is [01:36] DanteEdward, ask in #freenode and #hexchat [01:36] I'll try those inna minute, then. [01:36] ok [01:36] DanteEdward: Sure there is . it is just a config issue I bet . Many people here use hexchat . ( me too with irssi ) [01:36] i use to see it supported section on freenode website, have you checked there. [01:36] I'm gonna reconnect and see if this stutter's gone [01:37] eboot* [01:37] reboot* [01:37] ffs, learn to type, me. [01:44] I'm back. [01:44] And so is the graphics stutter. [01:44] wb. [01:45] The purge and autoinstall didn't fix the problem. [01:45] hey um [01:45] can anyone do me a quick favor [01:45] i just set up lighttpd [01:46] can anyone confirm if this link works? http://pareidolia.tk:92/mowindalawn.gif [01:46] my router is finicky [01:46] it works. [01:47] ty [01:48] DanteEdward: which nivida version currently in use $ $ dpkg -l | grep -i "NVIDIA binary driver [01:49] DanteEdward: Is X all happy ? what does the log file relate ? ' cat /var/log/Xorg.0.log | nc termbin.com 9999 ' . [01:50] sary: That command seems to be breaking my terminal. [01:51] Bashing-om: http://termbin.com/1k6l [01:52] DanteEdward: reading - I be a while . [01:53] DanteEdward: search for the available driver versions in the repo with $ $ sudo apt-cache search "NVIDIA binary driver" .. found a later one! [01:53] sary: I figured out what was wrong. NVidia binary driver v375.66 [01:53] well, it doesn't break mine. [01:54] So, v375 is the wrong one! [01:54] It does when you don't put " on the end. [01:54] And when you don't know how to linux [01:55] Case in point: me. [01:55] model video card is [01:55] Weel, we all learn something at one oint or another :) at least you're not lazzy as most newbies! [01:55] GTX 970 [01:56] work [01:56] my laptop [01:56] restart [01:56] Bashing-om Hey dude - I'm back...and ready to give my NVIDIA another try (holy cow - looks like Dante is working with the same thing0 [01:56] You've got the same graphics stutter issue? [01:57] DanteEdward - Nah... I *wish* it only stuttered.... every time the system updates, it knocks my drivers out of wack - and I can't boot to desktop!! [01:57] https://paste.ubuntu.com/25100834/ [01:58] see [01:58] Yikes D: [01:58] i use 2 [01:58] processor use 520 intel [02:01] DanteEdward: what is " VIZ D39h-C0 " ? You running with 3 monitors ? . what results when only one monitor is in use ? [02:01] intel 520 .. try the 'tearfree' and sna options https://askubuntu.com/questions/752743/ubuntu-16-04-skylake-6th-generation-screen-flickering [02:01] Dreaman ^^ [02:01] Melissa_McC: Remind me where we were . real short attention span here . [02:02] Bashing-om: I am running with three monitors, yes. [02:02] Bashing-om ok - I uninstalled the NVIDIA driver...and ensured nouveau was up to date... [02:02] VIZ D39h-C0 is my TV, hooked up by way of HDMI [02:02] DanteEdward: Just seems the driver is not happy with VIZ D39h-C0 . [02:03] Bashing-om but when I try to reboot - it takes me to black screen (with flashing cursor up top - but won't type) [02:03] Lemme see what happens when I disconnect it [02:03] Melissa_McC: What release are you running, and is there some issue with the nouveau driver ? [02:04] Bashing-om: Just disconnected my TV and I'm still getting stutter. [02:04] Bashing-om - it seems my GeForce 970 card doesn't like the default drivers - how do I get the release number? [02:05] Lemme disconnect my second monitor and give you another link, Bashing-Om [02:05] Melissa_McC: ' lsb_release -a ' . [02:06] Bashing-om: http://termbin.com/20wr [02:06] http://imgur.com/a/2mgHe oerheks_ 4k [02:06] work good [02:06] DanteEdward: pull the other monitor, reboot . Looking at the log file . X just is not in a happy state . Why, I do not know . [02:07] Huh. [02:07] Lemme reboot. I'll be back. [02:07] Bashing-om that cmd isn't working... (I tried 1sb_release -a ....and lsb_release -a) [02:07] Damnit [02:08] gnome-keyring-daemon keeps preventing me from shutting down [02:08] DanteEdward: " NVIDIA(GPU-0): VIZ D39h-C0 (DFP-1): connected" system still thinks that the TV is connected . [02:09] It is, physically. [02:09] I shut it off in the display menu though [02:10] Melissa_McC: that be a a ell (l) not a one (1) . " sysop@x1604:~$ lsb_release -a >> Description:Ubuntu 16.04.2 LTS " . [02:11] Can anyone help me make GKD quit stopping my shutdowns real quick [02:12] Bashing-om 17.04 [02:15] Hello [02:16] Can someone help me fix a ext4 fs please? I have booted from live disk and when i try to mount this drive i am getting "JBD2: Unrecognized features on journal, EXT4-fs (sda1): error loading journal". [02:16] I have a small 120G SSD that is full I have a bigger one what is the best way to migrate the data will DD be the best route. The drive is from my media server which is a dell poweredge I have a [02:16] It setup as a raid 0 === toothfairy_ is now known as toothfairy_zzz [02:17] Melissa_McC: Is this a desktop install or server ? - what do you normally boot too ? === Mrokii_ is now known as Mrokii [02:19] Bashing-om just desktop... and I found a good article... http://www.linuxandubuntu.com/home/how-to-install-latest-nvidia-drivers-in-linux (which I could follow - but I need to get netowrking !) [02:19] Can I just DD the drive and then go in with Gparted and extend out the root partition [02:19] Using a live cd [02:21] Bashing-om Each time I try to sudo apt-get something...I see "Temporary failure resolving..." [02:21] I wounder if DanteEdward has an intel CPU that has a built-in GPU! [02:21] Wb Melissa_McC . [02:21] sary Hey... [02:21] Melissa_McC: Well, yeah that is our trusted PPA. but why the PPA rather than the repo driver ? [02:22] Bashing-om ... you're asking that question like I'm supposed to know the difference ... :/ lol... [02:22] sary: I only see the one device for DanteEdward in the log file . [02:23] My old drive is showing up as /dev/sbd and the new one is /dev/sda [02:23] There is multiple partitions on the old drive [02:24] Bashing-om: we might want to see their syslog and dmesg , or simple ask. [02:24] Bashing-om I'm happy to try whatever ideas you may have :) [02:26] Melissa_McC: Then let us remain in our repo . // let me get a nigglong thought out of the way / do "you" have the authority to access your desktop ? ' ls -al .ICEauthority .Xauthority ' returns that you own and are grouped to these ? [02:26] So if I do dd if=/dev/sbd of=/dev/sda will DD copy the partitions? [02:29] Bashing-om Its my own computer (and I know the admin pass)...but that cmd returns: ls:cannot access '.ICEauthority.Xauthority': No such file or directory [02:30] Melissa_McC: that is 2 filkes . seperate the command targets with a space - .ICEauthority .Xauthority - . [02:31] Bashing-om after separating them I get two lines of the same :No such file or directory [02:32] Melissa_McC: " -rw------- 1 sysop sysop 9420 Jul 15 12:40 .ICEauthority " where I am sysop . [02:33] Bashing-om - are you asking me to type that in, or is that what the output should be? [02:33] Melissa_McC: Humm .. have you ever been able to get to the GUI ? [02:34] Bashing-om Yes. my normal gui is a beautiful picture...regular desktop (pass protected)... normallly works beautifully....BUT about every 60 - 90 days, I fight this battle with the device driver [02:34] Melissa_McC: That is what the output should be with "you" vice sysop . === toothfairy_zzz is now known as toothfairy_ [02:35] Melissa_McC: " -rw------- 1 sysop sysop 50 Jul 15 12:40 .Xauthority " . [02:36] Bashing-om Yeah - I'm not seeing that. Just the no such file error. (I'm at root@comp-name:~#) [02:37] Melissa_McC: Ho Kay ! root explains why not present :) [02:37] Bashing-om (I accidentally typed la -al the first time, and saw a list of access lines like the one you asked about... files like: .bash-aliases .bashrc .cache .config...etc....but no .Xauthority) [02:38] Bashing-om OK cool. so how do I get where you need to me to be? [02:38] Melissa_McC: So we are back to booting up and having networking - right ? [02:39] Bashing-om Yes, I got here to root via the recovery option in the GRUB [02:40] Melissa_McC: Rather than root, how about we boot into terminal as you from grub ? And there activate networking . [02:41] Bashing-om OK cool. How do I do that? === deathonater is now known as Smeef [02:44] Bashing-om Do you mean the cmd line in grub? (The one that looks like: GRUB> )? [02:45] that's grub rescue , i think he meant boot into normal mode ' ubuntu ' desktop . [02:46] sary I think he wanted me to boot into a cmd line terminal.... but I forgot how... something like hold F1 while its booting...or something like that? right? [02:47] Melissa_McC: Get out of root and reboot the system : terminal command : ' reboot ' . Get to the grub boot menu and there with the latest normal kernel selected to boot press the 'e' key for edit mode . -> boot parameters screen -> arrow down to the line starting with linux and across to "quiet splash" delete these terms and all after and insert the term systemctl isolate graphical.target . Key combo [02:47] ctl+x to continue the boot process to TTY1 . log in here with user name and password . advise when ypu are there . [02:49] you switch to a virtual console with Ctrl+alt+f2-6 wheile booted in normal mode. [02:50] sary: Melissa_McC :: Think the OP has tried the F1-6 acesses . no workie . [02:51] Bashing-om: Yeah , she might've tried to while in recovery mode as root. [02:52] I'm back [02:52] And the stutter seems to have been fixed [02:52] it's been awhile since i had to boot into recovery. [02:52] wb [02:52] Great! what was the fix? [02:52] I physically disconnected both of my monitors, and the problem disappeared [02:52] sary: Granted be much better from a console .. rather than from grub -> TTY . IF possible . [02:52] And it stayed gone after I reconnected them both and rebooted [02:53] Bashing-om: indeed :) [02:53] DanteEdward: and X's log gile is now clean . yes ? [02:53] file* [02:54] How do I check that? [02:55] Bashing-om OK - deleted the words "quiet splash" - and everything after those...and replaced them with systemctl isolate graphical.target : then ctl+x'ed out...and the screen turned purple... [02:55] Bashing-om ...and its still purple... [02:55] DanteEdward: ' cat /var/log/Xorg.0.log ' .Shorter and sweet now ? [02:56] DanteEdward: do you hapeen to know if your cpu has an integrated GPU , as in a an intel built -in GPU! [02:56] Melissa_McC: with Nvidia you want to the kernel boot nomodeset paramter. [02:56] Bashing-om (and when I first read your comment above to sary - I though you wrote "no wookie"...lol) [02:56] Melissa_McC: We have something real deeper goin on here . as at that point the kernel vesa driver is used ! [02:57] sary: My GPU is aftermarket. [02:57] !nomodset [02:57] And my mobo doesn't have any graphical capabilities [02:57] Well [02:57] Other than its own BIOS [02:57] sary YES! nomodeset is a term I vaguely remember from the last time I needed this fixed.... [02:57] Bashing-om screen is still purple.... [02:57] !nomodeset [02:57] A common kernel (boot)parameter is nomodeset, which is needed for some graphic cards that otherwise boot into a black screen or show corrupted splash screen. See http://ubuntuforums.org/showthread.php?t=1613132 on how to use this parameter [02:58] My mobo doesn't even have a VGA port built into it [02:59] is it home built desktop! [03:00] sary yes. [03:03] sary OK - read that post...and it didn't ring any bells for me...I'm pretty sure I didn't need to mess with that last time...the last time - someone here walked me thru installing the latest Nvidia driver - and it fixed it again (for about a month) until this week, when it updated and rebooted [03:04] Bashing-om Do I kill it ? Its still purple.... [03:05] Melissa_McC: I do have 17.04 in a test bed . I have the options to boot unity, wayland or gnome as the DE . which DE are you booting normally ? // To get out where you are now try ctl+alt+del . [03:08] Bashing-om Not sure what a DE is...? But when my computer starts - it goes directly to GRUB 2,02 and my only options for boot on that menu are Ubuntu , and "Advanced Options for Ubuntu" - which is the long list of versions [03:08] Bashing-om I don't see any Unity, Wayland or Gnome [03:10] Melissa_McC: Well, the options for the (D)esktop (E)nvironment are in a drop down in the log in bix from the icon . [03:11] Bashing-om Oh, I'm not getting to that log in at all! the pc hangs long before that login page! [03:11] Melissa_McC: noted , so what is the situation now .. are you able to login to the desktop enviroment , or you're not able to login , or you can't even reach the login screen! [03:11] sary no - I can't get to a log in screen at all. [03:11] so we are back to 0.. [03:11] Melissa_McC: Ouch ! // Houston we have a problem . [03:12] thah :) [03:12] um [03:12] deleting splash and quiet are good [03:12] but yuo need to delete the vt_handoff too [03:12] Bashing-om Yeah lol.... that's why I need you guys :P [03:12] i had that same issue [03:12] with black screen boot [03:12] its annoying [03:12] once you fix it, you can change it in /etc/default/grub [03:12] tsarompy yup. [03:13] yeah i dont know why we must have some sexy boot screen [03:13] thats my only beef with ubuntu [03:13] i like seeing my console so i know if anythings wrong [03:13] my fix was apt remove plymouth* and then editing /boot/grub/grub.cfg and taking out splash quiet and vt_handoff [03:13] then you need to edit /etc/default/grub and set uhh [03:14] let me check [03:14] Bashing-om that's why the only cmd line I could get was the one thru GRUB...root [03:14] uncomment GRUB_TERMINAL=console [03:14] now are you having issues besides plymouth [03:14] Melissa_McC: Kist to see what does happen let's try as sary advises ; At the grub boot menu 'e' key -> boot parameter scren -> linus delete ' quiet splash" and all after and insert the term nomodeset . crl+x . what results ? [03:14] can you get to your display manager or a tty login otherwise [03:16] Melissa_McC: I just scrolled up .. you mentioned havin' 3 monitors attached , what happens if you unplug them and try to reboot to ubuntu from grub .. also did you remove the second nvidia driver that you installed with .run .. [03:17] Bashing-om ok - lots of white words on black background...things like: Please append a correct "root=" boot option...... Kernel panic - not syncing: VFS Unable to mourne root fs on unknown-block [03:18] Bashing-om ....etc...etc... [end kernel panic - not syncing: VFS: Unable to mount root f s on unknown block (0,0) [03:18] lets stay in sync with the nomodeset for now , and see what changes. [03:18] sary ok- If you could say that again in 'human words'... [03:20] Melissa_McC: i meant we should try and take one step at a time. [03:20] I ran a DD from an 120Gb to a 256Gb the source drive was a RAID 0 pulled from a dell poweredge. There was only one disk in the raid group. I tired expanding out the / partition on the new drive using a live cd (gparted) it would not let me resize the partitions. The new drive has two other partitions on it. When looking at fdisk the drive has 120+Gb at the end of the drive. How to I expand out / [03:20] Bashing-om computer seems to have stopped...screen is still full of white words on black back... cursor blinking (but not with a regular cmd line)...and no text is going in [03:20] !sysreq | Melissa_McC [03:21] The new drive is currently installed on the server [03:21] !sysrq | Melissa_McC [03:21] Melissa_McC: In an emergency, you may be able to shutdown cleanly and reboot by holding down Alt+PrintScreen and typing slowly, in succession, R, E, I, S, U and B. For an explanation, see http://en.wikipedia.org/wiki/Magic_SysRq_key [03:22] So nothing changes when booting with nomodeset .. [03:23] Bashing-om ...that did nothing.... [03:23] lol [03:23] Melissa_McC, did you delete too much [03:23] when you edited the grub prompt [03:23] you just deleted quiet and splash right [03:23] sary well, technically, it was a differnt outcome... words on the screen....(as opposed to blank purple screen) ...but yeah - still didn't get to desktop [03:23] not the whole line? [03:23] Melissa_McC: the magic sysrq sequence did nothing ? [03:24] tsarompy Possibly. There was one more line under the quiet splash entry...that I deleted in full [03:24] lol [03:24] dont do that [03:24] hahaha [03:24] try again :) [03:24] just those words [03:24] not the line break or anything [03:25] just quiet, splash, $vt_handoff [03:25] Bashing-om yeah - did nothing (would have been cool - but nah - nothing) [03:25] tsarompy the other line was initrd ....I deleted that one too - but you say that's too much? [03:25] lol [03:25] yeah dont delete that [03:25] you need ur initrd [03:26] literally just those three words i listed above [03:26] dont worry about extra spaces just make sure those words are deleted [03:26] then ctrl+x [03:26] it should boot [03:26] Any ideas? Anyone? [03:26] tsarompy Ok cool....putting nomodeset in there...and keeping my (evidently) important initrd... [03:26] um [03:26] you dont need nomodeset [03:27] just delete splash quiet and $vt_handoff [03:27] it'll auto adjust your resolution after a few seconds [03:27] Melissa_McC: You see a line similar " linux /boot/vmlinuz-3.2.0-24-generic root=UUID=dbd69ed2-530c-4409-8f5a-a3f1ea41fc67 ro quiet splash $vt_handoff " . all you replace is the quiet splash ( and maybe all after ) . all else we use on the current boot . [03:28] i had issues with $vt_handoff as well [03:28] i dunno bruh whatever works [03:29] tsarompy OK - I had already hit ctl-x - and its working...and seems to be busy (lots of words...and even lots of [OK] 's...) [03:29] :D [03:29] is this a fresh ubuntu install? [03:29] zesty zapus im assuming [03:29] im on zesty x64 [03:30] if you have a display manager installed, its probably gonna take a minute to boot into it so dont freak out [03:30] tsarompy Not especially fresh - been running Zesty for several months... [03:30] okay well [03:30] you can edit /boot/grub/grub.cfg and remove those three options so you dont have to do this every boot [03:30] BUT [03:31] any updates to the kernel or a few other things will overwrite grub.cfg [03:31] tsarompy OK - its now saying ""You are in emergency mode ... press enter for maintenance or CTL-D" [03:31] but you know what to do now [03:31] you booted the emergency one? [03:31] any reason why [03:31] like did you actually boot into recovery mode or was there a problem [03:32] if you press enter it should drop you into a root shell [03:32]