Previously Jason Gunthorpe wrote:
> That's exactly what it means. As Wichert pointed out, you need PCI for
> ALSA to work - period. If you don't want PCI then you must hack alsa.
I'll add some checking to the postinst of ALSA to check for PCI support
in the kernel and warn if it isn't there.
> I
Jason Gunthorpe wrote:
>
> What exactly is that checksum a checksum of? I would hope that it is a
> hash of the function signature which should be constant for any kernel
> version. If it is a hash of the contents then there is no point in having
> binary modules..
It is computed from the signatu
On Fri, 12 Jun 1998, Herbert Xu wrote:
> > The thing you must realize is if those symbols are no present in your
> > kernel then there is nothing you can do to make that module work.
>
> Not strictly true. The symbols refered to above are always in the kernel, but
> the checksum is very much ve
In article <[EMAIL PROTECTED]> you wrote:
> On Thu, 11 Jun 1998, Hamish Moffatt wrote:
>>
>> Well, this sounds find, but I've never observed this to actually work.
>>
>> [5:30pm] [EMAIL PROTECTED]:~# dpkg -s ntfs2.0.33
>> Package: ntfs2.0.33
>> Status: install ok installed
>>
>> [5:30pm] [EMAIL
On Thu, Jun 11, 1998 at 07:17:19PM -0600, Jason Gunthorpe wrote:
> For instance, in this case you may not have mod versions enabled, it might
> be possible to convice ntfs to build without them and it might work, but
> it is equally good for you to compile your kernel with mod versions
> enabled to
On Thu, 11 Jun 1998, Yann Dirson wrote:
> Jason Gunthorpe writes:
> > Hm, we should really talk to the kernel people.. but here is my thoughts,
> > #1 - If person X compiles a module for kernel x.x.x and it doesn't work
> >on your compile of x.x.x then you need to recompile your kern
On Thu, 11 Jun 1998, Hamish Moffatt wrote:
>
> Well, this sounds find, but I've never observed this to actually work.
>
> [5:30pm] [EMAIL PROTECTED]:~# dpkg -s ntfs2.0.33
> Package: ntfs2.0.33
> Status: install ok installed
>
> [5:30pm] [EMAIL PROTECTED]:~# modprobe ntfs
> /lib/modules/2.0/fs/n
Wichert Akkerman writes:
> Previously Yann Dirson wrote:
> > It does not seem that we have currently any conventions regarding the
> > packaging of kernel modules. I just tried the new alsadriver from
> > slink, and, for the same reason I could not use the packaged joystick
> > driver, this o
Jason Gunthorpe writes:
> Hm, we should really talk to the kernel people.. but here is my thoughts,
> #1 - If person X compiles a module for kernel x.x.x and it doesn't work
>on your compile of x.x.x then you need to recompile your kernel.
>[General rule, most modules don't tr
On Thu, Jun 11, 1998 at 01:49:36AM -0400, Gregory S. Stark wrote:
> Hamish Moffatt <[EMAIL PROTECTED]> writes:
> > This sounds excellent. On one machine I am running 2.0.33
> > and have the appropriate ntfs package installed, but it will not insert
> > (many missing symbols), presumably because it
Hamish Moffatt <[EMAIL PROTECTED]> writes:
> On Wed, Jun 10, 1998 at 10:41:41AM +0200, Yann Dirson wrote:
>
> > I think the various modules should be primarily packaged in source
> > form, just as the kernel is, and installed under /usr/src/modules/.
>
> This sounds excellent. On one machine I a
On Wed, 10 Jun 1998, Yann Dirson wrote:
> It does not seem that we have currently any conventions regarding the
> packaging of kernel modules. I just tried the new alsadriver from
> slink, and, for the same reason I could not use the packaged joystick
> driver, this one too is useless to me.
H
Previously Yann Dirson wrote:
> It does not seem that we have currently any conventions regarding the
> packaging of kernel modules. I just tried the new alsadriver from
> slink, and, for the same reason I could not use the packaged joystick
> driver, this one too is useless to me.
Can you try re
Previously Branden Robinson wrote:
> For the sake of raging paranoia about namespace pollution, perhaps the
> directory is best called "kernel-modules".
Since we already have pcmcia packages use /usr/src/modules and nobody
seems to complain about that, I think it's save to use that.
Wichert.
--
Yann Dirson writes:
> I think the various modules should be primarily packaged in source
> form, just as the kernel is, and installed under /usr/src/modules/.
> >From these source packages, the binary packages would be generated for
> the various binary kernel images shipped with Debian (presumably
On Wed, Jun 10, 1998 at 06:47:57PM +1000, Hamish Moffatt wrote:
> On Wed, Jun 10, 1998 at 10:41:41AM +0200, Yann Dirson wrote:
> > I think the various modules should be primarily packaged in source
> > form, just as the kernel is, and installed under /usr/src/modules/.
>
> This sounds excellent. O
On Wed, Jun 10, 1998 at 10:41:41AM +0200, Yann Dirson wrote:
> I think the various modules should be primarily packaged in source
> form, just as the kernel is, and installed under /usr/src/modules/.
This sounds excellent. On one machine I am running 2.0.33
and have the appropriate ntfs package in
It does not seem that we have currently any conventions regarding the
packaging of kernel modules. I just tried the new alsadriver from
slink, and, for the same reason I could not use the packaged joystick
driver, this one too is useless to me.
Here are the main criticisms I have regarding how m
18 matches
Mail list logo
