[00:02] bulk convert should be about the same as any loop [00:03] for i in *.mkv; do ffmpeg -i "$i" -c:v libx265 "$i".mp4; done, etc. [00:03] you might want ffmpeg -i foo bar < /dev/null in certain circumstances === BrianG61UK_ is now known as BrianG61UK [00:04] and there are GUI frontends aplenty [00:05] -x265-params lossless=1, I think I should use this one. THis way I won't lose any quality, but the resulting file will be smaller (x264 to z265), correct? [00:06] much smaller [00:08] so: ffmpeg -i foo.mkv -x265-params lossless=1 bar.mkv? [00:08] make sure the hardware you plan on playing it back via can handle it before you transcode a large collection, though [00:08] testing with 1 [00:08] larger resolution h.265 in particular can be fairly demanding to play back [00:09] frad: you'll probably still need -c:v libx265 [00:09] if you throw in -t 00:00:30, that'll do it for 30 seconds only, for testing [00:09] ffmpeg -i foo.mkv -x265-params lossless=1 -c:v libx265 -t 00:00:30 bar.mkv? [00:10] looks good; it's possible the -c:v libx265 may have to come before -x265-params [00:10] it'll let you know if so [00:22] matsaman, how dows compressng to x265 affect grainy films? [00:22] from the 80's and 90s [00:23] does compressing* [00:23] if you're doing it losslessly, it'll merely be smaller in file size [00:23] I mean I wouldn't mind losing some grainy-ness [00:23] if you're doing it losslessly, probably nothing much [00:23] whoops [00:23] if you're doing it lossily*, probably nothing much [00:24] when you're allowing loss, what you need to watch out for is darks and lights and high contrast [00:24] animated things are usually higher file sizes to maintain quality, because there are so many large blocks of perceptible color [00:24] allowing loss = not running '-x265-params lossless=1' [00:24] the defaults will be very good for most things, though [00:24] frad: right [00:25] defaults = running your first command, ffmpeg -i foo.mkv -c:v libx265 bar.mp4? [00:26] yeah [00:26] that will be technically lossy [00:26] although perceptibly, as a human, most of the time, you will not notice loss [00:26] (except in file size, for h.264 -> h.265) [00:28] I have a small screen 15 inches, but I want to keep as much quality as possible, for when I buy a 27'' monitor. If this is the plan, would it make sense to just use '-x265-params lossless=1'? [00:28] will I then notice loss? [00:28] I don't think you'll notice loss either way [00:28] if you're trying to make a collection that will last "forever", it makes sense to go lossless [00:29] but only if the filesize remains small enough to be financially viable [00:29] since you're going from h.264 to h.265 that probably isn't an issue [00:29] because you can reduce size by at least half most of the time [00:40] matsaman, the command works. This is a 2 hour movie. How long will it last? if it says 'fps=3', 3 frames per second? [00:42] frad: there should be a timestamp readout in the output, hours, minutes, seconds [00:42] if you've got regular consumer grade hardware, it will be a decent while [00:42] try using -t 00:01:00 and you'll get a time for one minute [00:44] strange: I ran ffmpeg -i foo.mkv -c:v libx265 -x265-params lossless=1 -t 00:00:30 bar.mkv but the output is 15 seconds long... [00:45] that is strange =) [00:45] maybe :31 [00:46] encoded 411 frames in 237.54s (1.73 fps), 83098.82 kb/s, Avg QP:4.00 [00:46] so a second is made of 24 frames, correct? [00:47] frad: hrmm? [00:47] compressing this movie will take me exactly 24 hours at 2 fps... [00:47] matsaman, 'encoded 411 frames' 24 frames are a second, correct? [00:48] a temporal second is made of 24 frames [00:48] I would take the seconds of video you got [00:48] and the seconds of time it took to produce [00:49] 4 minutes to create 17 seconds of movie [00:49] bejesus [00:49] it could very well take a long time [00:50] it'd be interesting to compare not using the lossless option, for time [00:51] 29 hours [00:51] now I wonder what kind of equipment do pirates use to compress and offer so many movies === zbenjamin is now known as Guest99578 === zbenjamin_ is now known as zbenjamin [04:00] what is default location for mysql log and system log [04:02] robertparkerx: /var/log/ is the normal place for logs [04:03] ty === Napsterbater is now known as Guest7978 === Napsterbater_ is now known as Napsterbater === jelly-home is now known as jelly === Napsterbater is now known as Guest81968 === Napsterbater_ is now known as Napsterbater === Napsterbater is now known as Guest86747 === Napsterbater_ is now known as Napsterbater === Napsterbater is now known as Guest5102 === Napsterbater_ is now known as Napsterbater === popey8 is now known as popey [05:31] hey! any way to list the touchpad module in ubuntu 14.04 ? [05:31] (I was using Ubuntu 20.04 which's touchpad is ok, but I find the ubuntu 14.04 driver or module works better?) [05:32] (same goes with touchscreen module ?) [05:45] I was on the Cd Image server and noticed their is a Ubuntu-Canary iso. I was wondering what the differences are between it and the regular Ubuntu Daily ISO. [06:44] hello. how do I install kernel sources in Ubuntu? [06:47] https://www.cyberciti.biz/faq/installing-full-kernel-source-ubuntu-linux/ [06:47] first hit on google slidercrank [06:48] I did it [06:48] but the problem is it installs linux-source-5.4.0.tar.bz2. Just puts this archive to /usr/src/ [06:48] without unpacking it [06:48] so I thought I'm doing something wrong [06:49] in other distros you install kernel sources and they appear in /usr/src/kernels/ [06:50] and I don't find kernel sources with apt-cache search `uname -r` [06:50] it finds only headers and modules and some other files [06:51] hey, did something special happen on the 21th, at midnight? [06:51] !discuss | Baikonur [06:51] Baikonur: Want to talk about Ubuntu, but don't have a support question? /join #ubuntu-discuss for non-support Ubuntu discussion, or try #ubuntu-offtopic for general chat. Thanks! [06:52] one thing I was running on focal suddenly stopped working at the turn of midnight on the 21th [06:52] UTC time [06:53] never heard of such a thing happening [06:54] it's a python program that's run once per hour with a systemd timer, it works fine if I run it myself but if systemd time runs, there's a http request that times out [06:54] Hi, I try to debug an issue on an embedded device and to do it i need to "delay" the response of DHCP (dhcpoffer). Did you know a dhcp server that can do it ? dhcpd seems not. [06:54] *if systemd timer runs it [07:27] Do I ask questions about 21.04 in ubuntu-devel or where, i'm sorry [07:30] gimpnixon: in #ubuntu+1 [07:30] but don't expect any response [07:31] @maik thank you [07:31] yw [07:35] Does anyone know how to properly install kernel sources for the currently running kernel? `uname -r` returns 5.8.0-48-generic. I'm using VERSION="20.04.2 LTS (Focal Fossa)". Yes, I've tried different tutorials. They seem not applicable to Focal Fossa [07:36] I am tryign to figure out the process function of Settings>Accessability>Zoom>Color Effects>Brightness. any suggestions? === coetzeer3 is now known as coetzeer2 === Amaranth1 is now known as Amaranth === dvdmuckle_ is now known as dvdmuckle === popey8 is now known as popey === elSueco3 is now known as elSueco === victorbrca3 is now known as victorbrca === rtudu is now known as rtud [07:57] installing kernel source always felt too complicated in ubuntu === kevr` is now known as kevr [07:57] Compiling kernels always felt too complicated for me [07:59] I managed somehow to install it. Not sure if I did it correctly. The problem is that I can't compile an out-of-tree kernel module. It was so easy in Fedora [07:59] did you need just the headers, or the entire source tree? [08:00] the source tree [08:01] yeah, the ubuntu has like 20 extra steps to prepare the source [08:03] make[1]: Entering directory '/usr/src/linux-hwe-5.8-5.8.0' [08:03] make[2]: *** No rule to make target '/home//Workspace//driver/queue.o', needed by '/home//Workspace//driver/queue.mod'. Stop. [08:03] I want is to unpack a tarball to /usr/src and symlink it to /usr/src/linux [08:03] Aand there goes my idea of installing anbox :( [08:03] and this is where I'm stuck [08:04] Someone forget to change the string from an example? [08:04] Or is it just censored? [08:05] (me forgetting to ping slidercrank) [08:05] curloxide, no, I replaced it with <...> [08:05] because it's irrelevant [08:06] the same driver compiles in Fedora [08:06] So it's kinda censored [08:07] In Debian, I used to be able to have the unstable repo and only install packages from there if I explicitly specified it with e.g. /unstable behind the package name. [08:07] Weird. Normally I'd see "no rule to make target 'clean'" or similar [08:08] Outside my knowledge [08:08] Can I do a similar thing in Ubuntu? E.g. run 20.10 and then get something from Hirsute? [08:10] I also learned about [08:11] "Ondřej Surý" today, and apparently I can lots of packages from his backports repo [08:11] can get* [08:14] Specifically regarding PHP [08:14] So, any advice about running a 'newer' Ubuntu, optionally with 'newest of the new' for select packages? [08:21] I've finally solved the problem with driver compilation [08:50] in ubuntu server, where is the network config? [08:51] de-facto, this documentation page is very good: https://ubuntu.com/server/docs/network-configuration [08:53] de-facto, to answer your question: It's in multiple places. Check that page for e.g. "Static IP Address Assignment" and "DNS Client Configuration" [08:54] hmm ok [08:54] this looks completely different from what i was used to from debian [08:55] probably something to do with systemd [08:56] i was given a server and want to understand its network setup [08:57] it seems the interface does not even have an ip address but a whole network ? [08:57] " inet 192.168.0.10/24 brd 192.168.0.255 scope global ens3" [08:57] how can i even find my ip address? [08:59] hostname -I [08:59] mabe [08:59] ah maybe that is the ip address with hostmask 24 [08:59] weird i would have expected a public address, hmmm [09:00] there is a web service you can curl to get your public IP from behind NAT: curl ifconfig.me [09:02] de-facto: such IP addresses are allowed [09:02] yeah i am behind a NAT :((( [09:02] ugh this is ugly [09:03] de-facto: I'm not sure what you mean [09:03] What do you think is wrong? [09:04] 0 doesn't mean "network" here [09:04] There's literally nothing wrong with any of it, NAT or not [09:06] https://petri.com/csc_ip_subnet_zero [09:46] Good day all. I have a Gigabyte B365M DS3H Motherboard, with Ubuntu 20.04 - I cannot get the front panel audio ports to work or where to even begin solving it? [09:50] Hi there! My Raspberry Pi4B running on Xubuntu 20.10 64bit doesn't boot from SSD any longer after the 5.8.1020-raspi update :( [09:51] My sugguestion: Try using the Micro SD card slot with a MicroSD to USB adapter and see if it boots. [09:52] VMGuy23: yes, it boots from MicroSD to my backup [09:52] Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf files were found. [the mdadm errormsg gets repeated multiple times...] [09:52] that's what I get on bootup and then some, it boots straight into BusyBox [09:52] Whats BusyBox [09:52] ~ [09:53] "Gave up waiting for root file system device. Common problems: " ... [09:54] Something went wrong writing the config files [09:54] "ALERT! Label "WRITABLE" does not exist. Dropping to a shell." [09:55] what happens when you unplug the SSD (but keep the card in) [09:56] VMGuy23: unplug the SSD at what point? When it swaps the boot-up process to Ubuntu or .. ? [09:56] Just before you turn it on. Use the card only. [09:56] I'm using James A. Chambers' SSD boot-up script, don't know if that might've botched the boot up [09:56] VMGuy23: works just fine from the MicroSD card, like I said :) [09:57] this was right after I updated the 5.8-1020-raspi today [09:57] that build has been working for half a year with all the latest updates oknp [09:57] (and I've never had any issues like this before tbh) [09:58] should I make a vidcap of the boot process? [09:58] because it DOES boot but something goes haywire at some point of the process [09:58] I can't help anymore, but a screencap would be useful for others. [09:59] Hopefully someone else comes to help soon. [09:59] toffo: what's the problem? [10:00] EriC^^: Raspberry Pi 4B won't boot from SSD after today's 5.8.1020-raspi kernel update. [10:01] Here's the error: "Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... mdadm: No devices listed in conf files were found. " [10:01] or well, it does to a degree, but then I get BusyBox'd [10:03] does it mention anything at the top before it gives the busybox? [10:04] I said above [10:04] He told me earlier [10:04] right at the end, it was: ""Gave up waiting for root file system device. Common problems: " [10:05] aha, you could try to troubleshoot that from busybox, see what it expects to mount and if it exists or what [10:05] It looks like broken .conf files [10:05] toffo: do you have a live usb or some live system you can boot to troubleshoot? [10:05] toffo: are you using raid? [10:06] Maybe the james A. Chambers' bootup script got broken by the update, you were using that [10:07] try an older kernel from grub > advanced [10:08] https://images2.imgbox.com/c3/b9/7kqniKum_o.png so this is what the "end of the boot" looks like. The cursor is blinking active in the "(initramfs)" part of the BusyBox, but I can't type in anything with any wired or wireless USB keyboard. [10:09] How did you take the screenshot? [10:09] VMGuy23: I have a HDMI video capture USB3 dongle [10:09] toffo: Ok, just wondering [10:09] toffo: are you using raid? mdadm is for raid [10:09] VMGuy23: you can get those off of eBay/Amazon for $10-15USD today [10:10] EriC^^: nope. Just a Samsung T5 USB3 SSD [10:10] and note that it boots up until that point from the SSD, there's no MicroSD card anywhere [10:10] I'm not using a "boot jump" via MicroSD or anything. It's straight off the SSD. [10:10] toffo: ok, maybe see /etc/mdadm/mdadm.conf in case it has stuff it is trying to use [10:12] EriC^^: will take a look now. I wonder if that has something to do with the fact that I'm using the James A. Chambers' script ( https://jamesachambers.com/raspberry-pi-4-ubuntu-20-04-usb-mass-storage-boot-guide/ ) [10:12] it looks like it's expecting some /dev/md* devices and they dont exist and it ends up giving up waiting, if you're not using raid i think mdadm /dev/md* shouldn't be relevant [10:15] EriC^^: only two lines that are not #-commented out in /etc/mdadm/mdadm.conf: "HOMEHOST " , "MAILADDR root" [10:16] toffo: what's in /etc/fstab ? [10:17] toffo: also anything in /etc/mdadm.conf ? or also give "locate mdadm.conf" a try and see what files it gives [10:19] EriC^^: There's a few "mdadm.conf" files, one of them in "/etc/modprobe.d/" that says on an uncommented line: "options md_mod start_ro=1" [10:20] EriC^^: There's also "mdadm.config" and "mdadm.conffiles" in "/var/lib/dpkg/info" [10:21] toffo: anything interesting in /etc/fstab? [10:21] do you have internet access on the live system? [10:25] EriC^^: https://images2.imgbox.com/3d/ef/ria0w4Mq_o.png fstab [10:25] EriC^^: you mean internet access on the box that is not booting now? yes [10:26] could the problem be in /etc/fstab referring to the disk partitions via labels rather than (part)UUID [10:27] I've always thought that pointing out to partitions by their label instead of (part)UUID is wonky a.f. [10:27] yeah it's definitely better practice to put the uuids instead [10:27] yup [10:27] EriC^^: I have multiple boxes from the same build type tho ... now this other Ubuntu box, also a RPi4B, running on 64bit Ubuntu 20.10, wants to update the 5.8-1020-raspi kernel ... [10:28] And since this happened to the other box right after the update, I don't want to screw up yet another fully working box [10:29] toffo: do you still have older kernels on it? try "ls /boot" and look for vmlinuz files [10:29] I'm a/b comparing the other box and this one, the /dev/sr* ones are for the optical drive I sometimes have attached to the RPi that are not in use [10:29] i see [10:30] they shouldn't be a problem tho.. or haven't been. yes, I have the vmlinuz [10:30] the 'vmlinuz' file is from an hour ago which is exactly when everything went to hell ;D [10:30] multipe vmlinuz? [10:30] or just that one [10:31] one file named 'vmlinuz', dated today, and one file named 'vmlinuz.bak', from March 24th. [10:31] there's also a 'vmlinux' file from March 24th. [10:32] aha, try "sudo update-grub && cat /boot/grub/grub.cfg | nc termbin.com 9999" and paste the link it gives you here [10:32] EriC^^: ... so that's what you meant by the internet access :D [10:32] (you're assuming I can ssh into the box) [10:33] I haven't tried that out tbh, but since it booted to busybox and doesn't let me input anything via keyboard, I have a nagging feeling that it didn't load sshd [10:34] seems that just about all of the stuff in the boot directory have a ".bak" file that's dated March 24th. [10:35] EriC^^: I have the SSD mounted to another raspberry pi that's running the same distro and is near-identical in many ways [10:36] EriC^^: but did I misunderstand what you said and should I try ssh'ing into the box or? [10:37] because if I run that grub update, it will obviously do it on my rpi build that's alive? [10:38] toffo: sorry im back [10:39] toffo: ah, ok if the mounted ssd dir, nevermind the update-grub command, only run 'cat /mountpoint/boot/grub/grub.cfg | nc termbin.com 9999' [10:41] EriC^^: cat: /mnt/sdb2/boot/grub/grub.cfg: No such file or directory [10:42] EriC^^: there's no "grub/grub.cfg" on the FAT32 boot partition (/mnt/sdb1) either [10:42] toffo: what's in /mnt/sdb1 ? try "ls -lR /mnt/sdb1 | nc termbin.com 9999" [10:43] EriC^^: https://termbin.com/bbxd7 [10:44] toffo: are the labels still intact btw? give "sudo parted -ls" a shot and have a look [10:45] EriC^^: should that command show the disk labels ? it doesn't show anything for disk labels ... [10:46] yeah it should toffo , under "Name" [10:46] EriC^^: I got gparted to show them, yep, they're "system-boot" and "writable" [10:46] EriC^^: I wonder if I should change them to PARTUUID's and give it another go that way. [10:47] I did record the boot-up process to video tho [10:47] yes, change them to uuid, not partuuid [10:49] toffo: usually when you boot the rpi, can you get grub or it uses some other bootloader? [10:51] EriC^^: I use the James A. Chambers' SSD boot fix that he made for 20.04 and older Ubuntu versions. [10:52] EriC^^: "I know for Ubuntu I had to take a bunch of steps for it to be able to USB boot correctly on the Pi 4. I even went as far as to write a script called “BootFix.sh” which gets Ubuntu 20.04 to boot (otherwise it gets stuck after the Pi screen similar to how HA is)." [10:52] EriC^^: (from: https://jamesachambers.com/new-raspberry-pi-4-bootloader-usb-network-boot-guide/ ) [10:52] oh , well, that's the usb network boot guide [10:52] EriC^^: https://jamesachambers.com/raspberry-pi-4-usb-boot-config-guide-for-ssd-flash-drives/ <= it was probably this one. [10:55] EriC^^: cmdline.txt seems to point, once again, to the label of the drive. I could swear I had made these point to the (part)UUID [10:56] I wonder if kernel updates revert that to default and use the drive label instead. then again, if that's not the problem ... let's see. [10:58] toffo: maybe you have to run the bootfix script again after installing a new kernel? [11:00] how do i mount a remove ssh directory? [11:00] seems there is not sshfs anymore? [11:01] it seems like /boot/firmware/cmdline.txt has the kernel parameters and such, like how you can use nomodeset in grub, maybe adding a rootdelay=10 or so might help in case that's the issue, if it's the mdadm that's the problem i wonder where it's getting the idea to look for anything raid related [11:01] !info sshfs [11:01] sshfs (source: sshfs-fuse): filesystem client based on SSH File Transfer Protocol. In component universe, is optional. Version 3.6.0+repack+really2.10-0ubuntu1 (focal), package size 42 kB, installed size 120 kB [11:01] EriC^: that wasn't a problem before, also, pointing to the UUID's didn't help. it still waits for root file system [11:02] de-facto: looks like it's still there, it could be that universe repo isnt enabled on your system so it isnt showing up [11:02] ah [11:04] hmm on enabling that in software sources the "Cache Refresh" window blocks the dialogue [11:04] should i xkill it? [11:05] yeah had to kill it, weird [11:05] ok now its installed [11:06] toffo: maybe try to chroot into the install from the running system, and maybe either just purge mdadm since you're not using raid, and try to update-initramfs -c -k all so it recreates it for the kernels [11:07] and maybe have a look in /etc/initramfs-tools for anything related to raid/md [11:07] EriC^: I'm going through that litany of error messages during booth, the "Running /scripts/local-block ... done" being the last one, it seems that I'm not the only one having that problem https://forum.mxlinux.org/viewtopic.php?f=23&t=56351 [11:08] EriC^: ... should I increase the wait time before timeout? :O [11:09] " [11:09] When the initramfs gets updated due to whatever reason (like new kernel, grub-live, manually running update-initramfs -u -k all) you get an additional boot delay of ~30 sec where it runs some scripts/local-block. This is a known issue: https://bugs.debian.org/cgi-bin/bugrepo ... bug=860533" [11:10] although obviously I can't run the "update-initramfs -u" since I can only boot to the BusyBox .. [11:10] toffo: yeah, i'd check out /boot/firmware/cmdline.txt and add a bootdelay and see there's no md related stuff, and probably just purge mdadm completely, see there's no config for the initram relating to it and update-initramfs [11:10] if that works then maybe try removing the rootdelay [11:10] EriC^: is there any way to update-initramfs on a detached box [11:11] a.k.a. can I run it somehow on that other rpi box onto the now-problematic SSD [11:11] made a typo above, it's not bootdelay it's rootdelay [11:12] toffo: yeah, chroot into the system, type "for i in /dev /dev/pts /proc /sys; do sudo mount -B $i /mnt/sdb2$i; done" [11:13] then type "sudo umount /dev/sdb1" and type "sudo chroot /mnt/sdb2" then type "mount /boot/firmware" it should mount it, then you can work as if you're in the running system, use dpkg/apt/update-initramfs etc [11:13] EriC^: cool tip, thanks, I didn't know that was possible :D [11:13] np, yeah it's very useful :D [11:19] EriC^: alright, I'm now over there in chroot, thanks, will have to probe for a bit [11:20] hi [11:20] i disabled tpm/vtd and now i am getting 8hrs battery life [11:20] EriC^: so, I know this is a dumb question, but JIC, while in the chroot it's safe to apt purge the adadm packages ? [11:21] EriC^: mdadm, that is. [11:22] EriC^: also noticed when running apt -- E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. [11:23] EriC^: I wonder if something got botched up during the update and it wasn't installed properly [11:28] trying to do a restore of a server hdd, the server got two hdds one i could read and put a backup tar in out network, the other disk *seems* to be empty (i doubt it is), how can i look into a suspected corrupt disk? [11:28] the server died of a catastrophic hw failure (psu exploded) [11:29] EriC^: https://pastebin.com/0j5JpJmS [11:29] EriC^: there's that kernel compression/recompression thang. [11:29] EriC^: and it fails. [11:30] EriC^: the part that says [11:30] EriC^: "mv: cannot move '/boot/firmware/vmlinux' to '/boot/firmware/vmlinux.bak': Read-only file system" -- that part (sorry!) baffles me a bit [11:31] EriC^: obviously it's the FAT32 boot partition but ... [11:31] afaik uefi uses fat32 for its boot images [11:31] de-facto: is raspberry pi 4b [11:32] oh i see [11:33] I wonder should I reinstall initramfs-tools, oddly enough I get "initramfs-tools is already the newest version (0.137ubuntu12)." but I still get prompted on whether or not to install it [11:34] another ??? is the "update-initramfs: deferring update (trigger activated) [11:34] " [11:35] I get the same error of read-only file system if I try to 'apt-get install initramfs-tools' in chroot. [11:36] "dpkg --configure -a" throws me into the loop of update-initramfs generating /boot/initrd.img-5.8.0-1020-raspi [11:37] next step would be to find out what's causing the file system to be read-only for dpkg [11:38] toffo, I take it mount says both partitions are definitely "rw" instead of "ro"? [11:38] waveform: nope. // /dev/sdb1 on /boot/firmware type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro) [11:39] okay, might be worth trying "mount -o remount,rw /boot/firmware" (if I'm remembering that correctly) [11:39] but that may fail if there's some reason it can't be mounted rw (e.g. dirty filesystem which needs fsck first in some circumstances) [11:39] waveform: thanks! it worked. [11:39] good stuff :) [11:39] waveform: my filesystems are always dirty! [11:40] jk , but fsck found a dirty bit [11:40] heh - well, that would explain things [11:40] and yes, the initramfs packages tend to trigger things like flash-kernel to re-run during postinst which'll require a rw mounted boot partition [11:40] waveform: my rpi crashed right after the update, or it might've been running in the background, it might be the cause [11:41] very likely [11:41] am re-running dpkg --configure -a [11:41] and it's now initramfs updating the 5.8.0-1020-raspi [11:43] oh mi gosh it twerked! [11:43] at least the initramfs / kernel update went oknp [11:46] nice :) probably worth checking if it can boot now (exit chroot, cleanly umount first, etc. etc.), assuming dpkg is all done and exited cleanly [11:47] waveform: I'm running the 'update-initramfs -c -k all' now as EriC^ suggested to make sure that the previous ones are on board as well. [11:48] the initrd.img 's from 5.8.0-1017-raspi to 1020-raspi seem to be updating without any errors or warnings. [11:49] waveform: cant unmount the sdb2 partition btw after exiting chroot :O [11:49] waveform: is busy [11:49] make sure you've got no shells with a current directory in that mount [11:51] what in the -- now my host rpi's PTY is not working [11:51] hmm [11:52] and minor note for the future, "-k all" is usually not *that* useful on the pi given that only the latest kernel (or more precisely the one selected by flash-kernel which defaults to the latest) actually gets copied to the boot partition as there's no fallback boot mechanism in the pi's bootloader (currently) [11:52] doesn't boot. [11:53] it seems to get stuck at "scanning for btrfs filesystems" for a moment. [11:54] the outcome is nonetheless the same ... [11:56] https://images2.imgbox.com/05/2c/X50IgJ69_o.png [11:57] it's very strange, notice that in the previous errormsg before I changed the /etc/fstab to point to the partuuid, it didn't find the drive labeled "writable" [11:58] toffo: sorry was away, i read the backlog and caught up [11:59] toffo: it looks like it's saying the partuuid=ab... doesnt exist === EriC^ is now known as EriC^^ [11:59] I'm wondering if the J.A.Chambers' SSD boot script for ubuntu is colliding with something [11:59] Hi folks [11:59] toffo: what's the contents of '/etc/fstab' ? [12:00] sigh. [12:02] EriC^^: I changed it to point to the UUID's (not PARTUUID's) of the drive [12:05] EriC^^: cmdline.txt probably. [12:05] EriC^^: I'll try by pointing cmdline.txt to the UUID instead of PARTUUID [12:08] EriC^^: changed cmdline.txt to the UUID and now I end up in the same screen but with tha alert on the UUID not existing instead of the PARTUUID (or as it was originally, before that, the label) [12:09] EriC^^: gah, I mean the alert pointing out that the UUID doesn't exist. [12:09] the "Begin: Running /scripts/local-premount" part seems to run for suspiciously long, too.. [12:13] "Error during boot: Gave up waiting for root file system device" => seems to be pointing to a grub error perhaps, https://forum.openmediavault.org/index.php?thread/22879-unable-to-boot-after-installation-dropping-to-a-shell/&postID=187321#post187321 [12:15] Hello. I have a Gigabyte B365M DS3H Motherboard, with Ubuntu 20.04 - I cannot get the front panel audio ports to work? [12:24] EriC^^: yep it's gotta be this one that's causing a stir: /boot/firmware/auto_decompress_kernel [12:25] EriC^^: https://cstan.io/?p=12531&lang=en related to that one, (or the James A. Chambers' script -- I originally installed Ubuntu 20.04, then updated to 20.10 a while back -- which btw should support native booting from MSD USB on RPI4b) [12:29] After looking at the instructions found at https://cstan.io/?p=12531&lang=en , it seems I have the file "/etc/apt/apt.conf.d/999_decompress_rpi_kernel" that has a line pointing to run a script ("/boot/firmware/auto_decompress_kernel"), but that script simply isn't there. I'm wondering if I should stick it back in there or not. [12:30] Bluewolf, check your alsamixer with F6, and choose which audio device you want to use, then run, sudo alsactl store [12:32] EriC^^: hah! well, this explains a lot, my config.txt seems to have been rewritten [12:33] good afternoon peeps [12:33] lol [12:33] EriC^^: the latest update seems to have dne that, instead of having lines i.e.: boot_delay \ kernel=vmlinux \ initramfs initrd.img followkernel , etc. , it's been reverted back to rpi4b's default config.txt [12:34] Maik: not you as well... sigh. :D [12:34] hehe [12:35] Deano59: stop it for once, thanks in advance [12:35] BluesKaj: Done that. No output or change? [12:36] Bluewolf, you have a nvidia gpu correct? [12:37] BluesKaj: Yes. 1660 Super [12:39] there was abug a while ago that would switch the nvidia audio from the onboard when the gpu choice in the uefi bios was changed from onboard to pci..dunno if that is fixed [12:41] I wonder if I should make a forum post somewhere on this? seems really weird, didn't help if I tried to reinstate that script [12:41] BluesKaj: I've a dual boot with Win10. This issue is the same there. I've even bought a new front port audio and cable with the same result. [12:42] Bluewolf: is your PC under warranty? [12:43] Deano59: Probably - But my situation doesn't permit a replacement. [12:43] Is there any way to get the kernel module name from a pulseaudio device? [12:45] Bluewolf, speaking of pulse audio/pavucontrol, have you checked the devices there [12:45] ? [12:46] I think I did something along those lines [12:46] Why are you looking for in particular? [12:46] *what [12:46] odd you guys are speaking audio - does anyone play with the audio while using DWM? [12:47] Funny [12:47] Interesting coincidence that all three of us came to talk about audio at the same time [12:47] Bluewolf, output devices/port [12:48] Yeah, I tend to just lurk, but since you guys were speaking audio - I noticed just hte other day when using DWM my line-in isn't registered in Discord (but it is if I launch the normal window manager with Ubuntu) [12:48] BluesKaj: Gimme a command and I'll paste the output? [12:48] withered_dragon, is it firefox [12:49] or discord app [12:49] discord app [12:49] look in pavucontrol Bluewolf, it's a gui [12:49] Yeah pavucontrol, is there any way to find the kernel module name or similar for a particular device listed there? [12:50] pikapika, do you mean a driver? [12:50] Yes [12:52] pikapika, run, sudo lshw -C sound, then look for "configuration: driver" [12:53] Thanks that helped [12:54] which driver is it ? [12:54] can a person just apt install pavucontrol? I don't see it in my programs in DWM [12:54] yes [12:55] I just needed a listing of the drivers associated with audio devices for now [12:55] And it worked [12:55] withered_dragon, do a which [12:55] it should be /usr/bin/pavucontrol [12:55] if it exists [12:55] but isn't shown in whatever menu you are using [12:55]