10 More Discussions You Might Find Interesting
1. SCO
Hello all,
First off- great forum! I have learned a lot just by reading some of the questions and answers. Good to see there are good people out there still willing to help!
Here is my dilemma- I have a fairly new server running an Activant product on it, which runs SCO openserver 5.0.5... (9 Replies)
Discussion started by: crt001
9 Replies
2. UNIX for Advanced & Expert Users
Hi All ,
I wanted to install SCO Open server 5.0.7 on HP DC7600 Desktop Machine, is there any bootloader and which site i can find it to enable me install it because the system is not recognizing the Hard disk just like the ML G Series machine installations.
Please help if you have done this... (4 Replies)
Discussion started by: davosky
4 Replies
3. SCO
I am currently having a problem with my SCO OpenServer 5.0.5 / 3.2v5.0.5 system.
Running smoothly for the past 3 years, at random on March 16, 2010 the system crashes. I reboot it. Everything is normal again. 9 hours later it crashes again. This cycle has repeated itself ever since then. System... (2 Replies)
Discussion started by: jesmith
2 Replies
4. SCO
hello, i want to install release 5.0.5 on my notebook but the system hangs when extracing files from source media in fact after configuration all of setting please help me:confused: (1 Reply)
Discussion started by: hossein
1 Replies
5. SCO
we are installing Openserver 5.0.7, system have SAS controller (Hard Disk Attached) as well as Adaptec ultra 320 controller (Tape Drive Attached).
At the time of installation we link both driver BTLD
Boot: Defbootstr link=accraid ad320
Aftes succesfully installation of accraid btld... (6 Replies)
Discussion started by: hafizurr
6 Replies
6. SCO
Hi everyone,
We r installing sco openserver 5.07 on dell poweredge 2800 but we are facing problem when installing SCSI-raid drivers. Dell provide Perc4 raid card and we dont found raid drivers for this specific raid card. So we r stuck up on primary stage and we also dont know the... (2 Replies)
Discussion started by: mineshkoli
2 Replies
7. UNIX for Dummies Questions & Answers
I am running the beta version of Openserver by SCO and the
Graphical login only gives me the option of logging into the
system v xwindows and I know that this build included KDE 3.3
I have tried the kde kdm command at shell prompt: command not
found. Any ideas anyone? (0 Replies)
Discussion started by: coreykirk
0 Replies
8. UNIX for Dummies Questions & Answers
My company has a Compaq NeoServer running SCO OpenServer Release 5 (vintage late 1998) that we inherited from another small company. This has been a very reliable file server for our small company. We recently installed a new Linux server and would like to convert the NeoServer to other functions... (1 Reply)
Discussion started by: Jeff Boyce
1 Replies
9. Filesystems, Disks and Memory
Hello all,
I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I... (1 Reply)
Discussion started by: immulett
1 Replies
10. IP Networking
I have certain problems while Installing UNIX OPENSERVER.Could anyone solve that if I provide that problem. (3 Replies)
Discussion started by: Rajraius
3 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
