**** BEGIN LOGGING AT Mon Jun 11 03:00:03 2018
Jun 11 06:23:39 <brolin_empey> Do non-AMD chipsets still exist for current AMD x86 platforms?  Or is it like Intel x86 platforms, where there are no longer any non-Intel chipsets: apparently the Pentium 4 era was the last era with non-Intel chipsets.
Jun 11 06:42:06 <brolin_empey> I see only Intel and AMD chipsets listed on https://www.msi.com/Motherboards/ .  Apparently the Asus Web site does not allow filtering by chipset.
Jun 11 06:44:55 <brolin_empey> No, apparently the Asus Web site does allow filtering by chipset but it also lists only Intel and AMD chipsets.
Jun 11 06:51:47 <brolin_empey> Same for https://www.gigabyte.com/Motherboard .
Jun 11 07:35:27 <Maxdamantus> I suspect "chipset" practically means "class of CPUs" nowadays.
Jun 11 07:36:19 <Maxdamantus> (I don't know anything about whether AMD requires their own hardware on motherboards, but I imagine even if they didn't, people would still use the term "chipset" to denote the set of CPUs that will work on the board)
Jun 11 07:37:56 <Maxdamantus> Looking at the dates on the Wikipedia page for "List of AMD chipsets", I suspect they don't.
Jun 11 07:38:55 <bencoh> Maxdamantus: "chipset" actually refers to the specialized/helper chips on the motherboard, not the set of working CPUs
Jun 11 07:40:11 <bencoh> (and chip vendors eventually started merging their set of chips in a single helper chip)
Jun 11 07:44:08 <Maxdamantus> bencoh: yes, I know.
Jun 11 07:44:28 <Wizzup> there are some chinese companies taking amd zen and producing their 'own' CPUs with it
Jun 11 07:44:35 <Maxdamantus> bencoh: but I imagine even if they didn't have them (which seems to be the case for AMD), people would still use the term "chipset".
Jun 11 07:44:44 <bencoh> ah
Jun 11 07:45:52 <Maxdamantus> “This is an overview of chipsets sold under the brand AMD, manufactured before May 2004 by the company itself, before the adoption of open platform approach”
Jun 11 07:46:29 <Maxdamantus> So I guess since the "open platform approach", it's just been up to motherboard producers to implement whatever's necessary.
Jun 11 07:46:43 <Maxdamantus> (again, just a guess, don't know anything about AMD from actual experience)
Jun 11 08:26:09 <sixwheeledbeast^> Last non-AMD chipset I can remember would be AM2+ era (Athlon64), not long after ATI became part of AMD. I recall after that the only boards non-AMD chipset being GeForce. So imagine AM3 boards would be the last non-AMD chipset, I only recall 900 Series chipset from there.
Jun 11 10:23:00 <jonwil> Does anyone know of a mirror of the Nokia QT repository that used to be at https://gitorious.org/+qt-developers/qt/x11-maemo ? I dont mean https://github.com/community-ssu/qt-x11-maemo which is the Community SSU repository, I mean the nokia repository as it was at the time Nokia stopped making commits to it.
Jun 11 10:26:21 <Maxdamantus> Based on https://wiki.maemo.org/Qt_Maemo_Git_Process , maybe this one? https://gitorious.org/qt/x11-maemo
Jun 11 10:27:05 <Maxdamantus> The top of the log looks like nokia.
Jun 11 10:29:36 <Maxdamantus> (hint: add ".git" to the end of the URL to get a remote that you can actually clone through `git`)
Jun 11 10:31:05 <jonwil> Its not cloning
Jun 11 10:31:12 <jonwil> Now it is :)
Jun 11 10:31:13 <Maxdamantus> It seems slow.
Jun 11 10:31:17 <jonwil> I still want https://gitorious.org/+qt-developers/qt/x11-maemo though
Jun 11 10:31:27 <jonwil> since both are different repos with different contents
Jun 11 10:31:31 <Maxdamantus> afaict that was a community project.
Jun 11 10:31:47 <Maxdamantus> (according to the wiki page I linked)
Jun 11 10:32:19 <jonwil> What I am trying to figure out is the relationship between https://gitorious.org/+qt-developers/qt/x11-maemo, http://qt.gitorious.org/qt/x11-maemo and https://github.com/community-ssu/qt-x11-maemo
Jun 11 10:32:44 <jonwil> i.e. exactly what source code was first used to build https://github.com/community-ssu/qt-x11-maemo
Jun 11 10:33:56 <Maxdamantus> Actually, it's the same repo.
Jun 11 10:34:05 <Maxdamantus> well, the same head commit, at least.
Jun 11 10:34:10 <jonwil> which ones?
Jun 11 10:34:10 <Maxdamantus> https://web.archive.org/web/20110909004922/https://gitorious.org/+qt-developers/qt/x11-maemo
Jun 11 10:34:20 <Maxdamantus> last push is 1f7db84
Jun 11 10:34:32 <Maxdamantus> which is the head of the repo I first linked.
Jun 11 10:35:31 <Maxdamantus> guess the reason it's slow is just because the repository is so big.
Jun 11 10:35:36 <Maxdamantus> Receiving objects:  43% (230155/534275), 157.12 MiB | 744.00 KiB/s   
Jun 11 10:35:46 <jonwil> Yeah
Jun 11 10:36:28 <Maxdamantus> but you can they're the same by looking at the commit ids through the gitweb UI and through the wayback view of gitorious.
Jun 11 10:39:39 <jonwil> My guess is that https://gitorious.org/+qt-developers and http://qt.gitorious.org were aliases of each other
Jun 11 10:40:15 <jonwil> If you look at the wayback view of http://qt.gitorious.org/qt/x11-maemo you can see that its owned by +qt-developers
Jun 11 10:41:11 <jonwil> Aha, now 
Jun 11 10:41:13 <jonwil> now I see
Jun 11 10:41:35 <jonwil> http://gitorious.org/+qt-maemo-developers/qt/qt-maemo is a totally different repo than http://qt.gitorious.org/qt/x11-maemo aka https://gitorious.org/+qt-developers/qt/x11-maemo
Jun 11 10:42:53 * Maxdamantus hopes someday to use software on his phone that is not a fork of a fork of some mainstream software.
Jun 11 10:43:25 <jonwil> And https://github.com/community-ssu/qt-x11-maemo formerly https://gitorious.org/community-ssu/qt-x11-maemo is clearly a fork of https://gitorious.org/+qt-developers/qt/x11-maemo
Jun 11 10:48:13 <jonwil> so now I have yet another QT tree on my disk :)
Jun 11 10:49:19 <Maxdamantus> You can probably save disk space by just keeping them all in the same local repository.
Jun 11 10:52:21 <Maxdamantus> in one of the repositories, just add the other repositories as alternatives, then add all the remotes as used by the other repositories, and fetch.
Jun 11 10:52:41 <Maxdamantus> then `git repack -a -d`, and remove the alternates file.
Jun 11 10:53:20 <Maxdamantus> (won't need to download anything significant since you should already have the relevant objects accessible through alternates)
Jun 11 10:54:04 <jonwil> Total on-disk size of all 4 QT related repos I can find off the top of my head is only 2.69GB which isn't a problem
Jun 11 10:55:54 <jonwil> I have the Nokia QT repository, the CSSU repo that was forked from it, the upstream QT 4.x source repository and then the Debian QT 4.x repository (which is just the debian local packaging/patches stuff on top of the Nokia repo)
Jun 11 10:56:08 <jonwil> I mean the upstream QT repo
Jun 11 10:56:23 <jonwil> or rather its a fork on top of an upstream QT tarball :)
Jun 11 11:30:11 <Wizzup> Maxdamantus: you're welcome to help out @ not a fork of a fork :p
Jun 11 11:32:34 <Maxdamantus> Wizzup: yeah, if I can get around to doing stuff, it would basically just be making separate non-maemo software that is useful for my N900.
Jun 11 11:32:55 <Maxdamantus> (so I can just run those programs on debian or something)
Jun 11 11:34:39 <sixwheeledbeast^> https://gitorious.org/qt/niqts-qt-maemo-developers-x11-maemo.git/   ?
Jun 11 11:37:01 <jonwil> I got what I want now
Jun 11 11:37:04 <jonwil> So its all good
Jun 11 11:37:29 <Maxdamantus> That last repository linked is a subset of https://gitorious.org/qt/x11-maemo
Jun 11 11:37:55 <jonwil> https://gitorious.org/qt/x11-maemo is the same code that used to be at both http://qt.gitorious.org/qt/x11-maemo and http://qt.gitorious.org/qt/x11-maemo
Jun 11 13:33:41 <DocScrutinizer05> famous findings that should have been archived on a wiki page but never were
Jun 11 13:34:18 <DocScrutinizer05> ~qt
Jun 11 13:34:18 <infobot> it has been said that qt is TrollTech's QT library, available at http://www.trolltech.com
Jun 11 13:34:38 <DocScrutinizer05> ~#maemo qt is  https://gitorious.org/qt/x11-maemo is the same code that used to be at both http://qt.gitorious.org/qt/x11-maemo and http://qt.gitorious.org/qt/x11-maemo
Jun 11 13:34:38 <infobot> okay, DocScrutinizer05
Jun 11 13:34:47 <DocScrutinizer05> ~qt
Jun 11 13:34:47 <infobot> it has been said that qt is https://gitorious.org/qt/x11-maemo is the same code that used to be at both http://qt.gitorious.org/qt/x11-maemo and http://qt.gitorious.org/qt/x11-maemo
Jun 11 13:36:39 <DocScrutinizer05> ~literal x11
Jun 11 13:36:40 <infobot> "#maemo x11" is "Install xauth on N900 (apt-get install xauth). Run from your PC 'ssh -X user@Nokia-N900', and N900's X will be forwarded to your PC"
Jun 11 13:37:58 <DocScrutinizer05> ~#maemo x11 is also see ~qt
Jun 11 13:37:58 <infobot> okay, DocScrutinizer05
Jun 11 13:38:05 <DocScrutinizer05> ~x11
Jun 11 13:38:05 <infobot> [x11] Install xauth on N900 (apt-get install xauth). Run from your PC 'ssh -X user@Nokia-N900', and N900's X will be forwarded to your PC, or see ~qt
Jun 11 13:39:15 <DocScrutinizer05> ~listvalues x11-maemo
Jun 11 13:39:54 <DocScrutinizer05> WUT??
Jun 11 13:40:03 <DocScrutinizer05> ~+listvalues x11-maemo
Jun 11 13:40:08 <infobot> exceeded allowed forked count (shm 0): RSSFeeds, Debian
Jun 11 13:40:30 <DocScrutinizer05> wtf?!
Jun 11 13:40:39 <DocScrutinizer05> ~+listvalues x11
Jun 11 13:40:44 <infobot> exceeded allowed forked count (shm 0): RSSFeeds, Debian
Jun 11 13:40:53 <DocScrutinizer05> ~+listvalues poettering
Jun 11 13:40:59 <infobot> exceeded allowed forked count (shm 0): RSSFeeds, Debian
Jun 11 13:41:02 <KotCzarny> you've just dos'ed the poor bot
Jun 11 13:41:08 <KotCzarny> out of mem or shm space
Jun 11 13:41:08 <DocScrutinizer05> ~die
Jun 11 13:42:12 <DocScrutinizer05> ~+listvalues x11-maemo
Jun 11 13:42:17 <infobot> Factoid search of 'x11-maemo' by value (1): #maemo qt.
Jun 11 13:42:25 <DocScrutinizer05> o.O
Jun 11 13:46:06 <DocScrutinizer05> ~+status
Jun 11 13:46:06 <infobot> Since Mon Jun 11 13:41:20 2018, there have been 0 modifications, 0 questions, 0 dunnos, 0 morons and 1 command.  I have been awake for 4m 46s this session, and currently reference 119759 factoids.  I'm using about 82296 kB of memory. With 0 active forks. Process time user/system 1.16/0.14 child 0/0
Jun 11 13:46:22 <DocScrutinizer05> wish I've thought of that before killing it
Jun 11 13:47:19 <DocScrutinizer05> wonder what ": RSSFeeds, Debian" means
Jun 11 13:47:38 <KotCzarny> might be someone else started some task
Jun 11 13:48:33 <DocScrutinizer05> ~+help rssfeeds
Jun 11 13:48:33 <infobot>    Desc: rssfeeds is used to control the RSS Feed tracking module
Jun 11 13:48:34 <infobot>   Usage: rssfeeds [command]
Jun 11 13:48:34 <infobot> Example: rssfeeds flush
Jun 11 13:48:35 <infobot>    Desc: flush - Will erase the cache file. (Must be chattr +o)
Jun 11 13:48:35 <infobot>    Desc: update - Force a manual update of the feeds. (Must be chattr +o)
Jun 11 13:48:56 <DocScrutinizer05> never wrapped my head around that
Jun 11 13:50:06 <DocScrutinizer05> prolly an unmaintained command that somebody ran nevertheless for debian?
Jun 11 13:53:05 <DocScrutinizer05> nfc, rssfeeds is not making sense to me
Jun 11 13:53:43 <DocScrutinizer05> there must be more commands related to this
Jun 11 13:54:54 <DocScrutinizer05> can't spot anythinh meaningful that might be related, in ~help. No "feed" or whatever command
Jun 11 13:56:19 <DocScrutinizer05> news?
Jun 11 13:56:29 <DocScrutinizer05> ~+help news
Jun 11 13:56:29 <infobot>    Desc: News functions
Jun 11 13:56:29 <infobot>   Usage: news [chan] <add,del,mod,set,latest,read,help>
Jun 11 13:56:41 <DocScrutinizer05> ~+help newsadd
Jun 11 13:56:43 <infobot> no help on newsadd.  Use 'help' without arguments.
Jun 11 13:56:58 <DocScrutinizer05> ~+help news add
Jun 11 13:56:59 <infobot>    Desc: Add news items
Jun 11 13:56:59 <infobot>   Usage: news [chan] add <title>
Jun 11 13:57:00 <infobot> Example: news add This is a test
Jun 11 13:57:00 <infobot> see _news set Text_ aswell
Jun 11 13:57:29 <DocScrutinizer05> ~news
Jun 11 14:02:51 <DocScrutinizer05> the bot is bitrotting :-S
Jun 11 14:03:07 <DocScrutinizer05> ~+status
Jun 11 14:03:07 <infobot> Since Mon Jun 11 13:41:20 2018, there have been 0 modifications, 0 questions, 0 dunnos, 0 morons and 16 commands.  I have been awake for 21m 47s this session, and currently reference 119759 factoids.  I'm using about 82428 kB of memory. With 0 active forks. Process time user/system 2.62/0.43 child 0/0
Jun 11 14:06:22 <DocScrutinizer05> ~+uptime
Jun 11 14:06:23 <infobot> - Uptime for purl -
Jun 11 14:06:23 <infobot> Now: 25m 3s running infobot 1.5.4 (SVN) -- linux
Jun 11 14:06:23 <infobot> 1: 59d 8h 41m 19s running infobot 1.5.4 (SVN) -- linux, ended Sun Nov 14 18:39:57 2010
Jun 11 14:06:23 <infobot> 2: 57d 3h 9m 23s running infobot 1.5.4 (SVN) -- linux, ended Fri Jun 26 20:39:27 2009
Jun 11 14:06:24 <infobot> 3: 53d 8h 24m 4s running infobot 1.5.4 (SVN) -- linux, ended Tue Nov  7 05:34:20 2017
Jun 11 14:19:35 <brolin_empey> sixwheeledbeast^: Yes, at work we have an AM2 motherboard from 2006 with a non-AMD (nVidia nForce) chipset but I noticed that non-AMD chipsets for AMD x86 platforms seem to have disappeared.
Jun 11 14:25:14 <sixwheeledbeast^> brolin_empey: Nvidia have concentrated on GFX, ATI are part of AMD. also there is only the Southbridge chipset required on later stuff compared to older boards with a "northbridge".
Jun 11 15:07:56 <enyc> sixwheeledbeast^: what about VIA, SiS, Ali ?
Jun 11 15:10:00 <KotCzarny> all subpar performance, to say at least
Jun 11 15:11:07 <enyc> I remember the Pentium-II with silly chipset
Jun 11 15:11:25 <enyc> 'weird ISA timing issues on some cards, too
Jun 11 15:11:26 <enyc> etc
Jun 11 15:11:36 <sixwheeledbeast^> All older chipsets than above?
Jun 11 15:12:46 <enyc> no idea
Jun 11 15:14:13 <sixwheeledbeast^> I recall a SiS chipset on my first board Socket A
Jun 11 15:20:23 <enyc> i had loats of weird failures orf sockt-A athlons
Jun 11 15:20:31 <enyc> 'capactiros on board, chips fail, .....
Jun 11 15:20:40 <enyc> amd64's seem to have been more robust.
Jun 11 15:25:02 <sixwheeledbeast^> umm? 
Jun 11 15:27:43 <enyc> err as above?
Jun 11 15:27:44 <enyc> anyway
Jun 11 15:45:33 <sixwheeledbeast^> I never had any issues with any AMD stuff. I always understood Socket A and Athlon where solid. Most chip deaths where related to damaging the CPU on heatsink mounting
Jun 11 15:46:57 <sixwheeledbeast^> Latter CPU's "amd64" had lids on covering the die etc and therefore less likely to damage from heatsink mounting.
Jun 11 15:47:41 <sixwheeledbeast^> caps would be down to board manufacturer I suppose.
**** ENDING LOGGING AT Tue Jun 12 03:00:04 2018