"Dave J. Boers" wrote:
On Tue, Dec 21, 1999 at 11:22:12PM +0100, Thierry Herbelot wrote:
Let's start a thread on the BP6 ? (the release of the board was
carefully synchronized with stable SMP releases of FreeBSD : kudos to
the FreeBSD release engineering team ;-))
I second that!
Christopher Nielsen wrote:
On Tue, 21 Dec 1999, Andrey A. Chernov wrote:
With latest ppp I hear no phone numbers dial sounds at the stage:
Phase: Phone: N
ppp does _nothing_ until timeout occurse, then redial happens
with the same unsuccessful result.
I'm seeing the exact
It seems Alex Zepeda wrote:
Perhaps blacklisting all WD/Maxtor drives that don't report an ATA
version, as the ata (and wd) driver works flawlessly in UDMA33 mode with
my setup:
Hmm, thats an idea...
ata-pci0: Intel PIIX4 ATA controller at device 7.1 on pci0
ata-pci0: Busmastering DMA
It seems Pim van Grol wrote:
For your information:
I encountered the same problem on a MVP3 board (Epox ep-mvp3g-m)
with via vt82c596, which worked well untill 13-12-99. Matrox HD.
Are you sure you mean 596 ?? that is NOT supported (yet).
Correctly interpreted as doing UDMA33. From
At 8:00 PM +1300 1999/12/22, Joe Abley wrote:
Sorry if this is stating the obvious, but I've seen more than one
clueful person bitten by this:
hard-wire your duplex setting on your machine and also on the switch
If you check http://www.backplane.com/diablo/hard.html and
scroll
I'm planning to commit the bus space code(*) supporting indirection
into current for PC-98. As far as I know, only PC-98 needs
indirection. So, it will be enabled only when the `PC98' is defined
to avoid performance loss on IBM-PCs.
(*)The code is submitted by Takahashi-san [EMAIL PROTECTED].
It seem this is relevant.
Here is the output of "python test_select.py":
Traceback (innermost last):
File "test_select.py", line 63, in ?
test()
File "test_select.py", line 47, in test
rfd, wfd, xfd = select.select([p], [], [], tout)
select.error: (4, 'Interrupted system
If you end up doing this, can you have the driver print a line letting
people know this is intentional? i.e.,
ad0: DMA disabled: This drive does not properly support DMA mode.
ad0: To force DMA for this drive (at your own risk) set flags 0xXX.
Let's not go the Linux way and make the
Yes, I've heard that as well, the repeating, but not
consistent. Sometimes it happens, sometimes it doesn't. Sometimes it
loops forever (with my limited patience).
Nick
Cameron,
Thanks for fixing the regenerative feedback problem between the mic and
the speakers.
My ESS1869 is now
It seems Nick Hibma wrote:
If you end up doing this, can you have the driver print a line letting
people know this is intentional? i.e.,
ad0: DMA disabled: This drive does not properly support DMA mode.
ad0: To force DMA for this drive (at your own risk) set flags 0xXX.
Let's not
I cvsupped 24 hours ago, and I just re-cvsupped and there were no
changes to any ppp sources...
The dial string is not being parsed correctly
set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK ATE1Q0 OK
\\dATDT\\T TIMEOUT 40 CONNECT"
The \\d and the \\T are not being parsed.
today i had no luck with linux-netscape-4.7 from the ports. It dumps
core with bus error.
--
Fritz Heinrichmeyer mailto:[EMAIL PROTECTED]
FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany)
tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh
To Unsubscribe: send mail to
Mentioning it in the manpage should be sufficient I guess. Blacklisting
devices sounds like a good idea if tey fail to work correctly in many
cases.
The problem being how to get a list that is "good enough" for the
majority of cases.
I'd like to see it the other way around: Make sure
It seems Nick Hibma wrote:
Mentioning it in the manpage should be sufficient I guess. Blacklisting
devices sounds like a good idea if tey fail to work correctly in many
cases.
The problem being how to get a list that is "good enough" for the
majority of cases.
I'd like to see
I know your talking SMP but thought you'd like to know some temps for UP
systems as well...
I have a Celeron 300a that I overclock to 464 MHz (100 MHz FSB + extra
turbo frequency boost) running at 2.1 v and it runs at about 30 degrees
celcius when idle and at 52 degrees when running setiathome
Try installing linux-base 6.1 from www.freebsd.org/~marcel
-Charlie
On Wed, Dec 22, 1999 at 01:59:39PM +0100, F. Heinrichmeyer wrote:
today i had no luck with linux-netscape-4.7 from the ports. It dumps
core with bus error.
--
Fritz Heinrichmeyer mailto:[EMAIL PROTECTED]
Nick Hibma wrote:
If you end up doing this, can you have the driver print a line letting
people know this is intentional? i.e.,
ad0: DMA disabled: This drive does not properly support DMA mode.
ad0: To force DMA for this drive (at your own risk) set flags 0xXX.
Let's not go the
Soren Schmidt [EMAIL PROTECTED] wrote:
It seems Nick Hibma wrote:
If you end up doing this, can you have the driver print a line letting
people know this is intentional? i.e.,
ad0: DMA disabled: This drive does not properly support DMA mode.
ad0: To force DMA for this drive
: clueful person bitten by this:
:
:hard-wire your duplex setting on your machine and also on the switch
:
: If you check http://www.backplane.com/diablo/hard.html and
:scroll down to the "Network:" section (from the looks of things,
:written sometime back in 1997 or perhaps 1998),
In an earlier post on -hackers, I mentioned that attempting to kldload the
usb.ko module after the kernel had booted would panic the system. So far
I've managed to track this problem all the way down down to
sys/i386/isa/intr_machdep.c:add_intrdesc(). The system crashes when the
uhci_pci module
On Dec 12, 1999 at 11:37:42AM -0800, Matthew Dillon wrote:
I finally tracked it down. The loss is occuring in the link between
two of my switches. The link goes across my apartment - about 60 feet of
Cat-5 cable. That should be well within spec (you are supposed to be
able
On Wed, Dec 22, 1999 at 09:37:55AM +1030, Greg Lehey wrote:
On Tuesday, 21 December 1999 at 10:07:28 +0100, Wilko Bulte wrote:
On Mon, Dec 20, 1999 at 05:08:27PM -0800, Matthew Dillon wrote:
It's possible you might be on to something. I've been running iostat
at 1 second intervals, and
It seems Bill Paul wrote:
[snip snap]
I don't want to sound like an ungrateful wretch, unduly criticizing
someone else's code, especially at so late a date, but there are some
other things that just seem like they really shouldn't be there:
We've got used to it, on with matters...
-
On Wed, 22 Dec 1999 21:59:30 +0100 (CET), Soren Schmidt [EMAIL PROTECTED] said:
If you looked at the code, you would see that the ata driver only uses
this ugly method when we are dealing with the standard primary
secondary controller which are bound to specific addresses and interrupts.
It seems Garrett Wollman wrote:
On Wed, 22 Dec 1999 21:59:30 +0100 (CET), Soren Schmidt [EMAIL PROTECTED] said:
If you looked at the code, you would see that the ata driver only uses
this ugly method when we are dealing with the standard primary
secondary controller which are bound to
With latest ppp I hear no phone numbers dial sounds at the stage:
Phase: Phone: N
ppp does _nothing_ until timeout occurse, then redial happens
with the same unsuccessful result.
Erk! Fixed now. Thanks for the report.
--
Andrey A. Chernov
http://nagual.pp.ru/~ache/
MTH/SH/HE
Hi All,
This laptop has a couple of problems with FreeBSD-CURRENT
of about 1999/12/22 12:00 UTC.
The system hangs with the disk drive light on.
The output of boot -vc captured from the serial port follows.
current of about 1999/12/11 works in PIO mode.
The machine has a built-in modem that
On Wed, 22 Dec 1999, Eric J. Haug wrote:
Hi All,
This laptop has a couple of problems with FreeBSD-CURRENT
of about 1999/12/22 12:00 UTC.
The system hangs with the disk drive light on.
The output of boot -vc captured from the serial port follows.
current of about 1999/12/11 works in PIO
I think I have a partial explaination of the fsck not working on
the first try, and a reboot fixing it.
I've been using Soren's new driver for some time, and did a MAKEDEV
after the block device changes, but I found that it I booted with
a dirty root filesystem then fsck would fix the problem,
I cvsupped 24 hours ago, and I just re-cvsupped and there were no
changes to any ppp sources...
The dial string is not being parsed correctly
set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK ATE1Q0 OK
\\dATDT\\T TIMEOUT 40 CONNECT"
The \\d and the \\T are not being
+[ Brian Somers ]-
|
|
| Fixed now - my apologies.
Not a problem, that's why it's -current.
--
Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton
The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 |
ACN: 082
On Tue, Dec 21, 1999 at 12:50:24PM +, George Cox wrote:
Right. Get yourself cvsup-bin-16.0 from a FreeBSD ftp site (it's in the
cvsup directory). Install that and read the manpages, just to get a
flavour of how it works.
Next, look at the files in /usr/share/examples/cvsup --
On Wed, 22 Dec 1999, Jonathan Lemon wrote:
On Dec 12, 1999 at 11:37:42AM -0800, Matthew Dillon wrote:
I had a Netgear FS509 switch here that would eat packets transmitted
through the GigE port under certain conditions. Netgear shipped me
a new one, and I've been happy with it, until the
:
:There's some oddities in the 3.3 and 3.4 kernels as well -- I've actually
:nailed down the plexicity and speed on both the Accellar and my humble PC,
:and yet, I'm looking at weird TCP lockups from time to time.
:
:Mostly seems to be related to NFSv3, but will also happen when doing
:cvsup.
make sure you test odd packet lengths. (as in "not even")
there are occasional bugs that turn up with that sort of thing.
On Wed, 22 Dec 1999, Matthew Dillon wrote:
I am clueless as to what is going on. It seems to only happen with TCP
connections. I wrote a UDP-based packet loss
:
:make sure you test odd packet lengths. (as in "not even")
:there are occasional bugs that turn up with that sort of thing.
Yup. Way ahead of you.
Hmm. usleep() seems to have a high granularity - only about 150 Hz.
How annoying!
I've put the linktest program up on my web
On 1999-Dec-23 15:12:53 +1100, Matthew Dillon [EMAIL PROTECTED] wrote:
In fact, while its
running in the background I am *still* getting TCP stutters and tcpdump
still shows one machine sending a packet that the other machine never
gets! I have no friggin clue as to why TCP packets
A new version of linktest is up, much enhanced:
* fixes cpu use problems due to calling random() too much
* fixes usleep (we now use a pipe and select())
This version can really stuff the network.
http://www.backplane.com/FreeSrc/linktest-1.1.c
Running the
On Thu, 23 Dec 1999, David Malone wrote:
The problem seems to be that I'm listing the "/dev/wd1s1a" devices
in fstab instead of "/dev/ad1s1a", and fsck doesn't recognise that
they are the same thing, and so doesn't spot that it needs to set
the hotroot flag.
I'm not sure if this is purely
I'm adding Bill Paul to the list specifically.
Hmm. Now this is odd! I think I may have found something!
All of my 'rl' driver cards fail this test:
apollo# linktest -m 0.1:0.2 -s 16 -f16 lander
lander# linktest -m 0.1:0.2 -s 16 -f16 apollo
They get about
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
I'm adding Bill Paul to the list specifically.
Hmm. Now this is odd! I think I may have found something!
All of my 'rl' driver cards fail this test:
Oh sure. Bet the
On Dec 12, 1999 at 01:41:04AM -0500, Bill Paul wrote:
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
I'm adding Bill Paul to the list specifically.
Hmm. Now this is odd! I think I may have found something!
All
Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
(taking this off -current)
apollo# linktest -s 51 -f1 lander 1-51 byte payload - errors
lander# linktest -s 51 -f1 apollo
apollo# linktest -s 52 -f1 lander
Hi !
I'm seeing strange behaviour of fsck in -current.
FreeBSD titan.klemm.gtn.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Dec 22 07:07:11
CET 1999 root@:/usr/src/sys/compile/TITAN i386
SCSI bus hang, so I had to reboot. fsck checked every filesystem.
But then mount was unable to mount
I have the problem on my system using pure scsi disks.
My fstab entry:
# DeviceMountpoint FStype Options DumpPass#
/dev/da0s2b noneswapsw 0 0
/dev/da1s1b noneswapsw 0 0
45 matches
Mail list logo
