public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Griesser <tuxx@aon.at>
To: Joachim Backes <backes@rhrk.uni-kl.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.4.9, esssolo soundcard, NTFS support
Date: Mon, 20 Aug 2001 10:18:37 +0200	[thread overview]
Message-ID: <E15YkGb-0002Q8-00@mannix> (raw)
In-Reply-To: <XFMail.20010820093559.backes@rhrk.uni-kl.de>
In-Reply-To: <XFMail.20010820093559.backes@rhrk.uni-kl.de>

Outlook Users may want to press <CTRL> + <F3> here.
begin  followup on Joachim Backes:
>  having problems to build a 2.4.9 kernel with soundcard support (esssolo
>  for ex.). After having built the kernel with sound modules, depmod           >  complains about unresolved gameport_register_port and gameport_unregister_   +++port.

http://students.htblmo-klu.ac.at/tuxx/kernel-patches/es137x-2.4.6-ac2.diff

This is a workaround for your problem, should apply in 2.4.9 hopefully.

>  What has gameport to do with the soundcard support?

There are gameports an soundcards :)

>  Compiling the kernel with NTFS support fails during compilations of the
>  NTFS modules:

Known issue, discussed quite often here.
Do you people search the archives, before posting?

regards, alexx
--
|   .-.   | Alexander Griesser <tuxx@aon.at> -=- ICQ:63180135 |  .''`. |
|   /v\   |  http://www.tuxx-home.at -=- Linux Version 2.4.9  | : :' : |
| /(   )\ |  FAQ zu at.linux:  http://alfie.ist.org/LinuxFAQ  | `. `'  |
|  ^^ ^^  `---------------------------------------------------´   `-   |

      reply	other threads:[~2001-08-20  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-20  7:35 Kernel 2.4.9, esssolo soundcard, NTFS support Joachim Backes
2001-08-20  8:18 ` Alexander Griesser [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E15YkGb-0002Q8-00@mannix \
    --to=tuxx@aon.at \
    --cc=backes@rhrk.uni-kl.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox