Ok, after checking the entire forum, FAQS and stuff, I have done what I can
to avoid a repeat bug report. Interestingly, I searched for an email to
submit bugs to, but the info was ambiguous. I could not tell if they wanted
web page bugs or slackware bugs.

Version 10.2, using Sata.i kernel.
I have two DVD/CD Writers.
Two Sata Drives with XP NTFS for XP on same EIDE cable.
One EIDE drive as Master on the secondary EIDE port with the Slackware
loaded on this drive = /dev/hdc1.

Floppy is fat32.

Intel D865_Perl with latest bios.

1. Bios does not see the /dev/hdc as a boot option but this might be bios
problem.

2. Floppy and CD Drives do not sense when a disk is changed. LS shows the
same content as the disk that was there beforehand. I've gotten it to
finally read the real content, but only after fiddling about so long that I
forget how I got it to re-read.

This fake image persists between booting! I can put in a disk or CD in
today, Turn off the machine turn it back on and goto /mnt/cdrom or /mnt/fd0
with the DVD and floppy drives empty or with different media in the drives
and see the file names for media that I put in yesterday!

Sometimes accessing the drive while empty fixes it.

Files copied to the floppy do not actually go onto the floppy (The light
does not come on), but Slack thinks the file is there if I use cp.

If I use KDE to do my copying and accessing, usually things work ok, but
I've seen the KDE fail to sense a disk change too. This does not occur in
XP.

One stupid question, I did my research, but its amazing how much fossilized
documentation is out there on sites that are supposed to have only the
latest. ....

When making Device Links on KDE I have choices of choosing a CD, DVD, a CD
Writer but no DVD writer. I think the question might be moot, since when I
choose CDRom I can write to it, so I bet I can also work with DVD's too, and
that what I call it does not matter, but the device name I give it and what
I put in the fstab and mtab do matter.

Flames welcome, I know I hate reading newbie questions myself, but its been
ages since I've done Linux. Microslop shops are busy sweatshops sometimes.
Left me burned out for awhile
--
To reply to this message take off the .NoJunkSpam off of the end of
garryfre@pacbell.net.NoJunkSpam

Garry Freemyer wrote:
> Ok, after checking the entire forum, FAQS and stuff, I have done what I can
> to avoid a repeat bug report. Interestingly, I searched for an email to
> submit bugs to, but the info was ambiguous. I could not tell if they wanted
> web page bugs or slackware bugs.

They are for slackware bugs AFAIK

> Version 10.2, using Sata.i kernel.
> I have two DVD/CD Writers.
> Two Sata Drives with XP NTFS for XP on same EIDE cable.
> One EIDE drive as Master on the secondary EIDE port with the Slackware
> loaded on this drive = /dev/hdc1.
>
> Floppy is fat32.
>
> Intel D865_Perl with latest bios.
>
> 1. Bios does not see the /dev/hdc as a boot option but this might be bios
> problem.

What do you mean by this? Do you mean when you select /dev/hdc as boot
device it does not boot off of it? Or do you mean you cannot select
/dev/hdc as a device to boot off?

> 2. Floppy and CD Drives do not sense when a disk is changed. LS shows the
> same content as the disk that was there beforehand. I've gotten it to
> finally read the real content, but only after fiddling about so long that I
> forget how I got it to re-read.

Are you using mount/unmount or an automounter?

> This fake image persists between booting! I can put in a disk or CD in
> today, Turn off the machine turn it back on and goto /mnt/cdrom or /mnt/fd0
> with the DVD and floppy drives empty or with different media in the drives
> and see the file names for media that I put in yesterday!

What programs are you using to read the directories?

> Sometimes accessing the drive while empty fixes it.
>
> Files copied to the floppy do not actually go onto the floppy (The light
> does not come on), but Slack thinks the file is there if I use cp.
>
> If I use KDE to do my copying and accessing, usually things work ok, but
> I've seen the KDE fail to sense a disk change too. This does not occur in
> XP.

So it is not a hardware problem it is a software problem.

> When making Device Links on KDE I have choices of choosing a CD, DVD, a CD
> Writer but no DVD writer. I think the question might be moot, since when I
> choose CDRom I can write to it, so I bet I can also work with DVD's too, and
> that what I call it does not matter, but the device name I give it and what
> I put in the fstab and mtab do matter.

I don't think the Device type DVD/CD-ROM has any real effect in KDE,
they just appear to be different Icons.

> Flames welcome, I know I hate reading newbie questions myself, but its been
> ages since I've done Linux. Microslop shops are busy sweatshops sometimes.
> Left me burned out for awhile

____ __
{ --.\ | .)%%%)%%
'-._\\ | (\___ %)%%(%%(%%%
`\\|{/ ^ _)-%(%%%%)%%;%%%
.'^^^^^^^ /` %%)%%%%)%%%'
jgs //\ ) , / '%%%%(%%'
, _.'/ `\<-- \<
`^^^` ^^ ^^

Your flames as requested.

Richard

Garry Freemyer wrote:
> Ok, after checking the entire forum, FAQS and stuff, I have done what I can
> to avoid a repeat bug report. Interestingly, I searched for an email to
> submit bugs to, but the info was ambiguous. I could not tell if they wanted
> web page bugs or slackware bugs.
>
> Version 10.2, using Sata.i kernel.
> I have two DVD/CD Writers.
> Two Sata Drives with XP NTFS for XP on same EIDE cable.
> One EIDE drive as Master on the secondary EIDE port with the Slackware
> loaded on this drive = /dev/hdc1.
>
> Floppy is fat32.
>
> Intel D865_Perl with latest bios.
>
> 1. Bios does not see the /dev/hdc as a boot option but this might be bios
> problem.
>
> 2. Floppy and CD Drives do not sense when a disk is changed. LS shows the
> same content as the disk that was there beforehand.

I think your problem boils down to some issue
with the dbus/hotplug/udev/hal mess.

If you can get supermount to work on your kernel
you can dont need the above mess.



--
Software is not manufactured, it is something you write and publish.
Keep Europe free from software patents, we do not want censorship
by patent law on written works.

On 2005-11-26, Garry Freemyer <garryfre@pacbell.net> wrote:
<snip>

> 2. Floppy and CD Drives do not sense when a disk is changed. LS shows the
> same content as the disk that was there beforehand. I've gotten it to
> finally read the real content, but only after fiddling about so long that I
> forget how I got it to re-read.
>

I'm not sure what you mena by "sense". Are you mounting/unmounting the disks?
Slackware does not have autorun... by default

> This fake image persists between booting! I can put in a disk or CD in
> today, Turn off the machine turn it back on and goto /mnt/cdrom or /mnt/fd0
> with the DVD and floppy drives empty or with different media in the drives
> and see the file names for media that I put in yesterday!
>

This is pretty weird. I've never had something stay mounted in /mnt/cdrom
between reboots.

> Sometimes accessing the drive while empty fixes it.
>
> Files copied to the floppy do not actually go onto the floppy (The light
> does not come on), but Slack thinks the file is there if I use cp.
>

I believe this has something to do with how floppies work. Information is not
immediatly written to the disk. It is written right before it is unmounted IIRC
I think there is a way to specify when to write data in the mount command.

> If I use KDE to do my copying and accessing, usually things work ok, but
> I've seen the KDE fail to sense a disk change too. This does not occur in
> XP.
>

KDE probably has some wiz-bang automagical utilities.

> One stupid question, I did my research, but its amazing how much fossilized
> documentation is out there on sites that are supposed to have only the
> latest. ....
>

I'd imagine that most floppy information is "fossilized" as most people
consider floppies the same. Alot of new computers don't even come with floppy
drives anymore.

> When making Device Links on KDE I have choices of choosing a CD, DVD, a CD
> Writer but no DVD writer. I think the question might be moot, since when I
> choose CDRom I can write to it, so I bet I can also work with DVD's too, and
> that what I call it does not matter, but the device name I give it and what
> I put in the fstab and mtab do matter.
>

I have never used KDE to make device links. It's easy enough to do without a
gui. have a look in dmesg for your device. You should already have a /dev node
for the device. After you find out what the node is, open /etc/fstab, and add
the info for the device.
My dvd burner is this in fstab
/dev/hdc /mnt/dvdr udf,iso9660 noauto,ro,user 0 0

> Flames welcome, I know I hate reading newbie questions myself, but its been
> ages since I've done Linux. Microslop shops are busy sweatshops sometimes.
> Left me burned out for awhile

No need for flames

--
Best Regards,

Mike Reynolds

MikeReynolds <mreynolds@invalid.com> wrote:
: On 2005-11-26, Garry Freemyer <garryfre@pacbell.net> wrote:
: > This fake image persists between booting! I can put in a disk or CD in
: > today, Turn off the machine turn it back on and goto /mnt/cdrom or /mnt/fd0
: > with the DVD and floppy drives empty or with different media in the drives
: > and see the file names for media that I put in yesterday!
: >

: This is pretty weird. I've never had something stay mounted in /mnt/cdrom
: between reboots.

Not so wierd actually. I bet you the problem is that the original poster is
not properly using mount/umount. So at one point, he probably did cp blah
/mnt/fd0 when there was no device mounted to that mount point. This will
copy the files over to that portion of the hard drive. There's nothing
special about /mnt from the filesystem standpoint, it's just a normal
directory. So cp would chug along happily copying files over just like it
would if you gave it any writeable directory as the destination. The way
the OP could confirmi that this is the case is to boot up with no CDs or
floppies in the drive and see if there is content in /mnt. If there is, then
the OP used cp/mv/etc when there was no media mounted.

So to the OP, please read the documentation on mount and umount. Make sure
you are properly using those commands for your removable media devices. This
sounds more like a user bug than an OS bug with the information given so far.

On 2005-11-27, Melissa Danforth <danforth@pc60.cs.ucdavis.edu> wrote:
> MikeReynolds <mreynolds@invalid.com> wrote:
>: On 2005-11-26, Garry Freemyer <garryfre@pacbell.net> wrote:
>: > This fake image persists between booting! I can put in a disk or CD in
>: > today, Turn off the machine turn it back on and goto /mnt/cdrom or /mnt/fd0
>: > with the DVD and floppy drives empty or with different media in the drives
>: > and see the file names for media that I put in yesterday!
>: >
>
>: This is pretty weird. I've never had something stay mounted in /mnt/cdrom
>: between reboots.
>
> Not so wierd actually. I bet you the problem is that the original poster is
> not properly using mount/umount. So at one point, he probably did cp blah
> /mnt/fd0 when there was no device mounted to that mount point. This will
> copy the files over to that portion of the hard drive. There's nothing
> special about /mnt from the filesystem standpoint, it's just a normal
> directory. So cp would chug along happily copying files over just like it
> would if you gave it any writeable directory as the destination. The way
> the OP could confirmi that this is the case is to boot up with no CDs or
> floppies in the drive and see if there is content in /mnt. If there is, then
> the OP used cp/mv/etc when there was no media mounted.
>
<snip>

Hmmm I bet your right. I didn't think of that.

--
Best Regards,

Mike Reynolds

"richard" <c@dog.bird.eu> wrote in message
news:l5nn53-6al.ln1@orion.techdrive.foo...
> Garry Freemyer wrote:
>> Ok, after checking the entire forum, FAQS and stuff, I have done what I
>> can to avoid a repeat bug report. Interestingly, I searched for an email
>> to submit bugs to, but the info was ambiguous. I could not tell if they
>> wanted web page bugs or slackware bugs.
>
> They are for slackware bugs AFAIK
>
>> Version 10.2, using Sata.i kernel.
>> I have two DVD/CD Writers.
>> Two Sata Drives with XP NTFS for XP on same EIDE cable.
>> One EIDE drive as Master on the secondary EIDE port with the Slackware
>> loaded on this drive = /dev/hdc1.
>>
>> Floppy is fat32.
>>
>> Intel D865_Perl with latest bios.
>>
>> 1. Bios does not see the /dev/hdc as a boot option but this might be bios
>> problem.
>
> What do you mean by this? Do you mean when you select /dev/hdc as boot
> device it does not boot off of it? Or do you mean you cannot select
> /dev/hdc as a device to boot off?

I mean that the drive does not show up in CMOS Setup as a bootable drive. I
can mount /dev/hdc1 via lilo off a floppy or off itself via NTLoader just
fine.

>
>> 2. Floppy and CD Drives do not sense when a disk is changed. LS shows the
>> same content as the disk that was there beforehand. I've gotten it to
>> finally read the real content, but only after fiddling about so long that
>> I forget how I got it to re-read.
>
> Are you using mount/unmount or an automounter?

I tried these, I get can't unmount error. I'm looking into an auto mounter.

>
>> This fake image persists between booting! I can put in a disk or CD in
>> today, Turn off the machine turn it back on and goto /mnt/cdrom or
>> /mnt/fd0 with the DVD and floppy drives empty or with different media in
>> the drives and see the file names for media that I put in yesterday!
>
> What programs are you using to read the directories?
>

Command line slackware file listing commands like ls and Dir.

>> Sometimes accessing the drive while empty fixes it.
>>
>> Files copied to the floppy do not actually go onto the floppy (The light
>> does not come on), but Slack thinks the file is there if I use cp.
>>
>> If I use KDE to do my copying and accessing, usually things work ok, but
>> I've seen the KDE fail to sense a disk change too. This does not occur in
>> XP.
>
> So it is not a hardware problem it is a software problem.

Yes.

>
>> When making Device Links on KDE I have choices of choosing a CD, DVD, a
>> CD Writer but no DVD writer. I think the question might be moot, since
>> when I choose CDRom I can write to it, so I bet I can also work with
>> DVD's too, and that what I call it does not matter, but the device name I
>> give it and what I put in the fstab and mtab do matter.
>
> I don't think the Device type DVD/CD-ROM has any real effect in KDE, they
> just appear to be different Icons.

Exactly what I was thinking. Better worded too.
>
>> Flames welcome, I know I hate reading newbie questions myself, but its
>> been ages since I've done Linux. Microslop shops are busy sweatshops
>> sometimes. Left me burned out for awhile
>
> ____ __
> { --.\ | .)%%%)%%
> '-._\\ | (\___ %)%%(%%(%%%
> `\\|{/ ^ _)-%(%%%%)%%;%%%
> .'^^^^^^^ /` %%)%%%%)%%%'
> jgs //\ ) , / '%%%%(%%'
> , _.'/ `\<-- \<
> `^^^` ^^ ^^
>
> Your flames as requested.
>
> Richard
>
>

As I said before, I did read the manual.

The floppy will NOT unmount as I mentioned before.

I note that the /dev/mnt/floppy directory was empty before putting in a
floppy, that was also empty. I copied the stuff to that directory and then
tried /umount /dev/fd0 and got a message that this device was not
unmountable.

Nothing was using it, no links to it existed.

"Melissa Danforth" <danforth@pc60.cs.ucdavis.edu> wrote in message
news:dmd7s5$gjr$1@skeeter.ucdavis.edu...
> MikeReynolds <mreynolds@invalid.com> wrote:
> : On 2005-11-26, Garry Freemyer <garryfre@pacbell.net> wrote:
> : > This fake image persists between booting! I can put in a disk or CD in
> : > today, Turn off the machine turn it back on and goto /mnt/cdrom or
> /mnt/fd0
> : > with the DVD and floppy drives empty or with different media in the
> drives
> : > and see the file names for media that I put in yesterday!
> : >
>
> : This is pretty weird. I've never had something stay mounted in
> /mnt/cdrom
> : between reboots.
>
> Not so wierd actually. I bet you the problem is that the original poster
> is
> not properly using mount/umount. So at one point, he probably did cp blah
> /mnt/fd0 when there was no device mounted to that mount point. This will
> copy the files over to that portion of the hard drive. There's nothing
> special about /mnt from the filesystem standpoint, it's just a normal
> directory. So cp would chug along happily copying files over just like it
> would if you gave it any writeable directory as the destination. The way
> the OP could confirmi that this is the case is to boot up with no CDs or
> floppies in the drive and see if there is content in /mnt. If there is,
> then
> the OP used cp/mv/etc when there was no media mounted.
>
> So to the OP, please read the documentation on mount and umount. Make sure
> you are properly using those commands for your removable media devices.
> This
> sounds more like a user bug than an OS bug with the information given so
> far.

On Mon, 28 Nov 2005 05:19:48 GMT, "Garry Freemyer" <garryfre@pacbell.net> wrote:

>As I said before, I did read the manual.
>
>The floppy will NOT unmount as I mentioned before.
>
>I note that the /dev/mnt/floppy directory was empty before putting in a
>floppy, that was also empty. I copied the stuff to that directory and then
>tried /umount /dev/fd0 and got a message that this device was not
>unmountable.

You appear to be confusing device nodes with mountpoints, also,
you confuse SATA with PATA in OP: "2 Sata ... on same EIDE cable"

Grant.

Pata? I never said pata. I use Sata. If I typed Pata it was by mistake and
not intentional. I've never even heard of Pata, but I imagine it tastes
pretty good on tortillas.

device node?!?

"Grant" <g_r_a_n_t_@dodo.com.au> wrote in message
news:rn6lo1p7tmuq5a2h7hm5ig07mq9o7ct2nk@4ax.com...
> On Mon, 28 Nov 2005 05:19:48 GMT, "Garry Freemyer" <garryfre@pacbell.net>
> wrote:
>
>>As I said before, I did read the manual.
>>
>>The floppy will NOT unmount as I mentioned before.
>>
>>I note that the /dev/mnt/floppy directory was empty before putting in a
>>floppy, that was also empty. I copied the stuff to that directory and then
>>tried /umount /dev/fd0 and got a message that this device was not
>>unmountable.
>
> You appear to be confusing device nodes with mountpoints, also,
> you confuse SATA with PATA in OP: "2 Sata ... on same EIDE cable"
>
> Grant.