Nabble - freebsd-mobile

Re: wpi and suspend/resume

2009-12-23T02:50:46Z

Quoting Frank Staals <frank@...>:

> Hey everyone,
>
> Is anyone running a system with a wireless card using the wpi driver
> that can successfully suspend/resume ? I have a Dell Latitude D630
> running FreeBSD 8-STABLE on amd64, the system suspends and resumes fine
> ( acpiconf -s3 ). However after bringing it back up wpi0 refuses to
> reconnect to a network:
>
> frank@Rena# uname -a
> FreeBSD Rena.FStaals.LAN 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu Dec 10
> 21:06:05 CET 2009
> frank@...:/home/obj/usr/src/sys/RENAKERNEL amd64
>
> When I resume the system the following error message is printed to dmesg:
>
> Dec 18 21:34:29 Rena kernel: wpi0: fatal firmware error
> Dec 18 21:34:29 Rena kernel: wpi0: timeout resetting Rx ring
>
> I tried bringing the interface down and up again (ifconfig wpi0 down up
> ) and reassociate with wpa_cli. Unfortunately after resuming wpi simply
> won't reconnect again. It is very nice that my system actually
> successfully suspends and resumes for the rest, but without networking
> connectivity ( if_bge is also dead after a suspend ) uses are rather
> limited. So is anyone successfully resuming with a system using the wpi
> driver ?
>
>

You could try to unload the module before you go to standby and reload
it after resuming.

attachment0 (202 bytes) Download Attachment

Re: iwi connect problems in 9.0-CURRENT

2009-12-22T15:13:56Z

Paul B Mahol wrote:

> On 11/23/09, Rui Paulo<rpaulo@...> wrote:
>> On 22 Nov 2009, at 23:39, michael brindle wrote:
>>>
>>> So, my questions are:
>>> Why is txpower set to 0, what does that mean? That it can't transmit at
>>> all?
>>
>> No, it could just be that the driver is providing wrong tx power
>> information.
>
> No, because regdomain is not set txpower is always reported to be 0.
>
> iwi driver doesn't have TXPMGT cap (looks to be bug), so you can not set
> txpower at all because net80211 thinks it is not supported.

I can confirm that "the bug" is also in 8.0-RELEASE and that on 6.x
txpower was non-zero (100 IIRC).

Also, I'm seeing other issues ...

1) During boot wireless interface is too slow to associate and I'm
seeing connection errors from other programs (e.g. ntpd). This was not
the case with 6.x releases.

2) The following began appearing in the system log:
kernel: iwi0: need multicast update callback

Also wpa_supplicant(8) generates quite a lot of messages (it did none
before). Some of them seems interesting while others not (to me).

I hope someone will fix the issues (although they're not critical).

With regards,

Martin

_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: iwi connect problems in 9.0-CURRENT

2009-12-22T14:59:57Z

michael brindle wrote:
> Hey all.
> I recently upgraded to 9.0-CURRENT from 7.2-RELEASE, to help test and debug
> it.
> The only problem I've encountered so far that I've not yet been able to fix
> is that I have yet to get my wireless card (Intel IPW 2200 b/g) to connect
> to my wireless network (which has an Apple Airport as the wireless router).
>

Hallo, I've just upgraded to 8.0-release and I'm seeing some issues too.

> my /etc/rc.conf file (with unrelated parts deleted):
> wlans_iwi0="wlan0"
> defaultroute=192.168.1.1
> ifconfig_wlan0="up"
> ifconfig_wlan0="DHCP"
>
> my /etc/start_if.wlan0 file:
> ifconfig wlan0 ssid BrinNet channel 1 authmode shared wepmode on wepkey PASS
> weptxkey 1
>

First, off-topic, I'm wondering why you do it as above .. ?

These 2 lines are IMHO unnecessary:
defaultroute=192.168.1.1
ifconfig_wlan0="up"

Also, you could get rid off of /etc/start_if.wlan0 and use
wpa_supplicant(8) that is very convenient and powerful.

> with the license agreed to, as stated in the iwi(4) man page.
>
> dhclient will discover my network. However, it won't get any offers from it.
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping
>
> Another thing I noticed, the output of ifconfig wlan0
> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> ether 00:0e:35:20:37:0a
> inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
> media: IEEE 802.11 Wireless Ethernet autoselect mode 11b
> status: associated
> ssid BrinNet channel 1 (2412 Mhz 11b) bssid 00:60:1d:f1:51:1b
> country US authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit
> txpower 0 bmiss 24 scanvalid 60 wme
>
> most importantly, the txpower being set to 0, because I cannot change it at
> all, or even reconfirm that it's at 0:
> younata# ifconfig wlan0 txpower 1
> ifconfig: SIOCS80211: Operation not supported
> younata# ifconfig wlan0 txpower 0
> ifconfig: SIOCS80211: Operation not supported
>
> So, my questions are:
> Why is txpower set to 0, what does that mean? That it can't transmit at all?
> Why can I not manually change it?
> Which leads to the ultimate question of:
> How do I get it to connect?
>

The same here -- txpower is zero while it used to be non-zero before (on
6.x). Seems like a bug or something.

Regards,

Martin

_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

wpi and suspend/resume

2009-12-22T09:13:50Z

Hey everyone,

Is anyone running a system with a wireless card using the wpi driver
that can successfully suspend/resume ? I have a Dell Latitude D630
running FreeBSD 8-STABLE on amd64, the system suspends and resumes fine
( acpiconf -s3 ). However after bringing it back up wpi0 refuses to
reconnect to a network:

frank@Rena# uname -a
FreeBSD Rena.FStaals.LAN 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu Dec 10
21:06:05 CET 2009
frank@...:/home/obj/usr/src/sys/RENAKERNEL amd64

When I resume the system the following error message is printed to dmesg:

Dec 18 21:34:29 Rena kernel: wpi0: fatal firmware error
Dec 18 21:34:29 Rena kernel: wpi0: timeout resetting Rx ring

I tried bringing the interface down and up again (ifconfig wpi0 down up
) and reassociate with wpa_cli. Unfortunately after resuming wpi simply
won't reconnect again. It is very nice that my system actually
successfully suspends and resumes for the rest, but without networking
connectivity ( if_bge is also dead after a suspend ) uses are rather
limited. So is anyone successfully resuming with a system using the wpi
driver ?

--

- Frankn
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Atheros AR9281 still not supported?

2009-12-21T07:34:54Z

So I take it that the newer Atheros chipsets are still not supported in
FreeBSD 8? I thought I saw a rumor a while ago that they would be but
now I can't track it down and of course the BugBusting page shows this
series as still unsupported.

Unfortunately I'm having a problem with my formerly trusty ar5212
interface since I upgraded (hangs, can't reset, error "ath_chan_set:
unable to reset channel 36 (5180 Mhz, flags 0x140), hal status 3") so I
was hoping to use the builtin interface, but it appears that's out.
Please correct me if I'm wrong. Thanks.
--
Frank Mayhar frank@... http://www.exit.com/
http://www.exit.com/blog/frank/
http://www.zazzle.com/fmayhar*
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Important: Please verify your email address

2009-12-20T17:37:16Z

IMPORTANT: Please click on the link below to verify your email address:

http://www.bebo.com/T/4.fd8A5eFdS2a5uUtjTj5uEg/verify/10240484795a865203806

If you did not enter your email address and are not a member of Bebo please click below:

http://www.bebo.com/T/4.fd8A5eFdS2a5uUtjTj5uEg/notmine/10240484795a865203806

......................................................................
Please do not reply directly to this email.
Questions? Contact us - http://www.bebo.com/T/4.fd8A5eFdS2a5uUtjTj5uEg/contactus

Bebo, Inc., 795 Folsom St, #250, San Francisco, CA 94107, USA.
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: Thinkpad T23 60 second stall on resuming 8.0-RELEASE/i386

2009-12-18T07:33:49Z

On Tue, 15 Dec 2009, Nate Lawson wrote:
> Ian Smith wrote:
> > Hi,
> >
> > Precis: suspend by Fn-F4 or acpiconf -s3 works as usual. When resuming
> > by hitting Fn or raising the lid, however, the screen comes back on but
> > then system freezes for pretty well exactly 60 seconds before responding
> > to anything, after which it seems to be fine, although top shows running
> > processes' TIME havig being reset to 00:00 (sometimes, not always)
>
> > -wakeup from sleeping state (slept 00:00:07)
> > +t_delta 15.f9ad99f01204edd8 too short <<<<<<<
> > +t_delta 16.07bb5b66ef900000 too long <<<<<<<
> > +t_delta 15.f9ad90918acc0000 too short <<<<<<<
> > +ct_to_ts([2009-12-13 17:10:39]) = 1260724239.000000000
> > +wakeup from sleeping state (slept 00:01:07)
> > ata0: reiniting channel ..
> > ata0: reset tp1 mask=03 ostat0=50 ostat1=00
> > ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> > ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00
> > -ata0: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
> > +ata0: reset tp2 stat0=50 stat1=00 devices=0x1
> > ad0: setting PIO4 on ICH3 chip
> > ad0: setting UDMA100 on ICH3 chip
> > ata0: reinit done ..
> > @@ -36,7 +37,7 @@
> > ata1: reset tp1 mask=03 ostat0=00 ostat1=00
> > ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
> > ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00
> > -ata1: reset tp2 stat0=00 stat1=00 devices=0x4<ATAPI_MASTER>
> > +ata1: reset tp2 stat0=00 stat1=00 devices=0x10000
>
> I think it's ATA timing out for some reason.

Thanks Nate. I nearly clipped that part of the diff, figuring only the
<*_MASTER> messages had changed, but I now see ata1 devices differ too.

Have similar regressions re ATA been turning up elsewere, do you know?

I've been digging, still on the trail of those t_delta messages, but now
figure these might be spurious, some timecounter missing/gaining a tick
or something, if ATA is maybe what's hanging meanwhile?

There's no HD light activity at all from resume button/switch through
that 60 second wait, when 15? seconds after the third t_delta line is
written to console, the HD light flashes while apparently simultaneously
writing the rest of the resume messages, and it comes alive.

Guess I should next upgrade the 7.0-R slice to 7.2-STABLE to find out if
this problem has been mfc'd :)

cheers, Ian
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: Thinkpad T42p sound stopped working.[Solved]

2009-12-17T23:04:12Z

Understudy wrote:

> Hi,
>
> I recently had my sound stop working. It was fine and today it decided
> to just stop. I threw in my old hard drive and sound worked fine on that.
>
> So lets go over what I have here.
> Thinkpad T42p
> FreeBSD Gargoyle.brendhanhorne.com 7.2-RELEASE FreeBSD 7.2-RELEASE #0:
> Tue Aug 11 08:51:16 EDT 2009
> root@...:/usr/obj/usr/src/sys/STONE i386
>
> Gargoyle# cat /dev/sndstat
> FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386)
> Installed devices:
> pcm0: <Intel ICH4 (82801DB)> at io 0xc0000c00, 0xc0000800 irq 11 bufsz
> 16384 [MPSAFE] (1p:1v/1r:1v channels duplex default)
>
> Gargoyle# ll /dev/dsp*
> crw-rw-rw- 1 root wheel 0, 107 Dec 17 21:12 /dev/dsp0.0
>
> In my kernel
> # Sound support
> device sound
> device snd_ich
>
> dmesg
> pcm0: <Intel ICH4 (82801DB)> port 0x1c00-0x1cff,0x18c0-0x18ff mem
> 0xc0000c00-0xc0000dff,0xc0000800-0xc00008ff irq 11 at device 31.5 on pci0
>
> Gargoyle# cat .history > /dev/dsp
> produces no static sound at all.
>
>
> So what I can I do now?
>
> Sincerely,
> Brendhan
>
>
> _______________________________________________
> freebsd-mobile@... mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
> To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."
>

Well I found the problem.

In mixer the pcm was set at 0. I changed it to 99, I did not make any
changes that would have put it at 0 so I don't know how it happened.
However the problem is gone and sound is working.

Sincerely,
Brendhan

_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Thinkpad T42p sound stopped working.

2009-12-17T19:00:26Z

Hi,

I recently had my sound stop working. It was fine and today it decided
to just stop. I threw in my old hard drive and sound worked fine on that.

So lets go over what I have here.
Thinkpad T42p
FreeBSD Gargoyle.brendhanhorne.com 7.2-RELEASE FreeBSD 7.2-RELEASE #0:
Tue Aug 11 08:51:16 EDT 2009
root@...:/usr/obj/usr/src/sys/STONE i386

Gargoyle# cat /dev/sndstat
FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386)
Installed devices:
pcm0: <Intel ICH4 (82801DB)> at io 0xc0000c00, 0xc0000800 irq 11 bufsz
16384 [MPSAFE] (1p:1v/1r:1v channels duplex default)

Gargoyle# ll /dev/dsp*
crw-rw-rw- 1 root wheel 0, 107 Dec 17 21:12 /dev/dsp0.0

In my kernel
# Sound support
device sound
device snd_ich

dmesg
pcm0: <Intel ICH4 (82801DB)> port 0x1c00-0x1cff,0x18c0-0x18ff mem
0xc0000c00-0xc0000dff,0xc0000800-0xc00008ff irq 11 at device 31.5 on pci0

Gargoyle# cat .history > /dev/dsp
produces no static sound at all.

So what I can I do now?

Sincerely,
Brendhan

_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: Thinkpad T23 60 second stall on resuming 8.0-RELEASE/i386

2009-12-15T18:46:50Z

Ian Smith wrote:
> Hi,
>
> Precis: suspend by Fn-F4 or acpiconf -s3 works as usual. When resuming
> by hitting Fn or raising the lid, however, the screen comes back on but
> then system freezes for pretty well exactly 60 seconds before responding
> to anything, after which it seems to be fine, although top shows running
> processes' TIME havig being reset to 00:00 (sometimes, not always)

> -wakeup from sleeping state (slept 00:00:07)
> +t_delta 15.f9ad99f01204edd8 too short <<<<<<<
> +t_delta 16.07bb5b66ef900000 too long <<<<<<<
> +t_delta 15.f9ad90918acc0000 too short <<<<<<<
> +ct_to_ts([2009-12-13 17:10:39]) = 1260724239.000000000
> +wakeup from sleeping state (slept 00:01:07)
> ata0: reiniting channel ..
> ata0: reset tp1 mask=03 ostat0=50 ostat1=00
> ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
> ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00
> -ata0: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
> +ata0: reset tp2 stat0=50 stat1=00 devices=0x1
> ad0: setting PIO4 on ICH3 chip
> ad0: setting UDMA100 on ICH3 chip
> ata0: reinit done ..
> @@ -36,7 +37,7 @@
> ata1: reset tp1 mask=03 ostat0=00 ostat1=00
> ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
> ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00
> -ata1: reset tp2 stat0=00 stat1=00 devices=0x4<ATAPI_MASTER>
> +ata1: reset tp2 stat0=00 stat1=00 devices=0x10000

I think it's ATA timing out for some reason.

--
Nate

_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

8.0 hangs at boot time Thinkpad x32

2009-12-15T00:31:31Z

Hi there,

try to install 8.0-R on TP X32 with a 250GB WD HDD (WDC WD2500BEVE-00WZT0
250G)
from an external USB cdrom.

After probing ad0 it recognizes ad0 but then it freezes with HDD LED
burning.

OK, ACPI disabled, short time after entering the Standard procedure it
freezes.

Same problem with 7.2-R

Under OpenBSD it works without any probs.

Any Suggestions?

TIA

André

_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: Problems with Intel 965 and compiz

2009-12-14T08:04:21Z

On Mon, 2009-12-14 at 05:26 +0000, Leonardo Santagostini wrote:

> Hello people,
>
> After googling a lot about my problem, i have no more remedy than posting a
> question here.
>
> The point is. I have X working perfect, but when i want to start compiz,
> title bars, go out.
>
> I have tried changing in Xorg.conf a lot of parameters regarding
> acceleration methods, i have probed changing various parameters with
> driconf, seting LIBGL_ALWAYS_INDIRECT to true, trying to change sync to
> vblanc. But without good results.
>
> Anybody has THE point regarding this issue ?

1) Make sure that everything is up to date. ports/kernel. You don't
say what kernel you are using, but any -STABLE should be fine. I don't
remember if all of the Intel fixes are in 7.2-RELEASE or not.

2) I'll attach an xorg.conf that I use on my Intel boxes that you can
use for reference. The key bits are AIGLX and Composite.

3) Get X up and running and then in an xterm run "compiz-manager". It
should handle probing and setting up all of the correct flags or at
least giving you an error that people can work with.

robert.

> Thanks a lot.
>
> Kind Regards,
> Leonardo Santagostini
> _______________________________________________
> freebsd-mobile@... mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
> To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."
--
Robert Noland <rnoland@...>
FreeBSD

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Mouse1" "SendCoreEvents"
InputDevice "Keyboard0" "CoreKeyboard"
Option "AIGLX"
#Option "AllowEmptyInput" "Off"
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "synaptics"
Option "Protocol" "alps"
Option "Device" "/dev/psm0"
Option "SHMConfig" "On"
Option "LeftEdge" "120"
Option "RightEdge" "830"
Option "TopEdge" "120"
Option "BottomEdge" "650"
Option "FingerLow" "14"
Option "FingerHigh" "15"
Option "MaxTapTime" "180"
Option "MaxTapMove" "110"
Option "EmulateMidButtonTime" "75"
Option "VertScrollDelta" "20"
Option "HorizScrollDelta" "20"
Option "CornerCoasting" "1"
Option "CoastingSpeed" "3"
Option "MinSpeed" "0.3"
Option "MaxSpeed" "0.75"
Option "AccelFactor" "0.015"
Option "EdgeMotionMinSpeed" "200"
Option "EdgeMotionMaxSpeed" "200"
Option "UpDownScrolling" "1"
Option "CircularScrolling" "1"
Option "CircScrollDelta" "0.1"
EndSection

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/sysmouse"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
#DisplaySize 340 270 # mm
Identifier "Monitor0"
VendorName "DEL"
ModelName "DELL 1708FP"
### Comment all HorizSync and VertRefresh values to use DDC:
#HorizSync 30.0 - 81.0
#VertRefresh 56.0 - 76.0
Option "DPMS"
Option "PreferredMode" "1440x900"
# Option "RightOf" "TMDS-1"
EndSection

Section "Monitor"
#DisplaySize 340 270 # mm
Identifier "Monitor1"
VendorName "DEL"
ModelName "DELL 1708FP"
### Comment all HorizSync and VertRefresh values to use DDC:
#HorizSync 30.0 - 81.0
#VertRefresh 56.0 - 76.0
Option "DPMS"
Option "PreferredMode" "1280x1024"
# Option "Position" "0 0"
EndSection

Section "Monitor"
#DisplaySize 340 270 # mm
Identifier "Monitor2"
VendorName "DEL"
ModelName "DELL 1708FP"
### Comment all HorizSync and VertRefresh values to use DDC:
#HorizSync 30.0 - 81.0
#VertRefresh 56.0 - 76.0
Option "DPMS"
Option "PreferredMode" "1280x1024"
# Option "RightOf" "TMDS-1"
EndSection

Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "Mobile GM965/GL960 Integrated Graphics Controller"
BusID "PCI:0:2:0"
Option "XvMC" "True"
#Option "AccelMethod" "UXA"
#Option "AccelMethod" "XAA"
#Option "XAANoOffscreenPixmaps"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Virtual 1680 1050
EndSubSection
EndSection

Section "DRI"
Group 0
Mode 0666
EndSection

_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Problems with Intel 965 and compiz

2009-12-13T21:26:19Z

Hello people,

After googling a lot about my problem, i have no more remedy than posting a
question here.

The point is. I have X working perfect, but when i want to start compiz,
title bars, go out.

I have tried changing in Xorg.conf a lot of parameters regarding
acceleration methods, i have probed changing various parameters with
driconf, seting LIBGL_ALWAYS_INDIRECT to true, trying to change sync to
vblanc. But without good results.

Anybody has THE point regarding this issue ?

Thanks a lot.

Kind Regards,
Leonardo Santagostini
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Invitation from Gaby B

2009-12-13T21:11:53Z

See my latest photos, updates and friends on Bebo.

Click to view my profile.

http://www.bebo.com/T/2.l9R2upAmSNanABAX_kmICg/inv/10217469056a567059498b9512435886c0d0e141

.......................................................................
This email was sent to you at the direct request of Gaby B <chihuo@...>. You have not been added to a mailing list.

If you would prefer not to receive invitations from ANY Bebo members please click here - http://www.bebo.com/T/2.l9R2upAmSNanABAX_kmICg/unsub/10217469056a567059498

Bebo, Inc., 795 Folsom St, #250, San Francisco, CA 94107, USA.
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Thinkpad T23 60 second stall on resuming 8.0-RELEASE/i386

2009-12-13T03:36:08Z

Hi,

Precis: suspend by Fn-F4 or acpiconf -s3 works as usual. When resuming
by hitting Fn or raising the lid, however, the screen comes back on but
then system freezes for pretty well exactly 60 seconds before responding
to anything, after which it seems to be fine, although top shows running
processes' TIME havig being reset to 00:00 (sometimes, not always)

Also, quite often (but only when verbose messages are off, it seems), I
see "calcru: time went backwards .." for devd (if powerd is running),
and once with X/KDE3 up I got a calcru: msg for every process running,
including init! I have logs of that, but think it an effect, not cause.

I've spent a while exploring this over the last 10 days, and now have a
solid pointer to the problem by comparing suspend/resume messages with
what happens on 7.0-R, which exhibits no such problem (nor did 6.1-R)

Here's a diff of a suspend/resume cycle between 7.0R and 8.0R, with the
problem delay messages marked <<<<<<< .. there are always 3 of these,
sometimes with the too long/short in different order, and they appear on
VTY0 screen while resuming every 15 seconds, with a further 15s delay
before posting the rest of the messages, then coming back to life.

The shortest 'slept' messages I get, by resuming straight away after it
suspends, is 00:00:04 on 7.0R and 00:01:04 on 8.0R, which makes sense as
there's a 3 second sleep in rc.suspend. Here I'd paused a few seconds:

--- 7.0_verb_sleep_7sec 2009-12-13 16:57:28.000000000 +1100
+++ 8.0_dmesg_sleep_01:07_delays.13Dec09 2009-12-13 17:13:56.000000000 +1100
@@ -1,34 +1,35 @@
-Trying to mount root from ufs:/dev/ad0s2a
-start_init: trying /sbin/init
-Linux ELF exec handler installed
-splash: image decoder found: green_saver
acpi_button0: sleep button pressed
acpi_lid0: wake_prep enabled for \\_SB_.LID_ (S3)
acpi_button0: wake_prep enabled for \\_SB_.SLPB (S3)
pci0:1:0:0: Transition from D0 to D3
pci0:2:8:0: Transition from D0 to D3
+ct_to_ts([2009-12-13 17:09:32]) = 1260724172.000000000
vga0: saving 68 bytes of video state
======== acpi_printcpu() debug dump ========
-gdt[0097:c0bfe5a0] idt[07ff:c0c00240] ldt[0050] tr[0048] efl[00080006]
-eax[0101e000] ebx[c215d300] ecx[00000000] edx[00000000]
-esi[00000000] edi[00080246] ebp[cc6a8bfc] esp[cc6a8bdc]
-cr0[8005003b] cr2[28207000] cr3[0101e000] cr4[00000691]
-cs[0020] ds[0028] es[0028] fs[0008] gs[003b] ss[0028]
+gdt[0097:c0dfb6a0] idt[07ff:c0e03d00] ldt[0050] tr[0048] efl[00080006]
+eax[0101e000] ebx[00000000] ecx[c101e000] edx[0101e000]
+esi[c2571900] edi[00080202] ebp[cd27cb54] esp[cd27cb34]
+cr0[8005003b] cr2[2815f930] cr3[0101e000] cr4[00000691]
+cs[0020] ds[0028] es[0028] fs[0008] gs[001b] ss[0028]
======== acpi_printcpu() debug dump ========
-gdt[0097:c0bfe5a0] idt[07ff:c0c00240] ldt[0050] tr[0048] efl[00000002]
-eax[c2119c01] ebx[00000001] ecx[00000001] edx[c2119c60]
-esi[00000000] edi[00080246] ebp[cc6a8bfc] esp[cc6a8bdc]
-cr0[8005003b] cr2[28207000] cr3[0101e000] cr4[00000691]
-cs[0020] ds[0028] es[0028] fs[0008] gs[003b] ss[0028]
+gdt[0097:c0dfb6a0] idt[07ff:c0e03d00] ldt[0050] tr[0048] efl[00000002]
+eax[c28e8601] ebx[00000000] ecx[00000004] edx[c28e86c0]
+esi[c2571900] edi[00080202] ebp[cd27cb54] esp[cd27cb34]
+cr0[8005003b] cr2[2815f930] cr3[0101e000] cr4[00000691]
+cs[0020] ds[0028] es[0028] fs[0008] gs[001b] ss[0028]
acpi_lid0: run_prep cleaned up for \\_SB_.LID_
acpi_button0: run_prep cleaned up for \\_SB_.SLPB
pci0:1:0:0: Transition from D3 to D0
-wakeup from sleeping state (slept 00:00:07)
+t_delta 15.f9ad99f01204edd8 too short <<<<<<<
+t_delta 16.07bb5b66ef900000 too long <<<<<<<
+t_delta 15.f9ad90918acc0000 too short <<<<<<<
+ct_to_ts([2009-12-13 17:10:39]) = 1260724239.000000000
+wakeup from sleeping state (slept 00:01:07)
ata0: reiniting channel ..
ata0: reset tp1 mask=03 ostat0=50 ostat1=00
ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00
-ata0: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
+ata0: reset tp2 stat0=50 stat1=00 devices=0x1
ad0: setting PIO4 on ICH3 chip
ad0: setting UDMA100 on ICH3 chip
ata0: reinit done ..
@@ -36,7 +37,7 @@
ata1: reset tp1 mask=03 ostat0=00 ostat1=00
ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb
ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00
-ata1: reset tp2 stat0=00 stat1=00 devices=0x4<ATAPI_MASTER>
+ata1: reset tp2 stat0=00 stat1=00 devices=0x10000
acd0: setting PIO4 on ICH3 chip
acd0: setting UDMA33 on ICH3 chip
ata1: reinit done ..

I've tested this many times without powerd (or indeed any other daemons)
running and that makes no difference, nor does not loading acpi_ibm.
Looking back I see these "t_delta .. time too short|long" messages were
being logged from the first suspend after the install.

I see they're emitted by /sys/kern/kern_tc.c but I've no idea what's
calling what during resume. Happy to test any patches etc of course.

BIOS and EC are the latest, flashed a month or so ago, which did solve a
whole bunch of ACPI boot messages appearing on 7.0-R.

Further information, though I think the above shows the issue best ..

http://smithi.id.au/7.0_dmesg_verbose.11Dec09
http://smithi.id.au/8.0_dmesg_verbose.13Dec09
http://smithi.id.au/7.0_verb_sleep_7sec
http://smithi.id.au/8.0_dmesg_sleep_01:07_delays.13Dec09

cheers, Ian
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: iwi: Possibly wrong interpretation of beacon->number in if_iwi.c?

2009-12-08T02:42:46Z

On Tue, 08-Dec-2009 at 01:05:21 +0000, Rui Paulo wrote:
> On 7 Dec 2009, at 16:36, Andre Albsmeier wrote:
> > What do people think?
>
>
> This could be a new firmware interface. You might want to check out
> how the latest Linux driver does this.

They do it the same way (comparing the whole 32bit ints).

I don't know about the firmware interface (no docs). Originally,
FreeBSD-6 and FreeBSD-7 use the same fw (V3.0). 8+ uses V3.1.

Our code in FreeBSD-6 is the same as in 7. I didn't have problems with
6 in the very same environment, however, I remember I had to raise
bmissthreshold a bit which means that I actually had missed beacons
(the whole code in question is only triggered on a beacon miss). I don't
have any problems at home where I am only 2m away from the AP (possibly
no missed beacons there).

I have also seen other people report similarly insane numbers. I have
also found reports on the net where the values were reasonable.

As I said, I use fw V3.1 and not the original V3.0. I did so in
FreeBSD-6 as well.

To summarise things, here are my observations of how beacon->number
behaves with different software:

fw3.0 fw3.1
FreeBSD-6 OK OK
FreeBSD-7 insane insane

"insane" means that in 99% of all cases beacon->number is something
like 0xabcdXYXY (abcd can be 0000).

Maybe someone who got the docs can jump in here.

-Andre
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: iwi: Possibly wrong interpretation of beacon->number in if_iwi.c?

2009-12-07T17:05:21Z

On 7 Dec 2009, at 16:36, Andre Albsmeier wrote:
> What do people think?

This could be a new firmware interface. You might want to check out
how the latest Linux driver does this.

--
Rui Paulo

_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Samsung Jet vs Samsung Tocco Ultra. Which one would you buy?

2009-12-07T13:38:46Z

What should i buy?

Samsung Jet or Samsung Tocco Ultra???
Or recommend me a phone for no more than £220?

Thanks.

free phones

iwi: Possibly wrong interpretation of beacon->number in if_iwi.c?

2009-12-07T08:36:07Z

I am currently using iwi in a rather difficult WLAN
environment (multiple APs on the same channel and weak
signals).

While trying to find out why iwi0 reassociates every 10 to
60 seconds I used sysctl debug.iwi=5 and logged (among
others) these messages:

...
Beacon state (1, 18941446)
Beacon miss: 18941446 >= 254
Beacon state (1, 18941703)
Beacon miss: 18941703 >= 254
Beacon state (1, 18941446)
...

Trying to understand what this means, I found the corresponding
code in /sys/dev/iwi/if_iwi.c:

if (le32toh(beacon->number) >= ic->ic_bmissthreshold) {
DPRINTF(("Beacon miss: %u >= %u\n",
le32toh(beacon->number),
ic->ic_bmissthreshold));
ieee80211_beacon_miss(ic);
}

le32toh(beacon->number) seems to be the number of missed
beacons. However, I have no idea how it can be that high
after an uptime of only a few minutes.

Could it be that only the LSB of this value is meaningful?

I added some debug code to if_iwi.c:

iwi0: Beacon miss: 19006982 1220606
iwi0: Beacon miss: 19006982 1220606
iwi0: Beacon miss: 19007239 1220707
iwi0: Beacon miss: 19007496 1220808
iwi0: Beacon miss: 19269126 1260606
iwi0: Beacon miss: 19269383 1260707
iwi0: Beacon miss: 19269640 1260808
iwi0: Beacon miss: 19269126 1260606
iwi0: Beacon miss: 19269383 1260707
iwi0: Beacon miss: 19269640 1260808
iwi0: Beacon miss: 19269897 1260909
iwi0: Beacon miss: 19270154 1260a0a
iwi0: Beacon miss: 19270411 1260b0b
iwi0: Beacon miss: 19269126 1260606
iwi0: Beacon miss: 19006982 1220606
iwi0: Beacon miss: 19006982 1220606
iwi0: Beacon miss: 19007239 1220707
iwi0: Beacon miss: 19006982 1220606
iwi0: Beacon miss: 19007239 1220707
iwi0: Beacon miss: 19007496 1220808
iwi0: Beacon miss: 19007753 1220909
iwi0: Beacon miss: 19008010 1220a0a
iwi0: Beacon miss: 19006982 1220606
iwi0: Beacon miss: 19007239 1220707
iwi0: Beacon miss: 19007496 1220808
iwi0: Beacon miss: 19007753 1220909

The second value is le32toh(beacon->number) converted to
hex and we see that the two least significant bytes are
always the same. This, and the fact that bmissthreshold
must be in the range 1 to 255, makes me assume that we
possibly should ignore the upper 24 bits.

I am now using this patch to if_iwi.c:

--- if_iwi.c.ORI 2009-12-07 16:17:46.000000000 +0100
+++ if_iwi.c 2009-12-07 16:20:10.000000000 +0100
@@ -1497,7 +1497,7 @@
/* XXX check struct length */
beacon = (struct iwi_notif_beacon_state *)(notif + 1);

- DPRINTFN(5, ("Beacon state (%u, %u)\n",
+ DPRINTFN(5, ("Beacon state (%u, 0x%x)\n",
beacon->state, le32toh(beacon->number)));

if (beacon->state == IWI_BEACON_MISS) {
@@ -1508,9 +1508,9 @@
* 802.11 layer.
* XXX try to roam, drop assoc only on much higher count
*/
- if (le32toh(beacon->number) >= ic->ic_bmissthreshold) {
+ if ((le32toh(beacon->number) & 0xFF) >= ic->ic_bmissthreshold) {
DPRINTF(("Beacon miss: %u >= %u\n",
- le32toh(beacon->number),
+ le32toh(beacon->number) & 0xFF,
ic->ic_bmissthreshold));
ieee80211_beacon_miss(ic);
}

and things got a lot better. After rising bmissthreshold to
50, which would be perfectly acceptable here, I got no more
problems.

All this is on a fresh 7.2-STABLE, however, I have upgraded
the fw in /sys/contrib/dev/iwi from V3.0 to V3.1 manually
(this has no effect on the problem mentioned above).

What do people think?

Thanks,

-Andre
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Buy the Lg ks360?

2009-12-06T10:39:16Z

Hi everyone,
I live in France and the new LG KS 360 has just been out here!
I've been thinking of buying it, does anyone have it or know somebody who does, to tell me if it's good ?
Thanks

free phones

Samsung Gloss u440 help please!

2009-12-02T13:26:00Z

I really want to buy this phone, but someone told me it can only hold 100 messages in the inbox, and that's a deciding factor for me. i hate having to delete my inbox every couple days and not being able to refer back to ones from more than 48 hours ago. If someone could PLEASE set me straight on how many messages this phone can really hold, I would be so grateful.

free phones

The new Nokia N97

2009-12-02T09:42:30Z

I just saw this phone called the nokia N97 in youtube, man its such a cool phone, I really really want to have this phone, when is this phone going to be out in the market, i hope soon. I'll bye this phone as soon as it comes because I really loved the video that I saw in youtube. Just can't wait anylonger for this baby to come in. I damn sure that this N97 is going to become the number 1 phone and it will definitely beat the market of the Sony Ericsson X1. Guys do you have any Idea on how much this phone will cost? I really need to know because I have to start saving for this high end phone.
I have read that N96 is a better phone that iphone, is that right? People also say that it has cooler and better features than iphone, ok one quick question, Does this phone really have a bigger or wider screen than iphone? I heard that the iphone has the biggest screen compare to any other touch screen phone, What do you guys think, is the N97 going to beat the apple iphone as well?

THANKS ALL AND GOOD LUCK............

free phones

Planning to buy Iphone - is a new iphone on its way?

2009-12-01T12:48:31Z

Hi,

Am planning to buy an iphone ... Is a new one to be launched soon? How soon? Should I wait for the new iPhone? Your advice will be much appreciated Thanks!

free phones

Re: Samsung Impression Escalating ring

2009-11-30T23:18:38Z

Quoting Randy Bush <randy@...>:

>> I recently got a Samsung impression and i set it to escalating ring
>> but not i
>> dont want it and i cant find where i can change it back ive downloaded the
>> manual but i cant seem to find it in there can anyone help me please
>
> perhaps you need to portupgrade -fv
>
> rand

Please don't answer that Samsung spam mails.
Thank you.

attachment0 (202 bytes) Download Attachment

Re: Samsung Impression Escalating ring

2009-11-30T18:41:14Z

> I recently got a Samsung impression and i set it to escalating ring but not i
> dont want it and i cant find where i can change it back ive downloaded the
> manual but i cant seem to find it in there can anyone help me please

perhaps you need to portupgrade -fv

rand
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: Mobile/Cell Phones, What you got?

2009-11-30T16:29:51Z

The original message was never even close to on-topic for this list.

Responding to spam and/or off-topic postings only encourages more of
the same. Please stop.

Thanks,

Doug
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Samsung Impression Escalating ring

2009-11-30T14:05:51Z

I recently got a Samsung impression and i set it to escalating ring but not i dont want it and i cant find where i can change it back ive downloaded the manual but i cant seem to find it in there can anyone help me please

cell phone

Has anyone used a 2G Iphone Sim Card in the 3G Iphone?

2009-11-30T14:05:09Z

I was just wondering if anyone has slipped another accounts 2G Iphone Sim card in a 3G iphone and what were the results?

I would really like a new IPhone. But since I don't have 3G in my area I see no reason to upgrade my service as of yet. Just curious if the old service will work on the new phone.

Thanks,

cell phone

Re: Mobile/Cell Phones, What you got?

2009-11-30T09:19:39Z

On Sun, 29 Nov 2009 21:32:59 -0700 (MST)
Warren Block <wblock@...> wrote:

> OP (not CCed) seems to be really curious, so much so that the exact
> same messages are posted in a lot of off-topic places:

Let me guess: spammers harvesting adresses again.
--
Regards,
Torfinn Ingolfsen

_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: Mobile/Cell Phones, What you got?

2009-11-29T20:32:59Z

On Mon, 30 Nov 2009, Ian Smith wrote:

> On Sun, 29 Nov 2009, Matthias Apitz wrote:
> > El d?a Sunday, November 29, 2009 a las 02:53:38PM +1100, Ian Smith escribi?:
> >
> > > Unless you're trying to get FreeBSD running on your phone, or using
> > > FreeBSD on your laptop to communicate with your phone, please refer to
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile

OP (not CCed) seems to be really curious, so much so that the exact same
messages are posted in a lot of off-topic places:

http://www.gamespot.com/pages/forums/show_msgs.php?topic_id=27114197
http://www.devhardware.com/forums/mobile-computing-75/mobile-cell-phones-what-you-got-267368.html
http://forums.mozillazine.org/viewtopic.php?f=47&t=1615985
http://www.the12volt.com/installbay/forum_posts.asp~TID~118059~PN~1
http://www.phonearena.com/forums/showthread.php?p=56812
http://www.everythingwm.com/forum/general-discussion/mobile-cell-phones-what-you-got-37253.html

The payload is a URL attachment, which was apparently stripped by
Mailman.

-Warren Block * Rapid City, South Dakota USA
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: Mobile/Cell Phones, What you got?

2009-11-29T19:43:01Z

On Sun, 29 Nov 2009, Matthias Apitz wrote:
> El día Sunday, November 29, 2009 a las 02:53:38PM +1100, Ian Smith escribió:
>
> > Unless you're trying to get FreeBSD running on your phone, or using
> > FreeBSD on your laptop to communicate with your phone, please refer to
> > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
>
> I'm using a Linux based cellphone, the OpenMoko Freerunner:
> http://wiki.openmoko.org/wiki/Main_Page
> it would be nice to change to OS from Linux to FreeBSD in this;

Be sure to let us know when you've got that done? :)

> but even with Linux it works very well together with my FreeBSD laptop:
> - you can SSH to the cellphone
> - you can connect with vncviewer to the cellphone and have its screen on
> your laptop
> - you can use the cellphone as a GPS router to Internet
> - you can use the GPSD in the cellphone and having the maps with
> tangoGPS in your laptop
> - ...
>
> all this (and more) is described here:
>
> http://www.unixarea.de/openmoko.txt
>
> and I gave a talk a year ago in the Havana (Cuba) local Linux User
> Group about how they work together (it's in Spanish but maybe from the
> pictures you will get an idea):
>
> http://www.unixarea.de/OpenMokoLiaHab/

Very interesting Matthias. I find Spanish easier to 'sort-of' follow
than German, smaller words perhaps .. lots of it made sense anyway.

Browsed through that while dd'ing the 8.0-R memstick image from my T23
Thinkpad (25 minutes at USB 1.0 :), wondering whether there were recipes
for a 7.2-R bootable USB image somewhere when I found your usbBoot.txt
there, using a more traditional slice arrangement I gather. Will study
this for the generic techniques.

(No 3G phones here, no coverage - the price of living in Nirvana - but
by the time I graduate to the old folks' home I'll probably need one :)

I'll save my adventures trying to install 8.0-R for another topic ..

Thanks, Ian
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Samsung Impression

2009-11-29T14:39:27Z

Hi! I bought an Impression last week. I'm usually a WinMobile person, and was hesitant to go with this phone. It's alright; a good, sturdy phone with long battery life - but I'm not finding many apps like I had on my Q. The apps I have downloaded, such as Google maps , are not working. The screen shows the map, has it's truncated touch menu up, but will not let me do anything on the screen with the map. Even to close it will not work. I have to close the entire thing.
Has anyone found any apps that work well with this phone? Has anyone else had similar problems?
It would also be wonderful to find an app to enter in calendar items from the PC that would transfer into the calendar on the phone. I don't need anything as fancy as outlook - just want something easier to manage for appointments, etc. Any suggestions?

iphones
gadgets
at&t

Re: NDIS problem on 8.0-RELEASE

2009-11-29T06:09:18Z

On Sun, 29 Nov 2009 11:00:49 +0100
Paul B Mahol <onemda@...> wrote:

> On 11/28/09, Alex <alex323@...> wrote:
> > On Sun, 29 Nov 2009 00:59:26 +0100
> > Paul B Mahol <onemda@...> wrote:
> >
> >> On 11/29/09, Alex <alex323@...> wrote:
> >> > Hello. I have been using wireless drivers generated from ndisgen
> >> > on 7.2 quite successfully. I installed 8.0-RELEASE, recompiled
> >> > the driver, and sadly wireless is not functioning:
> >> >
> >> > orion# wpa_supplicant -dd -Dndis -i ndis0
> >> > -c/etc/wpa_supplicant.conf ...
> >> > Initializing interface (2) 'ndis0'
> >> > NDIS: Packet.dll version: FreeBSD WinPcap compatibility shim v1.0
> >> > NDIS: 1 adapter names found
> >> > NDIS: 0 - - dummy description
> >> > NDIS: Could not find interface 'ndis0'
> >> > Failed to initialize driver interface
> >> > Failed to add interface ndis0
> >> > Cancelling scan request
> >> > Cancelling authentication timeout
> >> > orion# ifconfig ndis0
> >> > ndis0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
> >> > ether 00:24:2c:e7:2d:fd
> >> > media: IEEE 802.11 Wireless Ethernet autoselect
> >> > (autoselect) status: no carrier
> >> >
> >> > Does anyone know what is wrong? I wouldn't have expected an
> >> > upgrade to break previous functionality.
> >> >
> >>
> >> with 8.0 you need to create wlanX:
> >>
> >> # ifconfig wlan create wlandev ndis0
> >>
> >> and replace ndis0 with wlan0:
> >>
> >> # wpa_supplicant -dd -Dndis -i wlan0 -c/etc/wpa_supplicant.conf
> >
> > That appears to have helped, but for some reason wpa_supplicant
> > keeps looping through its internal states. For example it'll be
> > associated in one moment and disconnected in the next (after which
> > point it loops over and over). Does anything special need to be
> > done in rc.conf? wpa_supplicant.conf? I am using the same
> > wpa_supplicant.conf file that worked under 7.2.
>
> Could you post wpa_supplicant debug output?
>

The problem appears to be intermittent. However, I am connected via
wireless right now so I think this issue can be considered resolved.

> > Eventually I will need to set up rc.conf so that it automates the
> > process of creating wlan0 as well.
> >
> > Any insight you could provide would be much appreciated.
>
> wlans_ndis0="wlan0"
> ifconfig_wlan0="WPA SYNCDHCP"

That has worked successfully. Thank you very much. I only consulted the
FreeBSD handbook online for my information, and I had neglected to read
UPDATING far back enough.

--
Alex

signature.asc (201 bytes) Download Attachment

Re: NDIS problem on 8.0-RELEASE

2009-11-29T02:00:49Z

On 11/28/09, Alex <alex323@...> wrote:

> On Sun, 29 Nov 2009 00:59:26 +0100
> Paul B Mahol <onemda@...> wrote:
>
>> On 11/29/09, Alex <alex323@...> wrote:
>> > Hello. I have been using wireless drivers generated from ndisgen on
>> > 7.2 quite successfully. I installed 8.0-RELEASE, recompiled the
>> > driver, and sadly wireless is not functioning:
>> >
>> > orion# wpa_supplicant -dd -Dndis -i ndis0 -c/etc/wpa_supplicant.conf
>> > ...
>> > Initializing interface (2) 'ndis0'
>> > NDIS: Packet.dll version: FreeBSD WinPcap compatibility shim v1.0
>> > NDIS: 1 adapter names found
>> > NDIS: 0 - - dummy description
>> > NDIS: Could not find interface 'ndis0'
>> > Failed to initialize driver interface
>> > Failed to add interface ndis0
>> > Cancelling scan request
>> > Cancelling authentication timeout
>> > orion# ifconfig ndis0
>> > ndis0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
>> > ether 00:24:2c:e7:2d:fd
>> > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
>> > status: no carrier
>> >
>> > Does anyone know what is wrong? I wouldn't have expected an upgrade
>> > to break previous functionality.
>> >
>>
>> with 8.0 you need to create wlanX:
>>
>> # ifconfig wlan create wlandev ndis0
>>
>> and replace ndis0 with wlan0:
>>
>> # wpa_supplicant -dd -Dndis -i wlan0 -c/etc/wpa_supplicant.conf
>
> That appears to have helped, but for some reason wpa_supplicant keeps
> looping through its internal states. For example it'll be associated in
> one moment and disconnected in the next (after which point it loops
> over and over). Does anything special need to be done in rc.conf?
> wpa_supplicant.conf? I am using the same wpa_supplicant.conf file that
> worked under 7.2.

Could you post wpa_supplicant debug output?

> Eventually I will need to set up rc.conf so that it automates the
> process of creating wlan0 as well.
>
> Any insight you could provide would be much appreciated.

wlans_ndis0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."

Re: Mobile/Cell Phones, What you got?

2009-11-28T23:10:14Z

El día Sunday, November 29, 2009 a las 02:53:38PM +1100, Ian Smith escribió:

> Unless you're trying to get FreeBSD running on your phone, or using
> FreeBSD on your laptop to communicate with your phone, please refer to
> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile

I'm using a Linux based cellphone, the OpenMoko Freerunner:
http://wiki.openmoko.org/wiki/Main_Page
it would be nice to change to OS from Linux to FreeBSD in this;

but even with Linux it works very well together with my FreeBSD laptop:
- you can SSH to the cellphone
- you can connect with vncviewer to the cellphone and have its screen on
your laptop
- you can use the cellphone as a GPS router to Internet
- you can use the GPSD in the cellphone and having the maps with
tangoGPS in your laptop
- ...

all this (and more) is described here:

http://www.unixarea.de/openmoko.txt

and I gave a talk a year ago in the Havana (Cuba) local Linux User
Group about how they work together (it's in Spanish but maybe from the
pictures you will get an idea):

http://www.unixarea.de/OpenMokoLiaHab/

HIH

matthias

--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <guru@...> - w http://www.unixarea.de/
Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu
_______________________________________________
freebsd-mobile@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@..."