I'm installing a new linux machine, and I chose Debian 1.3.1rev6
for various reasons I won't go into here.
The install kernel is 2.0.29, and I immediately went forward to
compile 2.0.30. While I'm sure this is several revisions backlevelled by
now, bear with me.
The syst
[EMAIL PROTECTED] (Timothy J. Miller) writes:
> What am I missing? Or should I return *both* set of sticks and
> give up?
Okay-- here's an update:
I hit the sig11 page I was pointed to and read it. I tried
disabling the cache to no effect. I *did* discover
[EMAIL PROTECTED] (Timothy J. Miller) writes:
> So I swapped the sticks. The memory test *still* failed at
> 11Mb. Reenabled the cache and it still fails at 11Mb.
*sigh* Failed at *17Mb*. Succeeded at *16Mb*. I *will* remember
to calculate in HEX, I *will* remember to cal
I'm attempting a new install on the ThinkPad 365XD w/800x600
display, 40Mb RAM, CDROM and external floppy; at boot, the system reports
root.bin loaded, then linux, then it simply halts.
I've created 3 rescue disks on three different diskettes from two
different downloads, and all h
Paul Rightley <[EMAIL PROTECTED]> writes:
> I thought that the consensus was that the 365XD cannot boot bzImages.
> I went the route of installing Debian 1.1 (with boot disks using
> zImages) and then upgrading. The most direct solution is to compile
> an appropriate zImage on a working Linux mac
[EMAIL PROTECTED] (Timothy J. Miller) writes:
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (minix filesystem)
> [MS-DOS FS Rel. 12,FAT 0,check=n,conv=b,uid=0,gid=0,umask=022,bmap]
> [me=0x0,cs=0,#f=0,fs=0,fl=0,ds=0,de=0,data=0,se=0,ts=0,ls=0]
> Transaction b
Someone sent me mail with the comment that X11_SVGA on the
non-TFT displays is a bear to configure properly.
He's right.
Unfortunately I lost his email address, and need to correspond
with him a bit more on the matter.
--
Cerebus <[EMAIL PROTECTED]>
PGP Fingerprint:
I'm compiling a 2.4.13 kernel with patches from non-debian sources.
"make-kpkg --initrd --config oldconfig kernel_image" produces an
installable package with proper symlinks to an initrd, and lilo works
fine.
But when booting the image it cannot mount the root cramfs.
Looking in the archives, I
On Thu, 2001-11-08 at 11:52, Jeremy T. Bouse wrote:
> Not sure I follow what you're trying to do with cramfs but I've
> not had to use the cramfs packaging at all... I just use mkinitrd in the
> initrd-tools package and haven't had a problem...
Done that, to no effect. All I'm trying to do
On Thu, 2001-11-08 at 15:33, Morbo wrote:
> It sound like the same or very similar problem I had with every single
2.4.x
> kernel I've tied.
> In my case LILO started loading and after putting some dots on the screen
> the PC just rebooted.
You're not getting far enough for initrd to make a diffe
://1tmiller.com/DownLoadIt/links.html
Thank You For Your Time,
Timothy J Miller
link to - http://1tmiller.com/DownLoadIt
11 matches
Mail list logo
