core.db will not sync and entropy

[danagain]

Hello forum,

Thank you for taking the time to look at this post. I am brand new to alarm and Arch but I am very motivated to learn and become proficient

So, I was very excited to make use of an old PogoPro. But when it comes time to -Syy I get this...

error: failed retrieving file 'core.db' from mirror.archlinuxarm.org : Connection time-out
error: failed to update core (download library error)

The rest of the databases update with no problem.

I have run the manual filesystem update, pacman -Syu --ignore filesystem && pacman -S filesystem --force, as well as, pacman -Syu --ignore filesystem && rm -rf /var/run /var/lock && \pacman -S filesystem.

I also followed the instructions that seemed useful at, All PLX based chips - Important Upgrade Note [updated], thread but still feel as though I may have missed something there.

So I seem stuck at the moment and was wondering if anyone can speed me along. I was able to make things work in Arch by adding ipv6.disable=1 to the kernel line in the /boot/grub/menu.lst, but I am not sure how to find a similar file in alarm.

And also, if anyone knows a magic spell for generating enough entropy to make pacman-key --init work I would be very grateful to learn it.

Thanks very much.

[WarheadsSE]

pacman-key init is not necessary at this time, but dd'ing a large file to /dev/null works rather well.

Grub is not used on ARM, so that method isn't going to work.

[danagain]

Thank you for helping.

What about poor core.db. Is there somewhere else I can switch off ipv6? Is that what is preventing the sync? Or is it my profound newness? I suspect the latter. Whatever it is, I am greatly hobbled by it. I got this when trying to install mutt, for instance...

error: failed retrieving file 'mime-types-8-1-any.pkg.tar.xz' from mirror.archlinuxarm.org : Connection time-out
warning: failed to retrieve some files from extra
mutt-1.5.21-6-arm 1134.4 KiB 1346K/s 00:01 [######################] 100%
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.


I am dying to get this going and am much more driven to make this work at the moment than I am my laptop with arch.

Thank you for the tip on entropy. I am going to get on that.

Dan.

[WarheadsSE]

This should help: https://wiki.archlinux.org/index.php/IPv6

[danagain]

Thank you,

I had just reached a sort of alarm version of St. John's Dark Night of The Soul, when I realized that maybe someone had thrown a rope down.

The only thing I was able to do was add noipv6rs to /etc/dhcpcd.conf.

I have to admit that despite my best efforts, I have not been able to locate the boot configuration file so that I can add ipv6.disable=1 to the kernel line. I also have to admit that the only two real revelations that I have experienced today are that 1: alarm uses u-boot, and finally 2: my oxnas plug does not use u-boot.

I also spent much of yesterday trying to get enough mental traction to try your suggestion for creating entropy with 'dd'. I am going to have to work on that; meanwhile, if I can get core.db updated and everything going, I will feel fortunate that we do not presently need to have the keyring up and fed.

So I still can't figure out how to disable ipv6, may I please have more help?

Thanks again.

D.

[WarheadsSE]

The oxnas plugs do use uboot. What problem are you having with that?

[danagain]

Thanks again,

I realize that I am misunderstanding the description of how the bootloader and the oxnas device work together on the 'platforms' page. Is uboot installed alongside whatever was originally on the memory in the pogoplug on sdb1?

My simple problem is that I don't know how to find the configuration file for the bootloader that has the kernel line.

Also, I am trying to install the OS to another drive right now using Arch and I am getting a "301 Moved Permanently" response when I try to connect to wget http://archlinux.org/os/ArchLinuxARM-ox ... est.tar.gz and then a 404.

Thank you for taking the time to help.

D.

[karog]

$this->bbcode_second_pass_quote('danagain', 'A')lso, I am trying to install the OS to another drive right now using Arch and I am getting a "301 Moved Permanently" response when I try to connect to wget http://archlinux.org/os/ArchLinuxARM-ox ... est.tar.gz and then a 404.
D.

[danagain]

Karog;

I am sure that I must have had the URL wrong. I finally was able to return to the project today and was able to prepare two drives from the re-installation page with no problem. Thank you for taking the time to help out.

WarheadsSE:

As I said, I was able to use the re-installation instructions no problem. Thank you so much for such a simple and elegant way to get that done. I feel a lot better knowing that I can fall back on that. I am still stuck though. coredb does not want to sync. I tried to address the issue in /etc/pacman.d/mirrorlist and /etc/pacman.conf by un-commenting the U.S. servers in the former and changing to PackageOptional in relation to core in the latter. It was all I could find or think to do. I also ran the scripts for the manual filesystem upgrade from the Arch news page like last time. I know this thread will ultimately go down as a testament to my thickheadedness, but what am I missing? I pacman -Syu and core does not sync, the rest does, and then I am told that there is nothing to do. Yet I cannot, for instance, even get my hands on dbus because there are dependencies in the core that I need.

Thank you for your patience.

D.

[pepedog]

Can you try pacman -Syy