=== ionstorm [n=ion@71-35-73-85.phnx.qwest.net] has joined #ubuntu-kernel === verwilst [n=verwilst@d51A4A585.access.telenet.be] has joined #ubuntu-kernel [01:59] hellow === rikai_ [n=rikai@unaffiliated/rikai] has joined #ubuntu-kernel [02:00] zul: i seem to be having a problem that i can't start a domU because it cannot connect to the vif ( which is what the message says ) [02:00] zul: changing nothing in the configs, but simply rebooting with the official 2.6.18-xen kernel makes it work just fine === paran [n=paran@cust.fiber-lan.snet.lk.212.214.112.112.visit.se] has joined #ubuntu-kernel === rikai_ is now known as rikai === pwnguin [n=jld5445@camaro.cis.ksu.edu] has left #ubuntu-kernel [] === anibal [n=anibal@debian/developer/anibal] has joined #ubuntu-kernel === bullgard4 [n=detlef@p54BF1902.dip0.t-ipconnect.de] has joined #ubuntu-kernel === jml [n=jml@ppp121-44-214-123.lns1.hba1.internode.on.net] has joined #ubuntu-kernel === l_ [n=l_@mix.mmjgroup.com] has joined #ubuntu-kernel === tehk [n=tehk@c-71-59-90-172.hsd1.nj.comcast.net] has joined #ubuntu-kernel === rikai [n=rikai@unaffiliated/rikai] has joined #ubuntu-kernel === l_ [n=l_@mix.mmjgroup.com] has joined #ubuntu-kernel === clever [n=clever@fctnnbsc16w-156034219024.nb.aliant.net] has joined #ubuntu-kernel === l_ [n=l_@mix.mmjgroup.com] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === calc [n=ccheney@conr-adsl-209-169-124-200.consolidated.net] has joined #ubuntu-kernel === Lure [n=lure@89-212-18-142.dynamic.dsl.t-2.net] has joined #ubuntu-kernel === kousotu [n=kousotu@adsl-68-79-2-50.dsl.emhril.ameritech.net] has joined #ubuntu-kernel === Lure [n=lure@89-212-18-142.dynamic.dsl.t-2.net] has joined #ubuntu-kernel === IntuitiveNipple [n=TJ@alexandros.tjworld.net] has joined #ubuntu-kernel === kousotu [n=kousotu@adsl-68-79-2-50.dsl.emhril.ameritech.net] has joined #ubuntu-kernel === Lure_ [n=lure@89-212-18-142.dynamic.dsl.t-2.net] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel === bullgard4 [n=detlef@p54BF3ADA.dip0.t-ipconnect.de] has joined #ubuntu-kernel === Lure [n=lure@s104.ljudmila.org] has joined #ubuntu-kernel === justinas_ [n=justinas@78-60-112-31.ip.zebra.lt] has joined #ubuntu-kernel === cobman [n=justinas@78-60-112-31.ip.zebra.lt] has joined #ubuntu-kernel === tseliot [n=tseliot@82.59.228.211] has joined #ubuntu-kernel [11:32] BenC: I need to talk to you about bug https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/98641 [11:33] my patch wasn't applied in its entirety therefore the wfb module is still missing [11:35] please contact me, even privately if you wish [11:35] thanks [11:49] Hi. Which system is used for suspend/hibernate in Ubuntu? === cobman [n=justinas@78-60-112-31.ip.zebra.lt] has joined #ubuntu-kernel [12:34] BenC: I wrote a full explanation of the reason for the changes in my patch: [12:34] https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/98641/comments/101 [12:52] and here's the latest patch: [12:52] https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/98641/comments/102 === jeromeg [n=jerome@gra94-2-82-66-142-60.fbx.proxad.net] has joined #ubuntu-kernel [01:42] hello [01:42] just a single question [01:43] should I assign hotkeys not working bugs to the kernel ? === zul_ [n=chuck@mail.edgewater.ca] has joined #ubuntu-kernel === zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-kernel === bullgard4 [n=detlef@p54BF3DB5.dip0.t-ipconnect.de] has joined #ubuntu-kernel === kousotu [n=kousotu@adsl-68-79-2-50.dsl.emhril.ameritech.net] has joined #ubuntu-kernel === stgraber [n=stgraber@dakara.stgraber.org] has joined #ubuntu-kernel === l_ [n=l_@mix.mmjgroup.com] has joined #ubuntu-kernel [05:09] BenC ? === asac_ [n=asac@d112179.adsl.hansenet.de] has joined #ubuntu-kernel === BenC [n=bcollins@debian/developer/bcollins] has joined #ubuntu-kernel [05:32] tseliot: it's fixed in gutsy, I plan an upload for feisty with 100 series driver [05:32] BenC: no it has a problem [05:32] I had a look at the code [05:33] tseliot: I think you're wrong [05:33] at least as far as the type of if statement to use [05:33] I have described what and above all why my patches did all that in the bugreport today [05:34] libwfb should be included if it exists, regardless of the version [05:34] ok, we agree on this [05:34] which is why I used the -e test and not a "new version" test [05:34] I see your point [05:35] and we could keep it your way and add other if-statements [05:35] whenever a new module is added to the [05:35] latest driver [05:35] right [05:35] but [05:36] there is another problem [05:36] the links for nvidia-glx-new [05:36] should be kept separate from the links [05:36] which links? [05:36] in nvidia-glx [05:36] not sure what you mean [05:36] the current package works, right? [05:36] it is working for me at least [05:37] there should be a link to the wfb module [05:37] otherwise the driver will crash with geforce 8xxx [05:37] there is a link [05:37] I am using 8400M right now [05:38] do you refer to version 2.6.22.3-11.2 ? [05:38] lrwxrwxrwx 1 root root 26 Aug 27 13:04 /usr/lib/xorg/modules/libwfb.so -> libnvidia-wfb.so.100.14.11 [05:39] wait, maybe that's a symlink I added manually before the fix in the package [05:39] Ok, I can fix that now and do another upload [05:39] where would you like to add the link? [05:40] in the debian/rules? [05:40] yes, I'm adding it to the if statement [05:40] give me 5 minutes, I'll have it uploaded [05:41] why don't you keep a separate nvidia-glx-new.links.in and a nvidia-glx-new.links.amd64.in ? [05:41] so that you can add the links there in the future? [05:42] I mean, instead of touching the debian/rules [05:44] tseliot: because again, that makes it ver specific, when it needs to be file specific [05:44] this saves us work down the road [05:44] don't want the same bug report popping up when we get an nvidia-glx-really-new :) [05:45] ahhh. Ok, now I do see your point [05:46] according to the same logic the script will create the link if the module exists. It makes sense to me now. [05:46] ln -s libnvidia-wfb.so.$$this_ver \ $(CURDIR)/debian/nvidia-glx$${nv_flav}/usr/lib/xorg/modules/libwfb.so;\ [05:46] added that, doing a build, and will upload once I verify it works [05:49] in the nvidia-glx-new.links I put this link: [05:49] usr/lib/xorg/modules/libnvidia-wfb.so.@@VERSION@@ usr/lib/xorg/modules/libwfb.so [05:50] which I guess is the same ;) [05:52] lrwxrwxrwx 1 root root 26 Sep 8 11:52 libwfb.so -> libnvidia-wfb.so.100.14.11 [05:52] works, so uploading [05:53] perfect [05:54] done [05:57] BenC: please, remember to put the link in Feisty's restricted modules as well [05:58] will do [05:58] thanks [06:08] How can I run the SysRq function on a x86 laptop computer using kernel 2.6.20-16generic? Pressing the SysRq key doesn't do it. [06:09] bullgard4: are you in X? [06:09] yes === Lure [n=lure@s121.ljudmila.org] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === paran [n=paran@cust.fiber-lan.snet.lk.212.214.112.112.visit.se] has joined #ubuntu-kernel === tseliot [n=tseliot@82.59.228.211] has left #ubuntu-kernel [] === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === allee [n=ach@dialin-212-144-130-033.pools.arcor-ip.net] has joined #ubuntu-kernel === tehk [n=tehk@c-69-249-157-157.hsd1.nj.comcast.net] has joined #ubuntu-kernel === johanbr [n=j@blk-224-159-249.eastlink.ca] has joined #ubuntu-kernel === johanbr_ [n=j@blk-224-159-249.eastlink.ca] has joined #ubuntu-kernel === alleeHol [n=ach@dialin-212-144-130-033.pools.arcor-ip.net] has joined #ubuntu-kernel === ant1 [n=ant1@41.233.87.179] has joined #ubuntu-kernel [09:45] Hello, I got a problem in gutsy, when I set vga=0x314 I cannot access the virtual console, when I switch from X to virtual console I just get messy colors, if I remove splash option,I don't see boot messages, also I tried with acpi=off, my laptop is of 15.4" screen. Is this bug kernel related ? If yes, is it known to you guys ? [09:46] if it is not kernel related, do you know in what component should I report this bug ? [09:54] How can I run the SysRq function on a x86 laptop computer using kernel 2.6.20-16generic? Pressing the SysRq key doesn't do it. Either in X or in a console. [09:54] ctrl+alt+sysrq ? === ionstorm [n=ion@71-36-164-32.phnx.qwest.net] has joined #ubuntu-kernel === tehk [n=tehk@c-69-249-157-157.hsd1.nj.comcast.net] has joined #ubuntu-kernel === alleeHol [n=ach@dialin-212-144-130-033.pools.arcor-ip.net] has joined #ubuntu-kernel === JanC [n=janc@lugwv/member/JanC] has joined #ubuntu-kernel === bullgard4 [n=detlef@p54BF3DB5.dip0.t-ipconnect.de] has joined #ubuntu-kernel === anibal [n=anibal@debian/developer/anibal] has joined #ubuntu-kernel === thom [n=thom@amnesiac.heapspace.net] has joined #ubuntu-kernel === n2diy_ [n=darryl@wlk-barre-208-103-148-76.dynamic-dialup.coretel.net] has joined #ubuntu-kernel