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

Re: 2.1 kernels on SX164?



Peter Rye wrote:
> 
> >>>>> "Quant-X" == Quant-X Alpha Linux Support <stefan@sime.com> writes:
> 
>     Quant-X> Hi !
>     >> >>>>> "Don" == Don Crimbchin <djc2@andrew.cmu.edu> writes:
>     >>
>     Don> Is it possible to use a 2.1 kernel on an SX164?  I compiled
>     Don> 2.1.103, and when MILO attempted to load it, it gave me soemthing
>     Don> like this:
> 
>     Quant-X> A customer has reported a problem like this.  I told him to
>     Quant-X> strip the kernel-image (before gzipping ;-}) and it worked.
> 
> This should be done for you if you "make boot". I wonder if he just did
> "make vmlinux" or similar?
> 

Well, I thought I used "make boot".  I untarred the sources 
and patched them again yet again, and ran "make boot" again, 
and this time kernel managed to load.  I'm really not sure 
what I did different.

Althought the kernel loads now, it gives me lots (LOTS!) of 
errors to the console like this:

  CPU[0]: where [fffffc000031735c] glocked[1] gicnt[1] licnt[1]

One rather important thing i forgot to mention--(because I 
thought the problem was with MILO, rather than the kernel) 
when I was building the kernel, I got two parse errors in 
ide-probe.c.  (I have IDE, not SCSI).  

The parse errors were at lines 531 and 696

devices/block/ide-probe.c

531: #if (DEBUG_SPINLOCK > 0)
532:		printk("hwgroup(%s) spinlock is %p\n", hwif->name, 
&hwgroup->spinlock);	/* FIXME */
533: #endif

696: #if (DEBUG_SPINLOCK > 0)
697: {
698:	static int done = 0;
699:	if (!done++)
700:		printk("io_request_lock is %p\n", &io_request_lock);    /* FIXME
*/
701: }
702: #endif


I figured that because I had no idea how to debug anything, I 
should comment these lines out.  (Which I know is probably a 
dumb thing to do.)  

I also tried chaning 

  #if (DEBUG_SPINLOCK > 0)

to 

  #ifdef DEBUG_SPINLOCK


(Could everyone please stop laughing at me now? ;-)  )

Anyway, whether or not anyone can help me with this, you two 
have been very helpful already.  (Who knows how long I would 
have spent playing with MILO images?)  

Don Crimbchin



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