Hi,
a few things to note:
- Loading the new kernel & acpi.ko with the old loader freezes the loader.
- Loading acpi.ko by hand with the new loader freezes or endless-loops the loader.
- Letting the new loader using the acpi.ko brings the system up and running except my
sound-system
(missing eq
/usr/src/sys/modules/aac/../../dev/aac/aac.c: At top level:
/usr/src/sys/modules/aac/../../dev/aac/aac.c:1976: warning: `aac_describe_code' was
used with no prototype before its definition
/usr/src/sys/modules/aac/../../dev/aac/aac.c:1976: conflicting types for
`aac_describe_code'
/usr/src/sys/m
On Thu, 30 Aug 2001 08:12:42 -0500, Michael Harnois <[EMAIL PROTECTED]> said:
> /usr/src/sys/modules/aac/../../dev/aac/aac.c: At top level:
> /usr/src/sys/modules/aac/../../dev/aac/aac.c:1976: warning:
> `aac_describe_code' was used with no prototype before its
> definition /usr/s
[Bcc'ed to -current]
Hi!
The current implementation of find(1) -flags primitive is a bit
icky and does not match the (poorly) documented behavior. For
example, the fact that only a certain set of file flags is recognized
is not documented, and there is no reason for this behavior. Also,
"no" f
> Hi,
> a few things to note:
> - Loading the new kernel & acpi.ko with the old loader freezes the loader.
> - Loading acpi.ko by hand with the new loader freezes or endless-loops the lo
> ader.
I've no idea what's going on here; I used a Tecra 8000 for much of my
testing, and never saw this. 8(
(repost, it didn't like me cross-posting to the -alpha and -ia64 lists.
sigh).
I'm going to be comitting the following changes soon:
syscalls.master: (going in now)
Instead of having an MPSAFE keyword, existing keywords such as STD
can be augmented with an
On 30-Aug-2001 Alexander N. Kabaev wrote:
| Freshly cvsuped kernel fails to build trying to find acpi_isa.c file, which
| does not exist anymore.
The following patch I sent to Mike allows the kernel to build.
Index: modules/acpica/Makefile
=
> On 30-Aug-2001 Alexander N. Kabaev wrote:
> | Freshly cvsuped kernel fails to build trying to find acpi_isa.c file, which
> | does not exist anymore.
>
> The following patch I sent to Mike allows the kernel to build.
The files omission has been fixed; the 'acpica' module has moved to
become
I'm in the process of getting set up for testing KSE too, but I was wondering, how are
you capturing the panic dump? Do you run a
serial console or something to do it?
Carlo Dapor wrote:
>>can you try the same with a "matching" -current?
>>I heard that msdosfs is bombing there too.
>>(just to
>Date: Wed, 29 Aug 2001 19:58:59 -0700
>From: Mike Smith <[EMAIL PROTECTED]>
>The loader now detects ACPI in your system, and loads the ACPI
>module if it is present. This has major ramifications for the
>device probe and attach phases of system initialisation.
Flushed with the success of getti
As Philipp Mergenthaler wrote:
> I saw something like this some time ago, too. In my case it was
> because in kern_sysctl:ogetkerninfo(), in "case KINFO_BSDI_SYSINFO:",
> the variable "size" is not always given a value. Maybe the patch in
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=25476
> fix
> can you try the same with a "matching" -current?
> I heard that msdosfs is bombing there too.
> (just to confirm this.. if it works there but not with KSE
> then we have work to do :-)
I build and run a kernel just before applying the patches, that was able to
mount the partition and 'accepted'
Freshly cvsuped kernel fails to build trying to find acpi_isa.c file, which
does not exist anymore.
On 30-Aug-2001 Mike Smith wrote:
>
> I have just committed some changes to the way that ACPI works in
> current. This has an impact on all -current users, so please
> take a few seconds to read
> On Thu, 30 Aug 2001 08:12:42 -0500, Michael Harnois <[EMAIL PROTECTED]> said:
>
>> /usr/src/sys/modules/aac/../../dev/aac/aac.c: At top level:
>> /usr/src/sys/modules/aac/../../dev/aac/aac.c:1976: warning:
>> `aac_describe_code' was used with no prototype before its
>> definitio
thanks..
I will try duplicate this tomorrow
(today is shaping up to be a bad day)
On Thu, 30 Aug 2001, Carlo Dapor wrote:
> > can you try the same with a "matching" -current?
> > I heard that msdosfs is bombing there too.
> > (just to confirm this.. if it works there but not with KSE
> > th
Houston, we have a . . .
I confirm that with the 'normal' current module sources mount_msdosfs collabo-
rates with me, successfully.
I did not set anything up. I simply get mails to root, like the one
pasted earlier on. In fact, I didn't even think that crash was reported
via mail to root . .
I can not reproduce this with a memory disk image of an msdos floppy
(I do not have a floppy on that machine)
can you try accessing the floppy without mounting?
e.g. can you try using it as a raw device with TAR or something?
Maybe it's the floppy driver rather than tehe filesystem.
If you can
The easiest way is to have a serial console.
that is VERY easy to do.
simply add the line
console="comconsole"
to the file /boot/loader.conf
After that you can also work on getting core-dumps (man dumpon)
and use gdb to get backtraces etc.
Some machines don't clear all of ram so "dmesg" can so
Hi,
I'm getting the following when trying to build lsof:
>> Checksum OK for lsof_4.58A.freebsd.tar.gz.
grep: README.lsof_4.58A.freebsd: No such file or directory
md5: lsof_4.58A.freebsd.tar: No such file or directory
lsof_4.58A.freebsd.tar.gz: No such file or directory
This configuration step (
Hackers,
Below some patches that implements device cloning (with devfs(5)
support) for tap(4) device. The implementation is based on resource
manager (just like tun(4) and gif(4)). Please review, test and if
there is no objection commit. If there are any problems, please let
me know.
http://ho
On 31-Aug-01 Peter Wemm wrote:
> Julian Elischer wrote:
>> The diff file is updated automatically one per hour
>> from the P4 repository that we are working on.
>> it IS possible that yuo might catch it at a time when what is in teh
>> repository may not match what is in -current but generally th
The following ipfw commands produce an error.
Could we make this work:
ipfw add allow udp from any to any lowport,higherport1-higherport2
Instead of
ipfw add allow udp from any to any highport1-highport2,lowpot
Could we make this work:
ipfw add allow udp from any to any range1-range2, range3
The medium I mount is a hard disk partition.
/dev/ad0s1 is my win98 boot drive, /dev/ad0s2* my FreeBSD world.
It has worked for almost a year, never had a crash or lost a single byte.
I can go back to the kse kernel, and remount Win98, with the instructions
You just posted.
Ciao, derweil,
--
Car
As Philipp Mergenthaler wrote:
> I saw something like this some time ago, too. In my case it was
> because in kern_sysctl:ogetkerninfo(), in "case KINFO_BSDI_SYSINFO:",
> the variable "size" is not always given a value. Maybe the patch in
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=25476
> fix
What you are doing doesn't work for sure. You are piping in and out of
the control enpoint which won't work. Perhaps
/usr/sbin/ppp -quiet -direct -nat <> /dev/ugen0.1
would work, if there is an endpoint 1-in and an endpoint 1-out and they
are both related to data transfer. Normally this
Julian
How often do You plan to produce diff files ?
I can not spend too much time in the next 2 to 3 weeks, since I will be travel-
ling most of the time.
Ciao, derweil,
--
Carlo
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 30 Aug, Nick Hibma wrote:
> /usr/sbin/ppp -quiet -direct -nat <> /dev/ugen0.1
>
I was confused by the following from ppp's man-page:
-direct
This is used for receiving incoming connections. ppp ignores
the ``set device'' line and uses descriptor 0 as t
The diff file is updated automatically one per hour
from the P4 repository that we are working on.
it IS possible that yuo might catch it at a time when what is in teh
repository may not match what is in -current but generally that should not
last to long.
(depends on how often one of us does an M
Julian Elischer wrote:
> The diff file is updated automatically one per hour
> from the P4 repository that we are working on.
> it IS possible that yuo might catch it at a time when what is in teh
> repository may not match what is in -current but generally that should not
> last to long.
> (depen
At 03:46 PM 8/30/2001 -0700, jkh wrote:
>*
>* The projected ship date for FreeBSD 5.0-RELEASE is now November 1st, 2002 *
>*
While I'd like to se
Robert Watson <[EMAIL PROTECTED]> writes:
> rwatson 2001/08/30 19:12:00 PDT
>
> Modified files:
> lib/libc/posix1e cap_text.c
> Log:
> o Remove definition of CAP_MAX_BUF_LEN since it is defined in
> sys/capability.h now.
>
> Submitted by: tmm
> Obtained
> | Most systems with soft power will perform a hard powerdown if you hold
> | down the power button for a sufficiently long period of time (10 - 20
> | seconds).
>
> Correct ... and unfortunately it's done in hardware so you can trap it :-(
> In some applications you want to make it really hard
> > > - I pushed the power button, and my system shut down cleanly!
> >
> > > Yes. ACPI brings some useful new features. 8)
> >
> > FSVO ``useful''. It's a real PITA to have to physically unplug the
> > machine when the kernel is wedged rather than have the power button
> > turn off the power
On Wed, 29 Aug 2001, Robert Watson wrote:
> On Wed, 29 Aug 2001, Garrett Wollman wrote:
> > FSVO ``useful''. It's a real PITA to have to physically unplug the
> > machine when the kernel is wedged rather than have the power button
> > turn off the power. (The machine in question does not have a
Ok, this is the 3rd revised patch for PnP. I think it works
fairely well.
I may not invest further time on this, now that ACPI is
taking over device configuration business... :-)
Kazu
>> I once wrote the following patch to deal with this problem by
>> probing ISA devices in the following order
35 matches
Mail list logo
