new kernel 3.2 does not boot on the dockstar

[phdeez]

Do you think it is possible to disable this on the repos for the time being? I went through the upgrade process on 2 last night and borked both of them...

I got the mtab error message and searching yielded a link to archlinux's main page saying a forced upgrade was required... link

Unfortunately, I did not look in the rest of the forum to see that dockstars were hosed.

[ax0r7ag0z]

Got it to boot and work by plugging the drive in a linux laptop,
deleting the 3.2 kernel, the modules folder and the kernel sources
and replacing them with pepedog's by untaring them in the "/" folder.
Everything is working fine now!! Kmod asks to be re-installed.

Waiting on a solid solution!!

Keep at it guys!!

[phdeez]

$this->bbcode_second_pass_quote('ax0r7ag0z', 'G')ot it to boot and work by plugging the drive in a linux laptop,
deleting the 3.2 kernel, the modules folder and the kernel sources
and replacing them with pepedog's by untaring them in the "/" folder.
Everything is working fine now!! Kmod asks to be re-installed.

Waiting on a solid solution!!

Keep at it guys!!

[ax0r7ag0z]

Sure thing!
I booted ubuntu and connected the drive to my laptop.
I downloaded those 2 files;

http://myplugbox.com/pkg/linux-3.1.4-2-arm.pkg.tar.xz
http://myplugbox.com/pkg/linux-headers- ... pkg.tar.xz

deleted

/boot/
/lib/modules/

and extracted the tars into "/" overwriting duplicates.

I then did a

fsck -f -y -v /dev/"partition"

which fixed all the file errors and then plugged the drive to my dockstar
and powered on!! To my amazement, i just had to fix fstab to make my
second partition mountable again!!

Instead of peppedog's files, you could try getting /boot and /lib/modules
from http://archlinuxarm.org/os/ArchLinuxARM ... est.tar.gz
as it is fairly recent!!

[phdeez]

Man, this helped alot!! Although, I'm not "completely" back to normal, the unit boots, I can ping it and at least 2 services are working properly (sickbeard and couchpotato). Since both of those are working I figured ssh would work, but it's only half-working.

I can ssh to the device, and if I enter the *wrong* password it errors out immediately but, if I enter the correct password it just "sits" there (waited >3mins). Any idea on that? I have a serial cable and I could connect that, but I'd prefer not to take it apart just yet...

[WarheadsSE]

My guess is the same "unable to allocate pty" problem

[phdeez]

WarheadsSE: any suggested solution?

[WarheadsSE]

unfortunately, No. I've had no issues so far with that, but it is cropping up across multiple platforms.

[phdeez]

I'll connect via serial and make sure that is the error I'm receiving... Let's say it is... are we talking about a complete system reinstall?

[WarheadsSE]

I insinuated I don't know didn't I