Formed from just a single commit (that reverses a former single wifi commit)
Was it that they couldn't wait to get to 666, or the hope that 666 wont be around for too long
Kernel 666
Moderator: Forum moderators
-
fatdoguser
- Posts: 175
- Joined: Sat Aug 05, 2023 10:54 am
- Has thanked: 22 times
- Been thanked: 79 times
-
ozsouth
- Posts: 1358
- Joined: Sun Jul 12, 2020 2:38 am
- Location: S.E. Australia
- Has thanked: 210 times
- Been thanked: 601 times
Re: Kernel 666
@fatdoguser - usually such a small, soon-after-previous update is for a critical error. Any LTS kernel with a single last digit is issued in a time of significant change.
-
rockedge
- Site Admin
- Posts: 5702
- Joined: Mon Dec 02, 2019 1:38 am
- Location: Connecticut,U.S.A.
- Has thanked: 1983 times
- Been thanked: 2092 times
- Contact:
Re: Kernel 666
I tried two compile runs that built 6.6.6 successfully also with trying some code substitution. Despite building apparently cleanly all attempted system boots using the kernel on F96-CE_4 end in Kernel Panic. 
-
ozsouth
- Posts: 1358
- Joined: Sun Jul 12, 2020 2:38 am
- Location: S.E. Australia
- Has thanked: 210 times
- Been thanked: 601 times
Re: Kernel 666
@rockedge - sadly, with still no aufs6.6.4 released, swapping in /fs/stat.c from 6.6.3 is the current workaround - I did it when the kernel config menu appeared, then ran option 1 (ncurses menu), with 6.6.5 - worked. Overlay is fine too.
-
fatdoguser
- Posts: 175
- Joined: Sat Aug 05, 2023 10:54 am
- Has thanked: 22 times
- Been thanked: 79 times
Re: Kernel 666
Eerily my 6.6.6 Linux kernel produced a 6.66MB vmlinuz filesize, was glad that 6.6.7 was released relatively soon after that. Not superstitious but after the initial amusement factor it did stick/niggle to the extent that I was contemplating a re-build just to shift the filesize, but then 6.6.7 came alone and saved the bother.