Nope - eject still doesn't work on 2.4.20. I've resorted to rmmod, see my other post.

Rick

--On 15 March 2004 10:12 +0000 Rick Jones <[EMAIL PROTECTED]> wrote:

Something strange going on?

Using eject doesn't seem to accomplish anything. There are no traces in
/var/log/messages, and no re-scanning of the device if inserted
afterwards.

Perhaps it's the kernel I'm using, it's currently 2.4.25 which I compiled
myself (not something I'm practiced at - compiling yes, kernels no!). As
it hasn't actually solved anything I'll go back to the known & stable
2.4.20 and try again.

Rick

--On 14 March 2004 21:03 -0800 Matthew Dharm
<[EMAIL PROTECTED]> wrote:

That's odd...

Even if it gives that error message, it should accomplish the goal.

eject is, primarily, used for removeable media devices.  However, even on
fixed-media it forces the kernel to 'forget' the media parameters (size,
etc.), and forces them to be redetected.

If you eject in between removing and re-inserting, it should forget the
drive size and re-scan when you reattach.

Matt



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to