Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!pipex!sunic!trane.uninett.no!eunet.no!nuug!EU.net!news.eunet.fi!KremlSun!kiae!relcom!newsserv From: "Andrew A. Chernov, Black Mage" <ache@astral.msk.su> Newsgroups: comp.os.386bsd.questions Subject: Re: GAMMA-sio and dsp problem Date: Mon, 02 May 94 14:53:52 +0400 Distribution: world Organization: Olam HaYetzirah Message-ID: <eY0lDnjKh2@astral.msk.su> Sender: news-service@kiae.su Reply-To: ache@astral.msk.su X-Return-Path: kiae!astral!astral.msk.su!ache Lines: 65 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 2266 In comp.os.386bsd.questions Lars Hentschke writes: >5. login over modem: > HERE COMES ON THE FOREIGN SITE MUCH LIKE "GF#@%$SGFA " AFTER > "CONNECT 14400" It looks much like that modem speed don't match serial speed. If you setup some speed into /etc/ttys many modems don't follows it automatically but needs to store this speed into configuration profile or issue AT command at this speed at least. You need to check also that your modem speed is the same after DTR reset (carrier drop). >6. after 1-2hours (TV or cookie-time): > tworivers ROOT root 25 (/tmp): cat /dev/cua00 > cat: /dev/cua00: Device busy > tip didnt work, but getty runs on ttyd0 > and sio0 is always bidir: > tworivers ROOT root 26 (/tmp): comcontrol /dev/ttyd0 > bidir dtrwait 200 > i cannot find a process, wich works on /dev/cua00 ! Many modems needs long time (up to 3 secs) for DTR reset. Now it fixed into -current as default time. You can try comcontrol /dev/ttyd0 dtrwait 300 in your /etc/rc.local >############################################################################## >The other Question is about the snd-driver and sampling over /dev/dsp >or /dev/dsp16: >My PAS16 has a buffer with a size of 64k on board. >FreeBSD-1.0-RELEASE detects this with 32k (ioctl SNDCTL_DSP_GETBLKSIZE) >Result was KNACK ................. KNACK ................ KNACK >FreeBSD-1.1-GAMMA detects this with 4k >Result was KNACK ... KNACK ... KNACK ... KNACK ... KNACK ... KNACK >WHY DO THEY NOT DETECT 64k ? At first GETBLKSIZE have nothing common with on-board ROMs and RAMs, it simple write buffer matching with DMA buffer for device. -current implements now contiguous DMA for sounddriver, so get you full 64K buffer. KNACK looks like dsp reset occurse, it is known problem with old sounddriver. You can comment all dsp_resets or got -current sounddriver. P.S. What kind of PAS16 you have? I have ProAudio16Basic and got strange problems with dead mixer: output level too low. -- Andrew A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: -- temp down -- : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849