Re: disklabel partition auto allocation problem

2021-06-09 Thread electronmuontau neutrino
I forgot to include my physical memory size:
# sysctl hw.physmem
hw.physmem=16897085440

On Wed, Jun 9, 2021 at 12:40 PM electronmuontau neutrino <
emtneutr...@gmail.com> wrote:

> disklabel in OpenBSD 6.9 doesn't seem to be allocating partition sizes
> correctly according to the actual size of my OpenBSD partition.  I dual
> booted my ThinkPad X1 Carbon 5th gen laptop with Windows 10 and OpenBSD.  I
> allocated about half the disk space to OpenBSD.  When I installed OpenBSD,
> it allocated partitions as if my disk size was > 2.5 GB instead of >= 10 GB
> as shown in the disklabel man page.  It allocated 2GB to /, 256M to swap,
> 3G to /usr, 2G to /home and apparently did not allocate the rest of the
> free space.  I've included the output of disklabel, fdisk and dmesg below.
> I haven't tried installing OpenBSD 6.8 to see if it does the same thing.  I
> believe auto allocation worked fine in OpenBSD 6.7.  If I'm not including
> any info that might help diagnose this problem, if it really is a problem,
> please let me know.
>
> 
> # disklabel sd0
>
> # /dev/rsd0c:
> type: SCSI
> disk: SCSI disk
> label: SAMSUNG MZVLB1T0
> duid: 9a51a841a90239b3
> flags:
> bytes/sector: 512
> sectors/track: 63
> tracks/cylinder: 255
> sectors/cylinder: 16065
> cylinders: 124519
> total sectors: 2000409264
> boundstart: 1002668032
> boundend: 1998360576
> drivedata: 0
>
> 16 partitions:
> #size   offset  fstype [fsize bsize   cpg]
>   a:  4194304   1002668032  4.2BSD   2048 16384 12960 # /
>   b:   524288   1006862336swap# none
>   c:   20004092640  unused
>   d:  6291456   1007386624  4.2BSD   2048 16384 12960 # /usr
>   e:  4194304   1013678080  4.2BSD   2048 16384 12960 # /home
>   i:   532480 2048   MSDOS
>   j:32768   534528 unknown
>   k:   1002100736   567296   MSDOS
>   l:  2048000   1998360576 unknown
>
>
> 
> # fdisk sd0
>
> Disk: sd0   Usable LBA: 34 to 2000409230 [2000409264 Sectors]
>#: type [   start: size ]
> 
>0: EFI Sys  [2048:   532480 ]
>1: e3c9e316-0b5c-4db8-817d-f92df00215ae [  534528:32768 ]
>2: FAT12[  567296:   1002100736 ]
>3: OpenBSD  [  1002668032:995692544 ]
>4: Win Recovery [  1998360576:  2048000 ]
>
>
> 
> # dmesg
>
> OpenBSD 6.9 (GENERIC.MP) #3: Mon Jun  7 08:21:26 MDT 2021
> r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
> GENERIC.MP
> real mem = 16897085440 (16114MB)
> avail mem = 16369602560 (15611MB)
> random: good seed from bootblocks
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x9f0e1000 (62 entries)
> bios0: vendor LENOVO version "N1MET65W (1.50 )" date 04/19/2021
> bios0: LENOVO 20HRCTO1WW
> acpi0 at bios0: ACPI 5.0
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT
> BOOT BATB SLIC SSDT SSDT SSDT WSMT SSDT SSDT DBGP DBG2 MSDM ASF! FPDT UEFI
> acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4)
> RP02(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) RP09(S4) RP10(S4)
> RP11(S4) RP12(S4) RP13(S4) [...]
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 2399 Hz
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz, 2692.98 MHz, 06-8e-09
> cpu0:
> FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
> cpu0: 256KB 64b/line 8-way L2 cache
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 24MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
> cpu1 at mainbus0: apid 2 (application processo

disklabel partition auto allocation problem

2021-06-09 Thread electronmuontau neutrino
disklabel in OpenBSD 6.9 doesn't seem to be allocating partition sizes
correctly according to the actual size of my OpenBSD partition.  I dual
booted my ThinkPad X1 Carbon 5th gen laptop with Windows 10 and OpenBSD.  I
allocated about half the disk space to OpenBSD.  When I installed OpenBSD,
it allocated partitions as if my disk size was > 2.5 GB instead of >= 10 GB
as shown in the disklabel man page.  It allocated 2GB to /, 256M to swap,
3G to /usr, 2G to /home and apparently did not allocate the rest of the
free space.  I've included the output of disklabel, fdisk and dmesg below.
I haven't tried installing OpenBSD 6.8 to see if it does the same thing.  I
believe auto allocation worked fine in OpenBSD 6.7.  If I'm not including
any info that might help diagnose this problem, if it really is a problem,
please let me know.


# disklabel sd0

# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: SAMSUNG MZVLB1T0
duid: 9a51a841a90239b3
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 124519
total sectors: 2000409264
boundstart: 1002668032
boundend: 1998360576
drivedata: 0

16 partitions:
#size   offset  fstype [fsize bsize   cpg]
  a:  4194304   1002668032  4.2BSD   2048 16384 12960 # /
  b:   524288   1006862336swap# none
  c:   20004092640  unused
  d:  6291456   1007386624  4.2BSD   2048 16384 12960 # /usr
  e:  4194304   1013678080  4.2BSD   2048 16384 12960 # /home
  i:   532480 2048   MSDOS
  j:32768   534528 unknown
  k:   1002100736   567296   MSDOS
  l:  2048000   1998360576 unknown



# fdisk sd0

Disk: sd0   Usable LBA: 34 to 2000409230 [2000409264 Sectors]
   #: type [   start: size ]

   0: EFI Sys  [2048:   532480 ]
   1: e3c9e316-0b5c-4db8-817d-f92df00215ae [  534528:32768 ]
   2: FAT12[  567296:   1002100736 ]
   3: OpenBSD  [  1002668032:995692544 ]
   4: Win Recovery [  1998360576:  2048000 ]



# dmesg

OpenBSD 6.9 (GENERIC.MP) #3: Mon Jun  7 08:21:26 MDT 2021
r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
GENERIC.MP
real mem = 16897085440 (16114MB)
avail mem = 16369602560 (15611MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x9f0e1000 (62 entries)
bios0: vendor LENOVO version "N1MET65W (1.50 )" date 04/19/2021
bios0: LENOVO 20HRCTO1WW
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT
BOOT BATB SLIC SSDT SSDT SSDT WSMT SSDT SSDT DBGP DBG2 MSDM ASF! FPDT UEFI
acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) RP02(S4)
RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) RP09(S4) RP10(S4) RP11(S4)
RP12(S4) RP13(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 2399 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz, 2692.98 MHz, 06-8e-09
cpu0:
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz, 2692.85 MHz, 06-8e-09
cpu1:
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, 

Re: Unable to associate with wifi AP until channel changed on AP

2013-12-26 Thread electronmuontau neutrino
Thanks for all the replies!

 I might be wrong, and the code might disprove me, but I don't believe
 that in hostap mode it can work without explicitly defining a channel,
 which is the issue you are having. I used to have a ralink 2500 in
 hostap mode, and it wouldn't work until I defined the channel. You
 should do a site survey and see the least busy channel in your area and
 set it on your hostname.if.

 --
 Giancarlo Razzolini
 GPG: 4096R/77B981BC

I ran another test booting with the channel set in hostname.athn0 on the
Acer Aspire One D250 and it was possible to associate with it without
having to change the channel.  On the Alix.2D13, that was not the case.  I
could see the Alix from the Mac but the connection would time out.  The
Windows machine couldn't see the nwid.  After changing the channel I was
able to associate.  In other words the same result as before.

This is what I put in hostname.athn0:
inet 192.168.2.1 255.255.255.0
nwid 1234567890 wpakey keykeykey
chan 3
mediaopt hostap
up

I also tested with chan 7 in hostname.athn0 with the same results.  So, I
had success with setting the channel in hostname.athn0 for the Acer, but no
such luck for the Alix.

$ ifconfig athn0
athn0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST
mtu
   
1500 lladdr: xx:xx:xx:xx:xx:xx
   
priority: 4
groups: wlan
media: IEEE802.11 autoselect (autoselect hostap)
status: active
   
ieee80211: nwid 1234567890 chan 3 bssi xx:xx:xx:xx:xx:x:
 It is working on channel 3 = 2422MHz
 Sorry - I overlooked this.

 Is channel 3 in the range of your client machines? Depending on the
 area it may not be. If your setup works fine with channel 7 then why
 not leaving it at that?

I did the tests with the AP's sitting beside the Mac and Windows machines.
 I also tested with the channel set to 3 and 7 in hostname.athn0 on the
Acer and Alix and still had the same results.

   WinXP machine might not work with 5GHz?
  
   Are the antennas suitable for 5GHz? What about signal strength?
   On the MAC it might be useful to install a WiFi scanner which will
   tell you all about signal strength.
   There is a free program called Wifi Scanner in the AppleStore.
   It is very useful.
 Please do install this program unless you want to go on fishing in
 the dark. It is very useful to see which channels are less crowded
 and thus being more likely to allow good reception.
 On my Android phone I installed Wifi Analyzer which is excellent to
 always being able to see what's going on in the area where you want to
 use wifi.

The Wifi Scanner appears to be non-free now.  It's price is $1.99 in the
apple store.  I haven't seen something comparable that is free.

 
  The antennas I used were from PCEngines - listed as antsma on their
  website. antsma - Antenna for 2.4 GHz band, 5 dBi nominal gain.
  Reverse SMA connector.
 
  They do have another antenna, antsmadb, that is dual band which I
  don't have. antsmadb - Antenna for 2.4 GHz and 5 GHz band, 5 dBi
  peak gain in 2.4 GHz band. Reverse SMA connector.
 This antenna is definitely needed if the 5GHz band is used.
 PCengines is fine but their shipping flunked with the antenna question
 before. They delivered the wrong antennas to me at least ...
 Field strength is -79dBm or worse right next to the transmitter using
 the wrong antenna. That is barely above the noise.
 But this is moot now.

 From their website:
 antsma = light colored coax cable inside (look near hinge),
 antsmadb = black coax cable.

 
  I don't think signal strength was an issue because I tested with
  each AP next to the Mac and Windows machines and still had the same
  result.
 A 2.4GHz antenna used on the 5GHz band is nothing but an energy sink
 also called a dummy load. Also the transmitter will reduce its output
 power greatly because the reflected wave might damage its final stage.

 I don't think that this problem is anything special to do with OpenBSD
 but I may be wrong.

 For the time being I'd just make the channel 7 permanent in
 /etc/rc.local and live with it, unless the 2.4GHz band is really
 crowded at your site.
 5GHz is from channel 36 up.

Apparently the Acer is only capable of 2.4GHz.  The channels listed by
ifconfig athn0 chan are 1 - 14.  The Alix, though, is capable of 2.4 and 5.
 I've run my previous tests on the Alix setting its channel to 36 and above
and connection to it works only after changing the channel.


 I wish you success
 Eike

Just a wild guess, but if athn_switch_chan is called from
/src/sys/dev/ic/athn.c
by ifconfig, could disabling and re-enabling interrupts have some good
effects on attemps to connect?



Re: Unable to associate with wifi AP until channel changed on AP

2013-12-25 Thread electronmuontau neutrino
 Sorry for late answer - had some problems with my ISP.

 On Sunday 22 December 2013 01:42:09 electronmuontau neutrino wrote:
  I have two machines configured as wifi access points that use the
  athn(4) driver.  One is an Acer Aspire One D250 and the other is an
  ALIX.2D13 with a Compex WLM200NX Atheros 802.11 a/b/g/n miniPCI
  card.  Both have OpenBSD 5.4 release installed.  I've been able to
  reproduce the problem reliably on both.  The following is one
  procedure I used to test the problem:
 
  -boot machine with athn down
 
  $ ifconfig athn0
  athn0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500
  lladdr: xx:xx:xx:xx:xx:xx
  priority: 4
  groups: wlan
  media: IEEE802.11 autoselect
  status: no network
  ieee80211: nwid 
  $ sudo ifconfig athn0 inet 192.168.2.1 255.255.255.0 nwid
  1234567890 wpakey keykeykey mediaopt hostap
  $ ifconfig athn0
  athn0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu
  1500 lladdr: xx:xx:xx:xx:xx:xx
  priority: 4
  groups: wlan
  media: IEEE802.11 autoselect (autoselect hostap)
  status: active
  ieee80211: nwid 1234567890 chan 3 bssid xx:xx:xx:xx:xx:x:
  wpakey not displayed wpaprotos wpa1, wpa2 wpaakms psk wpaciphers
  tkip, ccmp wpagroupcipher tkip
  inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255
  inet6 ::xxx:::%athn0 pfrefixlen 64 scopeid
  0x1
 
  -edit dhcpd.conf and run dhcpd daemon
  $ sudo /usr/sbin/dhcpd athn0
 
  -attempt to associate from MacOSX and WinXP machines
  -not able to see nwid on WinXP after refreshing list multiple
  times -can see nwid on MacOSX, but connection times out when trying
  to associate
 
 Down to here you are sending on 5120MHz, right?

I don't know.  How would you determine that?


  -change channel on access point
  $ sudo ifconfig athn0 chan 7
 Now you switch to 2.4GHz - right?

 
  -association with AP is successful from MacOSX and WinXP machines
  now and IP addresses are assigned
 WinXP machine might not work with 5GHz?

 Are the antennas suitable for 5GHz? What about signal strength?
 On the MAC it might be useful to install a WiFi scanner which will
 tell you all about signal strength.
 There is a free program called Wifi Scanner in the AppleStore. It is
 very useful.

The antennas I used were from PCEngines - listed as antsma on their website.
antsma - Antenna for 2.4 GHz band, 5 dBi nominal gain. Reverse SMA connector.

They do have another antenna, antsmadb, that is dual band which I don't have.
antsmadb - Antenna for 2.4 GHz and 5 GHz band, 5 dBi peak gain in 2.4
GHz band. Reverse SMA connector.

I don't think signal strength was an issue because I tested with each
AP next to the Mac and Windows machines and still had the same result.


 I can't help with the COMPEX miniPCI 'cause I got another brand on my
 Alix 2D13. But I realized that signal strength with 5GHz can be
 significantly lower than with 2.4GHz using antennas which are meant to
 work on both bands.

 Just my 2 c
 
  Acer Aspire One D250
  athn0 at pci1 dev 0 function 0 Atheros AR9281 rev 0x01: apic 4 int
  16 athn0: AR9280 rev 2 (2T2R), ROM rev 22, address
  xx:xx:xx:xx:xx:xx
 
  Alix 2D13
  athn0 at pci0 dev 12 function 0 Atheros AR9280 rev 0x01: irq 9
  athn0: AR9280 rev 2 (2T2R), ROM rev 22, address xx:xx:xx:xx:xx:xx
 Some might like to see a complete dmesg of this setup [hint-hint]
 
  Has anyone else encountered this?  Please let me know if more info
  is needed.

 Cheers
 Eike



Unable to associate with wifi AP until channel changed on AP

2013-12-21 Thread electronmuontau neutrino
I have two machines configured as wifi access points that use the athn(4)
driver.  One is an Acer Aspire One D250 and the other is an ALIX.2D13 with
a Compex WLM200NX Atheros 802.11 a/b/g/n miniPCI card.  Both have OpenBSD
5.4 release installed.  I've been able to reproduce the problem reliably on
both.  The following is one procedure I used to test the problem:

-boot machine with athn down

$ ifconfig athn0
athn0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500
lladdr: xx:xx:xx:xx:xx:xx
priority: 4
groups: wlan
media: IEEE802.11 autoselect
status: no network
ieee80211: nwid 
$ sudo ifconfig athn0 inet 192.168.2.1 255.255.255.0 nwid 1234567890
wpakey keykeykey mediaopt hostap
$ ifconfig athn0
athn0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
lladdr: xx:xx:xx:xx:xx:xx
priority: 4
groups: wlan
media: IEEE802.11 autoselect (autoselect hostap)
status: active
ieee80211: nwid 1234567890 chan 3 bssid xx:xx:xx:xx:xx:x: wpakey
not displayed wpaprotos wpa1, wpa2 wpaakms psk wpaciphers tkip, ccmp
wpagroupcipher tkip
inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255
inet6 ::xxx:::%athn0 pfrefixlen 64 scopeid 0x1

-edit dhcpd.conf and run dhcpd daemon
$ sudo /usr/sbin/dhcpd athn0

-attempt to associate from MacOSX and WinXP machines
-not able to see nwid on WinXP after refreshing list multiple times
-can see nwid on MacOSX, but connection times out when trying to
associate

-change channel on access point
$ sudo ifconfig athn0 chan 7

-association with AP is successful from MacOSX and WinXP machines now and
IP addresses are assigned

Acer Aspire One D250
athn0 at pci1 dev 0 function 0 Atheros AR9281 rev 0x01: apic 4 int 16
athn0: AR9280 rev 2 (2T2R), ROM rev 22, address xx:xx:xx:xx:xx:xx

Alix 2D13
athn0 at pci0 dev 12 function 0 Atheros AR9280 rev 0x01: irq 9
athn0: AR9280 rev 2 (2T2R), ROM rev 22, address xx:xx:xx:xx:xx:xx

Has anyone else encountered this?  Please let me know if more info is
needed.



Re: Acer Aspire One D250-1838 mouse problem

2010-02-27 Thread electronmuontau neutrino
On Sat, Feb 27, 2010 at 3:21 AM, J.C. Roberts list-...@designtools.org wrote:
 On Fri, 26 Feb 2010 22:17:01 -0500 electronmuontau neutrino
 emtneutr...@gmail.com wrote:

 Short Story:
 I have an Acer Aspire One D250-1838 whose trackpad mouse stops working

 You should search the bugs@ and misc@ lists. I recall seeing mouse
 issues with Acer Aspire One issues reported last month on both lists.


Thanks, I found some bugs involving acpi and Acer Aspire notebooks.
Disabling acpi fixes the issue.  Disabling apm was not required
though.



Acer Aspire One D250-1838 mouse problem

2010-02-26 Thread electronmuontau neutrino
Short Story:
I have an Acer Aspire One D250-1838 whose trackpad mouse stops working
after a couple of seconds on OpenBSD 4.3 and later, including all
current snapshots.  The mouse works fine on OpenBSD 4.0 to 4.2.  The
mouse behaves correctly when running 'od /dev/wsmouse' for a couple of
seconds of use, and then it stops responding.  It also doesn't respond
if I leave the mouse alone for the couple of seconds and then try to
use it.   Running 'wsmoused -f' also shows the same behavior.

Long Story:
I've been trying to find the differences in code between OpenBSD 4.2
and 4.3 regarding the mouse device.  I've been using the CVS web
interface to find the differences in those files.  I haven't seen
anything that seems relevant.  I inserted several printf's into the
kernel source using cscope to try and trace the flow of data from the
device to kernel to user.  So far, I haven't been able to really
figure out the path.  I'm guessing the flow somewhat follows
bus_space_read_1 - pckbcintr_internal - pmsinput - wsmouse_input.
I've briefly scanned
http://www.openbsd.org/papers/opencon06-drivers/index.html.  I'd
appreciate if someone could give me some pointers to try to solve the
problem.  Thanks.

The files I've looked at are the following:
/usr/src/sys/dev/wscons
wsconsio.h
wsevent.c
wseventvar.h
wsmouse.c
wsmoused.h
wsmousevar.h
wsmux.c
wsmuxvar.h
/usr/src/sys/dev/pckbc
pms.c
pms_intelli.c
pmsreg.h
/usr/src/sys/dev/ic
io8042reg.h
pckbc.c
pckbcvar.h
/usr/src/sys/dev/isa
pckbc_isa.c
/usr/src/usr.sbin/wsmoused/
mouse_protocols.c
mouse_protocols.h
wsmoused.c
wsmoused.h

Here is my dmesg using snapshot 2/25/2010:

OpenBSD 4.7-beta (GENERIC.MP) #424: Thu Feb 25 16:12:49 MST 2010
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
RTC BIOS diagnostic error 80clock_battery
cpu0: Intel(R) Atom(TM) CPU N280 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR
real mem  = 1062260736 (1013MB)
avail mem = 1020530688 (973MB)
RTC BIOS diagnostic error 80clock_battery
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 09/28/09, SMBIOS rev. 2.4 @
0xe8240 (31 entries)
bios0: vendor Acer version V1.21 date 09/28/2009
bios0: Acer Aspire one
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP SSDT HPET APIC MCFG ASF! SLIC BOOT
acpi0: wakeup devices UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) ECHI(S3)
ECH2(S3) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) AZAL(S0) MODM(S0)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 166MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Atom(TM) CPU N280 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 4
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (EXP1)
acpiprt2 at acpi0: bus 2 (EXP2)
acpiprt3 at acpi0: bus 3 (EXP3)
acpiprt4 at acpi0: bus 4 (EXP4)
acpiec0 at acpi0
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: FN00
acpitz0 at acpi0: critical temperature 100 degC
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: LID0
acpibtn2 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model 14132307362336085 type Lion oem PANASONIC 
acpiac0 at acpi0: AC unit offline
acpivideo0 at acpi0: OVGA
acpivout0 at acpivideo0: CRT1
acpivout1 at acpivideo0: DTV1
acpivout2 at acpivideo0: DFP1
acpivout3 at acpivideo0: LCD_
acpivout4 at acpivideo0: DTV2
acpivout5 at acpivideo0: DFP2
bios0: ROM list: 0xc/0xec00!
cpu0: Enhanced SpeedStep 1663 MHz: speeds: 1333, 1066, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 Intel 82945GME Host rev 0x03
vga1 at pci0 dev 2 function 0 Intel 82945GME Video rev 0x03
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0x4000, size 0x1000
inteldrm0 at vga1: apic 4 int 16 (irq 11)
drm0 at inteldrm0
Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02:
apic 4 int 16 (irq 11)
azalia0: codecs: Realtek ALC272
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 4
int 16 (irq 255)
pci1 at ppb0 bus 1
athn0 at pci1 dev 0 function 0 Atheros AR9281 rev 0x01: apic 4 int
16 (irq 11), address 0c:ee:e6:99:57:b5
athn0: AR9280 rev 2 (2T2R), ROM rev 22
ppb1 at pci0 dev 28 function 1 Intel 82801GB 

Re: Acer Aspire One D250 mouse problem

2010-01-23 Thread electronmuontau neutrino
On Fri, Jan 22, 2010 at 2:57 AM, J.C. Roberts list-...@designtools.org
wrote:
 On Thu, 21 Jan 2010 00:42:26 -0500 electronmuontau neutrino
 emtneutr...@gmail.com wrote:

 I have an Acer Aspire One D250 running snapshot (2010-01-20). The
 mouse will work for a couple of seconds and then freeze. This has
 occured when running wsmoused in a console(not in X), inside of X, and
 when I run od /dev/wsmouse.  If I kill wsmoused and start it again,
 the mouse works and then freezes.  When I go to a console
 (ctrl+alt+f1) from X and go back to X, the mouse works, then freezes.
 When I run od /dev/wsmouse, I see output and then nothing after a
 couple of seconds.  I can kill od and run it again and see the output
 again for a short time.  This behavior occurs in releases 4.3, 4.4,
 4.5, 4.6, and snapshot (2010-01-20).  The mouse works fine in releases
 4.0, 4.1, and 4.2.  Something was done between 4.2 and 4.3 that causes
 this problem.  The mouse is seen as a ps2 mouse.  The easiest work
 around is to plug in a usb mouse which works in all the releases
 mentioned as well as current.  Any help is appreciated.


 There was some discussion on the Acer AspireOne mouse just a few days
 ago on the bugs@ list, although it was a slightly different model.

 http://marc.info/?t=12639198483r=1w=2

 Thanks for posting your dmesg, but I have an odd question.

 Do you ever see pmsattach: disable error in your dmesg?

 According to Stuart (sthen@), the message above is not consistent so
 you'd only see it some of the time.


 --



Re: Acer Aspire One D250 mouse problem

2010-01-23 Thread electronmuontau neutrino
On Sat, Jan 23, 2010 at 11:13 AM, electronmuontau neutrino
emtneutr...@gmail.com wrote:
 On Fri, Jan 22, 2010 at 2:57 AM, J.C. Roberts list-...@designtools.org
wrote:
 On Thu, 21 Jan 2010 00:42:26 -0500 electronmuontau neutrino
 emtneutr...@gmail.com wrote:

 I have an Acer Aspire One D250 running snapshot (2010-01-20). The
 mouse will work for a couple of seconds and then freeze. This has
 occured when running wsmoused in a console(not in X), inside of X, and
 when I run od /dev/wsmouse.  If I kill wsmoused and start it again,
 the mouse works and then freezes.  When I go to a console
 (ctrl+alt+f1) from X and go back to X, the mouse works, then freezes.
 When I run od /dev/wsmouse, I see output and then nothing after a
 couple of seconds.  I can kill od and run it again and see the output
 again for a short time.  This behavior occurs in releases 4.3, 4.4,
 4.5, 4.6, and snapshot (2010-01-20).  The mouse works fine in releases
 4.0, 4.1, and 4.2.  Something was done between 4.2 and 4.3 that causes
 this problem.  The mouse is seen as a ps2 mouse.  The easiest work
 around is to plug in a usb mouse which works in all the releases
 mentioned as well as current.  Any help is appreciated.


 There was some discussion on the Acer AspireOne mouse just a few days
 ago on the bugs@ list, although it was a slightly different model.

 http://marc.info/?t=12639198483r=1w=2

 Thanks for posting your dmesg, but I have an odd question.

 Do you ever see pmsattach: disable error in your dmesg?

 According to Stuart (sthen@), the message above is not consistent so
 you'd only see it some of the time.


 --
 Sorry, I have never seen that error on my Aspire One, just the odd
 mouse behavior.  Have you tried to install previous releases like I
 did?  The mouse worked fine on releases 4.0, 4.1, and 4.2, but did not
 work on 4.3, 4.4, 4.5, 4.6, and any of the snapshots.



Acer Aspire One D250 mouse problem

2010-01-20 Thread electronmuontau neutrino
I have an Acer Aspire One D250 running snapshot (2010-01-20). The
mouse will work for a couple of seconds and then freeze. This has
occured when running wsmoused in a console(not in X), inside of X, and
when I run od /dev/wsmouse.  If I kill wsmoused and start it again,
the mouse works and then freezes.  When I go to a console
(ctrl+alt+f1) from X and go back to X, the mouse works, then freezes.
When I run od /dev/wsmouse, I see output and then nothing after a
couple of seconds.  I can kill od and run it again and see the output
again for a short time.  This behavior occurs in releases 4.3, 4.4,
4.5, 4.6, and snapshot (2010-01-20).  The mouse works fine in releases
4.0, 4.1, and 4.2.  Something was done between 4.2 and 4.3 that causes
this problem.  The mouse is seen as a ps2 mouse.  The easiest work
around is to plug in a usb mouse which works in all the releases
mentioned as well as current.  Any help is appreciated.

OpenBSD 4.6-current (GENERIC.MP) #392: Tue Jan 19 16:05:38 MST 2010
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
RTC BIOS diagnostic error 80clock_battery
cpu0: Intel(R) Atom(TM) CPU N280 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR
real mem  = 1062260736 (1013MB)
avail mem = 1020571648 (973MB)
RTC BIOS diagnostic error 80clock_battery
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 09/28/09, SMBIOS rev. 2.4 @
0xe7f30 (31 entries)
bios0: vendor Acer version V1.21 date 09/28/2009
bios0: Acer Aspire one
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP SSDT HPET APIC MCFG ASF! SLIC BOOT
acpi0: wakeup devices UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) ECHI(S3)
ECH2(S3) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) AZAL(S0) MODM(S0)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 166MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Atom(TM) CPU N280 @ 1.66GHz (GenuineIntel 686-class) 1.67 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 4
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (EXP1)
acpiprt2 at acpi0: bus 2 (EXP2)
acpiprt3 at acpi0: bus 3 (EXP3)
acpiprt4 at acpi0: bus 4 (EXP4)
acpiec0 at acpi0
acpicpu0 at acpi0: C3, C2, C1, PSS
acpicpu1 at acpi0: C3, C2, C1, PSS
acpipwrres0 at acpi0: FN00
acpitz0 at acpi0: critical temperature 100 degC
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: LID0
acpibtn2 at acpi0: SLPB
acpibat0 at acpi0: BAT0 model 14132307362336085 type Lion oem PANASONIC 
acpiac0 at acpi0: AC unit online
acpivideo0 at acpi0: OVGA
acpivout0 at acpivideo0: CRT1
acpivout1 at acpivideo0: DTV1
acpivout2 at acpivideo0: DFP1
acpivout3 at acpivideo0: LCD_
acpivout4 at acpivideo0: DTV2
acpivout5 at acpivideo0: DFP2
bios0: ROM list: 0xc/0xec00! 0xcf000/0x1000
cpu0: Enhanced SpeedStep 1663 MHz: speeds: 1333, 1066, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 Intel 82945GME Host rev 0x03
vga1 at pci0 dev 2 function 0 Intel 82945GME Video rev 0x03
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0x4000, size 0x1000
inteldrm0 at vga1: apic 4 int 16 (irq 11)
drm0 at inteldrm0
Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02:
apic 4 int 16 (irq 11)
azalia0: codecs: Realtek ALC272
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 4
int 16 (irq 255)
pci1 at ppb0 bus 1
athn0 at pci1 dev 0 function 0 Atheros AR9281 rev 0x01: apic 4 int
16 (irq 11), address 0c:ee:e6:99:57:b5
athn0: AR9280 rev 2 (2T2R), ROM rev 22
ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 4
int 17 (irq 255)
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02: apic 4
int 18 (irq 255)
pci3 at ppb2 bus 3
alc0 at pci3 dev 0 function 0 Attansic Technology L2C rev 0xc0: apic
4 int 18 (irq 11), address 00:26:22:67:57:d0
atphy0 at alc0 phy 0: F1 10/100/1000 PHY, rev. 11
ppb3 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x02: apic 4
int 19 (irq 255)
pci4 at ppb3 bus 4
uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 4
int 16 (irq 11)
uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 4
int 17 (irq 11)
uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: apic 4
int 18 (irq 11)
uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 4
int 19 (irq 11)
ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: apic 4
int 16