On 2004-02-07, Peter Samuelson penned:
>
> --Fig2xvG2VGoz8o/s Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
>
> [Monique Y. Herman]
>> luigi:~# lspci | grep audio 00:02.7 Multimedia audio controller:
>> Silicon Integrated Systems [SiS] Sound Controller (rev a0)
>
> That
Hello
Monique Y. Herman (<[EMAIL PROTECTED]>) wrote:
> I must be missing something ungodly obvious ...
>
> Okay, installed kernel image 2.4.24-1-k7. I have sound:
>
> luigi:~# lsmod | grep audio
> i810_audio 24124 2
> ac97_codec 13428 0 [i810_audio]
> soundcore
[Monique Y. Herman]
> luigi:~# lspci | grep audio
> 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS]
> Sound Controller (rev a0)
That's i810_audio, as you noticed in your old module list. The
menuconfig option looks like:
Intel ICH (i8xx), SiS 7012, NVidia nForce Audio
I must be missing something ungodly obvious ...
Okay, installed kernel image 2.4.24-1-k7. I have sound:
luigi:~# lsmod | grep audio
i810_audio 24124 2
ac97_codec 13428 0 [i810_audio]
soundcore 3972 2 [i810_audio]
luigi:~# lspci | grep audio
00:02.7
On Fri, Nov 29, 2002 at 03:05:27PM +0100, Alex Polite wrote:
> When I need to recompile my kernel I usually erase my /usr/src/linux,
> get a fresh version copy in my old .config and start working.
> Compiling the kernel only takes 10 minutes, so it's no big deal. But
> still... I'd rather just reco
without erasing the /usr/src/linux,
just cd there and make menuconfig (or whichever you prefer)
the config loaded will be the one you last choosed,
so adding a module should be seconds of typing and minutes of compiling
after config,
make-kpkg clean
and make-kpkg... (usual)
hope it helps
Alex Poli
When I need to recompile my kernel I usually erase my /usr/src/linux,
get a fresh version copy in my old .config and start working.
Compiling the kernel only takes 10 minutes, so it's no big deal. But
still... I'd rather just recompile the stuff that needs it. Sometimes
It's just a matter of adding
Ok, tried it again (recompiling the kernel with both variables set) and
now dhclient works. Hence, you were right, thanks for your help. :-) I
must have overlooked something earlier.
Auke
On Sun, 2002-10-27 at 13:48, Colin Watson wrote:
> On Sun, Oct 27, 2002 at 01:26:31PM +0100, Auke Jilderda
Hi fellow Eindhovenaar, (judging from the emailadress :-)),
I also posted my question on the debian-laptop list (because it seemed
to fit their better on second thought) and here's a clue to the issue at
hand:
| > "Auke" == Auke Jilderda <[EMAIL PROTECTED]> writes:
|
| Auke> Why do I need th
For most users dhclient works perfectly with kernel 2.4, IMHO. There seems
to be something interesting in Auke's case.
Qian
On 27 Oct 2002, Shyamal Prasad wrote:
> "Auke" == Auke Jilderda <[EMAIL PROTECTED]> writes:
>
> Auke> Makes me wonder though: Why the heck does Woody default come
>
"Auke" == Auke Jilderda <[EMAIL PROTECTED]> writes:
Auke> Makes me wonder though: Why the heck does Woody default come
Auke> with dhclient if it doesn't even work with kernel 2.4? I'd
Auke> suspect this is a problem more people will run into.
Uh? It dhclient works great for me wi
Ofcourse I included CONFIG_PACKET and I tried both with and without
CONFIG_FILTER. None worked. Why would CONFIG_FILTER be required? It
seems unrelated to DHCP to me.
Auke
On Sun, 2002-10-27 at 13:48, Colin Watson wrote:
>
> woody's dhclient does work with 2.4. You did remember to include bo
On Sun, Oct 27, 2002 at 01:26:31PM +0100, Auke Jilderda wrote:
> Yup, that did the trick! Thanks a lot, I started to get a serious
> headache from hitting the wall for hours. ;-)
>
> Makes me wonder though: Why the heck does Woody default come with
> dhclient if it doesn't even work with kernel 2
Yup, that did the trick! Thanks a lot, I started to get a serious
headache from hitting the wall for hours. ;-)
Makes me wonder though: Why the heck does Woody default come with
dhclient if it doesn't even work with kernel 2.4? I'd suspect this is a
problem more people will run into.
Anyway, th
I just installed Woody onto a brand new laptop (Dell Latitude c610).
Used a little installation cd and fetched the rest from the Net
(including security updates). Everything worked pretty good.
Had to get X-windows from unstable and compile the kernel to add a
couple of things:
- "Dell laptop su
On Wed, 21 Jul 1999, Stuart Ballard wrote:
> I was just thinking about the fact that the answer to many questions
> that I see on the list (mostly "how do I get sound?") is "recompile your
> kernel". Also the fact that recompiling the kernel is pretty much
> recommended in any situation.
In some
Hi there,
I was just thinking about the fact that the answer to many questions
that I see on the list (mostly "how do I get sound?") is "recompile your
kernel". Also the fact that recompiling the kernel is pretty much
recommended in any situation.
It occurred to me that perhaps, after the rest of
Quoting Brad ([EMAIL PROTECTED]):
> On Tue, 20 Jul 1999, David Wright wrote:
>
> > There were two. You didn't leave one there, did you?
>
> Recently, i noticed a file "setup-localhost" showed up in /etc/init.d (and
> properly symlinked) that tries to configure the lo interface (which is
> already
On Tue, 20 Jul 1999, David Wright wrote:
> Quoting Stuart Ballard ([EMAIL PROTECTED]):
> > Just one more question... I still get the notorious "SIOCADDRT: Invalid
> > argument" error on bootup. I've read all over the place that the
> > solution to this is to comment out the "route add -net" line i
Quoting Stuart Ballard ([EMAIL PROTECTED]):
> David Wright wrote:
> >
> > Quoting Stuart Ballard ([EMAIL PROTECTED]):
> > > I just compiled kernel 2.2.10 on my potato machine. This is the first
> > > time I've ever compiled a kernel, so these questions are probably
> > > elementary, but I can't fi
David Wright wrote:
>
> Quoting Stuart Ballard ([EMAIL PROTECTED]):
> > I just compiled kernel 2.2.10 on my potato machine. This is the first
> > time I've ever compiled a kernel, so these questions are probably
> > elementary, but I can't find the right docs anywhere...
> >
[Snipped question abou
Quoting Stuart Ballard ([EMAIL PROTECTED]):
> I just compiled kernel 2.2.10 on my potato machine. This is the first
> time I've ever compiled a kernel, so these questions are probably
> elementary, but I can't find the right docs anywhere...
>
> I used the build sequence from
> /usr/doc/kernel-sou
I just compiled kernel 2.2.10 on my potato machine. This is the first
time I've ever compiled a kernel, so these questions are probably
elementary, but I can't find the right docs anywhere...
I used the build sequence from
/usr/doc/kernel-source-2.2.10/debian.README.gz, which essentially was
"make
You need the bin86 pacakge. The kernel-package will make it go nicer.
Help!! I'm getting the following error messages on recompiling the
kernel to recognise my Ensoniq AudioPCI sound card:
make [1] as86: Command not found
make [1]: [bootsect.o] Error 127
make [1]: Leaving directory /usr/kernel-source-2.0.36/arch/i386/boot
make [1]: *** [zImage] Error 2
Originally,
John Galt <[EMAIL PROTECTED]> writes:
> Of course, you COULD solve all of this with kernel-packages, which makes
> the prospective kernel into a .deb file for easy installation. The
> zImage/bzImage problem is solved by kernel-package: IIRC it uses the
> Debian standard bzImage by preference, but
Of course, you COULD solve all of this with kernel-packages, which makes
the prospective kernel into a .deb file for easy installation. The
zImage/bzImage problem is solved by kernel-package: IIRC it uses the
Debian standard bzImage by preference, but either way, it works so well
that there's no
William R Pentney <[EMAIL PROTECTED]> writes:
> I'm currently compiling the 2.2 kernel for my slink system (it's
> relatively stable, right?), and I used "make bzImage" to create it. The
> README says to copy zImage to the current kernel image, but should I copy
> bzImage instead? (I just want to
Subject: Question about recompiling kernel ...
Date: Tue, Apr 13, 1999 at 04:47:24PM -0400
In reply to:William R Pentney
Quoting William R Pentney([EMAIL PROTECTED]):
>
> I'm currently compiling the 2.2 kernel for my slink system (it's
> relatively stable,
William R Pentney <[EMAIL PROTECTED]> writes:
WRP> I'm currently compiling the 2.2 kernel for my slink system (it's
WRP> relatively stable, right?), and I used "make bzImage" to create it. The
WRP> README says to copy zImage to the current kernel image, but should I copy
WRP> bzImage instead? (I ju
use the package :
kernel-package, it wll do all automaticaly.
I'm currently compiling the 2.2 kernel for my slink system (it's
relatively stable, right?), and I used "make bzImage" to create it. The
README says to copy zImage to the current kernel image, but should I copy
bzImage instead? (I just want to be sure before I do it ... the
documentation's a littl
>
> Hi,
> Here's a practical problem I encountered when recompiling 3c59x.c
> with kernel source 2.0.34. I followed instructions from Donald
> Becker: 1. install source code in /usr/src
> 2. cd /usr/src/linux; make include/linux/version.h
> 3. cp 3c59x.c /usr/src/linux/modules
>
Hi,
Here's a practical problem I encountered when recompiling 3c59x.c
with kernel source 2.0.34. I followed instructions from Donald
Becker: 1. install source code in /usr/src
2. cd /usr/src/linux; make include/linux/version.h
3. cp 3c59x.c /usr/src/linux/modules
4. gcc -
Try This
edit the Makefile and uncomment the SMP lines
make mrproper
make menuconfig (select Sound Support with a 'Y')
-Select the correct drivers
-(If sound blaster set io, irq etc.)
-in the 2.0.34 kernel there is a setting to "Use the old sound
configuration script--U
I had something of the same problem - turned out that my SB-compatible
card is on IRQ 5 instead of default 7, I change the setting in
/usr/src/linux/drivers/sound/Config.in and all worked well. It could be
something similar, maybe IRQ or DMA conflict...
good luck
---
Just call me a "sugar vampire"
t;X-Authentication-Warning: central.boulder.nist.gov: majordom set sender to
owner-lug using -f
>Delivered-To: [EMAIL PROTECTED]
>From: "LJP" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: Re: [lug] recompiling kernel and not loosing sound support
>Date: Sun, 4 Oct
Forwarded:
>X-Authentication-Warning: central.boulder.nist.gov: majordom set sender to
owner-lug using -f
>Date: Sun, 4 Oct 1998 15:36:46 -0600 (MDT)
>From: Manny Roque <[EMAIL PROTECTED]>
>X-Sender: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: [lug] recompilin
>> "CE" == Chris Evans <[EMAIL PROTECTED]> writes:
CE> 2nd newbie question:
CE> I know I have to change one line in the makefile to get a comment
CE> hash removed to reveal smp=1 to get my kernel makefile ready to
CE> recompile the kernel for my twin pentium machine in SMP mode.
CE> The catc
2nd newbie question:
I know I have to change one line in the makefile to get a comment
hash removed to reveal smp=1 to get my kernel makefile ready to
recompile the kernel for my twin pentium machine in SMP mode.
The catch is that I don't want to mess this up. Please would
someone tell me e
On Tue, May 05, 1998 at 12:02:30PM -0400, Bill Leach wrote:
> Hi Gerald;
>
> Though I noticed your original posting I did not then comment for it
> being too much of a 'blind leading the blind' situation.
More like the blind leading the stupid... Read on.
>
> What I did notice is that
Hi Gerald;
Though I noticed your original posting I did not then comment for it
being too much of a 'blind leading the blind' situation.
What I did notice is that the lines you quoted:
On Tue, May 05, 1998 at 12:25:40AM -0700, G. Crimp wrote:
[snip]
> if hash encaps 2> /dev/null; then \
> obj
Nathan E Norman wrote:
>On Tue, 5 May 1998, Oliver Elphick wrote:
>: Presumably someone else was having some kind of problem with this
>: feature.
>
>But why is "-k" being passed to `objdump' at all? According to the docs
>I have, "-k" is indeed not a legal option to `objdump'.
>
>
On Tue, 5 May 1998, Oliver Elphick wrote:
: "G. Crimp" wrote:
[ snip ]
: >if hash encaps 2> /dev/null; then \
: > objdump -k -q -o 0x10 /usr/src/kernel-source-2.0.30/vmlinux >
^^
: >$tmppiggy; \
: >else \
: > objcopy -O binary -R .note -R .comment -R .stab -R .
"G. Crimp" wrote:
...
> I finally installed the kernel-package as you suggested. I was
>hoping first to find out where my problem was coming from with the
>non-Debian specific kernel compile procedures. I am back to square one
>after trying `make-kpkg --revision custom.1.0 kernel-imag
On Sun, Apr 19, 1998 at 11:39:52PM +0200, Marcus Brinkmann wrote:
>
> Try kernel-package. "make-kpkg --revision custom.1.0 kernel-image" will
> creat you a deb file with your kernel. Then install the deb file in /usr/src
> with "dpkg -i " and answer "yes" when it is offering to make a
> boot disk.
On Wed, Apr 29, 1998 at 11:32:27AM -0400, Scott Ellis wrote:
[snip]
> > Somewhere in usr/src/linux/arch/i386/boot/compressed there is a file
> > that is invoking objdump (whatever that might be) with an option `-k'.
> > make zdisk and make zImage say this is an illegal option.
[snip]
> >
>
> If that is the case, then I'm not sure this will solve my problem.
> I think the problem is with the compile itself, and I don't know enough
> about C and make scripts, etc. to figure it out. Somewhere in
> /usr/src/linux/arch/i386/boot/compressed there is a file that is invoking
> objdu
On Sun, Apr 19, 1998 at 11:39:52PM +0200, Marcus Brinkmann wrote:
> On Sat, Apr 18, 1998 at 10:28:10PM -0700, G. Crimp wrote:
> > Hi,
> >
> > I tried recompiling the kernel to include sound support for a newly
> > acquired card. I got an error that I don't understand. I'm using Deb
> > 1.3.1
On Sat, Apr 18, 1998 at 10:28:10PM -0700, G. Crimp wrote:
> Hi,
>
> I tried recompiling the kernel to include sound support for a newly
> acquired card. I got an error that I don't understand. I'm using Deb
> 1.3.1, kernel 2.0.30. The card is of unknown manufacturer, 16 bit, chipset
> ES
Hi,
I tried recompiling the kernel to include sound support for a newly
acquired card. I got an error that I don't understand. I'm using Deb
1.3.1, kernel 2.0.30. The card is of unknown manufacturer, 16 bit, chipset
ESS 1868. I pretty much followed the same compile instructions that I
On Sat, 7 Dec 1996, Paul Christenson wrote:
> There is something that I've been wondering.. Why is everyone so
> fascinated with modules? I acknowledge that they have their uses, but
> how many people really need to UNLOAD a module once it's loaded?
>
> If you need it, compile it into the kernel,
On Sat, 7 Dec 1996, Paul Christenson wrote:
>
> There is something that I've been wondering.. Why is everyone so
> fascinated with modules? I acknowledge that they have their uses, but how
> many people really need to UNLOAD a module once it's loaded?
>
> If you need it, compile it into the ke
On Fri, 6 Dec 1996, Bruce Perens wrote:
> We had a report that adding PPP to /etc/modules rather than letting kerneld
> load it made it work. I don't know why that would be, so if you can
> corroborate it, that would help.
This isn't directed to you, Bruce.. but your message brought up a point.
We had a report that adding PPP to /etc/modules rather than letting kerneld
load it made it work. I don't know why that would be, so if you can
corroborate it, that would help.
Thanks
Bruce
--
Bruce Perens K6BP [EMAIL PROTECTED]
Finger [EMAIL PROTECTED] for PGP public key.
PGP f
Title says most of it.
I have had this problem before, and now I can't figure out how to fix it, nor
can I find the previous reference in the mailing list archives.
So here it is: I have been running 2.0.6 kernel for some time now with no
problems. I was experimenting around with trying to get
Kevin,
A similar problem occurs if mgetty is running on ttyS1 and I try to dial out
for ppp using cua1 - the messages is "Sorry - this system lacks PPP kernel
support". Changing the ppp dial out to ttyS1 works fine.
This looks like the reporting problem is either with the kernel or with pppd.
I
-BEGIN PGP SIGNED MESSAGE-
On Wed, 18 Sep 1996, Kevin Conover wrote:
kcppp>When I first came up with 2.0.0, I tested the modem with minicom before
kcppp>attempting PPP. No problem. After compiling the new kernel, I didn't
test
kcppp>minicom. I compiled the kernel a dozen times, somet
Hi All,
I'm replying to my own message since I got several responses and my problem
is now solved. Unfortunately, the problem (& solution) turned out to be
completely different.
When I first came up with 2.0.0, I tested the modem with minicom before
attempting PPP. No problem. After compiling
On Mon, 16 Sep 1996 08:48:06 EDT Kevin Conover ([EMAIL PROTECTED])
wrote:
> It installed 2.0.0. I got everything installed, including X (a
> pain, my #9 Motion 771 likes to shift the screen dramatically).
For this card, you need to add a
InvertVCLK "*" 0
for every Display section in ev
Hi All,
ok, yet another newbie to debian. I think I've RTFM but I'm missing
something.
the problem: "this kernel doesn't support ppp"
what I've done:
I just got a CD of debian 1.1.6 (with kernel 2.0.0 and 2.0.12) from
i-connect. It installed 2.0.0. I got everything installed, including X (a
Kevin> what am I missing?!?!?!?
You didn't tell us what you were selecting for PPP in "make xconfig". If I am
not mistaken, you need modules. I always use them where I can, and they work
great for me. I select:
#
# Network device support
#
CONFIG_NETDEVICES=y
62 matches
Mail list logo
