[00:03] sparr: tomreyn not sure if you've seen this: https://www.dell.com/support/article/us/en/19/sln302674/updating-to-the-latest-ubuntu-kernel-for-on-an-oem-dell-image-may-disable-some-components?lang=en [00:05] And for anyone else researching the original OEM Dell installs, seems you need to Dell Hosted Recovery Image ISO which should be found via https://www.dell.com/support/home/us/en/19/drivers/osiso/ and combined with the instructions at https://www.dell.com/support/article/us/en/19/sln301761/how-to-use-the-dell-hosted-recovery-image-of-linux?lang=en [00:05] hello I tried installing ubuntu 18.04 lts on a dual boot machine (already had ubuntu 16.04) and during install program wanted eif partition which I didn't have so pc never booted [00:06] TJ-: no, i hadn't seen this. but i guess disabling secure boot is fine for most users anyways. [00:06] I then created a usb flash os through ubuntu 16.04 lts "try ubuntu". I created a efi partition before creating an ext4 partition in which I installed ubuntu 18.04 lts [00:07] my secure boot is turned off [00:07] I wiped my original ubuntu partition before installing [00:07] tomreyn: it seems orthogonal to the problem of a kernel upgrade on its face. Maybe the inference is out-of-tree DKMS packages are built for the new kernel and aren't signed [00:08] any ideas? [00:09] ax562: sounds like originally 16.04 was booting in BIOS/MBR mode and then 18.04 installer booted in UEFI mode and therefore wanted to install for that mode as well, and couldn't find, nor create, an existing EFI system partition [00:09] TJ-: hmm yes, this can be. i'm not sure what to make out of it other than 'prefer linux-generic if you can' [00:10] tomreyn: indeed... and seems like Dell customers have to jump through hoops to get the installed image... i wonder where the source is hosted (GPL requirement) [00:10] Tj: Thanks. I did create efi partition the second install and still didn't work [00:11] I was running dual boot with windows 8.1 [00:11] everything was working great [00:11] ax562: did the installer report no errors? have you verified there's an "ubuntu" entry in the PC's manual boot menu ? [00:11] I am running a dell :) [00:12] TJ- I just booted in 18.04 usb flash and there was an "efi ubuntu" option [00:12] Tj: ^ [00:12] ax562: the last thing the installer does (in UEFI mode) is call "efibootmgr" to add the Ubuntu entry to the PC's boot menu [00:13] Im running this all off ssd drive with 4 different paritions [00:13] ax562: so first thing I'd do is boot the PC and press the key that brings up the PC's manual boot menu and see what is on it (or enter firmware Setup and see if you can view the entries in the boot menu) [00:14] under efi I have two options "boot off ubuntu" or "ubuntu flash" . "boot off ubuntu" doesn't work [00:14] I do not get grub2 options like before where I can choose either ubuntu or windows [00:15] ax562: did you maybe make changes to your bios setup before you started installing ubuntu 18.04? [00:15] no [00:16] I'm having problems running steam through a proxy... any ideas? [00:17] insom^: That's not something this channel can support. Please seek out one of Valve's customer support forums for assistance [00:17] note to self: when system suddenly runs slow the battery is exhausted and PC is about to shutdown! [00:17] all I did was boot into usb flash image and in "something else" option I first just created an ext4 at the end of my ssd hd. Ubuntu told me it would not boot without efi partition. I proceeded and it did not boot. [00:17] TJ-: heh :) [00:17] under efi I have two options "boot off ubuntu" or "ubuntu flash" . "boot off ubuntu" doesn't work [00:17] I do not get grub2 options like before where I can choose either ubuntu or windows [00:18] ^ TJ- welcome back, this is what you missed. [00:18] pragmaticenigma its linux specific... I don't have the problem in windows... its a proxy setup issue [00:18] tomreyn: thanks a lot ! [00:18] btw I appreciate all the help y'all! [00:18] insom^: It's still not an Ubuntu support question. Software provided through the Ubuntu Software Center is supported, applications installed from outside that network are not supported [00:19] Ubuntu 16.04 lts was running flawlessly. I decided to finally upgrade and boom, i'm down. [00:19] it's always a good learning experience though [00:19] ax562: you said there are multiple storage devices in that PC? It is possible the firmware itself cannot access the device with the EFI-SP on ... unusual but not unheard of, especially if the boot device was not factory installed or is not regular SATA (e.g. after-market NVMe) [00:20] I was expecting a smooth transition. doh [00:20] TJ-: also: ax562: did you maybe make changes to your bios setup before you started installing ubuntu 18.04? no [00:20] :D [00:20] ubuntu 14.04 FTW [00:20] haha [00:21] ax562: *usually* if the PC firmware cannot access the storage device efibootmgr will fail with an error about unknown blk device [00:21] Tj: not sure. I'm booting off ssd. original hd drive is still in the lappy. I just use it for audio and video game processing :p [00:22] ax562: saw this recently installing into a Windows Hyper-V Linux guest where I'd used PCI-passthrough to attach 2 NVMe storage devices [00:22] yo ubuntu users dont hate bob marley [00:22] TJ: interesting [00:22] I believe that is my setup [00:22] how can I view all usb information, I think this usb device is bootlooping but not sure how to use the loggin without dmesg [00:23] *logging [00:23] like the equivalent of tail -f /var/log/dmesg | grep USB [00:23] It's ssd 256 gb drive through mini-sata port [00:23] /set irc.server.freenode.globalkill on [00:24] It was running fine with ubuntu 16.04 though [00:24] !ot | zylop [00:24] zylop: #ubuntu is the Ubuntu support channel, for all Ubuntu-related support questions. Please register with NickServ (see /msg ubottu !register) and use #ubuntu-offtopic for other topics (though our !guidelines apply there too). Thanks! [00:24] ah you welcome [00:25] can I use terminal in any way to maybe identify issue or atleast provide more info? [00:26] Mibix: i'm not sure of a single command, but besides "usb" you can grep for "hci", and then for whatever the device provides, i.e a mass storage device would provide storage [00:27] right now I have an ssd with 4 different partitions. first is small 300 mb system partition, second is windows, third is 200mb efi partition and fourht is ext4 partition (18.04 lts installed). [00:27] ax562: "efibootmgr -v" if booted in UEFI mode to report the PC's boot menu entries including paths ot files [00:28] Tj: https://pastebin.com/1wn6k0Tv [00:29] ax562: sudo parted -ls | nc termbin.com 9999 or sudo fdisk -l | nc termbin.com 9999 may also be of help. [00:30] tomreyn: sudo parted -ls | nc termbin.com 9999Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes.https://termbin.com/g7x0y [00:32] so neither the 320 GB seagate disk (sda) nor the 250 GB samsung SSD have a a GPT partition table [00:32] tomreyn: https://termbin.com/dosm5 [00:34] only the WD My Passport 4TB disk (sdd) has a GPT [00:34] tomreyn: how can you tell? Do they need them? [00:34] GPT would be needed to do UEFI booting. [00:34] tomreyn: that is used for storage mostly [00:34] I used PIP to install a package and have to specify the PIP PREFIX in a .conf file. If I didn't specify a prefix, what would it be? /user/local/ ? [00:35] the line in the .conf file reads: local_blocks_path = {PIP_PREFIX}/share/gnuradio/grc/blocks [00:35] Is that the only way I can boot 18.04 lts? [00:36] ax562: ubuntu 18.04 LTS can boot in either UEFI or legacy BIOS mode. from what you said I understood that you were trying to install Ubuntu 18.04 so that it would boot in UEFI mode. [00:36] I used "pip install digital_rf" at the terminal and didn't specify any location [00:37] tomreyn: that is what I thought I should install it in. That's what I thought 16.04 lts installed as. [00:37] ax562: but since UEFI and BIOS booting are incompatible to one another, and you're doing multi-boot, you will need to install any operating system in one of the two modes, and the same one. [00:38] tomreyn: how can I tell which type each hd is? [00:38] ax562:i thionk you had windows 8.1. installed in BIOS mode, because i don't see a bootable EFI partition. if you would like to continue using this existing installation then the ubuntu installer will need to be booted and installed in BIOS mode, too. [00:39] ax562: look for "Partition Table:" at https://termbin.com/g7x0y [00:39] how can I do that? [00:39] !dualboot [00:39] Dual boot instructions: x86/AMD64: https://help.ubuntu.com/community/DualBoot/Windows - Macs: https://help.ubuntu.com/community/MacBookPro https://help.ubuntu.com/community/YabootConfigurationForMacintoshPowerPCsDualBoot [00:42] tomreyn: I'm more confused lol [00:43] ax562: so to keep the windows installation usable, you need to make your mainboard firmware ("bios") boot the ubuntu installer media in legacy bios mode. how to do this exactly depends on your mainboard and its firmware. if the installer wants to create an EFI partition (ESP) then it is booted in UEFI mode, not what you want. [00:43] tomreyn: I see that both "partition tables" are msdos. Does that mean they boot from BIOS? [00:44] ax562: if partition table is "msdos" it means that they are not "gpt" and thus no UEFI boot is possible off them, i.e. they cannot contain a bootable efi system partition. [00:45] I do see a "Legacy usb boot option" when I boot from "uefi usb flash". [00:45] ^when I boot into install [00:45] hmm, it could be that. [00:46] tomreyn: that's not strictly correct; UEFO spec does mandate support for MSDOS/MBR :) [00:46] TJ-: doh, ok, i have never seen this happen though, have you? [00:46] TJ: thanks, even more confuse :) [00:46] Yes :) [00:47] okay, then i'm happy to pass over to you again ;) [00:47] tomreyn: the problem is many firmware authors do not read the spec and don't support it (despite it being in the EDK) so many folks assume UEFI doesn't support it [00:47] Ok so since both hard drive partition tables are msdos this mean both have to boot non eif boot loader? [00:47] tomreyn: I was just providing info ... I have to go to bed :) [00:48] Tj: thanks! [00:48] TJ-: :) ok, i'll try to not let this additional info confuse me now, thanks though. [00:48] lol [00:49] tomreyn: welcome to the confused club. [00:49] ax562: you can run this from the live / installer system: echo -n 'This system booted via: '; [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS [00:50] fiddle with the mainboard firmware configuration until it says "BIOS", then do the installation. [00:50] echo -n 'This system booted via: '; [ -d /sys/firmware/efi ] && echo UEFI || echo BIOSThis system booted via: UEFI [00:50] and, of course, have backups [00:50] but that is giving me my flash drive info though? [00:52] ax562: /sys is a virtual file system, and a way to interact with the uefi firmware. this is only available when the system has booted in uefi mode, so this is a way to test how this system booted. [00:52] tomreyn: I have a clean backup of dual boot windows and 16.04 :) [00:52] good [00:52] tomreyn: wouldn't "this system" be "usb flash drive" though? [00:52] since that is what I booted into [00:53] yes, and if the usb flash drive contains the ubuntu installer then that's exactly what you need [00:53] it need to boot in the same mode you'll install in [00:53] ax562: no, tomreyn is talking about the *PC* which contains the boot firmware. [00:53] and you'll need to install in the same mode windows was installed in. [00:53] that's what I've been using to install ubuntu 18.04 [00:53] ax562: it's the code in the eeprom/flash on the motherboard [00:54] TJ: this is what checked it ? "echo -n 'This system booted via: '; [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS" [00:55] ax562: yes, it indicates what mode the motherboard firmware booted the system in [00:55] so does that mean that windows and ubuntu also boot using "uefi"? [00:55] ax562: we have to do this since in most cases an UEFI system has a Compatibilty Support mode (CSM) aka BIOS mode it cal fall back to using [00:56] cal -> can [00:57] ax562: so if there were no OS installed in UEFI mode (so no files in EFI system partition and no entry in the boot manager) it may fallback to BIOS/MBR mode and read sector 0 of the 1st boot device [00:57] TJ: so does that mean my system is configured for "UEFI" but it's been using "BIOS"? [00:58] ax562: possibly but the mode of the *current* boot doesn't indicate what mode *other* OS installs will use ! [00:58] if that's the case it didn't like sector 0 because it never booted [00:58] ax562: if you boot from the Ubuntu ISO live installer it will most likely boot in UEFI mode [00:58] TJ: I see [00:58] I'm installing Ubuntu 18.04 on 120GB SSD and I have additional 1TB HDD. [00:58] That's what I'm in right now [00:59] do I need to do something special during installation on the SSD? should I move some things to the HDD like the user home? [00:59] ax562: in which case *if* it is in UEFI mode right now "efibootmgr -v" can report all the entries in the motherboard firmware's boot menu [01:00] Tj: https://pastebin.com/1wn6k0Tv [01:00] neat, I havben't seen efibootmgr -v before [01:01] ax562: and there you go. Look at the BootOrder shows 0000 is the first to be tried, and that has "Boot0000* ubuntu HD(4,MBR,0x93d7aabb,0x1701d000,0x64000)/File(\EFI\ubuntu\shimx64.efi)" [01:01] bencc1: if this is the only operating system you will have then i'd just install it to the SSD and maybe add the HDD as additional storage later. it's probably the easiest way to go about it. [01:02] Tj: What does that mean? [01:02] bencc1: also, still if it'S the only operating system, then i suggest you prefer a UEFI installation over a BIOS installation wince UEFI is replacing BIOS nowadays and you'd thus gain forward compatibility. (it's not super important though.) [01:03] tomreyn: yes, I'll only have ubuntu installed [01:04] Tj: so what I was thinking of doing is deleteing both "efi" and "ext4" partition and rebooting into "Legacy usb" mode and hopefully get 18.04 lts installed that way. [01:04] tomreyn: never heard of UEFI installation. [01:04] tomreyn: should I put my user's home on the HDD? [01:04] bencc1: also make sure you're using a recently downloaded ubuntu installer, i.e. 18.04.3. [01:04] tomreyn: yes. I have 18.04.3 [01:05] ax562: notice the "MBR" in there telling us it is (trying to) read from partition 4 on an MBR [01:05] Tj: but it can't since it's efi right? [01:06] bencc1: HDDs are a lot slower than SSDs, as you know. if most of the data you'll move around will sit in /home then maybe you don't want this on the HDD. on the other hand, you may want to have a lot of space for the HDD. your mileage may vary. [01:06] * tomreyn senses that TJ will not get to sleep anytime soon [01:07] ax562: in theory it should :) tomreyn is correct... I have to go to bed... nursing a Migraine here [01:07] tomreyn: I have a lot of data and I thought that it's best practice to separate the OS from the data anyway [01:07] Tj: Thanks for all the help! [01:08] tomreyn: ax562 maybe use the currently booted live env to create a chroot on that installed system and test/fix from the chroot [01:08] tomreyn: thanks also. I will try this and report back :) [01:08] ax562: "lsblk" to identify the device name of that EFI-SP [01:08] ax562: unless this is a server, not really. [01:08] ax562: ignore what i just wrote, wasnt for you [01:08] brb [01:08] bencc1: unless this is a server, not really. [01:13] ax562: e.g. if you find the EFI-SP is /dev/sdc4 then you could do "sudo -i" then "DEV=/dev/sdc; P=4; mkdir /target; mount ${DEV}${P} /target; for n in proc sys dev; do mount --rbind /$n /target/$n; done; chroot /target mount -a; chroot /target grub-install -v ${DEV}; chroot /target update-grub;" and check for errors and resolve them [01:13] (i know they've gone but I have to go) [01:14] i really don't think this system booted either ubuntu 16.04 or windows 8.1 in uefi mode. [01:15] does windows give an option to change to uefi? [01:15] somehow i have this feeling that it is possible, post install [01:15] and the ESP is just there because of the failed 18.04 installation with custom partitioning on an existing MBR / mdos partitioned storage [01:15] yes, there's some utility for windows to do the conversion [01:16] tomreyn: my guess is that "EFI-SP" is actually the installed system's ext4 root-fs [01:16] TJ-: which installed system? [01:16] tomreyn: Boot0000 (which I assume is the 18.04) [01:18] this is why I think mounting that file-system and checking it will reveal the issue [01:18] Boot0000 is what an ubuntu installer, booted in uefi mode, would create on a disk which is MBR partitioned, if it noticed it was booted in uefi mode, and needed to install on this disk [01:19] No, as far as I can tell Boot0000 is the installed system, Boot000A is the currently booted live installer [01:19] ...and it was not taked to create a new partition table there, due to the user choosing to partition themself [01:20] *tasked [01:20] well, either way, i think we can agree this won't work as it is [01:21] it *theoretically* could, but probably won't. :) [01:22] yeah :D [01:22] right, I'm off! [01:23] back [01:23] Things are looking promising :) [01:23] good, good :) [01:23] woot [01:25] what do y'all think of 16.04 vs 18.04? [01:28] ax 20.04 is almost out! [01:32] oh wow lol [01:32] I might just be running this for a few months lol [01:33] it may take until late summer until you'll be able to upgrade 18.04 LTS to 20.04.1 LTS. [01:40] Hello when I alt-tab between windows' it flickers, does anyone know how I can fix that>? [01:42] !details [01:42] Please elaborate; your question or issue may not seem clear or detailed enough for people to help you. Please give more detailed information; for example, we might need errors, steps, relevant configuration files, Ubuntu version, and hardware information. Use a !pastebin to avoid flooding the channel. [01:45] Well I alt-tab between fullscreen emacs/firefox and it flickers, it doesn't flicker when I alt-tab between 2 emacs windows [01:45] by flicker I mean that the emacs window comes up but for a brief moment I catch a glimpse of the firefox windows [01:46] This didn't happen in 19.04, before upgrading [01:52] p0a: i've got to leave it there for now (need sleep), but for anyone to help it'd help to provide at least the ubuntu release you're currently running ( lsb_release -ds ), the graphics hardware you have there and the driver you're using ( lspci -knn | grep -A3 VGA | nc termbin.com 9999 ) [01:55] tomreyn: thank you [01:57] here is that information: https://pastebin.com/KMpuEwB8 [02:00] p0a: when did you first start noticing this? [02:00] p0a: I've heard the recent i915 security fixes introduced performance problems [02:00] indeed, certainly for the 2nd gen [02:01] sarnold: when I upgraded to 19.10 [02:01] which was a couple weeks ago [02:01] p0a: oh, hmm. that might be unrelated then [02:01] but .. it runs, so that is great. [02:01] I haven't rebooted into a new kernel lately so I'm not sure just how bad it gets [02:02] I was kinda mad about that upgrade [02:02] I kept getting messages pestering me about upgrading to a new version of ubuntu [02:02] only to be tricked into upgrading from LTS to 19.10 [02:03] i think it is due to the newer intel-microcode [02:03] I also cancelled the upgrade with the 'x' button but my sources.list did not revert back to normal [02:03] so my next apt-get upgrade triggered a full upgrade [02:03] p0a: ew :( [02:04] sarnold: yeah it was a wombo combo [02:14] Anyone know why nouveau (nvidia open source driver) does not work with Ubuntu? If I leave modeset enabled, Xorg uses the modesetting driver. If I set nouvea.modeset=0, nouveau attempts to load but fails because /dev/dri/card0 does not exist [02:14] Note: This is being experienced with all currently released Ubuntu livecds [02:15] kinda hard to use open source when the open source option doesn't work. [02:18] meh i'll just bite the bullet and use proprietary - this is exactly why open source will never win [02:19] what happens when you do the install and don't install the extra drivers? [02:21] Kow: "nomodeset" disables Kernel Mode Setting. No external driver will load, in addition to other things also disabled. Have you tried the proprietary driver for you rcard ? [02:21] Bashing-om: I don't want to use proprietary. If i wanted to use proprietary i'd just delete linux and go back to Windows. [02:21] So nouveau is broken? and nouveau is the only open source nvidia driver (aside from modesetting)? [02:22] so 2+2 -> there is no working open source linux nvidia driver? [02:23] Kow what videocard is this? [02:24] take your pick.. tried on multiple computers: GeForce 1070M (laptop) or GeForce 1650 (desktop) [02:24] Kow: "sysop@x1804mini:~$ lspci -k | grep -iEA5 'vga|3d' >> GK208B [GeForce GT 710] >> Kernel driver in use: nouveau" No issues here with nouveau:) [02:24] for the record, AMDGPU works rock solid out of the box [02:25] man linux has taken a 180 over the last decade. ATI/AMD used to be the joke now it seems to be nvidia [02:27] maybe your system needs a os option https://iam.tj/prototype/enhancements/Windows-acpi_osi.html [02:27] but nomodeset should work on both cards i guess. [02:27] Kow: compiz turnaround [02:29] guys I have tried the ubuntu livecd on multiple computers with nvidia cards and 100% of them have failed to use nouveau in the ubuntu livecds [02:29] This is an ubuntu problem, not hardware [02:29] (nouveau works fine in archlinux) [02:29] (on all referenced computers) [02:30] interesting, what is the difference? old kernel/i915 ? === [diablo]4 is now known as [diablo] === zbenjamin is now known as Guest45726 === zbenjamin_ is now known as zbenjamin [02:33] not sure.. ubuntu applies so much sauce to their kernels I'm sure that is where the issue is [02:33] easy solution.. delete ubuntu livecd and use archlinux i guess [02:35] half the internet is stating nouveau.modeset=0 is needed for nouveau to load, but the other half of the internet says modeset must be enabled for nouveau to work. So i guess that means novueau just doesn't work since there is no 3rd option - either modeset is enabled or it isnt [03:19] Anastasius [03:20] edenist: can we help you? [03:20] sorry lotuspsychje_, wrong chan ;-) === Leion1 is now known as Leion [03:31] Hello! Wondering if anyone can help me with an installation issue I'm having. I'm trying to install Ubuntu 18.04.3 LTS on a HP ProLiant DL360 G7. During the initial boot I receive the error "can't load firmware file bnx2/bnx2-mips-09-6.2.1b.fw" ... I was able to locate the firmware files and I've tried placing them in the root directory and into [03:31] /firmware directory that I made on the USB drive that has the install for Ubuntu. For some reason the install can't find the file and I'm wondering if anyone has some suggestions on how to get the install to see the firmware file. Thanks in advanced. [03:36] seems like this issue https://unix.stackexchange.com/questions/350350/ubuntu-16-10-not-recognising-bnx2-network-interfaces === westor{off} is now known as westor [03:38] yep but i'm trying to install the firmware during install [03:38] i was able to get it do it when I installed Debian 10 but I want to use Ubuntu now. I found this website that says place it in the root or /firmware but it's not seeing the filies [03:39] https://help.ubuntu.com/lts/installation-guide/arm64/ch06s04.html [03:39] you might want to reask in #ubuntu-server too [03:58] quick question, if i have a command like this : curl -X GET "https://api.coingecko.com/api/v3/global" -H "accept: application/json" <-- can i simply do a > filename and have the reply put into a file? [05:00] back [05:00] took a minute [05:01] After that fresh install I still couldn't boot. I had to reflash my hd back up. I'm up and running no in ubuntu 18.04 lts though :p [05:02] tomreyn: Thank you! [05:02] Tj: Thank you! === fcastillo_ is now known as fcastillo === benjaomi- is now known as benjaoming === davic_ is now known as davic === geheimni1` is now known as geheimnis` [07:18] thank you for flying #freenode [07:19] lol === lotuspsychje_ is now known as lotuspsychje [08:21] Due some odd reason my ubuntu 19.10 is not recognizing my external display anymore via HDMI [08:21] anyone who can assist me with this? All is up-to-date on OS level [08:22] Using the nvidia 435 driver. Also tried the native Nouveau driver but same outcome === anonimip_ is now known as anonymip [08:24] sorry, got a gnome restart so my browser closed [08:35] Dirkos: can you journalctl -f and plug out, back in your hdmi cable from your external screen and pastebin the output to the channel please [08:38] lotuspsychje empty [08:39] Dirkos: tryed another cable yet? [08:39] yeah, and my other notebook just works fine [08:40] Dirkos: how about the Fn key + screen switch F button? [08:41] lotuspsychje nothing [08:41] it is also not seeing the display at all in my settings [08:42] Dirkos: pastebin: sudo lshw -C video && uname -a please [08:43] lotuspsychjehttps://paste.ubuntu.com/p/xw5fg7TjTZ/ [08:43] lotuspsychje https://paste.ubuntu.com/p/xw5fg7TjTZ/ === ap5_ is now known as ap5 [08:45] Xrand is also showing me: HDMI-1-1 disconnected (normal left inverted right x axis y axis) [08:45] Dirkos: did this all happen after something, like updates for example? [08:45] yeah it auto updates sometimes [08:45] i lost all my icons after an update yesterday [08:46] but i recently had it after a kernel upgrade as well [08:46] somehow it uninstalled the gtk icons pack [08:46] reverted after that but that isnt working at this point as well [08:46] Dirkos: reverted? [08:46] Hey, I have a notice that there is an update of Linux-generic-hwe, I don't have any backups right now (my backup disks died), is this 100% safe, in current circumstances to install it? [08:47] konrados, yes, i noticed 5.3 for hwe too, upgrade went oke. [08:47] lotuspsychje booted the older kernel [08:47] oerheks, ok, thanks! [08:48] Dirkos: did you check your nvidia-settings? perhaps try switch powersaving vs performance if your card is optimus? [08:48] lotuspsychje yeah i checked nvidia-settings but no idea where to look there to be honest [08:49] i now set him to auto anyway (was performance all the time) [08:49] Also had some problems since wednesday, screen resolution was 1024x768 suddenly on a 1080p screen. Fix it by adding 1920x1080 again with xrandr [08:49] Dirkos: ok so last idea, try a liveusb see if you can make external work there [08:51] yeah dont really have any but ok [08:51] Im checking the nvidia forum threads as well and soo many people still complaining that it is not working with the same [08:52] I'm running ubuntu 16 with no GUI, how do I diagnose why I don't have any internet connectivity? [08:52] I'm running a USB wifi adapter [08:57] JadedJ: nmcli [08:58] JadedJ: "nmcli c" for saved connections, "nmcli d wifi list" to see available hotspots or "sudo iwlist scanning" [09:00] my internet was working fine for 2 days, [09:00] today it just suddenly stopped working [09:01] I'm running ubuntu server [09:05] so, those comands give no output? [09:05] !paste [09:05] For posting multi-line texts into the channel, please use https://paste.ubuntu.com | To post !screenshots use https://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. [09:05] JadedJ: Do you have nmcli available? Or iwconfig ? [09:07] nmcli tells me to install network-manager [09:07] Hard to do without network :P Can you use cable? [09:07] !pkg xserver-xorg-core-hwe-18.04 [09:08] !pkginfo xserver-xorg-core-hwe-18.04 [09:08] iwconfig says im connected to the access point [09:09] !info xserver-xorg-core-hwe-18.04 [09:09] xserver-xorg-core-hwe-18.04 (source: xorg-lts-transitional): Transitional package for xserver-xorg-core-hwe-18.04. In component universe, is extra. Version 3:14.5 (eoan), package size 1 kB, installed size 9 kB (Only available for amd64; arm64; armhf; i386; powerpc; ppc64el) [09:09] !help [09:09] Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience [09:09] Finally [09:13] JadedJ: Do you have a IP? Is your DNS set? Can you ping internal and external ? [09:14] JadedJ: Do you know what subnet you are on? Eventually set an temporary static ip, in case the dhcp server is not running. [09:14] lol whut [09:17] The subnet I'm trying to connect to is 192.168.1.0 [09:17] I already have an IP address and the wifi is connected to the access point [09:18] JadedJ: Can you ping the gateway? [09:18] But when I ping 8.8.8.8, it says the destination host is unreachable [09:18] I can't even ping the gateway [09:18] It might just be an issue with the driver [09:19] Shall I try unplugging the usb wifi adapter and plug it it back in? [09:20] JadedJ: Try that [09:20] But thats so fustrating though [09:20] JadedJ: how come? [09:20] I currently have this machine setup as a router [09:21] you could keep asing questions and not try that.. [09:21] It takes a wifi connection and shares it via the ethernet interface [09:21] JadedJ: Do the wifi and ethernet share subnet? [09:22] Maybe it's ip conflict [09:22] No differenet subnets [09:22] *different [09:22] It was working fine for 48 hours [09:22] Today it decided to just stop working [09:23] The wifi is controlled by wpa_supplicant and dhclient [09:23] I followed this guide, but adapted it for ubuntu 16 [09:23] https://www.ascinc.com/blog/linux/how-to-build-a-simple-router-with-ubuntu-server-18-04-1-lts-bionic-beaver/ [09:26] JadedJ: did you have to install a package to get the wifi adapter to work to begin with? [09:26] no [09:26] it worked out of the box [09:28] here is the info for the wifi adapter [09:28] configuration: broadcast=yes driver=ath9k_htc driverversion=4.4.0-171-generic firmware=1.4 [09:28] ^from sudo lshw -C network [09:29] sudo systemctl status networking might give a clue [09:31] hmmm [09:32] So I can ping the gateway now [09:33] But now I'm not sure which command fixed it [09:33] sudo service wpa_supplicant restart [09:33] or [09:33] there is something that keeps changing the permissions of '/opt/rclone/rclone.conf' to root ownership. how do i found out what is doing it [09:33] sudo service networking restart [09:33] I will wait till it goes down again in the future, and try one command and wait a while [09:35] Hopefully it won't :) [09:36] hope canonical can release an archlinux based ubuntu edition [09:38] Why? Archlinux exists already :) [09:38] ubuntu based on archlinux i mean [09:39] or arch based on ubuntulinux .. [09:39] come on, keep the channel free for support [09:41] I have HPE DL380 Gen10 with 6.7TB Disk size (SSD). When I install Ubuntu 18.04 server I see the full disk size, when I try to install Ubuntu 16.04 I only see 124.1GB of the size. Any thoughts? [09:42] Aviv: why do you need to use 16.04? it's EOL in about 15 months. [09:42] a server that new might require 18.04 to get full coverage. [09:43] ryuo, Because some project of TensorFlow that I need it to be on 16.04 [09:43] Aviv: could you use a container for that? [09:43] Nope, must be bare metal for deep learning [09:43] err... containers aren't a VM. they use the same kernel as the host. [09:44] I know I know, it's something very specific [09:44] did you try 16.04 with the HWE kernel? [09:44] Can't understand why 16.04 cannot see my full disk [09:44] Nope [09:44] Will try now [09:44] iirc, the boot media has an option to boot the HWE kernel. [09:45] i presume you're using the latest ISO for 16.04 server [09:45] .6 or w/e it's at now. [09:46] Yep [09:46] any difference? [09:46] On it now :) [09:47] https://askubuntu.com/questions/1012002/raid-disk-size-is-less-than-display-in-ssa-on-hp-proliant-dl380-gen10 [09:47] might be your answer [09:49] To use 04.3 then? [09:50] I'll try now with 06 first [09:50] newer should work. [09:50] that's minimum. [09:50] I am doing it via iLO so it a little bit slow [09:50] can't wait to see if it works, on it for 2 days already [09:51] Aviv: always try HWE if you have issues, especially with very recent hardware. === jelly-home is now known as jelly [09:55] Thanks ryuo!! Working [09:55] One more question - which is more stable CUDA 10-1 or 10-2? [10:00] Aviv: no experience with CUDA. [10:02] Thanks ! [10:04] Hey, i have a weird issue. I'm running Ubuntu LTS as a VmWare ESXI VM since one year back. Have worked great. Today not so much. Suddenly it is in read-only mode saying "Physical disk NOT OK BAD". [10:04] Have checked physical disk of server, no issues, everything else works fine. Rebooted the Linux VM and problem persist. Tried recovery mode. But can't even run FSCK there. [10:17] how do I disable the font scaling on ubuntu 18.04. [10:17] it is *never* ok to change it to 200 % in any configuration that I have... [10:18] and yet every time I change any display configuration, attach anything external I *always* get 200 % even though I *never* want it. === autra is now known as autrix === autrix is now known as autra [10:27] what you're saying is that you don't have a 4k display? [10:32]