Problems with bcm43xx-fwcutter
by bof
lo,
I am having some trouble getting bcm43xx to work. I have tried following
the HOWTO instructions that you had posted at
http://lists.infradead.org/pipermail/fedora-ppc/2006-March/000804.html.
I was able to install it on FC5 using yum, and it would appear to be
version -004 as it is in directory /usr/share/doc/bcm43xx-fwcutter-004.
First of my problems is that the md5sums on many of the links in the
README file do not agree with the files downloaded from the listed URLs
and extracting files from them fails. I also tried extracting from the
file that Gateway uses for my system (a Gateway notebook, model MX6440
with a Airforce One 54g card apparently using a BCM4318 chip) but that
also failed with the md5sum problem.
I was able to extract an older version of bcmwl5.sys , version 3.20.23.0
but with many dire warnings, viz.,
extracting bcm43xx_microcode2.fw ...
extracting bcm43xx_microcode4.fw ...
extracting bcm43xx_microcode5.fw ...
*****: Sorry, it's not posible to extract "bcm43xx_microcode11.fw".
*****: Extracting firmware from an old driver is bad. Choose a more
recent one.
*****: Luckily bcm43xx driver doesn't include microcode11 uploads at
the moment.
*****: But this can be added in the future...
extracting bcm43xx_pcm4.fw ...
*****: Sorry, it's not posible to extract "bcm43xx_pcm5.fw".
*****: Extracting firmware from an old driver is bad. Choose a more
recent one.
*****: bcm43xx driver will not work with with core revision 5 or higher.
extracting bcm43xx_initval01.fw ...
extracting bcm43xx_initval02.fw ...
extracting bcm43xx_initval03.fw ...
extracting bcm43xx_initval04.fw ...
extracting bcm43xx_initval05.fw ...
extracting bcm43xx_initval06.fw ...
extracting bcm43xx_initval07.fw ...
*****: Sorry, initval08 is not available in driver file "bcmwl5.sys".
*****: Extracting firmware from an old driver is bad. Choose a more
recent one.
*****: Luckily bcm43xx driver doesn't include initval08 uploads at
the moment.
*****: But this can be added in the future...
extracting bcm43xx_initval09.fw ...
extracting bcm43xx_initval10.fw ...
When I issued modprobe bcm43xx, it loaded. I then configured eth1 using
ifconfig and found after issueing ifconfig -a, it showed eth1 as having
an address of 172.16.5.38 and a HW address of 00:14:!5:85:4E:D5.
However iwconfig eth1 shows an invalid access point, and I am unable to
assign one using iwconfig with the ap switch set to the above mac address.
Could you advise me on (1) how to get a later file for extraction of the
driver (if this is necessary) and (2) why I am unable to bind eth1 to an
access point?
Thanx.
BOF
17 years, 12 months
You can make website which accept credit cards easily!
by webell＠eastlink.ca
Dear fedora-ppc:
Dreaming to own a website made by yourself? Please visit http://www.webell.ca to lean
how easy it is to make a website with advanced future such as image map, tab control,
menu, 3D buttons and even "Buy Now" buttons to make your website accept major
credit cards when you customers make purchases from you website when you don't
even know what it is and how they worked.
Traditionally getting a website for your personal or business means spending
thousands of dollars on a designer, software developer etc. This is not the case
anymore.
WebellExpress is packed full of supreme features, such as Menu, Tab control, image
map and even on line shopping "buy now" button. Not to mention, 3D buttons and
labels are also included in this release. You will find creating and updating your WEB
site a breeze. Most changes only require a click of your mouse, and editing text is just
like typing a letter with an editor that looks just like MS Word. Your website will be
ready instantaneously after you decide your website layout.
Perk up your web pages with animation, dropdown menus, 3D buttons and other
special effects. From the WebellExpress GUI just drag and drop objects from toolbox
to the pages and position them 'anywhere' you want.
WebellExpress can help you host your website as easy as a few clicks. Just select a
menu item from WebellExpress website design user interface and choose deploy.
Why wait and waste time and money, download a free demo from http://www.webell.ca and
start to enjoy the pleasure of making you unique WEB site
Please contact me if you have any question.
Sincerely,
Mack Chen
mailto:mchen@webell.ca
17 years, 12 months
FC4 --> FC5 need yaboot, OF help
by Mike Hammill
Hello all,
After upgrading FC4 to FC5, I have not been able to successfully
reboot yet. The problem is a messed up yaboot.conf, I think. I
could use some help and or advice on that. Specifically, can I
specify at yaboot's "boot:" prompt (or perhaps it's OpenFirmware's)
an "init=" ? And if so, how?
Background:
I've been running FC4 for quite a while on a Mac G3 (Blue and
White). Really nice. I decided to take the plunge and do the
upgrade to FC5. Since this old Mac has a DVD, I used the FC5 DVD.
The upgrade appeared to go fine, but when I reboot, I get:
Welcome
Welcome to yaboot version 1.3.13 (Red Hat 1.3.13-0.18)
boot:
Please wait, loading kernel...
:3,/vmlinux: Unable to open file, Invalid device
boot:
Using an old Gentoo 2004.3 CD I investigated further and found the
old FC4 kernels were removed from /dev/hda3 (my /boot) just as they
probably should have been, since it was getting full anyway. The
files in there now include vmlinuz-2.6.15-1.2054_FC5 and a
corresponding initrd file. So, I rebooted, ended up at the same
boot: prompt shown above and tried a number of things, firstly:
boot: hd:3,/vmlinuz-2.6.15-1.2054_FC5
This enters me into the kernel, shows it recognizes the HD with stuff
like:
hda: [mac] hda1 hda2 hda3 hda4
but then hits:
EXT2-fs warning (device hda3): ext2_fill_super: mounting ext3
filesystem as ext2
VFS: Mounted root (ext2 flesystem) readonly.
Freeing unused kernel memory: 196k init
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option
to kernel.
Call Trace:
...
<0> Rebooting after xxx seconds...
Since my entire FC4 installation--outside of /boot--was under LVM
(and possibly reiserfs, don't recall), my first reaction is that the
above Kernel needs an initrd file to help it get the LVM/reiserfs
stuff right. So, I tried:
boot: hd:3,/vmlinuz-2.6.15-1.2054_FC5 init="/
initrd-2.6.15-1.2054_FC5.img"
boot: hd:3,/vmlinuz-2.6.15-1.2054_FC5 init=/initrd-2.6.15-1.2054_FC5.img
boot: hd:3,/vmlinuz-2.6.15-1.2054_FC5 init=initrd-2.6.15-1.2054_FC5.img
boot: hd:3,/initrd-2.6.15-1.2054_FC5.img
None of these worked. I got messages like "Failed to execute
initrd-..... Attempting defaults...".
As you can see, I'm struggling with things I don't totally understand
here (probably why I am not succeeding!) First off, I'm not sure
exactly what initrd's really do. Second, I'm not sure not having one
is really the problem; it could be that odd message about the
console. Finally, even if I'm barking up the right tree, I don't
know how to make OpenFirmware/yaboot do the right thing.
Help or advice appreciated.
PS I don't have the yaboot.conf installed by the FC5 DVD in front of
me, but as I remember is didn't include much more than a boot=/dev/
hda2 and partition=3 in it.
/Mike
18 years
RE: G4 running FC4
by Peter M. Metcalf
I'm going to update my FC4 again and then do the "ybin -v" to see if that
is where I was running into ground.
After my first fail with FC4 I tried to run FC5 installer and couldn't get
disc 1 to the opening screen...figured FC5 was out of the question at that
point.
If we succeed with this try then we'll go for 5.
Thanks, Pete
At 11:09 AM 5/16/2006, you wrote:
>After each kernel update you MUST manually run "ybin -v" from root terminal.
>That will update the open firmware and allow you to boot the kernel you just
>updated to.
>
>Holt
>
>I run FC5, Yellow Dog 4, Ubuntu 6.06 Beta, OS9, 10.4.6 on a G5 Quad, a G4
>Powerbook 17", a G4 Digital Audio.
18 years
G4 running FC4
by Peter M. Metcalf
After much fooling around, was able to get original kernel version of FC4
to boot. Did a yum update to newest kernel and have been unable to get
past the kernel panic. Reloaded original kernel several times and that
went well until trying an update.
Back to "2.6.11-1.1369_FC4-ppc" and ready to settle at that unless somebody
has been there and resolved the issue already.
Thanks, Pete
18 years
Re: Bordeaux fails install
by Erick Calder
I tried your suggestion but get:
"Unable to read package metadata. This may be due to a missing repodata
directory. Please ensure that your install tree has been correctly
generated. Failure: repodata/primary.xml.gz from anaconda: [Errno: 256].
No more mirrors to try."
grr... what next?
> From: "Brian D. Carlstrom" <bdc(a)carlstrom.com>
> Reply-To: "Brian D. Carlstrom" <bdc(a)carlstrom.com>
> Date: Wed, 19 Apr 2006 23:44:31 -0700
> To: Erick Calder <e(a)arix.com>
> Cc: <fedora-ppc(a)lists.infradead.org>
> Subject: Bordeaux fails install
>
> Erick Calder writes:
>> I then tried a network install, in case the drive had problems. I attempted
>> an FTP-based install but with similar results.
>
> I've done a half dozen G5 DVD installs of FC5 ppc without significant
> issues (the only real one is that yaboot doesn't work on a G5 2.0GHz we
> have.
>
> I also have done two network installs, one a fresh install on ppc and
> the other an ugprade install on i386. For ppc try HTTP to
> mirrors.kernel.org:fedora/core/4/ppc/os/. In the network installs I just
> used the rescue CD.
>
> -bri
18 years
