Re: ATA? related trouble with r300299
As Oleg mentioned, that was due to the compatibility shims for the old ATA layer getting removed. The only thing required to get those machines to boot would be to change /dev/ad* in /boot/loader.conf to the correct /dev/ada device. Ken — Ken Merry k...@freebsd.org > On May 24, 2016, at 12:42 AM, Olli Hauer wrote: > > Not sure, but maybe related. > I had 5 old ata systems running, doing ntp and dns cache (running since 5.0 > lifted over time to 10.x) The systems showed no smart or any other defects. > Last year they began stop working with strange messages like adaX not found > where in fstab still was ataX (back from 5.x) ... > Meanwhile the systems are replaced and thrown away. > If from interest i can look for old logs. > > > On 23/05/2016, 21:25 "Kenneth D. Merry" wrote: > On Sat, May 21, 2016 at 09:30:35 +0300, Oleg V. Nauman wrote: > > > > I have faced the issue with fresh CURRENT stopped to boot on my old desktop > > after update to r300299 > > Verbose boot shows the endless cycle of > > > > ata2: SATA reset: ports status=0x05 > > ata2: reset tp1 mask=03 ostat0=50 ostat1=50 > > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 > > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00 > > ata2: reset tp2 stat0=50 stat1=50 devices=0x3 > > messages logged to console. > > > > Below is the relevant portion of ATA controller/devices probed/attached > > during > > the boot: > > > > atapci0: port > > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 > > ata0: at channel 0 on atapci0 > > atapci1: port 0xd080-0xd087, 0xd000-0xd003, > > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on pci0 > > ata2: at channel 0 on atapci1 > > ata3: at channel 1 on atapci1 > > ada0 at ata2 bus 0 scbus1 target 0 lun 0 > > ada0: ATA-7 SATA 2.x device > > ada1 at ata2 bus 0 scbus1 target 1 lun 0 > > ada1: ATA8-ACS SATA 3.x device > > cd0 at ata0 bus 0 scbus0 target 0 lun 0 > > cd0: <_NEC DVD_RW ND-3570A 1.11> Removable CD-ROM SCSI device > > I'm not entirely sure what is causing the problem with your system, but > hopefully we can narrow it down a bit. > > There is a bug that came in with my SMR changes in revision 300207 that > broke the quirk functionality in the ada(4) driver. I don't think that is > the problem you're seeing, though. > > Can you try out this patch: > > https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt > <https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt> > > In /boot/loader.conf, put the following: > > kern.cam.ada.0.quirks="0x04" > kern.cam.ada.1.quirks="0x04" > > If you're able to boot with those quirk entries in the loader.conf, try > taking one of them out, and reboot. If that works, try taking the other > one out and reboot. > > What I'm trying to figure out here is where the problem lies: > > 1. The bug with the ada(4) driver (in where it loaded the quirks). > 2. The extra probe steps in the ada(4) driver might be causing a problem > with ada0 (Samsung drive). > 3. The extra probe steps in the ada(4) driver might be causing a problem > with ada1 (Seagate drive). > 4. Something else. > > So, if you can try the patch and try to eliminate a few possibilities, we > may be able to narrow it down. > > Thanks, > > Ken > -- > Kenneth Merry > k...@freebsd.org > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > <https://lists.freebsd.org/mailman/listinfo/freebsd-current> > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: please add auditdistd user/group to -stable and the 9.1-release?
On Mon, 2012-12-03 at 08:36 +, Robert N. M. Watson wrote:
> My intuition (hope) is that 9.1 is past the point of no return on
> builds and so that boat has been missed; however, my plan is to MFC
> the auditdistd user to stable/8 and stable/9 after the 3-day MFC
> timeout. If Ken thinks builds have yet to start on the final 9.1
> image, however, then I'm happy to merge to there as well.
Sorry but your hope is correct - it (just...) missed the boat for 9.1.
--
Ken Smith
- From there to here, from here to | kensm...@buffalo.edu
there, funny things are everywhere. |
- Theodor Geisel |
signature.asc
Description: This is a digitally signed message part
Re: link_elf_obj: symbol vm_page_lock_queues undefined
Thank you, Alan. I temporary commented out vm_page_lock_queues()/vm_page_unlock_queues() in "src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c". So far, it works!! We need to wait for official fix, but just to report that it enabled to run. Regards, ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Q) KLDload error
Gee,,, It sounds not so easy as multiple queues indicates, but I hope that it is fixed soon... From: Lucas James > > Ahh, I see. After little more digging it would appear that alc@ removed > vm_page_lock_queues in r242941, as he replaced them with multiple > queues. Unfortunately this means VirtualBox will not be able to be run. > > I suggest submitting a PR. > > regards, > Lucas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Q) KLDload error
From: Lucas James > > You will need to rebuild and install the virtualbox-ose-kmod port. > > > regards, > Lucas Yes, I did and yet I have the following error with "kldload vboxdrv". Is "vm_page_lock_queues" renamed? It is in "./work/VirtualBox-4.1.22/src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c" # tail -f /var/log/messages :: : Nov 17 10:53:17 t3 pkg: virtualbox-ose-kmod-4.1.22 installed Nov 17 10:53:55 t3 kernel: link_elf_obj: symbol vm_page_lock_queues undefined Nov 17 10:53:55 t3 kernel: linker_load_file: Unsupported file type :: : ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Q) KLDload error
From: "Steven Hartland" > sounds like your kernel and world may be out of sync? No, I always DO "make buildworld && make installworld && make buildkernel && make installkernel". And I do not think they are not sync'd. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Q) KLDload error
I have the following error at booting with current kernel. Were there any changes? Any fixed? I need to run virtualbox. Nov 17 08:32:34 t3 kernel: FreeBSD 10.0-CURRENT #12 r243164M: Sat Nov 17 08:24:30 JST 2012 Nov 17 08:32:34 t3 kernel: k...@tyd3.sub.tydfam.jp:/usr/obj/usr/head/sys/TYD3 amd64 Nov 17 08:32:34 t3 kernel: link_elf_obj: symbol vm_page_lock_queues undefined Nov 17 08:32:34 t3 kernel: KLD file vboxdrv.ko - could not finalize loading Nov 17 08:32:34 t3 kernel: CPU: Intel(R) Core(TM) i7-3960X CPU @ 3.30GHz (3309.94-MHz K8-class CPU) Nov 17 08:32:34 t3 kernel: Origin = "GenuineIntel" Id = 0x206d7 Family = 0x6 Model = 0x2d Stepping = 7 Nov 17 08:32:34 t3 kernel: Features=0xbfebfbff Nov 17 08:32:34 t3 kernel: Features2=0x1fbee3bf Nov 17 08:32:34 t3 kernel: AMD Features=0x2c100800 Nov 17 08:32:34 t3 kernel: AMD Features2=0x1 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FYI: 9.0-RELEASE announced...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
JFYI for those of you who aren't subscribed to the announce@ mailing
list... 9.0-RELEASE is, finally, announced. The announcement message
is available here:
http://www.freebsd.org/releases/9.0R/announce.html
Lots of you noticed that the 9.0-RELEASE ISO and memstick images
appeared on the FTP sites a while ago. But as pointed out this
release turned out to be an example of why the "official policy" is
that it's not truly released until the announcement email gets sent
out. I had not tested using sysinstall(8) to install pre-built
packages from the DVD during my initial testing since we're sorta
moving away from sysinstall(8). I had just tested installing the
pre-built packages using pkg_add(8). Someone noticed sysinstall(8)
misbehaved before I got the images put up on Bittorrent and the
fix was simply adding one file to the DVD image that the new build
infrastructure omitted since bsdinstall(8) doesn't use it. So I
went ahead with replacing the DVD images on the FTP site. That's
also why we waited longer than normal between the images appearing
on the FTP sites and the announcement - we gave extra time to try
and make sure the updated images got to all the FTP mirrors. Sorry
about the screw-up.
If you downloaded the amd64 and/or i386 DVD images before now you
might want to check the checksums with the ones posted in the
release announcement. The fix to make sysinstall(8) happy about
installing from the DVD images was the *only* change made to the
updated images. The "bad" images were never available via
Bittorrent so if you got the images that way you wouldn't have
a bad image.
On behalf of the Release Engineering Team and the FreeBSD Developers
we hope you enjoy 9.0-RELEASE.
- --
Ken Smith
- - From there to here, from here to | kensm...@buffalo.edu
there, funny things are everywhere. |
- Theodor Geisel |
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8PcpsACgkQ/G14VSmup/aLFgCfar7x43ViPu44M3eF8MzvYhOU
/z0AnRN1jXDT1fS0UA9J0Trd5sRQcwdy
=oU1m
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: stable/9 still looking for packages at 9-current
On Fri, 2012-01-06 at 07:16 -0700, Peter wrote:
> Not for stable/9 [__FreeBSD_version 900500+:
Sorry for the delay cleaning that up. It should be fixed as of
r229748.
--
Ken Smith
- From there to here, from here to | kensm...@buffalo.edu
there, funny things are everywhere. |
- Theodor Geisel |
signature.asc
Description: This is a digitally signed message part
FreeBSD 9.0-RC3 Available...
7ce MD5 (FreeBSD-9.0-RC3-ia64-bootonly.iso) = 7a8e99a61d21ae8a5f6be9fb7f878b11 MD5 (FreeBSD-9.0-RC3-ia64-memstick) = 5484765d3373c59372cdb53bbea2ab2d MD5 (FreeBSD-9.0-RC3-ia64-release.iso) = 7791f810dbe7d1ee7cf30510f0981424 MD5 (FreeBSD-9.0-RC3-powerpc-bootonly.iso) = 97a947ccd413371e24cfc83971bfd83a MD5 (FreeBSD-9.0-RC3-powerpc-memstick) = 2ebbdb2379d1f0e1a24a5ac31f22cf6f MD5 (FreeBSD-9.0-RC3-powerpc-release.iso) = e6c38096826b015eaa63a8109b809250 MD5 (FreeBSD-9.0-RC3-powerpc64-bootonly.iso) = 360383e1d7fca3d93be73f5aa8ce085c MD5 (FreeBSD-9.0-RC3-powerpc64-memstick) = 4b74c2d73b56f5f38590b0da2cf64054 MD5 (FreeBSD-9.0-RC3-powerpc64-release.iso) = 3e6e9519b3debb61047491ee700f683b MD5 (FreeBSD-9.0-RC3-sparc64-bootonly.iso) = 8f352714c2c4228623239491aee88e6a MD5 (FreeBSD-9.0-RC3-sparc64-disc1.iso) = b51648c80862f54d230cf13b4a34604b SHA256 (FreeBSD-9.0-RC3-amd64-bootonly.iso) = 06d609bb0d927b64221f1207542794870b56538fd3983355c9013d1f17fe7382 SHA256 (FreeBSD-9.0-RC3-amd64-disc1.iso) = 16792eb1e90070b8c5d1ea8df55b290534efba1543fb37950f8c7acd61839208 SHA256 (FreeBSD-9.0-RC3-amd64-memstick.img) = ae533e43e2390c5992c83acebfee35636baaa0694b7f1bae973fd4547a4e97ee SHA256 (FreeBSD-9.0-RC3-i386-bootonly.iso) = 88f417817eec36e183fdb832720664956486ac169fb5528e93423e4ccd52ba61 SHA256 (FreeBSD-9.0-RC3-i386-disc1.iso) = cdbf1ce5668444c88ea141bfaec0bd414c09b39969076915d2d9257c9f0802f2 SHA256 (FreeBSD-9.0-RC3-i386-memstick.img) = ea6e4ce993bc534a05d247bd65ccf2a41e5e12cd36c75ca2a2dfdf0d77e996b5 SHA256 (FreeBSD-9.0-RC3-ia64-bootonly.iso) = cebb6bacde53bc4bc69f9048447107c38f69d6c655fcc5a7778dcae8c7387dc1 SHA256 (FreeBSD-9.0-RC3-ia64-memstick) = 46960b6567e3dcfea65dbeef107573f5147f2ec74d555d0aae19a81629cb2434 SHA256 (FreeBSD-9.0-RC3-ia64-release.iso) = a484ac6ac87e9a9c524cde453838a15aebffcc6b5811dbaf85b3b37691cea149 SHA256 (FreeBSD-9.0-RC3-powerpc-bootonly.iso) = a2a98542d9668b18ef10b85d0e10026e15e9c6991bc09d9fa070e6eed34a93bb SHA256 (FreeBSD-9.0-RC3-powerpc-memstick) = 0320db4828122ef851e1a26f28bd1eccf1b4e45d476fe23ec627c2daa559220b SHA256 (FreeBSD-9.0-RC3-powerpc-release.iso) = ee480650db05998560f26016bfcf2c392da8a3eae94bec49a162f9f655aaa3f9 SHA256 (FreeBSD-9.0-RC3-powerpc64-bootonly.iso) = 7bd60e65929fd70133a21f8517715b22d992a45a29c2677e4c7a66a226bc492a SHA256 (FreeBSD-9.0-RC3-powerpc64-memstick) = 3fab51275ddf71016d9422c6bfb0806c51b0243d79f9f5011f9f2f78a631a607 SHA256 (FreeBSD-9.0-RC3-powerpc64-release.iso) = d48ec66421b9f74b8c11212a6b9d5240b20629e0685e0ee3485233e28eb3cfcd SHA256 (FreeBSD-9.0-RC3-sparc64-bootonly.iso) = 739a9430198b91cac1d625bcde202447fc47addc92430a72080dce224c3b5c67 SHA256 (FreeBSD-9.0-RC3-sparc64-disc1.iso) = 18a63e0cb420694172f49f7ad5a209d40f348b19d3c96e8ecaeef8517b52cc22 -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
FreeBSD 9.0-RC2 Available...
release.iso) = c1f5623734132ea80a9fa2298262884c MD5 (FreeBSD-9.0-RC2-powerpc-bootonly.iso) = 35e667deaa7223e0829677c3762163d8 MD5 (FreeBSD-9.0-RC2-powerpc-memstick) = 01b06227124fc7f9ad224d0512940ea8 MD5 (FreeBSD-9.0-RC2-powerpc-release.iso) = 055e06744fa1b8c584cfda8be2352462 MD5 (FreeBSD-9.0-RC2-powerpc64-bootonly.iso) = 38d240e6cdfd5f986f0690ba1256eb0f MD5 (FreeBSD-9.0-RC2-powerpc64-memstick) = b820ed78bce87b69a04e9d473c63ecfc MD5 (FreeBSD-9.0-RC2-powerpc64-release.iso) = 44d550342db5090c1d0fb5f60705cb0c MD5 (FreeBSD-9.0-RC2-sparc64-bootonly.iso) = 7ffb3dc55bb02506cbc95d0f7a94edab MD5 (FreeBSD-9.0-RC2-sparc64-dvd1.iso) = fe4b87eff3f3cde33c2908b071e45c0f SHA256 (FreeBSD-9.0-RC2-amd64-bootonly.iso) = 81daa3aa92b8eb6f1bf0c6196c1cae138c881fe53dce22b9fbf2f19a8cf30551 SHA256 (FreeBSD-9.0-RC2-amd64-memstick.img) = fda9025bb8c3ee8c3a4f8db3a0144c669408707eab3dc7c5e2070342e979e33e SHA256 (FreeBSD-9.0-RC2-amd64-dvd1.iso) = d7071da7cf440f79a7368f8a8b26ba9b6e18dcb3785aec83df866ddf576ef418 SHA256 (FreeBSD-9.0-RC2-i386-bootonly.iso) = 200ac2b9e950548c873cba93f3b3c669e529720522897220d6b6dd438f806490 SHA256 (FreeBSD-9.0-RC2-i386-memstick.img) = 7888f9ed58da415a7356810c07768587c6d2b5d4734f9ca47c92bfc10dab1b0a SHA256 (FreeBSD-9.0-RC2-i386-dvd1.iso) = 41a1e12496ba5a44dba4c6e6cfb27c6dd5f49fb62378e05c1a61909a4f29d06c SHA256 (FreeBSD-9.0-RC2-ia64-bootonly.iso) = 059a05b4e779f94cb221fcb7ce261db13e45092510b1fbeac7e17d5f2f6c7c36 SHA256 (FreeBSD-9.0-RC2-ia64-memstick) = 3e9985eb02c0f8cd8e5d84356048a019c98d9628e5836ca777426a3abec3f83f SHA256 (FreeBSD-9.0-RC2-ia64-release.iso) = 49524a249f72ad6a8a21ba1ad0d1e738ddc09342c7086cf1a20c08ad06885539 SHA256 (FreeBSD-9.0-RC2-powerpc-bootonly.iso) = 3a584930ecfd772defa3d86879c62199b7a15f6e502bf4809a04a3fc8d10e10e SHA256 (FreeBSD-9.0-RC2-powerpc-memstick) = 06b2985c278362801e2c454d72a3ae0f873ad2e050a058e76f7b6da84f2d4812 SHA256 (FreeBSD-9.0-RC2-powerpc-release.iso) = 0402cca90eb4123fbf1d5dc46d9a36ba08b38c0e7b5e83a3a5c0cd7cd1095124 SHA256 (FreeBSD-9.0-RC2-powerpc64-bootonly.iso) = 7510745f1fbd3f1a4e1d7c9d0fed39f8ea3e2dc37de029e931f06856729e5183 SHA256 (FreeBSD-9.0-RC2-powerpc64-memstick) = a29bf56f7461be20b0fd15e6ff7ed08ea0a2baabcbf04430d337893113d19a68 SHA256 (FreeBSD-9.0-RC2-powerpc64-release.iso) = 54b1e14798839ced94863a5fb95b08c20a46474854effc022602cad018789b98 SHA256 (FreeBSD-9.0-RC2-sparc64-bootonly.iso) = 9e08825e9549d330384817296d832f9e00288357ccd1b2d6cce99d0f656b096b SHA256 (FreeBSD-9.0-RC2-sparc64-dvd1.iso) = f53810ff78e4015833e0ac9e81865c1abd93c622607d14aa2a74b918d2bc469c -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 9.0-RC1 Available...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/23/11 2:20 PM, Andrey Fesenko wrote: > On Sun, Oct 23, 2011 at 7:43 AM, Ken Smith > wrote: >> >> The 9.0-RELEASE cycle will be tracked here: >> >> http://wiki.freebsd.org/Releng/9.0-TODO >> > > link error, need http://wiki.freebsd.org/Releng/9.0TODO Correct, sorry about the hyphen sneaking in. > still no actual information on this page. Branch status not > actual. I updated the dates. If by "Branch Status" you're referring to the section with that title it is actual. We've created stable/9 but not releng/9.0 yet. That might come with RC2, sorta depends on how much people find wrong with RC1. When releng/9.0 gets created it will take one commit and two merges to get fixes into 9.0-RELEASE which is a bit of a pain if there is a lot of activity. - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6kZMQACgkQ/G14VSmup/amiACgj1mmb1TG+39IlZzQzFRTIcKi mGYAn2kdMJ5A8HEK6wBhE2RgrQmRKLzr =/j9J -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD 9.0-RC1 Available...
9.0-RC1-ia64-memstick) = 997bb23954682d503ba10fc3f1a2d624 MD5 (FreeBSD-9.0-RC1-ia64-release.iso) = 3703dc72d55fb9c66450e800b123cffe MD5 (FreeBSD-9.0-RC1-powerpc-bootonly.iso) = 2a651f4af37af85e49b6a8fcaa42a77f MD5 (FreeBSD-9.0-RC1-powerpc-memstick) = a2c33dfab3f98b0d83db382d73cdd87a MD5 (FreeBSD-9.0-RC1-powerpc-release.iso) = af4afc51149dcd61488b44ecbbf96fc5 MD5 (FreeBSD-9.0-RC1-powerpc64-bootonly.iso) = 96f2bce40f2974be55578bf9cc7318a1 MD5 (FreeBSD-9.0-RC1-powerpc64-memstick) = e4647934091f4c72b4df331eb1134eb3 MD5 (FreeBSD-9.0-RC1-powerpc64-release.iso) = b6989f2e4285b7479a72f4503dc420cf MD5 (FreeBSD-9.0-RC1-sparc64-bootonly.iso) = df7146d2497a16b502e92e35ae24921e MD5 (FreeBSD-9.0-RC1-sparc64-dvd1.iso) = 6cd56a20a6d907525077424c55a163a4 SHA256 (FreeBSD-9.0-RC1-amd64-bootonly.iso) = ec44fefd1c54fb724079b83951cfe721404ecb76a4a861a2ef4c2a1b63b88aff SHA256 (FreeBSD-9.0-RC1-amd64-dvd1.iso) = 6558689957ce2a48f3aa235ab11cd4613db7afe11f102b0ae5d566b22e30c132 SHA256 (FreeBSD-9.0-RC1-amd64-memstick.img) = c04abe37f83c8ed07e3645cbaff8cfa21d223f94cda059a053bd1a469c6b753c SHA256 (FreeBSD-9.0-RC1-i386-bootonly.iso) = 9e720cb8306171b137ae50d3887abf09f90fab6f953b39a9f552c87c3221d441 SHA256 (FreeBSD-9.0-RC1-i386-dvd1.iso) = 488599d5328b20278e90d5489b8d2afd49bf466a5d7a31694f3c0eb66d97c6f1 SHA256 (FreeBSD-9.0-RC1-i386-memstick.img) = 9eadded30ee684840bb6ead60f98d8d8e455e690148491b55dec9b657ab7ac10 SHA256 (FreeBSD-9.0-RC1-ia64-bootonly.iso) = b4b33ecc30555b532be4ebcc3a5f566189265066141b852a3a912ddc8e1aa203 SHA256 (FreeBSD-9.0-RC1-ia64-memstick) = f437f5af4c8dd780d329bb90f5189c7bb1b270df1b05bff979e7fbcc7cf819d6 SHA256 (FreeBSD-9.0-RC1-ia64-release.iso) = aaa21f0244d1238b11f5af267935c7cbea20f0d5fb393bef7534011ab7f017f1 SHA256 (FreeBSD-9.0-RC1-powerpc-bootonly.iso) = 5a45de1a72fd2c15f58c7306802533d48a5dee512b5e6f0377e859bf4a25200e SHA256 (FreeBSD-9.0-RC1-powerpc-memstick) = fe85b8232123a510468658380117e51a2ca3737e92cacb525717cefb73b9740c SHA256 (FreeBSD-9.0-RC1-powerpc-release.iso) = 8024a84ccf4962fe8ec7e030421a476f96c410fe67c9c9b25935248304029682 SHA256 (FreeBSD-9.0-RC1-powerpc64-bootonly.iso) = 43e97f229ccf823378078348390b6b75b3ca5c95db107a48087d6a5fc3980e92 SHA256 (FreeBSD-9.0-RC1-powerpc64-memstick) = 7323eb46e90849bab53c3b158753b1824ae9e464c63ffe7bb33fe726c6a7c415 SHA256 (FreeBSD-9.0-RC1-powerpc64-release.iso) = 6c0643f2de33a04426d168dd23187a71c971d3e4bfd222eb32bdbaa65f2c0368 SHA256 (FreeBSD-9.0-RC1-sparc64-bootonly.iso) = 8664ed9a0282b80341c6e243643011c84b058f4c8450a5e6e2b3f99bd9df469c SHA256 (FreeBSD-9.0-RC1-sparc64-dvd1.iso) = 5220f817e078024208b9ab3060518911c4e0ed0693575ca101a97608b73121af -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 9.0-BETA3 Available...
On Wed, 2011-10-12 at 14:39 +0100, Bruce Cran wrote: > On 29/09/2011 02:42, Ken Smith wrote: > > MD5 (FreeBSD-9.0-BETA3-amd64-bootonly.iso) = > > 2ce7b93d28fd7ff37965893f1af3f7fc > > MD5 (FreeBSD-9.0-BETA3-amd64-dvd1.iso) = 4affc701f2052edc548274f090e49235 > > MD5 (FreeBSD-9.0-BETA3-amd64-memstick.img) = > > e260f2f2122326cb9a93ac83eb006c1c > > The -dvd1.iso files seem to be less than a CD, at 610MB. Are they > expected to contain more data over time, or could 'dvd' be removed? > I was planning on them having package sets. The new installer doesn't support installing packages like sysinstall had but if I provide Gnome, KDE, and perhaps a small set of other stuff it would be useful to people with crummy network connectivity. They could install the packages from the DVD instead of needing to have everything downloaded. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 9.0-BETA3 Available...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/4/11 3:39 PM, Arnaud Lacombe wrote: > you've got to be fraking kidding me, aren't you ? > > Code freeze has happened, no date set. BETA-1, BETA-2 have been > released, no date set. stable/9 has been created, no date set. > Branch status has not been updated. I'll get to more of it later tonight. > At most, this edit is a bad joke, just like politician announcing > a few millions dollars in saving when the yearly budget is in > deficit by trillions... Or an edit done in the 5 minutes I had at the time so people who wanted to know the times of things that haven't happened already can get what they want to know. > For the record, I would have made a much better job, if you had let > me. I'd love to know what you would have put for the dates I filled in. - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6LY4IACgkQ/G14VSmup/btJACaAr3xKoUNxkMpNt6YEhV+hPDo wzUAn3cv3sHsMwZRiPcZ5yRN917IJYR5 =j4kk -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD 9.0-BETA3 Available...
On Tue, 2011-10-04 at 22:40 +0400, Andrey Fesenko wrote: > On Thu, Sep 29, 2011 at 5:42 AM, Ken Smith wrote: > > > > > > The 9.0-RELEASE cycle will be tracked here: > > > >http://wiki.freebsd.org/Releng/9.0TODO > > > > though the schedule listed there is still way off. We'll re-work the > > schedule some time soon. > > > > Last updated: 16 August 2011. :( > Hit refresh... -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: FreeBSD 9.0-BETA3 Available...
On Wed, 2011-09-28 at 21:42 -0400, Ken Smith wrote:
> If you would like to use csup/cvsup mechanisms to access the source
> tree the branch tag to use is now "RELENG_8", if you use "." (head)
> you will get 10-CURRENT.
Sigh. Sorry. It's late...
RELENG_9...
--
Ken Smith
- From there to here, from here to | kensm...@buffalo.edu
there, funny things are everywhere. |
- Theodor Geisel |
signature.asc
Description: This is a digitally signed message part
FreeBSD 9.0-BETA3 Available...
595ef753108886e092ba1efd88dfb24ebdbfc
SHA256 (FreeBSD-9.0-BETA3-sparc64-bootonly.iso) =
6eddeb18514d063d809e5b675413de43b6aa72815ebbe9f72fe548507f1e03cd
SHA256 (FreeBSD-9.0-BETA3-sparc64-dvd1.iso) =
8b56423ed00cf9902366eeb7fd51bf13f8702af51a8c031fbf295f68ca5df484
--
Ken Smith
- From there to here, from here to | kensm...@buffalo.edu
there, funny things are everywhere. |
- Theodor Geisel |
signature.asc
Description: This is a digitally signed message part
FreeBSD 9.0-BETA2 Available...
8ba04407cd8eea89f76 SHA256 (FreeBSD-9.0-BETA2-amd64-dvd1.iso) = e4fa69243aeefcfbce98ac8c30a8120a33ff122e7eb8c5fd73c23d49e3b2fad5 SHA256 (FreeBSD-9.0-BETA2-amd64-memstick.img) = ac5e08a1a7ed4e6e8f19c18fcd53306e9ab5b4636c1b390e7fccf271e2ffbbcc SHA256 (FreeBSD-9.0-BETA2-i386-bootonly.iso) = e31ca81caa14866c2f3eb837b346f1b853ddb9181a9aa7b8d45915a0ebebbfd1 SHA256 (FreeBSD-9.0-BETA2-i386-dvd1.iso) = 2ed439c308c874deb17f20682fa3d24ab64452912a1408d1b8c4220c29ef2728 SHA256 (FreeBSD-9.0-BETA2-i386-memstick.img) = bb8d8151863784c4147ba4e62f073fcdd4c9b194b55470d3133f7504c2bad5c6 SHA256 (FreeBSD-9.0-BETA2-powerpc-bootonly.iso) = 64d7fc1b97a00118b577103d9882f14b98523716c24d01c6498cce5b8b555154 SHA256 (FreeBSD-9.0-BETA2-powerpc-memstick) = 0fd99234ad81687d90f9cbffb375bf938444ca41e5f090d0c1cf86ce5b373422 SHA256 (FreeBSD-9.0-BETA2-powerpc-release.iso) = fbe44a2665f68f45c86e8f99a5e569ed5f9905e38c6f516472bac58e8e742be6 SHA256 (FreeBSD-9.0-BETA2-powerpc64-bootonly.iso) = e8ab1ece6460080951dfb7bac9de9e80703b0ccf7f684e8be82fd5a32405b093 SHA256 (FreeBSD-9.0-BETA2-powerpc64-memstick) = f9778f2c8d85709e027ceaf9d8b1c99cae8719bee0a363a29b0e97594a6b6b85 SHA256 (FreeBSD-9.0-BETA2-powerpc64-release.iso) = 92a754150b17eb8567fa3b9dd306dbb96f2476075ab646ba90840aa733364b7c SHA256 (FreeBSD-9.0-BETA2-sparc64-bootonly.iso) = 0ef5b1b41683bfa9047bbd556a81466ed5aa4609335380d611e63ad2d8517f51 SHA256 (FreeBSD-9.0-BETA2-sparc64-dvd1.iso) = 00477eaf46f93678a28878d87c4551f529915266aee96cbb7141445503efce8d -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
Re: x11/nvidia-driver / Compilation has failed
Could I test your patch for nvidia-driver, too? I cannot find your patch in this mail. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD 9.0-BETA1 Available...
SHA256 (FreeBSD-9.0-BETA1-powerpc64-bootonly.iso) =
7e4a8a24cd94d4fce60294d444525d9aea6c8d3e0ee55e6a9dda84a5ee9f
SHA256 (FreeBSD-9.0-BETA1-powerpc64-memstick) =
ec7eb9d6f5a69a0f3fbafd433ac309dcafd411921c4c51f2886c39649d59ca07
SHA256 (FreeBSD-9.0-BETA1-powerpc64-release.iso) =
2721be511db390a95ddf3081afd8152be14f147d5d8a8213c4045875631950e7
SHA256 (FreeBSD-9.0-BETA1-sparc64-bootonly.iso) =
3db8cf663cd1722488277c5c63f8daa2cd04a1e1aeb8bd54932cbc30d507bc3e
SHA256 (FreeBSD-9.0-BETA1-sparc64-disc1.iso) =
c051b5b9fad2e3183c595b3e7f786afb181bce91c7ce1c869a2c593ab9d29205
--
Ken Smith
- From there to here, from here to | kensm...@buffalo.edu
there, funny things are everywhere. |
- Theodor Geisel |
signature.asc
Description: This is a digitally signed message part
Re: snapshot images
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/16/10 8:35 PM, Phil Oleson wrote: > I just noticed that the memstick.img is not available in the > snapshots directories. > I'm just curious why they are not automatically built. Were they hand > built for the release? They were hand built for the 8.0-RELEASE. Why they were, and at least for now will continue to be, is mostly related to the setup of how the iso's themselves are built. Basically it's a two-step process. The first step builds everything that's needed to generate the iso's from a set of directory trees (disc1, disc2, disc3, bootonly, livefs, and dvd1) and stops there. At that point the packages directory appropriate for each of the iso images gets added to the proper directory, and the second step gets run to build the iso's. I decided to not add yet another directory tree named "memstick" because for the forseeable future the memstick image will just be what's on the DVD as far as everything but the packages is concerned, and for packages it will just be the documentation packages and no others. So in between the first and second steps of the normal release build I "borrow" the dvd1 directory tree (placing just the doc packages in it temporarily) to generate the memstick image before putting the packages used to generate the dvd iso image in place and running the second step of the release build. > Is there any way it can be included with the snapshots iso's? Yes, I'll be including memstick images with the 201002 snapshot which are in the works now. And I'm using this to convert what I had been doing manually into a script that should land in src/release/scripts some time in the not too distant future. If what we distribute for the memstick image isn't quite what you want you should be able to use this script to build what you do want... - -- Ken Smith - - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodore Geisel | -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkt7ad0ACgkQ/G14VSmup/bqngCePSu6cd7xrP/ievJ55ltUqNqd PBEAn1pNra54nPJuNEYsyEJ9EzirzPuV =yH4n -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Help request: problems with a 5.1 server and large numbers of ssh users.
On Thu, Nov 20, 2003 at 10:56:08AM -0500, Robert Watson wrote: > Hmm. Well, it certainly sounds like a resource limit to me, especially if > it's a nice round number like "150" or "300". One possibility might be running out of pseudo-terminals to support the login sessions. pty's are created as needed I think, and the code that handles it is in sys/kern/tty_pty.c. The limits on it appear to be 256 ptys: /* * This function creates and initializes a pts/ptc pair * * pts == /dev/tty[pqrsPQRS][0123456789abcdefghijklmnopqrstuv] * ptc == /dev/pty[pqrsPQRS][0123456789abcdefghijklmnopqrstuv] * * XXX: define and add mapping of upper minor bits to allow more * than 256 ptys. */ I don't know if simply changing the : static char *names = "pqrsPQRS"; to something longer is all that would be required or if there are other factors involved. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unfortunate dynamic linking for everything
On Thu, Nov 20, 2003 at 06:27:31AM +1100, Bruce Evans wrote:
> > set init_path=/rescue/init
>
> If dynamic root were ready to be turned on, then /rescue/init would be
> in the default init_path.
I had that explained to me too. :-)
There is a loop in sys/kern/init_main.c that "probes" for an init
to run. But it only does what you want for cases of the files
not existing or otherwise just totally not executable. It won't
handle the "started but then dumped core" case the way it would
need to if /sbin/init were to fail because of shared library
problems. So if just relying on this mechanism it would either
not work right (/sbin/init in the path before /rescue/init) or
it would always start /rescue/init (/rescue/init before /sbin/init
in the path).
--
Ken Smith
- From there to here, from here to | [EMAIL PROTECTED]
there, funny things are everywhere. |
- Theodore Geisel |
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unfortunate dynamic linking for everything
On Wed, Nov 19, 2003 at 09:19:50AM -0500, Leo Bicknell wrote:
> To boot a machine into single user mode you need a kernel, init,
> and /bin/sh (minimally).
Roughly the same thing was bothering me last night. You get a chance
to specify the shell when init is in the last phase of getting you to
single-user mode so you can say /rescue/sh at that point. init is
another story and I asked someone about that, they said it either is
or will shortly be a loader option so you can override that to be
/rescue/init that way.
--
Ken Smith
- From there to here, from here to | [EMAIL PROTECTED]
there, funny things are everywhere. |
- Theodore Geisel |
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: anoncvs connection refused?
On Tue, Nov 18, 2003 at 09:48:33AM -0800, Lars Eggert wrote: > I've seen this for the last few days: > > [EMAIL PROTECTED]: /usr/src] make -DCVS_UPDATE update > -- > >>> Updating /usr/src from cvs repository > -- > cd /usr/src; cvs -R -q update -A -P -d > cvs [update aborted]: connect to > anoncvs.freebsd.org(209.181.243.20):2401 failed: Connection refused > *** Error code 1 > > Is anoncvs filtering me? No, not filtering. There was a little problem with an upgrade followed by a little trouble finding who has the keys to that particular machine room. It's being worked on. Sorry for the hassles. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: /bin and /sbin are now dynamically linked
On Mon, Nov 17, 2003 at 12:59:47PM -0800, Peter Wemm wrote:
> It is 'system' binaries. The distinction between bin and sbin (and /usr/
> bin and /usr/sbin) is that the binaries in */sbin are only really supposed
> to be useful for administrators or other priviliged users.
Yup, this distinction was in place long before shared libraries came
along but not in its current form. You can only consider yourself a
true UNIX dinosaur if at some point you changed your path to replace
"/usr/etc /etc" with "/usr/sbin /sbin". /etc was where they lived
at first.
--
Ken Smith
- From there to here, from here to | [EMAIL PROTECTED]
there, funny things are everywhere. |
- Theodore Geisel |
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tcp hostcache and ip fastforward for review
Hi Andre, Your patch applies just fine for me now on Oct 10th current sources. Everything seems to be working fine on dual processor Dell 2500 with SMP kernel. This is a network backup machine. I don't see any problems, just as fast as always and seems to be solid so far, it has only been running a few hours. I ran some network backups to this server and ssh sessions out. Thanks Ken riker# sysctl -a net.inet.tcp.hostcache.list net.inet.tcp.hostcache.list: IP addressMTU SSTRESH RTT RTTVAR BANDWIDTH CWND SENDPIPE RECVPIPE HITS UPD EXP 209.123.219.10 00 14ms 9ms 1805600 6516 0043 3600 207.99.22.1900 17ms 13ms 109840065535 0043 600 - Original Message - From: "Andre Oppermann" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, November 09, 2003 11:19 AM Subject: tcp hostcache and ip fastforward for review > Hello all, > > this patch contains three things (to be separated for committing): > > tcp_hostcache > > - removes protocol cloning from routing table (IPv4+6) > - removes rtentry pointer from inpcb and in6pcb ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: since 2 days apm / ACPI doesn't work and boot instabilities
Hi Andreas, I bet acpi isn't even running. As of a few days ago acpi is disabled as a loadable module due to some changes in progress. Try adding 'device acpi' to your kernel.conf file and rebuild/reinstall the kernel. Ken - Original Message - From: "Andreas Klemm" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 07, 2003 11:07 AM Subject: since 2 days apm / ACPI doesn't work and boot instabilities > Hi, > > wanted to let you know, that since yesterday ACPI on my > Dell Latitude D600 doesn't work anymore. > > Does anybody have an idea what this breakage might have caused ? > > About a week ago I got apm/acpi working with an unoff patch from this URL. > > http://sandcat.nl/~stijn/freebsd/dell.php > > I didn't changed anything in: > /etc/rc.conf > /boot/loader.conf > and nothing in the kernel config file. > > I only did a "make world" as well as a new kernel and rebooted. > > Another thing is, that sometimes I can only boot 1 of 3 times > without a kernel panic. This morning 2 or 3 consecutive panics, > prior being able to boot my laptop. > > The problem with apm/acpi is since my last make world yesterday. > > The boot problems with many panics are longer ... > > But its always the same process, where it panics... > > In my next mail I'll attach a boot log. > > I could offer ssh access, if somebody would be willed trying to > troubleshoot one or both of these problems. > > A comconsole would also be possible. > > BTW, -current on my Server is stable. Its only the laptop, > where those panics happen. > > > Andreas /// > > -- > Andreas Klemm - Powered by FreeBSD 5.1-CURRENT > Need a magic printfilter today ? -> http://www.apsfilter.org/ > ___ > [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]"
build world build kernel correct order?
ference to `dumphook' /usr/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /usr/src/sys/netgraph/netgraph.h:689: undefined reference to `dumpitem' udbp.o: In function `ng_udbp_rcvdata': /usr/src/sys/dev/usb/udbp.c:738: undefined reference to `ng_free_item' /usr/src/sys/dev/usb/udbp.c:768: undefined reference to `M_NETGRAPH_META' udbp.o: In function `ng_udbp_rmnode': /usr/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /usr/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /usr/src/sys/netgraph/netgraph.h:457: undefined reference to `ng_unref_node' udbp.o: In function `ng_udbp_rmnode': /usr/src/sys/dev/usb/udbp.c:802: undefined reference to `ng_make_node_common' /usr/src/sys/dev/usb/udbp.c:805: undefined reference to `ng_name_node' udbp.o: In function `ng_udbp_rmnode': /usr/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /usr/src/sys/netgraph/netgraph.h:457: undefined reference to `ng_unref_node' /usr/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' udbp.o: In function `ng_udbp_connect': /usr/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /usr/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' udbp.o: In function `ng_udbp_disconnect': /usr/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /usr/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /usr/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /usr/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /usr/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /usr/src/sys/netgraph/netgraph.h:419: undefined reference to `dumpnode' /usr/src/sys/netgraph/netgraph.h:177: undefined reference to `dumphook' /usr/src/sys/netgraph/netgraph.h:248: undefined reference to `ng_rmnode_self' udbp.o: In function `udbp_match': /usr/src/sys/dev/usb/udbp.c:226: undefined reference to `ng_parse_int32_type' /usr/src/sys/dev/usb/udbp.c:227: undefined reference to `ng_parse_int32_type' /usr/src/sys/dev/usb/udbp.c:231: undefined reference to `ng_parse_struct_type' /usr/src/sys/dev/usb/udbp.c:250: undefined reference to `ng_parse_int32_type' *** Error code 1 Stop in /usr/obj/usr/src/sys/SERVER3. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ken easson justken.net [EMAIL PROTECTED] justken web programming and technical support. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: howto debug acpi_thermal on Dell 2500 servers
Thanks for the info. I did try mbmon, not the x version, but the command line version. It hung. I have hunted for thermal details for 2500 servers on dell's web site but can not find anything that seems to relate! I was hoping that acpi was the answer. Seems like the it's a secret :( , I am not an expert in this area. The acpi stuff looks really cool. Very easy to use in any program (I use nagios for monitoring (see ports)). If anyone knows a detail I don't about this I don't want to flood current unless it's relevant (I think acpi is relevant to curent, but general temp stuff would not be). I will entertain any other ideas in private messages, so please feel free to e-mail me privately. Thanks! Ken - Original Message - From: "Sten" <[EMAIL PROTECTED]> To: "Ken Menzel" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, October 10, 2003 1:48 PM Subject: Re: howto debug acpi_thermal on Dell 2500 servers > On Fri, 10 Oct 2003, Ken Menzel wrote: > > > Hi, > >I am trying to figure out how to use ACPI to get thermal info on > > Dell 2500 servers. I have compiled acpi into the kernel (see below > > for problems with acpi as module with ACPI_DEBUG in make.conf). I > > can't seem to get any addtional info from acpi. Do I need a debug > > kernel? Do I have to have more options in my kernel config? Is > > someone already doing (done?) this and I shouldn't bother to try and > > debug it? > > I do know that on the dell 1550, temperature monitoring is done > with an lm80, which didn't seem to want to play with smbus. > (x)mbmon which opens /dev/io directly is able to get temperature > readings. Might be worth a try. > > -- > Sten Spans > > There is a crack in everything that's how the light gets in. > ___ > [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]"
howto debug acpi_thermal on Dell 2500 servers
Hi, I am trying to figure out how to use ACPI to get thermal info on Dell 2500 servers. I have compiled acpi into the kernel (see below for problems with acpi as module with ACPI_DEBUG in make.conf). I can't seem to get any addtional info from acpi. Do I need a debug kernel? Do I have to have more options in my kernel config? Is someone already doing (done?) this and I shouldn't bother to try and debug it? Thanks, Ken I tried to include any relevant details that I saw in other messages in the archives: I seemed to get more info without ACPI_DEBUG on and the acpi as a KLD. sidenote: kernel would not load the acpi.ko file if I made it with ACPI_DEBUG=1 in make.conf. (See way below) now I am using: device acpi options ACPI_DEBUG I tried adding OPTIONS ACPI_VERBOSE but it gives 'unknown option "ACPI_VERBOSE" ' My loader.conf is as follows: riker# cat /boot/loader.conf hw.acpi.debug=1 hw.acpi.verbose = 1 debug.acpi.layer = "ACPI_ALL_COMPONENTS ACPI_FAN ACPI_THERMAL" debug.acpi.level = "ACPI_LV_WARN ACPI_LV_ERROR ACPI_LV_OBJECTS" sysctl utput --- riker# sysctl -a | grep acpi acpisem17 3K 3K 17 64,128 acpica 1357 175K177K15193 16,64,128,256,512,1024 acpidev44 1K 1K 44 16 debug.acpi.acpi_ca_version: 0x20030619 debug.acpi.layer: ACPI_UTILITIES ACPI_HARDWARE ACPI_EVENTS ACPI_TABLES ACPI_NAMESPACE ACPI_PARSER ACPI_DISPATCHER ACPI_EXECUTER ACPI_RESOURCES ACPI_CA_DEBUGGER ACPI_OS_SERVICES ACPI_CA_DISASSEMBLER ACPI_ALL_COMPONENTS ACPI_EC ACPI_AC_ADAPTER ACPI_THERMAL ACPI_FAN debug.acpi.level: ACPI_LV_ERROR ACPI_LV_WARN ACPI_LV_OBJECTS debug.acpi.semaphore_debug: 0 hw.acpi.supported_sleep_state: S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 5 hw.acpi.s4bios: 0 hw.acpi.verbose: 1 hw.acpi.disable_on_poweroff: 1 machdep.acpi_timer_freq: 3579545 machdep.acpi_root: 1039488 riker# Hope you can help: more details below See below for output of dmesg | grep acpi. -- riker# dmesg | grep acpi acpi0: on motherboard acpi0: Power Button (fixed) acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 pcib0: on acpi0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio1 port 0x2f8-0x2ff irq 3 on acpi0 ppc0 port 0x778-0x77f,0x378-0x37f irq 7 drq 1 on acpi0 pcib1: on acpi0 pcib3: on acpi0 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 riker#riker# pciconf -lv [EMAIL PROTECTED]:0:0:class=0x06 card=0x chip=0x00081166 rev=0x23 hdr=0x00 vendor = 'Reliance Computer Corp./ServerWorks' device = 'NB6536 (CNB20-HE) Hostbridge & MCH, bus/dev/func 0/0/0' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:1:class=0x06 card=0x chip=0x00081166 rev=0x01 hdr=0x00 vendor = 'Reliance Computer Corp./ServerWorks' device = 'NB6536 (CNB20-HE) Hostbridge & MCH, bus/dev/func 0/0/0' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:2:class=0x06 card=0x chip=0x00061166 rev=0x01 hdr=0x00 vendor = 'Reliance Computer Corp./ServerWorks' device = 'NB6536 (CNB20-HE) Host Bridge, function 2 and function 3' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:0:3:class=0x06 card=0x chip=0x00061166 rev=0x01 hdr=0x00 vendor = 'Reliance Computer Corp./ServerWorks' device = 'NB6536 (CNB20-HE) Host Bridge, function 2 and function 3' class= bridge subclass = HOST-PCI --- way below problems loading acpi as module with debug Normal boot riker# kldstat Id Refs AddressSize Name 17 0xc040 5aba64 kernel 21 0xc09ac000 4ceacacpi.ko 31 0xc890f000 19000linux.ko riker# buildkernel and installkernel with ACPI_DEBUG=1 %cat /etc/make.conf # -- use.perl generated deltas -- # # Created: Fri Apr 4 09:20:59 2003 # Setting to use base perl from ports: PERL_VER=5.6.1 PERL_VERSION=5.6.1 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo KERNCONF=ICARZ CPUTYPE=i686 CFLAGS= -O -pipe CXXFLAGS+= -fmemoize-lookups -fsave-memoized ACPI_DEBUG=1 result: % %kldstat Id Refs AddressSize Name 15 0xc040 5aba64 kernel 21 0xc88ca000 19000linux.ko %dmesg | grep acpi Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0a351f4. KLD file acpi.ko - could not finalize loading - Ken Menzel ICQ# 9325188 www.icarz.com [EMAIL PROTECTED] ___
Re: Q) Does em0 work under HTT?
From: dave <[EMAIL PROTECTED]> > This is an MSI 875P Neo MB. > > Do you have it enabled in the bios? > > dave Yes, I enable HTT in the bios because without enabling it, freebsd-current does not recognize HTT. I mean that; with bios HTT disables; /sys/i386/i386/identcpu.c (cpu_procinfo & CPUID_HTT_CORES) >> 16) returns 1 !! while bios HTT enables; /sys/i386/i386/identcpu.c (cpu_procinfo & CPUID_HTT_CORES) >> 16) returns 2. My board is SuperMicro X5DAL-G. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Q) Does em0 work under HTT?
Hi!
Does em{0,1} work under Hyperthreding enabled?
"em0", seemingly is not working under my environment;
FreeBSD 5.1-CURRENT #15: Sat Oct 4 09:46:38 JST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/TYD3
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0aae000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0aae2bc.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2799.22-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf27 Stepping = 7
Features=0xbfebfbff
Hyperthreading: 2 logical CPUs
However, I am not sure if it is because of HTT
enabled or not.
Any comments/suggestions are very appreciated.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
usb keyboard not working in single user mode
Hello I've got 5.1-current running on an IBM BladeCenter HS20. This thing has a USB KVM built-in. It's working in multi-user mode. Problem is when I boot to single user, can't do anything. I'm looking for a way to fire up the usbd in single user mode. So far I've tried: Loading usbd.ko, ugen.ko, ukbd.ko modules via loader.conf. NO GOOD, hangs the system. Setting /usr/sbin/usbd in /etc/ttys so that init(8) can run the usbd. If anyone needs access I can supply a root login via ssh. Thanks Ken McKittrick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HTT on current
JYI, I tested machdep.hlt_logical_cpus=0/1, buildworld, and found no particular reason to disable HTT as below with Zeon 2.8Ghz x 2, 1GBmem, Slow IDE HDD. It may not be the common case, so just for your info. # sysctl machdep.hlt_logical_cpus=0 # /usr/bin/time make -j32 buildworld 1910.29 real 2520.53 user 777.30 sys # sysctl machdep.hlt_logical_cpus=1 # /usr/bin/time make -j32 buildworld 2289.33 real 2666.66 user 645.88 sys ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HTT on current
Strange Mine (Supermicro X5DAL-G) goes like ; tyd3# dmesg Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #30: Sun Aug 24 20:25:11 JST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TYD3 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0794000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0794294. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2799.21-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1073152000 (1023 MB) avail memory = 1034416128 (986 MB) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 24 pins in IOAPIC #1 Programming 24 pins in IOAPIC #2 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee0 cpu1 (AP): apic id: 6, version: 0x00050014, at 0xfee0 cpu2 (AP): apic id: 1, version: 0x00050014, at 0xfee0 cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00178020, at 0xfec0 io1 (APIC): apic id: 3, version: 0x00178020, at 0xfec8 io2 (APIC): apic id: 4, version: 0x00178020, at 0xfec80100 Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 20 entries at 0xc00fde80 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_cpu0: port 0x530-0x537 on acpi0 acpi_cpu1: port 0x530-0x537 on acpi0 acpi_cpu2: port 0x530-0x537 on acpi0 acpi_cpu3: port 0x530-0x537 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 IOAPIC #0 intpin 16 -> irq 2 IOAPIC #0 intpin 19 -> irq 5 IOAPIC #0 intpin 18 -> irq 10 IOAPIC #0 intpin 23 -> irq 11 : : : And my /etc/rc.local has; #! /bin/sh sysctl machdep.hlt_logical_cpus=0 And, top shows 4 CPUs are running ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HTT on current
Did you do "sysctl machdep.hlt_logical_cpus=0"? Default setting halt logical CPUs, and won't start HTT. This is a kind of FAQ, and you will see a lot in the past mailing-list. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
xemacs hangs with -current
With these one week cvsup'd current, my xemacs hangs quite easily with operation like moving cursor beyond the end of line, some random mouse clicking, etc. (signal related??) Any fix, or suggestions? I am using ; A) FreeBSD 5.1-CURRENT #12: Fri Jul 25 23:37:43 JST 2003 CPU: Intel Pentium III (802.93-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x387fbff real memory = 805240832 (767 MB) avail memory = 773910528 (738 MB) B) XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: FreeBSD 5.0 i386 [ELF] C) kde 3.1.2 D) xemacs 21.5.13 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Does linux-sun-jdk_1.4.2 work?
I have the following error and cannot compile jdk14 on FreeBSD-current, July 20th. cvsup'ed with the latest linux_base. Is is unique to me alone? tyd3# /usr/local/linux-sun-jdk1.4.2/bin/java -version # # HotSpot Virtual Machine Error, Internal Error # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Client VM (1.4.2-b28 mixed mode) # # Error ID: 4F533F4C494E55580E43505001C9 # Heap at VM Abort: Heap ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Q) XFree86-4-Server
Thank you. I find that I haven't cvsup x11/XFree86-4-libraries for a while. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Q) XFree86-4-Server
Is it only with me? XFree86-4-Server cannot be compiled on recent -current, FreeBSD 5.0-CURRENT #34: Sat Mar 22 13:21:34 JST 2003, with the following error (patch cannot be applied); >>> ===> Applying FreeBSD patches for XFree86-Server-4.3.0_2 1 out of 2 hunks failed--saving rejects to lib/X11/imLcPrs.c.rej >> Patch patch-imLcPrs.c failed to apply cleanly. >> Patch(es) patch-FreeBSD.cf patch-Imake.cf patch-Imake.rules patch-Imake.tmpl patch-X11.tmpl patch-Xlc-fix patch-c2 patch-dps patch-dpsinfo patch-dri-Imakefile patch-f applied cleanly. *** Error code 1 Stop in /home/ports/x11-servers/XFree86-4-Server. >>> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: BOOT2_UFS=UFS1_ONLY works for today's current
Thank you for your info., Giorgos. BOOT2_UFS=UFS1_ONLY in /etc/make.conf made my buildworld OK. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current buildworld fails 24 hours
I have the following error with make buildworld since Feb. 21th, 0900GMT with my P3x2 box. boot2 seems exceeding the size limit, any fix? ::: sed -e '/align/d' -e '/nop/d' < boot2.s.tmp > boot2.s rm -f boot2.s.tmp as -o boot2.o boot2.s ld -nostdlib -static -N --gc-sections -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=1.01 size=780 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=1691 text=0 data=0 bss=0 entry=0 output: fmt=bin size=1f25 text=114 data=1e11 org=0 entry=0 -293 bytes available *** Error code 1 1 error *** Error code 2 1 error To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 5 not working with Linux Virtual Server
Terry I meant to say LVS/DR. Not LVS/Nat or LVS/Tun. The RealServers/Back-End machines reply directly back to the client. As I said, works fine with 4.7. I'm sure it's something 5.0-current specific. I'm currently processing 500K emails per day with this setup. :) Hmmm, I think I need to run tcpdump on a the client too. I'm only looking at the traffic between the LVS machine and the Real Server. Thanks Ken On Thursday, February 13, 2003, at 06:35 PM, Terry Lambert wrote: Ken McKittrick wrote: I've got a FreeBSD5.0-R machine that doesn't work with Linux Virtual Server. This is for SMTP and WWW services. I'm using LVS-Direct Routing. The LVS machine has the 66.218.0.54 Real IP and 66.218.0.58 and 66.218.0.59 as Virtual IP's. The FreeBSD machine has 66.218.0.28 and a Real IP on fxp0 and 66.218.0.58/59 on lo0 with -arp. Running tcpdump host 66.218.0.54 I can see the requests come in, but nothing is going back out. When you telnet into port 25 the connection times out. I've running Linux LVS with FreeBSD4-STABLE SMTP machines in production so I'm confident that it's a FreeBSD 5.0 issue. I'm guessing this is some LVS specific terminology that someone made up because they did not read the literature before writing their code? Is this the DSR or "Direct Server Return" configuration? If so, the answer is that you need to specify the LVS as the default return route, and not answer locally, even though it appears to be a local net. This can be handled using explicit routes for the alias IP addresses. You *did* put the alias IP addresses on the loopback interface, and turn of ARP'ing for them, right? If you need more help, probably the correct place to ask is not the -current list, but the -net list (after you replace the terminology "LVS-Direct" with it's real name; I'm only guessing you meant DSR here). -- Terry 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
FreeBSD 5 not working with Linux Virtual Server
Hello I've got a FreeBSD5.0-R machine that doesn't work with Linux Virtual Server. This is for SMTP and WWW services. I'm using LVS-Direct Routing. The LVS machine has the 66.218.0.54 Real IP and 66.218.0.58 and 66.218.0.59 as Virtual IP's. The FreeBSD machine has 66.218.0.28 and a Real IP on fxp0 and 66.218.0.58/59 on lo0 with -arp. Running tcpdump host 66.218.0.54 I can see the requests come in, but nothing is going back out. When you telnet into port 25 the connection times out. I've running Linux LVS with FreeBSD4-STABLE SMTP machines in production so I'm confident that it's a FreeBSD 5.0 issue. Thanks Ken McKittrick Network Engineer USADatanet To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Q) Does perl install libperl.so ?
Thank you, Simon for your response with pointer. I think I overlooked these as I did not care about then. I read through articles you pointed, but couldn't find the conclusion. What was the outcome of the discussion? or, still pending? I am now wrecked at 'plperl' installation as it is mentioned in the discussion. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Q) Does perl install libperl.so ?
/usr/ports/lang/perl5 seemingly does not generate libperl.so with FreeBSD-current port as shown below. Is it intended one? Why? : : : Any special flags to pass to cc -c to compile shared library modules? [-DPIC -fPIC] What command should be used to create dynamic libraries? [cc] Any special flags to pass to cc to create a dynamically loaded library? [-shared -L/usr/local/lib] Any special flags to pass to cc to use dynamic linking? [none] Build a shared libperl.so (y/n) [n] ??? System manual is in /usr/share/man/man1. Where do the main Perl5 manual pages (source) go? (~name ok) [/usr/local/man/man1] :: : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: installworld fail
Hi,
I had the same problem. "make installworld" does this:
mkdir -p /tmp/install.vmZBbRA0
for prog in [ awk cat chflags chmod chown date echo egrep find grep ln
make mk\
dir mtree mv pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp
`which $\
prog` /tmp/install.vmZBbRA0; done
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386
CPUTYP\
E=p2 GROFF_BIN_PATH=/usr/obj/usr/src/i386/usr/bin
GROFF_FONT_PATH=/usr/obj/us\
r/src/i386/usr/share/groff_font
GROFF_TMAC_PATH=/usr/obj/usr/src/i386/usr/shar\
e/tmac
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/\
obj/usr/src/i386/usr/games:/tmp/install.vmZBbRA0 make -f Makefile.inc1
reinstal\
l
Later on it adds that directory to $PATH
Seems that the copy of "echo" sometimes failed to come out right with md
/tmp.
For you it was the copy of mtree.
bsdlab# df -h
FilesystemSize Used Avail Capacity Mounted on
/dev/da0s1a 126M75M41M65%/
devfs 1.0K 1.0K 0B 100%/dev
/dev/da1s1d 2.0G 1.5G 337M82%/usr
/dev/da0s1d 504M 6.2M 457M 1%/var
/dev/da2s1e 2.0G 131M 1.7G 7%/home
procfs4.0K 4.0K 0B 100%/proc
/dev/md10 254M16K 233M 0%/tmp
bsdlab#
My work-around was to run emacs and use "M-x compile" followed by "make
installworld".
I might have contaminated my test by running "sync" in the middle of it.
I'll keep checking though.
Date: Mon, 25 Nov 2002 19:04:28 +0800
From: Ying-Chieh Liao <[EMAIL PROTECTED]>
To:[EMAIL PROTECTED]
Cc:Ying-Chieh Liao <[EMAIL PROTECTED]>
Subject: Re: installworld fail
Message-ID: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
--G4iJoqBmSsgzjUCe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Nov 22, 2002 at 00:06:59 +0800, Ying-Chieh Liao wrote:
I'm in DP2, and cvsup and then make world...
if [ -L /usr/share/examples/sunrpc ]; then rm -f /usr/share/examples/sunrpc; fi
if [ -L /usr/share/examples/worm ]; then rm -f /usr/share/examples/worm; fi
mtree -deU -f /usr/src/share/examples/../../etc/mtree/BSD.usr.dist -p /usr
/tmp/install.UiNprj9F/mtree: 1: Syntax error: "(" unexpected
maybe there's something wrong with mfs...
error occurs when I mount tmp as a mfs
and after I switch tmp to a "real harddisk", it's all ok
--
The sooner you start to code, the longer the program will take.
--- Roy Carlson
--G4iJoqBmSsgzjUCe
Content-Type: application/pgp-signature
Content-Disposition: inline
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (FreeBSD)
iD8DBQE94gO8rMYBZRHAI4IRAmRTAKCQMCL9YW50ytgD+rAgfpYaw+7DBwCfWV36
K/LBs1KuH8Zgk3z1PaEJe1I=
=5trs
-END PGP SIGNATURE-
--G4iJoqBmSsgzjUCe--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -current buildworld breakage
Thank you! From: Craig Rodrigues <[EMAIL PROTECTED]> > You don't have the latest sources. Did you use cvsup it > update your sources? If you used cvsup, then you > need to add src-sys-crypto to your cvsup file. It was my cvsup prroblem. Fixed!! msg45379/pgp0.pgp Description: PGP signature
Re: -current buildworld breakage
Thank you for your prompt reply.
From: walt <[EMAIL PROTECTED]>
: ::
>
> I can't see how line 222 includes an implicit declaration of 'panic'.
>
> Is your file different?
>
I do not know why compiler says line 222, but it is
below 222 and my latest source says;
# cat rijndael/rijndael-api-fst.c
::::
switch (cipher->mode) {
case MODE_ECB:
for (i = numBlocks; i > 0; i--) {
rijndaelEncrypt(input, outBuffer, key->keySched, key->RO
UNDS);
input += 16;
outBuffer += 16;
}
padLen = 16 - (inputOctets - 16*numBlocks);
if (padLen > 0 && padLen <= 16)
panic("rijndael_padEncrypt(ECB)");
^^
bcopy(input, block, 16 - padLen);
for (cp = block + 16 - padLen; cp < block + 16; cp++)
*cp = padLen;
rijndaelEncrypt(block, outBuffer, key->keySched, key->ROUNDS);
break;
msg45377/pgp0.pgp
Description: PGP signature
-current buildworld breakage
I have an error for a week and cannot make buildworld. Where can I find "panic" other than real panic? ===> sbin/gbde : : : : cc -O -pipe -mcpu=pentiumpro -I/usr/src/sbin/gbde/../../sys -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c template.c cc1: warnings being treated as errors /usr/src/sys/crypto/rijndael/rijndael-api-fst.c: In function `rijndael_padEncrypt': /usr/src/sys/crypto/rijndael/rijndael-api-fst.c:222: warning: implicit declaration of function `panic' *** Error code 1 msg45368/pgp0.pgp Description: PGP signature
Re: Issues I have w/ recent -current
Sorry for late to respond.
Thank you for your help. It solved the problem.
From: Alexander Kabaev <[EMAIL PROTECTED]>
> On Tue, 01 Oct 2002 23:29:34 +0900 (JST)
> Yamada Ken Takeshi <[EMAIL PROTECTED]> wrote:
> >
> >3) HelloWorld.cc can't be compiled while 4.6R can do it,
> > and it disables to compile kdebase3.
> >
> > #include int main(){ cout<<"Hello World\n";}
> >
> > c++ HelloWorld.cc -o HelloWorld
> > /var/tmp//cckSb4Nm.o: In function `main':
> > /var/tmp//cckSb4Nm.o(.text+0x19): undefined reference to `cout'
> > /var/tmp//cckSb4Nm.o(.text+0x1e): undefined reference to
> > `ostream::operator<<(char const*)'
>
> Pilot error. Get rid of stale /usr/include/g++ before your next
> installworld.
msg45247/pgp0.pgp
Description: PGP signature
Issues I have w/ recent -current
Just FYI.
I'm running -current (9/30) on PIII x 2(smp) and notice
the followings;
1) buildworld on XFree86-4 panics silently to reboot.
2) fsck -b after above reason reboot core dumps like;
ffs_snapgone: lost snapshot vnode 3
fatal trap 12: page fault while in kernel mode
cpuid = 1; lapic.id = 0100
fault virtual address = 0x20
fault code = supervisor read, page not found
instruction pointer = 0x8: 0xc02bfac7
stack pointer = 0x10: 0xd8fff7e0
frame pointer = 0x10: 0xd8fff804
code segment = base 0x0, limit 0xf, type=0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflag = interrupt enabled, resume, IOPL=0
current process = 386(fsck_ufs)
trap nubmer = 12
panic: page fault
cpuid = 1; elapic.id = 0100
boot() called on cpu#1
3) HelloWorld.cc can't be compiled while 4.6R can do it,
and it disables to compile kdebase3.
#include int main(){ cout<<"Hello World\n";}
c++ HelloWorld.cc -o HelloWorld
/var/tmp//cckSb4Nm.o: In function `main':
/var/tmp//cckSb4Nm.o(.text+0x19): undefined reference to `cout'
/var/tmp//cckSb4Nm.o(.text+0x1e): undefined reference to
`ostream::operator<<(char const*)'
4) xemacs hang-ups quite often on XFree86-4
msg43671/pgp0.pgp
Description: PGP signature
Re: 'sh' core dumps with signal 4 and another problems...
Hi! Do you enable softupdate? I have had "core dump" right after booting and about to "login:" prompt. I disabled all softupdates, and now it works fine so far. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC3.1 internal compiler error when compilingXFree86-4-libraries
Thank you! By eliminating "-O" option, I could make XFree86-4-Server which works. "-O -pipe" was in /usr/share/mk/sys.mk. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC3.1 internal compiler error when compilingXFree86-4-libraries
Thank you! Your patch-z32 made me happy a little.
When can I compile XFree86-4-Server-4.2.0_2 with -current?
It gives me "internal compiler error", too as below. I had
thought it uses XFree86-4-libraries port which was wrong.
===> Building for XFree86-Server-4.2.0_2
Building Release 6.6 of the X Window System: -
Sat Jun 8 21:40:08 JST 2002
::: (snip)
rm -f translate.o
LD_LIBRARY_PATH=../../../../exports/lib cc -c -O -pipe-ansi -pedantic -Dasm=__asm
-Wall -Wpointer-arith -I../../../../exports/include
-I../../../../exports/include/X11 -I../../../../include/extensions
-I../../../../extras/Mesa/src -I../../../../lib/GL/dri -I../../../..
-I../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS
-DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI
-DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA-DUSE_X86_ASM
-DUSE_MMX_ASM -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith
-I../../../../exports/include -I../../../../exports/include/X11
-I../../../../include/extensions -I../../../../extras/Mesa/src
-I../../../../lib/GL/dri -I../../../.. -I../../../../exports/include -DCSRG_BASED
-DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI
-DMALLOC_0_RETURNS_NULL -DGLXEXT -DXF86DRI -DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN
-DGLX_USE_MES!
A -DUSE_X86_ASM -DUSE_MMX_ASM-fPIC translate.c
In file included from translate.c:779:
../../../../extras/Mesa/src/trans_tmp.h: In function `trans_1_GLdouble_1ub_elt':
../../../../extras/Mesa/src/trans_tmp.h:124: could not find a spill register
(insn 96 94 97 (set (subreg:SF (reg:QI 75) 0)
(plus:SF (reg:SF 8 st(0) [76])
(reg:SF 9 st(1) [80]))) 525 {*fop_sf_comm_nosse} (insn_list 87 (nil))
(expr_list:REG_DEAD (reg:SF 8 st(0) [76])
(nil)))
../../../../extras/Mesa/src/trans_tmp.h:124: Internal compiler error in failed_reload,
at reload1.c:5050
Please submit a full bug report,
with preprocessed source if appropriate.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: GCC3.1 internal compiler error when compilingXFree86-4-libraries
I have the following error when I try to install it. Is it unique only to me? ===> Installing for XFree86-libraries-4.2.0_1 ===> XFree86-libraries-4.2.0_1 depends on executable: mkhtmlindex - found ===> XFree86-libraries-4.2.0_1 depends on shared library: freetype.9 - found : : : (snip) install in lib/GL/GL done installing in lib/GL/mesa/src/OSmesa... /usr/bin/install -c -m 0644 libOSMesa.a /usr/X11R6/lib ranlib /usr/X11R6/lib/libOSMesa.a rm -f ../../../../../lib/GL/mesa/src/translate.o unshared/../../../../../lib/GL/mesa/src/translate.o LD_LIBRARY_PATH=../../../../../exports/lib cc -c -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -I../../../../../exports/include/X11 -I../../../../../include/extensions -I../../../../../extras/Mesa/src/OSmesa -I../../../../../extras/Mesa/src -I../../../../../extras/Mesa/include -I../../../../.. -I../../../../../exports/include -DCSRG_BASED -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -DXUSE_MTSAFE_API -DXNO_MTSAFE_PWDAPI -DMALLOC_0_RETURNS_NULL ../../../../../lib/GL/mesa/src/translate.c -o unshared/../../../../../lib/GL/mesa/src/translate.o Assembler messages: FATAL: can't create unshared/../../../../../lib/GL/mesa/src/translate.o: No such file or directory *** Error code 1 Stop in /home/ports/x11/XFree86-4-libraries/work/xc/lib/GL/mesa/src/OSmesa. *** Error code 1 Stop in /home/ports/x11/XFree86-4-libraries/work/xc/lib/GL. *** Error code 1 Stop in /home/ports/x11/XFree86-4-libraries/work/xc/lib. *** Error code 1 Stop in /home/ports/x11/XFree86-4-libraries/work/xc. *** Error code 1 Stop in /home/ports/x11/XFree86-4-libraries/work/xc. *** Error code 1 Stop in /home/ports/x11/XFree86-4-libraries. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Current compile error at kerverosIV/lib
Recent current compilation causes the following error; : : : (snip) cc -O2 -pipe -DENCRYPTION -DAUTHENTICATION -DSRA -I/usr/src/kerberosIV/lib/libtelnet/../../../crypto/telnet -DKRB4 -I/usr/src/kerberosIV/lib/libtelnet/../../../crypto/kerberosIV/lib/krb -I/usr/src/kerberosIV/lib/libtelnet/../../include -Wall -DHAVE_CONFIG_H -I/usr/local/obj/usr/src/kerberosIV/lib/libtelnet/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -DLIBEXECDIR=\"/usr/libexec\" -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/crypto/telnet/libtelnet/kerberos.c -o kerberos.o cc1: warnings being treated as errors /usr/src/crypto/telnet/libtelnet/kerberos.c: In function `kerberos4_cksum': /usr/src/crypto/telnet/libtelnet/kerberos.c:496: warning: unreachable code at beginning of switch statement *** Error code 1 Stop in /usr/src/kerberosIV/lib/libtelnet. *** Error code 1 Stop in /usr/src/kerberosIV/lib. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't build kernel: config doesn't work
The same here, but 'config -d /sys/compile/GENERIC GENERIC' did what it is supposed to do. Is this a new specification of 'config', or bug? From: Michael Harnois <[EMAIL PROTECTED]> Subject: can't build kernel: config doesn't work mdharnois> Truly bizarre. Running config does nothing, although it generates the mdharnois> usual messages. I tried deleting my kernel object directory after an mdharnois> odd failure; ran config again, it didn't even recreate the directory. mdharnois> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Supported ATAPI cdr/cdrw drives
* Søren Schmidt <[EMAIL PROTECTED]> [010528 09:01]: > > As promised I've made up a list of reports I've received so far go to > http://freebsd.dk/ and follow the link. > > I also have a patch for the Yamaha's (yamaha-cdr.p1) which also > can be found via the above URL. Let me know if that make things > work... This patch (well, yamaha-cdr.p2), allows my Yamaha 2100E to fixate disks now! Thanks Soren and others! Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Q) lock order reversal
Hi! With recent -current kernel, I get message below with P3@800Mhz X 2 when booting up. What is wrong? lock order reversal 1st 0xc04d4ac0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c 1007 2nd 0xdb3001ac vnode interlock @ ../../ufs/ffs/ffs_vfsops.c 1016 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: My network is dead because of this program :(
* John Indra <[EMAIL PROTECTED]> [010515 21:19]: > Dear all... > > First of all, really sorry for cross-posting... > > I am running a -CURRENT system (Apr 30th 2001). There is a user in my > machine running this small program to DoS my xl0 interface. I doubt that > this program is specifically designed for xl cards though. > > Once the program is started, it starts forking childs I assume. Then after > sometime, this messages start popping to my screen: > > xl0: no memory for rx lists -- packet dropped > Shouldn't reasonable resource limits (man limits), prevent this from happening - particularly the sbsize setting? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: -CURRENT b0rked?
* Matthew D. Fuller <[EMAIL PROTECTED]> [010512 19:35]: > On Sat, May 12, 2001 at 12:21:55PM +0300 I heard the voice of > Maxim Sobolev, and lo! it spake thus: > > > > It seems that sysinstall(8) was not fully integrated into > > buildworld - it depends on content of /usr/share/syscons/keymaps, > > while it shouldn't. > > > > I've just committed a patch that should fix this problem. > > Hoo, here I come to make your life a living hell once more... > > In file included from /usr/src/usr.sbin/sysinstall/keymap.c:40: > keymap.h:2: `keymap_be_iso' undeclared here (not in a function) > keymap.h:2: initializer element is not constant > keymap.h:2: (near initialization for `keymapInfos[0].map') > keymap.h:3: `keymap_br275_iso' undeclared here (not in a function) > keymap.h:3: initializer element is not constant > keymap.h:3: (near initialization for `keymapInfos[1].map') > Deleting keymap.h (autogenerated, in obj/* somewhere, I forget), and restarting the build got me past this. K To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Threaded linux should work again
It makes my -current (ca. Mar.12) slightly happy, but I still have not-responding to I/O problem with jdk1.3-ibm(linux) when I run any java application - 'top' says java pauses. I did not apply the patch; http://www.cs.duke.edu/~gallatin/linux_sa_siginfo/diff as it was so different - beyond my skill to manually apply it - linux_machdep.c, linux_sysvec.c especially. Could anyone point the kernel patch for -current to run jdk1.3 if available ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is Sawfish running on -current?
Thank you for quick reply. I found that my librep was old one - Sept one living in /usr/local/libexec/rep., and the latest one (v 1.23 2001/01/07) goes under /usr/X11R6/libexec/rep/i386--freebsd5.0/. So, I deleted /usr/local/libexec/rep hoping that new one living under X11R6 be used. Sigh! rep-gtk (v 1.23 2000/12/05) could not be compiled because it looked at /usr/local/libexec/rep/i386-freebsd5.0/rules.mk. I understand that it may be because of librep and rep-gtk, but I cannnot solve this /usr/X11R6/libexec/ vs. /usr/local/libexec/ by myself considering other programs, and stucked. I hope you can suggest some solution of this issue. (I'll be out a week and can not respond to for a while, please accept it.) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Is Sawfish running on -current?
I have the following error while compiling Sawfish on recent -current. Is it my half updated fault or the -current issue? gmake[1]: Entering directory `/home/SRC/FreeBSD/FreeBSD-current/ports/x11-wm/sawfish/work/sawfish-0.36/lisp' SAWFISHLISPDIR=. SAWFISHEXECDIR=../src/.libexec SAWFISHDOCFILE=../DOC /usr/local/libexec/rep/i386--freebsd5.0/libtool --mode=execute -dlopen ../src/gradient.la ../src/sawfish --batch --no-rc compiler -f compile-batch sawfish/wm.jl Segmentation fault - core dumped gmake[1]: *** [sawfish/wm.jlc] Error 139 gmake[1]: Leaving directory `/home/SRC/FreeBSD/FreeBSD-current/ports/x11-wm/sawfish/work/sawfish-0.36/lisp' gmake: *** [all] Error 2 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mfs size limits?
Is there a reason I cannot create a ramdisk larger than 507627 1kB blocks? I create them using the syntax of mount_mfs -s [any numer] -T minimum /dev/null /ramdisk It never errors, but never creates anything larger than the 507627 blocks. My computer has 768MB of RAM. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
"Link Your Web Site" To IndustrySearch.Com
Increase traffic to your company's web site with a FREE Hyperlink to IndustrySearch.Com. Thousands of industrial purchasing agents, buyers, engineers and others searching for suppliers and services can locate your business easily with our USA Industrial Directory. You can visit IndustrySearch.Com at http://industrysearch.com "Link Your Web Site" to our USA Industrial Directory Data Base today! Visit IndustrySearch.Com at http://industrysearch.com and click on "Link Your Web Site" Thank you, K. Prater USA INDUSTRIAL DATA BASE MANAGEMENT To be removed from our mailing list, please click Reply and type "REMOVE" in the subject field To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Spontaneous reboot while CPU usage is high
Hi, I have FreeBSD3.2 from ftp7.de.freebsd.org dated May 1999 installed on an AMD K6-2 333MHz with Aladdin V chipset and have experienced spontaneous reboots while CPU usage is very high--compiling or bringing a new web link in another window within Netscape Communicator. There are no entries in /var/log/messages. The symptom is the machine wedges for around 5-10 seconds and then my machine reboots. I have searched for the GNATS database and in dejanews and the closest things that may be causing my problem is perhaps the K6-2 itself or need of finetuning of some kernel parameters. I am unsure of how to check for the bad K6-2 itself. This system is a "hand-me-down," but is fairly reliable under Linux. Attached, please browse through my dmesg log and my kernel configuration file. Regards, Ken ---dmesg--- Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-RELEASE #4: Wed May 26 12:55:59 PDT 1999 r...@black.tmpest1.org:/usr/src/sys/compile/BLACK Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (333.37-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping=0 Features=0x8001bf real memory = 100663296 (98304K bytes) avail memory = 95182848 (92952K bytes) Probing for devices on PCI bus 0: chip0: rev 0x04 on pci0.0.0 chip1: rev 0x04 on pci0.1.0 chip2: rev 0xb4 on pci0.7.0 ed1: rev 0x00 int a irq 9 on pci0.8.0 ed1: address 00:80:c8:fd:90:ae, type NE2000 (16 bit) ed2: rev 0x00 int a irq 9 on pci0.9.0 ed2: address 00:80:c8:fd:88:0d, type NE2000 (16 bit) adv0: rev 0x02 int a irq 9 on pci0.11.0 adv0: AdvanSys Ultra SCSI Host Adapter, SCSI ID 7, queue depth 240 ide_pci0: rev 0x20 int a irq 0 on pci0.15.0 Probing for devices on PCI bus 1: vga0: rev 0xf3 int a irq 10 on pci1.6.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0x Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0x) at 0x220-0x22f irq 5 drq 1 flags 0x10 on isa Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model MouseMan+, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pcm0 not probed due to drq conflict with pcm1 at 1 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1625MB (3329424 sectors), 3303 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 1 (wd3): wd3: 4121MB (8440992 sectors), 8374 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 0 (atapi): , removable, intr, dma, iordy acd0: drive speed 1031KB/sec, 120KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/1 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port lpt0: on ppbus 0 lpt0: Interrupt-driven port adv0 not found at 0x330 vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 on isa apm: found APM BIOS version 1.2 Waiting 5 seconds for SCSI devices to settle sa0 at adv0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) changing root device to wd3s1a da0 at adv0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) ---kernelconfiguration--- # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # http://www.FreeBSD.ORG/> # # An exhaustive list of options and more detailed explanations of the # device lines is 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.143.2.12 1999/05/14 15:12:26 jkh Exp $ machine "i386" #cpu"I386_CPU" #cpu"I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident BLACK maxusers32 options MATH_EMULATE#Support for x87 emulation options INET#InterNETwor
RELNOTES.TXT
In /usr/src/release/texts/RELNOTES.TXT it lists the following for supported adaptec controllers: Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274X/284X/2920/2940/2950/3940/3950 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers. Adaptec AIC7850, AIC7880, AIC789x, on-board SCSI controllers. As far as I know, I don't think the 2920 is supported since it's not a standard adaptec card (it was bought from another company) If I'm wrong, I'd be really pleased since we've been trying to get one of these cards to be supported in FreeBSD 3.0-current. But if I'm right, it should be removed because it's sure to piss people off :) The last known source for the old patches to get this card working are at the following URL: http://www.sbox.tu-graz.ac.at/home/r/rmike/freebsd/welcome.html They, of course, don't work with CAM. IRC: SchradeE-Mail: schr...@schrade.com http://www.schrade.com/> To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
