On Tue, 18 May 1999 17:04:56 MST, Doug White wrote:
> Fixed it earlier this week or last week in v1.63 (14 May) of
> /sys/ufs/mfs/mfs_vfsops.c. Resup.
I don't think so. Your changes didn't stop the panic for me. What _did_
fix it was Luoqi's change yesterday to kern_conf.c .
John, make sure yo
On Wed, 19 May 1999 12:04:54 +1000, Bruce Evans wrote:
> >dumping to dev (0, 131089), offset 524288
> >dump device bad
>
> The dev_t changes obfuscated it by printing it in %d format instead of
> as part of the dev number in [0x]%x format.
So you reckon that whatever problem is making it imp[o
Jonathan Lemon says:
:
: Not true. VM86 is also required to support VESA. Also, it is used
: for reliable memory detection (which is why I want to make it mandatory).
: No more "My Stinkpad only detected 64M, what do I do now??!" questions.
Actually, even with VM86, the kernel still doesn't co
>> >dumping to dev (0, 131089), offset 524288
>> >dump device bad
>>
>> The dev_t changes obfuscated it by printing it in %d format instead of
>> as part of the dev number in [0x]%x format.
>
>So you reckon that whatever problem is making it imp[ossible for me to
>take dumps, it was present before
On Wed, 19 May 1999 17:40:50 +1000, Bruce Evans wrote:
> so you must be using the old wd driver. The old wd_driver's d_dump
> only returns ENXIO when the drive doesn't exist or has never been
> opened or is not labeled.
I'm using the "old" wd driver (controller wdc in CURRENT). The disk is
lab
Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I want
to allow mtrr support for my Voodoo Banshee)
Stephen
--
The views expressed above are not those of PGS Tensor.
"We've heard that a million monkeys at a million keyboards could produce
the Complete
On 19-May-99 Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:
> Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I want
> to allow mtrr support for my Voodoo Banshee)
I don't think its supported for the K6 (it only happens if you have i686). You
can use it by playi
On Wed, May 19, 1999 at 01:20:01AM +0930, Matthew Thyer wrote:
>I have confirmed that the problem occurs if I just do:
>
> xsetpointer Joystick
> sleep 1
> xsetpointer pointer
>
>So M.A.M.E. is unrelated to the problem as Bruce Evans would suggest.
>
>So the problem appears to be with XFree86 no
No offense, but can we use something like "assigning" in place of the
rather loaded word "hanging?" I can just see the user bug reports now;
"My root device is hanging! It says so every time I boot! HELP!" :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd
> No offense, but can we use something like "assigning" in place of the
> rather loaded word "hanging?" I can just see the user bug reports now;
> "My root device is hanging! It says so every time I boot! HELP!" :)
Or better still, revert to printing the SCSI probe results on a line break,
rathe
im -current, lat build world was two days ago, it seems like in the past week
some1 has messed with the Voxware sound drivers, until last week i used a
SB-Pro emulation with Voxware, and it worked fine, now it still works, but
there are some annoying poping sound in the background (works FINE in w
i've been using the ATA driver for a while now, but since my last word & kernel
i get "WARNING: / was not properly dismounted" at the end of the dmesg and i
have to fsck /.
my last world was about 2 dayz ago.
dmesg output for that ATA driver :
ad1: ATA-4 disk at ata0 as slave
ad1: 6149MB (12
> Jonathan Lemon says:
> :
> : Not true. VM86 is also required to support VESA. Also, it is used
> : for reliable memory detection (which is why I want to make it mandatory).
> : No more "My Stinkpad only detected 64M, what do I do now??!" questions.
>
> Actually, even with VM86, the kernel st
Heh. Well, then you would have people asking you what "ssigning" root
devices means :)
The message seems to get garbled when the CAM probes (being done in the
background) emit their messages. The "c" in my "changing" creates a new
device called cda4 in my log file:
Waiting 5 seconds for SCSI d
Same settings under Windows and same I have used under Linux [with the 2.2
kernels].
Tom Veldhouse
ve...@visi.com
-Original Message-
From: Doug White
To: Thomas T. Veldhouse
Cc: FreeBSD-Current
Date: Tuesday, May 18, 1999 7:10 PM
Subject: Re: Sound Strangeness
>This is usually indici
The problem is that recent versions of MS-DOS (version 7 and above ?
...definitely the DOS that comes with Windows 98 and I think the DOS
with Windows 95 under some circumstances) change various vectors which
destroy FBSDBOOTs ability to work (this is because there is no way to
determine where thes
The big problem is that the silo overflows continue after I have
returned the pointer to the mouse (with "xsetpointer pointer").
This should close the joystick device shouldn't it ?
If it doesn't then there is a problem with either the X server
or FreeBSD.
Bruce has already indicated that there
Matthew Thyer wrote:
> Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22
> boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel
> and hence the whole system.
Obviously it makes no sense at all to make special DOS boot floppy with older
DOS
just to run FBSDBOOT
> No offense, but can we use something like "assigning" in place of the
> rather loaded word "hanging?" I can just see the user bug reports now;
> "My root device is hanging! It says so every time I boot! HELP!" :)
Actually, it says "changing", but the 'c' gets printed and then all of
the inter
> > Jonathan Lemon says:
> > :
> > : Not true. VM86 is also required to support VESA. Also, it is used
> > : for reliable memory detection (which is why I want to make it mandatory).
> > : No more "My Stinkpad only detected 64M, what do I do now??!" questions.
> >
> > Actually, even with VM86,
In message <199905171500.jaa22...@mt.sri.com> Nate Williams writes:
: The solution is to not poll and to make sure insertion/removal events
: generate an interrupt which can inform the card's interrupt handlers
: that there is no more card.
:
: (That's one of the main reasons polling is a very bad
Steven Ames wrote:
>
> *sigh* No suprise here. As 90% of these things are this was yet
> another Dumb User Error. I had a base address conflict that kept
> the card from being probed.
So, can we say it was due? ;-)
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.
> Not at all. If there's 640k chopped off the end of eg. 128M of
> physical memory, you'd have to use a 64M segment, a 32M segment, a 16M
> segment, an 8M segment, a 4M segment, a 2M segment, a 1M segment, a
> 256k segment and a 128k segment to map it accurately. That's 9
> variable MTRRs, an
> > Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22
> > boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel
> > and hence the whole system.
>
> Obviously it makes no sense at all to make special DOS boot floppy with older
> DOS
> just to run FBSDBOOT - it sim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have installed 4.0-CURRENT however, It seems that wdm is still broken.
Here is the tail end of a make install for wdm:
ras# make install > tmp
ras# more tmp
===> Extracting for wdm-1.0
>> Checksum OK for wdm/wdm-1.0.tar.gz.
>> Checksum OK for wdm/d
On May 05, 1999 at 03:38:05AM -0400, Jerry Alexandratos wrote:
> Jonathan Lemon says:
> :
> : Not true. VM86 is also required to support VESA. Also, it is used
> : for reliable memory detection (which is why I want to make it mandatory).
> : No more "My Stinkpad only detected 64M, what do I do
> > Not at all. If there's 640k chopped off the end of eg. 128M of
> > physical memory, you'd have to use a 64M segment, a 32M segment, a 16M
> > segment, an 8M segment, a 4M segment, a 2M segment, a 1M segment, a
> > 256k segment and a 128k segment to map it accurately. That's 9
> > variable
> > > Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22
> > > boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel
> > > and hence the whole system.
> >
> > Obviously it makes no sense at all to make special DOS boot floppy with
> > older DOS
> > just to run FBS
On May 05, 1999 at 12:27:31PM -0700, Mike Smith wrote:
> The issue here is that the BIOS will tell us how much memory we are
> _allowed_to_use_, which is not always the same as the amount of
> physical memory present in the system. Some memory may be (is
> sometimes) reserved for use by eg. APM
On Tue, May 18, 1999 at 11:48:40PM -0700, Archie Cobbs wrote:
> Vallo Kallaste writes:
> > > - History buffer (back-scroll buffer) management functions are moved
> > > to a new file, schistory.c.
> >
> > My question is slightly off-topic, but.. is it now possible (or in the
> > future) to choose
> > > > Therefore it *MAY* be possible to make a DOS 6.0, 6.20 or even 6.22
> > > > boot floppy which runs FBSDBOOT.EXE to boot your a.out FreeBSD kernel
> > > > and hence the whole system.
> > >
> > > Obviously it makes no sense at all to make special DOS boot floppy with
> > > old
> er DOS
> > >
May I suggest to add the XFree86 aout libraries to src/compat, or to
add them as port - for easy update via make.
Background:
Netscape 4.6 installation complained that I need X11 aout libs,
so I had to download xlib.tgz (3.3M) just for the aout libs (0.7M).
Or am I missing some opportunity else
>
> Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I want
> to allow mtrr support for my Voodoo Banshee)
It's being worked on. The K6 is a problematic device, as it only
supports two memory ranges, as opposed to the eight the P6 does.
--
\\ The mind's the standard
Thanks to all who pitched in their input to this issue. Most users of my
system are running Windows and don't want to have to reformat or repartition
their hard disk. So I am stuck with the DOS file system. I think the best
solution is to have my users use a FreeBSD boot floppy. The floppy will hav
The pccard code kinda sorta works on some systems, but not on others.
The support for sio and fdc no longer works on any system. I'm
working on a rewrite in the new bus framework. I have pcic
interrupting now, and hope to have I/O and memory mapping working
again to allow pccards to work again sh
In message Doug
Rabson writes:
: The sio support will need to wait until Warner Losh commits his changes to
: clean up the pccard driver.
I'm hoping to have this done before I take off for Memorial Day
weekend.
Warner
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebs
In article <199905191637.jaa03...@dingo.cdrom.com> you wrote:
> I'm not sure why it happens like this; try putting a DELAY() just
> before we actually set the root device and see if you can put it off.
Why not just spl() protect that printf call so that its output is
dumped contiguously into the
calcru() access p_stats, which is in upages. Therefore, as I understand,
it should not be called on a swapped out process. Neither calcru() nor
its callers seem to ensure this. At least the call in procfs_dostatus()
may happen on a swapped out process. (It test for P_INMEM for another
access to
Sounds like you want something like a FreeBSD version of DOS Linux. See
http://www.tux.org/pub/people/kent-robotti/index.html. How do they
overcome this problem?
Greg
At 02:45 PM 5/19/99 -0700, Carlos C. Tapang wrote:
>Thanks to all who pitched in their input to this issue. Most users of my
>sy
On Wed, 19 May 1999, Luoqi Chen wrote:
> > Jonathan Lemon says:
> > :
> > : Not true. VM86 is also required to support VESA. Also, it is used
> > : for reliable memory detection (which is why I want to make it mandatory).
> > : No more "My Stinkpad only detected 64M, what do I do now??!" quest
>> Well, I'll recheck mine...
> It'd be interesting to see if you (and others) can reproduce this too.
Using a May 17 15:00 CDT -current, I also have gotten a panic mounting
MFS. The line from fstab is:
/dev/da0s2b /tmpmfs rw 0 0
I commented it out
Some of you may already know this - I'm wondering about the pain involved in
fitting it to our architecture. Journaling. Hmmm.
http://www.news.com/News/Item/0,4,36807,00.html?owv
--
The views expressed above are not those of PGS Tensor.
"We've heard that a million monkeys at a million k
42 matches
Mail list logo
