Kernel config for 5.0

[curaga]

Again it's time to post if you'd like to see any changes in the official kernel config. This only affects x86 and x64, the ARM ports will do their own thing.

Current list of changes to be done:
- more serial ports
- alsa virmidi
- ehci new scheduling
- netconsole as a module
- efi support
- sd.c cache errors to warnings
- some more netlink/iptables xfrm modules
- pcie hotplug
- pcmcia=y

We're targeting 3.7 currently.

This thread will remain open for two weeks.

[Lee]

I'm not sure if this minor thing is a kernel issue or not and I haven't spent a lot of effort troubleshooting it but...

I have a system with two sata hard disks and, usually, one USB flash drive plugged in.   Occasionally, I plug a second USB stick in for backing up the primary one.

All connected drives mount and work fine (hence the minimal troubleshooting effort) but conky (the conky_plus extension) never recognizes "sdd", the second USB stick, as being mounted.  I've always assumed it was some issue with conky, and I still suspect so, but if you could eliminate the possibility that it is some kernel configuration setting, I'd appreciate it.

[curaga]

I can't think of anything in the kernel that would cause that.

[coreplayer2]

Appreciate  this http://forum.tinycorelinux.net/index.php/topic,13212.msg73014.html#msg73014

[coreplayer2]

Also is USB 3.0 enabled by default in this kernel ?

[tinypoodle]

Any chance to get the RealTek RTL81**** Wireless LAN NIC drivers in staging configured as modules?

[aus9]

For those who want to know what is in current try

http://tinycorelinux.net/4.x/x86/release/src/kernel/

[curaga]

@coreplayer2

That's the "ehci new scheduling", hadn't forgotten it. USB 3.0 was already enabled in the current kernel. If you're not getting usb 3.0 speeds, that may just be due to the 3.0 kernel not supporting your usb controller.

@tinypoodle

My stance wrt staging/unstable drivers is the same. I won't enable them by default, because no matter how many warnings there are, some noob will always follow a tutorial somewhere to load them and then blame Core when their computer crashes/hangs, loses data, and so on.

They are allowed in the repo if contributed, but it's an important line to keep on what's officially supported and what's not.

[tinypoodle]

Question: As the kernel config options for the drivers in question are of "type: tristate", if choosing N in kernel config, can they later be built as modules from same kernel source to work with the stock kernel or not?

[curaga]

Yes, as long as it doesn't change other code (such as with ifdefs).

[Ahmad]

Much appreciated: http://forum.tinycorelinux.net/index.php/topic,14987.0.html

I am willing to test the early development releases on the machines I mentioned in the above thread.

Can you share with us when should we expect a 5.0 release based on 3.7+ something kernel?

[coreplayer2]

Thanks curaga   I should have read more closely

[curaga]

Can't give a timeframe other than "when it's ready", sorry. Alphas and RCs will be public as usual when they're passing our testing.

[Zendrael]

Could it has some "kernel tuning"?

(I'm not a Kernel hacker... forget about it if I said something dumb...)

[curaga]

What do you mean?