Re: X230 Intel Centrino Wireless-N 2200 not working
On 23 August 2015 at 19:26, Adrian Chadd wrote: > hi! > > nope - it looks like you had the whole transmit side get out of sync, > it threw a seqno != seqno error, then firmware panic. > > I wish i knew what else was lurking here to cause this :( > > Does it happen often? > > > -a > > **Ag - how I loath gmail sometimes!** Only once so far.. but I only installed a few days ago... I've actually ordered a 6205, cos I'd really like to run 10.2 and have some stability. I will try and use the laptop as much as possible between now and when it arrives from China. Is there anything else I can test, or things I could poke to try and provoke another panic to help diagnose the cause? Also, would it be of any use to ship the 2200 to someone on the dev team once my 6205 arrives? -- 0x2b || !0x2b ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: X230 Intel Centrino Wireless-N 2200 not working
hi! nope - it looks like you had the whole transmit side get out of sync, it threw a seqno != seqno error, then firmware panic. I wish i knew what else was lurking here to cause this :( Does it happen often? -a On 23 August 2015 at 05:56, Toby Slight wrote: > > On 23 August 2015 at 06:26, Adrian Chadd wrote: >> >> email -wireless with some info, and if it's something we can poke, >> file a bug at bugs.freebsd.org/submit >> > > Cool. Well since this is already going to -wireless, here's the exert from > my /var/log/messages. Do you think enabling acpi_ibm or coretemp might have > had anything to do with it? > > Aug 23 00:45:17 xbsd kernel: acpi_ibm0: on acpi0 > Aug 23 00:51:07 xbsd kernel: coretemp0: on cpu0 > Aug 23 00:51:07 xbsd kernel: coretemp1: > Aug 23 00:51:07 xbsd kernel: on cpu1 > Aug 23 00:51:07 xbsd kernel: coretemp2: on cpu2 > Aug 23 00:51:07 xbsd kernel: coretemp3: on cpu3 > Aug 23 00:54:58 xbsd kernel: iwn0: device timeout > Aug 23 00:54:58 xbsd kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 23 00:55:03 xbsd kernel: iwn0: iwn_tx_data: m=0xf800105a7b00: seqno > (11604) (84) != ring index (0) ! > Aug 23 00:55:03 xbsd kernel: iwn0: iwn_intr: fatal firmware error > Aug 23 00:55:03 xbsd kernel: firmware error log: > Aug 23 00:55:03 xbsd kernel: error type = "UNKNOWN" (0x102C) > Aug 23 00:55:03 xbsd kernel: program counter = 0xCEA8 > Aug 23 00:55:03 xbsd kernel: source line = 0x06A4 > Aug 23 00:55:03 xbsd kernel: error data = 0x00FE8000 > Aug 23 00:55:03 xbsd kernel: branch link = 0xCDBACDBA > Aug 23 00:55:03 xbsd kernel: interrupt link = 0xE1AE > Aug 23 00:55:03 xbsd kernel: time= 4610402 > Aug 23 00:55:03 xbsd kernel: driver status: > Aug 23 00:55:03 xbsd kernel: tx ring 0: qid=0 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 1: qid=1 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 2: qid=2 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 3: qid=3 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 4: qid=4 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 5: qid=5 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 6: qid=6 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 7: qid=7 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 8: qid=8 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 9: qid=9 cur=14 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 10: qid=10 cur=1 queued=1 > Aug 23 00:55:03 xbsd kernel: tx ring 11: qid=11 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 12: qid=12 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 13: qid=13 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 14: qid=14 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 15: qid=15 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 16: qid=16 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 17: qid=17 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 18: qid=18 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: tx ring 19: qid=19 cur=0 queued=0 > Aug 23 00:55:03 xbsd kernel: rx ring: cur=24 > Aug 23 00:55:03 xbsd kernel: iwn0: iwn_panicked: controller panicked, > iv_state = 5; resetting... > Aug 23 00:55:03 xbsd kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > > I was hoping to have a crash dump to poke at (or at least try and learn how > to poke at), but it seems that despite having dumpdev set to AUTO in > rc.conf, because I don't have sufficient swap space and/or because I'm using > a full ZFS system nothing was saved in /var/crash. > > Is there any other information that might be useful? And is this worth > filing an official bug report about? ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: X230 Intel Centrino Wireless-N 2200 not working
On 23 August 2015 at 06:26, Adrian Chadd wrote: > email -wireless with some info, and if it's something we can poke, > file a bug at bugs.freebsd.org/submit > > Cool. Well since this is already going to -wireless, here's the exert from my /var/log/messages. Do you think enabling acpi_ibm or coretemp might have had anything to do with it? Aug 23 00:45:17 xbsd kernel: acpi_ibm0: on acpi0 Aug 23 00:51:07 xbsd kernel: coretemp0: on cpu0 Aug 23 00:51:07 xbsd kernel: coretemp1: Aug 23 00:51:07 xbsd kernel: on cpu1 Aug 23 00:51:07 xbsd kernel: coretemp2: on cpu2 Aug 23 00:51:07 xbsd kernel: coretemp3: on cpu3 Aug 23 00:54:58 xbsd kernel: iwn0: device timeout Aug 23 00:54:58 xbsd kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 Aug 23 00:55:03 xbsd kernel: iwn0: iwn_tx_data: m=0xf800105a7b00: seqno (11604) (84) != ring index (0) ! Aug 23 00:55:03 xbsd kernel: iwn0: iwn_intr: fatal firmware error Aug 23 00:55:03 xbsd kernel: firmware error log: Aug 23 00:55:03 xbsd kernel: error type = "UNKNOWN" (0x102C) Aug 23 00:55:03 xbsd kernel: program counter = 0xCEA8 Aug 23 00:55:03 xbsd kernel: source line = 0x06A4 Aug 23 00:55:03 xbsd kernel: error data = 0x00FE8000 Aug 23 00:55:03 xbsd kernel: branch link = 0xCDBACDBA Aug 23 00:55:03 xbsd kernel: interrupt link = 0xE1AE Aug 23 00:55:03 xbsd kernel: time= 4610402 Aug 23 00:55:03 xbsd kernel: driver status: Aug 23 00:55:03 xbsd kernel: tx ring 0: qid=0 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 1: qid=1 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 2: qid=2 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 3: qid=3 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 4: qid=4 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 5: qid=5 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 6: qid=6 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 7: qid=7 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 8: qid=8 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 9: qid=9 cur=14 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 10: qid=10 cur=1 queued=1 Aug 23 00:55:03 xbsd kernel: tx ring 11: qid=11 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 12: qid=12 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 13: qid=13 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 14: qid=14 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 15: qid=15 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 16: qid=16 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 17: qid=17 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 18: qid=18 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: tx ring 19: qid=19 cur=0 queued=0 Aug 23 00:55:03 xbsd kernel: rx ring: cur=24 Aug 23 00:55:03 xbsd kernel: iwn0: iwn_panicked: controller panicked, iv_state = 5; resetting... Aug 23 00:55:03 xbsd kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 I was hoping to have a crash dump to poke at (or at least try and learn how to poke at), but it seems that despite having dumpdev set to AUTO in rc.conf, because I don't have sufficient swap space and/or because I'm using a full ZFS system nothing was saved in /var/crash. Is there any other information that might be useful? And is this worth filing an official bug report about? ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: X230 Intel Centrino Wireless-N 2200 not working
On Wed, Aug 19, 2015 at 02:41:35PM +0100, Toby Slight wrote: > Forgot to cc the lists on the last response - doh! > > On 19 August 2015 at 14:25, Lars Engels wrote: > > > On Wed, Aug 19, 2015 at 02:12:30PM +0100, Toby Slight wrote: > > > On 19 August 2015 at 13:43, Lars Engels wrote: > > > > > > > > > > > > HEAD is CURRENT, so 11.0-CURRENT is what you need. > > > > Don't worry, it's pretty stable. I'm running HEAD on my X230 since I > > > > bought it. No problems so far. > > > > > > > > > > Cool - cheers for the response Lars :-) I just fired up the -CURRENT > > > installer and was able to configure my wifi - fantastic. Guess I'm going > > to > > > be running FreeBSD -CURRENT for a while then I must say it was nice > > > that the the vt driver was enabled by default :-) > > > > Perfect! :-) Suspend / Resume should also work. I can show you my > > loader.conf / rc.conf settings to get things going, if you like. > > > > That would be amazing and much appreciated :-) Finding it quite a jump from > OpenBSD and Linux - got A LOT to learn! Of particular interest would be > whether or not you still have to add to Intel KMS flags to loader.conf and > what else needs to be added to get Xorg to work nice and reliablely... Does > TTY to X switching work now? I remember a few years ago I could get X > running on FreeBSD, but if I switched to a TTY, that was the end of me > being able to use my laptop screen! So, a little late, but here are the relevant settings for the X230. loader.conf: aesni_load="YES" autoboot_delay="1" loader_logo="beastie" kern.maxfiles="25000" kern.cam.boot_delay="2000" # Energy saving hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 hint.pcm.0.buffersize=65536 hint.pcm.1.buffersize=65536 hw.snd.feeder_buffersize=65536 hw.snd.latency=7 # Increase netgraph memory size for heavy VirtualBox network load net.graph.maxdata=65536 # experimental vfs.read_max=64 # Don't power devices with no driver attached hw.pci.do_power_nodriver=3 # APIC Timers block C3 hint.apic.0.clock=0 # Mute speaker when headphone jack is inserted and enable headphones dev.hdaa.0.nid26_config="as=1 seq=0" dev.hdaa.0.nid22_config="as=1 seq=15" # No memory tests at boot time hw.memtest.tests=0 hw.psm.trackpoint_support=1 #hw.psm.synaptics_support=1 # un-comment if you use the touchpad # Boot-time kernel tuning kern.ipc.shmseg=1024 kern.ipc.shmmni=1024 kern.maxproc=1 # Increase max stack size kern.maxssiz=1073741824 kern.vty=vt #power saving (HUGE difference) drm.i915.enable_rc6=7 debug.psm.loglevel=0 kern.vt.splash_cpu=1 kern.vt.splash_cpu_style=1 == rc.conf: moused_enable="YES" # Enable scrolling with 3rd mouse button moused_flags="-VH -U12 -L5" powerd_enable="YES" powerd_flags="-a hiadaptive -b hiadaptive" # Kernel Modules kld_list="acpi_ibm aio sem cuse coretemp libiconv libmchain cd9660_iconv msdosfs_iconv vmm nmdm" performance_cx_lowest="Cmax" economy_cx_lowest="Cmax" webcamd_enable="YES" smartd_enable="YES" autofs_enable="YES" == sysctl.conf: # Disable the system speaker kern.vt.enable_bell=0 # Tune for desktop usage kern.sched.preempt_thresh=224 # Enable shm_allow_removed (for Chromium) kern.ipc.shm_allow_removed=1 # Suspend when the lid is closed hw.acpi.lid_switch_state=s3 kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules # Enable acpi_ibm button events dev.acpi_ibm.0.events=1 # Increase audio volume hw.snd.vpc_0db=15 hw.snd.vpc_autoreset=0 # faster shutdown hw.usb.no_shutdown_wait=1 == rc.suspend [...] /usr/sbin/service powerd quietrestart /usr/sbin/service netif restart [...] == I don't know if all that is still needed on HEAD, but it's all running fine on my box. Lars pgpfacwBA_kde.pgp Description: PGP signature
Re: X230 Intel Centrino Wireless-N 2200 not working
email -wireless with some info, and if it's something we can poke, file a bug at bugs.freebsd.org/submit -a On 22 August 2015 at 17:26, Toby Slight wrote: > Hi again :-) > > I have been running -current for a few days with working wifi (Yay!) on my > X230 & 2200 card, and just had my first kernel panic - which was exiting! > > This seemed to be due to the iwn0 driver - at least that's what the messages > above the db prompt stated... > > However, I had, about 10 minutes before the panic, loaded the coretemp and > acpi_ibm kernel modules, so I wonder if they might have somehow had > something to do with it? > > Anyway, I just wanted to find out what the best way to report this is, and > how to best get and submit whatever info might be useful to the developers? > > Cheers, > > Toby > > On 19 August 2015 at 18:29, Toby Slight wrote: >> >> >> On 19 Aug 2015 17:37, "Michael B. Eichorn" wrote: >> >> > From what I hear freebsd-update probably will not implement this, >> > however >> > there is a possibility that some option might develop as a result of >> > packaging base, which is currently an active project. For more info >> > checkout the presentation @bapt gave at BSDCan 2015 [1] and the >> > interview >> > he gave on the BSDNow Podcast [2]. >> > >> > [1] Presentation (44 min): https://youtu.be/Br6izhH5P1I >> > Q&A (14 min): https://youtu.be/v7px6ktoDAI >> > [2] Interview (12 min): https://youtu.be/gDi09Wfx-9s?t=25m2s >> >> Nice! Many thanks for the links :-) > > > > > -- > 0x2b || !0x2b ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: X230 Intel Centrino Wireless-N 2200 not working
Hi again :-) I have been running -current for a few days with working wifi (Yay!) on my X230 & 2200 card, and just had my first kernel panic - which was exiting! This seemed to be due to the iwn0 driver - at least that's what the messages above the db prompt stated... However, I had, about 10 minutes before the panic, loaded the coretemp and acpi_ibm kernel modules, so I wonder if they might have somehow had something to do with it? Anyway, I just wanted to find out what the best way to report this is, and how to best get and submit whatever info might be useful to the developers? Cheers, Toby On 19 August 2015 at 18:29, Toby Slight wrote: > > On 19 Aug 2015 17:37, "Michael B. Eichorn" wrote: > > > From what I hear freebsd-update probably will not implement this, however > > there is a possibility that some option might develop as a result of > > packaging base, which is currently an active project. For more info > > checkout the presentation @bapt gave at BSDCan 2015 [1] and the interview > > he gave on the BSDNow Podcast [2]. > > > > [1] Presentation (44 min): https://youtu.be/Br6izhH5P1I > > Q&A (14 min): https://youtu.be/v7px6ktoDAI > > [2] Interview (12 min): https://youtu.be/gDi09Wfx-9s?t=25m2s > > Nice! Many thanks for the links :-) > -- 0x2b || !0x2b ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: X230 Intel Centrino Wireless-N 2200 not working
On 19 Aug 2015 17:37, "Michael B. Eichorn" wrote: > From what I hear freebsd-update probably will not implement this, however > there is a possibility that some option might develop as a result of > packaging base, which is currently an active project. For more info > checkout the presentation @bapt gave at BSDCan 2015 [1] and the interview > he gave on the BSDNow Podcast [2]. > > [1] Presentation (44 min): https://youtu.be/Br6izhH5P1I > Q&A (14 min): https://youtu.be/v7px6ktoDAI > [2] Interview (12 min): https://youtu.be/gDi09Wfx-9s?t=25m2s Nice! Many thanks for the links :-) ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: X230 Intel Centrino Wireless-N 2200 not working
On Wed, 2015-08-19 at 14:41 +0100, Toby Slight wrote: > Forgot to cc the lists on the last response - doh! > > On 19 August 2015 at 14:25, Lars Engels wrote: > > > On Wed, Aug 19, 2015 at 02:12:30PM +0100, Toby Slight wrote: > > > On 19 August 2015 at 13:43, Lars Engels > > > wrote: > > > > > > > > > > > > HEAD is CURRENT, so 11.0-CURRENT is what you need. > > > > Don't worry, it's pretty stable. I'm running HEAD on my X230 > > > > since I > > > > bought it. No problems so far. > > > > > > > > > > Cool - cheers for the response Lars :-) I just fired up the > > > -CURRENT > > > installer and was able to configure my wifi - fantastic. Guess I'm > > > going > > to > > > be running FreeBSD -CURRENT for a while then I must say it was > > > nice > > > that the the vt driver was enabled by default :-) > > > > Perfect! :-) Suspend / Resume should also work. I can show you my > > loader.conf / rc.conf settings to get things going, if you like. > > > > That would be amazing and much appreciated :-) Finding it quite a jump > from > OpenBSD and Linux - got A LOT to learn! Of particular interest would be > whether or not you still have to add to Intel KMS flags to loader.conf > and > what else needs to be added to get Xorg to work nice and reliablely... > Does > TTY to X switching work now? I remember a few years ago I could get X > running on FreeBSD, but if I switched to a TTY, that was the end of me > being able to use my laptop screen! > > > > > > > > How often do you tend to update on current? And I take it a full > > recompile > > > is necessary? No freebsd-update from what I remember reading on the > > > bsdnow.tv site? Is there no way to go from one snapshot to another > > without > > > either recompiling or nuking and paving, like there is on OpenBSD > > -current? > > > > I update kernel and world on an irregular basis. Something between 3 > > days and 3 weeks. My X230 has the Core i7 CPU and 16 GB RAM, so > > building > > both takes 1,5 to 2 hours. Then I run etcupdate(8), so merging the > > config files is mostly painless. (Be sure to run etcupdate before the > > first upgrade, so it can use your running config. > > freebsd-update only works on RELEASES, and can be slower than > > building > > from source anyways. > > > > > Cool - cheers for the tips. I dare say my builds will be a fair bit > slower > as my machine only has an i3 and 6GB RAM... Is freebsd-update ever > likely > to be made to work with the current and stable branches? Or maybe > something > like the OpenBSD -current update mechanism? From what I hear freebsd-update probably will not implement this, however there is a possibility that some option might develop as a result of packaging base, which is currently an active project. For more info checkout the presentation @bapt gave at BSDCan 2015 [1] and the interview he gave on the BSDNow Podcast [2]. [1] Presentation (44 min): https://youtu.be/Br6izhH5P1I Q&A (14 min): https://youtu.be/v7px6ktoDAI [2] Interview (12 min): https://youtu.be/gDi09Wfx-9s?t=25m2s > > > > > > > > How about pkgng? Do binary pkgs and binary pkg upgrades work on > > > -current? > > > > pkg works like a charm on HEAD. You usually get new packages every > > second day. There are only some ports which get built against kernel > > sources which need to be compiled from ports. Oh, and if you use > > Flash: > > Flash may not be distributed as a package, so you have to install and > > upgrade it from ports. > > > > > > > That's great, I'm fine with building the system, but if I then had to > go > and recompile all my packages I think I'd be noping out at that > point... > I've done my time on Gentoo - and don't relish the thought of staring > at > walls of text for days on end any more! > > smime.p7s Description: S/MIME cryptographic signature
Re: X230 Intel Centrino Wireless-N 2200 not working
Forgot to cc the lists on the last response - doh! On 19 August 2015 at 14:25, Lars Engels wrote: > On Wed, Aug 19, 2015 at 02:12:30PM +0100, Toby Slight wrote: > > On 19 August 2015 at 13:43, Lars Engels wrote: > > > > > > > > > HEAD is CURRENT, so 11.0-CURRENT is what you need. > > > Don't worry, it's pretty stable. I'm running HEAD on my X230 since I > > > bought it. No problems so far. > > > > > > > Cool - cheers for the response Lars :-) I just fired up the -CURRENT > > installer and was able to configure my wifi - fantastic. Guess I'm going > to > > be running FreeBSD -CURRENT for a while then I must say it was nice > > that the the vt driver was enabled by default :-) > > Perfect! :-) Suspend / Resume should also work. I can show you my > loader.conf / rc.conf settings to get things going, if you like. > That would be amazing and much appreciated :-) Finding it quite a jump from OpenBSD and Linux - got A LOT to learn! Of particular interest would be whether or not you still have to add to Intel KMS flags to loader.conf and what else needs to be added to get Xorg to work nice and reliablely... Does TTY to X switching work now? I remember a few years ago I could get X running on FreeBSD, but if I switched to a TTY, that was the end of me being able to use my laptop screen! > > > > How often do you tend to update on current? And I take it a full > recompile > > is necessary? No freebsd-update from what I remember reading on the > > bsdnow.tv site? Is there no way to go from one snapshot to another > without > > either recompiling or nuking and paving, like there is on OpenBSD > -current? > > I update kernel and world on an irregular basis. Something between 3 > days and 3 weeks. My X230 has the Core i7 CPU and 16 GB RAM, so building > both takes 1,5 to 2 hours. Then I run etcupdate(8), so merging the > config files is mostly painless. (Be sure to run etcupdate before the > first upgrade, so it can use your running config. > freebsd-update only works on RELEASES, and can be slower than building > from source anyways. > > Cool - cheers for the tips. I dare say my builds will be a fair bit slower as my machine only has an i3 and 6GB RAM... Is freebsd-update ever likely to be made to work with the current and stable branches? Or maybe something like the OpenBSD -current update mechanism? > > > > How about pkgng? Do binary pkgs and binary pkg upgrades work on -current? > > pkg works like a charm on HEAD. You usually get new packages every > second day. There are only some ports which get built against kernel > sources which need to be compiled from ports. Oh, and if you use Flash: > Flash may not be distributed as a package, so you have to install and > upgrade it from ports. > > > That's great, I'm fine with building the system, but if I then had to go and recompile all my packages I think I'd be noping out at that point... I've done my time on Gentoo - and don't relish the thought of staring at walls of text for days on end any more! -- 0x2b || !0x2b ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: X230 Intel Centrino Wireless-N 2200 not working
On Wed, Aug 19, 2015 at 10:46:01AM +0100, Toby Slight wrote: > > > > > > please give a -HEAD snapshot on it and see if it works. :) > > > > > Ahh. I sort of suspected this might be the case ;-) Shame - I've been > running bleeding edge versions of various OSes on this thing for the last > couple of years and was hoping to have a break of stability on FreeBSD... > > Oh well, I'm still I'm pretty determined to run FreeBSD on this thing so > I'll do what it takes! However, I'm also unclear on what you mean by -HEAD. > Is that the 10.2-STABLE or the 11.0-CURRENT branch? Or either? HEAD is CURRENT, so 11.0-CURRENT is what you need. Don't worry, it's pretty stable. I'm running HEAD on my X230 since I bought it. No problems so far. pgpG2vQ2_q35m.pgp Description: PGP signature
Re: X230 Intel Centrino Wireless-N 2200 not working
> > > please give a -HEAD snapshot on it and see if it works. :) > > Ahh. I sort of suspected this might be the case ;-) Shame - I've been running bleeding edge versions of various OSes on this thing for the last couple of years and was hoping to have a break of stability on FreeBSD... Oh well, I'm still I'm pretty determined to run FreeBSD on this thing so I'll do what it takes! However, I'm also unclear on what you mean by -HEAD. Is that the 10.2-STABLE or the 11.0-CURRENT branch? Or either? ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: X230 Intel Centrino Wireless-N 2200 not working
hi, please give a -HEAD snapshot on it and see if it works. :) Thanks! -a On 18 August 2015 at 18:23, Toby Slight wrote: > Hi there, > > I just tried to install FreeBSD 10.2 on my Thinkpad X230 after reading that > it was well supported here - https://wiki.freebsd.org/Laptops/Thinkpad_X230. > > The wifi card (Intel Centrino Wireless-N 2200) is supported by iwn > according to that page and this page - https://wiki.freebsd.org/dev/iwn(4). > > However before and after install ifconfig only shows the ethernet device > and the loopback. I tried adding if_iwn_load="YES" to loader.conf as > suggested by the man page, but the dmesg just came back saying the iwn is > already loaded... > > I came across some threads from way back in the 9.1 days ( > http://freebsd.1045724.n5.nabble.com/What-driver-should-I-use-for-intel-centrino-wireless-N-2200-BGN-td5750303.html) > and tried some of the driver loading suggestions there, on the off chance > they might still be applicable, but still no interfaces show up other than > ethernet and loopback. > > Is this device supported in 10.2, and if so what am I doing wrong? > > Cheers, > Toby > > -- > 0x2b || !0x2b > ___ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
