Re: Why does Anaconda overrides user decisions?
On Wednesday, January 28, 2015 11:20:34 AM Matthew Miller wrote: It also covers more cases more simply than any other storage manager you've seen. You really can't have everything, here. How do you accomplish more by moving all items in a branched UI? If the some of the tasks are not imperative to complete the installation then it makes sense to hide them in separate branches but if the installation can't complete without actually going through each of the tasks then all branched UI does is to add more clicks to the process. -- Regards, Sudhir Khanger, sudhirkhanger.com, github.com/donniezazen, 5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394. signature.asc Description: This is a digitally signed message part. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: End of 32-bit support?
On 29.01.2015 14:52, Paul W. Frields wrote: On Wed, Jan 28, 2015 at 06:00:28PM +0100, poma wrote: On 28.01.2015 17:17, Matthew Miller wrote: On Sat, Jan 24, 2015 at 08:37:59AM +0100, Ralf Corsepius wrote: Hatters, or from Red Hatters working in their spare time. (Of course, as RH often does, many of the high-output contributors end up applying for and getting RH jobs, skewing the picture.) Well, I am observing quite a few people from major enterprises (RH business partners?) who are working on secondary archtectures, but I've very rarely (I don't recall any such incident) tripped over community folks who are working on them. Sometimes Red Hat business partners, but that doesn't mean that it's at Red Hat's direction. Overall, this is one of the few areas where we have money and paid effort flowing into the project that *isn't* coming from Red Hat, and I don't think that's a bad thing. These are community folks too, at least if we're doing it right. Additionally, I'm not privy to Red Hat's architecture strategy, but as far as I know, 32 bit ARM — currently our only primary non-x86 arch! — is not of particular corporate interest. It's obvious to me the aarch64 is RH's business interest. But aarch64 and 32-bit arm are _completely_ different architectures. I also think it's a little unfair to frame this as a conflict, overall. It may be the case that Red Hat is less interested in paying people to work on 32-bit x86 (although I don't actually know that to be a fact). But this is just like any other contributor to the community — you can't make people do work they're not interested in. Right, but that's not my point: My points are: - I once more feel pushed/tossed around by RH's interest and RH-Fedora-people who obviously don't properly separate RH and Community. I can't argue with feelings, but I also am not really sure what separation you're looking for here and how it would affect this. - Support for i386 falls out as a by-product at almost Zero-costs of the existing process. I don't think that's true at all. It signficantly increases QA load, and we're struggling a lot with release engineering being able to cope with Fedora at its current scale. Cutting back here has an clear benefit (whether or not it's significant enough to outweigh the other wide isn't settled, of course). More significantly, the Fedora kernel team tells me that _they_ don't feel like they have the resources to really honestly support the 32-bit kernel — and the rest all falls out from that. You write as if you - Fedora/Red Hat lack people capable of maintaining the kernel as if it were something special - they are not kernel developers. What Josh works except to maintains the kernel? I can't parse this last sentence correctly. Are you asking what Josh does other than maintain the kernel? Or are you asking something else? Ecco una traduzione in inglese di aver compreso: Fedora kernel position [Jan. 27th, 2015|10:22 am] As you might have seen Paul blog about, Red Hat has an immediate opening for a Fedora kernel maintainer position on my team. This is actually a fairly rare thing, as we don't have a lot of churn in our department and most of the engineering positions we hire for are primarily RHEL roles. If you have kernel experience and love working on fast-paced and frequently updated kernels, then this might be a good role for you. The job writeup is accurate in terms of what we expect, but it is also kind of broad. That is primarily because the role is too. Yesterday davej wrote a bit about how working on a Fedora kernel is like getting a 10,000ft view of everything. It's actually a really good analogy, and Dave would know as he did it longer than anyone. We deal with a lot of varied issues, on an even more varied set of hardware. This isn't a traditional development job. Being curious and willing to learn is key to enjoying a distro kernel maintainer role. That being said, we're also looking at ways to make a bigger impact both upstream and in Fedora itself. Filling this position is a key part of that and I'm excited to see how it plays out. If you're interested in it, please don't hesitate to send me questions via email or on IRC. Also be sure to apply via the online job posting here: http://jobs.redhat.com/jobs/descriptions/fedora-kernel-engineer-westford-massachusetts-job-1-5076703 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: What is Ghost i.e security hole in the Linux?
On 29 January 2015 at 02:17, Tim ignored_mail...@yahoo.com.au wrote: Allegedly, on or about 28 January 2015, Doug sent: ... A remote attacker able to call either of these functions could exploit the flaw to execute arbitrary code with the permissions of the user running the application All these security flaws come with the usual flaw allows escalation of privileges, able to execute arbitrary commands... red flags, but rarely give an understandable note about how easily an external hack can begin the attempt while the user is doing something ordinary that exposes them to the thing. i.e. It's all jargon aimed at programmers. In the dim and distant past, when I had a brief dalliance with Windows before Linux became realistically usable, you'd commonly get warnings about flaws which gave understandable information. e.g. Opening a malicious attachment, or even just reading a malicious email, with version of particular program less than x.y, allows the hacker to do destructive things to your system. I know I've vagued-up the example, but you've got a sample of something that you might actually do - simply read an email, not even do anything with the attachments, get a virus because your email program stupidly executes something embedded in it. That's probably less of a risk to Linux users, because we've never had stupid software like Outlook or Outlook express. But we've certainly got browsers with flash plug-ins installed, which (flash) has always been a security nightmare, and it's just not feasible to simply forbid it; so many websites that we regularly want to use would simply fail to work. This is to do with the nature of the exploit. You are /potentially/ vulnerable if you access the internet. As https://www.qualys.com/research/security-advisories/GHOST-CVE-2015-0235.txt notes, this is a vulnerability which programs may not run into at all depending how they use the functions in question. You could find out by doing a code audit on every program you use, or you could apply the fix. Warnings about opening emails and such things are to do with threat vectors. Here the vector is that function and the thing to do to close it is get a fixed glibc. If your email program is prone to running javascript or something not opening the email is a work around for something that needs to be fixed, it might seem nice to have advice that keeps you safe, but it's a bit like telling someone they shouldn't use a switch because the housing is live, the safe thing to do is fix the problem. -- imalone http://ibmalone.blogspot.co.uk -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: users Digest, Vol 131, Issue 86
On 2015-01-28 15:45:36, users-requ...@lists.fedoraproject.org wrote: ==quoted message from Gordon Messmer gordon.mess...@gmail.com, subject Re: Suddenly can't get nameserver resolution on FC21 after ...== On 01/28/2015 07:02 AM, William W. Austin wrote: I have checked my ifcfg-* files under/etc/sysconfig/ (all 3 links of each of the 2 nics) and they are unchanged. My /etc/hosts file is unchanged DNS is configured in /etc/resolv.conf. Look there. Attempt to ping your DNS servers to verify they are reachable. Use dig to query them directly: dig @dns IP address hostname Apologies - I neglected to include: A) I can ping my gateway (route/cablemodem) just as before B) I can ping all 3 of my nameservers with no trouble D) Using dig (as you suggest) works correctly and resolves properly/ C) My /erc/resolv.conf is unchanged (and identical those on 2 other machines which work correctly). D) IF I have the ip-address of a website (I can get that using another machine on my network), I can use the address in a browser and actually bring up the site. Nevertheless I cannot ping, ssh or telnet to, or sftp/ftp to ANY site (even those on my internal network) unless I have the ip address of the machine. So to me these are a clear indication that for some reason this system is refusing to use the nameservers as such. The reason WHY this is the case still escapes me, and any help with the matter would be greatly appreciated. Thanks, - wwa -- william w. austin aire...@att.net life is just another phase i'm going through. this time, anyway ... -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Recovering a Crashed Fedora
On Thursday 29 January 2015 06:34:06 Heinz Diehl wrote: On 29.01.2015, Mickey wrote: But what I'm concerned about is that Root will change the owner of the Tar files. after i do the new install it will have the same user on the crashed drive. Never ever compress backup data which contains valuable data. One single bit flip will render your whole archive useless. This one does not compress and preserves all important attributes: rsync -avxHSAX /source/ /target Note the trailing slash at the end of the source directory. You can still use tar. After running the tar zcvf ... run the command tar ztvf . to test it again. The benefit of tar over rsync is that you can save it to other filesystems, such as NTFS, memory stick etc. (Although I would never trust a memory stick to be my only version) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Recovering a Crashed Fedora
On 29.01.2015, Gary Stainburn wrote: After running the tar zcvf ... run the command tar ztvf . to test it again. And 1 day later you get a bad sector containing a part of your compressed archive, and your whole backup is gone (and according to Murphy's law, your harddisk containing the source data will refuse to start right after that :-) ). The benefit of tar over rsync is that you can save it to other filesystems, such as NTFS, memory stick etc. Yes (although you can virtually do that with any backup which is compressed, because all the attributes are safely stored in the archive). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Wireless can't ping wireless (SOLVED)
On 29.01.2015 06:07, Jim Lewis wrote: For those following this thread I solved the problem by getting a new router. Here's a quick recap: - I found I couldn't ping a wireless device from another wireless device. - I could not ping a wireless device from a wired device unless I pinged the wired device from the wireless device first (try saying that 3 times fast). - I then started noticing other strange things, a wireless device that could ping a wired device a few moments ago could not now do it. - Eventually all of my wireless stuff decided they didn't want to see my printer anymore. I was originally using a LinkSys E3000 which I have had for many years. I could have attempted to upgrade the firmware but chose not to do it. I bought a Netgear R6200 (AC1200) Dual Band Gigabit router. So far it has solved all of the above problems. It seems to be a bit faster than the old router as well. http://www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear PY312100189 or PY312400218? So, thanks to all who helped me with this. I will try to return the favor someday. Jim Lewis -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: CurrentPendingSector
Hello, Thank for the advise. however, I run smartctl -t long /dev/sdc smartctl 6.2 2014-07-16 r3952 [x86_64-linux-3.17.8-200.fc20.x86_64] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: Execute SMART Extended self-test routine immediately in off-line mode. Drive command Execute SMART Extended self-test routine immediately in off-line mode successful. Testing has begun. Please wait 38 minutes for test to complete. Test will complete after Thu Jan 29 01:54:45 2015 and I did not get much feedback! smartctl -A /dev/sdc does not provides change compared with before. Is there a log file? === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France === Sent: Thursday, January 29, 2015 at 12:52 AM From: Chris Murphy li...@colorremedies.com To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: CurrentPendingSector On Wed, Jan 28, 2015 at 4:19 PM, Patrick Dupre pdu...@gmx.com wrote: 197 Current_Pending_Sector 0x0022 100 100 000Old_age Always - 1 Right. So just use smartctl -t long on the drive. In the next section you didn't paste in, it'll tell you the LBA for the bad sector and that's what you need to write over to fix this. The smartmontools resource previously cited has useful information on how to find out what you've lost in this sector. If it's filesystem metadata it's rather important to e2fsck -f the file system (or xfs_repair, or btrfs scrub) to fix this so it doesn't end up causing worse problems down the road. A block of missing metadata can usually be reconstructed - but not always. Better to find out now. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: WiFi - Realtek - rtl8812au
On 28.01.2015 21:09, Stephen Morris wrote: On 01/28/2015 09:09 AM, poma wrote: On 27.01.2015 21:42, Stephen Morris wrote: On 01/28/2015 03:17 AM, poma wrote: On 25.01.2015 13:46, poma wrote: On 25.01.2015 00:05, Stephen Morris wrote: ... pci adapter. The only problem I have now is that it is very hard to get devices that support Linux from retail stores. Help yourself with these two references to search: http://wireless.kernel.org https://wikidevi.com Another reference: https://www.thinkpenguin.com/catalog/wireless-networking-gnulinux It seems Atheros is popular, - USB: AR9271 AR7010+AR9280 https://wireless.wiki.kernel.org/en/users/drivers/ath9k_htc http://linuxwireless.sipsolutions.net/en/users/Drivers/ath9k_htc https://wikidevi.com/wiki/Atheros_AR9271 https://wikidevi.com/wiki/Atheros_AR7010 - (Mini)PCI(e): AR9223 AR9227 AR9281 AR9285 AR9382 https://wireless.wiki.kernel.org/en/users/drivers/ath9k http://linuxwireless.sipsolutions.net/en/users/Drivers/ath9k https://wikidevi.com/wiki/Atheros Thanks poma, I looked at those pages but none of the devices that I can see listed there are ac devices they all appear to be only up to n. I'm trying to get ac support in Linux. Data(modelchipset) for these two devices are matched: http://linuxwireless.sipsolutions.net/en/users/Drivers/ath10k/#Supported_Devices ath10k supports Qualcomm Atheros 802.11ac QCA98xx hw2.0 based devices, ... - QCA9882 Version 2 found in Compex acWave: WLE600V5-23 - QCA9880 Version 2 found in Compex acWave: WLE900V5-23 http://www.compexshop.com/index.php/cPath/57_103 Atheros miniPCIe 802.11ac cards 5GHz - COMPEX WLE600V5-23 miniPCIe module, AR9882, 802.11ac, 2*2MIMO http://compexshop.com/product_info.php/cPath/57_103/products_id/447 - COMPEX WLE900V5-23 miniPCIe module, AR9880, 802.11ac, 3*3MIMO http://compexshop.com/product_info.php/cPath/57_103/products_id/445 Undoubtedly try to contact devs to confirm you these devices are truly supported. Good Luck! Thanks poma, I missed this info when I looked yesterday morning. Its looking like I'm going to have to go back to my N pci wireless card that is using the ATH9K driver as the rtl8812AU driver you pointed me at on git seems to be frequently crashing the kernel (I get frequent kernel core abends that can't be reported because the kernel is tainted). It may be coincidence but when immediately after the kernel issue the wifi interface activates I'm assuming its that driver that caused the issue. You can always try to contact the original manufacturer of hardware and retailer of the same. You can also try to find patches for the current kernel: http://lmgtfy.com/?q=rtl8812au+3.18 This does not guarantee that the device will actually work, this is just the best effort from users just like you. ;) Try this $ git clone https://github.com/vsurrel/rtl8812AU_8821AU_linux.git $ cd rtl8812AU_8821AU_linux/ $ git log -1 commit 7a427372bf5540285d95f090ad5523019a365415 Author: MilhouseVH milhousevh.git...@nmacleod.com Date: Thu Dec 18 11:42:48 2014 + Add support for kernel 3.18 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: End of 32-bit support?
On Wed, Jan 28, 2015 at 06:00:28PM +0100, poma wrote: On 28.01.2015 17:17, Matthew Miller wrote: On Sat, Jan 24, 2015 at 08:37:59AM +0100, Ralf Corsepius wrote: Hatters, or from Red Hatters working in their spare time. (Of course, as RH often does, many of the high-output contributors end up applying for and getting RH jobs, skewing the picture.) Well, I am observing quite a few people from major enterprises (RH business partners?) who are working on secondary archtectures, but I've very rarely (I don't recall any such incident) tripped over community folks who are working on them. Sometimes Red Hat business partners, but that doesn't mean that it's at Red Hat's direction. Overall, this is one of the few areas where we have money and paid effort flowing into the project that *isn't* coming from Red Hat, and I don't think that's a bad thing. These are community folks too, at least if we're doing it right. Additionally, I'm not privy to Red Hat's architecture strategy, but as far as I know, 32 bit ARM — currently our only primary non-x86 arch! — is not of particular corporate interest. It's obvious to me the aarch64 is RH's business interest. But aarch64 and 32-bit arm are _completely_ different architectures. I also think it's a little unfair to frame this as a conflict, overall. It may be the case that Red Hat is less interested in paying people to work on 32-bit x86 (although I don't actually know that to be a fact). But this is just like any other contributor to the community — you can't make people do work they're not interested in. Right, but that's not my point: My points are: - I once more feel pushed/tossed around by RH's interest and RH-Fedora-people who obviously don't properly separate RH and Community. I can't argue with feelings, but I also am not really sure what separation you're looking for here and how it would affect this. - Support for i386 falls out as a by-product at almost Zero-costs of the existing process. I don't think that's true at all. It signficantly increases QA load, and we're struggling a lot with release engineering being able to cope with Fedora at its current scale. Cutting back here has an clear benefit (whether or not it's significant enough to outweigh the other wide isn't settled, of course). More significantly, the Fedora kernel team tells me that _they_ don't feel like they have the resources to really honestly support the 32-bit kernel — and the rest all falls out from that. You write as if you - Fedora/Red Hat lack people capable of maintaining the kernel as if it were something special - they are not kernel developers. What Josh works except to maintains the kernel? I can't parse this last sentence correctly. Are you asking what Josh does other than maintain the kernel? Or are you asking something else? -- Paul W. Frieldshttp://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Why does Anaconda overrides user decisions?
On 01/28/2015 10:20 AM, Matthew Miller wrote: On Sat, Jan 24, 2015 at 05:15:53AM -0600, Glenn Holmer wrote: Anacoda is the weakest link in Fedora toolchain. The non-linear UI is completely non-intuitive +1, the partitioner is the worst I've seen in 20 years of using Linux. It also covers more cases more simply than any other storage manager you've seen. You really can't have everything, here. Wait, are you saying that we can't have both functionality and a good, intuitive UI? -- Glenn Holmer (Linux registered user #16682) After the vintage season came the aftermath -- and Cenbe. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Anaconda illegal address
On Thu, Jan 29, 2015 at 10:44 AM, CLOSE Dave dave.cl...@us.thalesgroup.com wrote: Chris Murphy wrote: When anaconda complains about an illegal IP address string passed to inet_aton, how can I discover what the bad string contains? So far as I can see, all the configured addresses are perfectly valid. Here's a copy of the traceback: http://ur1.ca/jkjvw. If you let the bug report dialog file this bug for you, it will check for duplicates and that bug might have a work around. Pretty much anytime the installer crashes like this rather than giving you a coherent error message (and failing gracefully) it's a bug. I checked for reported bugs before filing my question. But I'm happy to file a report anyway. I mean, when there's a crash libreport should pop up and offer to file the bug for you. You need to enter bugzilla credentials and then it automatically files the bug details including uploading all files. Before it does this, it checks if a bug has already been filed with this mechanism so that there aren't duplicates filed. It'll tell you the URL for the found bug. You don't have to check, it does it for you. If you go to the that bug URL there might be a suggestion how to work around it. I agree that the behavior is not ideal. Still, if there is a clue somewhere in the log files, I would have been happy to learn about it. Based on the lack of response, I presume there is no such clue. It's a crash. If there isn't already a bug filed then I'd definitely say you've hit an edge case. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Anaconda illegal address
Chris Murphy wrote: When anaconda complains about an illegal IP address string passed to inet_aton, how can I discover what the bad string contains? So far as I can see, all the configured addresses are perfectly valid. Here's a copy of the traceback: http://ur1.ca/jkjvw. If you let the bug report dialog file this bug for you, it will check for duplicates and that bug might have a work around. Pretty much anytime the installer crashes like this rather than giving you a coherent error message (and failing gracefully) it's a bug. I checked for reported bugs before filing my question. But I'm happy to file a report anyway. I agree that the behavior is not ideal. Still, if there is a clue somewhere in the log files, I would have been happy to learn about it. Based on the lack of response, I presume there is no such clue. -- Dave Close -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: CurrentPendingSector
On 01/29/2015 04:10 AM, Patrick Dupre wrote: Hello, Thank for the advise. however, I run smartctl -t long /dev/sdc smartctl 6.2 2014-07-16 r3952 [x86_64-linux-3.17.8-200.fc20.x86_64] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: Execute SMART Extended self-test routine immediately in off-line mode. Drive command Execute SMART Extended self-test routine immediately in off-line mode successful. Testing has begun. Please wait 38 minutes for test to complete. Test will complete after Thu Jan 29 01:54:45 2015 and I did not get much feedback! smartctl -A /dev/sdc does not provides change compared with before. Is there a log file? smartctl -l selftest /dev/sdc -- Bob Nichols NOSPAM is really part of my email address. Do NOT delete it. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
systemd: Failed at step CGROUP spawning ...
any idea of what this message means? systemd: Failed at step CGROUP spawning /usr/lib/systemd/systemd: No such file or directory -- -- Those who don't understand recursion are doomed to repeat it -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
rsyslogd is stuck in D state
/usr/sbin/rsyslogd is stuck in D state, seems to be hogging my disk I/O what is it doing?? I don't see anything interesting in /var/log/messages -- -- Those who don't understand recursion are doomed to repeat it -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Corrupted Hard Drive
Fedora 15 Hard drive. ext4 # e2fsck -b 8193 /dev/sdb e2fsck 1.42.8 (20-Jun-2013) e2fsck: Bad magic number in super-block while trying to open /dev/sdb The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device What command should I use to overcome this ? I'm using Fedora 20 to check the hard drive. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Corrupted Hard Drive
On 01/29/2015 09:59 AM, Mickey wrote: What command should I use to overcome this ? The hard drive is partitioned, yes? fsck /dev/sdb# If your file system is on the second partition: fsck /dev/sdb2 By not using a number you are pointing to the entire block device and not a partition. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: WiFi - Realtek - rtl8812au
... Try this $ git clone https://github.com/vsurrel/rtl8812AU_8821AU_linux.git $ cd rtl8812AU_8821AU_linux/ $ git log -1 commit 7a427372bf5540285d95f090ad5523019a365415 Author: MilhouseVH milhousevh.git...@nmacleod.com Date: Thu Dec 18 11:42:48 2014 + Add support for kernel 3.18 Also try PLD Linux method: $ curl -JLO https://github.com/pld-linux/rtl8812au/archive/master.tar.gz $ tar xf rtl8812au-master.tar.gz $ curl -JLO https://github.com/austinmarton/rtl8812au_linux/archive/master.tar.gz $ tar xf rtl8812au_linux-master.tar.gz $ cp rtl8812au-master/*.patch rtl8812au_linux-master/ $ cd rtl8812au_linux-master/ $ patch -p1 linux-3.11.patch $ patch -p1 disable-debug.patch $ patch -p1 enable-cfg80211-support.patch $ patch -p1 update-cfg80211-support.patch $ patch -p1 warnings.patch $ patch -p1 gcc-4.9.patch $ patch -p1 linux-3.18.patch $ make $ su # cp 8812au.ko /lib/modules/$(uname -r)/updates/ # depmod # modprobe -v 8812au # dmesg ... RTL871X: module init start RTL871X: rtl8812au v4.3.2_11100.20140411 RTL871X: build time: Jan 29 2015 20:10:14 usbcore: registered new interface driver rtl8812au RTL871X: module init ret=0 Ref. Driver for AC1200 (802.11ac) Wireless Dual-Band USB Adapter https://github.com/pld-linux/rtl8812au rtl8812au Linux driver (v4.3.2 fork) for Realtek based 802.11ac devices https://github.com/austinmarton/rtl8812au_linux = ftp://master-ftp.pld-linux.org/dists/3.0/PLD/SRPMS/RPMS/rtl8812au-4.3.2_11100.20140411-0.20140901.6@3.18.4_1.src.rpm -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: WiFi - Realtek - rtl8812au
On 29.01.2015 20:25, poma wrote: ... Try this $ git clone https://github.com/vsurrel/rtl8812AU_8821AU_linux.git $ cd rtl8812AU_8821AU_linux/ $ git log -1 commit 7a427372bf5540285d95f090ad5523019a365415 Author: MilhouseVH milhousevh.git...@nmacleod.com Date: Thu Dec 18 11:42:48 2014 + Add support for kernel 3.18 Also try PLD Linux method: $ curl -JLO https://github.com/pld-linux/rtl8812au/archive/master.tar.gz $ tar xf rtl8812au-master.tar.gz $ curl -JLO https://github.com/austinmarton/rtl8812au_linux/archive/master.tar.gz $ tar xf rtl8812au_linux-master.tar.gz $ cp rtl8812au-master/*.patch rtl8812au_linux-master/ $ cd rtl8812au_linux-master/ $ patch -p1 linux-3.11.patch $ patch -p1 disable-debug.patch $ patch -p1 enable-cfg80211-support.patch $ patch -p1 update-cfg80211-support.patch $ patch -p1 warnings.patch $ patch -p1 gcc-4.9.patch $ patch -p1 linux-3.18.patch $ make $ su # cp 8812au.ko /lib/modules/$(uname -r)/updates/ # depmod # modprobe -v 8812au # dmesg ... RTL871X: module init start RTL871X: rtl8812au v4.3.2_11100.20140411 RTL871X: build time: Jan 29 2015 20:10:14 usbcore: registered new interface driver rtl8812au RTL871X: module init ret=0 Ref. Driver for AC1200 (802.11ac) Wireless Dual-Band USB Adapter https://github.com/pld-linux/rtl8812au rtl8812au Linux driver (v4.3.2 fork) for Realtek based 802.11ac devices https://github.com/austinmarton/rtl8812au_linux = ftp://master-ftp.pld-linux.org/dists/3.0/PLD/SRPMS/RPMS/rtl8812au-4.3.2_11100.20140411-0.20140901.6@3.18.4_1.src.rpm This repo is also interesting: Rewrite RTL 8812 driver https://github.com/ulli-kroll/rtl8821au even has firmwares: $ ls rtl8821au/firmware/ rtl8812aufw.bin rtl8821aufw.bin make produces: ... error: macro __DATE__ ... error: macro __TIME__ Classic! :) Must be the ubiquitous Realtek RTL8812AU USB 3.0 802.11ac chipset is really popular. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Anaconda illegal address
Chris Murphy wrote: I mean, when there's a crash libreport should pop up and offer to file the bug for you. You need to enter bugzilla credentials and then it automatically files the bug details including uploading all files. Before it does this, it checks if a bug has already been filed with this mechanism so that there aren't duplicates filed. It'll tell you the URL for the found bug. You don't have to check, it does it for you. If you go to the that bug URL there might be a suggestion how to work around it. No, that doesn't work. There is no provision in the libreport popup for passing through a proxy. It's a crash. If there isn't already a bug filed then I'd definitely say you've hit an edge case. I agree it's a bug. However, it isn't the bug I originally thought. When searching, I had missed BZ 1178320. That report has been closed as NOTABUG although it is exactly my issue. I will now open two BZ reports: 1. Anaconda should fail with a useful message when a required address is missing. 2. Anaconda should not require --gateway or --nameserver for an interface with a static configuration. In my case, the static interface is secondary (it should not have a gateway) and DNS is already provided by the primary DHCP interface. -- Dave Close, Thales Avionics, Irvine California USA. cell +1 949 394 2124, dave.cl...@us.thalesgroup.com If a cluttered desk is a sign of a cluttered mind, of what then is an empty desk? --Albert Einstein -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Anaconda illegal address
Joe Zeff wrote: Closing a bug as a duplicate isn't saying that it's not a bug. It means that the bug's already been reported, and that it's a waste of resources keeping two versions of the report open. But it does mean that when the referenced report has already been closed and marked NOTABUG. -- Dave Close -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Anaconda illegal address
On 01/29/2015 01:52 PM, CLOSE Dave wrote: Joe Zeff wrote: Closing a bug as a duplicate isn't saying that it's not a bug. It means that the bug's already been reported, and that it's a waste of resources keeping two versions of the report open. But it does mean that when the referenced report has already been closed and marked NOTABUG. If whoever is responsible for a package has decided that this is not a bug, reporting it again isn't going to change their mind. You can always add a comment explaining why you think it's a bug and maybe change their mind. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Anaconda illegal address
I wrote: I will now open two BZ reports: 1. Anaconda should fail with a useful message when a required address is missing. My report has now been closed, marked as a duplicate of BZ 1178320. That means at least one developer thinks providing a useless error message is not a bug. I strongly disagree. -- Dave Close -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: WiFi - Realtek - rtl8812au
On 01/30/2015 08:34 AM, Stephen Morris wrote: On 01/30/2015 06:47 AM, poma wrote: On 29.01.2015 20:25, poma wrote: ... Try this $ git clone https://github.com/vsurrel/rtl8812AU_8821AU_linux.git $ cd rtl8812AU_8821AU_linux/ $ git log -1 commit 7a427372bf5540285d95f090ad5523019a365415 Author: MilhouseVH milhousevh.git...@nmacleod.com Date: Thu Dec 18 11:42:48 2014 + Add support for kernel 3.18 Also try PLD Linux method: $ curl -JLO https://github.com/pld-linux/rtl8812au/archive/master.tar.gz $ tar xf rtl8812au-master.tar.gz $ curl -JLO https://github.com/austinmarton/rtl8812au_linux/archive/master.tar.gz $ tar xf rtl8812au_linux-master.tar.gz $ cp rtl8812au-master/*.patch rtl8812au_linux-master/ $ cd rtl8812au_linux-master/ $ patch -p1 linux-3.11.patch $ patch -p1 disable-debug.patch $ patch -p1 enable-cfg80211-support.patch $ patch -p1 update-cfg80211-support.patch $ patch -p1 warnings.patch $ patch -p1 gcc-4.9.patch $ patch -p1 linux-3.18.patch $ make $ su # cp 8812au.ko /lib/modules/$(uname -r)/updates/ # depmod # modprobe -v 8812au # dmesg ... RTL871X: module init start RTL871X: rtl8812au v4.3.2_11100.20140411 RTL871X: build time: Jan 29 2015 20:10:14 usbcore: registered new interface driver rtl8812au RTL871X: module init ret=0 Ref. Driver for AC1200 (802.11ac) Wireless Dual-Band USB Adapter https://github.com/pld-linux/rtl8812au rtl8812au Linux driver (v4.3.2 fork) for Realtek based 802.11ac devices https://github.com/austinmarton/rtl8812au_linux = ftp://master-ftp.pld-linux.org/dists/3.0/PLD/SRPMS/RPMS/rtl8812au-4.3.2_11100.20140411-0.20140901.6@3.18.4_1.src.rpm This repo is also interesting: Rewrite RTL 8812 driver https://github.com/ulli-kroll/rtl8821au even has firmwares: $ ls rtl8821au/firmware/ rtl8812aufw.bin rtl8821aufw.bin make produces: ... error: macro __DATE__ ... error: macro __TIME__ Classic! :) That's the error I was getting with the original program that led to this thread. I'll also try the PLD drivers and see how they go. I've run the PLD patch process and the make to build the driver which I am using at the moment. I'll monitor this for a while and see how it goes. I'll also need to do the compile again as I have also just done an update run which has updated to the 3.18 kernel. Must be the ubiquitous Realtek RTL8812AU USB 3.0 802.11ac chipset is really popular. attachment: samorris.vcf-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: WiFi - Realtek - rtl8812au
On 01/30/2015 06:47 AM, poma wrote: On 29.01.2015 20:25, poma wrote: ... Try this $ git clone https://github.com/vsurrel/rtl8812AU_8821AU_linux.git $ cd rtl8812AU_8821AU_linux/ $ git log -1 commit 7a427372bf5540285d95f090ad5523019a365415 Author: MilhouseVH milhousevh.git...@nmacleod.com Date: Thu Dec 18 11:42:48 2014 + Add support for kernel 3.18 Also try PLD Linux method: $ curl -JLO https://github.com/pld-linux/rtl8812au/archive/master.tar.gz $ tar xf rtl8812au-master.tar.gz $ curl -JLO https://github.com/austinmarton/rtl8812au_linux/archive/master.tar.gz $ tar xf rtl8812au_linux-master.tar.gz $ cp rtl8812au-master/*.patch rtl8812au_linux-master/ $ cd rtl8812au_linux-master/ $ patch -p1 linux-3.11.patch $ patch -p1 disable-debug.patch $ patch -p1 enable-cfg80211-support.patch $ patch -p1 update-cfg80211-support.patch $ patch -p1 warnings.patch $ patch -p1 gcc-4.9.patch $ patch -p1 linux-3.18.patch $ make $ su # cp 8812au.ko /lib/modules/$(uname -r)/updates/ # depmod # modprobe -v 8812au # dmesg ... RTL871X: module init start RTL871X: rtl8812au v4.3.2_11100.20140411 RTL871X: build time: Jan 29 2015 20:10:14 usbcore: registered new interface driver rtl8812au RTL871X: module init ret=0 Ref. Driver for AC1200 (802.11ac) Wireless Dual-Band USB Adapter https://github.com/pld-linux/rtl8812au rtl8812au Linux driver (v4.3.2 fork) for Realtek based 802.11ac devices https://github.com/austinmarton/rtl8812au_linux = ftp://master-ftp.pld-linux.org/dists/3.0/PLD/SRPMS/RPMS/rtl8812au-4.3.2_11100.20140411-0.20140901.6@3.18.4_1.src.rpm This repo is also interesting: Rewrite RTL 8812 driver https://github.com/ulli-kroll/rtl8821au even has firmwares: $ ls rtl8821au/firmware/ rtl8812aufw.bin rtl8821aufw.bin make produces: ... error: macro __DATE__ ... error: macro __TIME__ Classic! :) That's the error I was getting with the original program that led to this thread. I'll also try the PLD drivers and see how they go. Must be the ubiquitous Realtek RTL8812AU USB 3.0 802.11ac chipset is really popular. attachment: samorris.vcf-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Old Kernel Modules Directories not Cleaned up
Hi, DNF is currently configured to keep 3 kernel versions, consequently when I exceed that number of kernels it automatically uninstalls the oldest kernel, which I don't have any issues with, but what I do have an issue with is when these uninstalls are done it does not clean up the /lib/modules directories, they are left lying around. I had to delete a dozen of these directories this morning manually, why are these not removed when the associated kernels are removed? I didn't check what was in these directories, but I do have the nvidia and virtualbox kernel drivers installed as well, is it possible the removal of these when the associated kernel is removed is not cleaning up properly? regards, Steve attachment: samorris.vcf-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Anaconda illegal address
On 01/29/2015 12:17 PM, CLOSE Dave wrote: My report has now been closed, marked as a duplicate of BZ 1178320. That means at least one developer thinks providing a useless error message is not a bug. I strongly disagree. Closing a bug as a duplicate isn't saying that it's not a bug. It means that the bug's already been reported, and that it's a waste of resources keeping two versions of the report open. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Wireless can't ping wireless (SOLVED)
On 29.01.2015 06:07, Jim Lewis wrote: For those following this thread I solved the problem by getting a new router. Here's a quick recap: - I found I couldn't ping a wireless device from another wireless device. - I could not ping a wireless device from a wired device unless I pinged the wired device from the wireless device first (try saying that 3 times fast). - I then started noticing other strange things, a wireless device that could ping a wired device a few moments ago could not now do it. - Eventually all of my wireless stuff decided they didn't want to see my printer anymore. I was originally using a LinkSys E3000 which I have had for many years. I could have attempted to upgrade the firmware but chose not to do it. I bought a Netgear R6200 (AC1200) Dual Band Gigabit router. So far it has solved all of the above problems. It seems to be a bit faster than the old router as well. http://www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear PY312100189 or PY312400218? It's the R6200 version 2 (PY312400218). And, the first thing I did after getting it was to upgrade the firmware. If it screwed up and got bricked I would just take it back. Jim Lewis -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Anaconda illegal address
On Thu, Jan 29, 2015 at 1:17 PM, CLOSE Dave dave.cl...@us.thalesgroup.com wrote: I wrote: I will now open two BZ reports: 1. Anaconda should fail with a useful message when a required address is missing. My report has now been closed, marked as a duplicate of BZ 1178320. That means at least one developer thinks providing a useless error message is not a bug. I strongly disagree. I think kickstarts are pretty much expected to be exactly correct. The release criteria says the GUI installer shouldn't crash, permitting it in certain instances. But for kickstarts, crashing if things aren't exactly spot on is probably permitted criteria wise. I'm not saying it's OK that it crashes, it's just that exception handling takes some coding either to parse the kickstart and reject it from the start, or some sort of fail graceful code. -- Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Old Kernel Modules Directories not Cleaned up
On 30.01.2015 00:21, Gordon Messmer wrote: On 01/29/2015 01:55 PM, Stephen Morris wrote: I had to delete a dozen of these directories this morning manually, why are these not removed when the associated kernels are removed? Were the kernel modules in those directories built locally by dkms rather than owned by rpm packages? That'd do it. These modules do not belong to the official kernel packages, as well as your hand-built Wi-Fi module. The point is, DKMS - Dynamic Kernel Module Support is not a perfect mechanism, therefore, it is normal for it to leave the old modules behind. https://wiki.archlinux.org/index.php/Dynamic_Kernel_Module_Support#Remove_modules -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Wireless can't ping wireless (SOLVED)
On 29.01.2015 22:15, Jim Lewis wrote: On 29.01.2015 06:07, Jim Lewis wrote: For those following this thread I solved the problem by getting a new router. Here's a quick recap: - I found I couldn't ping a wireless device from another wireless device. - I could not ping a wireless device from a wired device unless I pinged the wired device from the wireless device first (try saying that 3 times fast). - I then started noticing other strange things, a wireless device that could ping a wired device a few moments ago could not now do it. - Eventually all of my wireless stuff decided they didn't want to see my printer anymore. I was originally using a LinkSys E3000 which I have had for many years. I could have attempted to upgrade the firmware but chose not to do it. I bought a Netgear R6200 (AC1200) Dual Band Gigabit router. So far it has solved all of the above problems. It seems to be a bit faster than the old router as well. http://www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear PY312100189 or PY312400218? It's the R6200 version 2 (PY312400218). And, the first thing I did after getting it was to upgrade the firmware. If it screwed up and got bricked I would just take it back. :) RAM 256MB / Flash 128MB / USB 3.0 - nice. Too bad it isn't officially supported by DD-WRT, such as R6300v2. Jim Lewis -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: WiFi - Realtek - rtl8812au
On 29.01.2015 23:00, Stephen Morris wrote: On 01/30/2015 08:34 AM, Stephen Morris wrote: On 01/30/2015 06:47 AM, poma wrote: On 29.01.2015 20:25, poma wrote: ... Try this $ git clone https://github.com/vsurrel/rtl8812AU_8821AU_linux.git $ cd rtl8812AU_8821AU_linux/ $ git log -1 commit 7a427372bf5540285d95f090ad5523019a365415 Author: MilhouseVH milhousevh.git...@nmacleod.com Date: Thu Dec 18 11:42:48 2014 + Add support for kernel 3.18 Also try PLD Linux method: $ curl -JLO https://github.com/pld-linux/rtl8812au/archive/master.tar.gz $ tar xf rtl8812au-master.tar.gz $ curl -JLO https://github.com/austinmarton/rtl8812au_linux/archive/master.tar.gz $ tar xf rtl8812au_linux-master.tar.gz $ cp rtl8812au-master/*.patch rtl8812au_linux-master/ $ cd rtl8812au_linux-master/ $ patch -p1 linux-3.11.patch $ patch -p1 disable-debug.patch $ patch -p1 enable-cfg80211-support.patch $ patch -p1 update-cfg80211-support.patch $ patch -p1 warnings.patch $ patch -p1 gcc-4.9.patch $ patch -p1 linux-3.18.patch $ make $ su # cp 8812au.ko /lib/modules/$(uname -r)/updates/ # depmod # modprobe -v 8812au # dmesg ... RTL871X: module init start RTL871X: rtl8812au v4.3.2_11100.20140411 RTL871X: build time: Jan 29 2015 20:10:14 usbcore: registered new interface driver rtl8812au RTL871X: module init ret=0 Ref. Driver for AC1200 (802.11ac) Wireless Dual-Band USB Adapter https://github.com/pld-linux/rtl8812au rtl8812au Linux driver (v4.3.2 fork) for Realtek based 802.11ac devices https://github.com/austinmarton/rtl8812au_linux = ftp://master-ftp.pld-linux.org/dists/3.0/PLD/SRPMS/RPMS/rtl8812au-4.3.2_11100.20140411-0.20140901.6@3.18.4_1.src.rpm This repo is also interesting: Rewrite RTL 8812 driver https://github.com/ulli-kroll/rtl8821au even has firmwares: $ ls rtl8821au/firmware/ rtl8812aufw.bin rtl8821aufw.bin make produces: ... error: macro __DATE__ ... error: macro __TIME__ Classic! :) That's the error I was getting with the original program that led to this thread. I'll also try the PLD drivers and see how they go. I've run the PLD patch process and the make to build the driver which I am using at the moment. I'll monitor this for a while and see how it goes. I'll also need to do the compile again as I have also just done an update run which has updated to the 3.18 kernel. Take your time, man. BTW what Vendor Product/Model is that RTL8812AU device, what is the output of 'lsusb'? Also you mentioned Belkin router, what Vendor Product/Model is it? http://www.dd-wrt.com/wiki/index.php/Supported_Devices https://wikidevi.com/wiki/Main_Page -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Corrupted Hard Drive
On 01/29/2015 11:16 AM, Michael Cronenworth wrote: On 01/29/2015 09:59 AM, Mickey wrote: What command should I use to overcome this ? The hard drive is partitioned, yes? fsck /dev/sdb# If your file system is on the second partition: fsck /dev/sdb2 By not using a number you are pointing to the entire block device and not a partition. Thanks Michael, That did the trick. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: rsyslogd is stuck in D state
On 01/29/2015 06:38 AM, Neal Becker wrote: /usr/sbin/rsyslogd is stuck in D state, seems to be hogging my disk I/O You could strace -p pid to see which file descriptor it's reading/writing, and then look at /proc/pid/fd/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
libreport crashing
Every time I use abrt to try to report a problem, it crashes with an error in libreport. Unfortunately, I can't report that because attempting to do so crashes abrt. Is it just me or are others seeing this problem? -- -- Steve -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Old Kernel Modules Directories not Cleaned up
On 01/29/2015 01:55 PM, Stephen Morris wrote: I had to delete a dozen of these directories this morning manually, why are these not removed when the associated kernels are removed? Were the kernel modules in those directories built locally by dkms rather than owned by rpm packages? That'd do it. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
