[12:39] <cjwatson> highvoltage: best talk to evand, who wrote it
[12:41] <Kopfgeldjaeger> n8
[02:35] <m1ke> Will a xbox 360 wireless controller be supported in future updates?   Just curios since it is so popular and a preferred controller of choice.
[04:42] <mekius> bryce: ping
[05:19] <bryce> mekius: rather than ping me, just ask a question, so I can answer it when I get back, even if you're not
[05:20] <mekius> bryce: I apologize :)
[05:21] <mekius> bryce: Is the use of xdebconfigurator sane, or should i really be using something else?
[05:21] <mekius> i noticed it is looked for in the dexconf script
[05:21] <mekius> and is used if there
[05:22] <bryce> hmm, I don't notice 'xdebconfigurator' in my dexconf
[05:23] <mekius> oh wait
[05:23] <mekius> it is in the 20xconfig script in the casper-bottom scripts in initrd
[05:23] <mekius> sry about that, been looking at a lot of files trying to put this auto loading of drivers together
[05:24] <bryce> no prob
[05:24] <bryce> yeah it's a confusing nest of scripts in there
[05:24] <mekius> it seems though that xdebconfigurator uses a card db of sorts to setup the debconf database with the right X values
[05:24] <mekius> so that when dexconf reads it, it actually gets an autogenerated one
[05:24] <mekius> but there might be something else in place already
[05:26] <bryce> hmm, unfortunately I'm not too familiar with casper internals yet
[05:27] <mekius> ok :)
[05:27] <mekius> yeah, it is hard to find any docs on this type of stuff :)
[05:27] <bryce> yeah
[05:27] <bryce> can you explain what you're thinking you need it for?
[05:28] <mekius> well i don't know if you remember me, but we need to make sure a custom VIA driver loads for X, but don't want to break compatibility with other systems
[05:28] <mekius> but i'd like to do it as right as possible
[05:28] <bryce> ah, right
[05:28] <mekius> in case we work anything out with others
[05:29] <mekius> but dexconf reads from debconf db, just trying to find the piece that auto configures the db
[05:29] <mekius> and xdebconfigurator seems to do that :)
[05:30] <bryce> I think now you know more about this area of the code than me.  :-)
[05:30] <mekius> hehe
[05:30] <mekius> xorg 7.3 will be nice
[05:30] <mekius> it is suppose to do all this by itself
[05:30] <mekius> will be very cool if it works well
[05:31] <bryce> which package is the 20xconfig script in?
[05:31] <mekius> well it is part of the casper scripts, i'm not entirely sure :)
[05:31] <mekius> the scripts inside the initrd image
[05:31] <bryce> yup; of course that's not magic either - you'll want to make sure your driver is accounted for inside the x codebase so it gets detected and loaded correctly
[05:32] <mekius> yep
[05:32] <mekius> but i hope they make it easy to update this or something
[05:32] <mekius> if it is hardcoded that doesn't seem too good heh
[05:32] <bryce> it's hardcoded, but the code itself is pretty straightforward... just setting some defines and stuff
[05:33] <mekius> hmm
[05:33] <bryce> ok, found it in 'casper'
[05:34] <mekius> why not make this editable via a card database or something so if someone does have a newer card or a weird card, support can be added in a custom distribution for that PC
[05:36] <bryce> I suppose they don't see that as a huge need, but I'm not sure.  I imagine they'd say, "Send us a patch."  ;-)
[05:37] <mekius> yeah hehe
[05:38] <mekius> thx for all the help btw
[05:39] <bryce> sure, I'm digging into xdebconfigurator right now
[05:39] <bryce> looks like it's a wrapper around a variety of detection tools
[05:39] <mekius> yeah
[05:39] <mekius> tries to get strings and compare them against data in a Cards file
[05:39] <mekius> i installed the hwdata package but it didn't have a Cards file :P
[05:40] <mekius> i found a random one at /usr/share/apps/guidance/Cards+
[05:40] <mekius> seems to follow the format but not sure heh
[05:41] <bryce> oh that's different, that's for kde-guidance.  unrelated
[05:41] <mekius> yeah i know
[05:41] <mekius> but the format of the file is pretty much identical :)
[05:41] <mekius> and has quite a few of the cards in it
[05:42] <mekius> not sure why the hwdata package doesn't contain the Cards file unless there is no central file
[05:42] <mekius> and you are meant to just define you overrides
[05:42] <bryce> ok I get what's going on here
[05:43] <bryce> xdebconfiguration is a wrapper script that calls a variety of different underlying hardware identification systems
[05:43] <bryce> one of the systems it calls is discover, which I mentioned the other day
[05:44] <mekius> yeah
[05:44] <mekius> i figured this is the one i will want :)
[05:44] <bryce> I *think* that all you need to do is get your card+driver recorded in one of the underlying programs (i.e., insert it into discover-data, as I described before), and this should pick it up from there
[05:45] <bryce> xdebconfigurator will read the info from discover, and populate debconf with it
[05:45] <mekius> ok nifty, let me check this out :)
[05:47] <mekius> /lib/discover eh
[05:47] <mekius> ?
[05:47] <mekius> has a bunch of xml files :)
[05:47] <mekius> sweet, yes, this looks like the one :)
[05:47] <mekius> awesome, thx again, sometimes it helps to have that little push in the right direction :)
[05:48] <bryce> I have to say thanks myself - this xdebconfigurator finally explains the one piece of the whole process that was still sort of a black box to me.
[05:48] <mekius> :)
[05:48] <mekius> yeah, for some reason it wasn't on our live cd
[05:48] <mekius> i'm not sure if i accidentally removed it at some point :/
[05:53] <mekius> bryce: VIA has an open source driver that they develop, I don't know all the details of how open source it is or how much community involement they have, but what are the chances of this driver being able to be on the livecd and such to better support VIA hardware?
[05:54] <bryce> heh
[05:54] <bryce> there's quite a story here
[05:54] <mekius> hehe
[05:54] <bryce> there are actually three drivers for via.  -via, -openchrome, and -unichrome
[05:54] <bryce> all are adequately open source
[05:55] <bryce> -unichrome was a fork of it, that the community began developing
[05:55] <mekius> yeah, via -> openchrome
[05:55] <bryce> however due to a strong personality leading that effort, the community forked again, to make -openchrome
[05:55] <mekius> unichrome is supposedly better coded, but doesn't support as much :)
[05:55] <mekius> yeah i read most of it heh
[05:55] <bryce> I think partly due to this forking, it's hampered things
[05:56] <mekius> yeah, i can imagine
[05:56] <bryce> -via is the most official, but if I understand correctly, isn't very actively developed
[05:56] <mekius> the unichrome dev doesn't want to just put in new cards and features though unless they are coded perfectly :)
[05:56] <mekius> via i think is dead
[05:56] <bryce> I do not know if VIA is involved in its maintenance
[05:56] <mekius> i think openchrome has picked it up
[05:56] <mekius> i don't think so, they have their own driver
[05:56] <mekius> which i believe they release source for
[05:57] <mekius> and we are actually in talks to hopefully get this stuff even more out there and open
[05:57] <bryce> hmm, then that would be a fourth.  :-P
[05:57] <mekius> indeed, but this one should support most new hardware, but might be a bit less stable, not sure :)
[05:58] <bryce> url?
[05:58] <mekius> viaarena.com is their open source "portal"
[05:58] <mekius> well community portal i gues
[05:58] <mekius> guess*
[05:59] <bryce> anyway, I've heard good things about -openchrome and have considered promoting it to main and making it the default for via hardware; I hadn't thought about the livecd, though
[05:59] <mekius> i haven't looked at the licensing for them, but if there are any conflicts with packaging it, let me know and we can discuss this with them :)
[05:59] <mekius> yeah, openchrome is pretty good as far as i can tell
[05:59] <mekius> but still lacking support for the newest cards :)
[06:00] <mekius> openchrome has 3D for most of the older cards (can't imagine very fast, but doesn't hurt)
[06:00] <mekius> they are talking of trying to do compiz type effects on these cards, i'm a bit skeptical :)
[06:10] <mekius> bryce: i think this is it, has all the cards in there and I think the ones we have aren't returning anything, so i'm updating it and hopefully the via driver will load :)
[06:10] <mekius> will be so awesome if it does :)
[06:11] <bryce> great!
[06:11] <mekius> honestly it sucks that they all name their driver via :P
[06:11] <mekius> otherwise you could do hints for the different drivers heh
[06:11] <mekius> cause certain cards work best with the different drivers :)
[06:15] <bryce> yeah
[06:15] <bryce> hmm, poking through a few of their drivers, yeah they look like they're all licensed BSD
[06:16] <bryce> doesn't seem like they've structured things open source-ish though... no mention of how to contribute stuff, no sign of public rcs, etc.
[06:17] <bryce> so guess it qualifies as open source by license, not open source by community
[06:17] <mekius> yeah
[06:17] <mekius> which is what i've seen as well
[06:17] <mekius> so i think I and my team will try to push them to open up to the community
[06:17] <mekius> they have a lot of packaged versions
[06:18] <mekius> so i'm not sure if they do those themselves or have people do them for them
[06:18] <bryce> that'd be good.  I wonder if there's an overlap with what the openchrome folks are doing
[06:18] <mekius> the build system they have for their drivers is kinda ugly though :P
[06:18] <mekius> i don't think so
[06:18] <mekius> afaik the openchrome is just an extension of the original via driver and continues by just using docs that are available
[06:18] <bryce> ah
[06:19] <mekius> would be nice if via would fuel openchrome though
[06:19] <mekius> as openchrome is closer to the community and seems like a better overall drivers
[06:19] <bryce> yeah
[06:19] <bryce> unfortunately that hardly ever works out for a company to collaborate with an existing open source community
[06:20] <mekius> yeah :/
[06:20] <bryce> mekius: do you know if some of their drivers are already in ubuntu?
[06:20] <mekius> i really think they could help each other a lot
[06:20] <bryce> agreed
[06:20] <mekius> openchrome and via are in there
[06:21] <mekius> i don't think the unichrome drivers are in ubuntu
[06:21] <mekius> the via driver has feisty packages i believe, but not in the repo
[06:21] <bryce> what about their savage driver?  is that the same as xserver-xorg-video-savage?
[06:21] <mekius> not sure on that one
[06:21] <mekius> those cards are so old lol
[06:21] <bryce> yeah
[06:22] <mekius> it probably is not though
[06:22] <mekius> i love intel right now, working right with the community and contributing to the intel driver shipped with xorg
[06:22] <mekius> just lovely :)
[06:22] <bryce> yup
[06:22] <mekius> i bought an intel laptop largely because of that
[06:23] <bryce> yup, I got a laptop and a desktop because of that
[06:23] <mekius> :)
[06:23] <bryce> they've got a fair number of bugs though
[06:23] <mekius> gonna build a desktop soon, might go amd though, still deciding on the video card for that heh
[06:23] <bryce> but I like that the process is open and we can just chat directly with the devs about the problems
[06:23] <mekius> might go with an nvidia integrated until AMD releases enough specs to have a great driver for their stuff :)
[06:24] <mekius> bryce: yes, that is so nice
[06:24] <bryce> we've really been enjoying working with alex deucher on -radeon issues
[06:25] <mekius> how long before they release some more specs?
[06:25] <mekius> btw, do you work on X or what is your specialty?
[06:25] <bryce> yes X
[06:26] <bryce> I don't know when they're going to release more specs, but I suppose it should be any time now
[06:26] <bryce> I talked with one of the development managers for fglrx at XDS.
[06:26] <mekius> neat
[06:26] <bryce> smart fellow, but I wasn't as impressed at his attitude towards open source
[06:26] <mekius> yeah
[06:27] <mekius> i think some people just can't understand it
[06:27] <bryce> but it's amazing they're releasing the specs
[06:27] <mekius> I'm sure some of the long time ATI devs might be sore about that :)
[06:27] <mekius> maybe they feel threatened hehe
[06:28] <mekius> the only holdout is nvidia
[06:28] <mekius> hopefully they will crack too :)
[06:28] <bryce> it sounded like AMD's strategic goals required having their graphics chips with an available open source driver
[06:28] <bryce> I'm not so sure about that
[06:28] <mekius> that is cool
[06:29] <bryce> the reason ATI released specs is to support AMD's main processor sales
[06:29] <mekius> well you open source the driver, you open yourself up to embedded linux stuff much more
[06:29] <bryce> nVidia doesn't have that pressure
[06:29] <mekius> yes, true
[06:29] <mekius> i think the gpu should be just as open as the cpu at this point though
[06:29] <mekius> they are both processors, different instruction set
[06:30] <mekius> anything ever happen with that open graphics project?
[06:30] <bryce> you might be right, as embedded devices gain more sophisticated graphics capabilities
[06:30] <mekius> indeed
[06:30] <bryce> which one?
[06:30] <mekius> not sure
[06:30] <mekius> i recall one where they were building it ground up
[06:30] <mekius> designing the processor, making the drivers
[06:31] <bryce> the one to design an open design for a graphics chip?  don't know, but I think they took on a pretty ambitious objective
[06:31] <mekius> yeah heh
[06:31] <mekius> i don't think the hardware was as capable as today's hardware
[06:32] <mekius> not sure if it could hold against intel or what not heh
[06:34] <mekius> http://wiki.opengraphics.org/tiki-index.php
[08:35] <tepsipakki> mekius: unchrome is in universe since edgy
[08:35] <tepsipakki> unichrome..
[10:29] <tepsipakki> anyone here who could push the new ati package, currently waiting for approval?
[10:56] <Treenaks> hm, bugs.freedesktop.org's cert expired les Wednesday
[10:59] <Treenaks> les=last
[12:54] <Amaranth> mjg59: any idea how resume from suspend could fail on the ptyb9 device?
[02:00] <nicolai> siretart: any progress with the cryptsetup@installer thing? can i help somehow? i got it working in QEMU (manual partitioning, cryptsetup, lvm)
[03:19] <Lhademmo1> , can anyone tell me where in the docteam svn trunk is the GNOME Desktop Users Guide? I can't find it!
[03:22] <gameldar> heya all
[03:23] <minghua> Lhademmo1: Are you sure docteam has a svn repo for GNOME desktop user's guide?
[03:24] <gameldar> just looking at https://wiki.ubuntu.com/SponsorshipProcess - I have a fix for a bug I need to upload for sponsorship. Does the requestsponsor script work for others in gutsy?
[03:27] <geser> gameldar: iirc it was broken but I don't know if it still is
[03:27] <gameldar> geser: is there an alternative way of submitting them then?
[03:27] <persia> gameldar: You can also request sponsorship manually: just make sure everything is attached, and subscribe the appropriate team to the bug (see further down the page).
[03:34] <Lhademmo1> minghua. no, but wherer  is it thrn?
[03:35] <minghua> Lhademmo1: The upstream svn of GNOME desktop user's guide should be http://svn.gnome.org/viewcvs/gnome-user-docs/
[03:36] <minghua> Lhademmo1: I have no idea if docteam have another svn repo, I suggest you ask in #ubuntu-docs
[03:36] <minghua> Lhademmo1: Hmm, #ubuntu-doc, apparently.
[03:36] <Lhademmo1> minghuam its because of bug 126988
[03:36] <ubotu> Launchpad bug 126988 in ubuntu-doc "Incorrect text to add logout (exit) button" [Low,Confirmed]  https://launchpad.net/bugs/126988
[03:38] <minghua> Lhademmo1: As I've said, go to #ubuntu-doc and ask.
[03:38] <Lhademmo1> k
[03:38] <minghua> Lhademmo1: Be aware that it's weekend though, so developers may be not around.
[03:39] <Lhademmo1> nah, I've noticed that :)
[04:14] <cjwatson_> bryce: we don't use xdebconfigurator (it got into casper by way of a merge from Debian, where it's an optional feature I believe), so if you're looking to it to explain part of our process I think you've found a red herring :-)
[04:52] <gameldar> heya all again
[04:53] <gameldar> persia: sorry got disconnected (I updated to the latest packages and it killed my wireless kernel driver).... I have a question about the sponsorship still.
[04:54] <persia> gameldar: OK.  Which bug?
[04:55] <gameldar> bug 126314 - I have the debdiff now - do I modify that bug to add it to the list shown on: https://launchpad.net/~ubuntu-universe-sponsors/+subscribedbugs
[04:55] <ubotu> Launchpad bug 126314 in anjuta "Anjuta crashes on opening or creating a glade file" [Undecided,Confirmed]  https://launchpad.net/bugs/126314
[04:57] <persia> gameldar: First, this package is a universe package (MOTU Developers), so #ubuntu-motu is a better channel, but it's a weekend, so here is fine for now (next time, ask there).
[04:58] <persia> Second, you'll need to wrap the patch into a debdiff.  There are some instructions in the "Preparing New Revisions" section of https://wiki.ubuntu.com/MOTU/Contributing
[04:59] <gameldar> persia: ok thats done (followed that part)
[05:00] <persia> Do you mean with http://launchpadlibrarian.net/9678551/anjuta-2.2.0.patch?  If so, you're missing a changelog entry.
[05:00] <gameldar> no i haven't uploaded it yet - after I do that I assign the bug to ubuntu-universe-sponsors?
[05:00] <persia> Third, once you've attached the debdiff to the bug, use the "Subscribe Someone Else" action (upper left) to subscribe ubuntu-universe-sponsors
[05:01] <persia> gameldar: Don't assign.  Just subscribe.
[05:01] <gameldar> persia: ahh ok
[05:03] <gameldar> persia: thanks for that - I have it up there now!
[05:04] <persia> gameldar: Great.  Thanks for taking the time to make a debdiff from the patch.
[05:06] <gameldar> persia: Not a problem.
[05:08] <gameldar> thanks again for those steps. time for me to sleep - bye all
[05:23] <mekius> tepsipakki: ah ok, wasn't aware of that :)
[05:43] <cypherbios> ogra: Hi. Could you tell me who is the responsible for the Edubuntu addon CD? I mean, the building process. Is that the release team or someone else?
[05:45] <cjwatson> cypherbios: ubuntu-cdimage team; I deal with most of the code though much of the code for the Edubuntu addon CD was contributed by Edubuntu people
[05:45] <cypherbios> I am interested in the script used to separate the .desktop and icons files (if any is used) for use with the gnome-app-install
[05:46] <cjwatson> check out http://people.ubuntu.com/~cjwatson/bzr/cdimage/mainline/, check out the bits in configs/devel within that
[05:46] <cjwatson> then debian-cd/tools/gutsy/app-install.sh
[05:48] <mjg59> Amaranth: It doesn't. That's a false call from pm_trace
[05:49] <cypherbios> cjwatson: thank you. It seems to be exactly what I was looking for
[06:40] <Amaranth> mjg59: ok then, i'm lost :/
[06:52] <cromo> I just noticed that vino-server ignores hosts.allow and hosts.deny. this seems to be a serious security issue.
[07:08] <Amaranth> hrm, update-manager doesn't make sure ubuntu-desktop is installed?
[07:29] <pochu> slangasek: liferea uploaded, fyi (in case you have time to let it go in)
[08:01] <soren> Amaranth: No, but if it's installed, it makes sure that it stays that way.
[09:42] <superm1> bryce, i was looking a little more regarding bulletproofx stuff.  during the live cd, debconf is updated with the results of the casper-reconfigure xserver-xorg.  is this data supposed to also be copied over to the resultant system though?  By what mechanism is it supposed to occur?
[09:43] <bryce> I believe it should; yes.  I am not certain of the process used, though
[09:44] <superm1> hm well for us its for sure not happening, and that is where the issue lies.  i didn't see any references to reconfiguring xserver-xorg in ubiquity source, so i wonder if there is an external hook by which it is supposed to happen
[09:45] <superm1> bryce, do you know who i should ask to determine that this week?
[09:45] <bryce> superm1: cjwatson
[09:46] <superm1> bryce, okay i'll talk to him during business hours this week. thanks, have a good weekend :)
[09:59] <cjwatson_> superm1: casper/ubiquity-hooks/20xconfig copies xorg.conf over
[10:01] <cjwatson> superm1: the relevant bits of the debconf database aren't copied over, but per general debconf design principles they aren't supposed to need to be
[10:21] <cjwatson> superm1: apologies in advance for the confusing accept/reject mails about mythtv; I only noticed that there were two in the queue with the same version after hitting accept, and therefore switched to rejecting the first and accepting the second
[10:22] <cjwatson> (please try not to do that in future though; bump the version for the second upload instead)
[10:50] <YokoZar1> weird weird weird: put "xdg-open $HOME" (with the quotes) in a terminal
[10:50] <YokoZar1> It returns an error saying there's no such file or directory for your home folder
[10:51] <YokoZar1> without quotes it works fine
[10:51] <mjg59> YokoZar1: If you put quotes around the entire thing, bash is interpreting it as a command called xdg-open\ /home/whatever
[10:52] <mjg59> Which obviously doesn't exist
[10:52] <YokoZar1> mjg59: ok
[10:52] <Viper550> Just wondering, does Ubuntu use hwd to detect X settings?
[10:52] <YokoZar1> mjg59: it comes from this question though: if you make an applications menu entry for xdg-open $HOME, it will fail (with or without quotes)
[10:53] <mjg59> It's probably not doing environment expansion
[10:53] <mjg59> Try ~ rather than $HOME
[10:53] <xjkx> why not bring "broadcom dell wireless 1390" support natively?
[10:53] <mjg59> xjkx: It is.
[10:53] <YokoZar1> mjg59: ahh, that worked.  Hmmm
[10:54] <xjkx> mjg59, here http://ubuntuforums.org/showthread.php?t=297092 it says i have to apt-get lol...
[10:54] <mjg59> xjkx: There's a driver included with the distribution, but we're not allowed to distribute the firmware that's required for it to work
[10:55] <Viper550> hello, can I just discuss something?
[10:55] <xjkx> mjg59, then what should I do? apt-get won't work with no nic
[10:56] <mjg59> xjkx: Use a wired connection to obtain it? There's basically nothing we can do here, I'm afraid. We're not legally permitted to provide you with the firmware.
[10:57] <xjkx> mjg59, why you cant
[10:57] <xjkx> provite it
[10:57] <mjg59> xjkx: Because the copyright holder hasn't granted us permission to do so
[11:01] <xjkx> at least these sudo apt-get install build-essential ; sudo apt-get install linux-headers-`uname -r` could be avoided, they are free softwares
[11:02] <Viper550> Just wondering, is anyone familar with the tool hwd?
[11:04] <xjkx> mjg59, what do you think? Download the driver on other system that i have connection and install isn't the problem, the problem is building essential and getting kernel headers that i cant just simply download and install, there is the dependencies thing
[11:05] <mjg59> xjkx: You don't need to build anything. The driver is included already.
[11:05] <xjkx> the tutorial is crazy then? :p
[11:06] <xjkx> its on ubuntuforms
[11:07] <xjkx> mjg59, i am not an advanced user, what is really needed, this firmware is what package, ndiswrapper?
[11:09] <mjg59> xjkx: #ubuntu is a better place to ask this sort of thing
[11:13] <Chipzz> xjkx: for the record, apt-get *will* work without a nic (if you know what you're doing)
[11:13] <Viper550> Just wondering, I found this awesome tool for autoconfiguring X
[11:13] <xjkx> Chipzz, i mean with no connection at all
[11:14] <xjkx> its out of the network world
[11:15] <Chipzz> xjkx: you have to put the right files in the right place
[11:15] <Chipzz> by means of an usb stick
[11:15] <Chipzz> (for example)
[11:15] <Viper550> http://user-contributions.org/projects/hwd/hwd.html
[11:16] <Chipzz> /var/lib/apt/lists/ is where the package indexes go, /var/cache/apt/archives is where the .debs go
[11:16] <Chipzz> !weekend | Viper550
[11:16] <ubotu> Viper550: It's a weekend.  Often on weekends, the paid developers, and a lot of the community, may not be around to answer your question.  Please be patient, wait longer than you normally would, or try again during the working week.
[11:16] <xjkx> Chipzz, i know how to dpkg, the problem is that if i download the packages on other system i wouldn't have a way to know what needs what
[11:17] <Chipzz> sure you can?
[11:18] <Chipzz> apt-get --print-uris update
[11:18] <mjg59> Viper550: No, we don't use hwd
[11:18] <Chipzz> download the files it prints
[11:18] <Chipzz> (you have to rename them though)
[11:18] <Chipzz> put those in /var/lib/apt/lists
[11:18] <Viper550> why don't we? You know, if we used it, if someone had to regenerate their X config, they could just go "hwd -xa"
[11:18] <Chipzz> apt-get --print-uris install foo
[11:19] <Chipzz> download the files it prints and put these in /var/cache/apt/archives
[11:19] <mjg59> Viper550: As opposed to dpkg-reconfigure xserver-xorg?
[11:19] <Chipzz> apt-get install foo
[11:19] <mjg59> Chipzz: Please move this to #ubuntu
[11:19] <Viper550> yeah. it would be theoretically quicker to do that, since it wouldn't go through a long reconfigure process that is not needed
[11:19] <Chipzz> mjg59: or rather, I'll shut up now ;)
[11:19] <mjg59> Or just run dexconf
[11:20] <Viper550> is it as quick?
[11:20] <Amaranth> mjg59: if having it fail on ptyb9 is not correct do you have any idea what else i can test?
[11:20] <Amaranth> mjg59: on resume the cd drive spins up, don't think the HD does, and that's it
[11:20] <Amaranth> no keyboard, no screen, nothing
[11:23] <mjg59> Amaranth: What type of hardware?
[11:24] <Amaranth> mjg59: http://rafb.net/p/8MzWKH81.html
[11:24] <Amaranth> mjg59: hp laptop
[11:25] <mjg59> Using nvidia?
[12:23] <MrMazda> Does gutsy have a startup option that allows to use legacy drivers instead of libata for IDE HDs?