Installed the latest updates to 19 and Dell N7110 laptop now fails to boot. Does not appear to get to a point of even creating any logs. Returning to 0.48 in grub restores boot.
I see nothing in dmesg indicating an attempt to boot to .0-50
inxi -Fxxrzc0
System: Host: Chinook Kernel: 4.15.0-48-generic x86_64 bits: 64 gcc: 7.3.0
Desktop: MATE 1.20.1 (Gtk 3.22.30-1ubuntu3) dm: lightdm
Distro: Linux Mint 19 Tara
Machine: No /sys/class/dmi; using dmidecode: no smbios data. Old system?
Battery BAT0: charge: 37.4 Wh 100.0% condition: 37.4/48.8 Wh (76%)
volts: 12.4/11.1
model: SDI Dell serial: <filter>status: Full
hidpp__0: charge: N/A condition: NA/NA Wh volts: NA
model: Logitech Wireless Touch Keyboard K400 serial: <filter>status: Discharging
CPU: Dual core Intel Core i5-2450M (-MT-MCP-)
arch: Sandy Bridge rev.7 cache: 3072 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9966
clock speeds: min/max: 800/3100 MHz 1: 797 MHz 2: 900 MHz
3: 797 MHz 4: 797 MHz
Graphics: Card: Intel 2nd Generation Core Integrated Graphics Controller
bus-ID: 00:02.0 chip-ID: 8086:0126
Display Server: X.Org 1.19.6
drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1600x900@60.08hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile
version: 3.3 Mesa 18.2.8 (compat-v: 3.0) Direct Render: Yes
Audio: Card Intel 6 Series/C200 Series Family High Def. Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1c20
Sound: Advanced Linux Sound Architecture v: k4.15.0-48-generic
Network: Card-1: Intel Centrino Wireless-N 1030 [Rainbow Peak]
driver: iwlwifi bus-ID: 01:00.0 chip-ID: 8086:008a
IF: wlp1s0 state: up mac: <filter>
Card-2: Realtek RTL810xE PCIE Fast Ethernet controller
driver: r8169 v: 2.3LK-NAPI port: 2000
bus-ID: 03:00.0 chip-ID: 10ec:8136
IF: enp3s0 state: down mac: <filter>
Drives: HDD Total Size: 750.2GB (4.2% used)
ID-1: /dev/sda model: ST9750420AS size: 750.2GB
serial: <filter> temp: 26C
Partition: ID-1: / size: 687G used: 30G (5%) fs: ext4 dev: /dev/sda1
RAID: System: supported: N/A
No RAID devices: /proc/mdstat, md_mod kernel module present
Unused Devices: none
Sensors: System Temperatures: cpu: 44.0C mobo: 44.0C
Fan Speeds (in rpm): cpu: N/A
Repos: Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
deb http://packages.linuxmint.com tara main upstream import backport #id:linuxmint_main
deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
deb http://archive.canonical.com/ubuntu/ bionic partner
Info: Processes: 191 Uptime: 3 min Memory: 791.5/5854.3MB
Init: systemd v: 237 runlevel: 5 Gcc sys: 7.4.0
Client: Shell (sudo running in bash) inxi: 2.3.56
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 3 times in total.
Reason:Topic automatically closed 6 months after creation. New replies are no longer allowed.
I have the same issue with Ubuntu 18.04 on a HP Laptop nc6230. I also couldn't find any hint about the issue in the logs.
One interesting thing was that every time I had to hard-poweroff the device it booted correctly next time. But then the next boot it got stuck again.
Only solution so far was to remove this kernel and use the older one.
mike_kelly wrote: ⤴Wed May 15, 2019 2:37 am
I see nothing in dmesg indicating an attempt to boot to .0-50
The dmesg command gives you access to the kernel's in-memory ring buffer, i.e. the latest kernel messages from the current session. What you were probably looking for is the kernel log, which is found at /var/log/kern.log (and gets rotated).
What irritates me a bit about your inxi report is this line near the top: Machine: No /sys/class/dmi; using dmidecode: no smbios data. Old system?
Looks as if inxi fails to determine your machine type, motherboard and Bios. Might mean two things, I guess: either some software needed to determine these details is missing on your system; or your machine is so old that they simply cannot be determined at all.
Even on my oldest machines (from 2008 and 2009) inxi can display a proper "Machine" line, even though not all details may be found out. Machine: Type: Desktop Mobo: N/A model: N/A serial: N/A BIOS: American Megatrends v: 080015 date: 10/09/2009
(This is from my Zotec mini desktop. Works correctly, even on kernel 4.15.0-50 and the 2019 intel-microcode. But to be honest, the old Atom CPU (2 cores, hyperthreading) is not vulnerable to the most recently found security flaws anyway, because it does not support the needed features.)
Cheers,
Karl
The people of Alderaan have been bravely fighting back the clone warriors sent out by the unscrupulous Sith Lord Palpatine for 792 days now. Lifeline
I would check the size of your initrd files in /boot. I recently tried to build my own kernel and got initrd files that were too large for the amount of RAM that I was using.
Seeing similar issues on IBM/Lenovo T60 with ATI x1400 Graphics card (32BIt install)
Can see from the Ubuntu Bug report (mentioned earlier) there is another T60 user with same card reporting the issue too.
From what i can see, the machine does boot but as the radeon driver is possibly being unloaded during boot and the system is falling back to vesa driver, it can result in black screens etc. It is intermittent though. Sometimes will get a clean boot, sometimes will get black screen, sometimes will get the warning about software rendering mode (no hardware acceleration).
Originally thought it could be hardware issue (graphic card overheating etc) as in the process of resurrecting this T60 to add to my TP collection, as it is intermittent.
Am looking to upgrade this T60 to a 64 Bit Core 2 Duo at some point (currently running a T2600,but will go up to a T7400 or maybe a T7600, if i can find one cheap enough on FleaBay) but don't believe the architecture change will make any difference, as OP is running 64 Bit anyway.
As stated above, this could be graphics related (which would explain the black screens) but not sure why affecting different graphics architectures (ATI/AMD and Intel)
Jumping up to newer 4.18.X or 5.X kernels does not resolve it, the issue still persists (for me anyway!)
Nothing in the kern.log or any other log I can find. The recovery mode boot in 4.15.0.-50 ends in a kernel panic. I don't think it gets far enough to start to log anything.
The Intel microcode fix was installed, right before the kernel update.
My initrd files are 60mb
just a comment that might help figuring out what the trouble is when upgrading kernel on latest linux mint "tessa".
I made a fresh install last month of mint 19.1 on two very different PC, and was at first disappointed because the recommended kernel upgrade (on branch 4.15.*) won't work. On both pc I experienced kind of black screen (see image) and no boot logs.
I finally went through the kernel upgrade process in several steps (using only mint update manager) and have now linux-image-4.15.0-50 working on both computers.
I think this glitch is related with either linux-firmware or intel-microcode and suggest you had them installed before the newer linux kernel.
ps: BTW my linux system is 32-bit on one pc and 64-bit on the other.
As a further observation, my T60 now has Mint 19.1 XFCE on it (rebuilt again!) and i can install the latest kernel on the 4.15 branch. However, when i reboot, the DE crashes once or twice before being able to use the PC
To elaborate, login window (lightdm, assuming it IS lightdm on XFCE?) appears ok, swipe my fingerprint reader and login happens, but X Server crashes and I'm returned to the login window. Swipe again and it will login ok (or maybe not another time, again its intermittent...)
Looking at System Reports, it says that there is a log for _usr_lib_xorg_Xorg.0.crash but when i attempt to open it, it appears corrupt, as just a huge string of garbage (and the System Reports app is reporting that the file cannot be read)
5.X branch still showing the original issues, with no login screen appearing at all (black screen until reboot).
If the problem is causing those kind of issues (X server crashes) it must be video software related...right?
dongers wrote: ⤴Tue May 21, 2019 6:19 pm
If the problem is causing those kind of issues (X server crashes) it must be video software related...right?
Not necessarily, could be about memory management or some other kernel function like that, which the garbled crash log and the fact that you can log in the second time do make more likely actually (there's no reason why a video driver issue would corrupt the crash log). Could also be a hardware defect only made visible by some kernel change. But without more details on the crash it's all just speculation.
Just removed the 5.x branch kernel and now the 4.15.0.50 kernel wont boot cleanly (black screens again)...booted into 4.15.0.47 and I'm good.
Now removing and blacklisting .50 and any subsequent kernel updates until we get some definitive movement/answers to the original bug report (and subsequent fixes downstream!)
I had a similar issue with one of my laptops last week. It turned out th boot sector was full. I broke out an old boot fix text file and it worked. I got rid of 7 old kernals and some other things. Then I was able to load and boot everything including the newest kernal.
