site  contact  subhomenews

Kernel 3.9.5 experiment

June 13, 2013 — BarryK
I compiled the 3.9.5 Linux kernel, with devtmpfs enabled. This kernel also loads module firmware, another task that was previously handled by udev (and pup_event_backend).

So, there are two features of udev that are now done by the kernel:

1. Dynamically create/remove device nodes in /dev
2. Load module firmware.

I built Raring Puppy with this kernel, and with the 'kmod' package instead of 'module-init-tools', and with the 'eudev' package instead of udev (or systemd).

I had compiled it with PAE enabled and i586, however I am right now recompiling it for a i686 (Pentium Pro) minimum CPU, which, as far as I am aware, would be the case for PAE-capable CPUs.

The devtmpfs kernel, kmod and eudev all work well.

The next thing that I have to do is revise the pup_event_backend code, in light of the new capabilities of the kernel.


woof kmod bug - slacko
Username: 01micko
package-template/kmod/FIXUPHACK is wrong should be: [code] #for slackware... DISABLE_POST_INSTALL_SCRIPT=yes #get rid of stuff we don't need... rm -rf etc rm -rf usr/share #probably need this for slackware... if [ -f sbin/kmod ];then ln -snf ../sbin/kmod bin/lsmod ln -snf kmod sbin/lsmod ln -snf kmod sbin/depmod ln -snf kmod sbin/insmod ln -snf kmod sbin/modinfo ln -snf kmod sbin/modprobe ln -snf kmod sbin/rmmod fi[/code] Unless of course there is conflict with the other distros

Re kmod
Username: BarryK
"01micko, Thanks, fixed.

Username: 01micko
"Hi Barry I notice the new stuff in 3builddistro @lines 1370 & 3007. First one seems sane but the second, [i]sed -i -e 's%^DEVTMPFSFLG=.*%DEVTMPFSFLG=2%' rootfs-complete/etc/rc.d/rc.sysinit[/i] doesn't. That's because I cant find any string in /etc/rc.d/rc.sysinit with DEVTMPFSFLG=(0 by default I guess). Should I add it? Reason I ask is I'm thinking of doing a build with udev-182 (Slackware). Tried eudev but Xorg don't start with missing (eudev has Looking forward to the IPC implementation too.

Username: BarryK
"01micko, Hmmm, it looks like I forgot to put it in. OK, I have put this: DEVTMPFSFLG=0 #see 3builddistro just before the test if [ $DEVTMPFSFLG -ne 0 ];then

Username: 01micko
"I just built with udev-182 and udev-167pe and both end up with that var as 2. Seems to work ok though anyway. On my old laptop though, udev-182 didn't work right ie: wireless didn't load (probably because of the slackware rules, might try it with a template) but udev-167pe seems to work fine, wireless, sound, infrared, firewire all loaded. (Laptop is a Thinkpad r51 circa 2004/5; kernel is a steaming hot 3.10 (stable as of a couple of days ago, aufs uses the 3.rcN branch).

Slacko alpha
Username: 01micko
"The above build with k3.10 and udev-167 seems good so I uploaded it. Calling this [b]slacko-5.6-alpha[/b] (though it seems much better than alpha to me)

Username: aarf
"Network Error (tcp_error) A communication error occurred: "" The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time. For assistance, contact your network support team. from

re mktorrent
Username: 01micko
"Did seem down for a few minutes aarf, but working again now. Hopefully works ootb for you because it has modeset driver in correct place.

Username: aarf
"ok up and frisbee surfing in initially tapless slacko5567 via xorgwizard with modsetting 1024x600 # time geany real 0m13.367s user 0m1.457s sys 0m0.397s # # time abiword real 0m9.803s user 0m1.280s sys 0m0.897s #

Tags: woof