spec_getpages error in current kernel from last night
Just got this message while in cvsup: Sep 3 02:01:09 basil /kernel: spec_getpages: I/O read failure: (error code=0) bp 0xc44a3158 vp 0xc9e071c0 Sep 3 02:01:09 basil /kernel: size: 0, resid: 0, a_count: 803, valid: 0x0 Sep 3 02:01:09 basil /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 1 Sep 3 02:01:09 basil /kernel: vm_fault: pager read error, pid 921 (cvsup) Sep 3 02:01:09 basil /kernel: pid 921 (cvsup), uid 0: exited on signal 6 (core dumped) I'm guessing this is _bad_? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: spec_getpages error in current kernel from last night
can we have: uname -a, time of last cvsup/ctm and dmesg output please ? In message [EMAIL PROTECTED], Rob Snow writes: Just got this message while in cvsup: Sep 3 02:01:09 basil /kernel: spec_getpages: I/O read failure: (error code=0) bp 0xc44a3158 vp 0xc9e071c0 Sep 3 02:01:09 basil /kernel: size: 0, resid: 0, a_count: 803, valid: 0x0 Sep 3 02:01:09 basil /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 1 Sep 3 02:01:09 basil /kernel: vm_fault: pager read error, pid 921 (cvsup) Sep 3 02:01:09 basil /kernel: pid 921 (cvsup), uid 0: exited on signal 6 (core dumped) I'm guessing this is _bad_? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB errors (was: Re: Failure of new PCM code to pickup my CS4236.)
uhci0: VIA 83C572 USB controller irq 10 at device 7.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port 1 error, restarting uhub0: port 2 error, restarting Did you ever succeed in connecting and getting to work for example a keyboard or a mouse? Could you tell me the exact manufacturer and type of your motherboard, or if you have the case open, could you tell me the exact part number of the Via chip 83C572, the Super I/O chip that is? I'm looking for some early version of a Via chip that had some brains and therefore does things wrong with respect to EZ-USB chips and reenumeration when the device reconnects with the same VID/PID (/RID). Cheers, Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: spec_getpages error in current kernel from last night
basil# uname -a FreeBSD basil.dympna.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Sep 2 19:58:43 CDT 1999 [EMAIL PROTECTED]:/stripe/current/src/sys/compile/Basil-SMP-Current i386 Last cvsup was 2:03 on Sept 2 dmesg output: (I've snipped out non-existent di's and left the stuff from my mucking with density for my Exabyte 8505, several modes weren't supported) rsnow@basil% dmesg Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Sep 2 19:58:43 CDT 1999 [EMAIL PROTECTED]:/stripe/current/src/sys/compile/Basil-SMP-Current Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x616 Stepping = 6 Features=0xfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV real memory = 134217728 (131072K bytes) SNIPED OUT di's of non-existent devices avail memory = 127070208 (124092K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc02f1000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f109c. Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 ide_pci0: Intel PIIX3 Bus-master IDE controller at device 7.1 on pci0 fxp0: Intel EtherExpress Pro 10/100B Ethernet irq 16 at device 12.0 on pci0 fxp0: Ethernet address 00:a0:c9:93:da:0c ahc0: Adaptec 2940 SCSI adapter irq 17 at device 13.0 on pci0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs vga-pci0: Trident model 9660 VGA-compatible display device irq 18 at device 14.0 on pci0 ahc1: Adaptec 2940 Ultra SCSI adapter irq 19 at device 15.0 on pci0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): Maxtor 7850 AV wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 4 lun 0 sa0: EXABYTE EXB-85058SQANXR1 0781 Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 11) da0 at ahc0 bus 0 target 3 lun 0 da0: MICROP 3243-19 1128RA 28RA Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) da1 at ahc1 bus 0 target 6 lun 0 da1: SEAGATE ST39173W 5764 Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da2 at ahc1 bus 0 target 8 lun 0 da2: SEAGATE ST19171W 0023 Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) changing root device to wd0s2a vinum: loaded vinum: reading configuration from /dev/da2s1e vinum: updating configuration from /dev/da1s1e (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 1c 0 (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:4:0): Invalid field in parameter list (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 1c 0 (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:4:0): Invalid field in parameter list (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 1c 0 (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:4:0): Invalid field in parameter list (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:4:0): Invalid field in parameter list (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 0 0 0 c 0 (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:4:0): Invalid field in parameter list (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 1c 0 (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:4:0):
Re: Support for 3Com 3CCFE574BT 10/100 LAN Card
I notice that -current supports the 3C574, but not the newer 3C574B. Is anyone working on support for this card? Is the 3c574B PCCARD (old-style PCIMCA), or CARDBUS? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the sound card.
On Thu, 2 Sep 1999, Luoqi Chen wrote:
That's exactly what I have. This is just so weird. I am now reading the
debug register chapter of intel's manual, it is virtually impossible to
pinpoint the location by single-stepping through the code...
The debug register trick worked, and the discovery was quite unexpected:
because the isa bus is hanging off the pci bus, bus_release_resource()
call by a isa device, eventually reaches the pci_release_resource(),
where the device is blindly assumed to be a pci device and its isa_device
struct overwritten as if it were a struct pci_devinfo. pci_release_resource()
should check for pass-thru releases.
How about this patch:
Index: pci.c
===
RCS file: /home/ncvs/src/sys/pci/pci.c,v
retrieving revision 1.116
diff -u -r1.116 pci.c
--- pci.c 1999/08/28 00:51:03 1.116
+++ pci.c 1999/09/03 07:59:44
@@ -1375,40 +1375,42 @@
int rv;
struct pci_devinfo *dinfo = device_get_ivars(child);
pcicfgregs *cfg = dinfo-cfg;
+ int passthrough = (device_get_parent(child) != dev);
int map = 0;
- switch (type) {
- case SYS_RES_IRQ:
- if (rid != 0)
- return EINVAL;
- break;
+ if (!passthrough)
+ switch (type) {
+ case SYS_RES_IRQ:
+ if (rid != 0)
+ return EINVAL;
+ break;
- case SYS_RES_DRQ: /* passthru for child isa */
- break;
+ case SYS_RES_DRQ: /* passthru for child isa */
+ break;
#ifdef __alpha__
- case SYS_RES_DENSE:
- case SYS_RES_BWX:
+ case SYS_RES_DENSE:
+ case SYS_RES_BWX:
#endif
- case SYS_RES_MEMORY:
- case SYS_RES_IOPORT:
- /*
+ case SYS_RES_MEMORY:
+ case SYS_RES_IOPORT:
+ /*
* Only check the map registers if this is a direct
* descendant.
*/
- if (device_get_parent(child) == dev)
- map = pci_mapno(cfg, rid);
- else
- map = -1;
- break;
-
- default:
- return (ENOENT);
- }
+ if (device_get_parent(child) == dev)
+ map = pci_mapno(cfg, rid);
+ else
+ map = -1;
+ break;
+
+ default:
+ return (ENOENT);
+ }
rv = BUS_RELEASE_RESOURCE(device_get_parent(dev), child, type, rid, r);
- if (rv == 0) {
+ if (!passthrough rv == 0) {
switch (type) {
case SYS_RES_IRQ:
cfg-irqres = 0;
--
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: Problems with the sound card.
On Thu, 2 Sep 1999, Ollivier Robert wrote: According to Doug Rabson: changing over to the pcm driver. Since your card is a PnP one, you should be able to put just "device pcm0" in your kernel config. Even for ISA ones ? I though only PCI sound cards let you use the shorter form... The new ISA PnP code uses it too. -- 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: Failure of new PCM code to pickup my CS4236.
On Fri, 3 Sep 1999, Stephen Hocking-Senior Programmer PGS Perth wrote: A dmesg from it is as follows - note that the old PCM code used to find it. The voxware stuff needs a couple of delays inserted to find it. ... unknown1: WSS/SB at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 There was a bug where the pci code corrupted the PnP ID of the sound card. This might also fix the hanging problem that others have seen. -- 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: spec_getpages error in current kernel from last night
As Poul says.. first thing.. do a cvsup now and try a very modern kernel. if that fails we'll have some more things to try by then. (my workstation just croaked so I'm busy rerouting around the problem) julian On Fri, 3 Sep 1999, Rob Snow wrote: basil# uname -a FreeBSD basil.dympna.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Sep 2 19:58:43 CDT 1999 [EMAIL PROTECTED]:/stripe/current/src/sys/compile/Basil-SMP-Current i386 Last cvsup was 2:03 on Sept 2 dmesg output: (I've snipped out non-existent di's and left the stuff from my mucking with density for my Exabyte 8505, several modes weren't supported) rsnow@basil% dmesg Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Sep 2 19:58:43 CDT 1999 [EMAIL PROTECTED]:/stripe/current/src/sys/compile/Basil-SMP-Current Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x616 Stepping = 6 Features=0xfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV real memory = 134217728 (131072K bytes) SNIPED OUT di's of non-existent devices avail memory = 127070208 (124092K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc02f1000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f109c. Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 ide_pci0: Intel PIIX3 Bus-master IDE controller at device 7.1 on pci0 fxp0: Intel EtherExpress Pro 10/100B Ethernet irq 16 at device 12.0 on pci0 fxp0: Ethernet address 00:a0:c9:93:da:0c ahc0: Adaptec 2940 SCSI adapter irq 17 at device 13.0 on pci0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs vga-pci0: Trident model 9660 VGA-compatible display device irq 18 at device 14.0 on pci0 ahc1: Adaptec 2940 Ultra SCSI adapter irq 19 at device 15.0 on pci0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): Maxtor 7850 AV wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 4 lun 0 sa0: EXABYTE EXB-85058SQANXR1 0781 Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 11) da0 at ahc0 bus 0 target 3 lun 0 da0: MICROP 3243-19 1128RA 28RA Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) da1 at ahc1 bus 0 target 6 lun 0 da1: SEAGATE ST39173W 5764 Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da2 at ahc1 bus 0 target 8 lun 0 da2: SEAGATE ST19171W 0023 Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) changing root device to wd0s2a vinum: loaded vinum: reading configuration from /dev/da2s1e vinum: updating configuration from /dev/da1s1e (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 1c 0 (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:4:0): Invalid field in parameter list (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 1c 0 (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:4:0): Invalid field in parameter list (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 1c 0 (sa0:ahc0:0:4:0): ILLEGAL REQUEST asc:26,0 (sa0:ahc0:0:4:0): Invalid field in parameter list (sa0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 0 0 0 c 0
Re: Problems with the sound card.
What about documenting what you do here? It's not quite obvious to me why the dev is not the parent of the child in some cases. Cheers, Nick pcicfgregs *cfg = dinfo-cfg; +int passthrough = (device_get_parent(child) != dev); int map = 0; -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the sound card.
On Fri, 3 Sep 1999, Nick Hibma wrote: What about documenting what you do here? It's not quite obvious to me why the dev is not the parent of the child in some cases. It may be a great-grandchild. For instance in this case, the child is isab0, the grandchild is isa0 and the great-grandchild is pcm0. -- 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
make depend if_ed.c pnp.h
error after make depend . there is a #include i386/isa/pnp.h in sys/i386/isa/if_ed.c , but there is not pnp.h in the sys tree. Val __ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Still can't install current via ftp!
I just downloaded the latest floppies from current (19990827) and tried installing current on a different machine that did not have a previous version of FreeBSD on it. As before (search for vty3 and Alt-F3), once I went through the novice installation and got to the part to connect to FreeBSD, I could not get to the vt (ALT-F3) to start ppp. This is for a new installation. Should I present this problem to the hackers maillist? I really think this is a problem that should be fixed by somebody. BTW- I did a new install of 3.2 and it worked great. It appears something happened between 3.2 and 4.0. Perhaps I will have to install 3.2 and then upgrade to 4.0?? Thanks again, You should use vty2 rather than vty3. vty3 is a typo and has been fixed. The ppp startup failure has also been fixed now, so if you try a September snapshot, there should be no problem. Michael A. Endsley [EMAIL PROTECTED] (was [EMAIL PROTECTED]) -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.Awfulhak.org [EMAIL PROTECTED] Don't _EVER_ lose your sense of humour ! [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NAT speed?
Did anyone make any kind of benchmarking on the NAT? I am interested in number of connections per hour / total simultaneous connections and any other perfomance related experience you may have had with it? if you intend to work on this, for measurement criteria, you may want to look at draft-ietf-bmwg-secperf-08.txt. randy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
start xdm on a particular vty
There have been discussions about the xdm entry /etc/ttys does not guarantee the X server being started on the particular vty. So I wrote a shell script to explicitly tell xdm to start X server on a specific vty. It's been working great. I'd like to share it with you, maybe we could include it in the base system. Here's the script (I call it xdmstart), it's very simple, #!/bin/sh case $1 in ttyv*) vt=vt`expr $1 : 'ttyv\(.*\)' + 1`;; *) vt=;; esac exec /usr/X11R6/bin/xdm -nodaemon -server ":0 local /usr/X11R6/bin/X :0 $vt" and in /etc/ttys replace the xdm line with ttyv3 "/usr/local/bin/xdmstart" xterm on secure There's one thing should be noted, the vtxx option isn't a standard X server option, but both XFree86 and Xig support it, so majority of the people should be covered. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvs commit: src/sys/modules/linux Makefile (fwd)
Shouldn't /usr/bin/svr4 and /usr/bin/ibcs2 be moved to /usr/sbin as well? Blaz Zupan, [EMAIL PROTECTED], http://www.herbie.amis.net Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia -- Forwarded message -- Date: Fri, 3 Sep 1999 00:15:39 -0700 (PDT) From: Marcel Moolenaar [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: cvs commit: src/sys/modules/linux Makefile marcel 1999/09/03 00:15:39 PDT Modified files: sys/modules/linuxMakefile Log: Install linux.sh in /usr/sbin and not in /usr/bin. PR: 13545 Submitted by: Jose M. Alcaide [EMAIL PROTECTED] Revision ChangesPath 1.29 +2 -2 src/sys/modules/linux/Makefile To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe cvs-all" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes (FYI)
On Thu, Sep 02, 1999 at 10:21:14PM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] Oscar Bonilla writes: : Sep 2 08:43:28 voyager pccardd[24601]: No free configuration for card 3Com : : Then I kill pccardd and restart it and I get: : : ep0: No connectors or MII. : ep0: [*UTP*] address 00:60:08:b6:36:fb : Sep 2 08:47:51 voyager pccardd[31164]: pccardd started : : and from now on everything works fine. : : I could kill it and restart it from /etc/rc.resume, but I thought that : maybe you'd want me to look into something... How new is your userland? There have been some bugs in that area fixed in pccardd of late. Maybe we missed one? I have a 3C589D that I saw this problem with once or twice, but haven't seen it lately. Aug. 27th. Want me to make world again? I also have a 3C589D and it happens with it too. Regards, -Oscar -- For PGP Public Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
On Fri, 03 Sep 1999 10:41:12 -0400, Luoqi Chen wrote: There have been discussions about the xdm entry /etc/ttys does not guarantee the X server being started on the particular vty. So I wrote a shell script to explicitly tell xdm to start X server on a specific vty. It's been working great. I'd like to share it with you, maybe we could include it in the base system. I think it'd make a lot more sense if it were part of the XFree86 port. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes (FYI)
In message [EMAIL PROTECTED] Oscar Bonilla writes: : Aug. 27th. Want me to make world again? I also have a 3C589D and it happens : with it too. No. Aug 27 is new enough to be good. I'm swamped right now with a dozen other things at the moment, but if you could write me in about a week I'd be able to help you out more. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pnp.h missing
../../i386/isa/if_ed.c:84: i386/isa/pnp.h: No such file or directory cvsupped twice four hours apart. World builds and installs ok. find /sys -name pnp.h returns only the pnp in my build directory. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig PO Box 837 Indooroopilly QLD 4068|[EMAIL PROTECTED]|Specialist To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Fixed sound card problem.
I fixed the sound card problem I was having. I just commented out the pnp driver. I know I will run into problems later if I ever get pnp devices, but its a temporary fix. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H. Johnson II" wrote: Well, I got rid of the old Voxware drivers and went with the pnp drivers and still nothing. Here is the dmesg: What does "still nothing" mean? I can't see anything in your e-mail message which indicates what you're doing to test the sound and what you see in the way of error messages. I do see this: pcm0: SoundBlaster 16 4.13 at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0 That makes it look like your card's available. Are you sure you've created the appropriate devices and symlinks as follows: cd /dev ./MAKEDEV snd0 The pcm(4) manpage says snd1, but if your card's detected as pcm0, then that obviously doesn't apply. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
September snapshots?
I am looking for the latest snapshot, but under ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/i386, the last listed snapshot is for 19990827. Have the snapshots for later dates (Sept) been moved? Thanks again, Michael A. Endsley To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
That didnt work. When I ran mpg123 it said can't access /dev/dsp but the mixer worked. And yes, i did run makedev. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Sheldon Hearn wrote: On Fri, 03 Sep 1999 11:27:55 -0400, "Arthur H. Johnson II" wrote: Well, I got rid of the old Voxware drivers and went with the pnp drivers and still nothing. Here is the dmesg: What does "still nothing" mean? I can't see anything in your e-mail message which indicates what you're doing to test the sound and what you see in the way of error messages. I do see this: pcm0: SoundBlaster 16 4.13 at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0 That makes it look like your card's available. Are you sure you've created the appropriate devices and symlinks as follows: cd /dev ./MAKEDEV snd0 The pcm(4) manpage says snd1, but if your card's detected as pcm0, then that obviously doesn't apply. Ciao, Sheldon. 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 card problems with -current.
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: That didnt work. When I ran mpg123 it said can't access /dev/dsp but the mixer worked. And yes, i did run makedev. What are the permissions on /dev/dsp*? Are other deamons running that are attempting to access /dev/dsp? As an example, I ran E once and enabled 'sounds' from within e-conf only to find that while 'esd' is running, gqmpeg will not run (it reports 'Can't access /dev/dsp'). Good luck, -Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
Well, i recompiled with the Voxware drivers and commented out the pnp0 device, and now it works. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Mike Hoskins wrote: On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: That didnt work. When I ran mpg123 it said can't access /dev/dsp but the mixer worked. And yes, i did run makedev. What are the permissions on /dev/dsp*? Are other deamons running that are attempting to access /dev/dsp? As an example, I ran E once and enabled 'sounds' from within e-conf only to find that while 'esd' is running, gqmpeg will not run (it reports 'Can't access /dev/dsp'). Good luck, -Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl still broken in 4.0-CURRENT
In article [EMAIL PROTECTED], Dmitrij Tejblum [EMAIL PROTECTED] wrote: Pascal Hofstee wrote: Perl seems to be broken for about 3 consecutive days now Anybody have any idea what might be causing this ? I suspect it is the recent changes in rtld. Hmm, could be. Can one of you please give it a try with the older ld-elf.so.1 and see if it works again? I recommend trying the dynamic linker from August 25. If it works with the older dynamic linker, please send me (preferably simple :-) instructions for reproducing the problem. Thanks, John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: recent apm changes (FYI)
On Fri, Sep 03, 1999 at 09:33:29AM -0600, Warner Losh wrote: In message [EMAIL PROTECTED] Oscar Bonilla writes: : Aug. 27th. Want me to make world again? I also have a 3C589D and it happens : with it too. No. Aug 27 is new enough to be good. I'm swamped right now with a dozen other things at the moment, but if you could write me in about a week I'd be able to help you out more. sure, i'll talk back in a week... regards, -Oscar -- For PGP Public Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
i386/isa/pnp.h is absent!
Many drivers tries to include #include i386/isa/pnp.h which is absent now, please fix ASAP, kernel build fails on "make depend" -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC+ D A a++ C G+ QH+(++) 666+++ Y To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl still broken in 4.0-CURRENT
On Fri, 3 Sep 1999, John Polstra wrote: Hmm, could be. Can one of you please give it a try with the older ld-elf.so.1 and see if it works again? I recommend trying the dynamic linker from August 25. If it works with the older dynamic linker, please send me (preferably simple :-) instructions for reproducing the problem. Well ... I personally use CVSup to do my source-tree updating. If you could provide me with instructions on how to revert the current rtld-elf code to an older revision .. i sure would like to try out. As for the easiest way to reproduce just try to run the mirror-script it's bound to just Die with a SIGSEGV in DynaLoader.pm Pascal Hofstee - [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl still broken in 4.0-CURRENT
Pascal Hofstee wrote: On Fri, 3 Sep 1999, John Polstra wrote: Hmm, could be. Can one of you please give it a try with the older ld-elf.so.1 and see if it works again? I recommend trying the dynamic linker from August 25. If it works with the older dynamic linker, please send me (preferably simple :-) instructions for reproducing the problem. Well ... I personally use CVSup to do my source-tree updating. If you could provide me with instructions on how to revert the current rtld-elf code to an older revision .. i sure would like to try out. Thanks! Here are the instructions. Make a copy of your supfile. Let's call it "supfile.rtld". Now edit that file and add this line at the beginning: *default date=99.08.25.00.00.00 Run cvsup as usual, except for two changes: 1. Specify "supfile.rtld" instead of your usual supfile. 2. Add "-i src/libexec/rtld-elf" to the command line. That should back out the recent changes to ld-elf.so.1 quickly, without affecting anything else. Next, build and install the dynamic linker: 1. Make a backup copy of "/usr/libexec/rtld-elf.so.1". 2. Run these commands: cd /usr/src/libexec/rtld-elf make cleandir; make cleandir make obj make depend make all make install And try it out. Your next regular cvsup run will undo the changes. As for the easiest way to reproduce just try to run the mirror-script it's bound to just Die with a SIGSEGV in DynaLoader.pm I was hoping for something simpler that wouldn't require me to figure out how to configure mirror-script. :-( John --- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
There have been discussions about the xdm entry /etc/ttys does not guarantee the X server being started on the particular vty. So I wrote a shell script to explicitly tell xdm to start X server on a specific vty. I *like* it. I think you should share it with the XFree86 folks, and I think this would be great to have in the base installation (after proper testing of course...). Do you know the appropriate channel to contact the XFree86 folks? In the mean while, I can take Sheldon's advice, submit it to our XFree86 port. However, does this work with non-XFree86 X servers? (Or, maybe you can't test that...) I've only tested it with XFree86. Xig's document indicates it also supports the vtxx option (but I am unable to test it). I don't know anything about servers from other vendors. Nate -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
There have been discussions about the xdm entry /etc/ttys does not guarantee the X server being started on the particular vty. So I wrote a shell script to explicitly tell xdm to start X server on a specific vty. I *like* it. I think you should share it with the XFree86 folks, and I think this would be great to have in the base installation (after proper testing of course...). Do you know the appropriate channel to contact the XFree86 folks? Try [EMAIL PROTECTED], who is supposedly the FreeBSD contact for XFree86. However, does this work with non-XFree86 X servers? (Or, maybe you can't test that...) I've only tested it with XFree86. Xig's document indicates it also supports the vtxx option (but I am unable to test it). I don't know anything about servers from other vendors. Great. I'll see if I can try it out at home on my XIG server... Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl still broken in 4.0-CURRENT
Oops, I said: 1. Make a backup copy of "/usr/libexec/rtld-elf.so.1". but I meant "/usr/libexec/ld-elf.so.1". John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl still broken in 4.0-CURRENT
I was hoping for something simpler that wouldn't require me to figure out how to configure mirror-script. :-( I haven't paid much attention, but I'm running a recent version of -current. (Sorry I can't specify the date, everything's out of sync.) However, that aside, mirror-script is easy: Just install 'mirror' from the ports tree and then type 'mirror' at the prompt. I don't need to specify a mirror package to have it fall over with: lambic:~/work/vault mirror DynaLoader:/usr/libdata/perl/5.00503/DynaLoader.pm:188 Caught a SIGSEGV shutting down at /usr/local/bin/mirror line 3873. Happy trails, Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl still broken in 4.0-CURRENT
Brian Handy wrote: I was hoping for something simpler that wouldn't require me to figure out how to configure mirror-script. :-( I haven't paid much attention, but I'm running a recent version of -current. (Sorry I can't specify the date, everything's out of sync.) However, that aside, mirror-script is easy: Just install 'mirror' from the ports tree and then type 'mirror' at the prompt. I don't need to specify a mirror package to have it fall over with: lambic:~/work/vault mirror DynaLoader:/usr/libdata/perl/5.00503/DynaLoader.pm:188 Caught a SIGSEGV shutting down at /usr/local/bin/mirror line 3873. Thanks! I'll give it a try. John --- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make depend if_ed.c pnp.h
On Fri, 3 Sep 1999, Valentin S. Chopov wrote: error after make depend . there is a #include i386/isa/pnp.h in sys/i386/isa/if_ed.c , but there is not pnp.h in the sys tree. This will be fixed very soon when the if_ed driver is updated to use the new PnP code. -- 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: Perl still broken in 4.0-CURRENT
On Fri, Sep 03, 1999 at 01:04:53PM -0600, Brian Handy wrote: I was hoping for something simpler that wouldn't require me to figure out how to configure mirror-script. :-( The simplest thing I've come up with (as I wrote some days before) is $ perl -MIO -e '' I.e. *any* use of IO::File and friends fails miserably during XS bootsrap. If it is necessary, I will reinstallworld tomorrow with Aug-25 loader. Cheers, -- Anton Berezin [EMAIL PROTECTED] The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: Well, I got rid of the old Voxware drivers and went with the pnp drivers and still nothing. Here is the dmesg: -- pcm0: SoundBlaster 16 4.13 at port 0x220-0x22f irq 5 drq 5 flags 0x15 on isa0 unknown0: Game on isa0 unknown1: Audio at port 0x240-0x24f,0x300-0x301,0x388-0x38b irq 9 drq 1,7 on isa0 I'm confused by the unknown1 line. Could you send the output of 'pnpinfo' for this machine. -- 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: Fixed sound card problem.
I tried using snd1. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Ollivier Robert wrote: According to Arthur H. Johnson II: I fixed the sound card problem I was having. I just commented out the pnp driver. I know I will run into problems later if I ever get pnp devices, but its a temporary fix. Something to remember: if you have both pcm0 and pnp, then it will be probed as pcm0 BUT the device you must use is pcm1. That means that you need to do "sh MAKEDEV snd1" and not "sh MAKEDEV snd0". pcm0: MAKEDEV snd0 pcm0 + pnp: MAKEDEV snd1 Luigi gave a good explanation a while when he wrote pcm but I don't remember it now :) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #73: Sat Jul 31 15:36:05 CEST 1999 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
my new motherboard
My new mb(Asus P5A) has lots of new stuff, but one item on my dmesg is puzzling. pci0: unknown card DST5000 (vendor=0x1274, dev=0x5000) at 10.0 irq 5 Anybody know what a DST5000 is or who makes it? Or more importantly why FreeBSD doesn't know. Gene Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl still broken in 4.0-CURRENT
Anton Berezin wrote: On Fri, Sep 03, 1999 at 01:04:53PM -0600, Brian Handy wrote: I was hoping for something simpler that wouldn't require me to figure out how to configure mirror-script. :-( The simplest thing I've come up with (as I wrote some days before) is $ perl -MIO -e '' I.e. *any* use of IO::File and friends fails miserably during XS bootsrap. If it is necessary, I will reinstallworld tomorrow with Aug-25 loader. Thanks, guys. I have confirmed that the problem is connected with my recent dynamic linker changes. Now I just have to figure out why. I'll fix it as soon as I can. John --- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound card problems with -current.
On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: Okay. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] Now I'm really confused. It looks like you have an explicit line for the soundcard in your config (e.g. "device pcm0 at isa? port ? ...") but the config file which you posted only had a "device pcm0" line. With the new driver, if it is a pnp card, you mustn't specify resources. What appears to have happened is that the probe hints (which must have matched the bios settings) allowed pcm0 to probe and attach the card. After that, the pnp code allocated resources for the Audio logical device, avoiding the resources already allocated by pcm0. This moved the card settings away from what the driver was expecting, effectively disabling pcm0. Since the Audio device didn't probe as pcm1, you may also have the buggy version of pci.c which was overwriting some of the pnp information. Make sure that you have at least version 1.117 of pci.c. -- 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: Fixed sound card problem.
On Fri, 3 Sep 1999, Ollivier Robert wrote: According to Arthur H. Johnson II: I fixed the sound card problem I was having. I just commented out the pnp driver. I know I will run into problems later if I ever get pnp devices, but its a temporary fix. Something to remember: if you have both pcm0 and pnp, then it will be probed as pcm0 BUT the device you must use is pcm1. That means that you need to do "sh MAKEDEV snd1" and not "sh MAKEDEV snd0". pcm0: MAKEDEV snd0 pcm0 + pnp: MAKEDEV snd1 Luigi gave a good explanation a while when he wrote pcm but I don't remember it now :) This is no longer necessary (in fact it causes much confusion for the driver). The correct declaration for a pnp soundcard is 'device pcm0'. -- 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: Sound card problems with -current.
Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Fri, 3 Sep 1999, Doug Rabson wrote: On Fri, 3 Sep 1999, Arthur H. Johnson II wrote: Okay. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] Now I'm really confused. It looks like you have an explicit line for the soundcard in your config (e.g. "device pcm0 at isa? port ? ...") but the config file which you posted only had a "device pcm0" line. With the new driver, if it is a pnp card, you mustn't specify resources. Um, I did try that once, but I tried it the correct way and it still didnt work. What appears to have happened is that the probe hints (which must have matched the bios settings) allowed pcm0 to probe and attach the card. After that, the pnp code allocated resources for the Audio logical device, avoiding the resources already allocated by pcm0. This moved the card settings away from what the driver was expecting, effectively disabling pcm0. Since the Audio device didn't probe as pcm1, you may also have the buggy version of pci.c which was overwriting some of the pnp information. Make sure that you have at least version 1.117 of pci.c. BINGO! I had pci.c version 1.116. It is running off pcm0 now thou. -- 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
Need testers for aha driver change
I have just taken a pass through the aha_isa driver to convert it to
newbus and to make it use the new pnp system. Unfortunately I don't own
the hardware so I need testers, preferably both with non-pnp and pnp
cards. The code does compile but I have not tested it at all. Here is the
patch:
Index: aha_isa.c
===
RCS file: /home/ncvs/src/sys/i386/isa/aha_isa.c,v
retrieving revision 1.11
diff -u -r1.11 aha_isa.c
--- aha_isa.c 1999/09/02 04:37:07 1.11
+++ aha_isa.c 1999/09/03 20:47:55
@@ -31,34 +31,28 @@
* $FreeBSD: src/sys/i386/isa/aha_isa.c,v 1.11 1999/09/02 04:37:07 peter Exp $
*/
-/* #include "pnp.h" */
-#define NPNP 0
-
#include sys/param.h
#include sys/systm.h
#include sys/kernel.h
#include machine/bus_pio.h
#include machine/bus.h
+#include machine/resource.h
+#include sys/module.h
+#include sys/bus.h
+#include sys/rman.h
+
+#include isa/isareg.h
+#include isa/isavar.h
-#include i386/isa/isa_device.h
#include dev/aha/ahareg.h
#include cam/scsi/scsi_all.h
-
-#if NPNP 0
-#include i386/isa/pnp.h
-#endif
-
-static int aha_isa_probe(struct isa_device *dev);
-static int aha_isa_attach(struct isa_device *dev);
-static void aha_isa_intr(void *unit);
-struct isa_driver ahadriver =
-{
-aha_isa_probe,
-aha_isa_attach,
-"aha"
+static struct isa_pnp_id aha_ids[] = {
+ {AHA1542_PNP, NULL}, /* ADP1542 */
+ {AHA1542_PNPCOMPAT, NULL}, /* PNP00A0 */
+ {0}
};
/*
@@ -68,26 +62,41 @@
* autoconf.c
*/
static int
-aha_isa_probe(dev)
- struct isa_device *dev;
+aha_isa_probe(device_t dev)
{
/*
* find unit and check we have that many defined
*/
+ struct aha_softc **sc = device_get_softc(dev);
struct aha_softc *aha;
int port_index;
int max_port_index;
+ int error;
+ u_long port_start, port_count;
+ struct resource *port_res;
+ int port_rid;
+ int drq;
aha = NULL;
+ /* Check isapnp ids */
+ if (ISA_PNP_PROBE(device_get_parent(dev), dev, aha_ids) == ENXIO)
+ return (ENXIO);
+
+ error = ISA_GET_RESOURCE(device_get_parent(dev), dev,
+SYS_RES_IOPORT, 0,
+port_start, port_count);
+ if (error != 0)
+ port_start = 0;
+
/*
* Bound our board search if the user has
* specified an exact port.
*/
- aha_find_probe_range(dev-id_iobase, port_index, max_port_index);
+ aha_find_probe_range(port_start, port_index, max_port_index);
if (port_index 0)
- return 0;
+ return ENXIO;
/* Attempt to find an adapter */
for (;port_index = max_port_index; port_index++) {
@@ -103,12 +112,21 @@
*/
if (aha_check_probed_iop(ioport) != 0)
continue;
- dev-id_iobase = ioport;
- if (haveseen_iobase(dev, AHA_NREGS))
+ error = ISA_SET_RESOURCE(device_get_parent(dev), dev,
+SYS_RES_IOPORT, 0,
+ioport, AHA_NREGS);
+ if (error)
+ return error;
+
+ port_rid = 0;
+ port_res = bus_alloc_resource(dev, SYS_RES_IOPORT, port_rid,
+ 0, ~0, AHA_NREGS, RF_ACTIVE);
+ if (!port_res)
continue;
/* Allocate a softc for use during probing */
- aha = aha_alloc(dev-id_unit, I386_BUS_SPACE_IO, ioport);
+ aha = aha_alloc(device_get_unit(dev),
+ I386_BUS_SPACE_IO, ioport);
if (aha == NULL)
break;
@@ -139,44 +157,90 @@
switch (config_data.dma_chan) {
case DMA_CHAN_5:
- dev-id_drq = 5;
+ drq = 5;
break;
case DMA_CHAN_6:
- dev-id_drq = 6;
+ drq = 6;
break;
case DMA_CHAN_7:
- dev-id_drq = 7;
+ drq = 7;
break;
default:
printf("aha_isa_probe: Invalid DMA setting "
"detected for adapter at 0x%x. "
"Failing probe\n", ioport);
- return (0);
+ return (ENXIO);
}
- dev-id_irq = (config_data.irq 9);
- dev-id_intr = aha_isa_intr;
+ error = ISA_SET_RESOURCE(device_get_parent(dev), dev,
+SYS_RES_DRQ, 0, drq, 1);
+ if (error)
+
Re: my new motherboard
On Fri, 3 Sep 1999, gene wrote:
My new mb(Asus P5A) has lots of new stuff, but one item on my dmesg is
puzzling.
pci0: unknown card DST5000 (vendor=0x1274, dev=0x5000) at 10.0 irq 5
Anybody know what a DST5000 is or who makes it? Or more importantly why
FreeBSD doesn't know.
{ 0x1274, "Ensoniq", "Ensoniq" } ,
Looks like a sound card of some sort. Try the new sound drivers.
'DST5000' is just 0x12745000 written in 'EISA' format like PNP and EISA
devices.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever |
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: start xdm on a particular vty
Luoqi Chen scribbled this message on Sep 3:
There have been discussions about the xdm entry /etc/ttys does not guarantee
the X server being started on the particular vty. So I wrote a shell script
to explicitly tell xdm to start X server on a specific vty. It's been working
great. I'd like to share it with you, maybe we could include it in the base
system. Here's the script (I call it xdmstart), it's very simple,
#!/bin/sh
case $1 in
eval i=\$$#
case $i
ttyv*)
vt=vt`expr $1 : 'ttyv\(.*\)' + 1`;;
*)vt=;;
esac
exec /usr/X11R6/bin/xdm -nodaemon -server ":0 local /usr/X11R6/bin/X :0 $vt"
then you have a section like:
i=1
st=""
while [ $i -lt $# ]; do
st="$st"' "$'${i}'"'
i=$(($i + 1))
done
eval exec /usr/X11R6/bin/xdm -nodaemon -server \":0 local /usr/X11R6/bin/X $st :0
\$vt\"
that way you can provide -query hostname or another argument to the
Xserver..
I haven't tested that the eval exec line works properly, but I do know
that the rest of the script works fine though... :)
--
John-Mark Gurney Voice: +1 541 684 8449
Cu Networking P.O. Box 5693, 97405
"The soul contains in itself the event that shall presently befall it.
The event is only the actualizing of its thought." -- Ralph Waldo Emerson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
multipatch #11 available - commit candidate
Another resynchronization now that the issues over the weekend has been mostly resolved. No new features have been added. The patchset is now a commit candidate. http://www.backplane.com/FreeBSD4/ -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fixed sound card problem.
On Fri, Sep 03, 1999 at 09:08:59PM +0100, Doug Rabson wrote: This is no longer necessary (in fact it causes much confusion for the driver). The correct declaration for a pnp soundcard is 'device pcm0'. How do you set flags for particular cards, now? I used to have to use the flags option to tell the pcm driver which second DMA channel to use (5: flags 0x15). I haven't had the opportunity to do any full-duplex stuff since that change, so I don't know whether it has figured it out for itself or not. I assume that it has? The boot message now says: pcm1 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 flags 0x10 on isa So, is 0 a useful 2nd DMA channel, or does the driver make do with one channel now? This is on a -stable system cvsupped on 2nd September. -- Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
the pcm driver and the bktr device
It seems I have the classic IRQ conflict going on here. I have 4 devices that all seem to want the same irq. For some reason the USB port, the pcm driver, the bktr driver, and one other thing (I havn't figured out what) all want IRQ 11. The pcm driver is driving an aureal vortex right now. I have never had this problem before, and even though they are all sharing the same IRQ, they all work at the same time in windows. I would like to know why they won't work in FreeBSD. Here is the output from the dmesg command: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Fri Sep 3 18:57:32 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/MYKERNEL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA T,PSE36,MMX,FXSR real memory = 134152192 (131008K bytes) avail memory = 127393792 (124408K bytes) Preloaded elf kernel "kernel" at 0xc0293000. Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 0.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: VGA-compatible display device at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 ata-pci0: Intel PIIX4 IDE controller at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: UHCI USB controller irq 11 at device 7.2 on pci0 chip2: Intel 82371AB Power management controller at device 7.3 on pci0 pcm0: Aureal Vortex 8820 irq 11 at device 9.0 on pci0 pcm0: irq test failed pcm0: codec timeout reading register 2 (fe7604) pcm0: codec timeout reading register 26 (fe7604) ac97: dac not ready bktr0: BrookTree 878 irq 11 at device 13.0 on pci0 bktr0: could not map interrupt device_probe_and_attach: bktr0 attach returned 6 pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 13.1 irq 11 de0: Digital 21140A Fast Ethernet irq 10 at device 15.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:1f:21:02 pci0: unknown card DPZ0002 (vendor=0x121a, dev=0x0002) at 17.0 pci0: unknown card DPZ0002 (vendor=0x121a, dev=0x0002) at 19.0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 vpo0: Iomega VPI0 Parallel to SCSI interface on ppbus 0 vpo0: EPP 1.9 mode ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: Maxtor 90845D4/GAS54112 ATA-4 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmammode=2, udmamode=2 ad1: 16 secs/int, 0 depth queue, DMA mode Creating DISK ad1 Creating DISK wd1 ata1: master: setting up UDMA2 mode on PIIX4 chip OK ad2: FUJITSU MPC3064AT/6020 ATA-3 disk at ata1 as master ad2: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S ad2: piomode=4, dmamode=2, udmamode=2 ad2: 16 secs/int, 0 depth queue, DMA mode Creating DISK ad2 Creating DISK wd2 atapi: piomode=4, dmamode=2, udmamode=-1 atapi: PIO transfer mode set acd0: CD-ROM 40X/AKU/U30 CDROM drive at ata1 as slave acd0: drive speed 0 - 6875KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked da0 at vpo0 bus 0 target 6 lun 0 da0: IOMEGA ZIP 100 D.09 Removable Direct Access SCSI-2 device da0: Attempt to query device size failed: NOT READY, Medium not present changing root device to wd1s1a de0: enabling 10baseT port If someone can tell me how to make those devices stop sharing the same IRQ I'd appreciate it. Thanks. Kenneth Culver To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: the pcm driver and the bktr device
It seems I have the classic IRQ conflict going on here. I have 4 devices that all seem to want the same irq. For some reason the USB port, the pcm driver, the bktr driver, and one other thing (I havn't figured out what) all want IRQ 11. This is your BIOS' fault. You need to either move the devices around, or fiddle with your BIOS setup until it assigns separate IRQs to each device. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i386/isa/pnp.h is absent!
On Fri, 3 Sep 1999, Andrey A. Chernov wrote: Many drivers tries to include #include i386/isa/pnp.h which is absent now, please fix ASAP, kernel build fails on "make depend" I noticed this with with some NIC code too. /sys/pci/if_xl.c attempts to include "miibus_if.h" which doesn't exist and breaks make depend... a last ditch effort of pointing the include to "/usr/obj/usr/src/sys/modules/xl/miibus_if.h" allows make depend to finish, but make still dies. Later, -Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cds disappeared
i upgraded from mid-april to current and my cdrom drives went away. e.g. xmcd says CD audio: SCSI command fault on /dev/rcd0c: Status=0x16 # ls -lg /dev/cd* /dev/rcd* brw-r- 1 root operator6, 0 Sep 3 16:52 /dev/cd0a brw-r- 1 root operator6, 2 Sep 3 16:52 /dev/cd0c brw-r- 1 root operator6, 8 Sep 3 16:52 /dev/cd1a brw-r- 1 root operator6, 10 Sep 3 16:52 /dev/cd1c crw-r- 1 root operator 15, 0 Sep 3 16:52 /dev/rcd0a crw-r- 1 root operator 15, 2 Sep 3 16:52 /dev/rcd0c crw-r- 1 root operator 15, 8 Sep 3 16:52 /dev/rcd1a crw-r- 1 root operator 15, 10 Sep 3 16:52 /dev/rcd1c dmesg and kernel follow randy Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Sep 3 16:43:14 PDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/RIP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 134205440 (131060K bytes) config pnp 1 0 enable os port0 0x220 port1 0x330 port2 0x388 irq0 5 drq0 1 drq1 5 Invalid command or syntax. Type `?' for help. config pnp 1 1 enable os port0 0x200 Invalid command or syntax. Type `?' for help. config pnp 1 2 enable os port0 0x620 port1 0xa20 port2 0xe20 Invalid command or syntax. Type `?' for help. config quit avail memory = 126930944 (123956K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc02fc000. Preloaded userconfig_script "/kernel.config" at 0xc02fc09c. Pentium Pro MTRR support enabled ccd0-5: Concatenated disk drivers npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard pci0: PCI bus on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 vga-pci0: Matrox model 051f graphics accelerator irq 16 at device 0.0 on pci1 isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 chip1: Intel PIIX4 IDE controller at device 4.1 on pci0 chip2: UHCI USB controller irq 19 at device 4.2 on pci0 intpm0: Intel 82371AB Power management controller at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: System Management Bus on intsmb0 smb0: SMBus general purpose I/O on smbus0 intpm0: PM I/O mapped e400 ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter irq 19 at device 6.0 on pci0 BRDCTL = 0xfa ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: Intel EtherExpress Pro 10/100B Ethernet irq 19 at device 9.0 on pci0 fxp0: Ethernet address 00:a0:c9:df:c8:4e bktr0: BrookTree 878 irq 18 at device 10.0 on pci0 iicbb0: I2C generic bit-banging driver on bti2c0 iicbus0: Philips I2C bus on iicbb0 master-only iicsmb0: I2C to SMB bridge on iicbus0 smbus1: System Management Bus on iicsmb0 smb1: SMBus general purpose I/O on smbus1 WARNING: "iic" is usurping "iic"'s cdevsw[] iic0: I2C general purpose I/O on iicbus0 smbus2: System Management Bus on bti2c0 smb2: SMBus general purpose I/O on smbus2 bktr0: Hauppauge Model 6 A M Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo. bktr0: Detected a MSP3430G-A1 pci0: unknown card DD^0878 (vendor=0x109e, dev=0x0878) at 10.1 irq 18 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 4 virtual consoles, flags=0x200 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A wl0 at port 0x300-0x30f irq 7 on isa0 wl0: address 08:00:6a:2b:dd:a7, NWID 0x pcm0: SoundBlaster 16 4.16 at irq 5 drq 1 on isa0 pcm1: SB16 PnP at port 0x240-0x24f,0x330-0x331,0x388-0x38b irq 10 drq 0,5 on isa0 unknown0: Game at port 0x200-0x207 on isa0 unknown1: WaveTable at port 0x620-0x623 on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 wl0 XXX: driver didn't set ifq_maxlen Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 6 lun 0 sa0: DEC DLT2000 8B37 Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) changing root device to
Re: i386/isa/pnp.h is absent!
On Fri, 3 Sep 1999, FreeBSD mailing list wrote: I found this in the LINT file: Thanks for ending my stupidity. Not sure why I didn't check LINT, since it's always a good thing to do after a cvsup. Problem solved... Later, -Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcm, bktr, etc....
Well, as it turns out, my ethernet, and my bktr device have no problem shareing IRQ's, but my soundcard has plenty of problems, even when it gets it's own irq... it plays sound through the sound-in just fine, but the dsp doesn't work quit right: Applications can play sound (although it plays a little too fast), and when they try to stop playing sound, they just stutter until something else tries to use the dsp device. Also, my bios is really freaky. It refuses to assign any irqs except 10 and 11 to installed PCI devices. I can't figure it out. I've completely rearranged everything and it still refuses to work properly. Here is the pcm part of a dmesg: pcm0: Aureal Vortex 8820 irq 10 at device 19.0 on pci0 pcm0: irq test failed pcm0: codec timeout reading register 2 (fe7604) pcm0: codec timeout reading register 26 (fe7604) ac97: dac not ready Thanks Kenneth Culver To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm, bktr, etc....
On Fri, 3 Sep 1999, Kenneth Culver wrote: Also, my bios is really freaky. It refuses to assign any irqs except 10 and 11 to installed PCI devices. I can't figure it out. I've completely rearranged everything and it still refuses to work properly. The BIOS usually lets you mark IRQs as 'reserved for legacy ISA' or 'auto'. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm, bktr, etc....
On Fri, 3 Sep 1999, Kenneth Culver wrote: Also, my bios is really freaky. It refuses to assign any irqs except 10 and 11 to installed PCI devices. I can't figure it out. I've completely rearranged everything and it still refuses to work properly. The BIOS usually lets you mark IRQs as 'reserved for legacy ISA' or 'auto'. That doesn't help anything. It just picks 2 different IRQs and assigns them to everything. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm, bktr, etc....
On Fri, 3 Sep 1999, Kenneth Culver wrote: What motherboard? What version of BIOS? Is the BIOS version the latest? Well, I figured it out I think. It is Award BIOS, and it's the latest version. I have 2 VooDoo 2's and at the place I had them, they were causing problems, I moved them, and now everything works fine. I still had to remove the Vortex though, it wasn't working right. This is a board with 5 PCI slots right? If so then you are aware that 1 of the slots is a 'clone' of the other and only cards that can cope with sharing PCI INT pins should be used in those 2 slots. Your motherboard manual will have more information. Yeah, it has 5 pci slots and 2 ISA, and one of the PCI is shared. I think I may have had the soundcard, and the bktr card both in the shared slots. Anyway, That problem is fixed, but the aureal driver has some problems. It plays sound (dsp) but in xmms, the slower the kbps, the faster it plays. 56kbps sound sounds like The Chipmunks, and 128 Kbps sound is just a little too fast. Also, when a sound stops, it stutters until another app tries to use the dsp device. Kenneth Culver To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: i386/isa/pnp.h is absent!
On Fri, 3 Sep 1999, Andrey A. Chernov wrote: Many drivers tries to include #include i386/isa/pnp.h which is absent now, please fix ASAP, kernel build fails on "make depend" I noticed this with with some NIC code too. /sys/pci/if_xl.c attempts to include "miibus_if.h" which doesn't exist and breaks make depend... a last ditch effort of pointing the include to "/usr/obj/usr/src/sys/modules/xl/miibus_if.h" allows make depend to finish, but make still dies. I found this in the LINT file: # MII bus support is required for some PCI 10/100 ethernet NICs, # namely those which use MII-compliant transceivers or implement # tranceiver control interfaces that operate like an MII. Adding # "controller miibus0" to the kernel config pulls in support for # the generic miibus API and all of the PHY drivers, including a # generic one for PHYs that aren't specifically handled by an # individual driver. controller miibus0 Including that controller resolved the miibus_if.h issues completely. It seems to me that additional commentary to the effect of: # The xl NIC controller also requires inclusion of the miibus # controller. would clear this issue up for a lotta people. -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
PNP ids missing in sio.c
Can anyone think of a good reason why I can't migrate the
old PNP ids to the new sio.c? I just rebooted my box with
a fresh kernel and much to my shagrin (sp?) my USR PNP
modem didn't work anymore. The following patch got it
working again.
Index: sio.c
===
RCS file: /home/ncvs/src/sys/isa/sio.c,v
retrieving revision 1.260
diff -u -r1.260 sio.c
--- sio.c 1999/09/03 20:01:08 1.260
+++ sio.c 1999/09/04 03:31:10
@@ -573,6 +573,7 @@
{0x0205d041, "Multiport serial device (non-intelligent 16550)"}, /* PNP0502 */
{0x1005d041, "Generic IRDA-compatible device"}, /* PNP0510 */
{0x1105d041, "Generic IRDA-compatible device"}, /* PNP0511 */
+ {0x31307256, "USR3031"},/* USR3031 */
{0}
};
Now that we can't use the pnp command from 'boot -c', what
has (if anything) replaced it? I seem to be remember this
being discussed recently but I'll be darned if I can find
it in the mailing list archives.
Thanks.
-steve
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: cds disappeared
Randy Bush wrote... i upgraded from mid-april to current and my cdrom drives went away. e.g. xmcd says CD audio: SCSI command fault on /dev/rcd0c: Status=0x16 # ls -lg /dev/cd* /dev/rcd* brw-r- 1 root operator6, 0 Sep 3 16:52 /dev/cd0a brw-r- 1 root operator6, 2 Sep 3 16:52 /dev/cd0c brw-r- 1 root operator6, 8 Sep 3 16:52 /dev/cd1a brw-r- 1 root operator6, 10 Sep 3 16:52 /dev/cd1c crw-r- 1 root operator 15, 0 Sep 3 16:52 /dev/rcd0a crw-r- 1 root operator 15, 2 Sep 3 16:52 /dev/rcd0c crw-r- 1 root operator 15, 8 Sep 3 16:52 /dev/rcd1a crw-r- 1 root operator 15, 10 Sep 3 16:52 /dev/rcd1c dmesg and kernel follow [ ... ] cd0 at ahc0 bus 0 target 4 lun 0 cd0: TEAC CD-ROM CD-532S 1.0A Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 5 lun 0 cd1: YAMAHA CRW4416S 1.0f Removable CD-ROM SCSI-2 device cd1: 8.333MB/s transfers (8.333MHz, offset 31) cd1: cd present [270542 x 2048 byte records] Your CDROM drives look just fine to me. A lot has changed since mid-April. You need to recompile xmcd. If you're running -current, that's the first thing you should try when a port doesn't work. Interfaces in -current change much more often than in -stable. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cds disappeared
i upgraded from mid-april to current and my cdrom drives went away. e.g. xmcd says CD audio: SCSI command fault on /dev/rcd0c: Status=0x16 # ls -lg /dev/cd* /dev/rcd* brw-r- 1 root operator6, 0 Sep 3 16:52 /dev/cd0a brw-r- 1 root operator6, 2 Sep 3 16:52 /dev/cd0c brw-r- 1 root operator6, 8 Sep 3 16:52 /dev/cd1a brw-r- 1 root operator6, 10 Sep 3 16:52 /dev/cd1c crw-r- 1 root operator 15, 0 Sep 3 16:52 /dev/rcd0a crw-r- 1 root operator 15, 2 Sep 3 16:52 /dev/rcd0c crw-r- 1 root operator 15, 8 Sep 3 16:52 /dev/rcd1a crw-r- 1 root operator 15, 10 Sep 3 16:52 /dev/rcd1c [ ... ] cd0 at ahc0 bus 0 target 4 lun 0 cd0: TEAC CD-ROM CD-532S 1.0A Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 5 lun 0 cd1: YAMAHA CRW4416S 1.0f Removable CD-ROM SCSI-2 device cd1: 8.333MB/s transfers (8.333MHz, offset 31) cd1: cd present [270542 x 2048 byte records] Your CDROM drives look just fine to me. yup. that's what really confuses me. A lot has changed since mid-April. You need to recompile xmcd. had done so. and reconfigured it too. 'nother clue # mount /cdrom cd9660: Device not configured with /etc/fstab having /dev/cd0c /cdrom cd9660 ro,noauto 0 0 randy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PNP ids missing in sio.c
Steve Price wrote: Now that we can't use the pnp command from 'boot -c', what has (if anything) replaced it? I seem to be remember this being discussed recently but I'll be darned if I can find it in the mailing list archives. The old pnp code is fundamentally incompatable with the new pnp code and has gone. Doug's new pnp code is tightly integrated within the isa bus and is rather smart. It will choose it's own non-conflicting addresses for the devices. There isn't much use for the userconfig pnp command as the pnp devices are deactivated during the ISA probes and only switched on when a device claims them, based on their PNP id. Basically this means we've got to pay a lot more attention to the PNP id and compat id's now. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fixed sound card problem.
"Andrew Reilly" wrote: On Fri, Sep 03, 1999 at 09:08:59PM +0100, Doug Rabson wrote: This is no longer necessary (in fact it causes much confusion for the driver). The correct declaration for a pnp soundcard is 'device pcm0'. How do you set flags for particular cards, now? I used to have to use the flags option to tell the pcm driver which second DMA channel to use (5: flags 0x15). I haven't had the opportunity to do any full-duplex stuff since that change, so I don't know whether it has figured it out for itself or not. I assume that it has? The boot message now says: pcm1 (CS423x/Yamaha/AD1816 CS4236 sn 0x) at 0x530-0x537 irq 5 drq 1 flags 0x10 on isa So, is 0 a useful 2nd DMA channel, or does the driver make do with one channel now? I'm not sure, dma 0 works here, but it's specifically detected automatically (without flags) and is reported as such. # dmesg | grep pcm pcm0: AudioPCI ES1370 irq 11 at device 10.0 on pci0 pcm1: ESS1868 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 \ on isa0 On another box, I see: # dmesg | grep pcm pcm0: CS4236 at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 \ on isa0 I suspect this is the same device you have. Are you sure you are up to date with your source? The probe message looks a bit odd and looks more like the old pnp messages. Did you rerun config and do a 'make depend'? Also, the new pnp/pcm code will start at pcm0, rather than pcm1 unless there is a pcm0 already in use. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Need Installation Help...
installation process. I am trying to install FreeBSD on a IBM PC Server 325. However, as near as I can determine the Adaptec AIC 7880 SCCI card and the AMD/PCI network interface is giving me fits. After looking at the FAQ, and other documentation, it appears that the source of my problems are being caused by lack of support fo these devices in the generic install kernel. No; both of these devices are supported in any recent version of FreeBSD. The AMD network adapter is known to be troublesome, but there are many people running FreeBSD just fine on the 325. Which version of FreeBSD are you trying to install? What problems are you experiencing? -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Need Installation Help...
Hi All -- I am trying to become part of the FreeBSD world but am having problems with the installation process. I am trying to install FreeBSD on a IBM PC Server 325. However, as near as I can determine the Adaptec AIC 7880 SCCI card and the AMD/PCI network interface is giving me fits. After looking at the FAQ, and other documentation, it appears that the source of my problems are being caused by lack of support fo these devices in the generic install kernel. This is further complicated by the fact that I do not have a machine which is currently running FreeBSD, so I cannot build a custom installation disk. I really want to install FreeBSD on this box, but these issues are preventing me from doing so. Does anybody have any comments/thoughts which might help me get out of this corner I have painted myself into? Thanks in Advance, Andy. -- -- Andrew Whitcroft n9kws at execpc.com -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
