Discussion:
"Set Encode" (8B2A) error
Chris Delahousse
2007-04-18 02:14:49 UTC
Permalink
Hey guys,

I have a problem with my wireless card. I went looking back to the list
archives and found out that Arul had a problem almost EXACTLY like mine. The
only differences is that I'm using the amd64bit 2.6.19-r5 kernel on a Compaq
Presario R3440CA. Here's his problem. Same as mine, but there wasn't any say
of how to correct it.


"Hi all.

I am running Gentoo 64-bit 2.6.17-r5 on my Compaq Presario R3370.

I have bcm43xx built in my kernel and it works great without
encryption. But when I try connecting it to my home WEP network, it
gives this error:

# iwconfig eth1 key open ababababab
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Operation not supported.

lsmod returns this:

# lsmod
Module Size Used by
bcm43xx 415040 0
nvidia 5422804 8
snd_pcm_oss 36576 0
snd_mixer_oss 14592 1 snd_pcm_oss
ieee80211softmac 24512 1 bcm43xx
ieee80211 40104 2 bcm43xx,ieee80211softmac
ieee80211_crypt 4992 1 ieee80211

This is my script that worked before:

#!/bin/bash

/sbin/iwconfig eth1 essid shalom
/sbin/iwconfig eth1 mode Managed
/sbin/iwconfig eth1 key open ababababab
/sbin/dhcpcd eth1

Now, it messes up at the "key open" setting. Any help is appreciated.
Thanks guys.
-Arul"


Could you guys give me a hand?

_________________________________________________________________
Check Out Our List Of Trendy Restaurants. You'll Eat It Up!
http://local.live.com/?mkt=en-ca/?v=2&cid=A6D6BDB4586E357F!378
John Jason Jordan
2007-04-18 02:33:18 UTC
Permalink
On Tue, 17 Apr 2007 22:14:49 -0400
Post by Chris Delahousse
Hey guys,
I have a problem with my wireless card. I went looking back to the list
archives and found out that Arul had a problem almost EXACTLY like mine. The
only differences is that I'm using the amd64bit 2.6.19-r5 kernel on a Compaq
Presario R3440CA. Here's his problem. Same as mine, but there wasn't any say
of how to correct it.
I don't need to use WEP, so I haven't paid much attention to this. But
I know I have read somewhere that the bcm43xx driver can't do WEP or
has a problem with it or something. And I dimly recall that the
solution was to blacklist the bcm43xx driver and use ndiswrapper
instead. I would bet that I read this on Ubuntu forums, since Ubuntu
amd64 is all I have ever run on my R3240. Personally I could never get
the bcm43xx driver to work at all with the Broadcom 4306, so I just use
ndiswrapper. Somewhere I have a bookmark to an Ubuntu how-to on
installing ndiswrapper with the 4306. I'll dig it out if you need it.
Constantine 'Gus' Fantanas
2007-04-18 05:35:50 UTC
Permalink
Post by John Jason Jordan
On Tue, 17 Apr 2007 22:14:49 -0400
Post by Chris Delahousse
Hey guys,
I have a problem with my wireless card. I went looking back to the list
archives and found out that Arul had a problem almost EXACTLY like mine. The
only differences is that I'm using the amd64bit 2.6.19-r5 kernel on a Compaq
Presario R3440CA. Here's his problem. Same as mine, but there wasn't any say
of how to correct it.
I don't need to use WEP, so I haven't paid much attention to this. But
I know I have read somewhere that the bcm43xx driver can't do WEP or
has a problem with it or something. And I dimly recall that the
solution was to blacklist the bcm43xx driver and use ndiswrapper
instead. I would bet that I read this on Ubuntu forums, since Ubuntu
amd64 is all I have ever run on my R3240. Personally I could never get
the bcm43xx driver to work at all with the Broadcom 4306, so I just use
ndiswrapper. Somewhere I have a bookmark to an Ubuntu how-to on
installing ndiswrapper with the 4306. I'll dig it out if you need it.
Hmmmmm, maybe the solution is moving to a 2.6.20 kernel? Last Monday I
tried WEP *AND* WPA with a Linksys router, using the BCM43xx (built as
module) and I am happy to say it worked PERFECTLY. (The router, by the
way, had been loaded the openWrt "White Russian" Linux distro for
embedded devices. It is relatively easy to replace the original
firmware with OpenWrt on --at least some-- Linksys wireless routers.
More details at http://openwrt.org/ .) I got WPA to work on the very
first try (judging from the output of 'iwevent', running in a separate
window). Last time I tried to get WPA to work was about a year ago and
under ndiswrapper running under a 2.6.16 kernel. I had no success (WEP
was working fine, but I wanted WPA!).

I run SuSE 10.2 64-bit, but I have upgraded to a plain vanilla kernel
2.6.20.6 and I have enabled full preemption. With the latest "SuSEfied"
2.6.18.2 kernel I have only tried unencrypted wifi connections (again
with the BCM43xx built as module, not in the kernel). It worked OK, BUT
I got flaky numbers, something like -170dBm for signal strength and
100/100 signal quality (!!!!!) on each and every network detected (via
the 'iwlist wlan0 scanning' command --the wifi shows as 'eth?', but I
hacked the relevant file in '/etc/udev/rules.d/' to make it appear as a
symbolic link to wlan0, so I did not have to change my firewall
scripts). I saw none of these problems with the 2.6.20 kernel.

Do you have all the necessary options enabled in your kernel?

On March 26, 2007, Mr. Jose Carlos responded to one of my earlier
postings about the initial success I had with the BCM43xx driver,
suggesting that I go for an Atheros cardbus wifi. This was a very
insightful suggestion (thank you, Mr. Carlos!), but what if I need to
use the cardbus slot while being connected to a wifi network? The
BCM43xx does have its merits despite its shortcomings. If the BIOS
allowed the replacement of the Broadcom wifi with a better solution, it
would be great, but it doesn't, so we are stuck with the Broadcom wifi,
unless we can spare the cardbus slot and/or, perhaps, a USB port.
--
Running 64-bit Linux on AMD64
John Jason Jordan
2007-04-18 06:00:12 UTC
Permalink
On Wed, 18 Apr 2007 01:35:50 -0400
Post by Constantine 'Gus' Fantanas
Post by John Jason Jordan
On Tue, 17 Apr 2007 22:14:49 -0400
I don't need to use WEP, so I haven't paid much attention to this. But
I know I have read somewhere that the bcm43xx driver can't do WEP or
has a problem with it or something. And I dimly recall that the
solution was to blacklist the bcm43xx driver and use ndiswrapper
instead. I would bet that I read this on Ubuntu forums, since Ubuntu
amd64 is all I have ever run on my R3240. Personally I could never get
the bcm43xx driver to work at all with the Broadcom 4306, so I just use
ndiswrapper. Somewhere I have a bookmark to an Ubuntu how-to on
installing ndiswrapper with the 4306. I'll dig it out if you need it.
Hmmmmm, maybe the solution is moving to a 2.6.20 kernel? Last Monday I
tried WEP *AND* WPA with a Linksys router, using the BCM43xx (built as
module) and I am happy to say it worked PERFECTLY. (The router, by the
way, had been loaded the openWrt "White Russian" Linux distro for
embedded devices. It is relatively easy to replace the original
firmware with OpenWrt on --at least some-- Linksys wireless routers.
More details at http://openwrt.org/ .) I got WPA to work on the very
first try (judging from the output of 'iwevent', running in a separate
window). Last time I tried to get WPA to work was about a year ago and
under ndiswrapper running under a 2.6.16 kernel. I had no success (WEP
was working fine, but I wanted WPA!).
I run SuSE 10.2 64-bit, but I have upgraded to a plain vanilla kernel
2.6.20.6 and I have enabled full preemption. With the latest "SuSEfied"
2.6.18.2 kernel I have only tried unencrypted wifi connections (again
with the BCM43xx built as module, not in the kernel). It worked OK, BUT
I got flaky numbers, something like -170dBm for signal strength and
100/100 signal quality (!!!!!) on each and every network detected (via
the 'iwlist wlan0 scanning' command --the wifi shows as 'eth?', but I
hacked the relevant file in '/etc/udev/rules.d/' to make it appear as a
symbolic link to wlan0, so I did not have to change my firewall
scripts). I saw none of these problems with the 2.6.20 kernel.
Do you have all the necessary options enabled in your kernel?
On March 26, 2007, Mr. Jose Carlos responded to one of my earlier
postings about the initial success I had with the BCM43xx driver,
suggesting that I go for an Atheros cardbus wifi. This was a very
insightful suggestion (thank you, Mr. Carlos!), but what if I need to
use the cardbus slot while being connected to a wifi network? The
BCM43xx does have its merits despite its shortcomings. If the BIOS
allowed the replacement of the Broadcom wifi with a better solution, it
would be great, but it doesn't, so we are stuck with the Broadcom wifi,
unless we can spare the cardbus slot and/or, perhaps, a USB port.
I'm afraid I can't answer any of your questions. When I got my R3240
almost two years ago I tried various 64-bit distros on it. None could
get the video right -- they all dumped me in Vesa 1024 x 768. With each
one I tried and tried to get the video working properly, but had no
luck, in spite of hands-on assistance from several local Linux gurus.
Eventually I tried Ubuntu Hoary amd64. It found the video and
autoconfigured it for 1680 x 1050 and I was in heaven. And everything
else worked as well, except for the Broadcom 4306. I was brand new to
Linux and it took me a week to do it, but I finally got wireless
working with ndiswrapper. I haven't left Ubuntu ever since.

When Breezy came out it broke ndiswrapper and I had to set it up all
over again. This time it took me only a day. And after I got it working
I wrote it up and put it on our wiki so that next time I would have my
own personal documentation. Sure enough, when Dapper came out the
upgrade killed ndiswrapper again. But with Dapper we finally had the
bcm43xx driver. I tried and tried to get it to work, but the
instructions I found in the Ubuuntu forums just wouldn't work.
Eventually I said "screw it" and reinstalled ndiswrapper. This time
reinstalling ndiswrapper took me less than 15 minutes. And again when I
upgraded to Edgy I had to reinstall ndiswrapper once more.

The only thing I use the wireless on this notebook for is when I go to
the university or elsewhere. My home environment is all wired for
ethernet, which is faster and more secure. I have never had a wireless
router and wouldn't know anything about configuring it with the bcm43xx
driver.

I suppose I am going to have to do this all over again in a few days,
as Feisty is scheduled for release this Thursday. It will probably be a
few days late, though, because the release of the beta was three days
late.
Chris Delahousse
2007-04-18 06:16:06 UTC
Permalink
Can you send me the link for your ndiswrapper tutorial? All the ones I've
tried just haven't worked!
Reply-To: "Linux on AMD64 laptops (Compaq and
Re:[LinuxR3000] "Set Encode" (8B2A) error)
Date: Tue, 17 Apr 2007 23:00:12 -0700
MIME-Version: 1.0
Received: from mail.pcxperience.com ([206.197.251.210]) by
bay0-mc10-f5.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Tue,
17 Apr 2007 23:05:51 -0700
Received: from mail.pcxperience.com (localhost [127.0.0.1])by
mail.pcxperience.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id
l3I60l6m027786;Wed, 18 Apr 2007 01:00:54 -0500
Received: from hati.oit.pdx.edu (hati.oit.pdx.edu [131.252.120.59])by
mail.pcxperience.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP
idl3I60AVR027694(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256
01:00:11 -0500
Received: from localhost (c-67-160-166-64.hsd1.or.comcast.net
[67.160.166.64])(authenticated bits=0)by hati.oit.pdx.edu (8.13.3+/8.13.1)
with ESMTP id l3I609hj022970(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA
2007 23:00:11 -0700
LsUYwwHHNt1vXAE0gO6U549BBbE9em2IMxBUtqMnihXRFHAalaL6MfDMhVo/IytA
Hostc-67-160-166-64.hsd1.or.comcast.net [67.160.166.64] claimed tobe
localhost
Organization: None whatsoever
X-Mailer: Sylpheed 2.3.1 (GTK+ 2.10.6; x86_64-pc-linux-gnu)
X-xperience-MailScanner: Found to be clean, Found to be clean
X-xperience-MailScanner-SpamCheck: not spam, SpamAssassin
(score=2.23,required 3.2, BODY_GAPPY_TEXT 0.52, DNS_FROM_RFC_POST 1.71),
not spam, SpamAssassin (score=0.521,required 3.2, BODY_GAPPY_TEXT 0.52,
SPF_HELO_PASS -0.00)
X-xperience-MailScanner-SpamScore: ss
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Linux on AMD64 laptops (Compaq and
HP)"<linuxr3000.lists.pcxperience.com>
List-Archive: <http://lists.pcxperience.com/pipermail/linuxr3000>
X-OriginalArrivalTime: 18 Apr 2007 06:05:52.0044 (UTC)
FILETIME=[9E5356C0:01C7817F]
On Wed, 18 Apr 2007 01:35:50 -0400
Post by Constantine 'Gus' Fantanas
Post by John Jason Jordan
On Tue, 17 Apr 2007 22:14:49 -0400
I don't need to use WEP, so I haven't paid much attention to this. But
I know I have read somewhere that the bcm43xx driver can't do WEP or
has a problem with it or something. And I dimly recall that the
solution was to blacklist the bcm43xx driver and use ndiswrapper
instead. I would bet that I read this on Ubuntu forums, since Ubuntu
amd64 is all I have ever run on my R3240. Personally I could never get
the bcm43xx driver to work at all with the Broadcom 4306, so I just
use
Post by Constantine 'Gus' Fantanas
Post by John Jason Jordan
ndiswrapper. Somewhere I have a bookmark to an Ubuntu how-to on
installing ndiswrapper with the 4306. I'll dig it out if you need it.
Hmmmmm, maybe the solution is moving to a 2.6.20 kernel? Last Monday I
tried WEP *AND* WPA with a Linksys router, using the BCM43xx (built as
module) and I am happy to say it worked PERFECTLY. (The router, by the
way, had been loaded the openWrt "White Russian" Linux distro for
embedded devices. It is relatively easy to replace the original
firmware with OpenWrt on --at least some-- Linksys wireless routers.
More details at http://openwrt.org/ .) I got WPA to work on the very
first try (judging from the output of 'iwevent', running in a separate
window). Last time I tried to get WPA to work was about a year ago and
under ndiswrapper running under a 2.6.16 kernel. I had no success (WEP
was working fine, but I wanted WPA!).
I run SuSE 10.2 64-bit, but I have upgraded to a plain vanilla kernel
2.6.20.6 and I have enabled full preemption. With the latest "SuSEfied"
2.6.18.2 kernel I have only tried unencrypted wifi connections (again
with the BCM43xx built as module, not in the kernel). It worked OK, BUT
I got flaky numbers, something like -170dBm for signal strength and
100/100 signal quality (!!!!!) on each and every network detected (via
the 'iwlist wlan0 scanning' command --the wifi shows as 'eth?', but I
hacked the relevant file in '/etc/udev/rules.d/' to make it appear as a
symbolic link to wlan0, so I did not have to change my firewall
scripts). I saw none of these problems with the 2.6.20 kernel.
Do you have all the necessary options enabled in your kernel?
On March 26, 2007, Mr. Jose Carlos responded to one of my earlier
postings about the initial success I had with the BCM43xx driver,
suggesting that I go for an Atheros cardbus wifi. This was a very
insightful suggestion (thank you, Mr. Carlos!), but what if I need to
use the cardbus slot while being connected to a wifi network? The
BCM43xx does have its merits despite its shortcomings. If the BIOS
allowed the replacement of the Broadcom wifi with a better solution, it
would be great, but it doesn't, so we are stuck with the Broadcom wifi,
unless we can spare the cardbus slot and/or, perhaps, a USB port.
I'm afraid I can't answer any of your questions. When I got my R3240
almost two years ago I tried various 64-bit distros on it. None could
get the video right -- they all dumped me in Vesa 1024 x 768. With each
one I tried and tried to get the video working properly, but had no
luck, in spite of hands-on assistance from several local Linux gurus.
Eventually I tried Ubuntu Hoary amd64. It found the video and
autoconfigured it for 1680 x 1050 and I was in heaven. And everything
else worked as well, except for the Broadcom 4306. I was brand new to
Linux and it took me a week to do it, but I finally got wireless
working with ndiswrapper. I haven't left Ubuntu ever since.
When Breezy came out it broke ndiswrapper and I had to set it up all
over again. This time it took me only a day. And after I got it working
I wrote it up and put it on our wiki so that next time I would have my
own personal documentation. Sure enough, when Dapper came out the
upgrade killed ndiswrapper again. But with Dapper we finally had the
bcm43xx driver. I tried and tried to get it to work, but the
instructions I found in the Ubuuntu forums just wouldn't work.
Eventually I said "screw it" and reinstalled ndiswrapper. This time
reinstalling ndiswrapper took me less than 15 minutes. And again when I
upgraded to Edgy I had to reinstall ndiswrapper once more.
The only thing I use the wireless on this notebook for is when I go to
the university or elsewhere. My home environment is all wired for
ethernet, which is faster and more secure. I have never had a wireless
router and wouldn't know anything about configuring it with the bcm43xx
driver.
I suppose I am going to have to do this all over again in a few days,
as Feisty is scheduled for release this Thursday. It will probably be a
few days late, though, because the release of the beta was three days
late.
_______________________________________________
LinuxR3000 mailing list
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/
_________________________________________________________________
Win a webcam! Nominate your friend’s Windows Live Space in the Windows Live
Spaces Sweetest Space Contest and you both could win!
http://www.microsoft.com/canada/home/contests/sweetestspace/default.aspx
Chris Delahousse
2007-04-18 06:13:05 UTC
Permalink
Well, on the linuxquestions.org forums, they suggested I check my iee82011
modules so I added a TKIP iee82011 module in my kernel, recompiled and
rebooted with the new kernel. I had all the other iee82011 modules enabled
before, except for that one. After the reboot, I tried the same thing and
all I can say is NO DICE!
Same error!!

Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Operation not supported.


I've officially been an linux user for 2 weeks now, I had Suse before hand,
but wanted to turn my laptop into a powerhouse for live music performance so
I installed gentoo. NOT A FUN EXPERIENCE!!!! Well, I have everything running
on gentoo except KNetworkManager (can't figure out how to get the gui
running) and wireless. Wireless worked with encryption right off the bat
with Suse, but not this SOB!AARGE!
Post by Chris Delahousse
Post by John Jason Jordan
On Tue, 17 Apr 2007 22:14:49 -0400
Post by Chris Delahousse
Hey guys,
I have a problem with my wireless card. I went looking back to the list
archives and found out that Arul had a problem almost EXACTLY like
mine. The
Post by John Jason Jordan
Post by Chris Delahousse
only differences is that I'm using the amd64bit 2.6.19-r5 kernel on a
Compaq
Post by John Jason Jordan
Post by Chris Delahousse
Presario R3440CA. Here's his problem. Same as mine, but there wasn't
any say
Post by John Jason Jordan
Post by Chris Delahousse
of how to correct it.
I don't need to use WEP, so I haven't paid much attention to this. But
I know I have read somewhere that the bcm43xx driver can't do WEP or
has a problem with it or something. And I dimly recall that the
solution was to blacklist the bcm43xx driver and use ndiswrapper
instead. I would bet that I read this on Ubuntu forums, since Ubuntu
amd64 is all I have ever run on my R3240. Personally I could never get
the bcm43xx driver to work at all with the Broadcom 4306, so I just use
ndiswrapper. Somewhere I have a bookmark to an Ubuntu how-to on
installing ndiswrapper with the 4306. I'll dig it out if you need it.
Hmmmmm, maybe the solution is moving to a 2.6.20 kernel? Last Monday I
tried WEP *AND* WPA with a Linksys router, using the BCM43xx (built as
module) and I am happy to say it worked PERFECTLY. (The router, by the
way, had been loaded the openWrt "White Russian" Linux distro for
embedded devices. It is relatively easy to replace the original
firmware with OpenWrt on --at least some-- Linksys wireless routers.
More details at http://openwrt.org/ .) I got WPA to work on the very
first try (judging from the output of 'iwevent', running in a separate
window). Last time I tried to get WPA to work was about a year ago and
under ndiswrapper running under a 2.6.16 kernel. I had no success (WEP
was working fine, but I wanted WPA!).
I run SuSE 10.2 64-bit, but I have upgraded to a plain vanilla kernel
2.6.20.6 and I have enabled full preemption. With the latest "SuSEfied"
2.6.18.2 kernel I have only tried unencrypted wifi connections (again
with the BCM43xx built as module, not in the kernel). It worked OK, BUT
I got flaky numbers, something like -170dBm for signal strength and
100/100 signal quality (!!!!!) on each and every network detected (via
the 'iwlist wlan0 scanning' command --the wifi shows as 'eth?', but I
hacked the relevant file in '/etc/udev/rules.d/' to make it appear as a
symbolic link to wlan0, so I did not have to change my firewall
scripts). I saw none of these problems with the 2.6.20 kernel.
Do you have all the necessary options enabled in your kernel?
On March 26, 2007, Mr. Jose Carlos responded to one of my earlier
postings about the initial success I had with the BCM43xx driver,
suggesting that I go for an Atheros cardbus wifi. This was a very
insightful suggestion (thank you, Mr. Carlos!), but what if I need to
use the cardbus slot while being connected to a wifi network? The
BCM43xx does have its merits despite its shortcomings. If the BIOS
allowed the replacement of the Broadcom wifi with a better solution, it
would be great, but it doesn't, so we are stuck with the Broadcom wifi,
unless we can spare the cardbus slot and/or, perhaps, a USB port.
--
Running 64-bit Linux on AMD64
_______________________________________________
LinuxR3000 mailing list
http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000
Wiki at http://prinsig.se/weekee/
_________________________________________________________________
Check Out Our List Of Trendy Restaurants. You'll Eat It Up!
http://local.live.com/?mkt=en-ca/?v=2&cid=A6D6BDB4586E357F!378
John Jason Jordan
2007-04-18 07:25:06 UTC
Permalink
On Wed, 18 Apr 2007 02:13:05 -0400
Post by Chris Delahousse
Well, on the linuxquestions.org forums, they suggested I check my iee82011
modules so I added a TKIP iee82011 module in my kernel, recompiled and
rebooted with the new kernel. I had all the other iee82011 modules enabled
before, except for that one. After the reboot, I tried the same thing and
all I can say is NO DICE!
Same error!!
SET failed on device eth1 ; Operation not supported.
I've officially been an linux user for 2 weeks now, I had Suse before hand,
but wanted to turn my laptop into a powerhouse for live music performance so
I installed gentoo. NOT A FUN EXPERIENCE!!!! Well, I have everything running
on gentoo except KNetworkManager (can't figure out how to get the gui
running) and wireless. Wireless worked with encryption right off the bat
with Suse, but not this SOB!AARGE!
First, here is the URL for the ndiswrapper how-to:

http://ubuntuforums.org/showthread.php?t=340689&highlight=broadcom+4306

But note that it is for Ubuntu Edgy, which is a Debian based distro.
You could follow the same instructions word for word if you were using
any other Debian based distro, but Gentoo is RPM based. If you had more
experience you could "translate" the Debian parts to RPM-ese, but with
only two weeks experience in Linux it might be challenging for you.

I would suggest instead that you download the Ubuntu live/install CD
for Feisty beta. The final should be released in just a few days, so
the beta is very stable. The live/install CD cannot write to your hard
disk until you click on the big "install" icon on the desktop. The idea
is that you can run the entire OS from the CD to give it a try. You can
get Feisty here:

http://www.ubuntu.com/testing

Ack! I just went there and discovered that they have removed it! The
reason is that the final is due any day now. That being the case, I
would suggest you open the above link and keep refreshing the page a
couple times a day until it shows that the final is available. Or if
you are in a hurry you can probably find the beta on various mirrors if
you just google on "feisty beta."

Ubuntu is a lot easier for beginners that Gentoo or just about any
other distro. I strongly suggest you give it a try, especially Feisty.
Feisty is supposed to be the most user-firendly and easiest to
configure version of Linux ever created.
D. Hugh Redelmeier
2007-04-19 17:31:47 UTC
Permalink
| From: John Jason Jordan <***@comcast.net>

| I would suggest instead that you download the Ubuntu live/install CD
| for Feisty beta. The final should be released in just a few days, so
| the beta is very stable.

Thanks for reminding me. I'm downloading the release now (using
BitTorrent). I found the BitTorrent links on one of the mirrors. I don't
know why they don't advertise them more. Here's the page on the mirror I
used:

http://ftp.wayne.edu/linux_distributions/ubuntu/feisty/

I like using BitTorrent because it makes me feel like less of a
leech. Unfortunately, my ISP is one of those that throttles outgoing
BT.

It seems like a lot of distro activity is going on: a new Debian stable
(Etch) was released April 8 and Fedora Core 7 is scheduled for release
next month.
John Jason Jordan
2007-04-19 19:25:57 UTC
Permalink
On Thu, 19 Apr 2007 13:31:47 -0400 (EDT)
Post by D. Hugh Redelmeier
| I would suggest instead that you download the Ubuntu live/install CD
| for Feisty beta. The final should be released in just a few days, so
| the beta is very stable.
http://ftp.wayne.edu/linux_distributions/ubuntu/feisty/
I like using BitTorrent because it makes me feel like less of a
leech. Unfortunately, my ISP is one of those that throttles outgoing
BT.
I used mirrors.cat.pdx.edu because I'm a student there. Like you, I
like to use torrents, but when I started the torrent it was painfully
slow. So I decided that it was time to get back some of the tens of
thousands of dollars I've paid that university. I stopped the torrent
and just downloaded the ISO. Took about 12 minutes. I called a friend
who was on campus with his Linux laptop and told him to get it while he
was there. He said it took 2.5 minutes for the whole 698 MB. My
university got a $100 MM grant from Google recently, and as a result we
have awesome bandwidth.
Post by D. Hugh Redelmeier
It seems like a lot of distro activity is going on: a new Debian stable
(Etch) was released April 8 and Fedora Core 7 is scheduled for release
next month.
My R3240 will remain my main computer, but I needed something for
backups and as a second computer to get on the net with when I goober
up the laptop -- an occurrence that is unfortunately common. So I built
myself a new desktop with a couple of 320 GB SATA II drives to set up
in software RAID 1. I've been installing various amd64 distros just to
play with them. I tried Mepis, Gentoo, Mandriva, OpenSUSE, Fedora 7,
CentOS 5, Debian Etch and Ubuntu Edgy. This morning I tried Feisty.

The motherboard has a Realtek 8169 gigagit onboard, plus nVidia GeForce
6100, and all the rest is nVidia as well. The only ones that could
handle the Realtek were Etch and Feisty. The rest either ignored it or
went into a kernel panic. But Etch couldn't figure out the sound, which
all the rest had no trouble with. And only Fedora 7 and CentOS 5 found
and autoconfigured the nVidia 6100. However, having tried them all, I
am most impressed with Feisty, in spite of the fact that I had to
configure the video manually.

I tried to play a movie to see how the vaunted multimedia features in
Feisty would do. Totem popped up a window saying I needed more codecs
and did I want to go get them? I told it yes, but afterwards it still
couldn't play the movie. I closed Totem, then ejected and reinserted
the movie, whereupon Totem popped up again, and again with the same
message about needing more codecs. But this time the codecs it said I
needed were different from the first time. I told it to go ahead and
install them. Afterwards it still couldn't play the movie, although it
almost does. There is a background screen in the viewing window, but
the play buttons don't do anything. No more popups asking for
additional codecs. Oh well.

I also tried installing Flash by just downloading the tar.gz and
following the instructions on Adobe's website. As I expected, the
install failed with "ERROR: Your architecture, \x86-64\, is not
supported by the Adobe Flash player installer." Oh well. I could use
nspluginwrapper, but I think instead I'll install Opera 32-bit with
--force-architecture as I did on my laptop. On the laptop I have the
best of both worlds -- Firefox-64 without the annoyance of Flash, and
Opera-32 with Flash in case I want to see something on youtube.

Now I'm just finishing a backup of my entire laptop to the new
computer. I'll do an apt-get dist-upgrade to the laptop afterwards.
Continue reading on narkive:
Loading...