@ Linux

Joklem · **Posted:** Fri May 13, 2011 2:12 am

Challenge was accepted.

Should I send that upstream or something? Hahahaha

Meowth · **Posted:** Fri May 13, 2011 4:59 am

More like whybothernix

Eturnalshift · **Posted:** Fri May 13, 2011 6:51 am

Meowth wrote:

More like whybothernix

Because it's important to be viewed as a supernerd on an internet forum.

Henq · **Posted:** Fri May 13, 2011 7:07 am

Ebtables and nfqueue == I run fedora everyday at work

At home == vista

Sent from my SCH-I500 using Tapatalk

Meowth · **Posted:** Fri May 13, 2011 9:31 am

Eturnalshift wrote:

Meowth wrote:

More like whybothernix

Because it's important to be viewed as a supernerd on an internet forum.

Linux has its place in the world, don't get me wrong.

@Henq: Why not use this?

Joklem · **Posted:** Fri May 13, 2011 12:48 pm

Henq wrote:

Ebtables and nfqueue == I run fedora everyday at work

At home == vista

Sent from my SCH-I500 using Tapatalk

I used Fedora for a long time but switched to Debian-based a few months ago, running Ubuntu 11.04 right now.

They're different but I don't have a favourite, although doing things easily without mastering the Fedora Way(tm) is a breath of fresh air.

Yuratuhl · **Posted:** Fri May 13, 2011 4:26 pm

Ubuntu last update is turboAIDS, but the one right before that is classy.

Joklem · **Posted:** Fri May 13, 2011 4:36 pm

Yuratuhl wrote:

Ubuntu last update is turboAIDS, but the one right before that is classy.

Eh it's fine. If you don't like the Unity shell you can always switch back to Gnome 2.32, or install Gnome 3, or install XFCE, KDE, LXDE or whatever desktop you want to use.

Joklem · **Posted:** Fri May 13, 2011 7:10 pm

Yuratuhl wrote:

Ubuntu last update is turboAIDS, but the one right before that is classy.

Oh and suggestion instead of using generic kernels:

Grab the latest 2.6.39 source and pre-req:

Code:

sudo apt-get update
sudo apt-get install build-essential fakeroot kernel-package kernel-wedge libncurses5-dev libqt3-mt-dev
wget http://www.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.39-rc7.tar.bz2

The latest snapshot patch:

Code:

wget http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.39-rc7-git5.bz2

Extract and cd;

The ubuntu patches:

Code:

wget http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/0001-base-packaging.patch
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/0003-debian-changelog.patch
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/0004-default-configs.patch

Clean patches (only the ubuntu ones); apply patches:

Code:

scripts/cleanfile 0001-base-packaging.patch
scripts/cleanfile 0002-debian-changelog.patch
scripts/cleanfile 0003-default-configs.patch

patch -p1 < patchname.patch

Prepare for build:

Code:

fakeroot
debian/rules clean
export CFLAGS="-march=native -O2 -pipe -mtune=native"
# 'native' sets the appropriate cflags for your processor, no need to specify core2 or corei7 or whatevs
export CXXFLAGS="$CFLAGS"
cp /boot/name-of-your-current-config.config .config
# copy your current (ubuntu generic) config to .config, speeds things up a bit
make oldconfig
make menuconfig 
# or make xconfig

Configure it as you see fit,
enable pre-emptive desktop (low-latency) mode in general settings and set the frequency timer to 1000hz
In processor settings, select core2/newer xeon (if you have a core 2/quad/i3/i5/i7) or AMD
Select 'ondemand' as the default CPU governor, the default in the ubuntu config is performance
Select CFQ as the I/O scheduler and enable the CGROUPS options. That would be the famous "200 lines patch that does wonders"
Enable HPET and RTC in drivers->character devices
Add or remove whatever the fuck else you want or need that you know of in your hardware. The ubuntu default config is fine but I personally like slimmer configs

Save and exit

Build:

Code:

CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` make-kpkg --initrd --append-to-version=-preempt kernel_image kernel_headers
# add fakeroot after concurrency in that command if you lost it

Go out and buy a sandwich and beer in Switzerland, come back and

Code:

cd ..
mkdir linux-2.6.39-rc7-preempt
mv *.deb linux-2.6.39-rc7-preempt
cd linux-2.6.39-rc7-preempt
sudo dpkg -i *.deb

Check your /boot/grub/grub.cfg to make sure it's correct;
Reboot and check your dmesg

Start a youtube 720p video, a 720p video in VLC, and make -j64 something, jizz in your pants.

edit if you're wondering "how low can you go" in the latency department for sound and etc:

Code:

mbouffard@phy:~$ jack-info
SSE2 detected
system:playback_1
   port latency = 1.300000 ms
   total latency = 1.300000 ms
system:playback_2
   port latency = 1.300000 ms
   total latency = 1.300000 ms
buffer-size:   64 frames
samplerate:    96000

Tehra · **Posted:** Sat May 14, 2011 8:27 pm

if you're just looking to replace your kernel, you can just compile the kernel and drop it where it's supposed to go and link grub or lilo to it. no need to build a debian package of it.

anything that checks what kernel you're running would be doing so through normal linux calls, not asking the package maintainer what package is installed.

Joklem · **Posted:** Sat May 14, 2011 9:03 pm

Tehra wrote:

if you're just looking to replace your kernel, you can just compile the kernel and drop it where it's supposed to go and link grub or lilo to it. no need to build a debian package of it.

anything that checks what kernel you're running would be doing so through normal linux calls, not asking the package maintainer what package is installed.

Oh yeah, but it's convenient because the debian package does that, plus makes a folder in /lib/modules with symbolic links to the source, build dir and updated driver modules. Then you can uninstall the deb package to revert all that. Or recompile without cleaning the source dir to update a few drivers, etc.

Tehra · **Posted:** Sat May 14, 2011 9:14 pm

Joklem wrote:

Tehra wrote:

if you're just looking to replace your kernel, you can just compile the kernel and drop it where it's supposed to go and link grub or lilo to it. no need to build a debian package of it.

anything that checks what kernel you're running would be doing so through normal linux calls, not asking the package maintainer what package is installed.

Oh yeah, but it's convenient because the debian package does that, plus makes a folder in /lib/modules with symbolic links to the source, build dir and updated driver modules. Then you can uninstall the deb package to revert all that. Or recompile without cleaning the source dir to update a few drivers, etc.

make install
make modules_install

Joklem · **Posted:** Sat May 14, 2011 9:23 pm

Tehra wrote:

Joklem wrote:

Tehra wrote:

if you're just looking to replace your kernel, you can just compile the kernel and drop it where it's supposed to go and link grub or lilo to it. no need to build a debian package of it.

anything that checks what kernel you're running would be doing so through normal linux calls, not asking the package maintainer what package is installed.

Oh yeah, but it's convenient because the debian package does that, plus makes a folder in /lib/modules with symbolic links to the source, build dir and updated driver modules. Then you can uninstall the deb package to revert all that. Or recompile without cleaning the source dir to update a few drivers, etc.

make install
make modules_install

make install-modules

But yeah debian packages is a bit lazy but it doesn't add much to the build time which is already close to half an hour.

edit: what do you think of this?

Code:

#!/bin/sh
#
# JACK/Pulse/DSP startup loader                       
#                                                        
# Loads the patched up JACK/Pulse low latency setup for USB cards
# 
#      M. Bouffard <mbouffard@strangequarks.org>
#      Licensed under WTFPL
#-------------------------------------------------------------------#

# Variables
#-----------------------------------------#
PULSECONF=/home/`whoami`/jackd.pa
RACKFILE=/home/`whoami`/array.rack
LOGDIR=/home/`whoami`/logs
JACKLOG=/home/`whoami`/logs/jack.log
TRANS=/home/`whoami`/logs/transport
STATS=/home/`whoami`/logs/stats

# Clean up old log files
#-----------------------------------------#
if [ -s $LOGDIR/huge_success ]; then
   logger "JACKLoader: Starting the sound system"
   logger "JACKLoader: Mmmm, cake. I am quite pleased. Yes. Quite. (Script was succesfully run before)"
   TRIUMPH=huge_success
   rm -rf $LOGDIR/*
elif [ -s $LOGDIR/huge_failure ]; then
   logger "JACKLoader: Starting the sound system"
   logger "JACKLoader: Expected cake. Got a turd instead. (Script exited with an error before)"
   TRIUMPH=huge_failure
   rm -rf $LOGDIR/*
else
   logger "JACKLoader: Starting the sound system"
   logger "JACKLoader: Getting my cherry popped! Like a virgin. (First run)"
   TRIUMPH=virgin
   rm -rf $LOGDIR/*
fi
sleep 1


# Start JACK
#-----------------------------------------#

#      TO-DO: actually implement a way to choose the JACK settings...
#if [ "$REALTIME" == "rt" ]; then
#   jackd -dalsa -dhw:0 -r96000 -p256 -n2 -P -o2 > $JACKLOG 2>&1 &
#   echo "Scheduling: realtime\Format: 24bit\nRate: 96000hz\nFrames: 256\nPeriods: 2\nLatency: 5.3ms" > $STATS
#else
   jackd -r -dalsa -dhw:0 -r96000 -p512 -n4 -P -o2 > $JACKLOG 2>&1 &
   echo 'Scheduling: normal\nFormat: 24bit\nRate: 96000hz\nFrames: 512\nPeriods: 4\nLatency: 10.7ms' > $STATS
#fi
sleep 2 &&

# Start Pulse
#-----------------------------------------#
pulseaudio -n -F $PULSECONF >> $JACKLOG 2>&1 &
sleep 2 &&

# Start JACK transport
#-----------------------------------------#
echo "play" | jack_transport > /dev/null 2>&1 &
sleep 1 &&
jack-info > $TRANS &&

# Verify transport and notify user
#-----------------------------------------#
if [ -s $TRANS ]; then
   notify-send -i /usr/share/pixmaps/gjacktransport.png \
      "JACK" \
      "JACK and Pulse are up and operational.\nPrevious TRIUMPH level: $TRIUMPH\n`cat $STATS`"
   logger "JACKLoader: JACK and Pulse locked and loaded. And transported."
else
   notify-send -i /usr/share/pixmaps/gjacktransport.png \
      "JACK" \
      "There was an error starting the sound servers.\nPlease see the log files."
   logger "JACKLoader: I'm making a note here: HUGE FAILURE"
   echo "No cake" > $LOGDIR/huge_failure
   exit 1
fi

# Launch DSP
#-----------------------------------------#
jack-rack -n $RACKFILE > /dev/null 2>&1 &
sleep 4 &&
sleep 2 &&

# Connect the components together
#-----------------------------------------#
jack_disconnect "system:playback_1" "PulseAudio JACK Sink:front-left" >> $JACKLOG 2>&1
jack_disconnect "system:playback_2" "PulseAudio JACK Sink:front-right" >> $JACKLOG 2>&1
jack_connect "PulseAudio JACK Sink:front-left" "jack_rack:in_1" >> $JACKLOG 2>&1
jack_connect "PulseAudio JACK Sink:front-right" "jack_rack:in_2" >> $JACKLOG 2>&1
jack_connect "jack_rack:out_1" "system:playback_1" >> $JACKLOG 2>&1
jack_connect "jack_rack:out_2" "system:playback_2" >> $JACKLOG 2>&1

# All done
#-----------------------------------------#

notify-send -i /usr/share/pixmaps/gjacktransport.png \
   "JACK" \
   "The DSP is enabled and JACK is connected.\nSound card: X-Fi Surround 5.1 Pro\nChannels: Stereo"
logger "JACKLoader: DSP loaded and components connected. Leaving a cake for my next spawn."
logger "JACKLoader: Previous TRIUMPH status was: $TRIUMPH. Exiting with TRIUMPH status: huge_success."
echo "There will be cake" > $LOGDIR/huge_success
exit 0

Tehra · **Posted:** Sun May 15, 2011 4:07 pm

Joklem wrote:

Tehra wrote:

make modules_install

make install-modules

But yeah debian packages is a bit lazy but it doesn't add much to the build time which is already close to half an hour.

edit: what do you think of this?

Both are valid ways of installing modules. one's so that you can do make install, press up, _modules and press enter. the other's so you can make modules, then press up, _install and press enter.

cute script. building gcc & libc took 6 hours on a p75 with 64mb of ram. building x11 took 12 hours.

Jushiro · **Posted:** Sun May 15, 2011 5:03 pm

Joklem wrote:

Tehra wrote:

make modules_install

make install-modules

make instant noodles

Bucket Guild | FUBU BH Forums

@ Linux

Who is online