Hi. Thank you for working on these programs. Unfortunately I'm having trouble installing the BDI 4.30 version. I'm not a complete newby, have used Redhat, and now Debian on other PC's. I've checked the md5sum of the iso downloaded, and of the CD itself. I've turned "detect virus by trend" off in the bios, and am using LBA mode for the 40G hard drive, and reburnt the CDRW to a CDR just incase, all as suggested in the FAQ. The install starts fine, all packages are then installed, but when the screen saying "post install config" or something pops up it crashes. The PC I'm trying to install on is a 500MHz AMD K6II processor, with 128MB RAM. I think there was a problem with BDI on K6 processors, but think newer versions of BDI are OK. I'm trying to use LVM too, with my own partitioning scheme, based on that I've used on my desktop PC. I'm trying the graphical install since there's a problem with text installations mentioned in one of the docs. I've been testing the memory and hard drive incase they could be faulty, but haven't found a problem with 13 hours of memtest86+ and full drive scan using badblocks destructive test. I'm just setting an "automatic" install running incase that works. I like lvm though, so it'd be a shame to loose that. If I can get it installed I could then set up lvm on another drive and move the install.... I've looked at the install.log and install.log.syslog files by booting the PC using Knoppix, the first lists 475 packages, the second lists user creation commands, which I think must have failed since I don't have any user directories created under /home. Well, the "automatic" install works a little better, at least it boots, but the user account I created doesn't exist, so I cannot do a graphical login-root is blocked. Logging into a command prompt I've looked again at the log files. install.log this time has the list of packages installed, then those available which weren't installed, then says: Changing configs on 23-12-2005 User name not found - anaconda bug ? root login not allowed by kdm etc.... I'm wondering about trying either a minimal install with lvm, or running the upgrade script on the partially working version. Anyway, I wonder if you might be able to investigate this further for me? I can supply any other details/files you need. I'd like to try emc out-and this has unfortunately been a fraustrating start! Happy Christmas, Arthur
Hi Arthur On Friday 23 December 2005 23:36, Arthur Butler wrote:
Well, the "automatic" install works a little better, at least it boots, but the user account I created doesn't exist, so I cannot do a graphical login-root is blocked. Logging into a command prompt I've looked again at the log files. install.log this time has the list of packages installed, then those available which weren't installed, then says:
Changing configs on 23-12-2005 User name not found - anaconda bug ? root login not allowed by kdm
This is usually a result of not creating a usr account, but you say you had. There was a problem with upper case characters in the usr name silently causing the account creation to fail (which should be fixed..). Any chance you can remember the name and passwd used ?
I'm wondering about trying either a minimal install with lvm, or running the upgrade script on the partially working version.
The upgrade script on the CD is only there for pre BDI-4.24 installs. Running it on a fresh 4.30 install shouldn't have any effect. As for LVM support, the dm-mod.ko module is compiled, so in theory, LVM should work. However, this is another area that I haven't tested or used (too little time). The most likely reason LVM failed may be because dm-mod hasn't been added to the /etc/modules list. If this is the case, it would be a bug in the anaconda sources and more bug hunts for me.. I had got LVM earmarked for removal if/when additional space was required for other packages.. If you already have another computer running a Debian install, there is nothing to stop you from using the emc & kernel packages - I know of a couple of users who have installed the debs on Ubuntu systems with little difficulty. Regards, Paul. -- From the Klingon book of C: Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM.
Hi Paul, Thank you for your comments, and those of Kent. I retried the install without capitals, since I had used them. Same result. I gave up, and used a Debian testing install, using the new experimental GUI installer for a laugh. I now, I think, have a working EMC box, but haven't yet built any of the electronics to run stepper motors with. Having done this install, I think I've realised what the problem may be since a similar thing happened with that install, but less severe, a few minutes with Knoppix and it was bootable. I feel a bit silly now, but would have expected the install script to check this if it is what I think. I called the normal user account "operator", and Debian already creates this user and group, so it fails! I wonder if my foolish error could be documented to help anyone else who might have that problem in future? A few other comments, if I may? I like the fact that you're using Debian-provided easy updates, and supports many architectures. I'm now using 256MB RAM, I just hadn't tested the second 128MB, so was installing without it. LVM works now. I'm also using xfs-a journeling file system, little bit faster than ext3, no efsck time, well-developed, and not subject to as many changes as reiser. I'm just tinkering, so I'm happy to try newer things-it doesn't have to work flawlessly like a server! Could you tell me which of your packages modifies /etc/apt/sources.list please? I'm using testing and a few other unofficial repositories too, so want to look out for it being changed by a new version of a package. This happened to me-I'd set up sources.list, then installed your packages, and lost it all! One of your bdi-branding packages (I forget which, but can tell you another day if you want) failed to install-it does 5 patches which didn't apply cleanly, so I've removed it. Do you use initrd kernels? When I installed your kernel I didn't get an initrd, so have created it myself. Could just be an issue with the experimental nature of the GUI installer I used-gave a lilo error during the install. Thanks again, Happy New Year, Arthur
participants (2)
-
Arthur Butler -
Paul