Re: pcm0 sblive and dodgy irq: 100000
On Sun, 23 Jul 2000, Andrew Tulloch wrote:
I cvsup and built world on friday, after noticing I'd forgotten to add
sound support I recompiled today with device pcm added to my kernel config
and am no recieing kernel messages saying: pcm0: dodgy irq: 100
anyone got any clues?
FWIW, I cvsup'd/built world/etc. last night (4.1-RC) and my SB is seen by
device pcm as follows:
[101]mike@zeus{mike}$ cat /dev/sndstat
FreeBSD Audio Driver (newpcm) Jul 22 2000 19:24:24
Installed devices:
pcm0: Creative EMU10K1 at io 0x1060 irq 10 (4p/3r channels duplex)
But, after installing xmms, loading an mp3, and clicking 'play', the
system reboots. I've tried this a few times with a few different audio
files. I'm cvsup'ing again now, and I still want to try compiling xmms
with the flags mentioned earlier.
-mrh
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: make buildworld of RELENG4 fails only on 3.1-RELEASE
On Sat, 22 Jul 2000, Fred Condo wrote: I've updated several FreeBSD 4.x-STABLE systems to RELENG4 (4.1-RC) using the procedure in the UPDATING file. I have a 3.1-RELEASE system (whose uptime is currently 426 days), which I would like to update to 4-STABLE in a week's time with minimal down time. So I would like to pre-build the world and kernel before I go to the ISP and do the actual update. mkstemps() was only added to 3.x shortly before 3.4-RELEASE. It may be possible to develop a fix for the upgrade case, but in the meantime you could upgrade to 3.4-R and then to 4.1-RC. I assume that still works. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall resetting USA_RESIDENT=NO
On Sun, 23 Jul 2000, Larry Rosenman wrote: Yes I am. I cvsup'd recently, ran /stand/sysinstall to run the XFree86 config, and my USA_RESIDENT take got changed to NO. sysinstall isn't built or installed as part of make world - did you recompile it specifically? Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall resetting USA_RESIDENT=NO
Nope. I ass/u/med it was. Larry On Sun, 23 Jul 2000, Larry Rosenman wrote: Yes I am. I cvsup'd recently, ran /stand/sysinstall to run the XFree86 config, and my USA_RESIDENT take got changed to NO. sysinstall isn't built or installed as part of make world - did you recompile it specifically? Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall resetting USA_RESIDENT=NO
sysinstall isn't built or installed as part of make world - did you recompile it specifically? Kris Yes. I also built and ran it in gdb to see exactly the problem. - Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall resetting USA_RESIDENT=NO
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I can confirm that it DOES behave like this as of my last make world (yes, I rebuilt sysinstall as well) which was May 30 2000. - -r-xr-xr-x 1 root wheel 770340 May 30 01:30 /stand/sysinstall* So odds are it's still there, I haven't cvsup'd lately though... Matt On Sun, 23 Jul 2000, Larry Rosenman wrote: : : Nope. I ass/u/med it was. : : Larry : On Sun, 23 Jul 2000, Larry Rosenman wrote: : : Yes I am. I cvsup'd recently, ran /stand/sysinstall to run the : XFree86 config, and my USA_RESIDENT take got changed to NO. : : sysinstall isn't built or installed as part of make world - did you : recompile it specifically? : : Kris : : -- : In God we Trust -- all others must submit an X.509 certificate. : -- Charles Forsythe [EMAIL PROTECTED] : : : : -- : Larry Rosenman http://www.lerctr.org/~ler : Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED] : US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 : : : To Unsubscribe: send mail to [EMAIL PROTECTED] : with "unsubscribe freebsd-stable" in the body of the message : * Matt Heckaman - mailto:[EMAIL PROTECTED] http://www.lucida.qc.ca/ * * GPG fingerprint - A9BC F3A8 278E 22F2 9BDA BFCF 74C3 2D31 C035 5390 * -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.2 (FreeBSD) Comment: http://www.lucida.qc.ca/pgp iD8DBQE5e3H/dMMtMcA1U5ARAv+1AJ4wRH7jREOpuQlRtFOea5uzQZBWGQCcCSo1 SPBPpp/JvSw0CJZRYI0xVgs= =6Cx1 -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall resetting USA_RESIDENT=NO
Kris Kennaway wrote: On Sun, 23 Jul 2000, Larry Rosenman wrote: Yes I am. I cvsup'd recently, ran /stand/sysinstall to run the XFree86 config, and my USA_RESIDENT take got changed to NO. sysinstall isn't built or installed as part of make world - did you recompile it specifically? Kris No, he's right. sysinstall is definitely broken in this respect, and I'm definitely interested in your patches to fix it. :) -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pcm0 sblive and dodgy irq: 100000
Mike Hoskins wrote: pcm0: Creative EMU10K1 at io 0x1060 irq 10 (4p/3r channels duplex) But, after installing xmms, loading an mp3, and clicking 'play', the system reboots. You have ECC memory, right? This is a known problem. Cameron will soon have some ECC memory himself so he can reproduce this and hopefully fix it. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: root mount failed
On Sun, 23 Jul 2000, Charles Martin wrote: no devsw (majdev=0 bootdev=0xa030) Mounting root from ufs:/dev/ad0s2a no such device 'ad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Uhh... What is (or, better yet, isn't) in your new kernel? This looks like your kernel isn't recognizing your ATAPI disks... I.E. there's no driver in your kernel. Boot kernel.old, RTFM /usr/src/sys/i386/conf/LINT, try again. Specifically... I've seen people misread LINT's comment: # You only need one "device ata" for it to find all # PCI ATA/ATAPI devices on modern machines. Then go out and compile a kernel with only 'device ata' in it. With no 'atadisk' line, ad* isn't detected, so... no / for you. -mrh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Driver for Adaptec/Dell/HP PCI:SCSI RAID adapters available
--- Blind-Carbon-Copy X-Mailer: exmh version 2.1.1 10/15/1999 To: [EMAIL PROTECTED] Subject: Driver for Adaptec/Dell/HP PCI:SCSI RAID adapters available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Jul 2000 15:53:40 -0700 From: Mike Smith [EMAIL PROTECTED] The first BETA version of the 'aac' driver for the Adaptec AAC-364 'Jalapeno' and AAC-3642 'Jalapeno II' RAID adapters is available from http://people.freebsd.org/~msmith/RAID/index.html#adaptec These adapters are OEMed by Dell as the PERC 2/QC and by HP as the HP NetRAID-4m. The driver has been tested on FreeBSD 5.0-CURRENT, but is known to build and should function just fine on 4.0-STABLE as well. Testers are encouraged to contact me for assistance, or to report on progress. Thanks go to BSDi for funding the development of this driver, and Adaptec for supplying me with a profusion of sample adapters and the source for their Linux driver to work from. Particular thanks to Justin Gibbs for finding the right person at Adaptec to make all this happen. - -- ... 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] --- End of Blind-Carbon-Copy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall resetting USA_RESIDENT=NO
On Sun, 23 Jul 2000, John Baldwin wrote:
No, he's right. sysinstall is definitely broken in this respect, and
I'm definitely interested in your patches to fix it. :)
The patches are attached...
In either the case that no make.conf exists, or one exists without a
USA_RESIDENT line in it, the line is added, regardless of if I have
confirmed that the default NO is correct or not.
In the case that make.conf has a USA_RESIDENT line, I only overwrite that
line if the user has answered the question 'are you really a us resident'.
Let me know if you have any questions. Thanks.
- Tim
Index: config.c
===
RCS file: /usr/CVS/src/release/sysinstall/config.c,v
retrieving revision 1.156.2.3
diff -c -r1.156.2.3 config.c
*** config.c2000/07/16 17:29:58 1.156.2.3
--- config.c2000/07/23 22:38:29
***
*** 371,378
char *lines[MAX_LINES];
int i, nlines;
FILE *fp;
! if (!file_readable(config)) {
char *line = malloc(21);
sprintf(line, "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
lines[0] = line;
--- 371,379
char *lines[MAX_LINES];
int i, nlines;
FILE *fp;
+ bool needResLine=TRUE;
! if (!file_readable(config)) { /* create initial file */
char *line = malloc(21);
sprintf(line, "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
lines[0] = line;
***
*** 384,393
return;
for (i = 0; i nlines; i++) {
if (!strncmp(lines[i], "USA_RESIDENT", 12)) {
! free(lines[i]);
! lines[i] = malloc(21); /* big enough */
! sprintf(lines[i], "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
}
}
}
if ((fp = fopen(config, "w")) != NULL) {
--- 385,402
return;
for (i = 0; i nlines; i++) {
if (!strncmp(lines[i], "USA_RESIDENT", 12)) {
! if (USAResValid) { /* we have asked, so lets overwrite */
! free(lines[i]);
! lines[i] = malloc(21); /* big enough */
! sprintf(lines[i], "USA_RESIDENT=%s\n", USAResident ? "YES" :
"NO");
! }
! needResLine=FALSE;
}
+ }
+ if (needResLine) { /* add USA_RESIDENT line to existing file */
+ char *line = malloc(21);
+ sprintf(line, "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
+ lines[nlines++] = line;
}
}
if ((fp = fopen(config, "w")) != NULL) {
Index: dist.c
===
RCS file: /usr/CVS/src/release/sysinstall/dist.c,v
retrieving revision 1.175.2.2
diff -c -r1.175.2.2 dist.c
*** dist.c 2000/07/20 01:53:39 1.175.2.2
--- dist.c 2000/07/23 06:21:01
***
*** 405,410
--- 405,411
dialog_clear_norefresh();
USAResident = !msgYesNo("Are you actually resident in the United States?");
+ USAResValid = TRUE;
distVerifyFlags();
return i | DITEM_REDRAW | DITEM_RESTORE;
Index: globals.c
===
RCS file: /usr/CVS/src/release/sysinstall/globals.c,v
retrieving revision 1.24
diff -c -r1.24 globals.c
*** globals.c 2000/03/12 03:57:25 1.24
--- globals.c 2000/07/23 06:20:24
***
*** 48,53
--- 48,54
Boolean ColorDisplay; /* Are we on a color display? */
Boolean OnVTY; /* Are we on a VTY? */
Boolean USAResident;/* Are we cryptographically challenged? */
+ Boolean USAResValid;/* Have we asked yet? */
Variable *VarHead; /* The head of the variable chain */
Device*mediaDevice; /* Where we're installing from */
int BootMgr;/* Which boot manager we're using */
***
*** 70,73
--- 71,75
mediaDevice = NULL;
RunningAsInit = FALSE;
USAResident = FALSE;
+ USAResValid = FALSE;
}
Index: sysinstall.h
===
RCS file: /usr/CVS/src/release/sysinstall/sysinstall.h,v
retrieving revision 1.186.2.6
diff -c -r1.186.2.6 sysinstall.h
*** sysinstall.h2000/07/21 20:43:48 1.186.2.6
--- sysinstall.h2000/07/23 06:24:46
***
*** 347,352
--- 347,353
extern BooleanColorDisplay; /* Are we on a color display?
*/
extern BooleanOnVTY; /* On a syscons VTY?
*/
Boolean USAResident;/* Are we cryptographically
challenged? */
+ Boolean USAResValid;/* Have we asked yet?
Re: No /boot/loader (dangerously dedicated)
On Sun, 23 Jul 2000, John Baldwin wrote: Patrick M. Hausen wrote: Hello all! Mikhail Teterin wrote: John Baldwin once stated: Folks, gemoetries are for brain damaged PC operating systems. All the box needs to boot is a proper MBR. BIOSes that don't boot from a dedicated disk are _broken_. No, they are actually smart in that they attempt to use a geometry that matches the MBR so that you can move disks around. As a result, when we try to fake it, it confuses them. Hmmm. Perhaps my memory is failing me, but I've been using "dangerously dedicated" disks exclusively for the last few years, because it was supposed to insulate me from the silliness of BIOS geometry translation. By insulate, I mean that a disk formatted on one system was always usable on another even if it decided to have a different geometry translation. I don't shuttle disks around between systems as much as I used to, but I do recall dedicated mode helping. The only systems that had problem booting were old and are long gone. I haven't seen or bought anything in the last three years that won't boot a "dangerously dedicated" disk. Is the requirement of an MBR going to apply to removable media like MO drives? I've only ever gotten these to work in "dangerously dedicated" mode. I'm really puzzled by this thread, because after years of running FreeBSD I've come to the opinion that "dedicated" is how disks should be partitioned under all circumstances ... I mean, where's the partition table on my Sparc systems running Solaris? Who would care installing MS OSs additionally to FreeBSD on a server providing 24x7 service? IA-64 mandates a valid MBR. It boots from a special FAT-32 partition containing the EFI boot loader. Get used to the idea. Ugh. Well, I guess FAT-32 is no-longer a MS-DOS thing now, in the same way that the MBR ins't. So much for the advancement of technology. Adrian -- [ [EMAIL PROTECTED] -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall resetting USA_RESIDENT=NO
Tim Zingelman wrote: On Sun, 23 Jul 2000, John Baldwin wrote: No, he's right. sysinstall is definitely broken in this respect, and I'm definitely interested in your patches to fix it. :) The patches are attached... In either the case that no make.conf exists, or one exists without a USA_RESIDENT line in it, the line is added, regardless of if I have confirmed that the default NO is correct or not. Hmm, we probably shouldn't do this. I think your first patchset is actually the proper one. Ultimately, the user needs to choose whether or not they are in the U.S., we should never choose this for them. Thus, we should only write anything out if we ask them the question. In the case that make.conf has a USA_RESIDENT line, I only overwrite that line if the user has answered the question 'are you really a us resident'. Yes, this is good. :) Let me know if you have any questions. Thanks. - Tim -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Advansys SCSI controllers.
I have found that the Advansys controller which probes as: adw0: AdvanSys 3550 Ultra SCSI Adapter port 0xe800-0xe83f mem 0xe682-0xe68200ff irq 11 at device 9.0 on pci0 adw0: SCSI ID 7, High Low SE Term Enabled, Queue Depth 253 with drives: da0 at adw0 bus 0 target 0 lun 0 da0: SEAGATE ST318416W 0005 Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) da1 at adw0 bus 0 target 1 lun 0 da1: SEAGATE ST318416W 0005 Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) will under heavy usage spit out the message: Jul 22 19:00:27 mortar /kernel: (da0:adw0:0:0:0): Invalidating pack After which, the machine will respond to incoming telnet requests, but never print login. I assume this to be because the drive is no longer available. This is a server hosted at "rackspace.com". They report that this definately does not happen under 3.4 (which they consider a standard FreeBSD install), but I've found that it does happen with 4.0 and it appears to happen more often under 4.1-RC2. The message itself comes from CAM (scsi_da.c) in response to an ENXIO return code from the lower driver. A number of ENXIO returns were recently removed from the advansys driver, but they were all in a section dealing with attaching the device, etc. Anyhow, there appear to be several places were ENXIO can happen, and CAM appears to consider this unrecoverable. The server at rackspace.com will likely get IDE drives or a different scsi controller, so this is unfortunately a report without much ability to try patches. Rackspace.com aparently knows of this ... they've had this problem come up before with 4.0 installed customers. Replicating the problem is simple: make buildworld exercises it quite quickly. I will likely create a PR unless someone knows of a fix for this. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
