[01:22] <martalli|home> .msg nickserv identify jyestham
[01:23] <martalli|home> ugh
[06:56] <ajmorris_> i installed mozilla thunderbird 2.0, and now it won't run as mozilla-thunderbird cannot be found, in the installed files section of thunderbird there is no mozilla-thunderbird in /usr/bin, is version 2.0 broken?
[01:36] <nopcode> hey
[01:36] <nopcode> why is there a kernel package namend 2.6.22 when no such kernel exists according to kernel.org?
[01:37] <Tm_T> nopcode: because it's unstable version?
[01:37] <nopcode> uhm
[01:38] <Tm_T> unstable here means "not released as stable yet"
[01:38] <nopcode> yeah but then it'd be 2.7
[01:38] <Tm_T> no
[01:38] <Tm_T> that would be unstable unstable
[01:39] <nopcode> hm
[01:39] <nopcode> ok
[01:39] <nopcode> i just saw 2.6.26 is the very latest unstable
[01:39] <nopcode> are there packages for that?
[01:39] <nopcode> my realtek r8169/r8111 gigabit NIC doesnt work
[01:40] <nopcode> (that is with 2.6.22)
[01:40] <Tm_T> not that I know, but noone stop you building one
[01:41] <digitalpardoe> nopcode: 2.6.26 could be the latest unstable but it doesn't mean ubuntu are going to distribute it.
[01:41] <nopcode> well i'd rather want networking before i start getting the dependencies for kernel building
[01:41] <nopcode> for obvious reasons
[01:42] <digitalpardoe> In what way doesn't your ethernet work?
[01:43] <nopcode> the drivers loads then it says "link down"
[01:43] <nopcode> and dhcp doesnt answer
[01:44] <digitalpardoe> Did it work in Feisty? If you really want to be kernel building you should try Gentoo rather than Ubuntu.
[01:45] <borschty> you could install the 2.6.20 kernel, which i think is still in the repos
[01:45] <nopcode> i am using feisty
[01:45] <nopcode> i just took the kernel package from gutsy
[01:45] <nopcode> dude what? i always build my own kernel
[01:46] <markc> nopcode: do you use a nvidia gfx card ?
[01:46] <nopcode> dont tell me you're not expected to do that in ubuntu
[01:46] <digitalpardoe> Revert to the feisty kernel then and see if your drivers load.
[01:46] <nopcode> markc: yeah
[01:46] <markc> working okay ?
[01:46] <nopcode> digitalpardoe: i only upgraded because it didnt work there with 2.6.20
[01:46] <nopcode> markc: on windows, yeah
[01:47] <nopcode> with ubuntu i had to remove the "splash" option because that gave me a permanent black screen on boot
[01:47] <markc> nopcode: I just joined the channel, so you compiled 2.6.22-1-rt yourself and don't have nvidia.o ?
[01:47] <nopcode> i dont care about nvidia now
[01:47] <nopcode> i need to get my NIC to work
[01:47] <nopcode> a realtek r8169/8111 something gigabit nic
[01:47] <nopcode> i'm running the 64 bit version btw
[01:47] <markc> nopcode: right, so your nvidia is not working either
[01:48] <nopcode> what?
[01:48] <nopcode> i dont expect it to work
[01:48] <nopcode> since i didnt install any drivers yet
[01:48] <nopcode> i'm getting framebuffer-X11 i think
[01:48] <markc> so you didn't try to rebuild the restricted package ?
[01:48] <markc> as well
[01:48] <nopcode> hey man
[01:49] <nopcode> i cant do _anything_ without network card
[01:49] <nopcode> i need that for getting packages
[01:49] <digitalpardoe> Perhaps the 64bit kernel doesn't have support for your network cards then.
[01:49] <nopcode> it does
[01:49] <nopcode> the driver even loads
[01:49] <nopcode> it just says "link down" and doesnt work
[01:49] <markc> what driver is it ?
[01:50] <nopcode> r8169
[01:51] <markc> I just "upgraded" to gutsy and FWIW there is no r8169 that comes with 2.6.22-1-rt
[01:51] <nopcode> r8111?
[01:52] <nopcode> hm
[01:52] <nopcode> well atleast some driver loaded ;)
[01:52] <nopcode> ah wait
[01:52] <nopcode> 8168 maybe?
[01:52] <digitalpardoe> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/86798
[01:52] <ubotu> Launchpad bug 86798 in linux-source-2.6.20 "r8169 driver does not detect link" [Medium,Confirmed] 
[01:52] <markc> r8619 not r8169
[01:53] <markc> sorry, I typed that wrong, should have pasted
[01:53] <nopcode> windows says r8168 / r8111
[01:54] <nopcode> brb
[01:54] <digitalpardoe> It might be worth trying the workthrough on the bug page, just to see.
[01:57] <nopcode> ok lets see
[02:03] <nopcode> re
[02:03] <nopcode> no didnt work
[02:04] <nopcode> i booted with the cable unplugged and inserted it after boot
[02:04] <nopcode> didnt work
[02:04] <nopcode> then i tried cycling the module, no luck
[02:04] <digitalpardoe> Not sure what the issue could be then. Have you tried booting from the 32bit live CD to see if it is an issue with the 64bit driver.
[02:33] <IdleOne> !gutsy
[02:33] <ubotu> Gutsy Gibbon is the code name for the next release of Ubuntu (7.10). See https://lists.ubuntu.com/archives/ubuntu-devel-announce/2007-April/000276.html and https://wiki.ubuntu.com/GutsyReleaseSchedule Support in #ubuntu+1
[03:01] <gortiz> !list
[03:01] <ubotu> I am ubotu, all-knowing infobot. You can browse my brain at http://bots.ubuntulinux.nl - Usage info: http://wiki.ubuntu.com/UbuntuBots
[04:00] <Dink> Quick question .... libk3b2 is being held back on initial dist-upgrade ... known issue or should I just force the package install later ?
[07:01] <Answer> anybody here that can help with wep key?
[07:02] <cliebow_> Answer, perhaps..
[07:03] <Answer> I have a wired connection to the device, I put in the ssid and the wep key and it does not work.  with key:off I can associate to an AP.  I have verified the ssid and key are correct.  I can see the AP with iwlist scan
[07:05] <Answer> it seems very similar to http://madwifi.org/changeset/2081  and https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/30596
[07:05] <ubotu> Launchpad bug 30596 in netcfg "WEP key for wireless takes only uppercase" [Medium,Unconfirmed] 
[07:13] <Answer> from everything I can see it is online, but it is not   http://paste.ubuntu-nl.org/19649/
[07:15] <cliebow_> not sure i have an answer..wireless has been really wierd in kernels past 2.6.17.7 (my opinion)
[07:16] <cliebow_> Answer, you might try something called wifi-radar..i've had good luck wit that
[07:17] <Answer> I do not understand.  I have 11 examples of WEP that work and one that I cannot make work
[07:18] <Answer> I've got wpa/wpa2/leap/eap-fast/peap/ieee8021x whatever - and i'm stuck on a stupid wep key
[07:19] <Answer> How can I track down the incompatibility here
[07:19] <Answer> I have the same brand model firmware of the access point with an identical config in a test environment and it works
[07:20] <Answer> so it must be something behind the ap with the controller or radius server
[07:21] <PocketIRC> Is it true that it propably will be only like..2 of the ideas that will make it into gutsy?
[07:21] <cliebow_> ?
[07:23] <Toma-> what ideas
[07:24] <PocketIRC> all the ideas in the forums
[07:24] <gord> forums are not the place to suggest ideas to make it into ubuntu
[07:28] <PocketIRC> gord: http://ubuntuforums.org/forumdisplay.php?f=253
[09:17] <raf256> hello
[09:45] <crimsun> of course not.
[09:46] <crimsun> all 131 others of us are dead.
[10:38] <brainsik> ah!
[10:38] <raf256> crimsun: I was going to ask some questions, because #ubuntu have higher newb-to-signal ratio then debian have grumpy-to-signal, but seeing how its quiet here I am shy now