Mailinglist Archive: opensuse-testing (88 mails)

[Gabriel Stein <gabrielstein@xxxxxxxxx>]

2009/9/10 Larry Finger <Larry.Finger@xxxxxxxxxxxx>:
> Gabriel Stein wrote:
> > 2009/9/10 Larry Finger <Larry.Finger@xxxxxxxxxxxx>:
> > > I think it is a good idea to establish our frame of reference for
> > > openSUSE testing.
> > >
> > > My main interest is in wireless networking. I have worked for several
> > > years as a member of the team that developed the reverse-engineered
> > > driver for Broadcom BCM43XX devices, and for the past two years, I
> > > have been on the RE side of the fence converting MIPS binary into
> > > "specifications", i.e. a set of "do this, then do that" lists.
> > >
> > > Wireless has long been a problem with Linux in general. One
> > > continually hears the complaint "Why doesn't it work the way Windows
> > > does?".
> >
> > Brilliant! If you can help with this issue, will be a great step for
> > openSUSE! Better compatibility with wireless device, for example
> > Broadcom, which has a lot of problems.
>
> It is difficult without vendor support. Please specify the problems
> with Broadcom. I suspect I know most of them, but just in case.

I know Larry. Sometimes vendor support isn't the best. But I think
which you can guide us to discover these bugs, and we can do some
documentation about it. For a distro user, its so important to know
normal or expected errors running a final release. We can't be
responsible for everything, but if we define and discover before
users, shows confidence between Project and Testing Team.

> > > The driver side of the equation is in pretty good shape with the
> > > development of the MAC layer and associated components. We do handle
> > > regulatory requirements and restrictions really well, which is very
> > > important as many wireless devices are operated outside the region
> > > encoded in their PROM. Another development is that manufacturers are
> > > contributing more to drivers. In particular, Intel and Atheros have
> > > sizable groups devoted to Linux drivers. Unfortunately, Broadcom is
> > > not among that group, but they do now offer a binary driver for their
> > > latest devices. It has a lot of faults, which is why the RE group is
> > > working hard to support the newer BCM devices.
> > >
> > > The area that needs watching and testing is NetworkManager, which is
> > > early in the development cycle (Version 0.7). With each new release,
> > > existing code is likely to break configurations that were working. On
> > > two recent occasions, once with 11.1 and once with 11.2, updates made
> > > it impossible to connect to an encrypted network. That situation is
> > > what I hope to catch before the updates are released.
> >
> > Yes, work with encrypted connections are so important! Did you created
> > a bug report to NetworkManager too? NetworkManager to me is a problem
> > too, because I can`t do last KDE version(KDE 4.3) work automatically
> > with my own static ip configuration. If we can talk with
> > NetworkManager team and also with openSUSE developer team, will be a
> > great work!
>
> The bugs have not been with NM as much as the API changing and
> openSUSE not following. I do, however, follow the NM mailing list and
> have filed bug reports with then and openSUSE. I can certainly explore
> your issue with them. In my own case, I don't use NM when I have a
> static IP.

Yes, for sure. Thanks by your help and attention! I will try to not use NM too.

> Larry

Best,


-- 
/\
Gabriel Stein
gabrielstein@xxxxxxxxx
+55 51 9953 1337
-- 
To unsubscribe, e-mail: opensuse-testing+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-testing+help@xxxxxxxxxxxx