ioctl call fails with unknown command

hi, when trying to do ioctl call to my driver, i keep getting an error
message: unknown command fd(3). it seems that the ioctl

call is not invoking my driver ioctal method because the debug message
inside my ioctl method never get printed out.
although this may seems like i am using incorrect file descriptor,
since my ioctl method is not even being called, i know i am

using the correct file descriptor because my 'read' method gets
invoked fine.
And using the same code and driver, i was able to get it to work on a
486 target machine but it doesn't seem to work with this

particular linux version.

how can i debug this code? where in the kernel code can i begin to
trace to see what is happening? which file/function gets

called when ioctl function is fisrt called?
(i don't have a debugger and i am not able to gdb the code so i need
to resort to printing out debug messages in the source

code.)

thank you in advance.
.

Relevant Pages

  • Re: Kernel mode to user mode
    ... where they make sense in the context of using IoCtls for data passing also. ... An app passes an IoCtl to a driver initiating a series of tests that will ...
    (microsoft.public.development.device.drivers)
  • [RFC] dev_acpi: device driver for userspace access to ACPI
    ... The basic concept of operation is that the ioctl operates on the ACPI ... The sample, proof-of-concept app, is called acpitree. ... You can find the driver and sample app here: ...
    (Linux-Kernel)
  • Re: Accessing Ndis miniport from user mode application
    ... sticking to WMI, you confine yourself to strictly defined model - there are ... driver can indicate. ... to you - as I told you already, you should go for IOCTL model. ... Accessing custom OIDS through WMI. ...
    (microsoft.public.development.device.drivers)
  • Re: Why is remote system information calling ioctl for my driver?
    ... Changing the key name doesn't keep the System Information ... don't think the ioctl probing was causing the System Information util to fail ... How does it decide that my driver is a serial port ... the SerialPortIndex registry key to decide if the driver should be probed ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Linux read (true i.e. burned in) MAC address
    ... "The reading procedure is different for different vendors...". ... differences among vendors are taken care of by the driver. ... ifconfig, you do a SIOCGIFHWADDR ioctl, no matter who designed the NIC. ... need to care about the card itself or its manufacturer. ...
    (comp.os.linux.networking)