Mike,
Seems like I managed to solve my problem. Attached is to be applied against
sys/dev/acpica/acpi_pcib.c, rev 1.10 .
Thanks for tracking this down; without hardware to test here, it's been
difficult. Great bug report!
I've just committed a slightly different patch, based on a mix
On Sat, 28 Jul 2001, Mike Smith wrote:
You could also try building a kernel with CLK_CALIBRATION_LOOP defined
and then booting with -v (without the timer disabled). This might be
instructive (I don't know for certain that it'll calibrate the ACPI
timer, since it may not have been
Say
set debug.acpi.disable=timer
in the bootloader and see if you still get this. I've already got one
report of system time going twice as fast as it should; I'm unsure what's
going on here (I don't grok the timecounter code as well as I should, I
think)...
You could also try building a
Mike Smith schrieb:
Say
set debug.acpi.disable=timer
in the bootloader and see if you still get this. I've already got one
report of system time going twice as fast as it should; I'm unsure what's
going on here (I don't grok the timecounter code as well as I should, I
think
It is much easier, at least to me, to just remove much of the KLD
screen saver support from syscons to the user-land, than to utilize
the kthread :-)
Just FWIW, I think that moving the screen saver to userspace is an
excellent thing to do.
--
... every activity meets with opposition,
this problem.
(I would assume sometime in the next 2-3 weeks.)
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
though; my
last suspicion is that it doesn't contain any resources at all, and so
we're overrunning it when we go to try to stuff an interrupt resource
into it. If that's the case, it's easy to fix. If not, then we will
have to go hunting snarks.
Thanks.
Mike
--
... every activity meets
.
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. Fritz Todt]
V I C T O R Y
On 20 Jul, Mike Smith wrote:
attached is a diff for rc.i386, rc.conf.5 and defaults/rc.conf which
allows to enable the ACPI power management in rc.conf similar to
apm_enable.
This is not a good idea; ACPI isn't on or off, and by the time
What does acpiconf -e do then?
Nothing
attached is a diff for rc.i386, rc.conf.5 and defaults/rc.conf which
allows to enable the ACPI power management in rc.conf similar to
apm_enable.
This is not a good idea; ACPI isn't on or off, and by the time
rc.conf is running it's too late to en/disable it. There are several
seperate
are having with the PCI
interrupt routing _SRS method failing.
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
device statically compiled into the kernel and was also loading
the random KLD, it would always crash when starting the linux version of
netscape. Removing the random device from the kernel config fixed the problem.
So you don't happen to be doing anything similar are you?
Mike
--
Mike
I'm also having same hang-up, with acpi_pcib.c rev1.10 (no NEWCARD).
Sounds like calling _SRS is breaking something.
With acpi_pcib.c rev1.9, I loose my pccard.
This is known; I messed it up. 8(
With acpi_pcib.c rev1.8, everything seems ok.
This uses the old PCI interrupt routing code.
I've committed another round of ACPI changes to -current.
The major addition is CPU throttling support. This is implemented using
ACPI, not any vendor-specific technology, so it should work on any
platform that exports the relevant information. By default, the CPU will
run at 100%
sos Well, sortof, the ata driver doesn't allow for sharing irq1415
sos since lots of boards doesn't work that way. However if you need
sos it you can try to add the shared flag in the driver and see if
sos it works on yours. Hmm, maybe I should make this tunable...
It this patch OK?
: There is absolutely no reason for the ata driver not to simply set
: RF_SHAREABLE and be done with it. It's up to the driver's parent (isa,
: pci, etc) to decide whether the interrupt is in fact shareable or not.
:
: The ata driver itself can share interrupts just fine, and it should
Finally, if you're so damn concerned about your precious alpha I
expect you or at least ANYONE WHO CARES ABOUT ALPHA TO ASSIST IN
TESTING THESE DIFFS.
HOW THE FSCK AM I TO TEST THEM WHEN I CANNOT EVEN GET TO SINGLE USER??
By testing them before they're committed, obviously.
David -
On Fri, 6 Jul 2001, Bruce Evans wrote:
...
if_foo.c - /sys/modules/foo - foo.ko. There is no driver named if_foo.
that seems to be right.
No man if_ed(4) yust ed(4)...
No.
if_foo.c in /sys/modules/foo builds if_foo.ko.
This was discussed a year or so back; it's a compromise design.
ha/alpha/genassym.c
../../../vm/vm_zeroidle.c:13: opt_npx.h: No such file or directory
../../../vm/vm_zeroidle.c:17: opt_reset.h: No such file or directory
../../../vm/vm_zeroidle.c:38: machine/pcb_ext.h: No such file or
directory
../../../vm/vm_zeroidle.c:39: machine/vm86.h: No such file
again, it didn't even recreate the
| directory.
| mdharnois
|
| To Unsubscribe: send mail to [EMAIL PROTECTED]
| with unsubscribe freebsd-current in the body of the message
Mike
--
Mike Heffner mheffner@[acm.]vt.edu
Fredericksburg, VA [EMAIL PROTECTED]
PGP signature
On 01-Jul-2001 Mark Peek wrote:
| At 10:05 AM -0400 7/1/01, Mike Heffner wrote:
|It works for me ;) Remember that the new default is:
|
| /sys/${MACHINEARCH}/compile/${KERNCONF}
|
|
| Right, there is a new compile directory. Perhaps this needs to be
| added to UPDATING. Anyway, did you run
I'm running current and get the following error in dmesg while trying to
enable the minipci. This is a HP n5470 laptop.
dc0: Accton EN2242 MiniPCI 10/100BaseTX irq 11 at device 16.0 on pci0
dc0: failed to enable I/O ports!
device_probe_and_attach: dc0 attach returned 6
It is sharing
. 8)
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. Fritz Todt]
V
In message [EMAIL PROTECTED] Bruce Evans
writes:
: The first ls should create about 8000 new tun devices by first accessing
: them via stat(2), but there is some garbage collection, so the second ls
: may show that some of the devices have magically unappeared.
I just want to see the disk
The reason I said in the next week is actually because on Sat. June 23rd
(not this upcoming one, but the one after), I should be flying off to
Yugoslavia (actually to London, and only then to Yugoslavia). I will be
gone for 3 weeks and seeing as how maintaining this huge diff is a real
, so
this *won't* work for the Alpha. 8(
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
Just curious, but are there plans to support the EV6 bus that the dual
athlon motherboards use? I'm not going to buy that kind of system unless
FreeBSD 5 will support it.
FreeBSD works just fine on the dual K7 evaluation systems that AMD have
been shipping around. It seems that they wimped
The ACPI core code in -current has been updated to the 20010518 drop from
Intel. You can read more about APCI CA at
http://developer.intel.com/technology/ial/acpi
This update doesn't add any new, visible functionality, but it should
resolve a number of bugs and problems in the core
The ACPI core code in -current has been updated to the 20010518 drop from
Intel. You can read more about APCI CA at
http://developer.intel.com/technology/ial/acpi
Sorry, that should be
http://developer.intel.com/technology/iapc/acpi
Regards,
Mike
--
... every activity meets
SMAP type=01 base= len= 0009f800
SMAP type=02 base= 0009f800 len= 0800
SMAP type=02 base= 000e8400 len= 00017c00
SMAP type=01 base= 0010 len= 13ef
SMAP type=03 base= 13ff len=
locked up at the same
place. I'll be glad to try any patches to try and get this working.
You could try disabling the PCI BIOS calls;
set machdep.bios.pci=disable
at the loader prompt. Let me know if this helps; I'd want to track this
further if it does.
Regards,
Mike
--
... every activity
On 27-May-2001 Mike Smith wrote:
| You could try disabling the PCI BIOS calls;
|
| set machdep.bios.pci=disable
|
| at the loader prompt. Let me know if this helps; I'd want to track this
| further if it does.
Yes, this works =)
Mike
--
Mike Heffner [EMAIL PROTECTED
=0x02
chip3@pci0:11:1:class=0x060700 card=0x00011179 chip=0x06171179
rev=0x20 hdr=0x02
none1@pci0:12:0:class=0x040100 card=0x00011179 chip=0x00121073
rev=0x00 hdr=0x00
none2@pci1:0:0: class=0x03 card=0x00011179 chip=0x8c125333
rev=0x13 hdr=0x00
Thanks,
Mike
--
Mike Heffner
Could be, and I certainly don't know much about this code. But
it seems like the driver is being given reason to assume it has a
working device when it doesn't really have one. I assume the device
is unusable without its interrupt, so shouldn't it fail at probe or
attach time?
The bottom line is this; in your driver, ask for the resources that you
need. If you don't get them, you fail. The PCI bus infrastructure is
being worked on to improve your chances of getting these resources; it's
not something that a driver writer should be worrying about per se.
And
Segmentation fault (core dumped)
I also have DDB in my kernel config, but it didn't drop into DDB. Is
there anything else I can test? I'm willig to test any patches or
whatever.
Thanks,
Mike
--
Mike Heffner [EMAIL PROTECTED]
Fredericksburg, VA [EMAIL PROTECTED
On 20-May-2001 Dima Dorfman wrote:
| Please try the attached patch. I make no claims of its correctness,
| but this e-mail is coming to you via X on -current updated a few hours
| ago so it works here :-).
Thanks, it works so far (I'm running X). I'll see where it breaks next.
Mike
I have some more information about this now. There is a BIOS knob
USB IRQ which can be set to Disabled or Enabled. If it is Disabled,
the hangs occur as I described. If it is Enabled, everything works
fine. I think it ought to boot in either case (-4.x does). I am not
actually using the
In article [EMAIL PROTECTED],
Mike Smith [EMAIL PROTECTED] wrote:
You're not tying up an interrupt; PCI interrupts are shared. With the
new PCI code, even if you turn it off, we'll just turn it right back on
again. 8)
But if IRQ 5 is assigned to the uhci device, then it's
.
To get around it, I just commented out the file that was causing problems
in the makefile (ua..alt.kbd or something like that), but before that I
had nuked /usr/obj twice, and did fresh checkouts of /usr/src just to be
sure I hadn't messed up.
-Mike
-
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL
The only reference to isalnum() I see is in boot/ficl/words.c:274, and
appears to replace a couple of references, one to isdigit() and the
other to isalpha().
Perhaps something was omitted in the upgrade to ficl 2.05?
It's because words.c uses stand.h instead of ctype.h, and
On Tue, 24 Apr 2001 16:19:59 -0700, Dima Dorfman [EMAIL PROTECTED] said:
This is not a bug. This is an FAQ. So much that it's actually
documented in (*gasp!*) the FAQ:
Unfortunately, the A in the FAQ is wrong.
The ``can't assign resources'' messages indicate that the devices are
On Wed, 25 Apr 2001 16:57:56 -0600, Warner Losh [EMAIL PROTECTED] said:
Actually, it is a bug. The drivers in the tree should grok these pnp
ids.
Actually, no, it is not a bug. The FreeBSD drivers for these devices
manage their resources differently from the way the Windows drivers
In message [EMAIL PROTECTED] Mike Smith writes:
: I assume there's a better fix in the works, so that a dirpref-touched
: disk can be moved back to a pre-dirpref system?
If not, then dirpref should be backed out, imho.
I'd have to agree; this was a pretty poorly-thought-out aspect
You need to rebuild fsck and install it and fsck your filesystems. This is the
dirpref changes biting you. Warner, we probably need an entry in UPDATING for
the dirpref changes that warn people to build and install a new fsck before
booting a dirpref kernel.
Er. This really isn't very
Folks,
although there was much rejoicing, I think there's no need for a
new option to cp. Just use the toolbox, it's not too hard:
(cat bigfilelist; echo destdir) | xargs cp
Or even
echo destdir bigfilelist
xargs cp bigfilelist
should do the trick.
No, it won't. Consider a
subscribe freebsd-current
subscribe cvs-all
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Title: ÍÅ ÓÄÀËßÉÒÅ ÝÒÎ, ÎÒÏÅ×ÀÒÀÉÒÅ ÝÒÎ, ÏÐÎ×ÈÒÀÉÒÅ ÝÒÎ
ÎÒÏÅ×ÀÒÀÉÒÅ
ÝÒÎ, ÏÎÆÀËÓÉÑÒÀ, È ÑÏÎÊÎÉÍÎ
ÏÐÎ×ÈÒÀÉÒÅ !
ÂÛ ÇÀÐÀÁÎÒÀÅÒÅ ÌÍÎÃÎ
ÄÅÍÅÃ!
ÝÒÎÒ ÁÈÇÍÅÑ ÐÀÁÎÒÀÅÒ ÏÐÎÑÒÎ
ÂÅËÈÊÎËÅÏÍÎ!!!
ß ÐÀÁÎÒÀÞ ÏÎ ÝÒÎÉ ÏÐÎÃÐÀÌÌÅ ÎÄÈÍ -
ÄÂÀ ×ÀÑÀ  ÄÅÍÜ, ÂÊËÞ×Àß ÎÁÐÀÁÎÒÊÓ ÇÀÊÀÇÎÂ È ÄÎÐÎÃÓ Â ÁÀÍÊ!!!
Íà÷íèòå
ppc1: ECP parallel printer port at port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on
isa0
That's because the PnP entity is still matched. You can't disable PnP
devices; it just doesn't work that way. 8)
You mean it's impossible to disable lpt/floppy in a pnp system
and use thier
In message [EMAIL PROTECTED] Mike Smith writes:
: This looks OK, though you might want to disable the pccard support, since
: it's known to be broken right now.
pccard support is not broken right now. If there's a "known" issue, I
sure don't know about it.
Oh, sorry, I'm obv
Hi.
I have diskless-PC which was used /boot/pxeboot. But latest
FreeBSD-current is output below messages and some fsck_nfs problem.
WARNING: MFS is being phased out in preference for md devices
WARNING: Please see mdconfig(8) for details
WARNING: Continuing in 15 seconds
Does
gee - being like SysV is more comprehensible than worrying about IPv6
-mo
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Firstly, please don't send HTML mail. It's bad, and people have a hard
time dealing with it.
Semi-recently grabbed a snapshot of -CURRENT (from 03/06) to see if I could
finally get my 3Com 3c575C Fast Etherlink XL cardbus lancard to work. I saw
it mentioned in the HARDWARE.TXT so I decided
On Thu, 22 Mar 2001, Justin T. Gibbs wrote:
I think I found the problem. The problem occur since 03/14/2001. The
following files could be infvolved:
You'll have to ask Soren about this. It looks like one part of
ata-all (this is in -stable), clears the RF_SHAREABLE flag. I
don't
mething like:
interface "fxp0" {
media "media 100baseTX mediaopt full-duplex";
}
in /etc/dhclient.conf will make dhclient DTRT when ifconfig ing the
interface. Of course, that means that you're forcing the
interface to be 100meg (which won't work when you plug your
laptop in $C
Ian Dowse wrote:
In message [EMAIL PROTECTED], Mike Smith writes:
I don't quite understand Paul's reasoning, though; it's not actually
useful to unload/reload parts of a device's bus attachment without
unloading/reloading all the downstream parts of the driver.
What do you mean
See my PR kern/25582. The explanation why Bill Paul does not want to make this
change yet is there :)
That's Paul Richards, not Bill Paul.
I don't quite understand Paul's reasoning, though; it's not actually
useful to unload/reload parts of a device's bus attachment without
As suggested, if the correct root device can't be found, the boot
_should_ offer you a choice of running off others that appear to be
bootable.
The "appear to be bootable" criterion is almost impossible (and unsafe to
attempt) to determine.
Also, I certainly can see instances
There are two schools of thought here. One says "you should try very
hard to find a root device", the other says "you should boot only from
the exactly correct root device and complain otherwise". I took the
first approach because its advocates shouted more loudly than those of
Then wouldn't the "partially applied patch" rule apply? eg, back it
out until the issues can be resolved. Breaking the upgrade path isn't
acceptible.
I have to "me too" this; the change simply isn't OK. There are a variety
of ways that we can work around the issue and maintain binary
Then wouldn't the "partially applied patch" rule apply? eg, back it
out until the issues can be resolved. Breaking the upgrade path isn't
acceptible.
If you bump the library versions, doesn't that fix the upgrade
path?
No, because the library version bump has already happened.
I
On Mon, Feb 12, 2001 at 02:20:30PM -0800, Mike Smith wrote:
You can do better than this. Put the lock in FILE, and define a new
structure FILE_old, which has the same size/layout as the old FILE
structure.
How is this more acceptable than bumping the major number? Are they
really
Mike Smith wrote:
On Mon, Feb 12, 2001 at 02:20:30PM -0800, Mike Smith wrote:
You can do better than this. Put the lock in FILE, and define a new
structure FILE_old, which has the same size/layout as the old FILE
structure.
How is this more acceptable than bumping
. This happens
both with a ES1371 and an old SB16 ISA card. It seems I may also be
losing keystrokes from the keyboard, though I haven't confirmed it's not a
problem with the keyboard itself.
- Mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
in audio, just
when the machine gets busy (which is fine since I don't expect a P133 to
be able to do too much else when playing MP3's).
- Mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
FreeBSD currently only supports S1 and S5. I haven't done anything with
S1 lately, so I'm not sure if it's been broken recently.
In BIOS i can select weather to use S1 or S3, motherboard uses AWARD
ACPI,
which ever I select it doesn't wont to sleep, dou I can shut it down by
eather -s5 or
John Summerfield [EMAIL PROTECTED] types:
[EMAIL PROTECTED] said:
Isn't it early for april fool's?
Nah. Easter eggs are in the shops.
And the fools are forging mail.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Perforce
him about it.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
This is weird; the bridge appears to be clearly misconfigured, and unless
there's something funky in the datasheet (looking for it now) I'm not
quite sure what the "right" thing to do is here. 8(
Please let me know if you need anything more from me to help debug this.
This is enough for
for
shells added later, whether from ports or elsewhere.
And I want the shed crimson with cream trim.
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.
To Unsubscribe: send
Ok so I have tried the settings in
teh loader conf..
I have:
#autoboot_delay="10"# Delay in seconds before autobooting
#console="vidconsole" # Set the current console
currdev="disk1s1a" # Set the current device
module_path="/boot/kernel;/boot/modules"
VLF-incapable utilities. (on a related note, is there a need for
vlfread()/vlfwrite() in the BSD's, or is VLF support native in the read/write
calls?
The standard off_t is 64 bits in all of the BSDs.
--
... every activity meets with opposition, everyone who acts has his
rivals and
#autoboot_delay="10"# Delay in seconds before autobooting
#console="vidconsole" # Set the current console
currdev="disk1s1a" # Set the current device
module_path="/boot/kernel;/boot/modules"# Set the module search path
If you mean "it loads the kernel from the wrong place", that's one thing.
If you mean "it mounts / from the wrong filesystem", then you should be
aware that the loader reads /etc/fstab, and the kernel will mount
whatever you've put in there.
Just curious, but isn't there a
with the BIOS either.
Anyone got a clue as to why the IRQ would change? Is there anything in
FreeBSD that could change it?
Thanx,
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more
After installing a fresh cvsup last Sunday, I find that my usb printer
quit working. Some investigation shows that this is because the uhci
and fxp are now on the same IRQ.
Why would this cause your printer to stop working? Have you determined
that this is actually the case, or did you only
Mike Smith [EMAIL PROTECTED] types:
After installing a fresh cvsup last Sunday, I find that my usb printer
quit working. Some investigation shows that this is because the uhci
and fxp are now on the same IRQ.
Why would this cause your printer to stop working? Have you determined
Mike Meyer [EMAIL PROTECTED] types:
Mike Smith [EMAIL PROTECTED] types:
After installing a fresh cvsup last Sunday, I find that my usb printer
quit working. Some investigation shows that this is because the uhci
and fxp are now on the same IRQ.
Why would this cause your printer
Poul-Henning Kamp [EMAIL PROTECTED] types:
But while you're at it, migrate to md(4) instead of vn(4), it does
vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices
How close is the md rewrite to being able to replace mfs?
Thanxm
mike
Poul-Henning
I got quite upset about this last time, and I guess it's time to do it
again.
Folks, *please* stop exporting "pure" kernel structures to userland.
Make a sanitisied, versioned structure and just copy your damn args back
and forth. 'struct ucred' should probably never have been exported to
for disaster right
now).
Could you also make sure it makes it into /etc/defaults/make.conf
(KERNEL isn't mentioned there at all) and make.conf(5)?
Thanx,
mike
--
Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/
Independent WWW/Perforce/FreeBSD/Unix
John Baldwin [EMAIL PROTECTED] types:
On 22-Jan-01 Warner Losh wrote:
In message [EMAIL PROTECTED] Mike Meyer writes:
: Warner Losh [EMAIL PROTECTED] types:
: It is in the handbook, and has been for some time. I'm reviewing the
: recent KERNEL - KERNCONF changes to make sure
On Mon, Jan 22, 2001 at 12:16:38PM -0800, Mike Smith wrote:
In the meantime, perhaps we could
ask that one of the SMPng rules of engagement mandate that no mutex
structures or structure members should ever be exported as part of a
userspace interface?
This sounds fine in principle
in speed.
For those not familiar with openssl, the process of benchmarking is
simple - just type "openssl speed".
Any comments about how to improve my make syntax would also be helpful, if
one is so inclined.
Thanks,
Mike "Silby" Silbersack
(Please CC me on followups,
involvement?
I don't think it's ccd. I get similar hangs with "make -j 20 buildworld"
on a 2xPII-Xeon/450, 256M, two scsi disks on ahc without ccd.
I think more likely it's related to the problems that sos is currently
having/investigating.
mike
To Unsubscribe: send mail
That's one of the big reasons that we're 4.x based right now rather
than 3.x based, despite 4.x's slightly larger memory footprint. That
and 4.x's much better c++ compiler.
Well, Warner, I've never done embedded systems. So, tell me, do they
actually use any C++ code in embedded
Note that there are no \_TZ_ entries in that "vaiolx800.asl" dump
that I submitted for the ACPI collection. I'm not sure where that
collection is - I don't see it off www.jp.freebsd.org/acpi, if
anyone wants to see that .asl file I can put it somewhere public.
Is there a thermal zone
Note also that Scott Long ([EMAIL PROTECTED]) is also working on this,
you will want to check with him to work out where he's up to...
Now I'd like to figure out how to turn the damn fan up and down. This
machine is quiet under windows but sets the fan to high under FreeBSD
and never
On Sat, Dec 30, 2000 at 03:13:24AM +1000, Andrew Kenneth Milton wrote:
Is there a nice way to stop vga_pci from attaching to my video card, or
to allow another driver to attach to it after vga_pci has done its thing?
At the moment I'm removing all traces of vga_pci from the Makefile in
From: [EMAIL PROTECTED]
Date: Wed, 27 Dec 2000 21:55:51 -0500 (EST)
::md0: Malloc disk
::WARNING: Driver mistake: destroy_dev on 154/0
::** what's this? *
I'm not sure about this one.
It looks like a bug in the 'asr' driver. Mark - I'm guessing that you
have a
Please add that back again.
No. The Matsushita/Mitsumi/Sony CDROM interfaces have gone the way of
the 3c501. The drivers are there, and if you're really desperate, you're
welcome to try them, but they're not supported install devices anymore.
Note that it's trivial to build a
Since we are on the subject of ACPI, it is working great except for one
thing, it can't attach my sound card to the pcm device (does that sound
correct?). It definitely sees it:
unknown: YMH0021 can't assign resources
This would suggest that something else is taking one or more of the
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
Trying to upgrade an existing 3.4 system to 4.2
failed due to kernel.GENERIC not having mcd0 built in
anymore (MITSUMI CDROM) :-(
Please add that back again.
No. The Matsushita/Mitsumi/Sony CDROM interfaces have gone the way of
the 3c501. The drivers are there, and if you're really
Last night I installed a kernel with 'device acpica' for the 1st
time, and all seems fine, except that I see this at boot:
...
too many dependant configs
...
I traced this message to /usr/src/sys/dev/acpica/acpi_isa.c, function
acpi_isa_set_start_dependant().
Now, I have not had any
with a better
algorithm, but for the most part, this code seems to work just fine.
On Sun, Dec 24, 2000 at 11:50:13AM -0800, Mike Smith wrote:
Last night I installed a kernel with 'device acpica' for the 1st
time, and all seems fine, except that I see this at boot:
...
too many
While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
=== 3dfx
@ - /FreeBSD/FreeBSD-current/src/sys
ln: @: Read-only file system
*** Error code 1
Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
*** Error code 1
It looks like it's trying to mess around
Why is there the same VGA code in dev/fb/vga.c and libvgl? I think
especially of the set_palette routines.
The framebuffer code is a newer addition. Libvgl was done quite a while
ago as more or less a proof-of-concept.
As a more general rule, what's the philosophy for the future of
libvgl
Andrzej,
did you receive a response regarding your email the Intel
Pro 10/100B/100+ Ethernet being unresponsive after running windows?
i seem to have the same problem.
I'm working on the (longer-term) solution to this at the moment. In the
meantime, it's going to need a driver
801 - 900 of 1809 matches
Mail list logo
