Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

stable-digest V5 #802

4 views
Skip to first unread message

owner-freebsd...@freebsd.org

unread,
Feb 24, 2003, 9:18:57 AM2/24/03
to

stable-digest Monday, February 24 2003 Volume 05 : Number 802

In this issue:
Unable to intall 4.7 on Acer Acros
Re: Mozilla window won't open after upgrade
subscribe
vmware2 & parallel port
dhclient problem in stable
iHEADS UP: ipsec packet filtering change
Build of texinfo/makeinfo and others broken?
Re: Compaq WL200 wireless card trouble
wi card problem on 440lx motherboard
Re: Compaq WL200 wireless card trouble
Re: Compaq WL200 wireless card trouble
freebsd-hackers, LIVE FROM WALL STREET: VICC Test Results Are In...
Lost FireWire-support
burncd problem with NEC NR-7500A CD burner in DAO mode
Re: Maxtor Firewire Drives
ntp broadcast mode
OpenSSL-related problem
Re: OpenSSL-related problem
Re: OpenSSL-related problem
Re: OpenSSL-related problem
Re: burncd problem with NEC NR-7500A CD burner in DAO mode
Re: ntp broadcast mode
Re: burncd problem with NEC NR-7500A CD burner in DAO mode
Re: OpenSSL-related problem
fsck problem

----------------------------------------------------------------------

Date: Sun, 23 Feb 2003 15:03:15 +0100
From: Thomas Krause -CI- <freebsd...@chef-ingenieur.de>
Subject: Unable to intall 4.7 on Acer Acros

Hi,
I'm unable to intall 4.7-REL on an Acer Acros
(Pentium 75, Intel FX-Chipset, 32MB RAM).
http://www.uktsupport.co.uk/acer/mb/acv30-1.htm
The loader detects 1GB RAM and the setup routine hangs.

Any ideas?

Regards,
Thomas.

------------------------------

Date: Sun, 23 Feb 2003 11:01:59 -0500
From: Robert Withrow <wi...@rwwa.com>
Subject: Re: Mozilla window won't open after upgrade

For quite some time now, *linux* Mozilla segfaults for me on 4.7R.

<~>$ linux-mozilla -v
Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.1) Gecko/20020826, build 2002082612

None of the suggestions in this thread seem to help. Anyone else have this problem?
Anyone have a solution?

Thanks!


- ---------------------------------------------------------------------
Robert Withrow, R.W. Withrow Associates, Swampscott MA, wi...@rwwa.COM

------------------------------

Date: Sun, 23 Feb 2003 17:16:38 +0100
From: Edoardo Causarano <curiou...@katamail.com>
Subject: subscribe

------------------------------

Date: Sun, 23 Feb 2003 23:16:51 +0700
From: Eugene Grosbein <eu...@grosbein.pp.ru>
Subject: vmware2 & parallel port

Hi!

I have dual-boot 4.8-PRERELEASE/Win98SE machine and
installed vmware2 from ports. It works basically OK.

Now I'm trying to access parallel printer from vmware
but it complains at startup that cannot control printer.
Meantime, kernel writes to console:

linux: 'ioctl' fd=25, cmd=0x60b (' ',11) not implemented

Is is fatal?

Eugene Grosbein

------------------------------

Date: Sun, 23 Feb 2003 18:41:39 +0100
From: Raymond Wiker <Raymon...@fast.no>
Subject: dhclient problem in stable

This problem has actually existed for a while, but I never got
round to reporting it.

I'm using a Cisco 770 ISDN router to connect to my employer's
network. This router is set up with DHCP, so I can connect my various
machines to the router, tell them to get their network config from
DHCP, and all is dandy.

Well, no quite. It seems the router is set up to return 2^32 -
1 as the lease time, which the dhclient code interprets as -1. This
crashes at line 792 in /usr/src/contrib/isc-dhcp/client/dhclient.c,
at an expression that involves the modulo (%) operator. The reason for
the crash is that the rhs of the modulo operation is zero.

I can "fix" this by changing the code at line 787 (see patch
below). I'm not sure that this is the right solution, though: it may
be appropriate to make client->new->renewal an unsigned int instead of
a signed one. It is also possible that the config of the Cisco router
is out of spec :-)

- --- /usr/src/contrib/isc-dhcp/client/dhclient.c.org Thu Apr 11
12:16:45 2002
+++ /usr/src/contrib/isc-dhcp/client/dhclient.c Sun Feb 23 18:35:44
2003
@@ -784,7 +784,7 @@
client -> new -> renewal = 0;

/* If it wasn't specified by the server, calculate it. */
- - if (!client -> new -> renewal)
+ if (client -> new -> renewal <= 0)
client -> new -> renewal =
client -> new -> expiry / 2;

------------------------------

Date: Sun, 23 Feb 2003 09:47:05 -0800
From: "Sam Leffler" <s...@errno.com>
Subject: iHEADS UP: ipsec packet filtering change

This may affect your ipfw/ipf rules. If you are happy with the current
behaviour then add IPSEC_FILTERGIF to your kernel config file.

Sam

- ----- Original Message -----
From: "Sam Leffler" <s...@FreeBSD.org>
To: <src-com...@FreeBSD.org>; <cvs...@FreeBSD.org>;
<cvs...@FreeBSD.org>
Sent: Sunday, February 23, 2003 9:45 AM
Subject: cvs commit: src/sys/conf options src/sys/netinet ip_input.c
src/sys/i386/conf LINT


> sam 2003/02/23 09:45:29 PST
>
> Modified files: (Branch: RELENG_4)
> sys/conf options
> sys/netinet ip_input.c
> sys/i386/conf LINT
> Log:
> MFC: IPSEC_FILTERGIF config option
>
> Add a new config option IPSEC_FILTERGIF to control whether or not
> packets coming out of a GIF tunnel are re-processed by ipfw, et. al.
> By default they are not reprocessed. With the option they are.
>
> This reverts 1.214. Prior to that change packets were not re-processed.
> After they were which caused problems because packets do not have
> distinguishing characteristics (like a special network if) that allows
> them to be filtered specially.
>
> PR: 48159
> Reviewed by: Guido van Rooij <gu...@gvr.org>
> Approved by: re (jhb, murray)
>
> Revision Changes Path
> 1.191.2.47 +1 -0 src/sys/conf/options
>
http://cvsweb.FreeBSD.org/src/sys/conf/options.diff?r1=1.191.2.46&r2=1.191.2
.47
> 1.749.2.136 +11 -0 src/sys/i386/conf/LINT
>
http://cvsweb.FreeBSD.org/src/sys/i386/conf/LINT.diff?r1=1.749.2.135&r2=1.74
9.2.136
> 1.130.2.48 +7 -0 src/sys/netinet/ip_input.c
>
http://cvsweb.FreeBSD.org/src/sys/netinet/ip_input.c.diff?r1=1.130.2.47&r2=1
.130.2.48
>
>
>

------------------------------

Date: Sun, 23 Feb 2003 19:29:53 +0100
From: Thomas Stratmann <stra...@fsp1.physik.ruhr-uni-bochum.de>
Subject: Build of texinfo/makeinfo and others broken?

Hi,

make buildworld stops on makeinfo as shown below. The same strange things
happen for other tools in gnu/ , just makeinfo is the first of them to be hit
by buildworld.

That line 543 probably should expand to '"/usr/share/locale";' which should
be a legal C NOP. Maybe quoting is wrong on the way to the cc commandline
so the '"' are dropped or something.

I searched the archives but found nothing related, so I seem to be the only
one to have this problem. It's not unlikely that some config files are broken
(had severe fs damage after hardware related crashes; fsck did its best).
Sources are -stable from a few days ago.
Any ideas?

Cheers
Thomas Stratmann

===> gnu/usr.bin/texinfo/makeinfo
cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/locale\" -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo -I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/lib -D__FBSDID=__RCSID -c /usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/makeinfo/makeinfo.c
/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/makeinfo/makeinfo.c: In function `main':
/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/makeinfo/makeinfo.c:543: syntax error before `/'
*** Error code 1

Stop in /usr/src/gnu/usr.bin/texinfo/makeinfo.
*** Error code 1

Stop in /usr/src/gnu/usr.bin/texinfo.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

------------------------------

Date: Sun, 23 Feb 2003 20:52:30 +0100
From: Wilko Bulte <w...@freebie.xs4all.nl>
Subject: Re: Compaq WL200 wireless card trouble

On Sun, Feb 23, 2003 at 12:43:57PM +0100, Dirk-Willem van Gulik wrote:
>
> On Sun, 23 Feb 2003, Wilko Bulte wrote:
>
> > Ah, so I understand it is the PCI-PCMCIA bridge that is most likely
> > the source of the watchdog timeouts? The BP6 machine is at 4.7-stable
> > as of 2 days back or so.
> ..
> > I tried 5.0 on another machine (!!) and there the whole machine locks up
> > as soon as it sees the wi. I.e. when it displays the wi0 probe message.
> > To be fair, 4.7R does the same there.
>
> The commit you need is:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pccard/pcic_pci.c.diff?r1=1.122&r2=1.123
>
> the two lines after ' Tell the chip to do its routing thing'.
>
> static void
> -pcic_pci_pd67xx_init(device_t dev)
> +pcic_pci_pd6729_init(device_t dev)
> {
> struct pcic_softc *sc = device_get_softc(dev);
>
> - if (sc->csc_route == pcic_iw_pci || sc->func_route == pcic_iw_pci)
> - device_printf(dev, "PD67xx maybe broken for PCI routing.\n");
> + /*
> + * Tell the chip to do its routing thing.
> + */
> + pcic_pci_pd6729_func(&sc->slots[0], sc->func_route);
> + pcic_pci_pd6729_csc(&sc->slots[0], sc->csc_route);

It seems I'm getting watchdog timeouts after putting this patch in
4.7-stable. One needs to s/pd6729/pd67xx/ to use it on -stable by the way.

Other ideas?

- --
| / o / /_ _ wi...@tcja.nl - stichting TCJA, Arnhem
|/|/ / / /( (_) Bulte

------------------------------

Date: Mon, 24 Feb 2003 07:12:30 +1100
From: Rudolph Pereira <meme...@yahoo.com.au>
Subject: wi card problem on 440lx motherboard

Hello,
I am trying to get a wireless PCI card working on an old PC with an
intel 440lx chipset and it appears that the card is only intermittently
working.

First, the specs:
motherboard: msi-6111 (440lx chipset)
wi pci card: sparklan wl-360f; pciconf output is:

wi0@pci0:16:0: class=0x028000 card=0x38731260 chip=0x38731260 rev=0x01
hdr=0x00
vendor = 'Intersil Americas Inc (Was: Harris Semiconductor)'
device = 'PRISM 2.5 802.11b 11Mbps Wireless Controller'
class = network

I'm testing by pinging between this machine and a wi in my laptop (which
stays constant throughout my tests), the cards are in ad-hoc mode,
11Mbps, and about 2 metres from each other with no obvious sources of
interference.

results:
- - if I put the card into another (newer, completely different
configuration) machine running 4-stable, everything works fine
- - if I ping with a freebsd 4-stable or 5-current configuration on the
problem machine, I get ~20% packet loss (this is just a straight
ping), with the dropped packets being corrupted as described below
- - if I run the same ping test under netbsd (1.6), there's at most 3%
packet loss, but usually none

The corruption looks random. I've only seen it in packet headers (e.g
checksums, protocols etc), but I can't say it's only happening there.

Examples: (laptop == 192.168.0.2, faulty card == 192.168.0.1); I've
listed the tcpdump output from the src first

1.
06:19:14.698259 192.168.0.2 > 192.168.0.1: icmp: echo request (ttl 64,
id 51178, len 84)
4500 0054 c7ea 0000 4001 316b c0a8 0002
c0a8 0001 0800 04f0 0e09 0500 b21e 593e
dfa6 0a00 0809 0a0b 0c0d 0e0f 1011 1213
1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
3435
06:19:13.419329 truncated-ip - 51094 bytes missing! 192.168.0.2 >
192.168.0.1: icmp: echo request (ttl 64, id 51178, len 51178, bad cksum
316b!)
4500 c7ea c7ea 0000 4001 316b c0a8 0002
c0a8 0001 0800 04f0 0e09 0500 b21e 593e
dfa6 0a00 0809 0a0b 0c0d 0e0f 1011 1213
1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
3435

2.
06:31:56.804103 192.168.0.2 > 192.168.0.1: icmp: echo request (ttl 64,
id 53536, len 84)
4500 0054 d120 0000 4001 2835 c0a8 0002
c0a8 0001 0800 7f4c 230c 0500 ac21 593e
5444 0c00 0809 0a0b 0c0d 0e0f 1011 1213
1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
3435

06:31:56.471654 192.168.0.2 > 192.168.0.1: (frag 53536:64@8) (ttl 64,
len 84, bad cksum 2835!)
4500 0054 d120 4001 4001 2835 c0a8 0002
c0a8 0001 0800 7f4c 230c 0500 ac21 593e
5444 0c00 0809 0a0b 0c0d 0e0f 1011 1213
1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
3435

3.
06:41:05.800243 bad-hlen 0
0054 0054 d7de 0000 4001 2177 c0a8 0002
c0a8 0001 0000 7b6f 3d01 0300 d123 593e
232a 0c00 0809 0a0b 0c0d 0e0f 1011 1213
1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
3435

06:41:06.119715 192.168.0.2 > 192.168.0.1: icmp: echo reply (ttl 64, id
55262, len 84)
4500 0054 d7de 0000 4001 2177 c0a8 0002
c0a8 0001 0000 7b6f 3d01 0300 d123 593e
232a 0c00 0809 0a0b 0c0d 0e0f 1011 1213
1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
3435

4.
06:43:32.892415 192.168.0.2 > 192.168.0.1: gre gre-proto-0xAA06 (ttl 32,
id 55590, len 84, bad cksum 202f!)
4500 0054 d926 0000 202f 202f c0a8 0002
c0a8 0001 0000 aa06 3e01 0100 6424 593e
6192 0d00 0809 0a0b 0c0d 0e0f 1011 1213
1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
3435
06:43:33.208366 192.168.0.2 > 192.168.0.1: icmp: echo reply (ttl 64, id
55590, len 84)
4500 0054 d926 0000 4001 202f c0a8 0002
c0a8 0001 0000 aa06 3e01 0100 6424 593e
6192 0d00 0809 0a0b 0c0d 0e0f 1011 1213
1415 1617 1819 1a1b 1c1d 1e1f 2021 2223
2425 2627 2829 2a2b 2c2d 2e2f 3031 3233
3435


Lastly, the message "wi0: oversized packet received ...." is
occasionally displayed on the problematic machine's console.

So, does anyone have any ideas about this? I've tried putting some
printfs in the wi driver and it _seems_ like the corruption/duplication
is happening before it gets to the driver, but I'm not a kernel hacker
and could've got it wrong (then again, corruption there would be obvious
to other wi users I would think).
Any suggestions on how I can debug this?

Thanks in advance.

------------------------------

Date: Sun, 23 Feb 2003 21:14:44 +0100 (CET)
From: Dirk-Willem van Gulik <di...@webweaving.org>
Subject: Re: Compaq WL200 wireless card trouble

> It seems I'm getting watchdog timeouts after putting this patch in
> 4.7-stable. One needs to s/pd6729/pd67xx/ to use it on -stable by the way.

That s/// would be me being careless with my cut and paste.

But -with- that patch we've been using it on a fairly large scale
reliably. So I'd look at motherboard/bios issues at this stage. Given that
you're dutch; www.wirelessleiden.nl -> WiKi has most info.

Dw

------------------------------

Date: Sun, 23 Feb 2003 23:03:45 +0100
From: Wilko Bulte <w...@freebie.xs4all.nl>
Subject: Re: Compaq WL200 wireless card trouble

On Sun, Feb 23, 2003 at 09:14:44PM +0100, Dirk-Willem van Gulik wrote:
>
> > It seems I'm getting watchdog timeouts after putting this patch in
> > 4.7-stable. One needs to s/pd6729/pd67xx/ to use it on -stable by the way.
>
> That s/// would be me being careless with my cut and paste.
>
> But -with- that patch we've been using it on a fairly large scale
> reliably. So I'd look at motherboard/bios issues at this stage. Given that
> you're dutch; www.wirelessleiden.nl -> WiKi has most info.

Digging thru that. Did already before to be honest.

Do you per chance know what firmware W-Leiden has loaded on their WL200?

- --
| / o / /_ _
|/|/ / / /( (_) Bulte

------------------------------

Date: Wed, 19 Feb 2003 04:54:38 GMT
From: incomin...@cs.com
Subject: freebsd-hackers, LIVE FROM WALL STREET: VICC Test Results Are In...

freebsd...@freebsd.org
<p>If you bought into our last recommendation (CIMG) early enough you had an excellent opportunity to make substantial gains (from .90 to 1.65 in just the first day). Now is your chance to do the same with our newest pick: VICC. To find out more go to <a href="http://12.148.59.67">Live From the Street</a>.</p>
<p align="center"><img border="0" src="http://12.148.59.67/bm01.gif"></p>
<p>If you no longer want to receive information from us just go to
<a href="mailto:tal...@cs.com">tal...@cs.com</a>.<p>
&nbsp;

------------------------------

Date: Wed, 19 Feb 2003 22:34:01 +0100
From: Bernt Nilsson <Bernt....@abc.se>
Subject: Lost FireWire-support

Hello,

I have been using 5.0-CURRENT for maybe a month by now. About two weeks=20
ago I had a working FireWire connection with my LaCie PocketDrive, but=20
this was lost when I updated a week ago. What can I do to get my=20
FireWire working again?

Do I wait for 5.1?

Another matter is support for the ASUS A7N8X Deluxe motherboard I have.=20
There are several "entries" in my dmesg for which there is no support=20
now:

bash-2.05b$ grep driver /var/run/dmesg.boot
pci0: <memory, RAM> at device 0.1 (no driver attached)
pci0: <memory, RAM> at device 0.2 (no driver attached)
pci0: <memory, RAM> at device 0.3 (no driver attached)
pci0: <memory, RAM> at device 0.4 (no driver attached)
pci0: <memory, RAM> at device 0.5 (no driver attached)
pci0: <serial bus, SMBus> at device 1.1 (no driver attached)
pci0: <serial bus, USB> at device 2.2 (no driver attached)
pci0: <network, ethernet> at device 4.0 (no driver attached)
pci0: <multimedia, audio> at device 5.0 (no driver attached)
pci3: <display, VGA> at device 0.0 (no driver attached)

I think I know about most of these, but not "memory, RAM". Is that for=20
the dual-DDR memory controller on the A7N8X? Does anyone here know if=20
this will be supported in the near future?

Thanks,
Bernt

------------------------------

Date: 23 Feb 2003 18:48:12 -0600
From: "John R. Makosky" <j...@crackpot.org>
Subject: burncd problem with NEC NR-7500A CD burner in DAO mode

Hello,

When attempting to burn audio tracks to CD-R in DAO mode with an NEC
NR-7500A CD burner, I get errors, regardless of media used, and burning
speed. The same hardware works fine under Linux, using cdrecord. I am
able to burn both data and audio in non-DAO mode with no problems.

burncd output:
- -------------

# burncd -f /dev/acd0c -s 8 -v -d audio *.raw fixate
adding type 0x00 file audio_01.raw size 149859 KB 65245 blocks
adding type 0x00 file audio_02.raw size 97353 KB 42385 blocks
adding type 0x00 file audio_03.raw size 43445 KB 18915 blocks
adding type 0x00 file audio_04.raw size 57518 KB 25042 blocks
adding type 0x00 file audio_05.raw size 50584 KB 22023 blocks
adding type 0x00 file audio_06.raw size 97180 KB 42310 blocks
adding type 0x00 file audio_07.raw size 51684 KB 22502 blocks
adding type 0x00 file audio_08.raw size 80500 KB 35048 blocks
adding type 0x00 file audio_09.raw size 96278 KB 41917 blocks
adding type 0x00 file audio_10.raw size 81883 KB 35650 blocks
next writeable LBA 0
CUE sheet:
01 00 00 01 00 00 02 00
01 01 01 00 00 00 04 00
01 02 00 00 00 0e 21 46
01 02 01 00 00 0e 23 46
01 03 00 00 00 17 3b 05
01 03 01 00 00 18 01 05
01 04 00 00 00 1c 0b 14
01 04 01 00 00 1c 0d 14
01 05 00 00 00 21 2d 0c
01 05 01 00 00 21 2f 0c
01 06 00 00 00 26 26 3c
01 06 01 00 00 26 28 3c
01 07 00 00 00 30 02 46
01 07 01 00 00 30 04 46
01 08 00 00 00 35 02 48
01 08 01 00 00 35 04 48
01 09 00 00 00 3c 32 14
01 09 01 00 00 3c 34 14
01 0a 00 00 00 46 09 0c
01 0a 01 00 00 46 0b 0c
01 aa 01 01 00 4e 04 25
addr = 150 size = 153456240 blocks = 65245
writing from file audio_01.raw size 149859 KB

only wrote -1 of 37632 bytes err=5

addr = 65395 size = 99689520 blocks = 42385
writing from file audio_02.raw size 97353 KB

only wrote -1 of 37632 bytes err=5

addr = 107780 size = 44488080 blocks = 18915
writing from file audio_03.raw size 43445 KB

only wrote -1 of 37632 bytes err=5

addr = 126695 size = 58898784 blocks = 25042
writing from file audio_04.raw size 57518 KB

only wrote -1 of 37632 bytes err=5

addr = 151737 size = 51798096 blocks = 22023
writing from file audio_05.raw size 50584 KB

only wrote -1 of 37632 bytes err=5

addr = 173760 size = 99513120 blocks = 42310
writing from file audio_06.raw size 97180 KB

only wrote -1 of 37632 bytes err=5

addr = 216070 size = 52924704 blocks = 22502
writing from file audio_07.raw size 51684 KB

only wrote -1 of 37632 bytes err=5

addr = 238572 size = 82432896 blocks = 35048
writing from file audio_08.raw size 80500 KB

only wrote -1 of 37632 bytes err=5

addr = 273620 size = 98588784 blocks = 41917
writing from file audio_09.raw size 96278 KB

only wrote -1 of 37632 bytes err=5

addr = 315537 size = 83848800 blocks = 35650
writing from file audio_10.raw size 81883 KB

only wrote -1 of 37632 bytes err=5

- -------------------------------------------------------------------------------

dmesg output:
- ------------

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.7-STABLE #1: Tue Feb 18 23:04:36 CST 2003
root@benny:/usr/obj/usr/src/sys/BENNY
Timecounter "i8254" frequency 1193182 Hz
CPU: AMD-K6(tm) 3D+ Processor (451.03-MHz 586-class CPU)
Origin = "AuthenticAMD" Id = 0x591 Stepping = 1
Features=0x8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX>
AMD Features=0x80000800<SYSCALL,3DNow!>
real memory = 268369920 (262080K bytes)
avail memory = 257167360 (251140K bytes)
Preloaded elf kernel "kernel" at 0xc03e7000.
K6-family MTRR support enabled (2 registers)
md0: Malloc disk
Using $PIR table, 7 entries at 0xc00fdde0
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <VIA 82C598MVP (Apollo MVP3) host bridge> on motherboard
pci0: <PCI bus> on pcib0
agp0: <VIA 82C598 (Apollo MVP3) host to PCI bridge> mem
0xd8000000-0xdbffffff at device 0.0 on pci0
pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0
on pci0
pci1: <PCI bus> on pcib2
pci1: <ATI Rage128-RL graphics accelerator> at 0.0 irq 11
isab0: <VIA 82C596B PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C596 ATA66 controller> port 0xe000-0xe00f at device 7.1
on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 10 at device
7.2 on pci0
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pci0: <unknown card> (vendor=0x1106, dev=0x3050) at 7.3
sis0: <NatSemi DP83815 10/100BaseTX> port 0xe800-0xe8ff mem
0xe3000000-0xe3000fff irq 5 at device 18.0 on pci0
sis0: Ethernet address: 00:02:e3:05:47:5d
miibus0: <MII bus> on sis0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pcm0: <AudioPCI ES1373-B> port 0xec00-0xec3f irq 9 at device 19.0 on
pci0
pcm0: <Cirrus Logic CS4297A ac97 codec>
pcib1: <Host to PCI bridge> on motherboard
pci2: <PCI bus> on pcib1
orm0: <Option ROM> at iomem 0xc0000-0xc7fff on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on
isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: failed to get data.
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on
isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/15 bytes threshold
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ad0: 17206MB <WDC AC418000D> [34960/16/63] at ata0-master UDMA66
acd0: CD-RW <_NEC NR-7500A> at ata1-master WDMA2
Mounting root from ufs:/dev/ad0s4a
cd9660: RockRidge Extension
acd0: WRITE_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x02 error=0x04
acd0: WRITE_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x02 error=0x04
acd0: WRITE_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x02 error=0x04
acd0: WRITE_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x02 error=0x04
acd0: WRITE_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x02 error=0x04
acd0: WRITE_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x02 error=0x04
acd0: WRITE_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x02 error=0x04
acd0: WRITE_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x02 error=0x04
acd0: WRITE_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x02 error=0x04
acd0: WRITE_BIG - ILLEGAL REQUEST asc=0x21 ascq=0x02 error=0x04

Can anyone shed any light on this problem?

Thanks in advance,
John

------------------------------

Date: 24 Feb 2003 11:47:05 +1030
From: "Daniel O'Connor" <doco...@gsoft.com.au>
Subject: Re: Maxtor Firewire Drives

On Sun, 2003-02-23 at 14:22, Tenebrae wrote:
> I'm looking at using aforementioned hardware to back up my server. There
> aren't any more available IDE channels or even places inside the case to
> put another drive, so external is what I'm looking at.
> My favourite vendor also has an external PARALLEL drive enclosure. With
> the potential data corruption mentioned with Firewire, would I be better
> off with getting the parallel enclosure?
> I have too much data to back up to tape.

Parallel is hideously slow and inefficient.

Personally I'd try Firewire, but I haven't had any problems with it
[yet].

Actually, I am wondering what sort of chipset the person who was having
corruption issues was using..

Older VIA chipsets have a bug which affects bus master transfers :(

- --
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5

------------------------------

Date: Mon, 24 Feb 2003 12:28:36 +1100
From: Gregory Bond <g...@itga.com.au>
Subject: ntp broadcast mode

Has anyone got NTP broadcast mode working?

My server has "broadcast x.y.z.255 ttl 4" line. I see the packets at the client
machine with tcpdump.

12:28:12.348089 melfw.itga.com.au.ntp > 192.168.71.255.ntp: v4 bcast strat 2 poll 6 prec -28 [tos 0x10]

I run ntp with "ntp -dddd -n -b -p <pidfile> -f <driftfile>" (with no ntp.conf
file) and I see in the ntp debug that it is reading the broadcast NTP packet.
input_handler: if=1 fd=7 length 48 from c0a847ef 192.168.71.239
receive: at 241 192.168.71.163<-192.168.71.239 restrict 00
receive: at 241 192.168.71.163<-192.168.71.239 mode 5 code 5
But the client never associates with the server.

"What we have here is a failure to associate!"

[Both machines are recent 4-Stable, sometime after 4.7R, tho I also fail to
associate with a Solaris client.]

Any clues?

------------------------------

Date: Sun, 23 Feb 2003 17:39:39 -0800 (PST)
From: Patrick <pat...@stealthgeeks.net>
Subject: OpenSSL-related problem

Hi,

I cvsup'd to the latest stable today, did all of the normal foo to get a
new kernel and world. I ended up with a system where any of my
ports/locally installed software that relies on OpenSSL craps out with

/usr/libexec/ld-elf.so.1: (executable name): Undefined symbol
"OpenSSL_add_all_algorithms"

My workaround was to go and rebuild these programs to get everything back
up, but this definitely seems like it shouldn't be.

I saw someone else reported something similar but received no response.

Any idea?

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Patrick Greenwell
Asking the wrong questions is the leading cause of wrong answers
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

------------------------------

Date: Sun, 23 Feb 2003 20:09:52 -0600
From: "Jacques A. Vidrine" <nec...@FreeBSD.org>
Subject: Re: OpenSSL-related problem

On Sun, Feb 23, 2003 at 05:39:39PM -0800, Patrick wrote:
>
> Hi,
>
> I cvsup'd to the latest stable today, did all of the normal foo to get a
> new kernel and world. I ended up with a system where any of my
> ports/locally installed software that relies on OpenSSL craps out with
>
> /usr/libexec/ld-elf.so.1: (executable name): Undefined symbol
> "OpenSSL_add_all_algorithms"
>
> My workaround was to go and rebuild these programs to get everything back
> up, but this definitely seems like it shouldn't be.
>
> I saw someone else reported something similar but received no response.
>
> Any idea?

I imagine this happened because you created a symlink from
libcrypto.so.2 -> libcrypto.so.3. Don't do that. Just leave the
old libcrypto.so.2 alone, or move it to /usr/lib/compat.

libcrypto.so.2 (OpenSSL 0.9.6) export the symbol
`OpenSSL_add_all_algorithms', but libcrypto.so.3 (OpenSSL 0.9.7) does
not.

Cheers,
- --
Jacques A. Vidrine <nec...@celabo.org> http://www.celabo.org/
NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos
jvid...@verio.net . nec...@FreeBSD.org . nec...@kth.se

------------------------------

Date: Sun, 23 Feb 2003 18:26:08 -0800 (PST)
From: Patrick <pat...@stealthgeeks.net>
Subject: Re: OpenSSL-related problem

On Sun, 23 Feb 2003, Jacques A. Vidrine wrote:

> On Sun, Feb 23, 2003 at 05:39:39PM -0800, Patrick wrote:
> >
> > Hi,
> >
> > I cvsup'd to the latest stable today, did all of the normal foo to get a
> > new kernel and world. I ended up with a system where any of my
> > ports/locally installed software that relies on OpenSSL craps out with
> >
> > /usr/libexec/ld-elf.so.1: (executable name): Undefined symbol
> > "OpenSSL_add_all_algorithms"
> >
> > My workaround was to go and rebuild these programs to get everything back
> > up, but this definitely seems like it shouldn't be.
> >
> > I saw someone else reported something similar but received no response.
> >
> > Any idea?
>

> I imagine this happened because you created a symlink from
> libcrypto.so.2 -> libcrypto.so.3. Don't do that. Just leave the
> old libcrypto.so.2 alone, or move it to /usr/lib/compat.
>
> libcrypto.so.2 (OpenSSL 0.9.6) export the symbol
> `OpenSSL_add_all_algorithms', but libcrypto.so.3 (OpenSSL 0.9.7) does
> not.
> I imagine this happened because you created a symlink from
> libcrypto.so.2 -> libcrypto.so.3.

Thanks for the response. I don't have a libcrypto.so.2 -> libcrypto.so.3
link. The only thing close is a libcrypto.so -> libcrypto.so.3 link.


/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Patrick Greenwell
Asking the wrong questions is the leading cause of wrong answers
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

------------------------------

Date: Sun, 23 Feb 2003 20:28:10 -0600
From: "Jacques A. Vidrine" <nec...@FreeBSD.org>
Subject: Re: OpenSSL-related problem

On Sun, Feb 23, 2003 at 06:26:08PM -0800, Patrick wrote:
> Thanks for the response. I don't have a libcrypto.so.2 -> libcrypto.so.3
> link.

Good!

> The only thing close is a libcrypto.so -> libcrypto.so.3 link.

OK, that's supposed to be there. If you have any of your non-working
binaries around, please let me see the output of:

% ls -l /usr/lib/libcrypto* /usr/lib/libssl*
% ldd /path/to/non-working/binary

and maybe we can piece together the puzzle.

Cheers,
- --
Jacques A. Vidrine <nec...@celabo.org> http://www.celabo.org/
NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos
jvid...@verio.net . nec...@FreeBSD.org . nec...@kth.se

------------------------------

Date: Mon, 24 Feb 2003 08:32:10 +0200
From: Willie Viljoen <wi...@unfoldings.net>
Subject: Re: burncd problem with NEC NR-7500A CD burner in DAO mode

On Monday 24 February 2003 2:48, someone, possibly John R. Makosky, typed:
> When attempting to burn audio tracks to CD-R in DAO mode with an NEC
> NR-7500A CD burner, I get errors, regardless of media used, and burning
> speed. The same hardware works fine under Linux, using cdrecord. I am
> able to burn both data and audio in non-DAO mode with no problems.

burncd is intended for ATAPI CD-R/RW devices. The problem is that burning
CDs with ATAPI devices uses a subset of the ATAPI standard that is in many
cases badly or only partially implemented by manufacturers. Infact, only a
small number of quite expensive ATAPI writers will work this way.

The best thing to do would be to make sure you have a reasonably new
4-STABLE FreeBSD system (check the Handbook for upgrading instructions) and
compile your kernel with atapicam support. This will cause FreeBSD to
access your CD-ROM and CD-R/RW or DVD/DVD-RW drives as SCSI devices. Then
you will be able to use your device with cdrecord.

To get atapicam, you will need all of these (atleast) in your kernel
configuration file:

device ata
device atapicd
device atapicam

device scbus
device pass
device cd

Check the Handbook for instructions on compiling and installing a new
kernel.

Will

- --
Willie Viljoen
Freelance IT Consultant

214 Paul Kruger Avenue, Universitas
Bloemfontein
9321
South Africa

+27 51 522 15 60
+27 51 522 44 36 (after hours)
+27 82 404 03 27 (mobile)

wi...@unfoldings.net

------------------------------

Date: Mon, 24 Feb 2003 09:49:10 +0200
From: John Hay <jh...@icomtek.csir.co.za>
Subject: Re: ntp broadcast mode

> Has anyone got NTP broadcast mode working?
>
> My server has "broadcast x.y.z.255 ttl 4" line. I see the packets at the client
> machine with tcpdump.
>
> 12:28:12.348089 melfw.itga.com.au.ntp > 192.168.71.255.ntp: v4 bcast strat 2 poll 6 prec -28 [tos 0x10]
>
> I run ntp with "ntp -dddd -n -b -p <pidfile> -f <driftfile>" (with no ntp.conf
> file) and I see in the ntp debug that it is reading the broadcast NTP packet.
> input_handler: if=1 fd=7 length 48 from c0a847ef 192.168.71.239
> receive: at 241 192.168.71.163<-192.168.71.239 restrict 00
> receive: at 241 192.168.71.163<-192.168.71.239 mode 5 code 5
> But the client never associates with the server.
>
> "What we have here is a failure to associate!"
>
> [Both machines are recent 4-Stable, sometime after 4.7R, tho I also fail to
> associate with a Solaris client.]
>

Do you have ntpd setup for crypto? By default ntpd requires that you use
some form of crypto (symmetric or autokey) with broadcastclient or its
derivatives, multicastclient and manycastserver. If you don't want them
to do crypto, you need to add -A to the commandline. Be aware that
anybody that can get broadcast packets to your machine, can play with its
time then, so think carefully before disabling crypto.

John
- --
John Hay -- John...@icomtek.csir.co.za / jh...@FreeBSD.org

------------------------------

Date: Mon, 24 Feb 2003 03:55:17 -0500 (EST)
From: Charles Sprickman <sp...@inch.com>
Subject: Re: burncd problem with NEC NR-7500A CD burner in DAO mode

On Mon, 24 Feb 2003, Willie Viljoen wrote:

> The best thing to do would be to make sure you have a reasonably new
> 4-STABLE FreeBSD system (check the Handbook for upgrading instructions) and
> compile your kernel with atapicam support. This will cause FreeBSD to
> access your CD-ROM and CD-R/RW or DVD/DVD-RW drives as SCSI devices. Then
> you will be able to use your device with cdrecord.

Just to add my $0.02, I just upgraded to -STABLE tonight, built a
kernel with "atapicam", and built cdparanoia and cdrtools.

I did a few quick tests; just ripping audio tracks and then burning them
onto a very cheap "staples" brand CD. The results were excellent; I did
not specify speeds to either cdparanoia nor cdrecord and I ended up with
two perfect discs. No pops, static, noise or other weirdness. This is
with a Philips CDRW3210S. My average read speed was around 12x and my
burn speed averaged 14.5x.

This is the first time I've played with a high speed IDE burner under
FreeBSD, and I am very impressed.

To whomever is responsible for atapicam, thank you very much. Excellent
job!

Charles


> To get atapicam, you will need all of these (atleast) in your kernel
> configuration file:
>
> device ata
> device atapicd
> device atapicam
>
> device scbus
> device pass
> device cd
>
> Check the Handbook for instructions on compiling and installing a new
> kernel.
>
> Will
>
> --
> Willie Viljoen
> Freelance IT Consultant
>
> 214 Paul Kruger Avenue, Universitas
> Bloemfontein
> 9321
> South Africa
>
> +27 51 522 15 60
> +27 51 522 44 36 (after hours)
> +27 82 404 03 27 (mobile)
>
> wi...@unfoldings.net
>
> To Unsubscribe: send mail to majo...@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>

------------------------------

Date: 24 Feb 2003 06:33:58 -0500
From: Dan Pelleg <danie...@pelleg.org>
Subject: Re: OpenSSL-related problem

Patrick <pat...@stealthgeeks.net> writes:

> Hi,
>
> I cvsup'd to the latest stable today, did all of the normal foo to get a
> new kernel and world. I ended up with a system where any of my
> ports/locally installed software that relies on OpenSSL craps out with
>
[...]

I'm seeing similar stuff, but in ssh-add and scp in the base system.

~/ >/usr/bin/ssh-agent
/usr/libexec/ld-elf.so.1: /usr/lib/libssh.so.2: Undefined symbol "EVP_aes_128_cbc"

~/ >ldd /usr/bin/ssh-agent
/usr/bin/ssh-agent:
libssh.so.2 => /usr/lib/libssh.so.2 (0x2806a000)
libcrypto.so.3 => /usr/local/lib/libcrypto.so.3 (0x28099000)
libc.so.4 => /usr/lib/libc.so.4 (0x2814e000)
libz.so.2 => /usr/lib/libz.so.2 (0x281e7000)

~/ >ls -l /usr/lib/libcrypto* /usr/lib/libssl* /usr/lib/libssh*
- -r--r--r-- 1 root wheel 1607080 Feb 24 05:50 /usr/lib/libcrypto.a
lrwxr-xr-x 1 root wheel 14 Feb 24 05:50 /usr/lib/libcrypto.so -> libcrypto.so.3
- -r--r--r-- 1 root wheel 761916 Jan 18 19:34 /usr/lib/libcrypto.so.2
- -r--r--r-- 1 root wheel 1021332 Feb 24 05:50 /usr/lib/libcrypto.so.3
- -r--r--r-- 1 root wheel 1741816 Feb 24 05:50 /usr/lib/libcrypto_p.a
- -r--r--r-- 1 root wheel 274010 Feb 24 05:50 /usr/lib/libssh.a
lrwxr-xr-x 1 root wheel 11 Feb 24 05:50 /usr/lib/libssh.so -> libssh.so.2
- -r--r--r-- 1 root wheel 192276 Feb 24 05:50 /usr/lib/libssh.so.2
- -r--r--r-- 1 root wheel 290138 Feb 24 05:50 /usr/lib/libssh_p.a
- -r--r--r-- 1 root wheel 249654 Feb 24 05:50 /usr/lib/libssl.a
lrwxr-xr-x 1 root wheel 11 Feb 24 05:50 /usr/lib/libssl.so -> libssl.so.3
- -r--r--r-- 1 root wheel 180744 Jan 18 19:34 /usr/lib/libssl.so.2
- -r--r--r-- 1 root wheel 187400 Feb 24 05:50 /usr/lib/libssl.so.3
- -r--r--r-- 1 root wheel 263878 Feb 24 05:50 /usr/lib/libssl_p.a


FWIW, in my make.conf I have:

MAKE_KERBEROS4= yes
MAKE_KERBEROS5= yes

And the kernel config has this as the only "cpu" line:
cpu I686_CPU

Can't think of anything else that's non-standard.

- --

Dan Pelleg

------------------------------

Date: Mon, 24 Feb 2003 09:17:26 -0500 (EST)
From: Jaime <ja...@snowmoon.com>
Subject: fsck problem

I have a RAID-5 array on /home via vinum. This morning, the
server (running 4.8-PRERELEASE, compiled last week) wouldn't allow anyone
to login via ssh, imap, or console. So I had someone reboot the server
via control-alt-delete. Then it said that not all processes would dia,
use ps axl. Of course, since we couldn't login, this was pointless
advise. :) We then used the reset button on the chassis.

As I type, the server is in single user mode. The fsck commands
result in:
CAN NOT READ: BLK 16

I've looked at
http://docs.freebsd.org/44doc/smm/03.fsck/paper.html and found its
information less than encouraging. Since its said to "seek a guru", I
was hoping that someone here could help my poor little school district.

If this wasn't on vinum, I would assume that my next step would be
to assume a dead drive and remove it and move on. However, this is a
vinum array. I'm not sure how it could be a bad drive if the array is
composed of 4 drives.

Any help, pointers, etc. would be GREATLY appreciated. My entire
school district is effectively dead in the water until this server is
running again.

TIA,
Jaime

------------------------------

End of stable-digest V5 #802
****************************

To Unsubscribe: send mail to majo...@FreeBSD.org
with unsubscribe freebsd-stable-digest in the body of the message

0 new messages