Re: dmesg submission service -- please submit today
On Sun, Oct 07, 2018 at 08:21:46AM -0600, Warner Losh wrote: > > Oh right. There's a known bug I should have mentioned: If your uname doesn't > have a '#' in it, the script will reject it. You can add #0+ after the ALPHA8 > and before the r339174 and it will work. I've reported this to the dmesg > guys. Thanks, I have submitted them. > > Warner ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: dmesg submission service -- please submit today
On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote: > On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote: > > > Greetings, > > > > As you can tell, the project is looking to clear some of the deadwood from > > its driver lists. One problem is that we have to guess what's in used based > > on our personal experience. This has proven to be less reliable than hoped > > in the 10/100 discussions that are going on now. > > > > So, to that end, I'd like to request as many people as possible submit > > their current dmesg to the service at http://dmesgd.nycbug.org/index.cgi > > so that we have a better basis for future preliminary lists of drivers for > > other parts of the tree. Please take the time to make these submissions > > regardless of what your current hardware is. Please submit for any machine > > you'd like to upgrade to FreeBSD 12 or 13. Identifying information is > > generally masked out. > > > > This is just a request by me. I'll be using the data in about a month to > > look at old parallel scsi driver use. Though not definitive, it will be > > suggestive of what's in use. The data is currently a bit thin, so I thought > > I'd see what a message like this could do to improve that situation. This > > should be viewed as a personal suggestion right now... > > > > Warner > > > > P.S. I know there's other user generated data sites out there, but this > > appears to be the only one that's actually still working. > > > > This one-liner works to submit, though you'll need to change username, > email and maybe tweak the description if your system doesn't have decent > smbios entries. It's also x86 centric, since other systems won't have this > information as readily available. > > curl -v -d "nickname=$USER" -d "email=$USER@$(hostname)" -d > "description=FreeBSD/$(uname -m) on $(kenv smbios.system.maker) $(kenv > smbios.system.product)" -d "do=addd" --data-urlencode > 'dmesg@/var/run/dmesg.boot' > http://dmesgd.nycbug.org/index.cgi When I try to submit (with the oneliner or web form), it fails with "Sorry, this is an unsupported OS. If you feel it should be added, please contact admin." dmesg is from FreeBSD 12.0-ALPHA8 r339174=b24b22909(master). > > Hope helps facilitate submission of entries. Thanks to Charles Sprickman > for the idea of using a curl one-liner. > > Warner > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Sharing compiled builds between multiple 12-CURRENT boxes.
On Mon, Aug 20, 2018 at 05:48:04AM -0700, Cy Schubert wrote: > Make sure the archs are the same. Make sure the src and obj pathnames > on both servers are exactly the same. Make sure /usr/src (or wherever > you put it) is the same, it too needs to be rsynced. > > The tiniest differences will lead to this error. Starting from a make clean and rsyncing fixed the problems, I can install and boot my laptop from the build on my server. Thanks! Dhananjay Balan ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Sharing compiled builds between multiple 12-CURRENT boxes.
On Sat, Aug 18, 2018 at 04:36:15PM -0700, Cy Schubert wrote: > You can use NFS or rsync. Make sure the src and obj path names are > exactly the same on all thes servers. I used to use NFS until a year or > two ago when I started using different patches on different machines. > On occasion I've used rsync followed by a NO_CLEAN, WORLDFAST, KERNFAST > build on the target machine or simply installkernel and installworld. > I had a quick try of this, with rsync. installkernel worked properly and I can boot, howver installworld fails with lot of $PROGRAM not found erroer for env, mktemp etc. Thanks for all the suggestions I will grok at the installworld a bit more, and will also give PkgBase a try. - Dhananjay Balan ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Sharing compiled builds between multiple 12-CURRENT boxes.
Hi, I run 12-CURRENT on few machines, some more powerful that other (all of them x86_64, march varies). Is there is a way to avoid building CURRENT on all machines? Rather than building everywhere, can I just build it on the big server that I have and copy and update my laptop? - Dhananjay Balan ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: em0 link fail
On Mon, Aug 06, 2018 at 11:48:47AM -0700, R. Tyler Croy wrote: > 173.228.82.255 > Aug 5 23:46:18 strawberry dhclient: New Routers (em1): 173.228.82.1 > Aug 5 23:46:19 strawberry syslogd: last message repeated 1 times > Aug 5 23:49:35 strawberry dhclient[12645]: send_packet: No route to host > > > At the tail end of the syslog I was trying to get a new lease but was then > unable to get a lease or restore functionality to the em1 device. > > > This is rather perplexing to me, but I'm not savvy enough to figure out how to > further be a useful debugger here :-/ > > Any suggestions would be appreciated! It seems that I am hitting similiar problems with em(4) on my X230. https://lists.freebsd.org/pipermail/freebsd-current/2018-August/070490.html - Dhananjay ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Ethernet troubles with X230
On Sun, Aug 05, 2018 at 06:25:57PM +0800, Erich Dollansky wrote: > when I ran into this problem, I delete the IP address 0.0.0.0, kill > dhclient and start a new dhclient. As we used fixed IP addresses for > em0, the problem comes up only on wlan. I tried that, but now the interface just gives up with no carrier, eventhough the cables are plugged in properly. sudo dhclient em0 em0: no link .. giving up This is with 12.0-ALPHA1 #18 r337684 and my dmesg(8) is filled with em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 - Dhananjay ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Ethernet troubles with X230
Hi, I have a problems with ethernet on my laptop (X230). pciconf(8) identifies the device as Intel 82579LM Gigabit Network Connection (Lewisville). 1. Resuming after a long suspend (~5hr), sometimes the machine can't get a DHCP IP. 2. After suspend, the ethernet device starts reporting no carrier, eventhough the cables are plugged in and if I plug it to a different box, they would work I can reproduce both on 12.0-CURRENT #17 r336576. But not sure when they started. I have seen this behaviour with 2 routeres running three firmwares at the other end. 1. Easybox (linux 2.x?) 2. Edgerouter lite running stock fw (linux 2.x) and 12-CURRENT (~3 months old) For Problem (1) DHCP lease: ifconfig shows: em0: flags=8843 metric 0 mtu 1500 options=81249b ether xx:xx:xx:xx:xx:xx inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 It still can't get an ip if I invoke service netif restart em0: flags=8843 metric 0 mtu 1500 options=81249b ether xx:xx:xx:xx:xx:xx inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: Ethernet autoselect (1000baseT ) status: active nd6 options=29 If I try running dhclient manually, [dhananjay:~] 1 % sudo dhclient em0 dhclient already running, pid: 14305. exiting. [dhananjay:~] 1 % sudo kill 14305 [dhananjay:~] % sudo dhclient em0 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 17 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 9 No DHCPOFFERS received. No working leases in persistent database - sleeping. For (2) For status no carrier em0: flags=8c03 metric 0 mtu 1500 options=81249b ether xx:xx:xx:xx:xx:xx media: Ethernet autoselect status: no carrier nd6 options=29 and dmesg keeps repeating em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 The only solution I have found so far is to just reboot the laptop and then everything starts working. FWIW the router led never blinks (no data transfers during DHCPDISCOVER). I am not sure how to debug this. - Dhananjay Balan ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can't seem to use 5GHz APs with Intel wireless
On Wed, Jun 13, 2018 at 08:29:06AM -0700, Adrian Chadd wrote: > hm. Which country are you in? india? > > It seems to think you're in the FCC4 regdomain and DE country, which > if I read it right won't give you 5G. So somehow it determined you're > in the "wrong" country? No it was entirely my fault. I had "country DE regdomain FCC4" set in my rc.conf. I don't remmeber why I set regulatory domain or why I explicitly chose FCC4. :-( I was travelling around a bit when this thread was active, thats why my replies had different country code in them. - dbalan ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can't seem to use 5GHz APs with Intel wireless
On Sun, Jun 03, 2018 at 07:33:30PM +0200, Christoph Moench-Tegeder wrote: > Is the regdomain/country setting correct for your area and matches your > AP? Especially in the 5GHz band there are some "gaps" - not all channels > may be used in all countries (because of possible interference with > radar equipment and other stuff). See: > https://en.wikipedia.org/wiki/List_of_WLAN_channels#5_GHz_(802.11a/h/j/n/ac/ax) > Thanks for taking time to explain. Turns out PEBKAC. I had this offending line burried in rc.conf create_args_wlan0="country DE regdomain FCC4" According to regdomain(5) So I was forcing my card to do 2.4Ghz it seems, removed it - everything worked like charm. I can see and connect to 5GHz 11a aps. wlan0: flags=8843 metric 0 mtu 1500 ether inet 192.168.1.13 netmask 0xff00 broadcast 192.168.1.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11na status: associated ssid channel 36 (5180 MHz 11a ht/40+) bssid regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 17 bmiss 10 mcastrate 6 mgmtrate 6 scanvalid 60 ampdulimit 64k ampdudensity 4 -amsdutx amsdurx shortgi -stbc -ldpc wme roaming MANUAL - dbalan ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Can't seem to use 5GHz APs with Intel wireless
On Sat, Jun 02, 2018 at 12:37:12AM +0200, Christoph Moench-Tegeder wrote: > Did you try adding "mode 11a" to select 5GHz band? (This might be > out-of-date, as my WiFi stuff is all on 11) (currently I'm also > using 2.4GHz only, for compatibility with some devices and the fact > that I have quite some trouble running 2.4GHz and 5GHz from the same > interface at the same time). I did a bit more testing, I have to admit that I am not well versed in wifi internals. 1. ifconfig wlan0 list aps shows my aps having rate 54M (Im not entirely sure what this means). But however when I connect to it, it shows up as 11g wlan0: flags=8843 metric 0 mtu 1500 ether a4:4e:31:02:70:3c inet 192.168.23.111 netmask 0xff00 broadcast 192.168.23.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid LA03 channel 6 (2437 MHz 11g ht/20) bssid 52:d9:e7:47:c0:c2 regdomain FCC4 country DE authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi -stbc -ldpc wme roaming MANUAL groups: wlan 2. Adding mode 11a to rc.conf didn't change anything. Still connects to 2.4Ghz band. 3. ifconfing wlan0 scan still doesn't show my 5Ghz only APs (at least some I tested) Also, what does 11a mean? shouldn't it be 11n? - dbalan ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Can't seem to use 5GHz APs with Intel wireless
Hi,
(Apologies if this is the wrong list, please point me at the right one if you
know)
I run 12-CURRENT (r334442) on a Thinkpad X230. This machine has an Intel
Centrino Advanced N 6205. But freebsd only uses in in 11g mode. When I
try to scan, it won't even display 5GHz aps.
wlan0: flags=8843 metric 0 mtu 1500
ether a4:4e:31:02:70:3c
inet 192.168.1.108 netmask 0x broadcast 192.168.255.255
nd6 options=29
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid SSID channel 7 (2442 MHz 11g ht/20) bssid bc:8a:e8:0b:a9:3f
regdomain FCC4 country DE authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60
protmode CTS ampdulimit 32k ampdudensity 16 -amsdutx amsdurx shortgi
-stbc -ldpc wme roaming MANUAL
groups: wlan
>From reading man pages, I can see that iwn(4) supports 11n. Is it
really supprted? What can I do to enable 11n?
Here are my configs
/etc/rc.conf
wlans_iwn0="wlan0"
ifconfig_wlan0="ssid SSID WPA SYNCDHCP"
/etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
eapol_version=2
ap_scan=1
fast_reauth=1
network={
ssid="SSID"
scan_ssid=0
psk="PSK"
priority=5
}
/boot/loader.conf
# wifi
if_iwn_load="YES"
iwn1000fw_load="YES"
iwn100fw_load="YES"
iwn105fw_load="YES"
iwn135fw_load="YES"
iwn2000fw_load="YES"
iwn2030fw_load="YES"
iwn4965fw_load="YES"
iwn5000fw_load="YES"
iwn5150fw_load="YES"
iwn6000fw_load="YES"
iwn6000g2afw_load="YES"
iwn6000g2bfw_load="YES"
iwn6050fw_load="YES"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
