Welcome! Log In Create A New Profile

Advanced

Debian-3.17.0-oxnas boot fails: " udev requires a kernel >= 2.6.32, not started ... failed!"

Posted by Dieter 
Hello,

I have a POGO-B01 and I successfully installed ALARM.
I also installed debian-wheezy-pogoplugv3pro-shv.1.clean.tar.gz from from http://pogoplug.cwsurf.de/forum/portal.php?ap=2&announcement=0 which is booting fine.
However, I would like to have a more recent version and now prepared another USB stick with:
Quote

Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2

Unfortunately, I receive error message over the serial port as follows:

...
[   15.420000] VFS: Mounted root (ext3 filesystem) on device 8:1.
[   16.020000] devtmpfs: mounted
[   16.020000] Freeing init memory: 140K
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[FAIL] udev requires a kernel >= 2.6.32, not started ... failed!
 failed!
[ ok ] Activating swap...done.
[....] Checking root file system...fsck from util-linux 2.20.1
rootfs: clean, 11971/427392 files, 124707/1708984 blocks
done.
[   43.700000] EXT3 FS on sda1, internal journal
[ ok ] Cleaning up temporary files... /tmp /lib/init/rw.
[ ok ] Loading kernel modules...done.
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.20.1
done.
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables ...done.
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Cannot find device "eth0"
Bind socket to interface: No such device
Failed to bring up eth0.
done.
[ ok ] Starting rpcbind daemon....
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Cleaning up temporary files....
[....] startpar: service(s) returned failure: udev mountall-bootclean.sh procps [FAILnfs-bootclean.sh ... failed!
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1786 (syslogd)
. ok
[ ok ] Starting rpcbind daemon...[....] Already running..
[ ok ] Starting system message bus: dbus.
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting NFS common utilities: statd idmapd.
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1783 (klogd)
. ok
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[FAIL] startpar: service(s) returned failure: ssh ... failed!

Debian GNU/Linux 7 debian ttyS0

debian login:

I can log in over the serial connection, but the network is not configured.
Can anybody please help me figuring out what is going wrong?

Regards, Dieter
Re: Debian-3.17.0-oxnas boot fails: " udev requires a kernel >= 2.6.32, not started ... failed!"
April 09, 2015 03:45PM
Dieter,


> [FAIL] udev requires a kernel >= 2.6.32, not
> started ... failed!

It looks like you are still running the old kernel. Please do these:

- Decribe what you did to boot with new rootfs. Did you change any of u-boot envs? or just prepare the rootfs and then boot with it?
- Post the entire serial log.

-bodhi
===========================
Forum Wiki
bodhi's corner
Hello,

thank you for the quick response.
My buffer seems not big enough, this is all I have:

[    0.270000] Calibrating local timer... 349.99MHz.
[    0.340000] CPU1: Booted secondary processor
[    0.440000] Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
[    0.670000] Brought up 2 CPUs
[    0.680000] SMP: Total of 2 processors activated (558.69 BogoMIPS).
[    0.690000] tmpfs: No value for mount option 'mode'
[    0.690000] devtmpfs: initialized
[    0.700000] NET: Registered protocol family 16
[    0.700000] Number of DMA channels = 4, version = 4
[    0.710000] Reserving a DMA channel for DirectRAID
[    0.710000] Allocating 389 SRAM generic DMA descriptors
[    0.730000] bio: create slab <bio-0> at 0
[    0.740000] SCSI subsystem initialized
[    0.740000] usbcore: registered new interface driver usbfs
[    0.750000] usbcore: registered new interface driver hub
[    0.750000] usbcore: registered new device driver usb
[    0.780000] NET: Registered protocol family 2
[    0.780000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.790000] Switched to NOHz mode on CPU #0
[    0.790000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.790000] Switched to NOHz mode on CPU #1
[    0.800000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.810000] TCP: Hash tables configured (established 4096 bind 4096)
[    0.810000] TCP reno registered
[    0.820000] NET: Registered protocol family 1
[    0.820000] Create fragment cache
[    0.850000] fuse init (API version 7.12)
[    0.850000] msgmni has been set to 244
[    0.860000] alg: No test for stdrng (krng)
[    0.860000] io scheduler noop registered
[    0.860000] io scheduler anticipatory registered
[    0.870000] io scheduler deadline registered
[    0.870000] io scheduler cfq registered (default)
[    0.900000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.910000] serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A
[    0.920000] brd: module loaded
[    0.930000] loop: module loaded
[    0.940000] ox820sata: OX820 sata core.
[    0.940000] scsi0 : oxnassata
[    0.940000] scsi1 : oxnassata
[    0.950000] ata1: SATA max UDMA/133 irq 50
[    0.950000] ata2: SATA max UDMA/133 irq 50
[    0.960000] ox820sata: reseting SATA core
[    1.320000] ata1: SATA link down (SStatus 0 SControl 300)
[    1.320000] ox820sata: reseting SATA core
[    1.680000] ata2: SATA link down (SStatus 0 SControl 300)
[    1.680000] tun: Universal TUN/TAP device driver, 1.6
[    1.690000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    1.690000] NAND: Page read time 40ms
[    1.700000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[    1.710000] Scanning device for bad blocks
[    1.710000] Bad eraseblock 73 at 0x000000920000
[    1.730000] Bad eraseblock 303 at 0x0000025e0000
[    1.740000] Bad eraseblock 324 at 0x000002880000
[    1.750000] Bad eraseblock 373 at 0x000002ea0000
[    1.760000] Bad eraseblock 494 at 0x000003dc0000
[    1.780000] Bad eraseblock 737 at 0x000005c20000
[    1.790000] Bad eraseblock 759 at 0x000005ee0000
[    1.810000] Bad eraseblock 998 at 0x000007cc0000
[    1.810000] Bad eraseblock 999 at 0x000007ce0000
[    1.820000] Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit":
[    1.830000] 0x000000000000-0x000000e00000 : "boot"
[    1.830000] 0x000000e00000-0x000008000000 : "rootfs"
[    1.840000] UBI: attaching mtd2 to ubi0
[    1.840000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    1.850000] UBI: logical eraseblock size:    129024 bytes
[    1.860000] UBI: smallest flash I/O unit:    2048
[    1.860000] UBI: sub-page size:              512
[    1.870000] UBI: VID header offset:          512 (aligned 512)
[    1.870000] UBI: data offset:                2048
[    2.280000] UBI: attached mtd2 to ubi0
[    2.280000] UBI: MTD device name:            "rootfs"
[    2.290000] UBI: MTD device size:            114 MiB
[    2.290000] UBI: number of good PEBs:        904
[    2.300000] UBI: number of bad PEBs:         8
[    2.300000] UBI: max. allowed volumes:       128
[    2.300000] UBI: wear-leveling threshold:    4096
[    2.310000] UBI: number of internal volumes: 1
[    2.310000] UBI: number of user volumes:     1
[    2.320000] UBI: available PEBs:             0
[    2.320000] UBI: total number of reserved PEBs: 904
[    2.330000] UBI: number of PEBs reserved for bad PEB handling: 9
[    2.330000] UBI: max/mean erase counter: 2/1
[    2.340000] UBI: image sequence number: 0
[    2.340000] UBI: background thread "ubi_bgt0d" started, PID 306
[    2.340000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.340000] oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
[    2.340000] oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
[    2.370000] oxnas-ehci oxnas-ehci.0: irq 39, io mem 0x00000000
[    2.390000] oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00
[    2.390000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.400000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.400000] usb usb1: Product: OXNAS EHCI Host Controller
[    2.410000] usb usb1: Manufacturer: Linux 2.6.31.6_SMP_820 ehci_hcd
[    2.420000] usb usb1: SerialNumber: usb
[    2.420000] usb usb1: configuration #1 chosen from 1 choice
[    2.430000] hub 1-0:1.0: USB hub found
[    2.430000] hub 1-0:1.0: 2 ports detected
[    2.440000] Initializing USB Mass Storage driver...
[    2.440000] usbcore: registered new interface driver usb-storage
[    2.450000] USB Mass Storage support registered.
[    2.450000] usbcore: registered new interface driver libusual
[    2.460000] mice: PS/2 mouse device common for all mice
[    2.460000] usbcore: registered new interface driver hiddev
[    2.470000] usbcore: registered new interface driver usbhid
[    2.480000] usbhid: v2.6:USB HID core driver
[    2.480000] TCP cubic registered
[    2.480000] NET: Registered protocol family 10
[    2.490000] lo: Disabled Privacy Extensions
[    2.490000] NET: Registered protocol family 17
[    2.500000] RPC: Registered udp transport module.
[    2.500000] RPC: Registered tcp transport module.
[    2.510000] Waiting for root device /dev/sda1...
[    2.750000] usb 1-1: new high speed USB device using oxnas-ehci and address 2
[    2.900000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[    2.900000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.910000] usb 1-1: Product: USB2.0 Hub
[    2.910000] usb 1-1: configuration #1 chosen from 1 choice
[    2.920000] hub 1-1:1.0: USB hub found
[    2.930000] hub 1-1:1.0: 4 ports detected
[    3.210000] usb 1-1.4: new high speed USB device using oxnas-ehci and address 3
[    3.320000] usb 1-1.4: New USB device found, idVendor=23a9, idProduct=ef18
[    3.320000] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.330000] usb 1-1.4: Product: DISK
[    3.330000] usb 1-1.4: Manufacturer: USB
[    3.340000] usb 1-1.4: configuration #1 chosen from 1 choice
[    3.340000] scsi2 : SCSI emulation for USB Mass Storage devices
[    8.350000] scsi 2:0:0:0: Direct-Access     SCSI     DISK429          1.00 PQ: 0 ANSI: 4
[    8.360000] sd 2:0:0:0: [sda] 15759456 512-byte logical blocks: (8.06 GB/7.51 GiB)
[    8.370000] sd 2:0:0:0: [sda] Write Protect is off
[    8.370000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[    8.380000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[    8.390000]  sda: sda1 sda2
[    8.390000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[    8.400000] sd 2:0:0:0: [sda] Attached SCSI removable disk
[   15.420000] kjournald starting.  Commit interval 5 seconds
[   15.420000] EXT3 FS on sda1, internal journal
[   15.420000] EXT3-fs: recovery complete.
[   15.420000] EXT3-fs: mounted filesystem with writeback data mode.
[   15.420000] VFS: Mounted root (ext3 filesystem) on device 8:1.
[   16.020000] devtmpfs: mounted
[   16.020000] Freeing init memory: 140K
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[FAIL] udev requires a kernel >= 2.6.32, not started ... failed!
 failed!
[ ok ] Activating swap...done.
[....] Checking root file system...fsck from util-linux 2.20.1
rootfs: clean, 11971/427392 files, 124707/1708984 blocks
done.
[   43.700000] EXT3 FS on sda1, internal journal
[ ok ] Cleaning up temporary files... /tmp /lib/init/rw.
[ ok ] Loading kernel modules...done.
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.20.1
done.
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables ...done.
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Cannot find device "eth0"
Bind socket to interface: No such device
Failed to bring up eth0.
done.
[ ok ] Starting rpcbind daemon....
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Cleaning up temporary files....
[....] startpar: service(s) returned failure: udev mountall-bootclean.sh procps [FAILnfs-bootclean.sh ... failed!
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1786 (syslogd)
. ok
[ ok ] Starting rpcbind daemon...[....] Already running..
[ ok ] Starting system message bus: dbus.
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting NFS common utilities: statd idmapd.
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1783 (klogd)
. ok
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[FAIL] startpar: service(s) returned failure: ssh ... failed!

Debian GNU/Linux 7 debian ttyS0

debian login: root
Password:
Last login: Sat Nov  1 00:34:50 PDT 2014 from 192.168.0.100 on pts/0
Linux debian 2.6.31.6_SMP_820 #6 SMP Thu Jun 14 19:49:57 CDT 2012 armv6l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@debian:~# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@debian:~#

I did not change any u-boot envs, as I don't understand this:
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
rootfstype=ext2

Points 2-4 of the guide I followed to my best knowledge.

"Bad eraseblock" does not sound good, does it?

Regards, Dieter



Edited 2 time(s). Last edit at 04/09/2015 03:55PM by Dieter.
Re: Debian-3.17.0-oxnas boot fails: " udev requires a kernel >= 2.6.32, not started ... failed!"
April 09, 2015 04:02PM
Dieter,

> Linux debian 2.6.31.6_SMP_820 #6 SMP Thu Jun 14
> 19:49:57 CDT 2012 armv6l

You are still running the old kernel in NAND. And I guess stock u-boot too. The only thing different is because the new rootfs is on USB, it was used. So you are still running in a hybrid mode: old kernel in NAND, new rootfs on USB.

I would suggest to install new u-boot to make it easier if you are not sure how to change u-boot envs to boot new kernel on USB. The envs change described in the rootfs release thread is not enough to run with the old installation (WarheadsSE's procedure).

-bodhi
===========================
Forum Wiki
bodhi's corner
Hello,

thanks again for you ongoing support.

I want to try to update u-boot, but please let me ask some questions:
- The update of march states:
Quote

"- both FDT and non-FDT kernel booting " But what means then instruction two: "2. The env image pogopro_uboot_env.img should only be flashed if your rootfs has FDT kernel. If your kernel is an older non-FDT kernel then do not flash this env image. If you plan to run with the new rootfs then flash this image. "
In the end, I can do this step and decide later if I want to use FDT or not? Does it matter?

- Where Do I find "WarheadsSE's procedure", in case I wanted to try this first?

- Also step 9 and 10, what do I do here? (I plan to flash from the shv wheezy system) Does it matter?

- In the end, do I have to decide now for FDT or not?

Sorry for being so cautious, but I don't want to brick the system.

Regards, Dieter
Re: Debian-3.17.0-oxnas boot fails: " udev requires a kernel >= 2.6.32, not started ... failed!"
April 10, 2015 03:20AM
Dieter,

> - The update of march states:
Quote

"- both FDT
> and non-FDT kernel booting

It means you can use a kernel that is non-FDT, or a kernel that is FDT. Either will work, but both need u-boot envs set up correctly if installing from stock.

> " But what means then
> instruction two: "2. The env image
> pogopro_uboot_env.img should only be flashed if
> your rootfs has FDT kernel. If your kernel is an
> older non-FDT kernel then do not flash this env
> image. If you plan to run with the new rootfs then
> flash this image. "
>In the end, I can do
> this step and decide later if I want to use FDT or
> not?

No, you can not wait. You need to use the new rootfs.

> - Where Do I find "WarheadsSE's procedure", in
> case I wanted to try this first?

It is no longer supported by WarheadsSE, so I'd not try it.

> - In the end, do I have to decide now for FDT or
> not?

Yes

> Sorry for being so cautious, but I don't want to
> brick the system.

There is a rescue mechanism (SATA booting), so you could brick this box, but you can always recover.

So the bottom line is you need to do this:
http://forum.doozan.com/read.php?2,20686,21008#msg-21008

The best approach is to install rootfs and u-boot at the same time. And if you are really cautious, don't reboot right away, post the entire log of your installation here and I will look it over to verify that you've done it correctly or missed some steps.

-bodhi
===========================
Forum Wiki
bodhi's corner
Ok, thank you. I will have a try at the weekend. (You don't plan a longer holiday at the moment, do you?)
What do you mean by "at the same time"?
My plan is to boot the shv image, do all the uboot installation for FDT and post the output.
At the same time, on a different machine, I will prepare a FDT rootfs on a Stick and use it for the next reboot.
Is this ok?

Regards, Dieter
Re: Debian-3.17.0-oxnas boot fails: " udev requires a kernel >= 2.6.32, not started ... failed!"
April 10, 2015 05:00AM
Dieter,

> My plan is to boot the shv image, do all the uboot
> installation for FDT and post the output.

Yes.

> At the same time, on a different machine, I will
> prepare a FDT rootfs on a Stick and use it for the
> next reboot.
> Is this ok?

And yes. That's what I meant!

-bodhi
===========================
Forum Wiki
bodhi's corner
Hello Bodhi,

I did the uboot update, all the checks looked good. however I could not rewrite the MAC address:
root@pogoplug:/tmp# fw_printenv ethaddr
ethaddr=5e:2b:15:71:ec:b6
root@pogoplug:/tmp# cat /etc/network/interfaces | grep -i hwaddress
hwaddress ether 00:25:31:02:AE:F5
root@pogoplug:/tmp# fw_setenv ethaddr '00:25:31:02:AE:F5'
Can't overwrite "ethaddr"
root@pogoplug:/tmp#

Now, I rebooted, this is what I see on the serial port:

U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:
Led:    GREEN
mii0
Main Loop
Waiting for PHY auto negotiation to complete... done
ENET Speed is 1000 Mbps - FULL duplex connection
Using mii0 device
host 192.168.180.44 is alive
Uncompressing Linux... done, booting the kernel.
and this on netcat:

U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  0 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
4109737 bytes read in 652 ms (6 MiB/s)
1953812 bytes read in 288 ms (6.5 MiB/s)
7029 bytes read in 226 ms (30.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
   Image Name:   Linux-3.3.17.0-oxnas-tld-1
   Created:      2015-04-08  20:29:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4109673 Bytes = 3.9 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
   Image Name:   initramfs-3.17.0-oxnas-tld-1
   Created:      2014-11-01   7:18:53 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    1953748 Bytes = 1.9 MiB
   Load Address: 60000000
   Entry Point:  60000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
   Booting using the fdt blob at 0x62c00000


Starting kernel ...
and this is it!

So not yet succeded? I hope I have no serious problem?

Have I missed something? I checked the uboot config and I did not see a difference!

Regards, Dieter
Re: Debian-3.17.0-oxnas boot fails: " udev requires a kernel >= 2.6.32, not started ... failed!"
April 11, 2015 03:05PM
Dieter,

> I did the uboot update, all the checks looked
> good. however I could not rewrite the MAC
> address:

Don't worry about that. It can be taken care later easily.

> Now, I rebooted, this is what I see on the serial
> port:
>
> U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for
> OXNAS

Very good!

> ## Booting kernel from Legacy Image at 60500000
> ...
> Image Name: Linux-3.3.17.0-oxnas-tld-1
> Created: 2015-04-08 20:29:16 UTC
> Image Type: ARM Linux Kernel Image
> (uncompressed)
> Data Size: 4109673 Bytes = 3.9 MiB
> Load Address: 60008000
> Entry Point: 60008000
> Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at
> 60e00000 ...
> Image Name: initramfs-3.17.0-oxnas-tld-1
> Created: 2014-11-01 7:18:53 UTC
> Image Type: ARM Linux RAMDisk Image (gzip
> compressed)
> Data Size: 1953748 Bytes = 1.9 MiB
> Load Address: 60000000
> Entry Point: 60000000
> Verifying Checksum ... OK
> ## Flattened Device Tree blob at 62c00000
> Booting using the fdt blob at 0x62c00000
>
>
> Starting kernel ...

So far everything looks good. At this point, you should be able to find the Pogo in the network. Look in the router to see if its dynamic IP was assigned, and log in with SSH. User password root/root.

Does any thing appear in serial console after this?

-bodhi
===========================
Forum Wiki
bodhi's corner
Hello,

It does not show up in the network. I can not access it.
Can I access it somehow via the serial link and check my uboot envs again?
I have an idea. (pro instead of classic dtb? Simly renaming the files did not work)

Regards, Dieter
Re: Debian-3.17.0-oxnas boot fails: " udev requires a kernel >= 2.6.32, not started ... failed!"
April 12, 2015 02:40AM
Dieter Wrote:
-------------------------------------------------------
> Hello,
>
> It does not show up in the network. I can not
> access it.
> Can I access it somehow via the serial link and
> check my uboot envs again?
> I have an idea. (pro instead of classic dtb? Simly
> renaming the files did not work)
>
> Regards, Dieter

Boot with serial console, you should see the error (if any) during rootfs mounting phase. And post the log here if you're not sure what the problem is.

-bodhi
===========================
Forum Wiki
bodhi's corner
Hello,

the above shown this is all the output I get, nothing more neither from netcat nor from console.
The dmesg file on the usb stick is still mentioning a 2.6.x kernel, therfore I assume it is old.

Without any more information, I am blind and don't know what to do. All I can try now is to set up a new stick, step by step. Maybe I did something wrong.

Probably my
dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
is set wrongly, but I copied the classic file to the pro and it did not help. And because I can not access the box at the moment, neither by serial nor by netcat, I can not fix the variable.

Is there another log file to look at?

Regards, Dieter
Re: Debian-3.17.0-oxnas boot fails: " udev requires a kernel >= 2.6.32, not started ... failed!"
April 12, 2015 03:33AM
Dieter

The reason you can't see anything is either the kernel could not start, or the rootfs mounting has problem. So do this: start serial console and neconsole like you did. But when the netconsole comes up, interrupt it, and at the u-boot prompt, disable netconsole (you can do this without worrying because you already have serial console working).

printenv preboot

this should show that
preboot=run preboot_nc

Now clear this preboot env so netconsole will not run the next time:
setenv preboot
saveenv
reset

Upon u-boot restarting because of that reset , there will be no netconsole, only serial console. So in serial console, any failure of starting kernel or mounting rootfs will be apparent.

If you are still not seeing any output in serial console, then the kernel could not start. In this case, get the output of printenv and post here.
printenv

And I might add, you now have u-boot installed successfully, so any problem is easy to fix. Don't try setting preboot env to anything, just clear it like I showed above with
setenv preboot

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 3 time(s). Last edit at 04/12/2015 04:36AM by bodhi.
Sorry, for causing so much trouble.

switching off netcat worked.

Now the serial console output while booting is:


U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
  Boot device: NAND
Attempting to set PLLA to 850 MHz ...
  plla_ctrl0 : 0000020a
  plla_ctrl1 : 00330000
  plla_ctrl2 : 0065008b
  plla_ctrl3 : 000000f1

PLLA Set


U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:
Led:    GREEN
mii0
Main Loop
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
4109737 bytes read in 652 ms (6 MiB/s)
1953812 bytes read in 288 ms (6.5 MiB/s)
7033 bytes read in 227 ms (29.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
   Image Name:   Linux-3.3.17.0-oxnas-tld-1
   Created:      2015-04-08  20:29:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4109673 Bytes = 3.9 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
   Image Name:   initramfs-3.17.0-oxnas-tld-1
   Created:      2014-11-01   7:18:53 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    1953748 Bytes = 1.9 MiB
   Load Address: 60000000
   Entry Point:  60000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
   Booting using the fdt blob at 0x62c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 67c4b000, end 67e27fd4 ... OK
   Loading Device Tree to 67c46000, end 67c4ab78 ... OK

Led:    GREEN

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

nothing more happens.

Interupting boot gives:
Hit any key to stop autoboot:  0
OX820> printenv
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run dt_bootcmd_usb
bootdelay=10
console=console=ttyS0,115200n8
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dtb_addr=0x62c00000
ethact=mii0
ethaddr=5e:2b:15:71:ec:b6
if_netconsole=ping $serverip
ipaddr=192.168.180.19
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
ncip=192.168.180.44
preboot_nc=run if_netconsole start_netconsole
serverip=192.168.180.44
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
stderr=serial
stdin=serial
stdout=serial
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
usb_device=0:1
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10

Environment size: 1216/131068 bytes
OX820>

Regards, Dieter
Re: Debian-3.17.0-oxnas boot fails: " udev requires a kernel >= 2.6.32, not started ... failed!"
April 12, 2015 04:35AM
Dieter,

> Sorry, for causing so much trouble.

No problem:)

> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
>
> nothing more happens.
>

This is the symtom that the kernel is not the right one. So retrace your step when you create the rootfs. Since you are setting u-boot envs to boot a FDT kernel, the uImage should be left as is, there is no need to append DTB to it as in step 4:

Quote

4. Create uImage with embbeded DTB to run with older u-boot. Please see Note 2 below if you are running this kernel witht the new U-Boot.

Pogo Pro vs. Pogo Classic: If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb below with ox820-pogoplug-classic.dtb.

cd /media/sdb1/boot
cp -a zImage-3.17.0-oxnas-tld-1 zImage-3.17.0-oxnas-tld-1.fdt
cat dts/ox820-pogoplug-pro.dtb >> zImage-3.17.0-oxnas-tld-1.fdt
mkimage -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n 'Linux-3.3.17.0-oxnas-tld-1' -d zImage-3.17.0-oxnas-tld-1.fdt uImage
sync

If you did step 4 then that was the problem. In any case, for expediency, just recreate to rootfs without doing step 4 on another Linux box, and try to boot with it. Monitor serial console output to see if there is any problem.

-bodhi
===========================
Forum Wiki
bodhi's corner
Oh, yes, you are very right, my mistake!

Did all again, voila! currently running upgrade, will fix the rest later.

THANK YOU!

Dieter
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: