12-17-2009
hello, I already have the values:
Bus: 0
Device: 8
Function: 0
apply changes in netconfig, but when I press exit netconfig, press "YES" in Relinked Kernel, and displays the message:
Error: Cannot find Driver.o for sem.
Fatal Error: Erros encountered. Configuration Terminated.
idbuild: idconfig had errors
system build failed
restart the server, but the changes did not work.
in /usr/adm/messages shows the same as before:
ktcHT 0xd400-0xd41f - - Kingston Et ....... NOT FOUND [KNE120TX]
10 More Discussions You Might Find Interesting
1. IP Networking
I have a UnixWare 2 server that has an ISA 3Com NIC that has just a BNC connector on it. I want to remove this and install an ISA 3Com NIC that has a BNC/RJ45 connector. What steps do I have to go through to successfully complete this? Thye are almost the exact same cards except for the... (1 Reply)
Discussion started by: cparks
1 Replies
2. IP Networking
The Octane is driving me nuts . It was sitting on the network doing its job nicely and i had to pull the n/w cable out from the wall to pull it from the inside of the table and connected it again . The logs show this -- link down .... < when i pulled it out >
link ok < when i connected >
But... (0 Replies)
Discussion started by: DPAI
0 Replies
3. UNIX for Advanced & Expert Users
I have been having trouble with my sis900 neytwork card in slacwkare linux. I tried to modprobe the sis900, it didnt give me any errors but it didnt load it. so I put in a realtek 8139 network card and tried it too. These are the errors i get with the two cards when trying to do insmod on either of... (3 Replies)
Discussion started by: The Fridgerator
3 Replies
4. UNIX for Dummies Questions & Answers
Hi!.
I have problems installing my network card under
ther redhat kernel.
First i tryed my integrated intel pro set 10/100
then my d-link 530tx Pci but none of them seems to
be found.
also i huse my network card to connect to the net
trough PPPOE where i need to type my username and... (3 Replies)
Discussion started by: Gibbler
3 Replies
5. SCO
Hi,
I was wondering if anyone could help me out with this problem. I have SCO 5.0.5 installed on a system that I am using 3c905b (3 Com) network card. This system is always powered on. After no certain time period this NIC doesn't work. I can't ping to this system from any other machine or vice... (2 Replies)
Discussion started by: AtALoss
2 Replies
6. UNIX for Dummies Questions & Answers
I have three network cards in my unix box. I need to figure out which card corresponds to an assigned IP address. If there some command in unix I can use to make an ethernet interface blink?
Any advice would be appreciated. (6 Replies)
Discussion started by: mojoman
6 Replies
7. Solaris
Hi Experts,
Can we use some command from unix to find the available network interface? I did tried
Its listing following, however how can I decide the which vender card is attached
e.g. if its hme , bge or some thing else
Thanks (7 Replies)
Discussion started by: kumarmani
7 Replies
8. SCO
SCO unix 5.0.5 - Suddently network lost & has to be reboot. I try to stop TCP & start TCP. but no connection. Any idea about that.
thanks (8 Replies)
Discussion started by: ajantha
8 Replies
9. Solaris
Hi All,
Can somebody explain that whats the meaning of different interfaces naming scheme, Like ' hme, qfe, e1000g0, ce, eri, bge' ?
This is such a basic question which i always overlooked :(
Thanks ! (6 Replies)
Discussion started by: Solarister
6 Replies
10. Red Hat
Dear All ,
While taking backups in one Linux Server , we find one alert came with regard to Network Interface Card.
Pl find the below alert.
Network Interface Card performance for NIC:eth1 has exceeded Major threshold.
Bytes sent and received per second (Average)= 105540.303101... (6 Replies)
Discussion started by: jegaraman
6 Replies
UBT(4) BSD Kernel Interfaces Manual UBT(4)
NAME
ubt -- USB Bluetooth driver
SYNOPSIS
ubt* at uhub? port ? configuration ? interface ?
DESCRIPTION
The ubt driver provides support for USB Bluetooth dongles to the Bluetooth protocol stack.
USB Bluetooth dongles provide two interfaces, both of which the ubt driver claims. The second interface is used for Isochronous data and
will have several alternate configurations regarding bandwidth consumption, which can be set using the hw.ubtN.config sysctl(8) variable.
The number of alternate configurations is indicated by the value in the hw.ubtN.alt_config variable, and the isoc frame size for the current
configuration is shown in the hw.ubtN.sco_rxsize and hw.ubtN.sco_txsize variables.
By default, configuration 0 is selected, which means that no bandwidth is used on the Isochronous interface and no SCO data can be sent.
Consult the Bluetooth USB specification at https://www.bluetooth.org/ for complete instructions on setting bandwidth consumption. The fol-
lowing extract may be useful as a general guidance though details may differ between manufacturers.
0 No active voice channels
1 One voice channel with 8-bit encoding
2 Two voice channels with 8-bit encoding, or one voice channel with 16-bit encoding.
3 Three voice channels with 8-bit encoding
4 Two voice channels with 16-bit encoding
5 Three voice channels with 16-bit encoding
SEE ALSO
bluetooth(4), uhub(4), sysctl(8)
HISTORY
This ubt device driver was originally a character device written by David Sainty and Lennart Augustsson. It was rewritten to support socket
based Bluetooth access for NetBSD 4.0 by Iain Hibbert.
CAVEATS
Isochronous data is seemingly not well supported over USB in the current system and to get SCO working, you may have to calculate the SCO
packet size that the stack will use. This is the sco_mtu value reported by the btconfig(8) command, and when combined with the SCO header (3
bytes) should fit exactly into an integer number of Isochronous data frames where the frame size is indicated by the 'hw.ubtN.sco_txsize'
sysctl variable.
For example: I want one voice channel (which is all that is supported, for now) so am using configuration #2, with a frame length of 17
bytes. This gives possible values of:
(17 * 1) - 3 = 14
(17 * 2) - 3 = 31
(17 * 3) - 3 = 48
(17 * 4) - 3 = 65
(17 * 5) - 3 = 82
etc.
btconfig(8) shows the maximum SCO payload as 64 bytes, so I am using the next smaller size of 48, to minimize the overhead of the 3 header
bytes.
The SCO packet size can be changed using the 'scomtu' option to btconfig(8).
The failure mode is that the USB Bluetooth dongle locks up though generally removal/reinsertion will clear the problem.
BUGS
The Isochronous configuration can only be changed when the device is not marked up.
BSD
August 27, 2006 BSD