That would be pretty cool. I'd like to see a realtime version of puppylinux. That said, I'm sure there is much much more to building an effective realtime system than having the right kernel.peebee wrote:Hi Stemsee
It would be interesting to know why you've gone for the "rt" = "real time"?? versions of the kernels this time - and what differences this might make to their performance in a desktop environment??
Do you intend to only build rt variants from now on?
Many thanks for your efforts
Cheers
peebee
kernel compiling in woof-ce
@peebee
I used to build real-time kernels for ubuntu, then when I switched to puppy I had problems patching rt and adding aufs. I just hapened to search at kernel archives and found rt patches for recent kernels so i gave them a go and they work. During configure I am not able to compile to completion if Fully pre-emptible real time is selected, this 64 bit kernel has basic rt, and the pae has voluntary pre-emptible desktop. There are five options
1) non preemptible
2) voluntary (usual for puppy)
3) low-latency desktop
4) Basic rt
5) Fully preemptible
Most of the rt patches are now included in the kernel anyway. And I was curious to try something new. I have not noticed any performance increase. Perhaps after adding rtirq package and optimising a number of other settings to make use of rt kernel: there are some useful websites detailing system tuning for rt audio/video system.
@s243a
Iowtech provides studio 1337, multimedia distro, based on puppy linux slacko, every package compiled against a fully preemptible real time custom kernel.
here
http://www.getstudio1337.com/
I used to build real-time kernels for ubuntu, then when I switched to puppy I had problems patching rt and adding aufs. I just hapened to search at kernel archives and found rt patches for recent kernels so i gave them a go and they work. During configure I am not able to compile to completion if Fully pre-emptible real time is selected, this 64 bit kernel has basic rt, and the pae has voluntary pre-emptible desktop. There are five options
1) non preemptible
2) voluntary (usual for puppy)
3) low-latency desktop
4) Basic rt
5) Fully preemptible
Most of the rt patches are now included in the kernel anyway. And I was curious to try something new. I have not noticed any performance increase. Perhaps after adding rtirq package and optimising a number of other settings to make use of rt kernel: there are some useful websites detailing system tuning for rt audio/video system.
@s243a
Iowtech provides studio 1337, multimedia distro, based on puppy linux slacko, every package compiled against a fully preemptible real time custom kernel.
here
http://www.getstudio1337.com/
All seems pretty snappy here....
"Stuttering" printing during initial boot has gone....
Can select savefiles using usb keyboard during boot
There does seem to be some spurious firmware directories in /lib/firmware though... see screenie
Many thanks
peebee
"Stuttering" printing during initial boot has gone....
Can select savefiles using usb keyboard during boot
There does seem to be some spurious firmware directories in /lib/firmware though... see screenie
Many thanks
peebee
- Attachments
-
- Screenshot.png
- (128.42 KiB) Downloaded 1115 times
-
- Screenshot.png
- (8.2 KiB) Downloaded 1113 times
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Hello stemsee,stemsee wrote:kernel-4.4.1-EmSee-nopae-i486-rt3
https://drive.google.com/file/d/0B_gaN1 ... sp=sharing
This link seems to go to the previous huge-4.4.0-EmSeei486 (29M) instead of kernel-4.4.1-EmSee-nopae-i486-rt3 for me.
Thanks @ moeppyfan
I have removed the link until corrected.
In the mean time I recompiled 64 bit kernel because kernel modules for wireless were missing for my system!
4.4.1-EmSee-64-rt6
https://drive.google.com/file/d/0B_gaN1 ... sp=sharing
sources
https://drive.google.com/file/d/0B_gaN1 ... sp=sharing
I have removed the link until corrected.
In the mean time I recompiled 64 bit kernel because kernel modules for wireless were missing for my system!
4.4.1-EmSee-64-rt6
https://drive.google.com/file/d/0B_gaN1 ... sp=sharing
sources
https://drive.google.com/file/d/0B_gaN1 ... sp=sharing
4.4.1-EmSee-nopae-rt6 i486 no smp
https://drive.google.com/file/d/0B_gaN1 ... sp=sharing
https://drive.google.com/file/d/0B_gaN1 ... sp=sharing
Thanks stemsee. Nice work!stemsee wrote:4.4.1-EmSee-nopae-rt6 i486 no smp
https://drive.google.com/file/d/0B_gaN1 ... sp=sharing
Here is SUKK-2016
Updated configs + rt6 patch
other code added to not copy in firmware from running system if compiling on other linux system.
https://drive.google.com/file/d/0B_gaN1 ... GZlaHNnU0E
Updated configs + rt6 patch
other code added to not copy in firmware from running system if compiling on other linux system.
https://drive.google.com/file/d/0B_gaN1 ... GZlaHNnU0E
- Revolverve
- Posts: 255
- Joined: Sat 08 Nov 2008, 21:01
- Location: 45°17'28.8"N 72°16'08.8"W_avatar/ mira.ca
stemsee,
Nice work.For sure you could find some folks interested in rt preempt,more then just audio oriented ones,as machinekit(linuxcnc) for cnc,3d printer,laser,etc now got good latency result with rt-preempt .Dreaming end user point of view here..having no clues of the amount of work needed to achive it,well,lets say if based on my few attempts to learn chinese or kernel compiling/patching gave me an idea of it...and appreciate the work done.
Testing K4.4.1 rt on Tahrpup64 ,no real speed improvement here neither problems,for now.
Nice work.For sure you could find some folks interested in rt preempt,more then just audio oriented ones,as machinekit(linuxcnc) for cnc,3d printer,laser,etc now got good latency result with rt-preempt .Dreaming end user point of view here..having no clues of the amount of work needed to achive it,well,lets say if based on my few attempts to learn chinese or kernel compiling/patching gave me an idea of it...and appreciate the work done.
Testing K4.4.1 rt on Tahrpup64 ,no real speed improvement here neither problems,for now.
hi Revolverve
To get the most of rt kernel you will need to tune the system to raise certain threads to realtime priority. rtirq package
http://openavproductions.com/real-time-latency-tuning/
I notice the difference using the 64bit rt6 kernel on a core i5 desktop @ 3.05ghz. Hardinfo>CPU Blowfish scored 3 !!!
regards.
To get the most of rt kernel you will need to tune the system to raise certain threads to realtime priority. rtirq package
http://openavproductions.com/real-time-latency-tuning/
I notice the difference using the 64bit rt6 kernel on a core i5 desktop @ 3.05ghz. Hardinfo>CPU Blowfish scored 3 !!!
regards.
kernel-4.4.2-emsee-64-amd64.deb for full installs or DebianDog or Debian/Ubuntu
linux-image-*.deb
https://drive.google.com/file/d/0B_gaN1 ... zhnbzhiSlU
linux-headers-*.deb
https://drive.google.com/file/d/0B_gaN1 ... 1BGRVNOVVk
linux-image-*.deb
https://drive.google.com/file/d/0B_gaN1 ... zhnbzhiSlU
linux-headers-*.deb
https://drive.google.com/file/d/0B_gaN1 ... 1BGRVNOVVk
Hi Stemsee
Just tried compiling drivers in 4.4.1-pae-rt3
Small problem in that the /lib/modules are named differently:
/lib/modules/4.4.1-EmSee-32-pae in kernel sources
/lib/modules/4.4.1-EmSee-32-pae-rt3 in the zdrv
Easily solved by just copying the 2 links across - but thought you should know...
Cheers
peebee
Just tried compiling drivers in 4.4.1-pae-rt3
Small problem in that the /lib/modules are named differently:
/lib/modules/4.4.1-EmSee-32-pae in kernel sources
/lib/modules/4.4.1-EmSee-32-pae-rt3 in the zdrv
Easily solved by just copying the 2 links across - but thought you should know...
Cheers
peebee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Untested
huge-4.4.4-EmSeei686
https://drive.google.com/file/d/0B_gaN1 ... WFqSkg4STA
i686 sources
https://drive.google.com/file/d/0B_gaN1 ... 3lra1dlQm8
huge-4.4.4-EmSee64
https://drive.google.com/file/d/0B_gaN1 ... C1ZV3RiQ1U
huge-4.4.4-EmSeei686
https://drive.google.com/file/d/0B_gaN1 ... WFqSkg4STA
i686 sources
https://drive.google.com/file/d/0B_gaN1 ... 3lra1dlQm8
huge-4.4.4-EmSee64
https://drive.google.com/file/d/0B_gaN1 ... C1ZV3RiQ1U
Downloaded i686 to test....stemsee wrote:Untested
huge-4.4.4-EmSeei686
https://drive.google.com/file/d/0B_gaN1 ... WFqSkg4STA
i686 sources
https://drive.google.com/file/d/0B_gaN1 ... 3lra1dlQm8
Noticed big change in size - 25MB instead of the 55MB of 4.4.1....
Seems like there maybe quite a lot of firmware missing?
Also note from /lib/modules that this one is "rt9" - is that different to "rt3"??
Cheers & thanks
peebee
Last edited by peebee on Sat 05 Mar 2016, 18:01, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
hi stemsee, now that you're compiling brand new kenerls... how about compiling the full kernel, or something like that, I see here
http://archive.archlinux.org/repos/2016 ... e/os/i686/
That the kernel is about 56mb, xz compressed, the firmware is in another packages 36mb xz compressed.
I tested your 4.4.1 kernel in a 2003 machine, and it worked fine
http://archive.archlinux.org/repos/2016 ... e/os/i686/
That the kernel is about 56mb, xz compressed, the firmware is in another packages 36mb xz compressed.
I tested your 4.4.1 kernel in a 2003 machine, and it worked fine
Test not too good I'm afraid - would not boot to desktop when substituted for a working 4.4.1 vmlinuz/zdrvstemsee wrote:Untested
huge-4.4.4-EmSeei686
nvidia graphics - nouveau usually works without fail.
even tried making a ydrv with just /lib/firmware from 4.4.1 but that didn't help...
couldn't see anything in lsmod or dmesg to suggest why
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
@peebee
You must have missed something in your test! I have just used my newkern script to install the new kernel from huge package and it is working wonderfully. The modules sfs is only 21mb big, and everything is up and running.
Here is the script. Just have huge-4.*.tar.bz2 in ~/Downloads
You must have missed something in your test! I have just used my newkern script to install the new kernel from huge package and it is working wonderfully. The modules sfs is only 21mb big, and everything is up and running.
Here is the script. Just have huge-4.*.tar.bz2 in ~/Downloads
Code: Select all
#!/bin/sh
# Untar huge-kernel-archive.tar.bz2
# For all pups!
downkernarchivefn () {
. /etc/DISTRO_SPECS
echo "Defaultbrowser will now open download a kernel package in woof-ce format huge-xxx-name.tar.bz2
to ~/Downloads."
sleep 3
defaultbrowser http://tinyurl.com/gt8eltx &
echo "Press Enter when ready!"
read dummy
}
downkernarchivefn
getbootfn () {
echo "Now enter the path to the dir where your vmlinuz (kernel) is:
e.g. /mnt/sda2/Tahr/ or /mnt/home/EmSee/"
read BOOTPATH
}
getbootfn
if [ -z "$BOOTPATH" ]; then
getbootfn
fi
if [ ! -e $HOME/Downloads/huge-*.tar.bz2 ]; then
downkernarchivefn
else
kern=`ls $HOME/Downloads/huge-*.tar.bz2 | yad --title "Select Kernel Archive to install" --list --column="From these" --width=310`
if [[ -z "$kern" ]]; then
exec "$0"
exit
fi
fi
kern=`echo $kern | cut -f1 -d '|'`
cd $HOME/Downloads
[[ ! -z "$kern" ]] && tar -vxjf "$kern"
cd "$kern"
[[ "$BOOTPATH"vmlinuz ]] && rename vmlinuz vmlinuz-bak "$BOOTPATH"vmlinuz
[[ vmlinuz-*i686 ]] && cp -f vmlinuz-*i686 "$BOOTPATH"vmlinuz
[[ "$BOOTPATH""$DISTRO_ZDRVSFS" ]] && rename "$DISTRO_ZDRVSFS" "$DISTRO_ZDRVSFS"-bak "$BOOTPATH"/"$DISTRO_ZDRVSFS"
[[ kernel-modules.sfs*i686 ]] && cp -f kernel-modules.sfs*i686 "$BOOTPATH""$DISTRO_ZDRVSFS"
[[ "$BOOTPATH"vmlin64 ]] && rename vmlin64 vmlin64-bak "$BOOTPATH"vmlin64
[[ vmlinuz-*x86_64 ]] && cp -f vmlinuz-*x86_64 "$BOOTPATH"vmlin64
[[ "$BOOTPATH""$DISTRO_YDRVSFS" ]] && rename "$DISTRO_YDRVSFS" "$DISTRO_YDRVSFS"-bak "$BOOTPATH"/"$DISTRO_YDRVSFS"
[[ kernel-modules.sfs*x86_64 ]] && cp -f kernel-modules.sfs-*x86_64 "$BOOTPATH""$DISTRO_YDRVSFS"
[[ "$BOOTPATH"vmlin48 ]] && rename vmlin48 vmlin48-bak "$BOOTPATH"vmlin48
[[ vmlinuz-*i486 ]] && cp -f vmlinuz-*i486 "$BOOTPATH"vmlin48
[[ kernel-modules.sfs*i486 ]] && cp -f kernel-modules.sfs*i486 "$BOOTPATH""$DISTRO_ADRVSFS"
sync
exit 0
------
- Attachments
-
- capture31764.png
- (12.05 KiB) Downloaded 1234 times
Hi Stemseestemsee wrote:@peebee
You must have missed something in your test!
Re-downloaded to make sure I didn't have a bad'un - both same md5 = 0ac4e9cd4eecfbe3a520f24d204964d7
Tested on my laptop with intel graphics - worked AOK
Have now tested on my desktop with nvidia graphics (304.131 legacy type) using both a slacko and a tahrpup base, and in both cases the system does not boot to a desktop (whereas both do with k4.4.1)....
Would be interested to hear from somebody else with nvidia graphics - maybe mine is getting too long in the tooth??
Cheers
peebee
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
@Peebee
Did you boot without savefile? Do you try pfix=nox ? And then run xorgwizard ?
To get the nvidia proprietary graphics drivers working you will need to install the kernel sources and then run the nvidia installer from outside of X on cli. It needs to compile the module/driver for the new kernel ... it cannot work otherwise (as far as I know (which isn't too far!)).
Nvidia driver installer package select here:
http://www.nvidia.co.uk/Download/Find.aspx?lang=en-uk
Did you boot without savefile? Do you try pfix=nox ? And then run xorgwizard ?
To get the nvidia proprietary graphics drivers working you will need to install the kernel sources and then run the nvidia installer from outside of X on cli. It needs to compile the module/driver for the new kernel ... it cannot work otherwise (as far as I know (which isn't too far!)).
Nvidia driver installer package select here:
http://www.nvidia.co.uk/Download/Find.aspx?lang=en-uk