#asahi-alt · 2023-02-18 04:52
mashrafiit does #asahi-alt · 2023-02-18 04:52
chadmedalso make sure your VIDEO_CARDS use expand has "asahi" in it#asahi-alt · 2023-02-18 04:51
mashrafiokay#asahi-alt · 2023-02-18 04:50
chadmedalso mitigations=off does nothing here afaik #asahi-alt · 2023-02-18 04:50
mashrafiapparently i did not enable the drm module =(#asahi-alt · 2023-02-18 04:49
chadmedjust "having" rust is not enough#asahi-alt · 2023-02-18 04:48
chadmedand CONFIG_RUST=y #asahi-alt · 2023-02-18 04:48
chadmedmake sure youve got CONFIG_DRM_ASAHI=m#asahi-alt · 2023-02-18 04:47
mashrafihmm#asahi-alt · 2023-02-18 04:46
chadmedso you have not built your kernel properly#asahi-alt · 2023-02-18 04:46
chadmedthe asahi driver is not loaded#asahi-alt · 2023-02-18 04:46
mashrafichadmed: http://sprunge.us/eGUzBO#asahi-alt · 2023-02-18 03:49
chadmedi dogfood all of this stuff thoroughly before pushing it #asahi-alt · 2023-02-18 03:48
chadmedfrom the outset im going to assume youve done something nonstandard because everything Just Works(tm) with the ebuilds in the overlay#asahi-alt · 2023-02-18 03:47
chadmedmashrafi: paste the output of asahi-diagnose somewhere and link it #asahi-alt · 2023-02-18 03:40
mashrafichadmed: I have run `update-m1n1`. What else is missing?#asahi-alt · 2023-02-17 22:04
chadmed_mashrafi: did you update the device trees? #asahi-alt · 2023-02-17 14:52
mashrafichadmed: I have set the kernel up and merged Asahi's Mesa fork. What else is there to do? 'dbus-run-session startplasma-wayland` does not use the driver, and Plasma does not even start.#asahi-alt · 2023-02-17 14:49
opticronhmmm...I'm itchy enough to get the battery charge limit code that I may end up compiling my own kernel#asahi-alt · 2023-02-17 14:38
mashrafichadmed: I managed to solve it by removing lines containing `mesa` in `/var/lib/portage/world` and using `--backtrace=30`.#asahi-alt · 2023-02-17 13:24
Guest5141@chadmed. I've successfully compiled the kernel with Rust. However, I have a Gentoo system configured with Gentoo's Mesa package. When I try to merge Asahi's Mesa package, I get a dependency conflict.#asahi-alt · 2023-02-17 09:05
mpsby '32bit userspace' I mean complete install of 32bit alpine distro#asahi-alt · 2023-02-17 09:04
mpsbut I enabled COMPAT_32BIT_TIME=y on this kernel#asahi-alt · 2023-02-17 09:04
mpsthough I run some time ago 32bit userspace on 64bit kernel on arm64 machine, all worked#asahi-alt · 2023-02-17 09:03
mpsarnd: didn't tested it extensively#asahi-alt · 2023-02-17 09:03
arndas I said, it makes no difference on 64-bit, as the only change is the set of available syscalls for 32-bit tasks#asahi-alt · 2023-02-17 09:02
arndmps: do you mean you saw no problems on 64-bit applications or 32-bit applications?#asahi-alt · 2023-02-17 09:01
mpsarnd: also I tested systems with COMPAT_32BIT_TIME=n and didn't noticed any problem but I think keeping it enabled is not big problem#asahi-alt · 2023-02-17 09:00
arndmusl currently relies on it being enabled, so you don't have a choice#asahi-alt · 2023-02-17 09:00
arndI know, he cares more about his idea that syscalls can never go away than to actually make systems work in the future#asahi-alt · 2023-02-17 08:59
mpsiiuc it doesn't hurt to have it enabled#asahi-alt · 2023-02-17 08:59
mpsarnd: yes, and that was reason I asked Rich Felker on #musl about this, his advice was to have it enabled#asahi-alt · 2023-02-17 08:58
arndmps: a lot of applications make direct system calls and bypass libc, so COMPAT_32BIT_TIME is meant to help you find stuff that would break#asahi-alt · 2023-02-17 08:57
mpsbut I never know what I will use in future even 2038 year looks far away#asahi-alt · 2023-02-17 08:57
mpsarnd: I use musl on all of my machines and musl fixed Y2038 about year or two ago, iirc.#asahi-alt · 2023-02-17 08:55
arndmps: if you have a 32-bit userland and want to ensure it actually works beyond 2038, you should probably disable it and fix your libc to not call any of the deprecated syscalls, but most people don't need to worry because they will stop running 32-bit userspace before then, or can wait for someone else to fix it#asahi-alt · 2023-02-17 08:51
mpsarnd: ah, ok. I thougt it is needed for Y2038#asahi-alt · 2023-02-17 08:51
arnd(there are some remnants of OSF-1 compatibility in arch/alpha that use 32-bit time_t, but we don't care about those)#asahi-alt · 2023-02-17 08:51
arndmps: it is, but 64-bit architectures never defined a 32-bit time_t, so it has no effect unless you also enable CONFIG_COMPAT#asahi-alt · 2023-02-17 08:50
mpsI meant, 32bit time_t structure#asahi-alt · 2023-02-17 08:50
mpsI thought it about 32bit time_t#asahi-alt · 2023-02-17 08:50
arndah I see, the dependency is just for the default: "default !64BIT || COMPAT", rather than "depends on"#asahi-alt · 2023-02-17 08:49
arndmps: there have been patch proposals in the past to allow compat syscalls to be called from native 64-bit user space such as qemu-user or fex, but those never made it in#asahi-alt · 2023-02-17 08:49
mpsisn't COMPAT_32BIT_TIME syscall compatibility and not code execution (I'm not sure about this)#asahi-alt · 2023-02-17 08:48
mpshm, in my current config is COMPAT=n and I have COMPAT_32BIT_TIME=y#asahi-alt · 2023-02-17 08:48
j`ey(not intentionally)#asahi-alt · 2023-02-17 08:48
j`eyyou can, I have it#asahi-alt · 2023-02-17 08:47
arndmps: CONFIG_COMPAT is not needed, without that I don't think you can even enable COMPAT_32BIT_TIME#asahi-alt · 2023-02-17 08:46
mpsarnd: what you think about COMPAT_32BIT_TIME in asahi kernel? is it needed or not?#asahi-alt · 2023-02-17 08:29
mpsabout CAN net, maybe some users use it for their labs develeping CAN devices (I have two usb can addapters for testing some things)