| View previous topic :: View next topic |
| Author |
Message |
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
 Posted: Thu Apr 04, 2019 5:49 pm Post subject: Can't boot anymore my Raspberry Pi 2 [SOLVED] |
 |
|
Hi,
I have Raspberry Pi 2 Model B V1.1.
I have installed on it Gentoo linux system more than a year.
Suddenly I can't boot it a few days ago.
I can't remember what I did to get this error. Maybe I did run 'genkernel all' on it to get a newer kernel installed.
I can mount the SD card from this Raspberry Pi on my laptop which running Gentoo linux too.
I have access to the /boot and /root partition of this SD card.
What can I do to recover the Gentoo system on SD card and get it booted again?
_________________
Best, Pali
Last edited by paul_chany on Sun Apr 07, 2019 4:51 pm; edited 1 time in total |
|
| Back to top |
|
 |
Jaglover
Watchman
Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana
|
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Thu Apr 04, 2019 6:13 pm Post subject: |
|
|
| Jaglover wrote: | | I'd restore from backup. (I make backups of all my Pi SD cards after they work the way I want. SD card, as a hard drive, can die any time.) |
Wise advice. Unfortunately I have no backup.
_________________
Best, Pali |
|
| Back to top |
|
|
Logicien
Veteran
Joined: 16 Sep 2005
Posts: 1555
Location: Montréal
|
| Posted: Thu Apr 04, 2019 6:48 pm Post subject: |
|
|
Are you sure your boot FAT partition is up to date. Was it mounted in /boot when you did the last upgrade? If uBoot have change the data in this partition must reflect the upgrade. It can be some kernel parameters in /boot/cmdline.txt and/or in /boot/config.txt who prevent the boot. Is your sd card still good?
_________________
Paul |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54585
Location: 56N 3W
|
| Posted: Thu Apr 04, 2019 7:41 pm Post subject: |
|
|
paul_chany,
Describe what happens when you boot.
You should get 10 seconds of rainbow, then the rainbow is cleared.
If it sticks on the rainbow, bootcode.bin cannot be read.
When the rainbow disappears, what happens depends on your kernel setup.
It may go almost straight to text, if the console is built into the kernel.
If the console driver is a loadable module, you won't get any output until root is mounted.
I would be surprised if was useful on a raspberry pi.
Maybe with some very careful configuration?
How does it know what CPUs to build for and what *.dtb to install.
There's more but that's enough.
The output of
the content of config.txt and cmdline.txt would be good too.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54585
Location: 56N 3W
|
| Posted: Thu Apr 04, 2019 7:43 pm Post subject: |
|
|
Moved from Kernel & Hardware to Gentoo on ARM.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Fri Apr 05, 2019 4:12 am Post subject: |
|
|
| Logicien wrote: | | Are you sure your boot FAT partition is up to date. Was it mounted in /boot when you did the last upgrade? If uBoot have change the data in this partition must reflect the upgrade. It can be some kernel parameters in /boot/cmdline.txt and/or in /boot/config.txt who prevent the boot. Is your sd card still good? |
I am not sure mine boot FAT partition is up to date.
I did not mount it manually when did the last upgrade, but 'genkernel all' can mount the boot partition automatically.
Because I can mount this SD card to my laptop Gentoo system, I did copy of the boot and root partitions to my laptop.
So have here the content of the cmdline.txt file:
| Code: | dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p3 rootf
stype=ext4 elevator=deadline rootwait |
and the config.txt file:
| Code: | lcd_rotate=2
# Overclocking tp Medium
arm_freq=900
core_freq=333
sdram_freq=450
over_voltage=2
force_turbo=1
gpu_mem=16 |
I do not see in both file any kernel parameters out there.[/code]
I think my SD card is still in operational condition.
_________________
Best, Pali |
|
| Back to top |
|
|
Irre
Guru
Joined: 09 Nov 2013
Posts: 434
Location: Stockholm
|
| Posted: Fri Apr 05, 2019 6:17 am Post subject: |
|
|
| When I had similar problem I run "fsck /dev/mmcblk0p2" etc from another linux system. FAT-partition kan be repaired from Windows. It helped me. |
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Fri Apr 05, 2019 9:36 am Post subject: |
|
|
| Irre wrote: | | When I had similar problem I run "fsck /dev/mmcblk0p2" etc from another linux system. FAT-partition kan be repaired from Windows. It helped me. |
I did followings to check filesystems on partitions as root user:
| Code: | NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465,8G 0 disk
├─sda1 8:1 0 2M 0 part
├─sda2 8:2 0 511M 0 part
├─sda3 8:3 0 510M 0 part [SWAP]
└─sda4 8:4 0 464,8G 0 part /
sdb 8:16 1 29,8G 0 disk
├─sdb1 8:17 1 100M 0 part
├─sdb2 8:18 1 500M 0 part
└─sdb3 8:19 1 29,2G 0 part
sr0 11:0 1 1024M 0 rom
|
| Code: | fsck from util-linux 2.33
e2fsck 1.44.5 (15-Dec-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
|
| Code: | | /dev/sdb contains `DOS/MBR boot sector; partition 1 : ID=0xc, start-CHS (0x1,0,1), end-CHS (0x64,63,32), startsector 2048, 204800 sectors; partition 2 : ID=0x82, start-CHS (0x65,0,1), end-CHS (0x258,63,32), startsector 206848, 1024000 sectors; partition 3 : ID=0x83, start-CHS (0x259,0,1), end-CHS (0x33f,63,32), startsector 1230848, 61290496 sectors' data |
| Code: | fsck from util-linux 2.33
fsck.fat 4.1 (2017-01-24)
/dev/sdb1: 20 files, 9860/51091 clusters
|
| Code: | fsck from util-linux 2.33
e2fsck 1.44.5 (15-Dec-2018)
/dev/sdb3: clean, 334307/1916928 files, 3272990/7661312 blocks
|
I could use Gparted from my Gentoo system to check FAT partition on this SD card, no?
[Moderator edit: added [code] tags to preserve output layout. -Hu]
_________________
Best, Pali |
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Fri Apr 05, 2019 3:13 pm Post subject: |
|
|
| NeddySeagoon wrote: | paul_chany,
Describe what happens when you boot.
You should get 10 seconds of rainbow, then the rainbow is cleared.
If it sticks on the rainbow, bootcode.bin cannot be read.
When the rainbow disappears, what happens depends on your kernel setup.
It may go almost straight to text, if the console is built into the kernel.
If the console driver is a loadable module, you won't get any output until root is mounted.
I would be surprised if was useful on a raspberry pi.
Maybe with some very careful configuration?
How does it know what CPUs to build for and what *.dtb to install.
There's more but that's enough.
The output of
the content of config.txt and cmdline.txt would be good too. |
When I boot followings happen.
(actually I pull off SD card from my Raspberry Pi Model 2 and put into Raspberry Pi Model B+ which has the official touchscreen)
First I connected the Raspberry Pi to a monitor and to an USB keyboard.
Then power on the hardware.
On the monitor the output are these lines (within five seconds):
(these lines are the tail of the whole output - that is I can see on this monitor only these lines out there)
mmcblk0: p1 p2 p
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) readonly on device 179:3.
devtmpfs: mounted
Freeing unused kernel memory: 340K (c076b000 - c07c2000)
usb 1-1: new high-speed USB device number 2 using dwc_otg
Indeed it is in host mode hprt0 = 00001101
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
CPU: 0 PID: 1 Comm:init Not tainted 4.1.16+ #833
Hardware name: BCM2708
etc. etc.
PANIC: Attempted to kill init! exitcode=0x00000004
Enterung kdb (current=0xdd8d8000, pid 1) due to Keyboard Entry
kdb>
but here I can't enter anu letter with the keyboard!
Can this problem be solved at all?
_________________
Best, Pali |
|
| Back to top |
|
|
Logicien
Veteran
Joined: 16 Sep 2005
Posts: 1555
Location: Montréal
|
| Posted: Fri Apr 05, 2019 3:49 pm Post subject: |
|
|
Your Raspberry Pi sd card do not contain an whole disk partition so fsck do not see any possibility to make a filesystem check on that disk, you have to provide an Extended Filesystem (ext2, ext3 ext4) partition number to make a filsesystem check. You can use the command
| Code: | | dumpefs -h /dev/sdxy | grep 'Filesystem state:' |
Change x to the number of your sd card on your computer and y to the letter your Extended partition have. If the Filesystem state: clean, it do not really need a filesystem check. Otherwise do
| Code: | | fsck.ext4 -y /dev/sdxy |
from your computer. The command dosfsck can make a filesystem check on a Fat partition.
If you have a kernel panic the cause is probably the kernel image and or the initramfs. Genkernel can mount the boot partition to write the kernel image and the initramfs but when you upgrade the system this partition must be mounted in /boot for everything else who can be writed in it.
If /dev/mmcblk0p3 is your root filesystem, I do not see any parameter problem in /boot/config.txt and /boot/cmdline.txt. If you want more information about your disks execute lsblk with these parameters
| Code: | | lsblk -o VENDOR,MODEL,KNAME,NAME,TYPE,LABEL,SIZE,FSTYPE,MOUNTPOINT |
_________________
Paul |
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Fri Apr 05, 2019 3:56 pm Post subject: |
|
|
| Logicien wrote: | Your Raspberry Pi sd card do not contain an whole disk partition so fsck do not see any possibility to make a filesystem check on that disk, you have to provide an Extended Filesystem (ext2, ext3 ext4) partition number to make a filsesystem check. You can use the command
| Code: | | dumpefs -h /dev/sdxy | grep 'Filesystem state:' |
Change x to the number of your sd card on your computer and y to the letter your Extended partition have. If the Filesystem state: clean, it do not really need a filesystem check. Otherwise do
| Code: | | fsck.ext4 -y /dev/sdxy |
from your computer. The command dosfsck can make a filesystem check on a Fat partition. |
The following is the boot partition:
| Code: | | dumpe2fs -h /dev/sdb1 | grep 'Filesystem state:' |
dumpe2fs 1.44.5 (15-Dec-2018)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb1
The following is the root partition:
| Code: | | dumpe2fs -h /dev/sdb3 | grep 'Filesystem state:' |
dumpe2fs 1.44.5 (15-Dec-2018)
Filesystem state: clean
_________________
Best, Pali |
|
| Back to top |
|
|
Logicien
Veteran
Joined: 16 Sep 2005
Posts: 1555
Location: Montréal
|
| Posted: Fri Apr 05, 2019 4:09 pm Post subject: |
|
|
Your root filesystem is clean it do not need a filesystem check. But your Fat boot partition can need to be check.
| Code: | | fsck.fat -a /dev/sdb1 |
Your kernel image is read and loaded in memory from the Fat partition so, your boot partition is readable. One reason for this panic is that the ext4 support in not in the kernel image and not in the initramfs. Genkernel can make mistake.
There must be no confusion between the uBoot Fat partition and the Gentoo boot partition. What is /dev/sdb2 ? Show the output of
| Code: | | lsblk -o VENDOR,MODEL,KNAME,NAME,TYPE,LABEL,SIZE,FSTYPE,MOUNTPOINT |
it give precise informations.
_________________
Paul |
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Fri Apr 05, 2019 5:06 pm Post subject: |
|
|
| Logicien wrote: | Your root filesystem is clean it do not need a filesystem check. But your Fat boot partition can need to be check.
| Code: | | fsck.fat -a /dev/sdb1 |
Your kernel image is read and loaded in memory from the Fat partition so, your boot partition is readable. One reason for this panic is that the ext4 support in not in the kernel image and not in the initramfs. Genkernel can make mistake.
There must be no confusion between the uBoot Fat partition and the Gentoo boot partition. What is /dev/sdb2 ? Show the output of
| Code: | | lsblk -o VENDOR,MODEL,KNAME,NAME,TYPE,LABEL,SIZE,FSTYPE,MOUNTPOINT |
it give precise informations. |
| Code: | | fsck.fat -a /dev/sdb1 |
fsck.fat 4.1 (2017-01-24)
/dev/sdb1: 20 files, 9860/51090 clusters
| Code: | | lsblk -o VENDOR,MODEL,KNAME,NAME,TYPE,LABEL,SIZE,FSTYPE,MOUNTPOINT |
Generic- SD_MMC_MS_PRO sdb sdb disk 29,8G
sdb1 ├─sdb1 part 100M vfat
sdb2 ├─sdb2 part 500M swap
sdb3 └─sdb3 part 29,2G ext4
_________________
Best, Pali |
|
| Back to top |
|
|
Logicien
Veteran
Joined: 16 Sep 2005
Posts: 1555
Location: Montréal
|
| Posted: Fri Apr 05, 2019 5:44 pm Post subject: |
|
|
You do not have a Gentoo boot partition it is swap. On your computer mount only sdb3 the Gentoo root partition. Do not mount any other partition in the boot directory of the mount point of your root partition and do a ls -al in this boot directory to see if there is something in. It should not.
_________________
Paul |
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Fri Apr 05, 2019 5:57 pm Post subject: |
|
|
| Logicien wrote: | | You do not have a Gentoo boot partition it is swap. On your computer mount only sdb3 the Gentoo root partition. Do not mount any other partition in the boot directory of the mount point of your root partition and do a ls -al in this boot directory to see if there is something in. It should not. |
What I did follows:
| Code: | mount /dev/sdb3 /mnt/malnaroot/
cd /mnt/malnaroot/boot/
ls -al |
total 4296
drwxr-xr-x 2 root root 4096 2016 márc 13 .
drwxr-xr-x 20 root root 4096 2017 máj 23 ..
-rw-r--r-- 1 root root 15090 2016 márc 13 bcm2709-rpi-2-b.dtb
-rw-r--r-- 1 root root 15856 2016 márc 13 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 4354440 2016 márc 13 kernel7.img
_________________
Best, Pali |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54585
Location: 56N 3W
|
| Posted: Fri Apr 05, 2019 8:24 pm Post subject: |
|
|
paul_chany,
| Quote: | When I boot followings happen.
(actually I pull off SD card from my Raspberry Pi Model 2 and put into Raspberry Pi Model B+ |
What sort of Pi Model B+ ?
| boot: | -rw-r--r-- 1 root root 15090 2016 márc 13 bcm2709-rpi-2-b.dtb
-rw-r--r-- 1 root root 15856 2016 márc 13 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 4354440 2016 márc 13 kernel7.img |
will not work on the original Pi.
kernel7.img is an armv7a kernel, which will run on a Pi2 or a Pi3.
bcm2709-rpi-2-b.dtb is for the Pi2.
bcm2710-rpi-3-b.dtb is for the Pi3b in 32 bin mode.
bcm2710-rpi-3-b-plus.dtb (which you have missing, ir for the Pi3B+
The dtb matters. It describes the hardware to the kernel and there are significant differences between the 3B and 3B+
Your | Code: | | Kernel panic - not syncing: Attempted to kill init! |
tells that the content of /boot is mostly OK.
bootcode.bin was found and loaded the kernel and a dtb file. It does not mean it loaded the right dtb.
The root filesystem was mounted then something went wrong while the init script was running.
As the kernel paniced, it is unable to continue.
Edit your cmdline.txt file. Add to the end
When your Pi starts, it will load the kernel, mount root read only and start bash.
If that fails, bash or one of its libraries is corrupt.
If it works, its very lonely. Just you, bash and the kernel with a read only root.
You can look around - there is no $PATH set, so you need to either set it or give the full path to commands.
Root can be remounted read write if you want to.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Sat Apr 06, 2019 3:33 am Post subject: |
|
|
| NeddySeagoon wrote: | paul_chany,
| Quote: | When I boot followings happen.
(actually I pull off SD card from my Raspberry Pi Model 2 and put into Raspberry Pi Model B+ |
What sort of Pi Model B+ ?
| boot: | -rw-r--r-- 1 root root 15090 2016 márc 13 bcm2709-rpi-2-b.dtb
-rw-r--r-- 1 root root 15856 2016 márc 13 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 4354440 2016 márc 13 kernel7.img |
will not work on the original Pi.
kernel7.img is an armv7a kernel, which will run on a Pi2 or a Pi3.
bcm2709-rpi-2-b.dtb is for the Pi2.
bcm2710-rpi-3-b.dtb is for the Pi3b in 32 bin mode.
bcm2710-rpi-3-b-plus.dtb (which you have missing, ir for the Pi3B+
The dtb matters. It describes the hardware to the kernel and there are significant differences between the 3B and 3B+
Your | Code: | | Kernel panic - not syncing: Attempted to kill init! |
tells that the content of /boot is mostly OK.
bootcode.bin was found and loaded the kernel and a dtb file. It does not mean it loaded the right dtb.
The root filesystem was mounted then something went wrong while the init script was running.
As the kernel paniced, it is unable to continue.
Edit your cmdline.txt file. Add to the end
When your Pi starts, it will load the kernel, mount root read only and start bash.
If that fails, bash or one of its libraries is corrupt.
If it works, its very lonely. Just you, bash and the kernel with a read only root.
You can look around - there is no $PATH set, so you need to either set it or give the full path to commands.
Root can be remounted read write if you want to. |
NeddySeagoon,
I am using now the Raspberry Pi Model B+ for investigate the boot process of this SD card only.
I just wanted to see what happen at boot time.
I have two Raspberry Pi's:
the Pi2 (on which I used this SD card (let's call it SD card #1) so far - for my Moodle site)
and the Pi B+ (which is assembled with the official touchscreen) which has it's own SD card (SD card #2)- which can be booted.
So what I did is that that I used SD card #1 from Pi2 to boot it on Pi B+ - to see what happens at boot time.
If I use SD card #1 on Pi2 then I have not the official touchscreen so far to see what happen.
I shall disassemble the Pi B+ from the touchscreen and replace it with Pi2 out there.
This way I can boot SD card #1 assembled with touchscreen to the bash prompt. I shall do that today later.
I did it!
I assembled Pi2 with touchscreen and can boot the SD card #1.
I get the regular bash prompt.
Everything is right but shorewall init script.
After I edited it and added:
| Code: | | PRODUCTS="shorewall" |
it works.
Name resolution still works not.
Eg. I get this error message when boot finished:
Setting clock via the NTP client 'ntpdate' ...
Exiting, name server cannot be used: Temporary failure in name resolution.
Well, sorry for this thread (because I thought the boot did not work).
But now what can I do to solve the name resolution problem?
_________________
Best, Pali |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54585
Location: 56N 3W
|
| Posted: Sat Apr 06, 2019 9:29 am Post subject: |
|
|
paul_chany,
There are three different Pi B+ models.
Which one do you have?
We know its not the original Pi B+ as that has an armv6a CPU and your kernel is for an armv7a CPU.
The Pi 3B+ has a different network controller to all the others. It won't work with the *.dtb files for the 2B, and 3B, without the plus.
Likewise, the WiFi changed between the 3B and 3B+. The *.dtb files changed.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Sat Apr 06, 2019 11:54 am Post subject: |
|
|
| NeddySeagoon wrote: | paul_chany,
There are three different Pi B+ models.
Which one do you have?
We know its not the original Pi B+ as that has an armv6a CPU and your kernel is for an armv7a CPU.
The Pi 3B+ has a different network controller to all the others. It won't work with the *.dtb files for the 2B, and 3B, without the plus.
Likewise, the WiFi changed between the 3B and 3B+. The *.dtb files changed. |
NeddySeagoon,
I have Pi B+ V1.2 model (2014).
But, as I wrote earlier, I am using SD card #1 on Pi 2 model, and not on Pi B+ V1.2 model.
_________________
Best, Pali |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54585
Location: 56N 3W
|
| Posted: Sat Apr 06, 2019 1:48 pm Post subject: |
|
|
paul_chany,
How I am confused. A Pi B+ V1.2 model (2014) has an armv6a CPU.
Your Pi /boot contains
| Code: | -rw-r--r-- 1 root root 15090 2016 márc 13 bcm2709-rpi-2-b.dtb
-rw-r--r-- 1 root root 15856 2016 márc 13 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 4354440 2016 márc 13 kernel7.img |
The file kernel7.img will not run on a Pi B+ V1.2, and the dtb file for a Pi 1 is missing.
Further, those files are all from 2016, so they are three years old.
You said you updated your kernel ... but its not listed.
That can't be all your /boot. bootcode.bin is required. It runs on the GPU to load the kernel, dtb and optionally, the initrd.
You also need at least one *.dat and *.elf file.
All the bits don't fit together yet.
Please post all of the from the SD card.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Sat Apr 06, 2019 2:15 pm Post subject: |
|
|
| NeddySeagoon wrote: | paul_chany,
How I am confused. A Pi B+ V1.2 model (2014) has an armv6a CPU.
Your Pi /boot contains
| Code: | -rw-r--r-- 1 root root 15090 2016 márc 13 bcm2709-rpi-2-b.dtb
-rw-r--r-- 1 root root 15856 2016 márc 13 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 4354440 2016 márc 13 kernel7.img |
The file kernel7.img will not run on a Pi B+ V1.2, and the dtb file for a Pi 1 is missing.
Further, those files are all from 2016, so they are three years old.
You said you updated your kernel ... but its not listed.
That can't be all your /boot. bootcode.bin is required. It runs on the GPU to load the kernel, dtb and optionally, the initrd.
You also need at least one *.dat and *.elf file.
All the bits don't fit together yet.
Please post all of the from the SD card. |
I'm sorry for the misunderstanding.
I'm trying to explain the situation.
1. As I already wrote, I didn't know why the boot failed. I thought the boot failed and therefore could not log in using ssh to this Pi 2 system from my laptop. This happen on Raspberry Pi 2 Model B V1.1 . I used this hardware so far as my web server with my Moodle site. He was just lying on my shelf with an ethernet connection. I used with this hardware the SD card #1. This hardware was not connected to any keyboard nor any monitor, like touchscreen. That's why I had to connect from my laptop with ssh to this Pi 2.
2. So I decide to write here for help. You ask me to find out what happen at boot time on this system. Therefore I just pull off the SD card #1 from this Pi 2 model, and push in to other Raspberry pi, which is B+ model v1.2 . This Pi B+ was connected to touchscreen and a keyboard.Then the boot freezes at kbd> prompt. Then I realize that that I must to use SD card #1 with Pi 2 Model B V1.2 so I disassembled the Pi B+ from touchscreen hardware and replace it with Pi 2 Model B V1.1 . So now I have touchscreen and keyboard connected with Pi 2 Model B V1.2. This way I can see what happen at boot time on SD card #1.
So So I saw that the boot was actually successful on SD card #1 on hardware Pi 2 Model B V1.2.
Only I have no proper routing on it, so that's why can't I login from my laptop to Pi 2 Model B V1.2 through SSH.
I hope I have explain now what happen here.
Sorry for misunderstanding again.
_________________
Best, Pali |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54585
Location: 56N 3W
|
| Posted: Sat Apr 06, 2019 2:23 pm Post subject: |
|
|
paul_chany,
OK, that helps a lot. There is no Pi B+ V1.2 model (2014) involved.
With no proper routing and no internet connection, ntp will fail and the Pi clock will start from time zero.
That's 00:00 UTC, 1 Jan 1970. This causes things that need time to break.
Does putting time right then using swclock help?
swclock does not keep the time correct but it stops the backward steps.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
paul_chany
Tux's lil' helper
Joined: 01 Aug 2010
Posts: 82
Location: Europe, Serbia
|
| Posted: Sat Apr 06, 2019 4:00 pm Post subject: |
|
|
| NeddySeagoon wrote: | paul_chany,
OK, that helps a lot. There is no Pi B+ V1.2 model (2014) involved.
With no proper routing and no internet connection, ntp will fail and the Pi clock will start from time zero.
That's 00:00 UTC, 1 Jan 1970. This causes things that need time to break.
Does putting time right then using swclock help?
swclock does not keep the time correct but it stops the backward steps. |
I run the command:
as root to set the date and time right.
What is swclock? How to use it?
_________________
Best, Pali |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54585
Location: 56N 3W
|
| Posted: Sat Apr 06, 2019 5:14 pm Post subject: |
|
|
paul_chany,
swclock is a service, a bit like hwclock, except that it does not set system time from a hardware real time clock.
The Pi doesn't have one unless you add it yourself.
swclock saves the time at shutdown in a file and restores it at boot. This does not keep time correctly but it ensures that time never steps backwards.
| Code: | | $ rc-update show -v |
should list both hwclock and swclock. You must only use one.
Add the one you want to use to the boot runlevel as the clock must be set before networking is started.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on ARM
