wi(4), hostap mode and WEP

2002-08-18 Thread Gregory Bond


I have a DLINK 520 PCI card on a FreeBSD server (running 4.6-stable from around 
20 July) and a DLink 650 PCMCIA card in a WinMe laptop.

I can get these systems to communicate in Ad-Hoc mode with and without WEP, 
and in hostap mode on the FreeBSD end without WEP, but I cannot seem to get the 
combo of hostap and WEP working.  Whenever I set an encryption key, the laptop 
cannot associate, but as soon as I disable WEP on both ends, the laptop finds 
an association almost immediately.  I'm using hex keys at both ends, and even 
using silly but unambiguous keys like 0x I can't get this to work 
with hostap.  I've also tried with 64 and 128 bit WEP keys.

Nor can I change wi0 from hostap to adhoc mode - ifconfig wi0 adhoc returns
ENODEV: ifconfig: SIOCSIFMEDIA: Device not configured.  Going from adhoc to
hostap mode works fine.  This may or may not be related.

Has anyone else got this working?  Is it expected to work (the man page seems
to suggest it should) or is WEP and hostap not supported?

(Yes, I know WEP is not very secure, but my main hope is to stop random people 
leeching my cable link!)

wi0: Intersil Prism2.5 mem 0xfbfe-0xfbfe0fff irq 11 at device 12.0 on pci0
wi0: 802.11 address: 00:05:5d:5b:c4:c8
wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI)
wi0: Intersil Firmware: Primary 1.00.05, Station 1.03.04




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



Re: SMP Problems

2002-08-18 Thread Greg 'groggy' Lehey

On Sunday, 18 August 2002 at 13:51:54 -0700, Chern Lee wrote:
 I'm not sure where along the line I lost my second CPU, but I'm sure I had
 it 4.5.  Now, the second CPU is never detected.

 Dual Pentium III 600
 Intel L440GX motherboard w/ 440GX+ chipset

 This is a VA Linux machine.  Any ideas why I may have 'lost' my second
 CPU?

Did you build a kernel with SMP support?

Greg
--
See complete headers for address and phone numbers

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



Re: Booting on a removable disk ?

2002-08-18 Thread Daniel O'Connor

On Sat, 2002-08-17 at 21:01, Aurélien Nephtali wrote:
 I'm planning to buy a USB to IDE Adapter (BTW if someone has a list
 of those supprted by FreeBSD, mail me :p) to put a -CURRENT on it.
 
 I would like to know if this is possible to boot from the USB disk ?

I doubt your BIOS would support such a thing..

FreeBSD _should_ work if the BIOS boots off it but it's a bit hard to
test :)

-- 
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


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



Re: Internal modem/SCSI controller conflict

2002-08-18 Thread Kent Hauser



Thanks,

You were right -- the current problem with 'tip' is separate  different
from the 
internal modem/SCSI conflict. Let me describe *that* problem: when booting
from CD
(or running sysinstall from shell), sysinstall locks the machine with the
open for the internal sio.
I know this from running sysinstall under gdb and finding the system call
which locks the machine
(an open). 

So I took your advise, removed the SCSI controller, disabled the printer
 ttyb (?). Still locks 
when I access the internal modem via tip. I have attached the new dmesg.log.
(And I would be
interested in knowing how one controls interrupts, etc, assigned to these
"PnP" cards)

Sorry I seem so clueless on interrupts/memory/etc. I come from 15 years of
Sun admin 
might have to run down panics, but never "lockups". Panics are so much easier
as the disks get
synched which means that any kernal traces you had running are written out
so finding out what
syscall caused the panic (or even breaking into kdb) is a snap.

Thanks for the help.

Kent


ian j hart wrote:
[EMAIL PROTECTED]">
  "Justin T. Gibbs" wrote:
  

  Hi,My machine locks up tight whenever I access my internal modem. The modemis a standard modem (which works when the scsi controller is removed) andthe scsi controller is an Adaptec 29160 with a DAT drive attached.Whenever I type "tip dial" (from /etc/remote:dial:dv=/dev/cuaa4:br#38400:pa=none:) the box immed locks. Mouse doesn'twork. Alt-ctrl-del doesn't work.However, tape drive works fine.Any thoughts? dmesg attached.
  
  How is this related to your SCSI controller?  It is not sharing aninterrupt or any other resources with your internal modem.
  
  No, but the modem is sharing an irq with atapci1, whichhas the boot drive hanging off it.Questions.What does the dmesg look like without the SCSI card?How is it different?You appear to have a PS/2 mouse.Why are both COM ports enabled?If you don't have a printer, turn that port off too.You have way too much stuff in this box bg
  
  
  
  

Copyright (c) 1992-2002 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.6-STABLE #0: Fri Aug 16 03:47:35 EDT 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/CH
Timecounter i8254  frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (696.41-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x681  Stepping = 1
  
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real memory  = 134217728 (131072K bytes)
avail memory = 125464576 (122524K bytes)
Preloaded elf kernel kernel at 0xc0504000.
Preloaded elf module snd_emu10k1.ko at 0xc050409c.
Preloaded elf module snd_pcm.ko at 0xc0504140.
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 11 entries at 0xc00fdf10
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard
pci0: PCI bus on pcib0
pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: NVidia Riva TNT2 graphics accelerator at 0.0 irq 11
isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel PIIX4 ATA33 controller port 0x1400-0x140f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x10c0-0x10df irq 9 at device 
7.2 on pci0
usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
chip1: Intel 82371AB Power management controller port 0x7000-0x700f at device 7.3 on 
pci0
atapci1: Promise ATA66 controller port 
0x1080-0x10bf,0x1410-0x1413,0x1418-0x141f,0x1414-0x1417,0x1420-0x1427 mem 
0xf400-0xf401 irq 5 at device 13.0 on pci0
ata2: at 0x1420 on atapci1
ata3: at 0x1418 on atapci1
pcm0: Creative EMU10K1 port 0x10e0-0x10ff irq 10 at device 15.0 on pci0
xl0: 3Com 3c900B-TPC Etherlink XL port 0x1000-0x107f mem 0xf402-0xf402007f irq 9 
at device 16.0 on pci0
xl0: Ethernet address: 00:50:da:17:a0:3a
xl0: selecting 10baseT transceiver, half duplex
sio0: 3COM PCI FaxModem port 0x1430-0x1437 irq 5 at device 17.0 on pci0
sio0: moving to sio4
sio4: type 16550A
orm0: Option ROMs at iomem 0xc-0xc97ff,0xc9800-0xcafff,0xe4000-0xe 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: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, 

Re: vi in 8 bit mode

2002-08-18 Thread Bjoern Fischer

Hello Stoian,

 How can switch vi in 8 bit mode to be possible to edit files containig 
 cyrillic text. When trying to use vi with cyr text i see this
 
 oCMenu.makeMenu('sub32','top3','\xcf\xe0\xf0\xf2\xed\xfc\xee\xf0 
 2','part2.html')^M

What about setting the environment variable 'LC_CTYPE' to
'ru_RU.ISO8859-5' or 'ru_RU.KOI8-R'?

Make also sure that the terminal operates with 8 bit, see
stty(1) xterm(1).

Björn


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



Re: RELENG_4

2002-08-18 Thread Bruce A. Mah

If memory serves me right, Chris Johnson wrote:
 On Sun, Aug 18, 2002 at 04:50:28PM -0300, Vitor de Matos Carvalho wrote:
  Because when it left the 4.1.1-release version turned STABLE?
 
 I may be wrong, but I believe that was before the invention of the security
 branches. 4.1.1-RELEASE was a snapshot of RELENG_4--I don't think there was a
 RELENG_4_1--but 4.6.2-RELEASE isn't. 4.6.2-RELEASE is a snapshot of the
 security branch, RELENG_4_6.

This is correct.

4.1.1-RELEASE was a look, ma, we can get rid of RSAREF snapshot of
RELENG_4.  There wasn't much QA done on that release, that's why we
erred on the side of caution in trying to put out 4.6.2-RELEASE.

Bruce.





msg48838/pgp0.pgp
Description: PGP signature


CDROM/CDRW devices not working.

2002-08-18 Thread manny rosa

When ever I try to burn cds, I get the following...

burncd: open(/dev/acd1c): Device not configured

When I try to mount cds I get a similar errorcd

9660: /dev/acd0c: Device not configured

The devices are detected by the kernel, but they won't
work. dmesg says...

acd0: CDROM ASUS CD-S340 at ata0-slave UDMA33
acd1: CD-RW PCRW804 at ata1-master WDMA2

I used to work with 4.5-Release so the drivers should
work Any ideas?

FreeBSD 4.6-STABLE i386 i386


__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com

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



Re: CDROM/CDRW devices not working.

2002-08-18 Thread Gregory Bond

9660: /dev/acd0c: Device not configured

Did you remake the devices?  (cd /dev  sh MAKEDEV acd0)



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