**** BEGIN LOGGING AT Fri Sep 12 02:59:57 2008 Sep 12 07:25:24 any acx-mac80211 experts around? Sep 12 15:13:30 Warning: busybox hostid command segfaults! Using r12570 on ixp425. Sep 12 16:55:03 hi, anyone familiar with the rt2x00 wireless drivers? Sep 12 16:56:46 i am, a bit Sep 12 17:35:26 is it possible to get a readable baacktrace on a kernel oops in openwrt? Sep 12 17:35:38 yes Sep 12 17:35:46 enable KALLSYMS in kernel_menuconfig Sep 12 17:36:10 thx Sep 12 17:37:51 nbd: are you going to be available within the next half-hour or so? Sep 12 17:39:12 probably not Sep 12 17:39:23 :( Sep 12 17:43:51 sn9: I've got the rt2500pci working on an ixp425 system. I'm using the 2.6.26 drivers. The issue is how to set up openwrt to use it properly. for now I've configured manually. Sep 12 17:51:51 MateIn4: you need hostapd or hostapd-mini to use them in ap mode Sep 12 17:53:22 yes, the issue is that they use the mac8011. but under packages/mac80211 it's not really set up to use the kernel drivers in 2.6.26. it's a bit of a mess. Sep 12 17:53:41 what's not set up? Sep 12 17:54:19 openwrt provides a way to configure mac80211 devices Sep 12 17:54:54 just use 'option type mac80211' in /etc/config/wireless Sep 12 17:55:31 that should already be in the file automagically Sep 12 17:55:45 yeah Sep 12 17:58:05 the problem is that the mac80211 package uses compat-wireless and downloads the rt2x00 legacy drivers (i think). I want to use the kernel drivers. Sep 12 18:01:00 i think you're confused Sep 12 18:01:33 you can either use the legacy drivers or the kernel (compat-wireless) drivers, not both Sep 12 18:02:16 you should not need the legacy drivers for any kernel after 2.6.22 Sep 12 18:04:26 I'm using the kernel drivers. But where do I get the configuration scripts (/lib/wifi/mac80211.sh)? Sep 12 18:05:02 if you use the mac80211 pkg and the rt2x00 package, you should already have them Sep 12 18:06:48 I'm confused. isn't the packages/mac80211 the legacy drivers? it contains packages/mac80211/files/lib/wifi/mac80211.sh Sep 12 18:07:31 no, it's compat-wireless, which are the only available drivers that support ap mode Sep 12 18:08:30 the legacy drivers are the non-mac80211 things for pre-2.6.22 kernels Sep 12 18:08:43 so what do I select on the menuconfig to get the proper scripts? Sep 12 18:09:04 rt2x00 and hostapd Sep 12 18:09:43 remove mac80211 from kernel_menuconfig, too Sep 12 18:10:44 where do I find the rt2x00? Sep 12 18:11:07 use the / key to search Sep 12 18:12:09 ok, found it. I'll rebuild. Sep 12 18:16:53 well, it seems that I can't select rt2x00 kernel module because it doesn't work with the 2.6.26 kernel (only 2.6.24 and 2.6.25). Sep 12 18:17:17 this is a current trunk, right? Sep 12 18:18:20 I'm using r12570 Sep 12 18:18:24 ok Sep 12 18:19:10 i didn't look closely at how old the mac80211 and rt2x00 snapshots are in svn, but [florian] put them there Sep 12 18:19:18 [florian]: around? Sep 12 18:20:29 The test should be for kernels greater than 2_6_24. Is there a way to check for that. I can hack and add 2_6_26 so menuconfig will find it. Sep 12 18:20:45 in the makefile, you mean? Sep 12 18:20:53 yes Sep 12 18:21:58 in package/rt2x00/Makefile -- the exact line should be obvious Sep 12 18:24:32 I don't have that package! there's a package/rt2500 though. Sep 12 18:26:40 oh, i see, rt2x00 is separated into its individual drivers now Sep 12 18:29:11 but I don't see how this driver is going to create the /lib/wifi/mac80211.sh Sep 12 18:31:15 forget rt2500 and select mac80211 -- then you'll see rt2x00 Sep 12 18:33:01 rt2500 is useless; you need rt2x00 Sep 12 18:33:49 [florian]: never mind Sep 12 18:33:58 i agree. I don't see an rt2x00 option when I select kmod-mac80211. Sep 12 18:34:33 what do you see? Sep 12 18:35:46 nothing else shows up when I select it. Note: target is big endian, ixp425. the rt2500 is working when I use kernel_menuconfig. Sep 12 18:35:56 line 57 of package/mac80211/Makefile is the problem Sep 12 18:36:44 yes, let me hack some and report Sep 12 18:38:51 OK, changed line 57 and can now select the rt2500. Rebuilding now. Will test. Sep 12 18:41:19 [florian]: if the above works, can you please remove line 57? thanx Sep 12 18:47:56 x-alina: do you got my question in #freifunk ? Sep 12 18:49:55 xMff: No, sorry, whats your question? Sep 12 18:50:13 I'll pm you Sep 12 18:51:01 The IPv6-Servers has some problems at the moment. :/ Sep 12 18:51:53 build failure: seems that it's building compat-wireless-2008-08-06 and that is looking for cfg80211.ko Sep 12 18:52:38 that is part of compat-wireless Sep 12 18:52:40 this get's back to my original point. I've got the kernel 2.6.26 rt2500 support working. I just want the user level scripts. Sep 12 18:53:03 make sure cfg80211 is DESELECTED in kernel_menuconfig Sep 12 18:55:56 yes, I had cfg80211 selected. rebuilding now... Sep 12 19:11:20 bad news: the compat-wireless version doesn't work. get kernel load errors on the rt2* modules. Now I remember doing this a few weeks ago and that's why I switched to the kernel versions of the drivers. What's the benefit to this version? Sep 12 19:11:37 what are the errors? Sep 12 19:11:47 pastebin, please Sep 12 19:13:28 when loading rt2x00lib: Unknown symbol rt2x00lib_load_firmware (1st error) Sep 12 19:19:55 that is irrelevant to rt2500-pci Sep 12 19:21:04 that's the point, when I use kernel_menuconfig, the rt2x00lib is built without that symbol dependency. Sep 12 19:21:47 the symbol dependency only appears if you select rt73 or rt61 Sep 12 19:23:46 I'm not selecting those, only rt2500-pci Sep 12 19:27:20 and rt2x00-lib is deselected in kernel_menuconfig, right? that's the only other thing you could have missed Sep 12 19:27:37 ALL wifi things must be deselected Sep 12 19:29:33 I'm double checking but I don't see it. I had this problem before and then switched to the kernel drivers. I'll dig some more. Sep 12 19:35:23 rt2x00lib is normally built without that symbol for rt2500pci, but if you previously built rt2500pci against a rt2x00lib with rt61pci or rt73usb also built, you get this issue Sep 12 19:35:55 if you have a rt2500pci in kernel_menuconfig, that would do it Sep 12 19:36:30 you should "make target/linux/clean" AFTER kernel_menuconfig, not before Sep 12 19:37:19 the kernel must already be built BEFORE kernel_menuconfig (stupid, i know) Sep 12 19:37:20 nbd: Is it possible to add an option to the sysupgrade-script, that fork and wait 3 sec. or so for the reboot, so that LuCI has the time to send the full XHTML-Page to the User? Sep 12 19:37:45 MateIn4: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 12 19:43:19 I was not doing a make target/linux/clean. I did find that I had the "Wireless" extension option set. Turned that off but now it doesn't build because the kmod-madwifi is automatically selected and fails the kernel test. Not sure who is requiring kmod-madwifi because it's not in my configuration. Sep 12 19:43:34 x-alina: sure Sep 12 19:46:21 MateIn4: the target profile may be selecting it, but that doesn't matter; it must only be deselected in kernel_menuconfig, not menuconfig Sep 12 19:48:23 the only wireless related option that was set in the kernel_menuconfig was "Wireless extension". If I take that off, the madwifi doesn't build because it's selected by the generic ixp4xx profile. Sep 12 19:48:43 nbd: cool... thx. :) Sep 12 19:51:43 nbd * r12572 /trunk/package/base-files/files/ (lib/upgrade/common.sh sbin/sysupgrade): sysupgrade: add optional delay before rebooting Sep 12 19:53:18 MateIn4: yes, madwifi needs wext, but that should be ok Sep 12 19:53:54 just not anything superseded in compat-wireless Sep 12 19:55:55 nbd * r12574 /trunk/package/madwifi/patches/106-get_arch.patch: madwifi: fix x86_64 compilation Sep 12 19:56:01 nbd * r12573 /trunk/package/madwifi/ (ath_hal-20080815.tgz ath_hal-20080909.tgz): madwifi: upgrade to 2008-09-09 HAL Sep 12 20:28:34 lars * r12575 /packages/XOrg/lib/libast/Makefile: fix libast build: s/libtol/libtool/ Sep 12 20:32:47 nbd * r12576 /packages/libs/fftw3/ (. Makefile patches/ patches/001-makefile.patch): add fftw3 (patch from #3987) Sep 12 20:32:53 nbd * r12577 /packages/XOrg/lib/libXaw/Makefile: remove obsolete dependency on missing package libXp Sep 12 20:50:13 lars * r12578 /packages/XOrg/lib/gtk1/Makefile: Cleanup gtk1 Makefile. Sep 12 21:01:04 lars * r12579 /packages/libs/libdvbpsi4/Makefile: Cleanup libdvbpsi Makefile. Sep 12 21:10:20 lars * r12580 /packages/sound/lame/Makefile: Cleanup lame Makefile. Sep 12 21:32:45 ^^ heh, not often you get to make that joke Sep 12 21:33:12 it's like the old Munchkin "you have no class" one Sep 12 21:33:12 lars * r12581 /packages/libs/libnetfilter-queue/Makefile: Cleanup libnetfilter-queue Makefile. Sep 12 21:36:12 lars * r12582 /packages/libs/libnetfilter-queue/Makefile: Add libtool fixup to libnetfilter-queue. Sep 12 22:14:52 lars * r12583 /packages/libs/libol/Makefile: Cleanup libol Makefile. Sep 12 22:23:38 lars * r12584 /packages/libs/libmpcdec/Makefile: Cleanup libmpcdev Makefile. Sep 13 00:09:03 thepeople * r12585 /trunk/package/base-files/files/ (etc/init.d/led sbin/led.sh): make option name optional Sep 13 00:29:16 lars * r12586 /trunk/include/autotools.mk: Sep 13 00:29:16 Change libtool fixup behaviour. Still ugly but it works until we have a real Sep 13 00:29:16 fix. Sep 13 00:29:16 It uses a InstallDev/Post hook to find all .la files which are going to be Sep 13 00:29:16 installed in the staging dir and prefixes every path in those files which starts Sep 13 00:29:17 with /usr/lib with $(STAGING_DIR). Sep 13 02:32:32 OK, I'm back with some observations on trying to build the rt2500pci driver. Recall that after patching the packages/mac80211/Makefile to allow building with the 2.6.26 kernel, the resulting kernel modules don't load because of a missing symbol. Sep 13 02:36:03 After looking at the compat-wireless code, I see that the generated include/linux/compat_autoconf.h is basically defining all symbols not just for those that are selected, hence the dependency on a symbol (rt2x00lib_load_firmware) that is not valid. Sep 13 02:36:39 no, it should use config.mk Sep 13 02:38:30 it does use config.mk but the resulting compat_autoconf.h has lines like: Sep 13 02:39:03 #ifndef CONFIG_RT61 then #define CONFIG_RT61 1 Sep 13 02:39:14 lars * r12587 /packages/net/asterisk-1.4.x/patches/030-acinclude.patch: Fix asterisk-1.4.x build. Sep 13 02:39:15 It doesn't make sense to me. Sep 13 02:42:11 it should only contain that based on config.mk Sep 13 02:45:15 well, I just found an easy work around: select the RT61 module as well! this way the symbols are defined as well. A bit of a kludge but it gets the job done. Sep 13 02:45:15 your missing symbol is a result of a failure to clean -- rt2500pci references it, but rt2x00lib is built without it Sep 13 02:46:05 that kludge will only cause more problems until you fix the root cause Sep 13 02:46:20 No, this is a problem with the source. I've completely rebuilt openwrt from scratch to make sure I didn't have any lingering dependencies. Sep 13 02:47:48 it is not possible for the rt2500pci module to reference the symbol unless the config specifies rt61 or rt73, in which case it's not possible for rt2x00lib not to contain it Sep 13 02:49:23 I think the problem is that the compat_autoconf.h defines symbols that aren't selected so the rt2x00lib assumes that there's an rt61 driver but the rt2x00firmware.c is not liked to the rt2x00lib. Sep 13 02:49:46 it will not define symbols not specified by config.mk Sep 13 02:50:30 it's doing it. Sep 13 02:50:42 then regenerate the .h Sep 13 02:51:28 As I said, I've completely rebuilt openwrt from scratch. everything was regenerated. Sep 13 02:51:43 that's not what i mean Sep 13 02:54:43 please explain Sep 13 02:57:32 lars * r12588 /packages/net/asterisk-1.4.x/Makefile: Rebuild the package if the selected modules have changed. **** ENDING LOGGING AT Sat Sep 13 02:59:56 2008