Ok, obexftp not installed was the last straw. I switched to FC7 as you suggested, and I'm going to run RHEL on qemu. Ok, so FC7 has a newer kernel, I forgot what version it was, but I tried using bcm43xx-fwcutter and cutting out the firmware, then running make installfw. All that worked, then I did rmmod bcm43xx && modprobe bcm43xx, and then tried to connect, first with NetworkManager (failed) and then with iwconfig eth1 essid ... (failed). It did however set the Essid, but it said that the Access Point was invalid. It's a step in the right direction, but it's still far from wireless internet. I'll try again at home with more stable network connection, but more suggestions would be helpful.
Thanks, -Peter On 8/8/07, Peter Davoust <[EMAIL PROTECTED]> wrote: > I'll check out lsmod and see what I'm using vs what's enabled, that's > a good idea. For some reason I didn't think that far. I tried to copy > my .config from the 2.6.18 kernel, but I might have forgotten to. I > would switch distro's but I'm studying the the Red Hat Certified > Engineer exam, so I'd like to stick with 100% Red Hat. Although > recompiling my kernel isn't a very good way to do that, but I did buy > it to study from so I should at least stick with it for a while. > > -Peter > > On 8/8/07, Beso <[EMAIL PROTECTED]> wrote: > > if it gives you kernel panics then you've forgotten to compile something... > > take a look at the modules your base 2.6.18 is loading (lsmod) write them > > down and search them in the actual kernel. be sure you compile them (as > > modules or integrated into the kernel), and also be sure you have the initrd > > if you're going to compile processor, acpi, root filesystem, dma controller > > and that you have these base modules inside the initrd. > > for you the best choice is to search into the redhat repository for newer > > kernels, and best of it, i think that you should switch to fedora 8, instead > > of rhe5, if you don't really need it, cause you're bond to them for a > > looooooot of packages. and compiling external things (ati drivers/ nvidia > > drivers for example) is very troubling. so, if you're using a desktop and > > not using it for real enterprise thigs i would suggest you that you should > > do a backup of your data and switch to either: fedora 8, suse 10.2 (10.3 > > almost out - this is suggested if you want simple linux install), > > kubuntu/ubuntu (kde/gnome - also suggested for a good starter distro) or > > gentoo (if you want to understand more about linux and if you want an almost > > universal - up-to-date - no versioning disto - yep gentoo doesn't have a > > version, but only some profiles that are being updated from time to time, > > basically of use flags). red-hat-enterprise and suse enterprise are some non > > free linux distros that you pay, that you cannot use at best if you don't > > have hw fully supported by them, that you cannot easily update with new > > features/packages and that cause you a lot of problems, mainly in amd64 > > configuration. i wasn't able to use at all my amd64 on amd64 system before > > 2.6.17 kernel, i was able to use my wireless network card functional from > > 2.6.18 and with wpa from 2.6.21, i had to get 2.6.18 to get acpi work for > > some problems in the bios table and so on. if you experience hw > > compatibility on a linux box it is not good to use a distro that gives you > > aches when updating as rhle5. > > and i think that most people agree with me for that. > > > > > > 2007/8/8, Peter Davoust <[EMAIL PROTECTED]>: > > > > > > Thanks for the instructions. I'm about to try bcm43xx-fwcutter on the > > > firmware you suggested. As for your other questions, I'm running Red > > > Hat Enterprise 5 Desktop and Workstation, and my kernel is 2.6.18. > > > Being Red Hat, it's very hard to recompile the kernel and get it to > > > work. I've gotten it to compile, but I'm having trouble with kernel > > > panics when I boot with my new kernel. I could live with that if my > > > wireless card worked in this kernel version :). The error right before > > > the kernel panic is about svm_ something, if that makes sense to > > > anyone. > > > > > > -Peter > > > > > > On 8/8/07, Beso < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > 2007/8/8, Peter Davoust <[EMAIL PROTECTED]>: > > > > > I tried bcm43xx-fwcutter and and some kind of bcm43xx-softmac-sa > > > > > package that I read about on a forum. The softmac thing had some > > > > > compile time errors that looked like coding bugs. bcm43xx-fwcutter > > > > > seemed to work, it extracted the firmware, I did make installfw, and > > > > > then while modprobe bcm43xx didn't give me any errors, it also didn't > > > > > show up on iwconfig. I didn't see anything else on google. > > > > > > > > it's very strange for softmac to give compile errors. maybe it gives you > > > > warnings and then continue to compile, but these aren't great stuff. if > > it > > > > gives you errors then the kernel wouldn't be compiled at all... > > > > > > > > may i know what your pc is and what distro are you using and in which > > > > profile/version? it may a be of help to point you to right direction. > > the > > > > instruction for making the bcm work that i have given are pretty general > > and > > > > quite working for all distros, but sometimes there may happen to need > > > > something else to do. > > > > > > > -- > > > [EMAIL PROTECTED] mailing list > > > > > > > > > > > > > > -- > > dott. ing. beso > -- [EMAIL PROTECTED] mailing list
