Forum member 'steven p' sent me a message awhile back to set CONFIG_USB_OHCI_HCD_SSB=N as otherwise it conflicts with something -- can't recall exactly what he said it conflicts with, but anyway I have done that.
I will upload the sources and PET soon.
Comments:Posted on 7 Oct 2010, 2:22 by broomdodger
how to open port 22?
how to open port 22?
I tried Linux-firewall
Then edited /etc/rc.d/rc.firewall
to PERMIT="21 22"
restart and still nothing in port scan.
Posted on 7 Oct 2010, 6:54 by BarryK
Re port scan
Well, is your Internet connection through a router/modem? It will have its own firewall.
Best to ask this question on the forum, I don't know much about firewalls.
Posted on 7 Oct 2010, 7:00 by BarryK
The sources are here:
The PET is here (21MB):
...note that the PET needs to be used with a fairly recent version of Woof, as Woof now has all the firmware tarballs.
Posted on 7 Oct 2010, 7:25 by broomdodger
Re port scan
I am not really interested in a firewall, I have router.
All I want to do is open ports 21 and 22 for the local net.
Posted on 7 Oct 2010, 18:36 by Iguleder
Barry, is there any reason you don't enable CONFIG_SCHED_SMT (HyperThreading) in all your kernels? It's a MUST for all netbooks (as most Atom processors are single-core but support HyperThreading) and can be useful with old Pentium 4 processors or recent high-end Intel processors.
And another question ... why don't you compile Squashfs and Aufs into the kernel (y instead of m)? They're loaded anyway, so if you make the kernel more monolithic and less modular it could improve boot times. I just compiled a kernel for my own distro (18.104.22.168, tweaked and modified) and based it on the Puppy Squeeze 22.214.171.124 I compiled recently, but this time I moved things like USB into the kernel because most PCs need those modules loaded anyway. I mean, in your kernels all IDE/SATA stuff are in the kernel ... why don't you do the same with other things, like USB, generic input devices, ... ?
Posted on 7 Oct 2010, 20:14 by BarryK
usb is kept as modules because of how the init script works. Internal drives are detected first, see ATADRIVES in /etc/rc.d/PUPSTATE. This is how Puppy detects which are usb drives and which not. Building usb into the kernel will break this.
Hyperthreading is not enabled because of the description. The description given when you click the help button when running menuconfig, describes the hyperthreading as for a particular Pentium only, no mention is made of any later CPUs such as Atom etc.
Other SMP options are enabled, and my understanding is that the Atom CPU behaves like a twin-core CPU and kernel SMP scheduling works. But, this needs to be verified, it is just my understanding from limited reading.
Aufs is not built in because we sometimes use unionfs, and can even have both and choose which one we want at boot time.
Posted on 7 Oct 2010, 20:17 by BarryK
Hmmm, the first build with this kernel is a disaster, kernel panic.
There is a serious problem with usb detection. Will investigate further.
Posted on 7 Oct 2010, 21:06 by Iguleder
Thanks for the detailed reply, Barry :)
Regarding HyperThreading, it is used by more than just the Pentium 4 processors as the help text says. Here's a quote from Wikipedia: "simultaneous multithreading implementation in its Atom, Core i3, Core i5, Core i7, Itanium, Pentium 4 and Xeon CPUs."
I don't remember whether Lupu recognized my netbook's Atom as two processors, but I do know that Puppy Squeeze 009 (with a HyperThreading-enabled 126.96.36.199) has sched_smt_power_savings and not sched_mc_power_savings, which means it uses the SMT scheduler, HyperThreading. I'll try to ask jemimah in IRC, she knows better.
Posted on 9 Oct 2010, 14:29 by steven p
Hyperthreading seems to be working on my Intel Atom N270 (it shows two processors). I think all it needs is SMP enabled.
Thanks Barry for disabling CONFIG_USB_OHCI_HCD_SSB.
It conflicted with the proprietary Broadcom wireless driver on my brother's laptop.
Posted on 10 Oct 2010, 24:09 by BarryK
Oh <expletive/>, the boot parameter "video=640x480" does not work with this kernel.
I compiled it built-in, same as I did with the 2.6.34.x kernel (and that worked).
Typing it at bootup doesn't work either. It is just ignored. So, the goal posts have been moved.