Atheros wireless drivers in Suse 10.1 Beta3
Hi, I have searched the extras directories and rpmfind.net for the kernel-default-nongpl-<version>.rpm but I am unable to find it. Does anyone know if this is available yet? I managed to find the beta2 rpm of the non gpl drivers but the kernel version does not match. Thanks Steve Lamb
Hi, On Sat, 4 Feb 2006, Steven Lamb wrote:
I have searched the extras directories and rpmfind.net for the kernel-default-nongpl-<version>.rpm but I am unable to find it.
Does anyone know if this is available yet? I managed to find the beta2 rpm of the non gpl drivers but the kernel version does not match.
Seconded: kernel-smp-nongpl in /suse/10.1/SUSE-Linux10.1-Beta3-Extra is missing. Dear SUSE people, please hurry to deliver. ;-)) Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
On Sat, Feb 04, 2006 at 01:59:39AM +0100, Eberhard Moenkeberg wrote:
Hi,
On Sat, 4 Feb 2006, Steven Lamb wrote:
I have searched the extras directories and rpmfind.net for the kernel-default-nongpl-<version>.rpm but I am unable to find it.
Does anyone know if this is available yet? I managed to find the beta2 rpm of the non gpl drivers but the kernel version does not match.
Seconded: kernel-smp-nongpl in /suse/10.1/SUSE-Linux10.1-Beta3-Extra is missing. Dear SUSE people, please hurry to deliver. ;-))
https://bugzilla.novell.com/show_bug.cgi?id=147974 Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
On Sat, 4 Feb 2006, Eberhard Moenkeberg wrote:
I have searched the extras directories and rpmfind.net for the kernel-default-nongpl-<version>.rpm but I am unable to find it.
Does anyone know if this is available yet? I managed to find the beta2 rpm of the non gpl drivers but the kernel version does not match.
Seconded: kernel-smp-nongpl in /suse/10.1/SUSE-Linux10.1-Beta3-Extra is missing. Dear SUSE people, please hurry to deliver. ;-))
For all I know the kernel-*-nongpl packages have been blocked for Beta3 intentionally. Andreas can probably give some more details on this. To work around this, I'd suggest you guys get kernel-*-nongpl packages from http://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/projects/kernel/kotd/ i386 => i386/HEAD x86_64 => x86_64/HEAD etc... Don't forget to update kernel-default and kernel-source as well from that source, to make the versions match ;) Regards Christoph
On Sat, Feb 04, 2006 at 12:17:01PM +0100, Christoph Thiel wrote:
For all I know the kernel-*-nongpl packages have been blocked for Beta3 intentionally. Andreas can probably give some more details on this.
Such decissions should be announced. Up to now I found more bugs in the distribution system (intentional or nor) than in the product itself during the 10.1 release cycle. This can be interpreted as pretty high product quality or a pretty bad quality of the distribution system. And if someone tells you then after some time of saying _nothing_ about it that the breakage was intentional then this is _extremely_ annoying Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
Hi, On Sat, 4 Feb 2006, Christoph Thiel wrote:
On Sat, 4 Feb 2006, Eberhard Moenkeberg wrote:
I have searched the extras directories and rpmfind.net for the kernel-default-nongpl-<version>.rpm but I am unable to find it.
Does anyone know if this is available yet? I managed to find the beta2 rpm of the non gpl drivers but the kernel version does not match.
Seconded: kernel-smp-nongpl in /suse/10.1/SUSE-Linux10.1-Beta3-Extra is missing. Dear SUSE people, please hurry to deliver. ;-))
For all I know the kernel-*-nongpl packages have been blocked for Beta3 intentionally. Andreas can probably give some more details on this.
To work around this, I'd suggest you guys get kernel-*-nongpl packages from http://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/projects/kernel/kotd/
i386 => i386/HEAD x86_64 => x86_64/HEAD etc...
Don't forget to update kernel-default and kernel-source as well from that source, to make the versions match ;)
There is a version inconsistency at the x86_64 directory. emoenke@ftp4:0 15:42:11 /ftp/pub/linux/suse/ftp.suse.com/projects/kernel/kotd/x86_64/HEAD > find -type f | sort ./kernel-default-2.6.16_rc1_git6-20060202230008.abuild-extra.tar.gz ./kernel-default-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-default-debuginfo-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-default-nongpl-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-kdump-2.6.16_rc2-20060203075849.abuild-extra.tar.gz ./kernel-kdump-2.6.16_rc2-20060203075849.x86_64.rpm ./kernel-kdump-debuginfo-2.6.16_rc2-20060203075849.x86_64.rpm ./kernel-kdump-nongpl-2.6.16_rc2-20060203075849.x86_64.rpm ./kernel-smp-2.6.16_rc1_git6-20060202230008.abuild-extra.tar.gz ./kernel-smp-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-smp-debuginfo-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-smp-nongpl-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-source-2.6.16_rc2-20060203075849.abuild-extra.tar.gz ./kernel-source-2.6.16_rc2-20060203075849.src.rpm ./kernel-source-2.6.16_rc2-20060203075849.x86_64.rpm ./kernel-xen-2.6.16_rc1_git3-20060202135238.abuild-extra.tar.gz ./kernel-xen-nongpl-2.6.16_rc1_git3-20060202135238.x86_64.rpm emoenke@ftp4:0 15:42:17 /ftp/pub/linux/suse/ftp.suse.com/projects/kernel/kotd/x86_64/HEAD > kernel-source is newer. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
Hi, On Sat, 4 Feb 2006, Eberhard Moenkeberg wrote:
On Sat, 4 Feb 2006, Christoph Thiel wrote:
On Sat, 4 Feb 2006, Eberhard Moenkeberg wrote:
I have searched the extras directories and rpmfind.net for the kernel-default-nongpl-<version>.rpm but I am unable to find it.
Does anyone know if this is available yet? I managed to find the beta2 rpm of the non gpl drivers but the kernel version does not match.
Seconded: kernel-smp-nongpl in /suse/10.1/SUSE-Linux10.1-Beta3-Extra is missing. Dear SUSE people, please hurry to deliver. ;-))
For all I know the kernel-*-nongpl packages have been blocked for Beta3 intentionally. Andreas can probably give some more details on this.
To work around this, I'd suggest you guys get kernel-*-nongpl packages from http://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/projects/kernel/kotd/
i386 => i386/HEAD x86_64 => x86_64/HEAD etc...
Don't forget to update kernel-default and kernel-source as well from that source, to make the versions match ;)
There is a version inconsistency at the x86_64 directory.
emoenke@ftp4:0 15:42:11 /ftp/pub/linux/suse/ftp.suse.com/projects/kernel/kotd/x86_64/HEAD > find -type f | sort ./kernel-default-2.6.16_rc1_git6-20060202230008.abuild-extra.tar.gz ./kernel-default-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-default-debuginfo-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-default-nongpl-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-kdump-2.6.16_rc2-20060203075849.abuild-extra.tar.gz ./kernel-kdump-2.6.16_rc2-20060203075849.x86_64.rpm ./kernel-kdump-debuginfo-2.6.16_rc2-20060203075849.x86_64.rpm ./kernel-kdump-nongpl-2.6.16_rc2-20060203075849.x86_64.rpm ./kernel-smp-2.6.16_rc1_git6-20060202230008.abuild-extra.tar.gz ./kernel-smp-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-smp-debuginfo-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-smp-nongpl-2.6.16_rc1_git6-20060202230008.x86_64.rpm ./kernel-source-2.6.16_rc2-20060203075849.abuild-extra.tar.gz ./kernel-source-2.6.16_rc2-20060203075849.src.rpm ./kernel-source-2.6.16_rc2-20060203075849.x86_64.rpm ./kernel-xen-2.6.16_rc1_git3-20060202135238.abuild-extra.tar.gz ./kernel-xen-nongpl-2.6.16_rc1_git3-20060202135238.x86_64.rpm emoenke@ftp4:0 15:42:17 /ftp/pub/linux/suse/ftp.suse.com/projects/kernel/kotd/x86_64/HEAD >
kernel-source is newer.
This nasty inconsistency is still not fixed yet. What is going on at SUSE? Do we have to see a loss of quality with the loss of Hubert? Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
Hi,
On Sat, 4 Feb 2006, Eberhard Moenkeberg wrote:
This nasty inconsistency is still not fixed yet. What is going on at SUSE? Do we have to see a loss of quality with the loss of Hubert?
my goodness... please stop this shit ... you're using a beta version ... give it the time, or use a final version ... greetz F
On Sun, 5 Feb 2006, Eberhard Moenkeberg wrote: [...]
kernel-source is newer.
This nasty inconsistency is still not fixed yet. What is going on at SUSE?
Well, don't you think we deserve a weekend? ;) [However, did you report a bug yet?] Regards Christoph
Hi, On Sun, 5 Feb 2006, Christoph Thiel wrote:
On Sun, 5 Feb 2006, Eberhard Moenkeberg wrote:
[...]
kernel-source is newer.
This nasty inconsistency is still not fixed yet. What is going on at SUSE?
Well, don't you think we deserve a weekend? ;) [However, did you report a bug yet?]
You should focus on the quality management aspects. A failing build process should not destroy the matching files on the servers. Hubert surely could help you to understand. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
On Mon, Feb 06, 2006 at 12:04:24AM +0100, Eberhard Moenkeberg wrote:
Hi,
On Sun, 5 Feb 2006, Christoph Thiel wrote:
On Sun, 5 Feb 2006, Eberhard Moenkeberg wrote:
[...]
kernel-source is newer.
This nasty inconsistency is still not fixed yet. What is going on at SUSE?
Well, don't you think we deserve a weekend? ;) [However, did you report a bug yet?]
You should focus on the quality management aspects. A failing build process should not destroy the matching files on the servers. Hubert surely could help you to understand.
KOTD is just that a "kernel of the day" build. If it builds, it gets out, otherwise it does not. Ciao, Marcus
Hi, On Mon, 6 Feb 2006, Marcus Meissner wrote:
On Mon, Feb 06, 2006 at 12:04:24AM +0100, Eberhard Moenkeberg wrote:
On Sun, 5 Feb 2006, Christoph Thiel wrote:
On Sun, 5 Feb 2006, Eberhard Moenkeberg wrote:
[...]
kernel-source is newer.
This nasty inconsistency is still not fixed yet. What is going on at SUSE?
Well, don't you think we deserve a weekend? ;) [However, did you report a bug yet?]
You should focus on the quality management aspects. A failing build process should not destroy the matching files on the servers. Hubert surely could help you to understand.
KOTD is just that a "kernel of the day" build.
If it builds, it gets out, otherwise it does not.
Not true. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
On Sun, Feb 05, 2006 at 11:58:55PM +0100, Christoph Thiel wrote:
Well, don't you think we deserve a weekend? ;) [However, did you report a bug yet?]
https://bugzilla.novell.com/show_bug.cgi?id=147974 Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
On Mon, 6 Feb 2006, Robert Schiele wrote:
On Sun, Feb 05, 2006 at 11:58:55PM +0100, Christoph Thiel wrote:
Well, don't you think we deserve a weekend? ;) [However, did you report a bug yet?]
That's a different storry... -- and as Marcus already stated, that one is WONTFIX/INVALID ;) Regards Christoph
Eberhard Moenkeberg wrote:
This nasty inconsistency is still not fixed yet. What is going on at SUSE? Do we have to see a loss of quality with the loss of Hubert?
This happened a lot even when Hubert was there, it is a natural consequence of the experimental nature of the kotd kernels. If some part of the build process fails, the corresponding package will not be built. It happens and happened all the time, there would be kernel-source packages much newer than the binary packages, because the binaries wouldn't build Try not to have selective amnesia for the purposes of politics, please
Hi, On Mon, 6 Feb 2006, Anders Johansson wrote:
Eberhard Moenkeberg wrote:
This nasty inconsistency is still not fixed yet. What is going on at SUSE? Do we have to see a loss of quality with the loss of Hubert?
This happened a lot even when Hubert was there, it is a natural consequence of the experimental nature of the kotd kernels. If some part of the build process fails, the corresponding package will not be built. It happens and happened all the time, there would be kernel-source packages much newer than the binary packages, because the binaries wouldn't build
Try not to have selective amnesia for the purposes of politics, please
I am not able to justice about amnesia (not only because I can't reflect my own amnesia depth), but did you ever notice the first stage of this escalation? Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
On Sunday 05 February 2006 22:46, Eberhard Moenkeberg wrote:
Hi,
Hi Ebarhard
This nasty inconsistency is still not fixed yet. What is going on at SUSE? Do we have to see a loss of quality with the loss of Hubert?
I seem to recall problems just like this even when the blessed Hubert was working for SuSE. The distro is barely a beta, but you're worrying about the top brass losing quality. It's a nice way to praise Hubert, it's also a nice way to pour scorn on all the other hardworking SuSE people who are trying their best to work with the community to produce the best Linux distro.
Cheers -e
Problems can be solved, missing packages can be rolled into a distro. Very harsh words can't be taken back once they're spoken. Nobody is trying to hurt the project, so let's keep it that way, yes? :) Cheers Pete
Hi, On Sun, 5 Feb 2006, Pete Connolly wrote:
On Sunday 05 February 2006 22:46, Eberhard Moenkeberg wrote:
Hi Ebarhard
This nasty inconsistency is still not fixed yet. What is going on at SUSE? Do we have to see a loss of quality with the loss of Hubert?
I seem to recall problems just like this even when the blessed Hubert was working for SuSE. The distro is barely a beta, but you're worrying about the top brass losing quality. It's a nice way to praise Hubert, it's also a nice way to pour scorn on all the other hardworking SuSE people who are trying their best to work with the community to produce the best Linux distro.
Problems can be solved, missing packages can be rolled into a distro. Very harsh words can't be taken back once they're spoken. Nobody is trying to hurt the project, so let's keep it that way, yes? :)
If you would know me, you would see that my words were in no way harsh. I had claimed this inconsistency (the "harsh" word) as "<something> is newer" 48 hours before, with no reply and no reaction. It is a quality management failure, even if it should have been there already at Hubert's time, and it is addressed now. It was already addressed 48 hours before, but I guess exactly those people who are claiming "too harsh" now had not enough sensitivity for the first notice. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
On Mon, Feb 06, 2006 at 01:27:32AM +0100, Eberhard Moenkeberg wrote:
I had claimed this inconsistency (the "harsh" word) as "<something> is newer" 48 hours before, with no reply and no reaction.
It is a quality management failure, even if it should have been there already at Hubert's time, and it is addressed now. It was already addressed 48 hours before, but I guess exactly those people who are claiming "too harsh" now had not enough sensitivity for the first notice.
So you reported that saturday morning, half past one. Seems like the weekend shift was on strike or something. Rasmus
Hi, On Mon, 6 Feb 2006, Rasmus Plewe wrote:
On Mon, Feb 06, 2006 at 01:27:32AM +0100, Eberhard Moenkeberg wrote:
I had claimed this inconsistency (the "harsh" word) as "<something> is newer" 48 hours before, with no reply and no reaction.
It is a quality management failure, even if it should have been there already at Hubert's time, and it is addressed now. It was already addressed 48 hours before, but I guess exactly those people who are claiming "too harsh" now had not enough sensitivity for the first notice.
So you reported that saturday morning, half past one. Seems like the weekend shift was on strike or something.
Yes, there was something happening which was not detected by the scripts. A quality management issue. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
On Mon, 2006-02-06 at 10:15 +0100, Eberhard Moenkeberg wrote:
Hi,
On Mon, 6 Feb 2006, Rasmus Plewe wrote:
On Mon, Feb 06, 2006 at 01:27:32AM +0100, Eberhard Moenkeberg wrote:
I had claimed this inconsistency (the "harsh" word) as "<something> is newer" 48 hours before, with no reply and no reaction.
It is a quality management failure, even if it should have been there already at Hubert's time, and it is addressed now. It was already addressed 48 hours before, but I guess exactly those people who are claiming "too harsh" now had not enough sensitivity for the first notice.
So you reported that saturday morning, half past one. Seems like the weekend shift was on strike or something.
Yes, there was something happening which was not detected by the scripts. A quality management issue.
Cheers -e
Ok, please again: can you stop this bullshit ? get a life, get a final version ... if you try a beta version, create good bugreports ... and don't start complete threads with only wining etc. 10.0 is a very good distro, and 10.1 will be even better, that it will be better, it's thanks to all the good developers, bugreporters etc. not because people like you.
Folks, could you all calm down a bit? The problem turned out to be that a rsyncd deamon died on one of our servers. This was fixed yesterday, now the sync is running again. And yes, we didn't detect the problem due to severe overload caused by SL10.1, so we're grateful to Eberhard for writing a mail about this. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
On Sun, Feb 05, 2006 at 11:46:24PM +0100, Eberhard Moenkeberg wrote:
This nasty inconsistency is still not fixed yet. What is going on at SUSE? Do we have to see a loss of quality with the loss of Hubert?
The KOTD service runs fully automatic. As the kernels did build I guess something is wrong with Andreas' script that does the copying to ftp.suse.com. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
Hi, On Mon, 6 Feb 2006, Michael Schroeder wrote:
On Sun, Feb 05, 2006 at 11:46:24PM +0100, Eberhard Moenkeberg wrote:
This nasty inconsistency is still not fixed yet. What is going on at SUSE? Do we have to see a loss of quality with the loss of Hubert?
The KOTD service runs fully automatic.
As the kernels did build I guess something is wrong with Andreas' script that does the copying to ftp.suse.com.
Thanks for this first non-destructive reply. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)
Thanks this worked. Steve -----Original Message----- From: Christoph Thiel [mailto:cthiel@suse.de] Sent: Saturday, 4 February 2006 10:17 PM To: opensuse@opensuse.org Subject: Re: [opensuse] Atheros wireless drivers in Suse 10.1 Beta3 On Sat, 4 Feb 2006, Eberhard Moenkeberg wrote:
I have searched the extras directories and rpmfind.net for the kernel-default-nongpl-<version>.rpm but I am unable to find it.
Does anyone know if this is available yet? I managed to find the beta2 rpm of the non gpl drivers but the kernel version does not match.
Seconded: kernel-smp-nongpl in /suse/10.1/SUSE-Linux10.1-Beta3-Extra is missing. Dear SUSE people, please hurry to deliver. ;-))
For all I know the kernel-*-nongpl packages have been blocked for Beta3 intentionally. Andreas can probably give some more details on this. To work around this, I'd suggest you guys get kernel-*-nongpl packages from http://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/projects/kernel/kotd/ i386 => i386/HEAD x86_64 => x86_64/HEAD etc... Don't forget to update kernel-default and kernel-source as well from that source, to make the versions match ;) Regards Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
On Sat, Feb 04, 2006 at 11:09:37AM +1100, Steven Lamb wrote:
Hi,
I have searched the extras directories and rpmfind.net for the kernel-default-nongpl-<version>.rpm but I am unable to find it.
Does anyone know if this is available yet? I managed to find the beta2 rpm of the non gpl drivers but the kernel version does not match.
I am wondering why this was not announced yet too. *sigh* The idea is no longer to ship binary only drivers anymore. Everything binary only will be handled by a so called "Driver Process" in seperate RPMs. I have mentioned the design papers (how to build KMPs) to -factory some days. So the Atheros driver is one of those that will go into a seperate RPM too. Ciao, Marcus
On Sat, Feb 04, 2006 at 03:12:07PM +0100, Marcus Meissner wrote:
The idea is no longer to ship binary only drivers anymore.
Everything binary only will be handled by a so called "Driver Process" in seperate RPMs. I have mentioned the design papers (how to build KMPs) to -factory some days.
So the Atheros driver is one of those that will go into a seperate RPM too.
If that was the reason the old way of doing it should not have been abandoned as long as the new one is not jet installed in place. Robert -- Robert Schiele Tel.: +49-621-181-2214 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de "Quidquid latine dictum sit, altum sonatur."
participants (11)
-
Anders Johansson
-
Christoph Thiel
-
Eberhard Moenkeberg
-
Frederik Vos
-
frederik.vos@l4l.be
-
Marcus Meissner
-
Michael Schroeder
-
Pete Connolly
-
Rasmus Plewe
-
Robert Schiele
-
Steven Lamb