Re: Ralink pci on spark64?
It would help to see the dmesg(8) output of the card on a supported platform. Do you mean ral(4)? Many PCI drivers will just-work. ~BAS On Sat, 2007-03-31 at 16:12 +0200, Maxim Belooussov wrote: > Hi, > > I plan to turn my Sun Ultra 10 into a firewall/access point using a > supported Ralink PCI card. But I see on this page > http://www.openbsd.org/sparc64.html#hardware that Ralink PCI is not > supported by the port. > > ral man page says that some cards are fuzzy about PCI 2.2, and my Sun > Ultra with psycho bus probably doesn't have PCI 2.2. Is this the > reason? > > Maxim
Re: Ralink pci on spark64?
On Sat, Mar 31, 2007 at 04:12:20PM +0200, Maxim Belooussov wrote: > Hi, > > I plan to turn my Sun Ultra 10 into a firewall/access point using a > supported Ralink PCI card. But I see on this page > http://www.openbsd.org/sparc64.html#hardware that Ralink PCI is not > supported by the port. > > ral man page says that some cards are fuzzy about PCI 2.2, and my Sun > Ultra with psycho bus probably doesn't have PCI 2.2. Is this the > reason? > > Maxim Most Ralink cards are 3.3v only, which means your Ultra 10 probably isn't going to work, this is what the note is about. No one with the relevant Ralink hardware has a new enough sparc64 to play with to see if it works, so it is not enabled in the default sparc64 GENERIC kernel.
Re: Ralink pci on spark64?
On Sun, Apr 01, 2007 at 08:47:13AM +1000, Jonathan Gray wrote: > On Sat, Mar 31, 2007 at 04:12:20PM +0200, Maxim Belooussov wrote: > > Hi, > > > > I plan to turn my Sun Ultra 10 into a firewall/access point using a > > supported Ralink PCI card. But I see on this page > > http://www.openbsd.org/sparc64.html#hardware that Ralink PCI is not > > supported by the port. > > > > ral man page says that some cards are fuzzy about PCI 2.2, and my Sun > > Ultra with psycho bus probably doesn't have PCI 2.2. Is this the > > reason? > > > > Maxim > > Most Ralink cards are 3.3v only, which means your Ultra 10 > probably isn't going to work, this is what the note is about. > > No one with the relevant Ralink hardware has a new enough > sparc64 to play with to see if it works, so it is not > enabled in the default sparc64 GENERIC kernel. > Btw. last time I tested my ral(4) card in an Ultra 10 it did not work. That was about a year ago. I will retry it next week and probably I can find the issues. -- :wq Claudio
Re: Ralink pci on spark64?
Hi all, Thank you for your answers. My Ralink is Edimax EW-7128g model, ral(4). I've upgraded the Ultra to latest snapshot, and will try to compile a new kernel with ralink drivers this week (and will post both dmesg from GENERIC and the new kernel). Maxim On 4/1/07, Claudio Jeker <[EMAIL PROTECTED]> wrote: On Sun, Apr 01, 2007 at 08:47:13AM +1000, Jonathan Gray wrote: > On Sat, Mar 31, 2007 at 04:12:20PM +0200, Maxim Belooussov wrote: > > Hi, > > > > I plan to turn my Sun Ultra 10 into a firewall/access point using a > > supported Ralink PCI card. But I see on this page > > http://www.openbsd.org/sparc64.html#hardware that Ralink PCI is not > > supported by the port. > > > > ral man page says that some cards are fuzzy about PCI 2.2, and my Sun > > Ultra with psycho bus probably doesn't have PCI 2.2. Is this the > > reason? > > > > Maxim > > Most Ralink cards are 3.3v only, which means your Ultra 10 > probably isn't going to work, this is what the note is about. > > No one with the relevant Ralink hardware has a new enough > sparc64 to play with to see if it works, so it is not > enabled in the default sparc64 GENERIC kernel. > Btw. last time I tested my ral(4) card in an Ultra 10 it did not work. That was about a year ago. I will retry it next week and probably I can find the issues. -- :wq Claudio
Re: Ralink pci on spark64?
On 4/3/07, Maxim Belooussov <[EMAIL PROTECTED]> wrote: Hi all, Thank you for your answers. My Ralink is Edimax EW-7128g model, ral(4). I've upgraded the Ultra to latest snapshot, and will try to compile a new kernel with ralink drivers this week (and will post both dmesg from GENERIC and the new kernel). Maxim On 4/1/07, Claudio Jeker <[EMAIL PROTECTED]> wrote: > On Sun, Apr 01, 2007 at 08:47:13AM +1000, Jonathan Gray wrote: > > On Sat, Mar 31, 2007 at 04:12:20PM +0200, Maxim Belooussov wrote: > > > Hi, > > > > > > I plan to turn my Sun Ultra 10 into a firewall/access point using a > > > supported Ralink PCI card. But I see on this page > > > http://www.openbsd.org/sparc64.html#hardware that Ralink PCI is not > > > supported by the port. > > > > > > ral man page says that some cards are fuzzy about PCI 2.2, and my Sun > > > Ultra with psycho bus probably doesn't have PCI 2.2. Is this the > > > reason? > > > > > > Maxim > > > > Most Ralink cards are 3.3v only, which means your Ultra 10 > > probably isn't going to work, this is what the note is about. > > > > No one with the relevant Ralink hardware has a new enough > > sparc64 to play with to see if it works, so it is not > > enabled in the default sparc64 GENERIC kernel. > > > > Btw. last time I tested my ral(4) card in an Ultra 10 it did not work. > That was about a year ago. I will retry it next week and probably I can > find the issues. > > -- > :wq Claudio > > Success! All Sun Ultra 10 owners, rejoice! :) Thank you all who responsed for helpful tips. Documentation on http://developers.sun.com/solaris/developer/support/driver/IO_kit/docs/pci-bus-sun-ultra.pdf told me that Sun Ultra 10 had correct 3.3/5v pci-bus support, so the card would work if configured. I have compiled a custom kernel based on GENERIC, enabled one line: ral* on pci?, and the card is recognized and seems to see other networks as well (ifconfig -M ral0). I'll start measuring transfer rates soon. Dmesg follow - first one is for 'GENERIC' kernel, the other is for my custom kernel with ral(4) enabled: $ cat dmesg dmesg.with.ralink.generic dmesg2 at dmesg.with.ralink.generic new.dmesg< console is keyboard/display Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2007 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.1-current (GENERIC) #1113: Tue Mar 27 15:38:22 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC total memory = 536870912 avail memory = 479576064 using 3276 buffers containing 26836992 bytes of memory bootpath: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 mainbus0 (root): Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz) cpu0 at mainbus0: SUNW,UltraSPARC-IIi (rev 9.1) @ 440 MHz, version 0 FPU cpu0: physical 16K instruction (32 b/l), 16K data (32 b/l), 2048K external (64 b/l) psycho0 at mainbus0 addr 0xfffc4000: SUNW,sabre, impl 0, version 0, ign 7c0 psycho0: bus range 0-2, PCI bus 0 psycho0: dvma map c000-dfff, iotdb 126a2000-12722000 pci0 at psycho0 ppb0 at pci0 dev 1 function 1 "Sun Simba PCI-PCI" rev 0x13 pci1 at ppb0 bus 1 ebus0 at pci1 dev 1 function 0 "Sun PCIO EBus2" rev 0x01 auxio0 at ebus0 addr 726000-726003, 728000-728003, 72a000-72a003, 72c000-72c003, 72f000-72f003 power0 at ebus0 addr 724000-724003 ipl 37 "SUNW,pll" at ebus0 addr 504000-504002 not configured sab0 at ebus0 addr 40-40007f ipl 43: rev 3.2 sabtty0 at sab0 port 0 sabtty1 at sab0 port 1 comkbd0 at ebus0 addr 3083f8-3083ff ipl 41: layout 34 wskbd0 at comkbd0: console keyboard com0 at ebus0 addr 3062f8-3062ff ipl 42: mouse: ns16550a, 16 byte fifo lpt0 at ebus0 addr 3043bc-3043cb, 30015c-30015d, 70-7f ipl 34: polled "fdthree" at ebus0 addr 3023f0-3023f7, 706000-70600f, 72-720003 ipl 39 not configured clock1 at ebus0 addr 0-1fff: mk48t59 "flashprom" at ebus0 addr 0-f not configured audioce0 at ebus0 addr 20-2000ff, 702000-70200f, 704000-70400f, 722000-722003 ipl 35 ipl 36: nvaddrs 0 audio0 at audioce0 hme0 at pci1 dev 1 function 1 "Sun HME" rev 0x01: ivec 0x7e1, address 08:00:20:ff:cb:21 nsphy0 at hme0 phy 1: DP83840 10/100 PHY, rev. 1 vgafb0 at pci1 dev 2 function 0 "ATI Mach64 GP" rev 0x5c wsdisplay0 at vgafb0: console (std, sun emulation), using wskbd0 pciide0 at pci1 dev 3 function 0 "CMD Technology PCI0646" rev 0x03: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using ivec 0x7e0 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: wd0: 16-sector PIO, LBA, 19458MB, 39851760 sectors wd1 at pciide0 channel 0 drive 1: wd1: 16-sector PIO, LBA, 76293MB, 15625 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 wd1(pciide0:0:1): using PIO mode 4, DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom removable cd0(pciide0:1:1): u
Re: Ralink pci on spark64?
Hi, We have run Edimax WL-660R (ral0) with obsd 4.0 and signal is pretty good. The only thing that still need to figure out is an issue to gain dhcp IP out for some specific channels that I don't think it's due to interference. Otherwise it works pretty stable. Thanks, Kevin > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Maxim Belooussov > Sent: Tuesday, April 03, 2007 11:37 PM > To: misc@openbsd.org > Subject: Re: Ralink pci on spark64? > > On 4/3/07, Maxim Belooussov <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > Thank you for your answers. > > > > My Ralink is Edimax EW-7128g model, ral(4). I've upgraded > the Ultra to > > latest snapshot, and will try to compile a new kernel with ralink > > drivers this week (and will post both dmesg from GENERIC and the new > > kernel). > > > > Maxim > > > > On 4/1/07, Claudio Jeker <[EMAIL PROTECTED]> wrote: > > > On Sun, Apr 01, 2007 at 08:47:13AM +1000, Jonathan Gray wrote: > > > > On Sat, Mar 31, 2007 at 04:12:20PM +0200, Maxim > Belooussov wrote: > > > > > Hi, > > > > > > > > > > I plan to turn my Sun Ultra 10 into a firewall/access > point using a > > > > > supported Ralink PCI card. But I see on this page > > > > > http://www.openbsd.org/sparc64.html#hardware that > Ralink PCI is not > > > > > supported by the port. > > > > > > > > > > ral man page says that some cards are fuzzy about PCI > 2.2, and my Sun > > > > > Ultra with psycho bus probably doesn't have PCI 2.2. > Is this the > > > > > reason? > > > > > > > > > > Maxim > > > > > > > > Most Ralink cards are 3.3v only, which means your Ultra 10 > > > > probably isn't going to work, this is what the note is about. > > > > > > > > No one with the relevant Ralink hardware has a new enough > > > > sparc64 to play with to see if it works, so it is not > > > > enabled in the default sparc64 GENERIC kernel. > > > > > > > > > > Btw. last time I tested my ral(4) card in an Ultra 10 it > did not work. > > > That was about a year ago. I will retry it next week and > probably I can > > > find the issues. > > > > > > -- > > > :wq Claudio > > > > > > > > > > > Success! All Sun Ultra 10 owners, rejoice! :) > > Thank you all who responsed for helpful tips. > > Documentation on > http://developers.sun.com/solaris/developer/support/driver/IO_ > kit/docs/pci-bus-sun-ultra.pdf > told me that Sun Ultra 10 had correct 3.3/5v pci-bus support, so the > card would work if configured. > > I have compiled a custom kernel based on GENERIC, enabled one line: > ral* on pci?, and the card is recognized and seems to see other > networks as well (ifconfig -M ral0). I'll start measuring transfer > rates soon. > > Dmesg follow - first one is for 'GENERIC' kernel, the other is for my > custom kernel with ral(4) enabled: > > $ cat dmesg > dmesg.with.ralink.generic dmesg2 > at dmesg.with.ralink.generic new.dmesg > < > console is keyboard/display > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All > rights reserved. > Copyright (c) 1995-2007 OpenBSD. All rights reserved. > http://www.OpenBSD.org > > OpenBSD 4.1-current (GENERIC) #1113: Tue Mar 27 15:38:22 MDT 2007 > > [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC > total memory = 536870912 > avail memory = 479576064 > using 3276 buffers containing 26836992 bytes of memory > bootpath: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL > PROTECTED],0 > mainbus0 (root): Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 440MHz) > cpu0 at mainbus0: SUNW,UltraSPARC-IIi (rev 9.1) @ 440 MHz, > version 0 FPU > cpu0: physical 16K instruction (32 b/l), 16K data (32 b/l), 2048K > external (64 b/l) > psycho0 at mainbus0 addr 0xfffc4000: SUNW,sabre, impl 0, > version 0, ign 7c0 > psycho0: bus range 0-2, PCI bus 0 > psycho0: dvma map c000-dfff, iotdb 126a2000-12722000 > pci0 at psycho0 > ppb0 at pci0 dev 1 function 1 "Sun Simba PCI-PCI" rev 0x13 > pci1 at ppb0 bus 1 > ebus0 at pci1 dev 1 function 0 "Sun PCIO EBus2" rev 0x01 > auxio0 at ebus0 addr 726000-726003, 728000-728003, 72a000-72a003, > 72c000-72c003, 72f000-72f003 > power0 at ebus0 addr 724000-724003 ipl 37
Re: Ralink pci on spark64?
Hi all, I have compiled a custom kernel based on GENERIC, enabled one line: ral* on pci?, and the card is recognized and seems to see other networks as well (ifconfig -M ral0). I'll start measuring transfer rates soon. As promised, I've managed to measure the transfer rates, using my Thinkpad's ath0 card (ibm a/b/g). Ral(4) on Ultra was configured for WEP, static IP address, on a not-too-busy channel (6). To measure the rates, I have simply scp-ed a large binary file from the laptop to the machine. System under test: Sun Ultra 10, 512 MB ram, 440 MHz ultra sparc II, ral0 at pci2 dev 2 function 0 "Ralink RT2560" card, static ip, no pf, OpenBSD -current (rebuild from source a couple of days ago), custom kernel based on GENERIC with ral enabled, WEP with static keys. Laptop OS - Transfer rate OpenBSD 4.0650 KB/s Linux FC6.0 1 MB/s WindowsXP 1.4 MB/s (I've used cygwin ssh under Windows) Notes: I think almost everybody knows that OpenBSD ath doesn't work that well in 11g mode, hence the reduced (but stable) performance. Fedora Core 6.0 failed to correctly detect that it was actually connected. WindowsXP transfer rates looked solid. I've noticed high interrupt cpu usage (37%) on Sun Ultra when copying the files wirelessly from Linux/Windows. hme(4) NICs use about 10% of the cpu. I'm quite happy with the speed - more then enough to browse internet, and is anyway faster then my ADSL connection. And, proving the point, ral(4) does work beautifully on sparc64 architecture. Maxim
