Linking / advertising your own repositories is not allowed. Please refrain from doing so.
The newest (latest) kernel for Solus (6.0)
Harvey removed the Needs More Information tags .
Harvey So how do you want me to show the files for assembly? If it were possible to place it on your site I would do so. I just wanted to help the community get the latest kernel. Yeah... This forum once wrote that packing a new kernel is difficult. That's why I came to ask for help so that then Solus developers would just merge the 2 repositories and users would get the latest kernel. But instead of helping, my post was just deleted. Cool.
Since this discussion continued on IRC, and so people reading here have some more info: The problem was the hosting of ready-made eopkg files for users to install, not the package.yml and other files necessary to build a kernel package. Apart from that it was noted that this sort of help was not requested, and usually happens on the dev tracker instead of some random GitHub repository. Any actual cooperation regarding kernel updates would have to be coordinated with DataDrake to be useful.
(That's about it for a quick summary)
- Edited
Staudey Thanks. The guidelines prohibiting people from posting links to private eopkg's and repositories are longstanding, well known, and have been consistently enforced for as long as I have been reading this forum. The rationale behind the guidelines -- ensuring that packages with the Solus imprimitur, official or not, are curated, thoroughly tested, and well maintained -- makes a great deal of sense, doubly so, it seems to me, in the case of a core element like the kernel.
tomscharbach solus mods have always put the kibosh on those advocating for their own unofficial packages and repos, all solus-tweaked, and ready to rock. A part of me loves the wild west industriousness of these solus users....but that is better left to unofficial channels, not the forum. Besides Flatpak and an appimage, I personally ride with "the Solus imprimitur" only because I depend on this OS 24/7. As long as I've kept it clean it's always delivered
Too bad I couldn't get help from the community. So I spent more time and effort to install 6 kernel in my solus distribution. I hope that in the future your kernel guy will offer me a fix or a patch.
ketronixdev How did you get the latest kernel installed !!
I don't know what was deleted, I am assuming there was link to prebuild binaries. I think package.yml will not be deleted, or maybe a link to blog. I am really looking for a kernel update.
ketronixdev Too bad I couldn't get help from the community. So I spent more time and effort to install 6 kernel in my solus distribution. I hope that in the future your kernel guy will offer me a fix or a patch.
My experience (packaging Microsoft Edge into an eopkg, installing in a private repository and maintaining for about 9 months until a Flatpak was developed) is that ongoing maintenance/updating is our personal responsibility, not the team's. I think that others who have developed private eopkg's and repositories found this to be true, as well.
Abhinav1217 Yes, I mistakenly sent packages to the repository as well. But I will remove them in the next commit. I'm also building a zen kernel for solus right now. So far I haven't gotten permission to post the repository link. So alas I can only say that look for yourself) Alas. The team of moderators considered my help to the community "unnecessary"
- Edited
ketronixdev I personally build a liquorix patched kernel for my gaming machine. At the moment I have problems building the kernel. Did you make any adjustment to the package.yml besides kernel src and config file?
Edit: Found your repo, build still doesnt succeed for me with the unstable repo.
kaktuspalme I just created and sent the files to the linux-zen repository, I suggest you clone it and try to build it. I took a normal kernel, and in addition to the solucha patches I put a patch for zen.
- Edited
ketronixdev Yes I tried it, but using the unstable repo it doesn't build. But I can now finally build it, using solbuild and the main profile.
Edit:
@ketronixdev Btw. I understand that you probably don't like the teams decision. But it's a rule here which I personally can understand. There's only a small amount of people involved in this project and if users start using repos not maintained by the team, it's very hard to give support in the forum. Especially if someone is using a repo with core things like the kernel.
kaktuspalme At the moment I am still in the process of building a kernel zen (I understand your version of the kernel is the same but with a different name). As soon as I have a successful compilation and can boot from this kernel, I will make a release to the repository. But if your kernel is different from zen, I would like to get a link to the source code, or patches. And I would be happy to build a kernel for you. Like. Here's to star)))
kaktuspalme Alas and ah, since they won't let me submit links, I'll just do the job. Just so someone will appreciate it later. And maybe join in.
ketronixdev Not necessary, but thanks for your offer. My build is already booting.
I personally removed all the solus patches and just use liquorix patch + the liquorix kernel config. And it's now building again using the stable repo.
kaktuspalme There would then be some installation problems, which is why I took the package.yml from linux-current in the solus repository as the basis and edited it.
ketronixdev I also use the linux-current as a basis I even didn't edit the name.
Abhinav1217 And by the way, I got your message a bit wrong (my English is a bit bad, my native language would not be understandable to you), I downloaded the package.yml from the solus repository, with instructions to build the kernel, which I later edited, and thus got the 6.0 kernel on my system
kaktuspalme I recommend that you copy and paste yourself the build instructions which are posted in the install section, I edited something there too, because after building the kernel now does not create some of the files that it created in the 5.15 release.