Steven E Lumos wrote:
According to some posts I've found with deja and by searching the
mailing lists, these cards are now supported in the fxp driver. Since
the string "82559" does not appear either in the CVS logs, nor the
latest version of the driver available for CVS, I need somebody
Ken,
Unfortunately the AIC7890 has a 68pin HD connector for which I don't have a
cable. As far as the scanner goes: I didn't expect it to have a decent SCSI
implementation, this is the reason I used a separate NCR810 to connect it to
my system. But I find it strange that the system panics on
On Sat, 4 Sep 1999, Randall Hopper wrote:
Does FreeBSD support Write Combining on K6 processors?
Randall
Do you mean the MTRR support for K6-2 and above? Yes, that's in 3.3 and 4.0.
--
Brian Fundakowski Feldman / "Any sufficiently advanced bug is\
[EMAIL PROTECTED]
Brian F. Feldman:
|Randall Hopper:
| Does FreeBSD support Write Combining on K6 processors?
|
|Do you mean the MTRR support for K6-2 and above? Yes, that's in 3.3 and 4.0.
Great! Thanks.
Do you know what the status is on the XFree86-FreeBSD MTRR interface
that was being hammered out
On Sun, 5 Sep 1999, Randall Hopper wrote:
Brian F. Feldman:
|Randall Hopper:
| Does FreeBSD support Write Combining on K6 processors?
|
|Do you mean the MTRR support for K6-2 and above? Yes, that's in 3.3 and 4.0.
Great! Thanks.
Do you know what the status is on the
Brian F. Feldman:
|Well, from 3.9.16, I get
|(==) NV(0): Write-combining range (0xcc00,0x100):-)
|
|Nice to know that my work ...errr works.
Great! Thanks for the good piece of work.
| Also, I wonder if you've seen/heard of an MTRR patch for
On Fri, 03 Sep 1999 20:34:22 -0400, John Baldwin wrote:
It was the adding a new user/group just for the sake of adding a new
user/group that bothered many of us. ;)
I've learned to accept that argument on principle is inevitable.
:-)
Later,
Sheldon.
To Unsubscribe: send mail to [EMAIL
Before running soffice for the first time -- apply the trick
described by Andre Albsmeier on
http://www.freebsd.org/cgi/getmsg.cgi?fetch=432982+436209+/usr/local/www/db/text/1998/freebsd-hackers/19980628.freebsd-hackers
to the freshly installed lib/libosl516li.so
mv
Brian F. Feldman:
|Randall Hopper:
| Does FreeBSD support Write Combining on K6 processors?
|
|Do you mean the MTRR support for K6-2 and above? Yes, that's in 3.3 and 4.0.
Great! Thanks.
Do you know what the status is on the XFree86-FreeBSD MTRR interface
that was being
As Kenneth D. Merry wrote ...
Rene de Vries wrote...
Hi,
Today I bought a Umax 1220S scanner and tried to connect this to my FreeBSD
Stable (3.3RC) system. I added a NCR810 specially for the scanner (I don't
want such a device on the same bus as my root disk which is on an aic7890).
Well.. i just looked through some archives and also on the
recent traffic in freebsd-questions.
It seems there are great many people that have same problem i do - apparently
our beloved system does not support PCI modems? Now if i am wrong here -
kick me and ignore the rest of the message.
If
Well.. i just looked through some archives and also on the
recent traffic in freebsd-questions.
It seems there are great many people that have same problem i do - apparently
our beloved system does not support PCI modems? Now if i am wrong here -
kick me and ignore the rest of the
On Sun, 5 Sep 1999, Kevin Day wrote:
Well.. i just looked through some archives and also on the
recent traffic in freebsd-questions.
It seems there are great many people that have same problem i do - apparently
our beloved system does not support PCI modems? Now if i am wrong here -
Mike Smith:
| Also, I wonder if you've seen/heard of an MTRR patch for 3.2-RELEASE
|
|You could try to backport the two sets of commits I just made to the
|-stable branch, but you might be better off moving to -stable or to
|3.3-RELEASE.
Ok, I might try that. From Brian's message, it
On Sun, 5 Sep 1999, Kevin Day wrote:
Well.. i just looked through some archives and also on the
recent traffic in freebsd-questions.
It seems there are great many people that have same problem i do - apparently
our beloved system does not support PCI modems? Now if i am
I've been doing quite a bit of reasearch on NFS lately and some
issues have come up:
async locks, fsync, and a certain person returning from vacation.
1) async locks
To avoid polling on locks by the userland rpc.lockd I'd like to
be able to queue a lock on a file. This can also help
On Sun, 5 Sep 1999, Ugen Antsilevitch wrote:
If i am right - this really has to be fixed and soon. There aren't many ISA
56K modems out there that aren't winmodems. On my last search everything that
was 56K was divided about 80% winmodems and 20% PCI modems (with UART).
I think if you
At 02:27 PM 9/5/99 -0500, Kevin Day wrote:
I'm actually going to look at doing this tommorow, but I have to admit the
sio driver isn't really going to like doing this. Has anyone looked at this
before and could possibly give any suggestions as to how I should begin
this?
I might also point out,
On Sun, 5 Sep 1999, Randall Hopper wrote:
Mike Smith:
| Also, I wonder if you've seen/heard of an MTRR patch for 3.2-RELEASE
|
|You could try to backport the two sets of commits I just made to the
|-stable branch, but you might be better off moving to -stable or to
|3.3-RELEASE.
On Sun, 5 Sep 1999, Kevin Day wrote:
I'm actually going to look at doing this tommorow, but I have to admit
the sio driver isn't really going to like doing this. Has anyone
looked at this before and could possibly give any suggestions as to
how I should begin this?
It looks really ugly.
The
Thanks! Mine reports (after patching):
fxp0@pci0:13:0: class=0x02 card=0x10308086 chip=0x10308086 rev=0x08 hdr=0x00
I have no clue what is really the right way to do it, but here is
the tiny patch I made anyway:
*** if_fxpreg.h.origSat Sep 4 13:33:29 1999
--- if_fxpreg.h Sun Sep 5
Ben Rosengart wrote:
I'm sure this is old ground, but could anyone please tell me why vi is
in /usr/bin instead of /bin? It would be nice to be able to edit files
in /etc (especially the fstab) without /usr mounted on a vanilla install.
/bin/ed
- mark
Mark Newton
On Sun, 5 Sep 1999, Ben Rosengart wrote:
I'm sure this is old ground, but could anyone please tell me why vi is
in /usr/bin instead of /bin? It would be nice to be able to edit files
in /etc (especially the fstab) without /usr mounted on a vanilla install.
IIRC, because vi has a lot
In message [EMAIL PROTECTED] Kevin Day writes:
: No, I'm working on adding support for PCI based non-winmodems. Modems that
: still have a 16550 based uart interface to them, but just happen to sit on
: the PCI bus. I'm not at all planning on writing support for winmodems, just
: making sio.c
In message [EMAIL PROTECTED] Warren Welch
writes:
: I'd really like to see the sio driver code being able to support PCI
: devices...
Might be a good time have a sys/dev/sio and have pccard, cardbus, pci
and isa attachments there. Yes, I did say cardbus, since I have seen
cardbus PCI modems
The long-awaited moment (well, by me anyway) has arrived. Except for the
files in /etc/periodic I have finished the cleanup of the /bin/sh scripts
in /etc. I've followed the style guidelines requested by the majority of
-hackers, so I hope that I've made everyone as happy as possible
subscribe freebsd-hackers@freebsd.org tr...@abraxis.com
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Kherry Zamore wrote:
I installed Sun StarOffice 5.1 on my 4.0-CURRENT machine without any
modifications
at all.. Downloaded, set the ld library path, installed and started
staroffice. I
didn't modify _any_ files at all and it runs without a problem as root. I
haven't
tried playing
According to some posts I've found with deja and by searching the
mailing lists, these cards are now supported in the fxp driver. Since
the string 82559 does not appear either in the CVS logs, nor the
latest version of the driver available for CVS, I need somebody to tell
me which version of the
Steven E Lumos wrote:
According to some posts I've found with deja and by searching the
mailing lists, these cards are now supported in the fxp driver. Since
the string 82559 does not appear either in the CVS logs, nor the
latest version of the driver available for CVS, I need somebody to
Ken,
Unfortunately the AIC7890 has a 68pin HD connector for which I don't have a
cable. As far as the scanner goes: I didn't expect it to have a decent SCSI
implementation, this is the reason I used a separate NCR810 to connect it to
my system. But I find it strange that the system panics on this
On Sat, 4 Sep 1999, Randall Hopper wrote:
Does FreeBSD support Write Combining on K6 processors?
Randall
Do you mean the MTRR support for K6-2 and above? Yes, that's in 3.3 and 4.0.
--
Brian Fundakowski Feldman / Any sufficiently advanced bug is\
gr...@freebsd.org
Brian F. Feldman:
|Randall Hopper:
| Does FreeBSD support Write Combining on K6 processors?
|
|Do you mean the MTRR support for K6-2 and above? Yes, that's in 3.3 and 4.0.
Great! Thanks.
Do you know what the status is on the XFree86-FreeBSD MTRR interface
that was being hammered out
On Sun, 5 Sep 1999, Randall Hopper wrote:
Brian F. Feldman:
|Randall Hopper:
| Does FreeBSD support Write Combining on K6 processors?
|
|Do you mean the MTRR support for K6-2 and above? Yes, that's in 3.3 and 4.0.
Great! Thanks.
Do you know what the status is on the
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Brian F. Feldman:
|Well, from 3.9.16, I get
|(==) NV(0): Write-combining range (0xcc00,0x100)
:-)
|
|Nice to know that my work ...errr works.
Great! Thanks for the good piece of work.
| Also, I wonder if you've seen/heard of an MTRR patch for
On Fri, 03 Sep 1999 20:34:22 -0400, John Baldwin wrote:
It was the adding a new user/group just for the sake of adding a new
user/group that bothered many of us. ;)
I've learned to accept that argument on principle is inevitable.
:-)
Later,
Sheldon.
To Unsubscribe: send mail to
Before running soffice for the first time -- apply the trick
described by Andre Albsmeier on
http://www.freebsd.org/cgi/getmsg.cgi?fetch=432982+436209+/usr/local/www/db/text/1998/freebsd-hackers/19980628.freebsd-hackers
to the freshly installed lib/libosl516li.so
mv
Brian F. Feldman:
|Randall Hopper:
| Does FreeBSD support Write Combining on K6 processors?
|
|Do you mean the MTRR support for K6-2 and above? Yes, that's in 3.3 and 4.0.
Great! Thanks.
Do you know what the status is on the XFree86-FreeBSD MTRR interface
that was being
As Kenneth D. Merry wrote ...
Rene de Vries wrote...
Hi,
Today I bought a Umax 1220S scanner and tried to connect this to my FreeBSD
Stable (3.3RC) system. I added a NCR810 specially for the scanner (I don't
want such a device on the same bus as my root disk which is on an aic7890).
Well.. i just looked through some archives and also on the
recent traffic in freebsd-questions.
It seems there are great many people that have same problem i do - apparently
our beloved system does not support PCI modems? Now if i am wrong here -
kick me and ignore the rest of the message.
If i
Well.. i just looked through some archives and also on the
recent traffic in freebsd-questions.
It seems there are great many people that have same problem i do - apparently
our beloved system does not support PCI modems? Now if i am wrong here -
kick me and ignore the rest of the
On Sun, 5 Sep 1999, Ugen Antsilevitch wrote:
Well.. i just looked through some archives and also on the
recent traffic in freebsd-questions.
It seems there are great many people that have same problem i do - apparently
our beloved system does not support PCI modems? Now if i am wrong here -
On Sun, 5 Sep 1999, Kevin Day wrote:
Well.. i just looked through some archives and also on the
recent traffic in freebsd-questions.
It seems there are great many people that have same problem i do -
apparently
our beloved system does not support PCI modems? Now if i am wrong here
Mike Smith:
| Also, I wonder if you've seen/heard of an MTRR patch for 3.2-RELEASE
|
|You could try to backport the two sets of commits I just made to the
|-stable branch, but you might be better off moving to -stable or to
|3.3-RELEASE.
Ok, I might try that. From Brian's message, it
On Sun, 5 Sep 1999, Kevin Day wrote:
Well.. i just looked through some archives and also on the
recent traffic in freebsd-questions.
It seems there are great many people that have same problem i do -
apparently
our beloved system does not support PCI modems? Now if i am
I've been doing quite a bit of reasearch on NFS lately and some
issues have come up:
async locks, fsync, and a certain person returning from vacation.
1) async locks
To avoid polling on locks by the userland rpc.lockd I'd like to
be able to queue a lock on a file. This can also help database
On Sun, 5 Sep 1999, Ugen Antsilevitch wrote:
If i am right - this really has to be fixed and soon. There aren't many ISA
56K modems out there that aren't winmodems. On my last search everything that
was 56K was divided about 80% winmodems and 20% PCI modems (with UART).
I think if you
Hey!
Thanx a lot first of all!
Anytime i CAN write something myself - i do. I can go as low as networking code
or pseudodevice driver. But i am at loss when it comes to hardware (and within
my scope of work etc. i doubt i will ever learn this stuff). Thats why i
pleaded for help.
I
The different results people are having may be a result of the
date of their FreeBSD.
It Works Here[tm] OOTB (setup requires the LD_LIBRARY_PATH set)
with the following
-current of about Aug 22nd
-stable of Aug 26th
-stable of Sep 2nd
-stable of Sep 4th
It does not work here with
-current of
At 02:27 PM 9/5/99 -0500, Kevin Day wrote:
I'm actually going to look at doing this tommorow, but I have to admit the
sio driver isn't really going to like doing this. Has anyone looked at this
before and could possibly give any suggestions as to how I should begin
this?
I might also point
On Sun, 5 Sep 1999, Randall Hopper wrote:
Mike Smith:
| Also, I wonder if you've seen/heard of an MTRR patch for 3.2-RELEASE
|
|You could try to backport the two sets of commits I just made to the
|-stable branch, but you might be better off moving to -stable or to
|3.3-RELEASE.
I'm sure this is old ground, but could anyone please tell me why vi is
in /usr/bin instead of /bin? It would be nice to be able to edit files
in /etc (especially the fstab) without /usr mounted on a vanilla install.
--
Ben
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To
On Sun, 5 Sep 1999, Kevin Day wrote:
I'm actually going to look at doing this tommorow, but I have to admit
the sio driver isn't really going to like doing this. Has anyone
looked at this before and could possibly give any suggestions as to
how I should begin this?
It looks really ugly.
The
Thanks! Mine reports (after patching):
f...@pci0:13:0: class=0x02 card=0x10308086 chip=0x10308086 rev=0x08 hdr=0x00
I have no clue what is really the right way to do it, but here is
the tiny patch I made anyway:
*** if_fxpreg.h.origSat Sep 4 13:33:29 1999
--- if_fxpreg.h Sun Sep 5
Ben Rosengart wrote:
I'm sure this is old ground, but could anyone please tell me why vi is
in /usr/bin instead of /bin? It would be nice to be able to edit files
in /etc (especially the fstab) without /usr mounted on a vanilla install.
/bin/ed
- mark
Mark Newton
On Sun, 5 Sep 1999, Ben Rosengart wrote:
I'm sure this is old ground, but could anyone please tell me why vi is
in /usr/bin instead of /bin? It would be nice to be able to edit files
in /etc (especially the fstab) without /usr mounted on a vanilla install.
IIRC, because vi has a lot
In message 199909051942.oaa42...@celery.dragondata.com Kevin Day writes:
: No, I'm working on adding support for PCI based non-winmodems. Modems that
: still have a 16550 based uart interface to them, but just happen to sit on
: the PCI bus. I'm not at all planning on writing support for
In message 4.2.0.58.19990906100437.04bf3...@arthur.intraceptives.com.au
Warren Welch writes:
: I'd really like to see the sio driver code being able to support PCI
: devices...
Might be a good time have a sys/dev/sio and have pccard, cardbus, pci
and isa attachments there. Yes, I did say
This post is somewhat in relation to the local DoS thread
started on --security a few days ago.
To slightly put things back into context: The panic() signaling
out of mbuf clusters is a result of the initial MGET failing, calling
m_retry, and failing again. Since we seem to be
Hi,
I have a few questions on FreeBSD installation; I hope you would help me to
answer them.
1. How to change the labels and modify the FreeBSD Booteasy. I.e.,
From: F1 ??
F2 DOS
F3 DOS
F4 FreeBSD
F5 Disk1
toF1 WinNT 4.0
F2
: The only reason that I see for which we would actually panic() in
:this situation (as opposed to suffer the packet loss) is if we get to the
:point where we're losing packets because some script kid starts up
:something that will eat up sockbuf space and continuously fork, then we
:would
Once securelevel has been increased, no process can decrease it because
kernel always refuse decreasing it. This is inconsistent with the
manual page of init:
The kernel runs with four different levels of security. Any super-user
process can raise the security level, but only init can
On Sun, Sep 05, 1999 at 09:00:00PM -0600, Warner Losh wrote:
In message 4.2.0.58.19990906100437.04bf3...@arthur.intraceptives.com.au
Warren Welch writes:
Might be a good time have a sys/dev/sio and have pccard, cardbus, pci
and isa attachments there. Yes, I did say cardbus, since I have seen
Once securelevel has been increased, no process can decrease it because
kernel always refuse decreasing it. This is inconsistent with the
manual page of init:
The kernel runs with four different levels of security. Any super-user
process can raise the security level, but only init can
Rene de Vries wrote...
It sounds like there may be a couple of things going on. First, your
scanner may not be returning sense information properly.
Second, the NCR driver may be doing something wrong.
It would be helpful if you could hook this up to your 7890 controller and
see
[[ questions trimmed ]]
In message 19990906151211.a21...@gurney.reilly.home Andrew Reilly writes:
: And USB? This reference says that you can (now? soon?) buy a
: laptop docking station with all of the usual ports, connected
: only by USB...
:
:
Wilko Bulte wrote...
As Kenneth D. Merry wrote ...
It sounds like there may be a couple of things going on. First, your
scanner may not be returning sense information properly.
Second, the NCR driver may be doing something wrong.
It would be helpful if you could hook this up to
Bruce Evans b...@zeta.org.au wrote:
There used to be security holes that allowed root to lower `securelevel'
using init. Rev.1.9 defends against any undiscovered holes.
How about following change?
--
*** init.8.ORIG Mon Sep 6 14:20:46 1999
--- init.8 Mon Sep 6 14:23:01 1999
There used to be security holes that allowed root to lower `securelevel'
using init. Rev.1.9 defends against any undiscovered holes.
How about following change?
OK.
Bruce
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
On Mon, 06 Sep 1999, Warner Losh wrote:
: http://www.infoworld.com/cgi-bin/displayStory.pl?99093.piusb.htm
:
: Hmm. What sort of level of nesting do we support for this sort
: of thing? It's probably possible to buy USB interface cards
: that plug into ISA, PCI, SCSI? And vice-versa?
USB doesn't present a 16550A interface to the host, so I don't think
that sio would have a USB attachment.
So there's going to be manufacturer-specific terminal/serial port drivers
to talk to the serial ports on USB-attached laptop docking stations, like
the Annex ethernet terminal server
In message 9909061532290g.69...@gurney.reilly.home Andrew Reilly writes:
: So there's going to be manufacturer-specific terminal/serial port drivers
: to talk to the serial ports on USB-attached laptop docking stations, like
: the Annex ethernet terminal server things? I guess in the Windows
Hello!
The following program
#include stdio.h
#include fcntl.h
main() {
int control;
if ((control = open(STATUS,O_WRONLY|O_NONBLOCK))0) {
perror(Could not open STATUS );
exit(1);
}
printf(STATUS ready\n);
close(control);
74 matches
Mail list logo
