Re: Got diskless Sun booting from FreeBSD server...
Hi, How about adding a "howto" to the handbook ? /Jesper On Sun, Dec 19, 1999 at 09:38:09PM +0100, Ron Klinkien wrote: Thanks to Ian Dowse and Patrick Gardella i got my SPARCclassic booting and running as a nice Xterminal server. [cut] Thanks all. Ron. /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk Work:Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek@ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make world broken with NO_FORTRAN=true
After some more digging I have found out why buildworlds are failing on my system: it's because I have NO_FORTRAN=true in /etc/make.conf. cd /usr/src/gnu/usr.bin/cc/f771; make build-tools cc -O -pipe -march=pentium -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f -I. -c /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fini.c ... /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/hconfig.j:25: hconfig.h: No such file or directory When `NO_FORTRAN=true', the Fortran directories are not created under /usr/obj because of the following in /usr/src/gnu/usr.bin/cc/Makefile: .if !defined(NO_FORTRAN) SUBDIR+= f77 f771 f77doc .endif But the build-tools target in /usr/src/Makefile.inc1 unconditionally descends into gnu/usr.bin/cc/f771. As a result, the include reference to hconfig.h through /usr/src/gnu/usr.bin/cc/f771 fails. The other errors ae a result of the missing hconfig.h; it contains #include "auto-host.h" #include "gansidecl.h" #include "i386/xm-i386.h" #include "hwint.h" auto-host.h defines HAVE_STRERROR as 1, gansidecl.h defines PVPROTO. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make world broken with NO_FORTRAN=true
Jos Backus wrote: After some more digging I have found out why buildworlds are failing on my system: it's because I have NO_FORTRAN=true in /etc/make.conf. [snip] Thanks. Will be fixed. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868, newpcm, and Linux RealPlayer 5.0
On Sat, 18 Dec 1999, Donn Miller wrote: I just rebuilt my kernel from a recent cvsup. Of course, I have device pcm0 device sbc0 in my kernel config file. When I try to play a realaudio clip with Linux rvplayer (RealPlayer 5.0), rvplayer downloads the clip, and instead of playing the clip, rvplayer just hangs until I kill it. Is the ESS 1868 isa card working with sbc0 and pcm0? Anyone else have this problem with rvplayer? I tried the OSS driver modules, and the same rvplayer works OK there. The ESS 18xx support seems to be broken at the moment. I have one here and I'll fix it as soon as I get a chance to work on it. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sh(1) broken caching [was: Re: Broken sh(1)?]
In [EMAIL PROTECTED], Brian Fundakowski Feldman wrote: On Fri, 17 Dec 1999, Martin Cracauer wrote: I still think we should *seriously* consider switching to pdksh. As I said before, pdksh has other bugs. Also we would loose all the PRs we received in the past. This testing effort by our user base is a valuable resource. From the tests I ran on all available shells, only bash2 is considerably better than the other shells, pdksh has other bugs than our ash, not less. HAHAHAHAHAHAHAHAHAHAhahahahahahahahahahahaha *cough, HACK, wheeze*. Ahem. Heh, bash2 considerably better. *continues ROFL* Over the last year, I did an extensive amount of testinging on bourne shell behaviour. bash2 was the only free sh clone that I never had to complain over. Is there something substantially you'd like to contribute to the discussion, like - say - an example where bash-2.03 doesn't work well? If your experience is based on old bash1 stuff, forget it. bash got improved greatly since it is used as the standard shell for a UNIX clone in wide use. Just like our shell improved from the beatings it got because it has been the standard script-executing shell on FreeBSD and NetBSD for (together) 10 years now. Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP
Emre wrote: Hi people, I went to ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-19991218-CURRENT/README.TXT and read that document. Most hardware that I need to use is supported on that list, but I have a question: is SMP enabled in the GENERIC kernel in FreeBSD 4.0-current? we have a server that has dual 500Mhz P-III's and 2GB RAM...it's a waste to run Linux on it :\ You have to recompile the kernel to enable SMP : it's a matter of erasing four "#"s in the GENERIC config file. You may have to read a few pages of the handbook to see how to recompile your kernel (begin with http://www.freebsd.org/handbook/kernelconfig.html) TfH PS : could you break your lines at 72 chars ? Thanks! (PS: please reply in private as I am not subscribed to this list yet :) -- Emre Yildirim DH/DSS KeyID: 0xA007E75C | RSA KeyID: 0xFD5FD2C7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound and -current.
That's the hint I was looking for.. I had the pcm0 but didn't know we now had to add a special sbc entry.. THANKS! Now I know what I'm looking for i'll ge an dlook at LINT to see what else is in that vicinty. I guess I stopped reading at: # For pnp sound cards: #device pcm0 On Sun, 19 Dec 1999, Devin Butterfield wrote: Julian Elischer wrote: So is there any chance that my Vibra16 Soundblaster will ever be recognised again? I was surprised because I had imagined that the soundblaster would be the first card supported under the new code. unknown0: Audio at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 7 drq 0,5 on isa0 unknown1: IDE at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown2: Game at port 0x200-0x207 on isa0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message Silly question but...do you have: devicepcm0 devicesbc0 in your kernel config? I have the ViBRA16X and I got the same messages during boot until I compiled support into the kernel. Now it looks like: sbc0: Creative ViBRA16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq1,3 on isa0 pcm0: SB DSP 4.16 on sbc0 unknown0: Game at port 0x201 on isa0r Of course I'm not using the game port. :) -- Regards, Devin. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Sound and -current.
So is there any chance that my Vibra16 Soundblaster will ever be recognised again? I was surprised because I had imagined that the soundblaster would be the first card supported under the new code. unknown0: Audio at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 7 drq 0,5 on isa0 unknown1: IDE at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 unknown2: Game at port 0x200-0x207 on isa0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound and -current.
On Sun, Dec 19, 1999, Julian Elischer wrote: So is there any chance that my Vibra16 Soundblaster will ever be recognised again? Did you add the sbc0 bridge driver to your kernel configuration file? (I managed to miss that heads-up the first time around too.) -- |Chris Costello [EMAIL PROTECTED] |Computers are a more fun way to do the same |work you'd have to do without them. `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fsck not cleaning on first try
On Sun, Dec 19, 1999 at 11:28:29PM -0500, Bill Fumerola wrote: On Sun, 19 Dec 1999, Alex Zepeda wrote: Hmm. It happened again. This time I was playing around with the vmware stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think this is the way to go, not bloating *our* procfs), and eventually when run panic'd the system. I just rebooted it (nearly a day later), and fsck cleaned it and printed some info, but then mount refused to mount it. A simple reboot from the comandline seems to have worked. Hmmm indeed. Ditto. mount was telling me my fs wasn't clean, but after I rebooted it was fine and it didn't fsck that second time. I saw that too; I worked out it was because I hadn't done the MAKEDEV after upgrading to a -current without blkdevs (so it's surprising it worked at all). - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fsck not cleaning on first try
On Sun, 19 Dec 1999, Mike Smith wrote:
On Sun, 19 Dec 1999, Alex Zepeda wrote:
Ditto. mount was telling me my fs wasn't clean, but after I rebooted
it was fine and it didn't fsck that second time.
Bruce posted (but did not commit) what may be a fix for this a while back:
I wish he would commit these things!
diff -c2 ffs_vfsops.c~ ffs_vfsops.c
*** ffs_vfsops.c~ Thu Nov 25 23:27:44 1999
--- ffs_vfsops.c Sun Dec 5 05:12:51 1999
***
*** 218,222
--- 220,226
}
+ fs-fs_flags = ~FS_UNCLEAN;
if (fs-fs_clean == 0) {
+ fs-fs_flags |= FS_UNCLEAN;
if (mp-mnt_flag MNT_FORCE) {
printf(
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
fsck not cleaning on first try
Hmm. It happened again. This time I was playing around with the vmware stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think this is the way to go, not bloating *our* procfs), and eventually when run panic'd the system. I just rebooted it (nearly a day later), and fsck cleaned it and printed some info, but then mount refused to mount it. A simple reboot from the comandline seems to have worked. Hmmm indeed. - alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fsck not cleaning on first try
On Sun, 19 Dec 1999, Alex Zepeda wrote: Hmm. It happened again. This time I was playing around with the vmware stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think this is the way to go, not bloating *our* procfs), and eventually when run panic'd the system. I just rebooted it (nearly a day later), and fsck cleaned it and printed some info, but then mount refused to mount it. A simple reboot from the comandline seems to have worked. Hmmm indeed. Ditto. mount was telling me my fs wasn't clean, but after I rebooted it was fine and it didn't fsck that second time. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sh(1) broken caching [was: Re: Broken sh(1)?]
On Fri, 17 Dec 1999, Martin Cracauer wrote: I still think we should *seriously* consider switching to pdksh. As I said before, pdksh has other bugs. Also we would loose all the PRs we received in the past. This testing effort by our user base is a valuable resource. From the tests I ran on all available shells, only bash2 is considerably better than the other shells, pdksh has other bugs than our ash, not less. HAHAHAHAHAHAHAHAHAHAhahahahahahahahahahahaha *cough, HACK, wheeze*. Ahem. Heh, bash2 considerably better. *continues ROFL* Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fsck not cleaning on first try
On Sun, 19 Dec 1999, Alex Zepeda wrote:
Hmm. It happened again. This time I was playing around with the vmware
stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think
this is the way to go, not bloating *our* procfs), and eventually when run
panic'd the system. I just rebooted it (nearly a day later), and fsck
cleaned it and printed some info, but then mount refused to mount it. A
simple reboot from the comandline seems to have worked. Hmmm indeed.
Ditto. mount was telling me my fs wasn't clean, but after I rebooted
it was fine and it didn't fsck that second time.
Bruce posted (but did not commit) what may be a fix for this a while back:
diff -c2 ffs_vfsops.c~ ffs_vfsops.c
*** ffs_vfsops.c~ Thu Nov 25 23:27:44 1999
--- ffs_vfsops.cSun Dec 5 05:12:51 1999
***
*** 218,222
--- 220,226
}
+ fs-fs_flags = ~FS_UNCLEAN;
if (fs-fs_clean == 0) {
+ fs-fs_flags |= FS_UNCLEAN;
if (mp-mnt_flag MNT_FORCE) {
printf(
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
more patch for secondary buffer, polling and DMA emulation in
pcm
cc: Seigo Tanimura tanimura
User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7
(=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon)
(i386--freebsd)
Organization: Digital Library Research Division, Information Techinology Centre, The
University of Tokyo
MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai")
Content-Type: multipart/mixed;
boundary="Multipart_Mon_Dec_20_13:44:01_1999-1"
--Multipart_Mon_Dec_20_13:44:01_1999-1
Content-Type: text/plain; charset=US-ASCII
If you have a trouble playing pcm with some applications, could you
please try the patch attached below? The patch does the following things:
- All ioctl(2)s go to see the secondary buffer(if I have forget nothing).
- chn_setblocksize() changes the size of the secondary buffer.
- chn_mmap() maps the secondary buffer.
- chn_poll() invokes DMA.
- chn_wrintr() performs DMA emulation for pcm devices with no DMA
functionality(requested by nyan).
With the patch, snes9x(w/-r 7) and RealPlayer G2 for Linux worked fine.
The range of blksz in chn_setblocksize() may need further tuning...
--Multipart_Mon_Dec_20_13:44:01_1999-1
Content-Type: text/plain; type=patch; charset=US-ASCII
Content-Disposition: attachment; filename="2ndbuf-19991220.diff"
Content-Transfer-Encoding: 7bit
diff -urN -x CVS -x compile -x SILVER -x RINA -x aic7xxx -x ata
sys.apictimer/dev/sound/isa/ad1816.c sys.2ndbuf/dev/sound/isa/ad1816.c
--- sys.apictimer/dev/sound/isa/ad1816.cMon Dec 20 11:13:56 1999
+++ sys.2ndbuf/dev/sound/isa/ad1816.c Mon Dec 20 11:45:28 1999
@@ -403,6 +403,7 @@
struct ad1816_info *ad1816 = ch-parent;
int wr, reg;
+ if (go == PCMTRIG_EMLDMAWR) return 0;
buf_isadma(ch-buffer, go);
wr = (ch-dir == PCMDIR_PLAY);
reg = wr? AD1816_PLAY : AD1816_CAPT;
diff -urN -x CVS -x compile -x SILVER -x RINA -x aic7xxx -x ata
sys.apictimer/dev/sound/isa/mss.c sys.2ndbuf/dev/sound/isa/mss.c
--- sys.apictimer/dev/sound/isa/mss.c Mon Dec 20 11:44:09 1999
+++ sys.2ndbuf/dev/sound/isa/mss.c Mon Dec 20 11:45:28 1999
@@ -1772,6 +1772,7 @@
{
struct mss_chinfo *ch = data;
+ if (go == PCMTRIG_EMLDMAWR) return 0;
buf_isadma(ch-buffer, go);
mss_trigger(ch, go);
return 0;
diff -urN -x CVS -x compile -x SILVER -x RINA -x aic7xxx -x ata
sys.apictimer/dev/sound/isa/sb.c sys.2ndbuf/dev/sound/isa/sb.c
--- sys.apictimer/dev/sound/isa/sb.cMon Dec 20 11:13:58 1999
+++ sys.2ndbuf/dev/sound/isa/sb.c Mon Dec 20 11:45:28 1999
@@ -860,6 +860,7 @@
sbchan_trigger(void *data, int go)
{
struct sb_chinfo *ch = data;
+ if (go == PCMTRIG_EMLDMAWR) return 0;
buf_isadma(ch-buffer, go);
if (go == PCMTRIG_START) sb_start(ch); else sb_stop(ch);
return 0;
@@ -928,6 +929,7 @@
esschan_trigger(void *data, int go)
{
struct sb_chinfo *ch = data;
+ if (go == PCMTRIG_EMLDMAWR) return 0;
switch (go) {
case PCMTRIG_START:
if (!ch-ess_dma_started)
diff -urN -x CVS -x compile -x SILVER -x RINA -x aic7xxx -x ata
sys.apictimer/dev/sound/pci/aureal.c sys.2ndbuf/dev/sound/pci/aureal.c
--- sys.apictimer/dev/sound/pci/aureal.cFri Dec 10 10:17:22 1999
+++ sys.2ndbuf/dev/sound/pci/aureal.c Mon Dec 20 11:45:28 1999
@@ -353,6 +353,7 @@
{
struct au_chinfo *ch = data;
struct au_info *au = ch-parent;
+ if (go == PCMTRIG_EMLDMAWR) return 0;
if (ch-dir == PCMDIR_PLAY) {
au_setadb(au, 0x11, (go)? 1 : 0);
if (!go) {
diff -urN -x CVS -x compile -x SILVER -x RINA -x aic7xxx -x ata
sys.apictimer/dev/sound/pci/csapcm.c sys.2ndbuf/dev/sound/pci/csapcm.c
--- sys.apictimer/dev/sound/pci/csapcm.cFri Dec 10 10:20:07 1999
+++ sys.2ndbuf/dev/sound/pci/csapcm.c Mon Dec 20 11:45:28 1999
@@ -386,6 +386,7 @@
struct csa_chinfo *ch = data;
struct csa_info *csa = ch-parent;
+ if (go == PCMTRIG_EMLDMAWR) return 0;
if (ch-dir == PCMDIR_PLAY) {
if (go == PCMTRIG_START)
csa_startplaydma(csa);
diff -urN -x CVS -x compile -x SILVER -x RINA -x aic7xxx -x ata
sys.apictimer/dev/sound/pci/es137x.c sys.2ndbuf/dev/sound/pci/es137x.c
--- sys.apictimer/dev/sound/pci/es137x.cMon Dec 20 11:14:02 1999
+++ sys.2ndbuf/dev/sound/pci/es137x.c Mon Dec 20 11:45:28 1999
@@ -367,6 +367,7 @@
struct es_info *es = ch-parent;
unsigned cnt = ch-buffer-dl / ch-buffer-sample_size - 1;
+ if (go == PCMTRIG_EMLDMAWR) return 0;
if (ch-dir == PCMDIR_PLAY) {
if (go == PCMTRIG_START) {
int b = (ch-fmt AFMT_S16_LE)? 2 : 1;
diff -urN -x CVS -x compile -x SILVER -x RINA -x aic7xxx -x ata
sys.apictimer/dev/sound/pci/t4dwave.c sys.2ndbuf/dev/sound/pci/t4dwave.c
--- sys.apictimer/dev/sound/pci/t4dwave.c Mon Dec 20 11:14:04 1999
+++ sys.2ndbuf/dev/sound/pci/t4dwave.c Mon Dec 20
more fun games...
as far as I know, I have all sources up to date including today, but eventually I got (on a Tyan board): ad0: ad_timeout: lost disk contact - resetting ata0: resetting devices .. ata0: mask=01 status0=50 status1=00 ata0: master: success setting up WDMA2 mode on PIIX4 chip done To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD vs GENERIC
In message [EMAIL PROTECTED] Nate Williams writes: : So, my only comment is that if you believe that the code is stable : enough to not negatively effect desktop systems, and not too much bloat, : then have at it. Note, enabling PCCARD functionality w/out APM will be : a losing situation for many laptops, and adding APM functionality for : desktops may be a losing situation. The apm driver has been in GENERIC and PCCARD for a long time. They are both have the "disabled" keyword so that the user can enable them in userconfig. Also, apm on desktops makes more sense now than it used to, as many of the mobos now support it fairly well... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD vs GENERIC
PCCARD used to exist separate from GENERIC due to the zp and ze drivers not being compatible with pccard's pcic driver. These drivers were removed from the system not too long ago by phk. The reason I added PCCARD to the system was because in the old code, I didn't trust the PCCARD functionality to not negatively effect the normal code. Rather than potentially destabilize the desktop systems, I kept the PCCARD kernel seperate. The other reason is for the installation, but that's now a non-issue I believe in -current, because one can use the standard install for both desktop/laptop systems. So, my only comment is that if you believe that the code is stable enough to not negatively effect desktop systems, and not too much bloat, then have at it. Note, enabling PCCARD functionality w/out APM will be a losing situation for many laptops, and adding APM functionality for desktops may be a losing situation. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD vs GENERIC
: So, my only comment is that if you believe that the code is stable : enough to not negatively effect desktop systems, and not too much bloat, : then have at it. Note, enabling PCCARD functionality w/out APM will be : a losing situation for many laptops, and adding APM functionality for : desktops may be a losing situation. The apm driver has been in GENERIC and PCCARD for a long time. I know. ;) revision 1.67 date: 1996/04/22 19:40:24; author: nate; state: Exp; lines: +7 -1 - add apm to the GENERIC kernel (disabled by default), and add some comments regarding apm to LINT .. They are both have the "disabled" keyword so that the user can enable them in userconfig. Also, apm on desktops makes more sense now than it used to, as many of the mobos now support it fairly well... Except that it appears to break timekeeping on desktop machines. Again, without APM, PCCARD support may give the impression as being non-functional, since people will close the lids on the boxes and it won't work correctly. :( Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New sound driver and Linux games
On 19-Dec-99 Brian W. Buchanan wrote: (and hence its sound system) in mind, not portability. snes9x plays a half second of audio for me, then loops it a few times before either SIGBUS or SIGSEGV. I've tried rebuilding it in case it had something to do with include file changes, but no dice. Does it mmap() the DMA sound buffers? I know Quake 2 does this, and preusmably so does Q3.. I have noticed that the new pcm driver doesn't seem to do mmap()'d audio very well :( --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMP
Hi people, I went to ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-19991218-CURRENT/README.TXT and read that document. Most hardware that I need to use is supported on that list, but I have a question: is SMP enabled in the GENERIC kernel in FreeBSD 4.0-current? we have a server that has dual 500Mhz P-III's and 2GB RAM...it's a waste to run Linux on it :\ Thanks! (PS: please reply in private as I am not subscribed to this list yet :) -- Emre Yildirim DH/DSS KeyID: 0xA007E75C | RSA KeyID: 0xFD5FD2C7 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868, newpcm, and Linux RealPlayer 5.0
On Sat, 18 Dec 1999, Donn Miller wrote: I just rebuilt my kernel from a recent cvsup. Of course, I have device pcm0 device sbc0 in my kernel config file. When I try to play a realaudio clip with Linux rvplayer (RealPlayer 5.0), rvplayer downloads the clip, and instead of playing the clip, rvplayer just hangs until I kill it. Is the ESS 1868 isa card working with sbc0 and pcm0? Anyone else have this problem with rvplayer? I tried the OSS driver modules, and the same rvplayer works OK there. The ESS 18xx support seems to be broken at the moment. I have one here and I'll fix it as soon as I get a chance to work on it. a recent commit changed the assumptions made by the upper layer code, breaking devices not using auto-init dma. last night i committed a fix to make the ess cards use autoinit, so they should work now. - cameron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current for production?
as there now is almost only talk about sound and ata drivers in this list, would it be adviseable to use a current-snap on a server machine (apache,samba,ftp) without need for sound and ata drivers (box with aic-scsi-only drives)? The integrated gcc-2.95.2 is so handy and current does all i want on my private box anyway. -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound and -current.
On 19 Dec, Devin Butterfield wrote: sbc0: Creative ViBRA16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq1,3 on isa0 pcm0: SB DSP 4.16 on sbc0 unknown0: Game at port 0x201 on isa0r Of course I'm not using the game port. :) Just add "device joy0" to your config. sbc0: Creative ViBRA16C at port 0x220-0x22f,0x330-0x331,0x388-0x38b ... pcm0: SB DSP 4.13 on sbc0 joy0: Generic PnP Joystick at port 0x200-0x207 on isa0 The only use for it (for me) is to allow to move the mousecursor with the joystick (X11). It´s nice to look into the face of WinXX-users while you present the possibilities of a highly configurable system to them. Bye, Alexander. -- This message guarded by an attack llama. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sh(1) broken caching [was: Re: Broken sh(1)?]
Over the last year, I did an extensive amount of testinging on bourne shell behaviour. bash2 was the only free sh clone that I never had to complain over. I'm surprised. Is there something substantially you'd like to contribute to the discussion, like - say - an example where bash-2.03 doesn't work well? It's definitely broken on some of my scripts before. If you want me to go try to find one of those cases, I will. If your experience is based on old bash1 stuff, forget it. bash got improved greatly since it is used as the standard shell for a UNIX clone in wide use. Just like our shell improved from the beatings it got because it has been the standard script-executing shell on FreeBSD and NetBSD for (together) 10 years now. ISTR that bash1 had fundamental design flaws; it's been redesigned? Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Got diskless Sun booting from FreeBSD server...
I'll put one together over the holidays :) Patrick On 20 Dec, Jesper Skriver wrote: Hi, How about adding a "howto" to the handbook ? /Jesper On Sun, Dec 19, 1999 at 09:38:09PM +0100, Ron Klinkien wrote: Thanks to Ian Dowse and Patrick Gardella i got my SPARCclassic booting and running as a nice Xterminal server. [cut] Thanks all. Ron. /Jesper To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sh(1) broken caching [was: Re: Broken sh(1)?]
In [EMAIL PROTECTED], Brian Fundakowski Feldman wrote: Is there something substantially you'd like to contribute to the discussion, like - say - an example where bash-2.03 doesn't work well? It's definitely broken on some of my scripts before. If you want me to go try to find one of those cases, I will. That would be nice. I'm collecting items for a formal, automatic test suite. That goes to every reader of this list, of course :-). Thanks Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current for production?
On 20 Dec 1999, Fritz Heinrichmeyer wrote: as there now is almost only talk about sound and ata drivers in this list, would it be adviseable to use a current-snap on a server machine (apache,samba,ftp) without need for sound and ata drivers (box with aic-scsi-only drives)? The integrated gcc-2.95.2 is so handy and current does all i want on my private box anyway. I think you'd have better luck asking people what their experiences with the software have been, rather than asking for a recommendation. No one is likely to want to take the responsibility of recommending -current for a production site, but they'll be happy to share their own experiences and let you come to your own conclusion. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rlogin receiving sig 11 (randomly)
Hi, Before I dig into this, I'd like to know if anyone else is seeing the following on -current: (Not tested/seen on stable/release). Dec 20 10:57:58 magenta /kernel: pid 9869 (rlogin), uid 227: exited on signal 11 Dec 20 10:58:02 magenta /kernel: pid 9875 (rlogin), uid 227: exited on signal 11 This happens very randomly - 1 out of 50. But, when it fails, it typically fails multiple times as shown above. I've seen this over the last 5 weeks or so. Thanks, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current for production?
I'm inclined to agree. I have had great luck in production boxes with FreeBSD-CURRENT, but it's not reccomended to use -CURRENT for production just because sometimes things break. :-) = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Mon, 20 Dec 1999, Ben Rosengart wrote: On 20 Dec 1999, Fritz Heinrichmeyer wrote: as there now is almost only talk about sound and ata drivers in this list, would it be adviseable to use a current-snap on a server machine (apache,samba,ftp) without need for sound and ata drivers (box with aic-scsi-only drives)? The integrated gcc-2.95.2 is so handy and current does all i want on my private box anyway. I think you'd have better luck asking people what their experiences with the software have been, rather than asking for a recommendation. No one is likely to want to take the responsibility of recommending -current for a production site, but they'll be happy to share their own experiences and let you come to your own conclusion. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cc taking a signal 11
Hi,
While I'm at it, a co-worker gave this one to me earlier today.
cc: Internal compiler error: program cc1 got fatal signal 11
4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999
FreeBSD(root)/tmp %cc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
FreeBSD(root)/tmp %cc -O foo.c -o foo.o -c
cc: Internal compiler error: program cc1 got fatal signal 11
static void getsig11(parfree,dbl,lambda)
long parfree;
double *dbl;
double *lambda;
{
long i, j;
j = -1;
for(i = 0; i parfree; i++) {
j += i+1;
dbl[j] *= (1.0 + *lambda);
}
return;
}
Yes, the algorithm looks funny, but is correct. The program will
compile correctly if the 'j += i+1;' is changed to 'j = i+1;' or if
the variable 'lambda' is changed from a pointer to an actual value.
Anyone want to take a stab at this? I'm not a big compiler
person myself... (Dave, you there?).
Thanks,
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: cc taking a signal 11
Hi,
While I'm at it, a co-worker gave this one to me earlier today.
cc: Internal compiler error: program cc1 got fatal signal 11
4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999
FreeBSD(root)/tmp %cc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
FreeBSD(root)/tmp %cc -O foo.c -o foo.o -c
cc: Internal compiler error: program cc1 got fatal signal 11
static void getsig11(parfree,dbl,lambda)
long parfree;
double *dbl;
double *lambda;
{
long i, j;
j = -1;
for(i = 0; i parfree; i++) {
j += i+1;
dbl[j] *= (1.0 + *lambda);
}
return;
}
Yes, the algorithm looks funny, but is correct. The program will
compile correctly if the 'j += i+1;' is changed to 'j = i+1;' or if
the variable 'lambda' is changed from a pointer to an actual value.
Anyone want to take a stab at this? I'm not a big compiler
person myself... (Dave, you there?).
Yes - I'm here :-)
Typically - signal 11 problems from GNU's front-end are hardware
memory issues
I will add that a quick test on a 3.3 system compiles this just
fine (Systems/C compiles it as well.)
I would suspect hardware problems first.
As I have learned from painful experience, *always* use ECC or at least
parity memory...
- Dave R. -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Empty core files left with coredumpsize=0 (Was Re: cc taking a signal 11)
Hi,
While I'm at it, a co-worker gave this one to me earlier today.
cc: Internal compiler error: program cc1 got fatal signal 11
4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999
FreeBSD(root)/tmp %cc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
FreeBSD(root)/tmp %cc -O foo.c -o foo.o -c
cc: Internal compiler error: program cc1 got fatal signal 11
static void getsig11(parfree,dbl,lambda)
long parfree;
double *dbl;
double *lambda;
{
long i, j;
j = -1;
for(i = 0; i parfree; i++) {
j += i+1;
dbl[j] *= (1.0 + *lambda);
}
return;
}
Yes, the algorithm looks funny, but is correct. The program will
compile correctly if the 'j += i+1;' is changed to 'j = i+1;' or if
the variable 'lambda' is changed from a pointer to an actual value.
Anyone want to take a stab at this? I'm not a big compiler
person myself... (Dave, you there?).
I'll verify the compiler bug exists.
However, I'll also point out that csh is still dumping empty
core files when coredumpsize is 0. This isn't happening with tcsh
though.
-Skots
--
Scott G. Akmentins-Taylor InterNet: [EMAIL PROTECTED]
MRY Systems [EMAIL PROTECTED]
(Skots Gregorijs Akmentins-Teilors -- just call me "Skots")
- Labak miris neka sarkans -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: cc taking a signal 11
Hi,
While I'm at it, a co-worker gave this one to me earlier today.
cc: Internal compiler error: program cc1 got fatal signal 11
4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999
FreeBSD(root)/tmp %cc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
FreeBSD(root)/tmp %cc -O foo.c -o foo.o -c
cc: Internal compiler error: program cc1 got fatal signal 11
static void getsig11(parfree,dbl,lambda)
long parfree;
double *dbl;
double *lambda;
{
long i, j;
j = -1;
for(i = 0; i parfree; i++) {
j += i+1;
dbl[j] *= (1.0 + *lambda);
}
return;
}
Yes, the algorithm looks funny, but is correct. The program will
compile correctly if the 'j += i+1;' is changed to 'j = i+1;' or if
the variable 'lambda' is changed from a pointer to an actual value.
Anyone want to take a stab at this? I'm not a big compiler
person myself... (Dave, you there?).
Yes - I'm here :-)
Typically - signal 11 problems from GNU's front-end are hardware
memory issues
I will add that a quick test on a 3.3 system compiles this just
fine (Systems/C compiles it as well.)
I would suspect hardware problems first.
As I have learned from painful experience, *always* use ECC or at least
parity memory...
- Dave R. -
Nawww... I've tried this on a bunch of different machines.. as a matter
of fact it replicates with gcc version 2.7.2.1 from December of last
year. I find it hard to believe that I have 80 machines that all
exhibit the exact same memory failure... :-)
-John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: cc taking a signal 11
Nawww... I've tried this on a bunch of different machines.. as a matter of fact it replicates with gcc version 2.7.2.1 from December of last year. I find it hard to believe that I have 80 machines that all exhibit the exact same memory failure... :-) -John Yep - others have reported the problem is gcc... I'd suggest taking this up with Cygnus (http://www.cygnus.com) - Dave R. - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA: more Promise Ultra wedges
Soren Schmidt writes: It seems Andrew Gallatin wrote: Søren, It looks like I spoke to soon when I said the world was safe for Promise Ultra users: ad3: ad_timeout: lost disk contact - resetting ata4: resetting devices .. ad3: HARD WRITE ERROR blk# 6594768ad3: DMA problem en countered, fallback to PIO mode ad3: DMA problem encountered, fallback to PIO mode done ad1: UDMA CRC READ ERROR blk# 10522095 retrying ad3: ad_timeout: lost disk contact - resetting ata4: resetting devices .. done Is the above all info, or is it snipped somehow, its looks a bit wierd.. That was snipped directly from a serial console log. Now that I have the machine rebooted, here are the syslog messages from /var/log/messages: Dec 17 17:01:44 waffle /kernel: ad3: ad_timeout: lost disk contact - resetting Dec 17 17:01:44 waffle /kernel: ata4: resetting devices .. ad3: HARD WRITE ERROR blk# 6594768ad3: DMA problem encountered, fallback to PIO mode Dec 17 17:01:44 waffle /kernel: ad3: DMA problem encountered, fallback to PIO mode Dec 17 17:01:44 waffle /kernel: done Dec 17 17:02:09 waffle /kernel: ad1: UDMA CRC READ ERROR blk# 10522095 retrying Dec 17 17:02:14 waffle /kernel: ad3: ad_timeout: lost disk contact - resetting Dec 17 17:02:14 waffle /kernel: ata4: resetting devices .. done BTW, I'd really like a tunable or some way to prevent a permanent fallback to PIO. I'm more than willing to tolerate one hard error per week or so on a disk which sees 10s of gigabytes of data read written between errors. Hmm, I'll think about what we can do here... Thanks! That would be greatly appreciated. Cheers, Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cc taking a signal 11
On Mon, 20 Dec 1999, Thomas David Rivers wrote:
! FreeBSD(root)/tmp %cc -O foo.c -o foo.o -c
! cc: Internal compiler error: program cc1 got fatal signal 11
!
!
!
! static void getsig11(parfree,dbl,lambda)
! long parfree;
! double *dbl;
! double *lambda;
! {
! long i, j;
! j = -1;
! for(i = 0; i parfree; i++) {
!j += i+1;
!dbl[j] *= (1.0 + *lambda);
!}
! return;
! }
!
!
!Yes, the algorithm looks funny, but is correct. The program will
! compile correctly if the 'j += i+1;' is changed to 'j = i+1;' or if
! the variable 'lambda' is changed from a pointer to an actual value.
!
!Anyone want to take a stab at this? I'm not a big compiler
! person myself... (Dave, you there?).
!
! Yes - I'm here :-)
!
! Typically - signal 11 problems from GNU's front-end are hardware
! memory issues
!
! I will add that a quick test on a 3.3 system compiles this just
! fine (Systems/C compiles it as well.)
!
! I would suspect hardware problems first.
!
! As I have learned from painful experience, *always* use ECC or at least
! parity memory...
!
! - Dave R. -
This seems to only be an issue if you're compiling with optimization.
I *think* it's because the compiler tries to make `j' a register. If you
explicitly declare `j' a volatile, you should not get this.
Is this correct?
Bosko.
.. . . . . . . .. .. . .
. Bosko Milekic -- [EMAIL PROTECTED] . .
. . . .. . . . . .. .
. WWW: http://pages.infinit.net/bmilekic/ .
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
is this really a bad disklabel?
(This is probably a -questions issue, but I've tried without success, and the boot programs are all -current.) I can't seem to boot from wd1s3a. When I run the loader, and set currdev=disk2s3a, it won't ls, and when I try to lsdev, it says there is a bad partition table on wd1. I found it necessary to change the BIOS parameters using sysinstall before I could write the label and boot1, boot2. (I believe the boot and loader on both drives is -current now.) When I run fdisk from Win98, drive D: is shown as 504MB in toto, although the partition sizes are correct. wd0 is WDC AC313000R (primary master), while wd1 is WDC WC136AA (secondary master). I can run multiboot on wd1 using 'F5' in the wd0 multiboot, but attempting to boot wd1s3 thereafter fails, returning to the multiboot. Here's the partion table: *** Working on device /dev/rwd1 *** parameters extracted from in-core disklabel are: cylinders=1653 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1653 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6,(Primary 'big' DOS ( 32MB)) start 63, size 4192902 (2047 Meg), flag 0 beg: cyl 0/ sector 1/ head 1; end: cyl 260/ sector 63/ head 254 The data for partition 2 is: sysid 130,(Linux swap or Solaris x86) start 4192965, size 273105 (133 Meg), flag 0 beg: cyl 261/ sector 1/ head 0; end: cyl 277/ sector 63/ head 254 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 14795865, size 11759580 (5741 Meg), flag 80 (active) beg: cyl 921/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 254 The data for partition 4 is: sysid 131,(Linux filesystem) start 4466070, size 10329795 (5043 Meg), flag 0 beg: cyl 278/ sector 1/ head 0; end: cyl 920/ sector 63/ head 254 Both drives are LBA in the BIOS. I modelled wd1 on wd0: *** Working on device /dev/rwd0 *** parameters extracted from in-core disklabel are: cylinders=1582 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1582 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 6,(Primary 'big' DOS ( 32MB)) start 63, size 4192902 (2047 Meg), flag 0 beg: cyl 0/ sector 1/ head 1; end: cyl 260/ sector 63/ head 254 The data for partition 2 is: sysid 130,(Linux swap or Solaris x86) start 4192965, size 273105 (133 Meg), flag 0 beg: cyl 261/ sector 1/ head 0; end: cyl 277/ sector 63/ head 254 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 14795865, size 10618965 (5185 Meg), flag 80 (active) beg: cyl 921/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 254 The data for partition 4 is: sysid 131,(Linux filesystem) start 4466070, size 10329795 (5043 Meg), flag 0 beg: cyl 278/ sector 1/ head 0; end: cyl 920/ sector 63/ head 254 The BIOS and fdisk agree on the c/h/s limits. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
building world on pre-signals-change systems
If I recall correctly, someone posted recently that the time is not far off when one will be able to make world on an older, pre-signals-change system. Is there going to be an announcement when that happens, or has it perhaps happened already? I'm running an Oct 1 -current box, and I will eventually want to update it, and I'd like to know when it's safe. Thanks in advance. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Status on building modula-3 and cvsup on -current ...
What's the latest on building modula 3 and cvsup on -current systems? thanxs ... #:^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rlogin receiving sig 11 (randomly)
On Mon, 20 Dec 1999 11:05:30 -0500 (EST), "John W. DeBoskey" [EMAIL PROTECTED] said: This happens very randomly - 1 out of 50. But, when it fails, it typically fails multiple times as shown above. I've seen this over the last 5 weeks or so. `rlogin -x' has consistently failed for me (sending garbage on the transmit channel) since something happened a few months ago. It's somewhere between September 10 (which still works on my desktop) and late November (can't get a precise date right now) (which fails on my laptop). Compiler upgrade issue? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Archive mirror problem
I'm trying to get a snapshot from current.freebsd.org and keep getting this error all morning: Failure at end of remote directory () because: timed out This is using mirror.pl. It's worked flawlessly in the past, and for everything else I do. Has something changed on current.freebsd.org? _F To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: building world on pre-signals-change systems
Ben Rosengart wrote: If I recall correctly, someone posted recently that the time is not far off when one will be able to make world on an older, pre-signals-change system. You can already do a buildworld, but you still have to make and install a new kernel in order to do a installworld. At this time you should therefore not use `make world' yet. A full upgrade path can only be offered if the kernel is also made along with a buildworld and is also installed as part of the installation process. This requires a bit more work though. -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sio.c
I have included a patch for my Diamond SupraExpress 56i to be detected:
--- sio.c.orig Sat Dec 11 19:51:29 1999
+++ sio.c Sat Dec 11 19:51:20 1999
@@ -553,6 +553,7 @@
{0x31307256, NULL}, /* USR3031 */
{0x8020b04e, NULL}, /* SUP2080 */
{0x8024b04e, NULL}, /* SUP2480 */
+{0x7420b04e, NULL},/* SUP2070 */
{0}
};
Thanks for committing it :-) (please?)
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems Administrator | ICQ #: 24767726 |
| and student at The | AIM: AgRSkaterq |
| The University of Maryland, | Website: (Under Construction) |
| College Park. | http://www.wam.umd.edu/~culverk/|
=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: vm_page_remove panic
:Hi, : :I have been seeing vm_page_remove panic three times since :last week. During make world once, cvsup twice. It seems :reproducible. : :Any clue? : :Thanks : :Tammy What's your filesystem configuration? Do a 'df'. Are any of the filesystems non-standard? -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
error with install, Unable to make device nodes...
[ sorry if you get this twice, it didn't seem to go through the first time ] I'm having a problem trying to install the 12/20/99 -current snapshot. When I finalize all the settings and sysinstall is about to partition/setup the drive I get the following message: Unable to make device node of /dev/ad0s1b in /dev! The creation of filesystems will be aborted. If I switch to the second virtual terminal it says: DEBUG: Scanning disk ad0 for root filesystem DEBUG: Scanning disk ad0 for swap partitions DEBUG: MakeDev: Unable to lookup user "root". [ last line repeated several times ] The drive I'm installing on is a Seagate ST36451A IDE drive. I've tried switching between Auto and User(with proper geometry values) in the BIOS but neither worked. Is this a user error or is there something else wrong here? I checked the mailing lists but couldn't find anything appropriate. Thanks, - Mike Heffner [EMAIL PROTECTED] Fredericksburg, VA ICQ# 882073 Date: 20-Dec-99 Time: 15:44:09 - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error with install, Unable to make device nodes...
On Mon, 20 Dec 1999, Mike Heffner wrote: Unable to make device node of /dev/ad0s1b in /dev! The creation of filesystems will be aborted. If I switch to the second virtual terminal it says: DEBUG: Scanning disk ad0 for root filesystem DEBUG: Scanning disk ad0 for swap partitions DEBUG: MakeDev: Unable to lookup user "root". [ last line repeated several times ] aol Me too. /aol This is not a Danish thing however, this fails with scsi drives as well. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vm_page_remove panic
MattWhat's your filesystem configuration? Do a 'df'. Are any of the Mattfilesystems non-standard? non-standard? You mean block size, etc? I don't have access to that machine right now but it should be what you call standard ;-) I'll get back to you later today. No special newfs flags for all filesystems. It's just plain sysinstall created filesystems. By the way, all filesystems including / are softupdates enabled. Thanks Tammy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mic cannot be deactivated
It appears that the microphone controls for newpcm are not functioning, at least for my sound device. I've got a Vaio 505TX laptop. On probing the sound device, the speaker and mic together cause terrible feedback. mixer shows 0:0 for the mic, and adjusting this or using 'mixer -rec mic' has no effect. Otherwise, sound seems to work OK (tested w/ mpg123) With source from last night, I've got the following in my kernel config: optionsPNPBIOS device pcm0 device sbc0 which gives the following output on boot: unknown0: PNP0c02 at port 0x4d0-0x4d1,0x80,0x72-0x73,0x370-0x371,0xb2-0xb3,0x8000-0x804f,0x2180-0x218f,0x230-0x233 iomem 0xfffe-0x on isa0 unknown1: PNP0c01 at iomem 0-0x9,0xe8000-0xf,0x10-0x7ff on isa0 unknown2: PNP0200 at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown: PNP can't assign resources unknown3: PNP0100 at port 0x40-0x43 irq 0 on isa0 unknown4: PNP0b00 at port 0x70-0x71 irq 8 on isa0 unknown: PNP0303 can't assign resources unknown5: PNP0c04 at port 0xf0-0xff irq 13 on isa0 unknown: PNP0800 can't assign resources unknown6: PNP0a03 at port 0xcf8-0xcff on isa0 sbc0: ESS ES1879 at port 0x220-0x22f,0x388-0x38b,0x320-0x321 irq 5 drq 1,5 on isa0 pcm0: SB DSP 3.01 (ESS mode) on sbc0 unknown7: PNP0e03 at port 0x3e0-0x3e1 on isa0 unknown: PNP0700 can't assign resources unknown: PNP0401 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0510 can't assign resources unknown: ROK0010 can't assign resources unknown: PNP0f13 can't assign resources unknown8: ESS0009 at port 0x800-0x807 on isa0 I've also tried removing the PNPBIOS option, and using device pcm0 device sbc0at isa? port 0x220 irq 5 drq 1 flags 0x15 This produces different boot mesages, but the same behavior re. the mic. sbc0: ESS 688 at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 pcm0: SB DSP 3.01 (ESS mode) on sbc0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error with install, Unable to make device nodes...
On 20-Dec-99 Bill Fumerola said: | On Mon, 20 Dec 1999, Mike Heffner wrote: | | | Unable to make device node of /dev/ad0s1b in /dev! | The creation of filesystems will be aborted. | | If I switch to the second virtual terminal it says: | | DEBUG: Scanning disk ad0 for root filesystem | DEBUG: Scanning disk ad0 for swap partitions | DEBUG: MakeDev: Unable to lookup user "root". |[ last line repeated several times ] | | aol | Me too. | /aol | | This is not a Danish thing however, this fails with scsi drives as well. | Well, after some more tests...running sysinstall many times over ;(...I've found that it breaks between the 12/16 and 12/17 snapshots. Not sure where to start looking for problems though. I checked MAKEDEV (since the error seemed to be coming from that) but didn't see anything in that time period. What else is there to check? Later, - Mike Heffner [EMAIL PROTECTED] Fredericksburg, VA ICQ# 882073 Date: 20-Dec-99 Time: 17:06:27 - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rlogin receiving sig 11 (randomly)
`rlogin -x' has consistently failed for me (sending garbage on the transmit channel) since something happened a few months ago. It's somewhere between September 10 (which still works on my desktop) and late November (can't get a precise date right now) (which fails on my laptop). Compiler upgrade issue? I still have one -CURRENT box that is 100% current, minus the compiler which is still the last EGCS 1.1.2. I wouldn't mind having you test a binary compiled on that machine so we'd know for sure. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent current hangs frequently for 1 to 2 seconds.
On Saturday, 18 December 1999 at 20:16:53 -0800, Matthew Dillon wrote: I've just upgraded to -CURRENT as of yesterday, and I'm noticing a number of occasions where all activity ceases for a second or two at a time; it seems to be related to IDE disk activity with the new ATA driver, but I don't have much evidence. I'm running a SiS 5591 chipset. Has anybody else seen something like this? It's possible that the blockages you are seeing are due to the ATA driver, but it's also possible that they are due to a bug in the buffer cache flushing code which the following patch fixes. So try the patch and see if that fixes your problem. If it doesn't then we can at least rule it out as being the cause of the problem you are seeing. Thanks. I've put in the patch, but I'm still seeing the problems. It seems to be related to SCSI activity (I'm currently performing a backup on a DLT drive, and apart from that very little disk I/O). Any other ideas? It seems to me as if the whole system freezes (keystrokes don't echo, for example), so possibly something is going into splhigh for too long. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent current hangs frequently for 1 to 2 seconds.
:Thanks. I've put in the patch, but I'm still seeing the problems. It :seems to be related to SCSI activity (I'm currently performing a :backup on a DLT drive, and apart from that very little disk I/O). Any :other ideas? It seems to me as if the whole system freezes :(keystrokes don't echo, for example), so possibly something is going :into splhigh for too long. : :Greg No, this is very odd. Certainly reading from disk should not cause any blockages. But DLT SCSI -- there are lots of possiblities there. Is the DLT device sharing the same SCSI bus as the disks? I've historically had bad luck with a shared arrangement and now always put SCSI tape units on their own SCSI bus. If the SCSI bus is hanging something should show up in the kernel logs or dmesg output. Another possibility is that the SCSI operation is causing a hangup or bringing out a bug in the networking somewhere. A lockup for a second or two could be an indication of packet loss. Haven't there been a couple of mbuf-related commits recently? It would be something to look review, anyway. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent current hangs frequently for 1 to 2 seconds.
On Monday, 20 December 1999 at 16:19:06 -0800, Matthew Dillon wrote: :Thanks. I've put in the patch, but I'm still seeing the problems. It :seems to be related to SCSI activity (I'm currently performing a :backup on a DLT drive, and apart from that very little disk I/O). Any :other ideas? It seems to me as if the whole system freezes :(keystrokes don't echo, for example), so possibly something is going :into splhigh for too long. : :Greg No, this is very odd. Certainly reading from disk should not cause any blockages. But DLT SCSI -- there are lots of possiblities there. Is the DLT device sharing the same SCSI bus as the disks? Yes. I've historically had bad luck with a shared arrangement and now always put SCSI tape units on their own SCSI bus. For other reasons, I intend to do just this, though I'm not sure it's a good idea: for one thing, I don't have any spare PCI slots, so it will have to be a 1542B. But it will be worth checking. It's possible you might be on to something. I've been running iostat at 1 second intervals, and during the last hang I saw: ttyad2 da1 sa1 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 36 142 7.75 95 0.72 0.00 0.00 0 10.00 27 0.27 29 0 9 1 61 21 142 8.00 69 0.54 0.00 0.00 00.00 0 0.00 6 0 1 0 93 37 143 8.00 44 0.34 0.00 8.00 30.00 0 0.00 5 0 1 1 94 41 142 1.76 106 0.18 16.00 5.25 4 10.00 14 0.13 24 0 18 0 57 15 143 1.98 87 0.17 0.00 0.00 0 10.00 16 0.15 30 0 15 2 54 Note that the stop in tape activity corresponds with a start in disk activity. I'll keep an eye on that and see if it looks the same the next time. If the SCSI bus is hanging something should show up in the kernel logs or dmesg output. Right. But there's nothing there. Another possibility is that the SCSI operation is causing a hangup or bringing out a bug in the networking somewhere. A lockup for a second or two could be an indication of packet loss. Haven't there been a couple of mbuf-related commits recently? It would be something to look review, anyway. I don't see any evidence of network participation. All the activity here is local. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent current hangs frequently for 1 to 2 seconds.
:It's possible you might be on to something. I've been running iostat :at 1 second intervals, and during the last hang I saw: : : ttyad2 da1 sa1 cpu : tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id : 36 142 7.75 95 0.72 0.00 0.00 0 10.00 27 0.27 29 0 9 1 61 : 21 142 8.00 69 0.54 0.00 0.00 00.00 0 0.00 6 0 1 0 93 : 37 143 8.00 44 0.34 0.00 8.00 30.00 0 0.00 5 0 1 1 94 : 41 142 1.76 106 0.18 16.00 5.25 4 10.00 14 0.13 24 0 18 0 57 : 15 143 1.98 87 0.17 0.00 0.00 0 10.00 16 0.15 30 0 15 2 54 : :Note that the stop in tape activity corresponds with a start in disk :activity. I'll keep an eye on that and see if it looks the same the :next time. Tape drives may: * Not support disconnection (the SCSI bus is locked through the entire write sequence), or only partially support disconnection but run the bus so slowly that other devices are left out in the cold. * Implement a crappy SCSI command stack that breaks down when higher-speed operations are running on the same bus (e.g. the disks with their higher synchronous transfer rates). * Not properly terminate the SCSI bus (especially when mixing bus architectures. For example, a tape drive may only half-terminate a wide SCSI bus. Never use a tape drive to terminate a SCSI bus, not even an older SCSI bus. * Introduce too much noise onto the SCSI bus due to bad design. At one time or another I've been hit with all of these problems. You may be able to work around some of them by going into the adaptec bios config and intentionally slowing down all the devices on the bus. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ESS 1868, newpcm,
Cameron, Thanks, my sound now works but something is different. I am getting very high frequency oscillations that I've never had and don't understand. It must have something to to with the mike and the speakers on my laptop but there has never been regenerative feedback between them before. Could the driver somehow be responsible? Thanks again, ed Cameron Grant wrote: On Sat, 18 Dec 1999, Donn Miller wrote: I just rebuilt my kernel from a recent cvsup. Of course, I have device pcm0 device sbc0 in my kernel config file. When I try to play a realaudio clip with Linux rvplayer (RealPlayer 5.0), rvplayer downloads the clip, and instead of playing the clip, rvplayer just hangs until I kill it. Is the ESS 1868 isa card working with sbc0 and pcm0? Anyone else have this problem with rvplayer? I tried the OSS driver modules, and the same rvplayer works OK there. The ESS 18xx support seems to be broken at the moment. I have one here and I'll fix it as soon as I get a chance to work on it. a recent commit changed the assumptions made by the upper layer code, breaking devices not using auto-init dma. last night i committed a fix to make the ess cards use autoinit, so they should work now. - cameron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mount msdos floppy
Doug White wrote: On Sun, 19 Dec 1999, Edwin Culp wrote: When I try to mount an msdos floppy, that I almost never do, I am getting the following: # mount -tmsdos /dev/fd0 /mnt msdos: vfsload(msdos): Exec format error Disk works in windows. Your /modules/msdos.ko file is corrupted. cd /sys/modules/msdos make depend all install. If that doesn't work rebuild your kernle with 'options MSDOS'. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org I put the option back into the kernel. I had forgotten that I had taken it out some time ago. It works fine. Thanks, ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error with install, Unable to make device nodes...
On Mon, Dec 20, 1999 at 03:45:01PM -0500, Mike Heffner wrote:
[ sorry if you get this twice, it didn't seem to go through the first time ]
I'm having a problem trying to install the 12/20/99 -current snapshot. When I
finalize all the settings and sysinstall is about to partition/setup the drive I
get the following message:
Unable to make device node of /dev/ad0s1b in /dev!
The creation of filesystems will be aborted.
If I switch to the second virtual terminal it says:
DEBUG: Scanning disk ad0 for root filesystem
DEBUG: Scanning disk ad0 for swap partitions
DEBUG: MakeDev: Unable to lookup user "root".
[ last line repeated several times ]
I am seeing this as well. I am also trying to install the
4.0-19991220-CURRENT snapshot (on an IBM 9G IDE drive). From scanning
the sources it looks like this message (the Unable to lookup user
"root") is being issued from src/lib/libdisk/create_chunk.c because the
getpwnam("root") has failed. I have not investigated it any further
yet, so I don't have any idea why getpwnam() failed.
Bob
--
Bob Willcox Don't tell me that worry doesn't do any good.
[EMAIL PROTECTED] I know better. The things I worry about don't
Austin, TX happen. -- Watchman Examiner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
