/srv/irclogs.ubuntu.com/2009/04/17/#ubuntu-kernel.txt

=== SEJeff is now known as SEJeff_away
trichobezoarWhat do I have to do to get the improperly mentioned fix in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/275120/comments/5 looked at and hopefully put into the ubuntu kernel?00:32
ubot3Malone bug 275120 in linux "Atheros WLAN AR242x LED doesn't work" [Undecided,Fix released] 00:32
pgranertrichobezoar: That fix will prob never make Intrepid, it doesn't meet the SRU requirements00:49
mjg59Hm. Is bug #357760 restricted access?00:50
ubot3mjg59: Bug 357760 on http://launchpad.net/bugs/357760 is private00:50
mjg59Right00:50
trichobezoarIt's accepted into the main kernel iirc00:51
pgranermjg59: yep, it is for custom engineering work00:51
pgranertrichobezoar: IIRC is in Jaunty but won't make Intrepid00:51
trichobezoarOh.  I'm using jaunty but as of last update it's not working.  I guess there's nothing that needs to be done - just wait?00:52
pgranertrichobezoar: it didn't make the release kernel but should be in the first update. We have lots of stuff queued up00:53
pgranertrichobezoar: on a 2nd look it is in the current kernel if its not working for you, you'll need to open a new bug. There are various models that didn't work with that patch.00:56
trichobezoarYou're talking about 2.6.28-11-generic #41?00:57
=== k-s is now known as k-s[AWAY]
trichobezoarIf that's the right version, I assumed that it wasnt included because I do not have any /sys/class/rfkil/rfkillX/state, and I have a NC10 with the 168c:001c (rev 01) ar242x card01:07
trichobezoarCould be a config issue.  Says CONFIG_ATH5k_RFKILL has to be enabled01:08
=== _Purple_ is now known as _Purple_away
trichobezoarI want to know if I need to make a bug for this to be included or not.  03:03
jbuncherapw:  Sorry it took a while, but last week or so I finally got around to testing the ubuntu-modules package you posted in Bug #327431.  Let me know if you need me to test anything else.03:14
ubot3Malone bug 327431 in linux "iwl3945 cannot connect to hidden ssid WPA enterprise with Hardy 2.6.24-23 - Regression" [High,Incomplete] https://launchpad.net/bugs/32743103:14
=== k-s[AWAY] is now known as k-s
=== k-s is now known as k-s[AWAY]
randompieAnyone who can help me with: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/358255?06:32
ubot3Malone bug 358255 in linux "[jaunty] Root on nvidia raid 1 mirror does not boot" [High,Triaged] 06:32
randompiePointers to where I could download the Ubuntu Jaunty specific kernel source and build it?06:32
TheMusorandompie: Do you have the dmraid package installed?06:38
randompieyes - dmraid 1.0.0rc15-ubuntu1. And, let me clarify - I am typing this on the same machine running "2.6.28-11-generic #41-Ubuntu". The only thing is that while booting I used the 2.6.27-13 initrd06:41
TheMusoRight.06:41
TheMusorandompie: I have added to the bug.06:44
randompieTheMuso: sudo dmraid -s:06:51
randompie/dev/sdb: "sil" and "nvidia" formats discovered (using nvidia)!06:51
randompie/dev/sda: "sil" and "nvidia" formats discovered (using nvidia)!06:51
randompie*** Active Set06:51
randompiename   : nvidia_gdcfaafd06:51
randompiesize   : 31258176006:51
randompiestride : 12806:51
randompietype   : mirror06:51
randompiestatus : ok06:51
randompiesubsets: 006:51
randompiedevs   : 206:51
TheMusorandompie: please put that in the bug06:51
randompiespares : 006:51
randompieTheMuso: will you be online for the next 15 minutes? If so, I can reboot and tell what the output of "dmraid -ddd -ay" is. Bug is updated06:52
TheMusorandompie: yes I will be online.06:52
randompieok. will catch you later. thanks.06:52
TheMusorandompie: np.06:53
randompieTheMuso: I am back. Have updated: bug 35825507:22
ubot3Malone bug 358255 in dmraid "[jaunty] Root on nvidia raid 1 mirror does not boot" [High,Incomplete] https://launchpad.net/bugs/35825507:22
TheMusorandompie: thanks07:22
randompieTheMuso: it seems the core is "device-mapper:table: 252:7:mirror: Device lookup failure" so I guess your reasoning about dmraid is bang on target :) 07:23
TheMusorandompie: thanks for that.07:24
randompieare dmraid userland different in the two cases: 2.6.27-13 and 2.6.28-11? Ifo so, how can I update the initrd for 2.6.28-11 to use the dmraid tools of working initramfs and test it out - if it works - dmraid is the bad boy ...07:25
TheMusorandompie: the version of dmraid in the 2.6.27 initrd is older than the one in 2.6.28-11-generic and the only way you can fix them both up is if you downgrade the dmraid packages to the ones in intrepid.07:27
TheMusorandompie: once you do that, you will have to pin the dmraid packages to stay at those versions, however I don't know how to do that.07:28
randompieTheMuso:  Based on what you said about dmraid on Intrepid and Jaunty being different - my system is using 2 different versions of dmraid - at boottime the one in Intrepid which allows it to mount the RAID array and post boot-up the one in Jaunty which allows it to continue working. Now that I think about it, there is an issue with Jaunty's dmraid - I created an updated initramfs for 2.6.27-13 which also failed. So, I am using the older (intrepid)07:33
TheMusorandompie: right07:33
randompieso, is there a way to change just parts of the initramfs?07:34
TheMusorandompie: I think the problem could be that your system has more than one lot of dmraid metadata on the hard disks. What I think you would need to try is to firstly back up data, erase dmraid metadata, re-create in BIOS, and re-install from a fresh jaunty CD.07:34
TheMusothe multiple lots of dmraid metadata is confusing dmraid I think07:34
randompieTheMuso: why is it confusing the Jaunty version07:35
TheMusorandompie: I don't know yet07:35
TheMusorandompie: can you run this command for me? "sudo dmraid -R"07:36
randompieTheMuso: The Intrepid one works fine. Also, its picking up the correct set: "/dev/sda:"sil" and "nvidia" formats discovered (using nvidia)". The seciond version of metadata is because I had used a SIL controller earlier - I didn't even remeber it till I saw today's messages07:36
randompiewhat will "sudo dmraid -R" do?07:36
TheMusorandompie: right07:36
randompiesudo dmraid -R will rebuild the RAID array - how destructive is that?07:37
TheMusorandompie: sorry, sudo dmraid -r07:38
randompiewe had better be careful about case here - guess we should avoid such options :)07:39
TheMusorandompie: how about we go to private chat, so we don't clutter a channel thats not really for this sort of thing?07:39
randompieok07:40
=== _Purple_away is now known as _Purple_
=== emgent_ is now known as emgent
=== k-s[AWAY] is now known as k-s
=== k-s is now known as k-s[AWAY]
=== k-s[AWAY] is now known as k-s
=== lamont` is now known as lamont
=== k-s is now known as k-s[AWAY]
=== JayFo is now known as JFo
=== k-s[AWAY] is now known as k-s
macliI am compiling kernel on hardy, followed https://wiki.ubuntu.com/KernelTeam/KernelMaintenance, but still get /bin/bash: makedumpfile: command not found17:22
=== k-s is now known as k-s[AWAY]
maclidebuild -b: dpkg-checkbuilddeps: Unmet build dependencies: makedumpfile xmlto docbook-utils gs transfig sharutils17:23
smb_tpmacli, makedumpfile? is this a intrepid or jaunty kernel you try to compile?17:30
smb_tpCause makedumpfile does not exist for Hardy. You would need a compile chroot for that. See https://wiki.ubuntu.com/KernelTeam/KernelMaintenanceStarter17:33
maclismb_tp: thanks for the info17:49
=== SEJeff_away is now known as SEJeff
eagles0513875hey guys im having issues compiling the kernel i have the image source and it doesnt seem to be compiling right 17:52
eagles0513875i did it using apt-get source but im still haveing issues trying to install it17:52
=== mdz_ is now known as mdz
=== k-s[AWAY] is now known as k-s
=== mdz is now known as mdz-crashy
vadi21I need to package an updated madwifi snapshot for intrepid - where should I be looking to create a package? It doesn't seem that the madwifi drivers themselves haven't been packages for ubuntu previously22:02
=== asac_ is now known as asac

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!