9:58 a.m.
Hello list,
As a newcomer, I've tried to setup my account on fas.rpmfusion.org, and
uploaded my RSA public key. After a few tries to connect to the CVS,
making mistakes before getting the right method, it seems that my
account is blocked.
With environment variables set like this :
export CVSROOT=:ext:nvieville@cvs.rpmfusion.org:/cvs/nonfree
export CVS_RSH=ssh
Here's what "cvs co common" print:
ssh_exchange_identification: Connection closed by remote host
cvs [checkout aborted]: end of file from server (consult above messages
if any)
and if I try "ssh -v nvieville(a)cvs.rpmfusion.org" I get:
OpenSSH_5.6p1, OpenSSL 1.0.0e-fips 6 Sep 2011
debug1: Reading configuration data /home/nico/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to cvs.rpmfusion.org [195.10.6.64] port 22.
debug1: Connection established.
debug1: identity file /home/nico/.ssh/id_rsa type 1
debug1: identity file /home/nico/.ssh/id_rsa-cert type -1
debug1: identity file /home/nico/.ssh/id_dsa type 2
debug1: identity file /home/nico/.ssh/id_dsa-cert type -1
ssh_exchange_identification: Connection closed by remote host
To finish "ssh -v -i ~/.ssh/id_rsa nvieville(a)cvs.rpmfusion.org" gives :
OpenSSH_5.6p1, OpenSSL 1.0.0e-fips 6 Sep 2011
debug1: Reading configuration data /home/nico/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to cvs.rpmfusion.org [195.10.6.64] port 22.
debug1: Connection established.
debug1: identity file /home/nico/.ssh/id_rsa type 1
debug1: identity file /home/nico/.ssh/id_rsa-cert type -1
ssh_exchange_identification: Connection closed by remote host
So, I would be grateful if someone could unblock this situation, or
could point me to the mistakes I've done.
For information, if necessary, my actual IP and my login name on fas:
78.216.52.19
nvieville
Thanks in advance for your response.
Cordially,
--
Nicolas Viéville
1:49 p.m.
2011/10/25 Nicolas Viéville <nicolas.vieville(a)univ-valenciennes.fr>:
Hello list,
As a newcomer, I've tried to setup my account on fas.rpmfusion.org, and
uploaded my RSA public key. After a few tries to connect to the CVS,
making mistakes before getting the right method, it seems that my
account is blocked.
You are not approved yet, so this is not possible for you to
access
cvs even in RO.
The anonymous access isn't implemented either.
The best for you is to make a diff between the spec file from the
latest src.rpm from the f15 updates repository.
About wl-kmod, You might have read this article from the launch of linux 3.1.
http://linuxfr.org/news/sortie-du-noyau-linux%C2%A031#toc_31
In short, I wonder it it wouldn't be wise to have this new driver
enabled from the stating-kmod than the wl-kmod that might become
unmaintained.
Using staging-kmod with the brcmsmac enabled will requires to
blacklist b43 and b44. But a usability test has to be done by someone
who owns the hardware.
See also: https://bugzilla.rpmfusion.org/show_bug.cgi?id=1997
Nicolas (kwizart)
2:53 p.m.
> As a newcomer, I've tried to setup my account on
fas.rpmfusion.org, and
> uploaded my RSA public key. After a few tries to connect to the CVS,
> making mistakes before getting the right method, it seems that my
> account is blocked.
You are not approved yet, so this is not possible for you to access
cvs even in RO.
The anonymous access isn't implemented either.
The best for you is to make a diff between the spec file from the
latest src.rpm from the f15 updates repository.
Ok! But I think I didn't understood where to post/upload it. Any
information about this would be great.
About wl-kmod, You might have read this article from the launch of
linux 3.1.
http://linuxfr.org/news/sortie-du-noyau-linux%C2%A031#toc_31
I've also followed the links in this article :
https://lwn.net/Articles/456762/
https://lwn.net/Articles/457674/
It seems that the question is not in a stable state actually. But, if I
understand correctly what is discussed, different Broadcom wireless
drivers will still there, and the user have to choose what is best for
him.
In short, I wonder it it wouldn't be wise to have this new
driver
enabled from the stating-kmod than the wl-kmod that might become
unmaintained.
For the moment, as shown in this table
http://wireless.kernel.org/en/users/Drivers/b43#Supported_devices the
bcm4313 wireless chipset isn't supported by the b43 driver (WIP). As
it's my wireless chipset, I've only been able to use it with the wl
driver (hybrid driver: wireless + Bluetooth) provided by Broadcom.
Broadcom just released the 5.100.82.111 version of this driver, and it
seems to be compatible with kernels 3.x as the 5.100.82.38. For my part,
I haven't only tested these two versions with 2.6.40 kernel series on
Fedora. 5.100.82.111 kernel panics, like others maintainers noticed it
(http://aur.archlinux.org/packages.php?ID=19514). 5.100.82.38 works.
I've also tested the 5.100.82.38 driver on Ubuntu Oneiric amd64 with
kernel version 3.0.0-12 (Ubuntu names and versions) and a bcm4313
chipset too. It works too.
Using staging-kmod with the brcmsmac enabled will requires to
blacklist b43 and b44. But a usability test has to be done by someone
who owns the hardware.
Yes, tests have to be done on all supported hardware if possible. But,
if the situation described in the links above persist, with all the
different drivers co-existing, we had to provides blacklist files and
script to maintain/setup them at install time.
Thanks for your response!
--
Nicolas Viéville
8:39 a.m.
Hello list,
> In short, I wonder it it wouldn't be wise to have this new
driver
> enabled from the stating-kmod than the wl-kmod that might become
> unmaintained.
For the moment, as shown in this table
http://wireless.kernel.org/en/users/Drivers/b43#Supported_devices the
bcm4313 wireless chipset isn't supported by the b43 driver (WIP). As
it's my wireless chipset, I've only been able to use it with the wl
driver (hybrid driver: wireless + Bluetooth) provided by Broadcom.
Broadcom just released the 5.100.82.111 version of this driver, and it
seems to be compatible with kernels 3.x as the 5.100.82.38. For my part,
I haven't only tested these two versions with 2.6.40 kernel series on
Fedora. 5.100.82.111 kernel panics, like others maintainers noticed it
(http://aur.archlinux.org/packages.php?ID=19514). 5.100.82.38 works.
I've also tested the 5.100.82.38 driver on Ubuntu Oneiric amd64 with
kernel version 3.0.0-12 (Ubuntu names and versions) and a bcm4313
chipset too. It works too.
Responding to myself!
To correct this, from the 10/25/2011 (yesterday) Broadcom provided a new
version of the wl driver: 5.100.82.112. This one compiles fine and most
important works (no kernel panic) on my bcm4313. I have both broadcom-wl
and wl-kmod spec files and srpms files ready to be reviewed if
necessary. Let me know if I have to open new requests reviews or if I
have to modify 1998 and 1999 ones made for the 5.100.82.38 version
(https://bugzilla.rpmfusion.org/show_bug.cgi?id=1998
https://bugzilla.rpmfusion.org/show_bug.cgi?id=1999).
I think that kernel drivers developers discussions about kernel-staging
branch and brcm drivers, and Broadcom attitude in providing yesterday a
new working wl driver, indicates that both alternatives have to be
considered for the moment. Of course, as a newcomer, I'm not enough
aware of such questions and my point of view has to be considered as a
modest contribution to the discussion.
Thanks in advance for your responses!
--
Nicolas Viéville
4776
days inactive
4777
days old
rpmfusion-developers@lists.rpmfusion.org
3 comments
2 participants
participants (2)
-
Nicolas Chauvet -
Nicolas Viéville