Re: Why are module parameters under /etc/modprobe.d not respected?

2024-09-09 Thread Stefan Monnier
>> > options snd_hda_intel id=[HDMI,PCH] index=1,0 >> Might be you need to write with dashes, as the module files is named >> with dashes. > Thank you for the reply. However, dashes and underscores can be > interchanged in these files. FWIW: That's been my experience for the `modprobe` command arg

Re: Why are module parameters under /etc/modprobe.d not respected?

2024-09-07 Thread ael
On Fri, Sep 06, 2024 at 10:00:20AM +0700, Max Nikulin wrote: > > Have you read log messages reported by journalctl? There is a systemd unit > to load modules, but I expect that this one should be autoloaded in response > to an udev event. Yes, I did try to find anything relevant using journalctl.

Re: Why are module parameters under /etc/modprobe.d not respected?

2024-09-07 Thread ael
On Thu, Sep 05, 2024 at 08:52:26PM +0200, Franco Martelli wrote: > > I am running debian testing, updated daily. > I'm on stable, so I can't help much > > > > > After yesterday's update, the kernel module snd_hda_intel is being > > loaded with the wrong (default) parameters. > Have you verified t

Re: Why are module parameters under /etc/modprobe.d not respected?

2024-09-05 Thread Max Nikulin
On 03/09/2024 22:51, ael wrote: I have /etc/modprobe.d/snd-hda.conf which specifies: options snd_hda_intel id=[HDMI,PCH] index=1,0 [...] Maybe there are some release notes that I have failed to read? Can anyone point me in the right direction? (If the direction is Devuan, I have already moved

Re: Why are module parameters under /etc/modprobe.d not respected?

2024-09-05 Thread Franco Martelli
Hi, On 03/09/24 at 17:51, ael wrote: Hello, I am running debian testing, updated daily. I'm on stable, so I can't help much After yesterday's update, the kernel module snd_hda_intel is being loaded with the wrong (default) parameters. Have you verified this by running the following command

Re: Why are module parameters under /etc/modprobe.d not respected?

2024-09-03 Thread ael
ked dmsg and found nothing helpful. And just checked the kernel documention in linux-stable/Documentation/DocBook/admin-guide/kernel-parameters.rst which states: --- Module parameters can be specified in two ways: via the kernel command line with a module name prefi

Re: Why are module parameters under /etc/modprobe.d not respected?

2024-09-03 Thread ael
underscores as does /proc/modules. So I assume the underscore is actually the "real" name/alias. > Might be brackets are not the correct syntax for an array option. Well, yes the documentation on these module parameters is not very clear. However that options line has been working f

Re: Why are module parameters under /etc/modprobe.d not respected?

2024-09-03 Thread Nicolas George
ael (12024-09-03): > options snd_hda_intel id=[HDMI,PCH] index=1,0 Might be you need to write with dashes, as the module files is named with dashes. Might be brackets are not the correct syntax for an array option. Regards, -- Nicolas George

Why are module parameters under /etc/modprobe.d not respected?

2024-09-03 Thread ael
Hello, I am running debian testing, updated daily. After yesterday's update, the kernel module snd_hda_intel is being loaded with the wrong (default) parameters. I have /etc/modprobe.d/snd-hda.conf which specifies: options snd_hda_intel id=[HDMI,PCH] index=1,0 The details are very unlikely to b

Re: Setting module parameters?

2007-04-29 Thread Andrew M.A. Cater
27;t see, to help. I notice that that post is rather > old though. Is there a different way to set those module parameters now? > Is there a better way to solve this problem now? (other than buying a new > nic). > > Thanks > -Colin > > > -- > To UNSUBSCRIBE, ema

Re: Setting module parameters?

2007-04-29 Thread Andrew Sackville-West
3c905B that is using the 3c59x driver module, but it will > only come up at 10 Mb/s instead of 100. I tried the solution listed in > that link, but it doesn't see, to help. I notice that that post is rather > old though. Is there a different way to set those module parameters now? &g

Setting module parameters?

2007-04-29 Thread Colin Andrews
tried the solution listed in that link, but it doesn't see, to help. I notice that that post is rather old though. Is there a different way to set those module parameters now? Is there a better way to solve this problem now? (other than buying a new nic). Thanks -Colin -- To UNSUBSCRIBE,

Re: Module parameters

2003-01-28 Thread Nicos Gollan
On Tuesday 28 January 2003 17:50, Andrew M. Lindley wrote: > Two questions - how do I find out what parameters a module accepts (which > part of the kernel source if thats where you look)? No need to dig this deep. 'modinfo -p ' prints a list of parameters and descriptions. > And how do you get

Re: Module parameters

2003-01-28 Thread Stephen Gran
This one time, at band camp, Andrew M. Lindley said: > Hello, > > Two questions - how do I find out what parameters a module accepts (which > part of the kernel source if thats where you look)? > > And how do you get a driver to work with 2 network cards (two ne2000:s). > > TIA - Andrew You can

Module parameters

2003-01-28 Thread Andrew M. Lindley
Hello, Two questions - how do I find out what parameters a module accepts (which part of the kernel source if thats where you look)? And how do you get a driver to work with 2 network cards (two ne2000:s). TIA - Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "uns

Re: [Kernel 2.2.10] Figuring out module-parameters

1999-08-02 Thread Peter Ross
On 01-Aug-1999, Jonas Steverud <[EMAIL PROTECTED]> wrote: > > I've just built a 2.2.10 kernel on my own (banging my own chest like > Tarzan[1]) and compiled fat-fs-support as a module (and nls_cp437, > vfat, hpfs, msdos, ...) but modprobe (or whatever reads > /etc/conf.modules) complains when I bo

Re: [Kernel 2.2.10] Figuring out module-parameters

1999-08-01 Thread Patrik Magnusson
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Jonas Steverud) writes: > > I've just built a 2.2.10 kernel on my own (banging my own chest like > Tarzan[1]) and compiled fat-fs-support as a module (and nls_cp437, > vfat, hpfs, msdos, ...) but modprobe (or whatever reads > /etc/conf.mod

How to determine module parameters after insertion?

1999-04-20 Thread Brian Servis
Is there a way to determine what parameters were passed to a kernel module when it was inserted? Maybe some /proc file? As an example if I insert the joy-analog module with 'joy-analog js_an=0x201,0x8f3,0x00' is there anyway after the module is installed to determine that it was passed the optio

Re: changing module parameters

1998-06-25 Thread Mike Schmitz
On Thu, Jun 25, 1998 at 10:50:29AM -0400, Hank Fay wrote: > Mike, > > yup, that works fine, thanks. > > A followup question: the old "wrong parameters" install still shows up > earlier in the boot sequence. Where is that information stored? I'm > half-guessing, being new at this thi

RE: changing module parameters

1998-06-25 Thread Hank Fay
hen I built the system using the install. ??? Hank -Original Message- From: Mike Schmitz [mailto:[EMAIL PROTECTED] Behalf Of Mike Schmitz Sent: Thursday, June 25, 1998 2:20 AM To: 'Debian-User E-mail' Subject: Re: changing module parameters On Thu, Jun 25, 1998 at 01:52:11AM -040

Re: changing module parameters

1998-06-25 Thread Mike Schmitz
On Thu, Jun 25, 1998 at 01:52:11AM -0400, Hank Fay wrote: > Oops -- the info on modules to be loaded was in /etc/modules -- but no info > on the parameters being passed. You want /etc/conf.modules. my ne otions line is: options ne io=0x340 -- Mike Schmitz [EMAIL PROTECTED]ht

RE: changing module parameters

1998-06-25 Thread Hank Fay
Oops -- the info on modules to be loaded was in /etc/modules -- but no info on the parameters being passed. -Original Message- From: Hank Fay [mailto:[EMAIL PROTECTED] Sent: Thursday, June 25, 1998 1:36 AM To: Debian-User (E-mail) Subject: changing module parameters The Debian install

changing module parameters

1998-06-25 Thread Hank Fay
The Debian install (from floppies; CD is in the mail, couldn't wait ) went smoothly; a lot more smoothly than RedHat. The only hitch was that the ethernet was not installed correctly until the second try, and the first try's settings were stuck in some file (Running... says look for an .RC file, b