Debian I had destroyed grub

mrmazda · 05-19-2024, 01:52 PM

Quote:

Originally Posted by beginstart

Code:

ls -gGl /boot/vmlinu*/boot/initr* 

ls: Unable to access '/boot/vmlinu*/boot/initr*': file or directory not found

That is not the command I wrote. Please try again.

Code:

# ls -gGl /boot/vmlinu* /boot/initr*
-rw-r--r-- 1  9791450 Nov 12  2023 /boot/initrd.img-6.1.0-13-amd64
-rw-r--r-- 1 10207586 Dec 16 21:25 /boot/initrd.img-6.1.0-16-amd64
-rw-r--r-- 1  9792442 Feb 11 01:27 /boot/initrd.img-6.1.0-18-amd64
-rw-r--r-- 1  8135584 Sep 29  2023 /boot/vmlinuz-6.1.0-13-amd64
-rw-r--r-- 1  8148352 Dec 12 07:16 /boot/vmlinuz-6.1.0-16-amd64
-rw-r--r-- 1  8152768 Feb  1 03:05 /boot/vmlinuz-6.1.0-18-amd64
#

beginstart · 05-21-2024, 08:01 AM

I am sorry.

Thank You.

Code:


 ls -gGl /boot/vmlinu* /boot/initr* 
-rw-r--r-- 1 17593666 12. Mär 2022  /boot/initrd.img-4.9.0-18-686-pae
-rw-r--r-- 1 63751348 24. Jan 21:38 /boot/initrd.img-5.10.0-15-686-pae.old
-rw-r--r-- 1 63790452  2. Feb 17:12 /boot/initrd.img-5.10.0-27-686-pae
-rw-r--r-- 1 67437787 13. Mai 13:12 /boot/initrd.img-6.1.0-21-686-pae
-rw-r--r-- 1  3702240  7. Mär 2022  /boot/vmlinuz-4.9.0-18-686-pae
-rw-r--r-- 1  5042208 31. Dez 16:46 /boot/vmlinuz-5.10.0-27-686-pae
-rw-r--r-- 1  5720000  3. Mai 14:36 /boot/vmlinuz-6.1.0-21-686-pae

mrmazda · 05-22-2024, 11:12 PM

Please attach to a reply; do not paste the file into your reply: /boot/grub/grub.cfg

mrmazda · 05-22-2024, 11:43 PM

I looked for installed RAM/memory among all 228 messages without finding it.

What does inxi -ma report?

beginstart · 05-23-2024, 12:27 PM

I am sorry
for my mistake.

Code:



 inxi -ma
Memory:
  RAM: total: 2.95 GiB used: 896.1 MiB (29.7%)
  Array-1: capacity: 4 GiB slots: 4 EC: None max-module-size: 1024 MiB
    note: est.
  Device-1: XMM1 type: DDR2 detail: synchronous size: 1024 MiB
    speed: 800 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: JEDEC ID:2C 00 part-no: 8HTF12864AY-800G1 serial: B8A329E8
  Device-2: XMM2 type: DDR2 detail: synchronous size: 1024 MiB
    speed: 800 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: JEDEC ID:2C 00 part-no: 8HTF12864AY-800G1 serial: B7A329E8
  Device-3: XMM3 type: DDR2 detail: synchronous size: 1024 MiB
    speed: 800 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: JEDEC ID:2C 00 part-no: 8HTF12864AY-800G1 serial: B6A329E8
  Device-4: XMM4 type: no module installed
  Array-2: capacity: 4 GiB use: Flash Memory slots: 1 EC: None
    max-module-size: 4 GiB note: est.
  Device-1: SYSTEM ROM type: Flash detail: non-volatile size: 4 MiB
    speed: N/A volts: N/A width (bits): data: 2 total: 2 manufacturer: N/A
    part-no: N/A serial: N/A
~#

mrmazda · 05-24-2024, 02:23 PM

I suggest to download a Bookworm 64bit installation .iso, either regular DVD or NET installer, and burn it to CD (NET .iso) or DVD (DVD .iso) or USB stick (NET .iso or DVD .iso), then try booting it. Optionally, buy one already burned to media from an online source. Prices for these are historically modest. Does it panic, or does the installer initialize? If it initializes, I suggest to replace your 32bit installation with the 64bit OS version that your Intel E5200 processor is designed to use.

Another suggestion: try removing one of the RAM sticks so that the two left installed are in one of the two dual channel pairs, then try booting normally. It's possible you have a memory controller that isn't working as it should using a mixture of dual channel and single channel. If this succeeds, you may wish to add back the 3rd stick, and find a matching 4th stick to add.

beginstart · 05-25-2024, 08:09 AM

Sorry.
I did it. (install Debian 64b with DVD)
3 "stupid" questions.
Isnt the old kernel a problem?
Shall I post the log DEBIAN produced during the update?
What is a RAM- Stick?

Regards and thank You.

mrmazda · 05-25-2024, 09:26 AM

Quote:

Originally Posted by beginstart

I did it. (install Debian 64b with DVD)

Does this mean you are now able to boot Debian from the internal disk of your E5200 PC without getting panic?

Quote:

Isnt the old kernel a problem?

It shouldn't be. Is it even still there? What does ls -gGl /boot/vmlinu* /boot/initr* report?

Quote:

Shall I post the log DEBIAN produced during the update?

There's no need if nothing is broken. What does inxi -S report?

Quote:

What is a RAM- Stick?

If you take your PC's cover off you should see 4 slots alike side-by-side, with one empty, and a RAM module or "stick" in each of the other three.

beginstart · 06-02-2024, 06:22 AM

Thank You for friendly help.

Code:

 ls -gGl /boot/vmlinu* /boot/initr
ls: Zugriff auf '/boot/initr' not possible: file or directory not found
-rw-r--r-- 1 3702240  7. Mär 2022  /boot/vmlinuz-4.9.0-18-686-pae
-rw-r--r-- 1 5042208 31. Dez 16:46 /boot/vmlinuz-5.10.0-27-686-pae
-rw-r--r-- 1 5720000  3. Mai 14:36 /boot/vmlinuz-6.1.0-21-686-pae



 inxi -S
System:
  Host: use Kernel: 4.9.0-18-686-pae arch: i686 bits: 32 Desktop: LXDE
    v: 0.10.1 Distro: Debian GNU/Linux 12 (bookworm)

I did download Debian 12 64 bit. Burned it on DVD.
I put in the DVD
panic crash.

The problem is not solved. "Normal" booting created panic.

The RAM was checked here in the thread.
It is fine.

mrmazda · 06-03-2024, 05:04 AM

Quote:

Originally Posted by beginstart

Code:

ls -gGl /boot/vmlinu* /boot/initr
ls: Zugriff auf '/boot/initr' not possible: file or directory not...

You did not issue the command requested.

beginstart · 06-05-2024, 08:11 AM

I am sorry.

Code:



 ls -gGl /boot/vmlinu* /boot/initr*
-rw-r--r-- 1 17593666 12. Mär 2022  /boot/initrd.img-4.9.0-18-686-pae
-rw-r--r-- 1 63751348 24. Jan 21:38 /boot/initrd.img-5.10.0-15-686-pae.old
-rw-r--r-- 1 63790452  2. Feb 17:12 /boot/initrd.img-5.10.0-27-686-pae
-rw-r--r-- 1 67437787 13. Mai 13:12 /boot/initrd.img-6.1.0-21-686-pae
-rw-r--r-- 1  3702240  7. Mär 2022  /boot/vmlinuz-4.9.0-18-686-pae
-rw-r--r-- 1  5042208 31. Dez 16:46 /boot/vmlinuz-5.10.0-27-686-pae
-rw-r--r-- 1  5720000  3. Mai 14:36 /boot/vmlinuz-6.1.0-21-686-pae
~$

Thank You.

mrmazda · 06-06-2024, 08:06 PM

I am running very short of ideas. In post #209 I described need to confirm no obviously bad electrolytic capacitors, and found no clear response in reply. This applies both to motherboard, and power supply.

You may try downloading, burning and booting installation media of other 64bit distros. If they panic too, it suggests either hardware failure, or some incompatibility between your system and newer software, including kernel, drivers, and/or possibly other.

beginstart · 06-07-2024, 09:47 AM

Another stupid idea.
How about download a text-based Linux
burn it on DVD
and try to install it.
Because the crash does happen when the logo is appearing.

mrmazda · 06-07-2024, 01:07 PM

Quote:

Originally Posted by beginstart

the crash does happen when the logo is appearing.

Please show output from:

Code:

dpkg-query -W | grep mouth

If the response is not null, try booting by appending noplymouth plymouth=0 plymouth.enable=0 on the linu for the default 6.1 kernel like you did with nomodeset, and then proceed with an otherwis normal boot attempt. If this permits a boot without panic, remove the packages listed by dpkg-query and try a normal boot using the default Grub selection without modification.