[05:34] <Gunner_Sr> greetings, what functionality if any of i8k was introduce into the kernel?
[05:37] <Gunner_Sr> The reason I asked in I notice that the version number is different in gutsy than Massimo's one of 1.25..
[05:38] <mjg59> It hasn't been touched in the kernel since 2005
[05:38] <mjg59> If there's a more recent version externally, the author should push it into the kernel
[05:42] <Gunner_Sr> mjg59: thanks, I saw those updates. I am trying to get in touch with the author to see about getting rev'd for new dell models.
[05:44] <Gunner_Sr> mjg59: a couple of issues I am seeing is that it is not supporting a second fan well, I think this is the GPU one. The other is support for x86_64 support.
[05:47] <mjg59> The recommended way of interfacing with Dells is via libsmbios
[05:47] <mjg59> Dell are pretty anti i8k
[05:48] <Gunner_Sr> yep, I hear you on that one. what tool/app can interface to libsmbios?
[05:49] <Gunner_Sr> mjg59: okay found it. Google'd it. :-)
[05:52] <mdomsch> i8k is somewhat dangerous as the authors don't really know how Dell's SMIs work
[05:52] <mdomsch> libsmbios does
[05:55] <Gunner_Sr> mdomsch: the problem is that without i8k, today their is not good way on managing fans, etc.
[06:05] <Gunner_Sr> thanks. See you all later. Cheers.
[07:53] <kraut> moin
[13:14] <seb128> hi
[13:14] <seb128> is there an ubuntu specific patch which makes /proc/pid/smaps not being user readable?
[13:28] <BenC> seb128: 'cat /proc/$$/smaps' works for me
[13:29] <BenC> seb128: guess you have to own the process
[13:29] <seb128> BenC: I should have specified for an another user process
[13:29] <BenC> seb128: /proc/1/smaps shows 0444, but I can't read it as normal user
[13:29] <seb128> right
[13:29] <seb128> $ cat /proc/$(pidof cupsd)/smaps
[13:29] <seb128> cat: /proc/6049/smaps: Permission denied
[13:29] <BenC> don't think that's ubuntu specific
[13:30] <seb128> that makes gnome-system-monitor not display the memory usage of those processes correctly
[13:30] <seb128> and upstream says it works fine using a vanilla kernel
[13:30] <seb128> 2.6.23
[13:30] <BenC> what about a vanilla 2.6.22
[13:30] <zul> # enable /proc/$pid/maps privacy so that memory relocations are not
[13:30] <zul> # visible to other users.
[13:30] <zul> kernel.maps_protect = 1
[13:31] <seb128> BenC: I'll ask him
[13:31] <seb128> zul: is that a config option?
[13:31] <zul> yep its in /etc/sysctl.conf
[13:31] <zul> default btw
[13:33] <seb128> zul: right, changing that makes it work correctly
[13:33] <zul> seb128: cool
[16:35] <adam__> hi all
[16:36] <adam__> anybody here??
[17:49] <Ludwik> hi
[17:49] <Ludwik> Sorry to bother you, but people in #edubuntu told me you may be able to help me. I work for a high-school in Poland (Europe). We have more than 20 laptops we use in classrooms. In previous Ubuntu versions, at least since 6.06 our WiFi cards worked great. But after upgrading to Gutsy WiFi stoped working
[17:49] <Ludwik> I found a thread about this issue in Ubuntu Forms, but I didn't find the solution
[17:49] <Ludwik> It's a major problem fot us since we use WiFi not only to connect to the internet but also to network the laptops together - share user accounts and data
[17:50] <Ludwik> I'm new here. Is it ok for me to ask such questions on this channel and will anybody be able to help me?
[17:51] <IntuitiveNipple> Ludwik: what is the WiFi card/chipset make/model/version (PCI ID) ?
[17:52] <Ludwik> it's a rt2500-based PCI card
[17:52] <Ludwik> Here is the thread - http://ubuntuforums.org/showthread.php?t=582033
[17:53] <IntuitiveNipple> Ahhh... I have seen a few issues with the RT drivers during the Gutsy development cycle
[17:53] <IntuitiveNipple> I did fix it for a couple of people but I don't remember how right now
[17:54] <Ludwik> Aha... it shows the avaliable networks, but is unable to connect, at least to our WPA-protected network
[17:54] <Ludwik> Judging from this thread many paople have similar issues
[17:56] <IntuitiveNipple> What kind of WPA? WPA-PSK, WPA2-PSK, AES ?
[17:57] <Ludwik> WPA-Personal, TKIP
[17:58] <Ludwik> (I can change WPA settings in the router, though, if this will help)
[18:00] <IntuitiveNipple> I see your comment in the forum. Have you posted a bug report to launchpad ?
[18:00] <Nafallo> Ludwik: open network + ipsec? :-)
[18:01] <Ludwik> No, but there are other posts saying that there is already one - with a low priotyty asigned, though
[18:02] <IntuitiveNipple> Ludwik: The best place to register the problem is as a bug report in launchpad; that is where the developers look
[18:04] <Ludwik> IntuitiveNipple: but there is already bug 126407, so I shouldn't open a new one, should I?
[18:04] <ubotu> Launchpad bug 126407 in linux-ubuntu-modules-2.6.22 "[Gutsy] rt2500 driver missing from rt2x00 drivers in linux-ubuntu-modules-2.6.22-8-generic (dup-of: 118205)" [Undecided,Fix released] https://launchpad.net/bugs/126407
[18:04] <ubotu> Launchpad bug 118205 in linux-ubuntu-modules-2.6.22 "Gutsy kernel 2.6.22-7-generic missing rt61 module" [High,Fix released] https://launchpad.net/bugs/118205
[18:05] <IntuitiveNipple> Ludwik: Is the ESSID hidden ?
[18:05] <Ludwik> No, it isn't
[18:06] <IntuitiveNipple> Ludwik: no, add a comment on to a bug you feel is most like your experience. Those two you mention aren't the ones though
[18:17] <Ludwik> IntuitiveNipple: 126407 isn't the one? I'm not sure I understand (among other things my English isn't so great), but some people in the forums seem to suggest that the problem is that Ubuntu 7.10 doesn't includes the previous rt2x00.serialmonkey.com legacy driver, and only includes some new beta driver, that dosn't support some things right now.
[18:18] <IntuitiveNipple> Ludwik: Oh sorry, maybe I misunderstood your problem. You said it won't connect. That's different to using a different driver.
[18:19] <Ludwik> The problem is it shows the avialiable networks, but isn't able to connect (at least hen I choose our WPA protected one). I understand (thought I may get it wrong) that some people suggest it's because the new driver isn't complete yet.
[18:19] <Ludwik> *when
[18:20] <Ludwik> (and the old one isn't included anymore)
[18:25] <IntuitiveNipple> Ludwik: I'd suspect this is a report closest to your issue: Bug #134962
[18:25] <ubotu> Launchpad bug 134962 in network-manager "rt2500: network-manager fails to join wireless networks" [Medium,Incomplete] https://launchpad.net/bugs/134962
[18:26] <Ludwik> Yeah, I guess that's it. Thank you.
[18:26] <Ludwik> Also, at this very moment in the forum thread someone added a link to this instructions - http://ubuntuforums.org/showthread.php?t=584657
[18:26] <IntuitiveNipple> Ludwik: If you can attach the output of lspci -nn so the precise chipset ID is known
[18:27] <Ludwik> To the bug repport? Ok.
[18:32] <IntuitiveNipple> Ludwik: That forum thread you just pointed to - that reminded me that I also discovered the 'set' failure issue and I found a workaround for that user, but I can't remember now how we did it
[18:33] <IntuitiveNipple> Ludwik: But I know for one of the users I helped, I did build a the kernel module for them, so that might have been it
[18:40] <Ludwik> (I posted a new post to the bug 134962, and I see you also did so)
[18:40] <ubotu> Launchpad bug 134962 in network-manager "rt2500: network-manager fails to join wireless networks" [Medium,Incomplete] https://launchpad.net/bugs/134962
[18:51] <Ludwik> IntuitiveNipple: I have to go. Thank you very much for all your halp, really. I obviously subscribed to the bug, so I'll recived all the updates.
[18:52] <IntuitiveNipple> Ludwik: I'll do some digging but I don't have access to an rt2000 device so I can't do much more
[18:53] <Ludwik> ok, thank you anyway
[20:37] <zul> interesting i have volume muted but I can still hear sounds coming out of my speaker
[21:53] <pina> if you've been hacked, how can you find out what has been changed/added or compromised in the server
[21:53] <pina> look at binaries?
[21:53] <pina> or the kernel?
[21:54] <pina> like a "ps" that's been modified to not show the attacker's processes
[22:34] <glance> gutsy kernel pepole around?
[22:35] <glance> im wondering why the downgrade of unionfs?
[22:35] <glance> the downgrade broke a lot of stuff, and it was quite late in the process.
[22:42] <mjg59> Because the new version doesn't work
[22:43] <mjg59> It's unusably unstable right now
[22:43] <Nafallo> mjg59: hi mate :-)
[22:45] <glance> https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/150788 sas something about a backport of some bugfix?
[22:45] <ubotu> Launchpad bug 150788 in linux-ubuntu-modules-2.6.22 "unionfs problems with linux-ubuntu-modules-2.6.22-13-generic_2.6.22-13.34_amd64.deb " [Undecided,New] 
[22:46] <mjg59> Yes, it didn't work
[22:46] <mjg59> Or, rather, it partially worked
[22:46] <mjg59> But we were still getting oopses
[22:48] <glance> hmm...
[22:48] <glance> what was the problem with the newer unionfs?
[22:49] <mjg59> It's unusably unstable right now
[22:49] <glance> it worked in the cases i tested.
[22:49] <mjg59> And it didn't in the cases we tested
[22:49] <mjg59> Like, say, the install CDs...
[22:50] <glance> hmm,... =/ ok.
[22:50] <glance> thats reason to kick it out.
[22:51] <mjg59> We needed something that works for the CDs. It can be updated afterwards if necessary, but the CDs are kind of final...
[22:51] <glance> yes, im using unionfs in fai so i can update,
[22:53] <glance> tought it was time to reinstall my testclients to get them in a good state now when the release is done but it brok.
[23:04] <glance> hmm.. a old kernel, my favorite hex editor (vim) on the version magic and the problem is solved.