My D LINK 24 port switch contains GBIC module. My Switch is perfectly ok withour GIBIC but when I am connecting or try to communicate through GIBIC its showing packet loss. And sometimes not working also. I am unable find out where is the problem. Its card problem ot module problem? Please suggest how to identify and how to troubleshoot so that my Switch can work.

The Cisco switch will probably err-disable the port when you plug it in. The workaround is to add these commands:
Switch(config)#service unsupported-transciever
Switch(config)#no errdisable detect cause gbic-invalid
It'll either work or it won't!

The 'combo' ports can be ethernet or GBIC, not both. While the ports do provide flexibility for interconnects, they do cause some confusion when this comes up. If you need more ports, some Cisco switches do support 'stacking', where they can be interconnected via their StackWise ports located on the back. These switches work together and act like a single switch. Configuration is generally easy, with one switch being marked as 'master', generally the switch that has the uplink to the rest of the network.

try to check ur cable type

For mini-GBIC ports you have to set the media type under the interface settings

if you want to use fiber, set the meida type as fiber and for copper media type as rj45

https://www.manualslib.com/manual/529834/Allied-Telesis-At-8012m.html?page=45#manual

switch the fibre rx and tx around on one side of the link

It does not have to be port 24 to port 24 - You just need to make sure that whatever port you use is configured the same way as port 24 - Example: Log into switch #2 and set port 23 with the same attributes as port 24. Also log into you new switch and make sure port 23 (or 24) is configured the same as those on switch #2. You can the cleanly go from switch #1 - port 24 to switch #2 - port 23 AND switch #2 port 24 to switch #3 port 23 - If you also configure switch #3 port 24 like the others you'll be ready for any additional expansion

If you have device A connected to device B over a Gigabit link, and the link does not come up, perform this procedure.
Step-by-Step Procedure
1. Verify device A and B use the same GBIC, short wavelength (SX), long wavelength (LX), long haul (LH), extended wavelength (ZX), or copper UTP (TX). Both devices must use the same type of GBIC to establish link. An SX GBIC needs to connect with an SX GBIC. An SX GBIC does not link with an LX GBIC.

2. Verify distance and cable used per GBIC as defined by Cisco.

3. If either device has multiple Gigabit ports, connect the ports to each other. This tests each device and verifies that the Gigabit interface functions correctly. For example, you have a switch that has two Gigabit ports. Wire Gigabit port one to Gigabit port two. Does the link come up? If so, the port is good. STP blocks on the port and prevents any loops (port one receive (RX) goes to port two transmit (TX), and port one TX goes to port two RX).

4. If single connection or Step 3 fails with SC connectors, loop the port back to itself (port one RX goes to port one TX). Does the port come up? If not, contact the Cisco TAC, as this can be a faulty port.

5. If steps 3 and 4 are successful, but a connection between device A and B cannot be established, loop ports with the cable that adjoins the two devices. Verify that there is not a faulty cable.

6. Verify that each device supports 802.3z specification for Gigabit auto-negotiation. Gigabit Ethernet has an auto-negotiation procedure that is more extensive than the one used for 10/100 Ethernet (Gigabit auto-negotiation spec: IEEE Std 802.3z-1998). When you enable link negotiation, the system auto-negotiates flow control, duplex mode, and remote fault information. You must either enable or disable link negotiation on both ends of the link. Both ends of the link must be set to the same value or the link cannot connect. Problems have been seen when you connect to devices manufactured before the IEEE 802.3z standard was ratified. If either device does not support Gigabit auto-negotiation, disable the Gigabit auto-negotiation, and it forces the link up. Warning: Disabling auto-negotiation hides link drops or physical layer problems. Disabling auto-negotiation is only required if end-devices such as older Gigabit NICs are used which cannot support IEEE 802.3z. Do not disable auto-negotiation between switches unless absolutely required to do so, as physical layer problems can go undetected, which results in STP loops. The alternative is to contact the vendor for software/hardware upgrade for IEEE 802.3z Gigabit auto-negotiation support

Hi from the command line interface you will need to login and then type enable (enter) configure (enter), interface fast ethernet all (enter), no shutdown port (port #). Here is a link to the CLI manual if you need more help: http://www116.nortel.com/docs/bvdoc/baystack/doc_pdf/217152-A_CLI_Guide_for_Ethernet_Switch_325-425_Release_3.5.pdf Let me know how it goes or if you need more help. Regards