10:56 <xdeus> Hi, an initrd (not initramfs) should work, no? I can't manage to get it to work. Here's some info about how I built it and the kernel I'm using: https://x0.at/aY6W.txt

10:58 <xdeus> I'm using the tethered boot/proxy mode to boot it up with proxyclient/tools/run_guest_kernel.sh and passing in my kernel, args and initrd, in case it's relevant.

11:00 <chaos_princess> why are you using an actual initrd. And do you have anything at /sbin/init in the initrd?

11:01 <xdeus> No, no /sbin/init, but I don't think I should need it if I'm setting "rdinit=/bin/sh", no? I'm using initrd instead of initramfs because I just wanted to try it out. initramfs works fine though.

11:01 <chaos_princess> try doing that

11:01 <xdeus> Alright

11:01 <chadmed> i dont think m1n1 supports initrd payloads

11:02 <chadmed> the header is different to initramfs right

11:03 <xdeus> I don't know but it seems to be loaded according to those boot logs I think, it says "RAMDISK: gzip image found at block 0" and "using deprecated initrd support, will be removed soon."

11:03 <chaos_princess> kernel logs say the kernel has loaded something, so who knows

11:04 <chadmed> okay yeah that message also comes from the kernel i think

11:09 <xdeus> Okay I tried putting a script at /sbin/init that just has `#!/bin/sh` and `exec /bin/sh` and built in CONFIG_BINFMT_SCRIPT, still seems to give the same error about "root=" missing.

11:09 <chaos_princess> pass root=/dev/ram0

11:09 <xdeus> Yeah I tried that as well

11:10 <chaos_princess> oh well. there _might_ be a reason everyone uses an initramfs

11:11 <xdeus> Yeah I guess I will use a initramfs then :D

11:11 <xdeus> Thanks though <3

11:15 <psykose> is there any benefit to using an initrd whatsoever

11:15 <xdeus> I think not, from what I understand initramfs is much simpler and uses the caching code you would have compiled in anyways

21:05 <the_eye> I seem to be having some trouble that might just be fedora related, not sure, I'm not that used to fedora (normally an ARCH guy). I have here a very basic external drive that the system refuses to mount either via the graphical mounter or udisksctl or a manual sudo mount. The drive shows up in journalctl as /dev/sda but then mount times out. udisksctl says "Error mounting /dev/sda:

21:05 <the_eye> GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sda at /run/media/eye/WATCHBOOT: fsconfig system call failed: /dev/sda: Can't open blockdev" whereas in journal I'm seeing messages about "udisksd[1509]: Couldn't find existing drive object for device /sys/devices/platform/soc/b02280000.usb/xhci-hcd.3.auto/usb1/1-1/1-1:1.2/host0/target0:0:0/0:0:0:0/block/sda"

21:05 <the_eye> any hints where I should start poking? It's not SELinux related as sudo setenforce 0 doesn't change the behaviour

21:06 <chaos_princess> is it sda? not sda1 or something?

21:06 <the_eye> (the device in question is an embedded board that offers this drive to flash a firmware to) - the same device mounts fine on a ubuntu or arch system

21:06 <the_eye> just sda, yeah

21:07 <chaos_princess> so, no partition table, just a whole-disk fs?

21:07 <the_eye> (the new Sensor Watch Pro, in case anyone is curious - had the non-Pro already, absolutely loving it)

21:07 <the_eye> chaos_princess: yeah. it's just this not-really-a-drive that you copy the firmware to to flash the thing

21:08 <chaos_princess> cute. it i'd expect that to not work super well, the question is if debian also uses udisks

21:08 <the_eye> infos: https://paste.in-ulm.de/?0e4b62e82e6c0e0a#BWMVNr9BGbau2pTFSNVhG2TdcKv79RY4tCUfB35Gs81C and a journal paste: https://paste.in-ulm.de/?1ec5a0270a853a30#GhqpNA71Ya3SohS1EyPgqoSZhkbhSkyFuFkTXizBJuxQ

21:08 <chaos_princess> also, how exactly are you invoking sudo mount and what happens then?

21:09 <the_eye> sudo mount -t vfat /dev/sda /mnt

21:10 <chaos_princess> and the failure?

21:12 <the_eye> it runs for a while, then the board LED stops blinking (i.e. the board times out) and the mount command fails with "mount: /mnt: fsconfig system call failed: /dev/sda: Can't open blockdev."

21:13 <the_eye> dmesg tells me that at this point the device has reset itself

21:13 <chaos_princess> ok, about debian working then, same machine?

21:14 <the_eye> nope, little x86 thingy, GPD MicroPC running ubuntu with a MATE desktop

21:14 <chaos_princess> could be the usb controller then, or the drivers

21:14 <chaos_princess> tried macos?

21:15 <the_eye> on the Ubuntu machine udisks just automounts the thing

21:15 <the_eye> chaos_princess: ah, worth a try

21:15 <the_eye> didn't think of that TBH

21:16 <the_eye> will take a minute..

21:16 <chaos_princess> something tells me it is probably unrelated to fedora vs ubuntu

21:16 <the_eye> right, let me reboot and report back

21:18 <jannau> can you try to stop ModemManager?

21:23 <the_eye> chaos_princess: step one: under macos, it mounts right away (after I clicked "yes" on whether I wanted to allow it)

21:23 <chaos_princess> in that case, please also do the test that janne proposed

21:25 <the_eye> yep, doing that now as I'm logging into asahi again

21:30 <the_eye> jannau: that made it work right away! Many thanks!

21:36 <jannau> random suspicion from looking at the kernel log. Is NodemManager installed on the arch / ubuntu install?

21:38 <the_eye> jannau: at least on the Ubuntu MicroPC - no. Arch Thinkpad is ancient and would take a few minutes to find/boot, so I'll check that sometime tomorrow, I guess

21:41 <fl0_id> what is that even doing on asahi, just in case you plug in a lte/5g stick? or does it have other functionality?

21:41 <chaos_princess> it is probably a part of stock fedora

21:42 <the_eye> well I've disabled it for now at least

21:43 <the_eye> many thanks for the help chaos_princess jannau!

21:45 <the_eye> (also: can whole-heartedly recommend Sensor Watch and Sensor Watch Pro, they're a brilliant idea that works well - a board that replaces the innards of a Casio F91W or A158, turning into a thing you can modify/program. Has a temperature sensor and an accelerometer, battery lasts at least a year if not more)

21:47 <the_eye> (so I have a watch that looks like an F91W but shows the time in beats ("Swatch Internet Time). And also does things that are more useful than that but I am a person who was young and optimistic in the 90s, so..)