On 05/05/12 10:40 AM, Weldon Goree wrote:
On Fri, 2012-05-04 at 19:26 -0400, Ted Unangst wrote:
The only google hit for "netbsd ignphy" is... your email. ???
My mistake -- I was seeing igphy(4), which is for the ethernet, not the
wireless. At any rate, the iwn(4) driver does not need Intel'
On Fri, 2012-05-04 at 19:26 -0400, Ted Unangst wrote:
> The only google hit for "netbsd ignphy" is... your email. ???
>
My mistake -- I was seeing igphy(4), which is for the ethernet, not the
wireless. At any rate, the iwn(4) driver does not need Intel's firmware,
and seems to work pretty well.
On Fri, 2012-05-04 at 19:26 -0400, Ted Unangst wrote:
> The only google hit for "netbsd ignphy" is... your email. ???
>
I may have misremembered the name of the PHY, but iwn(4) in NetBSD
6.0-BETA does produce a PHY named something and doesn't require Intel's
firmware to run. Though this may als
On Fri, May 04, 2012 at 12:33, Weldon Goree wrote:
> On Fri, 2012-05-04 at 07:37 +0100, Laurence Rochfort wrote:
>> I wouldn't recommend the iwn(4) devices. I've had a bad experience even
>> with those in the man page.
>
> YMMV; I've had good results with the 4965 AGN. Of note: NetBSD 6 (in
> beta
On 05/04/2012 05:41 AM, Stuart Henderson wrote:
On 2012-05-04, Edward M wrote:
cpu0: Intel(R) Atom(TM) CPU N2600 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,NXE,LONG,S
On Fri, 2012-05-04 at 07:37 +0100, Laurence Rochfort wrote:
> I wouldn't recommend the iwn(4) devices. I've had a bad experience even
> with those in the man page.
YMMV; I've had good results with the 4965 AGN. Of note: NetBSD 6 (in
beta) has a new largely-non-Damien driver with its own PHY (ignph
On 2012-05-04, Edward M wrote:
>> cpu0: Intel(R) Atom(TM) CPU N2600 @ 1.60GHz ("GenuineIntel" 686-class) 1.60
>> GHz
>> cpu0:
>> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xT
hmm, on Fri, May 04, 2012 at 07:37:45AM +0100, Laurence Rochfort said that
> I wouldn't recommend the iwn(4) devices. I've had a bad experience even
> with those in the man page.
>
> I recently replaced an iwn(4) with ral(4) and athn(4) as advised on misc
> and they've been excellent. No firmware
here is sysctl hw as well:
hw.machine=i386
hw.model=Intel(R) Atom(TM) CPU N2600 @ 1.60GHz ("GenuineIntel" 686-class)
hw.ncpu=4
hw.byteorder=1234
hw.pagesize=4096
hw.disknames=sd0:73fc4ae5314f89db
hw.diskcount=1
hw.sensors.acpitz0.temp0=40.00 degC (zone temperature)
hw.sensors.acpiac0.indicator0=O
I wouldn't recommend the iwn(4) devices. I've had a bad experience even
with those in the man page.
I recently replaced an iwn(4) with ral(4) and athn(4) as advised on misc
and they've been excellent. No firmware needed for those I tried either.
On May 4, 2012 12:07 AM, "frantisek holop" wrote:
On 05/03/2012 04:04 PM, frantisek holop wrote:
OpenBSD 5.1-current (GENERIC.MP) #253: Thu Apr 26 01:45:24 MDT 2012
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Atom(TM) CPU N2600 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,
On 05/03/2012 07:04 PM, frantisek holop wrote:
hi there,
here is the dmesg for a spanking new acer aspire one D270 netbook.
installation was easy and fast.
devices not supported (yet):
intel integrated video,
BCM4313 (probably gonna replace with an iwn)
there is a curious ehci0 timeout..
the
12 matches
Mail list logo
