[02:05] <Glamdring1> I just inherited a used laptop. I've just installed Lubuntu, as I'd had good experiences with it on my desktop computer and had no DVDs around to carve nearly any other OS anyway. I can't seem, however, to enable its wi-fi. I'm wondering at this point if it's a hardware problem. How can I figure this out?
[02:07] <anarkhein> How far do you get? Any error messages? What laptop? What wifi card?
[02:08] <Glamdring1> Compaq 6715b. It basically acts like there's no wi-fi card at all, best I can figure; no error messages.
[02:08] <Glamdring1> Best assume I don't know what I'm doing, though.
[02:09] <Glamdring1> For example, while I take it on faith this has a wi-fi card in it because it has a little unlit wi-fi LED, I have little idea other than that.
[02:09] <anarkhein> Have you tried a command like "lshw", "lspci", etc.?
[02:10] <Glamdring1> Interesting. Here we are. 30:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 02)
[02:10] <anarkhein> This page got some commands for identifying hardware: http://www.brunolinux.com/02-The_Terminal/Hardware_info_commands.html
[02:10] <Glamdring1> That at all helpful?
[02:10] <anarkhein> WLAN... ok.
[02:11] <anarkhein> What about moduls...
[02:11] <Glamdring1> That's the name of the command?
[02:11] <Glamdring1> (Again, best assume I don't know what I'm doing.)
[02:12] <anarkhein> Try "lsmod"
[02:12] <anarkhein> See if you see something related to BCM there.
[02:12] <Glamdring1> Okay. Doing so now.
[02:13] <Glamdring1> bcma                   52443  1 b43
[02:13] <Glamdring1> Closest thing I saw to obviously related.
[02:13] <Glamdring1> Also, darnit, be right back.
[02:14] <anarkhein> Ok.
[02:14] <anarkhein> Have a look at these two threads: http://ubuntuforums.org/showthread.php?t=1528945    http://askubuntu.com/questions/461384/how-to-connect-to-wifi-from-lubuntu
[02:14] <anarkhein> I reckon there are some clues.
[02:16] <anarkhein> I think what you found is the right one: "Since the 3.3.1 kernel the bcma module was introduced." - https://wiki.archlinux.org/index.php/Broadcom_wireless
[02:16] <anarkhein> Maybe it's just a matter of specifying the details of your wifi network connection.
[02:16] <anarkhein> For info about that, check out those two ubuntuforums threads.
[02:22] <Glamdring1> Okies. Thanks, I'll take a look.
[02:22] <Glamdring1> Oh-ho-ho cute, so it's probably Broadcom's fault.
[02:30] <Glamdring1> Hrm. I'm afraid I don't really know how to parse the Archlinux info; a lot of it seems kinda specific to Arch.
[02:30] <Glamdring1> Seems to me, anyway.
[02:30] <Glamdring1> Is it feasible to use Arch stuff for Lubuntu with ease?
[02:35] <Glamdring> (Same guy, just two different computers. It's very, very uncomfortable sitting on the floor to deal with the short ethernet cord which allows that laptop to connect to the internet right now.)
[02:38] <Glamdring> Hrm. Odd.
[02:48] <Glamdring> Well, fringe benefit to trying to stay here on two computers. I'm still here.
[03:07] <anarkhein> Hmm.
[03:08] <Glamdring> If that happens too often, I'll take the laptop offline and just communicate from the desktop.
[03:08] <Glamdring> Thoughts on the Archlinux thing?
[03:08] <anarkhein> I didn't mean that you should use Arch stuff, I just found on that page a confirmation that the bcma module indeed is for Broadcom wifi.
[03:09] <Glamdring> Oh! Apologies. In which case I'm honestly not sure how to proceed.
[03:09] <anarkhein> What have you tried already when it comes to network config?
[03:09] <anarkhein> What programs?
[03:09] <Glamdring> Lemme check. Memory fails.
[03:09] <Glamdring1> nm-applet
[03:12] <anarkhein> And exactly how far do you get? Do you... the device isn't even detected by the program, so of course you see no networks in the list?
[03:13] <Glamdring> Precisely.
[03:14] <anarkhein> Hmm
[03:15] <anarkhein> Did you try any of the commands referenced in the two threads?
[03:16] <Glamdring> I believe so. Most were of a diagnostic nature, right?
[03:16] <anarkhein> I think maybe you should try: nmcli dev wifi connect mynetwork password my-password
[03:16] <anarkhein> However...
[03:17] <Glamdring> Oh?
[03:17] <anarkhein> First you should try some of the others, to get info about the wifi status
[03:17] <Glamdring> Fair enough.
[03:17] <anarkhein> For instance: nmcli d
[03:17] <anarkhein> Then: nm-tool
[03:19] <anarkhein> Does the first command return something along the lines of: "DEVICE TYPE             STATE
[03:19] <anarkhein> wlan0  802-11-wireless  disconnected"?
[03:19] <Glamdring> Be on that shortly.
[03:19] <anarkhein> And the second command something more elaborate, including driver info?
[03:24] <Glamdring1> Okies, let's take a look at this.
[03:24] <anarkhein> Wait.
[03:24] <Glamdring1> Oh?
[03:24] <anarkhein> There is another possibility.
[03:24] <anarkhein> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/545443
[03:24] <anarkhein> Hmm, but wait again. This was posted in 2010...
[03:25] <Glamdring1> Ah.
[03:25] <anarkhein> So surely it's fixed by now?
[03:25] <Glamdring1> Well then, for what it's worth, all I got was "eth0       802-3-ethernet    connected  "
[03:25] <anarkhein> CONNECTED?
[03:25] <anarkhein> Ahh -eth-, not wifi.
[03:25] <Glamdring1> eth0, right.
[03:25] <Glamdring1> Hence my being here at all.
[03:26] <anarkhein> I thought perhaps it was mentioned, but just didn't get anywhere.
[03:26] <Glamdring1> nm-tool doesn't mention anything about wireless.
[03:26] <anarkhein> Ok...
[03:26] <Glamdring1> So lspci sees it, but nm-applet decidedly does not.
[03:27] <anarkhein> How about using the ifconfig command?
[03:27] <Glamdring1> eth0 and lo
[03:27] <anarkhein> "sudo ifconfig wlan0 up", but first check whether it's called "wlan0" or something else
[03:28] <anarkhein> just "ifconfig", doesn't mention anything wlan-related?
[03:28] <Glamdring1> That was, sadly, just ifconfig
[03:28] <anarkhein> Ok.
[03:29] <Glamdring1> Would there be any harm in that wlan0 up command if, in fact, there was basically no wlan0 to be had?
[03:29] <anarkhein> I don't think so.
[03:29] <anarkhein> I can't guarantee anything, but...
[03:29] <anarkhein> ...I imagine something like "device not found".
[03:29] <Glamdring1> Doubt it'll do any good, but if there's no harm I can't see a reason not to try.
[03:30] <anarkhein> But it should have been listed.
[03:30] <Glamdring1> I figured as much.
[03:30] <Glamdring1> Yep. As you suspected.
[03:30] <anarkhein> À propos the bug from 2010:
[03:30] <anarkhein> "apparently the "trick" was to press fn+f2, don't know if that is the bulletproof solution, but it seems to work for me"
[03:31] <anarkhein> Could it be...?
[03:31] <Glamdring> O.o
[03:31] <Glamdring> That sounds odd.
[03:31] <anarkhein> Yea.
[03:31] <Glamdring> Like, now?
[03:31] <Glamdring> Or during boot?
[03:32] <anarkhein> Maybe when the network manager is up, I'm not sure.
[03:32] <anarkhein> But...
[03:32] <anarkhein> Could there be some driver issues?
[03:32] <Glamdring> Probable.
[03:33] <anarkhein> Hmm http://askubuntu.com/questions/453587/broadcom-wifi-issue-on-14-04-lubuntu
[03:33] <Glamdring> Broadcom apparently has a history of those.
[03:33] <anarkhein> http://askubuntu.com/questions/649662/lubuntu-15-04-broadcom-wi-fi-wont-work-at-all
[03:33] <Glamdring> 15.04, no less!
[03:34] <anarkhein> "You could take a look at the additional drivers page, if you search additional drivers in unity. (Sorry, did not notice you were using Lubuntu, just search for additional drivers.)"
[03:34] <anarkhein> "There you will come across the different drivers that may be used, which came in handy for me because Ubuntu did not use any driver for my wifi at all. For me it was just a simple flip from no driver to the broadcom driver."
[03:34] <Glamdring> Oddly, it found none for me. Though I'll look again.
[03:35] <anarkhein> http://askubuntu.com/questions/55868/installing-broadcom-wireless-drivers
[03:36] <Glamdring1> Sure seems like a familiar problem. It's 4 years old, though.
[03:36] <Glamdring1> Ah, yes.
[03:36] <anarkhein> How about "iwconfig"?
[03:36] <Glamdring1> I had looked at this one.
[03:36] <Glamdring1> Same. Just lo and eth0
[03:36] <anarkhein> Ok.
[03:37] <Glamdring1> That 4 year old one seemed promising, but the firmware package doesn't seem to be available anymore.
[03:38] <anarkhein> "lspci -knn | grep 'Eth|Net' -EA2" - This surely mentions the wifi card too at least?
[03:39] <Glamdring1> In addition to the ethernet card, it lists:
[03:39] <Glamdring1> 30:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 02)
[03:39] <Glamdring1> 	Subsystem: Hewlett-Packard Company BCM4311 802.11b/g Wireless LAN Controller [103c:1374]
[03:39] <Glamdring1> 	Kernel driver in use: b43-pci-bridge
[03:40] <anarkhein> Hmm...
[03:40] <anarkhein> Did you see...
[03:40] <anarkhein> "Then in a terminal and with a temporary working internet connection, do:"
[03:40] <anarkhein> "sudo apt-get purge bcmwl-kernel-source"
[03:41] <anarkhein> "If it is not removed because it isn't installed, that's fine, just continue:"
[03:41] <anarkhein> "sudo apt-get install firmware-b43-installer"
[03:41] <anarkhein> ?
[03:41] <anarkhein> "Reboot and your wireless should now be working."
[03:41] <Glamdring1> My only concern is that the apt-get command came up empty.
[03:42] <anarkhein> Which of them? The first one?
[03:42] <Glamdring1> The firmware one.
[03:42] <anarkhein> How about adding -v?
[03:42] <anarkhein> For verbose.
[03:43] <Glamdring1> I hadn't seen advice to purse the bcmwl yet, so I hadn't tried it, but unless I'm as much a n00b as I very well might be... Ah! Verbose is good.
[03:43] <Glamdring1> Hrm. Except it seems to have taken it to mean -version
[03:44] <Glamdring1> Purge. Purge. Why did I type purse?
[03:44] <Glamdring1> S isn't anywhere's near g.
[03:44] <anarkhein> Yeah, because... "-q, --quiet  Quiet. Produces output suitable for logging, omitting progress indicators."
[03:44]  * Glamdring1 purges his lips.
[03:44] <anarkhein> It is not without messages by default. This is peculiar.
[03:45] <Glamdring1> Well, you see, this was its message:
[03:45] <Glamdring1> E: Unable to locate package firmware-b43-installer
[03:45] <Glamdring1> Kinda straightforward, really.
[03:46] <Glamdring1> Aptitude, perhaps?
[03:46] <anarkhein> How about...
[03:46] <anarkhein> "apt-cache search b43"?
[03:47] <Glamdring1> Hrm. Literally nothing.
[03:48] <Glamdring1> Didn't even complain about the command.
[03:48] <anarkhein> "aptitude search b43"?
[03:48] <Glamdring1> I'll install aptitude real quick.
[03:48] <anarkhein> If nothing, look in the GUI package manager.
[03:48] <anarkhein> Ok.
[03:49] <Glamdring1> Or not.
[03:49] <Glamdring1> Also, the GUI package manager, Synaptic, came up with no results for b43
[03:49] <anarkhein> Hmmm...
[03:49] <anarkhein> What is your current repository URL?
[03:49] <Glamdring1> Package aptitude is not available, but is referred to by another package.
[03:49] <Glamdring1> This may mean that the package is missing, has been obsoleted, or
[03:49] <Glamdring1> is only available from another source
[03:49] <Glamdring1> E: Package 'aptitude' has no installation candidate
[03:50] <Glamdring1> What's the best command for finding out?
[03:50] <anarkhein> Also, this would have been easier if I had been more loyal towards e.g. Lubuntu. I'm all over the places, checking out various distros instead of becoming an expert on one.
[03:51] <Glamdring1> For shits and giggles, I changed my repository from the Canadian server to the main server.
[03:51] <Glamdring1> (I don't live in Canada, but that seems to have been the default.)
[03:51] <anarkhein> By the way...
[03:51] <Glamdring1> Hai?
[03:52] <anarkhein> dmesg | grep *b43*
[03:52] <anarkhein> or something else related to the wifi
[03:52] <anarkhein> Just to see if there are any error messages.
[03:52] <anarkhein> dmesg | grep *wifi*
[03:52] <Glamdring1> Oh fer fucks sakes, so you know how I just said that I just changed my repository from Canada to Main?
[03:52] <anarkhein> or maybe *wlan*
[03:52] <anarkhein> Yes.
[03:53] <anarkhein> It wasn't a good idea? Or something went awry?
[03:53] <Glamdring1> Dunno what the star means on the legend, but now Synaptic sees firmware- b43-installer
[03:53] <anarkhein> Ok...
[03:53] <anarkhein> GET IT
[03:53] <Glamdring1> As well as firmware-b43legacy-installer, which was also referenced.
[03:53] <anarkhein> Right.
[03:54] <Glamdring1> Looks like the star means it's not authenticated. Do we care?
[03:54] <anarkhein> I'm not a complete... formalist like that.
[03:54] <Glamdring1> Sounds like we don't care a great deal about it, then.
[03:55] <anarkhein> I don't. However, it's your call.
[03:55] <Glamdring1> Says some of the packages couldn't be retrieved from the server.
[03:55] <anarkhein> Ok.
[03:55] <anarkhein> Try some other repository URLs?
[03:55] <Glamdring1> In fact, rather a few.
[03:56] <Glamdring1> Any suggestions?
[03:56] <Glamdring1> Maybe Aptitude? I recollect it tends to be better at fixing broken packages.
[03:56] <anarkhein> Not specifically. Something close to where you are, then for the sake of diversification, maybe Germany, UK.
[03:56] <anarkhein> Ok.
[03:56] <anarkhein> Also...
[03:56] <anarkhein> "some of the packages" - that is, dependencies?
[03:57] <Glamdring1> Looks like, yes.
[03:57] <anarkhein> Packages which... right.
[03:57] <Glamdring1> I didn't go through painstakingly to see for sure, but they had that look.
[03:57] <anarkhein> Yeah.
[03:57] <Glamdring1> (I can't imagine another reason libc++ etc would have been mentioned.)
[03:58] <anarkhein> But "couldn't be retrieved from the server" - this makes me think of the repository URL anyway.
[03:58] <Glamdring1> Bah. Looks like that was an Aptitude dependency.
[03:58] <Glamdring1> I'll try simply installing the firmware.
[03:59] <anarkhein> Ok.
[03:59] <Glamdring1> Bah. Several errors along the lines of:
[03:59] <Glamdring1> W: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/b/b43-fwcutter/b43-fwcutter_019-1_amd64.deb
[03:59] <Glamdring1>   404  Not Found [IP: 91.189.91.23 80]
[04:00] <Glamdring1> Correction. Two such errors.
[04:00] <anarkhein> Hmm.
[04:00] <anarkhein> Get it manually?
[04:00] <Glamdring1> S'pose I must, somehow.
[04:00] <Glamdring1> Same with aptitude, I imagine, just so I have the tool handy.
[04:01] <Glamdring1> How do you recommend going about it?
[04:02] <Glamdring1> Browser?
[04:02] <anarkhein> "Your 4306 hardware, according to http://wireless.kernel.org/en/users/Drivers/b43 takes the b43legacy driver, NOT the b43 driver."
[04:02] <anarkhein> Is this relevant in your case?
[04:03] <Glamdring1> I think I read that mine's 4311.
[04:03] <anarkhein> Ah, that's right.
[04:03] <Glamdring1> Which, I believe, uses the non-legacy driver.
[04:03] <Glamdring1> I could double-check, of course.
[04:03] <Glamdring1> Or proceed with faith and risk breaking something. I might be fine with that.
 	Subsystem: Hewlett-Packard Company BCM4311 802.11b/g Wireless LAN Controller [103c:1374]
[04:04] <Glamdring1> Ah, there we are, thanks.
[04:05] <Glamdring1> Interestingly, there's an archive.ubuntu.com/stuff/things/b/b43-fwcutter/ folder, but no /f/firmware-b43-installer/ folder.
[04:06] <anarkhein> https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx#b43_-_Internet_access
[04:06] <anarkhein> By the way, have you done "sudo apt-get update"?
[04:06] <Glamdring1> I believe so, but it's usually worth doing twice.
[04:07] <Glamdring1> When you do this, by the way, do you always get a lot of 404? I experience that a lot on my desktop machine.
[04:07] <anarkhein> http://packages.ubuntu.com/precise/kernel/firmware-b43-installer
[04:07] <Glamdring1> And, apparently, on this laptop.
[04:07] <anarkhein> But what else was needed...
[04:08] <anarkhein> cutter
[04:08] <anarkhein> http://packages.ubuntu.com/precise/b43-fwcutter
[04:08] <anarkhein> More?
[04:08] <Glamdring1> Which is apparently a dependency.
[04:08] <anarkhein> Right.
[04:09] <anarkhein> Download, locate it somewhere for the package manager to find it?
[04:12] <Glamdring1> Actually, I got ambitious and simply downloaded fwcutter manually and installed it first.
[04:12] <Glamdring1> They'
[04:12] <Glamdring1> They're now both installed. Shall I reboot and watch my poor laptop burn?
[04:12] <Glamdring1> Might bask in the glow of spontaneous laptop combustion. I should get marshmallows.
[04:13] <anarkhein> Yeah reboot.
[04:14] <Glamdring1> Will do.
[04:15] <Glamdring> Well, the wi-fi LED lights up. So far so good.
[04:15] <anarkhein> Ok...
[04:15] <anarkhein> It didn't use to?
[04:15] <Glamdring> Yeah, this is new.
[04:16] <anarkhein> Bin those marshmellows.
[04:17] <Glamdring1> Success.
[04:17] <Glamdring1> Thank you.
[04:17] <anarkhein> Allright.
[04:17] <Glamdring1> We were both blundering around a bit, but you were doing so from a position of experience and wisdom, and it seems to have  been what was needed here.
[04:18] <Glamdring1> I now no longer have to sit a meter from my front door in order to use this laptop.
[04:18] <anarkhein> Great. You pretty much did it yourself, given my improvisatory mode, I am not using (L)ubuntu on a day to day basis right.
[04:18] <Glamdring1> In fact, if the battery's any good, I can probably be anywhere in the apartment.
[04:18] <Glamdring1> Actually, you had a few specific thoughts and inputs I wouldn't have thought of.
[04:18] <anarkhein> I recall doing this myself a year and a half ago or so, but I didn't have this trouble.
[04:18] <Glamdring1> Heck, I didn't find that firmware installer at all.
[04:19] <Glamdring1> And I'd looked.
[04:19] <anarkhein> I think installing fwcutter and the firmware via the package manager just worked.
[04:19] <Glamdring1> Sheesh. Was it the same company?
[04:19] <Glamdring1> Trying to imagine how "fun" this would have been compiling from source.
[04:19] <anarkhein> Haha.
[04:20] <Glamdring1> There we are. Estimated battery life: 53 minutes. Eh. Not terrible.
[04:20] <anarkhein> I haven't compiled much so far. I fooled around with minimalist distros before. But I wanted to test compiling. That was a misguided approach, because it entailed a dependency-hell.
[04:21] <Glamdring1> Yep. I go through a degree of that every time I install Aleph One.
[04:21] <anarkhein> I think I've steered away from compiling due to that, even though it was entire my own doing.
[04:21] <anarkhein> Ok.
[04:21] <Glamdring1> Sometimes it's worth it, like in that case, but it always slows me down for a few months.
[04:21] <anarkhein> Do you happen to be familiar with Focaltech touchpads?
[04:22] <anarkhein> The newest laptop got that, but right-clicking doesn't work on Puppy Linux.
[04:22] <anarkhein> I've temporarily given up, in order not to cause a mess.
[04:22] <ianorlin> anarkhein: I have not heard of focaltech touchpads
[04:22] <anarkhein> It's new, and I think I read something about Focaltech "not supporting Linux at all" more or less.
[04:23] <anarkhein> But it's only right-clicking that doesn't work.
[04:24] <anarkhein> I came across some driver which is supposed to work, but I didn't see any references to tests on Puppy Linux, so I've postponed it for now.
[04:24] <anarkhein> Glamdring, So to sum up, what was your main problem? Unreliable package manager/repository URL?
[04:25] <Glamdring1> Seems like it, yeah.
[04:25] <anarkhein> Ok.
[04:25] <Glamdring1> Well, actually, it also seems like, by default, lubuntu simply didn't come packaged with a relevant set of firmware.
[04:26] <anarkhein> Yeah.
[04:27] <ianorlin> for what braodcom?
[04:27] <Glamdring> Yeah.
[04:27] <ianorlin> ugh
[04:28] <ianorlin> that was annoying to figure out at first
[04:28] <Glamdring> Seems like it was a lot of manually looking things up to get lubuntu working with a Broadcom card.
[04:28] <Glamdring> Wroooong window.
[04:28] <ianorlin> which braodcom one ?
[04:28] <Glamdring> 4311
[04:29] <Glamdring> Apparently a known problem as recently as 15.04
[04:30] <Glamdring> Okay, so here's a much more general question. Let's say I've got everything working real nice in 14.10, but past upgrades have occasionally broken things of which I'm fond, so I'm leery of upgrading to 15.10. Is there a reasonable way to try to upgrade, then roll it back if it goes awry?
[04:31] <ianorlin> Glamdring: on the upgrade I don't think so but a disk image might be the best way to do that
[04:31] <anarkhein> I, for one, am gonna downgrade my state to sleepmode. See you around.
[04:31] <Glamdring> Ouch. That sounds like a good but mildly impractical idea for me.
[04:31] <ianorlin> but that basically reuqires another drive
[04:31] <Glamdring> Okies. Thanks, anarkhein.
[04:31] <Glamdring> Yep.
[04:31] <anarkhein> Haha. Bye.
[04:32] <Glamdring> I can think of worse ideas; goodness knows I could afford to back her up.
[04:32] <Glamdring> Expense and budget, however, are the dire foes of backups.
[04:32] <Glamdring> I'd pretty much need a good half-terabyte available just for that purpose.
[04:33] <Glamdring> And yet, given how well certain things work right now (Weland, Aleph One, my AMD drivers, my bleeping sound card), this is a state of affairs from which I fear to deviate, and to which I'd love to return.
[04:35] <Glamdring> So let's say right now it spans about 500 gigabytes of data. If I want an image of that, is there a way to span it across DVDs? If so, how much are we talking?
[04:35] <Glamdring> Suddenly a tape drive sounds very attractive.
[04:36]  * Glamdring looks up tape drive costs, has a moment of total sticker shock.
[05:55] <intx> anyone have vnc or rdp auto-starting for remote assistance?
[07:32] <intx> vino won't run
[19:10] <`Red> Hi. I was here yesterday. My Macpro G5 dual, is displaying a black screen after trying to install debian, mintppc, and now lubuntu. I need help possibly to recognize display, and graphics driver. Please help.
[19:15] <bioterror> maybe Radeon something
[19:17] <`Red> I have a rradeon 9600 xt
[19:24] <`Red> Can someone please assist me.
[19:26] <bioterror> https://help.ubuntu.com/community/RadeonDriver
[19:26] <bioterror> have you read that?
[19:26] <bioterror> your card is R300
[19:30] <`Red> any time i type any commands, such as sudo apt-get or other commands, it says invalid file not found, or another message not recognizing what I type. I was able to get into a "shell" from typing in "rescue". The shell also does not recognize any of the commands I've been told to type.
[19:30] <bioterror> okay
[19:31] <`Red> I am at the screen that says "boot:"
[19:35] <`Red> "Unable to open file, invalid device"
[19:36] <bioterror> and you have burned a CD-R?
[19:36] <`Red> yes, and installed it successfully. Just can't get into the operating system.
[19:37] <bioterror> sounds like the probably grub cant find the right device
[19:37] <`Red> I only have 700MB CDR's
[19:38] <`Red> I haven't tried a DVI monitor because I dont have one. I'm using Apple Cinema display, which has it's own unique connector
[19:38] <bioterror> it has nothing to do with that
[19:38] <`Red> Okay
[19:38] <bioterror> problem is that the loader cant find your partition
[19:39] <`Red> I installed it to my 80GB HD. I directed it to use the entire disk when installing.
[19:39] <`Red> I also have a 120GB HD with mac os x 10.5.8. I would like to keep OS X though. So I didn't install on the 12-GB
[19:39] <`Red> 120GB*
[19:40] <`Red> Also, the G5's fans are running at high speed, most of the time. Very loud. But I can live with that.
[19:41] <bioterror> I have to say that I have not run GNU/Linux systems on new world macs
[19:41] <bioterror> only on old world
[19:42] <bioterror> and it looks like a little confusing :D
[19:42] <`Red> The supprt for G5 is such as G3, and G4 according to the websites
[19:43] <bioterror> that 80GB drive is a regular SATA drive and not USB?
[19:43] <`Red> A lot of the results on google, people are experiencing the black screen on bootup, who are also using similar system to mine. Thing is, to resolve it, there are lots of commands and variables to be changed. And while reading it, it is fairly complex stuff to understand for a newbie
[19:43] <`Red> yes i believe so
[19:45] <`Red> I would try yellow dog linux, however, development for the OS has stopped several years ago.
[19:46] <bioterror> yes, for the G5
[19:46] <`Red> At boot up, there are options to type: such as.. install, install-free-powerpc64, install-powerpc64 etc. I don't want to spend 1 and half hours to try each and every one of the options.
[19:46] <bioterror> I would myself think something like MorphOS
[19:47] <`Red> The G5 is a 64bit processor
[19:48] <`Red> Ok, since the iso is 200mb for morph, i will try it
[19:48] <`Red> will it recognize my wireless usb adapater, and is it easy to use
[19:50] <bioterror> hard to say
[19:50] <`Red> It will have web browers, and offer to install open offiece suites?
[19:53] <`Red> It says its unsuported for PowerPC atm
[19:54] <bioterror> but I cannot help you with the PowerPC problems, becouse last time I owned Dual G4 was 2009 and I have never looked back into that time
[19:54] <bioterror> and those are probably something like yaboot /openfirmware related problems
[19:54] <`Red> Also says morph os will use only 1gb of ram, not the 4gb i have installed
[19:54] <`Red> ok
[19:59] <`Red> can anyone help me. Black Screen on boot up, it has happened on mintppc, debian, and now also lubuntu. I have a radeon 9600 xt, dual g5 powerpc.
[19:59] <wxl> hm
[19:59] <wxl> !ppv
[19:59] <wxl> oops
[19:59] <wxl> !ppc
[19:59] <wxl> read that faq if you haven't already `Red
[19:59] <wxl> most problems are answered there
[20:00] <wxl> we also have many ppc users on the mailing list, so i would post a message there
[20:00] <wxl> in general i have found graphics to be the biggest issue with ppc. they almost never work out of the box
[20:01] <wxl> basically distros have had to make compromises for older hardware when it comes to supporting newer hardware
[20:01] <wxl> e.g. not a good idea to make the graphics downgraded for everyone just to suport a few people using old hardware
[20:02] <wxl> similarly google chrome recently announced they'll be dropping support for 32-bit linux!
[20:02] <`Red> I don't want to spend time trying to find a resolution by reading the FAQ quite yet. I will try to find another distro that might work.
[20:02] <wxl> `Red: your only hope with that is a distro that is meant to work out of the box. i would expect mintppc to be that. if it fails, you probably have little hope
[20:03] <wxl> `Red: even netbsd which is meant to run on practically everything has a very long extensive installation guide for ppc
[20:03] <bioterror> NetBSD mentioned :D
[20:03] <wxl> `Red: the other thing to consider is that ppc machines are very different, down to some of them acting entirely different in their boot firmware
[20:04] <wxl> `Red: so a *detailed* post to the mailing list is probably the one option that will expedite things for you
[20:05] <wxl> note the emphasis on detailed
[20:05] <wxl> get very specific information on the processor you use and the pci ids on the graphics
[20:05] <wxl> figure out what openfirmware version you're using
[20:05] <`Red> Ok, can you link me to this place?
[20:10] <wxl> `Red: you can join the mailing list by sending any sort of email to lubuntu-users-join@lists.ubuntu.com
[20:10] <wxl> `Red: then send your actual message to lubuntu-users@lists.ubuntu.com
[20:11] <`Red> Can the body of the email include all the details of my problem, along with specifications of the G5
[20:11] <`Red> ok
[20:11] <wxl> `Red: if you don't join first it's likely you won't receive youre replies if someone replies to just the list which is quite possible
[20:11] <wxl> `Red: the first message (to join) should be blank. the second one can be as detailed as you like
[20:12] <wxl> `Red: just don't send images. i don't remember what the limit on messages was but it's fairly restrictive for anything that's not text
[20:12] <`Red> Ok, do i have to wait to be accepted to the group, or can I start an email after the blank one?
[20:13] <wxl> `Red: you'll be automatically added to the list and you'll get a message confirming this when you are. after that, you're free to send a message
[20:13] <wxl> `Red: just don't forget it's lubuntu-users-join to join but send messages to lubuntu-users
[20:14] <`Red> Ok. Maybe I should try MorphOS first?
[20:15] <wxl> `Red: ubuntu is participating in google code-in this year and i have tasks to create by the end of the day so i'm going to head out
[20:15] <`Red> ok seeyo
[20:15] <wxl> `Red: i have no familiarity with morphos, but everything's worth a shot. if it doesn't "just work" you'll have more support from the ubuntu community, especially within lubuntu
[20:16] <`Red> ok thanks for your help.
[20:32] <`Red> im trying to install gentoo
[21:58] <Lokie> I have configured xfce power manager and light-locker. Regardless screen won't switch off but stay black (active but black / blank) also suspend doesn't kick in
[21:58] <Lokie> any ideas?
[22:04] <eperzhand> Hello, guys! Please, help me - I'm completely stucked how to startup gnome-keyring-daemon in Lubuntu correctly...
[22:04] <eperzhand> I've added lines to /etc/pam.d/login and passwd - but no luck
[22:05] <anarkhos> Lokie, I recall having similar problems, I think I never fixed it.
[22:06] <eperzhand> : /
[22:06] <anarkhos> eperzhand, Version?
[22:07] <Lokie> that's great to here anarkhos :/
[22:08] <Lokie> did you switch to another distro or just "live with it" ?
[22:09] <anarkhos> Haha. It's maybe one and half a year ago, however, Lokie, so there should be more possibilities now.
[22:10] <anarkhos> I'm all over the Linux place. I'm a little familiar with various distros, but not an expert on any one particular.
[22:10] <anarkhos> Lokie, You too, what version?
[22:11] <anarkhos> eperzhand, I wonder whether what I just came across could be useful to you...
[22:12] <anarkhos> eperzhand, http://denilson.sa.nom.br/blog/2015-05-14/gnome-keyring-on-lubuntu-15-04/
[22:12] <eperzhand> anarkhos: thank you!
[22:12] <eperzhand> I've readed it already
[22:12] <eperzhand> but he tries to turn off keyring
[22:13] <anarkhos> Yes, but there are some details, I thought perhaps he mentioned initiating it as well.
[22:16] <eperzhand> The problem is that they are changing initiating process from version to version
[22:16] <anarkhos> Ok.
[22:26] <anarkhos> eperzhand, "<eperzhand> I've added lines to /etc/pam.d/login and passwd" - You tried to automate the process?
[22:26] <anarkhos> How about trying manually first?
[22:29] <Lokie> anarkhos ubuntu 15.10 with lubuntu-desktop
[22:30] <anarkhos> http://unix.stackexchange.com/questions/32646/how-to-start-the-keyring-daemon-after-a-gnome-shell-crash
[22:30] <anarkhos> This is in the context of Linux Mint, but...
[22:30] <anarkhos> Not sure how much difference there is.
[22:33] <anarkhos> eperzhand, Exactly what did you add to /etc/pam.d/login?
[22:35] <anarkhos> Lokie, "http://askubuntu.com/questions/tagged/suspend"
[22:35] <anarkhos> sorry
[22:35] <anarkhos> http://askubuntu.com/questions/tagged/suspend
[22:35] <anarkhos> "Computer does not suspend until network cable is disconnected"?
[22:38] <anarkhos> Lokie, "[SOLVED] I figured it out     What I didn't know was that xfce4-power-manager is a dialog menu. So I opened it's dialog menu and enabled all the necessary options and it was everything I was looking and it works." --- I assume this is to simple an explanation in your case
[22:39] <anarkhos> From http://forum.lxde.org/viewtopic.php?f=5&t=36125
[22:42] <anarkhos> Lokie, " Regardless screen won't switch off but stay black (active but black / blank)" - Exactly what did you click?
[22:46] <anarkhos> "This morning I installed Nvidia drivers and didn't like the look. Purged all Nvidia stuff. Did a reinstall libgl1-mesa-dri libdrm2 libdrm-nouveau2 xserver-xorg-core       Rebooted and now nouveau is back and things look fine. I am using a screen saver that isn't a blank screen. So far no blank screen lock up."   http://www.linux.org/threads/screen-goes-black-but-computer-not-off.6190/
[22:56] <eperzhand> anarkhos: midori behaves very strangely
[22:56] <eperzhand> it depends on gnome-keyring
[22:57] <eperzhand> but the idea is nice
[22:58] <eperzhand> first try to play with it manually to completely see the problem
[22:59] <eperzhand> thank you, anarkhos - i'll check it
[22:59] <eperzhand> where are you from?
[23:00] <anarkhos> Norway. What did you put in the pam.d file?
[23:00] <eperzhand> # session optional pam_gnome_keyring.so auto_start
[23:01] <eperzhand> but I'm commenting them out
[23:01] <eperzhand> looks like the XDG has some standard way to autostart apps through etc/xdg/autostart dis
[23:02] <eperzhand> X D G
[23:07] <eperzhand> the worst part of IRC is that the history is lost
[23:09] <anarkhos> What is the result of your current approach, eperzhand? Any messages? Also, what are you expecting?
[23:10] <eperzhand> The problem is that midori depends on gnome-keyring
[23:11] <eperzhand> if you try to open self-signed site it gives you Error granting trust: Couldn't find a place to store the pinned certificate
[23:11] <eperzhand> pkcs11:library-description=PKCS%2311%20Kit%20Trust%20Module
[23:11] <eperzhand> I've found the fix in Midori FAQ - but it doesn't work in Lubuntu
[23:14] <anarkhos> Hm, ok.
[23:15] <eperzhand> it looks like that there are lot of users suffers from the same
[23:15] <eperzhand> but they just moved to another browsers or distros
[23:16] <eperzhand> anarkhos, are you a programmer?
[23:20] <eperzhand> may you send me the link to similiar Linx Mint problem?
[23:20] <eperzhand> I've rebooted during changing config files, so lost the history
[23:28] <Lokie> anarkhos thx, will check the links in a sec
[23:29] <Lokie> it's not that it suspends and wakes up
[23:30] <Lokie> it doesn't suspend at all
[23:30] <anarkhos> eperzhand, No, although I'm moderately familiar with BASIC.
[23:30] <Lokie> also I have configured xfce
[23:30] <eperzhand> anarkhos, please wait a second - i need to reboot again
[23:44] <Guest2> 14.04.3 I think lubuntu updates make it use more and more disk space. I is now use 7.2GB of 8GB. What id the disk is be full and i can not run more updates ?
[23:59] <anarkhos> Guest2, Yeah, better think about this issue when partitioning.
[23:59] <anarkhos> Guest2, Also, maybe you could manually delete something.