Re: problem with sound
Hi, All! I can add to this ever so exceedingly slightly ... it occurs on 4.6-RC (and did on 4.5-Release IIRC ... anyone confirm?) for Alpha. Dex On Tue, 2002-05-28 at 15:12, Sean Kelly wrote: > I have experienced this as well ever since supping to 4.6-RC as of around > May 18th. Unlike Vladislav, I am not using modular sound but instead have > pcm built into my kernel. Other than that, I have little more to add. > Sound works for a while, but then randomly it seems as if the device is > never released after being used by something, thus resulting in Device busy > until my next reboot. > > FreeBSD Audio Driver (newpcm) > Installed devices: > pcm0: at io 0xcc00 irq 10 (4p/2r/0v channels duplex) > FreeBSD edgemaster.zombie.org 4.6-RC FreeBSD 4.6-RC #0: Sat May 25 20:31:13 CDT 2002 >[EMAIL PROTECTED]:/usr/obj/usr/src/sys/EDGEMASTER i386 > > On Mon, May 27, 2002 at 01:12:14PM +0300, Vladislav V. Zhuk wrote: > > Hi! > > > > After upgrading fbsd from 4.1.1 to 4.5 appears problem > > with sound: some times after reboot sound work properly, > > but later device dsp locks: > > > > $ play -d /dev/dsp0.2 -v 4 /usr/ftp/pub/wav/TEST.WAV > > sox: Can't open output file '/dev/dsp0.2': Device busy > > > > $ fstat /dev/dsp > > USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME > > > > lsof don't found who lock /dev/dsp too. > > > > PS: > > 4.6-PRERELEASE FreeBSD 4.6-PRERELEASE #0: Thu May 9 10:01:54 > > > > from dmesg.boot about my sound card (aureal vortex 2 CARD=8830): > > pci0: (vendor=0x12eb, dev=0x0002) at 17.0 irq 7 > > > > driver from ports/audio/aureal-kmod: > > $ kldstat > > Id Refs AddressSize Name > > 15 0xc010 1da330 kernel > > 21 0xc1329000 21000bump_saver.ko > > 31 0xc1434000 14000linux.ko > > 41 0xc1485000 34000snd_au8830.ko > > 51 0xc14b9000 14000snd_pcm.ko > > > > With freebsd 4.1.1 sound works good > > > > What can I do ?? Who lock /dev/dsp?? > > -- > Sean Kelly | PGP KeyID: 77042C7B > [EMAIL PROTECTED] | http://www.zombie.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Hardware RAID vs vinum
Ok, time to trow my anecdotes in. As a warning, I work for Adaptec and have been very close to both its hardware and software RAID projects. Not all RAID controllers are created equal. Many factors play a role: cache size cache architecture onboard processor type and speed host<->processor communication interface IDE vs SCSI driver architecture (scsi vs block) parity acceleration engine battery backing for the cache failure recovery reliability RAID 0 and 1 are not particularly hard to do. Many software RAID implementations do it fairly well, in fact, and are pretty competetive with their low-end hardware-based counterparts in both speed and CPU utilization. Only on the higher end controllers can you see a difference, but that difference may not be worth the $800+ that they cost. Conversely, some RAID controllers on the market today can't even do RAID 0 or 1 well, and aren't worth the trouble. One good measure of hardware vs software RAID lies in looking at RAID 5 performance. RAID 5 will always be much faster with a hardware solution than a software solution. Calculating parity is a very repetitive task, and your CPU has better things to do with its time. Furthermore, if you happen to be writing chuncks of data that are smaller than the stripe size, the operation turns into a read-modify-write that is much better offloaded in hardware. A hardware-based solution can be even faster if it has an on-board parity calculation engine that is separate from the cpu. Another good benchmark is transaction thoroughput. This is often dictated by the cache size, queue depth of the card, and the caching algorithm used on the card. In software, you are limited by the max thoroughput of the underlying disk controller, plus the overhead of computing the data layout. You can work around this by using multiple controllers, but this really only helps if you are using SCSI controllers. IDE, being a single transaction protocol (except for the IBM tagged queueing drives, but they still aren't as fast as SCSI by a long shot), will never allow a high transaction rate for software RAID. Hardware RAID, on the other hand, can achieve very high tranaction rates if designed well. A controller that uses a block interface, large cache, and a top-down cache design can perform very well while having very low CPU utilization. SCSI-based controllers are going to perform the best, but even IDE-based controllers can do well, since the cache can insulate the host from the slowness of IDE. Sequential access benchmarks are typically poor comparisions. Unless your application is something like a streaming video server, these benchmarks do not even closely model a real-world scenario. In reality, all they are testing is the PCI and memory bandwidth of your system, neither of which stresses hardware or software RAID implementations. The exception is that if a hardware controller perfoms poorly on these tests, it's pretty much guaranteed to be a dog. Finally, there is reliability. The whole purpose of RAID is to protect your data from drive failures. No matter how well designed and coded a software RAID subsystem is, drive failures are disruptive and can cause unexpected behavior. The problem may not even manifest itself in the raid subsystem, but rather in the disk subsystem. Hardware RAID, on the other hand, is an integrated package and is usually very well tested. On most controllers, a drive failure may even go unnoticed by the host OS, with the controller quickly detecting the error and transparently doing the corrective actions. So the real answer to hardware vs. software RAID is, what are your requirements? You have to weigh cost, reliability, and the myriad of performance needs. Scott On Tue, May 28, 2002 at 10:50:20AM -0600, Jan L. Peterson wrote: > My experience may be contrary to others. > > My particular application got much much better performance with > software RAID (vinum) than with hardware RAID (HP 3-Si card a.k.a. AMI > MegaRAID). > > The application in question had about 16 Windows boxes accessing an SMB > filesystem (Samba on the FBSD box). These clients would be all over > the disk, accessing hundreds or thousands of different files at > different locations on the filesystem every second. Mostly reading, > but some writing as well. > > I got excellent performance out of the hardware raid with only about > three or four clients running, but when all sixteen were pounding on > the disk, throughput (measured with iostat/systat) was abysmal. > > Moving the disks to a Symetrics controller and vinum resulted in at > least tripple the performance. > > I accredited it to the fact that the hardware controller had a small > cache (32M) vs. the system main memory (1G), and that the system could > better schedule reads and writes as it knew more about where the data > was on the various disks. > > I guess what I'm sa
ssh root login
Hi all, I have a FreeBSD 4.5 Rel. machine up running fine. Now, on the console I can log in fine. Log ins via ssh only work for users other than root. How can I log in as root using ssh? I checked "hosts.allow" and it didn't look like there's any place to set such thing in "sshd_config" I am looking forward to hearing a solution. Thanks, Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ssh root login
On Tue, 28 May 2002, Daniel Geske wrote:
> I have a FreeBSD 4.5 Rel. machine up running fine. Now, on the console I
> can log in fine. Log ins via ssh only work for users other than root. How
> can I log in as root using ssh?
> I checked "hosts.allow" and it didn't look like there's any place to set
> such thing in "sshd_config"
Why not login and su for more accountability? If you really want root to
login over the network, change your sshd_config:
mike@mojo{mike}$ grep Root /etc/ssh/sshd_config
PermitRootLogin no
Change 'no' to 'yes' and HUP sshd if needed.
Later,
-Mike
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." --Benjamin Franklin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: ssh root login
On Tue, May 28, 2002 at 09:46:41PM +0200, Daniel Geske wrote: > Hi all, > > I have a FreeBSD 4.5 Rel. machine up running fine. Now, on the console I > can log in fine. Log ins via ssh only work for users other than root. How > can I log in as root using ssh? > I checked "hosts.allow" and it didn't look like there's any place to set > such thing in "sshd_config" > > I am looking forward to hearing a solution. > Thanks, > $ grep -i root /etc/ssh/sshd_config PermitRootLogin no $ -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org msg45817/pgp0.pgp Description: PGP signature
Re: Hardware RAID vs vinum
On Tue, 28 May 2002, Greg 'groggy' Lehey wrote: > This can only happen if there's something very wrong with the software > RAID-5, either the implementation or the configuration. One thing > that springs to mind is too small a stripe size. There's a myth going > around that this improves performance, when in fact it seriously > degrades it. Mind expounding on this topic? The people at BayDel would like to disagree with you -- they ship a RAID 3 box that has good performance. /me puts on daemon horns :) Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ssh root login
On Tue, May 28, 2002 at 09:46:41PM +0200, Daniel Geske wrote: > Hi all, > > I have a FreeBSD 4.5 Rel. machine up running fine. Now, on the console I > can log in fine. Log ins via ssh only work for users other than root. How > can I log in as root using ssh? > I checked "hosts.allow" and it didn't look like there's any place to set > such thing in "sshd_config" This question should be asked in freebsd-questions, not -stable. Look in sshd(8) and more carefully in /etc/sshd_config. Its "PermitRootLogin" you're looking for. -- Jonathan Chen <[EMAIL PROTECTED]> -- Opportunities are seldom labeled To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ssh root login
Thanks everybody for the replies. I will try to get su working for me. Sorry, couldn't tell whether this was for questions or stable. Thought about posting to newbies first. Maybe should've - next time. Greetings from Berlin Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: Swap_pager error
I would totally agree with this, and will try the read, thanks for the
suggestions. My feeling is that it is NOT physical disk or a problem
with the disk drives. My experience in the past is that if the RAID
controller cannot successfully read or write blocks from either drive in
the array, the array alarm will sound. The array controller shows no
problems at all with the disk, and I have no red lights indicating a bad
drive.
Just seems rather strnage. I'll try doing the dd later at a slower time
and let you know how I make out.
Thanks again!
--
Robert Blayzor, BOFH
INOC, LLC
[EMAIL PROTECTED]
A successful tool is used to do something undreamed of by its author. -
Johnson
> If you see it suddenly drop down in the middle of the dd
> operation and
> then pick up again the hard drive may have soft errors
> internally but
> is still able to finally retrieve the block. If the
> kernel ('dmesg'
> program and '/var/log/messages' log file) reports disk
> errors during
> your dd then you may have a problem with one or more drives.
>
> -Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Keyboard detection failure (~4.6-RC3)
Hi, I've been getting some very strange behaviour booting 4.6-RC (~24/05/2002) on my Tyan Thunder K7, dual Athlon non-MP 1.2Ghz, 1GB workstation. Roughly 50% of the time, I get the following error in dmesg: ... atkbd0: flags 0x1 irq 1 on atkbdc0 device_probe_and_attach: atkbd0 attach returned 6 ... Whilst the Num Lock LED remains on, the keyboard is effectively dead, and I am forced to hard reset the machine (I know of no alternative). The other 50% of the time the machine boots beautifully, and I just get the standard "kbd0 at atkbd0" message. I have had no problems under Windows NT/2000/XP, so I'm left to assume the fault is somewhere in BSD. I *have* tried to run FreeBSD on this machine before (around November last year), and I seem to recall I had a similar problem which I didn't report, so I don't think this is particularly new, but as it's gone unmentioned, and 4.6 is so close I thought it would be worth bringing up again. If you need further details, I'll be happy to provide (I'm not on FreeBSD atm). Yours, Robin Breathe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Server won't boot after recompile the kernel with ipfw support
Dear All, I just upgraded one of my FreeBSD server remotely from 4.3 current to 4.6 RC1 (I cvsup-ed from the freebsd-stable tree last night). The make buildworld, and make installworld worked just fine, and the new kernel configuration compiled successfully. But why after I recompile the kernel for the second time, with options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=10 according to http://www.freebsd.org/handbook/firewalls.html, the server can't be ping-ed anymore ? I did check the configuration using /usr/bin/config my-kernel, and it worked just fine, and there was no error in the make depend, and make stage. Does anyone has ever got the same problem ? May I know it A.S.A.P, because the server is a colocated one, and I need to give instructions to the person who is going to "fix" the server. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Server won't boot after recompile the kernel with ipfw support
On Tue, 28 May 2002, Irwan Hadi wrote: > Dear All, > > compiled successfully. But why after I recompile the kernel for the > second time, with > options IPFIREWALL > options IPFIREWALL_VERBOSE > options IPFIREWALL_VERBOSE_LIMIT=10 according to > http://www.freebsd.org/handbook/firewalls.html, the server can't be > ping-ed anymore ? > I did check the configuration using /usr/bin/config my-kernel, and it > worked just fine, and there was no error in the make depend, and make > stage. > Does anyone has ever got the same problem ? May I know it A.S.A.P, > because the server is a colocated one, and I need to give instructions > to the person who is going to "fix" the server. > Did you specify any of the firewall rules / configuration before rebooting? The default deny rules will keep you from connecting to the box until you set up new rules that will accept connections. You'll want to check and modify the firewall_ lines in /etc/defaults/rc.conf . The ipfw man page suggests being at the console when you enable the firewall for this precise reason. The way to fix this problem is to log in at the console (or have someone else do it for you) and add the following rule: ipfw add 100 allow ip from any to any This will open up the firewall, and allow you to connect. You'll no doubt want to delete that rule when you add your own custom rules. man ipfw(8) will help you when you get around to doing that. - Jeff Jirsa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ssh root login
On Tue, May 28, 2002 at 09:46:41PM +0200, Daniel Geske wrote: > Hi all, > > I have a FreeBSD 4.5 Rel. machine up running fine. Now, on the console I > can log in fine. Log ins via ssh only work for users other than root. How > can I log in as root using ssh? > I checked "hosts.allow" and it didn't look like there's any place to set > such thing in "sshd_config" > > I am looking forward to hearing a solution. > Thanks, > > Daniel > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message I, You can use option `PermitRootLogin yes' in your sshd_config but it may have some impact in machine security. You can login as a normal user and then "su -" or, better, "sudo ". Bye, Nuno Teixeira -- /* PGP fingerprint: C6D1 06ED EB54 A99C 6B14 6732 0A5D 810D 727D F6C6 */ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Server won't boot after recompile the kernel with ipfw support
On Tue, May 28, 2002 at 02:39:03PM -0600, Jeff Jirsa wrote: > On Tue, 28 May 2002, Irwan Hadi wrote: > > > Dear All, > > > > compiled successfully. But why after I recompile the kernel for the > > second time, with > > options IPFIREWALL > > options IPFIREWALL_VERBOSE > > options IPFIREWALL_VERBOSE_LIMIT=10 according to > > http://www.freebsd.org/handbook/firewalls.html, the server can't be > > ping-ed anymore ? > > I did check the configuration using /usr/bin/config my-kernel, and it > > worked just fine, and there was no error in the make depend, and make > > stage. > > Does anyone has ever got the same problem ? May I know it A.S.A.P, > > because the server is a colocated one, and I need to give instructions > > to the person who is going to "fix" the server. > > > > Did you specify any of the firewall rules / configuration before > rebooting? The default deny rules will keep you from connecting to the > box until you set up new rules that will accept connections. You'll want > to check and modify the firewall_ lines in /etc/defaults/rc.conf . No I didn't because I'm accustomed on Linux that the default policy is open, unless it is defined otherwise. > > The ipfw man page suggests being at the console when you enable the > firewall for this precise reason. > > The way to fix this problem is to log in at the console (or have someone > else do it for you) and add the following rule: > > ipfw add 100 allow ip from any to any > > > This will open up the firewall, and allow you to connect. You'll no doubt > want to delete that rule when you add your own custom rules. man ipfw(8) > will help you when you get around to doing that. Thanks for your info. I will ask the person who near with the server to issue that command from the console then. BTW how can I keep the firewall rules to be permanent on FreeBSD ? Put it on rc.firewall, or create another script that runs everytime the server gets rebooted ? Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
