Re: Slim SCSI log errors (PCMCIA)
In message [EMAIL PROTECTED] Bruce Burden writes: : aic0: Adaptec 6260/6360 SCSI controller at port 0x340-0x35f irq 8 slot 1 on pccard1 : aic0: aic6360, dma, disconnection, parity check : pcic0: Error 22 irq 8 I believe that irq 8 is specifically filtered at pcic interface. It is a bogus interrupt and generally cannot be routed to the pcic. You'll want to use another interrupt. : I am a bit concerned about the second line, regarding the :"dma, disconnection, parity check". Note that I don't have the :SCSI cable connected to the card, so obviously I don't have the :card connected to anything. (Yes, I know, I could _try_ to :hook it up. :-) ). dma just means that the chip is capible of doing it. The driver doesn't do dma at all, which is good, since the FreeBSD pccard bus doesn't support DMA at all. :pccard.conf parameters are of the 2/5 -current cvsup. The irq line is likely bogus in /etc/pccard.conf. Here's what I used to test it. # Generally available IO ports io 0x300-0x360 # Generally available IRQs (Built-in sound-card owners remove 5) irq 15 # Available memory slots memory 0xd4000 96k # Adaptec SlimSCSI (also included with Sony CD-ROM players) card "Adaptec, Inc." "APA-1460 SCSI Host Adapter" config 0x9 "aic0" 10 insert echo Adaptec Slim SCSI inserted remove echo Adaptec Slim SCSI removed Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Megahertz pccard
In message [EMAIL PROTECTED] "David O'Brien" writes: : On Tue, Feb 08, 2000 at 11:56:43AM -0800, Parag Patel wrote: : Seems like the default IRQs used by pccard are being used by something : else on your laptop. The default line in /etc/pccard.conf.sample is : : irq 3 5 10 11 13 15 : : Personally I don't know of anyone that hasn't had to remove `3' and `5' : from the the sample pccard.conf file. I personally think we should : remove these two before 4.0-R. No. That won't likely happen. Some compaq machines want 3 and 5. Other machines want 10 and 11, while others want others. sysinstall does need to be updated to cope with these oddities. It doesn't right now. Damn laptops are the most pathologically eclictic machines that FreeBSD supports. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: timed/adjtime() on -current
In message [EMAIL PROTECTED], Ben Smithurs t writes: [sorry about the crosspost - I'm not sure if this is me being a dumbass, or something wrong with adjtime() on current. adjtime() certainly behaves as I expect it to on stable.] You're right, I used the wrong sign last I mucked about with this, I'll fix this. Anyway: Don't used timed, use ntpd. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED] "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sound Card
[EMAIL PROTECTED] wrote: Ron 'The InSaNe One' Rosson wrote: Under 3.3-RELEASE with PAO the sound card work with this entry in the config file: device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x0 Here is what the dmesg output looked like with that entry: pcm0 at 0x220 irq 5 drq 1 on isa ESS1879 (rev 11, native mode) Now under current I have tried both of these entries to get sound working to no avail. device pcm0 at isa? port? irq 5 drq 1 flags 0x0 device pcm0 at isa? port? irq 5 drq 1 flags 0x15 Any assistance in this matter would be greatly appreciated. Have you tried the following? device pcm device sbc or device pcm0 device sbc0at isa? port 0x220 irq 5 drq 1 flags 0x0 Cheers MIHIRA Yoshiro Yokohama, Japan. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: INET6 changes for tcp_wrappers broke libwrap?
On Sun, Feb 13, 2000 at 01:48:04PM +0100, Blaz Zupan wrote: Bumping libwrap's shared lib version is trivial. Lets *quickly* decided if this is necessary. I see that this has been done. It should also not be forgotten to add libwrap to the compat3x libraries! Yes, and I've already secured JKH's ok to do this yesterday. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interesting compile glitch in -current
On Sat, 12 Feb 2000, Peter Wemm wrote:
cc -fpic -DPIC -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/home/src/lib/libc/include
-D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/home/src/lib/libc/../libc/locale
-DBROKEN_DES -DYP -I/usr/obj/home/src/i386/usr/include -c
/home/src/lib/libc/../libc/stdtime/localtime.c -o localtime.So
{standard input}: Assembler messages:
{standard input}:87: Warning: warning: unrecognized characters `@GOTOFF' in
expression
{standard input}:114: Warning: warning: unrecognized characters `@GOTOFF' in
expression
.. which is kinda disturbing..
This seems to be non-cosmetic. gas apparently can't handle constants of
the form address@GOTOFF. %ebx normally has to be added to these constants
to get an address, but gcc sometimes "optimises"
"leal address@GOTOFF(%ebx),%eax" to
"movl $address@GOTOFF,%eax; addl %ebx,%eax".
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: lots of ad_timeouts
It seems Don Croyle wrote: Soren Schmidt [EMAIL PROTECTED] writes: If it would help, I'll try setting it to PIO with sysctl and doing another buildworld. It probably will... Made it through the world safely. I've just started a make release. Assuming that this isn't something that's readily fixable, where would the best place to put the sysctl command so I don't have to remember it every time I reboot? /etc/rc.local -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 snapshot install problems
They've simply been renamed - it's no biggie. I have some patches in my inbox for adding the new acd devices, I just haven't gotten to them yet since it's still easy enough to edit them in the "unknown" category if one really needs to. - Jordan Hi all I've been trying out FreeBSD 4.0-2208 snapshot. During the boot up proces s, in the Kernel Configuration Menu - using full-screen visual mode, the follow ing appears on the screen: Active Drivers -- AdvanSys SCSI narrow controller adv0 Adaptec 154x SCSI controller aha0 Adaptec 152x SCSI controller and compatible aic0 Buslogic SCSI controller bt0 Floppy disk controllerfdc0 --cut - Miscellaneous - Unknown deviceata1 Unknown deviceata0 What happened to wcd devices? On the last stable release (3.4) I have success fully installed on my machine booting from kern and mfsroot floppies I got some thing like: Active Drivers -- AdvanSys SCSI narrow controller adv0 Adaptec 154x SCSI controller aha0 Adaptec 152x SCSI controller and compatible aic0 Buslogic SCSI controller bt0 Floppy disk controllerfdc0 plus: IDE/ESDI/MFM disk controller wdc0 IDE/ESDI/MFM disk controller wdc1 The problem is once booting from kern and mfsroot floppies from the 4.0 snaps hot release I cannot install the system properly. After selecting an installati on mode (e.g. via hard disk), the system starts reading the binaries (bin.aa, bin.ab, etc) then suddenly hangs up, so I have to press the reset key and reboot the machine . I have two IDE hard disks that have been working perfectly under 3.4 stable. What's the matter? Did anybody get the same problems I had? Any help would be greatly appreciated. Thanks, Rickie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/ports/ too big?
On Wed, 9 Feb 2000, Kai Voigt wrote: Hello, I'm just doing a cvsup update of my system and -as many times before- I realize that /usr/ports/ takes a lot of time and also disk space to sync. # du -sk /usr/ports 71118 /usr/ports Am I the only one being little annoyed by this fact? Would it make any sense to offer some "castrated" ports repository. Like putting a target "overview" into each /usr/ports/*/Makefile to list all available subdiretories. Then, with some other command, one could fetch the current port's directory from the cvs server to install the port. Do these thoughts make any sense? I know this is a few days old, but I want to suggest this anyway. Restructure the ports tree so that at the top level are languages and then there are categories beneath that. Like this: en/ archivers/ astro/ ... jp/ archivers/ astro/ ... And so forth. I do know that foreign (I speak English natively, therefore everything else is foreign to me) have been seperated off into their own directories, but still a straight CVSup on ports will fetch them. Configuring CVSup to only get those non-language directories is both time consuming and problematic if a new directory is added and nobody tells you. This also takes a step towards removing the English bias that clearly exists within the ports tree (and elseware). I know this will only reduce the problem of an overly large ports tree for some time, but this is a good idea anyway, especially from an organizational standpoint. Has this been discussed before? Will I be laughed to scorn? Jamie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: timed/adjtime() on -current
Poul-Henning Kamp wrote: You're right, I used the wrong sign last I mucked about with this, I'll fix this. thanks... Anyway: Don't used timed, use ntpd. Do you have any hints about using xntpd over an intermittent dialup connection? At the moment, I use ntpdate to sync the time to my ISP's servers when ever I go online, I can't see it being easy to tell xntpd to sync the time when I tell it to, and only when I tell it to. Unless you know otherwise? :-) -- Ben Smithurst / [EMAIL PROTECTED] / PGP: 0x99392F7D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: lots of ad_timeouts
Soren Schmidt [EMAIL PROTECTED] wrote: It seems Don Croyle wrote: Assuming that this isn't something that's readily fixable, where would the best place to put the sysctl command so I don't have to remember it every time I reboot? /etc/rc.local Surely /etc/sysctl.conf Tony. -- * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ** * * * ** * * * ** * * * ** * * * * * * * * * * * * To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD-current question re: binutils
On Sat, Feb 12, 2000 at 02:35:51PM -0700, Daniel Robbins wrote: Hi there, I'm writing you on behalf of the freebsd-current mailing list, with some questions regarding binutils. Freebsd-current has integrated gcc 2.95.2 into the standard sources, but is still using a relatively old version of binutils (2.9.1 or thereabouts). Several people are wondering what version should be used alongside gcc 2.95.2. Could you help us out with this? Should the most recent version of binutils (2.9.5.0.24) be used? Which version, in your opinion, works best with gcc 2.95.2? Since I don't use freebsd, I can only speak from my experiences under Linux. Since both freebsd and Linux use ELF, I guess they shouldn't be so far off. I just made 2.9.5.0.27 last week. It is available at ftp://ftp.valinux.com/pub/support/hjl/binutils It works on Linux. I haven't heard any bad things about it yet. I won't use binutils 2.9.1. So many important bug fixes have been added since then. I will be happy to include any freebsd related patches in my binutils as long as 1. They work. 2. They don't break Linux. 3. Their authors will keep them up to date with binutils on sourceware. I will take them out if ony of 3 fails. I keep my binutils in sync with binutils on sourceware. I usually make a new release when I see enough changes from sourceware which warrant one. That is about once a month. H.J. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problems with openssl in 4.0rc and ports/security/openssh
I installed a fresh 4.0 release candidate this morning, including the crypto stuff (des, kerberos...). Tried to install openssh from ports tree as well, but couldn't. It was looking for /usr/include/openssl/rsa.h which was not there, and I couldn't find a knob to turn RSA requirement off. Where did you obtain your crypto sources from? You should be using internat.freebsd.org, which should have the RSA header (i.e you should not be using a US mirror site). Can you verify this? No sources, binary install. I haven't updated the openssh port yet to use the system version of openssl - once it's updated it will point you to a section of the handbook to explain what you need to do first (Chapter 6.5, thanks Jim :-) if it can't build with the version of openssl you currently have. The packages it refers to aren't yet available, because I haven't had the time to build them, but I'll either be doing this tonight or over the weekend. You'll have to rebuild from source as it explains there. hmm... ok. well, not too very important I guess, just a shame that it didn't work. -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problems with openssl in 4.0rc and ports/security/openssh
internat:/home/ftp/pub/FreeBSD/releases/i386/4.0-2211-SNAP/des cat des.?? | tar -tzvf - | grep rsa -r--r--r-- root/wheel12208 Feb 12 07:09 2000 usr/include/openssl/rsa.h Or is there something that I miss? That looks right. I think the original person was getting their crypto from the wrong place. The original person was not getting crypto anywhere, just installing from the install floppies, which didn't seem to work somehow for installing this port. That is all -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ABIT BP6 + UDMA66: ad_timeout: lost disk contact
Mine's a Western Digital WD205BARTL (Caviar 20.5 gig 7200 RPM) -- Marius Strom [EMAIL PROTECTED] Professional Geek/Unix System Administrator Alpha1 Internet http://www.alpha1.net http://www.marius.org/marius.pgp 0x5645C228 In theory, there is no difference between theory and practice... ...In practice, there is a big difference. On Sat, 12 Feb 2000, Soren Schmidt wrote: It seems Marius Strom wrote: Hans and others, I have the same situation - happy to get a new motherboard and processor, unhappy to hang FreeBSD. My situation is different, however - I'm running single processor currently and it still hangs. I've also experienced this issue with and without softupdates. What make of disk are you using ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rpc.lockd... is done.
"David E. Cross" wrote: Amitha (the person who has been working on the lockd code) has finished most of his work. There are still some issues with handling async locks and cancel messages. Also we were not able to implement the full NLM protocol as the FreeBSD kernel does not currently request NFS locks (we should fix that ASAP). This code is *ALPHA*. Even we will not be running it on production servers in the near future. In response to your previous message about getting people to test this, I'm not sure what exactly I can test here. Here is my scenario, tell me if I can help. I have many freebsd machines acting as nfs clients to access data on a combination of sun and netapp nfs servers. If I set up this version of rpc.lockd on the freebsd clients will it lock the files on the servers so that only one client at a time can access them? (Assuming of course that the code I'm working with is properly requesting a lock...) I will be happy to help, but I need to know in more detail what I'm testing, how you need it tested, what is the likelihood of success and what kind of feedback you're looking for. Glad to hear that progress is being made anyway, Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sbc and ViBRA16X - dsp device not working
Hi. I sent this a few days ago and haven't received any response. Is there anything I can do to get closer to this problem, or provide more useful information to someone who might know what the problem is? More info: if I do: $ mixer pcm 100:100 $ echo "foo" /dev/dsp then I hear a loud pop. If I do: $ mixer pcm 5:5 $ echo "foo" /dev/dsp then the pop is very soft. Also, XMMS isn't hanging anymore. All I've changed is I've rebooted a few times. When I try to play an mp3, it's progress thumb blinks. If I drag the progress thumb to the middle of a song, it pops. But it won't play. Is there a way I can write a test program to see what is happening? What man pages should I look at? The pcm and sbc man pages don't really say anything, once you've got your device recognized. Thanks, Tim - Forwarded message from Thimble Smith [EMAIL PROTECTED] - Date: Thu, 10 Feb 2000 09:01:22 -0500 From: Thimble Smith [EMAIL PROTECTED] Subject: sbc and ViBRA16X - dsp device not working To: [EMAIL PROTECTED] [ Long post, almost a narrative. Sorry. ] Hi. A month ago I installed -current on a new computer, and the dsp device didn't work. It reminded me of why I'd rather not be running -current, so I dropped back to -stable and everything worked fine. Now I saw that a release was coming up, so I wanted to see if the problem was solved. Last night I cvsup'd to current. My sound card is recognized fine: $ dmesg | g '(sbc|pcm)' sbc1: Creative ViBRA16X at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on isa0 sbc1: setting card to irq 5, drq 1, 3 pcm0: SB DSP 4.16 (ViBRA16X) on sbc1 $ tim@threads:~$ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Feb 10 2000 05:59:59 Installed devices: pcm0: SB DSP 4.16 (ViBRA16X) at io 0x220 irq 5 drq 1:3 (1p/1r channels duplex) I can listen to a CD through the sound card using cdcontrol, and use mixer to adjust the volume. This is my first computer w/ a sound card, so I don't know how to do much more than that. The problem comes when trying to use the /dev/dsp device (which is the only other thing I've tried). Xmms, for example, won't play - it opens fine, and I can manipulate the play list, etc. But when I try to play an mp3 file, it stops responding. Here's a before and after ps -axlww: Before trying to play the mp3 file: 1001 3124 1 1 2 0 9068 5632 poll S p00:01.99 xmms After: 1001 3124 1 0 2 0 10856 7356 poll S p00:02.68 xmms I couldn't see anything weird with ps or top. But xmms will not respond to any mouse events. A normal kill ends the program, though. Another program I have that uses /dev/dsp is xgalaga (from the 3.4 release package). When it starts up, it says: xgal.sndsrv: fragment set to 512 and ps -xw shows: 33248 p2 S+ 0:00.14 xgalaga 33249 p2 S+ 0:00.01 /usr/X11R6/lib/X11/xgalaga/xgal.sndsrv.freebsd /usr/X11R6/lib/X11/xgalaga/sounds/ /dev/dsp No sound is heard when I play the game, but otherwise game play is normal. After I quit the game, the sndsrv program is still running: 33249 p2 S 0:00.08 /usr/X11R6/lib/X11/xgalaga/xgal.sndsrv.freebsd /usr/X11R6/lib/X11/xgalaga/sounds/ /dev/dsp After a normal kill, it quits after a few seconds. These programs worked under -stable, using the pcm sound driver (didn't need the sbc bridge there). Last month when I tried it under -current, something very odd happened that isn't happening now. After running something like $ cat /dev/dsp a ps would show two instances of cat running; likewise if I ran xmms, it would show two instances of xmms! And I'd have to send a -KILL signal to get them to die. I don't know how else to debug this. Right now if I do: $ cat /dev/dsp foo ^D I can hear a pop through my headphones. So something's there; but my applications can't use it. I built the most recent port of xmms just this morning, in case something was buggy there. If this is not a bug, I'm very sorry to have wasted your time. If you need me to try anything out, just let me know. Thanks, Tim - End forwarded message - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Boca BB2016 (multiport non-AST) lost interrupts?
This is one of those problem reports I hate sending and one that I
know everyone hates receiving. I have gone over and over my settings
and I'm certain that I haven't done anything stupid, so please bear
with me.
I recently upgraded a machine from an old 3.0-RELEASE to the 2209
snapshot. It was previously running a Boca BB2016 multiport serial
card ("box" actually) correctly. Now the master port (16) on the card
works but none of the others seem to generate interrupts. I put a
printf at the beginning of siointr() and when I plug the modem into
the master port and talk to it with cu, it works fine and I get
messages from my printf signifying that siointr() was called with
((struct com_s *)arg)-unit = 17.
When I do the same with the other ports, siointr() is never called. I
get some characters back from the modem, but only when I press a key:
for instance I type "A" get nothing, type "T", get A, type "RET", get
T, type RET again and finally get \nOK\n. If I type ati10\n which
should give back a screenfull of stuff, I get about 16 characters
printed in cu and a silo overflow on the console.
Here is the relevant part of my kernel config, sorry for the length:
device sio0at isa? port IO_COM1 flags 0x10 irq 4
#device sio1at isa? disable port IO_COM2 irq 3
device sio2at isa? port 0x100 flags 0x01105
device sio3at isa? port 0x108 flags 0x01105
#device sio4at isa? port 0x110 flags 0x01105
device sio5at isa? port 0x118 flags 0x01105
device sio6at isa? port 0x120 flags 0x01105
device sio7at isa? port 0x128 flags 0x01105
device sio8at isa? port 0x130 flags 0x01105
device sio9at isa? port 0x138 flags 0x01105
device sio10 at isa? port 0x140 flags 0x01105
device sio11 at isa? port 0x148 flags 0x01105
device sio12 at isa? port 0x150 flags 0x01105
device sio13 at isa? port 0x158 flags 0x01105
device sio14 at isa? port 0x160 flags 0x01105
device sio15 at isa? port 0x168 flags 0x01105
device sio16 at isa? port 0x170 flags 0x01105
device sio17 at isa? port 0x178 flags 0x01105 irq 3
Note I am using irq 3 for the Boca and sio1 is disabled. The
corresponding port ("com2") IS disabled on the motherboard. Also sio4
is disabled to get my 3c509 to detect properly. I know this is an odd
setup but I am convinced it is correct and it worked setup exactly
like this with the 3.0-RELEASE. I have the 3.0 disk still and I tried
it again this afternoon, just to be sure it is not a hardware problem,
and it still works fine.
Here's the bad news: The 3.0-RELEASE had an sio.c rev. 1.209 and the
current is 1.287. I have stared and stared at the diff and I don't
see any obvious problems.
Here is the relevant part of my -v dmesg (and the full one is attached
- it's too long to not compress)
sio0: irq maps: 0x41 0x51 0x41 0x41
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio2: irq maps: 0x41 0x41 0x41 0x41
sio2 at port 0x100-0x107 flags 0x1105 on isa0
sio2: type 16550A (multiport)
sio3: irq maps: 0x41 0x41 0x41 0x41
sio3 at port 0x108-0x10f flags 0x1105 on isa0
sio3: type 16550A (multiport)
sio5: irq maps: 0x41 0x41 0x41 0x41
sio5 at port 0x118-0x11f flags 0x1105 on isa0
sio5: type 16550A (multiport)
sio6: irq maps: 0x41 0x41 0x41 0x41
sio6 at port 0x120-0x127 flags 0x1105 on isa0
sio6: type 16550A (multiport)
sio7: irq maps: 0x41 0x41 0x41 0x41
sio7 at port 0x128-0x12f flags 0x1105 on isa0
sio7: type 16550A (multiport)
sio8: irq maps: 0x41 0x41 0x41 0x41
sio8 at port 0x130-0x137 flags 0x1105 on isa0
sio8: type 16550A (multiport)
sio9: irq maps: 0x41 0x41 0x41 0x41
sio9 at port 0x138-0x13f flags 0x1105 on isa0
sio9: type 16550A (multiport)
sio10: irq maps: 0x41 0x41 0x41 0x41
sio10 at port 0x140-0x147 flags 0x1105 on isa0
sio10: type 16550A (multiport)
sio11: irq maps: 0x41 0x41 0x41 0x41
sio11 at port 0x148-0x14f flags 0x1105 on isa0
sio11: type 16550A (multiport)
sio12: irq maps: 0x41 0x41 0x41 0x41
sio12 at port 0x150-0x157 flags 0x1105 on isa0
sio12: type 16550A (multiport)
sio13: irq maps: 0x41 0x41 0x41 0x41
sio13 at port 0x158-0x15f flags 0x1105 on isa0
sio13: type 16550A (multiport)
sio14: irq maps: 0x41 0x41 0x41 0x41
sio14 at port 0x160-0x167 flags 0x1105 on isa0
sio14: type 16550A (multiport)
sio15: irq maps: 0x41 0x41 0x41 0x41
sio15 at port 0x168-0x16f flags 0x1105 on isa0
sio15: type 16550A (multiport)
sio16: irq maps: 0x41 0x41 0x41 0x41
sio16 at port 0x170-0x177 flags 0x1105 on isa0
sio16: type 16550A (multiport)
sio17: irq maps: 0x41 0x49 0x41 0x41
sio17 at port 0x178-0x17f irq 3 flags 0x1105 on isa0
sio17: type 16550A (multiport master)
Thanks for any help,
Chris
dmesg.insight.gz
Re: Boca BB2016 (multiport non-AST) lost interrupts?
On Sun, 13 Feb 2000 18:00:07 CST, Chris Radek writes:
I recently upgraded a machine from an old 3.0-RELEASE to the 2209
snapshot. It was previously running a Boca BB2016 multiport serial
card ("box" actually) correctly. Now the master port (16) on the card
works but none of the others seem to generate interrupts.
Argh, I sent that too soon. I think I found it.
It was broken in rev 1.274 - look at the current sio.c, line 715: idev
should be the master port and not the port being probed. It even says
so in the comment. It took me a large part of an evening to read the
bloody comment. :-)
Here's the patch:
% diff -u sio.c.orig sio.c
--- sio.c.orig Sun Feb 13 16:59:49 2000
+++ sio.c Sun Feb 13 18:23:22 2000
@@ -692,7 +692,7 @@
idev = dev;
mcr_image = MCR_IENABLE;
#ifdef COM_MULTIPORT
- if (COM_ISMULTIPORT(flags) !COM_NOTAST4(flags)) {
+ if (COM_ISMULTIPORT(flags)) {
Port_t xiobase;
u_long io;
@@ -702,14 +702,16 @@
device_get_unit(dev), COM_MPMASTER(flags));
idev = dev;
}
- if (bus_get_resource(idev, SYS_RES_IOPORT, 0, io, NULL) == 0) {
- xiobase = io;
- if (bus_get_resource(idev, SYS_RES_IRQ, 0, NULL, NULL))
- outb(xiobase + com_scr, 0x80); /* no irq */
- else
- outb(xiobase + com_scr, 0);
+ if (!COM_NOTAST4(flags)) {
+ if (bus_get_resource(idev, SYS_RES_IOPORT, 0, io, NULL) == 0)
+{
+ xiobase = io;
+ if (bus_get_resource(idev, SYS_RES_IRQ, 0, NULL, NULL))
+ outb(xiobase + com_scr, 0x80); /* no irq */
+ else
+ outb(xiobase + com_scr, 0);
+ }
+ mcr_image = 0;
}
- mcr_image = 0;
}
#endif /* COM_MULTIPORT */
if (bus_get_resource(idev, SYS_RES_IRQ, 0, NULL, NULL) != 0)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ATA problem? command aborted on IBM hd, compaq laptop
On Sat, 12 Feb 2000 20:57:44 +0100, Soren Schmidt writes: It seems Chris Radek wrote: ad0: HARD READ ERROR blk# 0 status=51 error=04 ad0: reading primary partition table: error reading fsbn 0 Try to disable the multi-sector stuff, that might be whats killing you.. -Søren I'm not sure exactly how to do this -- I changed ata-disk.c:139 to read secsperint=1; instead of secsperint = max(1, min(AD_PARAM-nsecperint, 16)); which gives me boot messages: ad0: IBM-H2344-A4/G4I_A8C0 ATA-0 disk at ata0 as master ad0: 328MB (672525 sectors), 915 cyls, 15 heads, 49 S/T, 512 B/S ad0: 1 secs/int, 1 depth queue, BIOSPIO ad0: piomode=2 dmamode=-1 udmamode=-1 cblid=0 but I get the same errors (above). Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: timed/adjtime() on -current
Ben Smithurst wrote: Poul-Henning Kamp wrote: Anyway: Don't used timed, use ntpd. Do you have any hints about using xntpd over an intermittent dialup connection? At the moment, I use ntpdate to sync the time to my ISP's servers when ever I go online, I can't see it being easy to tell xntpd to sync the time when I tell it to, and only when I tell it to. Unless you know otherwise? :-) Set your ppp filters carefully. Tell it that ntp packets (port 123) are not to cause a dialup, and are not to trigger the idle timer. The result of this will be that ntp will sync up while you are online but won't keep the connection alive and prevent an idle hangup (assuming you use idle timeouts). Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: getaddrinfo with IPv6 and unqualified hostname
Is it just some misconfiguration of mine which causes getaddrinfo() with an unqualified hostname, IPv6 and hints-ai_family == AF_UNSPEC to block (trying a DNS lookup I guess), even when the hostname has a perfectly good IPv4 address, or is this normal behaviour? This seems rather annoying, and means something as simple as "ftp otherhost" will block unless I use the FQDN. Is there any way to avoid this behaviour? It may happen with older versioin of getaddrinfo() at least. getaddrinfo() in getaddrinfo.c before 1.5 did reverse lookup when AI_CANONNAME flag is specified, so if reverse lookup information was not obtained, it would block. If the problem happens with newest getaddrinfo.c (1.8), then there might be another problem. I can't repeat it on my remote current machine, (As far as I tested as below. -find some IP addrs which I fail reverse lookup -and set it some name in my host's /etc/hosts file -and try with the name) but I'll also try it with my local machin when I back to my home today. Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interesting compile glitch in -current
Bruce Evans wrote:
On Sat, 12 Feb 2000, Peter Wemm wrote:
cc -fpic -DPIC -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/home/src/lib/libc/inclu
de -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/home/src/lib/libc/../
libc/locale -DBROKEN_DES -DYP -I/usr/obj/home/src/i386/usr/include -c /home
/src/lib/libc/../libc/stdtime/localtime.c -o localtime.So
{standard input}: Assembler messages:
{standard input}:87: Warning: warning: unrecognized characters `@GOTOFF' in
expression
{standard input}:114: Warning: warning: unrecognized characters `@GOTOFF' i
n expression
.. which is kinda disturbing..
This seems to be non-cosmetic. gas apparently can't handle constants of
the form address@GOTOFF. %ebx normally has to be added to these constants
to get an address, but gcc sometimes "optimises"
"leal address@GOTOFF(%ebx),%eax" to
"movl $address@GOTOFF,%eax; addl %ebx,%eax".
The current binutils gas deals with this without a complaint BTW. And
mozilla compiled with the new binutils seems to work fine too while when
I compiled the same source with the old as/ld it was crashing at startup.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: INET6 changes for tcp_wrappers broke libwrap?
On Sun, Feb 13, 2000 at 01:48:04PM +0100, Blaz Zupan wrote: Bumping libwrap's shared lib version is trivial. Lets *quickly* decided if this is necessary. I see that this has been done. It should also not be forgotten to add libwrap to the compat3x libraries! Yes, and I've already secured JKH's ok to do this yesterday. Please also consider libutil if it is not yet included in it. (I just committed libutil version up, because it also depends on libc.so.4) Thanks, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: getaddrinfo with IPv6 and unqualified hostname
Is it just some misconfiguration of mine which causes getaddrinfo() with an unqualified hostname, IPv6 and hints-ai_family == AF_UNSPEC to block (trying a DNS lookup I guess), even when the hostname has a perfectly good IPv4 address, or is this normal behaviour? This seems rather annoying, and means something as simple as "ftp otherhost" will block unless I use the FQDN. Is there any way to avoid this behaviour? It may happen with older versioin of getaddrinfo() at least. getaddrinfo() in getaddrinfo.c before 1.5 did reverse lookup when AI_CANONNAME flag is specified, so if reverse lookup information was not obtained, it would block. Ben, if you run tcpdump, do you see forward lookups for ? If so, I believe this problem is same as this one, not AI_CANONNAME issue in old getaddrinfo code: http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=9413 I intend to correct this one, however, the way to fix it is very dependent to resolver internal functions. so fix to netbsd-current won't apply to freebsd-current. itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
