Re: wi(4) or wicontrol broken

2005-10-16 Thread Ludwig Mises
> > At that point, I had to boot bsd.old because it simply refused to boot. > > Based on the incorrect assumption that the snapshot was pre -release I > > decided to download the kernel from 3.8-release and install that. The kernel > > now booted but wi didn't work. I started looking at the differe

Re: wi(4) or wicontrol broken

2005-10-16 Thread Otto Moerbeek
On Sun, 16 Oct 2005, Ludwig Mises wrote: > > You did not report any problem in a decent way. I'm almost 100% sure you > > created the problem yourself by not following the proper upgrade path. > > > > This is very probable. Actually, it gets more complex than this... I > installed the snapshot

Re: wi(4) or wicontrol broken

2005-10-16 Thread Matthew Weigel
Ludwig Mises wrote: This is very probable. Actually, it gets more complex than this... No, it doesn't. Once you 'upgraded' from -current to -release, you guaranteed that you'd see problems that the developers don't care about. You may have any number of such problems, all stemming from ker

Re: wi(4) or wicontrol broken

2005-10-16 Thread Ludwig Mises
> You did not report any problem in a decent way. I'm almost 100% sure you > created the problem yourself by not following the proper upgrade path. This is very probable. Actually, it gets more complex than this... I installed the snapshot from 10/14 and after rebooting the kernel wouldn't boot.

Re: wi(4) or wicontrol broken

2005-10-16 Thread Otto Moerbeek
On Sun, 16 Oct 2005, Ludwig Mises wrote: > > Of course it works perfectly in -current. > > > By the way, thank you for answering this question. Will this be backported > to 3.8-stable? This not, that neither. You did not report any problem in a decent way. I'm almost 100% sure you created the

Re: wi(4) or wicontrol broken

2005-10-16 Thread Ludwig Mises
> Of course it works perfectly in -current. By the way, thank you for answering this question. Will this be backported to 3.8-stable?

Re: wi(4) or wicontrol broken

2005-10-16 Thread Ludwig Mises
> The problem is you made an assumption which is false. Yes, I made an assumption. Is the snapshot of 10/14 3.8-current? If so, I'll just upgrade from my now 3.8-release system with the snapshot. I made the mistake of thinking that -release would be more recent than the snapshot, of course now I

Re: wi(4) or wicontrol broken

2005-10-16 Thread Theo de Raadt
> > You tried to go back... (3.8-current -> OPENBSD_3_8_BASE which > > corresponds to 3.8-release). If you want 3.8-release, the easiest thing to > > do will be to wait for the actual release, and then install from scratch. > > > Are you saying that the snapshot of 10/14 is 3.8-current? If so, my

Re: wi(4) or wicontrol broken

2005-10-16 Thread Ludwig Mises
> You tried to go back... (3.8-current -> OPENBSD_3_8_BASE which > corresponds to 3.8-release). If you want 3.8-release, the easiest thing to > do will be to wait for the actual release, and then install from scratch. Are you saying that the snapshot of 10/14 is 3.8-current? If so, my bad. Let me

Re: wi(4) or wicontrol broken

2005-10-16 Thread steven mestdagh
On Sat, Oct 15, 2005 at 11:53:42PM -0600, Ludwig Mises wrote: > I upgraded to OPENBSD_3_8_BASE (after first upgrading to the snapshot from > 10/14) and wicontrol no longer seems to work: quoting http://www.openbsd.org/faq/faq5.html#Flavors : "One should also understand that the update process is

wi(4) or wicontrol broken

2005-10-15 Thread Ludwig Mises
I upgraded to OPENBSD_3_8_BASE (after first upgrading to the snapshot from 10/14) and wicontrol no longer seems to work: # wicontrol wi0 wicontrol: SIOCGWAVELAN (0xfd0b): Invalid argument I notice that there was one change to sbin/wicontrol/wicontrol.c and a few changes to sys/dev/ic/if_wi.c but