ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov has quit [Read error: Connection reset by peer]
iivanov_ has quit [Ping timeout: 480 seconds]
<nirik>
so I had a bit of time today to play around some more... I didn't get usb boot working. ;( I did find that pxe boot does work and was able to pxe boot to a rescue shell... It might be I am hitting something in rawhide userspace, so tomorrow will try a f40 userspace and see if it gets any futher...
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
<colemickens>
So I'm not the only one struggling with USB boot at least.
<colemickens>
Though apparently it does work.
<colemickens>
I dont even know what to try now :/
<colemickens>
I guess I was encouraged to enable more built in kernel modules but I'm not even sure what that would be
iivanov has joined #aarch64-laptops
iivanov has quit [Quit: Leaving...]
iivanov has joined #aarch64-laptops
iivanov has quit []
iivanov has joined #aarch64-laptops
<steev>
if you aren't using it, i would highly encourage to use johan's 6.11-rc1 and his defconfig
<jhovold>
colemickens: also check out my instructions to FarchordSteveCossette[m] from yesterday
<colemickens>
so I do have the adsp firmware supposedly available, so that might be my issue
<colemickens>
I'll drop the firmware for now and try that. Otherwise I have all those kernel modules and then some. I'll also try both orientations again.
<colemickens>
Thank you 🙏
valentine has joined #aarch64-laptops
<valentine>
robclark: I pushed a fixup to your MR, I hope I'm not imposing too much
<jhovold>
colemickens: make sure you use johan_defconfig as well, otherwise there could be further modules needed
<jhovold>
and if you pass 'regulator_ignore_unused' to the kernel and have loaded the keyboard deps you should be able to inspect the system and determine what is missing
<jhovold>
given that your distro initramfs provides you a rescue shell (e.g. if it can't find the rootfs)
<jhovold>
see the commit message for johan_defonfig for the keyboard deps
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
<FarchordSteveCossette[m]>
<jhovold> "and if you pass 'regulator_ignor..." <- The issue I have at least is a chicken & egg kind of problem: I do have a rescue shell, but without keyboard and mouse support (USB or otherwise), I can't use it lol
<FarchordSteveCossette[m]>
I'll have to see if adding a bunch of modules helps, I believe I tried that before
<lollaritits[m]>
how do i install archlinux with encryption?
<lollaritits[m]>
i tried following ironrobins endeavouros terminal and then add encryption but did not work
iivanov has joined #aarch64-laptops
<jhovold>
FarchordSteveCossette[m]: I assume you're using my wip branch and johan_defconfig, then you only need to include the modules listed in the commit message for johan_defconfig for keyboard
<jhovold>
and note that the keyboard interrupts are not working with mainline so this won't work with, for example, a fedora rc1 kernel
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov has quit [Read error: No route to host]
prime has joined #aarch64-laptops
prime has quit [Remote host closed the connection]
prime has joined #aarch64-laptops
prime is now known as Guest1749
Guest1749 has quit [Remote host closed the connection]
prim- has joined #aarch64-laptops
prim- has quit [Remote host closed the connection]
prime_ has joined #aarch64-laptops
prime_ is now known as prime
iivanov_ has quit [Remote host closed the connection]
<FarchordSteveCossette[m]>
Here goes nothing, let's see how that looks
iivanov has joined #aarch64-laptops
<FarchordSteveCossette[m]>
Nope.... sigh
<FarchordSteveCossette[m]>
But let's see if the keyboard at least works in dracut rescue
<jhovold>
FarchordSteveCossette[m]: I haven't updated the display deps for x1e yet so you can leave those out, you should be good with efifb as long as pass 'regulator_ignore_unused'
craftyguy has quit [Remote host closed the connection]
<jhovold>
and in case you're having trouble including modules in your initramfs you can always build the keyboard deps into the kernel temporarily
craftyguy has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
<jhovold>
otherwise you may not be able to mount your rootfs
<jhovold>
yes
<FarchordSteveCossette[m]>
I figured it would, but lemme see
<FarchordSteveCossette[m]>
Alright added btrfs to the long list of force_drivers, let's see
<jhovold>
not forced drivers, but it needs to be enabled in the kernel config
<FarchordSteveCossette[m]>
Nope still the same
<FarchordSteveCossette[m]>
I thought it was, but lemme see
<jhovold>
it's not enabled in johan_defconfig currently as I only use ext4
<FarchordSteveCossette[m]>
Man building sure doesnt take a long time LOL aiite, lemme try to install that
iivanov has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
<Jasper[m]>
<FarchordSteveCossette[m]> "Nope.... sigh" <- Lemme check what I do on x13s, I think it's not force_drovers
<Jasper[m]>
*drivers
<Jasper[m]>
also I'd suggest specifying the fw files, iirc they don't include the entire folder the way you did it
<FarchordSteveCossette[m]>
Jasper[m]: There's also the fact that I somehow messed up the config <.< idk why, the menuconfig is.... annoying.
<steev>
it can be, but if you have a general idea of what you're after, you can use `/` for searching
<robclark>
valentine: thx.. I want to make one more change to the fd patch and then I'll squash your fixup
<FarchordSteveCossette[m]>
steev: problem is, I'm trying to make sure it baked in the btrfs driver. I selected it in menuconfig, exited. Then, I did make (In my case, amake -- it's an alias) rpm-pkg and it build. And it _seems_ to have built the rpm, but if I look at the installed kernel, there's no /fs/btrfs in the kernel
<FarchordSteveCossette[m]>
aiite the GOODCONFIG there does have btrfs, and yet the built rpm doesn'T have it. To heck, I'll skip the rpm packaging thing
iivanov has joined #aarch64-laptops
<gwolf>
steev: Thanks a lot! I'm taking note of your answer, will try to compile tomorrow (today I'm quite tired)
<steev>
there's no rush :)
<steev>
i'm just appreciative that ema wrote that blog :D
<FarchordSteveCossette[m]>
jhovold: So, I'm booted in to the default fedora kernel right now. Mind you, I still have no laptop keyboard, but I do have USB so I can enter commands. Anything I can do to try to pinpoint this issue?
<FarchordSteveCossette[m]>
One thing I wanna try too, we removed the 80-drivers udev rule... does that do anything in the initramfs...?
<nirik>
no no, I meant on my x86_64 laptop... I was going to copy a install to the nvme and then swap it into the 7x...
<colemickens>
Okay, I removed firmware, I tried both orientations for the USB-C drive, and it still is not seeing the root on USB in initamfs.
<colemickens>
Still no luck, threw in the regulator_ignore_unused kernel param and usb_storage module but same behavior.
<colemickens>
(also removed firmware)
<colemickens>
I do get a recovery shell, but not really sure what to look at once I'm there.
<colemickens>
* removed firmware) (also, with johan's kernel + johan_defconfig)
<steev>
look at the devices in /dev, look at the modules that are loaded, check dmesg output
<JensGlathe[m]>
perchance, do you'all build MHI as modules? Last year when I was trying to boot Volterra from USB, it was the final thing to make it work. MHI* as modules, not builtin
<colemickens>
I suspect MHI is built in. I don't think I include it in initrd and I do see it trying to load firmware.
<colemickens>
(also tried both orientations again)
<JensGlathe[m]>
I had to build mhi as modules to make the damn thing boot from anything USB, otherwise it would always fail on mounting root, regardless of fs. I guess there's a connection between bus enumeration and the way mhi is initialized. With mhi loaded as modules, the XHCI controllers are detected earlier, not after trying to mount root.
<steev>
jhovold: mani_s ^
<mani_s>
steev, how MHI is related to USB?
<steev>
mani_s: no idea, that's something jens would need to answer
<steev>
though looking at it, the MHI bits seem to be modules, at least for sc8280xp
<mani_s>
technically there is no relation between them. MHI uses PCIe
<mani_s>
there is no need to build mhi drivers as built-in
<JensGlathe[m]>
6.11 seems to have new tricks up its sleeve 😎 I can drive my 4k display with 4k again, suspend and re-awake. This didn't work reliably (or at all) since 6.6
<steev>
it seems like johan's defconfig does set it to M anyway
<mani_s>
steev, that's the correct one
<steev>
mani_s: i don't have an x1e device :) i'm just grepping around trying to help out the poor nix and fedora users :(
<JensGlathe[m]>
re MHI: Maybe MHI using PCIe changes the order of initialization or something, it was just observational. To observe it, though, I had to buy an X13s 😁
<colemickens>
I'm using johan's defconfig, so presumably it shouldn't be.
<steev>
check if it's in there because of a dependency anyway?
<steev>
because pcie_qcom is there, and that's gonna need it
<mani_s>
MHI is just for modems/WLAN. And it doesn't directly depend on any Qcom drivers
<mani_s>
It only depends on CONFIG_PCI
<colemickens>
Oh yeah, and I actually have pcie_qcom now from johan's tree I guess.
<JensGlathe[m]>
Would anybody try to boot an Ubuntu stick I could prepare from Johan's tree to see if we get it up? No X1E hardware ere, either
<steev>
oh, i guess not then?
<steev>
well if wlan is in there
<steev>
JensGlathe[m]: that's good news on the 4k, i only have a 2k monitor here though :(
iivanov has quit [Remote host closed the connection]
<nirik>
I'm happy to try images from folks on the 7x I have, but will likely be later today/this evening... in meetings/etc.
iivanov has joined #aarch64-laptops
<JensGlathe[m]>
Need to build it anyway
iivanov has quit [Quit: Leaving...]
<JosDehaes[m]>
I've been trying to get the Ubuntu installer to boot on my yoga, but so far was not successful. I see the device tree load and I see a few kernel messages but then the screen goes black. The initrd of the Ubuntu iso only has modules and firmware, so not sure how it could ever boot
<JensGlathe[m]>
I use a different image, I dervied from the 24.04 RPi preinstalled Desktop and modified it for Volterra and X13s. It brings up the Ubiquity installer, and sets up a fairly decent system.
<JensGlathe[m]>
That's the one I will use to derive for X1E stuff.
<JosDehaes[m]>
Thx I can try that base
<FarchordSteveCossette[m]>
I..... found it
<FarchordSteveCossette[m]>
....the custom kernel boots now. Well, it boots further at least
<FarchordSteveCossette[m]>
nirik: remember when I said to delete the udev 80-drivers rule? It needs to be in the initramfs....
<FarchordSteveCossette[m]>
keyboard's working, that's good
<FarchordSteveCossette[m]>
Wifi's not working, but meh.... I actually don't care right now
<JensGlathe[m]>
Welcome to Ubuntu 24.04 LTS (GNU/Linux 6.8.0-39-generic aarch64)
<FarchordSteveCossette[m]>
Lemme try to see, if I add it back in, is it gonna work now that I'm on a custom kernel
<JensGlathe[m]>
Jos Dehaes: pobably just mounting root. cloud_init does a lot of things
<FarchordSteveCossette[m]>
Oh seems zram is refusing to boot too
<FarchordSteveCossette[m]>
Maybe a kernel module?
<FarchordSteveCossette[m]>
*mount
<JensGlathe[m]>
who cares about zram, out with it. its a systemd unit, link to /dev(null
<JensGlathe[m]>
s/(///
<JensGlathe[m]>
* on this high-end laptop ofc
<steev>
i still use it :( but my high-end laptop only has 16GB of ram
<JensGlathe[m]>
I also have it enabled om the X13s
* FarchordSteveCossette[m]
has enabled zram, replicated fedora config in that regard. Rebuilds the kernel.
<colemickens>
booted johan's kernel/defconfig, removed the firmware (so no adsp), I have the usual kernel params ( _ignore_unused), and I'm in emergency console. Nothing jumps out at me from /dev/kmsg, under /dev/block I only have symlinks to /dev/nvme0n1p and loop devices. I don't know what else to check/try. Hotplugging the USB device does not produce new log lines in /dev/kmsg. (uas and usb_storage are loaded)
<pstef>
I'm afraid that's not correct ed syntax, BTW
<JensGlathe[m]>
I went looking for the T14s btw. my employer sells the 32GB / 1TB variant, regular price €1849. Competition goes down to 1670 or so, that would be the CAMPUS edition (also sold by NBB)
<colemickens>
ath12k loads in mhi. I suppose I could remove that so mhi isn't copied and see if that helps per the anecdote shared a bit ago.
<lollaritits[m]>
does fedora arm run steam? or any distro?
<FarchordSteveCossette[m]>
yeah, that udev rule is causing a mess XD
<FarchordSteveCossette[m]>
Backlight control works
<robclark>
lollaritits[m]: yes, with fex emu.. but not sure if there is f40 fex-emu RootFS published with new-enough mesa yet
<JosDehaes[m]>
Jens Glathe: that rpi image doesn't even have UEFI 😅
<JensGlathe[m]>
Didn't care, afterwards it had
<JosDehaes[m]>
hehe
<JosDehaes[m]>
what did you put in the initrd?
<JensGlathe[m]>
the modules and firmwares as specified by Johan / Steev
<JensGlathe[m]>
and what I found on armbian
<JensGlathe[m]>
the fun part of the rpi image was tht you could boot it on a rpi, if things didn't work. No chroot required, since it was a different boot mechanism
<JensGlathe[m]>
ut same arch
<JensGlathe[m]>
* but same arch
<nirik>
Farchord (Steve Cossette): which kernel are you using now? and for wireless you might need to just modprobe ath12k (and make sure you have the firmware)
<FarchordSteveCossette[m]>
nirik: The firmware is what I need to triple-check. But loading ath12k doesn't do much. I won't send logs until I'm sure I'Ve went through everything. I'm using Johan's 6.11-rc1 kernel
<nirik>
ok, fair
<FarchordSteveCossette[m]>
nirik: if you want, I can zip it up and upload it to my fedorapeople site. It'S not big. It's lacking the dtbs, but tbh I think the ones provided by Fedora are probably fine.
<nirik>
if you like. I have to head to a appointment, and will not have time to test anything until later. The dtb should be under /lib/modules/ ? or no?
<steev>
you're definitely gonna want to use the dtb that comes with johan's kernel
<steev>
s/with/from
<FarchordSteveCossette[m]>
steev: Ah, cuz for the life of me, I can't make the dtbs
<FarchordSteveCossette[m]>
make dtbs does nothing
<steev>
if you built the kernel, it should be part of that process, and running make dtbs afterwards wouldn't do anything because it's done already
<steev>
do you have .dtb files in the arch/arm64/boot/dts/qcom directory wherever your built kernel stuff is?
<FarchordSteveCossette[m]>
steev: I checked in the target folder where the kernel modules are, nope it's not
<steev>
not modules
<FarchordSteveCossette[m]>
Yeah the dts files are there
<FarchordSteveCossette[m]>
and dtsi
<steev>
can you give me tree output? fedora must be doing something weird
<FarchordSteveCossette[m]>
The tree of the build folder? sure
<steev>
yeah
<steev>
and then of the sources too, if you still have it
<FarchordSteveCossette[m]>
lol tree file size is 12mb
<FarchordSteveCossette[m]>
the pastebin wants nothing to do with it
<FarchordSteveCossette[m]>
colemickens: Here's the tl;dr of how I made mine work, idk what nixos uses for root partitions, but are the fs drivers in the kernel?
<colemickens>
yes
<FarchordSteveCossette[m]>
steev: I got a bunch of Samsung T7 SSDs right now, love them
<steev>
too bulky :D
<FarchordSteveCossette[m]>
I also got a Crucial SSD somewhere
<FarchordSteveCossette[m]>
Bulky? I guess... I mean it's about as big as a SATA SSD lol
<steev>
32gb is 12 bucks, and that's more than enough for bringup
<colemickens>
interestingly it doesn't even have uas/usb_storage loaded, but I guess maybe that's because dwc3 failed?
<steev>
colemickens: question
<steev>
can you ls your efi partition?
<colemickens>
presumably the nvme one? I can sure try...
<steev>
wherever nix is installing the files to :D
<colemickens>
oddly I can't mount any of the nvme parts, one fails obviously as bitlocker but not sure why the vfat didn't just mount
<colemickens>
anyway,lsing the usb is easy, I'll do it from here
<steev>
is it loading off the usb?
<JensGlathe[m]>
dosfstools mtools
<colemickens>
steev: it loads initrd off usb and then fails to move to our stage-2 because it can't find the root on the usb
<colemickens>
since it's not seeing the usb devices at all, hence my concern over dwc3
<colemickens>
steev: so I'm happy to ls the esp but I think it's sound enough
<steev>
sure, i just wanna see the contents
<steev>
and then also if you could the snapdragon.nix local you have
<colemickens>
it doesn't even get the screen/etc working without it
<colemickens>
(I know because I built a version where the devicetree line was missing and didn't even get this far)
<steev>
i really hate nixos paths
<colemickens>
it's like the matrix, eventually you get used to it :P
<colemickens>
(but also, no, I understand)
<steev>
i'll pass, we have fhs for a reason
<steev>
for shits and giggles
<colemickens>
heh plenty of both those going on here
<steev>
can you copy the dtb to the root EFI as x1e80100-lenovo-yoga-slim7x.dtb
<colemickens>
fwiw I've checked /proc/device-tree/compatible and it says "lenovo,yoga7xqcom,x1e80100"
<colemickens>
do you want me to change the systemd-boot entry too, even though it seems to be getting loaded?
<steev>
for giggles, comment out the devicetree line (does systemd-boot support commenting things out?)
<steev>
after doing so
<colemickens>
ok will do
<steev>
if that goes back to nothing at all working; add dtb=/x1e80100-lenovo-yoga-slim7x.dtb to the kernel command line
<steev>
(i'm not sure if you could do dtb=/nixos/qcom-x1e80100-lenovo-yoga-slim7x.dtb.efi but maybe?)
<colemickens>
EFI stub: generating empty DTB
<colemickens>
and then acts like it did when I didn't specify a dtb
<colemickens>
I'll add the kernel dtb param to the entry now
<steev>
does the x1e bios have a linux option or nah?
<colemickens>
uhhhh oh gosh
<steev>
they added one (beta) to the thinkpad bios, but idunno
<colemickens>
I don't know I flipped SB and then don't remember anything else
<colemickens>
I'll check
<steev>
for other devices
<steev>
i don't *think* it should matter, but iirc, with the linux option on the thinkpad, just putting the dtb onto the root of the efi partition would have the bios pass it in
<colemickens>
yeah, I wondered if that's what we were working towards
<colemickens>
so far, with the dtb kernel param line, it's acting like it did when I had systemd-boot loading it.
<steev>
okay
<colemickens>
45s til timeout to rec console
<colemickens>
I would really hope this doesn't matter but I'm on a Canadian model :|
<steev>
doesn't that mean it just says sorry after every audio blip?
<colemickens>
and an annoying kb
<steev>
oof :(
<colemickens>
I have also noticed some dp/edp related driver that kernel panics, but I also assume that shouldn't affect usb.
<steev>
that could potentially just be a splat for using panel-simple
<JensGlathe[m]>
okay, 6.11 lets the performance cores run hotter. seems like 75°C , that's a lot more
<colemickens>
seems like maybe this "failed to initialize core" message comes from a failed dma mappping
<colemickens>
oh right, the bios option...
<JensGlathe[m]>
build time goes down from 34m to 28m
<robclark>
yeah, the edp-panel WARN_ON() can be ignored.. once you get things working enough you can dump edid and figure out the panel module and then we can add the missing entry in panel-edp.c ... or switch the dts if it is an SLS OLED panel
<colemickens>
yeah typical sparse lenovo bios, sadly its not that simple, no linux option
<robclark>
steev: no linux option on the yoga 7x, fwiw.. the bios options are pretty minimal
<steev>
robclark: good to know :) that's why the empty dtb message :(
<robclark>
you've gotta pay thinkpad bucks to get extra bios options :-P
<colemickens>
I kinda don't get how my dwc3 can just not work when it works for others.
<colemickens>
It doesn't rely on some of the firmware does it?
<colemickens>
Did I make a different problem by trying to avoid adsp and dumping the rest of the FW? I guess dwc3 could require fw :/ ?
<robclark>
for usb boot, idk.. maybe it could depend on probe order
<steev>
i can't answer that because i don't know :(
<robclark>
on x13s dp over usb-c dependend on cdsp but iirc normal usb functions didn't... seemed like cdsp was controlling the dp/usb routing
<colemickens>
well, if someone else wants to try with my image I can wormhole it to them, but otherwise I'm out of ideas / out of my depth :(
<steev>
on the x13s, usb comes up way before the remote procs
<steev>
colemickens: how about a picture of "dmesg | grep usb"
<FarchordSteveCossette[m]>
Alright, so all the firmware is in the filesystem AND in the initramfs... how do I load wifi, graphics and etc?
<JensGlathe[m]>
the paths should be in the dts
<FarchordSteveCossette[m]>
Oh good point lmc
<FarchordSteveCossette[m]>
Yep I am using that dtb
<JensGlathe[m]>
and to check what firmwares are loaded I have this in the cmdline "dyndbg=file drivers/base/firmware_loader/main.c +p"
<JensGlathe[m]>
and can check with sudo dmesg|grep "Loaded FW"
Caterpillar has quit [Quit: Konversation terminated!]
<FarchordSteveCossette[m]>
No results
<JensGlathe[m]>
it needs to be booted with this (I assume)
<FarchordSteveCossette[m]>
Well the firmware files themselves are in
<FarchordSteveCossette[m]>
lemme c what the arch image has
<steev>
as long as the wifi firmwares are in the correct place, a modprobe ath12k should give you a device
<steev>
maybe ath12k_pci
<FarchordSteveCossette[m]>
steev: doesn'T look like it... I just double-checked. I even tried to apply the "robs_hacks" cfg in modules.load.d, oh boy didn't that go bad! XD
<FarchordSteveCossette[m]>
qcom_q6v5_pas causes the whole system to go off the rails lol
<robclark>
you could remove the q6v5 stuff for now, it might mean no battery status, but that isn't too critical yet
<FarchordSteveCossette[m]>
so, ath12k is loaded, but it's used by nothing
<steev>
anything in dmesg?
<robclark>
lsmod shows ath12k not used by anything for me too.. I think that is fine.. `dmesg | grep -i ath12k` should tell you if it is missing some fw or calibration data
<colemickens>
but lol now I'm getting the mid-boot reboot
<colemickens>
"phy-qcom-eusb2-repeater"
<colemickens>
"phy-qcom-snps-eusb2"
<colemickens>
"phy-qcom-snps-femto-v2"
<colemickens>
one of them did the trick, and/or in addition to the others I'd added
<colemickens>
do we know what udev rule in particular is problematic?
<colemickens>
seems like 80-drivers.rules
<FarchordSteveCossette[m]>
For me in fedora, /lib/udev/rules.d/80-drivers. But it does need to be in the initramfs, not in the actual main paritition
<colemickens>
wow thats ridiculously annoying to implement properly/cleanly :|
<colemickens>
can I blacklist the offending module instead?
<FarchordSteveCossette[m]>
Unknown
<FarchordSteveCossette[m]>
But have you removed the file yet? if not it's in your initramfs
<FarchordSteveCossette[m]>
just try to remove it from the filesystem
<colemickens>
well for me this wasn't an issue unless I made it out of initramfs
<robclark>
interesting that 80-driver.rules works in initrd.. I guess it would be useful to know _what_ it probes that causes things to (I assume) insta-reboot (which typically is the bios getting angry about accessing some hw block that is unclocked/unpowered)
<FarchordSteveCossette[m]>
Yeah I essentially extracted both the good fedora initramfs and the more recent ones, aside from the kernel modules, all I could find that was different was that file....
<robclark>
hmm, I deleted that file.. but not super familiar with udev rules syntax so not sure how to translate that into which driver is misbehaving
<FarchordSteveCossette[m]>
so bringing it back fixed it. Go figure
<FarchordSteveCossette[m]>
robclark: have you checked the dmesg I posted? Not sure if you might have an idea why wifi is just not working lol
<FarchordSteveCossette[m]>
And I wish time wouldn't keep resetting to midnight lol
<robclark>
could be that probing while some other driver has clks/etc enabled masks the problem?
<robclark>
not sure why wifi is not working, I'd expect to see some msgs about loading fw
<FarchordSteveCossette[m]>
I did see some, but none that I can see is specifically related to wifi
<steev>
that's the only rule i can think of that would cause issues - there's no mtd*ro files (are there?) - pretty sure no parallel ports either, so that one shouldn't be the issue, i2o i also don't think exists, same for memstick and tifm devices
<robclark>
so, I had to patch board-2.bin for calibration data.. but there should be some dmesg to give you a hint about what is missing after it loads fw
<colemickens>
I'm surprised there's not a proper kernel blacklist mechanism, though the rule y'all suspect means I don't really even know which one I'd want to blacklist
<colemickens>
afaict modprobe blacklist won't stop udev from being able to probe it
<robclark>
steev: yeah, that is why I wasn't sure wtf that file had to do with anything