[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1106196: Failure to install Trixie RC-1, Could not verify system name.



Package: installation-reports

Boot method: <How did you boot the installer? CD/DVD? USB stick? Network?>USB stick
Image version: <Full URL to image you downloaded is best> 

https://cdimage.debian.org/cdimage/trixie_di_rc1/amd64/iso-cd/debian-trixie-DI-rc1-amd64-netinst.iso

Date: <Date and time of the install>Tuesday May 20 about 2:30 PM PST

Machine: <Description of machine (eg, IBM Thinkpad R32)>Thinkpad X1 Carbon Gen 9
Device Name	VBHLaptop
Processor	11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz   3.00 GHz
Installed RAM	32.0 GB (31.7 GB usable)
Storage	477 GB SSD UMIS RPETJ512MGE2QDQ
Graphics Card	Intel(R) Iris(R) Xe Graphics (128 MB)
Device ID	66B79932-B445-44EE-BCBD-E9D42E9CDCC9
Product ID	00330-80000-00000-AA594
System Type	64-bit operating system, x64-based processor
Pen and touch	No pen or touch input is available for this display

Partitions: Did not get that far

Output of lspci -knn (or lspci -nn): Did not get that far.

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [o]
Detect network card:    [o]
Configure network:      [E] Could not connect to Wavelink Router via DHCP, Static IP worked.
Detect media:           [o]
Load installer modules: [o]
Detect hard drives:     [o]
Partition hard drives:  [o]
Install base system:    [E] Could not verify system name
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]

Comments/Problems: It seems that it could not verify that this was RC1 Trixie. Went back to Bookworm
standard install and it sailed through the network setup..

<Description of the install, in prose, and any thoughts, comments
      and ideas you had during the initial install.>

The WPSK wifi setup could not connect to my Wavelink Halo X2 rev B Router running DHCP using either 
wireless password option using the "automatic setup" option. I reconfigured the network install to 
use a static ip address and it sailed right through the network setup.  Got through the install to 
finishing up the hard drive partitioning. It appeared to complete that and then announced it could
not verify the system name. I tried twice and it appeared that it was trying to verify it was Trixie
RC-1 and not Bookworm which failed. I was unable to get past this.  I fell back to the standard 
Bookworm network install which showed the same network bump and sailed all the way through to completing 
the install.  

Please make sure that any installation logs that you think would
be useful are attached to this report. (You can find them in the installer
system in /var/log/ and later on the installed system under
/var/log/installer.) Please compress large files using gzip.

I never got this far in the install process. I have no idea how to find the install log in any
event. One of the things that amazes me is that the install process in Debian assumes a level of user understanding
that is well beyond the average user. The expectation that a normal user understands the difference between the 
types of wireless password encodings (three different choices) and also what disk partitions are (and how to set them up) 
with the real possibility that they could destroy their installed other system suggests that this 
installer is not directed at most people. It would be perhaps a good idea to see if you can figure out how to 
simplify the wireless setup and disk setup. In any event perhaps a "protect my existing system and data" install mode 
might be worth considering. I realize that it is tough to find an installation process that both covers an 
extremely wide variation in hardware systems and still keeps the process simple so I applaud how well the
installer works and hope that it will continue to improve.  


In the bug report, describe what the problem is, including the last visible kernel messages in the event of a kernel hang. Describe the steps that you did which brought the system into the problem state.


Reply to: