Standard installation with KDE desktop on an older i586 laptop (no UEFI or secure boot). Installed kernel update today with apper and afterwards there was the message to reboot. Then the Grub screen
Booting `openSUSE’
Loading Linux 3.16.7-24-desktop…
Loading initial ramdisk …
And that is it no movement any more so I presume the computer does not find the ramdisk after the update. Now this is the first time that I have problems with GRUB after the change from GRUB 0.97 to GRUB2. All I remember that you cannot change the entry in GRUB as you could with the previous version. Of course I can go to boot options and boot into the Linux 3.16.7-21-desktop. Here is the relevant entry in /boot/grub2/grub.cfg:
### BEGIN /etc/grub.d/10_linux ###
menuentry 'openSUSE' --class opensuse --class gnu-linux --class gnu --class os $menuentry
_id_option 'gnulinux-simple-cffe42a5-88ec-4ab3-b077-f3ceeba7990e' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos6'
if x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,m
sdos6 --hint-baremetal=ahci0,msdos6 --hint='hd0,msdos6' cffe42a5-88ec-4ab3-b077-f3ceeba7
990e
else
search --no-floppy --fs-uuid --set=root cffe42a5-88ec-4ab3-b077-f3ceeba7990e
fi
echo 'Loading Linux 3.16.7-24-desktop ...'
linux /boot/vmlinuz-3.16.7-24-desktop root=UUID=cffe42a5-88ec-4ab3-b077-f3ceeba7990e video=1366x768 resume=/
dev/disk/by-id/ata-TOSHIBA_MK5065GSX_70HYT1VDT-part5 splash=0 quiet showopts
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-3.16.7-24-desktop
}
submenu 'Advanced options for openSUSE' $menuentry_id_option 'gnulinux-advanced-cffe42a5-88ec-4ab3-b077-f3ceeba7990e' {
menuentry 'openSUSE, with Linux 3.16.7-24-desktop' --class opensuse --class gnu-linux --class gnu --class os $menuentry_
id_option 'gnulinux-3.16.7-24-desktop-advanced-cffe42a5-88ec-4ab3-b077-f3ceeba7990e' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos6'
if x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos6 --hint-efi=hd0,msdos6 --hint-baremetal=ahci0,ms
dos6 --hint='hd0,msdos6' cffe42a5-88ec-4ab3-b077-f3ceeba7990e
else
search --no-floppy --fs-uuid --set=root cffe42a5-88ec-4ab3-b077-f3ceeba7990e
fi
echo 'Loading Linux 3.16.7-24-desktop ...'
linux /boot/vmlinuz-3.16.7-24-desktop root=UUID=cffe42a5-88ec-4ab3-b077-f3ceeba7990e video=1366x768 resume=/
dev/disk/by-id/ata-TOSHIBA_MK5065GSX_70HYT1VDT-part5 splash=0 quiet showopts
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-3.16.7-24-desktop
Afterwards come the entry for the recovery mode (which does not boot either).
But the initrd file seems to be there:
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] (prog-if 00 [VGA controller])
Do you remember more about the problem?
caf4926, I don’t understand your reply which I presume goes back to the log file. I went into /var/log and used the command “more boot.log”. Don’t know about more verbose here.
Thanks, I will tomorrow. To load this page now took 9 minutes (otherwise the internet speed is normal). There may be some problems with the server or with the line to NZ but I cannot wait for each refresh or search. May be tomorrow the connection is better.
On 2015-08-16 06:46, fuerstu wrote:
>
> All I can see in the boot.log is the boot into the 3.16.7-21-desktop and
> nothing before.
The previous boot should be in /var/log/boot.omsg.
However, both files are kind of deprecated, they are no longer the
verbose logs they were. Currently, they are a dump of the on screen
messages that get hidden by plymouth, the graphical thing used during
boot for effect.
The real boot log is in /var/log/messages, but /only/ if you have a
syslog daemon installed. On current systems, you have to use journalctl
instead to query it.
journalctl -b -1
will give you access to the previous boot session log.
If the machine does not boot, there is no text file with logs that you
can read. It is a binary database.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Thanks, robin_listas, I have rsyslog installed but your command journalctl -b -1 does not show much:
-- Logs begin at Tue 2012-12-25 20:00:21 NZDT, end at Mon 2015-08-17 14:12:06 NZST. --
Aug 17 13:42:26 linux-dfsr.site hp-systray[1972]: hp-systray[1972]: error: option -s not recognized
Aug 17 13:42:31 linux-dfsr.site org.gnome.zeitgeist.Engine[1798]: ** (zeitgeist-datahub:2122): WARNING **: zeitgeist-datahub.val
Aug 17 13:42:34 linux-dfsr.site hp-upgrade[2170]: hp-upgrade[2170]: error: HPLIP upgrade is disabled by openSUSE for security re
Aug 17 13:43:39 linux-dfsr.site org.gtk.Private.AfcVolumeMonitor[1798]: Volume monitor alive
Aug 17 13:43:40 linux-dfsr.site org.gnome.OnlineAccounts[1798]: goa-daemon-Message: goa-daemon version 3.14.4 starting
Aug 17 13:45:21 linux-dfsr.site su[2544]: (to root) uli on pts/1
Aug 17 14:02:27 linux-dfsr.site su[3252]: (to root) uli on pts/3
Aug 17 14:02:28 linux-dfsr.site su[3257]: (to root) uli on pts/3
Aug 17 14:05:37 linux-dfsr.site org.kde.kuiserver[1798]: kuiserver: Fatal IO error: client killed
lines 1-10/10 (END)
I looked into messages but after looking back 500 lines without finding anything relevant I had enough. I am not really knowing what to look for and I cannot scroll back further after the command tail -550 messages command.
I searched for other update problems with AMD/ATI but could only find one threat which suggested deleting (and tabooing) ucode-amd and ucode-intel but that made no difference either.
So anyone any ideas?
Cheers
uli
On 2015-08-17 04:36, fuerstu wrote:
>
> Thanks, robin_listas, I have rsyslog installed but your command
> journalctl -b -1 does not show much:
…
> I looked into messages but after looking back 500 lines without finding
> anything relevant I had enough. I am not really knowing what to look for
> and I cannot scroll back further after the command tail -550 messages
> command.
If you run the command as I typed it, it gets automatically piped via
“less”, which is better than “more”. In this laptop I can see 56000
lines. The “home” key goes to the first line, and “end” to the last.
You have to query a session that crashed. The number in the command line
allows you to go back 1, 2, 3… sessions, like -1, -2, -3,… Just
choose the appropriate one.
So I rebooted to let the computer stall, then rebooted again into the 3.16.7-21-desktop. Then used the command journalctl -b -1 since it was the previous startup. 1352 lines but I could find nothing telling me of a problem except maybe “Aug 17 14:07:08 linux-dfsr kernel: pci 0000:00:14.4: System wakeup disabled by ACPI” whatever that means.However in between there are listings like “Aug 17 14:07:08 linux-dfsr kernel: usb usb1: Manufacturer: Linux 3.16.7-21-desktop ehci_hc” which indicate that it is the boot of the 3.16.7-21 desktop and not the stalled boot into the 3.16.7-24 desktop. So I must say I am at a loss of what to do next.
I tried now journalctl -b -2 and journalctl -b -0 and the result is similar. at some stage all three logs after a while report about network manager which certaily didn’t start at all when the boot hangs at the search for initrd. It looks as if the logs there always show logs of successful boots.
On 2015-08-17 05:56, fuerstu wrote:
>
> I tried now journalctl -b -2 and journalctl -b -0 and the result is
> similar. at some stage all three logs after a while report about network
> manager which certaily didn’t start at all when the boot hangs at the
> search for initrd. It looks as if the logs there always show logs of
> successful boots.
Yes, that’s a possibility I should have mentioned. I forgot: the failed
boot does not reach a point where it writes to hard disk any logs.
Your only chance then is the screen.
You have to try disable plymouth.
I would manually edit /boot/grub2/grub.cfg (the change will be
automatically undone on updates). Search the entry for the failing
kernel, something similar to this (starts with the word “linux”):
> linux /boot/vmlinuz-3.11.6-4-desktop root=UUID=d1ff0a04-4ecb-4d28-9f3b-0b639cbf1f9e resume=/dev/disk/by-label/Swap plymouth.enable=0 splash=verbose console=tty1 loglevel=3 3
What you need are the options at the end “plymouth.enable=0
splash=verbose console=tty1 loglevel=3 3”.
It should boot into text mode with a lot of messages, or perhaps fail.
If it ends on a prompt, login as root and do “startx”. Yes, I know this
is not fully supported, but will tell you if graphics works. If it does,
exit, then issue “init 5”.
Thanks you, robin_listas, I tried that but it made no difference - the computer stalled at the line “Loading initial ramdisk …”
First to the boot line in grub.cfg - the old line was:
linux /boot/vmlinuz-3.16.7-24-desktop root=UUID=cffe42a5-88ec-4ab3-b077-f3ceeba7990e video=1366x768 resume=/dev/disk/by-id/ata-TOSHIBA_MK5065GSX_70HYT1VDT-part5 splash=0 quiet showopts
and I changed it to:
linux /boot/vmlinuz-3.16.7-24-desktop root=UUID=cffe42a5-88ec-4ab3-b077-f3ceeba7990e video=1366x768 resume=/dev/disk/by-id/ata-TOSHIBA_MK5065GSX_70HYT1VDT-part5 plymouth.enable=0 splash=verbose console=tty1 loglevel=3
I wondered now if there is something wrong with initrd?
I showed in my first post:
On 2015-08-18 04:46, fuerstu wrote:
>
> Thanks you, robin_listas, I tried that but it made no difference - the
> computer stalled at the line “Loading initial ramdisk …”
Then it doesn’t even boot.
> I wondered now if there is something wrong with initrd?
Does this earlier thread give any help: kernel-desktop removal installs kernel-desktop-base, why?
I’m particularly looking at message #8 in that thread, which seemed to be useful for the OP. Maybe your problem is similar. It could be worth a try.
Thank you, nrickert and robin_listas.
Yesterday I had a look at the mkinitrd command and found so many conflicting answers on the internet (e.g the option -o which is not in the man pages, that it is superseded by the mkinitrdfs (or similar) command, how to enter the kernel version in this command (just the number or with vmlinuz…) that I am not sure about the correct options. So I tried nrickert’s option. Strangely the computer booted but but only in runlevel 3 (of course I changed the the grub entry with “plymouth.enable=0 splash=verbose console=tty1 loglevel=3 3” ). so I changed the entry back to the old version and included the dis_ucode_ldr so that the whole line reads:
linux /boot/vmlinuz-3.16.7-24-desktop root=UUID=cffe42a5-88ec-4ab3-b077-f3ceeba7990e video=1366x768 resume=/dev/disk/by-id/ata-TOSHIBA_MK5065GSX_70HYT1VDT-part5 splash=0 quiet showopts dis_ucode_ldr
with the result that it didn’t boot and hung just as before at the stage “Loading initial ramdisk …”. So without much understanding I tried:
linux /boot/vmlinuz-3.16.7-24-desktop root=UUID=cffe42a5-88ec-4ab3-b077-f3ceeba7990e video=1366x768 resume=/d
ev/disk/by-id/ata-TOSHIBA_MK5065GSX_70HYT1VDT-part5 plymouth.enable=0 splash=verbose console=tty1 dis_ucode_ldr
Now the computer booted but much slower than usual and even after login it took a while until the desktop was really there and usable. During the boot the scrolling of the text was in a different resolution as normal too (remember my settings were “splash=0”). So we are close but I still would like the boot at a normal speed. I suppose I could take the console=tty1 out but I thought before I try around without really knowing what I do I get some advice from you who understand more than I.
Cheers
Uli
On 2015-08-19 00:06, fuerstu wrote:
>
> Thank you, nrickert and robin_listas.
> Yesterday I had a look at the mkinitrd command and found so many
> conflicting answers on the internet (e.g the option -o which is not in
> the man pages, that it is superseded by the mkinitrdfs (or similar)
You do not need any options, or I would have told you what to use
Just enter it without any parameters. Default is all I have used in many
years, except on special circumstances so long ago that I have forgotten
about them.
> command, how to enter the kernel version in this command (just the
> number or with vmlinuz…) that I am not sure about the correct
> options. So I tried nrickert’s option. Strangely the computer booted but
> but only in runlevel 3 (of course I changed the the grub entry with
> “plymouth.enable=0 splash=verbose console=tty1 loglevel=3 3” ).
The last “3” makes it boot in text mode, intentionally in order to be
able to read all error messages. Then, login as root as enter “init 5”
and you are in graphics mode. Or simply remove that last “3” or replace
with “5”.
If without the “3” it still boots in text mode, that indicates that
graphics failed. To diagnose, login as root and enter “startx”.
> During
> the boot the scrolling of the text was in a different resolution as
> normal too
That’s the “video=…” option.
> So we are close but I
> still would like the boot at a normal speed. I suppose I could take the
> console=tty1 out but I thought before I try around without really
> knowing what I do I get some advice from you who understand more than I.
That option doesn’t affect speed or video setting. It only changes where
the boot messages go.
