-current of June 01:
For me it was in stage 4 at:
ln -sf libm.so.2 /usr/obj/usr/src/i386/usr/lib/libm.so
cd /usr/src/lib/libncurses; make depend; make all; make install
./make_keys /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/keys.lis
t init_keytry.h
sh
Three issues:
- floating point math doesn't seem to work properly:
To reproduce:
Build xaos from ports (/usr/ports/graphics/xaos)
Run xaos and press 'a'
- enjoy the show but I dont think its what the
author intended.
I have
For reference the ID reported is:
de0@pci0:3:0: class=0x02 card=0x chip=0x00191011 rev=0x11 hdr=0x00
Hm, ok. First of all, I made a mistake in what I told you. The code in
dcphy.c checks the subsystem ID, not the device ID. The device ID is always
the same, since that
Andreas Klemm wrote:
-current of June 01:
For me it was in stage 4 at:
ln -sf libm.so.2 /usr/obj/usr/src/i386/usr/lib/libm.so
cd /usr/src/lib/libncurses; make depend; make all; make install
./make_keys /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/keys.lis
t
Hi,
after the update of my rc scripts (~a month ago if I remember correctly)
to use source_rc_conf it didn't boots as expected. E.g. it didn't starts
anything from rc.i386. I had to source rc.conf* manually in rc.i386.
Other misbehavior:
- didn't set the defaultroute
- didn't start ntpd/lpd
On Fri, 02 Jun 2000 09:46:04 +0200, Alexander Leidinger wrote:
after the update of my rc scripts (~a month ago if I remember correctly)
to use source_rc_conf it didn't boots as expected. E.g. it didn't starts
anything from rc.i386. I had to source rc.conf* manually in rc.i386.
Could you
On 2 Jun, Sheldon Hearn wrote:
after the update of my rc scripts (~a month ago if I remember correctly)
to use source_rc_conf it didn't boots as expected. E.g. it didn't starts
anything from rc.i386. I had to source rc.conf* manually in rc.i386.
Could you run mergemaster again to make
On Fri, 02 Jun 2000 12:07:13 +0200, Alexander Leidinger wrote:
At the moment my /etc/rc contains:
---snip---
# If there is a global system configuration file, suck it in.
#
if [ -r /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
. /etc/rc.conf
.
On Thu, Jun 01, 2000 at 04:32:42PM -0700, Bill Paul wrote:
- It has a 21143 chip
Well, the de driver says 21142. The dc driver says 21143.
It's just a difference in chip revision, really.
OK.
This one does not have AUI so that is not going to be a problem. What I do
wonder,
Greetings,
I just subscribed to -current list to get suggestions on the following so if
I have missed comments on this already I am sorry for the redundancy.
I have just upgraded to 5.0-current in order to get the driver for my ether
card, which has corrected that problem (xe device).
But I
On Fri, 2 Jun 2000, Alexander Leidinger wrote:
I know, but I had to modify them to get it running.
If that's true, you already had some sort of custom modifications
which interfered with the way the system is supposed to work. That's not
"bad," it just makes debugging more complicated.
Seems to have happened since I updated and made world and kernel this
afternoon.
link_elf: symbol LINUX_SIGF_HANDLER undefined
pid 208 (ldconfig), uid 0: exited on signal 11 (core dumped)
dc0: promiscuous mode enabled
link_elf: symbol LINUX_SIGF_HANDLER undefined
KLD rtc.ko: depends on linux -
12 matches
Mail list logo
