Requesting Linux Kernel Sources

[Laika]

When and how do i get a hold of it? Steam Support shoved me here. :/
Specifically the SteamOS Kernel Sources. So i can build the kernel for myself and have working audio outside of using the Binaries..
Thereof i wonder and want to ask, can a user request them and where do i send my email to?
When will the 5.13.x sources be public?

Edit: Since this is top google search result somehow:
unofficial mirror: https://gitlab.com/evlaV/linux-integration (as mentioned below )
Status as of 2023 September. Upstream kernel works. Gamepad works using sc-controller or installing steam.
Audio should work now ootb. If having trouble getting it to work, dig trough the evalV mirror.
Valve is terrible in making source access easy. This is exactly like the Android early times, whereby only one vendor benefits. it feels.
Sources by valve itself are still only here: https://steamdeck-packages.steamos.cloud/archlinux-mirror/sources/jupiter-main/

[@R+5]

who knows if theres a way for common users to access them, but maybe you should check the guys that are trying to adapt steamos v3 for "common pcs" (i read that currently they were only able make it work with radeon gpus, and i think maybe integrated graphics).

maybe those guys know more about what is currently possible in relation to what you want.

[tekchip]

HOLOISO is the name of the project. https://github.com/theVakhovskeIsTaken/holoiso They're pulling code from somewhere.

[Laika]

Appears someone hosted them but that seems sketchy
https://github.com/theVakhovskeIsTaken/valve_linux_neptune
I wonder where Valve's upstream repo is?

[Emispin]

Ok this is crazy. Technically the sources are accessible which probably meets bare minimum obligations under GPLv2, but I think the sources need to be way more transparently accessible and come with some basic build instructions. And Valve seriously needs to respond to GPL requests in a compliant manner. Maybe try emailing their copyright request/DMCA email as that probably goes to actual lawyers instead of front line support.

So here's how I managed to get the sources. I haven't tried building anything yet.

https://steamdeck-packages.steamos.cloud/archlinux-mirror/sources/

You have to download the `.tar.gz` files in the `jupiter/` directories which start with `linux-neptune`. Then, you have to go to even more trouble. You have to rename `archlinux-linux-neptune` folder, which is really a `.git` folder, to `.git`, then you have to set the Git work tree to the root of the repo, and then reset the working tree on a branch, I did `master`. Then you'll have kernel tree on your filesystem.

They're doing development on the kernel in this project on a Valve-hosted GitLab instance, but of course the kernel integration repository is not publicly accessible, and neither is the issue tracker. https://gitlab.steamos.cloud/jupiter

I'd love for them to be doing development in a more open manner as I think the community could definitely contribute patches.

[Briggs]

Originally posted by Farrow:

When and how do i get a hold of it? Steam Support shoved me here. :/
Specifically the SteamOS Kernel Sources. So i can build the kernel for myself and have working audio outside of using the Binaries..
Thereof i wonder and want to ask, can a user request them and where do i send my email to?
When will the 5.13.x sources be public?

It's really strange that we still don't have source code for this. I mean, doesn't the GPL require the publication of source code?

[Laika]

Originally posted by Michaelspin:

Ok this is crazy. Technically the sources are accessible which probably meets bare minimum obligations under GPLv2, but I think the sources need to be way more transparently accessible and come with some basic build instructions. And Valve seriously needs to respond to GPL requests in a compliant manner. Maybe try emailing their copyright request/DMCA email as that probably goes to actual lawyers instead of front line support.
..
https://steamdeck-packages.steamos.cloud/archlinux-mirror/sources/

...
I'd love for them to be doing development in a more open manner as I think the community could definitely contribute patches.

Thanks for finding this, but this is still terrible. Will try building them and perhaps i can finally nuke SteamOS off the deck. (been using a 500gig sdcard with gentoo on it)
I been Dealing with Rockchip kernel sources before and they just put it on github, its amusing how a Chinese SOC maker gives better access to sources than valve.. lol

[Yeti]

Originally posted by Insignia:

Linux users will do anything to feel like they are special and smart.

This isn’t about being special or smart. Anyone who uses the Linux kernel has certain legal obligations that they have to follow. Valve doing the bare minimum and obfuscating this legal requirement is a faux pas, especially in the Linux community.

[Zelmor]

Originally posted by Michaelspin:

Ok this is crazy. Technically the sources are accessible which probably meets bare minimum obligations under GPLv2, but I think the sources need to be way more transparently accessible and come with some basic build instructions. And Valve seriously needs to respond to GPL requests in a compliant manner. Maybe try emailing their copyright request/DMCA email as that probably goes to actual lawyers instead of front line support.

So here's how I managed to get the sources. I haven't tried building anything yet.

https://steamdeck-packages.steamos.cloud/archlinux-mirror/sources/

You have to download the `.tar.gz` files in the `jupiter/` directories which start with `linux-neptune`. Then, you have to go to even more trouble. You have to rename `archlinux-linux-neptune` folder, which is really a `.git` folder, to `.git`, then you have to set the Git work tree to the root of the repo, and then reset the working tree on a branch, I did `master`. Then you'll have kernel tree on your filesystem.

They're doing development on the kernel in this project on a Valve-hosted GitLab instance, but of course the kernel integration repository is not publicly accessible, and neither is the issue tracker. https://gitlab.steamos.cloud/jupiter

I'd love for them to be doing development in a more open manner as I think the community could definitely contribute patches.

You build it like any other kernel branch. If you cannot build it without instructions, you shouldn't be mucking with it in the first place.

[Emispin]

Originally posted by Zelmor:

Originally posted by Michaelspin:

Ok this is crazy. Technically the sources are accessible which probably meets bare minimum obligations under GPLv2, but I think the sources need to be way more transparently accessible and come with some basic build instructions. And Valve seriously needs to respond to GPL requests in a compliant manner. Maybe try emailing their copyright request/DMCA email as that probably goes to actual lawyers instead of front line support.

So here's how I managed to get the sources. I haven't tried building anything yet.

https://steamdeck-packages.steamos.cloud/archlinux-mirror/sources/

You have to download the `.tar.gz` files in the `jupiter/` directories which start with `linux-neptune`. Then, you have to go to even more trouble. You have to rename `archlinux-linux-neptune` folder, which is really a `.git` folder, to `.git`, then you have to set the Git work tree to the root of the repo, and then reset the working tree on a branch, I did `master`. Then you'll have kernel tree on your filesystem.

They're doing development on the kernel in this project on a Valve-hosted GitLab instance, but of course the kernel integration repository is not publicly accessible, and neither is the issue tracker. https://gitlab.steamos.cloud/jupiter

I'd love for them to be doing development in a more open manner as I think the community could definitely contribute patches.

You build it like any other kernel branch. If you cannot build it without instructions, you shouldn't be mucking with it in the first place.

Woha, hold your horses. I never said I couldn't figure it out - I just haven't tried yet, and there's no point as I don't have a Deck yet.

I am used to kernel development on ARM platforms, where the build isn't always as straightforward.

[Logan]

Would be nice if they provided a patchset instead of just the whole source tree too. Would make it easier to forward-port their changes to later kernels, and track how much work is needed to run mainline. Not to mention make it easier for the community to help get patches upstreamed. Are they active on the LKML?

[Emispin]

After familiarizing myself a bit with how the Arch build system works, I've found that the evlaV mirror works well and has been a godsend in terms of convenience: https://gitlab.com/evlaV/linux-integration

You can use the PKGBUILD here to build pacman packages with makepkg; this also contains the config: https://gitlab.com/evlaV/jupiter-PKGBUILD/-/tree/master/linux-neptune

I've compiled the current WIP 6.0 branch (`6.0/cristicc/wip-integration`) by editing the PKGBUILD and it works on my Deck (sound from the speakers is broken though, I imagine it may be fixed with some patches that haven't been upstreamed or merged into the branch yet or some fixes in the config that I haven't been able to find - there's no config from Valve that I can find for the WIP 6.0 kernel). There are some spurious errors when installing the kernel and headers packages with `pacman -U`, but it boots just fine.

It would be great if Valve opened up their Gitlab repositories got rid of the need for this mirror.

[Briggs]

I would argue that Valve has done just about everything write from a pro-consumer standpoint. However in this regard they are failing horribly. I'm sure they are fulfilling their legal obligations—their lawyers would see to that—however I feel like it's only due to some kind of loop hole. I can't imagine how they could release a GPL licensed product and not also release the source without exploiting a loophole.

[Laika]

Still not seeing any attempt of them up-streaming the audio drivers.
Honestly if i knew that this kernel source bs is so ♥♥♥♥ i would have never bought one.
I'd rather buy a OneXPlayer 1S, they upstream the drivers it requires. (so far)