Long-term Kernel

I have compiled the kernel, with Rfkill and Hyperthreading enabled (and SMP, tickless, etc.). This is a long-term supported kernel, so interests me for use with Wary.

What has pleased me very much is that I was able to compile all but two of the analog modem drivers. The two that failed are:


However, there is potential that we will be able to get these two to compile. I used to communicate with the developer of the ESS driver -- I will get in contact with him again. The other two (more recent) agrsm driver variants do compile -- so probably whatever was fixed in them could be applied.

Which means that this long-term kernel could well become the next standard kernel for Wary. I also took the opportunity to enable Rfkill and Hyperthreading, as these have been requested many times. The Hso wireless driver neds Rfkill, for example.

The next build of Wary will have this kernel. I will also have a look at the suggestions from zigbert and others. It is 5.15am right now and I have a full day of family duties ahead, but this evening will get stuck into it -- looking forward to building this new Wary!

The sources are uploaded here:
Username: p#u#p#p#y Password: l#i#n#u#x

Posted on 7 Feb 2011, 6:14


Posted on 7 Feb 2011, 8:08 by Lalo Aguilar
Hi Barry
Hi Barry. I'm a Puppy 5.1 liveCD user. I just wanna to ask: What distribution of Linux is Puppy bassed on? (Did I write it well? 'Cause I'm learning english. I speak mexican spanish)

Answers at: luis.eulalio.aguilar[at]gmail.com

Posted on 7 Feb 2011, 16:54 by Sage
More bad news from Down Under
Hope none of your relatives in Perth have been caught up in the latest bush fires? Oz has had a terrible pasting this Summer. Is there anything we can do? Can ask UK government to send money, but suspect this lot is too busy counting their Swiss bank accounts. Anything we can do as individuals?
You deserve better.

Posted on 7 Feb 2011, 19:33 by dingo
ipv6 support
is this puppy kernel ipv6 ready?

in puppy 3.01 kernel (unique puppy version working very well on my hp d530c pc)i tried:

test -f /proc/net/if_inet6 && echo "Running kernel is IPv6 ready"

but no message is shown (this means that first command failed)

in addition to this, i also tried

modprobe ipv6

and the output is:

FATAL: Module ipv6 not found

the same for puppy 4.x-4.3.x series

Posted on 7 Feb 2011, 21:07 by FeodorF
IPv6 Support -How to-
a) IPv6 support is included in all Kernels since 2.6.x
b) Kernels 2.2.x and 2.4.x are outdated concerning IPv6

follow this way to install IPv6 support:
modprobe ipv6
lsmod |grep -w 'ipv6' && echo "IPv6 module successfully loaded"

Please notice:
You can not unmount the installed IPv6 support while running.

Posted on 7 Feb 2011, 21:18 by FeodorF
IPv6 autoinstall
If I am not mistaking you can add the following alias lines to:

alias net-pf-10 ipv6 # automatically load IPv6 module on demand

alias net-pf-10 off # disable automatically load of IPv6 module on demand

Posted on 7 Feb 2011, 21:29 by FeodorF

This should not be there!

Posted on 7 Feb 2011, 21:49 by dingo
ipv6 support
I have no /etc/modeprobe.d/puppy.conf, ls shows only a file named modprobe.conf in /etc

# ls -1 /etc | grep modprobe


I already tried to type modprobe ipv6 from a live cd session of puppy 3.01, but I get only the error reported: FATAL: Module ipv6 not found

Posted on 8 Feb 2011, 6:08 by technosaurus
console frame buffer
Feature request, build in the console frame buffer

* Barry's kernels were compiled with vesafb but
* without console framebuffer. When we boot using
* vga=??? we get a black screen ( we should blindly
* type "modprobe fbcon" to get a working console.)
* Barry's config:
* Should be:

Which is why why I could never get SDL-fb, DirectFB, QT-embedded, gtk2-fb, fbui and others to work
They would be nice to have, unless there is some conflict with the console framebuffer (I can see where it might need a command line flag to disable it by default)

a big second on enabling ipv6 by default for "long term support"

It may also be time to build glib with dbus and gvfs - too many _good_ apps need those and we spend a lot of time trying to get around them that could be better spent elsewhere.
You'd be surprised some of the "niceties" we are missing out on in existing apps because of this.
By "niceties" I mean the program actually doing what it is supposed to ... like opening or interacting with an external program. It gets even more integrated in gtk3 (really with later versions of glib's g_application bits)

Posted on 8 Feb 2011, 8:38 by BarryK
Puppy Linux is based on Puppy Linux, no other distro.

Yeah, over in Queensland they have had flooding then cyclone, in Victoria flooding, in Western Australia flooding up North, now around Perth there are fires. I saw some burnt terrain when I drove down to Perth yesterday.

Most of those entries in puppy.conf aren't needed, as they are already in /etc/modules/<kernel>/modules.alias. Ditto for that ipv6 alias.

Latest puppies do not have /etc/modprobe.conf, it is deprecated.

Posted on 8 Feb 2011, 17:53 by Terryphi
Puppy firewall and ipv6
It appears that Puppy firewall is incompatible with ipv6. I recently raised this in the forum:


UFW (Uncomplicated Firewall) used in Ubuntu can be made ipv6 compatible by changing one line in the config file. Maybe it is time to change the firewall used in Puppy/Wary.

Posted on 8 Feb 2011, 19:40 by dingo
ipv6 support for puppy 3.01
Since Puppy 3.01 is unique puppy version working fine with internet on my HP d530c PC, I need to:

- build ipv6 module for support
- build proper firewall utility

a lot of work is needed since with other puppies is not possible to connect to internet

Barry is a great man, but choice of not include ipv6 support in puppy is very questionable

Posted on 8 Feb 2011, 19:57 by BarryK
Re fbcon
fbcon.ko does get loaded in /etc/rc.d/rc.sysinit:

#101119 i really only want to load this for a kms-enabled video...

[ "`cat /proc/cmdline | grep 'modeset=1'`" != "" ] && KMS=yes
[ "`cat /etc/modprobe.d/* | grep '^options .* modeset=1'`" != "" ] && KMS=yes
[ "$KMS" = "yes" ] && modprobe fbcon #100703 needed by some xorg drivers when exit to console (ex: nouveau).

Posted on 9 Feb 2011, 4:11 by technosaurus
So just add modeset=1 vga=### to my grub menu entry then? That should work ... provided nothing goes wrong during the boot process (since you would only see a blank screen until rc.sysinit is run?) ... wait does this only work on intel, ati, nvidia - sis, and other chips can't use KMS can they? No matter though - I have an intel card, so I can work out the rest later.

That should be all I need for testing purposes. (I'm trying to get a basic webkit browser + mplayer/gstreamer/vlc + swfdec/gnash/lightspark running in the framebuffer for my really old PCs ... I already have the beginnings of a framework to use the browser as the UI via cgi scripts and httpd ... for setting up configurations etc...)

I'm basically using my html and bash+gtkdialog knowledge to work with the browser via cgi: