From matthias.apitz at oclc.org Tue Apr 1 00:52:26 2008 From: matthias.apitz at oclc.org (Matthias Apitz) Date: Tue Apr 1 00:52:31 2008 Subject: 7.0-RELEASE && panic after ~4 hours In-Reply-To: <20080331130404.GB1615@rebelion.Sisis.de> References: <20080326124324.GA1756@rebelion.Sisis.de> <47EAB19E.8010804@FreeBSD.org> <20080331101250.GA3094@rebelion.Sisis.de> <47F0BF52.1010109@FreeBSD.org> <20080331130404.GB1615@rebelion.Sisis.de> Message-ID: <20080401075221.GA2138@rebelion.Sisis.de> El d?a Monday, March 31, 2008 a las 03:04:04PM +0200, Matthias Apitz escribi?: > > You should unmount (or boot to single-user mode) and run a full fsck > > (fsck -fy). > > Thanks for your hint and I've done what you have advised and I'm > connected through Wifi again now (until next panic :-)) > The fsck has indeed correct something where the block count should have > been zero but was some decimal number of 20 digits, I think (don't > remember that large number); > > I'll copy this e-mail into the TT; While the laptop worked all night at home (and only with clean shutdows since the last 'fsck -fy' yesterday afternoon), it crashed after around 20 minutes in my office this morning; the kgdb says: # kgdb /boot/kernel/kernel vmcore.3 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xffff1a18 fault code = supervisor read, page not present instruction pointer = 0x20:0xc07fa3ee stack pointer = 0x28:0xe6904aa4 frame pointer = 0x28:0xe6904ad0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1546 (gkrellm) trap number = 12 panic: page fault cpuid = 0 Uptime: 16m21s Physical memory: 1009 MB Dumping 156 MB: (CTRL-C to abort) 141 125 109 93 (CTRL-C to abort) 77 61 45 29 (CTRL-C to abort) 13 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc0754457 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc0754719 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc0a4905c in trap_fatal (frame=0xe6904a64, eva=4294908440) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc0a492e0 in trap_pfault (frame=0xe6904a64, usermode=0, eva=4294908440) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc0a49c8c in trap (frame=0xe6904a64) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0a2fc0b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc07fa3ee in rt_msg2 (type=12, rtinfo=0xe6904b04, cp=0x0, w=0xe6904b34) at /usr/src/sys/net/rtsock.c:784 #8 0xc07fb1a5 in sysctl_rtsock (oidp=0xc0b84ac0, arg1=0xe6904c1c, arg2=4, req=0xe6904ba4) at /usr/src/sys/net/rtsock.c:1153 #9 0xc075dc97 in sysctl_root (oidp=Variable "oidp" is not available. ) at /usr/src/sys/kern/kern_sysctl.c:1306 #10 0xc075dde4 in userland_sysctl (td=0xc472fc60, name=0xe6904c14, namelen=6, old=0x0, oldlenp=0xbfbfe478, inkernel=0, new=0x0, newlen=0, retval=0xe6904c10, flags=0) at /usr/src/sys/kern/kern_sysctl.c:1401 #11 0xc075eb7e in __sysctl (td=0xc472fc60, uap=0xe6904cfc) at /usr/src/sys/kern/kern_sysctl.c:1336 #12 0xc0a49635 in syscall (frame=0xe6904d38) at /usr/src/sys/i386/i386/trap.c:1035 #13 0xc0a2fc70 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:196 #14 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) any advice to track this down? thanks in advance matthias -- Matthias Apitz From kris at FreeBSD.org Tue Apr 1 02:57:41 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Tue Apr 1 02:57:43 2008 Subject: 7.0-RELEASE && panic after ~4 hours In-Reply-To: <20080401075221.GA2138@rebelion.Sisis.de> References: <20080326124324.GA1756@rebelion.Sisis.de> <47EAB19E.8010804@FreeBSD.org> <20080331101250.GA3094@rebelion.Sisis.de> <47F0BF52.1010109@FreeBSD.org> <20080331130404.GB1615@rebelion.Sisis.de> <20080401075221.GA2138@rebelion.Sisis.de> Message-ID: <47F20719.9070507@FreeBSD.org> Matthias Apitz wrote: > El d?a Monday, March 31, 2008 a las 03:04:04PM +0200, Matthias Apitz escribi?: > >>> You should unmount (or boot to single-user mode) and run a full fsck >>> (fsck -fy). >> Thanks for your hint and I've done what you have advised and I'm >> connected through Wifi again now (until next panic :-)) >> The fsck has indeed correct something where the block count should have >> been zero but was some decimal number of 20 digits, I think (don't >> remember that large number); >> >> I'll copy this e-mail into the TT; > > While the laptop worked all night at home (and only with clean shutdows > since the last 'fsck -fy' yesterday afternoon), it crashed after around > 20 minutes in my office this morning; the kgdb says: > > # kgdb /boot/kernel/kernel vmcore.3 > [GDB will not be able to debug user-mode threads: > /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-marcel-freebsd". > > Unread portion of the kernel message buffer: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xffff1a18 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc07fa3ee > stack pointer = 0x28:0xe6904aa4 > frame pointer = 0x28:0xe6904ad0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 1546 (gkrellm) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 16m21s > Physical memory: 1009 MB > Dumping 156 MB: (CTRL-C to abort) 141 125 109 93 (CTRL-C to abort) 77 > 61 45 29 (CTRL-C to abort) 13 > > #0 doadump () at pcpu.h:195 > 195 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) bt > #0 doadump () at pcpu.h:195 > #1 0xc0754457 in boot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:409 > #2 0xc0754719 in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:563 > #3 0xc0a4905c in trap_fatal (frame=0xe6904a64, eva=4294908440) at > /usr/src/sys/i386/i386/trap.c:899 > #4 0xc0a492e0 in trap_pfault (frame=0xe6904a64, usermode=0, > eva=4294908440) > at /usr/src/sys/i386/i386/trap.c:812 > #5 0xc0a49c8c in trap (frame=0xe6904a64) at > /usr/src/sys/i386/i386/trap.c:490 > #6 0xc0a2fc0b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > #7 0xc07fa3ee in rt_msg2 (type=12, rtinfo=0xe6904b04, cp=0x0, > w=0xe6904b34) > at /usr/src/sys/net/rtsock.c:784 > #8 0xc07fb1a5 in sysctl_rtsock (oidp=0xc0b84ac0, arg1=0xe6904c1c, > arg2=4, req=0xe6904ba4) > at /usr/src/sys/net/rtsock.c:1153 > #9 0xc075dc97 in sysctl_root (oidp=Variable "oidp" is not available. > ) at /usr/src/sys/kern/kern_sysctl.c:1306 > #10 0xc075dde4 in userland_sysctl (td=0xc472fc60, name=0xe6904c14, > namelen=6, old=0x0, > oldlenp=0xbfbfe478, inkernel=0, new=0x0, newlen=0, > retval=0xe6904c10, flags=0) > at /usr/src/sys/kern/kern_sysctl.c:1401 > #11 0xc075eb7e in __sysctl (td=0xc472fc60, uap=0xe6904cfc) at > /usr/src/sys/kern/kern_sysctl.c:1336 > #12 0xc0a49635 in syscall (frame=0xe6904d38) at > /usr/src/sys/i386/i386/trap.c:1035 > #13 0xc0a2fc70 in Xint0x80_syscall () at > /usr/src/sys/i386/i386/exception.s:196 > #14 0x00000033 in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) > > any advice to track this down? thanks in advance OK, now this panic looks more reasonable :) At a guess, sysctl_rtsock is not protecting against a structure changing in mid-operation (e.g. missing locking). It might be a straightforward fix for someone familiar with the code. Try raising it on net@ and filing a new PR (since it's not related to your other one). Kris From fbsd.questions at rachie.is-a-geek.net Wed Apr 2 05:00:08 2008 From: fbsd.questions at rachie.is-a-geek.net (Mel) Date: Wed Apr 2 05:00:19 2008 Subject: [Wireless] Can't connect to wlan In-Reply-To: <47E1088A.8090203@clearchain.com> References: <47C078EC.4020907@student.utwente.nl> <47E1088A.8090203@clearchain.com> Message-ID: <200804021400.04442.fbsd.questions@rachie.is-a-geek.net> On Wednesday 19 March 2008 13:35:22 Benjamin Close wrote: > Yousif Hassan wrote: > > Benjamin Close wrote: > >> Sam Leffler wrote: > >>> Yousif Hassan wrote: > >>>> On Wed, 2008-03-12 at 08:06 +1030, Benjamin Close wrote: > > > > > > > >>>> The slightly wonky: > >>>> - As reported by someone else: > >>>> wpi0: timeout resetting Tx ring 1 > >>>> wpi0: timeout resetting Tx ring 3 > >>>> wpi0: timeout resetting Tx ring 4 > >>>> appear on startup and occasionally on kldload - however they don't > >>>> appear to adversely affect too much > > > > > > > >>> wpi doesn't yet support background scan so doing an explicit scan > >>> from the command line will disconnect you from any ap you care > >>> connected to. It shouldn't be hard to add bgscan--but that's easy > >>> for me to say :) > >> > >> It's certainly on my todo list! > > > > Thanks for reminding me about the bgscan thing. I had read that > > somewhere before and completely forgotten! > > > > Ben, are the > > wpi0: timeout resetting Tx ring 1 > > wpi0: timeout resetting Tx ring 3 > > wpi0: timeout resetting Tx ring 4 > > (and other variants thereof) > > messages anything to be concerned about? It doesn't seem to affect > > stuff but it does show up on initial startup and every other scan I do. > > > > Thanks to everyone who worked on wpi for a most excellent driver. > > The timeouts are related to the firmware not being able to reset the tx > ring. Normally this isn't too bad as the first thing after resetting the > tx rings is to stop the firmware and reinit it. Whilst it won't cause a > crash, it still a bug that needs fixing. I think I finally found the issue with the connection dropping. It is related to a beacon miss and the driver not getting back to authenticated state. The /root/bin/testwpi.sh script mentioned below pings the AP 50 times sends it to syslog and does it again. Apr 1 09:20:30 laptop kernel: Beacon miss: 20 >= 7 Apr 1 09:20:30 laptop kernel: Beacon miss: 21 >= 7 Apr 1 09:20:30 laptop kernel: wpi_newstate: RUN -> ASSOC Apr 1 09:20:30 laptop kernel: wpi0: link state changed to DOWN Then this Beacon miss continues incrementing until: Apr 1 09:20:56 laptop kernel: Beacon miss: 274 >= 7 At this point the packet loss is still 100%: Apr 1 09:21:04 laptop /root/bin/testwpi.sh: 50 packets transmitted, 14 packets received, 72.0% packet loss round-trip min/avg/max/stddev = 0.513/0.599/1.046/0.131 ms Apr 1 09:22:05 laptop /root/bin/testwpi.sh: 50 packets transmitted, 0 packets received, 100.0% packet loss Apr 1 09:23:06 laptop /root/bin/testwpi.sh: 50 packets transmitted, 0 packets received, 100.0% packet loss Then for no apparent reason, it tries again: Apr 1 10:49:41 laptop kernel: Beacon miss: 20 >= 7 Apr 1 10:49:41 laptop kernel: Beacon miss: 21 >= 7 Apr 1 10:49:41 laptop kernel: Beacon miss: 22 >= 7 ... Apr 1 10:50:07 laptop kernel: Beacon miss: 273 >= 7 Apr 1 10:50:37 laptop /root/bin/testwpi.sh: 50 packets transmitted, 0 packets received, 100.0% packet loss Apr 1 10:51:38 laptop /root/bin/testwpi.sh: 50 packets transmitted, 0 packets received, 100.0% packet loss Apr 1 10:53:40 laptop last message repeated 2 times Apr 1 11:03:51 laptop last message repeated 10 times ... Then for no apparent reason (as far as I know, no one was near the machine at the time): Apr 1 16:34:00 laptop kernel: wpi_newstate: ASSOC -> AUTH Apr 1 16:34:00 laptop kernel: wpi_ops: command: 16 Apr 1 16:34:00 laptop kernel: config chan 1 flags 8035 cck f ofdm 15 Apr 1 16:34:00 laptop kernel: wpi_ops: command: 1 Apr 1 16:34:00 laptop kernel: wpi_ops: command: 8 Apr 1 16:34:00 laptop kernel: Ignoring WPI_SET_CHAN Apr 1 16:34:00 laptop kernel: wpi_ops: command: 2 Apr 1 16:34:00 laptop kernel: Scanning Essid: "MYSSID" Apr 1 16:34:00 laptop kernel: Scanning 1 Passive: 0 Apr 1 16:34:00 laptop kernel: wpi_newstate: AUTH -> AUTH Apr 1 16:34:00 laptop kernel: wpi_ops: command: 16 Apr 1 16:34:00 laptop kernel: config chan 1 flags 8035 cck f ofdm 15 Apr 1 16:34:00 laptop kernel: scanning channel 1 status 1 Apr 1 16:34:00 laptop kernel: scan finished nchan=0 status=2 chan=0 Apr 1 16:34:00 laptop kernel: wpi_ops: command: 4 Apr 1 16:34:36 laptop /root/bin/testwpi.sh: 50 packets transmitted, 0 packets received, 100.0% packet loss Apr 1 16:35:37 laptop /root/bin/testwpi.sh: 50 packets transmitted, 0 packets received, 100.0% packet loss Apr 1 16:36:38 laptop /root/bin/testwpi.sh: 50 packets transmitted, 0 packets received, 100.0% packet loss Apr 1 16:46:49 laptop last message repeated 10 times And then my girl came home from work and did the "down and list scan trick": Apr 1 17:53:06 laptop sudo: rachie : TTY=ttyp1 ; PWD=/home/rachie ; USER=root ; COMMAND=/sbi n/ifconfig wpi0 down Apr 1 17:53:06 laptop kernel: Disabling Firmware execution Apr 1 17:53:06 laptop kernel: wpi_newstate: AUTH -> INIT Apr 1 17:53:10 laptop sudo: rachie : TTY=ttyp1 ; PWD=/home/rachie ; USER=root ; COMMAND=/sbi n/ifconfig wpi0 up list scan Apr 1 17:53:11 laptop kernel: wpi0: timeout resetting Tx ring 1 Apr 1 17:53:11 laptop kernel: wpi0: timeout resetting Tx ring 3 Apr 1 17:53:11 laptop kernel: wpi0: timeout resetting Tx ring 4 Apr 1 17:53:11 laptop kernel: Disabling Firmware execution Apr 1 17:53:11 laptop kernel: wpi_newstate: INIT -> INIT Apr 1 17:53:11 laptop kernel: Resetting the card - clearing any uploaded firmware Apr 1 17:53:11 laptop kernel: Attempting Loading Firmware from wpi_fw module Apr 1 17:53:11 laptop kernel: Firmware Version: Major 2, Minor 14, Driver 4, Apr 1 17:53:11 laptop kernel: runtime (text: 80524, data: 32768) init (text: 2668, data 32768) boot (text 900) Apr 1 17:53:11 laptop kernel: rtext 0xf802020 Apr 1 17:53:11 laptop kernel: rdata 0x0 Apr 1 17:53:11 laptop kernel: itext 0xf802020 Apr 1 17:53:11 laptop kernel: idata 0x0 Apr 1 17:53:11 laptop kernel: btext 0xf802020 Apr 1 17:53:11 laptop kernel: Loading microcode size 0x384 Apr 1 17:53:11 laptop kernel: firmware status=0xffff0000, val=0x40400000, result=0x40400000 Apr 1 17:53:11 laptop kernel: Status Match! - ntries = 0 Apr 1 17:53:11 laptop kernel: microcode alive notification version 10e02 alive 1 Apr 1 17:53:11 laptop kernel: microcode alive notification version 10e02 alive 1 Apr 1 17:53:11 laptop kernel: Firmware loaded to driver successfully Apr 1 17:53:11 laptop kernel: wpi_newstate: INIT -> SCAN Apr 1 17:53:11 laptop kernel: wpi_ops: command: 1 Apr 1 17:53:11 laptop kernel: wpi_ops: command: 8 Apr 1 17:53:13 laptop kernel: scan finished nchan=1 status=1 chan=165 Apr 1 17:53:13 laptop kernel: wpi_newstate: SCAN -> AUTH Apr 1 17:53:13 laptop kernel: wpi_ops: command: 4 Apr 1 17:53:13 laptop kernel: wpi_ops: command: 8 Apr 1 17:53:13 laptop kernel: Ignoring WPI_SET_CHAN Apr 1 17:53:13 laptop kernel: wpi_ops: command: 8 Apr 1 17:53:13 laptop kernel: Ignoring WPI_SET_CHAN Apr 1 17:53:13 laptop kernel: wpi_ops: command: 16 Apr 1 17:53:13 laptop kernel: config chan 1 flags 8005 cck f ofdm 15 Apr 1 17:53:13 laptop kernel: wpi_newstate: AUTH -> ASSOC Apr 1 17:53:13 laptop kernel: wpi_newstate: ASSOC -> RUN Apr 1 17:53:13 laptop kernel: wpi_ops: command: 32 Apr 1 17:53:13 laptop kernel: config chan 1 flags 8035 Apr 1 17:53:13 laptop kernel: wpi0: link state changed to UP At this point it's working again, connection is flakey with packet loss ranging from 0 to 50% but it's working. This is wpi from 7-RELEASE with patch mentioned in this thread. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. From maksim.yevmenkin at gmail.com Wed Apr 2 10:17:27 2008 From: maksim.yevmenkin at gmail.com (Maksim Yevmenkin) Date: Wed Apr 2 10:17:30 2008 Subject: Logitech V470 Bluetooth Mouse on FreeBSD ? In-Reply-To: <1207142908.576787.1033.nullmailer@galant.ukfsn.org> References: <47ED9AC5.4050505@users.sf.net> <47EF668D.1080003@users.sf.net> <1206904241.480342.891.nullmailer@galant.ukfsn.org> <47F13BAD.9060808@users.sf.net> <1207142908.576787.1033.nullmailer@galant.ukfsn.org> Message-ID: On 4/2/08, Iain Hibbert wrote: > On Mon, 31 Mar 2008, mato wrote: > > > Well, this mouse of mine presents itself exactly as you said ... > > > > Input id=2 size=12 count=1 page=Generic_Desktop usage=X Variable Relative, > > Input id=2 size=12 count=1 page=Generic_Desktop usage=Y Variable Relative, > > wow thats a sensitive mouse, 12 bit movements! :) amazing what you can get these days, huh? :) > > Input id=2 size=8 count=1 page=Generic_Desktop usage=Wheel Variable > > Input id=2 size=8 count=1 page=Consumer usage=AC_Pan Variable Relative, > > What can be done about it ?? > > I don't know - bthidd(4) could grow the support for AC_Pan fairly easily > but I don't know how you would get that into the kernel - the mouse_info > structure has no W direction and the ioctl would need to be versioned if > the structure was extended as there was no padding.. exactly Iain. parsing hid messages in bthidd(8) and extracting all the data is trivial. the question is how to feed those data into the kernel. right now, bthidd(8) uses console ioctl to feed data into the kernel. as you pointed out, mouse_info structure (specifically mouse_data union) does not have have w direction. > btw just to make you feel better I should say that sideways scroll does > not always work in applications; eg GThumb considers the extra buttons > to be 'next' and 'prev' instead and sideways scroll just jumps to the next > picture. i have a wired usb apple mighty mouse here and horizontal scrolling does not work for me at all. quick look at ums(4) showed that it does not export w data (it tries to locate both wheel and z axis, however it does not look for ac_pan axis). so, it appears that we need to teach moused(8), sysmouse(4) and mice drivers about second wheel. it appears to be a somewhat bigger chunk of work. thanks, max > > > iain > From netwarrior863 at gmail.com Wed Apr 2 14:00:31 2008 From: netwarrior863 at gmail.com (Net Warrior) Date: Wed Apr 2 14:00:35 2008 Subject: ThinkPad T20 Sound Problem Message-ID: Hi there guys. I bought my first note book and I 'm very excited, this not the latest intel in the market, but does what I nedd. But, I'm having problems with the sound driver, I 'm geting distortions when I switch from consoles or if I do an scroll, or ls. I had this kind of problem before with some clones, but the procedure followed bebore did not work. This is my config. FreeBSD-Realm# sysctl -a |grep pcm dev.pcm.0.%desc: CS461x PCM Audio dev.pcm.0.%driver: pcm dev.pcm.0.%parent: csa0 dev.pcm.0.eapd: 1 dev.pcm.0.play.vchans: 1 dev.pcm.0.play.vchanrate: 48000 dev.pcm.0.play.vchanformat: s16le dev.pcm.0.rec.vchans: 1 dev.pcm.0.rec.vchanrate: 48000 dev.pcm.0.rec.vchanformat: s16le dev.pcm.0.buffersize: 0 FreeBSD-Realm# sysctl -a | grep snd hw.snd.latency_profile: 1 hw.snd.latency: 5 hw.snd.report_soft_formats: 1 hw.snd.compat_linux_mmap: 0 hw.snd.feeder_buffersize: 65536 hw.snd.feeder_rate_round: 25 hw.snd.feeder_rate_max: 2016000 hw.snd.feeder_rate_min: 1 hw.snd.verbose: 1 hw.snd.maxautovchans: 16 hw.snd.default_unit: 0 hw.snd.version: 2007061600/i386 hw.snd.default_auto: 0 FreeBSD-Realm# FreeBSD-Realm# vmstat -i interrupt total rate irq0: clk 4973648 958 irq1: atkbd0 3670 0 irq3: cbb0 csa0 11666 2 irq5: uhci0 1941 0 irq8: rtc 639222 123 irq9: acpi0+ 3095 0 irq10: cbb1 dc0 4 0 irq12: psm0 969 0 irq14: ata0 71376 13 irq15: ata1 363 0 FreeBSD-Realm# dmesg |grep irq vgapci0: mem 0xf0000000-0xf7ffffff irq 3 at device 0.0 on pci1 cbb0: mem 0x50000000-0x50000fff irq 3 at device 2.0 on pci0 cbb1: mem 0x50100000-0x50100fff irq 10 at device 2.1 on pci0 csa0: mem 0xe8100000-0xe8100fff,0xe8000000-0xe80fffff irq 3 at device 5.0 on pci0 uhci0: port 0x1c20-0x1c3f irq 5 at device 7.2 on pci0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio1: configured irq 3 not in bitmap of probed irqs 0 dc0: port 0x1100-0x11ff mem 0x88000000-0x880003ff irq 10 at device 0.0 on cardbus1 FreeBSD-Realm# With the clones, I alway solved the problem, as suggested in the mailing list by increasing the buffersize including it in the device.hints file, but that did not work and dev.pcm.0.buffersize never get increased, always stays in zero. Thanks in advance, and for you time. I'm using 7-0Release Stable. From sarumont at sigil.org Thu Apr 3 15:57:57 2008 From: sarumont at sigil.org (Richard Kolkovich) Date: Thu Apr 3 15:58:00 2008 Subject: Thinkpad t43p suspend/resume only once Message-ID: <20080403155752.GB84382@snobol> On my T43p, I can suspend to RAM (S3) and resume once. After this, nothing happens when I close the lid (until a reboot). I started digging into this today, and it looks like the acpi device is in a bad state after the resume. Running devd -dD from a terminal shows no output from ACPI buttons after the resume. I discovered today, however, that I can run acpiconf -s S3 to regain my ability to sleep/resume. This will suspend the machine and immediately resume it, after which devd shows output again. Has anyone ever seen anything like this, or should I redirect my queries to freebsd-acpi? TIA -- Richard Kolkovich sarumont@sigil.org From markhobden at gmail.com Thu Apr 3 17:01:01 2008 From: markhobden at gmail.com (Mark Hobden) Date: Thu Apr 3 17:01:07 2008 Subject: Logitech V470 Bluetooth Mouse on FreeBSD ? In-Reply-To: References: <47ED9AC5.4050505@users.sf.net> <47EF668D.1080003@users.sf.net> <1206904241.480342.891.nullmailer@galant.ukfsn.org> <47F13BAD.9060808@users.sf.net> <1207142908.576787.1033.nullmailer@galant.ukfsn.org> Message-ID: On 02/04/2008, Maksim Yevmenkin wrote: > > I don't know - bthidd(4) could grow the support for AC_Pan fairly easily > > but I don't know how you would get that into the kernel - the mouse_info > > structure has no W direction and the ioctl would need to be versioned if > > the structure was extended as there was no padding.. > > exactly Iain. parsing hid messages in bthidd(8) and extracting all the > data is trivial. the question is how to feed those data into the > kernel. right now, bthidd(8) uses console ioctl to feed data into the > kernel. as you pointed out, mouse_info structure (specifically > mouse_data union) does not have have w direction. > > > btw just to make you feel better I should say that sideways scroll does > > not always work in applications; eg GThumb considers the extra buttons > > to be 'next' and 'prev' instead and sideways scroll just jumps to the next > > picture. > > i have a wired usb apple mighty mouse here and horizontal scrolling > does not work for me at all. quick look at ums(4) showed that it does > not export w data (it tries to locate both wheel and z axis, however > it does not look for ac_pan axis). > > so, it appears that we need to teach moused(8), sysmouse(4) and mice > drivers about second wheel. it appears to be a somewhat bigger chunk > of work. > > thanks, > max Hi Martin, I have a patch somewhere at home that manages to do all of the above. I had planned to re-wite part of it to not require increasing the size of an xorg structure I changed - but it doesn't look like I will have time to do that for a while. At present it applies on top of the uhidev patches but it probably wouldn't be too difficult to get it to apply without them. I have been using it for a little while now and its been working fine for me. I will try and clean it up and document what needs to be re-compiled to get it working and then post it sometime in the next few days. Kind Regards, Mark Hobden. From jhb at freebsd.org Thu Apr 3 22:57:59 2008 From: jhb at freebsd.org (John Baldwin) Date: Thu Apr 3 22:58:07 2008 Subject: Thinkpad t43p suspend/resume only once In-Reply-To: <20080403155752.GB84382@snobol> References: <20080403155752.GB84382@snobol> Message-ID: <200804031818.24967.jhb@freebsd.org> On Thursday 03 April 2008 11:57:52 am Richard Kolkovich wrote: > On my T43p, I can suspend to RAM (S3) and resume once. After this, nothing > happens when I close the lid (until a reboot). I started digging into this > today, and it looks like the acpi device is in a bad state after the resume. > Running devd -dD from a terminal shows no output from ACPI buttons after the > resume. > > I discovered today, however, that I can run acpiconf -s S3 to regain my ability > to sleep/resume. This will suspend the machine and immediately resume it, after > which devd shows output again. > > Has anyone ever seen anything like this, or should I redirect my queries to > freebsd-acpi? freebsd-acpi. Perhaps the code to rearm suspend events isn't working correctly for some reason. -- John Baldwin From plunky at rya-online.net Fri Apr 4 01:08:41 2008 From: plunky at rya-online.net (Iain Hibbert) Date: Fri Apr 4 01:08:51 2008 Subject: Logitech V470 Bluetooth Mouse on FreeBSD ? In-Reply-To: <47F13BAD.9060808@users.sf.net> References: <47ED9AC5.4050505@users.sf.net> <47EF668D.1080003@users.sf.net> <1206904241.480342.891.nullmailer@galant.ukfsn.org> <47F13BAD.9060808@users.sf.net> Message-ID: <1207142908.576787.1033.nullmailer@galant.ukfsn.org> On Mon, 31 Mar 2008, mato wrote: > Well, this mouse of mine presents itself exactly as you said ... > > Input id=2 size=12 count=1 page=Generic_Desktop usage=X Variable Relative, > Input id=2 size=12 count=1 page=Generic_Desktop usage=Y Variable Relative, wow thats a sensitive mouse, 12 bit movements! :) > Input id=2 size=8 count=1 page=Generic_Desktop usage=Wheel Variable > Input id=2 size=8 count=1 page=Consumer usage=AC_Pan Variable Relative, > > What can be done about it ?? I don't know - bthidd(4) could grow the support for AC_Pan fairly easily but I don't know how you would get that into the kernel - the mouse_info structure has no W direction and the ioctl would need to be versioned if the structure was extended as there was no padding.. btw just to make you feel better I should say that sideways scroll does not always work in applications; eg GThumb considers the extra buttons to be 'next' and 'prev' instead and sideways scroll just jumps to the next picture. iain From gamato at users.sf.net Fri Apr 4 19:11:29 2008 From: gamato at users.sf.net (mato) Date: Fri Apr 4 19:11:40 2008 Subject: Logitech V470 Bluetooth Mouse on FreeBSD ? In-Reply-To: <1207142908.576787.1033.nullmailer@galant.ukfsn.org> References: <47ED9AC5.4050505@users.sf.net> <47EF668D.1080003@users.sf.net> <1206904241.480342.891.nullmailer@galant.ukfsn.org> <47F13BAD.9060808@users.sf.net> <1207142908.576787.1033.nullmailer@galant.ukfsn.org> Message-ID: <47F67D5F.7030103@users.sf.net> Iain Hibbert wrote: > On Mon, 31 Mar 2008, mato wrote: > > >> Well, this mouse of mine presents itself exactly as you said ... >> >> Input id=2 size=12 count=1 page=Generic_Desktop usage=X Variable Relative, >> Input id=2 size=12 count=1 page=Generic_Desktop usage=Y Variable Relative, >> > > wow thats a sensitive mouse, 12 bit movements! :) > > Well, I don't know how much is it -- 12 bits across what ? 1 inch ? Anyway, I must say that mouse is quite sensitive and I'd like to adjust it a bit as it's sometimes difficult to control. However, I've no idea how to achieve this. Any suggestions please ? >> Input id=2 size=8 count=1 page=Generic_Desktop usage=Wheel Variable >> Input id=2 size=8 count=1 page=Consumer usage=AC_Pan Variable Relative, >> >> What can be done about it ?? >> > > I don't know - bthidd(4) could grow the support for AC_Pan fairly easily > but I don't know how you would get that into the kernel - the mouse_info > structure has no W direction and the ioctl would need to be versioned if > the structure was extended as there was no padding.. > > btw just to make you feel better I should say that sideways scroll does > not always work in applications; eg GThumb considers the extra buttons > to be 'next' and 'prev' instead and sideways scroll just jumps to the next > picture. > > iain > Well, I would expect "better" applications would allow to configure those extra buttons. Anyway, it's a bit shame having these cool buttons with no way to use them. :-( Regards, Martin From gamato at users.sf.net Fri Apr 4 20:10:58 2008 From: gamato at users.sf.net (mato) Date: Fri Apr 4 20:11:10 2008 Subject: Logitech V470 Bluetooth Mouse on FreeBSD ? In-Reply-To: References: <47ED9AC5.4050505@users.sf.net> <47EF668D.1080003@users.sf.net> <1206904241.480342.891.nullmailer@galant.ukfsn.org> <47F13BAD.9060808@users.sf.net> <1207142908.576787.1033.nullmailer@galant.ukfsn.org> Message-ID: <47F68B4F.4080706@users.sf.net> Maksim Yevmenkin wrote: > On 4/2/08, Iain Hibbert wrote: > >> On Mon, 31 Mar 2008, mato wrote: >> >>> Input id=2 size=8 count=1 page=Generic_Desktop usage=Wheel Variable >>> Input id=2 size=8 count=1 page=Consumer usage=AC_Pan Variable Relative, >>> What can be done about it ?? >>> >> I don't know - bthidd(4) could grow the support for AC_Pan fairly easily >> but I don't know how you would get that into the kernel - the mouse_info >> structure has no W direction and the ioctl would need to be versioned if >> the structure was extended as there was no padding.. >> > > exactly Iain. parsing hid messages in bthidd(8) and extracting all the > data is trivial. the question is how to feed those data into the > kernel. right now, bthidd(8) uses console ioctl to feed data into the > kernel. as you pointed out, mouse_info structure (specifically > mouse_data union) does not have have w direction. > > >> btw just to make you feel better I should say that sideways scroll does >> not always work in applications; eg GThumb considers the extra buttons >> to be 'next' and 'prev' instead and sideways scroll just jumps to the next >> picture. >> > > i have a wired usb apple mighty mouse here and horizontal scrolling > does not work for me at all. quick look at ums(4) showed that it does > not export w data (it tries to locate both wheel and z axis, however > it does not look for ac_pan axis). > > so, it appears that we need to teach moused(8), sysmouse(4) and mice > drivers about second wheel. it appears to be a somewhat bigger chunk > of work. > > The current situation seems to me not ideal and rather complicated. You said bthidd injects messages directly to kernel. I don't know what the consequences are but I noticed the following ... When I run moused my BT mouse works in console (except double clicks etc.). Unfortunately, because I wanted extra functionality from my Synaptics touchpad I installed x11-drivers/synaptics port which required disabling moused which handled the touchpad as ps/2 mouse. Now synaptics works great in X11 but it doesn't work in console at all and my BT mouse doesn't work in console either. But if I plug in a USB mouse devd runs moused and suddenly my BT mouse works in console too. Funny but very inconvenient, I can tell you. Fortunately I don't work in console that much anymore. With regards, Martin From gamato at users.sf.net Sun Apr 6 11:45:28 2008 From: gamato at users.sf.net (martinko) Date: Sun Apr 6 11:45:40 2008 Subject: Wi-Fi connection via iwi(4) dies regularly Message-ID: <47F8B7CA.1040001@users.sf.net> Hallo, I'm trying to use my Intel 2200bg WiFi card to access the internet (via D-Link DIR-655 gateway) but it is very unreliable. Usually within 1-3 hours connection dies and I have to restart it (I do it with /etc/rc.d/netif script). Then it works for some time and dies again and thus cycle repeats. :-/ Is there something I can do to help someone debug and fix this issue please ? Thanks! With regards, Martin I've got this in my /etc/rc.conf.local: ifconfig_iwi0="WPA DHCP" $ pciconf -lv [...] iwi0@pci2:3:0: class=0x028000 card=0x27018086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'MPCI3B driverIntel PRO/Wireless 2200BG' class = network $ ifconfig iwi0 iwi0: flags=8843 mtu 1500 inet 192.168.11.3 netmask 0xffffff00 broadcast 192.168.11.255 ether 00:0e:35:90:b1:7a media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) status: associated ssid gamato channel 1 bssid 00:1c:f0:f4:ab:a4 authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit TKIP 3:128-bit txpowmax 100 bmiss 10 protmode CTS roaming MANUAL bintval 100 $ uname -a FreeBSD mb-aw1n-bsd 6.3-STABLE FreeBSD 6.3-STABLE #0: Fri Mar 28 22:29:49 CET 2008 root@mb-aw1n-bsd:/usr/obj/usr/src/sys/MB-AW1N i386 PS: Please note that I'm not subscribed to freebsd-net@ From gamato at users.sf.net Sun Apr 6 11:45:29 2008 From: gamato at users.sf.net (martinko) Date: Sun Apr 6 11:45:40 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: <20080326155507.wiubhspc04ok440g@0x20.net> References: <0319208F-8098-4EAA-B3DA-22C6FE1C02DD@langille.org> <20080326155507.wiubhspc04ok440g@0x20.net> Message-ID: <47F8AD88.2010406@users.sf.net> Lars Engels wrote: > Quoting Dan Langille : > >> Hi, >> >> I'm running 7.0 amd64 with KDE 3.5 >> >> sysutils/klaptopdaemon works only on i386 >> >> What battery monitor software are you using? > > dbsd-battinfo from sysutils/desktopbsd-tools offers you a tray icon. > sysutils/nbosd can show you battery info and cpu frequency on demand > with and on screen display. > > > Lars Hi Lars, sysutils/nbosd looks very nice and rather useful, thanks! :-) However, I can think of the following: There are 2 important/interesting information missing: - remaining run-time in hours:minutes when running on battery - CPU temperature (especially on laptops) Also, it might be quite useful to render battery related info in red colour once battery charge drops below some (configurable) limit when not running on AC power. The last but not least important is this -- nbosd shows you info on demand only. I find that most often I forget about my battery running flat and thus nbosd wouldn't help. Any idea how to deal with it ? Cheers, Martin From besideinfo at yahoo.com Mon Apr 7 01:51:55 2008 From: besideinfo at yahoo.com (Pippo Pippone) Date: Mon Apr 7 01:52:02 2008 Subject: Wireless on hp 6710b Message-ID: <593165.78171.qm@web43142.mail.sp1.yahoo.com> Hi, I have a HP 6710b notebook with an Intel PRO/Wireless 802.1, and I'm trying to make the wireless to work. I followed the instruction from the freeBSD handbook but without result. When I type ifconfig I cant see the wireless card. I checked the kernel configuration file, and it contains all the devices needed (ath, ath_hal, ath_rate_sample, wlan, wlan_wep, wlan_ccmp, wlan_tkip). However, from the boot message I cant see any information for the ath0 device. The freeBDS I installed is 6.3 and the notebook is a core duo T7300. Thanks for your time in advance. --------------------------------- You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. From lars.engels at 0x20.net Mon Apr 7 11:33:59 2008 From: lars.engels at 0x20.net (Lars Engels) Date: Mon Apr 7 11:34:05 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: <47F8AD88.2010406@users.sf.net> References: <0319208F-8098-4EAA-B3DA-22C6FE1C02DD@langille.org> <20080326155507.wiubhspc04ok440g@0x20.net> <47F8AD88.2010406@users.sf.net> Message-ID: <20080407133354.djlrjmnm04ks0www@0x20.net> Quoting martinko : > Lars Engels wrote: >> Quoting Dan Langille : >> >>> Hi, >>> >>> I'm running 7.0 amd64 with KDE 3.5 >>> >>> sysutils/klaptopdaemon works only on i386 >>> >>> What battery monitor software are you using? >> >> dbsd-battinfo from sysutils/desktopbsd-tools offers you a tray icon. >> sysutils/nbosd can show you battery info and cpu frequency on >> demand with and on screen display. >> >> >> Lars > > Hi Lars, > > sysutils/nbosd looks very nice and rather useful, thanks! :-) > > However, I can think of the following: > > There are 2 important/interesting information missing: > - remaining run-time in hours:minutes when running on battery > - CPU temperature (especially on laptops) Good idea, it should be no problem to use sysctl to get those values. > Also, it might be quite useful to render battery related info in red > colour once battery charge drops below some (configurable) limit when > not running on AC power. > > The last but not least important is this -- nbosd shows you info on > demand only. I find that most often I forget about my battery running > flat and thus nbosd wouldn't help. Any idea how to deal with it ? nbosd was designed to show the value on demand. I have a keyboard shortcut which shows me the OSD whenever I need it. But the shortcut doesn't work in every case e.g. when playing fullscreen games. So I taught nbosd to work together with devd and now nbosd has an option to run as a daemon and only shows up when the battery percentage falls below a user-defined value. It still has some rough corners and the code needs to be cleaned up that's why I haven't committed the new version. I hope that my (very limited atm :-( ) time allows me get it finished, soon. Lars -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: Digitale PGP-Unterschrift Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080407/fd7099bd/attachment.pgp From fbsd.mobile at rachie.is-a-geek.net Mon Apr 7 13:54:48 2008 From: fbsd.mobile at rachie.is-a-geek.net (Mel) Date: Mon Apr 7 13:54:54 2008 Subject: [Regression] ACPI thermal not working HP Pavillion dv9207us Message-ID: <200804071554.15668.fbsd.mobile@rachie.is-a-geek.net> Hi, at present acpi thermal gives what I think are default values and no variance in the temperature at all. acpi0 is identified as: on motherboard The last known working version was Feb 22. At that time I stopped logging the temperature, so it's possible it was working afterwards. The version currently in the kernel is: $FreeBSD: src/sys/dev/acpica/acpi_thermal.c,v 1.64.2.4 2008/02/25 15:32:39 ume Exp $ Current output: hw.acpi.thermal.tz0.temperature: 32.0C hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.passive_cooling: 1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 80.0C hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 110.0C hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz0._TC1: 2 hw.acpi.thermal.tz0._TC2: 3 hw.acpi.thermal.tz0._TSP: 50 When I had hw.acpi.thermal.tz0.user_override=1 set, the value was a constant 28.0C. Both values seem way too low. Also, the _PSV and _CRT values set in sysctl.conf(5) are not set as I had them set: hw.acpi.thermal.tz0._PSV="75C" hw.acpi.thermal.tz0._CRT="82C" Before the lowest temperatures were around 40-50C and 55-65 when compiling large ports or world. At present it's compiling kdelibs, so I'd expect at least a 50C. Anything wrong on my end or is this known/patches floating? -- Mel From yousif at alumni.jmu.edu Mon Apr 7 15:40:35 2008 From: yousif at alumni.jmu.edu (Yousif Hassan) Date: Mon Apr 7 15:40:41 2008 Subject: Wireless on hp 6710b In-Reply-To: <593165.78171.qm@web43142.mail.sp1.yahoo.com> References: <593165.78171.qm@web43142.mail.sp1.yahoo.com> Message-ID: <2829B8CD63B1448295E02DDDDF4C2334@alderaan> "Pippo Pippone" wrote: > Hi, > I have a HP 6710b notebook with an Intel PRO/Wireless 802.1, and I'm > trying to make the wireless to work. > I followed the instruction from the freeBSD handbook but without result. > When I type ifconfig I cant see the wireless card. > I checked the kernel configuration file, and it contains all the devices > needed (ath, ath_hal, ath_rate_sample, wlan, wlan_wep, wlan_ccmp, > wlan_tkip). However, from the boot message I cant see any information for > the ath0 device. > The freeBDS I installed is 6.3 and the notebook is a core duo T7300. > > Thanks for your time in advance. You do realize that the ath driver is for Atheros cards, right? Do you have an Atheros card that you manually put in the system? If so, you need to send proper debugging output, like a verbose dmesg, ifconfig, pciconf -lv, etc so people can see why your Atheros card isn't recognized. However, out-of-the-box, that laptop probably has Intel PRO/Wireless, as you said. Try the wpi driver - if it's a 3945 it'll work. If you want to find out what model of wireless card you have, you can try the HP Parts Store online at hp.com or you can take the card out of the bottom of the laptop (usually mini-PCI slot) and look at it. --Yousif From maksim.yevmenkin at gmail.com Mon Apr 7 17:05:48 2008 From: maksim.yevmenkin at gmail.com (Maksim Yevmenkin) Date: Mon Apr 7 17:05:57 2008 Subject: Logitech V470 Bluetooth Mouse on FreeBSD ? In-Reply-To: <47F68B4F.4080706@users.sf.net> References: <47ED9AC5.4050505@users.sf.net> <47EF668D.1080003@users.sf.net> <1206904241.480342.891.nullmailer@galant.ukfsn.org> <47F13BAD.9060808@users.sf.net> <1207142908.576787.1033.nullmailer@galant.ukfsn.org> <47F68B4F.4080706@users.sf.net> Message-ID: [...] > > i have a wired usb apple mighty mouse here and horizontal scrolling > > does not work for me at all. quick look at ums(4) showed that it does > > not export w data (it tries to locate both wheel and z axis, however > > it does not look for ac_pan axis). > > > > so, it appears that we need to teach moused(8), sysmouse(4) and mice > > drivers about second wheel. it appears to be a somewhat bigger chunk > > of work. > > The current situation seems to me not ideal and rather complicated. You > said bthidd injects messages directly to kernel. I don't know what the > consequences are but I noticed the following ... When I run moused my BT > mouse works in console (except double clicks etc.). Unfortunately, because > I wanted extra functionality from my Synaptics touchpad I installed > x11-drivers/synaptics port which required disabling moused which handled the > touchpad as ps/2 mouse. Now synaptics works great in X11 but it doesn't > work in console at all and my BT mouse doesn't work in console either. But > if I plug in a USB mouse devd runs moused and suddenly my BT mouse works in > console too. Funny but very inconvenient, I can tell you. Fortunately I > don't work in console that much anymore. freebsd offers something called sysmouse(4). it allows the console and the user process (such as xorg) to share the mouse. if you use sysmouse(4) in xorg - the mouse will be shared between both console and xorg. if you use specific mouse driver (such as ums(4)) you will need to put /dev/ums0 in your xorg.conf and use appropriate xorg mouse driver. in the later case, the mouse will not be shared and will not work in the console. bthidd(8) uses console ioctl's to feed bluetooth mouse events into the kernel (i.e. feed events to sysmouse(4)). this way we automatically share bluetooth mouse between console and xorg. however, because sysmouse(4) protocol lacks knowledge about all the fancy buttons and wheels we can not pass this data to xorg. basically we are limited to whatever sysmouse(4) protocol knows about. currently, it is not possible to use bluetooth mouse directly from xorg/whatever, because there is no device node for it. in other words, there is no /dev/btmsX device node that feeds data in some protocol to consumers. i guess, it would be possible to write virtual mouse vms(4) driver (similar to virtual keyboard driver vkbd(4)) that would simply be used to pass through mouse data in, say, microsoft protocol or something like that. however, i think it would be better to add another level of operation to sysmouse(4) and change protocol so it can accommodate future extensions. thanks, max > > With regards, > > Martin > From volker at vwsoft.com Mon Apr 7 18:49:01 2008 From: volker at vwsoft.com (Volker) Date: Mon Apr 7 18:49:09 2008 Subject: Wireless on hp 6710b In-Reply-To: <593165.78171.qm@web43142.mail.sp1.yahoo.com> References: <593165.78171.qm@web43142.mail.sp1.yahoo.com> Message-ID: <47FA6845.8030008@vwsoft.com> On 12/23/-58 20:59, Pippo Pippone wrote: > Hi, > I have a HP 6710b notebook with an Intel PRO/Wireless 802.1, and I'm trying to make the wireless to work. > I followed the instruction from the freeBSD handbook but without result. When I type ifconfig I cant see the wireless card. > I checked the kernel configuration file, and it contains all the devices needed (ath, ath_hal, ath_rate_sample, wlan, wlan_wep, wlan_ccmp, wlan_tkip). However, from the boot message I cant see any information for the ath0 device. > The freeBDS I installed is 6.3 and the notebook is a core duo T7300. Pippo, please post output of `pciconf -lv' Volker From gamato at users.sf.net Mon Apr 7 19:42:47 2008 From: gamato at users.sf.net (martinko) Date: Mon Apr 7 19:42:52 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: <20080407133354.djlrjmnm04ks0www@0x20.net> References: <0319208F-8098-4EAA-B3DA-22C6FE1C02DD@langille.org> <20080326155507.wiubhspc04ok440g@0x20.net> <47F8AD88.2010406@users.sf.net> <20080407133354.djlrjmnm04ks0www@0x20.net> Message-ID: <47FA7351.4030601@users.sf.net> Lars Engels wrote: > Quoting martinko : >> Hi Lars, >> >> sysutils/nbosd looks very nice and rather useful, thanks! :-) >> >> However, I can think of the following: >> >> There are 2 important/interesting information missing: >> - remaining run-time in hours:minutes when running on battery >> - CPU temperature (especially on laptops) > > Good idea, it should be no problem to use sysctl to get those values. > >> Also, it might be quite useful to render battery related info in red >> colour once battery charge drops below some (configurable) limit when >> not running on AC power. >> >> The last but not least important is this -- nbosd shows you info on >> demand only. I find that most often I forget about my battery running >> flat and thus nbosd wouldn't help. Any idea how to deal with it ? > > nbosd was designed to show the value on demand. I have a keyboard > shortcut which shows me the OSD whenever I need it. > But the shortcut doesn't work in every case e.g. when playing > fullscreen games. So I taught nbosd to work together with devd and now > nbosd has an option to run as a daemon and only shows up when the > battery percentage falls below a user-defined value. > It still has some rough corners and the code needs to be cleaned up > that's why I haven't committed the new version. > I hope that my (very limited atm :-( ) time allows me get it finished, > soon. > Hi Lars, Remaining run-time (hours:minutes) could be next to the percentage value. I'm not sure about the temperature, though. I've set up a keyboard shotcut too (in WMaker) and it works great. However, sometimes I forget I'm running on battery and only find out when my laptop dies abruptly. That's why I'm trying to figure out how best to prevent such situations. And what do you say about my suggestion to render battery life text and graphics in red when running on DC and too low ? Would it be possible ? Cheers, Martin From andrey.kosachenko at gmail.com Mon Apr 7 20:45:59 2008 From: andrey.kosachenko at gmail.com (Andrey) Date: Mon Apr 7 20:46:03 2008 Subject: Wireless on hp 6710b In-Reply-To: <593165.78171.qm@web43142.mail.sp1.yahoo.com> References: <593165.78171.qm@web43142.mail.sp1.yahoo.com> Message-ID: <47FA8133.80106@gmail.com> Hi, Pippo Pippone! It seems you did things "literally" as they are described in handbook :o). Also you've not provided sufficient information concerned the wireless hardware you have. But still, you should use wpi instead of ath. Thus you need whether wpi in your kernel or you can load it as a kernel module. Actually (for quick start) you can try the configuration listed below: # less /boot/loader.conf if_wpi_load="YES" wlan_load="YES" wlan_amrr_load="YES" firmware_load="YES" legal.intel_wpi.license_ack=1 # this one is licence related stuff wpifw_load="YES" wlan_xauth_load="YES" wlan_wep_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" wlan_scan_sta_load="YES" wlan_scan_ap_load="YES" For more information take a look into man if_wpi. Also take into consideration that unfortunately if_wpi currently has limited abilities :(. For example Host AP and ad-hoc modes are not supported yet. Pippo Pippone wrote: > Hi, > I have a HP 6710b notebook with an Intel PRO/Wireless 802.1, and I'm trying to make the wireless to work. > I followed the instruction from the freeBSD handbook but without result. When I type ifconfig I cant see the wireless card. > I checked the kernel configuration file, and it contains all the devices needed (ath, ath_hal, ath_rate_sample, wlan, wlan_wep, wlan_ccmp, wlan_tkip). However, from the boot message I cant see any information for the ath0 device. > The freeBDS I installed is 6.3 and the notebook is a core duo T7300. > > Thanks for your time in advance. > > -- Sincerely, Andrey Kosachenko From besideinfo at yahoo.com Mon Apr 7 21:23:46 2008 From: besideinfo at yahoo.com (besideinfo) Date: Mon Apr 7 21:23:51 2008 Subject: Wireless on hp 6710b In-Reply-To: <2829B8CD63B1448295E02DDDDF4C2334@alderaan> Message-ID: <943905.64430.qm@web43138.mail.sp1.yahoo.com> I apologize for the poor post, but it was the first time I used a mailing list. (Newer stop to learn) Back to the topic you all are right; the atheros is not what I need. I have to wait to back in the office to try the correct driver. However, for your information following there is part of the pciconf. regards ------------------------------------------------ none3@pci16:0:0: class=0x028000 card=0x135c103c chip=0x42228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '10418086 Intel 3945ABG Wireless LAN controller' class = network bge0@pci24:0:0: class=0x020000 card=0x30c0103c chip=0x169314e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM 5787A Ethernet Controller Broadcom Netlink Gigabit' class = network subclass = ethernet --- Yousif Hassan wrote: > However, out-of-the-box, that laptop probably has > Intel PRO/Wireless, as you > said. Try the wpi driver - if it's a 3945 it'll > work. If you want to find > out what model of wireless card you have, you can > try the HP Parts Store > online at hp.com or you can take the card out of the > bottom of the laptop > (usually mini-PCI slot) and look at it. > > --Yousif > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to > "freebsd-mobile-unsubscribe@freebsd.org" > ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com From torfinn.ingolfsen at broadpark.no Mon Apr 7 23:21:59 2008 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Mon Apr 7 23:22:04 2008 Subject: Wireless on hp 6710b In-Reply-To: <2829B8CD63B1448295E02DDDDF4C2334@alderaan> References: <593165.78171.qm@web43142.mail.sp1.yahoo.com> <2829B8CD63B1448295E02DDDDF4C2334@alderaan> Message-ID: <20080408012156.e3686233.torfinn.ingolfsen@broadpark.no> On Mon, 07 Apr 2008 11:40:47 -0400 Yousif Hassan wrote: > However, out-of-the-box, that laptop probably has Intel PRO/Wireless, > as you said. Try the wpi driver - if it's a 3945 it'll work. If you > want to find out what model of wireless card you have, you can try > the HP Parts Store online at hp.com or you can take the card out of > the bottom of the laptop (usually mini-PCI slot) and look at it. Don't forget that 'pciconf -lv' is often the easiest way to identify many parts in a machine, among them the wireless card. (Easy as in "you don't have to physically dismantle something") HTH -- Regards, Torfinn Ingolfsen From andrey.kosachenko at gmail.com Tue Apr 8 07:09:55 2008 From: andrey.kosachenko at gmail.com (Andrey) Date: Tue Apr 8 07:10:01 2008 Subject: Wireless on hp 6710b In-Reply-To: <303421.62411.qm@web43132.mail.sp1.yahoo.com> References: <303421.62411.qm@web43132.mail.sp1.yahoo.com> Message-ID: <47FB1A36.3000903@gmail.com> Hi, besideinfo! It sounds like you've not loaded properly all the required modules. Make sure that everything you encountered in /boot/loader.conf is actually loaded (on this purpose use kldstat for example. NOTE I cut off unnecessary output below): # kldstat Id Refs Address Size Name .... 4 1 0xc08f8000 ebc4 if_wpi.ko 5 9 0xc0907000 2bfc0 wlan.ko 6 3 0xc0933000 30a8 firmware.ko 7 2 0xc0937000 1dc8 wlan_amrr.ko 8 1 0xc0939000 25f50 wpifw.ko 9 1 0xc095f000 1b3c wlan_xauth.ko 10 1 0xc0961000 2e2c wlan_wep.ko 11 1 0xc0964000 6ec4 wlan_ccmp.ko 12 1 0xc096b000 417c wlan_tkip.ko 13 1 0xc0970000 51dc wlan_scan_sta.ko 14 1 0xc0976000 1924 wlan_scan_ap.ko ..... Also make sure if license acknowledge variable is set (use kenv on this purpose): # kenv | grep 'wpi' legal.intel_wpi.license_ack="1" After all you should obtain smth. like this: # pciconf -lv | grep -B2 -A1 3945 wpi0@pci0:16:0:0: class=0x028000 card=0x135c103c chip=0x42228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '10418086 Intel 3945ABG Wireless LAN controller' class = network Also may it be you've already got support for wpi device in your kernel (as it is in ). So you don't need load modules you've in you kernel. But anyway firmware *must be* loaded before driver will work. According to documentation it is strict requirement. PS: Please, for further discussion make CC to freebsd-mobile@. It'll help to sort out your issue much faster. -- Sincerely, Andrey Kosachenko besideinfo wrote: > Hi Adrey, > I did as you suggest but steel the wireless doesn't > work. The strange thing is that on the dmesg there > isn't any information about the wireless. I believe > that wrong or correct I should see something from the > boot. If can help following there is my loader.conf > --------------- > sound_load="YES" > sound_ich_load="YES" > > if_wpi_load="YES" > wlan_load="YES" > wlan_amrr_load="YES" > firmware_load="YES" > legal.intel_wpi.license_ack=1 # this one is licence > related stuff > > wpifw_load="YES" > wlan_xauth_load="YES" > wlan_wep_load="YES" > wlan_ccmp_load="YES" > wlan_tkip_load="YES" > wlan_scan_sta_load="YES" > wlan_scan_ap_load="YES" > --------- > and this is part of my pciconf > > none3@pci16:0:0: class=0x028000 card=0x135c103c > chip=0x42228086 rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = '10418086 Intel 3945ABG Wireless LAN > controller' > class = network > bge0@pci24:0:0: class=0x020000 card=0x30c0103c > chip=0x169314e4 rev=0x02 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM 5787A Ethernet Controller > Broadcom Netlink Gigabit' > class = network > subclass = ethernet > ----- > If you want i can sent you a copy of dmesg > > thanks > --- Andrey wrote: > >> Hi, Pippo Pippone! >> >> It seems you did things "literally" as they are >> described in handbook >> :o). Also you've not provided sufficient information >> concerned the >> wireless hardware you have. >> >> But still, you should use wpi instead of ath. >> Thus you need whether wpi in your kernel or you can >> load it as a kernel >> module. >> >> Actually (for quick start) you can try the >> configuration listed below: >> >> # less /boot/loader.conf >> if_wpi_load="YES" >> wlan_load="YES" >> wlan_amrr_load="YES" >> firmware_load="YES" >> legal.intel_wpi.license_ack=1 # this one is licence >> related stuff >> >> wpifw_load="YES" >> wlan_xauth_load="YES" >> wlan_wep_load="YES" >> wlan_ccmp_load="YES" >> wlan_tkip_load="YES" >> wlan_scan_sta_load="YES" >> wlan_scan_ap_load="YES" >> >> For more information take a look into man if_wpi. >> >> Also take into consideration that unfortunately >> if_wpi currently has >> limited abilities :(. >> For example Host AP and ad-hoc modes are not >> supported yet. >> >> > > > > ____________________________________________________________________________________ > You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. > http://tc.deals.yahoo.com/tc/blockbuster/text5.com > > From besideinfo at yahoo.com Tue Apr 8 09:22:48 2008 From: besideinfo at yahoo.com (besideinfo) Date: Tue Apr 8 09:22:52 2008 Subject: Wireless on hp 6710b In-Reply-To: <47FB1A36.3000903@gmail.com> Message-ID: <451289.41848.qm@web43145.mail.sp1.yahoo.com> Hi Andrey, from the kldstat I can see five modules are missing. To be more specific the modules are: if_wpi.ko wlan_amrr.ko wpifw.ko wlan_scan_sta.ko wlan_scan_ap.ko my pciconf looks like: # pciconf -lv | grep -B2 -A1 3945 none2@pci16:0:0: class=0x028000 card=0x135c103c chip=0x42228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '10418086 Intel 3945ABG Wireless LAN controller' class = network However, as you can see from the /boot/loader.conf, the missing modules are declared. firmware_load="YES" if_wpi_load="YES" wlan_load="YES" wlan_amrr_load="YES" legal.intel_wpi.license_ack=1 wpifw_load="YES" wlan_xauth_load="YES" wlan_wep_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" wlan_scan_sta_load="YES" wlan_scan_ap_load="YES" #Intel HDA Audio snd_hda_load="YES". >From the dmesg the only message related to the wireless is the following: KLD file wlan_amrr.ko - could not finalize loading regards Agostino --- Andrey wrote: > Hi, besideinfo! > > It sounds like you've not loaded properly all the > required modules. > > Make sure that everything you encountered in > /boot/loader.conf is > actually loaded (on this purpose use kldstat for > example. NOTE I cut off > unnecessary output below): > > # kldstat > Id Refs Address Size Name > .... > 4 1 0xc08f8000 ebc4 if_wpi.ko > 5 9 0xc0907000 2bfc0 wlan.ko > 6 3 0xc0933000 30a8 firmware.ko > 7 2 0xc0937000 1dc8 wlan_amrr.ko > 8 1 0xc0939000 25f50 wpifw.ko > 9 1 0xc095f000 1b3c wlan_xauth.ko > 10 1 0xc0961000 2e2c wlan_wep.ko > 11 1 0xc0964000 6ec4 wlan_ccmp.ko > 12 1 0xc096b000 417c wlan_tkip.ko > 13 1 0xc0970000 51dc wlan_scan_sta.ko > 14 1 0xc0976000 1924 wlan_scan_ap.ko > ..... > > Also make sure if license acknowledge variable is > set (use kenv on this > purpose): > # kenv | grep 'wpi' > legal.intel_wpi.license_ack="1" > > After all you should obtain smth. like this: > > # pciconf -lv | grep -B2 -A1 3945 > wpi0@pci0:16:0:0: class=0x028000 > card=0x135c103c chip=0x42228086 > rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = '10418086 Intel 3945ABG Wireless > LAN controller' > class = network > > Also may it be you've already got support for wpi > device in your kernel > (as it is in ). So you don't need load modules > you've in you kernel. But > anyway firmware *must be* loaded before driver will > work. According to > documentation it is strict requirement. > > PS: > Please, for further discussion make CC to > freebsd-mobile@. It'll help to > sort out your issue much faster. > > -- > Sincerely, > Andrey Kosachenko ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com From besideinfo at yahoo.com Tue Apr 8 22:03:53 2008 From: besideinfo at yahoo.com (besideinfo) Date: Tue Apr 8 22:03:57 2008 Subject: Wireless on hp 6710b In-Reply-To: <96C1A65C78C446F9AA1C0D8145355971@alderaan> Message-ID: <84496.80244.qm@web43132.mail.sp1.yahoo.com> --- Yousif Hassan wrote: > I don't really understand what you mean here. Do > you mean they do not show > up in kldstat at all, or that they do show up in > kldstat but are still > "missing" in terms of being attached? (Both > scenarios possible). what I mean is that the five modules are declared in the loader.conf, but kldstat doesn't show them up. I tried to locate the five module using the locate command, but the only modules presents on my notebook are: wlan_amrr.ko and wpifw.ko > > my pciconf looks like: > > # pciconf -lv | grep -B2 -A1 3945 > > none2@pci16:0:0: class=0x028000 > card=0x135c103c > > chip=0x42228086 rev=0x02 hdr=0x00 > > vendor = 'Intel Corporation' > > device = '10418086 Intel 3945ABG Wireless > LAN > > controller' > > class = network > > I'm not sure if it'll matter - my pciconf is ever so > slightly different: > class=0x028000 card=0x135b103c chip=0x42228086 > rev=0x02 hdr=0x00 > ^ > I have b instead of c but I doubt this matters, > however only a developer of > wpi could answer definitively. > > > However, as you can see from the > /boot/loader.conf, > > the missing modules are declared. > > > > firmware_load="YES" > > if_wpi_load="YES" > > wlan_load="YES" > > wlan_amrr_load="YES" > > legal.intel_wpi.license_ack=1 > > wpifw_load="YES" > > wlan_xauth_load="YES" > > wlan_wep_load="YES" > > wlan_ccmp_load="YES" > > wlan_tkip_load="YES" > > wlan_scan_sta_load="YES" > > wlan_scan_ap_load="YES" > > > > #Intel HDA Audio > > snd_hda_load="YES". > > > >>>From the dmesg the only message related to the > > wireless is the following: > > KLD file wlan_amrr.ko - could not finalize loading > > It sounds like it could be because the modules are > failing to load - which > may *not* be a problem with the wireless card > itself, but something else. > If they *are* loading, but the device is not > attaching, then the problem > could be related to some hardware in your system. > > Did you try manually loading the if_wpi.ko module? > What error do you get? > There have been some bugs reported with certain PCI > implementations that > cause wpi not to attach, but I haven't (personally) > seen any bad reports for > HPs. My HP works, although it's a later model than > yours. In those cases, > the kernel module loads but doesn't attach. > > (Also, try not to top-post, it makes tracking the > current spot in the > conversation harder for new people coming into the > thread who may want to > help you.) > > --Yousif > > I forgot to say that this the first time I use freeBSD a mailing list and above my english is bad. ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com From besideinfo at yahoo.com Tue Apr 8 22:11:50 2008 From: besideinfo at yahoo.com (besideinfo) Date: Tue Apr 8 22:11:56 2008 Subject: Wireless on hp 6710b In-Reply-To: <96C1A65C78C446F9AA1C0D8145355971@alderaan> Message-ID: <36787.26104.qm@web43144.mail.sp1.yahoo.com> --- Yousif Hassan wrote: > I don't really understand what you mean here. Do > you mean they do not show > up in kldstat at all, or that they do show up in > kldstat but are still > "missing" in terms of being attached? (Both > scenarios possible). > > I'm not sure if it'll matter - my pciconf is ever so > slightly different: > class=0x028000 card=0x135b103c chip=0x42228086 > rev=0x02 hdr=0x00 > ^ > I have b instead of c but I doubt this matters, > however only a developer of > wpi could answer definitively. > It sounds like it could be because the modules are > failing to load - which > may *not* be a problem with the wireless card > itself, but something else. > If they *are* loading, but the device is not > attaching, then the problem > could be related to some hardware in your system. > > Did you try manually loading the if_wpi.ko module? > What error do you get? > There have been some bugs reported with certain PCI > implementations that > cause wpi not to attach, but I haven't (personally) > seen any bad reports for > HPs. My HP works, although it's a later model than > yours. In those cases, > the kernel module loads but doesn't attach. > > (Also, try not to top-post, it makes tracking the > current spot in the > conversation harder for new people coming into the > thread who may want to > help you.) > > --Yousif > > Sorry my previous post was incomplete. what I mean is that the five modules are declared in the loader.conf, but kldstat doesn't show them up. I tried to locate the five module using the locate command, but the only modules presents on my notebook are wlan_amrr.ko and wpifw.ko. The modules if_wpi, wlan_scan_sta and wlan_scan_ap do not exists. I forgot to say that this the first time I use freeBSD a mailing list and above my english is bad. So any advice are well accept. ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com From Benjamin.Close at clearchain.com Tue Apr 8 23:19:46 2008 From: Benjamin.Close at clearchain.com (Benjamin Close) Date: Tue Apr 8 23:19:52 2008 Subject: Wireless on hp 6710b In-Reply-To: <36787.26104.qm@web43144.mail.sp1.yahoo.com> References: <36787.26104.qm@web43144.mail.sp1.yahoo.com> Message-ID: <47FBFD8D.50501@clearchain.com> besideinfo wrote: > --- Yousif Hassan wrote: > > >> I don't really understand what you mean here. Do >> you mean they do not show >> up in kldstat at all, or that they do show up in >> kldstat but are still >> "missing" in terms of being attached? (Both >> scenarios possible). >> >> I'm not sure if it'll matter - my pciconf is ever so >> slightly different: >> class=0x028000 card=0x135b103c chip=0x42228086 >> rev=0x02 hdr=0x00 >> ^ >> I have b instead of c but I doubt this matters, >> however only a developer of >> wpi could answer definitively. >> It sounds like it could be because the modules are >> failing to load - which >> may *not* be a problem with the wireless card >> itself, but something else. >> If they *are* loading, but the device is not >> attaching, then the problem >> could be related to some hardware in your system. >> >> Did you try manually loading the if_wpi.ko module? >> What error do you get? >> There have been some bugs reported with certain PCI >> implementations that >> cause wpi not to attach, but I haven't (personally) >> seen any bad reports for >> HPs. My HP works, although it's a later model than >> yours. In those cases, >> the kernel module loads but doesn't attach. >> >> (Also, try not to top-post, it makes tracking the >> current spot in the >> conversation harder for new people coming into the >> thread who may want to >> help you.) >> >> --Yousif >> >> >> > Sorry my previous post was incomplete. > > what I mean is that the five modules are declared in > the loader.conf, but kldstat doesn't show them up. > > I tried to locate the five module using the locate > command, but the only modules presents on my notebook > are wlan_amrr.ko and wpifw.ko. > The modules if_wpi, wlan_scan_sta and wlan_scan_ap do > not exists. > > I forgot to say that this the first time I use freeBSD > a mailing list and above my english is bad. So any > advice are well accept. > > Some modules will not load as they are built into the kernel by default. Are you able to post the results of: ifconfig -v wpi0 a: dmesg |grep wpi would help after you boot verbosely (an option when FreeBSD starts) Cheers, Benjamin From besideinfo at yahoo.com Tue Apr 8 23:38:36 2008 From: besideinfo at yahoo.com (besideinfo) Date: Tue Apr 8 23:38:43 2008 Subject: Wireless on hp 6710b In-Reply-To: <47FBFD8D.50501@clearchain.com> Message-ID: <774099.14453.qm@web43135.mail.sp1.yahoo.com> --- Benjamin Close wrote: > besideinfo wrote: > > --- Yousif Hassan wrote: > > > > > >> I don't really understand what you mean here. Do > >> you mean they do not show > >> up in kldstat at all, or that they do show up in > >> kldstat but are still > >> "missing" in terms of being attached? (Both > >> scenarios possible). > >> > >> I'm not sure if it'll matter - my pciconf is ever > so > >> slightly different: > >> class=0x028000 card=0x135b103c chip=0x42228086 > >> rev=0x02 hdr=0x00 > >> ^ > >> I have b instead of c but I doubt this matters, > >> however only a developer of > >> wpi could answer definitively. > >> It sounds like it could be because the modules > are > >> failing to load - which > >> may *not* be a problem with the wireless card > >> itself, but something else. > >> If they *are* loading, but the device is not > >> attaching, then the problem > >> could be related to some hardware in your system. > >> > >> Did you try manually loading the if_wpi.ko > module? > >> What error do you get? > >> There have been some bugs reported with certain > PCI > >> implementations that > >> cause wpi not to attach, but I haven't > (personally) > >> seen any bad reports for > >> HPs. My HP works, although it's a later model > than > >> yours. In those cases, > >> the kernel module loads but doesn't attach. > >> > >> (Also, try not to top-post, it makes tracking the > >> current spot in the > >> conversation harder for new people coming into > the > >> thread who may want to > >> help you.) > >> > >> --Yousif > >> > >> > >> > > Sorry my previous post was incomplete. > > > > what I mean is that the five modules are declared > in > > the loader.conf, but kldstat doesn't show them up. > > > > > I tried to locate the five module using the locate > > command, but the only modules presents on my > notebook > > are wlan_amrr.ko and wpifw.ko. > > The modules if_wpi, wlan_scan_sta and wlan_scan_ap > do > > not exists. > > > > I forgot to say that this the first time I use > freeBSD > > a mailing list and above my english is bad. So any > > advice are well accept. > > > > > Some modules will not load as they are built into > the kernel by default. > Are you able to post the results of: > > ifconfig -v wpi0 > > a: > > dmesg |grep wpi > > would help after you boot verbosely (an option when > FreeBSD starts) > Cheers, > Benjamin > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to > "freebsd-mobile-unsubscribe@freebsd.org" > The result of ifconfig is: freebsd-box# ifconfig -v wpi0 ifconfig: interface wpi0 does not exist the result for dmesg is: freebsd-box# dmesg |grep wpi Preloaded elf module "/boot/kernel/wpifw.ko" at 0xc087d578. firmware: 'wpifw' version 2144: 149652 bytes loaded at 0xc07e9520 regards ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com From smithi at nimnet.asn.au Wed Apr 9 04:48:32 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Wed Apr 9 04:48:39 2008 Subject: Wireless on hp 6710b In-Reply-To: <47FBFD8D.50501@clearchain.com> Message-ID: On Wed, 9 Apr 2008, Benjamin Close wrote: > besideinfo wrote: > > --- Yousif Hassan wrote: > > > > > >> I don't really understand what you mean here. Do > >> you mean they do not show > >> up in kldstat at all, or that they do show up in > >> kldstat but are still > >> "missing" in terms of being attached? (Both > >> scenarios possible). [..] > > Sorry my previous post was incomplete. > > > > what I mean is that the five modules are declared in > > the loader.conf, but kldstat doesn't show them up. > > > > I tried to locate the five module using the locate > > command, but the only modules presents on my notebook > > are wlan_amrr.ko and wpifw.ko. > > The modules if_wpi, wlan_scan_sta and wlan_scan_ap do > > not exists. > > > > I forgot to say that this the first time I use freeBSD > > a mailing list and above my english is bad. So any > > advice are well accept. > > > > > Some modules will not load as they are built into the kernel by default. To besideinfo: In which case you should use kldstat -v to show all in-kernel modules. This can be a big list, so perhaps best search for 'missing' ones with: kldstat -v | egrep 'wpi|wlan' If they're there then there's no need to load them in /boot/loader.conf cheers, Ian > Are you able to post the results of: > > ifconfig -v wpi0 > > a: > > dmesg |grep wpi > > would help after you boot verbosely (an option when FreeBSD starts) > Cheers, > Benjamin From sam at freebsd.org Wed Apr 9 05:05:17 2008 From: sam at freebsd.org (Sam Leffler) Date: Wed Apr 9 05:05:20 2008 Subject: Wireless on hp 6710b In-Reply-To: References: Message-ID: <47FC4E6F.6030901@freebsd.org> Ian Smith wrote: > On Wed, 9 Apr 2008, Benjamin Close wrote: > > besideinfo wrote: > > > --- Yousif Hassan wrote: > > > > > > > > >> I don't really understand what you mean here. Do > > >> you mean they do not show > > >> up in kldstat at all, or that they do show up in > > >> kldstat but are still > > >> "missing" in terms of being attached? (Both > > >> scenarios possible). > > [..] > > > > Sorry my previous post was incomplete. > > > > > > what I mean is that the five modules are declared in > > > the loader.conf, but kldstat doesn't show them up. > > > > > > I tried to locate the five module using the locate > > > command, but the only modules presents on my notebook > > > are wlan_amrr.ko and wpifw.ko. > > > The modules if_wpi, wlan_scan_sta and wlan_scan_ap do > > > not exists. > > > > > > I forgot to say that this the first time I use freeBSD > > > a mailing list and above my english is bad. So any > > > advice are well accept. > > > > > > > > Some modules will not load as they are built into the kernel by default. > > To besideinfo: > > In which case you should use kldstat -v to show all in-kernel modules. > This can be a big list, so perhaps best search for 'missing' ones with: > > kldstat -v | egrep 'wpi|wlan' > > If they're there then there's no need to load them in /boot/loader.conf > > Folks, you're really making this more difficult than it needs to be. If you do man wpi you will see these modules are needed by the driver: if_wpi pci wlan wlan_amrr firmware (wpi is driver name specified in the config file; unfortunately the module name doesn't match). It turns out the wpi driver has builtin module dependencies for these so if you do: kldload if_wpi then the dependent modules will be brought in automatically. Now in addition the wlan code is broken up and (right now at least) requires that you manually load: wlan_scan_sta to get sta mode scanning support, and, depending on any security requirements: wlan_tkip wlan_ccmp wlan_wep Otherwise, as discussed in the wpi man page the firmware requires that you acknowlege use by setting the tunable with kenv or in your loader.conf. The hidden wlan dependencies should hopefully get fixed in HEAD soon. If someone were to pitch in to fixup sysinstall the firmware stuff could be handled at install time. That would mean you'd just need to do kldload if_wpi as was always intended. Sam From smithi at nimnet.asn.au Wed Apr 9 06:09:13 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Wed Apr 9 06:09:20 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: <47FA7351.4030601@users.sf.net> Message-ID: On Mon, 7 Apr 2008, martinko wrote: > Lars Engels wrote: > > Quoting martinko : > >> Hi Lars, > >> > >> sysutils/nbosd looks very nice and rather useful, thanks! :-) > >> > >> However, I can think of the following: > >> > >> There are 2 important/interesting information missing: > >> - remaining run-time in hours:minutes when running on battery > >> - CPU temperature (especially on laptops) > > > > Good idea, it should be no problem to use sysctl to get those values. > > > >> Also, it might be quite useful to render battery related info in red > >> colour once battery charge drops below some (configurable) limit when > >> not running on AC power. > >> > >> The last but not least important is this -- nbosd shows you info on > >> demand only. I find that most often I forget about my battery running > >> flat and thus nbosd wouldn't help. Any idea how to deal with it ? > > > > nbosd was designed to show the value on demand. I have a keyboard > > shortcut which shows me the OSD whenever I need it. > > But the shortcut doesn't work in every case e.g. when playing > > fullscreen games. So I taught nbosd to work together with devd and now > > nbosd has an option to run as a daemon and only shows up when the > > battery percentage falls below a user-defined value. > > It still has some rough corners and the code needs to be cleaned up > > that's why I haven't committed the new version. > > I hope that my (very limited atm :-( ) time allows me get it finished, > > soon. > > > > Hi Lars, > > Remaining run-time (hours:minutes) could be next to the percentage value. > I'm not sure about the temperature, though. > > I've set up a keyboard shotcut too (in WMaker) and it works great. > However, sometimes I forget I'm running on battery and only find out > when my laptop dies abruptly. That's why I'm trying to figure out how > best to prevent such situations. > > And what do you say about my suggestion to render battery life text and > graphics in red when running on DC and too low ? Would it be possible ? You may also like to have a look at sysutils/asapm which I've been using for years to good effect in KDE. Despite the name, and the initial blurb in pkg_descr, it works fine (better, actually) with ACPI, as detailed in the manual. It's also fully configurable regarding display colours etc, and if the remaining runtime isn't directly available, it can monitor state of charge over time to provide pretty good estimates, along with configurable setpoints for 'warning' and 'alarm' colours. I can't say whether it works on amd64 though .. On later (i386) machines I tend to use gkrellm which includes CPU temp, speed and much more, but again I don't know if it works with amd64. hth, Ian From freebsd.lists at fsck.ch Wed Apr 9 17:33:11 2008 From: freebsd.lists at fsck.ch (Tobias Roth) Date: Wed Apr 9 17:33:16 2008 Subject: S3 suspend/resume on T43p works like a charm with RELENG_7 Message-ID: <47FCF73A.4060302@fsck.ch> Hi everyone Today I was pleased to discover that S3 works like a charm on my IBM T43p with RELENG_7! Thanks to everybody who helped to make this possible. Regards, Tobias From besideinfo at yahoo.com Wed Apr 9 20:54:53 2008 From: besideinfo at yahoo.com (besideinfo) Date: Wed Apr 9 20:54:58 2008 Subject: Wireless on hp 6710b In-Reply-To: Message-ID: <549501.34648.qm@web43141.mail.sp1.yahoo.com> --- Ian Smith wrote: > On Wed, 9 Apr 2008, Benjamin Close wrote: > > besideinfo wrote: > > > --- Yousif Hassan > wrote: > > > > > > > > >> I don't really understand what you mean here. > Do > > >> you mean they do not show > > >> up in kldstat at all, or that they do show up > in > > >> kldstat but are still > > >> "missing" in terms of being attached? (Both > > >> scenarios possible). > > [..] > > To besideinfo: > > In which case you should use kldstat -v to show all > in-kernel modules. > This can be a big list, so perhaps best search for > 'missing' ones with: > > kldstat -v | egrep 'wpi|wlan' > > If they're there then there's no need to load them > in /boot/loader.conf > > cheers, Ian > As you asked following the output for kldstat -v | egrep 'wpi|wlan' freebsd-box# kldstat -v | egrep 'wpi|wlan' 5 5 0xc07c7000 1edf8 wlan.ko 4 wlan 7 1 0xc07e8000 26414 wpifw.ko 5 wpifw_fw 8 1 0xc080f000 1b10 wlan_xauth.ko 6 wlan_xauth 9 1 0xc0811000 2d08 wlan_wep.ko 7 wlan_wep 10 1 0xc0814000 6d04 wlan_ccmp.ko 8 wlan_ccmp 11 1 0xc081b000 4000 wlan_tkip.ko 9 wlan_tkip I try to use kldload, and the result make me believe that I'm missing the wpi driver or part of it. freebsd-box# kldload if_wpi kldload: can't load if_wpi: No such file or directory freebsd-box# kldload wlan_scan_sta kldload: can't load wlan_scan_sta: No such file or directory I'm thinking to reinstall freebsd maybe I did something wrong from the beginning. greetings __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From besideinfo at yahoo.com Wed Apr 9 21:50:42 2008 From: besideinfo at yahoo.com (besideinfo) Date: Wed Apr 9 21:50:48 2008 Subject: Wireless on hp 6710b In-Reply-To: Message-ID: <424763.95792.qm@web43138.mail.sp1.yahoo.com> --- Yousif Hassan wrote: > From: "besideinfo" > > > > --- Ian Smith wrote: > > > >> On Wed, 9 Apr 2008, Benjamin Close wrote: > >> > besideinfo wrote: > >> > > --- Yousif Hassan > >> wrote: > >> > > > >> > > > >> > >> I don't really understand what you mean > here. > >> Do > >> > >> you mean they do not show > >> > >> up in kldstat at all, or that they do show > up > >> in > >> > >> kldstat but are still > >> > >> "missing" in terms of being attached? > (Both > >> > >> scenarios possible). > >> > >> [..] > >> > >> To besideinfo: > >> > >> In which case you should use kldstat -v to show > all > >> in-kernel modules. > >> This can be a big list, so perhaps best search > for > >> 'missing' ones with: > >> > >> kldstat -v | egrep 'wpi|wlan' > >> > >> If they're there then there's no need to load > them > >> in /boot/loader.conf > >> > >> cheers, Ian > >> > > > > As you asked following the output for kldstat -v > | > > egrep 'wpi|wlan' > > > > freebsd-box# kldstat -v | egrep 'wpi|wlan' > > 5 5 0xc07c7000 1edf8 wlan.ko > > 4 wlan > > 7 1 0xc07e8000 26414 wpifw.ko > > 5 wpifw_fw > > 8 1 0xc080f000 1b10 wlan_xauth.ko > > 6 wlan_xauth > > 9 1 0xc0811000 2d08 wlan_wep.ko > > 7 wlan_wep > > 10 1 0xc0814000 6d04 wlan_ccmp.ko > > 8 wlan_ccmp > > 11 1 0xc081b000 4000 wlan_tkip.ko > > 9 wlan_tkip > > > > I try to use kldload, and the result make me > believe > > that I'm missing the wpi driver or part of it. > > > > freebsd-box# kldload if_wpi > > kldload: can't load if_wpi: No such file or > directory > > > > freebsd-box# kldload wlan_scan_sta > > kldload: can't load wlan_scan_sta: No such file or > > directory > > > > I'm thinking to reinstall freebsd maybe I did > > something wrong from the beginning. > > > > greetings > > It's becoming pretty clear that the reason you can't > load the wpi module is > because you may be missing some kernel module files > (this is why we asked > what happens if you manually kldload if_wpi). > > Do you see an if_wpi.ko (and the other "missing" > modules) in /boot/kernel/? As I said before the modules if_wpi, wlan_scan_sta and wlan_scan_ap do not exists. I try to locate them but without result. > If not, search for them elsewhere on the system - if > they're in the wrong > directory, move them into /boot/kernel. > > If they're completely missing, I wonder if you > rebuilt a kernel incorrectly, Yes I rebuilt the kernel, and I followed the instruction. I made some changing on the kernel configuration files, but the compilation process was completed without any error. > or anything like that. You don't have to reinstall > FBSD. Just rebuild the > kernel according to the instructions in the FreeBSD > Handbook. Make sure all > the object binaries are cleaned out before you > start. That should rebuild > the modules, too, and when you install the kernel, > it will put them into > /boot/kernel Please Yousif what you mean by "Make sure all the object binaries are cleaned out". If it can help, I can post my configuration file. regards __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From smithi at nimnet.asn.au Thu Apr 10 05:35:38 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Thu Apr 10 05:35:41 2008 Subject: Wireless on hp 6710b In-Reply-To: <549501.34648.qm@web43141.mail.sp1.yahoo.com> Message-ID: On Wed, 9 Apr 2008, besideinfo wrote: > --- Ian Smith wrote: > > > On Wed, 9 Apr 2008, Benjamin Close wrote: > > > besideinfo wrote: > > > > --- Yousif Hassan > > wrote: > > > > > > > > > > > >> I don't really understand what you mean here. Do > > > >> you mean they do not show > > > >> up in kldstat at all, or that they do show up in > > > >> kldstat but are still > > > >> "missing" in terms of being attached? (Both > > > >> scenarios possible). > > > > [..] > > > > To besideinfo: > > > > In which case you should use kldstat -v to show all > > in-kernel modules. > > This can be a big list, so perhaps best search for > > 'missing' ones with: > > > > kldstat -v | egrep 'wpi|wlan' > > > > If they're there then there's no need to load them > > in /boot/loader.conf > > > > cheers, Ian > > > > As you asked following the output for kldstat -v | > egrep 'wpi|wlan' > > freebsd-box# kldstat -v | egrep 'wpi|wlan' > 5 5 0xc07c7000 1edf8 wlan.ko > 4 wlan > 7 1 0xc07e8000 26414 wpifw.ko > 5 wpifw_fw > 8 1 0xc080f000 1b10 wlan_xauth.ko > 6 wlan_xauth > 9 1 0xc0811000 2d08 wlan_wep.ko > 7 wlan_wep > 10 1 0xc0814000 6d04 wlan_ccmp.ko > 8 wlan_ccmp > 11 1 0xc081b000 4000 wlan_tkip.ko > 9 wlan_tkip > > I try to use kldload, and the result make me believe > that I'm missing the wpi driver or part of it. > > freebsd-box# kldload if_wpi > kldload: can't load if_wpi: No such file or directory > > freebsd-box# kldload wlan_scan_sta > kldload: can't load wlan_scan_sta: No such file or > directory > > I'm thinking to reinstall freebsd maybe I did > something wrong from the beginning. Hmm. On re-reading the whole thread I notice that you didn't show what Andrey asked about, and while I don't know if it should actually affect the module loading, it's said that you need this in your loader.conf: : Also make sure if license acknowledge variable is set (use kenv on : this purpose): : # kenv | grep 'wpi' : legal.intel_wpi.license_ack="1" Otherwise it does look like your 6.3 install is missing something. cheers, Ian (Sam, sorry if I complicated matters, but many new users don't know about using 'kldstat -v' to check modules, in my humble experience) From smithi at nimnet.asn.au Thu Apr 10 09:41:18 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Thu Apr 10 09:41:21 2008 Subject: [OT, sorry] Mail delivery failed: returning message to sender (fwd) Message-ID: Every time I post to mobile@ lately I get one of these, complete with a full-headers attachment of the message as attempted to be delivered to luigi@acampo.net by the list. I'll get another one for this message. As I can't contact him directly for obvious reasons, would somebody mind informing the subscriber luigi@acampo.net that I don't care if he wants to blacklist messages originally from me for whatever reason might take his fancy, but I really don't need to know about it each time, thanks. cheers, Ian attachment removed: 1. [Text: original-mail.eml] (7.8KB) "" ---------- Forwarded message ---------- Received: from mail.acampo.net (mail.acampo.net [213.203.218.253]) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with ESMTP id PAA23573 for ; Thu, 10 Apr 2008 15:37:24 +1000 (EST) (envelope-from Mailer-Daemon@mail.acampo.net) Received: from mail by mail.acampo.net with local (Exim 4.63) (envelope-from ) id 1JjpTI-0000Fc-5C for smithi@nimnet.asn.au; Thu, 10 Apr 2008 07:37:16 +0200 To: smithi@nimnet.asn.au Subject: Mail delivery failed: returning message to sender From: "Mail Delivery System" MIME-Version: 1.0 Date: Thu, 10 Apr 2008 07:37:16 +0200 Content-Type: multipart/mixed;report-type=delivery-status; boundary="--Boundary-=_cce87ed64a9797cc15baf3dfc30d4285" X-Mailer: Acampo 6.2.0 (www.acampo.net) X-Sender-IP: [] X-Priority: 3 Message-Id: X-Info: valid message X-Info: original Date The original message was received at Thu, 10 Apr 2008 07:37:16 +0200 from smithi@nimnet.asn.au by Acampo.net Error: You are on the blacklist of the recipient. From brd at FreeBSD.org Thu Apr 10 16:50:21 2008 From: brd at FreeBSD.org (Brad Davis) Date: Thu Apr 10 16:50:27 2008 Subject: [OT, sorry] Mail delivery failed: returning message to sender (fwd) In-Reply-To: References: Message-ID: <20080410162133.GE47438@valentine.liquidneon.com> On Thu, Apr 10, 2008 at 07:41:12PM +1000, Ian Smith wrote: > Every time I post to mobile@ lately I get one of these, complete with a > full-headers attachment of the message as attempted to be delivered to > luigi@acampo.net by the list. I'll get another one for this message. > > As I can't contact him directly for obvious reasons, would somebody mind > informing the subscriber luigi@acampo.net that I don't care if he wants > to blacklist messages originally from me for whatever reason might take > his fancy, but I really don't need to know about it each time, thanks. > > cheers, Ian Testing to check and see if he is blacklisting the entire mailing list or just Ian. Regards, Brad Davis (On behalf of postmaster@) From besideinfo at yahoo.com Thu Apr 10 16:52:27 2008 From: besideinfo at yahoo.com (besideinfo) Date: Thu Apr 10 16:52:31 2008 Subject: Wireless on hp 6710b In-Reply-To: Message-ID: <490957.84586.qm@web43136.mail.sp1.yahoo.com> --- Ian Smith wrote: > Hmm. On re-reading the whole thread I notice that > you didn't show what > Andrey asked about, and while I don't know if it > should actually affect > the module loading, it's said that you need this in > your loader.conf: > > : Also make sure if license acknowledge variable is > set (use kenv on > : this purpose): > : # kenv | grep 'wpi' > : legal.intel_wpi.license_ack="1" > > Otherwise it does look like your 6.3 install is > missing something. > > cheers, Ian > > (Sam, sorry if I complicated matters, but many new > users don't know > about using 'kldstat -v' to check modules, in my > humble experience) > At this point I believe it is better to summarize all I have done so far. I rebuilt my kernel the same day I installed freeBSD. I followed the instructions on the handbook, and all process was successfully completed. Later, I realized that the wireless card wasn't working, and after some posts I found out(with your help) ath0 wasn't suitable for the wireless card. Because of that I decided to "rebuild again" the kenel, but this time I removed all wireless devices from the configuration file and used the /boot/conf.loader so configurated: #hint.acpi.0.disabled="1" firmware_load="YES" if_wpi_load="YES" wlan_load="YES" wlan_amrr_load="YES" legal.intel_wpi.license_ack=1 wpifw_load="YES" wlan_xauth_load="YES" wlan_wep_load="YES" wlan_ccmp_load="YES" wlan_tkip_load="YES" wlan_scan_sta_load="YES" wlan_scan_ap_load="YES" #Intel HDA Audio snd_hda_load="YES" After reboot I the freebsd still wasn't able to "see" the wireless card. Following there are the result of parts of the tests you asked me to do: ---------------- freebsd-box# pciconf -lv | grep -B2 -A1 3945 none2@pci16:0:0: class=0x028000 card=0x135c103c chip=0x42228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '10418086 Intel 3945ABG Wireless LAN controller' class = network ------------------- freebsd-box# kldstat -v | egrep 'wpi|wlan' 5 5 0xc07c7000 1edf8 wlan.ko 4 wlan 7 1 0xc07e8000 26414 wpifw.ko 5 wpifw_fw 8 1 0xc080f000 1b10 wlan_xauth.ko 6 wlan_xauth 9 1 0xc0811000 2d08 wlan_wep.ko 7 wlan_wep 10 1 0xc0814000 6d04 wlan_ccmp.ko 8 wlan_ccmp 11 1 0xc081b000 4000 wlan_tkip.ko 9 wlan_tkip -------------------- freebsd-box# kenv | grep 'wpi' legal.intel_wpi.license_ack="1" -------------------- freebsd-box# ifconfig -v wpi0 ifconfig: interface wpi0 does not exist -------------------- regards __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From dan at langille.org Thu Apr 10 17:25:16 2008 From: dan at langille.org (Dan Langille) Date: Thu Apr 10 17:25:24 2008 Subject: [OT, sorry] Mail delivery failed: returning message to sender (fwd) In-Reply-To: <20080410162133.GE47438@valentine.liquidneon.com> References: <20080410162133.GE47438@valentine.liquidneon.com> Message-ID: <10A1D80A-86C7-4DCD-8D41-DEF8DA99702E@langille.org> On Apr 10, 2008, at 12:21 PM, Brad Davis wrote: > On Thu, Apr 10, 2008 at 07:41:12PM +1000, Ian Smith wrote: >> Every time I post to mobile@ lately I get one of these, complete >> with a >> full-headers attachment of the message as attempted to be >> delivered to >> luigi@acampo.net by the list. I'll get another one for this message. >> >> As I can't contact him directly for obvious reasons, would >> somebody mind >> informing the subscriber luigi@acampo.net that I don't care if he >> wants >> to blacklist messages originally from me for whatever reason might >> take >> his fancy, but I really don't need to know about it each time, >> thanks. >> >> cheers, Ian > > Testing to check and see if he is blacklisting the entire mailing > list or > just Ian. FYI I've seen similar message myself when posting. -- Dan Langille -- http://www.langille.org/ dan@langille.org From smithi at nimnet.asn.au Thu Apr 10 17:25:56 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Thu Apr 10 17:26:03 2008 Subject: [OT, sorry] Mail delivery failed: returning message to sender (fwd) In-Reply-To: <20080410162133.GE47438@valentine.liquidneon.com> Message-ID: On Thu, 10 Apr 2008, Brad Davis wrote: > On Thu, Apr 10, 2008 at 07:41:12PM +1000, Ian Smith wrote: > > Every time I post to mobile@ lately I get one of these, complete with a > > full-headers attachment of the message as attempted to be delivered to > > luigi@acampo.net by the list. I'll get another one for this message. Actually I didn't get another bounce from my previous message (that one) so maybe it's now sorted. > Testing to check and see if he is blacklisting the entire mailing list or > just Ian. > > > Regards, > Brad Davis > (On behalf of postmaster@) Thanks Brad. Will notify offlist if further probs. Thanks also to Alexandre for mailing Luigi offlist. cheers, Ian From dan at langille.org Thu Apr 10 18:14:46 2008 From: dan at langille.org (Dan Langille) Date: Thu Apr 10 18:14:52 2008 Subject: [OT, sorry] Mail delivery failed: returning message to sender (fwd) In-Reply-To: <10A1D80A-86C7-4DCD-8D41-DEF8DA99702E@langille.org> References: <20080410162133.GE47438@valentine.liquidneon.com> <10A1D80A-86C7-4DCD-8D41-DEF8DA99702E@langille.org> Message-ID: On Apr 10, 2008, at 1:24 PM, Dan Langille wrote: > > On Apr 10, 2008, at 12:21 PM, Brad Davis wrote: >> On Thu, Apr 10, 2008 at 07:41:12PM +1000, Ian Smith wrote: >>> Every time I post to mobile@ lately I get one of these, complete >>> with a >>> full-headers attachment of the message as attempted to be >>> delivered to >>> luigi@acampo.net by the list. I'll get another one for this >>> message. >>> >>> As I can't contact him directly for obvious reasons, would >>> somebody mind >>> informing the subscriber luigi@acampo.net that I don't care if he >>> wants >>> to blacklist messages originally from me for whatever reason >>> might take >>> his fancy, but I really don't need to know about it each time, >>> thanks. >>> >>> cheers, Ian >> >> Testing to check and see if he is blacklisting the entire mailing >> list or >> just Ian. > > FYI > > I've seen similar message myself when posting. FWIW, it happened again on the above post. -- Dan Langille -- http://www.langille.org/ dan@langille.org From Benjamin.Close at clearchain.com Thu Apr 10 22:44:54 2008 From: Benjamin.Close at clearchain.com (Benjamin Close) Date: Thu Apr 10 22:44:58 2008 Subject: Wireless on hp 6710b In-Reply-To: <490957.84586.qm@web43136.mail.sp1.yahoo.com> References: <490957.84586.qm@web43136.mail.sp1.yahoo.com> Message-ID: <47FE985E.5080400@clearchain.com> besideinfo wrote: > --- Ian Smith wrote: > > > >> Hmm. On re-reading the whole thread I notice that >> you didn't show what >> Andrey asked about, and while I don't know if it >> should actually affect >> the module loading, it's said that you need this in >> your loader.conf: >> >> : Also make sure if license acknowledge variable is >> set (use kenv on >> : this purpose): >> : # kenv | grep 'wpi' >> : legal.intel_wpi.license_ack="1" >> >> Otherwise it does look like your 6.3 install is >> missing something. >> >> cheers, Ian >> >> (Sam, sorry if I complicated matters, but many new >> users don't know >> about using 'kldstat -v' to check modules, in my >> humble experience) >> >> > > At this point I believe it is better to summarize all > I have done so far. > > I rebuilt my kernel the same day I installed freeBSD. > I followed the instructions on the handbook, and all > process was successfully completed. > > Later, I realized that the wireless card wasn't > working, and after some posts I found out(with your > help) ath0 wasn't suitable for the wireless card. > > Because of that I decided to "rebuild again" the > kenel, but this time I removed all wireless devices > from the configuration file and used the > /boot/conf.loader so configurated: > > #hint.acpi.0.disabled="1" > > firmware_load="YES" > if_wpi_load="YES" > wlan_load="YES" > wlan_amrr_load="YES" > legal.intel_wpi.license_ack=1 > wpifw_load="YES" > wlan_xauth_load="YES" > wlan_wep_load="YES" > wlan_ccmp_load="YES" > wlan_tkip_load="YES" > wlan_scan_sta_load="YES" > wlan_scan_ap_load="YES" > > #Intel HDA Audio > snd_hda_load="YES" > > After reboot I the freebsd still wasn't able to "see" > the wireless card. Following there are the result of > parts of the tests you asked me to do: > ---------------- > freebsd-box# pciconf -lv | grep -B2 -A1 3945 > none2@pci16:0:0: class=0x028000 card=0x135c103c > chip=0x42228086 rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = '10418086 Intel 3945ABG Wireless LAN > controller' > class = network > ------------------- > freebsd-box# kldstat -v | egrep 'wpi|wlan' > 5 5 0xc07c7000 1edf8 wlan.ko > 4 wlan > 7 1 0xc07e8000 26414 wpifw.ko > 5 wpifw_fw > 8 1 0xc080f000 1b10 wlan_xauth.ko > 6 wlan_xauth > 9 1 0xc0811000 2d08 wlan_wep.ko > 7 wlan_wep > 10 1 0xc0814000 6d04 wlan_ccmp.ko > 8 wlan_ccmp > 11 1 0xc081b000 4000 wlan_tkip.ko > 9 wlan_tkip > -------------------- > freebsd-box# kenv | grep 'wpi' > legal.intel_wpi.license_ack="1" > -------------------- > freebsd-box# ifconfig -v wpi0 > ifconfig: interface wpi0 does not exist > -------------------- > > The problem you are facing is caused by the driver module not being loaded You should have a file: if_wpi.ko when you run kldstat -v Because that module is not loaded you won't see the wpi0 interface. In previous email you stated that you don't have /boot/kernel/if_wpi.ko That seems very wrong, as the driver should be built as part of a kernel build. The quick fix for your problem is: cd /usr/src/sys/modules/wpi make make install That should provide you with the module you need. Why it was not built in the first place on your system I've got no idea. Cheers, Benjamin From besideinfo at yahoo.com Thu Apr 10 23:35:11 2008 From: besideinfo at yahoo.com (besideinfo) Date: Thu Apr 10 23:35:18 2008 Subject: Wireless on hp 6710b In-Reply-To: <47FE985E.5080400@clearchain.com> Message-ID: <144605.60321.qm@web43143.mail.sp1.yahoo.com> --- Benjamin Close wrote: > besideinfo wrote: > > --- Ian Smith wrote: > > > > > > > >> Hmm. On re-reading the whole thread I notice > that > >> you didn't show what > >> Andrey asked about, and while I don't know if it > >> should actually affect > >> the module loading, it's said that you need this > in > >> your loader.conf: > >> > >> : Also make sure if license acknowledge variable > is > >> set (use kenv on > >> : this purpose): > >> : # kenv | grep 'wpi' > >> : legal.intel_wpi.license_ack="1" > >> > >> Otherwise it does look like your 6.3 install is > >> missing something. > >> > >> cheers, Ian > >> > >> (Sam, sorry if I complicated matters, but many > new > >> users don't know > >> about using 'kldstat -v' to check modules, in my > >> humble experience) > >> > >> > > > > At this point I believe it is better to summarize > all > > I have done so far. > > > > I rebuilt my kernel the same day I installed > freeBSD. > > I followed the instructions on the handbook, and > all > > process was successfully completed. > > > > Later, I realized that the wireless card wasn't > > working, and after some posts I found out(with > your > > help) ath0 wasn't suitable for the wireless card. > > > > Because of that I decided to "rebuild again" the > > kenel, but this time I removed all wireless > devices > > from the configuration file and used the > > /boot/conf.loader so configurated: > > > > #hint.acpi.0.disabled="1" > > > > firmware_load="YES" > > if_wpi_load="YES" > > wlan_load="YES" > > wlan_amrr_load="YES" > > legal.intel_wpi.license_ack=1 > > wpifw_load="YES" > > wlan_xauth_load="YES" > > wlan_wep_load="YES" > > wlan_ccmp_load="YES" > > wlan_tkip_load="YES" > > wlan_scan_sta_load="YES" > > wlan_scan_ap_load="YES" > > > > #Intel HDA Audio > > snd_hda_load="YES" > > > > After reboot I the freebsd still wasn't able to > "see" > > the wireless card. Following there are the result > of > > parts of the tests you asked me to do: > > ---------------- > > freebsd-box# pciconf -lv | grep -B2 -A1 3945 > > none2@pci16:0:0: class=0x028000 > card=0x135c103c > > chip=0x42228086 rev=0x02 hdr=0x00 > > vendor = 'Intel Corporation' > > device = '10418086 Intel 3945ABG Wireless > LAN > > controller' > > class = network > > ------------------- > > freebsd-box# kldstat -v | egrep 'wpi|wlan' > > 5 5 0xc07c7000 1edf8 wlan.ko > > 4 wlan > > 7 1 0xc07e8000 26414 wpifw.ko > > 5 wpifw_fw > > 8 1 0xc080f000 1b10 wlan_xauth.ko > > 6 wlan_xauth > > 9 1 0xc0811000 2d08 wlan_wep.ko > > 7 wlan_wep > > 10 1 0xc0814000 6d04 wlan_ccmp.ko > > 8 wlan_ccmp > > 11 1 0xc081b000 4000 wlan_tkip.ko > > 9 wlan_tkip > > -------------------- > > freebsd-box# kenv | grep 'wpi' > > legal.intel_wpi.license_ack="1" > > -------------------- > > freebsd-box# ifconfig -v wpi0 > > ifconfig: interface wpi0 does not exist > > -------------------- > > > > > The problem you are facing is caused by the driver > module not being loaded > You should have a file: if_wpi.ko when you run > kldstat -v > Because that module is not loaded you won't see the > wpi0 interface. > > In previous email you stated that you don't have > /boot/kernel/if_wpi.ko > That seems very wrong, as the driver should be built > as part of a kernel > build. > The quick fix for your problem is: > > cd /usr/src/sys/modules/wpi > make > make install > > That should provide you with the module you need. > Why it was not built in the first place on your > system I've got no idea. > > Cheers, > Benjamin > Benjamin the path "" dcd /usr/src/sys/modules/wpioesn't exist, and I don't know why. Maybe when I install freebsd I did something wrong. Should I use sysinstall to get the missing files? greetings __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From andrey.kosachenko at gmail.com Fri Apr 11 07:31:19 2008 From: andrey.kosachenko at gmail.com (Andrey) Date: Fri Apr 11 07:31:23 2008 Subject: Wireless on hp 6710b In-Reply-To: <144605.60321.qm@web43143.mail.sp1.yahoo.com> References: <144605.60321.qm@web43143.mail.sp1.yahoo.com> Message-ID: <47FF13B3.1030907@gmail.com> Hmm... things you've mentioned above sound very (*very*) suspicious. Could you please provide us with output of # uname -a Also (just in case) could you please show the output of: # egrep -A1 '^200[78][0-9]{4}:' /usr/src/UPDATING | head -n 30 and # ls -alF /usr/src/sys/dev/wpi/ besideinfo wrote: > --- Benjamin Close > wrote: > >> besideinfo wrote: >>> --- Ian Smith wrote: >>> >>> >>> >>>> Hmm. On re-reading the whole thread I notice >> that >>>> you didn't show what >>>> Andrey asked about, and while I don't know if it >>>> should actually affect >>>> the module loading, it's said that you need this >> in >>>> your loader.conf: >>>> >>>> : Also make sure if license acknowledge variable >> is >>>> set (use kenv on >>>> : this purpose): >>>> : # kenv | grep 'wpi' >>>> : legal.intel_wpi.license_ack="1" >>>> >>>> Otherwise it does look like your 6.3 install is >>>> missing something. >>>> >>>> cheers, Ian >>>> >>>> (Sam, sorry if I complicated matters, but many >> new >>>> users don't know >>>> about using 'kldstat -v' to check modules, in my >>>> humble experience) >>>> >>>> >>> At this point I believe it is better to summarize >> all >>> I have done so far. >>> >>> I rebuilt my kernel the same day I installed >> freeBSD. >>> I followed the instructions on the handbook, and >> all >>> process was successfully completed. >>> >>> Later, I realized that the wireless card wasn't >>> working, and after some posts I found out(with >> your >>> help) ath0 wasn't suitable for the wireless card. >>> >>> Because of that I decided to "rebuild again" the >>> kenel, but this time I removed all wireless >> devices >>> from the configuration file and used the >>> /boot/conf.loader so configurated: >>> >>> #hint.acpi.0.disabled="1" >>> >>> firmware_load="YES" >>> if_wpi_load="YES" >>> wlan_load="YES" >>> wlan_amrr_load="YES" >>> legal.intel_wpi.license_ack=1 >>> wpifw_load="YES" >>> wlan_xauth_load="YES" >>> wlan_wep_load="YES" >>> wlan_ccmp_load="YES" >>> wlan_tkip_load="YES" >>> wlan_scan_sta_load="YES" >>> wlan_scan_ap_load="YES" >>> >>> #Intel HDA Audio >>> snd_hda_load="YES" >>> >>> After reboot I the freebsd still wasn't able to >> "see" >>> the wireless card. Following there are the result >> of >>> parts of the tests you asked me to do: >>> ---------------- >>> freebsd-box# pciconf -lv | grep -B2 -A1 3945 >>> none2@pci16:0:0: class=0x028000 >> card=0x135c103c >>> chip=0x42228086 rev=0x02 hdr=0x00 >>> vendor = 'Intel Corporation' >>> device = '10418086 Intel 3945ABG Wireless >> LAN >>> controller' >>> class = network >>> ------------------- >>> freebsd-box# kldstat -v | egrep 'wpi|wlan' >>> 5 5 0xc07c7000 1edf8 wlan.ko >>> 4 wlan >>> 7 1 0xc07e8000 26414 wpifw.ko >>> 5 wpifw_fw >>> 8 1 0xc080f000 1b10 wlan_xauth.ko >>> 6 wlan_xauth >>> 9 1 0xc0811000 2d08 wlan_wep.ko >>> 7 wlan_wep >>> 10 1 0xc0814000 6d04 wlan_ccmp.ko >>> 8 wlan_ccmp >>> 11 1 0xc081b000 4000 wlan_tkip.ko >>> 9 wlan_tkip >>> -------------------- >>> freebsd-box# kenv | grep 'wpi' >>> legal.intel_wpi.license_ack="1" >>> -------------------- >>> freebsd-box# ifconfig -v wpi0 >>> ifconfig: interface wpi0 does not exist >>> -------------------- >>> >>> >> The problem you are facing is caused by the driver >> module not being loaded >> You should have a file: if_wpi.ko when you run >> kldstat -v >> Because that module is not loaded you won't see the >> wpi0 interface. >> >> In previous email you stated that you don't have >> /boot/kernel/if_wpi.ko >> That seems very wrong, as the driver should be built >> as part of a kernel >> build. >> The quick fix for your problem is: >> >> cd /usr/src/sys/modules/wpi >> make >> make install >> >> That should provide you with the module you need. >> Why it was not built in the first place on your >> system I've got no idea. >> >> Cheers, >> Benjamin >> > > Benjamin the path "" dcd > /usr/src/sys/modules/wpioesn't exist, and I don't know > why. Maybe when I install freebsd I did something > wrong. Should I use sysinstall to get the missing > files? > > greetings > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > -- Sincerely, Andrey Kosachenko From besideinfo at yahoo.com Fri Apr 11 19:09:05 2008 From: besideinfo at yahoo.com (besideinfo) Date: Fri Apr 11 19:09:11 2008 Subject: Wireless on hp 6710b In-Reply-To: <47FF13B3.1030907@gmail.com> Message-ID: <84817.76904.qm@web43135.mail.sp1.yahoo.com> --- Andrey wrote: > Hmm... things you've mentioned above sound very > (*very*) suspicious. > Could you please provide us with output of > # uname -a > > Also (just in case) could you please show the output > of: > # egrep -A1 '^200[78][0-9]{4}:' /usr/src/UPDATING | > head -n 30 > > and > > # ls -alF /usr/src/sys/dev/wpi/ > > Following the output you asked. Just one more thing, yesterday I compiled again the kernel backing to the GENERIC one, but the result didn't change. ---------------------------------------------------- freebsd-box# uname -a FreeBSD freebsd-box 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Fri Apr 11 08:35:29 CEST 2008 root@freebsd-box:/usr/obj/usr/src/sys/GENERIC i386 ----------------------------------------------------- freebsd-box# egrep -A1 '^200[78][0-9]{4}:' /usr/src/UPDATING | head -n 30 20080118: FreeBSD 6.3-RELEASE -- 20080118: FreeBSD-SA-08:01.pty, FreeBSD-SA-08:02.libc Fix issues which allow snooping on ptys. [08:01] -- 20071129: FreeBSD-SA-07:09.random Correct a random value disclosure in random(4). -- 20071127: The AT keyboard emulation of sunkbd(4) has been turned on -- 20071024: A breakage was introduced in libc and fixed later. Make sure -- 20070806: An incorrect field size in an ioctl struct for if_bridge(4) has been -- 20070426: The ABI breakage in sendmail(8)'s libmilter has been repaired -- 20070411: sendmail(8) has been updated to version 8.14.1. Mail filters -- 20070115: FreeBSD 6.2-RELEASE ---------------------------------------------------- freebsd-box# ls -alF /usr/src/sys/dev/wpi/ ls: /usr/src/sys/dev/wpi/: No such file or directory __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From andrey.kosachenko at gmail.com Fri Apr 11 19:36:05 2008 From: andrey.kosachenko at gmail.com (Andrey) Date: Fri Apr 11 19:36:12 2008 Subject: Wireless on hp 6710b In-Reply-To: <84817.76904.qm@web43135.mail.sp1.yahoo.com> References: <84817.76904.qm@web43135.mail.sp1.yahoo.com> Message-ID: <47FFBD79.1040808@gmail.com> O-o-ops... Sorry, I was so inattentive to details. The wpi driver has not been MFC'ed to RELENG_6 yet :(. It was clear from the very beginning. But I missed the version of your system (you've mentioned it at the first message!!!) For more details refer to CVS repository or just take a glance here: http://www.clearchain.com/wiki/Wpi I don't know why, but I was completely sure that wpi has already been backported to RELENG_6. besideinfo wrote: > --- Andrey wrote: > >> Hmm... things you've mentioned above sound very >> (*very*) suspicious. >> Could you please provide us with output of >> # uname -a >> >> Also (just in case) could you please show the output >> of: >> # egrep -A1 '^200[78][0-9]{4}:' /usr/src/UPDATING | >> head -n 30 >> >> and >> >> # ls -alF /usr/src/sys/dev/wpi/ >> >> > > Following the output you asked. Just one more thing, > yesterday I compiled again the kernel backing to the > GENERIC one, but the result didn't change. > ---------------------------------------------------- > freebsd-box# uname -a > FreeBSD freebsd-box 6.3-RELEASE FreeBSD 6.3-RELEASE > #0: Fri Apr 11 08:35:29 CEST 2008 > root@freebsd-box:/usr/obj/usr/src/sys/GENERIC i386 > ----------------------------------------------------- > freebsd-box# egrep -A1 '^200[78][0-9]{4}:' > /usr/src/UPDATING | head -n 30 > 20080118: > FreeBSD 6.3-RELEASE > -- > 20080118: FreeBSD-SA-08:01.pty, > FreeBSD-SA-08:02.libc > Fix issues which allow snooping on ptys. > [08:01] > -- > 20071129: FreeBSD-SA-07:09.random > Correct a random value disclosure in > random(4). > -- > 20071127: > The AT keyboard emulation of sunkbd(4) has > been turned on > -- > 20071024: > A breakage was introduced in libc and fixed > later. Make sure > -- > 20070806: > An incorrect field size in an ioctl struct for > if_bridge(4) has been > -- > 20070426: > The ABI breakage in sendmail(8)'s libmilter > has been repaired > -- > 20070411: > sendmail(8) has been updated to version > 8.14.1. Mail filters > -- > 20070115: > FreeBSD 6.2-RELEASE > ---------------------------------------------------- > freebsd-box# ls -alF /usr/src/sys/dev/wpi/ > ls: /usr/src/sys/dev/wpi/: No such file or directory > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > -- Sincerely, Andrey Kosachenko From besideinfo at yahoo.com Fri Apr 11 21:08:15 2008 From: besideinfo at yahoo.com (besideinfo) Date: Fri Apr 11 21:08:19 2008 Subject: Wireless on hp 6710b In-Reply-To: <47FFBD79.1040808@gmail.com> Message-ID: <330871.94187.qm@web43137.mail.sp1.yahoo.com> --- Andrey wrote: > O-o-ops... > > Sorry, I was so inattentive to details. > The wpi driver has not been MFC'ed to RELENG_6 yet > :(. > > It was clear from the very beginning. But I missed > the version of your > system (you've mentioned it at the first message!!!) > > For more details refer to CVS repository or just > take a glance here: > http://www.clearchain.com/wiki/Wpi > > I don't know why, but I was completely sure that wpi > has already been > backported to RELENG_6. > > > No problem at all. To be my first time with FreeBSD has been very interesting and very good learning experience. Also I had chance to see how help-full can be the FreeBSD community. As I understood the driver is include in FreeBSD 7,so I will download and install it. It will help to kill the time in this night shift. regards __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From besideinfo at yahoo.com Sat Apr 12 04:35:28 2008 From: besideinfo at yahoo.com (besideinfo) Date: Sat Apr 12 04:35:34 2008 Subject: Wireless on hp 6710b In-Reply-To: <330871.94187.qm@web43137.mail.sp1.yahoo.com> Message-ID: <801759.23146.qm@web43139.mail.sp1.yahoo.com> Hi, the installation of FreeBSD 7 solved the problem. Now the wireless card is working ;-) Thanks to everyone gretings Agostino __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From greenant at fastmail.fm Sun Apr 13 10:30:30 2008 From: greenant at fastmail.fm (Alberto Rizzi) Date: Sun Apr 13 10:30:34 2008 Subject: ThinkPad X61s functions keys In-Reply-To: <47F03BB8.7070803@langille.org> References: <47EFF8B4.8050709@fastmail.fm> <47F03BB8.7070803@langille.org> Message-ID: <4801E0B8.5070004@fastmail.fm> Dan Langille ha scritto: > > The paste was taken BEFORE I manually set events = 1. > > FWIW, the problem is solved. I will reply with details soon. Any news? From dan at langille.org Sun Apr 13 15:45:20 2008 From: dan at langille.org (Dan Langille) Date: Sun Apr 13 15:45:26 2008 Subject: ThinkPad X61s functions keys In-Reply-To: <47ED5BF7.2000109@fastmail.fm> References: <47ED5BF7.2000109@fastmail.fm> Message-ID: <48022A8F.3010703@langille.org> Elsewhere in this thread I had stated I'd solved the problem. I'm posting the details here. Alberto Rizzi wrote: > Dan Langille ha scritto: >> Hi, >> >> Running FreeBSD 7.0-RELEASE on a ThinkPad X61s. >> >> Some keys do not work: >> >> - volume adjustment >> - screen brightness (FN HOME, FN END) >> >> The keyboard light does work (FN-PgUp) as does >> Numeric Lock (FN ScrLk). >> >> What can I do to help diagnose the issue so we can get these >> functions working? >> > Have the same problem with a Thinkpad T61 > If you read man acpi_ibm there is a partial solution > > You have to load acpi_ibm at boot. Add > acpi_ibm_load="YES" > to /boot/loader.conf This is loaded: $ kldstat Id Refs Address Size Name 1 15 0xffffffff80100000 ac6c08 kernel 2 1 0xffffffff80bc7000 39138 linux.ko 3 1 0xffffffff80c01000 7108 if_tap.ko 4 1 0xffffffff80c09000 1a670 snd_hda.ko 5 2 0xffffffff80c24000 673b8 sound.ko 6 1 0xffffffff80c8c000 53d0 acpi_ibm.ko 7 1 0xffffffffb16e4000 4b61 i915.ko 8 1 0xffffffffb16e9000 d5d8 drm.ko > > Then activate event passing to devd. Add > dev.acpi_ibm.0.events=1 > to /etc/sysctl.conf I cannot get this set to 1 after boot: $ grep ibm /etc/sysctl.conf dev.acpi_ibm.0.events=1 $ sysctl dev.acpi_ibm.0.events dev.acpi_ibm.0.events: 0 Under these circumstances, the keys will not work. If I manually set the events flag: $ sudo sysctl dev.acpi_ibm.0.events=1 Password: dev.acpi_ibm.0.events: 0 -> 1 $ sysctl dev.acpi_ibm.0.events dev.acpi_ibm.0.events: 1 Then the brightness keys start working > > Then tell devd that you want to get events. Add > notify 10 { > match "system" "ACPI"; > match "subsystem" "IBM"; > action "/usr/local/sbin/acpi_oem_exec.sh $notify ibm"; > } This was the missing key. The last line needs a trailing ; Once I added that in, things started working. > > to /etc/devd.conf > > Now you have to create that script > ---------- > #!/bin/sh > NOTIFY=`echo $1` > ECHO="echo" > CALC="bc" > > case ${NOTIFY} in > 0x10) > LEVEL=`sysctl -n dev.acpi_ibm.0.lcd_brightness` > PERCENT=`${ECHO} "${LEVEL} + 1" | ${CALC}` > MESSAGE="brightness level ${PERCENT}" > sysctl dev.acpi_ibm.0.lcd_brightness=${PERCENT} > ;; > 0x11) > LEVEL=`sysctl -n dev.acpi_ibm.0.lcd_brightness` > PERCENT=`${ECHO} "${LEVEL} - 1" | ${CALC}` > MESSAGE="brightness level ${PERCENT}" > sysctl dev.acpi_ibm.0.lcd_brightness=${PERCENT} > ;; > *) > ;; > esac > echo `date` >> /tmp/prova > ${ECHO} ${LEVEL} ${NOTIFY} ${MESSAGE} >> /tmp/prova > exit 0 > > ------- > If you leave the last two debug line, with a tail -f /tmp/prova you can > check the events sent to devd. > > With this script you can change the brightness both under console and > under xorg but you are bound to 8 levels (0 - 7) > If you want 100 levels you can use xbacklight under xorg only and modify > the script to use xbacklight instead of sysctl > > Mute and volume keys don't send events to devd: I don't know why but if > I press mute it works and dev.acpi_ibm.0.mute becomes 1 > If I press volume up or down, dev.acpi_ibm.0.mute becomes 0 Using the Fn key and pressing the F1-F12 keys, I get the following log entrys in /tmp/prova: Sun Apr 13 11:39:48 EDT 2008 0x01 Sun Apr 13 11:39:48 EDT 2008 0x02 Sun Apr 13 11:39:49 EDT 2008 0x03 Sun Apr 13 11:39:50 EDT 2008 0x05 Sun Apr 13 11:39:50 EDT 2008 0x06 Sun Apr 13 11:39:50 EDT 2008 0x07 Sun Apr 13 11:39:54 EDT 2008 0x08 Sun Apr 13 11:39:54 EDT 2008 0x09 Sun Apr 13 11:39:55 EDT 2008 0x0b Sun Apr 13 11:39:55 EDT 2008 0x0c Note the following exceptions which can be observed from the above log entries: Fn-F4 - sleep: does not give any log entry Fn-F10 - unlabelled on the keyboard, gives no log entry Other Fn key results: SysReq - no log entry, no effect seen NumLk - no log entry but system goes into NumLock mode Pause - no log entry, no effect seen ThinkLight - works, and creates a log entry 0x12 Spacebar - create log entry 0x14 From dan at langille.org Sun Apr 13 17:19:34 2008 From: dan at langille.org (Dan Langille) Date: Sun Apr 13 17:19:38 2008 Subject: setting dev.acpi_ibm.0.events at boot time Message-ID: <480240AB.9080003@langille.org> I'm trying to set dev.acpi_ibm.0.events to 1. I'm failing. I can set it from the command line: $ sudo sysctl dev.acpi_ibm.0.events=1 Password: dev.acpi_ibm.0.events: 0 -> 1 $ sysctl dev.acpi_ibm.0.events dev.acpi_ibm.0.events: 1 This allows the special keys (screen brightness etc) to work on my ThinkPad X61s (see http://lists.freebsd.org/pipermail/freebsd-mobile/2008-March/010567.html). I have tried /etc/sysctl.conf: $ grep ibm /etc/sysctl.conf dev.acpi_ibm.0.events=1 and /boot/loader.conf: $ grep ibm /boot/loader.conf acpi_ibm_load="YES" dev.acpi_ibm.0.events="1" Neither of which result in the desired results. Clues? From smithi at nimnet.asn.au Mon Apr 14 04:21:58 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Mon Apr 14 04:22:06 2008 Subject: ThinkPad X61s functions keys In-Reply-To: <48022A8F.3010703@langille.org> Message-ID: On Sun, 13 Apr 2008, Dan Langille wrote: > Elsewhere in this thread I had stated I'd solved the problem. I'm > posting the details here. We've been waiting with bated breath :) > Alberto Rizzi wrote: > > Dan Langille ha scritto: > >> Hi, > >> > >> Running FreeBSD 7.0-RELEASE on a ThinkPad X61s. > >> > >> Some keys do not work: > >> > >> - volume adjustment > >> - screen brightness (FN HOME, FN END) > >> > >> The keyboard light does work (FN-PgUp) as does > >> Numeric Lock (FN ScrLk). > >> > >> What can I do to help diagnose the issue so we can get these > >> functions working? > >> > > Have the same problem with a Thinkpad T61 > > If you read man acpi_ibm there is a partial solution > > > > You have to load acpi_ibm at boot. Add > > acpi_ibm_load="YES" > > to /boot/loader.conf > > This is loaded: > > $ kldstat > Id Refs Address Size Name > 1 15 0xffffffff80100000 ac6c08 kernel > 2 1 0xffffffff80bc7000 39138 linux.ko > 3 1 0xffffffff80c01000 7108 if_tap.ko > 4 1 0xffffffff80c09000 1a670 snd_hda.ko > 5 2 0xffffffff80c24000 673b8 sound.ko > 6 1 0xffffffff80c8c000 53d0 acpi_ibm.ko > 7 1 0xffffffffb16e4000 4b61 i915.ko > 8 1 0xffffffffb16e9000 d5d8 drm.ko > > > > > > Then activate event passing to devd. Add > > dev.acpi_ibm.0.events=1 > > to /etc/sysctl.conf > > I cannot get this set to 1 after boot: > > $ grep ibm /etc/sysctl.conf > dev.acpi_ibm.0.events=1 Strange if that doesn't work. Can you check your /var/log/console.log (assuming you've got 'console.info /var/log/console.log' in syslog.conf) which should show the transition, or at least the attempt, eg: Apr 1 02:51:32 paqi kernel: vfs.usermount: Apr 1 02:51:32 paqi kernel: 0 Apr 1 02:51:32 paqi kernel: -> Apr 1 02:51:32 paqi kernel: 1 Apr 1 02:51:32 paqi kernel: Apr 1 02:51:32 paqi kernel: hw.snd.verbose: Apr 1 02:51:32 paqi kernel: 1 Apr 1 02:51:32 paqi kernel: -> Apr 1 02:51:32 paqi kernel: 2 > $ sysctl dev.acpi_ibm.0.events > dev.acpi_ibm.0.events: 0 > > Under these circumstances, the keys will not work. If I manually set > the events flag: > > $ sudo sysctl dev.acpi_ibm.0.events=1 > Password: > dev.acpi_ibm.0.events: 0 -> 1 > $ sysctl dev.acpi_ibm.0.events > dev.acpi_ibm.0.events: 1 > > > Then the brightness keys start working You could, if maybe sysctl.conf is being run too early (?), try adding 'sysctl dev.acpi_ibm.0.events=1' to /etc/rc.local, which, as I recall, also reports into console.log > > Then tell devd that you want to get events. Add > > notify 10 { > > match "system" "ACPI"; > > match "subsystem" "IBM"; > > action "/usr/local/sbin/acpi_oem_exec.sh $notify ibm"; > > } > > This was the missing key. The last line needs a trailing ; > > Once I added that in, things started working. Fussy, ain't it. > > to /etc/devd.conf > > > > Now you have to create that script > > ---------- > > #!/bin/sh > > NOTIFY=`echo $1` > > ECHO="echo" > > CALC="bc" > > > > case ${NOTIFY} in > > 0x10) > > LEVEL=`sysctl -n dev.acpi_ibm.0.lcd_brightness` > > PERCENT=`${ECHO} "${LEVEL} + 1" | ${CALC}` > > MESSAGE="brightness level ${PERCENT}" > > sysctl dev.acpi_ibm.0.lcd_brightness=${PERCENT} > > ;; > > 0x11) > > LEVEL=`sysctl -n dev.acpi_ibm.0.lcd_brightness` > > PERCENT=`${ECHO} "${LEVEL} - 1" | ${CALC}` > > MESSAGE="brightness level ${PERCENT}" > > sysctl dev.acpi_ibm.0.lcd_brightness=${PERCENT} > > ;; > > *) > > ;; > > esac > > echo `date` >> /tmp/prova > > ${ECHO} ${LEVEL} ${NOTIFY} ${MESSAGE} >> /tmp/prova > > exit 0 > > > > ------- > > If you leave the last two debug line, with a tail -f /tmp/prova you can > > check the events sent to devd. > > > > With this script you can change the brightness both under console and > > under xorg but you are bound to 8 levels (0 - 7) > > If you want 100 levels you can use xbacklight under xorg only and modify > > the script to use xbacklight instead of sysctl > > > > Mute and volume keys don't send events to devd: I don't know why but if > > I press mute it works and dev.acpi_ibm.0.mute becomes 1 > > If I press volume up or down, dev.acpi_ibm.0.mute becomes 0 Are the bits for these keys set in .availmask, or posted to .eventmask? > Using the Fn key and pressing the F1-F12 keys, I get the following log > entrys in /tmp/prova: > Sun Apr 13 11:39:48 EDT 2008 > 0x01 > Sun Apr 13 11:39:48 EDT 2008 > 0x02 > Sun Apr 13 11:39:49 EDT 2008 > 0x03 > Sun Apr 13 11:39:50 EDT 2008 > 0x05 > Sun Apr 13 11:39:50 EDT 2008 > 0x06 > Sun Apr 13 11:39:50 EDT 2008 > 0x07 > Sun Apr 13 11:39:54 EDT 2008 > 0x08 > Sun Apr 13 11:39:54 EDT 2008 > 0x09 > Sun Apr 13 11:39:55 EDT 2008 > 0x0b > Sun Apr 13 11:39:55 EDT 2008 > 0x0c > > > Note the following exceptions which can be observed from the above log > entries: > > Fn-F4 - sleep: does not give any log entry > Fn-F10 - unlabelled on the keyboard, gives no log entry Does Fn-F4 (still?) act as sleep (suspend-to-RAM)? ie does/did STR work on your X61s, and does dev.acpi_ibm.0.events=1 affect that at all? You might like to compare your results with Beto's Z60m at: http://lists.freebsd.org/mailman/htdig/freebsd-mobile/2006-August/008959.html and also his earlier reference: http://lists.freebsd.org/pipermail/freebsd-mobile/2006-August/008948.html where a) he gets to use Fn-F4 for a custom sleep script, b) also found that Fn-F10 does nothing, but c) gets events from volume and mute keys. > Other Fn key results: > > SysReq - no log entry, no effect seen > NumLk - no log entry but system goes into NumLock mode > Pause - no log entry, no effect seen On my T23, Pause does nothing in X, but (same as NumLk/ScrollLock key pressed without Fn) works as the scroll lock in a vty. Also on mine, Fn-F7 switches between LCD/Monitor/both. > ThinkLight - works, and creates a log entry 0x12 > Spacebar - create log entry 0x14 Weird about the sysctl not getting set from sysctl.conf though .. cheers, Ian From gamato at users.sf.net Mon Apr 14 08:18:04 2008 From: gamato at users.sf.net (mato) Date: Mon Apr 14 08:18:08 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: References: Message-ID: <48031338.5050801@users.sf.net> Ian Smith wrote: > On Mon, 7 Apr 2008, martinko wrote: > > Lars Engels wrote: > > > Quoting martinko : > > >> Hi Lars, > > >> > > >> sysutils/nbosd looks very nice and rather useful, thanks! :-) > > >> > > >> However, I can think of the following: > > >> > > >> There are 2 important/interesting information missing: > > >> - remaining run-time in hours:minutes when running on battery > > >> - CPU temperature (especially on laptops) > > > > > > Good idea, it should be no problem to use sysctl to get those values. > > > > > >> Also, it might be quite useful to render battery related info in red > > >> colour once battery charge drops below some (configurable) limit when > > >> not running on AC power. > > >> > > >> The last but not least important is this -- nbosd shows you info on > > >> demand only. I find that most often I forget about my battery running > > >> flat and thus nbosd wouldn't help. Any idea how to deal with it ? > > > > > > nbosd was designed to show the value on demand. I have a keyboard > > > shortcut which shows me the OSD whenever I need it. > > > But the shortcut doesn't work in every case e.g. when playing > > > fullscreen games. So I taught nbosd to work together with devd and now > > > nbosd has an option to run as a daemon and only shows up when the > > > battery percentage falls below a user-defined value. > > > It still has some rough corners and the code needs to be cleaned up > > > that's why I haven't committed the new version. > > > I hope that my (very limited atm :-( ) time allows me get it finished, > > > soon. > > > > > > > Hi Lars, > > > > Remaining run-time (hours:minutes) could be next to the percentage value. > > I'm not sure about the temperature, though. > > > > I've set up a keyboard shotcut too (in WMaker) and it works great. > > However, sometimes I forget I'm running on battery and only find out > > when my laptop dies abruptly. That's why I'm trying to figure out how > > best to prevent such situations. > > > > And what do you say about my suggestion to render battery life text and > > graphics in red when running on DC and too low ? Would it be possible ? > > You may also like to have a look at sysutils/asapm which I've been using > for years to good effect in KDE. Despite the name, and the initial > blurb in pkg_descr, it works fine (better, actually) with ACPI, as > detailed in the manual. It's also fully configurable regarding display > colours etc, and if the remaining runtime isn't directly available, it > can monitor state of charge over time to provide pretty good estimates, > along with configurable setpoints for 'warning' and 'alarm' colours. I > can't say whether it works on amd64 though .. > > On later (i386) machines I tend to use gkrellm which includes CPU temp, > speed and much more, but again I don't know if it works with amd64. > > hth, Ian > > Ian, thanks! :-) I've been using wmbsdbatt but it isn't configurable at all and often I just didn't notice my battery gone flat. Now I've switched to asapm which provides better visual attention (battery turning red) and more importantly I could configure it to produce notifications via notify-send and xmessage, so it's unlikely I'll miss my battery running flat. :-)) Cheers, Martin From barner at FreeBSD.org Mon Apr 14 19:25:55 2008 From: barner at FreeBSD.org (Simon Barner) Date: Mon Apr 14 19:26:04 2008 Subject: fprint (finger print sensor framework) port ready for testing Message-ID: <20080414180740.GA1050@dose.local.invalid> Hi, I did a port [2] of the fprint finger print sensor framework [1] and would like to receive some feedback before I commit it. It comes with a PAM module for finger print based authentication, a graphical (fprint_demo) and a console (pam_fprint_enroll) application for finger print enrollment. I did my tests with the UPEK sensor found in Lenovo's T61. Simon (M'fup2 ports@) [1] http://www.reactivated.net/fprint/wiki/Main_Page [2] http://home.leo.org/~barner/freebsd/fprint.tar.gz -- Best regards / Viele Gr??e, barner@FreeBSD.org Simon Barner barner@gmx.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080414/bdf4fc67/attachment.pgp From amistry at am-productions.biz Mon Apr 14 21:20:38 2008 From: amistry at am-productions.biz (Anish Mistry) Date: Mon Apr 14 21:21:04 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <20080414180740.GA1050@dose.local.invalid> References: <20080414180740.GA1050@dose.local.invalid> Message-ID: <200804141645.59915.amistry@am-productions.biz> On Monday 14 April 2008, Simon Barner wrote: > Hi, > > I did a port [2] of the fprint finger print sensor framework [1] > and would like to receive some feedback before I commit it. > > It comes with a PAM module for finger print based authentication, a > graphical (fprint_demo) and a console (pam_fprint_enroll) application > for finger print enrollment. > > I did my tests with the UPEK sensor found in Lenovo's T61. > > Simon > > (M'fup2 ports@) > > [1] http://www.reactivated.net/fprint/wiki/Main_Page > [2] http://home.leo.org/~barner/freebsd/fprint.tar.gz Just tested fprint_demo on my Fujitsu P8010 and it works! Thanks for porting it. -- Anish Mistry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part. Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080414/41361bd4/attachment.pgp From lme at FreeBSD.org Mon Apr 14 22:06:43 2008 From: lme at FreeBSD.org (Lars Engels) Date: Mon Apr 14 22:06:50 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: <47FA7351.4030601@users.sf.net> References: <0319208F-8098-4EAA-B3DA-22C6FE1C02DD@langille.org> <20080326155507.wiubhspc04ok440g@0x20.net> <47F8AD88.2010406@users.sf.net> <20080407133354.djlrjmnm04ks0www@0x20.net> <47FA7351.4030601@users.sf.net> Message-ID: <20080414220641.GK50049@e.0x20.net> On Mon, Apr 07, 2008 at 09:17:37PM +0200, martinko wrote: > Lars Engels wrote: > >Quoting martinko : > >>Hi Lars, > >> > >>sysutils/nbosd looks very nice and rather useful, thanks! :-) > >> > >>However, I can think of the following: > >> > >>There are 2 important/interesting information missing: > >>- remaining run-time in hours:minutes when running on battery > >>- CPU temperature (especially on laptops) > > > >Good idea, it should be no problem to use sysctl to get those values. > > > >>Also, it might be quite useful to render battery related info in red > >>colour once battery charge drops below some (configurable) limit when > >>not running on AC power. > >> > >>The last but not least important is this -- nbosd shows you info on > >>demand only. I find that most often I forget about my battery running > >>flat and thus nbosd wouldn't help. Any idea how to deal with it ? > > > >nbosd was designed to show the value on demand. I have a keyboard shortcut which shows me the > >OSD whenever I need it. > >But the shortcut doesn't work in every case e.g. when playing fullscreen games. So I taught > >nbosd to work together with devd and now nbosd has an option to run as a daemon and only shows > >up when the battery percentage falls below a user-defined value. > >It still has some rough corners and the code needs to be cleaned up that's why I haven't > >committed the new version. > >I hope that my (very limited atm :-( ) time allows me get it finished, soon. > > > > Hi Lars, > > Remaining run-time (hours:minutes) could be next to the percentage value. > I'm not sure about the temperature, though. > > I've set up a keyboard shotcut too (in WMaker) and it works great. > However, sometimes I forget I'm running on battery and only find out when my laptop dies > abruptly. That's why I'm trying to figure out how best to prevent such situations. > > And what do you say about my suggestion to render battery life text and graphics in red when > running on DC and too low ? Would it be possible ? Hi Martin, somehow I didn't see you mail until now... I just worked a bit on nbosd and it should fulfill your needs now: A -d switch was added to run it as a daemon. You can give it an alarm threshold with -a and the osd will pop up (in red ;-) ) when the current battery level is below that threshold. Additionally the remaining battery time is displayed. I haven't committed the new version yet. I'd like to have one or two testers before: http://bsd-geek.de/FreeBSD/distfiles/nbosd-0.5.0.tar.gz So if you would like to try it, please give a feedback on it. Lars -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080414/3ee1cf51/attachment.pgp From freebsd at meijome.net Tue Apr 15 07:05:38 2008 From: freebsd at meijome.net (Norberto Meijome) Date: Tue Apr 15 07:05:42 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <480240AB.9080003@langille.org> References: <480240AB.9080003@langille.org> Message-ID: <20080415163843.1f899be5@meijome.net> On Sun, 13 Apr 2008 13:19:39 -0400 Dan Langille wrote: > I'm trying to set dev.acpi_ibm.0.events to 1. I'm failing. I can set > it from the command line: [...] > I have tried /etc/sysctl.conf: > > $ grep ibm /etc/sysctl.conf > dev.acpi_ibm.0.events=1 > > and /boot/loader.conf: > > $ grep ibm /boot/loader.conf > acpi_ibm_load="YES" > dev.acpi_ibm.0.events="1" > > Neither of which result in the desired results. hi Dan, sysctl.conf works ok for me: # Needed for custom ACPI control # This will pass ACPI events to devd after acpi_ibm. # Custom devd config can be found in /usr/local/etc/devd dev.acpi_ibm.0.events=1 BUT i clearly remember that a few times, after rebuilding kernel (or world?) events wouldn't be set, as it is the case with you. It hasn't happened for a while..and I don't remember if it was on 6 or 7... it just got fixed by building kernel again, i think... _________________________ {Beto|Norberto|Numard} Meijome "All that is necessary for the triumph of evil is that good men do nothing." Edmund Burke I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From tevans.uk at googlemail.com Tue Apr 15 09:20:59 2008 From: tevans.uk at googlemail.com (Tom Evans) Date: Tue Apr 15 09:21:03 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <20080414180740.GA1050@dose.local.invalid> References: <20080414180740.GA1050@dose.local.invalid> Message-ID: <1208249813.8904.34.camel@localhost> On Mon, 2008-04-14 at 20:07 +0200, Simon Barner wrote: > Hi, > > I did a port [2] of the fprint finger print sensor framework [1] > and would like to receive some feedback before I commit it. > > It comes with a PAM module for finger print based authentication, a > graphical (fprint_demo) and a console (pam_fprint_enroll) application > for finger print enrollment. > > I did my tests with the UPEK sensor found in Lenovo's T61. > > Simon > > (M'fup2 ports@) > > [1] http://www.reactivated.net/fprint/wiki/Main_Page > [2] http://home.leo.org/~barner/freebsd/fprint.tar.gz > This is fantastic! People have always been asking me 'so does the fingerprint sensor work?' when they find out I run FreeBSD on my laptop - and now I can tell them it does! Just tested with fprint_demo, but successfully enrolled and verified my fingerprints no problem, using an HP nc6320 and the aes2501 sensor. Cheers Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080415/b379da7c/attachment.pgp From dirkx at webweaving.org Tue Apr 15 10:00:33 2008 From: dirkx at webweaving.org (Dirk-Willem van Gulik) Date: Tue Apr 15 10:00:45 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <20080414180740.GA1050@dose.local.invalid> References: <20080414180740.GA1050@dose.local.invalid> Message-ID: <4714B277-3EEF-4AE6-A54A-CF8DCAD2C5C7@webweaving.org> On Apr 14, 2008, at 8:07 PM, Simon Barner wrote: > I did a port [2] of the fprint finger print sensor framework [1] > and would like to receive some feedback before I commit it. > > It comes with a PAM module for finger print based authentication, a > graphical (fprint_demo) and a console (pam_fprint_enroll) application > for finger print enrollment. > > I did my tests with the UPEK sensor found in Lenovo's T61. Well done ! Works with the VAIO fps just fine. Dw From vova at fbsd.ru Tue Apr 15 11:21:21 2008 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Tue Apr 15 11:21:32 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <20080414180740.GA1050@dose.local.invalid> References: <20080414180740.GA1050@dose.local.invalid> Message-ID: <1208256383.1513.6.camel@localhost> On Mon, 2008-04-14 at 20:07 +0200, Simon Barner wrote: > Hi, > > I did a port [2] of the fprint finger print sensor framework [1] > and would like to receive some feedback before I commit it. > > It comes with a PAM module for finger print based authentication, a > graphical (fprint_demo) and a console (pam_fprint_enroll) application > for finger print enrollment. > > I did my tests with the UPEK sensor found in Lenovo's T61. Cool, it works for me, even pam module. As I understand, pam module requires user name first. So there no way to make gdm/kdm/*dm just scan image, find apropriate user and login him ? ?Have you seen/reviewed security/bioapi and security/bsp_upektfmess (later works only on RELENG_6 now) ? Looks like fprint ports are introduce one new bioapi ? > Simon > > (M'fup2 ports@) > > [1] http://www.reactivated.net/fprint/wiki/Main_Page > [2] http://home.leo.org/~barner/freebsd/fprint.tar.gz > -- Vladimir B. Grebenschikov vova@fbsd.ru From dan at langille.org Tue Apr 15 13:02:52 2008 From: dan at langille.org (Dan Langille) Date: Tue Apr 15 13:02:55 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <20080415163843.1f899be5@meijome.net> References: <480240AB.9080003@langille.org> <20080415163843.1f899be5@meijome.net> Message-ID: <4804A739.2090403@langille.org> Norberto Meijome wrote: > On Sun, 13 Apr 2008 13:19:39 -0400 > Dan Langille wrote: > >> I'm trying to set dev.acpi_ibm.0.events to 1. I'm failing. I can set >> it from the command line: > [...] >> I have tried /etc/sysctl.conf: >> >> $ grep ibm /etc/sysctl.conf >> dev.acpi_ibm.0.events=1 >> >> and /boot/loader.conf: >> >> $ grep ibm /boot/loader.conf >> acpi_ibm_load="YES" >> dev.acpi_ibm.0.events="1" >> >> Neither of which result in the desired results. > > hi Dan, > > sysctl.conf works ok for me: > > # Needed for custom ACPI control > # This will pass ACPI events to devd after acpi_ibm. > # Custom devd config can be found in /usr/local/etc/devd > dev.acpi_ibm.0.events=1 > > BUT i clearly remember that a few times, after rebuilding kernel (or world?) > events wouldn't be set, as it is the case with you. It hasn't happened for a > while..and I don't remember if it was on 6 or 7... > > it just got fixed by building kernel again, i think... No new kernel here. But it works no. Not sure how or why, but it's working now. -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ From freebsd at meijome.net Tue Apr 15 13:29:32 2008 From: freebsd at meijome.net (Norberto Meijome) Date: Tue Apr 15 13:29:39 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <4804A739.2090403@langille.org> References: <480240AB.9080003@langille.org> <20080415163843.1f899be5@meijome.net> <4804A739.2090403@langille.org> Message-ID: <20080415232922.2421ddfb@meijome.net> On Tue, 15 Apr 2008 09:01:45 -0400 Dan Langille wrote: > No new kernel here. But it works no. Not sure how or why, but it's > working now. yeah, the same weird thing that happened to me... i seem to remember now that i thought it was related to new kernel, i reverted and still had the same problem..then it was gone.... gremlins. :P _________________________ {Beto|Norberto|Numard} Meijome Real Programmers don't comment their code. If it was hard to write, it should be hard to understand and even harder to modify. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From freebsd at meijome.net Tue Apr 15 13:57:49 2008 From: freebsd at meijome.net (Norberto Meijome) Date: Tue Apr 15 13:59:35 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <20080414180740.GA1050@dose.local.invalid> References: <20080414180740.GA1050@dose.local.invalid> Message-ID: <20080415235732.70f0d395@ayiin.octantis.com.au> On Mon, 14 Apr 2008 20:07:40 +0200 Simon Barner wrote: > Hi, > > I did a port [2] of the fprint finger print sensor framework [1] > and would like to receive some feedback before I commit it. > > It comes with a PAM module for finger print based authentication, a > graphical (fprint_demo) and a console (pam_fprint_enroll) application > for finger print enrollment. > > I did my tests with the UPEK sensor found in Lenovo's T61. > > Simon > > (M'fup2 ports@) > > [1] http://www.reactivated.net/fprint/wiki/Main_Page > [2] http://home.leo.org/~barner/freebsd/fprint.tar.gz > Hi Simon, I installed both packages. Used wheel instead of operators for devfs (I am member of wheel). running as root made it work great :) I have a Lenovo Thinkpad z60m, upekts driver. The details : FreeBSD ayiin.octantis.com.au 7.0-STABLE FreeBSD 7.0-STABLE #43: Mon Apr 14 11:50:52 EST 2008 root@ayiin.octantis.com.au:/usr/obj/usr/src/sys/AYIIN i386 $ sudo usbdevs -v -d [...] Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub2 port 1 powered port 2 addr 2: full speed, power 100 mA, config 1, Biometric Coprocessor(0x2016), STMicroelectronics(0x0483), rev 0.01 ugen0 [...] dmesg shows : Apr 14 22:17:08 ayiin kernel: ugen0: on uhub2 Best regards, B _________________________ {Beto|Norberto|Numard} Meijome "A dream you dream together is reality." John Lennon I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From outbackdingo at gmail.com Tue Apr 15 15:23:08 2008 From: outbackdingo at gmail.com (Outback Dingo) Date: Tue Apr 15 15:23:13 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <1208256383.1513.6.camel@localhost> References: <20080414180740.GA1050@dose.local.invalid> <1208256383.1513.6.camel@localhost> Message-ID: <5635aa0d0804150751n3f89e885mdac8fb3077cdc331@mail.gmail.com> pam_fprint works (see below) but when i try to run the fprint demo i get STATUS: No Devices Found pam_fprint_enroll -f 7 This program will enroll your finger, unconditionally overwriting any selected print that was enrolled previously. If you want to continue, press enter, otherwise hit Ctrl+C Found device claimed by UPEK TouchStrip driver Opened device. It's now time to enroll your finger. You will need to successfully scan your Right Index Finger 3 times to complete the process. Scan your finger now. upekts:error [read_msg] non-zero bytes in cmd response upekts:error [read_msg28] expected response, got -1 seq=40 Enroll stage passed. Yay! Scan your finger now. Enroll stage passed. Yay! Scan your finger now. Enroll complete! Enrollment completed! From barner at FreeBSD.org Tue Apr 15 19:38:38 2008 From: barner at FreeBSD.org (Simon Barner) Date: Tue Apr 15 19:38:44 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <1208256383.1513.6.camel@localhost> References: <20080414180740.GA1050@dose.local.invalid> <1208256383.1513.6.camel@localhost> Message-ID: <20080415193836.GA1956@dose.local.invalid> Vladimir Grebenschikov wrote: > As I understand, pam module requires user name first. > So there no way to make gdm/kdm/*dm just scan image, find apropriate > user and login him ? As far as I can tell, it currently is not supported, but somebody seems to work on it: http://www.mail-archive.com/fprint@reactivated.net/msg00471.html > > ???Have you seen/reviewed security/bioapi and security/bsp_upektfmess > (later works only on RELENG_6 now) ? Yes. In the mean time, there even is a binary of the UPEK driver for FreeBSD 7 i386, but the pam module did not work for me. > > Looks like fprint ports are introduce one new bioapi ? Yes, but at it seems, the developers deliberated well about it: http://www.reactivated.net/fprint/wiki/FAQ#Why_no_BioAPI.3F -- Best regards / Viele Gr??e, barner@FreeBSD.org Simon Barner barner@gmx.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080415/f85630d2/attachment.pgp From barner at FreeBSD.org Tue Apr 15 19:43:49 2008 From: barner at FreeBSD.org (Simon Barner) Date: Tue Apr 15 19:43:57 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <5635aa0d0804150751n3f89e885mdac8fb3077cdc331@mail.gmail.com> References: <20080414180740.GA1050@dose.local.invalid> <1208256383.1513.6.camel@localhost> <5635aa0d0804150751n3f89e885mdac8fb3077cdc331@mail.gmail.com> Message-ID: <20080415194347.GB1956@dose.local.invalid> Outback Dingo wrote: > pam_fprint works (see below) but when i try to run the fprint demo i get > > STATUS: No Devices Found Are you sure you have r/w access to the sensor's USB device? > > pam_fprint_enroll -f 7 > This program will enroll your finger, unconditionally overwriting any selected > print that was enrolled previously. If you want to continue, press enter, > otherwise hit Ctrl+C > > Found device claimed by UPEK TouchStrip driver > Opened device. It's now time to enroll your finger. > > You will need to successfully scan your Right Index Finger 3 times to complete > the process. > > Scan your finger now. > upekts:error [read_msg] non-zero bytes in cmd response > upekts:error [read_msg28] expected response, got -1 seq=40 Something seems to go wrong. I have never seenn this error message. Which sensor are you using? Can you send me the output of `usbdevs -vd' in a private mail please? -- Best regards / Viele Gr??e, barner@FreeBSD.org Simon Barner barner@gmx.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080415/00fe1dbe/attachment.pgp From fli at shapeshifter.se Tue Apr 15 20:14:07 2008 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Tue Apr 15 20:14:20 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <20080415193836.GA1956@dose.local.invalid> References: <20080414180740.GA1050@dose.local.invalid> <1208256383.1513.6.camel@localhost> <20080415193836.GA1956@dose.local.invalid> Message-ID: <480508C3.8070609@shapeshifter.se> Simon Barner wrote: > Vladimir Grebenschikov wrote: >> ???Have you seen/reviewed security/bioapi and security/bsp_upektfmess >> (later works only on RELENG_6 now) ? > > Yes. In the mean time, there even is a binary of the UPEK driver for > FreeBSD 7 i386, but the pam module did not work for me. A new binary has been re-rolled which takes care of the Undefined symbol errors in the first one. It works with PAM as well. The updated port can be found in ports/122768 However, if fprint suites your needs I would recommend using it instead. Another possibility would be to create BioAPI modules based on the reversed engineered code from fprint. Fredrik Lindberg From takash-i at sophia.ac.jp Wed Apr 16 03:47:10 2008 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Wed Apr 16 03:47:13 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <480240AB.9080003@langille.org> References: <480240AB.9080003@langille.org> Message-ID: <480576F3.3090709@sophia.ac.jp> Hi friends, I have a similar probrem with 7.0R on X61s. "dev.acpi_ibm.0.lcd_brightness=4" in sysctl.conf does NOT work with xorg(gdm). I think changing VT reset it. > I'm trying to set dev.acpi_ibm.0.events to 1. I'm failing. I can set > it from the command line: > > $ sudo sysctl dev.acpi_ibm.0.events=1 > Password: > dev.acpi_ibm.0.events: 0 -> 1 > > $ sysctl dev.acpi_ibm.0.events > dev.acpi_ibm.0.events: 1 > > > This allows the special keys (screen brightness etc) to work on my > ThinkPad X61s (see > http://lists.freebsd.org/pipermail/freebsd-mobile/2008-March/010567.html). > > I have tried /etc/sysctl.conf: > > $ grep ibm /etc/sysctl.conf > dev.acpi_ibm.0.events=1 > > and /boot/loader.conf: > > $ grep ibm /boot/loader.conf > acpi_ibm_load="YES" > dev.acpi_ibm.0.events="1" > > Neither of which result in the desired results. > > Clues? > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" -- Takashi Inoue From smithi at nimnet.asn.au Wed Apr 16 05:21:53 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Wed Apr 16 05:21:56 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: <48031338.5050801@users.sf.net> Message-ID: On Mon, 14 Apr 2008, mato wrote: > Ian Smith wrote: [..] > > You may also like to have a look at sysutils/asapm which I've been using > > for years to good effect in KDE. Despite the name, and the initial > > blurb in pkg_descr, it works fine (better, actually) with ACPI, as > > detailed in the manual. It's also fully configurable regarding display > > colours etc, and if the remaining runtime isn't directly available, it > > can monitor state of charge over time to provide pretty good estimates, > > along with configurable setpoints for 'warning' and 'alarm' colours. I > > can't say whether it works on amd64 though .. > > > > On later (i386) machines I tend to use gkrellm which includes CPU temp, > > speed and much more, but again I don't know if it works with amd64. > Ian, thanks! :-) My pleasure Martin .. I've not heard of anyone else running it before :) > I've been using wmbsdbatt but it isn't configurable at all and often I > just didn't notice my battery gone flat. Now I've switched to asapm > which provides better visual attention (battery turning red) and more > importantly I could configure it to produce notifications via > notify-send and xmessage, so it's unlikely I'll miss my battery running > flat. :-)) Yeah, good old-fashioned X configuration. I use apmd notifications on this old 300MHz 800x600 beast for also good old-fashioned /dev/speaker tunes for battery warnings, but haven't yet explored xmessage - thanks. FWIW, I've also long used sysutils/ascpu as a 60sec visual load monitor, matching asapm's 'look', res. size and low cpu usage. At ~7days uptime: 3680 smithi 8 0 2344K 448K nanslp 44:06 0.00% 0.00% asapm 3681 smithi 8 0 2564K 448K nanslp 41:53 0.00% 0.00% ascpu 3514 root 96 0 1280K 264K select 36:32 0.00% 0.00% moused cheers, Ian From barner at FreeBSD.org Wed Apr 16 05:36:51 2008 From: barner at FreeBSD.org (Simon Barner) Date: Wed Apr 16 05:36:56 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <480508C3.8070609@shapeshifter.se> References: <20080414180740.GA1050@dose.local.invalid> <1208256383.1513.6.camel@localhost> <20080415193836.GA1956@dose.local.invalid> <480508C3.8070609@shapeshifter.se> Message-ID: <20080416053649.GA1339@dose.local.invalid> Fredrik Lindberg wrote: > Simon Barner wrote: >> Vladimir Grebenschikov wrote: >>> ???Have you seen/reviewed security/bioapi and security/bsp_upektfmess >>> (later works only on RELENG_6 now) ? >> Yes. In the mean time, there even is a binary of the UPEK driver for >> FreeBSD 7 i386, but the pam module did not work for me. > > A new binary has been re-rolled which takes care of the Undefined > symbol errors in the first one. It works with PAM as well. > The updated port can be found in ports/122768 Ok, good to know, I'll take care of your PR. > > However, if fprint suites your needs I would recommend using it instead. > Another possibility would be to create BioAPI modules based on the > reversed engineered code from fprint. The latter option might be interesting. However, the fprint developers plan more advanced authentication (and also identification) in the future (see link in my mail to Vladimir Grebenschikov earlier in this thread). -- Best regards / Viele Gr??e, barner@FreeBSD.org Simon Barner barner@gmx.de -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080416/9df0fe7a/attachment.pgp From outbackdingo at gmail.com Wed Apr 16 06:06:44 2008 From: outbackdingo at gmail.com (Outback Dingo) Date: Wed Apr 16 06:06:48 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <20080415194347.GB1956@dose.local.invalid> References: <20080414180740.GA1050@dose.local.invalid> <1208256383.1513.6.camel@localhost> <5635aa0d0804150751n3f89e885mdac8fb3077cdc331@mail.gmail.com> <20080415194347.GB1956@dose.local.invalid> Message-ID: <5635aa0d0804152306s170586c3ia4410cb766a2f196@mail.gmail.com> Yupp I even set the permissions 777 and added the user i tested to group operator.... still no joy ive used the upek port no problems even with GDM. the "root" user works great, but regular users cant even register ls -al /dev/ugen* crw-rw-rw- 1 root operator 0, 84 Apr 15 14:14 /dev/ugen0 crw-rw-rw- 1 root operator 0, 85 Apr 15 14:14 /dev/ugen0.1 crw-rw-rw- 1 root operator 0, 86 Apr 15 14:14 /dev/ugen0.2 crw-rw-rw- 1 root operator 0, 87 Apr 15 14:14 /dev/ugen0.3 crw-rw-rw- 1 root operator 0, 88 Apr 15 14:14 /dev/ugen0.4 crwxrwxrwx 1 root operator 0, 89 Apr 15 14:14 /dev/ugen1 crwxrwxrwx 1 root operator 0, 90 Apr 15 14:14 /dev/ugen1.1 crwxrwxrwx 1 root operator 0, 91 Apr 16 01:34 /dev/ugen1.2 crwxrwxrwx 1 root operator 0, 92 Apr 15 14:14 /dev/ugen1.3 usbdevs -vd Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub0 port 1 powered port 2 addr 2: low speed, power 98 mA, config 1, USB Receiver(0xc521), Logitech(0x046d), rev 57.00 ums0 uhid0 Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub2 port 1 addr 2: full speed, self powered, config 1, BCM2045B(0x2110), Broadcom Corp(0x0a5c), rev 1.00 ugen0 port 2 addr 3: full speed, power 100 mA, config 1, Biometric Coprocessor(0x2016), STMicroelectronics(0x0483), rev 0.01 ugen1 Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub3 port 1 powered port 2 powered Controller /dev/usb4: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub4 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered port 7 powered port 8 powered On Wed, Apr 16, 2008 at 2:43 AM, Simon Barner wrote: > Outback Dingo wrote: > > pam_fprint works (see below) but when i try to run the fprint demo i get > > > > STATUS: No Devices Found > > Are you sure you have r/w access to the sensor's USB device? > > > > pam_fprint_enroll -f 7 > > This program will enroll your finger, unconditionally overwriting any > selected > > print that was enrolled previously. If you want to continue, press > enter, > > otherwise hit Ctrl+C > > > > Found device claimed by UPEK TouchStrip driver > > Opened device. It's now time to enroll your finger. > > > > You will need to successfully scan your Right Index Finger 3 times to > complete > > the process. > > > > Scan your finger now. > > upekts:error [read_msg] non-zero bytes in cmd response > > upekts:error [read_msg28] expected response, got -1 seq=40 > > Something seems to go wrong. I have never seenn this error message. > > Which sensor are you using? Can you send me the output of `usbdevs -vd' > in a private mail please? > > -- > Best regards / Viele Gr??e, barner@FreeBSD.org > Simon Barner barner@gmx.de > From andrey.kosachenko at gmail.com Wed Apr 16 07:02:17 2008 From: andrey.kosachenko at gmail.com (Andrey) Date: Wed Apr 16 07:02:23 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <20080414180740.GA1050@dose.local.invalid> References: <20080414180740.GA1050@dose.local.invalid> Message-ID: <4805A461.6040704@gmail.com> Hi, It looks like it works on my HP machine. (HP 6710b, AuthenTec Fingerprint device) # dmesg | egrep 'ugen' ugen0: # usbdevs -dv ... Controller /dev/usb3: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub3 port 1 powered port 2 addr 2: full speed, power 100 mA, config 1, Fingerprint Sensor(0x2580), vendor 0x08ff(0x08ff), rev 6.23 ugen0 ... Great work! Thanks. Simon Barner wrote: > Hi, > > I did a port [2] of the fprint finger print sensor framework [1] > and would like to receive some feedback before I commit it. > > It comes with a PAM module for finger print based authentication, a > graphical (fprint_demo) and a console (pam_fprint_enroll) application > for finger print enrollment. > > I did my tests with the UPEK sensor found in Lenovo's T61. > > Simon > > (M'fup2 ports@) > > [1] http://www.reactivated.net/fprint/wiki/Main_Page > [2] http://home.leo.org/~barner/freebsd/fprint.tar.gz > -- Sincerely, Andrey Kosachenko From greenant at fastmail.fm Wed Apr 16 08:05:43 2008 From: greenant at fastmail.fm (Alberto Rizzi) Date: Wed Apr 16 08:05:46 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <480576F3.3090709@sophia.ac.jp> References: <480240AB.9080003@langille.org> <480576F3.3090709@sophia.ac.jp> Message-ID: <4805B357.7020901@fastmail.fm> Takashi Inoue ha scritto: > Hi friends, > > I have a similar probrem with 7.0R on X61s. > > "dev.acpi_ibm.0.lcd_brightness=4" in sysctl.conf > does NOT work with xorg(gdm). > > I think changing VT reset it. > I read somewhere that Xorg bypass these values, and so you can't change the brightness with that sysctl. Under xorg, for my T61, I use x11/xbacklight From takash-i at sophia.ac.jp Wed Apr 16 09:26:36 2008 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Wed Apr 16 09:26:39 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <4805B357.7020901@fastmail.fm> References: <480240AB.9080003@langille.org> <480576F3.3090709@sophia.ac.jp> <4805B357.7020901@fastmail.fm> Message-ID: <4805C682.3060004@sophia.ac.jp> Alberto Rizzi wrote: > I read somewhere that Xorg bypass these values, and so you can't change > the brightness with that sysctl. > Under xorg, for my T61, I use x11/xbacklight Thanks for the information. I'll try it from now. I can change the brightness using sysctl by hand in x-term after login. However, /etc/sysctl.conf has no effect on ttyv8. Moreover, I see sometimes inconsistency between the value and actual brightness, after several change of ttyv#. T Inoue From takash-i at sophia.ac.jp Wed Apr 16 11:39:23 2008 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Wed Apr 16 11:39:27 2008 Subject: pciconf -w Message-ID: <4805E5A2.1070705@sophia.ac.jp> Hi friends, Does anyone know how to trun off a pci device using pciconf -w ? Becase my MiniPCI Express wireless card is realy hot, I want to turn off when I don't need it. ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212 Atheros AR5212 802.11abg wireless' class = network subclass = ethernet cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message cap 10[60] = PCI-Express 1 legacy endpoint cap 11[90] = MSI-X supports 1 message in map 0x10 -- T. Inoue From takash-i at sophia.ac.jp Wed Apr 16 11:48:54 2008 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Wed Apr 16 11:49:00 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <4805C682.3060004@sophia.ac.jp> References: <480240AB.9080003@langille.org> <480576F3.3090709@sophia.ac.jp> <4805B357.7020901@fastmail.fm> <4805C682.3060004@sophia.ac.jp> Message-ID: <4805E7DD.3060505@sophia.ac.jp> > Thanks for the information. I'll try it from now. > > I can change the brightness using sysctl by hand in x-term after login. > However, /etc/sysctl.conf has no effect on ttyv8. > Moreover, I see sometimes inconsistency between the value and actual > brightness, after several change of ttyv#. I've tried xbacklight. It works perfectly. No need to be root. It's great! I'll not use lcd_brightness more. T. Inoue From freebsd at meijome.net Wed Apr 16 14:23:31 2008 From: freebsd at meijome.net (Norberto Meijome) Date: Wed Apr 16 14:23:37 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <480576F3.3090709@sophia.ac.jp> References: <480240AB.9080003@langille.org> <480576F3.3090709@sophia.ac.jp> Message-ID: <20080417002315.2089a8bd@ayiin> On Wed, 16 Apr 2008 12:48:03 +0900 Takashi Inoue wrote: > I have a similar probrem with 7.0R on X61s. > > "dev.acpi_ibm.0.lcd_brightness=4" in sysctl.conf > does NOT work with xorg(gdm). > > I think changing VT reset it. lcd_brightness has never worked for me and others. The event is detected and handled by devd, but the sysctl seems DOA. B _________________________ {Beto|Norberto|Numard} Meijome Which is worse: ignorance or apathy? Don't know. Don't care. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From jhb at freebsd.org Wed Apr 16 15:05:52 2008 From: jhb at freebsd.org (John Baldwin) Date: Wed Apr 16 15:05:58 2008 Subject: pciconf -w In-Reply-To: <4805E5A2.1070705@sophia.ac.jp> References: <4805E5A2.1070705@sophia.ac.jp> Message-ID: <200804161037.26572.jhb@freebsd.org> On Wednesday 16 April 2008 07:40:18 am Takashi Inoue wrote: > Hi friends, > > Does anyone know how to trun off a pci device using pciconf -w ? > > Becase my MiniPCI Express wireless card is realy hot, > I want to turn off when I don't need it. > > > ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5212 Atheros AR5212 802.11abg wireless' > class = network > subclass = ethernet > cap 01[40] = powerspec 2 supports D0 D3 current D0 > cap 05[50] = MSI supports 1 message > cap 10[60] = PCI-Express 1 legacy endpoint > cap 11[90] = MSI-X supports 1 message in map 0x10 Bug warner (imp@FreeBSD.org) for his devctl patch and use that to turn it off. -- John Baldwin From gaijin.k at gmail.com Wed Apr 16 15:42:28 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Wed Apr 16 15:42:32 2008 Subject: pciconf -w In-Reply-To: <200804161037.26572.jhb@freebsd.org> References: <4805E5A2.1070705@sophia.ac.jp> <200804161037.26572.jhb@freebsd.org> Message-ID: <1208358909.10448.1.camel@RabbitsDen> On Wed, 2008-04-16 at 10:37 -0400, John Baldwin wrote: > On Wednesday 16 April 2008 07:40:18 am Takashi Inoue wrote: > > Hi friends, > > > > Does anyone know how to trun off a pci device using pciconf -w ? > > > > Becase my MiniPCI Express wireless card is realy hot, > > I want to turn off when I don't need it. > > > > > > ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c > > rev=0x01 hdr=0x00 > > vendor = 'Atheros Communications Inc.' > > device = 'AR5212 Atheros AR5212 802.11abg wireless' > > class = network > > subclass = ethernet > > cap 01[40] = powerspec 2 supports D0 D3 current D0 > > cap 05[50] = MSI supports 1 message > > cap 10[60] = PCI-Express 1 legacy endpoint > > cap 11[90] = MSI-X supports 1 message in map 0x10 > > Bug warner (imp@FreeBSD.org) for his devctl patch and use that to turn it off. > Just out of curiosity... would setting hw.pci.do_power_nodriver="3" and unloading if_ath.ko do the trick? -- Alexandre "Sunny" Kovalenko (????????? ?????????) From sam at freebsd.org Wed Apr 16 16:03:45 2008 From: sam at freebsd.org (Sam Leffler) Date: Wed Apr 16 16:03:52 2008 Subject: pciconf -w In-Reply-To: <4805E5A2.1070705@sophia.ac.jp> References: <4805E5A2.1070705@sophia.ac.jp> Message-ID: <48062360.8000106@freebsd.org> Takashi Inoue wrote: > Hi friends, > > Does anyone know how to trun off a pci device using pciconf -w ? > > Becase my MiniPCI Express wireless card is realy hot, > I want to turn off when I don't need it. > > > ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5212 Atheros AR5212 802.11abg wireless' > class = network > subclass = ethernet > cap 01[40] = powerspec 2 supports D0 D3 current D0 > cap 05[50] = MSI supports 1 message > cap 10[60] = PCI-Express 1 legacy endpoint > cap 11[90] = MSI-X supports 1 message in map 0x10 > > Did you mark the interface down? When you do that it should power off the radio and the stop the mac's clock. Device id 0x1014 is not pcie as far as I know and I've never seen an Atheros card that supports MSI so something doesn't make sense here (perhaps I'm just unaware of MSI support coming in). Sam From imp at bsdimp.com Thu Apr 17 00:35:14 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Apr 17 00:35:20 2008 Subject: pciconf -w In-Reply-To: <200804161037.26572.jhb@freebsd.org> References: <4805E5A2.1070705@sophia.ac.jp> <200804161037.26572.jhb@freebsd.org> Message-ID: <20080416.183554.-1751000258.imp@bsdimp.com> In message: <200804161037.26572.jhb@freebsd.org> John Baldwin writes: : On Wednesday 16 April 2008 07:40:18 am Takashi Inoue wrote: : > Hi friends, : > : > Does anyone know how to trun off a pci device using pciconf -w ? : > : > Becase my MiniPCI Express wireless card is realy hot, : > I want to turn off when I don't need it. : > : > : > ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c : > rev=0x01 hdr=0x00 : > vendor = 'Atheros Communications Inc.' : > device = 'AR5212 Atheros AR5212 802.11abg wireless' : > class = network : > subclass = ethernet : > cap 01[40] = powerspec 2 supports D0 D3 current D0 : > cap 05[50] = MSI supports 1 message : > cap 10[60] = PCI-Express 1 legacy endpoint : > cap 11[90] = MSI-X supports 1 message in map 0x10 : : Bug warner (imp@FreeBSD.org) for his devctl patch and use that to turn it off. You could unload the ath driver :-) Of course, one could argue that the ath driver should set the device into D3 state when it has been ifconfig'd down. Warner From imp at bsdimp.com Thu Apr 17 00:38:46 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Apr 17 00:38:50 2008 Subject: pciconf -w In-Reply-To: <1208358909.10448.1.camel@RabbitsDen> References: <4805E5A2.1070705@sophia.ac.jp> <200804161037.26572.jhb@freebsd.org> <1208358909.10448.1.camel@RabbitsDen> Message-ID: <20080416.183606.-772296126.imp@bsdimp.com> In message: <1208358909.10448.1.camel@RabbitsDen> "Alexandre \"Sunny\" Kovalenko" writes: : On Wed, 2008-04-16 at 10:37 -0400, John Baldwin wrote: : > On Wednesday 16 April 2008 07:40:18 am Takashi Inoue wrote: : > > Hi friends, : > > : > > Does anyone know how to trun off a pci device using pciconf -w ? : > > : > > Becase my MiniPCI Express wireless card is realy hot, : > > I want to turn off when I don't need it. : > > : > > : > > ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c : > > rev=0x01 hdr=0x00 : > > vendor = 'Atheros Communications Inc.' : > > device = 'AR5212 Atheros AR5212 802.11abg wireless' : > > class = network : > > subclass = ethernet : > > cap 01[40] = powerspec 2 supports D0 D3 current D0 : > > cap 05[50] = MSI supports 1 message : > > cap 10[60] = PCI-Express 1 legacy endpoint : > > cap 11[90] = MSI-X supports 1 message in map 0x10 : > : > Bug warner (imp@FreeBSD.org) for his devctl patch and use that to turn it off. : > : Just out of curiosity... would setting hw.pci.do_power_nodriver="3" and : unloading if_ath.ko do the trick? Yes. Warner From smithi at nimnet.asn.au Thu Apr 17 05:30:21 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Thu Apr 17 05:30:28 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <20080417002315.2089a8bd@ayiin> Message-ID: On Thu, 17 Apr 2008, Norberto Meijome wrote: > On Wed, 16 Apr 2008 12:48:03 +0900 > Takashi Inoue wrote: > > > I have a similar probrem with 7.0R on X61s. > > > > "dev.acpi_ibm.0.lcd_brightness=4" in sysctl.conf > > does NOT work with xorg(gdm). > > > > I think changing VT reset it. > > lcd_brightness has never worked for me and others. The event is > detected and handled by devd, but the sysctl seems DOA. Just wondering; did it work before setting dev.acpi_ibm.0.events=1 ? It works on my T23 out of the box. I'm yet to use the devd events, yet notice that Fn-F4 quits working as STR when .events=1 (though +/-brightness work properly either way) on my old 6.1-R / xorg6.9 If so, maybe excluding those keys from the .eventmask (theoretically using default handling for those keys) might work? If not, ah well .. cheers, Ian From takash-i at sophia.ac.jp Thu Apr 17 07:12:02 2008 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Thu Apr 17 07:12:09 2008 Subject: pciconf -w In-Reply-To: <200804161037.26572.jhb@freebsd.org> References: <4805E5A2.1070705@sophia.ac.jp> <200804161037.26572.jhb@freebsd.org> Message-ID: <4806F879.2000400@sophia.ac.jp> John Baldwin wrote: > On Wednesday 16 April 2008 07:40:18 am Takashi Inoue wrote: > >>Hi friends, >> >>Does anyone know how to trun off a pci device using pciconf -w ? >> >>Becase my MiniPCI Express wireless card is realy hot, >>I want to turn off when I don't need it. >> >> >>ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c >>rev=0x01 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR5212 Atheros AR5212 802.11abg wireless' >> class = network >> subclass = ethernet >> cap 01[40] = powerspec 2 supports D0 D3 current D0 >> cap 05[50] = MSI supports 1 message >> cap 10[60] = PCI-Express 1 legacy endpoint >> cap 11[90] = MSI-X supports 1 message in map 0x10 > > > Bug warner (imp@FreeBSD.org) for his devctl patch and use that to turn it off. > I'm using 7.0R. Can I use it? And where can I find it? Thanks, T. Inoue From takash-i at sophia.ac.jp Thu Apr 17 07:31:49 2008 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Thu Apr 17 07:31:55 2008 Subject: pciconf -w In-Reply-To: <20080416.183606.-772296126.imp@bsdimp.com> References: <4805E5A2.1070705@sophia.ac.jp> <200804161037.26572.jhb@freebsd.org> <1208358909.10448.1.camel@RabbitsDen> <20080416.183606.-772296126.imp@bsdimp.com> Message-ID: <4806FD1D.9030706@sophia.ac.jp> M. Warner Losh wrote: > In message: <1208358909.10448.1.camel@RabbitsDen> > "Alexandre \"Sunny\" Kovalenko" writes: > : On Wed, 2008-04-16 at 10:37 -0400, John Baldwin wrote: > : > On Wednesday 16 April 2008 07:40:18 am Takashi Inoue wrote: > : > > Hi friends, > : > > > : > > Does anyone know how to trun off a pci device using pciconf -w ? > : > > > : > > Becase my MiniPCI Express wireless card is realy hot, > : > > I want to turn off when I don't need it. > : > > > : > > > : > > ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c > : > > rev=0x01 hdr=0x00 > : > > vendor = 'Atheros Communications Inc.' > : > > device = 'AR5212 Atheros AR5212 802.11abg wireless' > : > > class = network > : > > subclass = ethernet > : > > cap 01[40] = powerspec 2 supports D0 D3 current D0 > : > > cap 05[50] = MSI supports 1 message > : > > cap 10[60] = PCI-Express 1 legacy endpoint > : > > cap 11[90] = MSI-X supports 1 message in map 0x10 > : > > : > Bug warner (imp@FreeBSD.org) for his devctl patch and use that to turn it off. > : > > : Just out of curiosity... would setting hw.pci.do_power_nodriver="3" and > : unloading if_ath.ko do the trick? > > Yes. No. none1@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212 Atheros AR5212 802.11abg wireless' class = network subclass = ethernet cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message cap 10[60] = PCI-Express 1 legacy endpoint cap 11[90] = MSI-X supports 1 message in map 0x10 As you see, even in case without driver, it's power status is D0 and the device is hot. Setting hw.....nodriver=3 has no effect. I think I need to write D3 by hand. T. Inoue From takash-i at sophia.ac.jp Thu Apr 17 07:43:55 2008 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Thu Apr 17 07:44:02 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <20080417002315.2089a8bd@ayiin> References: <480240AB.9080003@langille.org> <480576F3.3090709@sophia.ac.jp> <20080417002315.2089a8bd@ayiin> Message-ID: <4806FFB9.9030804@sophia.ac.jp> Norberto Meijome wrote: > On Wed, 16 Apr 2008 12:48:03 +0900 > Takashi Inoue wrote: > > >>I have a similar probrem with 7.0R on X61s. >> >>"dev.acpi_ibm.0.lcd_brightness=4" in sysctl.conf >>does NOT work with xorg(gdm). >> >>I think changing VT reset it. > > > lcd_brightness has never worked for me and others. The event is detected and handled by devd, but the sysctl seems DOA. > I find also the value dev.cpu.#.cx_lowest are not kept. These values are reseted to C1 after change ttyv once. Very stupid. T. Inoue From freebsd at meijome.net Thu Apr 17 08:10:47 2008 From: freebsd at meijome.net (Norberto Meijome) Date: Thu Apr 17 08:10:53 2008 Subject: setting dev.acpi_ibm.0.events at boot time In-Reply-To: <20080417002315.2089a8bd@ayiin> References: <480240AB.9080003@langille.org> <480576F3.3090709@sophia.ac.jp> <20080417002315.2089a8bd@ayiin> Message-ID: <20080417181033.4cf8ee04@ayiin> On Thu, 17 Apr 2008 00:23:15 +1000 Norberto Meijome wrote: > From: Norberto Meijome > To: Takashi Inoue > Cc: freebsd-mobile@freebsd.org > Subject: Re: setting dev.acpi_ibm.0.events at boot time > Date: Thu, 17 Apr 2008 00:23:15 +1000 > Sender: owner-freebsd-mobile@freebsd.org > X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i386-portbld-freebsd7.0) > > On Wed, 16 Apr 2008 12:48:03 +0900 > Takashi Inoue wrote: > > > I have a similar probrem with 7.0R on X61s. > > > > "dev.acpi_ibm.0.lcd_brightness=4" in sysctl.conf > > does NOT work with xorg(gdm). > > > > I think changing VT reset it. > > lcd_brightness has never worked for me and others. The event is detected and handled by devd, but the sysctl seems DOA. hmm let me qualify this. "on my thinkpad z60m", the sysctl itself doesn't seem to be doing anything. But fn-Home and fn-End actually change the dimming of the lcd. It of course wont work with other software that try to affect the brightness of the LCD, i will give backlight a spin. cheers, B _________________________ {Beto|Norberto|Numard} Meijome Law of Conservation of Perversity: we can't make something simpler without making something else more complex I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. From takash-i at sophia.ac.jp Thu Apr 17 08:24:27 2008 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Thu Apr 17 08:24:34 2008 Subject: pciconf -w In-Reply-To: <48062360.8000106@freebsd.org> References: <4805E5A2.1070705@sophia.ac.jp> <48062360.8000106@freebsd.org> Message-ID: <48070939.6010701@sophia.ac.jp> Sam Leffler wrote: > Takashi Inoue wrote: > >> Hi friends, >> >> Does anyone know how to trun off a pci device using pciconf -w ? >> >> Becase my MiniPCI Express wireless card is realy hot, >> I want to turn off when I don't need it. >> >> >> ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c >> rev=0x01 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> device = 'AR5212 Atheros AR5212 802.11abg wireless' >> class = network >> subclass = ethernet >> cap 01[40] = powerspec 2 supports D0 D3 current D0 >> cap 05[50] = MSI supports 1 message >> cap 10[60] = PCI-Express 1 legacy endpoint >> cap 11[90] = MSI-X supports 1 message in map 0x10 >> >> > > > Did you mark the interface down? When you do that it should power off > the radio and the stop the mac's clock. Really? I don't think so. At here, ath0 is ON(D0) regardress ath0 is up or down or driver is loaded or unloded. > Device id 0x1014 is not pcie as far as I know and I've never seen an > Atheros card that supports MSI so something doesn't make sense here > (perhaps I'm just unaware of MSI support coming in). That is Lebovo option MiniPCI Express card in below(in Japanese). http://www-06.ibm.com/jp/pc/option/obi/nob11/40y7028/40y7028a.shtml T. Inoue From dirkx at webweaving.org Thu Apr 17 10:05:51 2008 From: dirkx at webweaving.org (Dirk-Willem van Gulik) Date: Thu Apr 17 10:05:55 2008 Subject: pciconf -w In-Reply-To: <20080416.183606.-772296126.imp@bsdimp.com> References: <4805E5A2.1070705@sophia.ac.jp> <200804161037.26572.jhb@freebsd.org> <1208358909.10448.1.camel@RabbitsDen> <20080416.183606.-772296126.imp@bsdimp.com> Message-ID: <328A981E-AAC9-42D5-BCA7-8F83B8E3BB63@webweaving.org> On Apr 17, 2008, at 2:36 AM, M. Warner Losh wrote: > : > > Does anyone know how to trun off a pci device using pciconf -w ? > ..... > : > > ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 > chip=0x1014168c .... > : > > cap 01[40] = powerspec 2 supports D0 D3 current D0 > : > > cap 05[50] = MSI supports 1 message > : > > cap 10[60] = PCI-Express 1 legacy endpoint > : > > cap 11[90] = MSI-X supports 1 message in map 0x10 > : > > : > Bug warner (imp@FreeBSD.org) for his devctl patch and use that > to turn it off. > : > > : Just out of curiosity... would setting > hw.pci.do_power_nodriver="3" and > : unloading if_ath.ko do the trick? > > Yes. Hmm - this does not work for me on a Soekris and in a Sony VAIO -- even after down, sysctl and unloading the driver it reports sitting in D0. Does this require certain support in the PCI controller ? Dw From dan at langille.org Thu Apr 17 13:14:21 2008 From: dan at langille.org (Dan Langille) Date: Thu Apr 17 13:14:27 2008 Subject: pciconf -w In-Reply-To: <4806FD1D.9030706@sophia.ac.jp> References: <4805E5A2.1070705@sophia.ac.jp> <200804161037.26572.jhb@freebsd.org> <1208358909.10448.1.camel@RabbitsDen> <20080416.183606.-772296126.imp@bsdimp.com> <4806FD1D.9030706@sophia.ac.jp> Message-ID: <48074D2F.4050602@langille.org> Takashi Inoue wrote: > M. Warner Losh wrote: > >> In message: <1208358909.10448.1.camel@RabbitsDen> >> "Alexandre \"Sunny\" Kovalenko" writes: >> : On Wed, 2008-04-16 at 10:37 -0400, John Baldwin wrote: >> : > On Wednesday 16 April 2008 07:40:18 am Takashi Inoue wrote: >> : > > Hi friends, >> : > > >> : > > Does anyone know how to trun off a pci device using pciconf -w ? >> : > > >> : > > Becase my MiniPCI Express wireless card is realy hot, >> : > > I want to turn off when I don't need it. >> : > > >> : > > >> : > > ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 >> chip=0x1014168c >> : > > rev=0x01 hdr=0x00 >> : > > vendor = 'Atheros Communications Inc.' >> : > > device = 'AR5212 Atheros AR5212 802.11abg wireless' >> : > > class = network >> : > > subclass = ethernet >> : > > cap 01[40] = powerspec 2 supports D0 D3 current D0 >> : > > cap 05[50] = MSI supports 1 message >> : > > cap 10[60] = PCI-Express 1 legacy endpoint >> : > > cap 11[90] = MSI-X supports 1 message in map 0x10 >> : > : > Bug warner (imp@FreeBSD.org) for his devctl patch and use that >> to turn it off. >> : > : Just out of curiosity... would setting >> hw.pci.do_power_nodriver="3" and >> : unloading if_ath.ko do the trick? >> >> Yes. > > No. > > none1@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5212 Atheros AR5212 802.11abg wireless' > class = network > subclass = ethernet > cap 01[40] = powerspec 2 supports D0 D3 current D0 > cap 05[50] = MSI supports 1 message > cap 10[60] = PCI-Express 1 legacy endpoint > cap 11[90] = MSI-X supports 1 message in map 0x10 > > As you see, even in case without driver, > it's power status is D0 and the device is hot. > Setting hw.....nodriver=3 has no effect. > I think I need to write D3 by hand. I have a ThinkPad X61s. Here is what I see when ath0 is up: ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212 Atheros AR5212 802.11abg wireless' class = network subclass = ethernet cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message cap 10[60] = PCI-Express 1 legacy endpoint cap 11[90] = MSI-X supports 1 message in map 0x10 After an ifconfig ath0 down: ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212 Atheros AR5212 802.11abg wireless' class = network subclass = ethernet cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message cap 10[60] = PCI-Express 1 legacy endpoint cap 11[90] = MSI-X supports 1 message in map 0x10 after hw.pci.do_power_nodriver="3" ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212 Atheros AR5212 802.11abg wireless' class = network subclass = ethernet cap 01[40] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message cap 10[60] = PCI-Express 1 legacy endpoint cap 11[90] = MSI-X supports 1 message in map 0x10 As for loaded modules: [root@laptop ~]# kldstat | grep ath [root@laptop ~]# HTH From outbackdingo at gmail.com Thu Apr 17 14:31:38 2008 From: outbackdingo at gmail.com (Outback Dingo) Date: Thu Apr 17 14:31:51 2008 Subject: fprint (finger print sensor framework) port ready for testing In-Reply-To: <20080415194347.GB1956@dose.local.invalid> References: <20080414180740.GA1050@dose.local.invalid> <1208256383.1513.6.camel@localhost> <5635aa0d0804150751n3f89e885mdac8fb3077cdc331@mail.gmail.com> <20080415194347.GB1956@dose.local.invalid> Message-ID: <5635aa0d0804170731t14898e8evf6d6c45e2ef986ae@mail.gmail.com> any luck on this.... ? On Wed, Apr 16, 2008 at 2:43 AM, Simon Barner wrote: > Outback Dingo wrote: > > pam_fprint works (see below) but when i try to run the fprint demo i get > > > > STATUS: No Devices Found > > Are you sure you have r/w access to the sensor's USB device? > > > > pam_fprint_enroll -f 7 > > This program will enroll your finger, unconditionally overwriting any > selected > > print that was enrolled previously. If you want to continue, press > enter, > > otherwise hit Ctrl+C > > > > Found device claimed by UPEK TouchStrip driver > > Opened device. It's now time to enroll your finger. > > > > You will need to successfully scan your Right Index Finger 3 times to > complete > > the process. > > > > Scan your finger now. > > upekts:error [read_msg] non-zero bytes in cmd response > > upekts:error [read_msg28] expected response, got -1 seq=40 > > Something seems to go wrong. I have never seenn this error message. > > Which sensor are you using? Can you send me the output of `usbdevs -vd' > in a private mail please? > > -- > Best regards / Viele Gr??e, barner@FreeBSD.org > Simon Barner barner@gmx.de > From sam at freebsd.org Thu Apr 17 15:47:58 2008 From: sam at freebsd.org (Sam Leffler) Date: Thu Apr 17 15:48:05 2008 Subject: pciconf -w In-Reply-To: <48070939.6010701@sophia.ac.jp> References: <4805E5A2.1070705@sophia.ac.jp> <48062360.8000106@freebsd.org> <48070939.6010701@sophia.ac.jp> Message-ID: <4807712D.20502@freebsd.org> Takashi Inoue wrote: > Sam Leffler wrote: > >> Takashi Inoue wrote: >> >>> Hi friends, >>> >>> Does anyone know how to trun off a pci device using pciconf -w ? >>> >>> Becase my MiniPCI Express wireless card is realy hot, >>> I want to turn off when I don't need it. >>> >>> >>> ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c >>> rev=0x01 hdr=0x00 >>> vendor = 'Atheros Communications Inc.' >>> device = 'AR5212 Atheros AR5212 802.11abg wireless' >>> class = network >>> subclass = ethernet >>> cap 01[40] = powerspec 2 supports D0 D3 current D0 >>> cap 05[50] = MSI supports 1 message >>> cap 10[60] = PCI-Express 1 legacy endpoint >>> cap 11[90] = MSI-X supports 1 message in map 0x10 >>> >>> >> >> >> Did you mark the interface down? When you do that it should power >> off the radio and the stop the mac's clock. > > Really? > I don't think so. > At here, ath0 is ON(D0) regardress ath0 is up or down > or driver is loaded or unloded. I didn't say marking the interface down powered down the socket; I said it powered off the radio and stopped the MAC. This means the chip should be doing nothing to draw power so if it is then either something is not being stopped or there's an issue elsewhere. I'm aware of several PCIE power-related errata and can investigate but must have the mac+phy revs from the chip which you haven't provided. > > >> Device id 0x1014 is not pcie as far as I know and I've never seen an >> Atheros card that supports MSI so something doesn't make sense here >> (perhaps I'm just unaware of MSI support coming in). > > That is Lebovo option MiniPCI Express card in below(in Japanese). > > http://www-06.ibm.com/jp/pc/option/obi/nob11/40y7028/40y7028a.shtml > Sorry, all I can get out of that is a picture :) Provide the mac+phy revs from dmesg | grep ath0 and tell me the hal version. Sam From imp at bsdimp.com Thu Apr 17 15:48:26 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Apr 17 15:48:32 2008 Subject: pciconf -w In-Reply-To: <328A981E-AAC9-42D5-BCA7-8F83B8E3BB63@webweaving.org> References: <1208358909.10448.1.camel@RabbitsDen> <20080416.183606.-772296126.imp@bsdimp.com> <328A981E-AAC9-42D5-BCA7-8F83B8E3BB63@webweaving.org> Message-ID: <20080417.094732.-399283795.imp@bsdimp.com> In message: <328A981E-AAC9-42D5-BCA7-8F83B8E3BB63@webweaving.org> Dirk-Willem van Gulik writes: : : On Apr 17, 2008, at 2:36 AM, M. Warner Losh wrote: : : > : > > Does anyone know how to trun off a pci device using pciconf -w ? : > ..... : > : > > ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 : > chip=0x1014168c : .... : > : > > cap 01[40] = powerspec 2 supports D0 D3 current D0 : > : > > cap 05[50] = MSI supports 1 message : > : > > cap 10[60] = PCI-Express 1 legacy endpoint : > : > > cap 11[90] = MSI-X supports 1 message in map 0x10 : > : > : > : > Bug warner (imp@FreeBSD.org) for his devctl patch and use that : > to turn it off. : > : > : > : Just out of curiosity... would setting : > hw.pci.do_power_nodriver="3" and : > : unloading if_ath.ko do the trick? : > : > Yes. : : Hmm - this does not work for me on a Soekris and in a Sony VAIO -- : even after down, sysctl and : unloading the driver it reports sitting in D0. Does this require : certain support in the PCI controller ? No. It is chip-level support. It worked for me when I put it in /boot/loader.conf and it worked for me. Did you reboot or no? I didn't try it w/o rebooting. Warner From dirkx at webweaving.org Thu Apr 17 15:57:04 2008 From: dirkx at webweaving.org (Dirk-Willem van Gulik) Date: Thu Apr 17 15:57:10 2008 Subject: pciconf -w In-Reply-To: <20080417.094732.-399283795.imp@bsdimp.com> References: <1208358909.10448.1.camel@RabbitsDen> <20080416.183606.-772296126.imp@bsdimp.com> <328A981E-AAC9-42D5-BCA7-8F83B8E3BB63@webweaving.org> <20080417.094732.-399283795.imp@bsdimp.com> Message-ID: <88FC551D-4638-4959-83AD-6F3EFCA452D8@webweaving.org> On Apr 17, 2008, at 5:47 PM, M. Warner Losh wrote: > : Hmm - this does not work for me on a Soekris and in a Sony VAIO -- > : even after down, sysctl and > : unloading the driver it reports sitting in D0. Does this require > : certain support in the PCI controller ? > > No. It is chip-level support. > > It worked for me when I put it in /boot/loader.conf and it worked for > me. Did you reboot or no? I didn't try it w/o rebooting. Yes - across a proper reboot is fine. Dw From imp at bsdimp.com Thu Apr 17 16:08:40 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Thu Apr 17 16:08:46 2008 Subject: pciconf -w In-Reply-To: <88FC551D-4638-4959-83AD-6F3EFCA452D8@webweaving.org> References: <328A981E-AAC9-42D5-BCA7-8F83B8E3BB63@webweaving.org> <20080417.094732.-399283795.imp@bsdimp.com> <88FC551D-4638-4959-83AD-6F3EFCA452D8@webweaving.org> Message-ID: <20080417.100714.635731945.imp@bsdimp.com> In message: <88FC551D-4638-4959-83AD-6F3EFCA452D8@webweaving.org> Dirk-Willem van Gulik writes: : : On Apr 17, 2008, at 5:47 PM, M. Warner Losh wrote: : : > : Hmm - this does not work for me on a Soekris and in a Sony VAIO -- : > : even after down, sysctl and : > : unloading the driver it reports sitting in D0. Does this require : > : certain support in the PCI controller ? : > : > No. It is chip-level support. : > : > It worked for me when I put it in /boot/loader.conf and it worked for : > me. Did you reboot or no? I didn't try it w/o rebooting. : : Yes - across a proper reboot is fine. OK. That sounds like a simple bug in the dynamic support. I'll look into it. Warner From takash-i at sophia.ac.jp Mon Apr 21 03:07:35 2008 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Mon Apr 21 03:07:41 2008 Subject: pciconf -w In-Reply-To: <4807712D.20502@freebsd.org> References: <4805E5A2.1070705@sophia.ac.jp> <48062360.8000106@freebsd.org> <48070939.6010701@sophia.ac.jp> <4807712D.20502@freebsd.org> Message-ID: <480C04FC.4060900@sophia.ac.jp> Sam Leffler wrote: > I didn't say marking the interface down powered down the socket; I said > it powered off the radio and stopped the MAC. This means the chip > should be doing nothing to draw power so if it is then either something > is not being stopped or there's an issue elsewhere. I'm aware of > several PCIE power-related errata and can investigate but must have the > mac+phy revs from the chip which you haven't provided. > > Sorry, all I can get out of that is a picture :) Provide the mac+phy > revs from dmesg | grep ath0 and tell me the hal version. > Sorry for late. I was out in this weekend. Here is mac+phys and hal. Please investigate it. Thanks. ath0: mem 0xf7f00000-0xf7f0ffff irq 17 at device 0.0 on pci3 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: ath0: mac 10.3 phy 6.1 radio 10.2 ath_hal: 0.9.30.13 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133) I think ath_hal is newest writen by you. I am using 7.0R. Best, T. Inoue From june2007 at myjaring.net Mon Apr 21 17:09:18 2008 From: june2007 at myjaring.net (June) Date: Mon Apr 21 17:09:24 2008 Subject: [OTC] Boiler - Every 2 pax FREE 1 pax!!! Message-ID: <161c4716961bde6161dc02090019c999@myjaring.net> THE PRACTICAL APPROACH TO BOILER OPERATIONS, MAINTENANCE & MANAGEMENT Date: 21 & 22 May 2008 PLEASE NOTE THAT ALL OUR COURSES ARE CLAIMABLE UNDER HRDF!!! OVERVIEW Being able to service your boiler is one thing. Being able to maintain and do it safely is another thing. Boilers have been commonly used by the industries for centuries in producing steam. These industries varies from manufacturing lines to processing industries like food, agriculture, oil & gas, utility power plants and even commercial building sectors, for instance hotel, hospital etc. Over time, the basic boilers have grown in respect of the power as well as capacities, and applications of sophisticated automation and electro-techniques are used; hence increasing the possibilities of operation failures, flaws and accidents. Improving knowledge and skills through practical training in boiler management is perhaps the most tangible way to avoid such losses, not only on human lives, but also on maintenance costs. Anyone can teach theory, but there simply is no substitution for real practical experiences. The 2-days intensive course on Boiler/ Steam Plant Operation & Management focuses in establishing the proper maintenance procedures and correct practices in the Steam Plant Operation. It will cover Boiler Safety, Boiler Management, and Cost Control (Boiler Efficiency) in operating the Steam Plant. In addition, it will provide practical guidance in boiler management procedures, which is highly useful in their work routine. In general, this program will escalate the practical knowledge base of participants to become better Operators and Technicians in their own plants. The participants will develop ideas & suggestions from the course, which then could be forwarded to their management for improvements in their work process. UPON COMPLETION _ Increase their confidence to Operate & Supervise Steam Plant _ Explain the Importance of the components used in Steam Plant _ Describe the Principles of Operation and Maintenance of Steam Plant _ Understand the Concepts such as Water Treatment, Combustion System & Material used in the Steam Plant _ Provide some proper Guidelines & Procedures in Maintaining the Boilers OUR CONSULTANT Mr R.C.Raj holds a First Grade Steam and Internal Combustion Engine (ICE) Engineer Certification issued by JKKP, DOSH. With more than 35 years of working experience, mainly in the operation and maintenance of palm oil mills and petro-chemical complex manufacturing, his professional specialization ranges from the operation and maintenance of all Steam Generating Equipments and Steam Usage Equipments, to other utilities such as Natural Gas Fired Boilers, Waste Heat Boilers, Steam Turbine, Gas Turbine, Water and Condensate Treatment, Cooling Water System and Chilled Water System. He is also the Visiting Engineer and Advisor for another Utility Steam Plant and Co-generation Plants. His current projects include: Working with a Team of Engineers on Biomass Project; Design and Engineering Study on Direct Fired Chillers 1500Usrt; Carrying out a Study on Cost Optimization for Co-Gen Plant. Chiller Operation, Boiler, Gas Turbine, Cooling and Chilled Water Systems Apart from his profession, he has conducted numerous training programs for technicians, engineers and managers in companies or institutions like Petronas, MPOB, Gas District Cooling Holdings Sdn Bhd (GDC), MEC Works Sdn Bhd, Thermal System & Engineering Sdn Bhd, Boiler Care Sdn Bhd, University Malaya (UM),University Technology Petronas (UTP) etc. COURSE OUTLINE ? 1. Steam Plant Operation - Safety Boiler House: Housekeeping Safety PPE Requirements 2. Steam Plant Management Log Books Records History 3. Boiler Construction Water Tube Fire Tube Materials Setup 4. Boiler Operation Start /Stop Routine Check - Before, While, & After Operation Min. Operation Guidelines 5. Understanding of Water Treatment in Steam Plant Importance of Water Treatments References in other Industries & Process Plants 6. Routine Inspection /DOSH Inspection Requirements Boiler Preparation for DOSH Inspection Requirements 7. Combustion System /Fuel Understanding of: Boiler Fuel Systems Cost Saving Aspects 8. Factories & Machinery Act 9. Steam Traps Operation & Maintenance 10. Boiler Efficiency 11. Boiler Maintenance & Repairs Maintenance Practices Common Repairs Minor Methods Major Methods Please contact Saliknee @ 03-56338162 or saliknee@otc.com.my for more information From lme at FreeBSD.org Tue Apr 22 09:49:45 2008 From: lme at FreeBSD.org (Lars Engels) Date: Tue Apr 22 09:50:12 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: <20080414220641.GK50049@e.0x20.net> References: <0319208F-8098-4EAA-B3DA-22C6FE1C02DD@langille.org> <20080326155507.wiubhspc04ok440g@0x20.net> <47F8AD88.2010406@users.sf.net> <20080407133354.djlrjmnm04ks0www@0x20.net> <47FA7351.4030601@users.sf.net> <20080414220641.GK50049@e.0x20.net> Message-ID: <20080422114943.bih64qriwwo80k84@0x20.net> Quoting Lars Engels : > On Mon, Apr 07, 2008 at 09:17:37PM +0200, martinko wrote: >> Lars Engels wrote: >> >Quoting martinko : >> >>Hi Lars, >> >> >> >>sysutils/nbosd looks very nice and rather useful, thanks! :-) >> >> >> >>However, I can think of the following: >> >> >> >>There are 2 important/interesting information missing: >> >>- remaining run-time in hours:minutes when running on battery >> >>- CPU temperature (especially on laptops) >> > >> >Good idea, it should be no problem to use sysctl to get those values. >> > >> >>Also, it might be quite useful to render battery related info in red >> >>colour once battery charge drops below some (configurable) limit when >> >>not running on AC power. >> >> >> >>The last but not least important is this -- nbosd shows you info on >> >>demand only. I find that most often I forget about my battery running >> >>flat and thus nbosd wouldn't help. Any idea how to deal with it ? >> > >> >nbosd was designed to show the value on demand. I have a keyboard >> shortcut which shows me the >> >OSD whenever I need it. >> >But the shortcut doesn't work in every case e.g. when playing >> fullscreen games. So I taught >> >nbosd to work together with devd and now nbosd has an option to >> run as a daemon and only shows >> >up when the battery percentage falls below a user-defined value. >> >It still has some rough corners and the code needs to be cleaned >> up that's why I haven't >> >committed the new version. >> >I hope that my (very limited atm :-( ) time allows me get it >> finished, soon. >> > >> >> Hi Lars, >> >> Remaining run-time (hours:minutes) could be next to the percentage value. >> I'm not sure about the temperature, though. >> >> I've set up a keyboard shotcut too (in WMaker) and it works great. >> However, sometimes I forget I'm running on battery and only find >> out when my laptop dies >> abruptly. That's why I'm trying to figure out how best to prevent >> such situations. >> >> And what do you say about my suggestion to render battery life text >> and graphics in red when >> running on DC and too low ? Would it be possible ? > > > Hi Martin, > > somehow I didn't see you mail until now... > I just worked a bit on nbosd and it should fulfill your needs now: > A -d switch was added to run it as a daemon. You can give it an alarm > threshold with -a and the osd will pop up (in red ;-) ) when the current > battery level is below that threshold. > Additionally the remaining battery time is displayed. > I haven't committed the new version yet. I'd like to have one or two > testers before: > http://bsd-geek.de/FreeBSD/distfiles/nbosd-0.5.0.tar.gz > > So if you would like to try it, please give a feedback on it. > > Lars I updated the port to the last version. Have fun :) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: PGP Digital Signature Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080422/29bd64e9/attachment.pgp From gamato at users.sf.net Tue Apr 22 19:52:33 2008 From: gamato at users.sf.net (mato) Date: Tue Apr 22 19:52:37 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: References: Message-ID: <480E41FB.2080503@users.sf.net> Ian Smith wrote: > FWIW, I've also long used sysutils/ascpu as a 60sec visual load monitor, > matching asapm's 'look', res. size and low cpu usage. At ~7days uptime: > > 3680 smithi 8 0 2344K 448K nanslp 44:06 0.00% 0.00% asapm > 3681 smithi 8 0 2564K 448K nanslp 41:53 0.00% 0.00% ascpu > 3514 root 96 0 1280K 264K select 36:32 0.00% 0.00% moused > > There's something wrong with asapm or with my system -- I configured asapm for 5 seconds updating (as opposed to default 1s) and after 3 hours of uptime it already consumed 30 CPU-seconds. (!) Regarding look, I would prefer asapm to use a bit more of space like wmbsdbatt does (or wmcpuload which I've long been using as a visual load monitor). Regards, Martin From gamato at users.sf.net Tue Apr 22 19:56:50 2008 From: gamato at users.sf.net (mato) Date: Tue Apr 22 19:56:56 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: <20080422114943.bih64qriwwo80k84@0x20.net> References: <0319208F-8098-4EAA-B3DA-22C6FE1C02DD@langille.org> <20080326155507.wiubhspc04ok440g@0x20.net> <47F8AD88.2010406@users.sf.net> <20080407133354.djlrjmnm04ks0www@0x20.net> <47FA7351.4030601@users.sf.net> <20080414220641.GK50049@e.0x20.net> <20080422114943.bih64qriwwo80k84@0x20.net> Message-ID: <480E42FE.6040903@users.sf.net> Lars Engels wrote: > Quoting Lars Engels : > >> On Mon, Apr 07, 2008 at 09:17:37PM +0200, martinko wrote: >>> Lars Engels wrote: >>> >Quoting martinko : >>> >>Hi Lars, >>> >> >>> >>sysutils/nbosd looks very nice and rather useful, thanks! :-) >>> >> >>> >>However, I can think of the following: >>> >> >>> >>There are 2 important/interesting information missing: >>> >>- remaining run-time in hours:minutes when running on battery >>> >>- CPU temperature (especially on laptops) >>> > >>> >Good idea, it should be no problem to use sysctl to get those values. >>> > >>> >>Also, it might be quite useful to render battery related info in red >>> >>colour once battery charge drops below some (configurable) limit when >>> >>not running on AC power. >>> >> >>> >>The last but not least important is this -- nbosd shows you info on >>> >>demand only. I find that most often I forget about my battery >>> running >>> >>flat and thus nbosd wouldn't help. Any idea how to deal with it ? >>> > >>> >nbosd was designed to show the value on demand. I have a keyboard >>> shortcut which shows me the >>> >OSD whenever I need it. >>> >But the shortcut doesn't work in every case e.g. when playing >>> fullscreen games. So I taught >>> >nbosd to work together with devd and now nbosd has an option to >>> run as a daemon and only shows >>> >up when the battery percentage falls below a user-defined value. >>> >It still has some rough corners and the code needs to be cleaned >>> up that's why I haven't >>> >committed the new version. >>> >I hope that my (very limited atm :-( ) time allows me get it >>> finished, soon. >>> > >>> >>> Hi Lars, >>> >>> Remaining run-time (hours:minutes) could be next to the percentage >>> value. >>> I'm not sure about the temperature, though. >>> >>> I've set up a keyboard shotcut too (in WMaker) and it works great. >>> However, sometimes I forget I'm running on battery and only find >>> out when my laptop dies >>> abruptly. That's why I'm trying to figure out how best to prevent >>> such situations. >>> >>> And what do you say about my suggestion to render battery life text >>> and graphics in red when >>> running on DC and too low ? Would it be possible ? >> >> >> Hi Martin, >> >> somehow I didn't see you mail until now... >> I just worked a bit on nbosd and it should fulfill your needs now: >> A -d switch was added to run it as a daemon. You can give it an alarm >> threshold with -a and the osd will pop up (in red ;-) ) when the current >> battery level is below that threshold. >> Additionally the remaining battery time is displayed. >> I haven't committed the new version yet. I'd like to have one or two >> testers before: >> http://bsd-geek.de/FreeBSD/distfiles/nbosd-0.5.0.tar.gz >> >> So if you would like to try it, please give a feedback on it. >> >> Lars > > I updated the port to the last version. Have fun :) > Hi Lars, I've been on holiday but I'll upgrade and try the new version soon.. Cheers, M. From smithi at nimnet.asn.au Wed Apr 23 03:46:46 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Wed Apr 23 03:46:49 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: <480E41FB.2080503@users.sf.net> Message-ID: On Tue, 22 Apr 2008, mato wrote: > Ian Smith wrote: > > FWIW, I've also long used sysutils/ascpu as a 60sec visual load monitor, > > matching asapm's 'look', res. size and low cpu usage. At ~7days uptime: > > > > 3680 smithi 8 0 2344K 448K nanslp 44:06 0.00% 0.00% asapm > > 3681 smithi 8 0 2564K 448K nanslp 41:53 0.00% 0.00% ascpu > > 3514 root 96 0 1280K 264K select 36:32 0.00% 0.00% moused > > > > > > There's something wrong with asapm or with my system -- I configured > asapm for 5 seconds updating (as opposed to default 1s) and after 3 > hours of uptime it already consumed 30 CPU-seconds. (!) Yeah Martin, that seems a lot; mine's using ~6 seconds per day. Perhaps to do with running on amd64 rather than i386, though I've no idea why, unless it's much busier with ACPI than with APM. Might be worth trying with the explicit -acpi switch, in case it tries using the apm-over-acpi calls on your system? Pure speculation .. Are you running any commands on any conditions from the resource file? I don't use ~/.asapmrc at all, just run 'asapm -lower forestgreen'. > Regarding look, I would prefer asapm to use a bit more of space like > wmbsdbatt does (or wmcpuload which I've long been using as a visual load > monitor). Well this ol' beastie has an 800x600 screen, so small (about 0.9" square with frame) is good for me. You'd have to play with the sources to make it bigger, which is way beyond my ability (or interest :) cheers, Ian From jordan at JordanColeman.com Wed Apr 23 20:13:09 2008 From: jordan at JordanColeman.com (Jordan Coleman) Date: Wed Apr 23 20:13:17 2008 Subject: "International" channels on a CM9 Message-ID: <6B39D996-3A54-43FD-922F-C5883FA8B405@JordanColeman.com> I have an embedded system that contains a Wistron CM9 802.11 card, purchased in the US. After extensive testing in the US, the unit is now being installed in Europe, where 802.11b/g channels 1-13 are employed. How can I enable channels 12 and 13 on this hardware, which currently seems to only be able to use the "US" channels, 1-11? ifconfig has the 'chanlist' command, but it seems like there's more to enabling those channels than just giving the 802.11 stack permission to scan there. Any help is appreciated. ++Jordan From Benjamin.Close at clearchain.com Wed Apr 23 23:17:04 2008 From: Benjamin.Close at clearchain.com (Benjamin Close) Date: Wed Apr 23 23:17:09 2008 Subject: "International" channels on a CM9 In-Reply-To: <6B39D996-3A54-43FD-922F-C5883FA8B405@JordanColeman.com> References: <6B39D996-3A54-43FD-922F-C5883FA8B405@JordanColeman.com> Message-ID: <480FC364.40808@clearchain.com> Jordan Coleman wrote: > I have an embedded system that contains a Wistron CM9 802.11 card, > purchased in the US. After extensive testing in the US, the unit is > now being installed in Europe, where 802.11b/g channels 1-13 are > employed. How can I enable channels 12 and 13 on this hardware, which > currently seems to only be able to use the "US" channels, 1-11? > > ifconfig has the 'chanlist' command, but it seems like there's more to > enabling those channels than just giving the 802.11 stack permission > to scan there. > > Any help is appreciated. > > ++Jordan Hi Jordan, It might be a limitation of the driver. Can you provide more details? ie: ifconfig -v Cheers, Benjamin From jordan at JordanColeman.com Wed Apr 23 23:51:32 2008 From: jordan at JordanColeman.com (Jordan Coleman) Date: Wed Apr 23 23:51:35 2008 Subject: "International" channels on a CM9 In-Reply-To: <480FC364.40808@clearchain.com> References: <6B39D996-3A54-43FD-922F-C5883FA8B405@JordanColeman.com> <480FC364.40808@clearchain.com> Message-ID: <686EBD19-7FE3-4B6E-BA74-5E7329A91A41@JordanColeman.com> On Apr 23, 2008, at 7:16 PM, Benjamin Close wrote: > Jordan Coleman wrote: >> I have an embedded system that contains a Wistron CM9 802.11 card, >> purchased in the US. After extensive testing in the US, the unit >> is now being installed in Europe, where 802.11b/g channels 1-13 are >> employed. How can I enable channels 12 and 13 on this hardware, >> which currently seems to only be able to use the "US" channels, 1-11? [...] > It might be a limitation of the driver. Can you provide more > details? ie: ifconfig -v Happy to: ath0: flags=8843 metric 0 mtu 1500 ether 00:15:6d:54:65:c6 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) status: associated ssid PortOfSeattle channel 6 (2437 Mhz 11g) bssid 00:0f:66:ae:31:44 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit powersavemode OFF powersavesleep 100 txpower 31.5 txpowmax 16.0 rtsthreshold 2346 fragthreshold 2346 bmiss 7 scanvalid 60 bgscan bgscanintvl 30 bgscanidle 250 roam:rssi11a 7 roam:rate11a 12 roam:rssi11b 7 roam:rate11b 1 roam:rssi11g 7 roam:rate11g 5 -pureg protmode CTS -ht -htcompat -ampdu ampdulimit 8k ampdudensity - -amsdu -shortgi htprotmode RTSCTS -puren -wme burst -ff -dturbo roaming MANUAL bintval 100 This is running FreeBSD 7.0-STABLE. For completeness, here are a few seemingly-relevant lines from dmesg: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) [...] ath0: mem 0xa0010000-0xa001ffff irq 11 at device 14.0 on pci0 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:15:6d:54:65:c6 ath0: mac 5.9 phy 4.3 radio 4.6 Thanks. ++J From jmt at twilley.org Thu Apr 24 07:51:16 2008 From: jmt at twilley.org (Jack Twilley) Date: Thu Apr 24 07:51:21 2008 Subject: Status on Asus Eee support? Message-ID: <48103774.9040201@twilley.org> I have an Asus Eee 8G and I'm loving it. The EeeBSD page at http://nighthack.org/wiki/EeeBSD has been really helpful. What's the status on porting the NetBSD drivers for ACPI and wired Ethernet to the device? Also, any idea when the wireless Ethernet drivers will be supported without having to copy in the HAL from madwifi? Jack. From oberman at es.net Fri Apr 25 17:35:35 2008 From: oberman at es.net (Kevin Oberman) Date: Fri Apr 25 17:35:45 2008 Subject: Dial-up Networking with Verizon and Treo Message-ID: <20080425173533.2205345010@ptavv.es.net> I have a Verizon Wireless Palm 755p with which I can connect my laptop to the Internet under Windows. I would really like to be able to do this under FreeBSD, but I have no idea of what the appropriate USB driver would be or how PPP would be configured for it. The Verizon software does not even have an account name or password for the connection. Has anyone managed to get this to work? I suspect any Treo on Verizon would connect in much the same manner. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 224 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080425/a5bdca70/attachment.pgp From lists at swaggi.com Fri Apr 25 19:54:00 2008 From: lists at swaggi.com (Yuri Lukin) Date: Fri Apr 25 19:54:03 2008 Subject: Dial-up Networking with Verizon and Treo In-Reply-To: <20080425173533.2205345010@ptavv.es.net> References: <20080425173533.2205345010@ptavv.es.net> Message-ID: <20080425185238.M24089@swaggi.com> On Fri, 25 Apr 2008 10:35:33 -0700, Kevin Oberman wrote > I have a Verizon Wireless Palm 755p with which I can connect my > laptop to the Internet under Windows. I would really like to be able > to do this under FreeBSD, but I have no idea of what the appropriate > USB driver would be or how PPP would be configured for it. The > Verizon software does not even have an account name or password for > the connection. > > Has anyone managed to get this to work? I suspect any Treo on Verizon > would connect in much the same manner. > -- I did this with my old Verizon Motorola phone several years ago via Bluetooth. I paired my laptop (6.0-RELEASE afaik) with the phone and used it as a modem to dial-up to Verizon's network. The speed wasn't great (EVDO) but it worked. Verizon phones dial #777 for a data connection where the username is your_10_digit_number@vzw3g.com and the password is vzw. Don't think you need the cable/dongle as long as your 755p supports DUN via bluetooth. I have a 700wx myself but haven't tried this yet. From oberman at es.net Fri Apr 25 20:28:57 2008 From: oberman at es.net (Kevin Oberman) Date: Fri Apr 25 20:29:00 2008 Subject: Dial-up Networking with Verizon and Treo In-Reply-To: Your message of "Fri, 25 Apr 2008 14:58:14 EDT." <20080425185238.M24089@swaggi.com> Message-ID: <20080425202854.E5BD645010@ptavv.es.net> > From: "Yuri Lukin" > Date: Fri, 25 Apr 2008 14:58:14 -0400 > > On Fri, 25 Apr 2008 10:35:33 -0700, Kevin Oberman wrote > > I have a Verizon Wireless Palm 755p with which I can connect my > > laptop to the Internet under Windows. I would really like to be able > > to do this under FreeBSD, but I have no idea of what the appropriate > > USB driver would be or how PPP would be configured for it. The > > Verizon software does not even have an account name or password for > > the connection. > > > > Has anyone managed to get this to work? I suspect any Treo on Verizon > > would connect in much the same manner. > > -- > > > I did this with my old Verizon Motorola phone several years ago via Bluetooth. > I paired my laptop (6.0-RELEASE afaik) with the phone and used it as a modem > to dial-up to Verizon's network. The speed wasn't great (EVDO) but it worked. > Verizon phones dial #777 for a data connection where the username is > your_10_digit_number@vzw3g.com and the password is vzw. Don't think you need > the cable/dongle as long as your 755p supports DUN via bluetooth. I have a > 700wx myself but haven't tried this yet. This might do the trick! Now I have a username and password, so I'll give it another try. Thanks! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 224 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080425/e9ba63a6/attachment.pgp From jordan at jordancoleman.com Fri Apr 25 21:52:11 2008 From: jordan at jordancoleman.com (Jordan Coleman) Date: Fri Apr 25 21:52:15 2008 Subject: "International" channels on a CM9 In-Reply-To: <200804240842.16865.asstec@matik.com.br> References: <6B39D996-3A54-43FD-922F-C5883FA8B405@JordanColeman.com> <200804240842.16865.asstec@matik.com.br> Message-ID: On Apr 24, 2008, at 7:42 AM, AT Matik wrote: >> I have an embedded system that contains a Wistron CM9 802.11 card, >> purchased in the US. After extensive testing in the US, the unit is >> now being installed in Europe, where 802.11b/g channels 1-13 are >> employed. How can I enable channels 12 and 13 on this hardware, >> which >> currently seems to only be able to use the "US" channels, 1-11? > on some cards it is possible to achieve by setting the country code > at boot > time (sysctl in loader.conf) on others not sysctl shows countrycode=0, regdomain=0. I can change the countrycode to other (valid) settings, but I have a feeling that setting that at runtime is already too late. > there is a way again on some cards to tweak the card's eprom memory > to get the > extended channels It was my impression based on the research I did before purchasing the card that there aren't multiple SKUs representing hardware for different regions -- just the one card which can cover the full range of frequencies. Is that not the case with the CM9? > you can try attached exec which should run on i386 at least on 5.3 > and perhaps > 6... (i don't remember) > > in order to do it you need to boot with the card installed in single > user mode > and after setting reboot to see if it works If I do end up having to make an EEPROM change, single-user mode isn't an easy option in this case. The hardware is built into a weathertight box mounted on the outside of a structure; there's no console. The system boots via PXE and mounts its root filesystem via NFS, though, and I have remote power control as well, so I have fairly complete control over bootup. Is single-user strictly necessary? ++J From ml at t-b-o-h.net Sat Apr 26 02:43:36 2008 From: ml at t-b-o-h.net (Tuc at T-B-O-H.NET) Date: Sat Apr 26 02:44:00 2008 Subject: Dial-up Networking with Verizon and Treo Message-ID: <200804260243.m3Q2h9Zj014014@himinbjorg.tucs-beachin-obx-house.com> > > I have a Verizon Wireless Palm 755p with which I can connect my laptop > to the Internet under Windows. I would really like to be able to do this > under FreeBSD, but I have no idea of what the appropriate USB driver > would be or how PPP would be configured for it. The Verizon software > does not even have an account name or password for the connection. > > Has anyone managed to get this to work? I suspect any Treo on Verizon > would connect in much the same manner. > I've tried a few times to get the Treos recognized in the OS, if your running a fairly new version it should be in there. It'll show up on ucom0 . When I ran USB, I put in /etc/ppp/pp.conf : vzwenusb: set phone "#777" set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATZ OK AT\$QCMDR=3 OK AT\$QCQNC=0 OK \\dATDT\\T TIM EOUT 40 CONNECT" set authname 9175555505@vzw3g.com set authkey vzw set device /dev/ucom0 set speed 230400 add default HISADDR Then invoke /usr/sbin/ppp -ddial vzwenusb I've also done it with bluetooth. In /etc/rc.local : /etc/rc.bluetooth start ubt0 /usr/sbin/sdpd /usr/local/bin/sdptool add DUN /usr/sbin/rfcomm_pppd -s -C 1 -l rfcomm-server /sbin/sysctl net.inet.ip.forwarding=1 /sbin/ipnat -C /sbin/ipnat -f /usr/local/etc/rfcomm_ppd.nat.conf (I think there was something special about the sdptool I used, it was from sdp-1.5, maybe even with a modification from one of the list people...) In /etc/ppp/ppp.conf : rfcomm-server: set timeout 0 set lqrperiod 60 set ifaddr 10.0.0.1 10.0.0.2 255.255.255.0 enable lqr accept lqr # Do not use PPP authentication. Assume that # Bluetooth connection was authenticated already disable pap deny pap disable chap deny chap # Added by Tuc enable dns In /usr/local/etc/rfcomm_ppd.nat.conf: map wi0 10.0.0.2/32 -> 0/32 portmap tcp/udp auto map wi0 10.0.0.2/32 -> 0/32 You'll need to change the interface as appropriate. Tuc From oberman at es.net Sun Apr 27 03:35:35 2008 From: oberman at es.net (Kevin Oberman) Date: Sun Apr 27 03:35:37 2008 Subject: Dial-up Networking with Verizon and Treo In-Reply-To: Your message of "Fri, 25 Apr 2008 22:43:09 EDT." <200804260243.m3Q2h9Zj014014@himinbjorg.tucs-beachin-obx-house.com> Message-ID: <20080427033529.DCC0345010@ptavv.es.net> > From: "Tuc at T-B-O-H.NET" > Date: Fri, 25 Apr 2008 22:43:09 -0400 (EDT) > > > > > I have a Verizon Wireless Palm 755p with which I can connect my laptop > > to the Internet under Windows. I would really like to be able to do this > > under FreeBSD, but I have no idea of what the appropriate USB driver > > would be or how PPP would be configured for it. The Verizon software > > does not even have an account name or password for the connection. > > > > Has anyone managed to get this to work? I suspect any Treo on Verizon > > would connect in much the same manner. > > > I've tried a few times to get the Treos recognized in the OS, > if your running a fairly new version it should be in there. It'll > show up on ucom0 . > > When I ran USB, I put in /etc/ppp/pp.conf : > > vzwenusb: > set phone "#777" > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ > \"\" AT OK-AT-OK ATZ OK AT\$QCMDR=3 OK AT\$QCQNC=0 OK \\dATDT\\T TIM > EOUT 40 CONNECT" > set authname 9175555505@vzw3g.com > set authkey vzw > set device /dev/ucom0 > set speed 230400 > add default HISADDR > > > Then invoke > > /usr/sbin/ppp -ddial vzwenusb > > > I've also done it with bluetooth. > > In /etc/rc.local : > > /etc/rc.bluetooth start ubt0 > /usr/sbin/sdpd > /usr/local/bin/sdptool add DUN > /usr/sbin/rfcomm_pppd -s -C 1 -l rfcomm-server > /sbin/sysctl net.inet.ip.forwarding=1 > /sbin/ipnat -C > /sbin/ipnat -f /usr/local/etc/rfcomm_ppd.nat.conf > > (I think there was something special about the sdptool I > used, it was from sdp-1.5, maybe even with a modification from > one of the list people...) > > In /etc/ppp/ppp.conf : > > rfcomm-server: > set timeout 0 > set lqrperiod 60 > set ifaddr 10.0.0.1 10.0.0.2 255.255.255.0 > enable lqr > accept lqr > # Do not use PPP authentication. Assume that > # Bluetooth connection was authenticated already > disable pap > deny pap > disable chap > deny chap > # Added by Tuc > enable dns > > > In /usr/local/etc/rfcomm_ppd.nat.conf: > > map wi0 10.0.0.2/32 -> 0/32 portmap tcp/udp auto > map wi0 10.0.0.2/32 -> 0/32 > > > You'll need to change the interface as appropriate. > > Tuc Thanks for the suggestions, but no joy. I have not tried BT, but the USB idea is getting nowhere, so far. First, the Treo is detected just fine, but the devices created are cuaU0 and ttyU0, not ucom0. I tried those, but had no success in getting the Treo to dial. I just get an error setting the speed to 0. I tried connecting to the port with kermit, but I could not get it to respond at all. Any other ideas? Guess I'll try the BT next. Thanks again for taking the time to help. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 224 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080427/223f03d0/attachment.pgp From zkolic at sbb.co.yu Sun Apr 27 14:27:22 2008 From: zkolic at sbb.co.yu (Zoran Kolic) Date: Sun Apr 27 14:27:27 2008 Subject: Dial-up Networking with Verison and Treo In-Reply-To: <20080427120017.44A271065772@hub.freebsd.org> References: <20080427120017.44A271065772@hub.freebsd.org> Message-ID: <20080427140858.GA820@faust.net> > > vzwenusb: > > set phone "#777" > > set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ > > \"\" AT OK-AT-OK ATZ OK AT\$QCMDR=3 OK AT\$QCQNC=0 OK \\dATDT\\T TIM > > EOUT 40 CONNECT" > > set authname 9175555505@vzw3g.com > > set authkey vzw > > set device /dev/ucom0 > > set speed 230400 > > add default HISADDR > > Then invoke > > /usr/sbin/ppp -ddial vzwenusb > > I've also done it with bluetooth. > > In /etc/rc.local : > > /etc/rc.bluetooth start ubt0 > > /usr/sbin/sdpd > > /usr/local/bin/sdptool add DUN > > /usr/sbin/rfcomm_pppd -s -C 1 -l rfcomm-server > > /sbin/sysctl net.inet.ip.forwarding=1 > > /sbin/ipnat -C > > /sbin/ipnat -f /usr/local/etc/rfcomm_ppd.nat.conf > > Thanks for the suggestions, but no joy. I'll take a chance with ubt0. hccontrol -n ubt0hci inquiry /etc/rc.bluetooth stat ubt0 btsockstat If device found in /dev, nothing to stop you. :) Zoran From ml at t-b-o-h.net Sun Apr 27 17:16:54 2008 From: ml at t-b-o-h.net (Tuc at T-B-O-H.NET) Date: Sun Apr 27 17:16:56 2008 Subject: Dial-up Networking with Verizon and Treo In-Reply-To: <20080427033529.DCC0345010@ptavv.es.net> Message-ID: <200804271716.m3RHGNS4049288@himinbjorg.tucs-beachin-obx-house.com> > Thanks for the suggestions, but no joy. > > I have not tried BT, but the USB idea is getting nowhere, so far. > > First, the Treo is detected just fine, but the devices created are cuaU0 > and ttyU0, not ucom0. I tried those, but had no success in getting the > Treo to dial. I just get an error setting the speed to 0. I tried > connecting to the port with kermit, but I could not get it to respond at > all. > What program are you using on the Treo side? I use WModem and it really works well. I do it on a 600 and 650, but not sure it'll go to a 700 or above. It may be that your not putting the Treo into a "teathering" mode. Tuc From gamato at users.sf.net Tue Apr 29 19:22:57 2008 From: gamato at users.sf.net (martinko) Date: Tue Apr 29 19:23:02 2008 Subject: battery monitor with KDE 64 bit In-Reply-To: References: <480E41FB.2080503@users.sf.net> Message-ID: <48177585.3040103@users.sf.net> Ian Smith wrote: > On Tue, 22 Apr 2008, mato wrote: > > Ian Smith wrote: > > > FWIW, I've also long used sysutils/ascpu as a 60sec visual load monitor, > > > matching asapm's 'look', res. size and low cpu usage. At ~7days uptime: > > > > > > 3680 smithi 8 0 2344K 448K nanslp 44:06 0.00% 0.00% asapm > > > 3681 smithi 8 0 2564K 448K nanslp 41:53 0.00% 0.00% ascpu > > > 3514 root 96 0 1280K 264K select 36:32 0.00% 0.00% moused > > > > > > > > > > There's something wrong with asapm or with my system -- I configured > > asapm for 5 seconds updating (as opposed to default 1s) and after 3 > > hours of uptime it already consumed 30 CPU-seconds. (!) > > Yeah Martin, that seems a lot; mine's using ~6 seconds per day. Perhaps > to do with running on amd64 rather than i386, though I've no idea why, > unless it's much busier with ACPI than with APM. > > Might be worth trying with the explicit -acpi switch, in case it tries > using the apm-over-acpi calls on your system? Pure speculation .. > > Are you running any commands on any conditions from the resource file? > I don't use ~/.asapmrc at all, just run 'asapm -lower forestgreen'. > Funny.. when I run it with -acpi I get the following: $ asapm -withdrawn -u 5 -acpi asapm: Neither ACPI nor APM are available! and it quits. When run w/o -acpi it works OK. Hm.. M. PS: I do use ~/.asapmrc but I don't think that is the culprit as asapm consumes CPU even when there are no actions triggered (always running on AC power).