[00:19] i cant upgrade to jaunty always says that some packages cant be downloaded [00:19] W:Failed to fetch http://security.ubuntu.com/ubuntu/dists/jaunty-security/Release Unable to find expected entry partner/binary-i386/Packages in Meta-index file (malformed Release file?) [00:19] , W:Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/jaunty-updates/Release Unable to find expected entry partner/binary-i386/Packages in Meta-index file (malformed Release file?) [00:19] , E:Some index files failed to download, they have been ignored, or old ones used instead. [00:24] hello? [00:25] can someone help with that? [00:26] nevermind, ill just edit sources.list [00:35] i dont see partner in any of the releases [00:35] you need to enable it [00:36] System> Administration> Software Sources> Third-Party Software> Partner [00:42] hadnt noticed that repo before [01:55] hello all [01:56] I know this is the wrong place for support with atheros wireless cards, but I have tried my local chat, #ubuntu, and madwiwfi and I cant find any help anywhere. can you all please help [02:01] I have a atheros AR242X , I have tried 6 different drivers and I cant get it to work [02:10] if someone is able to and hopes to help, they will certainly need a little more detail [02:26] hello all, i am running the latest jaunty, and my x is broken (using nvidia's video drivers from the repo), is this a known issue? is there a workaround? [03:00] dereks: set to nv instead of nvidia for driver in xorg.conf until you figure it out [03:01] mikegriffin: i did that :) but i like nvidia's when possible [03:01] you asked for a workaround [03:02] i just upgraded and also have a broken nvidia binary driver, i have yet to spend much time working on it [03:02] was this a new install or an upgrade? [03:13] mikegriffin: new install [03:18] are you familiar with dkms? i am just figuring out where the pieces are [04:53] !info deluge-torrent [04:53] deluge-torrent (source: deluge-torrent): A Bittorrent client written in Python/PyGTK. In component universe, is optional. Version 0.5.9.3-1 (jaunty), package size 2074 kB, installed size 5872 kB [04:54] :oo [07:02] <^Manu> is it recommended not to use 9.04? [07:02] <^Manu> 8.10 is causing me problems. [07:03] <^Manu> what sort of things should i expect to go wrong in 9.04? [07:13] ^Manu: you can probably expect things to just randomly not work if using a pre-release version [07:13] since they are still in the process of getting everything to work together [07:13] <^Manu> the 8.10 iso seems to be busted, it wont boot no matter what i do.. the 8.04 and 9.04 iso's both work fine.. [07:14] <^Manu> i've downloaded 8.10 from 2 different places, and burned it to a few discs at different speeds... i can't install 8.10 :/ [07:14] i would install 8.04 then update to 8.10 then, personally [07:14] <^Manu> i have no internet .. i can't update on the net :( [07:14] ah [07:14] <^Manu> i have unmetred access to a bunch of iso's, that's it.. [07:15] <^Manu> so 9.04 will just cause me problems then? without a doubt? [07:15] well, it depends how much you care if some things may not work sometimes then lol if it were me, i would install 8.04, it wasn't that much different than 8.10 [07:15] <^Manu> its just a media player.. i don't need the gui.. [07:16] <^Manu> i have 8.04 installed now.. [07:16] i would say its very likely that 9.04 would cause you some problems [07:16] <^Manu> its too old.. [07:16] <^Manu> it doesn't support my hardware. [07:16] especially if you cant update it [07:16] <^Manu> i had to install the kernel from 9.04 in 8.04 to make the ethernet and sata work.. [07:16] <^Manu> but i need video drivers from 8.10 at least aswell.. [07:16] <^Manu> and its leading into a mess. [07:16] ah [07:17] i wonder why your 8.10 iso's are not booting [07:17] <^Manu> i have no idea.. [07:17] well if its not a critical system, you could always instal 9.04 and hope for the best [07:17] <^Manu> either the 8.10 kernel doesn't like this pc for some reason, or the burner i'm using really doesn't like something about the 8.10 iso.. [07:17] <^Manu> there's something slightly wrong with the 8.10 iso either way.. [07:18] <^Manu> i've wasted a bunch of cd's on it.. i only have one left... i can't waste that one. [07:18] <^Manu> yeah, that's what i'm thinking.. [07:18] <^Manu> will 9.04 update as it progresses? [07:18] <^Manu> ie, will updates be released, until i am running an effective mirror of the release when it comes? [07:19] yes, it updates constantly [07:19] but that could be a pain without internet... [07:19] <^Manu> okay well i'll just see how i go i guess.. [07:19] <^Manu> i need cutting edge drivers.. [07:20] how will you update it? [07:20] lol [07:20] <^Manu> 9.04 has the latest kernel and seems to get the latest stuff yeah? [07:20] <^Manu> i have extremely slow internet, i can update one or 2 packages.. [07:20] ah [07:20] <^Manu> but i can't install 8.10 from the net.. thats hundreds of mb.. [07:20] yep thats true [07:21] <^Manu> haha, it's not going well.. the 9.04 installers partitioning program is having trouble straight up :( [07:21] if you need cutting edge drivers, current 9.04 won't work [07:22] the X server abi is incompatible with the proprietary non-Free drivers [07:22] <^Manu> intel drivers are free aren't they? [07:22] <^Manu> are the intel drivers supported by 9.04? [07:22] yes [07:22] <^Manu> so i'll be okay then? [07:23] <^Manu> i have an X4500HD, very new intel IGP.. [07:23] that's just as far as the X server abi is concerned [07:23] <^Manu> man.. everything i try and do is causing a shit fight.. [07:24] <^Manu> i've heard that i can copy the 8.10 live cd to a usb stick and boot the installer from that? [07:24] <^Manu> somehow... [07:24] i did that for my eeepc a while back with 8.04 i think [07:24] <^Manu> it's "Scanning disks" and taking forever.. [07:24] i dont remember the exact process, but yeah [07:24] <^Manu> 9.04 doesn't like me either.. [07:24] maybe some problem with the sata [07:25] <^Manu> grrr [07:25] <^Manu> the sata didn't work in 8.04 [07:25] <^Manu> i installed the latest kernel from jaunty and that worked though.. [07:25] <^Manu> 8.04 complained about some things while booting with that kernel, but it generally worked fine.. [07:26] well there is always Vista (soooo j/k) [07:26] <^Manu> *sigh [07:26] maybe you need a different distro... [07:26] <^Manu> ubuntu is the only super cutting edge distro thats well supported. [07:26] ubuntu is not usually the best for supporting a broad range of drivers in my experience [07:26] <^Manu> and i like debian based distros [07:26] <^Manu> what is best? [07:27] <^Manu> can i just use debian? it's usually way old though. [07:27] <^Manu> actually, it can't hate the sata.. it displayed the partition table.. [07:27] in my personal experience (this is just my experience) suse and mandriva tend to have much better hardware support than ubuntu (i use all three daily) [07:28] <^Manu> it just wont let me click the 'format' checkbot, and tell it the partitions mount point. [07:28] you could, after all, just use jaunty's kernel with the rest being hardy or intrepid [07:28] <^Manu> hrmm, i dont like rpm based distros :/ [07:28] <^Manu> i can't install intrepid.. [07:28] i like distros that work on my hardware ;-) [07:28] <^Manu> haha [07:29] <^Manu> okay, so what i'll do now.. [07:29] <^Manu> is boot 8.04 again. [07:29] <^Manu> change my package repos to intrepid. [07:29] <^Manu> and install the latest video drivers from intrepid.. [07:29] <^Manu> and hope for the best.. [07:29] <^Manu> what are the chances if epic meltdown? [07:29] * kniolet wishes you luck [07:30] <^Manu> so 'high' then? [07:30] i dunno [07:30] thats hard to say without trying it [07:30] <^Manu> man, linux sucks.. it never bloody works :P [07:30] <^Manu> i've been messing with this for 2 and a half days now.. [07:30] wait didnt you say you dont need the gui? [07:30] <^Manu> trying assorted mixtures of stuff... [07:31] <^Manu> i plan to boot right into xbmc, a media front end.. [07:31] <^Manu> and i'll want to run emulators and shit too.. [07:31] <^Manu> but i don't *need* a gui... no.. [07:31] ah [07:32] just wondering since you updating the video drivers [07:32] <^Manu> i do need all the drivers and shit set up properly. and i'm a linux spastic.. i figured ubuntu would sort that out for me, and then i'd just edit the startup to not start the window manager. [07:32] <^Manu> well i need the video drivers for video related stuff, but i don't need a windows environment.. [07:33] <^Manu> jaunty's being retarded.. the partition tool is freaking out for some reason.. [07:33] <^Manu> i can't progress... [07:33] :-( [07:33] <^Manu> i just need to tell it which partition is root.... [07:35] <^Manu> i need an easy way to boot from a cd image on a usb.. [07:35] <^Manu> i'm so over messing with shit.. [07:36] https://help.ubuntu.com/community/Installation/FromUSBStick [07:51] <^Manu> okay, so i have a new idea.. [07:51] <^Manu> i can install the latest intel driver from source in 8.04 right? [07:51] <^Manu> how do i go abou tthat? [11:26] Hi, I am doing the upgrade right now, what do you guys think about it? What should I expect? === erle64- is now known as erle- [14:13] not sure if this is the right place for this as I am running 8.10 but I enabled ubuntu-backport I got the 2.6.27-11 kernel from ubuntu-backport and a couple of things stopped working. Is that relevant for Jaunty? Should I report it somewhere? [14:38] andresmh, report the bug against intrepid. [14:38] ok === Dereks_ is now known as xdereksx [18:29] someone wake up and take my bug report, I've got an issue specific to 8.10 and compiz. [18:29] To be specific , when all graphical effects are turned off and metacity runs alone, firefox does... weird shit. [18:29] !bug | terli [18:29] terli: If you find a bug in Ubuntu or any of its derivatives, please file a bug report at: http://bugs.launchpad.net/ubuntu - Bugs in/wishes for the bots can be filed at http://launchpad.net/ubuntu-bots [18:29] but if you turn compiz back on , even if it uses the gtk generic generator [18:29] it will not freak out [18:29] and terli, please watch the language [18:30] jussi01: are you certain you want me to file the bug report? [18:30] terli: bug reports are a good thing if thewres a bug. also, 8.10 support is in #ubuntu now [18:30] When I file bug reports people on canary island run around in really small circles holding their ears and chanting "nonononono this should never, ever, ever happen even with a one in a million chance!" [18:31] um, sorry I ment jaunty [18:31] 9.04 [18:31] I'm getting my versions mixed up [18:31] hehe. ok, but please do file a bug report, if its not correct a triager will tell you [18:32] well I don't know what to file it on [18:32] firefox or compiz [18:32] it technically effects neither [18:32] and it involves both [18:34] terli: there is an "I dont know" option [18:34] *rolls some dice* [18:34] the dice say this issue will not be fixed by release date. [18:35] *crushes the dice into really small dicelets* [18:35] terli: please file the bug, it doesnt take long, and lets see. :) [18:35] I'm doing it ASAP [18:41] bug report filed. [20:02] hey, does anyone else have problems with 3d acceleration running old radeon cards in jaunty? [20:05] terli: with fglrx_ [20:06] um [20:06] radoen [20:06] aiglx [20:06] open source [20:09] Is there any way to bring up the i810 chipset in Jaunty? I get a blank screen for gdm, and a lot of color [20:09] in the tty terminals. I can´t use any of it. [20:12] I get the same thing for the terminals [20:12] gdm works fine here though [20:12] try shaking the cursor :-P [20:15] hey! YOU! DEVS! users have to be in group video for accelleration! [20:57] Poison[BLX]: the module you seek maybe in the additional modules packages, but I don't think it is [20:58] the restricted modules? [20:58] yup [20:58] it's not :/ [20:59] madwifi based drivers are, but they don't work on the card I have [21:00] rats [21:00] actually running intrepid on the box, but grabbed the jaunty 2.6.28 kernel because 100 mi away from here I have the same card in a Gentoo box and couldn't get it running with anything other than 2.6.28 and the ath5k driver lol [21:01] mixing the kernel is a bad call [21:01] (in my opinion) [21:01] perfectly reasonable but unsupported [21:02] * DanaG wishes there were a non-warranty-voiding way to make his new USB sound card stop BLINKING. [21:02] DanaG: black electrical tape over the led? [21:03] * DanaG slaps the manufacturer ("Voyetra Turtle Beach")... [21:03] I mean why the does a sound card need to BLINK? [21:03] =þ [21:04] Electrical tape would work, yes. [21:04] I also wonder why it has a "Speaker" slider AND a "Speaker 1" slider. [21:05] How, without any access to internet from a *nix system, would I get ahold of the tree and headers to hand build a module? Everything I've found starts with the assumption that I can use apt-get [21:05] You can download the headers .deb file and stick it on a storage device of some sort. [21:06] Use another system to download the deb file. [21:07] DanaG: all I have in the way of other systems is a borrowed Vista laptop (and no joy on livecd wireless working on it, painfully enough) [21:08] I'm about ready to pack up the system and drag it off 100mi with me to some proper internet... it would spare the silly questions ;) [21:08] What I mean is, you could download from in Windows. [21:09] Just browse the http://archive.ubuntu.com/pool tree to find the headers .deb files. [21:09] Or even go to packages.ubuntu.com [21:09] (that'll give you info on dependencies, which you'll need.) [21:09] ooh, handy! thanks! [21:10] You'll likely need linux-headers-generic, linux-headers-2.6.28, linux-headers-2.6.28-generic, and some other variants. [21:10] start at the top with linux-headers-generic. [21:10] http://packages.ubuntu.com [21:12] if you have register-level data docs, you can simply twiddle the appropriate registers to disable the blinking or the led altogether [21:12] or, if you can disable the blinking in another os, just sniff the urb traffic [21:13] the latter process is more time-consuming, of course, but it's how we reverse-engineer a lot of stupid OEM usb-audio quirks [21:13] thanks for all the help on this (especially considering how far removed from "supported" it technically is... :D) [21:15] The official drivers don't let you disable it, either. [21:15] The official Turtle Beach drivers make it a solid red on mute, but alternate CM106 drivers I need for Vista 64 do not. [21:17] Perhaps I should contact the company and ask how to disable the LED entirely. [21:18] yeah, ask for docs, too, while you're at it =) [21:18] Even their own Vista64 drivers also don't have working channels 7 and 8, supposedly. [21:19] Oh yeah, another thing in my laptop: AES2810 fingerprint reader... http://www.reactivated.net/fprint/wiki/Unsupported_devices#AuthenTec_AES2550_.26_AES2810 [21:20] " Sourcing one of each of these devices (this is made difficult because they only seem to be found in laptops) " -- not really that hard; it's like 30 bucks for the board from HP's parts store. [21:20] get one and ship it to daniel drake, then [21:22] http://h20141.www2.hp.com/hpparts/Part_Where_Used.asp?mscssid=FA5D63B6FE14424B8CAD91E598E90F44&SearchCriteria=495063-001 [21:23] Oh yeah, and my issue with the stick buttons on the touchpad... it turns out it also affects Windows. I can't use stick-middle for scrolling and pad-middle for actual middle button. :( [21:24] do you have an alps or a synaptics? [21:24] Synaptics. [21:24] interesting. hp usually ships alps. [21:24] The stick's buttons seem to be actually wired to the touchpad device, electrically. :( [21:25] It also has multi-touch disabled; my old laptop's Synaptics could do at least basic multi-touch. [21:25] No "Advanced Capability Bits" reported. === Rafik_ is now known as Rafik [21:40] Oh yeah, is there any way to tell, from an xorg log, which CRTCs particular outputs on a video card are attached to? [21:41] My dad got an HD3450 video card with DVI-I, HDMI, and VGA, and I'm trying to figure out (without buying any hardware) whether it'll be able to do DVI-D + HDMI. [21:41] Simultaneously, I mean. [21:49] DanaG: depends how verbose the logging to Xorg.*.log is [21:50] Aah. He's using XP, but I'd be using the Intrepid 64-bit livecd. [21:52] For comparison, here's the log on my laptop. http://pastebin.com/f3826df28 [21:53] Oh, easiser: xrandr --verbose === sepheebear is now known as Sepheebear [22:24] hi [22:24] in gnome-appearance the dpi setting is not correct [22:24] it seems that it is hard coded to 96 instead of the real dpi of the display [22:24] https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/157398 [22:24] Ubuntu bug 157398 in gnome-control-center "GNOME default DPI doesn't match X default DPI" [Wishlist,Won't fix] [22:25] btw, i just wonder why the dpi is changeable by the user ... [22:25] this seems pretty stupid to me ... [22:40] I also think it's bad that people recommend CHANGING the dpi setting as a fix for too-big font sizes. [22:40] If your fonts are too big... change the font size! [22:40] "My fonts are too big!" answer: "Change it to 96DPI!" -- WRONG! [22:40] err, not precisely [22:41] if there is a dpi issue with the driver, then that definitely needs to be fixed [22:41] yes, it would be better to remove that dpi-thing in gnome [22:41] crimsun: but it has to be fixed in the xorg.conf, not in some gconf-key [22:41] What I mean is that, if the DPI is correct and the fonts are too big... people suggest changing the DPI, and that's wrong. [22:42] so either the whole setting should change the xorg.conf-file or remove it [22:42] On my laptop, radeon and radeonhd give different DPI results. [22:42] DanaG: yes, i have seen that many times [22:42] Real DPI is 147; radeonhd gets it correct. Radeon assumes 96. [22:43] maybe it would be good to slap a big label next to the dpi setting "don't touch this freaking thing " [22:43] Or link here: [22:43] this bug annoys the hell out of me [22:43] http://members.ping.de/~sven/dpi.html [22:43] at least 5 different bug reports on that matter and at least the same amount on "ideas" on brainstorm [22:43] DanaG: yes, that bit about changing the font size as a hackaround is understood to be utterly incorrect [22:44] however, we do need the infrastructure to be correct -first- [22:44] crimsun: the gnome bug is already fixed" [22:44] It also reminds me of how people often suggest "dpkg-reconfigure xserver-xorg" as if it were the be-all, end-all (not sure I'm using that expression correctly) of solutions. [22:44] the patch is already there, who checks that xorg's values are at least reasonable, before using them [22:45] either gnome has forgotten to include the patch, or ubuntu has forgotten it [22:45] either way, it sucks :-P [22:45] Oh yeah, so that is a bug: [22:45] (II) RADEON(0): clock: 165.3 MHz Image Size: 331 x 207 mm [22:45] (==) RADEON(0): DPI set to (96, 96) [22:46] that radeon thing is obsolete by all means, i hope they through it out in the future [22:46] It has all the info it needs: physical size and screen resolution (1920x1200); it shouldn't be assuming 96. [22:46] DanaG: can you point me to the svn/git? [22:46] svn? I haven't used it, myself. [22:46] ah ok [22:47] I'm actually using Jaunty with the Intrepid X server, so I can use fglrx; oddly enough, anything newer than 8.543 panics. [22:47] Or rather, gets a general protection fault. [22:48] That reminds me: /me switches to radeonhd... [22:51] OOpsie... (EE) No devices detected. [22:52] ouch [22:52] which card? [22:53] afaiu thgis is our problem: [22:53] driver sets the wrong dpi -> toolkits expect that xorg doesn't report the right idea, assume something themselves -> toolkits have userchangeable dpi-settings, so users can fix it theirselves -> users do stupid things with it like using it to change their font size [22:53] Mobility HD3650. [22:53] Note that I'm also on the Intrepid radeonhd. [22:53] Latest 64-bit Jaunty kernel breaks * by building CONFIG_DRM=y [22:54] * as in "everything" [22:54] :-/ [22:54] mhh will try it [22:54] ... apparently it affects radeonhd, and not just fglrx. [22:54] have jaunty myself [22:54] Either that... or loading the fglrx module breaks loading radeonhd. [22:54] ... even after unloading fglrx. [22:55] I do wonder why all the newer fglrx versions give me hard-lockups like that. [22:55] It happens even with fglrx on the intrepid livecd. [22:55] * DanaG tries fglrx again... [22:57] Undefined symbol firegl_queryMCRange [22:58] you have to reboot [22:59] DanaG: i'm just bugging the radeon-devs about the dpi ... [23:00] The thing is, fglrx is also broken... undefined symbol. [23:00] could you load radeon and tell me the output of xdpyinfo | grep resolution? [23:02] That gives 147x147. [23:02] mhh [23:02] Perhaps the log is lying about using 96x96. [23:02] and what does your xorg-log say? [23:02] is 147 right? [23:03] (==) RADEON(0): DPI set to (96, 96) [23:03] could you paste the /var/log/Xorg.0.log to pastebin.com? [23:03] 147 is correct. [23:03] ah ok [23:04] handy thing: serial-over-lan. it lets me get full stacktraces for panics and such. [23:05] http://pastebin.com/f71b2be17 [23:05] thx [23:05] That's fglrx panic log. [23:05] i would need the log with "(==) RADEON(0): DPI set to (96, 96)" [23:05] Oh, the full Xorg log? Easy enough. [23:06] http://pastebin.com/f184b7b55 [23:06] (pidgin slashexec plugin + pastebinit == win) === bobbo_ is now known as bobbocanfly === bobbocanfly is now known as bobbo [23:10] Oh, I see why it's getting undefined symbol: that symbol is in libfglrxdrm... which won't load because of the CONFIG_DRM=y [23:11] why would the router reboot itself sporadically ? Tried 2 different firmwares Oleg's and dd-wrt mega build - same thing [23:11] on Asus WL500 Premium v2 [23:15] bug 312721 [23:15] Launchpad bug 312721 in linux "Jaunty: CONFIG_AGP=y breaks ATI graphics" [Medium,Fix committed] https://launchpad.net/bugs/312721 [23:16] ah, that's the one. [23:16] Good, fix committed. [23:17] I do still wonder why newer fglrx panics, whereas the older one does not.