**** BEGIN LOGGING AT Sat Jan 19 02:59:59 2013 Jan 19 03:02:00 mmagcww: ifconfig never does. thats the job of udev on GNU/Linux systems. on Android it seems to be vold or something else Jan 19 03:18:39 I just found a page on the Dream at htc-linux.org that says the msm_wifi module is suppose to find it in /lib/firmware. They say that if it doesn't load it the first time to remove it and try loading it again. I've done this multiple time and still nothing. Jan 19 03:19:39 I guess I should see an entry in dmesg that shows it either loading or attempting to load the firmware Jan 19 03:21:12 I hate to seem a bit impatient, I just can't wait to get this all in one place Jan 19 03:21:43 should be something in dmesg, yeah Jan 19 03:28:02 even if I have the wrong firmware for some reason, it should show it choking on it when it tries to load it. By the way, I used the firmware found on the "running OpenMoko on the HTC Dream" page Jan 19 03:32:49 has anyone tried to apply the patch http://htc-linux.org/wiki/index.php?title=Dream for PSM, how about adding it to cfg80211 without the patch -- any experience with that? Jan 19 03:47:54 I must have done something, I'll try again with a fresh image, both full and lite and if that doesn't work I'll try with a older image Jan 19 03:51:08 so there is nothing dmesg? Jan 19 03:53:13 No, I'm at a dead end, I'm thinking if I try some more images I can at least rule out myself as being the culprit Jan 19 03:53:51 I've crashed the thing many times, used fsck to fix it many times, who knows Jan 19 03:54:49 maybe the driver just doesn't emit anything to dmesg, I guess you will need to look at the code to figure it out Jan 19 03:55:35 good suggestion, though I'm not there yet Jan 19 03:55:52 Brute force, caveman smash Jan 19 03:57:40 I have found a very good tutorial on learning C, the best I've ever found "The GNU C Programming Tutorial" Jan 19 03:58:05 brute force is not always the best way Jan 19 04:00:31 C programming is a fair bit different inside the kernel, http://kernelnewbies.org/ Jan 19 04:15:51 Good to know, I'll have to reference that site as well. Jan 19 06:18:09 The thing that gets me about this problem is that this is a clone, it's suppose to work, and I just feel shitted out, wasted a whole day on this problem. Sure if I had more experience I could have sorting things out sooner but that's not the case. I really wish the documentation was better, it really is skimpy, at least coming from a guy that is not a software engineer. I'm taking notes as I go, gathering any useful pointers that I may be able to of Jan 19 06:19:12 mmagcww: truncated after "able to of" Jan 19 06:19:30 fer. I guess that's the point, it doesn't matter if big brains know it all can figure it out, it's called development. Jan 19 06:20:53 mmagcww: ifconfig doesn't load the firmware, the kernel drivers request the firmware and then kernel asks udev and it loads it for the kernel. Jan 19 06:21:04 mmagcww: so the place to put the firmware files depends on udev (or replacement) config. Jan 19 06:22:32 The explination I received says that msm_wifi looks for the firmware at /lib/firmware Jan 19 06:23:04 It could have been nice to have an explination of where to put the firmware files, that's a no brainer Jan 19 06:23:06 mmagcww: msm_wifi doesn't look for the firmware, it just requests it from the kernel. And then the kernel requests it from udev. Jan 19 06:23:31 mmagcww: that depends on the particular distro, but /lib/firmware is about the same on all major distros, so it's sort of "standard". Jan 19 06:26:08 Well it doesn't want to work for me, and I need a break, a C tutorial break Jan 19 06:26:50 mmagcww: what do you see in dmesg? Jan 19 06:30:25 I've seen firmware get loaded more then once over the years and it's always a very clean entry in dmesg, when the msm_wifi module is loaded, I get nothing about firmware loading. When I try and test out the wlan0 with ifconfig up, it freezes up on me. I'm sure I could be doing alot of trouble shooting better, though like I said, I need a breather Jan 19 06:31:21 mmagcww: if it freezes and nothing is output to dmesg it means there's some other important issue. Do you mean the whole devices becomes unresponsive? Jan 19 06:32:22 no, I can still move through windows, execute other commands -- it's only ifconfig that freezes Jan 19 06:33:13 mmagcww: have you tried looking into dmesg after that? Jan 19 06:33:29 yep, no change Jan 19 06:34:02 mmagcww: is udev running on your system? Jan 19 06:34:25 one sec Jan 19 07:09:48 opkg info on udev showed that it was not installed, I installed it and reboot Jan 19 07:18:12 mmagcww: but were you probably running another implementation? Jan 19 07:24:17 I didn't really think to check before installing the package under the opkg manager, I only checked that it was not installed, I didn't think that there would have been another udev already on the system Jan 19 07:24:57 I just uninstalled it and am rebooting Jan 19 07:49:22 PaulFertser: Well it's off to bed for me, I'll have to get back at this tomorrow, goodnight Jan 19 07:59:26 mmagcww: night Jan 19 08:32:01 mmagcww: ifconfig freezes in your shell, or your whole system freezes? Jan 19 08:32:20 oops i was scrolled up **** ENDING LOGGING AT Sun Jan 20 02:59:58 2013