Re: [gentoo-user] Re: Digest verification failed:
On April 8, 2016 4:15:04 AM GMT+02:00, Valmor de Almeida wrote: >On Thu, Apr 7, 2016 at 9:14 PM, R0b0t1 wrote: > >> Use webrsync or webrsync-gpg and see if the problem persists. >> > >Waited for a few hours and tried both > > emerge --sync > >and > > emerge-webrsync > >still problematic. > >Thanks for the replies. > >-- >Valmor Try downloading a snapshot from the gentoo servers? -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] Re: Digest verification failed:
On Thu, Apr 7, 2016 at 9:14 PM, R0b0t1 wrote: > Use webrsync or webrsync-gpg and see if the problem persists. > Waited for a few hours and tried both emerge --sync and emerge-webrsync still problematic. Thanks for the replies. -- Valmor
Re: [gentoo-user] Re: Digest verification failed:
Use webrsync or webrsync-gpg and see if the problem persists.
[gentoo-user] Re: Digest verification failed:
On Fri, 8 Apr 2016 09:26:07 +1000 Sam Jorna wrote: > On Thu, Apr 07, 2016 at 06:52:20PM -0400, Valmor de Almeida wrote: > >Hello, > >I have done several > >emerge --sync > >today but the digest verification problem below does not go away. > >Any thoughts? > >Thank you. > > This has been reported in Bug 579204 [0] and, as far as I am aware, > was either caused by bad timing between commits and rsync metadata > generation or some other factor in generating the metadata being > pushed out to rsync servers; though from what I've seen it seems to > only affect some mirrors. > > 0: https://bugs.gentoo.org/579204 If anyone knows of a good rsync mirror, please post. (This has hit me in the middle of migration to plasma 5, perfect timing.)
Re: [gentoo-user] Digest verification failed:
On Thu, Apr 07, 2016 at 06:52:20PM -0400, Valmor de Almeida wrote: >Hello, >I have done several >emerge --sync >today but the digest verification problem below does not go away. >Any thoughts? >Thank you. This has been reported in Bug 579204 [0] and, as far as I am aware, was either caused by bad timing between commits and rsync metadata generation or some other factor in generating the metadata being pushed out to rsync servers; though from what I've seen it seems to only affect some mirrors. 0: https://bugs.gentoo.org/579204 -- Sam Jorna (wraeth) GnuPG Key: D6180C26 signature.asc Description: Digital signature
[gentoo-user] Digest verification failed:
Hello, I have done several emerge --sync today but the digest verification problem below does not go away. Any thoughts? Thank you. -- Valmor >>> Fetching (165 of 221) media-libs/mesa-11.0.6::gentoo !!! Digest verification failed: !!! /usr/portage/media-libs/mesa/mesa-.ebuild !!! Reason: Failed on SHA256 verification !!! Got: e2eb88ce00f4e8f37a940c982bfc7c38d5ed015477caa3397508792ca620968d !!! Expected: eb7a5581c6001e07d6a2a817f023cfd005ee45cda03cfca498e825bf3d3104a4 >>> Failed to emerge media-libs/mesa-11.0.6
[gentoo-user] Re: NVMe drive and grub
pe...@prh.myzen.co.uk wrote on 2016-04-07 17:24: > I have a new box with an NVMe SSD drive attached to the PCI bus via an M.2 > interface. The drive shows up as /dev/nvme0n1, with partitions > /dev/nvme0n1p1, /dev/nvme0n1p2, ... > > After following the instructions in the handbook for a UEFI system, I get as > far as a kernel panic. Grub finds the kernel and starts it, but it seems to > be passing a null root device name. > > Can anyone offer some advice to help me get past this? Make sure you have BLK_DEV_NVME compiled into your kernel (not as a module), and that you pass the right device name as a root FS to the kernel. It might also help to use a very recent kernel. FWIW, I'm writing this from a laptop that boots from two NVMe devices in RAID 1 configuration, with kernel 4.4.5. -- Remy
Re: [gentoo-user] NVMe drive and grub
On Thu, Apr 7, 2016 at 5:24 PM, wrote: > Hello list, > > I have a new box with an NVMe SSD drive attached to the PCI bus via an M.2 > interface. The drive shows up as /dev/nvme0n1, with partitions > /dev/nvme0n1p1, /dev/nvme0n1p2, ... > > After following the instructions in the handbook for a UEFI system, I get as > far as a kernel panic. Grub finds the kernel and starts it, but it seems to > be passing a null root device name. > What is in your grub.conf? Have you thought about adding an initramfs and letting it drop you to its rescue shell so that you can investigate?
[gentoo-user] NVMe drive and grub
Hello list, I have a new box with an NVMe SSD drive attached to the PCI bus via an M.2 interface. The drive shows up as /dev/nvme0n1, with partitions /dev/nvme0n1p1, /dev/nvme0n1p2, ... After following the instructions in the handbook for a UEFI system, I get as far as a kernel panic. Grub finds the kernel and starts it, but it seems to be passing a null root device name. Can anyone offer some advice to help me get past this? A few pints of Wainwright go to the winner. Conditions apply :-) Rgds Peter
