[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problems installing Sarge (Debian 3.1r7) on Amiga 4000T



On Tue, 29 Jan 2008, Daniele Gratteri wrote:
> It has been some time since when I was trying to install Debian with the
> 2.4.27 kernel included on the CD-ROM: it gave me kernel panic, because of the
> buggy NCR 53C710 SCSI driver. But, at least, it displayed on screen something.
> 
> A couple of days ago I wrote to Christian T. Steigies asking him to enable
> support for 53C710 controllers in the kernel images he compiles: he replied
> and I had the ability of trying an experimental kernel, which seems to be
> working, strictly speaking of SCSI, but gives me headaches because it won't
> show anything on screen! But this is common to other 2.6 kernels.
> 
> This is the output of dmesg:
> 
> Searching for SAVEKMSG magic...
> Found 4448 bytes at 0x001dc010
> >>>>>>>>>>>>>>>>>>>>
> Linux version 2.6.24-rc8-amiga (Debian
> 2.6.24~rc8-1~experimental.2~snapshot.10176) (waldi@debian.org) (gcc version
> 3.3.6 (Debian 1:3.3.6-15)) #1 Mon Jan 28 00:45:45 CET 2008
> Warning: no chipram present for debugging

> Warning: unable to open an initial console.
> 
> Now my SCSI controllers (onboard A4091 and Warp Engine) and peripherals are
> properly detected, no more panic :-)

Good!

> But the kernel seems to complain about no Chip RAM being available for debug,

This is harmless, as Christian's kernel obviously contains the temporary
workaround for the real problem. Else `dmesg' wouldn't have worked for you.

> and that it is unable to open a console (?).
> What the problem can be?

Does your root file system have /dev/console?

| $ ls -l /dev/console 
| crw------- 1 root root 5, 1 2008-01-27 13:46 /dev/console
| $ 

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


Reply to: