Re: Intel Centrino Wireless-N 1000 can't connect to AP

Hi. Can you paste the whole dmesg log from the time you start WPA supplicant up to when it crashes? I'd like to see what commands lead to the firmware crash. Thanks! Adrian On Dec 7, 2013 7:13 PM, "乔楚" wrote: > 1. > # uname -a > FreeBSD x201i.honestqiao.com 11.0-CURRENT FreeBSD 11.0-CURRENT #2

Re: Intel Centrino Wireless-N 1000 can't connect to AP

1. # uname -a FreeBSD x201i.honestqiao.com 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r259057M: Sun Dec 8 08:27:41 CST 2013 r...@x201i.honestqiao.com:/usr/obj/usr/src/sys/HonestQiaoKernel11 amd64 # pciconf -lv iwn0@pci0:2:0:0:class=0x028000 card=0x13158086 chip=0x00848086 rev=0x00 hdr=0x00

Re: Centrino Wireless N2230 support

Hi Adrian! Please commit the attached patch, to fix iwn2030 when compiled in to kernel. On 12/7/13, Adrian Chadd wrote: > Hi, > > I don't plan a backport of any of this just yet. > > I'd like to let the changes shake out a bit first. There's been some > reports about things not working between 1

Re: [Newcons] EDID message every second or 2?

Larry Rosenman написав(ла): >I'm getting the following: > >error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is >invalid, remainder is 128 >error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is >invalid, remainder is 128 >error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID che

Re: vtnet broken on -CURRENT when using VirtualBox

- Original Message - > Hi list, > I'm observing a 100%-reproducible panic in the following setup: > > Host system: FreeBSD 9.1-RELEASE-p7 amd64 > $ pkg info | grep virtualbox > virtualbox-ose-4.2.18_1A general-purpose full virtualizer for > x86 hardware > virtualbox-ose-kmod-4.2.

Re: [Newcons] EDID message every second or 2?

On 2013-12-07 18:07, Aleksandr Rybalko wrote: Hi Larry, Looks like you have display with broken info block (a.k.a. EDID). That message come from drm2 code, so you can to try to remove DRM debug flag from kernel config (if it there). Otherwise we have to find way to preload correct EDID. XOrg

[Newcons] EDID message every second or 2?

I'm getting the following: error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 12

[head tinderbox] failure on sparc64/sparc64

TB --- 2013-12-07 21:45:47 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-07 21:45:47 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013

Re: KGDB and kvm_write

On Sat, 07 Dec 2013 19:09:26 +0100 Hans Petter Selasky wrote: > Hi, > > Is there a particular reason that "set variable = value" is not > implemented when using kgbd from the command prompt? > > --HPS Just a thought: maybe you forgot -w on kgdb command line? -- Alexander Kabaev signature.

r259072 is not a happy camper...

I updated my "canary" machine to -current today and it's not a happy camper. Trying to run a buildworld on it I get the follwing reproducible panic: FreeBSD/amd64 (ni.freebsd.dk) (cuau0) login: lock order reversal: 1st 0xf8011641a9a0 ufs (ufs) @ /freebsd/head/sys/kern/vfs_lookup.c:518 2nd

vtnet broken on -CURRENT when using VirtualBox

Hi list, I'm observing a 100%-reproducible panic in the following setup: Host system: FreeBSD 9.1-RELEASE-p7 amd64 $ pkg info | grep virtualbox virtualbox-ose-4.2.18_1A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.2.18 VirtualBox kernel module for FreeBSD Sy

KGDB and kvm_write

Hi, Is there a particular reason that "set variable = value" is not implemented when using kgbd from the command prompt? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send

Re: Centrino Wireless N2230 support

Hi, I don't plan a backport of any of this just yet. I'd like to let the changes shake out a bit first. There's been some reports about things not working between 10.0 and 11.0 (eg, 5 minutes ago someone reported the centrino 100 doesn't work!) and I'd like to get those fixed before we consider a

Re: Intel Centrino Wireless-N 1000 can't connect to AP

A lot of work has gone on in -current with the iwn driver. It's quite possible that the recent changes has broken things. Would you please do this: * recompile with IWN_DEBUG defined in your kernel cofig * sysctl dev.iwn.0.debug=0x13ff (That turns on command debugging, tx/rx debugging, interrupt

Re: Centrino Wireless N2230 support

Hello Adrian, Am 04.11.2013 06:59, schrieb Adrian Chadd: > [snip] > > For what it's worth, I've started merging this stuff into -HEAD. > I've just installed 11.0-CURRENT r258208 on my Thinkpad E330 and the Wireless N2230 stuff is now in working condition. Thanks for your work - It's a pleasure

Intel Centrino Wireless-N 1000 can't connect to AP

Today ,I upgrade my freebsd from 10-beta4 to current. Now, my freebsd can't connect to wireless AP. Wireless LAN strike. iwn0 in /var/log/message: Dec 7 08:02:00 x201i kernel: iwn0: mem 0xf240-0xf2401fff irq 16 at device 0.0 on pci2 Dec 7 08:02:00 x201i kernel: iwn0: attempting to allocate

[head tinderbox] failure on sparc64/sparc64

TB --- 2013-12-07 09:33:13 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-07 09:33:13 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013