Re: SB AWE64 not recognised anymore

2000-05-28 Thread Ollivier Robert
According to Szilveszter Adam: > The only remaining issue this far has been that when the Linux RealPlayer > starts playing a clip, it will always start-stop-start in the beginning and Last time I started the RealPlayer7, it went fine but I'll have to test it again as soon as I get my card back

Re: SB AWE64 not recognised anymore

2000-05-28 Thread Szilveszter Adam
On Sun, May 28, 2000 at 10:12:57AM +0200, Ollivier Robert wrote: > > What does 'cat /dev/sndstat' say on your system? > > Device non configured of course :-( Hmmm I think I'll have to give up on this one... apart from "it should work" I cannot think of any more insight just now. Maybe testing i

Re: Scheduler changes?

2000-05-28 Thread Bruce Evans
On Sun, 28 May 2000, Jacob A. Hart wrote: > I remember the scheduler bug you're talking about. My system feels much > the same as it did during 4.0-CURRENT when that bug was active. I had a Scheduling was broken in -current on 2004/04/30 11:33:44 PDT. "nice -20" in -current does essentially t

Re: SB AWE64 not recognised anymore

2000-05-28 Thread Jose M. Alcaide
Ollivier Robert wrote: > > I just upgraded my home machine from 4.0-R to 5.0-CURRENT and have found > something odd. I have an ISA PnP SB AWE64 in the machine and it is not seen by > the system at all. > -CURRENT kernel built last Thursday recognizes my AWE64 PnP: $ uname -a FreeBSD defiant.we

HEADS UP - minor API change in -current's old ISA drivers.

2000-05-28 Thread Peter Wemm
I've made old-style ISA drivers self identifying and got rid of the dreaded isa_compat.h table. As a consequence, the 'struct isa_driver' stuff has changed slightly to store the additional data that was in the compat tables and a new line is required (COMPAT_ISA_DRIVER()) so the driver registers

Re: SB AWE64 not recognised anymore

2000-05-28 Thread Szilveszter Adam
On Sun, May 28, 2000 at 04:34:57PM +0200, Jose M. Alcaide wrote: > Ollivier Robert wrote: > > > > I just upgraded my home machine from 4.0-R to 5.0-CURRENT and have found > > something odd. I have an ISA PnP SB AWE64 in the machine and it is not seen by > > the system at all. > > > > -CURRENT k

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Martin Cracauer
In <[EMAIL PROTECTED]>, Steve Kargl wrote: > First, the error message: > > cc -fpic -DPIC -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF >-I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libmd/i386/rmd160.S -o rmd160.So > building shared library libmd.so.2 > cc: Internal compiler

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Steve Kargl writes: : cc: Internal compiler error: program ld got fatal signal 10 : : *default date=2000.05.23.00.00.00 : : as specified in my cvsup supfile. The system builds fine : for all earlier dates that I've tried. I have used the : following three CFLAGS a

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Bob Martin writes: : If you are using an older K6 with more than 32mb of ram, this will : happen from time to time of it's own accord. I have never taken the time : to find out why, but if you search the archives, you will find that it : happens quite a bit. I'm usi

Re: HEADS UP - minor API change in -current's old ISA drivers.

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Peter Wemm writes: : I've made old-style ISA drivers self identifying and got rid of the dreaded : isa_compat.h table. As a consequence, the 'struct isa_driver' stuff has : changed slightly to store the additional data that was in the compat tables : and a new line

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Martin Cracauer writes: : Have you tried building and installing the new binutils before : compiling the rest of the world? This shouldn't be required for buildworld. If it is, then it is a bug in the buildworld process. Buildworld makes all the stuff it needs to

Dual-booting: FreeBSD, NetBSD and OpenBSD

2000-05-28 Thread Warner Losh
I need to setup a machine that will boot FreeBSD, NetBSD and OpenBSD. Assume I have an insane amount of disk space. What's the best way to accomplish this? Last time I tried it, the partition ID numbers were all the same, making this difficult if not impossible. Warner To Unsubscribe: send

Re: Dual-booting: FreeBSD, NetBSD and OpenBSD

2000-05-28 Thread itojun
>I need to setup a machine that will boot FreeBSD, NetBSD and OpenBSD. >Assume I have an insane amount of disk space. What's the best way to >accomplish this? Last time I tried it, the partition ID numbers were >all the same, making this difficult if not impossible. just a starter: Net

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Martin Cracauer
In <[EMAIL PROTECTED]>, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Martin Cracauer writes: > : Have you tried building and installing the new binutils before > : compiling the rest of the world? > > This shouldn't be required for buildworld. If it is, then it is a bug > in the buildwor

Re: Dual-booting: FreeBSD, NetBSD and OpenBSD

2000-05-28 Thread Udo Schweigert
On Mon, May 29, 2000 at 01:52:24 +0900, [EMAIL PROTECTED] wrote: > > >I need to setup a machine that will boot FreeBSD, NetBSD and OpenBSD. > >Assume I have an insane amount of disk space. What's the best way to > >accomplish this? Last time I tried it, the partition ID numbers were > >all the

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Steve Kargl
Warner Losh wrote: > In message <[EMAIL PROTECTED]> Bob Martin writes: > : If you are using an older K6 with more than 32mb of ram, this will > : happen from time to time of it's own accord. I have never taken the time > : to find out why, but if you search the archives, you will find that it > :

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Martin Cracauer writes: : I know that it is supposed to do so, I suspect that might not be the : case here. I don't think so. It is already using the new ld when it coredumps. I don't think that having it on the system would change things much. BTW, if I do a make

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
Here's the full list. I think something very bad is going on here. Here's the list from my last build: i386/usr/lib/libc.so: file not recognized: File truncated i386/usr/lib/libcalendar.so: file not recognized: File truncated i386/usr/lib/libcrypt.so: file not recognized: File truncated i386/usr

Unknown Devices in Dmesg

2000-05-28 Thread Thomas D. Dean
I cvsup'ed, make world, rebuild+install kernel, reboot, without problem. Good work. I upgraded from Apr 4 -current to May 28 -current and have devices listed as 'unknown' in dmesg. Everything appears to function OK. The serial ports, sio0 and sio1 appear both as sio and unknown. tomdean ===

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Thomas D. Dean
I just completed a 'make world' on a -current cvsup'ed yesterday and saw no errors. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: : I just completed a 'make world' on a -current cvsup'ed yesterday and saw : no errors. When was the previous time that you did this? And did you update the binutils first? It sure would be a MAJOR BUMMER if one needed to update binutils f

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Marcel Moolenaar
Warner Losh wrote: > > In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: > : I just completed a 'make world' on a -current cvsup'ed yesterday and saw > : no errors. > > When was the previous time that you did this? And did you update the > binutils first? It sure would be a MAJOR BUMMER

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Marcel Moolenaar writes: : The ability to do cross builds rules out the need to update binutils : first. I haven't done any cross-builds since, well, februari, so I'm not : at all up to date on that front; things may have been broken by then... I did a complete buil

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Steve Kargl
Warner Losh wrote: > In message <[EMAIL PROTECTED]> Marcel Moolenaar writes: > : The ability to do cross builds rules out the need to update binutils > : first. I haven't done any cross-builds since, well, februari, so I'm not > : at all up to date on that front; things may have been broken by the

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Steve Kargl writes: : I've got 500MB of swap. It is never touched during : the build. The machine is very lightly loaded (i.e., : only "make buildworld" running). Ditto. I just tried it with root and all the limits set to unlimited. I had the same problem. : I

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Szilveszter Adam
On Sun, May 28, 2000 at 01:10:20PM -0600, Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: > : I just completed a 'make world' on a -current cvsup'ed yesterday and saw > : no errors. > > When was the previous time that you did this? And did you update the > binutils f

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread John Baldwin
On 28-May-00 Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: >: I just completed a 'make world' on a -current cvsup'ed yesterday and saw >: no errors. > > When was the previous time that you did this? And did you update the > binutils first? It sure would be a MAJO

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> John Baldwin writes: : I built a new world fine with the new binutils right after all my commits : in /sys/boot. Also, I built world again with today's sources: OK. I have the old binutils installed on my system. : -- : build

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Thomas D. Dean
Before upgrade: FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Tue Apr 4 11:47:34 PDT 2000 \ [EMAIL PROTECTED]:/usr/src/sys/compile/CELEBRIS-SMP i386 After upgrade: FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #1: \ Sun May 28 11:07:09 PDT 2000 \ root@celebris:/usr/src/sy

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Thomas D. Dean
Sorry for two replies: I did: make world reboot rebuild+install kernel reboot tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: : make world : reboot : rebuild+install kernel : reboot OK. I'm trying on my bouncer box now. It is over NFS so it is slow. Also it is a PPro 180, so that is slow too :-(. FreeBSD billy-club.village.org 5.0-CURRENT FreeBSD 5.0-CUR

Re: Dual-booting: FreeBSD, NetBSD and OpenBSD

2000-05-28 Thread Garance A Drosihn
At 10:34 AM -0600 5/28/00, Warner Losh wrote: >I need to setup a machine that will boot FreeBSD, NetBSD and >OpenBSD. Assume I have an insane amount of disk space. What's >the best way to accomplish this? Last time I tried it, the >partition ID numbers were all the same, making this difficult >

have a couple of problems.

2000-05-28 Thread Steve Heistand
Hi, ok so I am having a couple of problems. The first is that I get tons of "sio0: x more silo overflows" messages when I boot an SMP enabled kernel under the latest 5.0 source. Well as of friday I re'cvs-upped. I can get rid of these by not booting an SMP kernel but then I get really freak

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Warner Losh writes: : OK. I'm trying on my bouncer box now. It is over NFS so it is slow. : Also it is a PPro 180, so that is slow too :-(. : : FreeBSD billy-club.village.org 5.0-CURRENT FreeBSD 5.0-CURRENT #33: : Sun Apr 30 22:57:58 MDT 2000 : [EMAIL PROTECTED]:/

Re: Unknown Devices in Dmesg

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: : and have devices listed as 'unknown' in dmesg. Everything appears to : function OK. They are ok. : The serial ports, sio0 and sio1 appear both as sio and unknown. Yes. This is expected. The PnP BIOS code which should execute before al

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
Did install of new binutils. now ld dumps core ALL the time. Further testing impossible. DO NOT TRY TO UPGRADE JUST BINUTILS IF YOU ARE GETTING THE SIGNAL 10 ERROR. YOU WON'T BE ABLE TO BUILD ANYTHING ELSE ON THE SYSTEM. Now, I'm grumpy... Warner To Unsubscribe: send mail to [EMAI

Re: have a couple of problems.

2000-05-28 Thread Andreas Klemm
On Sun, May 28, 2000 at 02:30:59PM -0600, Steve Heistand wrote: > Hi, > > ok so I am having a couple of problems. > > The first is that I get tons of "sio0: x more silo overflows" messages when I > boot an SMP enabled kernel under the latest 5.0 source. Well as of friday I > re'cvs-upped. Sa

ftp(1) breakage w/ passive mode?

2000-05-28 Thread Will Andrews
[ i'm not on -stable, but am on -current ] Hi all, I'm having trouble with ftp(1) in passive mode on 4-STABLE and 5-CURRENT: FreeBSD 4.0-STABLE #0: Sat May 27 10:26:43 EDT 2000 FreeBSD 5.0-CURRENT #1: Fri May 26 04:52:03 EDT 2000 <2 5002-0> (18:46:17) [will@radon ~]% ftp ftp://ftp.FreeBSD.org/p

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
David, looks like I found the problem. Or at least how to trivially recreate the problem and how to work around it for those people that need to do so. I've cc'd current since I've been talking there with people about it. I'm fairly certain that there are malloc related bugs in the new

Re: FW: GDB 5.0 is released!

2000-05-28 Thread Brian Dean
On Fri, 26 May 2000, David O'Brien wrote: > > > > GDB 5.0 is released! > > Do you have any forecasts as to when we will see this baby in the -current? > > Its priority is behind GCC 2.96 I haven't had a chance to examine this yet ... do you know if it includes support for our new hardware debug

Re: ftp(1) breakage w/ passive mode?

2000-05-28 Thread Cy Schubert - ITSD Open Systems Group
In message <[EMAIL PROTECTED]>, Will Andrews writes: > [ i'm not on -stable, but am on -current ] > > Hi all, > > I'm having trouble with ftp(1) in passive mode on 4-STABLE and 5-CURRENT: > FreeBSD 4.0-STABLE #0: Sat May 27 10:26:43 EDT 2000 > FreeBSD 5.0-CURRENT #1: Fri May 26 04:52:03 EDT 200

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Anatoly Vorobey
On Sun, May 28, 2000 at 05:12:05PM -0600, Warner Losh wrote: > I think that this is strong evidence that there are bugs in the new > binutils that AJ is finding. I think it may be that it incorrectly > expects memory to be zero'd when it gets it or something. I've further verified that: - it's

Re: ftp(1) breakage w/ passive mode?

2000-05-28 Thread Will Andrews
On Sun, May 28, 2000 at 05:53:38PM -0700, Cy Schubert - ITSD Open Systems Group wrote: > According to the ftp(1) man page: > > Please note that if you are connecting to IPv6 ftp server, > the program will use EPSV/EPRT pair and LPSV/LPRT pair, in- > stead of PASV and PORT. The m

Re: unknown:

2000-05-28 Thread gh
(5-28-2000) while trying to install. Rather than check the list for a solution, I went back to the 4.0 boot disks (which worked really well) and changed them to setup a snapshot (5.0-2528-CURRENT). If you so desire (which presumably is the case), I can just boot up the current floppies and t

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Anatoly Vorobey
On Sun, May 28, 2000 at 05:12:05PM -0600, Warner Losh wrote: > I get these failures on hello world: > > int main() { printf("hello world\n"); } > > cc -c xxx.c > cc -o xxx xxx.o > Can you test this patch? I think I tracked down the problem. At some point, someone added a new field into a hash

Re: have a couple of problems.

2000-05-28 Thread Matthew Dillon
:Hi, : :ok so I am having a couple of problems. : :The first is that I get tons of "sio0: x more silo overflows" messages when I :boot an SMP enabled kernel under the latest 5.0 source. Well as of friday I :re'cvs-upped. : :I can get rid of these by not booting an SMP kernel but then I get real

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Steve Kargl
Warner Losh wrote: > David, > I'm fairly certain that there are malloc related bugs in the new > binutils. If I have malloc.conf pointing at AJ, then we die in ld all > the time. If I remove that file, then we don't and things appear to > work. That's why some people succeeded in their upgrade,

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
The patch works for me! Yippie! I have my AJ back again. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread David O'Brien
On Mon, May 29, 2000 at 05:05:29AM +, Anatoly Vorobey wrote: > You need to apply the patch and remake /usr/src/gnu/usr.bin/binutils/libbfd > and then /usr/src/gnu/usr.bin/binutils/ld . I'll pass this onto the Binutils people. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread David O'Brien
On Sun, May 28, 2000 at 08:32:30PM -0600, Warner Losh wrote: > If it works, then I think it should be committed in the usual way > for this stuff: Filtered through David O'Brien... Give me a few days if you can. (if people think that is unacceptable, please let me know) I've forwarded the

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> "David O'Brien" writes: : On Sun, May 28, 2000 at 08:32:30PM -0600, Warner Losh wrote: : > If it works, then I think it should be committed in the usual way : > for this stuff: Filtered through David O'Brien... : : Give me a few days if you can. (if people th

Re: Scheduler changes?

2000-05-28 Thread Andy Farkas
On Mon, 29 May 2000, Bruce Evans wrote: > Scheduling was broken in -current on 2004/04/30 11:33:44 PDT. "nice -20" in > -current does essentially the same thing as "nice -10" in 4.0 (not enough > even in 4.0). hmmm... so there's a few years to wait before we have to worry.. :-) > > Bruce >

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Anatoly Vorobey writes: : Can you test this patch? I think I tracked down the problem. At some : point, someone added a new field into a hash table struct and didn't : add initialization for it into the general hash table struct init func. : This patch cures the prob