[gentoo-amd64] Re: IRQ Disabled
Steev Klimaszewski [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Tue, 07 Aug 2007 16:54:35 -0500: Duncan wrote: Beso [EMAIL PROTECTED] posted: you're wrong! the bcm4310 is supported and currently working fine with bcm43xx. you just have to [snip a whole series of steps, some of them scary steps] OK, this is a bit of a rant, but anyway... I'm a pretty die-hard Linux supporter [but] the above is /certainly/ one reason Linux doesn't have a greater share than it does. Just have to do, yeah, right. And for most people, they just have to do a similarly daunting series of steps to honestly say they've climbed Mt. Everest. This is Gentoo... not your average Joe's Linux distro... Agreed. See below. [W]hen one has to [get] software from multiple sites, [excise] a firmware blob [and configure] by hand the system to use it, there's no way I can see that fitting the description supported and working fine. Rather, it seems to me a more accurate claim would be that it can be made to work, provided one jumps thru a series of possibly scary hoops. You're right, we do have to run through hoops, because sadly, we can't just distribute the firmware blob, which isn't *our* fault, however it is a limitation that is fairly easily worked around. FWIW, the rant wasn't triggered by Gentoo or even the hoops one has to jump thru, but based on an article I had been reading, pointing out this stereotypical Linux geek reply (Oh, it's just this and that and the other thing, which might as well be climbing Mt. Everest for all the OP can make of it) and how it really does scare a lot of folks off -- much more than honestly telling them it's a bit difficult, but here's the steps and you'll be OK if you follow them. So all I'm saying is be realistic. If it's a major pain in the rear, lots of hassle, but simple enough if one follows the step by step instructions in order, say so. Don't make it out to be a walk in the park when it's not. That's all. -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Sandbox violations
Peter, I'm running a non-~amd64 box as well. My package.keywords file is getting rather large, but it's still a stable system. I'd have to guess that it is something with the new kernel, as I'm running x11-drivers/nvidia-drivers-100.14.09 under the 2.6.20-gentoo-r8 kernel and not having problems with the sandbox violations. Granted this may be a faulty supposition as some of the major unstable packages I'm running is gcc-4.2.0 and glibc-2.6. I am curious why you had to turn sandbox off for nvidia-drivers. I've never had to. If memory serves, the last time I had trouble with the sandbox was firefox-1.5.xx. Ain't Gentoo fun. Two systems running the same things and two different experiences. I love it. On Wed, 2007-08-08 at 08:51 +0100, Peter Humphrey wrote: On Tuesday 07 August 2007 20:06, Beso wrote: have you switched to the no-multilib profile by chance?! If I'd tried anything of that magnitude I'd not have been puzzled by such a small consequence as this. or do you have an nvidia package?! Yes, I have nvidia-drivers. It's one of the packages that need sandbox switched off. How does that help? try adding -sandbox to your features in the make.conf and see if it works. Of course I tried that, and it did. Actually, I said FEATURES=-sandbox emerge --resume, and the emerge finished properly. The problem seems to be in switching to this new kernel version. -- Rgds Peter. Linux Counter 5290, Aug 93 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Sandbox violations
Am Dienstag 07 August 2007 10:20 schrieb Peter Humphrey: Has anyone here had problems with emerge's sandbox? This is an amd64 box, not ~amd64, and a few days ago the kernel was upgraded from 2.6.20-r8 to 2.6.21-r4. Since then I've had quite a few packages fall over with a sandbox violation. I get this line from each one, on the screen and in a sandbox log file, twice: open_wr: /usr/src/linux-2.6.21-gentoo-r4/-.gcda What is gcda? It seems to have something to do with static analysis of code, but as far as I know I haven't asked for anything like this in my kernel config. -- Rgds Peter. Linux Counter 5290, Aug 93 Hi Peter, May be it is a bug? [Bug 135745] gcc tries to write gcda files in wrong dir (read-only by sandbox). Secure: https://bugs.gentoo.org/show_bug.cgi?id=135745 There was a comment, hth. --- Comment #42 from [EMAIL PROTECTED] 2007-07-30 14:48 --- I get this error on my ~amd64 system with gentoo-sources-2.6.22-r1/r2, but only when I have selected the stack smashing protection kernel configuration option. If that is unselected, everything compile fine. Brgds Jörg -- [EMAIL PROTECTED] mailing list
Re: [gentoo-amd64] Re: IRQ Disabled
2007/8/8, Peter Davoust [EMAIL PROTECTED]: I'm going to try really hard to reply to all three of these conflicting messages. First, I didn't get Beso's last e-mail, but I think another reason many linux newbs are repelled are abrupt responses on forums and messages like 'you're wrong'. Not to poke a stick in anyone's cage, but ouch. However, that's not what we're talking about. the 4310 isn't even on Broadcom's website, I have no clue how to get it working. Beso, does WPA work with your 4310? yep, i currently work with wpa_supplicant and network manager. I also have a friend that is in the bcm43xx developer list, so i'm quite a bit informed on the matter. The main issue that you may have is that the bcm driver has problems with the power management which currently causes you to disconnect randomly. another problem with this driver is connecting to wireless ap which don't distribute the network name. in these cases you may experience some delay connecting and some connection issues. but for what i know the ndiswrapper version is worse, at least on a amd64 compiled system. if i don't recall badly, the 4310 has entered full support from may of this year. the list on the broadcom site is quite old as it is not greatly mantained. you should also look for changes in the kernel source. an example of this functioning is: http://gentoo-wiki.com/HARDWARE_Gentoo_on_HP_Compaq_nx6325#Onboard_Wireless_.28802.11.29 the main problem with broadcom chips is that they're bugged, there aren't specs around, and that you'll always have to upgrade to the latest wpa_supplicant/wireless tools/kernel to have patched and working drivers. I didn't buy the card specifically, and if I had a choice I would have gotten something that was better supported and didn't die on me every 3 minutes. I even tried an airport pc card, but I have an express pc card slot/whatever, so it didn't work. I would really appreciate if someone could send me said excruciating steps so I could give it a try. I hope I didn't offend anyone, but I know that, being only a lowly highschool student and not a system administrator, I would really appreciate if people would take a little more time to answer the stupid questions. now, the steps for a broadcom to work under linux is: 1. download the latest kernel 2. unzip kernel in /usr/src 3. go the kernel dir 4. make menuconfig and chose: iee802.11 stack and softmac stack from networking - wireless; and bcm43xx from device drivers - network device support - wireless lan 5. compile kernel: make make modules_install make install 6. download wl_apsta.o firmware from this link: http://svit.epfl.ch/stuff/wl_apsta.o or use your distro firmware if it's given to you (for example gentoo gives it from sabayon overlay, kubuntu gives it too) 7. if you downloaded the file from internet you have to cut it with bcm43xx_fwcutter (which normally is in the distro installation repo) and then copy the .fw files to /lib/firmware and the do a chmor +r+x /lib/firmware/*.fw 8. reboot with the new kernel and the chip will get up quite smoothly. On 8/7/07, Dustin J. Mitchell [EMAIL PROTECTED] wrote: On Tue, Aug 07, 2007 at 09:35:58PM +, Duncan wrote: OK, this is a bit of a rant, but anyway... Always good fun :) I'm a pretty die-hard Linux supporter, I doubt anyone would argue that, but the above is /certainly/ one reason Linux doesn't have a greater share than it does. I agree, but I would offer: - Gentoo is, among the many great things it is, not for those who don't get a visceral thrill from following long series of scary steps. Especially if you're looking to eek out good performance by using better drivers. - Things have gotten a lot better, and continue to do so. Dustin -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list -- dott. ing. beso
Re: [gentoo-amd64] Re: IRQ Disabled
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.
Re: [gentoo-amd64] Sandbox violations
2007/8/8, B. Nice [EMAIL PROTECTED]: Peter, I'm running a non-~amd64 box as well. My package.keywords file is getting rather large, but it's still a stable system. I'd have to guess that it is something with the new kernel, as I'm running x11-drivers/nvidia-drivers-100.14.09 under the 2.6.20-gentoo-r8 kernel and not having problems with the sandbox violations. Granted this may be a faulty supposition as some of the major unstable packages I'm running is gcc-4.2.0 and glibc-2.6. I am curious why you had to turn sandbox off for nvidia-drivers. I've never had to. If memory serves, the last time I had trouble with the sandbox was firefox-1.5.xx. i don't really why you have to do this. for what i know the sandbox violation come when some package tries to use the root in a strange way. this may be due to some ebuild bug. anyway i didn't experienced many problems of sandbox violation, but when i did, putting feature -sandbox when compiling it has given me no problem. Ain't Gentoo fun. Two systems running the same things and two different experiences. I love it. On Wed, 2007-08-08 at 08:51 +0100, Peter Humphrey wrote: On Tuesday 07 August 2007 20:06, Beso wrote: have you switched to the no-multilib profile by chance?! If I'd tried anything of that magnitude I'd not have been puzzled by such a small consequence as this. or do you have an nvidia package?! Yes, I have nvidia-drivers. It's one of the packages that need sandbox switched off. How does that help? try adding -sandbox to your features in the make.conf and see if it works. Of course I tried that, and it did. Actually, I said FEATURES=-sandbox emerge --resume, and the emerge finished properly. The problem seems to be in switching to this new kernel version. -- Rgds Peter. Linux Counter 5290, Aug 93 -- [EMAIL PROTECTED] mailing list -- dott. ing. beso
Re: [gentoo-amd64] Re: IRQ Disabled
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 looot 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.3almost 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
Re: [gentoo-amd64] Re: IRQ Disabled
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 looot 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
[gentoo-amd64] unsubscribe
-- Regards, Jim Millard Linux Systems Administrator Canyon County Idaho http:www.canyonco.org I think they called them transistor units Montgomery Scott -- Stardate 3191.4 signature.asc Description: This is a digitally signed message part
