[00:44] amitk_: unfortunately, no. I've often started by mv'ing /etc/udev/rules.d/85-alsa.rules out of the way so that on a fresh boot, asound.state isn't `alsactl restore`'d at all [00:46] crimsun: would it be that hard to create a minimal asound.state with fore example Master, PCM, Line In? [00:47] crimsun: the problem we are trying to solve is not having to 1. delete asound.state, 2. kill mixer applet, 3. rmmod driver 4. modprobe driver just to get a clean slate [00:48] amitk_: the cleanest slate that can be gotten is simply not to `alsactl restore` on boot [00:49] amitk_: even with a "minimal" asound.state, there's no guarantee said mixer elements are even enumerated :/ [00:49] crimsun: we want to _try_ one step better. Instead of a clean slate, give 'em a minimal default that is known to work on majority of that HW [00:50] crimsun: I understand the codec wiring will dictate a lot of details, but surely everyone will have Master, PCM and Line In? [00:51] amitk_: nope, some emu10k-based ones don't [00:51] a lot of usb ones don't [00:52] for HDA, Conexant, Realtek, and Sigmatel should [00:52] will 3-4 such minimal configs cover 90% of the HW out there? [00:52] hmm, yes [00:54] I'm guessing that 90% of the HW will be PCI-based, with the vast majority being HDA [00:55] crimsun: so if we can have them pre-installed as say, asound.state.intel, asound.state.dell or whatever, we could ask the user to check if sound works with 'alsactl -F -f restore' [00:56] amitk_: yes, that is feasible [00:56] crimsun: it could even be exposed in the mixer applet UI [00:59] crimsun: I can try to come up with something for HDA, Realtek, Sigmatel stuff. Could you help with the USB, emu10k ones? [01:00] amitk_: I'm afraid I can't promise, but I certainly will try. [01:00] crimsun: ok... thanks Daniel. I will keep you posted on this. [01:00] amitk_: http://pastebin.ca/search.php?q=alsa-info&s=Search should help [01:01] amitk_: for some time, we've been accumulating pastebinned codec dumps [01:03] crimsun: great... this might prove handy [05:11] ....imbrandon or zul around? [05:12] ..........was looking for imbrandon's fatx module [05:13] id rather try not and ...... well you know, recreate the wheel [05:36] im just reading old irc logs [05:36] tons of info :P [05:39] themuse - yeah I have that [05:39] but it was my understanding, he got the thing built [05:39] and had it up on his website somewhere :) [05:40] Hasufin: Ah ok. [05:40] or they had a patch or something [05:40] Ive been reading irc logs [05:41] thanks for replying and looking that up btw -- I appreciate it [05:41] Hasufin: Are you willing to build it for your kernel yourself? [05:42] Yeah, I'll have to get into the wiki's and such [05:42] I haven't built kernel modules since........ uh [05:42] redhat 6.x/suse 7.x days [05:42] or built a kernel since then [05:44] hmm [05:44] i think im going to have to do the exact same thing he did [05:44] he has a test fatx image posted [05:44] but doens't have the module source or anything so [05:44] this will be a learning exercise :) [05:50] i just realized something [05:50] wrong srever/cahnnel [06:50] Zul -- (or imbrandon) if you have that patch........ :) i'd appreciate if you pointed it to me. === fabbione is now known as thegodfather === asac_ is now known as asac === mekius_ is now known as mekius [08:28] moin [10:37] Hasufin: what kernel version are you looking for the patch for ? [10:37] im on gutsy [10:37] 2.6.22-14 [10:38] generic [10:38] .............if you only knew what ive been thru tonight to get a damn dos boot disk modified :) [10:38] well... a dos boot iso [10:38] i didn't find a program to pull out a binary boot image off an iso.... [10:38] holy crap has it been heck :P [10:39] anyways another story [10:41] ok i have two diffrent patches, one for the kernel to run ON the xbox, and one to just run on gutsy x86 and read/write fatx filestsems [10:41] i'm guessing you need the latter ? [10:41] yes :) [10:42] hard drive is getting read errors [10:42] so I need to run ddrescue on it to get all my xbox stuff off it [10:42] ahh, is it unlocked or locked ? [10:42] this wont unlock the drive [10:42] it has to be unlocked by the xbox or xbhdm [10:43] why im doing the whole dos thing [10:43] trying varios spare drives i have to see if they are lockable [10:43] I have the password, etc [10:43] so I can unlock it [10:44] the drive just has a lot of bad sectors on it...... [10:44] ahh ok, do you have xbhdm ? ( btw mostly any modern ide drive can be locked ) [10:44] which is causing linux not to boot... or to install [10:44] ....no i don't have that... [10:44] what is it? [10:44] i haven't seen it in any of the readme's [10:45] xbox hard drive maker , it is a custom linux boot cd, that has the fatx modules, xbox harddrive clone utils etc [10:45] :P [10:45] wow [10:45] nice [10:45] one sec lemme find it [10:45] I will google it [10:45] is more what you need [10:45] well yes [10:45] that would help me not have to do the insmod.... mount rmmod thing on my desktop [10:47] ok here is the link, its 100% legal etc, but you can only gget it via torrent [10:47] http://www.torrentz.com/ec05e2c927a69699896a929d9c73eeacce07838d [10:48] read the README with it, but basicly there is a shellscripot in that zip that will make a custom iso just for your xbox with the eprom backup from your xbox or hdd passord [10:49] boot off that iso with your xbox hdd as the only drive attached ( and past this feel free to join me in #buntubox , we're getting a little OT for -kernel ) [11:06] zul, did you ever commit the fatx stuff to l-u-m ? === \sh_away is now known as \sh === \sh is now known as \sh_away === \sh_away is now known as \sh [12:30] hi there, anyone alive? need to ask about format of kallsyms === LifeHacker is now known as tuxmaniac === \sh is now known as \sh_away === Traxer is now known as Traxer|on === Traxer|on is now known as Traxer [16:43] Is somebody not affected by bug 177713? How can I debug this? [16:43] Launchpad bug 177713 in linux "2.6.24-2: Regression with idle cpu cycle handling" [Medium,Confirmed] https://launchpad.net/bugs/177713 [17:13] Can anyone help me figure out why ACPI support causes my IDE drives not to be recognized? [17:16] mtretin: what do you mean with "not to be recognized"? [17:18] w/o ACPI support, using the AHCI driver for my hdd and PIIX driver for my cdrom, when the kernel says it probes ide0 and ide1 it picks up my drive as /dev/hdb - when I turn *on* ACPI support int he kernel this doesn't happen [17:18] blueyed: but it it doesn't pick the drive up as /dev/srX either [17:20] mtretin: unfortunately I have no clue, but others might help you know better (with this info). Have you search for a bug about it on launchpad.net? [17:20] I've been google searching for about a week for something relevant, and there are a few fixes -- none of which have worked, I'll try laynchpad now [17:23] did you check for /dev/sdX mtretin [17:23] above you speak about srX [17:23] maks_: yup, there's nothing but /dev/sda :( === smb is now known as smb_away [17:32] mtretin: what's your config? [17:32] are you using stock kernels [17:33] maks_: I've treid stock, custom rebuilds using stock sources, and rebuilds using vanilla [17:33] 2.6.24-rc7 ? [17:34] 2.6.23.13 [17:36] 23 is a strange release i don't trust it much.. [17:37] I'm meaning to try .24 (that's latest unstable, right?) but time keeps in slipping into /dev/null [17:38] we have test builds on the debian side i guess ubuntu too [17:38] they should just install fine [17:40] maks_: I switched to Ubuntu hoping everything woudl work out of box, so, I'd love to install one - but what repository is it in? [17:42] trunk http://wiki.debian.org/DebianKernel [17:51] maks_: Thanks for the hint, I can use those images instead of building it from git myself to test if my regression is still there. [18:10] bleh. idle regression still in 2.6.24-rc7-686 from http://wiki.debian.org/DebianKernel [18:10] Is this enough to send it to the upstream bugtracker? (.config might be involved, so I'll include it of course) === \sh_away is now known as \sh === smb_away is now known as smb [18:34] uswsusp (0.6~cvs20070618-1ubuntu2) gutsy; urgency=low; mjg59: "* Don't build s2ram. It's not sensible on Ubuntu." I understand 'sensible' = reasonable. What is the reason? [18:36] Because we use pm-utils [18:36] And, in earlier versions, acpi-support [18:36] There's no reason to provide multiple packages that do exactly the same thing [18:36] If it doesn't work out of the box, that's a bug [18:36] Thank you very much for explaining. === \sh is now known as \sh_away