I recently bought an Inspiron 530 running Ubuntu Hardy Heron from Dell. Either it was shipped to me before it had been properly configured or something went wrong in the initial boot (see later).
The most obvious symptom of the problem is that username oem is automatically logged in. To use my own username, i.e. the one created by adduser during the initial boot, I have to log out the oem session and then log in again. I know why the autologin of oem is occurring and hence I know which file needs editing to stop it. Unfortunately that leads me on to the most severe symptom of the problem...
When it was created during the initial boot my own username was not added to the admin group. The only member of the admin group is oem. I, of course, do not know the oem password. Therefore there is no way I can use sudo.
I thought I knew how to get out of this impasse. I hit ESC at the appropriate stage of the boot so that grub would give me a list of boot options. I selected
Ubuntu 8.04, kernel 2.6.24-16-generic (recovery mode)
in the belief that it would boot up in single-user mode. Alas it appeared to do a normal boot. I repeated this procedure and paid attention to the messages appearing on the screen. I'm fairly sure I saw a reference to being unable to do 'init 1', together with an error number. I repeated the procedure again, intending to record the exact details of the error message but got a different one, namely:
root=UUID=8369f4ef-bc20-4d3a-8912-f9e18d5a7a31 ro all_generic_ide quiet
kinit: name_to_dev_t(/dev/disk/by-uuid/66b05f48-e346-4baa-a0d2-2d871a9ac2fc) = sda5(8,5)
kinit: trying to resume from /dev/disk/by-uuid/66b05f48-e346-4baa-a0d2-2d871a9ac2fc
kinit: No resume image, doing normal boot..
That is the error message that now occurs very time I try the recovery-mode boot.
I mentioned above that I suspected that either the PC was shipped to me before Dell had configured it properly or that something had gone wrong in the initial boot. An error certainly was reported during the initial boot (the monitor had come with two cables and no indication of which one should be used; one cable was already connected to the monitor, so I used that one and it proved to be wrong). Although the initial boot continued, e.g. prompting me for details of a username to be created, it occurs to me that maybe some of the script was unable to run because of the incorrect monitor configuration.
I've now exhausted my knowledge of how to gain control of my own PC. I'm looking for the following:
* Suggestions about what I can do to gain control.
* Speculation about what else might be wrong, i.e. what else might not have been done by the initial boot. Better yet, is the script that the initial boot ran likely to be around somewhere so that I can check it out?
Thanks in advance.