Okay, I'm confused.

Read a thread talking about not being able to get 2.6.9 to do what 2.6.7
did. One complaint was that the card reader wouldn't mount using /dev/sda1,
and that turns out to be my problem as well.

So I took the advice of adding the line:
'none /sys sysfs defaults 0 0' to /etc/fstab, then did 'mount -a'. It
came back and said it was already mounted. So that didn't work.

Removed that line from /etc/fstab.

Then I read a thread that says a scanner needs the usbdevfs mounted, like:
'none /proc/bus/usb usbdevfs devmod=666,auto 0 0'. So I added that and
did 'mount -a'. No response and so I looked at /etc/mtab, and got:

<snip>
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
usbfs /proc/bus/usb usbfs rw 0 0
none /proc/bus/usb usbdevfs rw,devmod=666 0 0

That means I've got /proc/bus/usb now mounted as usbfs and as usbdevfs. I
don't know what now does not work that should, but still no /dev/sda1. That
means that neither of these suggestions did the trick for me.

I'm going to comment out the last line in fstab before going down for the
night, so that things will boot happily tomorrow.

Meanwhile, does anyone have a handle on this business?

Thanks for reading.
--
Email is wtallman at olypen dot com

On Saturday 23 October 2004 8:11 am name wrote:

> Okay, I'm confused.
>
Not sure if this will help but it may give you some pointers.
My system is Slack 10.0
Kernel 2.6.9
udev-035-i486-1 from -current.

> So I took the advice of adding the line:
> 'none /sys sysfs defaults 0 0' to /etc/fstab, then did 'mount -a'. It
> came back and said it was already mounted. So that didn't work.
>
Take a look at /etc/rc.d/rc.S, this mounts it for you.

> devpts /dev/pts devpts rw,gid=5,mode=620 0 0
> usbfs /proc/bus/usb usbfs rw 0 0
> none /proc/bus/usb usbdevfs rw,devmod=666 0 0
>
> That means I've got /proc/bus/usb now mounted as usbfs and as usbdevfs. I
I only have the usbfs line.

> don't know what now does not work that should, but still no /dev/sda1. That
> means that neither of these suggestions did the trick for me.
The way it works here is that as soon as I plug in the USB card reader, the
modules usb_storage and scsi_mod get loaded and udev creates /dev/sda
and /dev/sda1. You can see this happening in /var/log/messages.

Check how you have USB Mass Storage support set in your kernel. Is it a module
or is it built in? If a module, try modprobe usb_storage. Check the same for
scsi device support. Also look through /var/log for any messages.

--
Dave.
dave (at) dhoulden (dot) demon (dot) co (dot) uk

On 2004-10-23, David Houlden <dave@see.my.sig.below> wrote:
> On Saturday 23 October 2004 8:11 am name wrote:
>
>> Okay, I'm confused.
>>
> Not sure if this will help but it may give you some pointers.
> My system is Slack 10.0
> Kernel 2.6.9
> udev-035-i486-1 from -current.

Slack-10.0, 2.6.7 udev-026.

>> So I took the advice of adding the line:
>> 'none /sys sysfs defaults 0 0' to /etc/fstab, then did 'mount -a'. It
>> came back and said it was already mounted. So that didn't work.
>>
> Take a look at /etc/rc.d/rc.S, this mounts it for you.

Indeed. After finding out it was mounted already, that's where I figured
the instruction to be... <grin>

>> devpts /dev/pts devpts rw,gid=5,mode=620 0 0
>> usbfs /proc/bus/usb usbfs rw 0 0
>> none /proc/bus/usb usbdevfs rw,devmod=666 0 0
>>
>> That means I've got /proc/bus/usb now mounted as usbfs and as usbdevfs. I
> I only have the usbfs line.

Okay, confirmation.

>> don't know what now does not work that should, but still no /dev/sda1. That
>> means that neither of these suggestions did the trick for me.
> The way it works here is that as soon as I plug in the USB card reader, the
> modules usb_storage and scsi_mod get loaded and udev creates /dev/sda
> and /dev/sda1. You can see this happening in /var/log/messages.
>
> Check how you have USB Mass Storage support set in your kernel. Is it a module
> or is it built in? If a module, try modprobe usb_storage. Check the same for
> scsi device support. Also look through /var/log for any messages.
>

ARGH!!! I HATE this!!!!

It works just fine today!!! And I've no idea why it didn't yesterday, or
the other times I tried it recently and it didn't work!!!!

Anyway, I checked /var/log/messages, and sure 'nuff: unplugging the card
reader was logged, as was plugging it back in. This time, when I looked in
the /dev directory, /dev/sda and /dev/sda1 were there! And I could mount
sda1, of course. Can't remember now if I actually checked to see if the
files existed before, so don't know (my bad...)

Now, I did unplug and replug the reader each time I tried it before, just to
see if the red light blinked when I plugged it back in. So I didn't do
anything differently this time, at least that I can recognize.

I'm willing to let this business go, with a grumble or two, but it damn well
better work each and every time I use it from now until this distro returns
to dust!!! Or I will be pissed!!!

LOL!!!!!

Now, however, I've a question here: Did you have to upgrade udev when you
got 2.6.9, or does udev-026 work just fine in any case?

In any case, thanks for the response! Guess I'll never know what happened
here... <grin>
--
Email is wtallman at olypen dot com

On Saturday 23 October 2004 7:32 pm name wrote:

> ARGH!!! I HATE this!!!!
>
> It works just fine today!!! And I've no idea why it didn't yesterday, or
> the other times I tried it recently and it didn't work!!!!
Odd, but that's the way of these things sometimes. Maybe the reboot did it.


> Now, however, I've a question here: Did you have to upgrade udev when you
> got 2.6.9, or does udev-026 work just fine in any case?
>
To be honest, I never used udev until a couple of days ago which is why it's
still fresh in my mind. I just decided to get the latest before giving it a
try so never used 026.

> In any case, thanks for the response! Guess I'll never know what happened
> here... <grin>
No problem.

--
Dave.
dave (at) dhoulden (dot) demon (dot) co (dot) uk

On 2004-10-23, David Houlden <dave@see.my.sig.below> wrote:
> On Saturday 23 October 2004 7:32 pm name wrote:
>
>> ARGH!!! I HATE this!!!!
>>
>> It works just fine today!!! And I've no idea why it didn't yesterday, or
>> the other times I tried it recently and it didn't work!!!!
> Odd, but that's the way of these things sometimes. Maybe the reboot did it.
>
>
>> Now, however, I've a question here: Did you have to upgrade udev when you
>> got 2.6.9, or does udev-026 work just fine in any case?
>>
> To be honest, I never used udev until a couple of days ago which is why it's
> still fresh in my mind. I just decided to get the latest before giving it a
> try so never used 026.
>
>> In any case, thanks for the response! Guess I'll never know what happened
>> here... <grin>
> No problem.

Well, I guess I should learn to read every thread that sounds even close to
relevant... <sigh>. There was a recent thread on upgrading to 2.6.9, in
which someone asserted that udev should be upgraded as well. To be fair,
though, 2.6.7 was(is?) an option for Slack10, and since Pat uses vanilla
kernels, the one I have (from kernel.org) should work fine with the included
udev.

So, for the benefit of anyone reading this particular thread: upgrade your
kernel, upgrade udev as well, or so others have said.

Thanks again...
--
Email is wtallman at olypen dot com