Re: wi0 almost works with Wavelan Turbo card

[Ernie Elu]

> Of all the gin joints in all the towns in all the world, Ernie Elu had 
> to walk into mine and say:
> 
> > I am looking for help with getting a Lucent Wavelan Turbo ISA (Bronze) 
> > card running.
> 
> What speed is the card, exactly.

It runs in 3 modes, I have been testing in high speed mode which is
supposed to be 10Mbps also the default mode. It can fall back to 2Mbps when
talking to older cards or other 802.11 compatible cards.


> 
> > Having read a few posts about the Wavelan IEEE 802.11 card not working with
> > the wi driver I thought I would give it a go anyway with the turbo card.
> 
> "Not working with the wi driver?" I hope you meant "now working."

Good point:)

> 
> > I installed a Wavelan Turbo PCMCIA card in my Toshiba 2520CDT notebook, and
> > an idetical card with the Wavelan ISA adapter board into an Advantech 6154
> > Slot PC.
> 
> I am not familiar with an "Advantech 6154 Slot PC." Please don't assume that
> everyone automatically knows your hardware by name. Describe it. In detail.
>

It's a slot PC that plugs into an ISA passive backplane, popular with the
picobsd crowd.

It has the following probed hardware:

 Copyright (c) 1992-1999 The FreeBSD Project.
 Copyright (c) 1982, 1986, 1989, 1991, 1993
 The Regents of the University of California. All rights reserved.
 FreeBSD 4.0-CURRENT #3: Mon Jul 19 15:35:49 EST 1999
 [EMAIL PROTECTED]:/usr/src/sys/compile/ADVANTECH
 Timecounter "i8254"  frequency 1193182 Hz
 CPU: AMD-K6(tm) 3D processor (299.52-MHz 586-class CPU)
   Origin = "AuthenticAMD"  Id = 0x58c  Stepping = 12
   Features=0x8021bf
   AMD Features=0x8800
 real memory  = 15728640 (15360K bytes)
 avail memory = 12660736 (12364K bytes)
 Preloaded elf kernel "kernel" at 0xc02bf000.
 K6-family MTRR support enabled (2 registers)
 Probing for PnP devices:
 npx0:  on motherboard
 npx0: INT 16 interface
 pcib0:  on motherboard
 pci0:  on pcib0
 isab0:  at device 1.0 on pci0
 ide_pci0:  irq 14 at device 1.1 on pci0
 rl0:  irq 11 at device 17.0 on pci0
 rl0: Ethernet address: 00:c0:6c:74:55:92
 rl0: autoneg complete, link status good (half-duplex, 10Mbps)
 vga-pci0:  irq 15 at device 20.0 on pci0
 isa0:  on motherboard
 fdc0:  at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: <1440-KB 3.5" drive> at fdc0 drive 0
 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
 wdc0: unit 0 (wd0): 
 wd0: 2446MB (5009760 sectors), 4970 cyls, 16 heads, 63 S/T, 512 B/S
 wdc0: unit 1 (atapi): , removable, accel, ovlap, dma, iordis
 wcd0: drive speed 5512KB/sec, 128KB cache
 wcd0: supported read types: CD-R, CD-RW, CD-DA, packet track
 wcd0: Audio: play, 256 volume levels
 wcd0: Mechanism: ejectable tray
 wcd0: Medium: no/blank disc inside, unlocked
 atkbdc0:  at port 0x60-0x6f on isa0
 atkbd0:  irq 1 on atkbdc0
 psm0:  irq 12 on atkbdc0
 psm0: model Generic PS/2 mouse, device ID 0
 vga0:  at port 0x3b0-0x3df iomem 0xa-0xb on isa0
 sc0:  on isa0
 sc0: VGA <16 virtual consoles, flags=0x200>
 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
 PC-Card Vadem 469 (5 mem & 2 I/O windows)
 pcic: controller irq 5
 Initializing PC-card drivers: wi
 changing root device to wd0s1a
 Card inserted, slot 0
 wi0:  at 0x240-0x27f irq 10 on isa
 wi0: Ethernet address: 00:60:1d:04:72:6a
 

> > Both computers are running FreeBSD 4.0-CURRENT with their IRQ set
> > to 10 in pccard.conf, all other settings are default.
> > 
> > It sort of works, the notebook end seems fine, but the Advantech end keeps
> > coming up with the same error on the console every few seconds when there is
> > traffic between them:
> > 
> > wi0: oversized packet received (wi_dat_len=24576, wi_status=0x2000)
> > 
> > No such error on the laptop.
> > 
> > When the error occurs ftp or whatever you were doing stalls for a bit then
> > continues.
> > 
> > Any suggestions?
> 
> No. I never obtained any real documentation from Lucent (they won't release
> the Hermes programming manual without NDA) and I don't have a turbo WaveLAN
> card so I'm unable to duplicate your problem on my own equipment. If I can't
> duplicate the problem and analyze it, I can't even begin to fix it.
> 
> -Bill


I think the source to their Linux driver for the 802.11 card is at:

FTP://FTP.WAVELAN.COM/PUB/SOFTWARE/IEEE/PC_CARD/LINUX/wavelan2_cs-3.10.tar.gz

It's supposed to work with the turbo card, according to the one line comment at:
http://www.wavelan.com/support/software/index.html


There is also a version 4 linux driver for the silver card, thats the one with 
the WEV encryption.

- Ernie.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

readline/readline.h missing from 4-current snapshots

[Satoshi Asami]

The recent current snapshots are missing readline.h.  It has been
missing since at least the July 4 snap at current/releng3.freebsd.org.

Satoshi
---
# tar tvf bindist.tar | grep readline
drwxr-xr-x root/wheel 0 Jul 15 04:01 1999 usr/include/readline/
-r--r--r-- root/wheel202008 Jul 15 04:04 1999 usr/lib/libreadline.a
-r--r--r-- root/wheel138156 Jul 15 04:04 1999 usr/lib/libreadline.so.4
lrwxrwxrwx root/wheel 0 Jul 19 00:20 1999 usr/lib/libreadline.so -> 
libreadline.so.4
drwxr-xr-x root/wheel 0 Jul 15 04:02 1999 
usr/libdata/perl/5.00503/mach/readline/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: wi0 almost works with Wavelan Turbo card

[Bill Paul]

Of all the gin joints in all the towns in all the world, Ernie Elu had 
to walk into mine and say:

> I am looking for help with getting a Lucent Wavelan Turbo ISA (Bronze) 
> card running.

What speed is the card, exactly.

> Having read a few posts about the Wavelan IEEE 802.11 card not working with
> the wi driver I thought I would give it a go anyway with the turbo card.

"Not working with the wi driver?" I hope you meant "now working."

> I installed a Wavelan Turbo PCMCIA card in my Toshiba 2520CDT notebook, and
> an idetical card with the Wavelan ISA adapter board into an Advantech 6154
> Slot PC.

I am not familiar with an "Advantech 6154 Slot PC." Please don't assume that
everyone automatically knows your hardware by name. Describe it. In detail.

> Both computers are running FreeBSD 4.0-CURRENT with their IRQ set
> to 10 in pccard.conf, all other settings are default.
> 
> It sort of works, the notebook end seems fine, but the Advantech end keeps
> coming up with the same error on the console every few seconds when there is
> traffic between them:
> 
> wi0: oversized packet received (wi_dat_len=24576, wi_status=0x2000)
> 
> No such error on the laptop.
> 
> When the error occurs ftp or whatever you were doing stalls for a bit then
> continues.
> 
> Any suggestions?

No. I never obtained any real documentation from Lucent (they won't release
the Hermes programming manual without NDA) and I don't have a turbo WaveLAN
card so I'm unable to duplicate your problem on my own equipment. If I can't
duplicate the problem and analyze it, I can't even begin to fix it.

-Bill

-- 
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home:  [EMAIL PROTECTED] | Columbia University, New York City
=
 "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

wi0 almost works with Wavelan Turbo card

[Ernie Elu]

I am looking for help with getting a Lucent Wavelan Turbo ISA (Bronze) card running.

Having read a few posts about the Wavelan IEEE 802.11 card not working with
the wi driver I thought I would give it a go anyway with the turbo card.


I installed a Wavelan Turbo PCMCIA card in my Toshiba 2520CDT notebook, and
an idetical card with the Wavelan ISA adapter board into an Advantech 6154
Slot PC. Both computers are running FreeBSD 4.0-CURRENT with their IRQ set
to 10 in pccard.conf, all other settings are default.

It sort of works, the notebook end seems fine, but the Advantech end keeps
coming up with the same error on the console every few seconds when there is
traffic between them:

wi0: oversized packet received (wi_dat_len=24576, wi_status=0x2000)

No such error on the laptop.

When the error occurs ftp or whatever you were doing stalls for a bit then
continues.

Any suggestions?

- Ernie.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Question about MTRR boot message

[Oliver Fromme]

First, thank you for answering my question.

Amancio Hasty wrote in list.freebsd-current:
 > Is a nice feature if you happen to have a fast video card . It speed up writes 
 > by
 > four times. 

That particular box of mine contains an ISA VGA graphics card
with 256 Kbyte video memory.  It's a server, not a desktop
machine (in fact it wouldn't need a gfx card at all, but it's
more convenient than a serial console).

 > The MTTR stuff is an old hack which some motherboards enabled it
 > automatically for you. 
 > 
 > So to answer your question , the MTTR stuff is supposed to disabled caching
 > to your VGA card.

OK, so it has nothing to do with disabling caching for my main
memory, which was my concern.  :-)  Thanks for making that
clear.

BTW, is there a way to disable that MTRR stuff?  Just to be
sure...  And I really don't need it.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Question about MTRR boot message

[Amancio Hasty]

Is a nice feature if you happen to have a fast video card . It speed up writes 
by
four times. 

Long time ago, tests writing to my Matrox millenium would yield about 20MB/sec.

With MTTR enabled -- wrote a litte hack over here to do it -- the same
test generated about 80MB/sec create for dumping raw video to my 
Matrox Millenium.

The MTTR stuff is an old hack which some motherboards enabled it
automatically for you. 

So to answer your question , the MTTR stuff is supposed to disabled caching
to your VGA card.

Cheers

> Hi,
> 
> There's the following message in my dmesg:
> 
>"Pentium Pro MTRR support enabled, default memory type is uncacheable"
> 
> I seriously hope that it does not mean that my memory
> is not chached...  does it?  I haven't found any manual
> pages or other docs about it.
> 
> (If it matters:  I cvsupped and built a -current world
> yesterday.  It's an SMP box (dual Celeron), which seems
> to run fine so far.)
> 
> Regards
>Oliver
> 
> -- 
> Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
> (Info: finger userinfo:[EMAIL PROTECTED])
> 
> "In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
>  (Terry Pratchett)
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message

-- 

 Amancio Hasty
 [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Question about MTRR boot message

[Oliver Fromme]

Hi,

There's the following message in my dmesg:

   "Pentium Pro MTRR support enabled, default memory type is uncacheable"

I seriously hope that it does not mean that my memory
is not chached...  does it?  I haven't found any manual
pages or other docs about it.

(If it matters:  I cvsupped and built a -current world
yesterday.  It's an SMP box (dual Celeron), which seems
to run fine so far.)

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ftp current.freebsd.org

[Oliver Fromme]

Adam Smaza wrote in list.freebsd-current:
 > Why can I access current.freebsd.org ?
 > All connections are refused.

You can use releng3.freebsd.org, it has the same contents.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: PLIP is still broken :(

[David O'Brien]

> Does anybody have a plans to fix plip code which is broken a quite
> awhile (several months or so)? 

Since I used it just last week on two -CURRENT boxes, I'd say there is
some other problem you are experecing.

-- 
-- David([EMAIL PROTECTED]  -or-  [EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: PLIP is still broken :(

[Maxim Sobolev]

David O'Brien wrote:

> > Does anybody have a plans to fix plip code which is broken a quite
> > awhile (several months or so)?
>
> Since I used it just last week on two -CURRENT boxes, I'd say there is
> some other problem you are experecing.

I'm also using two -current boxes (P133 and K6-2/300) and when trying to
do more or less massive file transfer one of the boxes dying with panic
(usually one with a slower processor, but not alvays). Changing ppc
flags also doesn't resolve a problem. If you can please try to test it
by doing "ping -f -s 8000 other_side" - this test actually bring one
side to its knees it several seconds (at lease for me). Some time ago I
had rised this question and Bruce Evans told that this problem arise
because of switch to newbus. Maybe you can look at his original meassage
at:
http://www.freebsd.org/cgi/getmsg.cgi?fetch=1692956+1694453+/usr/local/www/db/text/1999/freebsd-current/19990607.freebsd-current

-Maxim


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

make buildworld -DWANT_AOUT -DCOMPAT3X fails on 4.0-current

[nakaji]

I got this error on last Friday in Japan.

The last part of log is following.

--->8--->8--->8--->8--->8--->8--->8---
===> compat/compat3x
install -c -o root -g wheel -m 444 libf2c.so.2 libg++.so.4 libstdc++.so.2  
/usr/obj/aout/usr/src/tmp/usr/lib/aout/compat
usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2
   install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ...
 fileN directory
   install -d [-g group] [-m mode] [-o owner] directory ...
*** Error code 64

Stop.
(snip)
Fri Jul 16 15:21:48 JST 1999
--->8--->8--->8--->8--->8--->8--->8---

The log is made by the command,
(date; make buildworld; date) 2>&1 | tee -a make.bw.$(date "+%y%m%d")
---
NAKAJI Hiroyuki


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problem with cvsup

[Tugrul Galatali]

On 18 Jul 1999, Dag-Erling Smorgrav wrote:

> obituary <[EMAIL PROTECTED]> writes:
> > If anyone can shed some light on my situation (or has experienced
> > similar troubles themselves) I'd be most grateful to hear from you.
> 
> You forgot to attach the output of 'ipfw -a l'.
> 

The exact cvsup command would also be nice I think. Are you using
"-P m" as the FAQ hints at if you are behind a firewall?



> DES
> -- 
> Dag-Erling Smorgrav - [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

PLIP is still broken :(

[Maxim Sobolev]

Does anybody have a plans to fix plip code which is broken a quite
awhile (several months or so)? I could send several panic backtraces if
anyone will express interest in it.

-Maxim




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Question about MTRR on AMD chips

[Maxim Sobolev]

Does anybody can clarify starting from which model/revisions MTRR is
supported on k6 family chips, because in the list archives I found that
it supported starting from k6-II, but when I'm trying to configure it
using memcontrol on my k6-II (rev. 0) I'm only get a varionus error
massages.

Sincerely,

Maxim





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

ftp current.freebsd.org

[Adam Smaza]

Why can I access current.freebsd.org ?
All connections are refused.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: please test (linux emulation)

[Marcel Moolenaar]

Poul-Henning Kamp wrote:
> 
> I have no idea how to excercise this piece of code, if somebody
> could verify that it still DTRT I would be most grateful.

[piece of code snipped]

If nobody replies, then I'll run the code with verification (eg the
original code) until I know it has been used. If the new code behaves
differently than the original code, It will show. That's the best thing I
can do right now. 

-- 
Marcel Moolenaar  mailto:[EMAIL PROTECTED]
SCC Internetworking & Databases http://www.scc.nl/
Amsterdam, The Netherlands tel: +31 20 4200655


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Some problems with atapi-drivers under -current...

[Osokin Sergey]

Hello!
I try to use new atapi-drivers under -current & have some problems.
at kernel:

controller  ata0
device  atadisk0
device  atapicd0
device  atapifd0

I have following devices:
IDE0: HDD UDMA (master)
IDE1: CD-ROM (master)
IDE1: LS-120 (slave)

Kernel can't detect my LS-120, it says:

Jul 18 19:15:39 ozz /kernel: ata-pci0:  at
device 7.1 on pci0
Jul 18 19:15:39 ozz /kernel: ata-pci0: Busmastering DMA supported
Jul 18 19:15:39 ozz /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 
Jul 18 19:15:39 ozz /kernel: ata1 at 0x0170 irq 15 on ata-pci0

Jul 18 19:15:40 ozz /kernel: ata1: unwanted interrupt 1 status = 00

Jul 18 19:15:40 ozz /kernel: ata0: master: setting up WDMA2 mode on
PIIX3/4 chip OK
Jul 18 19:15:40 ozz /kernel: ad0:  ATA-3 disk at
ata0 as master
Jul 18 19:15:40 ozz /kernel: ad0: 2503MB (5126688 sectors), 5086 cyls, 16
heads, 63 S/T, 512 B/S
Jul 18 19:15:40 ozz /kernel: ad0: piomode=4, dmamode=2, udmamode=-1
Jul 18 19:15:40 ozz /kernel: ad0: 16 secs/int, 0 depth queue, DMA mode
Jul 18 19:15:40 ozz /kernel: acd0:  CDROM
drive at ata1 as master
Jul 18 19:15:40 ozz /kernel: acd0: drive speed 171 - 8250KB/sec, 128KB
cache
Jul 18 19:15:40 ozz /kernel: acd0: supported read types: CD-R, CD-RW,
CD-DA, packet track
Jul 18 19:15:40 ozz /kernel: acd0: Audio: play, 255 volume levels
Jul 18 19:15:40 ozz /kernel: acd0: Mechanism: ejectable tray
Jul 18 19:15:40 ozz /kernel: acd0: Medium: no/blank disc inside, unlocked
Jul 18 19:15:40 ozz /kernel: changing root device to wd0s1a

& nothing about LS-120...

Old drivers (aka wdcX, wcd0 & wfd0) detect all devices & work correct.

And another problem: if i use kernel with atapicd0, wcdplay play one track
from CD & stop. If i use wcd0, wcdplay play all tracks.

Any idea?

Rgdz,
ïÓÏËÉÎ óÅÒÇÅÊ aka oZZ,
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ata delay

[Trevor Johnson]

> Hi!

Hi, Thomas.

> I switched to the ata IDE driver some time ago. Since then, booting
> stops for about 30 seconds when the driver is installed. It didn't
> happen when using the old wd driver.

In /usr/src/sys/i386/conf/LINT it says:

# This option allow you to override the default probe time for IDE
# devices, to get a faster probe.  Setting this below 1 violate
# the IDE specs, but may still work for you (it will work for most
# people).
#
options   IDE_DELAY=8000  # Be optimistic about Joe IDE device
__
Trevor Johnson



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problem with cvsup

[Dag-Erling Smorgrav]

obituary <[EMAIL PROTECTED]> writes:
> If anyone can shed some light on my situation (or has experienced
> similar troubles themselves) I'd be most grateful to hear from you.

You forgot to attach the output of 'ipfw -a l'.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Problem with cvsup

[obituary]

I've been having some trouble with cvsup of late, and unfortunately I'm
at a complete loss as to what may be causing it.

There are two machines here that I've tried to update.  My personal
machine runs 4.0-CURRENT and the network firewall that runs 3.2-RELEASE.

The cvsup program establishes a connection with a server properly, and
everything is fine up until the "Running" phase.  It's at this point
where the transfer rate falls through the floor.  Data is only
transferred in short bursts of, say, 5k at a time, once every 10-15
seconds.  After about 3 minutes of this behaviour the connection goes
completely idle and eventually times out with the error:

TreeList failed: Network write failure: Connection timed out

The strange thing is that this problem only occurs when I'm using
FreeBSD on my firewall box.  I initially thought that my firewall rule
set could be to blame, so I flushed all the rules and set the default
policy to pass all packets.  I then tried to cvsup the 3.2-RELEASE box
using a direct modem connection to the net (no natd/firewall in the
road), but still no luck.

The last successful cvsup I did was about a month and a half ago, and at
that time the firewall box was a linux machine using IP masquerading. 
I'd kept the harddrive with the linux setup around "just in case" so I
swapped the harddrives, booted linux, and tried a cvsup from my
4.0-CURRENT machine (using linux as the firewall).  It worked flawlessly
-- and now I'm *really* confused.  The FreeBSD 3.2-RELEASE firewall box
has worked perfectly for everything I've used it for (web browsing, ftp,
mail, news, etc.) and yet it stumbles over cvsup connections??

If anyone can shed some light on my situation (or has experienced
similar troubles themselves) I'd be most grateful to hear from you.


-jake (obituary)  Powered by FreeBSD
[EMAIL PROTECTED] http://www.freebsd.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message