[06:58] <xubuntu-1925> hola! buenas tardes amigos
[06:58] <xubuntu-1925> howdy everyone?
[06:58] <xubuntu-1925> just a kwik question from me
[06:58] <xubuntu-1925> does xubuntu 13.10 support uefi laptops?
[06:59] <xubuntu-1925> why do i ask rather than trying out? because my network connection is very slow
[06:59] <bazhang> !uefi
[06:59] <bazhang> xubuntu-1925, ^
[07:00] <xubuntu-1925> hey bazhang! howdy man? u redirected me from the other forum
[07:00] <xubuntu-1925> :)
[07:06] <xubuntu-1925> alrighty then! ima gonna go ahead and try it out. wish me luck guys as i get ready to wipe off windows 8 and install xubuntu 13.10 pre-release. and pray for my well being. ;)
[07:06] <xubuntu-1925> :)
[10:24] <majorJ> can install saucy salamander desktop from command line while running 13.04 desktop currently? or do i need to install it from ISO?
[10:26] <Ian_Corne> yes
[10:26] <Ian_Corne> replace the sources
[10:26] <Ian_Corne> and run apt-get update && apt-get dist-upgrade
[10:26] <IdleOne> that isn't the proper way
[10:26] <Ian_Corne> sure fire way :p
[10:27] <Ian_Corne> IdleOne: he asked for commandline
[10:27] <IdleOne> do-release-upgrade -d
[10:27] <k1l> Ian_Corne: that is not the ubuntu way.
[10:27] <Ian_Corne> won't that run the update-manager ?
[10:27] <k1l> Ian_Corne: we have so-release-manager for cli
[10:27] <IdleOne> Ian_Corne: that is a command line way, but you're still wrong
[10:27] <k1l> nope
[10:27] <Ian_Corne> aha
[10:27] <Ian_Corne> ok :)
[10:27] <Ian_Corne> what does do-release-upgrade do more?
[10:27] <IdleOne> debian way doesn't always work best in ubuntu.
[10:27] <Ian_Corne> remove old packages?
[10:28] <IdleOne> Ian_Corne: it handles the process in the way ubuntu expects it to be handled
[10:28] <k1l> Ian_Corne: depends on what changes come with a new release
[10:29] <k1l> and a important thing is the handling of the PPA
[10:29] <IdleOne> also, he didn't wait long enough to get an answer. Probably best he didn't.
[10:38] <Ian_Corne> Aha, you mean disabling them all k1l ? :p
[10:38] <Ian_Corne> or does it pick up when there's $newversion ppa's available?
[10:38] <IdleOne> ppa handling is not done by the upgrade-manager
[10:39] <IdleOne> don't know if there is a 3rd party utility that does it, but in the past they had to be manually updated. the upgrade-manager does disable them o upgrade.
[10:39] <IdleOne> s/o/on/
[15:48] <MoPac> Howdy. I'm wondering if I'm alone in being unable to get CCSM to run in Saucy?
[16:10] <MoPac> Alternately, is there any non-ccsm program or procedure I can use to enable such functions as edge flipping between workspaces?
[19:12] <comodo_dragon> i want to install iceweasel browser on ubuntu 13.10
[19:12] <ikonia> is there a package for it in the repo ?
[19:12] <ikonia> (I've not checked so don't know)
[19:12] <comodo_dragon> i try that but i get iceweasel is up to date
[19:13] <comodo_dragon> Note, selecting 'firefox' instead of 'iceweasel'
[19:13] <ikonia> correct ?
[19:13] <ikonia> comodo_dragon: so you don't want to install it, you want to update it
[19:13] <comodo_dragon> how? how do i run it too?
[19:13] <ikonia> hang on, one thing at a time
[19:13] <ikonia> is it installed already, yes/no
[19:13] <comodo_dragon> ok
[19:13] <comodo_dragon> Note, selecting 'firefox' instead of 'iceweasel'
[19:13] <comodo_dragon> firefox is already the newest version.
[19:13] <comodo_dragon> 0 upgraded, 0 newly installed, 0 to remove and 32 not upgraded.
[19:13] <comodo_dragon> thats output of apt-get install iceweasel
[19:13] <ikonia> no, that's not what I'm asking
[19:14] <ikonia> ok, ok
[19:14] <ikonia> so iceweasel is actually a package reference to firewall
[19:14] <ikonia> sorry, firefox
[19:14] <ikonia> typo
[19:14] <k1l> !find iceweasel
[19:14] <ikonia> (mind whas elsewhere)
[19:14] <k1l> i think there is no iceweasel in ubuntu
[19:15] <k1l> iceweasel is the debian free stuff for firefox
[19:15] <ikonia> no, looks like it's firefox - or not at all
[19:15] <comodo_dragon> ah
[19:16] <comodo_dragon> so what do i do
[19:16] <ikonia> use firefox would be the easy solution
[19:16] <Pricey> iceweasel IS firefox!
[19:16] <comodo_dragon> i like the gui,
[19:17] <ikonia> well, it has somethings removed, mostly branding I believe
[19:17] <comodo_dragon> and its abit lighter
[19:17] <TJ-> Pricey: No it isn't! (looks over Pricey's shoulder at the approaching IP lawyers from Mozilla :)
[19:18] <comodo_dragon> haha
[19:18] <ikonia> there maybe 3rd party repos that host it, but be aware of the risks (potentially) of using them
[19:18] <TJ-> Iceweasel was the Debian repackaging of Mozilla's Firefox because the Firefox trademark rights make it non-free according to Debian. Ubuntu had to get an agreement with Mozilla to carry it. https://support.mozilla.org/en-US/questions/959830
[19:18] <Pricey> TJ-: Pfft.
[19:19] <Pricey> https://wiki.debian.org/Iceweasel too fwiw
[19:20] <TJ-> Yeah... harks back to 2008
[19:20] <TJ-> bug #269656
[19:21] <comodo_dragon> http://packages.debian.org/squeeze/i386/iceweasel/download
[19:21] <comodo_dragon> dependency not satisfiable xulrunner-1.9.1
[19:22] <TJ-> comodo_dragon: If you want to use iceweasel why not just install Debian?
[19:22] <comodo_dragon> its not very user friendly
[19:22] <comodo_dragon> prefer ubuntu
[19:22] <TJ-> Most of Ubuntu *is* Debian!
[19:23] <Pricey> iceweasel IS firefox :(
[19:26] <k1l> like i said before: iceweasel is firefox just with removed name and logo due to license drama the debian guys like.
[20:50] <ochawkeye_> hello all - trying to get a driver installed on a brand new piece of hardware.  [this page](http://wireless.kernel.org/en/users/Drivers/brcm80211) mentions [this](http://wireless.kernel.org/en/users/Drivers/brcm80211).  What am I looking for?
[20:50] <ochawkeye_> (this test)[http://wireless.kernel.org/en/users/Drivers/brcm80211]
[20:51] <ochawkeye_> doh - that's the same link twice.  sorry. was trying to point out this portion http://pastebin.com/SCAhavbH
[20:51] <ikonia> what's your actual question ?
[20:52] <ochawkeye_> "The kernel log will tell you the exact file name.".  Am I looking for something in particular in /var/log/kern.log?
[20:53] <ikonia> what is the question, what are you looking for ?
[20:53] <ochawkeye_> the nvram file name
[20:53] <ikonia> for what ?
[20:53] <ikonia> could you just summerise your question onto a line
[20:53] <ochawkeye_> For SDIO driver you need to copy the nvram for your system and place it in /lib/firmware/brcm. The nvram file name depends on the chip you have. The kernel log will tell you the exact file name. For the USB driver no nvram file is needed.
[20:54] <ikonia> ok, so you want the chip name so you can find hte firmware,
[20:54] <ikonia> lspci should show you the chipset, as will the kernel log at boot time when it detects the device
[20:54] <ochawkeye_> based on specification, i know the chip name.  but i do not know the nvram file name
[20:54] <ikonia> you'll probably seee it trying to find/load it in the kernel boot
[20:57] <ochawkeye_> device is BCM43241 [8086:9c3a] (rev 04); i do not see that anywhere in kern.log:  http://paste.ubuntu.com/6211053/
[20:59] <ikonia> you should see it trying to find the firmware and failing file not found
[21:00] <ikonia> that file name should give you a clue to what it's looking for
[21:00] <ochawkeye_> in kern.log?  that was my entire dump
[21:00] <ikonia> I've not looked through it
[21:00] <ikonia> I was just telling you what you should be looking for
[21:00] <ikonia> or suggesting I should say
[21:01] <ochawkeye_> i appreciate any help; but you've told me *what* i should be looking for.  problem is i don't know  *where* to be looking for that
[21:02] <ochawkeye_> my kern.log is 11 lines; it doesn't mention this device or any file names, so I am doubtful kern.log is the log I am interested in
[21:02] <ikonia> the kernel log should show it at boot time, it will try to find the firmware and you'll see it try to load the file it wants
[21:03] <ikonia> look in the syslog
[21:03] <ochawkeye_> (one of) my problems is knowing semantics.  you say "the kernel log".  i thought that meant kern.log.  looks like syslog is more what i am trying to use
[21:04] <ikonia> the kernel log can be the right place, if you look at the syslog config you'll see different message levels are redirected to specific log files, mail log, syslog, kernel log, security log etc etc
[21:04] <ikonia> you'd have to check the syslog config, but it will be the kernel log that's either in the syslog or the kern.lo
[21:04] <ikonia> log
[21:05] <TJ-> ochawkeye_: /var/log/kern.log will contain all messages from the kernel... it should be a *lot* more than 11 lines, unless  /var/log/kern.log has just been 'rotated' by logrotate, in which case the rotated file will be /var/log/kern.log.1
[21:06] <TJ-> ochawkeye_: syslog will contain message from the kernel and other daemons as well, which can be useful during run-time to identify related events from different sources.