[Solved] Stuck at Starting Hostname Service...

[DeadTOm76]

This is after a fresh installation of Debian Bullseye, the system hangs at "Starting Hostname Service..." with no errors.

If I ctrl-alt-F5 and log into the console, and try a "systemctl start hostname", it returns "unit hostname.service not found".

Any idea where I go from here?

[donald]

Did you give the system a hostname?

If not,

Code: Select all

$ hostname newhostname

[DeadTOm76]

Did you give the system a hostname?

Yes, verified that the correct hostname is in /etc/hostname and /etc/hosts. Should I run the command anyway?

[DeadTOm76]

I tried it, no dice.

[donald]

When you run hostnamectl from the command line does it respond with hostname, icon-name and so forth?

Looks like this:

Code: Select all

 donald@domaster ~ $ hostnamectl 
   Static hostname: domaster
         Icon name: computer-laptop
           Chassis: laptop
        Machine ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
           Boot ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  Operating System: Debian GNU/Linux 11 (bullseye)
            Kernel: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      Architecture: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

[DeadTOm76]

When you run hostnamectl from the command line does it respond with hostname, icon-name and so forth?

Looks like this:...

Yes, it's returning all the right information.

[CwF]

If I ctrl-alt-F5 and log into the console, and try a "systemctl start hostname", it returns "unit hostname.service not found".

This suggest you getting a prompt, and what does it list as the domain?
Is the hang on "Starting Hostname Service..." or perhaps the following line returning the status of an interface. I'd expect a 'fail to raise' error on the next line. Have you waited for a timeout?

[DeadTOm76]

Fixed it by adding "nomodeset" to Grub.

Finally up and running.

Thanks!

[donald]

Ahhh, good fix. Please add a [solved] to the thread subject to help future searchers. Thank you.

[p.H]

No, "nomodeset" is never a good fix and is merely a workaround which degrades graphic resolution and performance because it disables kernel mode-setting and acceleration.
What is or are the GPU(s) ?

Code: Select all

lspci -nnkd ::0300 ; lspci -nnkd ::0302 ; lspci -nnkd ::0380

Are they supported by the running kernel ?
If AMD/ATI Radeon, is the package firmware-amd-graphics installed (required) ?
If Intel or Nvidia and using the driver "nouveau", is the package firmware-misc-nonfree installed (may help) ?

[DeadTOm76]

No, "nomodeset" is never a good fix and is merely a workaround which degrades graphic resolution and performance because it disables kernel mode-setting and acceleration.
What is or are the GPU(s) ?

Code: Select all

lspci -nnkd ::0300 ; lspci -nnkd ::0302 ; lspci -nnkd ::0380

Are they supported by the running kernel ?
If AMD/ATI Radeon, is the package firmware-amd-graphics installed (required) ?
If Intel or Nvidia and using the driver "nouveau", is the package firmware-misc-nonfree installed (may help) ?

I wondered about this, and continued to have graphics problems after this.

I'm using an AMD Radeon RX 6600.

Code: Select all

12:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [1002:73ff] (rev c7)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:5022]
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu

Using the shipped kernel (5.10), amdgpu refused to load. After hours of tinkering with it unsuccessfully, I installed kernel 6.0 from backports. This resolved all the graphics issues I was having, and no need for nomodeset.

So far, so good.

[p.H]

Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [1002:73ff] (rev c7)

It appears that this GPU is not supported by kernel 5.10.

Code: Select all

/sbin/modinfo -k 5.10.0-20-amd64 -F alias amdgpu | grep 'pci:v00001002d000073FF' || echo 'no match'

returns no match.

PS: No need to quote the whole previous post.

[donald]

Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [1002:73ff] (rev c7)

It appears that this GPU is not supported by kernel 5.10.

Code: Select all

/sbin/modinfo -k 5.10.0-20-amd64 -F alias amdgpu | grep 'pci:v00001002d000073FF' || echo 'no match'

returns no match.

I looked into this last night and found most complaints and fixes around this were Nvidia card users, good to knowledge that it is the GPU and not just a brand of card.

[p.H]

It appears that this GPU is not supported by kernel 5.10.

Thinking twice, nomodeset should not have any effect if no KMS driver is available for this GPU...