Sponsored Content
Full Discussion: Supporting NIC speed
Operating Systems Solaris Supporting NIC speed Post 302741103 by solaris_1977 on Friday 7th of December 2012 11:44:32 AM
Old 12-07-2012
Thanks Jim for the reply.
I edited my question. Sorry for the confusion. Actully I wanted to check speed of consoles, which are sc, rsc, ilom.
 

10 More Discussions You Might Find Interesting

1. Solaris

How to check Virtual NIC card speed on solaris

Hi, We have a 4 port Sun gigaswift NIC card on our sun fire server. If the card is a physical one I know how to check the settings/speed. But since this is a virtual card with 4 ports , I am not sure as how we can check the settings. Details ----------- root:/> ifconfig -a lo0:... (3 Replies)
Discussion started by: pray44u
3 Replies

2. Solaris

Sun box's NIC speed setting

Is there a way to check if my Sun box's network interface card is set to 10 or 100 Mbps? Thanks! (1 Reply)
Discussion started by: FredSmith
1 Replies

3. IP Networking

NIC speed 100M/full duplex problem

I have a TOSHIBA AS7000 B150 Sun Box I wanted to run it with 100M/full duplex I had added this to the /etc/system file to make to setting permenant So it would be set correctly on reboot. set eri:eri_adv_100fdx_cap=1 set eri:eri_adv_100hdx_cap=0 set eri:eri_adv_autoneg_cap=0 But when I... (4 Replies)
Discussion started by: AirWalker83
4 Replies

4. Filesystems, Disks and Memory

data from blktrace: read speed V.S. write speed

I analysed disk performance with blktrace and get some data: read: 8,3 4 2141 2.882115217 3342 Q R 195732187 + 32 8,3 4 2142 2.882116411 3342 G R 195732187 + 32 8,3 4 2144 2.882117647 3342 I R 195732187 + 32 8,3 4 2145 ... (1 Reply)
Discussion started by: W.C.C
1 Replies

5. Linux

changing speed of NIC Card in linux

Hi, I would like to know how to change the speed of ethernet card in linux? as it is showing auto-neg using mii-tool -v eth0 and my requirement is 100mbps full duplex. Regards, Manoj (3 Replies)
Discussion started by: manoj.solaris
3 Replies

6. Solaris

change NIC speed

how can we change the nic card speed please explain through commands & steps ???? and i want to change NIC speed 100 --1000Mbps and what is full & half duplex gives thanks in advance (6 Replies)
Discussion started by: wkbn86
6 Replies

7. UNIX for Advanced & Expert Users

Determine the ethernet (NIC) card speed.

Hi, Does anyone know how can I determine the maximum capable speed on a network interface card for different OS like HP, Sun, AIX and Linux. I am aware of the tool "ethtool" which can be used for Linux. Are there any handly commands or /proc files where I can get this info depending on the OS.... (3 Replies)
Discussion started by: devtakh
3 Replies

8. Solaris

x86 Solaris 10 nic driver added but not attached. NIC is not detected.

I couldn't install my nic in solaris 10. I compiled and added the driver but failed to attach the driver and ifconfig output shows only loopback dev. Please see the following output and tell me whether my nic has been detected and why the driver failed to attach? My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies

9. Red Hat

I want to tune NIC's rps, rfs and xps value. which NIC device should I modify.

Dear All I want tune my NIC's rps, rfs and xps value. In my system I have two NIC (eth0, eth1) and I have a bond0 ( eth0, eth1). Here is the question? Which device should I modify ? eth0 and eth1? or just modify bond0 or modify all device (eth0, eth1, bond0) Any advice is welcome.... (0 Replies)
Discussion started by: nnnnnnine
0 Replies

10. Red Hat

Finding speed of NIC Card

Hi, I would like to know how to find out ACTUAL speed of NIC Card. I have used the command ethtool eth0, it is showing supported modes, but what is acutal speed ? how to find out? (4 Replies)
Discussion started by: manoj.solaris
4 Replies
xcb_xkb_get_device_info(3)					   XCB Requests 					xcb_xkb_get_device_info(3)

NAME
xcb_xkb_get_device_info - SYNOPSIS
#include <xcb/xkb.h> Request function xcb_xkb_get_device_info_cookie_t xcb_xkb_get_device_info(xcb_connection_t *conn, xcb_xkb_device_spec_t deviceSpec, uint16_t wanted, uint8_t allButtons, uint8_t firstButton, uint8_t nButtons, xcb_xkb_led_class_spec_t ledClass, xcb_xkb_id_spec_t ledID); Reply datastructure typedef struct xcb_xkb_get_device_info_reply_t { uint8_t response_type; uint8_t deviceID; uint16_t sequence; uint32_t length; uint16_t present; uint16_t supported; uint16_t unsupported; uint16_t nDeviceLedFBs; uint8_t firstBtnWanted; uint8_t nBtnsWanted; uint8_t firstBtnRtrn; uint8_t nBtnsRtrn; uint8_t totalBtns; uint8_t hasOwnState; uint16_t dfltKbdFB; uint16_t dfltLedFB; uint8_t pad0[2]; xcb_atom_t devType; uint16_t nameLen; } xcb_xkb_get_device_info_reply_t; Reply function xcb_xkb_get_device_info_reply_t *xcb_xkb_get_device_info_reply(xcb_connection_t *conn, xcb_xkb_get_device_info_cookie_t cookie, xcb_generic_error_t **e); Reply accessors xcb_xkb_string8_t *xcb_xkb_get_device_info_name(const xcb_xkb_get_device_info_request_t *reply); int xcb_xkb_get_device_info_name_length(const xcb_xkb_get_device_info_reply_t *reply); xcb_generic_iterator_t xcb_xkb_get_device_info_name_end(const xcb_xkb_get_device_info_reply_t *reply); xcb_xkb_action_t *xcb_xkb_get_device_info_btn_actions(const xcb_xkb_get_device_info_request_t *reply); int xcb_xkb_get_device_info_btn_actions_length(const xcb_xkb_get_device_info_reply_t *reply); xcb_xkb_action_iterator_t xcb_xkb_get_device_info_btn_actions_iterator(const xcb_xkb_get_device_info_reply_t *reply); int xcb_xkb_get_device_info_leds_length(const xcb_xkb_get_device_info_reply_t *reply); xcb_xkb_device_led_info_iterator_t xcb_xkb_get_device_info_leds_iterator(const xcb_xkb_get_device_info_reply_t *reply); REQUEST ARGUMENTS
conn The XCB connection to X11. deviceSpec TODO: NOT YET DOCUMENTED. wanted TODO: NOT YET DOCUMENTED. allButtons TODO: NOT YET DOCUMENTED. firstButton TODO: NOT YET DOCUMENTED. nButtons TODO: NOT YET DOCUMENTED. ledClass TODO: NOT YET DOCUMENTED. ledID TODO: NOT YET DOCUMENTED. REPLY FIELDS
response_type The type of this reply, in this case XCB_XKB_GET_DEVICE_INFO. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. sequence The sequence number of the last request processed by the X11 server. length The length of the reply, in words (a word is 4 bytes). deviceID TODO: NOT YET DOCUMENTED. present TODO: NOT YET DOCUMENTED. supported TODO: NOT YET DOCUMENTED. unsupported TODO: NOT YET DOCUMENTED. nDeviceLedFBs TODO: NOT YET DOCUMENTED. firstBtnWanted TODO: NOT YET DOCUMENTED. nBtnsWanted TODO: NOT YET DOCUMENTED. firstBtnRtrn TODO: NOT YET DOCUMENTED. nBtnsRtrn TODO: NOT YET DOCUMENTED. totalBtns TODO: NOT YET DOCUMENTED. hasOwnState TODO: NOT YET DOCUMENTED. dfltKbdFB TODO: NOT YET DOCUMENTED. dfltLedFB TODO: NOT YET DOCUMENTED. devType TODO: NOT YET DOCUMENTED. nameLen TODO: NOT YET DOCUMENTED. DESCRIPTION
RETURN VALUE
Returns an xcb_xkb_get_device_info_cookie_t. Errors have to be handled when calling the reply function xcb_xkb_get_device_info_reply. If you want to handle errors in the event loop instead, use xcb_xkb_get_device_info_unchecked. See xcb-requests(3) for details. ERRORS
This request does never generate any errors. SEE ALSO
AUTHOR
Generated from xkb.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. XCB
2014-06-10 xcb_xkb_get_device_info(3)
All times are GMT -4. The time now is 07:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy