Linux

48434 readers

942 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r

Kernel Maintenance By a Novice. (lemm.ee)

submitted 2 months ago by squid_slime@lemm.ee to c/linux@lemmy.ml

17 comments fedilink hide all child comments

been using Arch for years but i am still a novice, yesterday i had found that in order for something to work on my system i will need to edit a few lines in kernel which i did, then removed unnecessary modules > intel, > nvidia, compiled. it worked great but with Arch and its rolling release i am dreading the next update and having to go through this again.
what methods are there to automate this process?

you are viewing a single comment's thread
view the rest of the comments

[–] Static_Rocket@lemmy.world 10 points 2 months ago (1 children)

What modifications were required? The good part of a rolling release is that upstreaming things means you only have to deal with manual fixes for like 2 or 3 updates.

[–] squid_slime@lemm.ee 6 points 2 months ago* (last edited 2 months ago) (2 children)

set LINK_TRAINING_ATTEMPTS from 5 to 10 in drivers/gpu/drm/amd/display/dc/link/link_dpms.c and set LINK_TRAINING_RETRY_DELAY from 50 to 100 in drivers/gpu/drm/amd/display/dc/link/protocols/link_dp_training.c.

i doubt this will be added to kernel as its a fix for an issue that isn't wide spread.

[–] Static_Rocket@lemmy.world 19 points 2 months ago (2 children)

That wouldn't be accepted as is, but those sound like tunables. They could be exposed as kernel parameters. May be worth submitting the patch as an RFC just to call attention to it.

[–] squid_slime@lemm.ee 6 points 2 months ago

thank you i will read up on how to submit this kind of stuff.

[–] squid_slime@lemm.ee 1 points 2 months ago (2 children)

I followed your advice, Github my edit link_dpms.c, - Github my edit link_dp_training.c how do i submit as RFC. total noob with github lol.

[–] fool@programming.dev 4 points 2 months ago (1 children)

Successful GitHub pulls are rare; more often, patches live like this. You're better off contacting the maintainer of the subsystem you're editing. See the official submission guide.

Not to be dejecting!

[–] squid_slime@lemm.ee 3 points 2 months ago* (last edited 2 months ago)

thank you and no dejection taken. you're actually very helpful :D

[–] Static_Rocket@lemmy.world 3 points 2 months ago

Ah, so the kernel actually uses mailing lists. You need to use the get maintainers Perl script to get the people you need to send the email TO and then send it to them with the dri-devel list CC'd.

[–] imecth@fedia.io 8 points 2 months ago (1 children)

Use diff patches and automate with some bash scripting.

[–] squid_slime@lemm.ee 1 points 2 months ago

cheers, I'm using sed to patch the files then auto mated compiling