SUSE10.1 - no option given to set root password

[fishface]

I'm trying to install SUSE10.1 on a clean system, it installs, but at no point am I given an option to setup a root password, so when it starts up for the first time I get the logon prompt, so what do I enter?

I've installed SUSE9.2 many many times and it always asked you to set-up a root password during the installation process - this version just seems to skip that bit.

[moopaws]

I'm suprised it didn't prompt you for a password, but first I would try logging into root with no password and seeing if that works. If that fails, check out this wiki:

http://wiki.suselinuxsupport.de/wikka.php?wakka=HowToResetlostrootpassword

[fishface]

That was the first thing I tried - and various other combinations.

I've now tried SUSE10.1 again, from another DVD, and it is the same - so it has failed twice with 1 DVD and once with another DVD.

I also tried SUSE9.2, same problem, except it hangs at the point where YAST states it is configuring the root password, it hangs there, little time icon (watch) just whizzing around, been like that for 4 hours now :mad:

[moopaws]

Ok, do the install just as you normally do with 10.1
Once installed, use a knoppix livecd or something like the lightweight Gentoo Install cd, mount your suse install, chroot (it wont ask for a password), and simply change your root password :)

[cybertron]

That's bizarre. Does it ask you to configure a regular user either? I just did about 10 Suse 10.1 installs and each and every one of them asked me for a root password (granted I was using the 5 CD installer, so it's possible there's a bug on the DVD, but it seems very unlikely). Are you using Autoyast or something to do the install (doesn't sound like it, but that's the only thing I can think of that would do this)?

[fishface]

This just a very plain old SUSE install, nothing fancy. Both DVDs have be used successfully on other install - different hardware though.

I have installed SUSE many times, and this the first time I've seen this error. I've had install problems before (usually locking up) but this has been down to hardware compatabilty issues vs the varying kernels. This problem is just weird, but it can be repeated every time.

I cannot really use a work around (boot from Knoppix et al) as I'm using this install as base image for software testing so it has to be plain vanilla as possible.

[cybertron]

Out of curiousity, what kind of hardware are you installing on? It just seems very odd that a hardware incompatibility would mess up user creation. If you need a workaround you might try looking into Autoyast. You can set up all of the configuration stuff on another working Suse system and then just point the installer at it. It would still be a standard install, but might get you around the installer bug that you're hitting.

[fishface]

Mainboard is this http://www.motherboard.cz/mb/ecs/K7VMM+.htm with an AMD XP2000, 1GM memory, 40GB Hitachi HD, no additional cards installed, using onboard G/C and NIC

[fishface]

Might have a hardware issue here. I tested the Seagate HD using their diagnostic tools, it past the first basic test, I then test it again, with the other basic test and it states 'bad device' - the Seagate report tool is a bit confusing as it states that the drive past the test and is ok at the beginning, then further down it notes the 'bad device'. Anyways, I ran the diagnostic twice more and it passes all of them, but the drive seems to be getting unusually hot for my liking, so I decide to try XP out on it - it fails to install as well, I get a blank screen just after it says it is examing your hardware...so I'm starting to think duff HD.

I try XP with the same Seagate HD, it fails at the formatting stage, try two Maxtor drives, same result, both of the Maxtor drives have past extensive testing with Maxtor diagnostics, so I'm begining to think I have a fault on the mainboard or something, HD controller maybe...I've had it happen before on other systems,especially after PSU failure or power surges.

So, thats where I'm at with it!

[cybertron]

Yep, sounds like a hardware issue to me. Maybe check for a bad cable too if you've been using the same one. Would be cheaper than a new motherboard at least.:)