Re: kernel compile fails...
On Sun 06 Jan 02 06:54, Makoto Matsushita wrote: coolvibe What header file defines SWI_NOSWITCH? http://snapshots.jp.freebsd.org/tour/current/cgi-bin/global.cgi?pattern=SWI _NOSWITCHid=type=symbol SWI_NOSWITCH are used and/or defined by these files. You can easily find that this list have only one *.h file -- sys/sys/interrupt.h. [snip] It's easy to find :-) Yeah indeed. The funny thing was that compiling suddenly worked when I switched INVARIANTS et al back on. I now have other problems, but I'll report them when I've done some more testing... Cheers, Emiel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Question to PAM hackers
Is there a way (i.e. interface function) to check if particular PAM module loaded, inside application? No. Annd nor should there be. The authentication process with PAM means that the authentication policy (including which modules are loaded) are none of the applications damn business :-) M -- o Mark Murray \_ FreeBSD Services Limited O.\_Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Why does bus_alloc_resource fail for sound and PCIC?
In message: 20020105232557.S706-10@nihil Michael Reifenberger [EMAIL PROTECTED] writes: : But why? : Where is PCI_ENABLE_IO_MODES different from: : : pci_enable_busmaster(dev); : pci_enable_io(dev, SYS_RES_IOPORT); : pci_enable_io(dev, SYS_RES_MEMORY); : : or : : data = pci_read_config(dev, PCIR_COMMAND, 2); : data |= (PCIM_CMD_PORTEN | PCIM_CMD_MEMEN | PCIM_CMD_BUSMASTEREN); : pci_write_config(dev, PCIR_COMMAND, data, 2); : : which allready existed in snd_ich ?!? I think it has to do with the caching of these values in the pci layer. The option turns them on and updates the values in the cache, while the other options do not appear to do so. : BTW: In the case of the PCIC I still get: : pcib2: PCI-PCI bridge at device 30.0 on pci0 : pci2: PCI bus on pcib2 : pccbb0: RF5C478 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device : 0.0 on pci2 : pcib2: device pccbb0 requested unsupported memory range 0x5000-0x5fff : (decoding 0xc020-0xcfff, 0xe800-0xefff) : pccbb0: Could not map register memory : device_probe_and_attach: pccbb0 attach returned 12 : pccbb0: RF5C478 PCI-CardBus Bridge mem 0x5010-0x50100fff irq 11 at device : 0.1 on pci2 : pcib2: device pccbb0 requested unsupported memory range 0x5010-0x50100fff : (decoding 0xc020-0xcfff, 0xe800-0xefff) : pccbb0: Could not map register memory : device_probe_and_attach: pccbb0 attach returned 12 Maybe you need some patches to the pci bridge code to map the range requested, or to just allow it (since it just works anyway). There's another kludge option: PCI_ALLOW_UNSUPPORTED_IO_RANGE. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
installworld error (ex: not found)
I've been having some trouble getting this -CURRENT system to do a proper installworld. I installed a JPSNAP (20011230) with only the /bin distribution, then cvsup'ed, made world and kernel, and went on to the installworld. I've done this thrice now (January 3,5,6), and each time I get the same error: [snip things going fine] ... install -c -o root -g wheel -m 444 xerox1730 /usr/share/tabset/xerox1730 install -c -o root -g wheel -m 444 xerox1730-lm /usr/share/tabset/xerox1730-lm install -c -o root -g wheel -m 444 zenith29 /usr/share/tabset/zenith29 === share/termcap install -c -o root -g wheel -m 444 /usr/src/share/termcap/map3270 /usr/share/misc/map3270 TERM=dumb ex - /usr/src/share/termcap/termcap.src /usr/src/share/termcap/reorder ex: not found *** Error code 127 Stop in /usr/src/share/termcap. *** Error code 1 ...so wondering where ex is and what is wrong with it: [15:26 munish@rn-re116a13 ~] ll /usr/bin/ex -r-xr-xr-x 6 root wheel 279952 Dec 29 15:19 /usr/bin/ex ...it's there and fine. The PATH is set fine too. So I don't really know where to go from here...hints are welcome. Thanks. -- Munish Chopra To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel build fails
On Sat, 5 Jan 2002, Sheldon Hearn wrote: Yeah, that script was committed untested. :-( Try the untested patch included below. Why are there C-style comments in a Perl script? * This file is produced automatically. * Do not modify anything in here by hand. * - * Created from $FreeBSD: src/sys/kern/vnode_if.pl,v 1.28 2002/01/04 05:27:47 silby Exp $ + * Created from \$FreeBSD: src/sys/kern/vnode_if.pl,v 1.28 2002/01/04 05:27:47 silby Exp $ */ Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mergemaster and /etc/pam.d
On Fri, Jan 04, 2002 at 17:12:56 -0800, John Baldwin wrote: On 05-Jan-02 Michael Harnois wrote: I don't think pam.d is installed right now by default. Hmm. I'm not sure how it got installed on my system at all, then ... mtree creates the directory but the current makefiles don't install anything in the directory. There is error can sneak here easily. If /etc/pam.d directory even exist, PAM ignores /etc/pam.conf contents. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Question to PAM hackers
On Sat, Jan 05, 2002 at 13:21:08 +0200, Mark Murray wrote: Is there a way (i.e. interface function) to check if particular PAM module loaded, inside application? No. Annd nor should there be. The authentication process with PAM means that the authentication policy (including which modules are loaded) are none of the applications damn business :-) Chaining as concept is poor when conditionalized modules handling is needed. F.e. currently it is impossible to write proper pam_opie and pam_unix interaction using just chaining even they appearse always in fixed order. As workaround pam_unix forced to be removed and handled by application itself. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel build fails
On Sun, 2002-01-06 at 19:38, Doug White wrote: Why are there C-style comments in a Perl script? At a guess, it's a here document. -- brandon s. allbery [os/2][linux][solaris][japh] [EMAIL PROTECTED] system administrator [WAY too many hats][EMAIL PROTECTED] electrical and computer engineeringKF8NH carnegie mellon university [better check the oblivious first -ke6sls] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Why does bus_alloc_resource fail for sound and PCIC?
On Sun, 6 Jan 2002, M. Warner Losh wrote: ... : pci2: PCI bus on pcib2 : pccbb0: RF5C478 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device : 0.0 on pci2 : pcib2: device pccbb0 requested unsupported memory range 0x5000-0x5fff : (decoding 0xc020-0xcfff, 0xe800-0xefff) : pccbb0: Could not map register memory : device_probe_and_attach: pccbb0 attach returned 12 : pccbb0: RF5C478 PCI-CardBus Bridge mem 0x5010-0x50100fff irq 11 at device : 0.1 on pci2 : pcib2: device pccbb0 requested unsupported memory range 0x5010-0x50100fff : (decoding 0xc020-0xcfff, 0xe800-0xefff) : pccbb0: Could not map register memory : device_probe_and_attach: pccbb0 attach returned 12 Maybe you need some patches to the pci bridge code to map the range requested, or to just allow it (since it just works anyway). There's another kludge option: PCI_ALLOW_UNSUPPORTED_IO_RANGE. Thanks for the hint. After applying my attached patch this option got accepted and led to probed and attached NEWCARD devices. Inserting a FA411 Card leads to a frozen system (after reading the CIS info) until the card gets ejected. Haven't tried the OLDCARD (which worked in compat mode anyway) yet. Maybe NEWCARD is trying to use wrong resources here... Maybe we need some special handling for the new Intel-mobile-chipset used by IBM (which supports up to 1GB of memory). Bye! Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS --- conf/options.orig Sat Dec 22 17:05:24 2001 +++ conf/optionsMon Jan 7 02:44:51 2002 @@ -418,4 +418,5 @@ PCI_QUIET opt_pci.h PCI_ENABLE_IO_MODESopt_pci.h +PCI_ALLOW_UNSUPPORTED_IO_RANGE opt_pcib.h # NFS options --- dev/pci/pci_pci.c.orig Mon Nov 26 08:12:35 2001 +++ dev/pci/pci_pci.c Mon Jan 7 02:44:27 2002 @@ -35,4 +35,7 @@ */ +#include opt_bus.h +#include opt_pcib.h + #include sys/param.h #include sys/systm.h
xfree86 4?
What are the plans about replacing XFree86 3.3.6 with XFree86 4? The -current archives have a message saying this replacement already took place last October, but the JP SNAP I installed last November certainly wasn't aware of that fact, and the current.freebsd.org snapshot from January 6 still lists 3.3.6 as well. Two more months and it will be two years since XFree86-4.0... Looking at xfree86.org's comparisons of supported video cards, it seems quite obvious that XFree86 4 supports almost everything 3 did, and a lot more. I just got a computer with a nvidia GeForce2 GTS - not exactly a new card, but completely unsupported in 3.3.6 - but well supported in 4.1.0. 3.3.6 is over two years old, and none of the ATI or nvidia cards (and that's just about all desktops, no?) made since then are supported. There's always the port, but integration would be a much more friendly solution. I must be growing lazy :) Out-of-the-box XFree86 4 and easy PPPoE setup led me to use RedHat (desk top only - the server's still FreeBSD, of course), but I'm missing FreeBSD. Apologies if this has already been discussed to death, but such discussions aren't in the -current or -stable archives :) -David To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mergemaster and /etc/pam.d
On 07-Jan-02 Andrey A. Chernov wrote: On Fri, Jan 04, 2002 at 17:12:56 -0800, John Baldwin wrote: On 05-Jan-02 Michael Harnois wrote: I don't think pam.d is installed right now by default. Hmm. I'm not sure how it got installed on my system at all, then ... mtree creates the directory but the current makefiles don't install anything in the directory. There is error can sneak here easily. If /etc/pam.d directory even exist, PAM ignores /etc/pam.conf contents. DES has fixed this. What it did was break the 'other' type, but this issue has been addressed. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
