On Wed, Nov 27, 2002 at 10:06:44PM -0500, Kenneth Culver wrote:
What flags are you starting winex with? Also, you can't run the game as
normal I'm assuming because FreeBSD doesn't have block devices. The game
needs to be able to check the cdrom, in order to be able to run, and it
expects to
Hi Poul-Henning,
Poul-Henning Kamp wrote on Tue, Nov 26, 2002 at 08:58:09PM +0100:
[..]
I think we can more or less conclude that something has trashed your
memory.
I'd suggest you try to run your program with ElectricFence or similar.
[..]
I found the problem. It seems to result in a
Bingo! :)
When I changed the bsqh initialisation, I get speed above 400 KB/s,
that makes me feel much better :)
I am sending a corrected patch as attachment.
Tomas
On Thu, 28 Nov 2002, Ian Dowse wrote:
I had a quick look at the patch - one thing I noticed is that you
are possibly not
On Wed, 27 Nov 2002, M. Warner Losh wrote:
Well, right now the following code is trying to force INTA#:
..
sp-putb(sp, PCIC_INT_GEN, /* Assume INTA# */
(sp-getb(sp, PCIC_INT_GEN) 0xF0) | 3);
Which seems to cause the hang. Commenting this out will resort
Woohoo! Congrats. Nice job. If other people could test this, this should
be committed. I'll have to have a quick look at the initialisation code
that has been added to see whether there is no problem with that, but
from the quick glance I just had, I don't think there is a prolbem in
there.
Nick
On Thu, 28 Nov 2002, Dirk-Willem van Gulik wrote:
This doesn't force the interrupt to be IRQ3, but rather tells the card
to use INTA#. The probe line for wi card should say irq N where N is
I may be mistaken - but it seems that
pcic_pci_pd67xx_csc(struct pcic_slot *sp, enum
On Thu, 28 Nov 2002, Dirk-Willem van Gulik wrote:
On Thu, 28 Nov 2002, Dirk-Willem van Gulik wrote:
This doesn't force the interrupt to be IRQ3, but rather tells the card
to use INTA#. The probe line for wi card should say irq N where N is
I may be mistaken - but it seems that
Hello,
I run a number of jail enviroments in a public server, so, i would like to
limit the disk usage of each jail to, say, X GB. Lets think of a practical
issue. I have 40GB storage space, and what i want is to limit disk usage
to 5GB each jail.
This way i will be always sure that, say, if i
In message: [EMAIL PROTECTED]
Dirk-Willem van Gulik [EMAIL PROTECTED] writes:
:
:
: On Thu, 28 Nov 2002, Dirk-Willem van Gulik wrote:
:
: On Thu, 28 Nov 2002, Dirk-Willem van Gulik wrote:
:
:This doesn't force the interrupt to be IRQ3, but rather tells the card
:to use
2 things, first try using the latest version of winex. Second, try editing
/usr/compat/linux/usr/bin/winex (it's a shell script) so that #!/bin/sh
says #!/usr/compat/linux/bin/bash
I found that doing that solves a few problems for me, although I never had
the problem you're having.
Ken
On Thu,
Hello,
I have a question concerning struct sysctl_oids initial value for
oid_refcnt. Why is oid_refcnt set to 0 with the SYSCTL_OID macro
but to 1 if created with sysctl_add_oid()?
And another question: Is it guaranteed that all sysctls from a
modules sysctl_set (obtained with 'sysctls = (struct
Hello,
I believe it has been discussed on one of these lists before.
Create a file that is 5G and use vnconfig to define pseudo disk
device, create a new file system using newfs, then create the jail.
Stefanos
--- Forwarded Message
Date: Thu, 28 Nov 2002 15:40:50 -0200
On Thu, 28 Nov 2002, M. Warner Losh wrote:
this is bogus. However, a less bogus version is:
/*
* Tell the chip to do its routing thing.
*/
sc-chip-func_intr_way(sc-slots[0], sc-func_route);
sc-chip-csc_intr_way(sc-slots[0], sc-csc_route);
The reason
On Thu, 28 Nov 2002, Dirk-Willem van Gulik wrote:
Hmm - no cookie; worse than before.
I take that back.
With the cardbus init -all was essentially functional as far as I could
test; but in with the above the timeouts have returned - abeit in a
..
So something in the cardbus_init() may be
I noticed that there are a couple of things in the pcic_isa.c and in the
pcic.c resume() function which seem to have no equivalent in the
pcic_pci.c; such as speaker/power setup:
pcic_setb(sc-slots[0], PCIC_MISC1, PCIC_MISC1_SPEAKER);
pcic_clrb(sc-slots[0], PCIC_MISC2,
In message: [EMAIL PROTECTED]
Dirk-Willem van Gulik [EMAIL PROTECTED] writes:
: So something in the cardbus_init() may be needed ?
:
: A full powercycle seems to change the situation; and does allow for the
: card(s) to work with just the csc/func calls.
I'm very confused now. I
On Thu, 28 Nov 2002, M. Warner Losh wrote:
So after the first power cycle, can you reboot w/o a power cycle?
Rewired to make that possible.
Not getting very conclusive results; on some reboots (w/o power cycle) it
may take minutes before the Timeout's kick in - whereas on other reboots
it is
In message: [EMAIL PROTECTED]
Dirk-Willem van Gulik [EMAIL PROTECTED] writes:
:
: I noticed that there are a couple of things in the pcic_isa.c and in the
: pcic.c resume() function which seem to have no equivalent in the
: pcic_pci.c; such as speaker/power setup:
:
:
PLEASE LOOK AT LISTING FOR CHINESE SEARCH ENGINE
I WILL CALL YOU TOMORROW
I THINK THIS IS A GOOD IDEA
CHECK OUT THE LISTINGS TO GET AN IDEA
http://www.chinawebs.com/comp/list_sub2.php?sub2_id=2234
6560XRTp8-082omig6367HlQc2-510l28
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
PLEASE LOOK AT LISTING FOR CHINESE SEARCH ENGINE
I WILL CALL YOU TOMORROW
I THINK THIS IS A GOOD IDEA
CHECK OUT THE LISTINGS TO GET AN IDEA
http://www.chinawebs.com/comp/list_sub2.php?sub2_id=2234
3805jplU1-751hUDD6371IseJ3-902kkLq2629RQwh8-695VjQq8603TdUe9-692FENf2350IiBPl72
To Unsubscribe:
In message: [EMAIL PROTECTED]
Dirk-Willem van Gulik [EMAIL PROTECTED] writes:
: wi1: timeout in wi_cmd 0x0002; event status 0x8000
: wi1: timeout in wi_cmd 0x; event status 0x8000
: wi1: wi_cmd: busy bit won't clear.
: wi1: wi_cmd: busy bit won't clear.
:
21 matches
Mail list logo