Skip to Content.
Sympa Menu

baslinux - Re: [BL] Compaq Deskpro and Presario versus Basiclinux

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: sindi keesan <keesan AT sdf.lonestar.org>
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] Compaq Deskpro and Presario versus Basiclinux
  • Date: Tue, 1 Aug 2006 23:42:03 +0000 (UTC)

The Deskpro is now mostly usable. (Unless taking out the IDE drive messes up the SCSI drive).

Xvesa - the BL3 static version works fine, it was the Delilinux libc6 version that requires a lilo boot (on this computer that won't boot if you put in a lilo boot diskette, and won't boot linux if you bypass config.sys, and would not do Xvesa with config.sys and the libc6 Xvesa).

SVGA and Mach64 X servers work fine with Steven's generic XF86Config. I tried xf86config on the Mach64 and got something that appeared to be 1280 virtual and 800 actual, not useful. I added 1024 and 1280 modelines to the generic config file.

The moral - stick with Steven's Xvesa and his no-xvesa.tgz for computers that don't do Xvesa.

zgv - I have zgv-uclibc and the Delilinux libc6 zgv on the computer.

BL3 with 2.2.26 kernel works with zgv-uclibc if I add the required uclibc libraries and update libvga too. I did not try the older libc6 zgv there.

BL2 2.2.16 works with libc6 zgv. I did not try uclibc zgv there.

For the scsi drive I am using kernel 2.4.31, which I cannot get to work with either zgv in BL3. The libc6 one segfaults. David's uclibc one has mmap error rr.

In BL2 2.4.31 the uclibc zgv won't work, some problem with libc6 in the error message. The older libc6 version works with 2.4.31 in BL2.

I don't know how much of the problem is related to this hardware and how much to my kernel and how much to scsi.

So I need to use BL2 for zgv with scsi.

I put in the scsi drive and an IDE drive from my other computer and copied the files to the IDE drive. The scsi controller in the other computer had started failing and I had been trying to copy files and /etc got messed up somehow so I copied cp -a /etc/* from a good installation to both drives and now it won't boot but it will chroot. It may have bootyed before I copied over inittab and a few other things, but now it tells me to reboot.


It gets stuck in rc.S checking file systems and says something is wrong but I can type root and boot anyway. It appears to be checking the third drive in here (one I was using to boot BL from to do the file transfer) but e2fsck on that drive says the partition it gets stuck on is okay.

I will try the drive in another computer, but what might I have messed up by copying over parts of /etc between computers? I had somehow replaced a few BL2 files with ones from BL3 when the scsi controller failed.

What other than files in /etc could cause this type of refusal to boot?

e2fsck found no problems on either of my drives.

Sindi




Archive powered by MHonArc 2.6.24.

Top of Page