You are not logged in.
Pages: 1
Hi
I tried to switch mkinitcpio (even though I have no idea what it actually is) - and it went fine ... I just followed the wiki. But I can't get my ipw3945 wireless card to work.
From kernel.log
Aug 28 12:09:24 E4484Marianne ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.0.12dmpr
Aug 28 12:09:24 E4484Marianne ipw3945: Copyright(c) 2003-2006 Intel Corporation
Aug 28 12:09:24 E4484Marianne ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Aug 28 12:09:24 E4484Marianne ipw3945: ipw3945.ucode load failed: Reason -2
Aug 28 12:09:24 E4484Marianne ipw3945: Could not read microcode: -2
Aug 28 12:09:24 E4484Marianne ipw3945: probe of 0000:05:00.0 failed with error -2
What is reason -2? I have a ipw3945.ucode file on my system in /lib/firmware
Offline
mkinitcpio and wireless networking are completely unrelated.
Offline
"Could not read microcode" sounds like you need some firmware or that daemon or something... ipw3945 pisses me off because they shirk the GPL like asshats, so I refuse to figure it out. Try the wiki, though.
Offline
ipw3945 pisses me off because they shirk the GPL like asshats, so I refuse to figure it out.
I understand that. I have similar opinion. But I am not aware of any other reliable way to use Intel 3945 wifi card. Are you?
M.
# edit: typo
What happened to Arch's KISS? systemd sure is stupid but I must have missed the simple part ...
... and who is general Failure and why is he reading my harddisk?
Offline
No, but I'd make sure you followed the wiki entry about setting this up. iphitus knows much more about ipw3945, but he's shying away from the forums right now... you may be able to reach him on IRC though.
Offline
to phrakture: Not a problem, I have my ipw3945 up and running for quite a time. You got the point, there really is a problem with firmware. But I'm not the guy who posted this thread and I was reflecting only to your opinion since I really thought you may know about different way of how to make that card working without having need to use ipw3945
to Molinero: All has been said, you have to get the firmware to proper place. Look at http://ipw3945.sf.net for howto. If the problem persist, post it here, the catch really may be in the ramdisk itself then.
-M.
What happened to Arch's KISS? systemd sure is stupid but I must have missed the simple part ...
... and who is general Failure and why is he reading my harddisk?
Offline
But I'm not the guy who posted this thread
Oh crap, I need to pay more attention 8)
Offline
i mean network on early userspace makes only sense if you use something like netboot.
add the firmware hook at least that the firmware is included in the image.
Don't know it ipw needs an additional daemon to run too
Offline
Okay - now I'm confused.
1: Does the ipw3945 problem have something to do with the new boot image I made? Or is it unrelated as brain0 says?
2: ipw3945 is working with my current conf (ipw3945 installed via pacman and with a daemon) - is all I need just a new firmware?
3: What is the difference between the way it works now and the way it is supposed to work after the mkinitcpio install thingy?
I followed the wiki and I have added net.
So what do I really need to do?
Offline
are you booting something like a pxe/netboot thing?
if not then you don't need the net hook at all on bootup, also the firmware hook is then useless.
in early userspace you need only stuff that is needed to mount the root filesystem, if your root filesystem is not on a network like nfs, then you don't need it.
Offline
Your network at runtime has nothing to do with mkinitcpio. You need the net hook if you are BOOTING off of an NFS share. I'm 99% certain you are not. Therefore you have no need of the net hook.
Offline
Okay - I'm not using net boot. I removed the net hook from the mkinitcpio.conf file.
Still if I boot with the new boot image that I made the way it says in the wiki then I cannot use my wireless card. iwconfig tells me no wireless extensions on my wifi card - but if I boot with my old boot image it works perfectly.
I really do not care whether or not this is caused by mkinitcpio.
I did not post here to be YELLED at just because I don't know what the stupid mkinitcpio does and why I need it/don't need it. All I did was read this:
This is an announcement for those of you still using mkinitrd to boot your machines.
For some time now there has been a notice upon kernel install that mkinitrd will be replaced by mkinitcpio once the 2.6.18 series is released. That time is quickly approaching. To anyone who has not at least tried mkinitcpio (/boot/kernel26.img) is advised to try it and report any issues on the bug tracker before this goes live.
Thank you,
phrakture
Hope you enjoyed yourself making me feel bad.
Offline
sounds like a real strange problem to me then.
Offline
I really do not care whether or not this is caused by mkinitcpio.
I did not post here to be YELLED at just because I don't know what the stupid mkinitcpio does and why I need it/don't need it.
Ah, the wonders of text-based communication. No one yelled at you. There's no reason to get defensive.
The confusion comes from the fact that you stated in your original post that this was caused by mkinitcpio. This may be indirectly caused by mkinitcpio, but more likely, it's caused by udev loading the module in early userspace (when the firmware is not there).
Can you post your menu.lst (or lilo.conf) along with your mkinitcpio.conf?
Offline
custom 2.6.19.1 kernel, ipw3945-1.1.2, ieee80211-1.2.15. All downloaded from sourceforge. I don't have and never had any problems with intel 3945. works really well.
I would suggest to get ipw3945-1.1.3 though (fixed compiling problems with config.h)
I have
in /etc/rc.conf
MODULES=(........ ipw3945 .........)
DAEMONS=(.......... @ipw3946d ...............)
and nothing related to network in /etc/mkinitcpio.conf
That is all.
Offline
Pages: 1