LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 02-01-2005, 11:33 AM   #1
spage0506
Member
 
Registered: Dec 2004
Distribution: SimplyMepis 3.3.1
Posts: 30

Rep: Reputation: 15
SIOCSIFFLAGS: cannot allocate memory


hey folks, I'm a Newbie running FC2 on kernel 2.6.10-8 on i686

today the startup revealed an error when initializing my ethernet device (eth0) which is a Broadcom 4400. I am using FC2's driver. Startup revealed: "SIOCSIFFLAGS: cannot allocate memory".
To me, this came as a suprise since everything has been running perfectly until now.
The only things i can think of is: #1 that I recently tried to install my soundcard as a module (which failed) and #2 I accidently booted a previous kernel version via GRUB (2.4.... the version that comes with FC2).
Why is this happening? What can I do to fix this?? As a newbie i find this very frustrating.

Trying to keep hope alive,
Stu
 
Old 02-01-2005, 12:54 PM   #2
rylan76
Senior Member
 
Registered: Apr 2004
Location: Potchefstroom, South Africa
Distribution: Fedora 17 - 3.3.4-5.fc17.x86_64
Posts: 1,552

Rep: Reputation: 103Reputation: 103
Hmm - never heard of that one. If everything WAS working correctly, it might be that you booted the wrong kernel. Have you tried rebooting? Or even switching the whole system off, waiting two minutes or so, then switching on again?

If everything ELSE is working fine (especially see if, for example, you have Windows, that ITS network stuff is running) it might mean that you have a hardware fault - your network card could have gone bad, or been hit by lightning or something.

You most probably then need to install a new network card, or, if it is an onboard card, disable it in the BIOS and get a network card that is on the Linux HCL, install and use that.
 
Old 02-01-2005, 04:31 PM   #3
spage0506
Member
 
Registered: Dec 2004
Distribution: SimplyMepis 3.3.1
Posts: 30

Original Poster
Rep: Reputation: 15
Hey Stefan, thanks for your reply
I wouldn't be so perplexed if the network card was not working in window. But my card is working perfectly in windows, (as i'm on the net now with it).
Here's my sequence of events:
I installed Fedora, then I installed rppp-oe and got my DSL connection configured on eth0, then everything was perfect. I started working on my soundcard, trying to get it working. I tried to install it as a module, but I tried two separate drivers for my card (alsa and i810 intel) and they seem to both want to be built as modules. Needless to say the build failed and now two build attempts show up on bootup as failed module builds. I restarted the computer this morning, but accidently booted the wrong kernel from GRUB, so i restarted and loaded the correct kernel 2.6.10-8 and i got the "SIOCSIFFLAGS: cannot allocate memory" error when the OS tried to initialize eth0..... now eth0 is not working in Linux, but still works in Windows.
Very confused

any ideas?? thanks
 
Old 02-02-2005, 08:03 AM   #4
rylan76
Senior Member
 
Registered: Apr 2004
Location: Potchefstroom, South Africa
Distribution: Fedora 17 - 3.3.4-5.fc17.x86_64
Posts: 1,552

Rep: Reputation: 103Reputation: 103
Hmm that does not sound too good. I am a bit confused though - building modules should not affect the kernel itself (loadable modules) as far as I know (I may be wrong). Also, you should NOT be able to select -modules- to load with GRUB, only -kernels-. Are you sure you did what you think you did?

Sorry this is something I often have to ask myself when I am trying to do something. My whole point is that is is unlikely that a module build AFTER getting the LAN card working should affect the LAN card in -any- way. UNLESS you actually compiled a whole new kernel (with support for the LAN card "compiled into" the kernel, and then also support for the soundcard compiled in).

Modules are just that - modules - and must me loaded with insmod (I think). I. e. you can have a state where your kernel natively supports your LAN card, but you load a module on boot that supports your soundcard. I. e. if you do not load the soundcard module, it can in no way affect a "LAN capable" working kernel. Even when loading a faulty or buggy soundcard module, I think it is highly unlikely that working on your soundcard's configuration could have somehow affected the LAN card.

This is a little out of my league, but have you checked that somehow the sound and LAN cards aren't trying to use the same IRQ? I've got no idea how to check for (or change) this though.

One other thing that just popped up - highly unlikely and speculative - can you check that in Windows the LAN card is at 10 MBPS speed or 100 MBPS? Maybe (very maybe) your LAN card has a problem running at 100 MBPS (which Linux tries to FORCE it to do) but which Windows automagically detects is unavailable and configures it for 10 MBPS? I've got no idea how you are going to force the card to a slower speed, even if this unlikely tangent proves correct.

A remaining alternative is to either remove or disable the LAN card (if it is onboard, you will need to get into the BIOS and disable it) and replace it. LAN cards are absurdly cheap, in $ terms I think about $10, so it might benefit you to try that. Try to get a LAN card that is on the Linux HCL (see the links on this site).

As for just why it WAS working in Linux, and was broke after your soundcard trouble, but is STILL working in Windows, I've got no other ideas!

Let us know if you get it fixed....!
 
Old 02-02-2005, 08:04 AM   #5
rylan76
Senior Member
 
Registered: Apr 2004
Location: Potchefstroom, South Africa
Distribution: Fedora 17 - 3.3.4-5.fc17.x86_64
Posts: 1,552

Rep: Reputation: 103Reputation: 103
Oh yeah - you say you restarted your PC - did you just reboot it, or physcially switch it off for a few minutes?
 
Old 02-02-2005, 08:27 AM   #6
spage0506
Member
 
Registered: Dec 2004
Distribution: SimplyMepis 3.3.1
Posts: 30

Original Poster
Rep: Reputation: 15
I completely turned my machine off and rebooted it, the modules are not in GRUB, but I have two different kernels listed in GRUB, my new one, and the kernel that came with FC2 (along with WindowsXP which resides on a different drive) I also recently installed NTFS drivers too btw. When the kernel boots, it lists all the stuff it's initializing...and along the way, it tries to build modules for the two sound card drivers (i only have one sound card, and one LAN card) and then it displays that it's initializing eth0, saying that that the process FAILED (in big red evil letters) and consequently that my ppp-oe connection also failed (that only makes sense). I'd hate to have to get a new NIC, since I know that the card is still good--i suppose I'll leave that to a last resort.
Now the Sound card has not been fully installed as far as I know, i.e. Linux does not yet recognize it as a working piece of hardware, could it be using an IRQ? How do I check which IRQ these things are operating on, and can I disable the soundcard temporarily?

Again, Stefan, you're a life saver!
 
Old 02-02-2005, 04:28 PM   #7
rylan76
Senior Member
 
Registered: Apr 2004
Location: Potchefstroom, South Africa
Distribution: Fedora 17 - 3.3.4-5.fc17.x86_64
Posts: 1,552

Rep: Reputation: 103Reputation: 103
Quote:
Originally posted by spage0506
I completely turned my machine off and rebooted it, the modules are not in GRUB, but I have two different kernels listed in GRUB, my new one, and the kernel that came with FC2 (along with WindowsXP which resides on a different drive) I also recently installed NTFS drivers too btw. When the kernel boots, it lists all the stuff it's initializing...and along the way, it tries to build modules for the two sound card drivers (i only have one sound card, and one LAN card)

>Eh? TWO soundcards?! This is getting weirder and weirder. You seem to have some major screwup in your Linux drivers and or config files... Have you considered just reinstalling Linux? Sorry - I can understand that that sounds dreadful, but something is very wrong here i. e. the system tries to start TWO soundcards, and you only have one. This might also tie in to why the NIC is not working.

and then it displays that it's initializing eth0, saying that that the process FAILED (in big red evil letters) and consequently that my ppp-oe connection also failed (that only makes sense). I'd hate to have to get a new NIC, since I know that the card is still good--i suppose I'll leave that to a last resort.

>Rather first try to re-install Linux completely. Oh yeah - make sure that the NIC is plugged in to a hub or something when you install. Hopefully it will be autodetected and you'll be able to configure it correctly. But you seem to already have done this successfully?

Now the Sound card has not been fully installed as far as I know, i.e. Linux does not yet recognize it as a working piece of hardware, could it be using an IRQ? How do I check which IRQ these things are operating on, and can I disable the soundcard temporarily?

>I think if you plug it into the board and switch on the system, it "grabs" an IRQ wherever it can. So even if you can't get any drivers loaded to work with it, it still sits there and "eats" one IRQ line. As for finding what IRQ it is using, try this:

[root@StefanLinux rylan]# /sbin/lspci -v
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440] (rev a3) (prog-if 00 [VGA])
Subsystem: LeadTek Research Inc.: Unknown device 2870
Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 5
Memory at e4000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (32-bit, prefetchable) [size=128M]
Memory at d8000000 (32-bit, prefetchable) [size=512K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 2.0

02:01.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
Subsystem: Creative Labs: Unknown device 8064
Flags: bus master, medium devsel, latency 32, IRQ 9
I/O ports at c000 [size=32]
Capabilities: [dc] Power Management version 1

02:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet Controller (rev 03)
Subsystem: Intel Corp. EtherExpress PRO/100 VE
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at e6000000 (32-bit, non-prefetchable) [size=4K]
I/O ports at c800 [size=64]
Capabilities: [dc] Power Management version 2

This is what is reported on my system - as you can see, my Creative SBLive uses IRQ 9, and my Intel NIC is using IRQ 11. BTW - if you decide to get a new NIC, try getting a PCI plug-in board version of this Intel NIC (mine is onboard) - it works perfectly out of the box with my RedHat 9 Linux version, autodetected & all.

As for disabling the soundcard temporarily, I think the only sure way to stop it using an IRQ is to turn off the system, open the case, physically remove it from the slot it is in, then booting up the system again. If the problem goes away when you remove the soundcard, it must mean that some conflict is going on between the two cards as regards either memory OR IRQ's.

If you see in your lspci -v that both use the same IRQ, there's your problem! How you fix that I don't know however - you might check your soundcard docs to see if you can reconfigure it via jumpers, and I've heard of some cards that you can apparently set in Windows to use some IRQ, which it will hopefully keep using when you reboot into Linux.

As for the logic of it working in Windows and not Linux (now), maybe the Windows driver for either the NIC or the soundcard detects an IRQ conflict and automatically selects another?

Oh yeah keep in mind this all CONJECTURE and I don't guarantee anything!

So, solutions:

1. Use /sbin/lspci -v to see if the NIC is even there, and if it is, try to find out if it is using the same IRQ as the soundcard.
2. If it is in the lspci listing (if it not, don't ask me - then you've got some kind of major hardware headache) and it does not use the same IRQ, mebbe it is trying to use the same area of memory? How you fix that is beyond me. The fact that the kernel reports that it can't allocate memory for the NIC might hint at that?
3. If it does not use the same IRQ, it might still be that both of the devices are trying to use the same memory. Again, no idea how to fix that, and I think this is quite unlikely as well.
4. Still, next try removing the soundcard and starting the system. If the NIC now works, that must mean that it clashes somehow with your soundcard. See if it is at all possible to reconfigure the soundcard to use a different memory area or IRQ.
5. Even if removing the soundcard won't fix it, don't give up!
6. Next, put the soundcard back and reinstall the whole system (it worked previously, didn't it?)
7. Since this whole thang started with you trying to get your soundcard working, maybe you might consider going without sound for a while? Meanwhile I would suggest going to your soundcard supplier's site and seeing if they have any docs about getting it working in Linux.

I still feel a tingle that this has something to do with an IRQ clash... since it all started with your soundcard setup attempt. Have you taken a look at ALSA? It is a generic set of drivers for Linux that might include your card? What card do you have?

Again, Stefan, you're a life saver!
Hehe - thanks. I'm just shooting the bull. None of this actually helps, and it is all conjecture. But hopefully at least it gives you some ideas and makes you feel better and motivates you to keep trying and not abandon Linux....!

Regards,
 
Old 02-03-2005, 09:13 AM   #8
spage0506
Member
 
Registered: Dec 2004
Distribution: SimplyMepis 3.3.1
Posts: 30

Original Poster
Rep: Reputation: 15
Hey Stefan,
I decided to follow your advice, and I'm going to reinstall the whole lot, and upgrade to FC3 while I'm at it. It's too much hassle to try to figure out what went wrong, and perhaps the new OS might actually support my sound card...(a long shot, but maybe).

BTW, any way to find out what hardware is supported by FC? Do you recommend anything better? Any ideas about where I can find decent ext3 drivers for WinXP?

I sincerely appreciate all your time and effort you've spent on me, It definitely makes me feel welcome in the Linux community! I'm not going to give up, I hate Microsoft too much to quit now. I get more help with Linux anyway!

I'll keep you posted on any developments i.e. when I get the new OS up and running.

again, thanks!


--stu


--XP stands for ex-spen-sive
 
Old 02-06-2005, 09:32 AM   #9
rylan76
Senior Member
 
Registered: Apr 2004
Location: Potchefstroom, South Africa
Distribution: Fedora 17 - 3.3.4-5.fc17.x86_64
Posts: 1,552

Rep: Reputation: 103Reputation: 103
Quote:
Originally posted by spage0506
Hey Stefan,
I decided to follow your advice, and I'm going to reinstall the whole lot, and upgrade to FC3 while I'm at it. It's too much hassle to try to figure out what went wrong, and perhaps the new OS might actually support my sound card...(a long shot, but maybe).

>Well if it reasonably recent, and especially if it is some kind of Creative Labs card, I think the percentile of success is very high. It seems IMHO that Creative cards are excellently represented in the Linux world. I use a SBLive 5.1 myself, and it is autodetected and installed perfectly with Rh9, so I think FC3 should have no problems.

>BTW, any way to find out what hardware is supported by FC? Do you recommend anything better? Any i
ideas about where I can find decent ext3 drivers for WinXP?

Check the HCL (Hardware Compatibility List) on this site. As for reading ext3 partitions from XP, sorrrrryy... - no idea. Never needed to do that.

>I sincerely appreciate all your time and effort you've spent on me, It definitely makes me feel welcome in the Linux community! I'm not going to give up, I hate Microsoft too much to quit now. I get more help with Linux anyway!

That's the spirit! Linux takes some effort and commitment, but it rewards in equal measure.

>I'll keep you posted on any developments i.e. when I get the new OS up and running.

again, thanks!

Sure thing man! Sorry this reply is late but I upgraded my system over the weekend. Let me know how you get on.

Kind regards,


--XP stands for ex-spen-sive
 
Old 02-06-2005, 02:04 PM   #10
spage0506
Member
 
Registered: Dec 2004
Distribution: SimplyMepis 3.3.1
Posts: 30

Original Poster
Rep: Reputation: 15
hey, Thanks again for the help, I loaded FC3 and it solved the ethernet problem, but alas, i'm still working on the sound card problem. The soundcard is an Intel chipset build into my motherboard, I still need to look over the HCL, but if it didn't automatically work when I loaded the OS, i'm sure i'm going to have to work with ALSA or the native Intel linux driver... i'll be sure to only try ONE this time!
As for ext3 drivers for XP, i found one (ext2fsd from sourceforge) that works really well. It works on a mount/unmount basis and isn't automatic, but i wrote a batch file and inserted it into the startup group for XP and works just fine.
One thing I was shocked (pleasantly) to discover was that upon setup of FC3 (fresh setup, not an upgrade), the OS automatically set up my internet connection... without having to input all the username/pw settings for my DSL connection... weird and slightly disconcerting, but surprised it did it all itself. Microsoft would never let that happen.

Thanks so much for the feedback!
--stu
 
Old 03-11-2006, 01:25 PM   #11
thustad
LQ Newbie
 
Registered: Nov 2005
Location: Santee, CA
Posts: 1

Rep: Reputation: 0
I had the same problem (SIOCSIFFLAGS: cannot allocate memory). Everything had been working fine then one day I couldn't connect through the network. The computer is at church and I noticed it had been rebooted. After reading this and noticing I too was booting into 2.6.10, I tried to just boot into 2.6.8 and the problem went away.
 
Old 07-17-2015, 09:43 PM   #12
debguy
Member
 
Registered: Oct 2014
Location: U.S.A.
Distribution: mixed, mostly debian slackare today
Posts: 207

Rep: Reputation: 19
i get it too

I get that too. But ONLY ON ONE MACHINE - though more than one use the same kernel and network card. i thought it was debian. nope.

i now think it's a race condition todo with their feature hacks. to reset the network (ifconfig ethx down,up or using dhcp to do the same) you have to stop the card and sockets and drivers and start. do that too quick and something is on an io wait or connection wait or what? race condition. also Changelogs have a few/many flip flop changes complaining of races.

i think answer is: make sure you "sleep 1" and do an ifconfig make sure the card and all are ready before reset / dhcp / coming back up

i haven't fully tested that - but it worked once!

--------

tovalds has been signing on many man new network driver hacks i hardly beleive it

continually they are poking in changes, reverting. they don't appear to be attempting to make anything stable it's a shame. they are crossing their testimony of what is stable quite a bit and frequently even in a single minor release (the 2.6 series shows evidence of)! i'm sure torvalds is hoping eventually it levels out i would distrust that, and go strictly by what works / reports / quats - and ban updates from people that revert without "someone who rarely reverts".

else there's a HUGE risk that the new feature hacks never get fixed and are obstructive, using old version wouldn't work since kernel demands change: leaving a trail of "no going back" - no new kernel works with anything old all broken by hackers. i feel that strongly.

i think the "ultimate answer" if you keep having the problem is to recompile the (same) kernel except with older or newer driver for your card (the older is probably a "known good", all new bugs are probably related to feature hacking)
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Cannot allocate memory Terroth Linux - General 13 02-09-2005 05:22 AM
How to allocate memory for a multidimensional array ? indian Programming 12 11-19-2004 03:37 AM
allocate more memory? sockknitter Debian 3 11-06-2004 05:23 PM
Error: cannot allocate memory ion111 Linux - Software 7 07-04-2004 06:33 AM
unable to allocate memory vedant Linux - Hardware 0 07-15-2003 07:22 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 04:16 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration