[06:56] <Sarvatt> wow, hd 6770m is one unhappy camper at the moment, all kinds of crashy in stock natty and compiz doesn't work with edgers
[06:57] <Sarvatt> well this is a firepro m5950 in a precision m4600, same GPU though
[06:58] <RAOF> Heh.  If only I had such problems :)
[07:01] <Sarvatt> 240w power brick for it is bigger than a netbook :)
[07:04] <RAOF> Sorry, *what* ?  That's a 240W power brick for a *laptop* ?
[07:04] <RAOF> Or should I say “portable”? :)
[07:06] <Sarvatt> 10.4lbs with 2 little strips of foam in the box :)
[07:07] <RAOF> 4.7 kg?  That's pretty heavy.
[07:08] <Sarvatt> the laptops only 2.8 of that
[07:08] <Sarvatt> rest is power brick
[07:08] <tjaalton> ...
[07:08] <RAOF> Does the laptop not actually have a battery?
[07:08] <RAOF> :)
[07:10] <Sarvatt> it's got the 6 cell option, 2 hours :)
[07:10] <tjaalton> "option"..
[07:10] <Sarvatt> yeah vs the heavier 9 cell for an extra 20 minutes
[07:10] <tjaalton> ah
[07:11] <RAOF> How much power does it draw under full load?
[07:15] <Sarvatt> i'll let ya know tomorrow when it's working again and not 2 am, needs to sit without a battery for another hour or so to be able to power back on after what I did to it :)
[07:16] <RAOF> How have you been mistreating the poor box!
[07:16] <tjaalton> ran unity on it, obviously
[07:16] <tjaalton> or tried to
[07:25] <Sarvatt> the GPU is only 25W TDP
[07:25] <Sarvatt> think they just grabbed a brick from a m6600 and sent that
[07:28] <RAOF> Well, at least it can charge the battery under full load!
[07:37] <LLStarks> sarvatt, D:
[07:37] <LLStarks> i was about to get one
[07:37] <LLStarks> *the 6770m
[08:21] <tjaalton> bryceh: I'll merge xorg and drop the drivers that were discussed on the list
[08:21] <tjaalton> from -video-all
[08:22] <bryceh> tjaalton, great
[08:25] <tjaalton> probably need to drop the doc-building stuff from build-deps, unless they are all in main
[08:25] <tjaalton> which I doubt
[08:29] <tjaalton> hum, it's only asciidoc now, and it's in main
[08:35] <bryceh> tjaalton, btw I trimmed down the arm drivers a while back; if there's other architectures we care enough about, might want to do similarly for them
[08:39] <tjaalton> bryceh: looks like powerpc is supported, I'll check that one too
[08:40] <tjaalton> and i think -vesa is useless on arm?
[08:41] <RAOF> That matches my understanding.
[08:42] <RAOF> VESA only works where there's a video bios, and since arm boards don't have bioses…
[08:42] <tjaalton> right
[08:49] <bryceh> tjaalton, yeah I left it only because I couldn't pin down an absolute, "Yes it's definitely not needed on arm" from anyone, and since it's such a trivially tiny driver just left it
[08:49] <tjaalton> bryceh: indeed it is
[08:50] <LLStarks> bryceh. fallback in a nutshell: gnome-panel as manual fallback or automatic for gnome-shell. unity-2d as manual and automatic fallback for unity.
[08:51] <LLStarks> according to didrocks from ayatna/desktop
[08:51] <LLStarks> gnome-shell pulls in all requisite packages.
[08:52] <LLStarks> automatic applies to all 3d-less scenarios. failsafex is our judgment call.
[08:53] <LLStarks> https://lists.ubuntu.com/archives/ubuntu-desktop/2011-June/003079.html
[09:01] <RAOF> I've also replied to that; I think that whatever fallback session would normally kick in is the right thing to use.
[09:11] <bryceh> traditionally we've not bothered to fire up a WM at all.  Since we only need to run a single app we just run that as the root application
[09:11] <bryceh> however nothing says we can't revisit that design
[09:12] <bryceh> the one trade off is the more things we depend on the less failsafey we become
[09:12] <RAOF> Yeah.
[09:13] <tjaalton> aren't we mixing two things here? the one fallback is if the hw can't handle full 3d-unity/gnome-shell, the other is where the normal gdm/lightdm startup failed and so we use some defaults
[09:13] <RAOF> Hm.  We might be able to kill two birds with one stone.
[09:14] <RAOF> Since we'd want FailsafeX to *say* it's failsafe, we could pop up, say ‘Failsafe mode ENGAGE!’ and offer a minimal or full session.
[09:14] <tjaalton> so the other fallback is for the system, the other for the user session
[09:17] <bryceh> tjaalton, yeah two separate things conceptually
[09:18] <RAOF> My conception of FailsafeX is that we want to end up with it kicking in when the recovery boot is activated, right?
[09:23] <bryceh> in situations where the recovery boot is needed due to a graphics failure, that's correct
[09:24] <bryceh> gdm/lightdm failing to start X would be another situation (probably rare) where failsafex should be popped up
[09:25] <bryceh> there may be one or two other situations where we might want to tie it in
[09:25] <bryceh> where I'm a bit fuzzy is if in the recovery boot should xdiagnose or whatever pop itself up, or just be provided as a clickable icon or some such
[09:26] <tjaalton> "clickable icon" sounds like something that needs X :)
[09:28] <tjaalton> hmm forgot that it's not just failsafex
[10:05] <tjaalton> a flowchart from grub to unity, covering all the possible scenarios would be nice :)
[10:07] <bryceh> tjaalton, ...and as soon as you finish drawing it, someone would immediately introduce a change to render it obsolete ;-)
[10:07] <bryceh> actually, there is a good description of the sequence listed with one of the kernel troubleshooting docs
[10:08] <hyperair> Sarvatt: meh. X segfaults. =(
[10:08] <hyperair> Sarvatt: i guess it's to be expected from an ABI-incompatible X.
[10:10] <bryceh> tjaalton, https://wiki.ubuntu.com/X/Troubleshooting/BlankScreen
[10:11] <bryceh> hm, not much of a flow chart
[10:12] <tjaalton> bryceh: well, one covering the boot-up from X's perspective, that shouldn't change too often :)
[10:52] <scoundrel50a> Hi, I have a new Acer Aspire 5736Z laptop that I am having problems upgrading to 11.04 on. Have tried upgrading via the Update Manager, fresh install, alternative cd fresh isntall, and I get to reboot and as soon as the screen comes after clicking on the kernal option, the screen goes black, there is no backlight. There is a bug number #759104, has anybody any idea if this will get fixed? I cant upgrade otherwise. Funny thing though, I have
[10:52] <scoundrel50a>  an Acer Aspire One netbook, and it works ok on there. 
[11:08] <tjaalton> scoundrel50a: try installing 2.6.39-oneiric from here http://kernel.ubuntu.com/~kernel-ppa/mainline/
[11:19] <scoundrel50a> oh hello, just noticed this now. Thank you. Will see how far I get. Can that be installed over the top, or on another partition? 
[11:20] <scoundrel50a> One thing I forgot, I am using 64bit, is there a 64bit version?
[11:20] <tjaalton> http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.39-oneiric/
[11:20] <tjaalton> yes
[11:20] <tjaalton> grab the amd64.deb and install it
[11:22] <scoundrel50a> linux headers, or linux image?
[11:22] <tjaalton> image
[11:22] <scoundrel50a> ok, will give it a go, be back soon
[11:23] <scoundrel50a> thank you
[11:26] <scoundrel50a> do I just install as I would a normal .deb package, not done it this way before.
[11:26] <tjaalton> dpkg -i ...deb
[11:27] <scoundrel50a> ok, will give it a try
[11:29] <scoundrel50a> daft question I know, but should I close everything down before starting the installation, will be going offline if I do
[11:29] <scoundrel50a> will trying logging in again on a different pc
[11:30] <tjaalton> um no
[11:30] <tjaalton> you can install it from a running session.. then reboot
[11:30] <scoundrel50a> ok, well, I am about to install
[11:30] <tjaalton> though if you just have a black screen then you can't install it, right?
[11:31] <scoundrel50a> it gets to the end of the installation, I click on the kernal and the screen goes blac
[11:31] <scoundrel50a> too late now its going through it again
[11:31] <scoundrel50a> ok, installation finished, what do I do now?
[11:32] <scoundrel50a> reboot?
[11:32] <tjaalton> how did you install it?
[11:32] <scoundrel50a> using the command you gave, dpkg -i ....deb
[11:33] <scoundrel50a> I can see its added an extra kernal
[11:33] <tjaalton> you said it had a black screen, so I gave you bad advice
[11:33] <scoundrel50a> ah
[11:33] <scoundrel50a> well, as its installed, I will try to boot that up, see if anything has changed, one sec
[11:34] <scoundrel50a> brb
[11:34] <scoundrel50a> have another pc so will log in with that one
[11:36] <scoundrel50a_> ok,on different oc
[11:36] <scoundrel50a_> going to reboot other one now, 
[11:38] <scoundrel50a_> rebooting, same thing happened, backlight not working, can just see the log in screen, but can not log in as I cant see curser
[11:39] <scoundrel50a_> tried using ctrl+alt+ > not working either
[11:40] <tjaalton> scoundrel50a_: "same thing.." that's not the same you described earlier, getting a black screen and nothing else
[11:43] <scoundrel50a_> um, sorry, I thought I mentioned the backlight didnt work
[11:44] <tjaalton> so what login screen are you talking about?
[11:44] <tjaalton> and are you saying it hasn't changed with the new kernel
[11:45] <scoundrel50a_> the log in box, where it has the logo and choice to pick users, no it hasnt changed, still no backlight
[11:46] <tjaalton> and you installed the .39 kernel when you had booted using the one from maverick?
[11:46] <scoundrel50a_> if you check the bug I posted, it should tell you there, and it gives you the xorg and old xorg files
[11:47] <scoundrel50a_> no, havent installed fromMaverick since the day 11.04 came out, as I got this same problem
[11:47] <tjaalton> no they don't tell me how you installed the kernel
[11:47] <tjaalton> I'm just trying to make sure you actually are running it
[11:48] <tjaalton> on the bug you said that the way to boot natty was to use the previous kernel (=maverick)
[11:48] <scoundrel50a_> yes
[11:48] <scoundrel50a_> I could do it that way
[11:48] <scoundrel50a_> but it looked like windows 98 on a very old machine
[11:49] <tjaalton> then you could try the 3.0-rc1 kernel from the same url i gave you
[11:50] <scoundrel50a_> ok, need to reboot again
[11:50] <scoundrel50a_> how can I uninstall that version? as I dont want loads of kernals showing
[11:51] <tjaalton> dpkg --purge linux-image-2.6.39-020639-generic
[11:51] <scoundrel50a_> ok,
[11:52] <tjaalton> (and it's kernel)
[11:52] <scoundrel50a_> oh sorry using a netbook, 10 inch, and got big fingers
[11:56] <scoundrel50a_> purging now
[11:59] <scoundrel50a_> um, I dont have the url, it went when I rebooted and changed pc, can you give it to me again
[12:01] <tjaalton> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0-rc1-oneiric/
[12:01] <scoundrel50a_> ok, will try that one, thank you
[12:03] <scoundrel50a_> ok, about to install this version
[12:10] <scoundrel50a_> about to reboot
[12:12] <scoundrel50a_> exactly the same, once you chosse the kernel, it starts to boot, the backlight turns off, and that is it, 
[12:13] <scoundrel50a_> brb, 
[12:13] <scoundrel50a_> #
[12:13] <tjaalton> then it would be nice to get the dmesg output of the broken kernel
[12:13] <tjaalton> attached to the bug
[12:15] <scoundrel50a_> how do I do that?
[12:15] <tjaalton> install openssh-server on the system, and log in remotely with ssh
[12:16] <scoundrel50a_> have to start up, have to tell you, I cant even boot up the rescue bit, that has the same problem, no backlight
[12:17] <scoundrel50a_> ok, will see if i can do that
[12:20] <scoundrel50a_> ok, I'm on my netbook, on 11.04, my laptop do I need to boot up to the new kernel, the  try to connect from netbook?
[12:20] <tjaalton> do you have ssh-access to the laptop?
[12:21] <scoundrel50a_> well openssh-server is installed on both machines
[12:21] <scoundrel50a_> how do I connect?
[12:21] <tjaalton> so that the networking works without the user session running..
[12:21] <tjaalton> ssh uid@foo
[12:22] <scoundrel50a_> ok, not done this before, the uid is the id of the laptop yes? What is foo?
[12:22] <tjaalton> no, username@machinename
[12:23] <tjaalton> or ip instead of the name
[12:23] <scoundrel50a_> how do I find out the ip address? and see if both machines are viewable on the network?
[12:23] <tjaalton> i give up
[12:24] <tjaalton> sorry
[12:24] <scoundrel50a_> ok, I'm sorry too
[12:25] <tjaalton> upstream might be interested, but they need the dmesg output
[12:25] <tjaalton> though, you can probably parse it from /var/log/kern.log too
[12:26] <tjaalton> which you can get to with the maverick kernel
[12:26] <scoundrel50a_> but I cant get that till I can find out if I can get into other machine, thank you anyway,
[12:27] <tjaalton> no, you use the same method to get it as you used to install the test kernels..
[12:31] <scoundrel50a_> I'll see if I can work it out, and find out the ip address adn connect
[12:32] <tjaalton> easier to find the kern.log* which has the information from the bad boot..
[12:33] <scoundrel50a_> how do I do that then?
[12:33] <scoundrel50a_> oh just saw
[12:33] <scoundrel50a_> will go check
[12:34] <scoundrel50a_> just rebooting other machine
[12:37] <scoundrel50a_> I found kern.log, would you like to see a copy? See if you find out?
[12:38] <tjaalton> are there many of them? kern.log.1 etc
[12:38] <tjaalton> locate the one that has the info about the 3.0-rc1 kernel
[12:39] <scoundrel50a_> kern.log and kern.log.1
[12:40] <scoundrel50a_> and I think it is just kern.log that shows the kernels you want, shall I pastebin it?
[12:40] <tjaalton> for instance
[12:40] <tjaalton> you know the 'pastebinit' command?
[12:41] <tjaalton> need to install the package first
[12:41] <scoundrel50a_> can I do it via ubuntu pastebin it, can copy it
[12:41] <scoundrel50a_> give you the url
[12:42] <tjaalton> no, apt-get install pastebinit, then run 'pastebinit /var/log/kern.log'
[12:42] <tjaalton> then give me the url
[12:47] <scoundrel50a_> http://paste.ubuntu.com/619840/ sorry took so long, netbook at its limit
[12:49] <scoundrel50a_> brb
[12:53] <tjaalton> you could try adding 'GRUB_GFXPAYLOAD_LINUX=text' to /etc/default/grub, then run update-grub
[12:55] <scoundrel50a_> ok, will give it a go, is that done in Maverick?
[12:55] <tjaalton> no, it's a new feature in natty
[12:56] <scoundrel50a_> so how do I GET INTO IT THEN?
[12:56] <tjaalton> huh?
[12:56] <scoundrel50a_> oops sorry didnt know I had caps lock on till I sent sorry
[12:56] <tjaalton> you edit the file, and add that line..
[12:56] <scoundrel50a_> ok
[12:56] <tjaalton> then run update-grub, and reboot
[12:59] <scoundrel50a_> ok, do I need to add the inverted commers or leave them out
[13:03] <scoundrel50a_> ok, going to reboot into 11.04, after updating
[13:04] <tjaalton> inverted commers?
[13:05] <scoundrel50a_> things at beginning and end of text you gave me, dont know what they call them here
[13:05] <scoundrel50a_> and left them out, ran update rebooted and nothing
[13:05] <scoundrel50a_> backlight turned off again
[13:06] <scoundrel50a_> it actually turns off just before the log in page appears, and the drums sound
[13:06] <scoundrel50a_> why should it turn the light off
[13:07] <tjaalton> can you ctrl-alt-F1
[13:07] <tjaalton> to change to the virtual console
[13:07] <scoundrel50a_> I dont know, tried but no backlight, cant see anything
[13:09] <scoundrel50a_> I treid to get into recovery mode, a load of script went up the page, then the screen went black and now I cant see anything
[13:09] <scoundrel50a_> something is turning the light off
[13:11] <tjaalton> probably when the i915 module is loaded
[13:12] <scoundrel50a_> is there a way around it? I just tried to log on blind, clicked enter, then entered my password and I get logged in, but no light
[13:13] <scoundrel50a_> I have to use the on off button to turn off then
[13:13] <scoundrel50a_> it is loading
[13:13] <tjaalton> what is?
[13:13] <scoundrel50a_> Ubuntu
[13:14] <scoundrel50a_> I get the music
[13:14] <scoundrel50a_> but black screen
[13:14] <scoundrel50a_> the backlight needs to turn on
[13:15] <scoundrel50a_> I wish there was a way foryou to see what was happening
[13:15] <scoundrel50a_> I honestly think it is as simple as finding out what is turning the backlight off
[13:16] <scoundrel50a_> if this little netbook, Acer Aspire One can work on 11.04 I dont understand why my Lsptop which is the same make cant work either
[13:16] <tjaalton> you can blacklist the i915 kernel module, but you'd have a "crippled" system then
[13:17] <tjaalton> "the same make" != "the same hw"
[13:17] <scoundrel50a_> but if I have a crippled system that isnt worth using then
[13:17] <tjaalton> i bet the netbook doesn't have intel GM45 on it
[13:17] <tjaalton> then stick with maverick
[13:17] <scoundrel50a_> dont know
[13:17] <tjaalton> or lucid
[13:17] <tjaalton> which is lts
[13:18] <scoundrel50a_> I think I am going to have to. Its Maverick
[13:18] <scoundrel50a_> thank you I really appreciate the help
[13:18] <scoundrel50a_> I hope they manage to find out why it keeps turning the backlight off
[13:19] <tjaalton> an upstream bugreport might help..
[13:19] <scoundrel50a_> how can I do that?
[13:20] <tjaalton> sign in on bugs.freedesktop.org and file it under xorg, driver/intel
[13:22] <scoundrel50a_> ok, not seen that before, will try set up an account an file a report, thank you
[13:24] <tjaalton> actually, use product DRI and component DRM/Intel
[13:29] <scoundrel50a_> what version?
[13:30] <scoundrel50a_> and should I add an attatchment of anything?
[13:31] <tjaalton> leave the version
[13:33] <tjaalton> you could boot with adding 'drm.debug=0x02' to the kernel options
[13:34] <ScottK> RAOF: Is http://wstaw.org/m/2011/06/06/plasma-desktopcs1575.jpg what's supposed to happen when someone reports a bug on xserver-xorg-video-intel?
[13:34] <tjaalton> either by editing the grub boot entry when selecting the kernel, or add it to GRUB_CMDLINE_LINUX="" in /etc/default/grub
[13:36] <scoundrel50a_> tjaalton: ok, will try adding that to the grub file, just finishing the bug report
[13:36] <RAOF> ScottK: In Natty, or in Oneiric?  It is in natty, because the bugs filed post-release are generally of very low quality.
[13:37] <ScottK> It was natty.
[13:38] <RAOF> Bryce added that to the apport hook for natty post-release; a lot of the bugs that we get post-release for X *are* support requests, and so aren't well-handled on launchpad.
[13:38] <jcristau> a non-question with a question mark and yes/no answers?
[13:38] <ScottK> One of our more technical users was a bit put off by it, but was cool with it once I explained.
[13:38] <ScottK> In fact, there he is now.
[13:39]  * ScottK waves to jussi.
[13:39] <jussi> heya ScottK
[13:39] <RAOF> jcristau: Hm.  Now that I *read* it more thoroughly, it could do with a bit of a reword :)
[13:39] <ScottK> I've started using 'convert to a question' more, but you're right, that doesn't really solve the problem.
[13:40] <RAOF> It went through a couple of revisions; at first it pointed more directly at askubuntu.com, and that resulted in a lot of poor quality questions there :/
[13:41] <ScottK> That sounds like progress at least.
[13:41] <ScottK> Poor quality questions in the place for questions beats poor quality questions on the bug tracker.
[13:44] <jussi> I think it may be useful to reword the second option to include something like "Im sure its a bug" or something, rather than the only options being that it started after an update or I talked to people already. It doesnt leave much room for "I understand what Im doing, I want to report the bug"
[13:45] <ScottK> The problem is everyone thinks they know what they are doing.
[13:45] <RAOF> Heh.
[13:46] <jussi> Hrm
[13:47] <RAOF> I think it could do with a re-wording, and we'll likely do the same thing once 11.10 ships.  Would you consider sending a mail to ubuntu-x?
[13:47] <jussi> RAOF: of course I can do that - ubuntu-x@l.u.c? 
[13:48] <RAOF> Yup.
[13:50] <jussi> Ok, Ill try send it this afternoon. If you get a chance, please take a look at bug 793487 :) (and scream at me for all the things Ive missed telling you). 
[13:50] <ubot4`> Launchpad bug 793487 in xserver-xorg-video-intel (Ubuntu) "Kubuntu does not shut down when external monitor attached through displayport (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/793487
[13:59] <scoundrel50a_> tjaalton: hi I entered a bug, its #37986
[13:59] <jussi> RAOF: sent. Hope that isnt too log'sy.
[14:03] <tjaalton> scoundrel50a_: ok, now add the drm.debug=0x02 to the kernel options so the kern.log gets debugging info about the state
[14:04] <scoundrel50a_> so how do I do that? Would not have a clue
[14:05] <jussi> bryceh: looks like my message got caught in moderation or rejected. do I need to resend now Im subscribed or can you just accept it? 
[14:07] <tjaalton> scoundrel50a_: scroll back..
[14:11] <jussi> bryceh: never mind, I resent. 
[14:16] <scoundrel50a_> tjaaltonnow you lsot me, if I add that to /etc/default/grub how do I add it to the bug report? I have no clue, sorry, I have not entered a bug report before.
[14:18] <tjaalton> scoundrel50a_: add it to /etc/default/grub, run update-grub, boot with the bad kernel, then boot with the good one and edit kern.log to only have the bootlog from the bad kernel, attach that to the bugreport...
[14:18] <tjaalton> that=the edited log
[14:20] <scoundrel50a_> ok, I know you are going to kill me when I ask this, but how do I edit kern.log to only have bootlog from bad kernel......as I said this is completely new to me.......I am really sorry. :(
[14:20] <tjaalton> so you have a program you use to edit /etc/default/grub...
[14:20] <tjaalton> now copy kern.log somewhere and edit it
[14:21] <tjaalton> ..
[14:22] <tjaalton> it's big, but you'll find the new stuff at the end
[14:23] <tjaalton> or just attach the whole file, but remember to mark it as text/plain
[14:25] <scoundrel50a_> ok, added drm.debug=0x02 to /etc/default/grub ran update-grub and got this error /etc/default/grub: 13: drm.debug=0x02: not found.......it wont update now
[14:26] <scoundrel50a_> ok, added drm.debug=0x02 to /etc/default/grub ran update-grub and got this error /etc/default/grub: 13: drm.debug=0x02: not found.......it wont update now
[14:27] <scoundrel50a_> oh, sorry about that, dont know why it posted twice
[14:27] <tjaalton> you need to add it inside the double quotes in GRUB_CMDLINE_LINUX=""...
[14:27] <scoundrel50a_> ohhh
[14:29] <scoundrel50a_> updating now,
[14:31] <scoundrel50a_> ok done that, now I have opened the kern.log what do I add, to the log?
[14:34] <tjaalton> not add, delete the stuff that aren't interesting
[14:35] <tjaalton> which kernel did you boot?
[14:35] <scoundrel50a_> the broken one, now i am booting the old one, Maverick
[14:36] <tjaalton> which broken one, natty or 3.0-rc1
[14:36] <tjaalton> ?
[14:36] <scoundrel50a_> I see what you mean about editing, if I can work out what we need
[14:37] <tjaalton> so you can skip everything else, just take what was generated by the previous boot, and why not the current one that's with the known good kernel
[14:38] <tjaalton> +also
[14:40] <scoundrel50a_> I dont have natty, I only have 3.0-rc1 I am looking through now, but cant work out when it started from booting to 3.0-rc1, I found something that talks about backlight, trying to look through
[14:41] <tjaalton> sure you do
[14:41] <tjaalton> check the timestamps
[14:42] <tjaalton> and the version string
[14:42] <scoundrel50a_> even found something about status failed, timestamps are what I found
[14:43] <hyperair>  /aw
[14:43] <hyperair> oops
[14:43] <tjaalton> "Linux version 3.0.0-0300rc1-generic", search for that
[14:44] <scoundrel50a_> ok, completely lost, can I give you the file in pastebin, so you edit it? I honestly dont know what I am looking for.
[14:44] <tjaalton> no
[14:45] <tjaalton> if you can't edit it, then attach the whole file as text/plain mimetype
[14:46] <scoundrel50a_> I think I will have to do that, as I cant see what I am looking for......
[14:46] <tjaalton> you can't search for a string?
[14:46] <tjaalton> what editor are you using?
[14:53] <scoundrel50a_> sorry I havent got back to you, trying to add the file, but getting an error saying its too big, even though I set it to plain text.....have to pastebin it, by the looks of things.
[14:54] <tjaalton> it won't stay there forever
[14:55] <scoundrel50a_> Its times like this I wish I was younger and went to college to learn about computers
[14:55] <tjaalton> or buy machines that are certified ;)
[15:06] <scoundrel50a_> kern.log added, edited, but not sure if it is in the right place
[15:06] <scoundrel50a_> added the kern.log as attachment
[15:09] <tjaalton> yeah, looks good
[15:10] <scoundrel50a_> ok, I have to say, that was the most difficult thign i have done in ages, I love Ubuntu, but sometimes it is really confusing using it and the things associated with it. 
[15:10] <scoundrel50a_> Thank you for your help, I really appreciate it
[15:27] <tjaalton> scoundrel50a_: can you see a blinking cursor or the "ubuntu" splash-screen when the machine is booting up, and does the backlight turn off right when the login screen appears?
[15:32] <tjaalton> scoundrel50a_: also, you could try editing /etc/modprobe.d/local.conf, and add a line that says "blacklist acer_wmi", then try booting the 3.0-rc1 kernel
[15:33] <tjaalton> could be that it's conflicting with the i915 graphics module, both fighting for the acpi backlight control
[15:44] <tjaalton> at least that's something not loaded with the maverick kernel, so maybe blacklisting it will fix the issue
[15:49] <tjaalton> scoundrel50a_: I added that to the bug too, update it with what you find out
[15:49] <tjaalton> gotta run ->
[17:24] <scoundrel50a_> its booting up now
[18:07] <tjaalton> scoundrel50a_: booting up, as in working fine or not?
[18:11] <scoundrel50a_> not working
[18:12] <tjaalton> is the latest log with the acer_wmi module blacklisted?
[18:13] <scoundrel50a_> yes
[18:13] <scoundrel50a_> and still doesnt work
[18:13] <scoundrel50a_> no, sorry, just got what you meant, i WILL HAVE TO POST THAT NOW. sORRY
[18:14] <scoundrel50a_> sorry about caps
[18:14] <tjaalton> thanks :)
[18:14] <scoundrel50a_> on netbook
[18:41] <scoundrel50a_> tjaalton: have added the kern.log hope its worked properly
[18:56] <tjaalton> scoundrel50a_: ok, add to the upstream bug that this was with the acer_wmi module blacklisted
[20:25] <bjsnider> ricotz, have you noticed anything weird about the numlock key in gnome 3? Mine is chaotic. the key needs to be off for the numpad to work, or something
[21:13] <ricotz> bjsnider, havent noticed this, works for me as expected