Re: $FreeBSD tag confusion
On Wed 1999-09-01 (21:03), Kevin Street wrote: > I think I should set up a separate cvs repository for the FreeBSD src > since I may not want the same options for my own cvs repository. In > particular that tagexpand line turns off all tag expansions except for > $FreeBSD and $Id. Does this include $Date? I think the www tree expects them to be expanded. (I can't check at the moment, though) Neil -- Neil Blakey-Milner [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
LINT warnings
What about these? Looks like trivial for someone who knows what he is doing :-) In file included from ../../kern/subr_diskslice.c:58: ../../sys/devfsext.h:32: warning: #warning "Using obsolete " In file included from ../../miscfs/devfs/devfs_tree.c:48: ../../sys/devfsext.h:32: warning: #warning "Using obsolete " In file included from ../../netinet/mlf_ipl.c:34: ../../sys/devfsext.h:32: warning: #warning "Using obsolete " 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
LINT warnings sysent
In file included from ../../kern/init_sysent.c:11: ../../sys/sysent.h:72: warning: `struct vnode' declared inside parameter list ../../sys/sysent.h:72: warning: its scope is only this definition or declaration, ../../sys/sysent.h:72: warning: which is probably not what you want. ../../kern/init_sysent.c:23: warning: cast discards `volatile' from pointer target type What's this? Sounds strange. 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
yes! or should I say Oh no! (CD ROM problems)
Jordan, You were referring to these messages? #cd/2: invalid sector size 2352 Symptoms: Once in a while ripenc doesn't work. Most of the times it does. The problem can be reproduced here, by inserting a CD into the player and then running the following commands: [Blast! Now it does work?! after opening and closing the drawer] In any case, the commands I used were: cda -dev /dev/rcd0c on cda -dev /dev/rcd0c toc This makes sense because ripenc failed once in a while before without a proper explanation. So it looks like something is not initialised sometimes, or there is a stack variable that is not initialised. Kernel: FreeBSD elpc36.jrc.it 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Aug 30 08:37:12 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ELPC i386 Device: Device: /dev/cd0c -- "TEAC" "CD-R55S" "1.0L" Hope this helps. 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
LINT warnings fdesc_vnops
../../miscfs/fdesc/fdesc_vnops.c: In function `fdesc_open': ../../miscfs/fdesc/fdesc_vnops.c:352: warning: enumeration value `Froot' not handled in switch ../../miscfs/fdesc/fdesc_vnops.c:352: warning: enumeration value `Fdevfd' not handled in switch ../../miscfs/fdesc/fdesc_vnops.c:352: warning: enumeration value `Flink' not handled in switch Shouldn't there be a default at the end of that switch and why not? Otherwise a comment about this? 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
Problems with the sound card.
My sound card used to work, and with a backup kernel it still did ( I lost it ) but after doing a make update world yesturday I came to the realization that it no longer works. Did someone break the sb drivers? I get a drq / irq conflict error, but they are set to the sound card's settings. 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
make release is broken in STABLE?
Hello! All my attempts to make release (with time-proven script) fails with ===> en_US.ISO_8859-1/articles cd /usr/doc/en_US.ISO_8859-1/articles ; make afterdistribute DESTDIR=/R/stage/tr ees/bin ===> en_US.ISO_8859-1/articles/diskless-x make: don't know how to make distribute. Stop *** Error code 2 What should I investigate? -- Alexander B. Povolotsky[ICQ 18277558] [2:5020/145] [http://freebsd.svib.ru] [[EMAIL PROTECTED]] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the sound card.
Could you send the output of dmesg. It could be that your BIOS has rearranged the irq settings and has put another card on that IRQ. Is the sound card PNP? If not, could you check that the card's IRQ is marked as legacy in the BIOS? Nick > My sound card used to work, and with a backup kernel it still did ( I lost > it ) but after doing a make update world yesturday I came to the > realization that it no longer works. Did someone break the sb drivers? I > get a drq / irq conflict error, but they are set to the sound card's > settings. > > 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 > > -- 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: $FreeBSD tag confusion
Neil Blakey-Milner writes: >On Wed 1999-09-01 (21:03), Kevin Street wrote: >> I think I should set up a separate cvs repository for the FreeBSD src >> since I may not want the same options for my own cvs repository. In >> particular that tagexpand line turns off all tag expansions except for >> $FreeBSD and $Id. > >Does this include $Date? I think the www tree expects them to be >expanded. (I can't check at the moment, though) $Date is off. -- Kevin Street [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
recent apm changes (FYI)
I have a Vaio PCG-505FX, and first of all let me tell you guys that the recent apm changes are working great. I can use both the suspend and hibernate functions without a problem. There's just one weird thing going on that I'd like you to know about, if someone gives me instructions on how to debug it I can help find the problem. If I hibernate the laptop, at resume time i need to kill the pccardd daemon and restart it in order to be able to use my 3Com Fast Etherlink XL PCMCIA card. Here's the log from the console... Called APM sound suspend hook for unit 0 ep0: unload Return IRQ=10 Card disabled, slot 0 Called APM sound resume hook for unit 0 Card inserted, slot 0 Sep 2 08:43:23 voyager /kernel: resumed from suspended mode (slept 13:11:45) 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... thanks and 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
$B%F%l%SEEOC$N$*CN$i$;!!(BInfo on Videophone
$B$3$s$K$A$o!"(B $B$3$l$OJXMx!*(B Here's a good news for you, $B%[%F%k!"N94[!"C1?HIkG$!"N13X$K$b(B a news of the Videophone $B:GE,$J%K%e!<%9(B! over the normal coloer telephone line. $B:#!"@$3&$GOCBj$N4JC1%F%l%SEEOC(B All you have to do is just $B$N>R2p$G$9!#(B connect this videophone with $B<+Bp$N%F%l%S$HEEOC$K$D$J$0$@$1$G(B the telephone and television. $B#T#VEEOC$KAaJQ$o$j!*!J9);vITMW!K(B which you have in your home. $BEEOCBe$O!":#$^$G$HF1$8$G$9!#(B Telephone charge is the same as ever. $B1s$/$NM'?M$d2HB2$H!"4i$r8+$J$,$i(B Face to face communication with distant $BOC$;$k$N$G0l0B?4!*!*(B your distant family $BCMCJ$O0lBf$G(B69,000$B1_$G$9!#(B Price per unit: 6,9000 yen $B2<$r%/%j%C%/$7$F$_$F2<$5$$!#(B Please click left below. http://www.academyjapan.co.jp [EMAIL PROTECTED] $B%"%+%G%_!
Re: Problems with the sound card.
here it is: 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 #4: Thu Sep 2 10:45:54 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ARTHUR Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 62173184 (60716K bytes) Preloaded elf kernel "kernel" at 0xc02d1000. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 ide_pci0: at device 7.1 on pci0 vga-pci0: irq 10 at device 10.0 on pci0 xl0: <3Com 3c905B-TX Fast Etherlink XL> irq 11 at device 11.0 on pci0 xl0: Ethernet address: 00:10:4b:c5:24:df miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: 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 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (atapi): , removable, dma, iordis wcd0: drive speed 1377KB/sec, 240KB cache wcd0: supported read types: CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: 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: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppi0: on ppbus 0 sb0 at port 0x220 irq 5 drq 1 on isa0 snd0: sbxvi0 at port 0x drq 5 on isa0 isa_compat: didn't get ports for sbxvi snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] unknown0: on isa0 unknown1: at port 0x221-0x230,0x300-0x301,0x388-0x38b irq 9 drq 3,7 on isa0 changing root device to wd0s1a Sound: DMA (output) timed out - IRQ/DRQ config error? Sound: DMA (output) timed out - IRQ/DRQ config error? Sound: DMA (output) timed out - IRQ/DRQ config error? thanks. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Thu, 2 Sep 1999, Nick Hibma wrote: > > Could you send the output of dmesg. It could be that your BIOS has > rearranged the irq settings and has put another card on that IRQ. Is the > sound card PNP? If not, could you check that the card's IRQ is marked as > legacy in the BIOS? > > Nick > > > My sound card used to work, and with a backup kernel it still did ( I lost > > it ) but after doing a make update world yesturday I came to the > > realization that it no longer works. Did someone break the sb drivers? I > > get a drq / irq conflict error, but they are set to the sound card's > > settings. > > > > 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 > > > > > > -- > 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 > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: yes! or should I say Oh no! (CD ROM problems)
What you're saying is that it fails on the second open but resets if you eject/reload the CD ? Could you do me the favour and update to the latest current and try again. If that message comes from where I think, something is trying to do non BDEV_SIZE multiple requests on a char device, a clear no-no. I know that Søren have had similar trouble reading audio tracks (which have 2352 bytes/"sector") from ATAPI CD drives. Poul-Henning In message, Nick Hibma writes: > >Jordan, > >You were referring to these messages? > > #cd/2: invalid sector size 2352 > >Symptoms: Once in a while ripenc doesn't work. Most of the times it >does. The problem can be reproduced here, by inserting a CD into the >player and then running the following commands: > >[Blast! Now it does work?! after opening and closing the drawer] > >In any case, the commands I used were: > > cda -dev /dev/rcd0c on > cda -dev /dev/rcd0c toc > > >This makes sense because ripenc failed once in a while before without a >proper explanation. So it looks like something is not initialised >sometimes, or there is a stack variable that is not initialised. > >Kernel: >FreeBSD elpc36.jrc.it 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Aug 30 >08:37:12 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/ELPC >i386 > >Device: >Device: /dev/cd0c -- "TEAC" "CD-R55S" "1.0L" > > > >Hope this helps. > >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 > -- 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
Re: yes! or should I say Oh no! (CD ROM problems)
> What you're saying is that it fails on the second open but > resets if you eject/reload the CD ? No. Insert CD, run cda /dev/rcd0c toc, error message in /var/log/messages. Eject CD reinsert it, same command, it works. > Could you do me the favour and update to the latest current > and try again. I'll do that. There is no way to definitely trigger the problem, so it's going to be difficult to asses the state we are in. > If that message comes from where I think, something is trying > to do non BDEV_SIZE multiple requests on a char device, a clear > no-no. And where do you think the message comes from? Especially because the error does not occur always on the same CD. FYI, the drive is SCSI: ahc0: irq 11 at device 20.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ... cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: cd present [332707 x 2048 byte records] 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: yes! or should I say Oh no! (CD ROM problems)
In message, Nick Hibma writes: > > What you're saying is that it fails on the second open but > > resets if you eject/reload the CD ? > >No. Insert CD, run cda /dev/rcd0c toc, error message in >/var/log/messages. Eject CD reinsert it, same command, it works. So it fails the first time after a reboot and never again until reboot ? Or is it just heads-or-tails everytime ? > > If that message comes from where I think, something is trying > > to do non BDEV_SIZE multiple requests on a char device, a clear > > no-no. > >And where do you think the message comes from? Especially because the >error does not occur always on the same CD. I suspect that it is from this code in kern/subr_diskslice.c:dscheck() if (ssp->dss_secmult == 1) { if (bp->b_bcount % (u_long)DEV_BSIZE) goto bad_bcount; secno = blkno; nsec = bp->b_bcount >> DEV_BSHIFT; } else if (ssp->dss_secshift != -1) { if (bp->b_bcount & (ssp->dss_secsize - 1)) goto bad_bcount; if (blkno & (ssp->dss_secmult - 1)) goto bad_blkno; secno = blkno >> ssp->dss_secshift; nsec = bp->b_bcount >> (DEV_BSHIFT + ssp->dss_secshift); } else { if (bp->b_bcount % ssp->dss_secsize) goto bad_bcount; if (blkno % ssp->dss_secmult) goto bad_blkno; secno = blkno / ssp->dss_secmult; nsec = bp->b_bcount / ssp->dss_secsize; } As you can see it would pass through the third block, but not the two first, so if you could place a couple of strategic printfs and see which one of these it fails on (only print on the error, otherwise your printout will come en each and every transfer.) Is this by any chance a mixed-cd, ie both sound&data tracks ? -- 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
Re: yes! or should I say Oh no! (CD ROM problems)
> >No. Insert CD, run cda /dev/rcd0c toc, error message in > >/var/log/messages. Eject CD reinsert it, same command, it works. > > So it fails the first time after a reboot and never again > until reboot ? > > Or is it just heads-or-tails everytime ? The machine is normally up for several weeks at a time, so it's head-or-tails, with it being ok most of the time. When it goes wrong it goes wrong for several changes of CD"s, but all of a sudden it starts to work again. I'm sorry I can't be more precise, but the error occurs at random places. > As you can see it would pass through the third block, but not > the two first, so if you could place a couple of strategic > printfs and see which one of these it fails on (only print on > the error, otherwise your printout will come en each and every > transfer.) See attached diff against CURRENT in case any one else wants to have a go at it. > Is this by any chance a mixed-cd, ie both sound&data tracks ? Nope, off the shelf sound CD. Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy --- subr_diskslice.c.orig Thu Sep 2 18:21:33 1999 +++ subr_diskslice.cThu Sep 2 18:37:48 1999 @@ -173,22 +173,38 @@ sp = &ssp->dss_slices[dkslice(bp->b_dev)]; lp = sp->ds_label; if (ssp->dss_secmult == 1) { - if (bp->b_bcount % (u_long)DEV_BSIZE) + if (bp->b_bcount % (u_long)DEV_BSIZE) { + printf("PHK1 bp->b_bcount(=%ld) %% %d != 0\n", + bp->b_bcount, DEV_BSIZE); goto bad_bcount; + } secno = blkno; nsec = bp->b_bcount >> DEV_BSHIFT; } else if (ssp->dss_secshift != -1) { - if (bp->b_bcount & (ssp->dss_secsize - 1)) + if (bp->b_bcount & (ssp->dss_secsize - 1)) { + printf("PHK2 bp->b_bcount(=%ld) & (ssp->dss_secsize - 1)(=%d) +!= 0\n", +bp->b_bcount, ssp->dss_secsize - 1); goto bad_bcount; - if (blkno & (ssp->dss_secmult - 1)) + } + if (blkno & (ssp->dss_secmult - 1)) { + printf("PHK3 blkno(=%d) & (ssp->dss_secmult - 1)(= +%d) != 0\n", + blkno, ssp->dss_secmult - 1); goto bad_blkno; + } secno = blkno >> ssp->dss_secshift; nsec = bp->b_bcount >> (DEV_BSHIFT + ssp->dss_secshift); } else { - if (bp->b_bcount % ssp->dss_secsize) + if (bp->b_bcount % ssp->dss_secsize) { + printf("PHK4 bp->b_bcount(=%ld) %% ssp->dss_secsize(=%d) != +0\n", +bp->b_bcount, ssp->dss_secsize - 1); goto bad_bcount; - if (blkno % ssp->dss_secmult) + } + if (blkno % ssp->dss_secmult) { + printf("PHK5 blkno(=%d) %% ssp->dss_secmult(=%d) != 0\n", + blkno, ssp->dss_secmult); goto bad_blkno; + } secno = blkno / ssp->dss_secmult; nsec = bp->b_bcount / ssp->dss_secsize; }
Re: Problems with the sound card.
> Could you send the output of dmesg. It could be that your BIOS has > rearranged the irq settings and has put another card on that IRQ. Is the > sound card PNP? If not, could you check that the card's IRQ is marked as > legacy in the BIOS? > > Nick > > > My sound card used to work, and with a backup kernel it still did ( I lost > > it ) but after doing a make update world yesturday I came to the > > realization that it no longer works. Did someone break the sb drivers? I > > get a drq / irq conflict error, but they are set to the sound card's > > settings. > > > > Arthur H. Johnson II > > http://www.linuxberg.com > > Linuxberg Manager > > [EMAIL PROTECTED] > > I too have problems with my on board CS4236 sound chip and it is of a very strange nature: in the new isa pnp code, function isa_assign_resources() mysteriously overwrites the isa_device structure and sets logical_id to 0, and as a result subsequent probe would not recognize it any more. I have narrowed it down to the bus_release_resource() call at the end of isa_find_irq(). It was so convoluted beyond that point and I gave up. I'd like to see someone more familiar with the code to continue. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current kernel breakage
I recently recompiled my kernel with the following kernel config file, and now when I boot up, I get about halfway through probing, and the computer freezes, accepting no keyboard input or anything else but a hard reset (reset button) here is my kernel Config file.. # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.freebsd.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.178 1999/07/25 04:32:43 wpaul Exp $ machine i386 cpu I686_CPU ident "MYKERNEL" maxusers64 #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INET#InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE#Allow users to grab the console options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options SC_DISABLE_REBOOT options SOFTUPDATES # To make an SMP kernel, the next two are needed #optionsSMP # Symmetric MultiProcessor Kernel #optionsAPIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #optionsNCPU=2 # number of CPUs #optionsNBUS=4 # number of busses #optionsNAPIC=1 # number of IO APICs #optionsNINTR=24# number of INTs controller isa0 controller pnp0# PnP support for ISA controller pci0 # Floppy drives controller fdc0at isa? port IO_FD1 irq 6 drq 2 diskfd0 at fdc0 drive 0 controller ata0 device atadisk0 device atapicd0 # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #optionsXSERVER # support for X server #optionsFAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #optionsPCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0at nexus? flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? # Serial (COM) ports device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 # Parallel port device ppc0at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0# Printer device plip0 # TCP/IP over parallel device ppi0# Parallel port interface device controller vpo0# Requires scbus and da0 # PCI Ethernet NICs. device de0 # DEC/Intel DC21x4x (``Tulip'') # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop# Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun 1 # Packet tunnel, for ppp(1) pseudo-device pty 16 # Pseudo-ttys (telnet etc) pseudo-device gzip# Exec gzipped a.out's # The `bpf' pseudo-device e
Make world broken
Make world is broken, these are the errors I get: cc -nostdinc -O -pipe -I/usr/src/sbin/kget/../../sys/i386 -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/kget/kget.c /usr/src/sbin/kget/kget.c:34: isa/pnp.h: No such file or directory /usr/src/sbin/kget/kget.c: In function `main': /usr/src/sbin/kget/kget.c:131: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:131: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:135: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:137: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:137: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:141: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:141: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:142: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:143: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:143: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:143: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:143: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:144: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:145: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:147: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:148: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:152: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:153: dereferencing pointer to incomplete type /usr/src/sbin/kget/kget.c:159: sizeof applied to an incomplete type *** Error code 1 Stop in /usr/src/sbin/kget. *** Error code 1 Stop in /usr/src/sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Thanks Kenneth Culver To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-CURRENT SMP crash with vinum raid-5 and softupdates
Just to let everyone know, Greg's going to be out-of-town for a little while and won't be able to continue debugging. I'm taking a crack at it again. So far, it seems to be a combination of softupdates+vinum+raid5 that triggers the bug, whatever it is. If I turn off softupdates the raid5 volume seems happy, with and without async. It seems likely to be some odd interaction between the raid5 code and softupdates, since the simpler mirror/striping seems to work fine with it. Ring any bells for anyone? -- Parag Patel 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, Arthur H. Johnson II wrote: > here it is: > sb0 at port 0x220 irq 5 drq 1 on isa0 > snd0: > sbxvi0 at port 0x drq 5 on isa0 > isa_compat: didn't get ports for sbxvi > snd0: > WARNING: "snd" is usurping "snd"'s cdevsw[] > unknown0: on isa0 > unknown1: at port 0x221-0x230,0x300-0x301,0x388-0x38b irq 9 drq 3,7 on isa0 > changing root device to wd0s1a > Sound: DMA (output) timed out - IRQ/DRQ config error? > Sound: DMA (output) timed out - IRQ/DRQ config error? > Sound: DMA (output) timed out - IRQ/DRQ config error? Could you try removing the old voxware drivers from your config and 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. -- 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: current kernel breakage
On Thu, 2 Sep 1999, Kenneth Wayne Culver wrote: > I recently recompiled my kernel with the following kernel config file, and > now when I boot up, I get about halfway through probing, and the computer > freezes, accepting no keyboard input or anything else but a hard reset > (reset button) here is my kernel Config file.. What is printed just before it freezes? -- 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: 4.0-CURRENT SMP crash with vinum raid-5 and softupdates
Forgot to mention - SMP makes no difference to the crash. I've turned it off for now to simplify debugging. Just vinum+raid5+softupdates seems to be enough. -- Parag To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
newpcm
apologies for this message being late. newpcm has now been committed in -current, with functional trident 4dwave, es1370, sb and mss support. minimal changes to kernel config should be required: pci devices: device pcm0 isa pnp devices: controller pnp0 device pcm0 non-pnp isa devices: device pcm0 at ..., as before newpcm should work on any freebsd-supported platform as it uses newbus. it has been tested on i386 and alpha. there should be no change to the userland interface other than addition of mmap()/trigger support, which has been tested with an oss sample program, but no real applications. a design overview of newpcm is available at http://www.vilnya.demon.co.uk/design.txt i intend to put a hardware driver skeleton up on the same site in the next few days. - cameron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
Cameron Grant wrote: >a design overview of newpcm is available at >http://www.vilnya.demon.co.uk/design.txt > >i intend to put a hardware driver skeleton up on the same site in the next >few days. What about a man page? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
Cameron Grant wrote: > newpcm has now been committed in -current, with functional trident 4dwave, > es1370, sb and mss support. minimal changes to kernel config should be > required: > > pci devices: > device pcm0 > > isa pnp devices: > controller pnp0 > device pcm0 Unfortunately I can't get it working on my SB16PNP with previously worked flamessly with "oldpcm". I've did as you suggested - as it seems to be pnp card I've removed all "at isa0 ", rebuilded and rebooted. But with the new kernel I've observed 2 things: (1) my "pnp 1 0 os enable ..." string is no longer recognised; (2) SB is no longer works :-(. Following is relevant pieces of my dmesg output for both cases: "newpcm:" config> pnp 1 0 os enable port0 0x220 irq0 5 drq0 1 drq1 3 Invalid command or syntax. Type `?' for help. avail memory = 62058496 (60604K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fb020 bios32: Entry = 0xfb4a0 (c00fb4a0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb4d0 pnpbios: Found PnP BIOS data at 0xc00fc0e0 pnpbios: Entry = f:c108 Rev = 1.0 pnpbios: 15 devices, largest 98 bytes pnpbios: handle 0 device ID PNP (d041) pnpbios: handle 1 device ID PNP0200 (0002d041) pnpbios: handle 2 device ID PNP0100 (0001d041) pnpbios: handle 3 device ID PNP0b00 (000bd041) pnpbios: handle 4 device ID PNP0303 (0303d041) pnpbios: handle 5 device ID PNP0800 (0008d041) pnpbios: handle 6 device ID PNP0c04 (040cd041) pnpbios: handle 7 device ID PNP0c01 (010cd041) pnpbios: handle 8 device ID PNP0c02 (020cd041) pnpbios: handle 9 device ID PNP0a03 (030ad041) pnpbios: handle 11 device ID PNP0c02 (020cd041) pnpbios: handle 12 device ID PNP0501 (0105d041) pnpbios: handle 13 device ID PNP0700 (0007d041) pnpbios: handle 15 device ID PNP0401 (0104d041) pnpbios: handle 16 device ID PNP0501 (0105d041) Other BIOS signatures found: ACPI: Preloaded elf kernel "kernel" at 0xc02f7000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f70a8. isab0: at device 7.0 on pci0 Trying Read_Port at 203 isa0: on isab0 unknown0: on isa0 unknown1: on isa0 unknown2: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 unknown3: at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 And following was with "oldpcm": config> pnp 1 0 os enable port0 0x220 irq0 5 drq0 1 drq1 3 Probing for PnP devices: Trying Read_Port at 203 PnP: CSN 1 COMP_DEVICE_ID = 0x0006d041 CSN 1 Vendor ID: CTL0028 [0x28008c0e] Serial 0x1013c276 Comp ID: PNP0600 [0x0006d041] PnP: override config for CSN 1 LDN 0 vend_id 0x28008c0e port 0x 0x 0x 0x irq 0:0 drq 4:4 en 0 Called nullpnp_probe with tag 0x0001, type 0x28008c0e Called nullpnp_probe with tag 0x0001, type 0x0006d041 port 0x0220 0x 0x 0x irq 5:0 drq 1:3 en 1 port 0x0220 0x 0x 0x irq 5:0 drq 1:3 en 1 pcm1 (SB16pnp sn 0x1013c276) at 0x220-0x22f irq 5 drq 1 flags 0x13 on isa Sincerely, Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
On Fri, 3 Sep 1999, Maxim Sobolev wrote: > Cameron Grant wrote: > > > newpcm has now been committed in -current, with functional trident 4dwave, > > es1370, sb and mss support. minimal changes to kernel config should be > > required: > > > > pci devices: > > device pcm0 > > > > isa pnp devices: > > controller pnp0 > > device pcm0 > > Unfortunately I can't get it working on my SB16PNP with previously worked > flamessly with "oldpcm". I've did as you suggested - as it seems to be pnp card > I've removed all "at isa0 ", rebuilded and rebooted. But with the new > kernel I've observed 2 things: (1) my "pnp 1 0 os enable ..." string is no > longer recognised; (2) SB is no longer works :-(. Following is relevant pieces > of my dmesg output for both cases: Could you send the output of pnpinfo. We are probably missing an ID in the driver. The new pnp code doesn't need the "pnp 1 0 ..." stuff as it deals with resource allocation itself without the need for user intervention. -- 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, Luoqi Chen wrote: > > Could you send the output of dmesg. It could be that your BIOS has > > rearranged the irq settings and has put another card on that IRQ. Is the > > sound card PNP? If not, could you check that the card's IRQ is marked as > > legacy in the BIOS? > > > > Nick > > > > > My sound card used to work, and with a backup kernel it still did ( I lost > > > it ) but after doing a make update world yesturday I came to the > > > realization that it no longer works. Did someone break the sb drivers? I > > > get a drq / irq conflict error, but they are set to the sound card's > > > settings. > > > > > > Arthur H. Johnson II > > > http://www.linuxberg.com > > > Linuxberg Manager > > > [EMAIL PROTECTED] > > > > > I too have problems with my on board CS4236 sound chip and it is of a very > strange nature: in the new isa pnp code, function isa_assign_resources() > mysteriously overwrites the isa_device structure and sets logical_id to 0, > and as a result subsequent probe would not recognize it any more. I have > narrowed it down to the bus_release_resource() call at the end of > isa_find_irq(). It was so convoluted beyond that point and I gave up. > I'd like to see someone more familiar with the code to continue. This sounds pretty strange. What do you have in your kernel config? For PnP cards, you just need: device pcm0 in the config file (i.e. no explicit bus location or resource assignments). -- 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.
> > I too have problems with my on board CS4236 sound chip and it is of a very > > strange nature: in the new isa pnp code, function isa_assign_resources() > > mysteriously overwrites the isa_device structure and sets logical_id to 0, > > and as a result subsequent probe would not recognize it any more. I have > > narrowed it down to the bus_release_resource() call at the end of > > isa_find_irq(). It was so convoluted beyond that point and I gave up. > > I'd like to see someone more familiar with the code to continue. > > This sounds pretty strange. What do you have in your kernel config? For > PnP cards, you just need: > > device pcm0 > > in the config file (i.e. no explicit bus location or resource > assignments). > 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... -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
Doug Rabson wrote: > > Unfortunately I can't get it working on my SB16PNP with previously worked > > flamessly with "oldpcm". I've did as you suggested - as it seems to be pnp card > > I've removed all "at isa0 ", rebuilded and rebooted. But with the new > > kernel I've observed 2 things: (1) my "pnp 1 0 os enable ..." string is no > > longer recognised; (2) SB is no longer works :-(. Following is relevant pieces > > of my dmesg output for both cases: > > Could you send the output of pnpinfo. We are probably missing an ID in the > driver. The new pnp code doesn't need the "pnp 1 0 ..." stuff as it deals > with resource allocation itself without the need for user intervention. this is the second such report i've had; in the previous case the pnp id was present, so i guess there is a problem elsewhere. - cameron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ATAPI CR writing problem after onp
Hi, I have the following errors when I try to append audio to a fixated onp CD-R First, shall I reuse burnaudio when reopening a CD? I made burnaudio work with the following tricks: >>> device=/dev/r$1 wormcontrol -f$device prepdisk single shift for f in $* do echo Burning file $f wormcontrol -f $device track audio wormcontrol -f $device nextwriteable dd if=$f of=$device bs=2352 done wormcontrol -f $device fixate 0 onp <<< fixate 0 instead of 1 prepdisk single instead of double >>> atapi_error: READ_TOC - ILLEGAL REQUEST skey=5 asc=24 ascq=00 error=00 acd0: sequence error (PREP_TRACK) atapi_error: READ_TOC - ILLEGAL REQUEST skey=5 asc=24 ascq=00 error=00 atapi_error: READ_TOC - ILLEGAL REQUEST skey=5 asc=24 ascq=00 error=00 atapi_error: WRITE_BIG - ILLEGAL REQUEST skey=5 asc=21 ascq=17 error=00 atapi_error: READ_TOC - ILLEGAL REQUEST skey=5 asc=24 ascq=00 error=00 atapi_error: READ_TOC - ILLEGAL REQUEST skey=5 asc=24 ascq=00 error=00 acd0: read_toc failed acd0: read_toc failed i4b-L1-timer4_expired: state = F3 Deactivated atapi_error: READ_TRACK_INFO - ILLEGAL REQUEST skey=5 asc=21 ascq=10 error=00 atapi_error: WRITE_BIG - ILLEGAL REQUEST skey=5 asc=64 ascq=21 error=00 atapi_error: READ_TRACK_INFO - ILLEGAL REQUEST skey=5 asc=21 ascq=10 error=00 atapi_error: WRITE_BIG - ILLEGAL REQUEST skey=5 asc=64 ascq=21 error=00 cd9660: Joliet Extension i4b-L1-timer4_expired: state = F3 Deactivated atapi_error: READ_TRACK_INFO - ILLEGAL REQUEST skey=5 asc=21 ascq=10 error=00 atapi_error: WRITE_BIG - ILLEGAL REQUEST skey=5 asc=64 ascq=21 error=00 atapi_error: READ_TRACK_INFO - ILLEGAL REQUEST skey=5 asc=21 ascq=10 error=00 atapi_error: WRITE_BIG - ILLEGAL REQUEST skey=5 asc=64 ascq=21 error=00 <<< The dmesg is >>> atapi: piomode=3, dmamode=1, udmamode=-1 atapi: PIO transfer mode set acd0: CDROM drive at ata0 as master acd0: drive speed 1034KB/sec, 768KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: supported write types: CD-R, CD-RW, test write acd0: Audio: play, 128 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked, lock protected ata0: unwanted interrupt 2 status = 00 ata_command: timeout waiting for interrupt <<< Thanks in advance! Nicholas -- [EMAIL PROTECTED] / [EMAIL PROTECTED] FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the sound card.
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... -- 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
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? Any1? --Ugen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
The problem earlier
OK, I have 2 problems, first the pnp stuff in the kernel is broken, when I took the pnp device out of the kernel, it boots without hanging. Second, the new pcm stuff doesn't work (at least not with my creative Vibra16X). If someone can tell me if the new pcm has full support (except midi, I don't use that) for the Aureal Vortex soundcard, I'll happily try that one, because I have one sitting around waiting for the driver. Second, make world is broken, See my previous message for information about that. Kenneth Culver To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with the sound card.
> 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. -lq To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Failure of new PCM code to pickup my CS4236.
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. 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:25:14 WST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/bloop Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 416530931 Hz CPU: AMD-K6(tm) 3D processor (416.53-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x8800 real memory = 67043328 (65472K bytes) avail memory = 62074880 (60620K bytes) Preloaded elf kernel "kernel" at 0xc02da000. VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc028d642 (122) VESA: NVidia K6-family MTRR support enabled (2 registers) npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 uhci0: irq 10 at device 7.2 on pci0 usb0: 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 rl0: irq 12 at device 9.0 on pci0 rl0: Ethernet address: 00:00:e8:53:a2:3e miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: unknown card DPZ0001 (vendor=0x121a, dev=0x0001) at 11.0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> fdc0: 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 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A joy0 at port 0x201 on isa0 joy0: joystick unknown0: on isa0 unknown1: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 unknown2: at port 0x208-0x20f on isa0 unknown3: at port 0x330-0x331 irq 9 on isa0 ds0 XXX: driver didn't set ifq_maxlen ata0: master: setting up generic WDMA2 mode OK ad0: ATA-4 disk at ata0 as master ad0: 6179MB (12656448 sectors), 12556 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode changing root device to wd0s4a The voxware dmesg is as follows - I needed to have some of the debug statements enabled to reliably detect the card, which argues a timing problem somewhere. 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:39:03 WST 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/bloop Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 416530661 Hz CPU: AMD-K6(tm) 3D processor (416.53-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x8800 real memory = 67043328 (65472K bytes) avail memory = 62033920 (60580K bytes) Preloaded elf kernel "kernel" at 0xc02e4000. VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc0297222 (122) VESA: NVidia K6-family MTRR support enabled (2 registers) npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 uhci0: irq 10 at device 7.2 on pci0 usb0: 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 rl0: irq 12 at device 9.0 on pci0 rl0: Ethernet address: 00:00:e8:53:a2:3e miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: unknown card DPZ0001 (vendor=0x121a, dev=0x0001) at 11.0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> fdc0: 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 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ad1848_detect(534) ad1848_detect() - step A ad1848_detect() - step B, test indirect register ad1848_detect() - step C ad1848_detect() - step D, last 4 bits of I12 readonly ad1848_detect() - step F ad1848_detect() - step G ad1848_detect() - step H ad1848_detect() - s
Re: recent apm changes (FYI)
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. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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, Michael A. Endsley [EMAIL PROTECTED] (was [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
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: irq 10 at device 7.2 on pci0 > usb0: 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=0xfbff real memory = 134217728 (131072K bytes) 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: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 ide_pci0: at device 7.1 on pci0 fxp0: irq 16 at device 12.0 on pci0 fxp0: Ethernet address 00:a0:c9:93:da:0c ahc0: irq 17 at device 13.0 on pci0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs vga-pci0: irq 18 at device 14.0 on pci0 ahc1: irq 19 at device 15.0 on pci0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: 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: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: 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: 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: 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: 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: 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): 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 spec_getpages: I/O read failure: (error code=0) bp 0xc44a3158 vp 0xc9e071c0 size: 0, resid: 0, a_count: 803, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 1 vm_fault: pager read error, pid 921 (cvsup) pid 921 (cvsup), uid 0: exited on signal 6 (core dumped) Poul-Henning Kamp wrote: > > can we have: > > uname -a, > time of last cvsup/ctm > and > dmesg output > > please
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