[00:10] <mattfly> how to i upgrade from beta to RC?
[01:16] <iconoclasthero> howarth?
[01:23] <iconoclasthero> yes:  https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965
[01:23] <ubottu> Launchpad bug 1873965 in linux-meta (Ubuntu) "booting into recovery mode hangs under 20.04" [Undecided,New]
[01:43] <iconoclasthero> howarth, though it isn't doing it anymore.  when i first installed it did.  though i did run update-grub a couple times.  
[01:43] <iconoclasthero> for some reason, however, it installed the low-latency kernels as (i assume) the default that didn't list a kernel; it was the first in the advanced list.
=== housecat changed the topic of #ubuntu+1 to: Welcome to #ubuntu+1, the support channel for pre-release versions of Ubuntu. Pre-release versions are unstable and will probably break your computer. | Current dev version: Focal Fossa (20.04) | Schedule: http://ubottu.com/y/ff | Download: http://iso.qa.ubuntu.com/qatracker/milestones/412/builds (downloading updates regularly? see http://ubottu.com/y/zsync ) | For 19.10 support, please
[02:21]  * housecat sighs at TOPICLEN
=== housecat changed the topic of #ubuntu+1 to: Welcome to #ubuntu+1, the support channel for pre-release versions of Ubuntu. Pre-release versions are unstable and will probably break your computer. | Current dev version: Focal Fossa (20.04) | Schedule: http://ubottu.com/y/ff | Download: http://iso.qa.ubuntu.com/qatracker/milestones/412/builds (downloading often? see http://ubottu.com/y/zsync ) | For 19.10 support, see #ubuntu
[02:39] <flying_sausages> Hey guys, I've got a fresh dedicated remote server I'd like to test Ubuntu 20.04 on but I don't have access to KVM. I've tried to upgrade via the `do-release-upgrade -d` option but focal is not available yet. Any ideas how I can get this done from the live root partition?
[02:54] <lotuspsychje> good morning
[02:54] <flying_sausages> morgen
[02:55] <lotuspsychje> hey flying_sausages 
=== RocketRaccoon is now known as Thanos
[03:19] <housecat> flying_sausages: what version is your server currently on?
[03:22] <flying_sausages> housecat: bionic
[03:22] <flying_sausages> I'm trying to do the "debian" way now by switching sources and doing a dist-upgrade
[03:22] <housecat> odd, i would have thought do-release-upgrade -d from bionic would get you to focal
[03:23] <housecat> what version did it offer you (if any)?
[03:23] <flying_sausages> none :/
[03:23] <flying_sausages> changed the prompt to normal too
[03:23] <flying_sausages> not even eoaaen
[03:23] <housecat> maybe i'm misunderstanding https://changelogs.ubuntu.com/meta-release-lts-development then
[03:24]  * housecat shrugs
[04:13] <valorie> do-release-upgrade -d worked for me....
[07:31] <lotuspsychje> TJ-: i see your bug got more love already
[07:38] <Seveas> My upgrade to focal crashed my computer halfway through. Had to boot off a live usb, manually cryptsetup/mount/chroot and run dpkg --configure -a to recover. Not fun :(
[07:39] <lotuspsychje> ouch
[07:39] <lotuspsychje> what was the crash about?
[07:40] <Seveas> dunno, I got the ubuntu equivalent of a bsod: fullscreen message that something had gone wrong and it wouldn't do anything except power down
[07:41] <lotuspsychje> no relevant errors you can recall?
[07:41] <Seveas> none. One second I am watching apt logs zip by normally, the next I have that message.
[07:42] <Seveas> Haven't had that happen before. Older upgrades (around 2010) used to regularly fail for me, but wouldn't crash, so I could do the recovery before rebooting. This one was more annoying.
[07:42] <Seveas> (also, the older upgrades usually failed because I upgraded 3 months before the actual release :D)
[07:43] <Seveas> So yeah, /topic definitely applied for me this time
[07:43] <Seveas> Unstable, will break your computer.
[07:48] <lotuspsychje> every case is different Seveas 
[07:48] <Seveas> yeah
[07:48] <lotuspsychje> we have smooth upgrade experiences too from the volunteers
[07:56] <Seveas> waddayaknow, journald did capture an error
[07:56] <Seveas> apr 09 09:35:47 starfire gnome-shell[1404]: GNOME Shell crashed with signal 11
[07:56] <Seveas> that's guaranteed to cause problems during an upgrade :)
[07:57] <Seveas> this is followed by lots and lots of errors trying to start it, probably due to the system being half upgraded
[07:58] <Seveas> apr 09 09:37:42 starfire systemd[1]: Removed slice User Slice of UID 121.
[07:58] <Seveas> -- Reboot --
[07:58] <Seveas> apr 09 11:18:07 starfire kernel: microcode: microcode updated early to revision 0xca, date = 2019-09-26
[07:59] <Seveas> so it took me about two hours to recover, mostly because I didn't have a live usb at hand and IE on my windows pc kept crashing at 95% download of the iso. Finally had to resort to using the mac to create the live usb. And first time around I did cryptsetup wrong, so when rebooting it couldn't find the rootfs, so I had to redo the cryptsetup/mount/chroot dance and recreate the initramfs
[08:00] <Seveas> all in all, a not very friendly recovery experience. Wondering how we could make that easier.
[09:28] <sufy> my realtek drivers weren't working i am wondering what was the update recently for realtek drivers in ubuntu beta
[09:28] <sufy> i am wondering if that was something on kernels
[09:39] <erle-> Are there any release-delaying major/dangerous bugs?
[09:40] <erle-> (known bugs)
[09:50] <soon> Fresh install of 20.04 on Lenovo P52s -- choosing the 'Erase disk and install' option, it hangs when formatting (ext4) the drive
[10:36] <TJ-> lotuspsychje: upstream have provided some patches we've tested but so far not fixed
[12:15] <nikolam> Hi, does 20.04 has ability to install Ubuntu on ZFS partition?
[12:16] <nikolam> I recently had broken BTRFS partition that resulted in unmountable partition, I managed to save data, but I am thinking to install on ZFS now.
[12:37] <howarth> A bit of progress on https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965
[12:37] <ubottu> Launchpad bug 1873965 in linux-meta (Ubuntu) "booting into recovery mode hangs under 20.04" [Undecided,New]
[12:38] <howarth> I discovered that removing 'nomodeset' from the grub kernel options of the recovery kernel entry eliminates the hang at loading the ramdisk
[12:38] <howarth> Wonder if this is a bug in the 5.4 kernel
[12:39] <howarth> Perhaps if I can install a similar 5.4 kernel under bionics, it will trigger as well
=== halvors1 is now known as halvors
[14:18] <howarth> It appears that https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873965 maybe bug introduced in 5.4.
[14:18] <ubottu> Launchpad bug 1873965 in linux-meta (Ubuntu) "booting into recovery mode hangs under 20.04" [Undecided,New]
[14:19] <howarth> Ubuntu 18.04, which doesn't show the bug under its 5.3 kernels, shows the bug when the generic mainline kernel for 5.4.25 is installed.
[14:19] <howarth> It also appears to be an issue in the generic 5.6.6 mainline kernel.
[14:44] <iconoclasthero> howarth:  i don't know if you saw my message from last night.  i had a problem getting into recovery mode when i first installed it but it isn't causing a problem now.
[14:46] <iconoclasthero> linux	/boot/vmlinuz-5.4.0-25-generic root=UUID=3850d501-dfdd-4615-b28e-c99b9d3ec5cc ro recovery nomodeset persistent
=== halvors1 is now known as halvors
[15:09] <takov751> Hello
[15:11] <takov751> I have a quick question. After the release of the focal fossa if someone used the daily image as an install. And would like to stay on the safe lts ,we just have to turn off the pre-released option in the softare@ updates
[15:12] <oerheks> pre-released option ??
[15:13] <oerheks> what is that?
[15:13] <takov751> the proposal
[15:13] <takov751> update
[15:13] <takov751> where i am able to test the proposed software updates
[15:14] <oerheks> ah oke, i think they are disabled when you get the full release?
[15:15] <takov751> Nice , thank you :D
[15:39] <Kon> Do exFAT kernel drivers make exfat-fuse obsolete?
[15:40] <Kon> IIRC 5.4 is the first kernel with native support
[16:11] <oerheks> have you tried?
[16:44] <Kon> Nope. I suppose I'll try it after upgrading
[18:24] <nikolam> Hi, does Ubuntu 20.04 Beta, already allow installing form Boot/Live media, to the ZFS pool created on top od the disk MBR PARTITION. (to keep dual-boot)
[18:24] <nikolam> I recently had crash of Btrs leading to unmountable partition, I would like to try out ZFS Root. 
[18:25] <nikolam> Does installed allows installing on Partition by creating new ZFS pool of partition, and not just the whole drive, like in 19.10 ?
[18:38] <Kon> nikolam: The MBR should be installed at the top of the device, for example, /dev/sda, not in a standard partition like /dev/sda1 or /dev/sda2, which would would format as ZFS and mount at /
[18:40] <nikolam> yes I know that.. I think. I already have sda1 and sda2 for Other OS in dual boot and used to use GRUB with Btrfs on sda3. I would like a new ZFS pool on sda3. Or to be able to install onto pre-existing pool on sda3..
[18:42] <nikolam> Latter should be preferable, since I want to be able to choose OpenZFS "Feature flags" to my likings, to get OpenZFS compatible with other systems too, not just Linux.
[18:44] <nikolam> I actually usually use illumos to create ZFS partition, because it's fdisk creates Slice inside MBR partition. Unlike Linux that just puts ZFS pool inside raw MBR partition.
[18:45] <nikolam> pool on top of raw MBR partition, sometimes confuse some boot loaders.. (or can lead to seeing "sdaX" designation in zpool list, when pool is imported to other OS then Linux..
[18:47] <nikolam> Kon, so no, i don't want to give it whole drive. I need GUI installer option to choose partition for pool (sda3) and as best, to use pre-existing ZFS pool. 
[18:48] <nikolam> How Linux/Ubuntu uses ZFS datasets is separate topic, because I love everything nice and tidy in it's sub/datasets. And not having / subfolders all over in it's datasets on top of the pool root.
[18:49] <nikolam> I hope I wouldn't need to install somewhere separately, just to have ZFS pool with Ubuntu and then copy dataset to existing pool..
[18:49] <nikolam> (or better replicate from snapshot)
[18:52] <nikolam> Kon, ZFS does not mount at "/". ZFS uses datasets, that mount wherever you want, so system dataset could mount to "/" but other datasets can mount elsewhere.. Every dataset is a separate filesystem.
=== skookum0 is now known as skookum
[23:17] <CarlFK> apt upgrade... Setting up linux-headers-5.4.0-26-generic (5.4.0-26.30) ...
[23:17] <CarlFK> but I don't see linux-5.4.0-26
[23:18] <CarlFK> ls /boot .. no -26.