<lavaball>
lsmod is lying to me! rfkill 24576 1 cfg80211 product specifications say: no wifi. oh, never mind .wrong product page. i have wifi! crap. i have wifi.
lavaball has left #crux [#crux]
lavaball has joined #crux
<lavaball>
says here Only the following wireless adapters have been evaluated for regulatory compliance for use with the Intel NUC Kit DE3815TYKHE in all regions:... but i haven't installed anything. also i didn't see anything in there and no antennas and nothing.
ukky has joined #crux
<SiFuh_>
lavaball: Ahh the file you are looking for or requesting is regulatory.db used by the Linux Kernel. Not all Wi-Fi adapters follow this though. Mostly no one cares because most adapters are way below the regulatory limit already.
<lavaball>
anwyay, i'm compiling. Intel(R) Atom(TM) CPU E3815 @ 1.46GHz Fill By OEM CPU @ 1.4GHz. see you in two weeks.
<SiFuh_>
Hehe
<SiFuh_>
HAHA
lavaball has left #crux [#crux]
lavaball has joined #crux
<lavaball>
god damn console controls! ctrl w - delete last word, here - close window.
<lavaball>
anwyay, i'm still contemplating if it was wise to not go with an out of the box solution.
lavaball has quit [Remote host closed the connection]
groovy2shoes has quit [Remote host closed the connection]
groovy2shoes has joined #crux
lavaball has joined #crux
<SiFuh_>
farkuhar: I followed almost every exact measurement and cursed the use of grams. Anyway all went well but the Biga never rised. I warmed it up and it started to rise. I mixed everything together and nothing happened. Hahaha.
<SiFuh_>
I did sample the raw dough and it tastes great!
<SiFuh_>
So, I will put the entire thing in the refrigerator overnight, add some flour again and some yeast and re-knead it. That way I can salvage the dough.
<SiFuh_>
From what I see the liquids are way too high. Or they were not measured in grams but in ml. Water ml and Milk ml are not the same measurement in grams for example
<SiFuh_>
So I don't know, I can only say it was a bit wet for what a bread dough should be. Also, I have never had to flour, oil or wet my hands to knead dough. That seemed strange to me. The autolysis was great! But no worries, it can be salvaged.
<SiFuh_>
Kind of really wanting to try it now because after 24 hours, the raw dough tasted awesome
serpente has joined #crux
<farkuhar>
SiFuh: thanks for the feedback. In a humid environment like Malaysia, it's hard to prevent flour from absorbing moisture out of the air. Those liquid measurements in my recipe were based on the assumption that the flour would be more dry.
<farkuhar>
Even in mid-latitudes, I find I have to adjust the liquid measurements every time the seasons change. The flour never has the same moisture content from one season to the next.
Guest30 has joined #crux
<SiFuh_>
farkuhar: That could be it. I did seal everything moisture tight but humidity here pisses me off a lot. In Australia I change the mealworm bed once every few months. Here it is every couple of days.
<SiFuh_>
I left them alone for 14 days with a fresh dry bed and came back to find they are almost all gone. Poor bastarads drowned. I was not happy
<Guest30>
guys may i paste a foot print missmatch with pulseaudio ?
<SiFuh_>
Maybe you can test my plain flour recipe there and see if there is a difference.
<SiFuh_>
Guest30: If it is more than 3 lines, use dpaste or that xi.io thing
<SiFuh_>
These measurements are precise and never need changing here in Malaysia. Maybe you can attempt it there and see if your lack of humidity causes it to become more dry
<Guest30>
i uninstall bash-completion pkgrm bash-completion and i dont get the last lines of the footprint
<SiFuh_>
That means you have something installed that was detected that the port maintinaer didn't have installed when they built it.
<SiFuh_>
This is not an error or a bad thing. It is more like a notification and for many of us we just configure to ignore NEW
<SiFuh_>
/etc/pkgmk.conf and can set PKGMK_IGNORE_NEW="yes"
<Guest30>
ahhhh ok
<Guest30>
like this i know
<SiFuh_>
If you see MISSING then you should be concerned ;-)
<SiFuh_>
Actually it would be nice if the ERROR was changed to a WARNING for that. But it is kind of universal so..
<SiFuh_>
Or a message that says "If you see NEW, don't panic"
<Guest30>
cool
serpente has quit [Read error: No route to host]
<farkuhar>
SiFuh_: I suspect that your recipe would be very difficult to knead, using the flour in my pantry. I'll give it a try, though.
<Guest30>
now another question lets say i want to install jack from your collecction yenjie, i download the httup link and i use pkgmk in the folder... correct?
<SiFuh_>
farkuhar: my wife makes it. She comaplins it is too dry. I tell her to not modify. The one time she did, the bread flopped like a cake.
<SiFuh_>
Guest30: Downloat the httpup or git file. You then do ports -u yenjie then you can do prt-get depinst jack and no need to be in the directory.
<SiFuh_>
If you wish to use pkgmk you can do in the directory but you will not be building any deps that jack requires and just build only jack itself, and this may fail because of missing deps
<farkuhar>
SiFuh's IRC client did not try to interpret /etc/pkgmk.conf as an IRC command. I've been bitten by such parsing errors when I forget to insert a leading space in a comment that starts with a slash.
<Guest30>
where do i download the httpup file? do i create mkdir /usr/ports/yenjie ?
<SiFuh_>
I used space farkuhar
<SiFuh_>
Guest30: I don't know if jack(2) works anymore. It is 8 months olf
<SiFuh_>
New files found isn't really a warning, but it is acceptable
<SiFuh_>
What I actually meant is for those whom have not modified pkgmk.conf
<farkuhar>
Yeah, that's a problem when the hard-coded defaults diverge from recommended practice. As Fun writes in FS#1313, "It looks like most people use the default way (code) or the recommended way (comments/wiki/fake news) ... It is confusing to have the docs so different than the code/defaults."
<farkuhar>
Fun actually proposed a new pkgmk feature (FS#1576) to avoid spurious warnings of mismatched footprints like the one Guest30 shared today. Fun's hasty dismissal of PKGMK_IGNORE_NEW=yes as a valid solution, I found unpersuasive.
<farkuhar>
That said, with the trend toward flexible Pkgfiles, there's an argument to be made that PKGMK_IGNORE_NEW=yes should actually be the default. The rare user who installs only inflexible ports (with every compile-time option hard-coded) can set it back to "no" easily enough; everyone else will have errors downgraded to warnings, as SiFuh suggested.
<SiFuh_>
I was one of the guys who actually voted no
<SiFuh_>
I liked the way the original pkgmk.conf was set and it should be emphasized highly in the handbook since everyone that uses crux begins there
<SiFuh_>
But for a warning saying "Hey this is a new thing, don't panic, don't worry, it is going to pass"
<SiFuh_>
Problem with a warning is once it compiles you won't see it again.
<SiFuh_>
The error on the other hand stops dead in its tracks, then you can see why
<SiFuh_>
What if we had a way of informing the users at the very end that this failed, this was successful and these from this were new entries?
<farkuhar>
"at the very end" of what, though? If you're just running pkgmk in the port directory, then warnings or errors should not disappear into the scrollback buffer; they remain visible once pkgmk stops. But for multiple pkgmk processes orchestrated by prt-get, there aren't the necessary data structures to retain all the NEW footprint entries until the post-transaction report.
<SiFuh_>
farkuhar: huh?
<SiFuh_>
pkgmk ends at one pkg
<SiFuh_>
prt-get ends at the entire attempt
<farkuhar>
Unless using grpinst, that is. But consider how many details of the individual pkgmk processes are already being discarded. Quoting from the linked notes in the last comment of FS#1910: "teodor's second observation is more interesting. During dependency resolution, the invalid arguments (ports not found in the active repos) were silently being dropped, rather than being kept in memory for a
<farkuhar>
post-transaction report."
<SiFuh_>
WTF is a grpinst?
<SiFuh_>
I have never even heard of this thing haha
<guest683>
I think, new version this guys did not released for a long long time (xwayland have another release cycle)
<guest683>
so, this patches remove tearfree on mesa drivers. This is remove depends on any compositors and add performance ;) In FF after 115 we have native support VAAPI if we use modesetting driver. On xf86-intel driver native support disabled.
<guest683>
or Crux users just leave Xorg and use Wayland? But any WM in wayland use their own implementation...
<guest683>
sorry, my eng IS still terrible
<r0ni>
i'm using xorg, dont appear to have tearing issues
<r0ni>
but i mean, xorg is known for tearing in FF to my knowledge
<guest683>
Any DE include compositor, WMs - not, on my Intel video and modesettings tearing everywhere - FF, mpv etc...
<r0ni>
i'm using xfce4 on crux, and things seem good in my uses
<guest683>
and video adapter?
<r0ni>
intel hd3000
<guest683>
hm.. And u did not use any picom/compton? And u use FF or Chrome(any)? If u watch video in Youtube, do u have a tearing or not?
<r0ni>
nope just have xfwm4 and using FF and there's no tearing on youtube
<guest683>
well, u are lucky guy. ;)
<serpente>
you can use picom v-sync, but particularly i prefer to set TearFree on Xorg conf
<serpente>
my config looks like this:
<serpente>
/etc/X11/xorg.conf.d/20-amdgpu.conf
<guest683>
thanks for your answer. But after this patch no needed any picom!
<serpente>
Section "Device"
<serpente>
Option "TearFree" "true"
<guest683>
I understand, what u mean. So, this patch added this section 'Option "TearFree" "true"' in modesetting driver
<guest683>
Option "TearFree" "true" before works only in old intel driver. Most distros today use mesa driver
<serpente>
true
serpente has left #crux [ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.1)]
serpente has joined #crux
<guest683>
>← serpente has left (ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.1))
<guest683>
lol
<guest683>
IRC in Emacs with tree-sitter, eglot and jit
<guest683>
serpente: do u recompile gcc in Crux for enable support native compilation for Emacs?
<guest683>
need add here --enable-languages=c,c++,lto new option - 'jit', but for this need mirrored in local repo and set prior in prt-get... If I did not forgot...
<guest683>
cheers, guys, see ya
guest683 has quit [Quit: Client closed]
disapper4nce has joined #crux
disapper4nce has quit [Quit: leaving]
disapper3nce has joined #crux
disapper3nce has quit [Client Quit]
Guest30 has joined #crux
Guest30 has quit [Client Quit]
Guest30 has joined #crux
Guest30 has quit [Quit: Client closed]
farkuhar has left #crux [#crux]
lavaball has quit [Remote host closed the connection]