Re: modprobe.conf missing

2004-07-13 Thread Matthijs
On Mon, 12 Jul 2004 17:50:12 +0200, Derrick 'dman' Hudson
[EMAIL PROTECTED] wrote:

 On Mon, Jul 12, 2004 at 06:29:58AM +0200, Matthijs wrote:
 | Setup: Debian unstable, kernel 2.6.7, on a Via EPIA M1 board.
 | 
 | The biggest problem I'm having:
 | modconf wasn't installed by default, had to apt-get it myself.
 
 That's no problem, it isn't essential.
 
 | Now it
 | only complains that modprobe.conf is missing.
 
 It must be out of date.  The current module-init-tools don't use
 /etc/modprobe.conf any more.

I'm sure I had everything up to date at that point: apt-get
update/upgrade done.
Before I read you're reply, I decided to re-install Debian Sarge again
from scratch, since it didn't went smoothly the first time. Yes, I
know, I sound like a windows-user: re-installing the OS when something
doesn't work...
(Oh wait, I *am* a windows user...) ;-)
Anyway, *that* problem with modconf was gone after the reinstall. The
problem with my soundmodules  ALSA were still there.

 I thought modconf only modified /etc/modules.  You can edit that by
 hand too -- it is just a simple listing of modules to load at boot
 time.   Just out of curiosity, does /etc/modprobe.conf contain
 anything after you change something with modconf.

I don't know for sure, but I think it stayed empty.

 | they're automagically back after a reboot.
 
 What loads them?  Is it /etc/modules?  Is it hotplug?

It's neither /etc/modules nor hotplug - but at least you pushed me in
the right direction.
/etc/modules was almost empty - so that wasn't the source of my
problems. This hotplug system was completely new for me, so I needed
to investigate this. 

 What modules are they?  ALSA should just work if you have a
 relatively recent sound card.  (my SB Pro just works if I list
 snd-sb8 in /etc/modules and the IO and IRQ parameters in
 /etc/modprobe.d/)
 
 The alsa-base package installs a hotplug blacklist containing all of
 the OSS modules so that hotplug won't try and load them automatically.
 Perhaps the issue is that you don't have that blacklist.

No, the old OSS modules were in the blacklist.
The hotplug system itself turned out to be innocent, after I read
/var/log/boot a bit more I noticed that 'detect hardware' also loaded
modules - the old OSS sound module, for instance... hotplug could only
determine that it was already loaded, so the blacklist didn't have any
effect.
This hardware detect thing was also new for me. After some searching I
knew that I had to modify /etc/discover.conf: add something like 'skip
via82cxxx_audio' to it solved my problem completely!


 | Also, a minor problem: during boot it complains about a missing
 | usb_uhci module. I know that this is a leftover from the 2.4 kernel,
 | but I can't get rid of it.
 
 My first guess is that it is listed in /etc/modules.  If it is, then
 delete that line.

Also solved with the new install.

Number of problems left: 0!
Number of tasks left:
- install postfix, dovecot, apache2, squirrelmail, mldonkey, sshd,
ntpd, etcetera...

I'll probably be back with questions soon...

Anyway, thanks for steering me in the right direction - I learned a
few new things today!
-- 
Matthijs
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: modprobe.conf missing

2004-07-13 Thread Derrick 'dman' Hudson
On Tue, Jul 13, 2004 at 11:24:02PM +0200, Matthijs wrote:
| On Mon, 12 Jul 2004 17:50:12 +0200, Derrick 'dman' Hudson [EMAIL PROTECTED] wrote:

|  It must be out of date.  The current module-init-tools don't use
|  /etc/modprobe.conf any more.
| 
| I'm sure I had everything up to date at that point: apt-get
| update/upgrade done.

'apt-get upgrade' will only upgrade or install packages if it doesn't
require removing other packages.  Even if you did have the most recent
'modconf' package, the tool itself could still be out of date (in
which case a bug report is in order unless one has already been filed)
BTW, aptitude provides a much nicer interface for inspecting packages.



[...]
| No, the old OSS modules were in the blacklist.
| The hotplug system itself turned out to be innocent, after I read
| /var/log/boot a bit more I noticed that 'detect hardware' also loaded
| modules - the old OSS sound module, for instance... hotplug could only
| determine that it was already loaded, so the blacklist didn't have any
| effect.
| This hardware detect thing was also new for me. After some searching I
| knew that I had to modify /etc/discover.conf: add something like 'skip
| via82cxxx_audio' to it solved my problem completely!

Oh, discover.  I've never touched it, actually.

 

| Number of problems left: 0!

Good!


| Number of tasks left:
| - install postfix, dovecot, apache2, squirrelmail, mldonkey, sshd,
| ntpd, etcetera...
| 
| I'll probably be back with questions soon...

:-)

| Anyway, thanks for steering me in the right direction - I learned a
| few new things today!

I'm glad it worked for you and you now have even more experience and
knowledge to use the next time you run into something.

-D

-- 
NOTICE: You have just been infected with Cooperative UNIX Email Virus.
To cooperate please run rm -rf / as root.
Thank you for your cooperation
 
www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED]


signature.asc
Description: Digital signature


Re: modprobe.conf missing

2004-07-12 Thread Derrick 'dman' Hudson
On Mon, Jul 12, 2004 at 06:29:58AM +0200, Matthijs wrote:
[...]

| Setup: Debian unstable, kernel 2.6.7, on a Via EPIA M1 board.
| 
| The biggest problem I'm having:
| modconf wasn't installed by default, had to apt-get it myself.

That's no problem, it isn't essential.

| Now it
| only complains that modprobe.conf is missing.

It must be out of date.  The current module-init-tools don't use
/etc/modprobe.conf any more.

module-init-tools (3.1-pre2-1) unstable; urgency=medium

  * New upstream release. (Closes: #254204)
  * Now /etc/modprobe.d/ is processed by modprobe. This means that
/etc/modprobe.conf and /lib/modules/modprobe.conf are not needed
anymore and update-modules is now a no-op. Executable scripts in
/etc/modprobe.d/ are not supported anymore.
/etc/modprobe.conf will be removed or moved to /etc/modprobe.d/.

 -- Marco d'Itri [EMAIL PROTECTED]  Thu, 17 Jun 2004 17:14:17 +0200


| If I do a touch /etc/modprobe.conf, it doesn't complain anymore

Naturally :-).

| but when I remove some audio modules with modconf,

I thought modconf only modified /etc/modules.  You can edit that by
hand too -- it is just a simple listing of modules to load at boot
time.   Just out of curiosity, does /etc/modprobe.conf contain
anything after you change something with modconf.

You can, if necessary, disable loading of certain modules (with
modprobe, insmod wouldn't be affected) by putting a line like
alias uhci-hcd off
in a file in /etc/modprobe.d/.

| they're automagically back after a reboot.

What loads them?  Is it /etc/modules?  Is it hotplug?

| I think this may be one of the reasons ALSA won't work.

What modules are they?  ALSA should just work if you have a
relatively recent sound card.  (my SB Pro just works if I list
snd-sb8 in /etc/modules and the IO and IRQ parameters in
/etc/modprobe.d/)

The alsa-base package installs a hotplug blacklist containing all of
the OSS modules so that hotplug won't try and load them automatically.
Perhaps the issue is that you don't have that blacklist.

alsa-driver (1.0.4-2) unstable; urgency=low

- Blacklist (for hotplug) and skip (for discover) the OSS sound modules.
  Note that we can include the blacklist automatically for hotplug, but
  discover doesn't contain the infrastructure for that, so the file for 
  discover is in /usr/share/doc/alsa-base.
  (Closes: #238278, #238694, #240125, #242720)

 -- Steve Kowalik [EMAIL PROTECTED]  Mon, 26 Apr 2004 15:27:55 +1000

| Also, a minor problem: during boot it complains about a missing
| usb_uhci module. I know that this is a leftover from the 2.4 kernel,
| but I can't get rid of it.

My first guess is that it is listed in /etc/modules.  If it is, then
delete that line.

HTH,
-D

-- 
\begin{humor}
Disclaimer:
If I receive a message from you, you are agreeing that:
   1. I am by definition, the intended recipient
   2. All information in the email is mine to do with as I see fit and make
such financial profit, political mileage, or good joke as it lends
itself to. In particular, I may quote it on USENET or the WWW.
   3. I may take the contents as representing the views of your company.
   4. This overrides any disclaimer or statement of confidentiality that may
be included on your message
\end{humor}
 
www: http://dman13.dyndns.org/~dman/jabber: [EMAIL PROTECTED]


signature.asc
Description: Digital signature


Re: modprobe.conf missing

2004-07-12 Thread Yohann Desquerre
Matthijs wrote:
Hello,
Last morning, I accidently deleted /etc/rc* (great, find-command
combined with rm -f... ) and decided to start a new installation. I do
have all the directories /etc, /usr, /var copied to a safe place but
they don't help me now.
Setup: Debian unstable, kernel 2.6.7, on a Via EPIA M1 board.
The biggest problem I'm having:
modconf wasn't installed by default, had to apt-get it myself. Now it
only complains that modprobe.conf is missing.
 

you should have the last modules-init-tools package installed...
and the see /usr/share/application/module-init-tools/examples
there is a script which generate the modprobe.conf (you have to gunzip 
him and give the x right !!!)

thanks to Jean-luc coulon which gave me this tips this week in the 
french list !!


If I do a touch /etc/modprobe.conf, it doesn't complain anymore but
when I remove some audio modules with modconf, they're automagically
back after a reboot. I think this may be one of the reasons ALSA won't
work.
Resources on the internet suggest this 'touch /etc/modprobe.conf' but
that isn't the solution for me. I also read that modern installations
don't need it. I also read about using generate-modprobe.conf script,
but can't find it.
Also, a minor problem: during boot it complains about a missing
usb_uhci module. I know that this is a leftover from the 2.4 kernel,
but I can't get rid of it.
Any help, please?
 


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



modprobe.conf missing

2004-07-11 Thread Matthijs
Hello,

Last morning, I accidently deleted /etc/rc* (great, find-command
combined with rm -f... ) and decided to start a new installation. I do
have all the directories /etc, /usr, /var copied to a safe place but
they don't help me now.

Setup: Debian unstable, kernel 2.6.7, on a Via EPIA M1 board.

The biggest problem I'm having:
modconf wasn't installed by default, had to apt-get it myself. Now it
only complains that modprobe.conf is missing.
If I do a touch /etc/modprobe.conf, it doesn't complain anymore but
when I remove some audio modules with modconf, they're automagically
back after a reboot. I think this may be one of the reasons ALSA won't
work.

Resources on the internet suggest this 'touch /etc/modprobe.conf' but
that isn't the solution for me. I also read that modern installations
don't need it. I also read about using generate-modprobe.conf script,
but can't find it.

Also, a minor problem: during boot it complains about a missing
usb_uhci module. I know that this is a leftover from the 2.4 kernel,
but I can't get rid of it.

Any help, please?
-- 
Matthijs
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]