2007/8/8, Peter Davoust <[EMAIL PROTECTED]>: > > Ok, obexftp not installed was the last straw. I switched to FC7 as you > suggested, and I'm going to run RHEL on qemu.
you can also run it on xen, but you'll need to configure the kernel to do so. if you have time to do that could be an interesting option for someone who wants the rhel certification. you'll have to read some documentation on that. 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) what does "tail -f /var/log/messages" say when trying to connect to the network? the logs would be very useful. also a ls -l /usr/src to see what kernel you're using (you'll need at least 2.6.21 even if you'll have bugfixes and other improvements in 2.6.22). read where /usr/linux link is pointing. then do a iwconfig --version (i currently have 29 version) and a wpa_supplicant --version (the latest stable and good one for bcm is 0.5.8 so at least you'll need that one). and then with iwconfig eth1 essid ... (failed). It did however set the > Essid, but it said that the Access Point was invalid. that's due to something in the wireless tools that don't set the essid right: for example on my network i had to set 3 times the essid cause it has set only the 2 first letters of the network essid. have you also chosen the right channel? this is important at first. also, with networkmanager you have to look out for network encryption. at first i would suggest you to remove the network encryption in your router, then i would suggest to check if you mac address is enabled to connect (you may have set it to blacklist without paying attention) and last, be sure that your router is broadcasting the essid. at that time try to connect. after being sure that you can connect, 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. the 2.6.22 kernel has changed the place for some options. you'll most likely have the right config if you copy a .config but you'll always have to verify it before recompiling a new kernel. and the newer versions have the tickless support for optimization of power consuming. it works only for x86, but it is a good thing. i'm actually trying it on my old athlon xp to see how it works. 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. fedora core is also 100% red hat. it is only the free version. i've been using it for some time, but i didn't liked it much. i had preferred opensuse for that. now, remember to search for fedora core 7 repositories, cause i don't know if functions like mp3 or video playing are included by default (this how to explains what to do http://forums.fedoraforum.org/forum/showthread.php?t=161228&highlight=repositry), and for updates. this site could be useful: http://rhold.fedoraproject.org/Download/updates.html this is a faq for fedora systems: http://www.fedorafaq.org/ and this the official forum in which you may find a lot of things http://www.fedoraforum.org/ 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. > > the recompiling of the linux kernel is a must for every linux user. of course, distro like fc, opensuse don't encourage the recompilations for "stability" issues, but others like gentoo encourage them. it's a waste of time fixing something when there's a new version that already fixex it. other distro like rhel or suse enterprise desktop almost don't allow the changing of kernel, cause they usually have some modules compiled expressively for that particular kernel they're using (as apparmor for suse that cannot be upgraded for newer kernels unless the new kernel comes already compiled from official sources). this is the only problem. at last i have to say that the recompilation of the kernel is very simple: all that you have to do is identify your hw, indentify your needs (for example dvb and similar) then configure the kernel (make menuconfig), compile it with make, install modules with make_modules install, install the kernel with make install, point the bootloader to the new kernel (on some distros), recompile external kernel modules as ati drivers or truecrypt, and then reboot. ps. i don't really knwo what the red hat engineer exam is, but if red hat eng. don't know how to compile a kernel or how to make something work i wouldn't allow them to become engineers. the recompilation of kernel sources or the compilation or removal of external tools is quite important in a linux distro. at least in my personal opinion.
