Re: [CentOS] Update to 3.10.0-693.17.1 breaks ath5k

2018-02-03 Thread Akemi Yagi 
On Fri, Feb 2, 2018 at 10:57 PM, Stephen Davies  wrote:
> Where can I find a suitable module or even source code to build here?
>
> (Centos 7)

ELRepo used to provide the kmod-ath5k package. However, the module
does not compile under EL7.4 due to the change in the wireless stack.
If your device needs ath5k, give ELRepo's kernel-lt a try. The module
is enabled in this kernel.

Akemi
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Anyone using GQRX in Centos-7, for SDR ?

2018-02-03 Thread Nux! 
Cool, thanks for testing. Packages moved to main repo.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Fred Smith" 
> To: "CentOS mailing list" 
> Sent: Friday, 2 February, 2018 20:53:06
> Subject: Re: [CentOS] Anyone using GQRX in Centos-7, for SDR ?

> On Fri, Feb 02, 2018 at 09:38:17AM +, Nux! wrote:
>> Is it a Realtek chipset?
> 
> yes it is.
> 
>> I've had problems with it on CentOS as the system will load up the DVB 
>> drivers
>> (for TV tuner) thus interfering with the SDR.
>> What worked for me is blacklisting them & reboot. Give it a try.
> 
> Ah, thanks, that's the trick. works now.
> 
>> 
>> cat /etc/modprobe.d/blacklist_rtl.conf
>> blacklist dvb_usb_rtl28xxu
>> blacklist rtl2832
>> blacklist rtl2830
>> 
>> BTW there's a new package at http://li.nux.ro/download/nux/tmp/gqrx7/ if you
>> care to test and confirm success so I can move it to the main repo.
> 
> I've installed it and it seems to be working fine (based on about 20
> minutes of use, and note that I"m not an expert yet).
> 
> thanks!
> 
>> Nux!
>> www.nux.ro
>> 
>> - Original Message -
>> > From: "Fred Smith" 
>> > To: "CentOS mailing list" 
>> > Sent: Thursday, 1 February, 2018 22:38:09
>> > Subject: [CentOS] Anyone using GQRX in Centos-7, for SDR ?
>> 
>> > I gave myself a toy, one of those cheap USB Software Define Radios, and
>> > would like to use it on my C7 box. Having wasted some time on it, I gave
>> > up and installed Ubuntu on a USB HD so I can boot that to play with SDR.
>> > The Ubuntu GQRX installation is well documented and went off without a 
>> > hitch.
>> > but I just hate having to boot something else on my main box (partly 
>> > because
>> > it also runs a mailserver for my personal domain, partly because, well,
>> > I just want my box running CentOS, not Ubuntu.)
>> > 
>> > Searching through SDR info on line I see someone has documented installing
>> > all the bits for C6, but I suspect the process is different for C7.
>> > 
>> > BTW, I installed the various bits I could find from, er, I think some
>> > came from li.nux.ro, some perhaps from epel, on C7, but couldn't get
>> > them to properly function.
>> > 
>> > Worse, when the USB radio is unplugged from the system, it locks up hard.
>> > 
>> > then a few days ago, I  had been playing with it using the UBUNTU install,
>> > did a reboot and for kicks fired up the GQRX on Centos, and lo and behold
>> > it worked! I tried running it on Centos yesterday and it reverted to type,
>> > i.e., lock up hard. I suspect that Ubuntu is leaving some hardware in a
>> > state that allows it to work on a subsequent Centos boot (without 
>> > poweroff),
>> > but no clue what.
>> > 
>> > So, if anyone can point me to how  to use it on C7, I'd greatly appreciate 
>> > it.
>> > 
>> > thanks in advance!
>> > 
>> > Fred
>> > --
> 
> --
>  Fred Smith -- fre...@fcshome.stoneham.ma.us -
>   I can do all things through Christ
>  who strengthens me.
> -- Philippians 4:13 
> ---
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Re-enable grub boot in UEFI (Windows took over it) [SOLVED]

2018-02-03 Thread wwp 
Hello Chris,


On Thu, 1 Feb 2018 13:25:14 -0700 Chris Murphy  wrote:

> On Thu, Feb 1, 2018 at 10:13 AM, wwp  wrote:
> > Hello Chris,
> >
> >
> > On Thu, 01 Feb 2018 17:00:03 + Chris Murphy  
> > wrote:
> >  
> >> You can to use efibootmgr for this. NVRAM boot entry is what changed, not
> >> the contents of the EFI System partition.
> >>
> >> efibootmgr -v
> >>
> >> Will list all entries and Boot Order. You need to use --bootorder to make
> >> sure the CentOS entry is first.  
> >
> > Interesting.. thanks for your reply!
> >
> > Too bad I never run this command when things were OK (in order to
> > compare), 'cause now, what it says doesn't mention anything that seem
> > related to the CentOS partition or I read wrong:
> >
> > BootCurrent: 0007
> > Timeout: 0 seconds
> > BootOrder: 0001,0002,0003,0004,0005,0006,0007
> > Boot* Windows Boot Manager  
> > HD(1,GPT,a6b87338-9b9c-4a50-8fde-2447e8fdebb6,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}
> > Boot0001* UEFI: A400 NVMe SanDisk 512GB, Partition 1
> > HD(1,GPT,a6b87338-9b9c-4a50-8fde-2447e8fdebb6,0x800,0xfa000)/File(EFI\Microsoft\Boot\bootmgfw.efi)..BO
> > Boot0002* Diskette DriveBBS(Floppy,Diskette Drive,0x0)..BO
> > Boot0003* M.2 PCIe SSD  BBS(HD,P0: A400 NVMe SanDisk 512GB,0x0)..BO
> > Boot0004* USB Storage DeviceBBS(USB,KingstonDataTraveler 
> > 3.0PMAP,0x0)..BO
> > Boot0005* CD/DVD/CD-RW DriveBBS(CDROM,CD/DVD/CD-RW Drive,0x0)..BO
> > Boot0006* Onboard NIC   BBS(Network,Onboard NIC,0x0)..BO
> > Boot0007* UEFI: KingstonDataTraveler 3.0PMAP, Partition 1   
> > PciRoot(0x0)/Pci(0x14,0x0)/USB(16,0)/HD(1,MBR,0x61f11812,0x800,0x737f800)..BO
> >
> > I don't know what 0001 and 0002 refer to exactly (there's only one SSD
> > drive in this laptop).  
> 
> For whatever reason the CentOS entry is missing.

I'd like to know the reason (not formally asking here), the 1st time it
happened it was because I booted in Windows, which is known to more or
less rewrite the boot entries (in case of updates, IIRC), but this time
it was not the case, I was attempting to boot a pmagic live USB drive..
UEFI killer? :-/


> Option 1:
> 
> A relatively easy cheat is to mount your root volume to /mnt and then search
> 
> grep efibootmgr /mnt/var/log/anaconda/program.log ##this is the
> path and name on Fedora, not 100% certain on CentOS
> 
> And what you'll get back is a line that contains the efibootmgr
> command that was used during the installation. So you'll need to
> modify the forward slashes for it to work, something like this:
> 
> sudo efibootmgr -c -w -L CentOS -d /dev/sda -p 2 -l
> \\EFI\\redhat\\grub\\shimx64.efi
> 
> Option 2:
> 
> At least on Fedora 27 + Windows 10, this is what my ESP contains:
> 
> ├── EFI
> │   ├── Boot
> │   │   ├── bootx64.efi
> │   │   ├── fallback.efi
> │   │   └── fbx64.efi

(no fallback.efi here, but I presume fbx64.efi is a fallback too?)


> Those are Fedora installed default bootloaders. So if you wipe out all
> the NVRAM boot entries, these get used first. And when fallback.efi
> figures out that there isn't a proper NVRAM boot entry, it's supposed
> to insert one, just like the Option 1 command above does. You'll use
> 'efibootmgr -b  -B' to delete them one by one; looks like you
> might be able to get away with just deleting 0001 and . Of course
> it means the Windows boot entry is blown away, which might make you
> nervous - but the way it's supposed to work is the GRUB menu should
> have a Windows boot option in it, and you just pick that for booting
> Windows.
> 
> 
> I've mainly used option 1.

You were right, the initial efibootmgr command was in anaconda's log, I
could do, for the sake of the archives:

$ efibootmgr -c -w -L CentOS Linux -d /dev/nvme0n1 -p 1 -l 
\\EFI\\centos\\shim.efi
BootCurrent: 0007
Timeout: 0 seconds
BootOrder: 0008,0001,0002,0003,0004,0005,0006,0007
Boot* Windows Boot Manager
Boot0001* UEFI: A400 NVMe SanDisk 512GB, Partition 1
Boot0002* Diskette Drive
Boot0003* M.2 PCIe SSD
Boot0004* USB Storage Device
Boot0005* CD/DVD/CD-RW Drive
Boot0006* Onboard NIC
Boot0007* UEFI: KingstonDataTraveler 3.0PMAP, Partition 1
Boot0008* CentOS

And it simply works, I could restart the system and boot from grub
(which proposes to boot to Windows too, grub is a good boy).

A huge thanks to you, Chris, I owe you one.


Regards,

-- 
wwp


pgphuZ4c8WU74.pgp
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] OT: RepoForge/RPMForge State Survey

2018-02-03 Thread David Hrbáč 
Hello,

RepoForge used to be one of the important repositories for CentOS/RHEL. I
know that RepoForge is considered to be clinically dead nowadays. On the
other hand RepoForge is still physically alive.

We would like to harness community opinion on RepoForge status and future.
In case that you use or used to use the RepoForge I kindly ask you to fill
up this form to help us with the decision.

The form is here: https://goo.gl/forms/4SLFnD16K4yJeitt2

Thanks a lot,
David Hrbáč
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos