new kernel 3.2 does not boot on the dockstar

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.
Topic locked

Re: new kernel 3.2 does not boot on the dockstar

Postby ax0r7ag0z » Wed Jan 25, 2012 7:39 pm

phdeez did you go for pepedog's files or for the rootfs?
Try one over the other!!
ax0r7ag0z
 
Posts: 38
Joined: Mon Aug 30, 2010 8:59 pm
Top

Re: new kernel 3.2 does not boot on the dockstar

Postby cyberic » Wed Jan 25, 2012 11:19 pm

$this->bbcode_second_pass_quote('WarheadsSE', 'M')y guess is the same "unable to allocate pty" problem

yes do the mkmod thing I suggested above, it solved the problem with another device I have.
what does ssh say with a -v flag?
Image
cyberic
 
Posts: 71
Joined: Sun Jan 15, 2012 11:26 pm
Top

Re: new kernel 3.2 does not boot on the dockstar

Postby WarheadsSE » Thu Jan 26, 2012 1:22 pm

See viewtopic.php?f=29&t=2334
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm
Top

Re: new kernel 3.2 does not boot on the dockstar

Postby phdeez » Thu Jan 26, 2012 6:28 pm

$this->bbcode_second_pass_quote('cyberic', '')$this->bbcode_second_pass_quote('WarheadsSE', 'M')y guess is the same "unable to allocate pty" problem

yes do the mkmod thing I suggested above, it solved the problem with another device I have.
what does ssh say with a -v flag?


Holy crap, that worked!!!!!

Although, I will say I had to "disable" using a pty by ssh'ing from my tomato router with a -T option (-T Don't allocate a pty). I could then use ls commands.

Then, I used the info from your post earlier

$this->bbcode_second_pass_quote('cyberic', 'Y')ou're missing a /dev/pts or /dev/ptmx device
you should be able to type in commands anyway (try ls)
or, do a:
ssh <dockstar_ip> /bin/mknod /dev/ptmx c 5 2
or try to mount devpts on /dev/pts


mknod /dev/ptmx c 5 2

and viola, I could login and get "normal" ssh responses... I did do an ls under /dev/ and saw there was a /dev/pts already there. Although none of my block devices are present (sdX#). I tried to mknod sda1, sdb1 with no success

I'm doing much better than yesterday! Thanks for the help ax0r7ag0z, WarheadsSE & cyberic!
phdeez
 
Posts: 25
Joined: Wed Apr 07, 2010 3:05 am
Top

Re: new kernel 3.2 does not boot on the dockstar

Postby cyberic » Thu Jan 26, 2012 7:42 pm

$this->bbcode_second_pass_quote('', 'A')lthough none of my block devices are present (sdX#). I tried to mknod sda1, sdb1 with no success

Great progress indeed. no success? what happens with the mknod command?
Image
cyberic
 
Posts: 71
Joined: Sun Jan 15, 2012 11:26 pm
Top

Re: new kernel 3.2 does not boot on the dockstar

Postby phdeez » Fri Jan 27, 2012 3:59 am

$this->bbcode_second_pass_quote('cyberic', '')$this->bbcode_second_pass_quote('', 'A')lthough none of my block devices are present (sdX#). I tried to mknod sda1, sdb1 with no success

Great progress indeed. no success? what happens with the mknod command?


I guess "no success" wasn't exactly correct... it was more like confusing output... Since I used:
$this->bbcode_second_pass_code('', 'mknod /dev/sda1 b 8 1
mknod /dev/sdb1 b 8 2
mknod /dev/sdc1 b 8 3')
Obviously, the problem was with my lack of understanding the mknod command and how it was supposed to work.

This made "real sda1" show up regardless of the mount identifier (/dev/sda1, /dev/sdb1, /dev/sdc1, etc)

After I looked into the real workings of mknod, I was able to add my other physical drives that were showing up in dmesg.... AND I was able to get some fdisk -l output which I was unable to do earlier. A little googling led me here.

What in the world happened to all the connections between /dev/ and the physical drives? Crazy upgrade action here... Here's the "ls -al" output from my /dev/ directory now...

$this->bbcode_second_pass_code('', 'brw-r--r-- 1 root root 8, 0 Jan 26 21:37 sda
brw-r--r-- 1 root root 8, 1 Jan 26 03:14 sda1
brw-r--r-- 1 root root 8, 16 Jan 26 21:37 sdb
brw-r--r-- 1 root root 8, 17 Jan 26 21:37 sdb1
brw-rw---- 1 root disk 8, 32 Jan 1 1970 sdc
brw-r--r-- 1 root root 8, 33 Jan 26 21:41 sdc1
brw-rw---- 1 root disk 8, 34 Jan 1 1970 sdc2
')

Here is another useful link to find other things you're missing from dev (ie translate what "mknod ... b X Y" means and how to use it).

Thanks again for your guidance cyberic, ax0r7ag0z and pepedog for hosting!
phdeez
 
Posts: 25
Joined: Wed Apr 07, 2010 3:05 am
Top

Re: new kernel 3.2 does not boot on the dockstar

Postby cyberic » Fri Jan 27, 2012 9:10 am

$this->bbcode_second_pass_quote('', 'W')hat in the world happened to all the connections between /dev/ and the physical drives?

The 'connections' is normally handled by udev, which seems to have problems right know.
I think a fix in on the way, I don't really know whre we are now.... anyone?
Image
cyberic
 
Posts: 71
Joined: Sun Jan 15, 2012 11:26 pm
Top

Re: new kernel 3.2 does not boot on the dockstar

Postby Sagittarius » Fri Jan 27, 2012 12:21 pm

Same issue on Goflex Net :(

$this->bbcode_second_pass_code('', '# nc -l -u -p 6666

U-Boot 2010.09 (Oct 23 2010 - 11:53:10)
Marvell-GoflexNet by Jeff Doozan, Peter Carmichael
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 219 MiB
UBI: number of good PEBs: 1751
UBI: number of bad PEBs: 1
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 1730
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..

Reset IDE: Bus 0: OK Bus 1: OK
Device 0: Model: ST9500325AS Firm: 0002BSM1 Ser#: 6VEVJ8RJ
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Device 1: Model: ST9500325AS Firm: 0002BSM1 Ser#: 6VEVJ8RJ
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Loading file "/boot/uImage" from ide device 0:1 (hda1)
2952192 bytes read
Loading file "/boot/uInitrd" from ide device 0:1 (hda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.2.1-1-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2952128 Bytes = 2.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...
')

And then nothing. The /dev/ folder is almost empty.
Dockstar / GoFlexNet booting on NFS / Odroid C1+ / Odroid C2
Sagittarius
 
Posts: 61
Joined: Mon Nov 14, 2011 9:21 pm
Location: France
Top

Re: new kernel 3.2 does not boot on the dockstar

Postby Sagittarius » Fri Jan 27, 2012 3:16 pm

$this->bbcode_second_pass_quote('ax0r7ag0z', 'I')nstead 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!!


Thank you to mention it.
I've managed to get my audiophile mpd server back on my GoFlex Net with just /boot/uImage
and /lib/modules/3.1.7-2-ARCH 3.2.1-1-ARCH extramodules-3.1-ARCH.
Dockstar / GoFlexNet booting on NFS / Odroid C1+ / Odroid C2
Sagittarius
 
Posts: 61
Joined: Mon Nov 14, 2011 9:21 pm
Location: France
Top

Re: new kernel 3.2 does not boot on the dockstar

Postby phdeez » Fri Jan 27, 2012 4:41 pm

$this->bbcode_second_pass_quote('Sagittarius', '')$this->bbcode_second_pass_quote('ax0r7ag0z', 'I')nstead 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!!


Thank you to mention it.
I've managed to get my audiophile mpd server back on my GoFlex Net with just /boot/uImage
and /lib/modules/3.1.7-2-ARCH 3.2.1-1-ARCH extramodules-3.1-ARCH.


I ended up doing this, and overwriting pepedog's files. Apparently, the 3.1.7-2 modules/kernel work fine with udev, since my /dev/ directory is filled up with all kinds of stuff. Also, more importantly, my cifs mounting is working properly now (for some reason it didn't on 3.1.4, even after a insmod of the cifs module.

Also, I had some sort of weird problem with downloading nzb files via https, and my ssl connection to my newsgroup server wasn't working on 3.1.4, but both work fine on 3.1.7!
phdeez
 
Posts: 25
Joined: Wed Apr 07, 2010 3:05 am
Top
PreviousNext
Topic locked

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 2 guests

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group    © Arch Linux ARM