Re:Question for the masses of linu-geeks
by
ink
·
· Score: 3, Informative
cd/usr/src
rm linux
mkdir linux-2.4.8
ln -s linux-2.4.8 linux
bunzip2 -c linux-2.4.8.tar.bz2 | tar xv
cp old-redhat-linux/.config linux
cd linux
make menuconfig (config, xconfig, whatever)
make dep && make bzImage && make modules && make modules_install
cp arch/blah/boot/bzImage/boot/bzImage-2.2.18
emacs/etc/lilo.conf
lilo; sync
reboot
Change as you prefer, of course.
-- The wheel is turning, but the hamster is dead.
emu10k1 drivers broken on compile
by
Omnifarious
·
· Score: 3, Informative
The Makefile for the emu10k1 drivers erroneously includes 'joystick.o' in the emu10k1.o module. That.o file should only be included in 2.2 kernels in the first place, and in those, it should be stuck into a seperate module, emu10k1-joy.o
Re:Just hit kernel.org?
by
mlafranc
·
· Score: 3, Informative
Please kids, it's simple, I got my PATCH within 25 seconds of typying:
src@primal:~$ ftp ftp.ca.kernel.org
ftp
me@myaddress.com
cd pub/linux/kernel/v2.4
get patch-2.4.8.bz2
get patch-2.4.8.bz2.sign
bye
KeepItSimpleStupid
Use a MIRROR!
ftp.YOURCOUNTRYABBREV.kernel.org
Re:Build Fails
by
kilrogg
·
· Score: 3, Informative
The patch was rushed in at the last minute:
From the kernel mailing list:
"hm, edit drivers/sound/emu10k1/Makefile and remove the object reference
for `joystick.o' -- i dont compile as a module so i missed this, thanks."
Re:But I just got 2.4.7 working right!!!
by
Uruk
·
· Score: 5, Informative
Older config files usually work great, especially just between a patchlevel difference like 2.4.7 -> 2.4.8.
Go into your source directory and do a "make mrproper". Then copy your old config file into ".config" and run "make oldconfig". It *might* ask you one or two questions, often they won't matter if your old kernel was working OK as is.
Then just go straight to the "make dep", "make bzImage", "make modules", etc.
Life would suck without the "make oldconfig" target.:)
-- --
Truth goes out the door when rumor comes innuendo. -- Groucho Marx
Re:Fix available
by
Sits
·
· Score: 2, Informative
This update adds support for the 5.1 cards (including the IR remote, though it's still being reversed-eng'd), AC3 passthrough, multichannel playback (for AC3 pre-decoded in software), sequencer support, dsp effects (flanger, chorus, etc), and much more.
This is the first sync with CVS in almost a year (development was idle between Nov-April). Report any problems with the driver on the emu10k1 mailing, here:
emu10k1-devel@opensource.creative.com
Ok, this one has various VM niceness tweaks that have made some people
much happier. It also does a upgrade to the XFree86-4.1.x style DRM code,
which means that people with XFree86-4.0.x can no longer use the built-in
kernel DRM by default.
However, never fear. It's actually very easy to get the old DRM code too:
if you used to use the standard kernel DRM and do not want to upgrade to a
new XFree86 setup, just get the "drm-4.0.x" package from the same place
you get the kernel from, and do
- unpack the kernel
- cd linux/drivers/char
- unpack the "drm-4.0.x" package here
- mv drm new-drm
- mv drm-4.0.x drm
and you should be all set.
Re:EMU10K1 fixes, still no ice1712/envy24 :-(
by
Anonymous Coward
·
· Score: 1, Informative
I just received my DIO2496 card, and it works well
with the latest alsa 0.9.0beta6, and envy24control
from cvs tree.
I am listening to music stored on my HD (raw pcm, no mp3 thanks) on my stereo system, via the optical output of the card.
Re:EMU10K1 fixes, still no ice1712/envy24 :-(
by
Phork
·
· Score: 3, Informative
well thtas all well and good, but he is talking about delta cards, not hte sblive, there are multiple free drivers for sblive, but the poster said there are no free drivers for the delta cards that work(though a comment says the alsa drivers works now). Read the comment(not just the title), then reply.
-- --
free as in swatantryam - not soujanyam.
Re:But I just got 2.4.7 working right!!!
by
norton_I
·
· Score: 4, Informative
In case you didn't realize it: You should run "make oldconfig" after patching your kernel to make sure everything is in order, and to see what new options there are (I didn't see any in this one)
Re:Build Fails
by
Anonymous Coward
·
· Score: 3, Informative
Nope... Its not just you... Apparently the update to the emu10k broke building it as a module. I just build it into the kernel itself (not as a module) and it seems to work fine.
Re:What I Want To Know Is...
by
danEger
·
· Score: 3, Informative
The reason why the latest i-patch doesn't work with newest kernels is because of some minor problems with the Makefile.
For 2.4.7, I found this: http://www.xs4all.nl/~marceln/Misc/patch-int-2.4.7.mn1.bz2. Works perfectly for me. I hope it works with 2.4.8 too:)
-Hans
Just hit kernel.org?
by
qslack
·
· Score: 5, Informative
I wonder why the/. editors are telling us to "Just hit Kernel.org" when everyone SHOULD use the mirrors.
Wait a few hours for the changes to propogate, then find a local mirror at http://kernel.org/mirrors/. It helps everyone: Kernel.org still has bandwidth, and you get faster download speeds!
Re:Hurry up and wait
by
tzanger
·
· Score: 3, Informative
Damn. I forgot about that stupid third party kernel patch for my Tekram/Creative Labs/Nvidia/ hardware.
Not sure what you're smoking but most kernel updates don't break third-party drivers unless the source API has changed -- something which doesn't occur often in stable releases.
My nVidia kernel module (1241) has compiled without issue on every 2.4.x release to date. The VMWare kernel modules have worked up to 2.4.7, where they did manage to change the source API and ended up breaking compatibility. However, the VMWare mailing lists provided an answer (patch) the same day that the new kernel was released.
Perhaps you should start using the more expensive crack, since the cheap stuff seems to be affecting your thinking.
Re:2.4.6+ broke vmware
by
mrossbrown
·
· Score: 5, Informative
I wouldn't mention this, but 2.4 is supposed to be the STABLE tree. If the interface is changing, that's what the 2.5 series is for.
You shouldn't have. 2.4.x is the stable tree, which means that bugfixes, optimizations, and suggestions of improvement go into these kernels. Massive changes to the entire tree (like a rewrite of the MM, CML2) do not, as it would break kernel builds for a number of releases.
Something as big as compatability with VMWare ought to be checked before releasing.
Hmm, I think you have it the other way around. The VMWare developers are responsible for any breakage to their source-only modules, that's the reason they distribute them in source form, so that they can be in tune with the latest kernel release.
Anyway, get all your 2.4.6+ (and older) VMWare kernel fixes here:
Professional users of Linux are still hurting for credibility, and this kind of thing just does not help.
Professional Linux users already know that when you update a kernel, anything that's closely tied to the kernel (ALSA, VMWare, etc.) gets recompiled too. It comes with the territory.
M. R.
Re:Build Fails
by
Anonymous Coward
·
· Score: 3, Informative
read the changelog...
they've changed teh emu10k module...
merged it with some other stuff.
the options will be different.
bound to happen eventually.
consider it a Good Thing (tm)
It means the driver you rely on
is now (hopefully) that much stabler.
Re:Aureal Vortex
by
Anonymous Coward
·
· Score: 3, Informative
For those who don't know of which CVS tree Nitsuj speaks of, go to aureal.sourceforge.net, and checkout the CVS repository there.
Re:But I just got 2.4.7 working right!!!
by
jhittner
·
· Score: 2, Informative
You could also use the save config to alt file, and load config from alt file in make menuconfig and make xconfig
Its also a nice way of tracking different configurations
Slashdot Mirror
Yes this would be much better in the original article.
-- Could you use my software consulting serv
- cd
/usr/src
- rm linux
- mkdir linux-2.4.8
- ln -s linux-2.4.8 linux
- bunzip2 -c linux-2.4.8.tar.bz2 | tar xv
- cp old-redhat-linux/.config linux
- cd linux
- make menuconfig (config, xconfig, whatever)
- make dep && make bzImage && make modules && make modules_install
- cp arch/blah/boot/bzImage
/boot/bzImage-2.2.18
- emacs
/etc/lilo.conf
- lilo; sync
- reboot
Change as you prefer, of course.The wheel is turning, but the hamster is dead.
The Makefile for the emu10k1 drivers erroneously includes 'joystick.o' in the emu10k1.o module. That .o file should only be included in 2.2 kernels in the first place, and in those, it should be stuck into a seperate module, emu10k1-joy.o
Need a Python, C++, Unix, Linux develop
Please kids, it's simple, I got my PATCH within 25 seconds of typying:
src@primal:~$ ftp ftp.ca.kernel.org
ftp
me@myaddress.com
cd pub/linux/kernel/v2.4
get patch-2.4.8.bz2
get patch-2.4.8.bz2.sign
bye
KeepItSimpleStupid
Use a MIRROR!
ftp.YOURCOUNTRYABBREV.kernel.org
From the kernel mailing list:
"hm, edit drivers/sound/emu10k1/Makefile and remove the object reference for `joystick.o' -- i dont compile as a module so i missed this, thanks."
Older config files usually work great, especially just between a patchlevel difference like 2.4.7 -> 2.4.8.
:)
Go into your source directory and do a "make mrproper". Then copy your old config file into ".config" and run "make oldconfig". It *might* ask you one or two questions, often they won't matter if your old kernel was working OK as is.
Then just go straight to the "make dep", "make bzImage", "make modules", etc.
Life would suck without the "make oldconfig" target.
-- Truth goes out the door when rumor comes innuendo. -- Groucho Marx
As mentioned in another post there is a fix available for this. Take a look at this post emu10k1 mailing list.
The user-tools can be download here
This update adds support for the 5.1 cards (including the IR remote, though it's still being reversed-eng'd), AC3 passthrough, multichannel playback (for AC3 pre-decoded in software), sequencer support, dsp effects (flanger, chorus, etc), and much more.
This is the first sync with CVS in almost a year (development was idle between Nov-April). Report any problems with the driver on the emu10k1 mailing, here: emu10k1-devel@opensource.creative.com
As Linus wrote in his e-mail to LKML:
Ok, this one has various VM niceness tweaks that have made some people
much happier. It also does a upgrade to the XFree86-4.1.x style DRM code,
which means that people with XFree86-4.0.x can no longer use the built-in
kernel DRM by default.
However, never fear. It's actually very easy to get the old DRM code too:
if you used to use the standard kernel DRM and do not want to upgrade to a
new XFree86 setup, just get the "drm-4.0.x" package from the same place
you get the kernel from, and do
- unpack the kernel
- cd linux/drivers/char
- unpack the "drm-4.0.x" package here
- mv drm new-drm
- mv drm-4.0.x drm
and you should be all set.
I just received my DIO2496 card, and it works well with the latest alsa 0.9.0beta6, and envy24control from cvs tree. I am listening to music stored on my HD (raw pcm, no mp3 thanks) on my stereo system, via the optical output of the card.
well thtas all well and good, but he is talking about delta cards, not hte sblive, there are multiple free drivers for sblive, but the poster said there are no free drivers for the delta cards that work(though a comment says the alsa drivers works now). Read the comment(not just the title), then reply.
-- free as in swatantryam - not soujanyam.
In case you didn't realize it: You should run "make oldconfig" after patching your kernel to make sure everything is in order, and to see what new options there are (I didn't see any in this one)
Nope... Its not just you... Apparently the update to the emu10k broke building it as a module. I just build it into the kernel itself (not as a module) and it seems to work fine.
The reason why the latest i-patch doesn't work with newest kernels is because of some minor problems with the Makefile. For 2.4.7, I found this: http://www.xs4all.nl/~marceln/Misc/patch-int-2.4.7 .mn1.bz2. Works perfectly for me. I hope it works with 2.4.8 too :)
-Hans
I wonder why the /. editors are telling us to "Just hit Kernel.org" when everyone SHOULD use the mirrors.
Wait a few hours for the changes to propogate, then find a local mirror at http://kernel.org/mirrors/. It helps everyone: Kernel.org still has bandwidth, and you get faster download speeds!
qslack.com
Damn. I forgot about that stupid third party kernel patch for my Tekram/Creative Labs/Nvidia/ hardware.
Not sure what you're smoking but most kernel updates don't break third-party drivers unless the source API has changed -- something which doesn't occur often in stable releases.
My nVidia kernel module (1241) has compiled without issue on every 2.4.x release to date. The VMWare kernel modules have worked up to 2.4.7, where they did manage to change the source API and ended up breaking compatibility. However, the VMWare mailing lists provided an answer (patch) the same day that the new kernel was released.
Perhaps you should start using the more expensive crack, since the cheap stuff seems to be affecting your thinking.
Anyway, get all your 2.4.6+ (and older) VMWare kernel fixes here:
I'm currently using VMWare with 2.4.7.
Professional Linux users already know that when you update a kernel, anything that's closely tied to the kernel (ALSA, VMWare, etc.) gets recompiled too. It comes with the territory.M. R.
read the changelog...
they've changed teh emu10k module...
merged it with some other stuff.
the options will be different.
bound to happen eventually.
consider it a Good Thing (tm)
It means the driver you rely on
is now (hopefully) that much stabler.
For those who don't know of which CVS tree Nitsuj speaks of, go to aureal.sourceforge.net, and checkout the CVS repository there.
You could also use the save config to alt file, and load config from alt file in make menuconfig and make xconfig
Its also a nice way of tracking different configurations