On 2020-12-11 13:07, Jeffrey Bouquet wrote: > On Fri, 11 Dec 2020 10:53:55 -0800, Chris <bsd-lists_at_bsdforge.com> wrote: > >> On 2020-12-11 10:32, Chris wrote: >> > On 2020-12-11 08:10, Steve Kargl wrote: >> >> On Fri, Dec 11, 2020 at 06:12:42AM -0800, Jeffrey Bouquet wrote: >> >>> Longtime BSD current user, due to several constraints I had to update from >> >>> a recent dec 10 image in >> >>> a quasi-piecemeal fashion. Fixed all issues [ I think ] From 11-Current >> >>> to 13-Current except >> >>> service netif onestart wlan0 up >> >>> no longer completes. >> >>> .................................... >> >>> /etc/rc.d/netif set_rcvar_obsolete: not found >> >>> eval: wlan_up: not found >> >>> starting wpa_supplicant >> >>> /etc/rc.d/wpa_supplicant: WARNING: failed to start... >> >>> starting dhclient >> >>> eval: wlan0: not found >> >>> /etc/rc.d/dhclient: WARNING: failed to start dhclient >> >>> /etc/rc.d/netif: WARNING: $ipv6_enable is not set properly, see >> >>> rc.conf(5) >> >>> starting network wlan0 >> >>> eval: check_startmsgs: not found >> >>> eval: afexits: not found >> >>> .......................................................................................... >> >>> Piecemeal update was needed because make toolchain and make buildworld >> >>> failed each early on. >> >> >> >> I have a Dec 2 i386-*-freebsd (typing on it now), which uses wlan0 >> >> over a lowly D-Link DWL-G630. Works fine. The change causing >> >> you problems appears to have occurred after Dec 2. >> > >> > mergemaster appears to have not been done (I know. You said >> > quasi-piecemeal). Fair >> > enough. Assuming you have both your /etc && (proposed 13) /etc; >> > perhaps a diff -ruN /your-etc /13-etc >./new-stuff.diff >> > will help you discover what function names were changed/moved/deleted. As >> > well >> > as what services were altered/added/deleted >> Actually. As I think about it. Adding a p to the diff(1) line above may >> make >> it >> easier to visually determine the differences eg; >> >> $ diff -rupN orig-etc/ 13-etc/ >> >> > >> > --Chris >> _______________________________________________ >> freebsd-current_at_freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" > > I had done a full mergemaster previously... > It gets stranger. > I tried etcmerge, it could not do any useful work [ no conflicts found iirc > ] > I tried etcupdate, it could neither [ no /usr/src on the .img file > filesytem iirc ] > I found a wpa_supplicant line that creates wlan0 but run0 never gets beyond > 'no carrier' > ..................................... > then I started Xorg and it worked... so maybe I just forgot to copy the new > kernel over, > but then why would the newer binaries and .ko files be working? > .................................... > Also, when trying the install of the dec 10 .img again, it failed in a > second or so > ..................................... > When copying several files I missed in /etc over, I accidently converted the > system to a 'live cd'... in other words, the system boots normally [ except > the > run0 not starting and other error messages ] but after login I am presented > with the install menu even thought the thumbdrive is not present. And get > a real boot completed by choosing 'live CD ' > .... which is also off topic though... > ................................... > So I got further along, [ fixed Xorg ... ] but it maybe shouldn't be. > ................................... > Thanks for the suggestions. I don't wish anyone to spend any more time on > this, eventually > I may revert to a wired interface [ if only I was certain how to connect > [ type of ethernet cable, ifconfig, route add paramaters... ] > to the wifi > modem ethernet > router ports] ... I have more research to do. > ........................... Well FWIW when I've been confronted with the need to perform an "unorthodox" upgrade path. I always perform a cd / && cp -rp /etc /eetc *prior* to a mergemaster(8) because you never know. ;-) Sorry for your grief, and best wishes for a quick & easy resolve. :-) --ChrisReceived on Fri Dec 11 2020 - 20:55:21 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:26 UTC