With the recent slaughter^Wrework of the PCI code, my hack to allocate
resources for unattached PCI devices in pci_probe_nomatch() no longer works.
The updated patch can be found at
http://www.FreeBSD.org/~jhb/patches/cardbus.hack.patch.
I have a set of working patches at
I have a set of working patches at
http://ziplok.dyndns.org/msmith/pci.diff
which handle resource reservation, making your hack unnecessary. They're
not ready for commit yet, but they're known to work (assuming you get
this message 8).
Cool, my hack is all b0rked
From: Michael Harnois [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 12, 2000 6:31 AM
On Tue, 12 Dec 2000 05:02:59 -0800, Mike Smith
[EMAIL PROTECTED] said:
I'll keep working on this one; things will go a lot faster if I
can get my hands on a system
with the code, I'd be more
than happy to point you at a few things worth checking out.
Regards,
Mike
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships
going on. Sorry about this.
Regards,
Mike
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr
it goes on / or /usr is actually a minor issue. I want
packages installed on /usr. If the standard winds up being /opt, I'll
just symlink /opt to /usr/opt, and forget it. Likewise, if the
standard is /usr/opt, you can symlink /usr/opt to your file system on
/opt, and forget it.
mike
To Unsubscribe:
On Sun, Dec 10, 2000 at 03:15:19AM -0800, Mike Smith wrote:
msmith 2000/12/10 03:15:19 PST
Modified files:
sys/dev/pci isa_pci.c
Log:
The ICH2 reports itself as a PCI:ISA bridge, so don't special-case it
here.
On a related(?) note, my 810 (ICH
);
pci_enable_io(dev, SYS_RES_IOPORT | SYS_RES_MEMORY);
pci_set_powerstate(dev, PCI_POWERSTATE_D0);
Consider the above a request for review on the matter.
Regards,
Mike
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also
David O'Brien [EMAIL PROTECTED] types:
On Sun, Dec 10, 2000 at 11:33:33PM -0600, Mike Meyer wrote:
The thing is, the package system has grown into something more than
that. It really is vendor-supplied and vendor-supported third party
software, and part of the distribution.
I can back
David O'Brien [EMAIL PROTECTED] types:
On Mon, Dec 11, 2000 at 08:14:47AM -0600, Mike Meyer wrote:
The problem is that the shared libraries aren't getting found when I
run the applix binary after a reboot.
Why do you say that? Where is the error message??
I say that because 1
pci_enable_busmaster(dev);
pci_enable_io(dev, SYS_RES_IOPORT | SYS_RES_MEMORY);
pci_set_powerstate(dev, PCI_POWERSTATE_D0);
Consider the above a request for review on the matter.
Shouldn't that be:
pci_enable_io(dev, SYS_RES_IOPORT | SYS_RES_MEMORY);
David O'Brien [EMAIL PROTECTED] types:
On Mon, Dec 11, 2000 at 05:24:19PM -0600, Mike Meyer wrote:
At that point, you're running VistaSource's software, so they should
give you the details.
Then I'll just back out of trying to help figure out why many others can
run it outside of /usr
W, pkg_add (at least) honors the environment variable PKG_DBDIR to
set the location of the ports metadata directory. Is there some reason
you can't just set that to /usr/local/etc/db/pkg or some such?
Final comment - I wish more ports developers *would* set PREFIX.
mike
To Unsubscribe:
David O'Brien [EMAIL PROTECTED] types:
On Sun, Dec 10, 2000 at 11:42:37PM -0600, Mike Meyer wrote:
On the other hand, Applixware Office ships a precompiled package for
/usr/local, and doesn't like being installed anywhere else. Which
means I've got a couple of hundred megabytes being
Warner Losh [EMAIL PROTECTED] types:
In message [EMAIL PROTECTED] Mike Meyer writes:
: I know. Unfortunately, support for PREFIX seems to draw more lip
: service than actual service.
Actually, which ports, specically, doesn't this work with? I've
installed several ports with PREFIX defined
Daniel C. Sobral [EMAIL PROTECTED] types:
Mike Meyer wrote:
Rant second: FreeBSD *violates* years of traditions with it's
treatment of /usr/local. /usr/local is for *local* things, not add-on
software packages! Coopting /usr/local for non-local software creates
needless complexity
Garrett Wollman [EMAIL PROTECTED] types:
On Sun, 10 Dec 2000 09:37:53 -0600 (CST), Mike Meyer [EMAIL PROTECTED] said:
However, FreeBSD is still the only vendor distribution I know of that
installs software in /usr/local. That's the problem - software that
comes from the vendor doesn't
Joe Kelsey [EMAIL PROTECTED] types:
Mike Meyer writes:
If memory serves (and it may not at this remove), /usr/local/bin
wasn't on my path until I started using VAXen, meaning there were few
or no packages installing in /usr/local on v6 v7 on the 11s.
If you remember v6 and v7
ing "local" things are pointed directly at
/usr/local; none of them check LOCALBASE.
All of these would be solved if the FreeBSD took a lesson from their
peers. Most of them could be solved without changing the default value
for LOCALBASE - if people wanted them solved.
mike
Nat Lanza [EMAIL PROTECTED] types:
Mike Meyer [EMAIL PROTECTED] writes:
Whether or not it's part of FreeBSD is immaterial. It's part of the
distribution that comes from FreeBSD, and is treated differentlyh from
locally installed software (whether written locally or by a third
party
Brian Dean [EMAIL PROTECTED] types:
On Sun, Dec 10, 2000 at 01:02:09PM -0600, Mike Meyer wrote:
The problem is that *it doesn't work*. Well, not very well. Part of it
is that it's only given lip service: the porters handbook says "make
your ports PREFIX clean"; portlint does
Joe Kelsey [EMAIL PROTECTED] types:
Mike Meyer writes:
Sure, the software in ports/packages aren't part of FreeBSD. Using
that to claim they should have the same status or treatment as locally
written or maintained software is a rationalization.
You are simply wrong in your
t decision. That this is the case says a lot about the
implementation of that design, none of it good.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
)) is thus completely justified.
Do you understandy why NetBSD's Packages install in /usr/pkg ?
What is your position behind that?
I have no problem with /usr/pkg. I personally do not see the need for
it. I have been arguing with Mike over his historic characterization of
/usr/local
scripts provided
by FreeBSD in /root add /usr/local/bin, *not* $(LOCALBASE)/bin. So
such runtime dependencies don't break for users, but do for root -
which means they are more likely to be noticed if they are build
dependencies than if they are run dependencies.
mike
To Un
en I asked, no one
with the commit bit actually runs systems using PREFIX that
way. Providing an untested "solution" isn't a good thing.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
David O'Brien [EMAIL PROTECTED] types:
On Sun, Dec 10, 2000 at 02:19:12PM -0600, Mike Meyer wrote:
I intend "LOCALBASE clean" to mean "all files installed by other ports
are looked for in the LOCALBASE tree".
If all ports are PREFIX clean, you will have that.
what *packages* are, not what
/usr/local was used for.
By your own admission, /usr/local wasn't used on v7. So the discussion
should turn to when BSD started seeing prebuilt vendor packages to
install in /usr/local.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &
Andrew Reilly [EMAIL PROTECTED] types:
On Sun, Dec 10, 2000 at 12:31:10PM -0600, Mike Meyer wrote:
Not /usr/local - that's for locally maintained software. I'd rather it
go on /usr, so I don't like /opt. When I got to choose, I chose
/usr/opt. But anything other than /usr/local on /usr
another some of us want - quite
legitimately - want to treat those two things differently, and
packages using a directory name that has an established use makes that
difficult.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
differently, and
packages using a directory name that has an established use makes that
difficult.
Not true. You can change the source to point to
'/usr/mike-likes-it-here', and it *should* work. If it doesn't, then
it's borken. :)
True. I can also go through and fix everything in FreeBSD
ytes being backup up for no
good reason :-(.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
do with them. That's not true
for FreeBSD packages.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
complexity and confusion, which of course leads to needless
pain.
All of which has nothing to do with the question of whether we want to
continue giving error messages that are wrong, or commit this patch
and provide ones that are actually informative.
mike
To Unsubscribe: send mail to [EMAIL
fixed.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Unix/FreeBSD consultant,email for more information.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
David O'Brien [EMAIL PROTECTED] types:
On Sat, Dec 09, 2000 at 01:59:51PM -0600, Mike Meyer wrote:
I know. Unfortunately, support for PREFIX seems to draw more lip
service than actual service.
I disagree. If one of the ports I maintain isn't PREFIX-clean, let me
know and it _will_
On Fri, Dec 08, 2000 at 03:44:28AM +0200, Tomi Vainio - Sun Finland - wrote:
sense = 3 asc = 11 asq = 0
This is not so bad but 5-30 minutes after this command system will
always panic.
Are you surprised? The system is complaining that it's having intermittent
difficulty accessing
We got old Mylex DAC960PD-Ultra-raid-adapter and have tried to use it
with FreeBSD 4.2-stable and 5.0-current. Adapter is configured with
three luns 5+5*9G, 8+8*9G (raid5) and 1+1*2G (mirrored boot disk).
All 9G disks are quite old Seagate Barracuda 9 disks ST19171W. System
is working quite
I'm trying to write some experimental mutex operations similar to those
in -current, but to do differnt things (e.g. a read/write lock)
however, I am having some problems with the __asm stuff.
Julian; Wheels were invented around 1500BC. We don't need to go through
all that again.
--
...
Modified files:
sys/dev/acpica acpi.c acpi_button.c acpi_ec.c acpi_isa.c
acpi_lid.c acpi_pcib.c acpi_processor.c
acpi_resource.c acpi_thermal.c
acpi_timer.c acpiio.h acpivar.h
Log:
- Convert a
So you can use it either with hardware RAID controllers which allow for
non destructive extending of the size of existing volumes at the end(!).
Cool. We support the FlexRAID Virtual Sizing stuff on the AMI
controllers already, and I bet that the Mylex MORE stuff would work too.
*
This is not so bad but 5-30 minutes after this command system will
always panic.
cd /uu ; dump 0buf 126 - /w | restore xbf 126 -
mode = 0100644, inum = 720391, fs = /uu
panic: ffs_valloc: dup alloc
This looks like memory or PCI data corruption. You don't say how
Since all I WANT to do is
pushf
disable intr
fiddle
popf (chache hit)
I am annoyed by the fact that I have all those extra bus cycles going on.
I can live with it for development but it still annoys me.
You haven't yet explained how you plan to disable interrupts on the other
CC: to -current as that's what I'm running.
"John W. De Boskey" wrote:
Hi,
I can't answer your questions directly, but you might want
to checkout the sources to newfs (/usr/src/sbin/newfs/newfs.c or
http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sbin/newfs/newfs.c?annotate=1.31
Mike Smith wrote:
The program works on Compaq True64 UNIX v 4.0d
It also works on Solaris 7 (only tested sparc).
So it seems FreeBSD is broken here.
FreeBSD just behaves differently. If you want to write to the whole
disk, open the whole-disk device, not the 'c' partition
Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G.
3com 3c410, or D-Link DHN-520?
No; as far as I'm aware they're all using the Broadcom MAC, and Broadcom
refuse to give us documentation.
--
... every activity meets with opposition, everyone who acts has his
rivals
In my bios I have PnPOS=NO, USB-IRQ=Disabled.
The commit below results in a PCI interrupt storm and a terminally
wedged system right after interrupts are enabled.
This would be a bug in the UHCI or OHCI driver then. You can avoid it by
not running the driver.
Poul-Henning
| nsayer
In my bios I have PnPOS=NO, USB-IRQ=Disabled.
The commit below results in a PCI interrupt storm and a terminally
wedged system right after interrupts are enabled.
This would be a bug in the UHCI or OHCI driver then. You can avoid it by
not running the driver.
I should have
I should have mentioned; you can probably also avoid it by letting your
BIOS give the USB controller an IRQ, since it'll almost certainly also
perform whatever initialisation the driver is currently missing out on.
Right, that is what I did once I realized that this particular commit
was
Mike Smith wrote:
Do we support any of the PNA 2.0 cards (10 Mb net over telephone line)? E.G.
3com 3c410, or D-Link DHN-520?
No; as far as I'm aware they're all using the Broadcom MAC, and Broadcom
refuse to give us documentation.
I don't know whether their chips support
involved.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Unix/FreeBSD consultant,email for more information.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I have the modem in the office, not at home. And of course there is that
tricky part where Windows wants my BIOS set to PNP OS=YES and FreeBSD
wants it set to NO. but well :-) we can survive that for the moment.
Can you expand on what actually goes wrong if you boot -current with it
set to
David O'Brien [EMAIL PROTECTED] types:
On Wed, Nov 29, 2000 at 07:41:14PM -0600, Mike Meyer wrote:
Hmm - what's the stupidity? I have a test machine running both
-current and -stable
Do you have the two FreeBSD installations on the same disk? If so, I'd
love to hear how you did it. I
, ...), and you use it just like a tty line tied to
an external modem.
mike
--
Mike Meyer http://www.mired.org/home/mwm/
Independent WWW/Unix/FreeBSD consultant,email for rates.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
k that had this on it one day started
thumping, turning it into a rather large paperweight...
FWIW, my system running both -current and -stable off of one disk uses
grub for booting, not booteasy.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
the stupidity? I have a test machine running both
-current and -stable (and NetBSD-current, Solaris, Linux, and last and
least Win98), and haven't encountered any problems with it.
mike
--
Mike Meyer http://www.mired.org/home/mwm/
Independent WWW/Unix/FreeBSD
On Tue, 28 Nov 2000, Wilko Bulte wrote:
On Mon, Nov 27, 2000 at 02:42:52PM -0600, Mike Eldridge wrote:
On Sat, 25 Nov 2000, Bernd Walter wrote:
LCA systems doesn't like probing after PCI slot 19.
Probing slot 20 panics the system.
The following patch made it into single user mode
and I need
to update the world before further testing.
Hmm, what exactly happens when slot 20 is probed? I remember my problems
with my Multia were related to PCI interrupts. It would spit out
"dec_axppci_33_intr_map: bad interrupt pin 192" about 50 or so times and
then pa
Isn't the page coloring algoritm in _vm_page_list_find totally bogus?
No, it's not. The comment is, however, misplaced. It describes
the behavior of an inline function in vm_page.h, and not the function
it precedes.
Hrm. My comment was based on John Dyson's own observations on its
Alfred Perlstein [EMAIL PROTECTED] types:
* Mike Meyer [EMAIL PROTECTED] [001122 22:41] wrote:
Could I get some feedback on URL:
http://www.freebsd.org/cgi/query-pr.cgi?pr=22755 ? It's just a
one-line kernel patch with some attendant updates in the kernel and
libc, but it makes dealing
:-(.
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
That's what I mean. You call this, and it will remap the CIS (if it
has been unmapped), walk it for you and pass you a pointer to each CIS
entry one at a time to the function you specify.
Warner
I'd rather have a seek/read interface than have a callback.
Let's be realistic; the right
IIRC, and I haven't looked it up, the CIS entries that would be
problematical have two next pointers. One is for the next function,
while the other is for the first entry specific to this function. The
driver code could look at the CIS entry to tell what to do, and if it
was the wrong
: Let's be realistic; the right way to do this is going to be to use the
: ivar interface; cardbus_get_cistuple(dev, index) just like all the other
: PCI bus accessor functions. PCI will just need to pass the request
: through to its parent, assuming its parent is a cardbus bridge, or
In message [EMAIL PROTECTED] Mike Smith writes:
: No; the CIS parser should know which function it's being called on behalf
: of, and simply elide the tuples that don't relate to that function.
This isn't always the right thing to do. At least in the 16-bit
world, there are drivers
function its own CIS chain. These CIS chains can live in
configuration space, in memory space or the expansion ROM (which I
assume is the same thing as the ROM BAR on function 0, but maybe I'm
mistaken) and the bridge is responsible for properlly mapping the last
two.
The config space
: You can also short IOCHK to ground to get an NMI which kicks you into
: the debugger, even in an interrupt context.
:
: Bad news for you warner: On a too large sample of my newer
: motherboards this doesn't work anymore :-(
There's also a pci signal that you can either pull up or pull
Does anyone know of any current issues with PXE?
Some ROMs out there are pretty bad.
I've searched the mailing
lists and I don't see any mention of a problem similar to mine.
I'm running FreeBSD-CURRENT from 2000 09 15 on a server. The client has an
Intel 21143 based ethernet card that
As near as I can tell on my laptop, the following change causes panics
with kernel page faults. With it, my laptop panics every time on
boot (although in slightly different places for my two different
kernels) and without it I'm rock solid.
Has anybody else seen this?
Yes; I think it's
/Makefile 2000/11/14 22:12:02 1.27
@@ -1,4 +1,4 @@
-# $FreeBSD: src/secure/lib/libcrypto/Makefile,v 1.26 2000/11/13
+.# $FreeBSD: src/secure/lib/libcrypto/Makefile,v 1.27 2000/11/14 22:12
^
A period before the comment somehow crept into the commit.
--
Mike Heffner [EMAIL PROTECTED
Now that someone has implementented resource alignment in the resource
allocator, someone could review and integrate the attached patch.
This looks fine to me. I assume you'd want the same changes applied to
aligning memory regions?
Background:
I do have an old system with several PnP
Something actually was changed at some point perhaps?
On i386, kernelname is dug out of bootinfo and copied
(in assembler).
On alpha:
p = getenv("kernelname");
if (p)
strncpy(kernelname, p, sizeof(kernelname) - 1);
Did the loader used to set
Timesharing requires co-operation from both device and bus, but this
is a completely different issue. No drivers currently support
timesharing. `sio' at a minimum probably should, as it was the
motivating example for adding that feature. (My laptop has three PnP
sio ports: an internal
At one (gross) time in history, Alphas included an x86 emulator
in ROM to facilitate this (and other BIOS POST initialization stuff,
mostly).
They still do.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because
Hi,
executing /compat/linux/bin/rpm issues a halt and powerdown under -current
an my TECRA8000.
Is it just me?
No. You don't have the Linux module loaded. There's a Linux system call
which (alarmingly) maps to shutdown-and-poweroff if run as a FreeBSD
binary.
--
... every activity
Hi,
Hi,
executing /compat/linux/bin/rpm issues a halt and powerdown under -current
an my TECRA8000.
Is it just me?
No. You don't have the Linux module loaded. There's a Linux system call
which (alarmingly) maps to shutdown-and-poweroff if run as a FreeBSD
binary.
Not really.
meone from shotting themselves
in the foot by, for instance, creating ssh host keys using the
low-quality /dev/random. There are certainly others.
Just some thoughts, possibly useful, probably not - but I thought
worth sharing.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &q
I had my first CVSup-ed source tre d/loaded today. It compiled correctly
(make buildworld) and installed correctly (make installworld).
But on rebooting the box, the loader fails to find a bootable kernel. It
seems my loader.conf got trashed somewhere ... I get the list of the /
partition,
On Fri, Oct 27, 2000 at 09:49:57PM +1100, Bruce Evans wrote:
[...]
NetBSD supports the ntohl family on constants, but only on some arches
(at least in last year's version). It takes fancier macros to support
constants. This gives an excuse to change the inline functions back to
On Fri, Oct 27, 2000 at 07:34:06AM -0700, Mike Smith wrote:
On Fri, Oct 27, 2000 at 09:49:57PM +1100, Bruce Evans wrote:
[...]
NetBSD supports the ntohl family on constants, but only on some arches
(at least in last year's version). It takes fancier macros to support
convention,
so that it can be used for the script's stop command :-).
Now, which process do I need to create a pidfile for to get my ipfw
config reloaded?
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
probably a better way to organize the subroutines, but that's
the general idea.
The next step is to get ports authors to start using /etc/rc.setup or
whatever it gets called :-).
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Don't want to step on toes.. Someone please commit. I believe
we need to 'load /kernel' no matter what... it's the
'read' that's in question. Allows a cdrom to autoboot.
Actually, the kernel should be autoloaded anyway, but you appear to be
right here.
patch also located at
istency ports should be tweaked to use have the
same provides/requires setup, and use rc.subr instead of the homegrown
hacks.
Which brings up the real downside of doing this - you have to parse
rc.subr and rc.conf for *every* one of those scripts.
mike
To Unsubscribe: send mail
but they get little enough use that I'd
rather use the vendor's API and let it be wasteful. After all, if they
got a lot of use, having different interface wouldn't be a problem.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
will I'm sure there are better things to disable, like MFS, SYSV*,
will P1003_P1B and friends, and ICMP_BANDLIM.
MFS is required; don't forget we have mfsroot.flp :-)
The name is historical; we use md(4) not MFS.
--
... every activity meets with opposition, everyone who acts has his
the
same knobs whenever possible.
I'm in the midst of trying to install NetBSD so I can look at this. If
no one else steps forward to do it, I can put together a patch.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
much good
this will do since you'll still be running an SMP kernel. Please
let us know how that works.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
as /boot after the system comes up.
BTW, kudos to the FreeBSD install team. Much as the FreeBSD install
may be maligned, it's much more intuitive, flexible and in general
better than what Sun is doing with for Solaris 8.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED
Maxim Sobolev writes:
"Michael C . Wu" wrote:
On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled:
| Just curious - now that the kernel has moved into /boot/kernel/kernel,
| does anyone know how well would it work to put /boot in it's own
| partition (possibly i
later, doing nothing but tapping return
every so often. I don't get enough response to start a debugger in
either case.
The best data I can contribute is a dmesg from the same hardware
booting -stable.
Suggestions? Pointers? Fixes?
mike
Oct 14 23:27:24 eve /kernel: Copyright (c) 1992
Just curious - now that the kernel has moved into /boot/kernel/kernel,
does anyone know how well would it work to put /boot in it's own
partition (possibly in it's own slice)?
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
h
*no* boot messages), I get a prompt from init.
Since the same sources build and boot properly elsewhere, I assume
I've missed a step. I normally run mergemaster after installworld and
rebooting singleuser. Could someone provide the clue I've not got?
thanx,
mike
To Unsubscribe:
,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
s -current (as of Saturday),
XFree86-4.0.1, Diamond Viper 550, SDL-1.1.5, SMPEG-0.4.0.
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
That was it. Is the 4MB kernel size limit documented anywhere?
I don't know :-) I luckily noticed this by a lot of trials.
I'm not aware of any 4MB limit on kernel size (and I ought to be if there
is one 8). Can you run the details past me? (I've regularly booted much
larger kernels
http://people.freebsd.org/~msmith/acpica-bsd-20001008.tar.gz
New in this patch:
- Fixes for the EC code (error handling)
- Fixes for power/sleep button handling (should work for both
control method and fixed buttons)
- Host:PCI bridges are now detected and attached using ACPI rather
attila! writes:
on Sat, 7 Oct 2000 20:03:12 -0500 (CDT), Mike Meyer [EMAIL PROTECTED] said:
I recently got my digital camera back out, and started pulling the old
pictures from it. I noticed something I hadn't ever seen before - silo
overflows from the sio port. At the moment, I'm
Yea, guess so, but I cant help but notice this started after the buyout by
BSDI
Uh, folks, releng4 is hosted at (and donated by) Yahoo, and BSDi have
exactly *nothing* to do with its availability or otherwise.
Before making absurd allegations like this, please apply a few neurons to
http://people.freebsd.org/~msmith/acpica-bsd-20001007.tar.gz
This includes:
- ACPI as PnP enumerator for ISA (there are issues here, and this doesn't
disable the "real" PnPBIOS code yet, so you will get duplicates on some
machines).
- Power/Sleep button code (Iwasaki-san)
- Improved
901 - 1000 of 1809 matches
Mail list logo
