builtin openssl and debugging?
How do I rebuild the builtin openssl with debugging symbols? I thought I could simply edit /usr/src/crypto/openssl/Makefile and then run make from the same directory, but that doesn't seem to work. Is there some way to do this w/o rebuilding world? Using the port isn't an option since I need to test against the version in the src tree. Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is login.conf.db now required?
Mikhail Teterin wrote: Hi! I updated world to today's 6.1 and my syslog is filling up with: Mar 24 15:08:29 aldan sshd[2163]: login_getclass: unknown class 'root' The /etc/login.conf did not change since November. I never had login.conf.db -- it was always optional. Did that just change, or is something else broken here? The only radical change I made today was setting NO_NIS to yes. Thanks! I had similar problems when I disabled NIS too. I'm not sure if your problem is the same, but I fixed mine by editing /etc/nsswitch.conf and replacing all occurrences of nis with files. Apparently there are some things that don't respect NO_NIS and therefore keep trying to use it anyway. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NSSWITCH errors in /var/log/cron
Ceri Davies wrote: What does your nsswitch.conf look like, and does removing the NIS entries fix it? Somebody else pointed out that changing compat to files for the group and passwd lines silences the error. It appears to be working. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
NSSWITCH errors in /var/log/cron
I have several machines running 6-STABLE that are showing the error listed below in /var/log/cron every few minutes. Google didn't turn up much of relevance, other than the fact that this might be related to disabling NIS. And, in fast, I have NO_NIS=true in /etc/make.conf on every single box. Is this a bug or a feature? Is it harmful? The error messages are... Feb 11 16:25:00 poseidon /usr/sbin/cron[95789]: (root) CMD (/usr/libexec/atrun) Feb 11 16:25:00 poseidon cron[95789]: NSSWITCH(nss_method_lookup): nis, group_compat, setgrent, not found Feb 11 16:25:00 poseidon cron[95789]: NSSWITCH(nss_method_lookup): nis, group_compat, endgrent, not found Feb 11 16:25:00 poseidon cron[95789]: NSSWITCH(nss_method_lookup): nis, passwd_compat, endpwent, not found ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Centralized building
Eirik Øverby wrote: I've spent about a week trying to accomplish a rather simple task: To build kernel and world once for each architecture we have, and distribute this precompiled src and obj tree via NFS to all the systems that need updating. I have combined this with a locally maintained CVS tree, in order to assure coherent releases being installed on all our systems. AFAICT cross-compiling amd64 on a i386 machine isn't supported yet. I ran into a similar problem when I upgraded an i386 machine to amd64. I thought I could just set CPUTYPE=athlon-64 and buildworld would do the right thing. Apparently not. I haven't bothered to try building i386 on an amd64 box though. Maybe you'll have better luck with that. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.x, 6.x and CPUTYPE
Scot Hetzel wrote: You just need to define the _MAKE_CONF variable for the appropriate OS that you are building: make _MAKE_CONF=/etc/make.conf.6x [build|install]world make _MAKE_CONF=/etc/make.conf.6x [build|install]kernel I spent a bit of time today trying to figure out why the above doesn't work. Eventually it occured to me to grep /usr/src to see if the variable even existed. It turns out it doesn't, however __MAKE_CONF does exist (that's with *two* leading underscores). Hopefully this will clear things up a bit in case anyone else is trying it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.0 release date and stability
Dick Hoogendijk wrote: Oops, it seems this feature is in 7-CURRENT only. If the appropiate person is reading this, why isnt something like that available in 6? I think it would be a very useful feature. What a shame. You made me glad for a very short time. This seemed to be the option I was looking for. Straight forward and understandable. It's not in 6 though .. so, any tips on another easy way? What about installing one of the compat ports and then removing it? Would it take the old libraries with it? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: twa kernel panic under heavy IO
Vinod Kashyap wrote: Going by the dmesg, you have a 9.1.5.2 driver and 9.2 firmware. The driver in 5 -STABLE is from the 9.2 release. So, you might not have the driver upgrade done properly. Try using the driver and firmware from the same release. If you still see problems, please contact 3ware support. How did you figure out the versions? I'm looking at his dmesg, and my own, and I'm not seeing the version info in a recognizable form. I must admit that I haven't been able to grok the 3ware version numbers at all, so maybe I'm dense. What am I missing? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: twa kernel panic under heavy IO
Vinod Kashyap wrote: How did you figure out the versions? I'm looking at his dmesg, and my own, and I'm not seeing the version info in a recognizable form. I must admit that I haven't been able to grok the 3ware version numbers at all, so maybe I'm dense. What am I missing? 9.1.5.2 and 9.2 are releases from 3ware, of packages of software and firmware for 9000 series controllers. The driver version he has (2.50.02.012) is from the 9.1.5.2 release, and is part of FreeBSD 5.4. The driver version corresponding to the 9.2 release that's on 5 -STABLE is 3.50.00.017. You can view/download the different releases from 3ware on the 3ware website. Thanks, that helped. I take it that you just have to know this somehow? Is there a list somewhere that shows the mapping between FreeBSD, driver, and firmware versions? The 3ware page has 9.2.1.1, which is what I updated to when I installed my 9500, but since then I've cvsup'd to 5-stable. Do I now have mismatched driver-firmware versions? How do I check this in the future? (besides bothering you about it) And since we're here...is there any reason to update to 9.3 if I only have a 9500S? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Disable hifn crypto card?
I have a Soekris crypto card (hifn driver) in a box that I don't have immediate access to. Is there some way to disable the card w/o rebooting the machine? I know I could take the driver out of the kernel or force it not to load, but that requires a reboot that I'd like to avoid if possible. hifn is currently compiled into the kernel so I can't do a kldunload either. That was the first thing I thought of, but apparently today is not my lucky day. Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: twa kernel panic under heavy IO
Vinod Kashyap wrote: Under 'Release Notes to View', select 'release_Release_Notes_Web', and you will get to a page which lists the version of each individual component that's part of the release, among other things. :) I would have known that if Firefox wasn't barfing on PDF's right now, or if I had bothered to boot my laptop (OSX). The Release Details section has a note that reads Linux and FreeBSD drivers are bundled with firmware 2.08.00.003. What does that mean? Do the drivers in 5-stable have a copy of the firmware embedded in them? Is the driver going to try and downgrade my firmware? The 9.2* versions are compatible. There are small incompatibilities if you are mixing 9.1* and 9.2*. And since we're here...is there any reason to update to 9.3 if I only have a 9500S? Good to know. Thanks for the quick reply. FWIW I went with 3ware because I saw somewhere that a 3ware person was supposedly on this list. Glad to see it wasn't a rumor. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Jail to jail network performance?
Robert Watson wrote: Last I checked, MySQL used solely TCP and UNIX domain sockets for communication, and not System V IPC. I believe PostgreSQL, however, used System V IPC. For some reason I was thinking that domain sockets and System V IPC were the same thing. Now I know better. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Jail to jail network performance?
Ok, here's what I've decided. But first, thanks for all of the help. Currently the MySQL databases are on a seperate RAID volume, and I'd like to keep it that way for performance purposes. In general I want to avoid putting anything on the raid that isn't a database. I don't want the raid volme to get hit for both database access and regular httpd/system use. In order to make a hardlink to the mysql socket it would have to be on the same volume as the httpd jail, which would then mean both jails have to be on the raid volume, which is what I want to avoid. However, if mysql isn't jailed it has access to both system and raid volumes and can put it's socket someplace accessible to the httpd jail. Since I've already set mysql to only accept domain socket connections I can probably get away without putting it in a jail. So I've decided to jail httpd and friends and leave mysql running in the host environment. I would have liked to use Robert Watson's suggested socket brokering daemon, and I stumbled on socat which appears to do the trick. But as far as I can tell socat just copies between two sockets, which seems like it might have performance issues. Albeit less so than using TCP sockets. Ideally I would like a daemon like socat that can connect/merge two sockets into one, effectively creating a direct connection and eliminating a copy. But AFAICT that isn't possible with the current interface. I don't know enough about the kernel to know if such a thing is even possible, but intuitively it seems like it should be. If somebody where to make socket merging possible, or tell me how to do it, I would be happy to write the daemon to make use of it. Until then I'm using an unjailed mysql. Thanks for the help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Jail to jail network performance?
Robert Watson wrote: There are several ways you can do it, but they generally fall into two classes of activies: (1) Modifying the name space exclusion assumption for jails, so that the file system name spaces overlap. One way to do this is with nullfs. (2) Having a daemon or tool that runs outside of the jail and brokers communication between the jails. One example might be a daemon that inserts a UNIX domain socket into both jails and then provides references to shared IPC objects between the two by request. Another example might be a daemon or tool that responds to a request and creates a hard link from a socket/fifo endpoint visible in one jail to a name visible in another jail, perhaps when setting up the jail. The former requires more infrastructure, but the latter is less flexible. The jail(8) man page says that if the MIB security.jail.sysvipc_allowed=1 processes inside a jail can use IPC to talk to stuff in other jails. How does that affect mysql in a jail? Do I need this enabled to run mysql? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Jail to jail network performance?
Robert Watson wrote: (1) Modifying the name space exclusion assumption for jails, so that the file system name spaces overlap. One way to do this is with nullfs. nullfs looks interesting. I was thinking about sharing files between jails using NFS, but it looks like nullfs would do the trick with better performance. Although the bugs section of the man page for mount_nullfs is rather scary. Does anyone have any experience with it? Does it actually work? If the point here is to make /tmp/mysql.sock show up in another jail's file space, can I use a symlink instead? Can a jailed process see the target of the symlink? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Jail to jail network performance?
I have a 5.4-S box running apache2 that's serving data from mysql running on the same box. I'm thinking about putting both in seperate jails, partly for security and partly for practice. Would this impact network performance between the two? Currently the mysql connection is using localhost which I understand to be faster than a network socket. Does jail-to-jail traffic use the same mechanism? or something else? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Odd rm behavior on 5.4-S with 3ware raid
The machine is an amd64 running 5.4-S with a 3ware 9500S-12 card. I wrote a test script to fill up the raid array with lots of files, and it did just that. Afterwards I did a 'rm *' to clean out the test files and naturally checked the results with ls. All the files were gone. For some reason, after waiting a few seconds, I did ls again. Some of the files had magically reappeared. After a few more seconds, more files were back. Its still happening as I type this. The drive lights are flashing wildly, but I kind of expected that. df is also showing that the array is filling back up. Any ideas? Is my computer possessed? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Odd rm behavior on 5.4-S with 3ware raid
heh...typed too fast. It appears that my array filling script didn't die when I told it to, or maybe an older instance was still running. Hard to say for sure, but it was still running and when I made room on the array it started filling it up. Just like it was supposed to. Sorry for the trouble. Nothing to see here...move along. :) Brandon Fosdick wrote: The machine is an amd64 running 5.4-S with a 3ware 9500S-12 card. I wrote a test script to fill up the raid array with lots of files, and it did just that. Afterwards I did a 'rm *' to clean out the test files and naturally checked the results with ls. All the files were gone. For some reason, after waiting a few seconds, I did ls again. Some of the files had magically reappeared. After a few more seconds, more files were back. Its still happening as I type this. The drive lights are flashing wildly, but I kind of expected that. df is also showing that the array is filling back up. Any ideas? Is my computer possessed? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install from USB flash drive? Sort of...
Oliver Fromme wrote: Brandon Fosdick [EMAIL PROTECTED] wrote: [...] Determined to press on I tried the install from existing file system option, w hich I had never noticed before. That didn't work since I had no idea what path to give it, or even if the flash drive had been mounted. It depends on the FreeBSD version. Older versions mounted it on /dist, if I remember correctly, but newer ones mount it directly on /. So assuming the flash is mounted as /, what path do I give sysinstall when it asks? I've tried /, /dist and /mnt. None worked. You can copy directly from the ISO to your flash drive, excluding the things that you don't need (i.e. packages). There's no need to make an additional copy on your HD. For example: # cd /cdrom; find . | grep -v /packages | cpio -dump /flash That worked much better. Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install from USB flash drive? Sort of...
Oliver Fromme wrote: It depends on the FreeBSD version. Older versions mounted it on /dist, if I remember correctly, but newer ones mount it directly on /. I just tried booting to the flash with a cdrom installed so I could run the fixit shell. Apparently the cdrom is mounted on /dist and the flash isn't mounted at all. So either sysinstall isn't recognizing the flash as installation media or its favoring the cd when its present. How can I tell which is happening? How do I get it to mount the flash automatically? I also tried using the fixit shell to mount the flash to /mnt but that didn't work either. However, I can install from cd after booting to flash, but that defeats the purpose. And since the crazy bios on my motherboard renumbers the ata devices I end up with a useless etc/fstab after removing the cd-rom drive. I love the way sysinstall congratulates me for installing FreeBSD after it fails to find the installation media. Its just so friendly. :P ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Install from USB flash drive? Sort of...
So I had this brilliant idea that I was going to install FreeBSD on my new amd64 system using a 512MB flash drive since I didn't feel like digging out a CD-ROM. I ended up installing from CD anyway, but I thought I'd share my experience in case anyone else knows how to do this. My first thought was to fdisk and newfs my flash drive to make it look like a bootable drive. I had successfully made a win98 boot floppy on a smaller flash drive so it seemed like a natural place to start. Surprisingly, that actually worked. I was able to boot from the device, but naturally there wasn't anything else on the device. So, then late at night when I wasn't thinking clearly I proceeded to do a make release with the intent of copying the release onto the flash drive. The next morning it occured to me that I probably could have just copied the files from an install CD. Oh well. The drive booted fine and went into sysinstall and everything seemed to work in the normal fashion. However, I ran into a problem when it came time to select the installation media. Obviously I couldn't select the CDROM/DVDROM option (although I tried it anyway, just for kicks) so I tried to do an FTP install. Oddly, the network chip wasn't detected, even though it is recognized when booting from a CD. Perhaps there was something wrong with the release I had rolled. Determined to press on I tried the install from existing file system option, which I had never noticed before. That didn't work since I had no idea what path to give it, or even if the flash drive had been mounted. I suspected it hadn't been, so I proceeded to the emergency holographic shell, at which point I realized just how useless that feature is if you don't have a CD in the drive. So I returned to the network install idea. Thinking that maybe I had built a bad release I decided to try copying from the disc1 iso. The iso is listed at 515MB which is almost small enough. The packages are about 70MB and they're not strictly necessary so I thought it would work. So I mounted the iso and proceeded to copy the files out, since iso's mount read only and I needed to delete stuff. To my surprise it turned into 1.1GB when copied onto a real filesystem. Obviously that's a problem. The handbook (Section 2.13.1) says that the boot-only iso has everything needed to do a network install. So I downloaded that, mounted it and copied it to the flash disk. It boots and recognizes the NIC. Now I can do a network install. Finally. But that's a really slow way to do an install. There has to be some way to get sysinstall to install from a flash drive. Right? So now I have questions... How do I use a USB drive as installation media? How do I get sysinstall to recognize the USB drive as a fixit disc/holographic shell? How does an ISO manage a 50% compression ratio? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Create 2.5TB file system on 5.4S?
David Magda wrote: There's the Bonnie and Bonnie++ file system testing programs. I believe one or both are in the Ports. Thanks. I'll take a look. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Create 2.5TB file system on 5.4S?
I recently dealt with the same controller, with a 3TB array. My solution is tons easier than dealing with gpt or breaking it up. So long as you don't need to boot from the raid, and you just want it as one big disk, forget partitioning it. newfs the device directly, and mount it directly. [EMAIL PROTECTED]:~$ df -h ... /dev/da0 2.6T182G2.3T 7%/d I just did a newfs on /dev/da0 and mounted it. Works /great/. No fuss. Did you just newfs /dev/da0? I think I tried that already without success, something about a bad superblock. I'll try it again tonight just to make sure. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Create 2.5TB file system on 5.4S?
Mikael Krantz wrote: I had the same problem with 8x400 disk on a areca hardware sata card in fbsd 5.4-stable. Soo I just did newfs -m 2 -U -O 2 -i 262144 /dev/da0 with those options as I needed as much space as possible. Ok, so that appears to have worked. Is there any benefit to doing this? Or using gpt? Any downsides? Which method will produce the fewest problems long term? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Create 2.5TB file system on 5.4S?
dpk wrote: Whatever you end up doing (we used auto-carving here, had to unfortunately) be sure to test the partitions fully before proceeding. Any suggestions? Are there specialized raid test suites or should I just write a script that writes/deletes a lot of files? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: firefox, Xorg and crash.
Firefox keeps taking X11 and then the whole machine with it. It requires a hard reset as even pinging the machine does not work. Only Firefox seems to be doing this. Does anyone else have the same problem? Anyone knows how to solve/debug this? I've been having this problem for about a month now. The machine doesn't always lock up completely. The times when I can login remotely top shows Xorg using the 97-98% cpu time. Killing Xorg drops to the console, but its still unresponsive and I have to reboot. Once or twice this has happened without firefox running so I'm thinking it might be an Xorg problem. I've also noticed that sometimes shortly before the lock up fonts start being replaced with red boxes when a window is refreshed. I've tried new/more RAM but that didn't seem to help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Create 2.5TB file system on 5.4S?
Chuck Swiger wrote: If it's going to be a big database server, why aren't you using all of those drive spindles to help break up the I/O load? :-) I have other drives for other things, but I still end up with a single large volume. Thanks for the suggestion. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Create 2.5TB file system on 5.4S?
Now that my shiny new 9500S is installed and not fighting for IRQs, I've created and initialized a ~2.5TB array using the bios utility. So the next step is mounting the new array. I naively tried following the regular handbook instructions for adding a new drive and failed miserably. And after googling a bit I now know why, and realized that I knew why before, but I was being stupid. I've seen a few mentions of using gpt(8) and some vague references to using dedicated mode. But I haven't seen anything that says this is the Right Way to do it. So...what's the proper way to make a large file system? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Create 2.5TB file system on 5.4S?
Jon Dama wrote: Where exactly did you run into trouble? I'm guessing you made the array, you have a device for it in /dev but ran into problems (expected) using fdisk or bsdlabel. Yup, that's exactly what happened. I ended up with a 0.5TB partition. At least, thats what df said. A few minutes ago I tried using gpt(8) to create a partition and then I newfs'd the whole thing using the defaults. It appears to have worked, but I have no idea if I did it right or if there's a better way. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Create 2.5TB file system on 5.4S?
Erik Stian Tefre wrote: You can avoid the problem by splitting the array up in partitions smaller than 2TB each. (I know this does not answer your question, but it simplifies things, and it works for me(TM)... :-) :) Thanks, but I thought of that already. This is going to be a big database server and I don't want to have to deal with splitting the database across two partitions. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
Darren Pilgrim wrote: I believe the IEEE was involved. :) That explains a lot :) IRQ sharing is a known issue with many RAID cards and even some gigabit ethernet cards. It seems to correlate to cards that push the performance limit of the bus. And here I am with both a RAID card and a gigabit ethernet chip. Fortunately the slot swap seems to have sorted everything out. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
IRQ conflict between twa0 and skc0
So I'm having yet another problem with my AMD64x2/nforce4 system. Of the two builtin NICs 5.4-S is only recognizing the marvell gigabit chip, which wasn't a problem until I added a 3ware 9500S-12. With the 3ware card in the network doesn't work, take it out and it works. From the dmesg bits below it looks like both twa0 and skc0 are trying to use irq 18 and twa0 is winning. I have the bios set to handle pnp stuff so I don't know whats going on. Any suggestions? --- pcib1: ACPI PCI-PCI bridge at device 9.0 on pci0 pci1: ACPI PCI bus on pcib1 3ware device driver for 9000 series storage controllers, version: 3.50.00.017 twa0: 3ware 9000 series Storage Controller port 0xac00-0xacff mem 0xfd00-0xfd7f,0xfcfff000-0xfcfff0ff irq 18 at device 6.0 on pci1 twa0: INFO: (0x15: 0x1300): Controller details:: 12 ports, Firmware FE9X 2.06.00.009, BIOS BE9X 2.03.01.051 pci1: display, VGA at device 7.0 (no driver attached) skc0: Marvell Gigabit Ethernet port 0xa800-0xa8ff mem 0xfcff8000-0xfcffbfff irq 18 at device 10.0 on pci1 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:01:29:fc:8c:59 miibus0: MII bus on sk0 e1000phy0: Marvell 88E1000 Gigabit PHY on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto skc0: couldn't set up irq e1000phy0: detached miibus0: detached sk0: detached device_attach: skc0 attach returned 22 pci0: bridge at device 10.0 (no driver attached) --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
Mike Jakubik wrote: The easiest thing would probably be to disable the onboard sk card, and put in an em (intel gigabit card). The marvell chipset and driver is known to be problematic. I had thought of that, but the motherboard only has 2 non-express PCI slots and they're both currently filled by the video card and the raid card. I could take the video card out, but then I wouldn't be able to see what I was doing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
Mike Jakubik wrote: Forgot to mention. You can always buy a cheap pciE video card :) You're a big help :) I was fiddling and I noticed something odd. Previously, the ESCD screen at boot showed the raid controller and network controller both at IRQ 5. The dmesg I sent before showed both at IRQ 18. That seemed odd to me. I also noticed that unused drive channels were being assigned IRQs so I disabled them in the BIOS. The idea being to free up an IRQ and maybe one of the controllers would use it. Now the ESCD table shows both the raid and the network on IRQ 10 and dmesg still shows them at IRQ 18. This seems screwy to me, but I have no idea what it means. Now that I know both IRQs 10 and 18 are useable, is there some way to force the drivers? Aren't there some boot hints that handle this? Or was it done in the kernel config. I can't remember. BTW, this is all with the stock SMP kernel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IRQ conflict between twa0 and skc0
Darren Pilgrim wrote: Try switching slots with the RAID and video cards. It's silly, but then so is PCI interrupt routing. Unbelievable. Who ever wrote the PCI spec should have been shot. I switched the cards and now the network card is sharing an interrupt with the video card, but neither seems to mind. More importantly it isn't sharing with the raid card and they all appear to be happy. Thanks, that was a big help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing 5.4-S on nvidia raid1?
Christian Brueffer wrote: It doesn't work because the ataraid code in 5.4 doesn't understand the NVIDIA MediaShield metadata format. It is supported on HEAD and the RELENG_6 branch that will result in FreeBSD 6.0-RELEASE. Take a look at the ataraid(4) manpage in HEAD and RELENG_6 for more information on how software RAID works and which metadata formats are supported. That explains it, thanks. Any idea if/when the relevant code will be MFCd? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Installing 5.4-S on nvidia raid1?
I have a DFI Lanparty nf4 Ultra-D with two 80GB drives configured as a raid1 array. The bios lists the array as scsi-0 and claims that its healthy. When I boot from the disc1 cd and try to do the usual install the only device options I'm given for fdisk are ad4 and ad6, which obviously aren't a scsi array. Just the be sure I ran dmesg in the holographic shell and it shows ad4 and ad6 as the two 80GB drives. So how do I install to the raid array? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SMP support maturity? AMD64x2 or FX-57?
Thanks for all of the replies. It sounds like SMP is doing better than I thought so I've decided to go with the dual core option. Thanks for the help ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
SMP support maturity? AMD64x2 or FX-57?
SMP support in FreeBSD seems to be a perpetually favorite feature to gripe about, but every release seems to say that its getting better. I'm about to build a new server and am trying to determine if I should go with dual procs or just a single. The AMD64x2 is slightly cheaper than the FX-57 so I'm leaning that way, but it would be a rather pointless savings if SMP isn't well supported. So, is SMP in -STABLE ready for primetime? Can it really make use of two processors? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACL not supported on 5.4?
Björn König wrote: Hello Brandon, I get the same error messages if ACL are not enabled. I just want to make sure that you didn't overlook the part of the handbook where it says that you have to enable it. It seems that's exactly what happened. Thanks for pointing it out. By the way, the option -k won't work on non-directories at all, see also the manpage of setfacl. Ok, then the handbook needs fixing because it says The -k flag will remove all of the currently defined ACLs from a file or file system, which would seem to imply that it works on files. Naturally I would have known better if I had read the man page, but I didn't. Are handbook bugs handled through send-pr like everything else? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ACL not supported on 5.4?
I have a 5.4 install that I'm trying to use to experiment with ACL (and extended attributes). Handbook section 14.12.1 (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/fs-acl.html) has a few sample commands that I tried running. But I get operation not supported, like so: 17:02 [EMAIL PROTECTED]touch test 17:03 [EMAIL PROTECTED]ll test -rw-r--r-- 1 bfoz user 0 Jun 10 17:03 test 17:03 [EMAIL PROTECTED]getfacl test #file:test #owner:1001 #group:1001 user::rw- group::r-- other::r-- 17:03 [EMAIL PROTECTED]setfacl -k test setfacl: acl_get_file() failed: Operation not supported 17:03 [EMAIL PROTECTED]setfacl -b test setfacl: acl_get_file() failed: Operation not supported I tried doing the above as root, but the result was the same. I'm pretty sure this was a fresh install of 5.4 (its been awhile since I made this box) so it should have UFS2 by default and the kernel does in fact have UFS_ACL compiled in. What else do I need to do? How do I check to see if I really do have UFS2? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: WIFI access software
Jeff Seeman wrote: I have a client who has 3 restaurants and wants to provide wifi access to the customers. He wants to be able to control who and when it can be accessed. He is not planning on charging for the access at the moment but certainly would like that ability. I want to use freebsd, but can not find a software pkg that will allow me to do this. Does anyone have an idea or better yet implemented something like this? If you don't absolutely have to use FreeBSD there are a number of hacks to wifi routers that will do what you want. The Linksys series seems to be the most popular. Google for things like HyperWRT, OpenWRT, eWRT, DD-WRT, Sveasoft (they're getting evil though). I think DD-WRT uses chillispot that someone else mentioned. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
putc to a clist with no reserved cblocks
I'm working on a small app that talks to a device with a FTDI USB to 232 chip in it. ucom and uftdi seem to detect it just fine. But calls to read() hang and I'm getting messages like putc to a clist with no reserved cblocks in my kernel logs. Any idea what this is? In a previous post (subject: ucom and sio) I asked about a similar problem with read() hanging on prolific chips. The fix involved ignoring modem control lines with CLOCAL, but that doesn't appear to do the trick here. Oddly, the exact same software/hardware works fine on my powerbook. What am I missing? I can send code if its needed. Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: putc to a clist with no reserved cblocks
Daniel O'Connor wrote: On Mon, 28 Feb 2005 11:14, Brandon Fosdick wrote: I'm working on a small app that talks to a device with a FTDI USB to 232 chip in it. ucom and uftdi seem to detect it just fine. But calls to read() hang and I'm getting messages like putc to a clist with no reserved cblocks in my kernel logs. Any idea what this is? What version of FreeBSD? Oops, sorry about that. 17:14 [EMAIL PROTECTED]uname -a FreeBSD poseidon.bfoz.net 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #6: Sat Feb 26 21:32:38 PST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/POSEIDON i386 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
AGP, AMD and FreeBSD
I'm getting this message when starting X with the nvidia driver... NVRM: AGP cannot be enabled on this combination of the AMD CPU and OS kernel NVRM: kernel upgrade recommended. NVRM: AGP cannot be enabled on this combination of the AMD CPU and OS kernel NVRM: kernel upgrade recommended. It always comes up in pairs like that. It obviously has something to do with the nvidia drivers, but it seems to have something to do with the OS too, so that's why I posted it here and not on ports. I've been seeing this for many months now and upgrading the kernel doesn't help. Xorg and XFree86 produce the same behavior. Any ideas? I'm running a Sempron 3100+ on a DFI K8M800-MLVF mboard with a GeForce MX4 and agp is compliled into the kernel. The nvidia driver was compiled with both freebsd_agp and acpi support. Here's uname -a: FreeBSD dvr.bfoz.net 5.3-STABLE FreeBSD 5.3-STABLE #5: Sun Jan 9 15:41:54 PST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DVR i386 Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ucom and sio
M. Warner Losh wrote: In message: [EMAIL PROTECTED] Brandon Fosdick [EMAIL PROTECTED] writes: : Judging from the man page, ucom is limited to acting like a tty with no : support for sio. Is this true? Is there some magic config bit somewhere : that will enable hidden sio support? Ummm, I don't know what you are asking here. ucom supports all the rs232 stuff w/o problem. I use it all the time with my phone to dial into the network. Well, then I must be doing something wrong. The man page for ucom would seem to indicate that it is tty only... The ucom driver attaches to USB modems, serial ports, and other devices that need to look like a tty. The ucom driver shows a behavior like a tty(4). This means that normal programs such as tip(1) or pppd(8) can be used to access the device. If I use tip it works fine. But if I try to write a C program that opens the device it hangs on open, unless I set it to non-blocking. Then open returns and I set it back to blocking then try a read or a write. read() blocks regardless of whether any data has been sent by the other device (a terminal app on my palm pilot for debugging purposes) and write() blocks without sending anything. If I set the device to be non-blocking read() will return the data that was sent by the other device, but write() will still block. Oddly, I get the same behavior on my powerbook, so I thought the adapter was defective. But it works with terminal apps on freebsd, osx and windows, so I'm pretty sure its working. I have no idea what I'm doing wrong though. Once I figure out where I put the code for this thing I'll send the test program I've been using. I always seem to lose something when I travel... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ucom and sio
Daniel O'Connor wrote: Is it blocking waiting for carrier detect to come up? Try using the cuaNN device instead. The software in question worked fine using a cuaNN device until said device died. Somebody else mentioned that I could set the device to ignore the carrier detect signal. How do I do that? Is it a flag to tcsetattr() or some kind of ioctl? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ucom and sio
Daniel O'Connor wrote: ie setting CLOCAL. That fixed it, thanks. Is it worthwhile to change the ucom man page to not imply that it only works for tty? That led me astray. I think I would have eventually found CLOCAL if I hadn't stopped looking. Or am I the only one that finds it misleading? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ucom and sio
Judging from the man page, ucom is limited to acting like a tty with no support for sio. Is this true? Is there some magic config bit somewhere that will enable hidden sio support? I have some old software that talks to some old hardware over rs232 (using cuaa) and the builtin 232 port just died. I'm trying to get a Bafo BF-810 working in raw mode but haven't had much luck (open()'s and write()'s block, unless non-blocking is set, but then they return without doing anything). Any suggestions? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Beastie/ how about Mozilla?
Scott Long wrote: Please drop the religious argument. My decision was based on months of experience, not a single email. I'm most concerned that we are allowing ourselves to be so distracted by it. If you don't like it, don't use it. If you like it, use it. If you don't like those that don't like it, please keep it to yourself. So, what was the actual reason for the commit? Negelcting, for a moment, your claim to have a real reason, which I don't doubt, its just that we/I don't have it at hand...this thread was started by religious issues. So either the religious argument is relevant in this thread or we declare that religion has no place here (and therefore this thread shouldn't have been started the way it was). I vote for the latter. Now to add my rant... To the orignal poster: in my experience, this group doesn't make design decisions based on religious issues, or anything other than technical/practical issues (ideally). For future reference, the best way to get something changed around here is to present a good solid technical reason for the change. As you just saw, arguing for a design change based on delicate sensibilities is not looked well upon by the community. Hopefully it was just a mistake and not the attempt to add religiosity to our fine OS that I'm sure some people took it as. Hopefully Scott will come up with a good argument for the loss of the boot menu so that I don't look like a liar :) To everyone else: IMHO, The proper response to this would have been pointing out that the request wasn't based on anything that this group uses to make design decisions. Despite how strongly we all felt the looming spectre of religiosity, the bashing was innapropriate. And it was certainly below any reasonable standard of our culture. -- Brandon Fosdick http://www.terranspace.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ftp.freebsd.org
Jack Raats wrote: At this moment I cann't connect with ftp.freebsd.org. I've had the same problem all day. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cannot boot system built today
I've filed PR i386/69218 for this problem. Lee Harr wrote: Wanting to test the -RC, I ran through the updating procedure this evening, but I am unable to boot the resulting kernel. The system hangs trying to detect something with the disks... This is one of those troublesome nvidia chipset A7N8X motherboards. I do not have a serial console set up, but here are the last few lines of a verbose boot... if I need to set up a serial line for more from the verbose boot, let me know... I can easily post a regular dmesg from my working kernel (built from March 5th sources) if that will help. (probe2:ata1:0:0:0): INQUIRY.CDB: 12 1 80 0 ff 0 (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 (probe2:ata1:0:0:0): Invalid field in CDB (probe2:ata1:0:0:0): TEST UNIT READY.CDB: 0 0 0 0 0 0 (probe2:ata1:0:0:0): NOT READY asc:3a,0 (probe2:ata1:0:0:0): medium not present (probe2:ata1:0:0:0): INQUIRY.CDB: 12 1 80 0 ff 0 (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 (probe2:ata1:0:0:0): invalid field in CDB at this point it stops. _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cannot boot system built today
Doug White wrote: Also, Lite-on drives are known to have buggy firmware. Does removing the CDROM drive make it boot? No. It hangs on whatever the last drive is. For example, if I have a hard drive and a cd-rom it displays ad0... for the hard drive and then will hang on the cdrom (after displaying acd0...). With just the hard drive it hangs on the drive. If I try a hard drive and two cd-roms it hangs on the last cdrom drive. I haven't yet determined if last is equivalent to slave. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cannot boot system built today
Lee Harr wrote: So, now... what could be the difference that allows the cd to boot, but not the same kernel booting from the hard drive? Do we know that the cd has the same kernel? Could it be possible that the install cd's kernel isn't GENERIC? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ftp/fetch command not understood on stable and current
On both stable and current I'm having problems getting ftp or fetch to connect to ftp servers (fetch can't connect to anything). I'm behind a firewall but the ftp ports are open and I'm sitting next to an HPUX box that doesn't have the same problem. All of the output below came from a 5.1-R box: 13:16 [EMAIL PROTECTED]uname -a FreeBSD mse.fbm.lmms.lmco.com 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Here's what happens when I ftp to ftp.freebsd.org and try to do 'ls' (or anything other command for that matter)... --- Trying 2001:4f8:0:2::e... ftp: connect to address 2001:4f8:0:2::e: No route to host Trying 204.152.184.73... Connected to ftp.freebsd.org. 220 freebsd.isc.org FTP server ready. Name (ftp.freebsd.org:bfoz): anonymous 331 Guest login ok, send your complete e-mail address as password. Password: 230- 230-You have reached freebsd.isc.org/ftp.freebsd.org. 230- 230-insert some funky ASCII art here 230- 230-This server is operated by Internet Software Consortium (ISC), 230-on behalf of the FreeBSD Project, and is serving the full 230-FreeBSD FTP archive via IPv4 and IPv6. 230- 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. ftp ls 500 command not understood 227 Entering Passive Mode (204,152,184,73,184,121) --- At this point it sits there for a minute or so and then either provides the directory listing or disconnects due to inactivity. If it works I get: --- 200 PORT command successful. 150 Opening ASCII mode data connection for directory listing. total 8 drwxrwxr-x 3 root root 512 Apr 17 2003 pub 226 Transfer complete. ftp --- Odly, it doesn't actually go into passive mode acording to status: --- ftp status Connected and logged into ftp.freebsd.org. No proxy connection. Gate ftp: off, server (none), port ftpgate. Passive mode: off; fallback to active mode: on. Mode: stream; Type: binary; Form: non-print; Structure: file. Verbose: on; Bell: off; Prompting: on; Globbing: on. Store unique: off; Receive unique: off. Preserve modification times: on. Case: off; CR stripping: on. Ntrans: off. Nmap: off. Hash mark printing: off; Mark count: 1024; Progress bar: on. Get transfer rate throttle: off; maximum: 0; increment 1024. Put transfer rate throttle: off; maximum: 0; increment 1024. Socket buffer sizes: send 32768, receive 65536. Use of PORT cmds: on. Use of EPSV/EPRT cmds for IPv4: on (disabled for this connection). Command line editing: on. Version: lukemftp 1.6-beta2 ftp --- That's not too bad, I can deal with waiting a few minutes for results, but about half the time I get kicked, which is annoying. My biggest problem is with fetch, it just can't get to anything at all which makes installing ports a real PITA. I'm getting a Host not found error but nslookup seems to think my DNS server is working just fine since I can always lookup the hosts I'm trying to connect to. I know the files are there because I can see them with ftp (when it works). A few example fetch runs... --- openmotif-2.2.2.tgz doesn't seem to exist in /usr/ports/distfiles/openmotif. Attempting to fetch from ftp://openmotif.opengroup.org/pub/openmotif/R2.2/tars/. fetch: ftp://openmotif.opengroup.org/pub/openmotif/R2.2/tars/openmotif-2.2.2.tgz: Host not found Attempting to fetch from ftp://ftp.opengroup.org/pub/openmotif/R2.2/tars/. fetch: ftp://ftp.opengroup.org/pub/openmotif/R2.2/tars/openmotif-2.2.2.tgz: Host not found Attempting to fetch from ftp://ftp.kddlabs.co.jp/X11/openmotif/R2.2/tars/. fetch: ftp://ftp.kddlabs.co.jp/X11/openmotif/R2.2/tars/openmotif-2.2.2.tgz: Host not found Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/openmotif/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/openmotif/openmotif-2.2.2.tgz: Host not found Couldn't fetch it - please try to retrieve this port manually into /usr/ports/distfiles/openmotif and try again. --- 13:12 [EMAIL PROTECTED]fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages/All/nedit-5.3.tbz fetch: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages/All/nedit-5.3.tbz: Host not found 13:16 [EMAIL PROTECTED]nslookup ftp.freebsd.org Server: ddns2.lmms.lmco.com Address: 129.197.11.4 Non-authoritative answer: Name:ftp.freebsd.org Addresses: 204.152.184.73, 62.243.72.50 13:16 [EMAIL PROTECTED] --- Other, non-FreeBSD, unix boxes on the same network can connect just fine and I can't seem to find any significant configuration differences. Maybe I just don't know what I'm doing. Here's the status output from an HPUX box... --- [EMAIL PROTECTED]:/home/bfosdick2 ftp ftp.freebsd.org Connected to ftp.freebsd.org. 220 freebsd.isc.org FTP server ready. Name (ftp.freebsd.org:bfosdick): anonymous 331 Guest login ok, send your complete e-mail address as password. Password: 230-You have reached freebsd.isc.org/ftp.freebsd.org. 230- 230-insert some funky
Re: 4.9 Boot Hang when USB Devices Attached
Joe Kelsey wrote: I have a system running FreeBSD zircon.zircon.seattle.wa.us 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #20: Fri Sep 19 12:55:28 PDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZIRCON i386 When I upgraded to fix the OpenSSH problems, the system started hanging at boot time right after the USB/OHCI messages whenever I had devices plugged into the USB ports (mainly a USB mouse). Now, in order to boot, I have to unplug the mouse and wait for the system to pass the USB part of boot before replugging. There are several threads discussing this ATM. If you have an nforce2 board search for the thread with the subject fix/workaround for usb probe lockups on nForce2 mbs. Andrew Atrens posted a patch that worked for me. In the same thread Ian Dowse has offered a few other ideas to try. I haven't tried them yet. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Creative DI5631 pci modem on 4.5-R?
M. Warner Losh wrote: Where 0x12345678 is obtained from pciconf -l and 0x10 is the BAR. If you don't know the BAR, try 0x10, 0x14 and 0x18. None of the BAR values worked. In case anyone cares the type value returned by pciconf -l was 0x1507148d. However, I'd bet a good dinner that your Creative Labs modem is not a 16550 device. What would you like for dinner? Double or nothing if you can tell me how to make it work. :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Dangerously Dedicated
Cy Schubert - ITSD Open Systems Group wrote: In message [EMAIL PROTECTED], "David O'Brien" writes: On Sun, Nov 19, 2000 at 01:55:29PM +0100, Roelof Osinga wrote: Yesterday I installed the 4.2 RC1 in dangerously dedicated mode on a SCSI disk I had lying around. Why did you choose a "dangerously dedicated" install? "dangerously dedicated" might go away in the future (as it doesn't leave space enough space for boot0). Unless the normal slice configuration won't work for you, there really is no good reason to use "dangerously dedicated". If/when dangerously dedicated goes away, will there be special provision for Zip and Jazz disks? Or, will we need to put an fdisk style partition table on Zip and Jazz disks, then slice them with disklabel? So we're going to be stuck with MS style partitions on machines that only run FreeBSD? I don't like this idea. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Kernel Panic with Stable
I cvsup'd on friday (8 Sept), did the whole make world/kernel routine thats in UPDATING, rebooted and the kernel panics with "kmem_malloc(very large negative number):kmem_map too small: 3592192 total allocated". I tried booting off the generic and .old kernels but that doesn't work either (same error). So now I'm totaly stumped and I can't even boot the machine. Help?! -Brandon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Kernel Panic with Stable
Brandon Fosdick wrote: I cvsup'd on friday (8 Sept), did the whole make world/kernel routine thats in UPDATING, rebooted and the kernel panics with "kmem_malloc(very large negative number):kmem_map too small: 3592192 total allocated". I tried booting off the generic and .old kernels but that doesn't work either (same error). So now I'm totaly stumped and I can't even boot the machine. Help?! No laughing... The great thing about posting to the list is that you find your errors right away. :) Back in the day when the kernel building system was more insane and installed new kernels as $KERNELNAME I had changed my /boot/loader.conf to load the right kernel. It turns out that this machine hadn't been rebuilt since those days, so...when friday's kernel was installed as /kernel the machine kept booting off of /TUNGSTEN and I didn't even notice. On top of that kernel.GENERIC was so old that it didn't work either. I guess I should remember to build a new generic kernel when crossing releases. :) Sorry for the waste of bandwidth. -Brandon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: New kernel with its ATA drivers damages the filesystem
Thomas Köllmann wrote: Grigoriy Strokin wrote/schrieb (Friday, March 31, 2000): | While the bug wiping out filesystems on machines with Apollo MVP3 when ATA | driver is in UDMA mode is being fixed, I suppose there at least should be some | note added to /usr/src/UPDATING, so that another users do not loss | all their data and have to reinitialize /usr and restore it from backup, as I | had to do? | | Something like that: | | If you use the Apollo MVP3 chipset, it is STRONGLY | recommended that you disable the use of DMA mode in ATA drivers | BEFORE you try to boot the system after `make installkernel'. | Add the following line: | /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio | to the very beginning of your /etc/rc, | ~root/.profile and ~root/.login. | Be warned that if you don't disable the DMA mode, | all your filesystems may be corrupted because | of a bug in the driver that is still being fixed. | Please excuse if this was mentioned before (I did not follow this thread very closely), but isn't _not_ using options ATA_ENABLE_ATAPI_DMA enough as a measure of precaution? This is from LINT: # ATA_ENABLE_ATAPI_DMA: enable DMA on ATAPI device, since many ATAPI # devices claim to support DMA but doesn't actually work, this is # not enabled as default. Gruß - Thomas I missed the first part of this thread but I wish I hadn't cause my filesystem has been trashed twice in as many days. The first time I was doing 'chown -R' and the kernel paniced, rebooted to lots of fsck errors. Not only was the directory I was chown'ing trashed, but several others as well (/usr/src, /usr/ports). Then second time I was doing 'rm -r' and the same thing happened, but I lost most of my home dir too. I have a P3-600 on an Asus P3B-F with a Maxtor 20GB HDD(UDMA/33). Everything worked fine under 3.4. Thanks, Brandon -- [EMAIL PROTECTED] "Lead, follow, or get run over" "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: /sbin/dhclient-script and llinfo error
David O'Brien wrote: On Tue, Dec 07, 1999 at 11:23:54AM -0500, Brandon Fosdick wrote: I asked the same question abot a month ago and didn't get an answer. A quick search of the archives will find some others with the same problem. It seems to I got the report, but got busy and forgot about it (as it has never caused me problems). Let me try to revisit the patch for 3.4. -- -- David([EMAIL PROTECTED]) Thanks. -- [EMAIL PROTECTED] "Lead, follow, or get run over" "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
