I've been trying out the 2.2.18pre kernel and no luck.
I still can't make a generic kernel. I've tried to use
the debian config file.. no luck. I'm now trying the
2.4 kernel.. yes.. very beta.. but we'll see if it's
fixed yet or not. I've also tried an older version of
aboot and the new version.. no change. This is not
good... I do believe it to be a kernel or aboot bug.
It does not appear to be a scsi problem for me though.
If the kernel starts the boot, I get a kernel swapper
Opps right after it sees my IDE CDROM.
--- Jesper Juhl <juhl@eisenstein.dk> wrote:
>
> > (1) Any luck with building working kernels?
>
> Unfortunately, no. You will not believe how many
> different configurations
> I have tried :-(
>
> Here's a list of what I have found so far:
>
> If I create a very mimimal configuration that only
> just support the
> hardware I have, then it does not Oops. I don't know
> exactely what option
> I'm excluding that causes the Oops seen previously,
> but that should be
> possile to work out once I get it to boot completely
> (see below).
> With the minimal config the kernel works no matter
> if it's GENERIC or
> Avanti, which I think is good news :-).
>
> Although the kernel no longer Oopses, I can still
> not boot it as it now
> seems to have some problems with my scsi controller.
> I have tried
> everything from the most conservative settings to
> the most agressive, but
> no matter what I choose it hangs at boot with this
> message:
>
> scsi : aborting command due to timeout : pid 0,
> scsi0, channel 0, id 0,
> lun
> 0 Test Unit Ready 00 00 00 00 00
>
> I have also tried the exact same settings that the
> debian kernel use
> (which boots fine on this box), but that does not
> work either - which
> seems very strange to me.
> I tried upgrading to the latest 2.2.18pre kernel,
> but that one has the
> same scsi issue (although it uses a newer version of
> the driver).
>
> Here is a dump of the relevant boot messages, first
> from the working
> debian kernel and then from my latest try with
> 2.2.18pre:
>
> 2.2.17 (debian kernel) :
>
> sym53c8xx: at PCI bus 0, device 6, function 0
> sym53c8xx: not initializing, device not supported
> ncr53c8xx: at PCI bus 0, device 6, function 0
> ncr53c8xx: 53c810 detected
> ncr53c810-0: rev=0x01, base=0x4200000,
> io_port=0x8000, irq=11
> ncr53c810-0: ID 7, Fast-10, Parity Checking
> ncr53c810-0: restart (scsi reset).
> scsi0 : ncr53c8xx - version 3.2a-2
> scsi : 1 host.
> Vendor: QUANTUM Model: FIREBALL ST4.3S Rev:
> 0F0C
> Type: Direct-Access ANSI
> SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 0,
> lun 0
> Vendor: DEC Model: RRD45 (C) DEC Rev:
> 0436
> Type: CD-ROM ANSI
> SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 4,
> lun 0
> ncr53c810-0-<0,0>: tagged command queue depth set to
> 8
> scsi : detected 1 SCSI cdrom 1 SCSI disk total.
> ncr53c810-0-<4,*>: FAST-5 SCSI 4.0 MB/s (250 ns,
> offset 8)
> Uniform CD-ROM driver Revision: 3.11
> ncr53c810-0-<0,*>: FAST-10 SCSI 10.0 MB/s (100 ns,
> offset 8)
> SCSI device sda: hdwr sector= 512 bytes. Sectors=
> 8471232 [4136 MB] [4.1
> GB]
> eth0: DE434/5 at 0x8800 (PCI bus 0, device 12), h/w
> address
> 00:00:f8:22:2c:32,
> and requires IRQ14 (provided by PCI BIOS).
> de4x5.c:V0.544 1999/5/8 davies@maniac.ultranet.com
> Partition check:
> sda: sda1 sda2 sda3
>
>
>
>
> 2.2.18pre :
>
> ncr53c8xx: at PCI bus 0, device 6, function 0
> ncr53c8xx: 53c810 detected
> ncr53c810-0: rev=0x01, on pci bus 0 device 6
> function 0 irq 11
> ncr53c810-0: ID 7, Fast-10, Parity Checking
> scsi0 : ncr53c8xx-3.4.1-20000726
> scsi : 1 host.
> scsi : aborting command due to timeout : pid 0,
> scsi0, channel 0, id 0,
> lun
> 0 Test Unit Ready 00 00 00 00 00
> ncr53c8xx_abort: pid=0 serial_number=1
> serial_number_at_timeout=1
>
>
> it hangs here...
>
> Here's the scsi related info from proc :
>
> root@odin:/usr/src/linux# cat /proc/scsi/ncr53c8xx/0
> General information:
> Chip NCR53C810, device id 0x1, revision id 0x1
> IO port address 0x8000, IRQ number 11
> Synchronous period factor 25, max commands per lun
> 32
>
> root@odin:/usr/src/linux# cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: QUANTUM Model: FIREBALL ST4.3S Rev: 0F0C
> Type: Direct-Access ANSI SCSI
> revision: 02
> Host: scsi0 Channel: 00 Id: 04 Lun: 00
> Vendor: DEC Model: RRD45 (C) DEC Rev: 0436
> Type: CD-ROM ANSI SCSI
> revision: 02
>
>
>
> Any ideas on what could be wrong?
>
>
>
> > (2) Does anyone have any experiences with X they
> would like to share?
>
> Unfortunately the kernel I'm using to boot is not
> compiled with support
> for the ATI Mach64, so I cannot use the Framebuffer
> X server. All the
> other servers refuse to start, with the exception of
> the mono server and
> the Mach64 server. The mono server starts but
> presents me with a
> completely messed up screen, and starting the Mach64
> server has the
> effect of dumping me straight back in the SRM
> console.
> The graphics card in this box is a ISA based Mach64
> GX (chip is:
> 210888GX00, RamDac is: AT&T PrecisionDAC
> ATT20C408-13).
>
>
> /Jesper Juhl
>
>
=====
******************************************************
* Octave J. Orgeron * Specializing in : *
* Unix Systems Administrator * Solaris/Tru64/Linux *
* Sun Microsystems, Inc. * Certified Solaris *
* octave@sun.com * Systems Administrator *
******************************************************
__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/
This archive was generated by hypermail 2b30 : Fri May 09 2003 - 10:00:02 PDT