Skip to main content

Laptop PC trouble after upgrade to Debian 9 (stretch), and solution

The last new year holidays was more than a month ago. it was a good chance to make a major version upgrade on my PC.
I upgraded my laptop PC from Debian 8 (Jessie) to Debian 9 (stretch).
During the upgrade, I did encountered several times, but no serious trouble.
I started to enjoy the lightdm login console showing up with the Debian 9 new theme.

But when I booted it without AC power supply, the boot sequence ended in strange way. The lightdm did not show up. Instead, a black screen remains with many error messages.

I searched for a hint in the log files in /var/log directory, and found that the root file system was mounted in read-only mode.
With this hit, I search for any hints around the world and found a similar problem in the bug database in http://bugs.debian.org/ It seemed to imply that laptop-mode-tools package was involved.

In order to test whether the laptop-mode-tools is involved in my case, I installed tlp package which conflicted with laptop-mode-tools.
With tlp instead of laptop-mode-tools, the strange boot problem resolved.

If you are in similar trouble booting Debian 9, I would like to suggest tlp package instead of laptop-mode-tools.

Comments

Popular posts from this blog

Configuring Network Manager for PPPoE connection

When I'm home, I use fiber-optic line with a dedicated old small router (YAMAHA RT107e) for access to the Internet. But I recently became anxious about the router. If it fails, how can I survive until I get another one? So, I tried to connect my Debian desktop PC to the fiber-optic line without the router. The PC have to talk to the other side of the line with PPPoE but I did not know how. In my PC, the Network Manager manages network configuration. So, I had to configure the Network Manager to utilize the pppoe like : nmcli connection add ifname eth0 connection.type pppoe username USERNAME password PASSWORD

Xen on Squeeze failed to start up the X server with an Intel graphics controller

I recently tried to set up Xen on my Squeeze box, with intel 945GM graphics controller. I followed the instruction on Xen - Debian Wiki . I installed the Xen hypervisor, kernel, xen-tools and other stuff, then created a domU image of Ubuntu natty. After that, I rebooted the system. But when X server was about to be launched, the screen became black out,  both keyboard and mouse don't work anymore. I reread the article on the wiki, and figured out the Xorg driver for Intel graphics controller  is suspicious. So, I changed the Xorg driver 'intel' to 'fbdev' wrting /etc/X11/xorg.conf , and rebooted.  This workaround works out! The drawback of the workaround is, 'intel' driver specific features, including DRI and XvMC, are disabled.

Sharing one home directory between the Linux machines with the different display resolutions and different pointing devices, keeping $HOME/.config data for each machine

 Back in 1990's, it was common practice to share one home directory between many UNIX servers using NFS. But it is not in these days. But I have become to want to share my home directory between two different Linux machines: One is  a Debian GNU/Linux installed as a primary OS of a dual boot machine,  and the other is a virtualized Linux box within the Virtualbox running under the Windows 10, a secondary OS of the dual-boot. They have different display resolutions and pointing devices. These differences led me to an annoying problem: if you open GNOME desktop environment, display and pointing device setting became broken. Today's GNOME desktop environment stores most of the settings to the files under $HOME/.config directory. But if you share $HOME/.config between two machines, the stored configuration for a particular machine may become incompatible with other machines with different display resolutions and pointing devices. Indeed, my GNOME desktop has become unusable. To ove