06-28-2013
Relink kernel error
SCO Unix 5.0.5
wd Srom 1
/var/opt/K/SCO/link/1.1.0Eb/etc/conf/cf.d/msci - parameter count
Idbuild idscsi had errors
System build failed.
Any idea ?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi!!!
I installed the patch: DUV40F16-C0040500-10245-Manual-20010328 to avoid a reboot problem in my server, AlphaServer 4100 with Tru64 4.0F.
When the patch instalation finished I rebuild the kernel like this:
# duconfig -c ORACLE-TEST
Start de rebuild and a few minutes after appear... (0 Replies)
Discussion started by: irasela
0 Replies
2. AIX
Hi,
I'm in the process of compiling gnu gettext on a rs/6000 43p-260 running AIX 5.1 in 64bit-mode. The compilation itself runs fine as I understand it, however the installation itself fails like so:
I'm pretty much clueless about this relink stuff, so if anyone has suggestions, I'll try... (0 Replies)
Discussion started by: töfte
0 Replies
3. UNIX for Advanced & Expert Users
Hi,
under Unix AIX 5 3 , when launching a binary called adworker (ORACLE BINARY) I have this message :
Could not load program /exec/products/OA/v11.5.10.2/p13drec/p13dsmsappl/ad/11.5.0/bin/adworker:
rtld: 0712-001 Symbol __pth_init was referenced
from module adworker(), but a runtime definition... (1 Reply)
Discussion started by: big123456
1 Replies
4. UNIX for Advanced & Expert Users
Hello,
I installed a new java version on a suse linux box. I see directory java is linked to the old SunJava 1.3 version. How can I relink it to the j2re1.4.2_15 directory so it will use the new java version without me having to hardcode the directory. Thanks.
lrwxrwxrwx 1 root ... (4 Replies)
Discussion started by: benefactr
4 Replies
5. SCO
Hi All,
While installing a Service Pack on my Unix Solaris machine, i got the following error:
UX:acomp: ERROR: "space.c", line 16: undefined symbol: CHROOT_SECURITY
UX:acomp: ERROR: "space.c", line 16: non-constant initializer: op "NAME"
UX:idmkunix: ERROR: Compile/link of 'Driver_atup.o... (9 Replies)
Discussion started by: am_yadav
9 Replies
6. Linux
Hi,
Nov 13 12:47:53 FIREWALL003 kernel: warning: many lost ticks.
Nov 13 12:47:53 FIREWALL003 kernel: Your time source seems to be instable or some driver is hogging interupts
Nov 13 12:47:53 FIREWALL003 kernel: rip __do_softirq+0x4d/0xd0
I was able to login at 1pm but I can't do anything. ... (5 Replies)
Discussion started by: itik
5 Replies
7. Red Hat
Hi Guys,
I'm working with a down RedHat Server. Whenever the server tries to boot, there's an error stating:
Kernel panic: No init found. Try passing init= option to kernel.
In addition to this, the "Caps Lock" and "Scroll Lock" lights start flashing. The server doesn't boot pass this... (1 Reply)
Discussion started by: bbbngowc
1 Replies
8. Ubuntu
Hi
I'm compiling a real-time kernel in linux, but after I type make bzImage things end with this:
(Things going well doing CC and things)....
CC arch/x86/kernel/kgdb.o
CC arch/x86/kernel/vm86_32.o
CC arch/x86/kernel/early_printk.o
CC arch/x86/kernel/ipipe.o... (2 Replies)
Discussion started by: mdop
2 Replies
9. UNIX for Dummies Questions & Answers
Hi I m using redhat 6 with kernel release
2.6.32-71.el6.i686
I have downloaded latest kernel 3.3.1 from kernel.org .
when i run make module_install i get below error.
# make modules_install
/usr/src/kernels/linux-3.3.1/scripts/depmod.sh: line 37: 11314 Killed ... (0 Replies)
Discussion started by: pinga123
0 Replies
10. AIX
Hello,
There is a need to link a new dynamic library to a big number of exes.
Unfortunately, I cannot recompile/link all these exes against the new library.
Is there any way to link an existing executable with the new library?
(everything has been compiled using the xlc tool)
Thanks (1 Reply)
Discussion started by: geodimo
1 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