| bpmedley | rrq : Do you have any specific functional test requests? | 00:00 |
|---|---|---|
| rrq | not sure; maybe check up some expert install variations.. eg lvm and/or encrypted disk and different partition set ups, then using sysvinit/openrc and maybe LILO boot as well... basically straying off the default installation path | 00:05 |
| rrq | though I think the main question marks would be about the pool completeness of offlne server+CD uses cases.. but those trial isos aren't there anymore | 00:06 |
| bpmedley | Cool. Should every test be conducted on Legacy, EFI32, and EFI64? Also, is the code for the install system available? | 00:06 |
| rrq | my iso building uses https://git.devuan.org/ralph.ronnquist/devuan-installer-iso | 00:08 |
| rrq | I run debootstrapped bewulf VM (amd64/i386) to build using the master branch of that project | 00:09 |
| bpmedley | Neat. | 00:09 |
| rrq | the build hosts need source.list including main/debian-installer and hmm one or two less common packages (esp newlisp) | 00:10 |
| rrq | and build-essential | 00:11 |
| rrq | afk | 00:22 |
| bpmedley | rrq : May I get the proper deb line for the sources.list and 'main/debian-installer' ? | 00:22 |
| rrq | I have these three: | 00:47 |
| rrq | deb http://deb.devuan.org/merged beowulf main contrib non-free | 00:47 |
| rrq | deb http://deb.devuan.org/merged beowulf main/debian-installer | 00:47 |
| rrq | deb-src http://deb.devuan.org/merged beowulf main contrib non-free | 00:47 |
| rrq | I also have an apt-cacher-ng as caching proxy.. on the host | 00:48 |
| rrq | speeds up repeated building | 00:49 |
| rrq | https://termbin.com/ma3l is my /var/log/apt/history.log for the amd64 VM | 00:53 |
| rrq | https://git.devuan.org/ralph.ronnquist/buildisobuildvm is a project I used for debootstrapping the VMs | 01:01 |
| rrq | (with a little bit of magic touch re nfs) | 01:03 |
| bpmedley | Sorry, I was afk for a bit.. | 03:08 |
| bpmedley | rrq : What I'm doing is getting beowulf setup for iso creation. After I do that I'll work on some meandering functional testing. If you have a need for a specific VM test, please ask at your leisure. | 04:17 |
| bpmedley | rrq : # dmesg | grep nomodeset --> You have booted with nomodeset. This means your GPU drivers are DISABLED. | 04:49 |
| bpmedley | With nomodeset X11 does not load. Without nomodeset X11 loads. | 04:50 |
| rrq | fair enough. X11 is not needed by the installer | 05:10 |
| bpmedley | rrq : Excuse my lack of context. The nomodeset reference was when booting the installed OS. | 05:11 |
| rrq | mmm I suppose grub is helpful and "inherits" the installer's nomodeset | 05:12 |
| rrq | would possibly be in /etc/default/grub then (hopefully) | 05:14 |
| bpmedley | I'll make a note to check that next time I install. Currently I'm wondering why nomodeset is required for the installer, but works after Devuan is installed. | 05:14 |
| rrq | the feature is whether the kernel loads the graphics firmware early or not | 05:15 |
| rrq | if early, there's no display until X11 starts alhough it depends on the "graphics card" | 05:17 |
| bpmedley | rrq : What I hear you say is: the nomodeset feature details the time at which the GPU drivers are "turned on". Is that correct? | 05:17 |
| rrq | that's how I understand it right now | 05:18 |
| bpmedley | The dmesg quote mentions that the GPU is disabled, though. I'm a bit confused. | 05:19 |
| rrq | https://forums.linuxmint.com/viewtopic.php?t=200884 | 05:20 |
| rrq | lot's of info I would rather not learn :) | 05:21 |
| rrq | no blip | 05:21 |
| bpmedley | What's a "blip"? | 05:21 |
| rrq | sorry meant my misspelling .. no single-quote | 05:23 |
| bpmedley | https://www.reddit.com/r/Ubuntu/comments/1i7kps/what_does_nomodeset_do/ | 05:23 |
| rrq | and this is good too https://wiki.archlinux.org/index.php/Kernel_mode_setting | 05:24 |
| bpmedley | rrq : Do you believe we might not be including all the video drivers in the installer's kernel? | 05:43 |
| rrq | not really, but it's possible of course | 05:44 |
| rrq | lib/modules/4.19.0-8-amd64/kernel/drivers/gpu/drm of the initrd does look empty | 05:52 |
| bpmedley | If you want to roll another iso I would happily download and try installing again (without nomodeset). | 05:54 |
| rrq | the installer doesn't need the video drivers.. and there's no package to get only them; I'd have to copy from the build host | 06:34 |
| bpmedley | rrq : So, the Beowulf installer is text only? | 06:37 |
| rrq | yes | 06:37 |
| bpmedley | Interesting. I was confused/ignorant.. | 06:38 |
| rrq | I'll get these published and then make a trial that copies the build host gpu modules .. it's ~20Mb extra, and then maybe one can skip nomodeset | 06:40 |
| rrq | that might be less confusing for the installed system | 06:41 |
| rrq | though hmm the grub setup is done in the target chroot, so it shouldn't be confused... I suppose it refers to dmesg and the boot parameters | 06:43 |
| rrq | bpmedley: did you get nomodeset into the boot parameters for the installed system? | 07:01 |
| bpmedley | Yes. I just reinstalled. I had to remove from /boot/grub/grub.cfg. | 07:02 |
| bpmedley | Sorry, I got excited about the iso stuff and forgot to report status. | 07:02 |
| rrq | hmm was that a standard installation? | 07:02 |
| bpmedley | I can't remember if I did Expert or just "Install". | 07:03 |
| rrq | efi or bios? | 07:03 |
| bpmedley | Legacy Bios. | 07:03 |
| rrq | hmm didn't happen for me | 07:03 |
| rrq | on "Install" | 07:04 |
| bpmedley | Just so I understand, when you add a manual "nomodeset" onto the linux kernel command-line, then your grub.cfg does not have a nomodeset present. Is that what you're saying? | 07:04 |
| rrq | yes. it's a oot parameter for the installer, but before "---" and therefore grub don't use it ... maybe you added it after "---" | 07:05 |
| rrq | b | 07:05 |
| bpmedley | Yes, I feel I added the nomodeset after "---" . | 07:06 |
| rrq | ok. good. then I think it's safe enough to use nomodeset for the installer | 07:06 |
| bpmedley | Want me to try again with nomodeset before the "---" ? | 07:07 |
| rrq | well I just tried that so I think it's fine ... maybe checking lilo boot instead of grub boot? | 07:08 |
| bpmedley | Sure, I can try lilo. Would you like the answer before I get the iso creation stuff working? | 07:10 |
| rrq | actually it's maybe better you can build isos (first) | 07:11 |
| bpmedley | make[1]: *** No rule to make target 'library-amd64-contrib', needed by 'NETINSTALL_dists_beowulf_contrib_binary-amd64_Packages'. Stop. <-- This is my current issue. | 07:12 |
| bpmedley | $ make ISO=netinstall | 07:12 |
| rrq | you've done "apt-get update" after setting sources list | 07:13 |
| bpmedley | Wow! That was an issue. Getting further. | 07:14 |
| rrq | yes the building dismantles the Packages files intl "library" directories with individual package meta files | 07:15 |
| rrq | to make it easy to create partial Packages files for the various pools | 07:16 |
| rrq | I'll be afk for an hour or so | 07:21 |
| bpmedley | I get a netinstall-amd64.iso, but it's a little weird. For example, I only get Ext2, FAT16, and FAT32 in the "How to use this partition" list. | 07:38 |
| bpmedley | I'll be back later. | 07:46 |
| Joril | Hi everyone, I've just found a workaround for this issue https://git.devuan.org/devuan-packages/lightdm/issues/2 | 17:14 |
| Joril | I've added a comment with the workaround, is this enough? | 17:15 |
| LeePen | Joril: If you have the correct packages, this issue is fixed in beowulf. | 17:28 |
| Joril | LeePen: Where can I find which packages are correct? | 17:30 |
| LeePen | Are you using logind of consolekit? | 17:31 |
| LeePen | s/of/or/ | 17:31 |
| Joril | I've just installed Beowulf from the mini.iso, I think I'm using elogind | 17:33 |
| Joril | no consolekit package here | 17:33 |
| Joril | and AFAICS I'm running al the latest versions | 17:33 |
| Joril | *all | 17:33 |
| LeePen | Actually, are you talking about the lightdm greeter shutdown/reboot buttons? | 17:35 |
| Joril | Yes | 17:36 |
| LeePen | OK, my mistake. This is still unfixed in Debian. See #932047. | 17:37 |
| LeePen | The correct fix is to add pam_elogind to the greeter config. | 17:37 |
| LeePen | I have 2 alternative patches in Debian BTS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932047#5 | 17:38 |
| Joril | LeePen: Nice! Thanks :) | 18:05 |
| rrq | bpmedley: yes the ISOs are a bit "weird" in their partition layout | 23:24 |
| rrq | it's an iso-hybrid disk image with an el-torrito alt boot iso9660 (as if that would explain something) | 23:27 |
| rrq | as a disk image, its (dos) partition table declares a first (type "Empty") partition spanning the whole disk and a second (type EFI) partition mapped into an image file contained in the first partition (which is actually an iso9660 format partition) | 23:37 |
| rrq | as an iso9660 it also presents 2 (other) paritions .. an el torrito bootable cdrom .. which I'm hazier about | 23:40 |
| rrq | so what you see in that tool of yours would be Ext2=main file system, FAT16=el torrito boot, and FAT32=the EFI boot image | 23:42 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!