I have upgraded to 'Current' and now find a problem when I attach my USB Digital camera.

Previous to the upgrade, I had no problem and I used to manually 'mount' the device.

This does not work now and I tracked this down to the 'sd_mod' module not being automatically loaded when Slackware boots. I do not see any 'sda' in '/dev' directory. The only SCSI module which loads is the 'generic' one 'sg' which is no use to me here.

I can get things to work by issuing: '/sbin/modprobe sd_mod' but I would like a neater solution.

I could obviously make an entry in 'rc.modules', but I am certain the way forward is to put a suitable command somewhere in the '/etc/udev/rules.d' directory, but I am not skilled enough to be able to do this myself.

Can anyone help with this please?.

Thanks,

Bill.

Are you sure you're not using a custom kernel?
If memory serves correctly, sd_mod is compiled statically into the official Slackware kernels.

You are quite right - my kernel is 'custom'. The 'sd_mod' is built as a module. I was using essentially the same '.config' that I was using previously (Slackware 12).

I am not sufficiently skilled to understand the changes made to udev scripts which could have led to the module not now being loaded at 'boot'.

So I would still like 'good' solution to loading this module at boot rather than just putting a command in rc.modules.

[bb]Bill.[[/b]

Off the top of my head, I don't have any ideas, but to be honest (and quite frank), that's just not something I'm willing to spend time debugging. That's not to imply that it isn't worth solving or that I don't like you, so please don't take it that way, but support time is better spent (IMHO) on issues that affect Slackware as a whole instead of custom kernels.

That's the purpose of rc.modules, for what it's worth, but I do understand why you want a different solution.

The udev rules are written so many different ways over the different distros so figure out the issue will be like finding a needle in a haystack. I don't use Slackware so can't help much there.

Loading the module in rc.modules is the easiest in my opinion. I load about 8 different non standard modules for mine and other machines.

Brian

In -current, that's largely a non-issue. There's been quite a bit of effort among several different distributions (including Slackware) and the udev maintainers to ship a sane default set of rules with udev. Slackware (and other distros) then add a few distro-specific rules files (for example, 40-slackware.rules) to the udev rules directory. This will be a tremendous help from both a development and user standpoint -- less time and effort from the Slackware end in customizing the setup, and less time and effort on the user end in applying the various documentation out there on the web.

Indeed. Slackware supports an rc.modules.local which, if it's present, overrides the other rc.modules* files. Make sure the top portion of a stock rc.modules file is present in there (the part that (re)generates module dependency information, add your custom modules, and now you don't have to be concerned with redoing the changes after every kernel upgrade.

Many thanks for your comments and advice.

I have made a temporary solution by un-commenting the approriate line in 'rc.modules'.

I didn't know about the possibility of using a 'rc.module.local' file to make upgrades easier. I will do that next.

Bill.