On Monday, 8 January 2001 at 10:04:44 +0200, Roman Shterenzon wrote:
* Roman Shterenzon [EMAIL PROTECTED] [010107 10:24] wrote:
Hi,
Could you please take a look at :
http://www.freebsd.org/cgi/query-pr.cgi?pr=24019
It's my friend's PR. Can you give me some hints on how can I debug this
On Mon, 8 Jan 2001, Greg Lehey wrote:
On Monday, 8 January 2001 at 10:04:44 +0200, Roman Shterenzon wrote:
* Roman Shterenzon [EMAIL PROTECTED] [010107 10:24] wrote:
Hi,
Could you please take a look at :
http://www.freebsd.org/cgi/query-pr.cgi?pr=24019
It's my friend's PR. Can you
Mohan Khurana wrote:
Well, this is going to seem like a rather strange question. I understand
that Xbox is simply IA-32, however I have heard that the Xbox has a
special ROM that boots Windows CE, to ensure that people do not purchase
the Xbox for the sole reason of running FreeBSD or any
Warner Losh wrote:
In message [EMAIL PROTECTED] Graham Wheeler writes:
: Nope - as I said, I added log messages to apm.c to log the BIOS probe
: and they log a failure (I have "device apm0" in my config file).
What's the failure mode? Is it enabled in the BIOS (I assume it is,
otherwise
On Sun, 7 Jan 2001, Nick Hibma wrote:
There is, I think, at least a bug in subr_bus.c that might cause this,
although, this is just a hunch. I've not been able to explain what's
happening yet.
What is happening is that device_probe_child sets the device class, and
in case of an error
On Sun, 7 Jan 2001, Nick Hibma wrote:
Jon, could you try the attached patch and tell me whether that works for
you?
Unfortunately, no. The probe messages differ, but it still panics.
This is 4.2-RELEASE, I can try something more recent if it'll get you any
better details.
uhci0: Intel
[.. redirected to hackers@ and msmith@, quotes kept for context ..]
On Mon, Jan 08, 2001 at 04:22:30PM -0800, Peter Brezny wrote:
I've been trying to find the port for this utility.
Mike Smith mentioned that it was in the testing phase, close to being
released, but I'm not sure what
On 08-Jan-01 Robert Lipe wrote:
Hi, Gang.
In 4.1.1, I have a pretty simple need for a kernel thread or two, but
I'm having problems with kthread_exit(). The problem is that the thread
goes zombie after I kthread_exit in it, but it never gets reaped. Since
I'm doing this during a
uhid0: vendor 0x product 0x0667, rev 1.00/2.88, addr 2, iclass 3/0
uhid0: no report descriptor
device_probe_and_attach: uhid0 attach returned 6
ugen0: vendor 0x product 0x0667, rev 1.00/2.88, addr 2
ugen0: setting configuration index 0 failed
device_probe_and_attach: ugen0 attach
[.. redirected to hackers@ and msmith@, quotes kept for context ..]
On Mon, Jan 08, 2001 at 04:22:30PM -0800, Peter Brezny wrote:
I've been trying to find the port for this utility.
Mike Smith mentioned that it was in the testing phase, close to being
released, but I'm not sure what
On Sun, 7 Jan 2001, cristian nicolae wrote:
I have a Compaq DL380 with an integrated Compaq Smart Array Controller.
I have succesfully managed to install the FreeBSD 4.2-20010104
and everything is fine but the DAT drive which is not detected.
The SCSI passthrough interface on that controller
hi,
I have some questions... but most of them may be prerry lame because I am new
to FreeBSD.
I am running 5.0 and I have a driver for a card which was written for 4.1.
The driver uses bus_if.h, device_if.h and pci_if.h and these files are generated
by makedevops.pl. The driver is written as
John Baldwin wrote:
On 08-Jan-01 Robert Lipe wrote:
I'm having problems with kthread_exit(). The problem is that the thread
goes zombie after I kthread_exit in it, but it never gets reaped. Since
I'm doing this during a MOD_UNLOAD phase, if I happen to do a `ps -ax'
after the module
Vijo Cherian wrote:
2. When did kobj find place in the kernel? (which release)
(that is what makeobjops.pl does,right?)
Kobj was added to 5.0-current (which is not (yet) a release).
4. Can you point me to a driver that can be loaded as kld?
Look at /sys/modules or check out
Hook the DAT drive up to the internal SCSI adapter (I assume it has one
since it would be fairly silly not to.)
Actually, I'm not sure that it does. They use the Symbios part with the
integrated ARM processor, and assume that SCSI passthrough works.
--
... every activity meets with
On 09-Jan-01 Robert Lipe wrote:
John Baldwin wrote:
On 08-Jan-01 Robert Lipe wrote:
I'm having problems with kthread_exit(). The problem is that the thread
goes zombie after I kthread_exit in it, but it never gets reaped. Since
I'm doing this during a MOD_UNLOAD phase, if I happen
"Kenneth D. Merry" wrote:
On Sun, Jan 07, 2001 at 14:35:53 +0100, cristian nicolae wrote:
Dear all,
I have a Compaq DL380 with an integrated Compaq Smart Array Controller.
I have succesfully managed to install the FreeBSD 4.2-20010104
and everything is fine but the DAT drive which is
If this is not proper place to ask this, let me know and I'll go elsewhere as
it is a TCP question. . . but I specifically use (and prefer) FreeBSD.
I wrote a simple little I/O multiplexing thing that can act as a client or
server as a personal project in network programming. Everything seems
There is a workaround, if not a fix, for this problem in -CURRENT.
Apply the following patch to /sys/isa/psm.c and add flags 0x8000
to psm driver in your kernel config file as follows.
device psm0at atkbdc? irq 12 flags 0x8000
Kazu
I have an intermittent (and fairly rare) problem
John Baldwin wrote:
Unloading modules adds all sorts of new problems. Right now the WITNESS code
will do bad bad things if you kldunload a module that contains a mutex. Even
if the mutex is mtx_destroy'd because it still has a reference to its name in
the internal lists it keeps.
Funny.
Hi Michael,
What version of FreeBSD are you running? If it's not too much trouble,
can you please provide the code you're using to simulate the problem? Are the
TIME_WAIT state connections eventually timing out/disappearing?
Michael wrote:
If this is not proper place to ask this, let me
On Fri, Jan 05, 2001 at 14:45 -0800, Doug Barton wrote:
[ -chat or -advocacy parts deleted :) ]
Since I wanted this OT subthread to die soon and to keep the
technical discussion away from it, I will cite your message in
the other subthread to keep the "solution" (or put better: the
way
[ citing from Doug's message in the "OT: silence ..." subthread
to keep the technical discussion in the "how to test" subthread ]
On Tue, Jan 05, 2001 at 14:45 -0800, Doug Barton wrote:
You stated in another post that you wished I had elaborated
more. I was in a hurry when I wrote that post,
Hi,
I'm thinking of messing with the syscons ioctl handler to allow setting
of color values - all EGA- and VGA-compatible video controllers allow this.
The idea is to later define my termcap(5) entry to let ncurses deal with
color setting.
termcap(5) lists the 'cc' - 'can change color' and 'Ic'
24 matches
Mail list logo
