Re: [current] hostap+wi
On Sun, Jul 06, 2003 at 09:40:38AM +0900, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Ruslan Ermilov [EMAIL PROTECTED] writes: : On Sat, Jul 05, 2003 at 04:48:09PM -0400, David Gilbert wrote: : [...] : The hostap machine is 4.8-STABLE and the client is 5.1-RELEASE. : : One nice thing about the hostap is that bridge(4) works with wi(4) : that is in hostap mode. Does anybody know if only Intersil cards : have the hostap mode, or some Prism's also do? Intersil and Prism are the same thing. Prism 2, 2.5 and 3 cards have Intersil firmware. There are some cards based on prism chipsets that have Symbol firmware, but those are rare. The wavelan/lucent/orinoco firmware doesn't support a hostap mode, but there are add-ins that give ap functionality. Uh sorry, it was very late in the night here; of course I meant Lucent chipsets when asking if they also support host-ap mode. What are these add-ins you're talking about? I'm mostly interested in the bridge(4) functionality. As I understand, to do briding, the card should be able to send frames with arbitrary MAC addresses, and when not in host-ap mode, Lucent based chipsets do not allow this (i.e., you see with tcpdump(1) that packets is written to wi0 interface, but the other end doesn't receive the frame). What surprises me here, is that these same cards appear to work (by forwarding arbitrary Ethernet frames) when inserted into Lucent-based APs. Does anyone have a valid explanation to this? Is this an artificial limitation on these cards to limit their commercial use, or am I missing an obvious? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software Ltd, [EMAIL PROTECTED] FreeBSD committer pgp0.pgp Description: PGP signature
[-CURRENT tinderbox] failure on i386/i386
TB --- 2003-07-06 06:32:55 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-07-06 06:32:55 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-06 06:34:48 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/i386/src TB --- /usr/bin/make -B buildworld Building an up-to-date make(1) Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/i386/i386/obj/vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/share/man/man9/vfs_rootmountalloc.9 vfs_rootmountalloc.9.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/share/man/man9/vfs_timestamp.9 vfs_timestamp.9.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/share/man/man9/vfs_unbusy.9 vfs_unbusy.9.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/share/man/man9/vfs_unmountall.9 vfs_unmountall.9.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/share/man/man9/vfsconf.9 vfsconf.9.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/share/man/man9/vget.9 vget.9.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/share/man/man9/vgone.9 vgone.9.gz Segmentation fault (core dumped) *** Error code 139 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/share/man. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src/share. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/i386/src. TB --- 2003-07-06 07:26:28 - /usr/bin/make returned exit code 1 TB --- 2003-07-06 07:26:28 - ERROR: failed to build world TB --- 2003-07-06 07:26:28 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on i386/pc98
TB --- 2003-07-06 07:26:29 - starting CURRENT tinderbox run for i386/pc98 TB --- 2003-07-06 07:26:29 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-06 07:31:53 - building world TB --- cd /home/des/tinderbox/CURRENT/i386/pc98/src TB --- /usr/bin/make -B buildworld Building an up-to-date make(1) Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/i386/pc98/obj/pc98/vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] === lib/msun gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/msun/man/acos.3 acos.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/msun/man/acosh.3 acosh.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/msun/man/asin.3 asin.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/msun/man/asinh.3 asinh.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/msun/man/atan.3 atan.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib/msun/man/atan2.3 atan2.3.gz Segmentation fault (core dumped) *** Error code 139 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src/lib. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/i386/pc98/src. TB --- 2003-07-06 08:09:28 - /usr/bin/make returned exit code 1 TB --- 2003-07-06 08:09:28 - ERROR: failed to build world TB --- 2003-07-06 08:09:28 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb mouse on ehci controller doesn't work
On Sat, 5 Jul 2003, Bruce Cran wrote: I'm sure I used to be able to use a usb mouse in earlier versions of FreeBSD, but now whatever I try, I just can't get the secondary mouse (or primary, if I don't configure the laptop mouse pad) to work. When I plug it in, it finds it and allocates it to /dev/ums0 (ums0: Logitech USB Receiver, rev 1.10/13.10, addr 2, iclass 3/1. ums0: 5 buttons and Z dir) but XFree86 doesn't seem to like it - the log file Dying on a fcntl O_ASYNC, strange. is attached. Also, moused doesn't show the pointer when I run 'moused -p /dev/ums0 -t auto'. I can confirm that my wired mx300 mouse with a Hi-speed USB machine works fine. Note that it shouldn't be attaching to ehci but to the underlying controller, uhci most likely. 'usbdevs' will show you the device tree. Are you doing 'vidcontrol -m on' to enable the mouse in the current vty? Has something in the ums driver changed that X11 doesn't like, or have I not configured something. Could it be that I've always used it on a computer with USB1 and there's something about the usb2 I've now got that the logitech controller doesn't like? The lines from XF86Config are: Have you tried using moused + xfree86? -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: 3COM ep0 pccard device broken in current.
i had reported failure of my combo card 3c556 before, the serial device sio4 seems to be working(not tested with connectivity) but the ep0 device give up with errors ep0: 3Com Megahertz 3CCFEM556B at port 0x100-0x11f irq11 function 0 config 7 on pccard1 ep0: eeprom failed to come ready. device_probe_attach: ep0 attach returned 6 will the latest cvs changes fix this too ? the card works on almost all *BSD's including 4-stable. dheeraj -Original Message- From: Andrea Campi [EMAIL PROTECTED] To: Mark Murray [EMAIL PROTECTED] Date: Sat, 5 Jul 2003 16:45:04 +0200 Subject: Re: 3COM ep0 pccard device broken in current. On Fri, Jul 04, 2003 at 03:26:07PM +0100, Mark Murray wrote: There were two changes. One is in pccbb.c that makes things a MPSAFE interrupt. You could revert to version 1.175 of pccbb.c. I'll play with that in a few hours when I get home. [...] Revision 1.115 / (download) - annotate - [select for diffs], Thu Jun 26 13:27:44 2003 UTC (7 days, 23 hours ago) by mux Changes since 1.114: +5 -7 lines I played with this, but without playing with the pccbb.c stuff. I'll give it a go tonight. Mark, I used to see the same issue you are seeing starting from the time the change to pccbb.c went in, but mux's fix to if_ep.c solved it all for me. However, it's always possible that yours is a slightly different problem, so I'd be interested to hear what you are doing exacly so that I could try and repeat it. Bye, Andrea -- Loose bits sink chips. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Call for testers: patch to convert dc(4) to busdma
On Sat, Jul 05, 2003 at 04:07:26PM +0200, Maxime Henrion wrote: Wilko Bulte wrote: Could it be there is something fishy with mbuf handling? Could you please try the attached patch? It's absolutely untested except for compilation because I have to leave right now, but I believe it should fix the mbuf leaks you've been reporting. I ran netperf and bonnie via nfs in both directions. Everything ran fine, no mbuf issues or whatever. Anything specific you want tested in addition? Wilko -- | / o / /_ _ [EMAIL PROTECTED] |/|/ / / /( (_) Bulte ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Movie
This is an automatic answering service that allows you to get more information about our program and prepare material for a formal application ELECTRICAL AND COMPUTER ENGINEERING LOUISIANA STATE UNIVERSITY INSTRUCTIONS FOR e-mail APPLICANTS You can get information about our program from our homepage on the WEB http://www.ee.lsu.edu You can also download information using our FTP server location ftp.ee.lsu.edu/gradinfo You can also obtain information using e-mail as follows send e-mail message [EMAIL PROTECTED] put in the subject line ONE of the following code words computers info on the area of computer engineering electronics info on the area of materials and electronics power info on electric power and power electronics systems info on communications, signal processing and automatic control labsinfo on some of the research facilities finance info on financial assistance faculty faculty names, areas of interest and e-mail addressess preapplication to receive an electronic pre-application application to receive a PDF version of the Graduate School Application recommendation to receive an electronic recommendation form -- You MUST complete and e-mail the pre application form to [EMAIL PROTECTED] Make sure that ALL data are completed, especially the information about test scores and academic ranking. TOGETHER with the pre application form, e-mail a STATEMENT OF PURPOSE indicating which area of our graduate program is of particular interest to you and why. Briefly summarize the qualifications that would make you suitable for an assistanship (research and/or teaching) Ask three professors that know you academically to send us letters of recommendation If feasible, download from our site the postscript file with letter of recommendation form, make three copies of it and ask your professors to mail them directly to GRADUATE ADVISOR ELECTRICAL AND COMPUTER ENGINEERING LOUISIANA STATE UNIVERSITY BATON ROUGE, LA 70803-5901 Alternatively, send an email message to[EMAIL PROTECTED] put in the subject line put the wordrecommendation You will receive a plain text form that your professors can complete and mail. For the sake of speed, YOUR PROFESSOR CAN E-MAIL the completed form to us at [EMAIL PROTECTED] If e-mail is used, it MUST be supplemented by a letter from your major professor with his or her signature. ONCE WE HAVE RECEIVED ALL THE MATERIAL REQUESTED ABOVE, WE WILL MAKE A PRELIMINARY EVALUATION AND IF APPLICABLE WE WILL SEND YOU ALL THE MATERIAL NECESSARY FOR A FORMAL APPLICATION ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Movie
This is an automatic answering service that allows you to get more information about our program and prepare material for a formal application ELECTRICAL AND COMPUTER ENGINEERING LOUISIANA STATE UNIVERSITY INSTRUCTIONS FOR e-mail APPLICANTS You can get information about our program from our homepage on the WEB http://www.ee.lsu.edu You can also download information using our FTP server location ftp.ee.lsu.edu/gradinfo You can also obtain information using e-mail as follows send e-mail message [EMAIL PROTECTED] put in the subject line ONE of the following code words computers info on the area of computer engineering electronics info on the area of materials and electronics power info on electric power and power electronics systems info on communications, signal processing and automatic control labsinfo on some of the research facilities finance info on financial assistance faculty faculty names, areas of interest and e-mail addressess preapplication to receive an electronic pre-application application to receive a PDF version of the Graduate School Application recommendation to receive an electronic recommendation form -- You MUST complete and e-mail the pre application form to [EMAIL PROTECTED] Make sure that ALL data are completed, especially the information about test scores and academic ranking. TOGETHER with the pre application form, e-mail a STATEMENT OF PURPOSE indicating which area of our graduate program is of particular interest to you and why. Briefly summarize the qualifications that would make you suitable for an assistanship (research and/or teaching) Ask three professors that know you academically to send us letters of recommendation If feasible, download from our site the postscript file with letter of recommendation form, make three copies of it and ask your professors to mail them directly to GRADUATE ADVISOR ELECTRICAL AND COMPUTER ENGINEERING LOUISIANA STATE UNIVERSITY BATON ROUGE, LA 70803-5901 Alternatively, send an email message to[EMAIL PROTECTED] put in the subject line put the wordrecommendation You will receive a plain text form that your professors can complete and mail. For the sake of speed, YOUR PROFESSOR CAN E-MAIL the completed form to us at [EMAIL PROTECTED] If e-mail is used, it MUST be supplemented by a letter from your major professor with his or her signature. ONCE WE HAVE RECEIVED ALL THE MATERIAL REQUESTED ABOVE, WE WILL MAKE A PRELIMINARY EVALUATION AND IF APPLICABLE WE WILL SEND YOU ALL THE MATERIAL NECESSARY FOR A FORMAL APPLICATION ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb mouse on ehci controller doesn't work
On Sun, Jul 06, 2003 at 01:21:47AM -0700, Doug White wrote: On Sat, 5 Jul 2003, Bruce Cran wrote: I'm sure I used to be able to use a usb mouse in earlier versions of FreeBSD, but now whatever I try, I just can't get the secondary mouse (or primary, if I don't configure the laptop mouse pad) to work. When I plug it in, it finds it and allocates it to /dev/ums0 (ums0: Logitech USB Receiver, rev 1.10/13.10, addr 2, iclass 3/1. ums0: 5 buttons and Z dir) but XFree86 doesn't seem to like it - the log file Dying on a fcntl O_ASYNC, strange. is attached. Also, moused doesn't show the pointer when I run 'moused -p /dev/ums0 -t auto'. I can confirm that my wired mx300 mouse with a Hi-speed USB machine works fine. Note that it shouldn't be attaching to ehci but to the underlying controller, uhci most likely. 'usbdevs' will show you the device tree. Are you doing 'vidcontrol -m on' to enable the mouse in the current vty? I swapped the Logitech wireless mouse for a Microsoft Intellimouse optical, and this time had slightly more success. If I run moused and tell XFree86 to use both /dev/psm0 and /dev/sysmouse, it still dies with the fcntl error. However, if I'm only using /dev/sysmouse, it works perfectly. The kernel has uhci but not ehci compiled in, so it must indeed be using the low-speed driver, not ehci. If I don't run moused but just tell X11 to use /dev/ums0, it still fails with the fcntl error. -- Bruce Cran ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Call for testers: patch to convert dc(4) to busdma
Wilko Bulte wrote: On Sat, Jul 05, 2003 at 04:07:26PM +0200, Maxime Henrion wrote: Wilko Bulte wrote: Could it be there is something fishy with mbuf handling? Could you please try the attached patch? It's absolutely untested except for compilation because I have to leave right now, but I believe it should fix the mbuf leaks you've been reporting. I ran netperf and bonnie via nfs in both directions. Everything ran fine, no mbuf issues or whatever. Cool! Anything specific you want tested in addition? No, I've got everything I need, thanks a bunch. I'll probably commit this patch later tonight since I received successful reports on x86, alpha and ia64, modulo this mbuf leak that is now fixed. Thanks to everyone who tested this patch, it's very much appreciated. Maxime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Silicon Image SiI 3112 Serial ATA controller support?
Hi, Is the Silicon Image SiI 3112 Serial ATA controller supported in -CURRENT, or is anybody working on support? I have one here (on a Asus A7N8X mainboard), but the controller is not recognized at boot. If I can help anyone with information about the system, that'd be very nice - I'd like to have support for those fast Western Digital Raptors :). Best regards, Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Silicon Image SiI 3112 Serial ATA controller support?
It seems Arjan van Leeuwen wrote: Hi, Is the Silicon Image SiI 3112 Serial ATA controller supported in -CURRENT, or is anybody working on support? I have one here (on a Asus A7N8X mainboard), but the controller is not recognized at boot. If I can help anyone with information about the system, that'd be very nice - I'd like to have support for those fast Western Digital Raptors :). I committed support for that couple of days ago: ata-chipset.c: revision 1.32 date: 2003/07/02 10:50:44; author: sos; state: Exp; lines: +114 -46 Update the SATA support code to work more correctly with real SATA disks now that I can test it. Add support for the SiI 3112 SATA chip using memory mapped I/O. Update the support for the SiI 0680 to use the memio interface as well. Sponsored by: David Leimbach [EMAIL PROTECTED] (3112 based controller) Sponsored by: FreeBSD Systems (www.FreeBSDsystems.com) (SATA disks) -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Silicon Image SiI 3112 Serial ATA controller support?
On Sunday 06 July 2003 18:01, Soeren Schmidt wrote: It seems Arjan van Leeuwen wrote: (...) I committed support for that couple of days ago: ata-chipset.c: revision 1.32 date: 2003/07/02 10:50:44; author: sos; state: Exp; lines: +114 -46 Update the SATA support code to work more correctly with real SATA disks now that I can test it. Add support for the SiI 3112 SATA chip using memory mapped I/O. Update the support for the SiI 0680 to use the memio interface as well. Thanks! I'll update immediately. Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ffs_copyonwrite: locking against myself - snapshot related panic
I created snapshots of /var, /, /tmp and /usr, and then continued to use the system normally, after beginning to move one of the snapshots across to an nfs directory, then cancelling the move. When I later came to install lftp from /usr/ports/ftp/lftp, I had the following panic: ffs_copyonwrite: locking against myself since a debug kernel wasn't built, I rebooted, fsck'd the filesystems and rebuilt the kernel. I then proceeded to trigger the panic again by running 'make install' in /usr/ports/ftp/lftp, and got the following trace: Debugger panic lockmgr BUF_TIMELOCK getblk breadn bread ffs_alloccg ffs_hashalloc ffs_alloc ffs_balloc_ufs2 ffs_copyonwrite spec_xstrategy spec_specstrategy spec_vnoperate bwrite bawrite ffs_nodealloccg ffs_hashalloc ffs_valloc ufs_makeinode ufs_create ufs_vnoperate VOP_CREATE vn_open_cred vn_open kern_open open syscall Xint0x80_syscall syscall(5, FreeBSD ELF32, open) I can trigger this on demand, whether the 'nvidia' module is loaded or not. All my slices are UFS2, and have been fsck'd in single-user mode. The second panic I had generated messages about recovering errors for about 30 seconds when I fsck'd /usr, so I don't know what kind of state it's now in. The panic seems to have disappeared after I deleted the snapshot files. Are snapshots supposed to be able to be moved/copied around like images - or are they part of the 'real' filesystem, and so have to be treated carefully? -- Bruce Cran ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Silicon Image SiI 3112 Serial ATA controller support?
Yeah... and it works wonderfully On Sunday, July 6, 2003, at 11:13AM, Arjan van Leeuwen wrote: On Sunday 06 July 2003 18:01, Soeren Schmidt wrote: It seems Arjan van Leeuwen wrote: (...) I committed support for that couple of days ago: ata-chipset.c: revision 1.32 date: 2003/07/02 10:50:44; author: sos; state: Exp; lines: +114 -46 Update the SATA support code to work more correctly with real SATA disks now that I can test it. Add support for the SiI 3112 SATA chip using memory mapped I/O. Update the support for the SiI 0680 to use the memio interface as well. Thanks! I'll update immediately. Arjan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3COM ep0 pccard device broken in current.
What a weekend. Frigging _everything_ was a messup. M. Warner Losh writes: In message: [EMAIL PROTECTED] Mark Murray [EMAIL PROTECTED] writes: : M. Warner Losh writes: : Have you gotten all of the recent changes to current wrt ep0? It was : broken by my making cbbintr mpsafe. Well, it was broken a long time : ago, my change just opened a race that used to be won, but now is : lost. : : Yup. I believe so, but please confirm where the change was to be sure? There were two changes. One is in pccbb.c that makes things a MPSAFE interrupt. You could revert to version 1.175 of pccbb.c. Bingo! (I presumed that you meant 1.75, pccbb doesn't go as far as 1.175). Backing out to 1.75 has my ep0 working again! For ep.c, you need the following or newer Revision 1.115 / (download) - annotate - [select for diffs], Thu Jun 26 13:27:44 2003 UTC (7 days, 23 hours ago) by mux Changes since 1.114: +5 -7 lines Got that. NOW. Can I interest you in doing some ToPIC97 fixes, helping to sort out some working but uncommitted Libretto-110CT ACPI/HDD fixes and a has-never-worked dc0 cardbus card? Pleze? :-) M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [acpi-jp 2366] Re: Updated ec-burst.diff patch
On Sat, 5 Jul 2003, Anish Mistry wrote: The patch is not a complete implementation but it should help identify any hw problems in burst mode support. I won't put it into the tree without making sure it can fall back correctly. Also, since I forgot the URL the second time: http://root.org/~nate/freebsd/ec-burst.diff -Nate I applied it on my Fujitsu P-2110 and rebuilt world, but didn't see any changes or regression. Ok. I'm reworking it a bit but do not have time to test and get it out this weekend. Work is crazy until Tuesday. Outstanding issues: - - Battery still drains uncontrollably in S3 No idea on this. - - USB devices dead on resume (working a usb code patch for this) I have the same problem. I have a feeling there is not sufficient save/restore of usb uhci registers. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Promise SX6000 - error 128 lba 0
I have installed FreeBSD 5.1 from CD onto a machine with a Promise SX6000 controller with a RAID5 on 360GB. The installation went very well, but when the machine start to boot from the disk, the console shows: --- START --- F1 FREEBSD Default: F1 error 128 lba 0 FreeBSD/i386 boot Default: 0:ad(0,a)/boot/loader boot: error 128 lba 0 No /boot/loader --- STOP --- From what I can see the bootdevice is wrong ? shouldn't it be the pst0 device instead of ad(0,a) ? -- Gorm J. Siiger - SonnIT ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [acpi-jp 2366] Re: Updated ec-burst.diff patch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Outstanding issues: - - Battery still drains uncontrollably in S3 No idea on this. I seem to be getting this answer from everyone. Is there some specific debugging info that I could provide the list to help with fixing this? - - USB devices dead on resume (working a usb code patch for this) I have the same problem. I have a feeling there is not sufficient save/restore of usb uhci registers. My laptop uses ohci, but looking at the code it's quite similar. I am able to have devices work on resume if I use my code patch to completely reinitilize the usb bus, but cause panics if devices are plugged in and being accessed, since the interrupt values change. I'll look into the register values. - -- Anish Mistry -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/CH45xqA5ziudZT0RAnf0AKCddBGxH6QwZSxBoNJNANS0nbplcACeKKyt AyJdH6KtAvdziAzwVBVsrWI= =EQOn -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3COM ep0 pccard device broken in current.
Andrea Campi writes: I played with this, but without playing with the pccbb.c stuff. I'll give it a go tonight. Mark, I used to see the same issue you are seeing starting from the time the change to pccbb.c went in, but mux's fix to if_ep.c solved it all for me. However, it's always possible that yours is a slightly different problem, so I'd be interested to hear what you are doing exacly so that I could try and repeat it. Hi. Reverting pccbb.c to 1.75 fixed this for me. M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise SX6000 - error 128 lba 0
It seems Gorm J. Siiger wrote: I have installed FreeBSD 5.1 from CD onto a machine with a Promise SX6000 controller with a RAID5 on 360GB. The installation went very well, but when the machine start to boot from the disk, the console shows: You cant boot from a sx6000 controller, our bootblocks does something stupid that the sx6000 BIOS doesn't understand... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise SX6000 - error 128 lba 0
You cant boot from a sx6000 controller, our bootblocks does something stupid that the sx6000 BIOS doesn't understand... Damn, can I put the bootblock on another device ? CD for example. -- Gorm J. Siiger - SonnIT ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise SX6000 - error 128 lba 0
It seems Gorm J. Siiger wrote: You cant boot from a sx6000 controller, our bootblocks does something stupid that the sx6000 BIOS doesn't understand... Damn, can I put the bootblock on another device ? CD for example. Sure, you can mount the pst devices as soon as the kernel is running, so you just need to get the thing off the ground (CD, floppy, ZIP, flash whatever) -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on ia64/ia64
TB --- 2003-07-06 21:23:01 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2003-07-06 21:23:01 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-06 21:26:15 - building world TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64/src TB --- /usr/bin/make -B buildworld Building an up-to-date make(1) Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/ia64/ia64/obj/ia64/vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libc/locale/mbsinit.3 mbsinit.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libc/locale/mbsrtowcs.3 mbsrtowcs.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libc/locale/multibyte.3 multibyte.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libc/locale/nl_langinfo.3 nl_langinfo.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libc/locale/rune.3 rune.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libc/locale/setlocale.3 setlocale.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib/libc/locale/toascii.3 toascii.3.gz Segmentation fault (core dumped) *** Error code 139 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src/lib. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/ia64/ia64/src. TB --- 2003-07-06 22:08:46 - /usr/bin/make returned exit code 1 TB --- 2003-07-06 22:08:46 - ERROR: failed to build world TB --- 2003-07-06 22:08:46 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI vs fdc0
Hi, my floppy disc drive does not work. I was ignoring this fact until today, because I need to write something to a floppy. It's probably clashing with something ACPI is claiming: [during boot] fdc0: cmd 3 failed at out byte 1 of 3 fdc0: cmd 3 failed at out byte 1 of 3 fdc0: cannot reserve I/O port range (6 ports) [devinfo -u] 0x3f0-0x3f1 (acpi_sysresource0) 0x3f2-0x3f5 0x3f6 (ata0) 0x3f7 (root0) How can I get tell ACPI to free those two I/O ports? It works fine when I disable ACPI, but disabling ACPI is not an option, because X does not start without it. I need floppy under X. I searched mailing list archives and exactly this same problem was discussed back in summer 2001. I can't believe no solutions have been made since then. [uname -a] FreeBSD hood.oook.cz 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri Jul 4 21:23:06 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PAV i386 I'll provide any other debug information needed. -- Pav Lucistnik [EMAIL PROTECTED] What do we know about love? Love is like a pear. Pear is sweet and have a specific shape. Try to exactly define the shape of a pear. -- Marigold: 50 Years Of Poetry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
OpenPAM dynamic module loading not working ?
Hey, I'm trying to setup authentication against a PostgreSQL Database with OpenPAM and pam_pgsql. I have installed the pam_pgsql port and configured a few services (samba, pop3) to authenticate against the DB. Whenever an authentication request is made I get the following errors (regardless of the source service): Samba: Jul 7 22:22:18 bacon smbd[67333]: in openpam_load_module(): no pam_pgsql.so found Jul 7 22:22:18 bacon smbd[67333]: [2003/07/07 22:22:18, 0] passdb/pampass.c:smb_pam_error_handler(71) Jul 7 22:22:18 bacon smbd[67333]: smb_pam_error_handler: PAM: Init Failed : failed to load module Dovecot: Jul 7 22:10:40 bacon dovecot-auth: in openpam_load_module(): no pam_pgsql.so found Jul 7 22:10:40 bacon dovecot-auth: PAM: pam_start(example) failed: failed to load module I have checked I installed things properly, I also created the link although that shouldn't be required (from looking at the source). bacon# ls -l /usr/lib/pam_pgsql.so* lrwxr-xr-x 1 root wheel 14 Jul 7 21:45 /usr/lib/pam_pgsql.so - pam_pgsql.so.2 -r--r--r-- 1 root wheel 14052 Jan 12 10:46 /usr/lib/pam_pgsql.so.2 The pam.d file I'm using for Samba: bacon# cat /etc/pam.d/samba # # /etc/pam.d/samba # authrequiredpam_pgsql.so account requiredpam_pgsql.so passwordrequiredpam_pgsql.so I can't find anything wrong in my configuration, but maybe I'm being stupid. If someone has any ideas on a resolution, I'd appreciate it. Thanks, -- Dominic dom at cus.org.uk dominic.marks at npl.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
[-CURRENT tinderbox] failure on sparc64/sparc64
TB --- 2003-07-06 22:09:15 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2003-07-06 22:09:15 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-06 22:11:45 - building world TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64/src TB --- /usr/bin/make -B buildworld Building an up-to-date make(1) Rebuilding the temporary build tree stage 1: legacy release compatibility shims stage 1: bootstrap tools stage 2: cleaning up the object tree stage 2: rebuilding the object tree stage 2: build tools stage 3: cross tools stage 4: populating /home/des/tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/i386/usr/include stage 4: building libraries stage 4: make dependencies stage 4: building everything.. [...] gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/timezone.3 timezone.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/ttyname.3 ttyname.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/tzset.3 tzset.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/ualarm.3 ualarm.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/ucontext.3 ucontext.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/ulimit.3 ulimit.3.gz gzip -cn /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib/libc/gen/uname.3 uname.3.gz Segmentation fault (core dumped) *** Error code 139 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src/lib. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /vol/vol0/users/des/tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2003-07-06 22:48:30 - /usr/bin/make returned exit code 1 TB --- 2003-07-06 22:48:30 - ERROR: failed to build world TB --- 2003-07-06 22:48:30 - tinderbox aborted ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Tinderboxes segfaulting (Re: [-CURRENT tinderbox] failure onsparc64/sparc64)
On Sun, Jul 06, 2003 at 10:48:30PM +, Tinderbox wrote: Segmentation fault (core dumped) *** Error code 139 Does anyone know why all the tinderboxes are segfaulting? Does the machine have hardware problems, or did someone introduce a malloc bug into -current? Kris pgp0.pgp Description: PGP signature
/dev/shm
I attempted to install the linux java sapgui on FreeBSD 5.0, but the jar file only unpacked part of it. I then copied the files from my Redhat 9 machine. I linked up all the linux libraries needed and attempted to start it. It gives me an error saying cant find /dev/shm. I tried adding this to /dev but was unable to. Does anyone have any information? Thank you. I am somewhat new to FreeBSD but have used linux for Many years. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/shm
Myron J. Mayfield wrote: I attempted to install the linux java sapgui on FreeBSD 5.0, but the jar file only unpacked part of it. I then copied the files from my Redhat 9 machine. I linked up all the linux libraries needed and attempted to start it. It gives me an error saying cant find /dev/shm. I tried adding this to /dev but was unable to. Does anyone have any information? Thank you. I am somewhat new to FreeBSD but have used linux for Many years. For some unexcused reason there is the trend in Linux to represent everything as kind of a wired half finished pseudo file system. /proc pipe devicefs sysctl and so on... The list is really long. Even shared memmory is mapped to ehrm a filesystem. This is expected to be mounted at /dev/shm by the system. You can't expect FreeBSD to follow this path... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/shm
Marcin Dalecki wrote: Myron J. Mayfield wrote: I attempted to install the linux java sapgui on FreeBSD 5.0, but the jar file only unpacked part of it. I then copied the files from my Redhat 9 machine. I linked up all the linux libraries needed and attempted to start it. It gives me an error saying cant find /dev/shm. I tried adding this to /dev but was unable to. Does anyone have any information? Thank you. I am somewhat new to FreeBSD but have used linux for Many years. For some unexcused reason there is the trend in Linux to represent everything as kind of a wired half finished pseudo file system. /proc pipe devicefs sysctl and so on... The list is really long. Even shared memmory is mapped to ehrm a filesystem. This is expected to be mounted at /dev/shm by the system. You can't expect FreeBSD to follow this path... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] Is there a way to emulate /dev/shm? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/shm
On Mon, Jul 07, 2003 at 01:58:19AM +0200, Marcin Dalecki wrote: Myron J. Mayfield wrote: I attempted to install the linux java sapgui on FreeBSD 5.0, but the jar file only unpacked part of it. I then copied the files from my Redhat 9 machine. I linked up all the linux libraries needed and attempted to start it. It gives me an error saying cant find /dev/shm. I tried adding this to /dev but was unable to. Does anyone have any information? Thank you. I am somewhat new to FreeBSD but have used linux for Many years. For some unexcused reason there is the trend in Linux to represent everything as kind of a wired half finished pseudo file system. /proc pipe devicefs sysctl and so on... The list is really long. Even shared memmory is mapped to ehrm a filesystem. This is expected to be mounted at /dev/shm by the system. You can't expect FreeBSD to follow this path... Linux isn't the only system that does this (learn a little, criticize less). -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/shm
On Sun, Jul 06, 2003 at 08:14:44PM -0400, Thomas Dickey wrote: : On Mon, Jul 07, 2003 at 01:58:19AM +0200, Marcin Dalecki wrote: : Myron J. Mayfield wrote: : start it. It gives me an error saying cant find /dev/shm. I tried : adding this to /dev but was unable to. Does anyone have any : : For some unexcused reason there is the trend in Linux to represent : everything as kind of a wired half finished pseudo file system. /proc pipe : devicefs sysctl and so on... The list is really long. Even shared memmory is : mapped to ehrm a filesystem. This is expected to be mounted at : /dev/shm by the system. You can't expect FreeBSD to follow this path... : : Linux isn't the only system that does this (learn a little, criticize less). If you're talking about Plan 9 or Inferno, they at least have a history of finishing their filesystems and understanding why it's done that way. If Linux attempts to copy without understanding, and doesn't complete the job, it doesn't imply that the original idea was a Bad Thing, only that the implementation sucks. -- Christopher Vance ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/shm
On Mon, 7 Jul 2003, Christopher Vance wrote: On Sun, Jul 06, 2003 at 08:14:44PM -0400, Thomas Dickey wrote: : On Mon, Jul 07, 2003 at 01:58:19AM +0200, Marcin Dalecki wrote: : Myron J. Mayfield wrote: : start it. It gives me an error saying cant find /dev/shm. I tried : adding this to /dev but was unable to. Does anyone have any : : For some unexcused reason there is the trend in Linux to represent : everything as kind of a wired half finished pseudo file system. /proc pipe : devicefs sysctl and so on... The list is really long. Even shared memmory is : mapped to ehrm a filesystem. This is expected to be mounted at : /dev/shm by the system. You can't expect FreeBSD to follow this path... : : Linux isn't the only system that does this (learn a little, criticize less). If you're talking about Plan 9 or Inferno, they at least have a history of finishing their filesystems and understanding why it's done that way. If Linux attempts to copy without understanding, and doesn't complete the job, it doesn't imply that the original idea was a Bad Thing, only that the implementation sucks. Better, apparently to copy (not actually), rather than to whine in the background... Still - your response is equally ignorant (Plan 9 is well known - even to students), since it offers no useful information. The /proc stuff is used in real Unix's such as Solaris. Just checking, I see that FreeBSD implements procfs, which is along the same lines. (still waiting for FreeBSD to complete a sysinstall program that doesn't look as if it was an assignment for high-school interns). -- T.E.Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/shm
Thomas Dickey wrote: On Mon, Jul 07, 2003 at 01:58:19AM +0200, Marcin Dalecki wrote: Myron J. Mayfield wrote: I attempted to install the linux java sapgui on FreeBSD 5.0, but the jar file only unpacked part of it. I then copied the files from my Redhat 9 machine. I linked up all the linux libraries needed and attempted to start it. It gives me an error saying cant find /dev/shm. I tried adding this to /dev but was unable to. Does anyone have any information? Thank you. I am somewhat new to FreeBSD but have used linux for Many years. For some unexcused reason there is the trend in Linux to represent everything as kind of a wired half finished pseudo file system. /proc pipe devicefs sysctl and so on... The list is really long. Even shared memmory is mapped to ehrm a filesystem. This is expected to be mounted at /dev/shm by the system. You can't expect FreeBSD to follow this path... Linux isn't the only system that does this (learn a little, criticize less). There is a great span between everything and some things where it makes sense. Just please compare the devfs *implementations* between FreeBSD and Linux to see the difference. Some examples: /etc/rc.d/init.d# cat /proc/meminfo total:used:free: shared: buffers: cached: Mem: 526184448 515764224 104202240 43528192 353251328 Swap: 5368627200 536862720 MemTotal: 513852 kB MemFree: 10176 kB MemShared: 0 kB Buffers: 42508 kB Cached: 344972 kB SwapCached: 0 kB Active: 332328 kB ActiveAnon: 79088 kB ActiveCache:253240 kB Inact_dirty: 8932 kB Inact_laundry: 0 kB Inact_clean:125308 kB Inact_target:93312 kB HighTotal: 0 kB HighFree:0 kB LowTotal: 513852 kB LowFree: 10176 kB SwapTotal: 524280 kB SwapFree: 524280 kB /etc/rc.d/init.d# Wonderfull well tought out conscise and dense design isn't it? Or maybe: /etc/rc.d/init.d# cat /proc/filesystems nodev rootfs nodev bdev nodev proc nodev sockfs nodev tmpfs nodev shm nodev pipefs ext2 nodev ramfs iso9660 nodev devpts ext3 nodev usbdevfs nodev usbfs nodev binfmt_misc /etc/rc.d/init.d# And this is 2.4 kernel not the upcomming 2.6 Oh and I know well about the motivation behing /dev/shm - the excuse is called POSIX shm semantics. Which are broken in first place and never got over the standard draft state. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/shm
Thomas E. Dickey wrote: The /proc stuff is used in real Unix's such as Solaris. Just checking, I see that FreeBSD implements procfs, which is along the same lines. There isn't much either Solaris /proc or FresBSD /proc have in common with what Linux calls /proc. And finally on my FreeBSD box - kozaczek# mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) kozaczek# top And top doesn't eat tons of CPU time there like it does on Linux. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Current kernel not compiling
I'm trying to 'make buildworld' then 'make buildkernel' from 5.1-RELEASE against today's current. I'm getting a missing P_THREADED symbol in kern_synch.c in the make buildkernel step. UPDATING is silent on this. Is there an easy workaround? Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
mergemaster broken
mergemaster broken in today's current like this: mergemaster -dv [snip] cd /usr/src/etc/sendmail; make distribution install -o root -g wheel -m 644 /usr/src/etc/sendmail/freebsd.mc freebsd.cf /var/tmp/temproot.0707.11.55/etc/mail install: freebsd.cf: No such file or directory *** Error code 71 Stop in /usr/src/etc/sendmail. *** Error code 1 Stop in /usr/src/etc. *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the temproot environment -- Shin-ichi YOSHIMOTO [EMAIL PROTECTED] http://diary.waishi.jp/~yosimoto/diary/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mergemaster broken
mergemaster -dv [snip] cd /usr/src/etc/sendmail; make distribution install -o root -g wheel -m 644 /usr/src/etc/sendmail/freebsd.mc freebsd.cf /var/tmp/temproot.0707.11.55/etc/mail install: freebsd.cf: No such file or directory *** Error code 71 Thanks, I just committed a fix for this. ---BeginMessage--- gshapiro2003/07/06 20:19:46 PDT FreeBSD src repository Modified files: etc/sendmail Makefile Log: Put back install/distribution dependency on the buildable .cf files to get mergemaster working again. Noticed by: Shin-ichi YOSHIMOTO [EMAIL PROTECTED] Revision ChangesPath 1.25 +1 -1 src/etc/sendmail/Makefile ---End Message--- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [current] hostap+wi
In message: [EMAIL PROTECTED] Ruslan Ermilov [EMAIL PROTECTED] writes: : Uh sorry, it was very late in the night here; of course I meant Lucent : chipsets when asking if they also support host-ap mode. What are : these add-ins you're talking about? The add-ins that I'm talking about are what is known as a tertiary firmware. This firmware is downloaded by the 'host' into the card so that it can do the ap functionality. There's an authentication api to the host, but I only know about it in general terms : I'm mostly interested in the bridge(4) functionality. OK. Keep in mind that 802.11 isn't the same as 802.3 ethernet. There are a number of different things that need to happen for devices to work as well as special tags that bridging woul dneed to work. This is basically the hostap functionality. : As I understand, to do briding, the card should be able to send : frames with arbitrary MAC addresses, and when not in host-ap mode, : Lucent based chipsets do not allow this (i.e., you see with : tcpdump(1) that packets is written to wi0 interface, but the other : end doesn't receive the frame). Some versions of lucent firmware support these sorts of things, in addition to receiving all packets off the air, but most versions do not. I think that the receive all packets was the only one available in public firmware, and then only a few select versions. : What surprises me here, is that : these same cards appear to work (by forwarding arbitrary Ethernet : frames) when inserted into Lucent-based APs. Does anyone have a : valid explanation to this? Is this an artificial limitation on : these cards to limit their commercial use, or am I missing an : obvious? The reason they work when inserted into AP is due to the tertiary firmware that I alluded to above... Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3COM ep0 pccard device broken in current.
In message: [EMAIL PROTECTED] Mark Murray [EMAIL PROTECTED] writes: : Reverting pccbb.c to 1.75 fixed this for me. Then the fixes to if_ep are still insufficient... Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
