User1: hey all
User1: im thinking of grabbing 2.6.25 kernel for built in 8165 wlan support that i hear  rumors of
User1: is there an official 2.6.25 (k)ubuntu kernel package?
User2: no.  Do you mean 2.6.27?
User1: i didnt mean that
User1: User2 what if i mean that now
User1: ?
User2: (the only 2.6.25ish one is for -ports)
User1: User2 i didn't explain myself well.  i dont care what version the knerel is, so long as it has a module for the 8165 wlan chipset
User1: but i found some ubuntu docs
User3: User4 I had a git tree from earlier in Intrepid, and just did a 'git pull'
User3: this gave me a bunch of conflicts, though I never modified by working tree. why is this?
User4: User3 I suspect it's because it's been rebased.
User4: I see this occur when ever the latest rc patches are pulled in - if there are too many of these merge conflicts I just get the entire repo again from clean - which is probably not an efficient way of working buy my network connection is fast
User4: s/buy/but
User4: I am sure amit has the necessary runes to resolve this efficiently
User5: User3 during development, git pull will almost never work
User5: User3 because we rebase, as cking mentioned
User3: User5 how do you keep your tree up to date?
User5: git fetch; git rebase origin
User3: (I won't ask why we rebase...)
User5: but wait
User5: since your tree is probably in a mess right now...
User5: User3 do you have any local changes you care about? or do you just need the latest kernel tree?
User5: User3 'git fetch; git reset --hard origin' will restore you to a pristine tree if you don't have (or care about) local changes.
User3: User5 thanks
User6: Hi I'm looking at bug 280451 raised by doko - is there any historic reason why the ports kernels builddep on gcc-4.1 specifically?
User6: Hi I'm looking at bug 280451 raised by d o k o - is there any historic reason why the ports kernels builddep on gcc-4.1 specifically?
User6: I just have this recollection that I saw a check in <kernel src>/Makefile ages ago that enforced use of gcc 4.1 for a certain arch but I can't see it
User6: there now
User7: User6 some of the arches used to have compiler dependencies. dunno if they are still true.
User7: compiler version dependencies, that is.
User6: User7 yep
User7: if they no longer exist in Hardy, then they are probably not appropriate for the ports kernels.
User6: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/280451
User7: User6 propose a patch and get smb_tp to test build
User6: User7 yes will do
User8: munckfish, best mail to the kernel team list
User8: munckfish, if you are done and have something to pull
User6: User8 yep usual procedure.
User9: is there some news on the e1000 for module regarding the eeprom-corruption?
User7: User9 the EEPROM corruption is related to ICH{8,9,10} e1000e parts, and yes, it appears to have been resolved by marking mapped memory to be read-only.
User9: User7 anyway I can do that on my laptop right now? I am at the GNOME/GUI-hackfest without any network-access on my own laptop (just using a colleagues machine for the moment)
User7: User9 you can do what on your laptop? update? 2.6.27-5 and later should be fine.
User9: User7 oh... hm... I already updated to 2.6.27-6 (via usb-stick) and that still does not give me back a working eth0
User9: User7 i am on a core 2 duo (using amd64 arch)
User7: User9 what NIC? lspci -vvnn
User9: User7 using a Ubuntu 7.10 live cd ethernet works so the hardware is ok
User9: 00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM Gigabit Network Connection [8086:1049]
User9: Subsystem> Lenovo Device [17aa:20de]
User7: User9 hang on a sec...
User7: User9 ok, that is an ICH8 device. do you see any eth devices with 'ifconfig -a'
User9: User7 I get lo and pan0
User7: User9 look in dmesg, e.g., dmesg | grep -i e1000e
User9: oh one sec
User7: User9 also, make sure its not still black listed in /etc/modprobe.d
User9: User7 nothing shown from dmesg
User7: User9 check for black listing?
User9: User7 there is blacklist-e1000e in /etc/modprobe.d still
User9: just delete that? and try to restart networking?
User7: User9 ok, then you're not completely up to date. 'sudo rm /etc/modprobe.d/ blacklist-e1000e; sudo update-initramfs -u'
User9: probably due to me just updating the package manually and not via apt-get or synaptic (since I have not network) so some scripts were skipped
User9: User7 manually loading e1000e now should work I assume
User7: User9 well, my first attempt at removing blacklist-e1000e in module-init-tools wasn't correct. Steve Langasek had to come along behind and clean up my mess.
User7: User9 yep - you should be able to just modprobe e1000e (or reboot)
User9: hm.. looks good sofar... trying to plug in a cable an see NetworkManager hopefully do its magic
User9: User7 sweet works again
User9: User7 you don't also happen to know a bit about iwl3945
User9: :)
User7: User9 a bit, though I'm not sure I'll of much help.
User7: s/of/be of/
User9: User7 ok huge thanks at least ethernet is working again
User10: hum
User10: aufs is broken *again*
User5: User10 in what way?
User10: NFS branches
User10: i'd like to blame kees cook commit (118463fa8236a123fdf6f81fb0c0176f7fd1caa7), but i can't tell for sure yet
User10: i still wonder why i have to constantly explain funny changes to aufs to junjiro
User10: kees cook re-introduced aufs_do_setattr which hasn't existed in a long time in aufs. although it looks like it's just a wrapper, so i'm not sure if it's to blame
User10: User5 http://launchpadlibrarian.net/18342118/DSC00183.JPG - this is what you get if you try to boot a mythbuntu-diskless client
User10: i will set up a test system tomorrow and revert that commit. i'm glad someone noticed before the release :)
User5: User10 just talked to kees. If reverting that patch fixes the problem, could you possibly prepare a patch separating the vfs changes from the fsetattr changes?
User10: yes, i think i could do that. i'll get back to you
User11: do we have any way to support RT2700E wlan chipsets ?
User11: apparently they are in the eee1000
User12: ok
User12: following -> Intrepid crashes on my Intel D945GCLF + Atom 230 (its a Intel bundled mobo+processor)
User12: desktop / server (also tried alternative version)
User11: you should mention that you try to run 64bit kernels on it, i doubt anyone will actually associate 64bit with atom (since thats the exact thing you ran into in the other channels ;) )
User12: im currently installing the 32bit version of Intrepid beta server (32bit), the installation is nearly completed
User12: User11 i wasnt done typing yet :P
User11: heh
User12: So -> problem is, Intrepid (64) kernels do not work on the Atom 230 (probably not on the newer 330 either, i'll buy this as soon as possible)
User12: but i cannot test that yet
User12: funny detail, with acpi=off .. the kernel of the livecd's does work
User12: What can i do, how can i help with adding support / fixing what is broken?
User11: amitk, did you ever do any work with 64bit atoms yet ?
User5: User11 not yet... so what does 'crashed' mean here?
User12: kernel segfaults, no CPU time for xxSeconds
User12: errors
User5: User12 It will be hard to debug or look into without detailed info. dmesg, lspci -vvnn, /proc/version_signature attached to a bug report would help a lot.
User5: but booting with acpi=off seems to suggest acpi bug in bios or kernel
User12: User5 i will provide all those details as good as i can, its easy ...  as i can use the livecd for it...
User12: but i just installed 32bit server, and i do want to use my server as well .. (so i keep that on)
User5: User12 so it works just fine with 32-bit?
User12: i think it does yes
User12: (well quiet sure actually)
User13: Hi, on intrepid, why the current version of linux is not the 2.6.27 on powerpc ?
User6: User13 because powerpc is now community supported and therefore uses the linux-ports kernel source not the standard one
User6: it's stuck 2.6.25 cause no one was motivated enough or had enough time to upgrade it
User6: I'm hoping that'll change in intrepid+1
User6: cause I'm hoping to do something about it myself
User13: User6 Ok thanks for your answers
User6: User13 np
User13: When is intrepid+1 ?
User6: well pretty much 6.5 months from now I guess
User6: User13 is there a specific feature you're missing?
User13: User6 no, I understand now
User13: User6 thank you
User13: bye
User14: hi, did anybody test gspca with 2.6.27? in worst case it does not even boot with webcam connected...
User14: 2 ppl dont get the webcam working with it... with 2.6.26 old gspca it works
User1: hey all...  im reading the ubuntu custom kernel docs...  i dont want to use the git method on a production kernel, do i?  i basically want a kernel built the same way as the default kernel, + the 8159 wlan driver...
User14: just compile it externally,what the problem
User1: User14 isnt there a certain kernel package out there just for (k)ubuntu?
User14: you only need the headers + a driver that compiles against the kernel
User1: with whatever relevant patches that we use
User1: User14 the driver is in the kernel id like to use
User1: so i just grab any linux-headers and kernel, and i dont worry about patches or anything like that?
User14: which config option?
User1: User14 its the wlan module for 8159 chipsets
User14: config option?
User14: there is no option with 8159 in the name..
User1: User14 i dont know, i head someone say it was in there so i was gonna look through menuconfig
User14: i think you are dreaming
User1: check 8150
User1: and pinch me
User14: CONFIG_USB_RTL8150=m
User14: is already set
User1: does it add support for 8159 in the newest kernel or something?
User14: /sbin/modinfo rtl8150
User14: shows it, what i find problematic is that rt2500usb and rt73usb share the same ids
User1: that doesnt look like it supports the 8159 chipset anywya
User14: lsusb
User14: then you can check the id
User1: its not a usb nic
User14: then use lspci -nn
User14: and show the line
User1: User14 im beginning to think i was misinformed..  sure, one sec
User14: 8150 IS usb
User14: also wlan is very simple to use with ndiswrapper
User1: im a knuckle head, its 8185
User1: and i have serious problems with ndiswrapper, which im certain constitute a bug
User1: http://ubuntuforums.org/showthread.php?p=5931608
User1: which is why im here
User14: User1 rtl8180 is already there, if you want to use ndiswrapper you have to blacklist it
User1: i dont have ndiswrapper, but i didnt have wlan0, so i assumed i needed it
User14: User1 grep 10ec /lib/modules/$(uname -r)/modules.pcimap |grep 8185
User1: sorry, i meant to say 'i dont want to use ndiswrapper, im only using it because i didnt have an interface for my wlan, so google searching seemed to imply i needed it_
User14: ndiswrapper is usually very good
User14: but in that case you would have to blacklist rtl8180
User1: User14 nothing returns from that grep
User14: then your kernel is too old
User1: i have 8139 and 8169, which are obviously wired drivers
User14: i use 2.6.27-6
User1: User14 and you have it  right?
User14: of course
User1: great, sorry for the confusion, my fault
User1: so i can just grab linux kernel sources from anywhere right?  there isnt any 2.6.27 *buntu specific-patched kernel that you would recommend i use
User14: in 8.10?
User14: it is
User1: these need to go into production, asap, or i would just use intrepid personally
User1: i need a kernel for use with 8.04.1
User15: User14 thanks, those .debs worked great
User14: fine
User15: lol
ubuntu-kernel
Ubuntu IRC