[08:27] <croraf> Hi. I have a very new laptop. I managed somehow to install 18.04 but it crashed soon after install. I cannot install "19.10" and "20.04 daily build", not even with "acpi=off" nor "nomodeset" nor 
[08:28] <croraf> "modprobe.blacklist=nouveau"
[08:28] <croraf> nor "modprobe.blacklist=intel-lpss-pci"
[08:28] <croraf> what should I do?
[09:01] <lotuspsychje> croraf: wich graphics card?
[10:01] <tomreyn> do a bios upgrade first of all. by then you'll also know which exact model you have, and can tell us.
[10:01] <tomreyn> croraf: ^
[10:02] <tomreyn> oh looks like you posted to #ubuntu as well
[11:12] <croraf> lotuspsychje tomreyn I have Nvidia RTX 2080, I already upgraded bios from AMI F.15 to AMI F.16 - latest
[11:14] <croraf> the news is I managed to boot live ubuntu 18.04.3
[11:14] <lotuspsychje> !nomodeset | croraf 
[11:14] <ubottu> croraf: 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
[11:14] <croraf> with nomodeset and modprobe.blacklist=nouveau
[11:14] <lotuspsychje> RTX cards might need the latest nvidia drivers
[11:14] <lotuspsychje> !nvidia
[11:14] <ubottu> For nvidia and matrox graphics cards, see https://help.ubuntu.com/community/VideoDriverHowto . For AMD/ATI graphics cards, see « /msg ubottu ati » and « /msg ubottu fglrxmissing » For the latest Nvidia drivers see https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa
[11:14] <croraf> I tried nomodeset already on each version
[11:15] <croraf> nomodeset is set when you try (safe graphics) also
[11:15] <lotuspsychje> uefi or legacy?
[11:15] <croraf> I think it is UEFI
[11:15] <lotuspsychje> try booting legacy/nomodeset
[11:15] <OerHeks> RTX2080 needs nvidia 410 or up
[11:15] <OerHeks> i would try 19.10 with kernel 5.3.x
[11:19] <croraf> I tried 19.10 even worse result
[11:20] <croraf> cannot even boot live with any parameter tries
[11:20] <croraf> nomodeset, blacklist=nouveau, acpi=off... | OerHeks
[11:20] <croraf> same with 20.04
[11:21] <lotuspsychje> cannot boot..stuck where exactly?
[11:22] <OerHeks> maybe you need this page, https://iam.tj/prototype/enhancements/Windows-acpi_osi.html
[11:23] <lotuspsychje> croraf: this isnt a ryzen system or so?
[11:26] <croraf> lotuspsychje | cannot install at all, with nomodeset (safe graphics) installation shows ACPI error and ACPI boot error, and then crashes
[11:26] <croraf> with nomal graphics, it crashes after 1 sec with broken screen
[11:26] <croraf> It is HP Omen
[11:26] <lotuspsychje> intel i9 or ryzen?
[11:26] <croraf> https://askubuntu.com/questions/1188788/cannot-install-ubuntu-20-04-on-omen-by-hp-17-cb0013nm/1188791
[11:27] <croraf> i9
[11:27] <croraf> sorry, thought ryzen was a laptop brand :D not a processor brand
[11:27] <croraf> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852636
[11:27] <ubottu> Launchpad bug 1852636 in linux (Ubuntu) "Cannot install any release on HP Omen 17-cb0013nm " [Undecided,Incomplete]
[11:27] <croraf> I opened that bug
[11:28] <lotuspsychje> croraf: could you apport-collect BUGID on your system please?
[11:28] <OerHeks> try that iam.tj page, boot with something like acpi_osi=! "acpi_osi=Windows 2015"
[11:28] <lotuspsychje> to complete your bug
[11:38] <croraf> lotuspsychje | where should i type this, in live ubuntu boot?
[11:39] <croraf> I can only enter ubuntu 18.04 live with nomodeset and blacklist=noveau
[11:39] <lotuspsychje> croraf: from a terminal: apport-collect 1852636
[11:40] <croraf> Btw, I have windows installed on the system, I managed to create 2 more partitions with ubuntu live
[11:40] <croraf> So I boot ubuntu live and then in terminal I input this?
[11:40] <croraf> Because I reproted bug for 20.04, and with that I cannot enter the system at all
[11:41] <croraf> neither with 19.10. Only with 18.04 and nomodeset blacklist=nouveau
[11:42] <croraf> OerHeks so you want me to try inputting this                         GRUB_CMDLINE_LINUX="acpi_osi=! \"acpi_osi=Windows 2015\"
[11:43] <croraf> in which config exactly, 18/19/20.04 try try with safe graphics?
[11:46] <tomreyn> this channel is about what will be 20.04 LTS at some point
[11:47] <croraf> Yes, I'm talking about this, and what will be is that 20.04 won't work on new HP Omen laptops
[11:56] <tomreyn> !bootlog
[11:56] <ubottu> To get a more verbose log of the boot process, remove "quiet" and "splash" from the kernel boot parameters and add "debug systemd.log_level=info". For info on editing kernel boot parameters, see https://wiki.ubuntu.com/Kernel/KernelBootParameters
[11:56] <tomreyn> croraf: so if you're trying to boot with an early 20.04 test build you could boot with these options, placed on the grub 'linux' line, after removing "quiet" and "splash": recovery modprobe.blacklist=intel-lpss-pci acpi_osi=! "acpi_osi=Windows 2015" debug systemd.log_level=info
[11:58] <tomreyn> if you can reach the recovery menu this way, you can then proceed by mounting file systems, dropping to a shell, and running:   journalctl -b | nc termbin.com 9999
[11:58] <tomreyn> if you have network acc3ess, this would then return a http address you can report back here
[12:06] <croraf> ok, now I inputed all of what you said, and half of the screen crashed, the rest is kinda running correctly
[12:06] <croraf> tomeryn on 18.04.3 though
[12:07] <croraf> I cannot even boot 18.04.3 Try Ubuntu now. Maybe even my usb got corrupted
[12:12] <tomreyn> croraf: for 18.04.3, /join #ubuntu
[12:13] <tomreyn> to ensure your installation media isn't corrupt:
[12:13] <tomreyn> !checksum
[12:13] <ubottu> To verify your Ubuntu ISO image (or other files for which an MD5 checksum is provided), see https://help.ubuntu.com/community/HowToMD5SUM or http://www.linuxquestions.org/linux/answers/LQ_ISO/Checking_the_md5sum_in_Windows
[12:19] <croraf> i verified the downloaded ISO is correct, but my stick can have bad sectors or something?
[12:44] <tomreyn> there is software which can verify that your iso was correctly written to the installation media. a GUI one for doing this is balena etcher.
[17:15] <croraf> Where can I see the updates / commits on Ubuntu daily builds from version to version
[17:16] <croraf> Like I have a version from yesterday morning, and I see this morning another version came out :). Where can I see the diff?
[17:24] <mason> croraf: There are mailing lists.
[17:26] <mason> croraf: https://lists.ubuntu.com/   and look at the "Package Upload and Automatic Notification Lists" section
[17:44] <croraf> mason | will I get previous updates with that?
[17:45] <croraf> Why cannot I just search, give me updates from last 7 days or something like that
[17:48] <mason> croraf: Maybe you can, but I don't know how off the top of my head. You can certainly look at the archives.
[17:52] <croraf> Subscribing to mailing list will only give me the future updates, right?
[17:52] <croraf> mason
[17:53] <mason> croraf: You can look at the archives. Example, https://lists.ubuntu.com/archives/xenial-changes/2019-November/date.html
[17:56] <croraf> mason thx
[18:48] <cybercrypto> hi there, question here: Do you happen to know if zfs option will be offered together with full disk encryption: During installation?
[20:36] <mason> cybercrypto: Eventually. At present you have to do a manual install to get that.
[20:36] <mason> cybercrypto: Also, evidently they're still taking some time to weight LUKS vs native encryption.
[20:36] <lordcirth> "eventually" as in "probably not in 20.04", or?
[20:37] <mason> cybercrypto: My experience with native encryption has been decent so far, although I miss having multiple keyslots ala LUKS.
[20:37] <mason> lordcirth: I don't have a way to know, but I'd suspect it won't be in 20.04 if it hasn't had a chance to burn in with 19.10.
[20:38] <mason> That said, supporting either kind of encryption isn't too bad.
[20:38] <mason> My favourite installs at the moment use the UEFI stub in Linux directly (no bootloader) and a native-encrypted ZFS root.
[20:39] <mason> My naive assumption is that native encryption will be a big win in mirrored or bigger vdevs.
[20:42] <lordcirth> Yeah, native is awesome but LUKS is fine
[20:44] <mason> I'm slowly working up a reasonable install script that handles mirrored/unmirrored root, and either LUKS or native encryption. I'm not considering it ready for release yet, but I've been sharing it as an example or a starting point for install scripting.
[20:44] <lordcirth> cool!
[20:45] <mason> The most recent version does Devuan, but it's easy to adapt. Half a sec.
[20:46] <mason> lordcirth: https://bpaste.net/show/OTEVW
[20:46] <lordcirth> thanks!
[20:47] <mason> lordcirth: The Ubuntu version isn't too wildly different. No need for update-rc.d, no special tricks to install ZFS binaries, etc.
[20:48] <cybercrypto> mason: thanks. you mean this option is not considered for the roadmap, or it is included and they are deciding on 'what kind of encryption' will be offered? (luks/ native)
[20:48] <mason> Also, it turns out that if you set a legacy mount on foo/var/log and include it in fstab, you can work around a race that zfs-initramfs loses otherwise.
[20:49] <mason> cybercrypto: I can't speak to the roadmap at all - not a Canonical person. I'm just speculating that it'd be a big change they'd want to see tested in a non-LTS release first. I don't actually know.
[20:50] <cybercrypto> mason: i see. I also believe this is only to be part of the lts release after being proper tested. I would go for native encryption as well (no need to luks extra stuff)
[20:51] <OerHeks>  such change would not be stable in an LTS release
[20:51] <mason> lordcirth: I'll try to remember to ping you when I get to where I have the one script handling all the various distribution options. Right now I'm keeping separate scripts more or less in parallel, and this one happens to be the most recent.
[20:51] <cybercrypto> mason: i believe one day in the future this will mature enougth to be part of any lts distro.
[20:51] <mason> cybercrypto: Agreed.
[20:51] <mason> cybercrypto: FWIW, I run it myself today, so *I* trust it, but *I* don't have to offer commercial support for it to giant organizations. :)
[20:55] <cybercrypto> mason: I also run zfs encrypted... (not on linux, but in bsd) and I am pretty satisfied with stability). I am glad cannonical is bringing it to linux distro (commercially/backing up)... other companies are strugling with xfs-red hat, brfs-suse, etc...  but in the end... zfs itself is way better. Lets hope for the best.
[20:55] <mason> Mm.
[20:55] <mason> FreeBSD, I assume, and not NetBSD...?
[20:56] <cybercrypto> freebsd
[20:57] <mason> I'd run more FreeBSD if Bhyve were more capable.
[20:57] <mason> libvirt/qemu/kvm has spoiled me.
[20:57] <cybercrypto> mason: hehe.. 
[21:01] <mason> What I need to explore now is LXC. It was unusable last time I looked at it, maybe 5-6 years ago, but lately it looks competitive with jails.
[21:02] <mason> LXD is also appealing, but heavier.
[21:05] <cybercrypto> mason: bsd's are not up to the speed of the virtualization architecture (believe me I feel they are great in many aspects) but is different to run against commercial companies that is heavily focusing on it... IBM and cannonical for instance). 
[21:06] <cybercrypto> mason: I am no expert on it.. I am just trying to run applications on top of them :)
[21:06] <mason> Yeah.
[21:07] <cybercrypto> mason: to be honest, i dont think 'they are running against'... they are following an ideal... that's it. 8-)
[21:09] <cybercrypto> mason: it has been like what? 10 years since zfsonlinux project is up? they are great but project is running low profile... I believe now it will fly! having cannonical backing it up, things will move faster, and marked will 'realize' zfs advantages.
[21:09] <cybercrypto> let's wait and see what future will bring us...
[21:10] <mason> cybercrypto: You know FreeBSD's adopting ZOL. It'll be the ZFS they ship in FreeBSD 13.
[21:17] <cybercrypto> mason: i see that is great for the software quality... there will be huge community working towards single purpose. if you check today the zol project, you will already notice that are several developer leaders from different domains/companies engaged (specially from cannonical)
[21:18] <lordcirth> Seeing these projects merge is great, yeah
[21:18] <mason> Yeah. It's fulfilling the promise of OpenZFS. Good stuff.
[21:19] <cybercrypto> lordcirth: Agree.