new kernel 3.2 does not boot on the dockstar

[kmihelich]

3.1.10 is in the repo now, booting on all devices. The kmod problem is still present, however.

[sputnik]

Not sure how useful it is, but I thought I would add some observations to this thread.
I have been running the 3.1.7-2-ARCH kernel on my dockstar without incidence for a few weeks now, it is great.
I have an early A.M. cron task that runs pacman -Suy --noconfirm (perhaps not so wise with bleeding edge Arch). Sure enough, like many others, my dockstar lunched after the kmod update (& 3.21? kernel).
I have a nightly Dirvish backup, so nothing concerns me much, I can restore anything in short order, saved to 45 days back.
I have fooled with this a bit though. Initially, I found that my ArchNumber had been set to 2097 and by correcting it to 2998, besides having my constant green indicator light again, I was also able to update to the new kernel/kmod and actually ssh in! However, I have tried various methods of updating, from my original 3.1.7... installation (with progs, configs, etc.) to starting from scratch from the wiki instructions and adding configs and reinstalling programs. Thanks for the heads up btw kmihelich, thought I was going crazy when it "updated" to the 3.10 kernel the last time. Anyhow, every time I find the same symptoms I cannot solve: bluetooth does not work and I had the same iptables problem that WarheadsSE spoke of here: http://archlinuxarm.org/forum/viewtopic.php?f=18&t=2329
All else worked fine. It appeared to me that some modules were not loading, obviously the bluetooth and iptables related modules. When I did a lsmod in the NEW kernel the only modules shown were: autofs4, ipv6, dm_mod and 1 other, maybe mv_cesa? That's it.
I've just restored again from original installation backup, did lsmod and I get this:
$this->bbcode_second_pass_code('', 'Module Size Used by
xt_multiport 1496 1
xt_tcpudp 1933 2
iptable_filter 962 1
ip_tables 9417 1 iptable_filter
x_tables 11726 4 xt_multiport,xt_tcpudp,iptable_filter,ip_tables
rfcomm 31147 4
bnep 7512 2
autofs4 21958 2
ipv6 254067 14
dm_mod 57749 3
btusb 10055 3
bluetooth 134986 27 rfcomm,bnep,btusb
rfkill 14388 2 bluetooth
mv_cesa 9021 0
')
Now I know that embedded modules don't show up in a lsmod listing, but it's suspicious that all the bluetooth and iptables modules show up in this listing. Incidentally, my bluetooth dongle isn't recognized by the 3.10 kernel as well (with a pacman -Suy update).
So I've disabled the auto-update for the time being and we're sticking with this. Bluetooth phone chimed in right away on boot
Thanks so much for all the hard work from the developers, I really enjoy my Dockstar/Alarm partnership. And I hope I am not just really stating the obvious here, just trying to help. I was going to try compiling the new kernel myself but it threw me a curve with needing ncurses-devel, which we don't have in the normal repos, of course I could have gotten it somehow. edit: Dang, should've done it on pc thru smb rather than thru ssh terminal, it's got ncurses-devel. Well, it's gone now.

[cyberic]

$this->bbcode_second_pass_quote('sputnik', 'I') have an early A.M. cron task that runs pacman -Suy --noconfirm

[WarheadsSE]

Generally speaking, I would say it's worth the time to do it once a week, by hand. Generally takes ~5 minutes, and is much safer.

As for the kmod issues, it's not recognizing the dependencies correctly, and thus you try to modprobe the module you find out it errors because all of it's supporting modules have disappeared.

[ygator]

When I do a pacman pacman -Syyu
I am asked the question: Replace module-init-tools with core/kmod?
I say no because you say kmod it is still broken.
I am then asked the question: kmod and module-init-tools are in conflict. Remove module-init-tools?
I again say no because of kmod.
I also am assuming you need either kmod or module-init-tools and since kmod is broke the only other choice is module-init-tools.
Then I get:
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: kmod and module-init-tools are in conflict

How do I go about upgrading while kmod is broke?

Thanks

[dock1]

Do we have by now some kind of "recommended recovery instructions" by now?

[BinaryJay]

Is there a fix for the modules in the works or is it just, well, broken from here on out? I can find surprisingly little mention of this particular type of problem in the greater community out there.

[WarheadsSE]

The problem is being looked into.

kmod is not generating the depmod output correctly, and thus the problem we are having. Also, this only occurs on the v5, and almost exclusively on the kirkwoods. Yet, in the build environment, it works and generates fine! Hence, the WTF moment.

[phdeez]

$this->bbcode_second_pass_quote('dock1', 'D')o we have by now some kind of "recommended recovery instructions" by now?

[ax0r7ag0z]

Thank you phdeez for giving me credit but I myself must give credit to hojnikb
for giving me the idea. I probably would have started from scratch if it wasn't for
him.

On the main subject now, should there be an "official" recovery thread?
I believe we could use the pogoplug software instead of a computer
and how could we get the latest fsck in there?