I noticed that I can put the driver in monitor mode before starting X. After starting X I get the same errors as before...
I'll dig into this later I guess...
]]>might beworth checking out
]]>However, the ipw2200-issue is still there, but I'm pretty sure it has nothing to do with this particular kernel. I'm now having the same issue with older kernels that previously posed no such problem with ipw2200.
I hate this; it seems after a certain amount of time with every new installation of any distro, I end up having weird unsolvable problems. Now, there's this, and there's the problem of not being able to compile evfs for some outlandish reason.
Heh... I guess I'm gonna be 0.7.1-iso beta tester after all :?
]]>no freezing anymore, but on the other hand I am not running dbus anymore..
]]>andy
]]>I'm experiencing random freezes with the 2.6.14-archck1 kernel. Anyone else?
Also, I'm not able to put the wifi card (ipw2200, I'm using the 1.0.8 drivers) in monitor mode, getting fw-loding errors. I'm pretty sure I could do this before, but I wonder if I'm getting too little sleep or something; cause I can't do that anymore even if I revert back to 2.6.13...
But mostly, I'm curious if anyone else is experiencing the freezes.
i too have had random freezes, but they seem to have been related to dbus-daemon....not sure if it is the new kernel that is incompatible with dbus or if it recently were a new upgrade for dbus =?!
]]>Also, I'm not able to put the wifi card (ipw2200, I'm using the 1.0.8 drivers) in monitor mode, getting fw-loding errors. I'm pretty sure I could do this before, but I wonder if I'm getting too little sleep or something; cause I can't do that anymore even if I revert back to 2.6.13...
But mostly, I'm curious if anyone else is experiencing the freezes.
]]>Build ieee80211 in extra with abs, enter y when it prompts you to overwrite things (yes I know, very techincal). Install it then build ipw2200 with abs. Install it, modprobe it, and you're set. Well atleast it worked great for me. Also if you use wpa_supplicant make sure you are on the 0.4.* development branch or it seems it just wont work.
andy
]]>Since I'm the kamikaze pilot on this one, I'll just spit out all the problems I come over, in hope that it may be of some help.
Firstly, the ipw2200 stuff is now working. It seems to require firmware version 2.2. I used the ipw2200 PKGBUILD to get the firmware. Here it is the rewrite:
pkgname=ipw2200-firmware
pkgver=2.2
pkgrel=1
pkgdesc="ipw2200 Drivers Firmware"
url="http://ipw2200.sourceforge.net/"
depends=('wireless_tools')
source=(http://bughost.org/firmware/ipw2200-fw-2.2.tgz)
build() {
cd $startdir/src
# Install firmware
for i in *.fw
do
install -D -m 644 $i $startdir/pkg/lib/firmware/$i
done
# Install firmware license
install -D -m 644 LICENSE $startdir/pkg/lib/firmware/LICENSE-ipw2200
}
I have no clue about the ext3 module. I'm not using ext3 myself so it's not a problem for me.
]]>There will be no build of 2.6.14-archck in [community] until at least -archck2. Early kernel releases are always slightly buggy and updates come thick and fast so we'll wait on those.
Cheers,
]]>FATAL: Error inserting ext3 (/lib/modules/2.6.14-archck1/kernel/fs/ext3/ext3.ko): Unknown symbol in module, or unknown parameter (see dmesg)
and dmesg says:
ext3: Unknown symbol freezer_state
Reiser4 seems to work perfectly with 4k stacks right now, and I'm about to test hibernation.
Thanks a lot for your work, iphitus!
EDIT: I noticed I get this when the kernel compile is finished:
WARNING: /var/abs/local/repo/pkgbuild/kernel26archck/pkg/lib/modules/2.6.14-archck1/kernel/fs/ext3/ext3.ko needs unknown symbol freezer_state