All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Steffl <steffl@bigfoot.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA HD 137GB limitation?
Date: Wed, 06 Aug 2003 00:30:43 -0700	[thread overview]
Message-ID: <3F30AEA3.2080007@bigfoot.com> (raw)
In-Reply-To: <3F2D52FB.5040304@pobox.com>

Jeff Garzik wrote:
> I just realized, 2.4 kernels don't support scsi's READ_CAPACITY_16, nor 
> 64-bit sector_t on a 32-bit processor.
> 
> Can you test Alan Cox's 2.6.0-test-ac tree?  I bet the 137GB limitation 
> may disappear there.

   thanks,

   just tried 2.6.0-test1-ac3 but it fails, is there a particular 
version that might work?

   will the READ_CAPACITY_16 and 64-bit sector_t be ported to 2.4 tree? 
or do I have to wait for usable 2.6?

   2.6.0-test1-ac3 complies OK but when installing modules there are 
number of unresolved symbols:

  INSTALL lib/zlib_deflate/zlib_deflate.ko
   INSTALL lib/zlib_inflate/zlib_inflate.ko
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 
2.6.0-test1-ac3; fi
depmod: *** Unresolved symbols in 
/lib/modules/2.6.0-test1-ac3/kernel/crypto/def
late.ko
depmod:         zlib_inflateInit2_
...
depmod:         zlib_deflateReset
depmod: *** Unresolved symbols in 
/lib/modules/2.6.0-test1-ac3/kernel/drivers/bl
ock/paride/paride.ko
depmod:         parport_unregister_device
..depmod:         parport_find_base
depmod: *** Unresolved symbols in 
/lib/modules/2.6.0-test1-ac3/kernel/drivers/ch
ar/agp/nvidia-agp.ko
depmod:         agp_remove_bridge
...
depmod:         agp_generic_alloc_by_type
depmod: *** Unresolved symbols in 
/lib/modules/2.6.0-test1-ac3/kernel/drivers/ch
ar/lp.ko
depmod:         parport_read
...
depmod:         parport_release
depmod: *** Unresolved symbols in 
/lib/modules/2.6.0-test1-ac3/kernel/drivers/ch
ar/ppdev.ko
depmod:         parport_read
...

   I tried to boot the kernel anyway and it fails to boot, right after 
LILO line and checking BIOS line it stars to print something so fast 
that I have no idea what it is, no keys work, only hw reset... found 
nothing relevant on lkml archives... any ideas why it fails (or which 
version would be more likely to work)?

   TIA

	erik


  reply	other threads:[~2003-08-06  7:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24  1:17 SATA HD 137GB limitation? Erik Steffl
2003-07-24 17:12 ` Jeff Garzik
2003-07-24 17:43   ` Erik Steffl
2003-08-03 18:22     ` Jeff Garzik
2003-08-06  7:30       ` Erik Steffl [this message]
2003-08-06 20:00       ` kernel 2.6.0-test1-ac3: unresolved symbols in modules Erik Steffl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F30AEA3.2080007@bigfoot.com \
    --to=steffl@bigfoot.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.