Linux 7.0 is ready for release, with many exciting changes

How do we fix this? Should i complain to ICANN that my FunnyWeirdProtocol packets are being dropped while they shouldn't? Do i sue my ISP for breaching net neutrality rules? Perhaps it would be better to contact hardware manufacturers to ensure support for any L4 protocol?

[-]

nelmaloc@reddit

Can't read the tone of this message, but

How do we fix this?

Go the QUIC route and obfuscate the hell out of FWP. Enforce the end-to-end principle.

Should i complain to ICANN that my FunnyWeirdProtocol packets are being dropped while they shouldn't?

ICANN doesn't have enforcement powers, it's just a glorified database.

Do i sue my ISP for breaching net neutrality rules?

Net neutrality is only about ISP charging the same for all services.

But yes, you should talk to your ISP. Offering a sub-par service isn't illegal.

Perhaps it would be better to contact hardware manufacturers to ensure support for any L4 protocol?

Hardware manufacturers don't control what the customers of their devices do.

[-]

spin81@reddit

I like the last point but the other ones feel like they're more that they're cool than actual reasons to want to use IPv6 at home. Don't get me wrong, that's not criticism: Linux is all about using it the way you like it.

[-]

Preisschild@reddit

SLAAC + mDNS (no static dhcp assignements and needing to remember ips) is great too!

Also Matter/Thread, which are ipv6-native

[-]

jrcomputing@reddit

I prefer to do the opposite. I go exclusively IPv4 in my kernels, because my ISP is 4 only and it's easier to match.

[-]

NamedBird@reddit

And you can already do that.
I just want to do the same as you but with IPv6...

[-]

MrMelon54@reddit

I am also excited for this, it will probably end up in 7.1 or 7.2 at this rate.

Unfortunately you would still need to compile IPv4 into the kernel for IPv6-mostly networking, unless you are a very special individual who manages to use no software with hardcoded IPv4 literals.

[-]

blackcain@reddit

I'm mostly looking forward to the ACPI suspend fixes for Lunar Lake on my Lenovo Yoga - damn thing at time wont come out of sleep. :P

[-]

F9-0021@reddit

I had similar issues on my laptop with discrete Arc graphics. Best I could figure was some graphics driver thing not playing nicely with the sleep function. Eventually it kind of went away on its own, presumably with updates to the graphics driver.

[-]

myreditacount11@reddit

I had this exact issue on my ASUS Vivobook with the Core 258V. I am on windows still but what fixed this issue was a setting in the intel graphics application called “Panel Self Refresh” under the Display tab. Is there a way to use that application on Linux?

[-]

F9-0021@reddit

Nah, there's no IGS application for Linux. At least for me with Alchemist, the wake from sleep issues were solved on Windows since mid to late 2023 iirc.

[-]

myreditacount11@reddit

For me I was having the issues on windows since 2025. I wasn’t aware of lunar lake before 2025.

[-]

Scholes_SC2@reddit

Same thing for my acer a515

[-]

myreditacount11@reddit

Hey man I had this exact issue on my ASUS Vivobook with the Core 258V. I am on windows still but what fixed this issue was a setting in the intel graphics application called “Panel Self Refresh” under the Display tab. Is there a way to use that application on Linux?

[-]

Scholes_SC2@reddit

Don't really know, i use the open source driver. Maybe installing the intel driver would offer that option but I wouldn't know

[-]

myreditacount11@reddit

That setting completely fixed the issue of the laptop refusing to wake up or screen turn on after opening the lid

[-]

rv77ax@reddit

Is this random thing that cause the screen sometimes blank after wake up? Which Lenovo Yoga model did you have?

[-]

myreditacount11@reddit

Hey man I had this exact issue on my ASUS Vivobook with the Core 258V. I am on windows still but what fixed this issue was a setting in the intel graphics application called “Panel Self Refresh” under the Display tab. Is there a way to use that application on Linux?

[-]

blackcain@reddit

Yep that's the one. Lenovo yoga aura by Intel. Apparently they were using some Microsoft standard that wasn't in the kernel

[-]

myreditacount11@reddit

Hey man I had this exact issue on my ASUS Vivobook with the Core 258V. I am on windows still but what fixed this issue was a setting in the intel graphics application called “Panel Self Refresh” under the Display tab. Is there a way to use that application on Linux?

[-]

ntropia64@reddit

Odd, I have a Lunar Lake X1 Carbon with Debian 13 (no fancy rolling release, vanilla kernel) and it worked out of the box.

Maybe a DM/distro-specific issue?

[-]

Smartich0ke@reddit

Same thing with my MSI b550 g3 motherboard. Endless bizarre problems with suspend.

[-]

glhaynes@reddit

I keep hearing how on Linux version numbers, the major number bump (well, first number, since it’s not semver) doesn’t mean anything… but it seems like there’s been a lot more discussion around 7.0 than, say, 6.19. Is this just people thinking it means something more than it does or is 7.0 a relatively large release relatively?

[-]

ray591@reddit

Linux doesn't follow semver strictly. But major number releases tend to be large. It's more like vibe releasing.

[-]

wintrmt3@reddit

Linux doesn't follow semver at all, what would it even mean? It never breaks userspace so there would be no major release ever, or it always breaks kernel modules, so all versions would have to be major?

[-]

CryptographerNo8497@reddit

It breaks user space all of the fucking time

[-]

wintrmt3@reddit

Any particular example?

[-]

CryptographerNo8497@reddit

Like mongoDB not starting on the most recent kernel?

[-]

wintrmt3@reddit

Semver is about intentional breakage, not bugs.

[-]

CryptographerNo8497@reddit

This isnt a bug, this was a very intentional change that broke the memory allocator used in mongodb.

[-]

nelmaloc@reddit

it always breaks kernel modules, so all versions would have to be major?

Yeah? It's how systemd does it.

[-]

wintrmt3@reddit

Linus would run out of fingers and toes very soon then.

[-]

nelmaloc@reddit

He just needs to ask for a finger in exchange for patch privileges to new developers.

[-]

MelioraXI@reddit

7.0 is a huge release, lot of improvements in various areas. While not designated as a LTS kernel, Ubuntu 26.04 will use it as such.

[-]

spin81@reddit

Being aware of this, that confused me: my question when reading the post title was, wait is the 7.0.0 kernel not out yet? Because it feels weird to me that they would put an unreleased kernel in an LTS release. OTOH I would not be surprised if some people on the Canonical kernel team were kernel contributors themselves.

[-]

foo@reddit

Linux 7.0 is not released yet, but neither is Ubuntu 26.04, which is the Ubuntu version that will use 7.0 7.0 will be released tomorrow, so by the time Ubuntu 26.04 releases on the 23rd the kernel will be officially released.

[-]

paeschli@reddit

Are there any risks associated with how close the two releases are ? I don't know if this is 'usual practice' to work with such short notice or whether Ubuntu is making an exception given the large number of improvements.

[-]

foo@reddit

I'm probably not the best person to ask, but personally I'm not worried about it. Of course new software inherently has less real world testing in the field compared to older software. But Linux releases tend to be quite stable.

It's also not like kernel releases get thrown over the fence and that's the first time anyone sees the new code. Linus releases weekly release candidates during the kernel development process, and with linux development being completely public everyone has access to any development in between the RCs too. I'm sure Ubuntu has been integrating and running pre-releases of linux 7.0 since 7.0 development started. They have had almost 2 months to find and fix issues not only in the kernel but also how the new kernel works together with all the other software they intend to release with Ubuntu 26.04.

But if your system stability is very important to you, wait for Ubuntu 26.04.1. But in this case I'd recommend this anyways, no matter how old the kernel was at the release of the distro. That's also how Ubuntu handles their LTS updates. Ubuntu 24.04 LTS will only show upgrade notices once 26.04.1 is released.

[-]

haakon@reddit

How could they just "use it as such"? Are they just going to backport fixes to a non-LTS kernel for years on end?

[-]

sylvester_0@reddit

IIRC Ubuntu LTS versions have also eventually bumped up to newer kernel versions during their support cycle. So they could just use 7.0 as a bridge to a later upstream LTS.

[-]

Infinity-of-Thoughts@reddit

Yes? They'll backport any fixes that affect their kernel.

That's what Ubuntu has always done.

[-]

JockstrapCummies@reddit

With the LTS Enablement Stack though, you can get kernel version upgrades even when sticking with an LTS release of Ubuntu.

[-]

Infinity-of-Thoughts@reddit

Yes, but those kernels are still Ubuntu kernels, not the LTS kernels from kernel.org

[-]

JockstrapCummies@reddit

Yes, but back in the day (I don't know if it's still true or not these days) the Ubuntu specific patches were useful, e.g. AppArmor needed downstream patches.

[-]

rantingdemon@reddit

Linux himself says a release like this doesn't mean anything significant. He says he goes to a x.0 release just because he only has 20 fingers and toes.

[-]

esmifra@reddit

Linus. But despite the numbers don't mean anything except an increment, this release in particular has a lot of new stuff.

[-]

rantingdemon@reddit

Autocorrect fail

[-]

esmifra@reddit

Happens to the best of us. And as fail goes it could be a lot worse.

[-]

Neither-Phone-7264@reddit

i love Microsoft Windows™ Torvalds

[-]

thegreatpotatogod@reddit

Microsoft Windows™ Gates

[-]

NoTime_SwordIsEnough@reddit

Pro tip: If you want information on MS Gates, the Epstein Files documents him pretty well.

[-]

the_bighi@reddit

/r/YourJokeButWorse

[-]

Forward_Froyo_429@reddit

what if he loses a toe?

[-]

ZX_BURP_77@reddit

We can assume it's already happened, as version numbers only go to .19 now.

[-]

ggppjj@reddit

The number 0 gets the respect, and thus the finger, it deserves. All 20 digits are filled, there is no overflow.

[-]

StillNewspaper4799@reddit

You 0 simps always make me laugh. It's literally the smallest possible amount, nothing, nil, an absence of any value.

It can only be useful with other numbers. 0 is the sidekick number. Good at what it does, sure. But always a sidekick.

[-]

MrWeirdoFace@reddit

Some folk will never lose a toe, but then again some folk'll.

[-]

Vespytilio@reddit

The kernel versioning system changes. Retroactively. Every x.19 release shifts to a .0, throwing Linux versioning into chaos.

They have plans in case Linus gets hit by a bus. There's no contingency or hope if Linus loses a toe.

[-]

tanksalotfrank@reddit

What if a bus hits only his toe?

[-]

Vespytilio@reddit

In that situation, they cut off one of Kroah-Hartman's toes and stitch it onto Torvalds' foot.

[-]

Valefoth@reddit

Yeah you know, Linux created Geat to version Linus

[-]

the_humeister@reddit

Ah yes,nLonux Torvalds, the man who created Linus.

[-]

mglyptostroboides@reddit

Actually, Nils and Anna Torvalds made Linus.

[-]

kinleyd@reddit

Lol. You crack me up!

[-]

TheG0AT0fAllTime@reddit

John Linux

[-]

MrWeirdoFace@reddit

Narrator: John Linux was a New York cop with a reputation for destruction, but now he's being teamed up with a new partner...

[-]

FiftySix57@reddit

This is diabolical..

Diabolically good tho 🥴💀😂

[-]

Originzzzzzzz@reddit

Dont make light of big Linux, Linus Torvalds is his greatest creation yet, it will do great things

[-]

tanksalotfrank@reddit

Mr. John Linux?

[-]

TheG0AT0fAllTime@reddit

John Linux

[-]

redundant78@reddit

it's purely people getting hyped over a round number. Linus bumps the major version just because he doesn't like the minor number getting too high (he said he starts running out of fingers and toes lol). the actual release cycle and amount of changes is basically the same as any other release.

[-]

ilep@reddit

They are all "large" releases these days.. There are again notable changes but so does every release.

[-]

Business_Reindeer910@reddit

he doesn't care about the number, but people who contribute fixes and people who write about releases seem to care.

[-]

2rad0@reddit

I keep hearing how on Linux version numbers, the major number bump (well, first number, since it’s not semver) doesn’t mean anything…

Ignore the karma farmers and parrots, your intuition is correct here, just because the guy changing the number says something doesn't mean the hundreds of other individuals are on the same page.

[-]

Ill_Reindeer_5046@reddit

Yeah as it said so in the very first sentences of the article.

[-]

glhaynes@reddit

I think this is trying to be a "you didn't read the article" gotcha but I read the article and it doesn't seem like you read my questions.

I said, it just seems like there's tons of talk about this being a huge release that I don't remember seeing before for previous kernel versions. So my question was: is this just a normal release and people are acting like it's particularly big because of ignorance? Or is it actually particularly big; and, if so, is that just by random coincidence?

[-]

CulturedHollow@reddit

Must be because it 89

[-]

MrScotchyScotch@reddit

I still can't get off 6.8.0 because my fucking AMD graphics card won't stop crashing on a laptop from 3 years ago (and yes AMD knows)

[-]

rbitton@reddit

That actually sucks my condolences

[-]

Buckwheat469@reddit

New Kconfig options make it easier to replace the Tux logo with a logo of your choice for displaying during the kernel boot process.

You hear that OEMs? You can put your logo on it so people can buy your branded Linux computer.

[-]

oxez@reddit

You already could.

My custom Linux distribution has my own logo at the top. The old way was quite cumbersome, as you had to embed your image in a .c file, the new one I hear you can just tell it where to find the image

[-]

yawara25@reddit

If I'm not mistaken, this means that adding a custom boot logo through this new method would require an initramfs, correct?

[-]

Askolei@reddit

I noticed this too when I installed Bazzite. Now my PC boots with a high definition logo of my motherboard (Asus TUF) and a smaller Bazzite logo underneath.

It's pretty cool.

[-]

SomeRedTeapot@reddit

I think what you're describing is just Plymouth that takes the mobo manufacturer's logo from the UEFI (there is an API for that). I've done the same but with a spinning fox from Minecraft for lolz

[-]

MarzipanEven7336@reddit

That’s different.

[-]

sunny0_0@reddit

It is exciting! And not just because it won't make my computer un-bootable like a certain AI slop company.

[-]

StillNewspaper4799@reddit

And here I thought making posts about unrelated political/societal trends was mostly a YouTube thing. But let me guess, when your political rivals do it it's because they're bad and trying to push an agenda.

Reddit never fails to disappoint.

[-]

sunny0_0@reddit

Wut

[-]

Adept-Interactions@reddit

I have been beta testing the release candidates and can say I have yet to crash or even find an error with it at all.

[-]

jduartedj@reddit

Linux 7.0 feels weird to say out loud honestly. I know Linus said version numbers are meaningless but it still feels like a milestone somehow?

The Rust integration stuff is whats most exciting to me. Slowly but surely we're getting to a point where new drivers can be written in Rust from the start instead of just bindings. The memory safety benefits alone make it worth the growing pains.

Also that VRAM management work from Valve is huge for anyone gaming on linux with a non-massive GPU. Running an 8GB card and having the kernel intelligently manage VRAM pressure is the kind of thing that makes linux gaming actually viable on mid range hardware. Cant wait to try this on my setup

[-]

Michaeli_Starky@reddit

And Postgress performance regression...

[-]

kukivu@reddit

´´´ Continued upstreaming work around Qualcomm Snapdragon X2 Elite SoC and laptop support.

That’s the most appealing thing to me about this update! Awesome to see this.

[-]

hawseepoo@reddit

ikr, i’m super excited for Qualcomm’s X chips to be well-supported. Even better if Framework releases a motherboard with one

[-]

RafaelSenpai83@reddit

It's all exciting and stuff but let's remember the biggest problem of ARM in consumer computers - there's no proper way for OS to detect the hardware.

But who knows, maybe Framework will do the second breakthrough in the industry by being the first one making an ARM board that has some sensible standard of HW detection equivalent to ACPI on x86_64.

[-]

MJStone66@reddit

Could this be handled by shipping device tree binaries for the SoC? And then each manufacturer can ship overlays for the specific peripheral set their computer adds.

[-]

SomeRedTeapot@reddit

Isn't this how it's done currently? As a result, you need device-specific kernel patches for every single model, which sucks because even if you have support for one device running a specific SoC, a different device with the same SoC won't work

[-]

MJStone66@reddit

I'm not familiar with consumer ARM world but assumed it must be something like that. I could see a system where you treat dtb and dtbo files like packages potentially working. If an install USB only needs to ship with dtb files for all the common SoCs, then ideally that would be enough to get networking working and pull down the correct dtbo for the model specific peripherals. Otherwise we'd probably need to look at something like the raspberry pi imager program that let's you tweak settings and files before flashing the install media. For common SoCs I could see something working, but anything less common would risk hitting issues if you need to start adding kernel features that aren't considered default. You can choose a dtb at boot time, but kernel changes from my understanding would require recompilation.

[-]

CrackedP0t@reddit

Oh that's weird, is there somewhere I can learn more about that?

[-]

hawseepoo@reddit

I'll be honest, I didn't even know that was an issue. I just want that sweet battery life lol

[-]

Synthetic451@reddit

But didn't Qualcomm say they won't open source the headers for the DSP and NPU? Or has that changed?

[-]

power10010@reddit

Wait for fixes 7.x.x

[-]

IAMAHobbitAMA@reddit

Not how Linux works.

Unlike Windows, they actually thoroughly test their software before shipping it.

[-]

power10010@reddit

And read the article what it says in the end:

“Look forward to Linux 7.0 hopefully releasing on Sunday followed by the start of the Linux 7.1 merge window.”

[-]

Sir_Render_of_France@reddit

Followed by the start of the next merge window, followed by the start of the next merge window, etc.

Each release will have new features, new fixes and new bugs. You sure you know how this stuff works?

[-]

power10010@reddit

Bunch of hyped enthusiast.

[-]

Sir_Render_of_France@reddit

What do you suggest waiting for then oh wise redditor? I am seeing a lot of complaining but no advice or insights. I am all ears

[-]

power10010@reddit

Most of people here see linux as their cute os, windows free bla bla. Would you trust first major kernel release on your production machine? I would not.

[-]

Sir_Render_of_France@reddit

Ahh, so you didn't read the article properly. This is rephrasing the article here but: After revision X.19 Linus feels that it's time to increment the major version number as it's been through enough changes to make the change somewhat meaningful.

It could just as easily have been called 6.20 but Linus' preference is to just change to the next major number after x.19. Only once has it hit X.20 and that was on major 4, every other major since 3 has stopped at x.19. It's a Ship of Theseus type deal, you change enough of the code and is it still the same kernel anymore?

Linux kernel major releases are not like Windows or MacOS where the major releases come with drastic changes or overhauls. They're incremental like all other releases, it's just Linus' preferred numbering scheme.

[-]

power10010@reddit

There are standards, not preferences. Again, software is software.

[-]

kJon02@reddit

Linux doesn't follow the standart, so what's your point exactly?

[-]

Sir_Render_of_France@reddit

There are multiple competing standards (see XKCD 927)

Apple (and now Minecraft) have their own numbering scheme where the major is defined by the year it is released in, if a minor release were to be delayed to the point of being pushed to the next year it would get re-versioned to become the next major yet it's still the same build wether it was 26.12 or 27.0. Sure they might hold some features for the next major but no guarantees so the same principal applies. It is their preference for naming their releases. Major release number changes don't necessarily mean major code overhauls or revisions.

[-]

MrMelon54@reddit

Yeah 7.0 is overhyped lets wait until 8.0 /s

[-]

power10010@reddit

Yes yes

[-]

RedSquirrelFtw@reddit

This isn't Windows. ;)

[-]

spin81@reddit

I like that they're still finding ways to optimize ext4.

[-]

Moonbeard-Wizard@reddit

Here is a summary of important changes, according to the kernelnewbies.org:

https://kernelnewbies.org/Linux_7.0

[-]

shwaamon@reddit

Wooo gon be awhile for us on Mint. We're still 6.17

[-]

dingman58@reddit

Can always compile with a new kernel

[-]

proton_badger@reddit

Ubuntu derivatives also have PPAs available with latest kernels, for those with the need.

[-]

MelioraXI@reddit

Around time you get next major version, since it will be based off Ubuntu 26.04

[-]

onefish2@reddit

Use the mainline kernel. Update to 7.0 today.

https://github.com/cappelikan/mainline

[-]

RayneYoruka@reddit

This is the way to go.

[-]

Ok-Scarcity-7468@reddit

Hey everyone, I’m really stuck and need advice. I got a virus after plugging in a USB and running a suspicious .exe. My CPU went wild—fan at full speed—but Task Manager showed low usage. I got logged out of all my Google accounts, and even after resetting passwords, the virus keeps returning. I did a full format six times: first time, it came back from the drive; second time, after syncing Google; and even without any action, it just returns—possibly linked to the BIOS partition. On top of that, my iPhone is also acting strange: Safari glitches, random touch issues, and Apple ID settings won’t load. I even lose notifications when using a VPN. Is this all connected? Could malware survive a full format and spread via accounts? Please, I really need help to fully secure both my PC and iPhone. Thanks so much!

[-]