[00:39] <octocpp> how do i send acpi_osi=Linux as a boot param while booting from the cd, I tryed acpi_osi=Linux,acpi_osi="Linux",acpi_osi=linux, acpi_osi="linux", acpi_osi=!Linux and evern tryed acpi_osi=eatshit and i ge tthe same result, like a hundred acpi errors saying stuff is not found, I cant make it our bcause it doenst stop scrolling even after like 5 minutes
[00:40] <octocpp> I have the  insyde h2o bios on this laptop and I cant even boot without calling up acpi=off
[00:41] <octocpp> i cant seem to even try acpi_osi=Linux
[00:43] <johanbr> sounds like your bios doesn't handle acpi very well
[00:45] <octocpp> it is a new bios that changes the way we have to interact with the hardware somehow from what Ive read, I cant believe that windows is the only OS that has the lowdown On how to operate this laptop, it is a Tooshiba Sattelite l505d_es5025
[00:46] <octocpp> is that what MS is up to now? getting firmware writers to block linux from being able to even use the machine? or is the kernel just falling behind the time a bit? Or should I just return this piece of crap laptop that can only run windows?
[00:46] <johanbr> it was probably never tested with linux
[00:46] <johanbr> there are lots of crappy bioses out there
[00:47] <octocpp> the L303 has worked but i guess there are some acpi issues
[00:47] <octocpp> I cant even get it to boot without acpi=off, but then I only have one CPU and I am sure a ton of other  problems
[00:48] <octocpp> is there some common work around for this that I am unaware of?
[00:48] <octocpp> Or I just have to wait untill they start to work with that Bois in the kernel?
[00:49] <johanbr> there may be workarounds, depends on how badly broken it is
[00:49] <johanbr> you could try booting with "noapic nolapic"
[00:50] <octocpp> yea, Ill try them out reall quick
[00:53] <johanbr> well, gotta go... good luck
[11:58] <gnomefreak> is it just me or is 2.6.32-12 broken? i get an error when booting. "something over range" i dont recall first word so i used something
[12:36] <gnomefreak> i cant report the bug using ubuntu-bug it gives me "The problem cannot be reported: This is not a genuine Ubuntu package" I'm using the Ubuntu kernel
[13:56] <indus> test
[13:56] <Ayla> hello
[13:57] <indus> Ayla, please file a bug first , they will only look at that
[13:57] <indus> bye
[13:58] <Pici> We've stopped having random channel attacks since moving to the new ircd, probably should /mode -q $~a  here (that will let unidentified users speak)
[13:58] <Pici> ping me if there are any questions about that. 
[18:15] <MaximLevitsky> I need sources of kernel package of 2.6.33-rc6, so I could patch them with my driver, and expose in an PPA
[18:16] <MaximLevitsky> http://kernel.ubuntu.com/~kernel-ppa/mainline/ contains only binaries
[18:35] <jk-> MaximLevitsky: linux-source-2.6.33_2.6.33-020633rc6_all.deb
[18:35] <MaximLevitsky> jk-: not that
[18:35] <MaximLevitsky> I need .tar.gz, .dsc, files
[18:36] <MaximLevitsky> so I can build new package
[18:36] <MaximLevitsky> but I guess that make-kpg will do that
[18:36] <_ruben> why repackage a complete kernel for a driver? drivers can be installed seperately just fine .. ideally using a dkms package for instance
[18:36] <MaximLevitsky> _ruben: I did several changes in several places
[18:37] <MaximLevitsky> I sent patches upstream
[18:37] <_ruben> ah
[18:38] <MaximLevitsky> This is same reason I patch against 2.6.33
[18:38] <MaximLevitsky> I initially targeted 2.6.32,  but for merge I ported everything to 2.6.33
[18:39] <_ruben> guess one of the ubuntu kernel devs will have to help out here .. perhaps best to send an email to the -kernel mailinglist
[18:39] <MaximLevitsky> Maybe
[18:39] <MaximLevitsky> Only one question
[18:39] <MaximLevitsky> Does ubuntu customized kernel 2.6.33 exist?
[18:40] <MaximLevitsky> or it is vanilla git
[18:40] <jk-> MaximLevitsky: it's vanilla git
[18:40] <_ruben> those mainline builds are annlia
[18:40] <_ruben> err
[18:40] <_ruben> vanilla
[18:40] <MaximLevitsky> Thanks a lot
[18:40] <jk-> so you can probably just make-kpgk it
[18:41] <MaximLevitsky> jk-: that what I am doing now
[18:41] <jk-> cool.
[18:46] <ssam> is there a special way that i should mark Bug #508746 as having a patch upstream?
[18:47] <ssam> i have linked to the commit in a comment