On Tue, 18 Jan 2000, Warner Losh wrote:
> Also, you will likely need to add an IRQ to the pcic line in your
> kernel config.
The pcic driver should be smart enough to find a free IRQ; in addition
pccardd shouldn't have to specify a list of IRQs to use; thats info the
kernel knows about.
I'm ki
In message <[EMAIL PROTECTED]> "Matthew N. Dodd"
writes:
: The pcic driver should be smart enough to find a free IRQ; in addition
: pccardd shouldn't have to specify a list of IRQs to use; thats info the
: kernel knows about.
Should be smart enough? How? There are a limited number of IRQs
avai
In message <[EMAIL PROTECTED]> "Matthew N. Dodd"
writes:
: pccardd shouldn't have to specify a list of IRQs to use; thats info the
: kernel knows about.
Oops. Missed this part. The problem again is that the kernel doesn't
know about this. At least it knows it only to a point. It knows
which
On Tue, 18 Jan 2000, Warner Losh wrote:
> Oops. Missed this part. The problem again is that the kernel doesn't
> know about this. At least it knows it only to a point. It knows
> which IRQs are in use, but it doesn't know if the pcic (or cardbus
> bridge in compat mode) can route to a given fr
On Wed, 19 Jan 2000, Warner Losh wrote:
> Well, yes. The IRQs are supposed to be free AND ROUTABLE TO THE PCIC
> part. If they are, then it works great. If they aren't, then we lose
> bigtime.
It seems to me that any IRQ that the PCIC can see will be usable for
assignment to a card no? Is the
In message <[EMAIL PROTECTED]> "Matthew N. Dodd"
writes:
: Otherwise your timeout solution seems good. Are the valid IRQs dependent
: on the board integrator or on the chip used? Since we can identify the
: chips (well, it looks like we can) couldn't we maintain a 'quirk' table?
That I'm not s
On Wed, 19 Jan 2000, Warner Losh wrote:
> I'd love to find a good solution to this problem. I'm glad your flame
> caught me at a time when my brain was up for trying to solve this
> silly problem.
Well, I wasn't really trying to flame you, or anyone. It is frusterating
to see how much time gets
In message <[EMAIL PROTECTED]> "Matthew N. Dodd"
writes:
: Well, I wasn't really trying to flame you, or anyone. It is frusterating
: to see how much time gets tied up in tracking down dodgy PCIC configs
: though. Solving that would probably free you up of several emails a
: week. If I start m
In message <[EMAIL PROTECTED]> "Matthew N. Dodd"
writes:
: Ok, I'm obviously missing something here... You mean the IRQs specified
: in /etc/pccard.conf are a complete crapshoot?
Well, yes. The IRQs are supposed to be free AND ROUTABLE TO THE PCIC
part. If they are, then it works great. If
"Matthew N. Dodd" wrote:
>
> Matching drivers to hardware is
> something a newbus driver should do itself; relying on an external hint
> mechanism strikes me as a solution prone to user aggravation. (speaking
> as an aggravated user of course.)
Do you really want to cram a list of all known PCc
In message <[EMAIL PROTECTED]> Wes Peters writes:
: Do you really want to cram a list of all known PCcard and USB devices
: into your kernel? Ugh.
Do you really want to cram a list of all known pci cards into the
kernel? Same thing really.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED
In message <[EMAIL PROTECTED]> Edwin Culp writes:
: Thanks, I would not have found it for a while. I checked UPDATING and saw nothing,
: although my problem may have been because I haven't been able to finish a world
: since the commit.
That's an oversight on my part. Which I'm correcting right
Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Edwin Culp writes:
> : Thanks, I would not have found it for a while. I checked UPDATING and saw nothing,
> : although my problem may have been because I haven't been able to finish a world
> : since the commit.
>
> That's an oversight on my pa
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Wes Peters writes:
> : Do you really want to cram a list of all known PCcard and USB devices
> : into your kernel? Ugh.
>
> Do you really want to cram a list of all known pci cards into the
> kernel? Same thing really.
Mmm... Good point.
On Wed, 19 Jan 2000, Wes Peters wrote:
> Mmm... Good point. This means updating code and compiling a new
> kernel every time Joe's hardware company sticks their own name on a
> generic OEM PCI or PCCard, doesn't it? I love this industry.
Too many drivers require knowledge of specific cards in
In message <[EMAIL PROTECTED]> "Matthew N. Dodd"
writes:
: Too many drivers require knowledge of specific cards in order to properly
: handle 'quirks'. This isn't going to change. While a recompile is
: annoying we can be assured that a driver maintainer will only add IDs to a
: driver after th
On 19-Jan-00 Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Wes Peters writes:
> : Do you really want to cram a list of all known PCcard and USB
> : devices
> : into your kernel? Ugh.
> Do you really want to cram a list of all known pci cards into the
> kernel? Same thing really.
So a
> In message <[EMAIL PROTECTED]> "Matthew N.
>Dodd" writes:
> : pccardd shouldn't have to specify a list of IRQs to use; thats info the
> : kernel knows about.
>
> Oops. Missed this part. The problem again is that the kernel doesn't
> know about this. At least it knows it only to a point. I
In message <[EMAIL PROTECTED]> Mike Smith writes:
: It can make a pretty good guess though; certainly good enough in most
: cases.
The problem with guesses is that they are guesses and often wrong.
Consider a simple case. If I don't have a sound driver configured on
my laptop, IRQ 5 could appe
On Wed, Jan 19, 2000 at 03:50:49PM -0700, Wes Peters wrote:
> Mmm... Good point. This means updating code and compiling a new kernel
> every time Joe's hardware company sticks their own name on a generic OEM
> PCI or PCCard, doesn't it? I love this industry.
Do the above and try and figure ou
Bill Fumerola wrote:
>
> On Wed, Jan 19, 2000 at 03:50:49PM -0700, Wes Peters wrote:
>
> > Mmm... Good point. This means updating code and compiling a new kernel
> > every time Joe's hardware company sticks their own name on a generic OEM
> > PCI or PCCard, doesn't it? I love this industry.
>
Thomas Schuerger wrote:
[Charset ISO-8859-1 unsupported, filtering to ASCII...]
>
> This happens when the install script wants to call {PREFIX}/sbin/ldconfig
> (the Linux-ldconfig).
>
> I rebuilt and reinstalled the linux emulation module, but that
> didn_t help either.
> Installing the above po
... ath_ahb is only needed for MIPS platforms. Why are you building it for x86?
Also, do you have the 5416 support option in your kernel?
adrian
On 4 January 2013 20:37, Super Bisquit wrote:
> In sys/modules/svr4 needs machine/_align.h to read
> X86/include/_align.h, if that means anything.
>
I did not know that ath_ahb was MIPS only. Why? I wanted the most/best
performance for my system's wireless.
Support for 5416 is there but the card is a 2413.
On Sat, Jan 5, 2013 at 12:03 AM, Adrian Chadd wrote:
> ... ath_ahb is only needed for MIPS platforms. Why are you building it for
> x86?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/29/10 14:50, Aryeh Friedman wrote:
> System i386
>
> CVSTag:
>
> # $FreeBSD: src/COPYRIGHT,v 1.11.2.2 2009/12/31 10:00:49 obrien Exp $
> # @(#)COPYRIGHT 8.2 (Berkeley) 3/21/94
>
> flosoft# make -j4 DESTDIR=/ world kernel
Remove -j i
On Wed, Dec 29, 2010 at 6:15 PM, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 12/29/10 14:50, Aryeh Friedman wrote:
>> System i386
>>
>> CVSTag:
>>
>> # $FreeBSD: src/COPYRIGHT,v 1.11.2.2 2009/12/31 10:00:49 obrien Exp $
>> # @(#)COPYRIGHT 8.2 (Berkeley) 3/21/94
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/29/10 16:02, Aryeh Friedman wrote:
> On Wed, Dec 29, 2010 at 6:15 PM, Xin LI wrote:
> On 12/29/10 14:50, Aryeh Friedman wrote:
System i386
CVSTag:
# $FreeBSD: src/COPYRIGHT,v 1.11.2.2 2009/12/31 10:00:49 obrien Exp $
>
On Wed, Dec 29, 2010 at 7:19 PM, Xin LI wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 12/29/10 16:02, Aryeh Friedman wrote:
>> On Wed, Dec 29, 2010 at 6:15 PM, Xin LI wrote:
>> On 12/29/10 14:50, Aryeh Friedman wrote:
> System i386
>
> CVSTag:
>
> # $FreeBS
Hopefully I'm not stating the obvious, but have you tried doing toolchain first?
Sent from my iPhone
On Dec 29, 2010, at 4:30 PM, Aryeh Friedman wrote:
> On Wed, Dec 29, 2010 at 7:19 PM, Xin LI wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> On 12/29/10 16:02, Aryeh Friedma
%I'm running -current from a couple of weeks ago. I recently re-compiled
%XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't
%work with X11, though it does work inside an Xterm. My old aout emacs
%still works (with old aout libraries - the re-compiled aout libraries
%seem to
Peter Jeremy writes:
> I'm running -current from a couple of weeks ago. I recently re-compiled
> XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't
> work with X11, though it does work inside an Xterm. My old aout emacs
> still works (with old aout libraries - the re-compil
Dag-Erling Smorgrav wrote:
>Peter Jeremy writes:
>> I'm running -current from a couple of weeks ago. I recently re-compiled
>> XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't
>> work with X11, though it does work inside an Xterm.
>
>I run an Elf build of Emacs 19.34b dai
> % gdb foobar foobar.core
> Register %s not found in core file.
^^
Should read:
"Register eax not found in core file."
Silly me... :-)
-scooter
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
On Thu, 6 May 1999, Scott Michel wrote:
> > % gdb foobar foobar.core
> > Register %s not found in core file.
>^^
> Should read:
>
> "Register eax not found in core file."
>
> Silly me... :-)
I'll look at it today - My head is in gdb mode at the moment after doing
the import.
--
Dou
On Fri, 4 Jun 1999, Bret Ford wrote:
> vx0: <3Com 3C597-TX Network Adapter> at slot 5 on eisa0
> vx0: No I/O space?!
> device_probe_and_attach: vx0 attach returned -1
This was fixed in version 1.45 of sys/i386/eisaconf.c
--
| Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprit
On 01.05.2021 21.09, Nilton Jose Rizzo wrote:
Hi all
I using a FreeBSD 14-Current and get random error with my NIC. The watchdog
timer send a timeout message and I loose connection temporaly. In logs show
only this message:
May 1 14:24:18 valfenda kernel: re0: watchdog timeout
May 1 14:24:1
On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote:
> I using a FreeBSD 14-Current and get random error with my NIC. The watchdog
> timer send a timeout message and I loose connection temporaly. In logs show
> only this message:
>
Switch to the official Realtek driver in ports: net/rea
Am 01.05.21 um 21:48 schrieb Greg Rivers via freebsd-current:
> On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote:
>> I using a FreeBSD 14-Current and get random error with my NIC. The watchdog
>> timer send a timeout message and I loose connection temporaly. In logs show
>> only this
On Saturday, 1 May 2021 16:45:03 CDT Stefan Esser wrote:
> Am 01.05.21 um 21:48 schrieb Greg Rivers via freebsd-current:
> > On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote:
> >> I using a FreeBSD 14-Current and get random error with my NIC. The
> >> watchdog timer send a timeout mess
Am 02.05.21 um 01:37 schrieb Greg Rivers:
> On Saturday, 1 May 2021 16:45:03 CDT Stefan Esser wrote:
>> Am 01.05.21 um 21:48 schrieb Greg Rivers via freebsd-current:
>>> On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote:
I using a FreeBSD 14-Current and get random error with my NIC.
On Sun, Jan 24, 1999 at 01:47:25PM -0600, Stingray wrote:
> I just CVSup'd 4.0-current and installed it, then made an elf kernel.
> The elf kernel seemed to boot up just fine, but when the file systems
> where being mounted, it couldn't mount /:
>
> Specified device does not match mounted de
> Hi.
>
> I saw that my 4-CURRENT box from 8 February dropped to ddb
> after my last make world. I rebuilt world today, and the
> same problem is occuring. These problems started occuring
> after Matt Dillon's changes to the VM system.
>
> What is worrying/troubling is that in single user mode,
>
On Monday, 15 February 1999 at 18:00:16 -0500, Luoqi Chen wrote:
>> Hi.
>>
>> I saw that my 4-CURRENT box from 8 February dropped to ddb
>> after my last make world. I rebuilt world today, and the
>> same problem is occuring. These problems started occuring
>> after Matt Dillon's changes to the VM
:maxusers 256
Try reducing maxusers to 128. Another person reported similar behavior
to me and after a bunch of work he tried going back to a basic
distribution -- and everything started working again.
It turned out that a maxusers value of 256 and 512 were causing his mac
On Tue, 16 Feb 1999, Matthew Dillon wrote:
> :maxusers 256
>
> Try reducing maxusers to 128. Another person reported similar behavior
> to me and after a bunch of work he tried going back to a basic
> distribution -- and everything started working again.
>
> It turned out t
On Tue, 16 Feb 1999, Matthew Dillon wrote:
MD> Try reducing maxusers to 128. Another person reported similar behavior
MD> to me and after a bunch of work he tried going back to a basic
MD> distribution -- and everything started working again.
Hmmm, ok.
MD> It turned out tha
On Tue, 16 Feb 1999, Matthew Dillon wrote:
> Try reducing maxusers to 128. Another person reported similar behavior
> to me and after a bunch of work he tried going back to a basic
> distribution -- and everything started working again.
>
> It turned out that a maxusers value of
Matthew Dillon said:
> :maxusers 256
>
> Try reducing maxusers to 128. Another person reported similar behavior
> to me and after a bunch of work he tried going back to a basic
> distribution -- and everything started working again.
>
> It turned out that a maxusers value of
: Tuesday, February 16, 1999 7:48 AM
> To: Matthew Dillon
> Cc: Khetan Gajjar; curr...@freebsd.org
> Subject: Re: Problems in VM structure ?
>
>
> On Tue, 16 Feb 1999, Matthew Dillon wrote:
>
> > :maxusers 256
> >
> > Try reduc
[ CC trimmed ]
tc...@staff.circle.net wrote in message ID
:
> I've had it at MAXUSERS=256 on both the P5 and the P6. The P5 stays
> stable, the P6 doesn't. If I reduce MAXUSERS to 128 then these
> heavily loaded boxen will fall over due to out of MBUFs errors, or
> so I believe.
If you are runn
On Tue, Feb 16, 1999 at 12:19:07AM -0800, Matthew Dillon wrote:
> :maxusers 256
>
> Try reducing maxusers to 128. Another person reported similar behavior
> to me and after a bunch of work he tried going back to a basic
> distribution -- and everything started working again.
>
T
On Wed, Feb 17, 1999 at 08:46:49AM -0500, tc...@staff.circle.net wrote:
>
>
> > -Original Message-
> > From: Matthew Dillon [mailto:dil...@apollo.backplane.com]
> > :What's the chance that our kernel adaptations for PIIs
> > :is partly at fault?
> > :
> > :-Troy Cobb
> > : C
I've adjusted MAXUSERS to 128 on my heavily loaded PIIs and the crashes
have not re-occurred for 24 hours now. (Had to adjust NMBCLUSTERS up,
though)
The panics were happening every 5-8 hours like clockwork prior to this.
I believe that these crashes are caused by heavy network traffic, not
heavy
On Tue, 2003-10-14 at 17:21, Rossam Souza Silva wrote:
> Hi, I'm running 5.1-CURRENT (sources/ports from Oct/13) and
> the X package isn't compiling:
>
> FeaNoR# make package
> ===> Installing for XFree86-4.3.0,1
> ===> XFree86-4.3.0,1 depends on executable: xvinfo - not found
> ===>Verifyi
On Monday, 2 June 2003 at 10:54:06 +0930, Greg 'groggy' Lehey wrote:
> I've just cvsupped the latest -CURRENT, and it dies on me in
> gnu/usr.bin/gperf/doc:
*sigh*
Yes, of course I saw the dialogue between DES and obrien, and the
subsequent commit, so I re-supped and cvs updated and it still
hap
On Wed, Aug 13, 2003 at 01:44:15PM +0200, Robert Blacquière wrote:
> Hi,
>
> I have some problems getting wi cards working. I've traced the behavour
> of it.
>
> It assigns the first io memory 0x100-0x13f and the card fails to work.
> I plugin a second wi card and it gets 0x180-0x1bf and the ca
: Is there a better way to toggle the start address for 16 bit and 32 bit
: cards with sysctl??
u_long cbb_start_16_io = CBB_START_16_IO;
TUNABLE_INT("hw.cbb.start_16_io", (int *)&cbb_start_16_io);
SYSCTL_ULONG(_hw_cbb, OID_AUTO, start_16_io, CTLFLAG_RW,
&cbb_start_16_io, CBB_START_16_IO,
Mmhh,
must have been blind... i was looking for it a very long time (without
my eyes .)
Thanks !!!
Robert
On Thu, Aug 14, 2003 at 11:21:36PM -0600, M. Warner Losh wrote:
> : Is there a better way to toggle the start address for 16 bit and 32 bit
> : cards with sysctl??
>
> u_long cbb_s
Andrzej Kwiatkowski wrote:
Hello..
I would like to install 4.7-Release on my Intel 1210 server.
I've got Adaptec 2120s iserted and two 72Gb disk
configured as Raid 1. When i start to install everything is ok,
but when system boots i've got :
**MONITOR** NormPrioCommand was received with Fib Str
I had issues with 4.7 Release and the Adaptec 2120 as well. I installed
5.0 RC3 using the ISO image and both my 2120 and 2200 controllers are
working fine.
I don't know what use you are putting this server to, might CURRENT be a
solution? After compiling my kernel with out debugging options turn
On Thu, 16 Jan 2003, Matt Hartzell wrote:
> I had issues with 4.7 Release and the Adaptec 2120 as well. I installed
> 5.0 RC3 using the ISO image and both my 2120 and 2200 controllers are
> working fine.
>
> I don't know what use you are putting this server to, might CURRENT be a
> solution? Aft
On Thu, 16 Jan 2003, Scott Long wrote:
> This is a known issue that I am working on correcting. Right now there
> is no workaround that I know of. Stay tuned =-)
>
> Scott
What can i do ??
I want FreeBSD not Linux as my server...
and 4.7 is the best candidate for it...
Thanks in advance
Andrz
On Mon, Feb 10, 2003 at 11:20:24AM +0100, Gunnar Flygt wrote:
> Since it works with 4.7-STABLE it must(?) be a current problem
> more than a XFree86 problem. Or?
>
> Any suggestions?
>
> --
> Gunnar Flygt, SR
Could you paste your /var/log/XFree86*.log with the error parts? Maybe some will be
ab
> Since it works with 4.7-STABLE it must(?) be a current problem
> more than a XFree86 problem. Or?
I had the same problem -- something to do with files left
over from the original 4.7 installation. Cured by
deinstalling XFree86-* ports, renaming /usr/X11R6 to
something else (in case something wa
I've got a cheesy cigar-pro USB flash-drive (256MB) that works fine on
current (as of last night)
> -- Thus, Richard Nyberg had said:
> Hello current-users!
>
> I'm not having any luck getting my USB flash drive to work.
> The machine runs current as of today (24:th feb).
> Below is the output I
On Mon, Feb 24, 2003 at 03:11:14PM -0700, Ned Wolpert wrote:
> I've got a cheesy cigar-pro USB flash-drive (256MB) that works fine on
> current (as of last night)
Oh! I know that many other umass devices work ;)
What I meant to ask was if anybody knew how to make FreeBSD
to work with my creative n
-- Forwarded message --
Date: Fri, 28 Mar 2003 23:18:35 +0100 (CET)
From: Friedemann Becker <[EMAIL PROTECTED]>
To: Andris <[EMAIL PROTECTED]>
Subject: Re: Problems with clock
Try this one. I had the same problem, and de fix described put the clock
back to norm
On Sun, Jul 07, 2002 at 11:35:46PM +0200, Szilveszter Adam wrote:
> Hello everybody,
>
> I upgraded to yesterday's -CURRENT and have made a few observations:
> 2) and much more alarmingly: Although the new ipfw really seems to
> process the ruleset faster, some rules appear to do nothing! I
> ha
On Sun, Jul 07, 2002 at 04:45:52PM -0500, Richard Seaman, Jr. wrote:
> On Sun, Jul 07, 2002 at 11:35:46PM +0200, Szilveszter Adam wrote:
> > Hello everybody,
> >
> > I upgraded to yesterday's -CURRENT and have made a few observations:
>
> > 2) and much more alarmingly: Although the new ipfw real
On 03-Jun-01 Tony Fleisher wrote:
> I just tried to boot a -current kernel cvsupped
> at Sat Jun 2 14:11:35 PDT 2001, and was thrown
> the following error trying to boot to single-user
> (transcribed by hand):
>
> src/sys/kern/kern_sync.c:385 sleeping with "eventhandler"
> locked from src/sys
On Mon, 4 Jun 2001, John Baldwin wrote:
>
> On 03-Jun-01 Tony Fleisher wrote:
> > I just tried to boot a -current kernel cvsupped
> > at Sat Jun 2 14:11:35 PDT 2001, and was thrown
> > the following error trying to boot to single-user
> > (transcribed by hand):
> >
> > src/sys/kern/kern_sync.
On 05-Jun-01 Tony Fleisher wrote:
> On Mon, 4 Jun 2001, John Baldwin wrote:
>
>>
>> On 03-Jun-01 Tony Fleisher wrote:
>> > I just tried to boot a -current kernel cvsupped
>> > at Sat Jun 2 14:11:35 PDT 2001, and was thrown
>> > the following error trying to boot to single-user
>> > (transcrib
After blowing away my obj/ and src/ directories and
getting them fresh, this problem was no longer
present... not sure what caused them, but either
I had something strange in my obj/ or src/ tree,
or the problem was fixed in the last week.
Regards,
Tony.
On Mon, 4 Jun 2001, John Baldwin wrote:
Sun, Jun 24, 2001 at 09:25:22, stephen (Stephen Montgomery-Smith) wrote about
"Problems with md5 -p":
I reproduce it stably on my -current. The second checksum is constant
and it is MD5 checksum of an empty stream:
root@iv:/usr/HEAD/src/sbin/md5##md5 Suppose I have a file xxx. If I type
>
OK, I'm going to make this into a PR so that it gets fixed soon. (The
problem in stable appeared between May 19 and June 16.)
Valentin Nechayev wrote:
>
> Sun, Jun 24, 2001 at 09:25:22, stephen (Stephen Montgomery-Smith) wrote about
>"Problems with md5 -p":
>
> I reproduce it stably on my -c
Sun, Jun 24, 2001 at 13:16:07, stephen (Stephen Montgomery-Smith) wrote about "Re:
Problems with md5 -p":
> OK, I'm going to make this into a PR so that it gets fixed soon. (The
> problem in stable appeared between May 19 and June 16.)
Yes, it appeared with commits:
r
On 14-Dec-01 Luigi Rizzo wrote:
> With a freshly cvsupped version of CURRENT, cross-compiled on a
> 4.3 box, (after the usual stdio.h fix related to the FILE handling),
> I am having problems compiling several programs, with errors such
> as the ones attached at the end.
Just use WARNS=0 or some
On Tue, Dec 05, 2000 at 11:06:12AM +0300, Hostas Red wrote:
> I have a following problem in making world for some time already:
...
> Any suggestions?
rm -rf /usr/obj/*
cd /usr/src && make cleandir
update your /usr/src and try again
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscr
Hi!
On Tue, 5 Dec 2000, David O'Brien wrote:
> On Tue, Dec 05, 2000 at 11:06:12AM +0300, Hostas Red wrote:
> > I have a following problem in making world for some time already:
> ...
> > Any suggestions?
>
> rm -rf /usr/obj/*
> cd /usr/src && make cleandir
> update your /usr/src and try again
Ilya Naumov wrote:
> i have installed today's world and now cannot compile almost anyting (incuding the
>same world) because as (gnu assembler) coredumps every time.
>
> it could be because of the older kernel (built yesterday), but i cannot recomile it
>due to the problem described above. any
In message <[EMAIL PROTECTED]> Ilya Naumov writes:
: i have installed today's world and now cannot compile almost anyting (incuding the
:same world) because as (gnu assembler) coredumps every time.
A patch was installed to fix this. If you can grab an old as, you can
fix this with a recompile o
It seems Theo van Klaveren wrote:
>
> When installing the 08-dec-1999 snapshot (before ATA went in GENERIC),
> a recompile from the kernel with the ATA driver instead of the WD
> driver resulted in an unbootable system because of the following
> error (approx.):
>
> mounting root /dev/ad0s1a
>
On Tue, 21 Dec 1999, Soren Schmidt wrote:
> > Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
> >Western Digital Caviar (2.5 GB), DMA-33.
> > Mainboard: Asus P5A-B Super7
> > Chipset: ALi Aladdin V AGPset
>
> It probably because I relaxed the requirements for doing WDMA on di
It seems Theo van Klaveren wrote:
> On Tue, 21 Dec 1999, Soren Schmidt wrote:
>
> > > Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
> > >Western Digital Caviar (2.5 GB), DMA-33.
> > > Mainboard: Asus P5A-B Super7
> > > Chipset: ALi Aladdin V AGPset
> >
> > It probably becau
Soren Schmidt writes:
> It seems Theo van Klaveren wrote:
> > On Tue, 21 Dec 1999, Soren Schmidt wrote:
> >
> > > > Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
> > > >Western Digital Caviar (2.5 GB), DMA-33.
> > > > Mainboard: Asus P5A-B Super7
> > > > Chipset: ALi
On Tue, 21 Dec 1999, Soren Schmidt wrote:
> > Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
> >Western Digital Caviar (2.5 GB), DMA-33.
> > Mainboard: Asus P5A-B Super7
> > Chipset: ALi Aladdin V AGPset
>
> It probably because I relaxed the requirements for doing WDMA on di
It seems Doug White wrote:
> >
> > It probably because I relaxed the requirements for doing WDMA on disks
> > that doesn't bother to tell whihc verson of the ATA spec they conform to.
> > I think your case is the more seldom one, but I'm this close to
> > blacklisting all WD/Maxtor drives, that w
Theo van Klaveren wrote:
>
> When installing the 08-dec-1999 snapshot (before ATA went in GENERIC),
> a recompile from the kernel with the ATA driver instead of the WD
> driver resulted in an unbootable system because of the following
> error (approx.):
>
> mounting root /dev/ad0s1a
> ata-mast
:> it broke again as I recompiled my system yesterday (This was the first
:> time after it had been fixed, so I don't know when exactly it broke).
:>
:> Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
:>Western Digital Caviar (2.5 GB), DMA-33.
:> Mainboard: Asus P5A-B Super7
:
It seems Peter Wemm wrote:
>
> Same here, but with a toshiba laptop disk. I have to comment out a version
> test in ata-disk.c to get it to work.
I've just a few hours ago committed a change that does this...
>
> --- ata-disk.c 1999/12/18 20:06:30 1.46
> +++ ata-disk.c 1999/12/21 21:48:2
It seems Matthew Dillon wrote:
>
> The thread 'vm_page_remove panic' that Tamiji Homma initiated may be
> related. She is getting a panic in the buffer cache subsystem while
> using the new ATA driver with softupdates + NFS exported filesystems.
>
> I do not know if it is relat
On Tue, 21 Dec 1999, Soren Schmidt wrote:
> It probably because I relaxed the requirements for doing WDMA on disks
> that doesn't bother to tell whihc verson of the ATA spec they conform to.
> I think your case is the more seldom one, but I'm this close to
> blacklisting all WD/Maxtor drives, tha
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: at device 7.1 on pci0
> ata-pci0: Busmastering DMA supported
> ata0 at 0x0
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 ve
> 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
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.
>
> > 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: Mak
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
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 n
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
101 - 200 of 709 matches
Mail list logo
