Bug#131553: missing keyboard selection?

2002-02-05 Thread Rich Johnson

Martin Michlmayr wrote:

 * Phil Blundell [EMAIL PROTECTED] [20020205 11:44]:
  Where did the adb (mac-ext) keyboards go?
  Selecting _any_ keyboard from the list prevents further input.

 ADB keycodes are no longer supported.  When your kernel sends ADB
 keycodes, console-data will say:

  Your kernel is configured to have the keyboard send ADB keycodes.  This
  behaviour is now deprecated and no longer supported by Debian.
  .

Thanks for the clarification, but it begs the question:
 How should one install the initial system _before_ being able to rebuild
the kernel?

I am currently up and limping.  I used debootstrap to load the base system and
then debootstrap's shell to obtain a benh kernel.  The process was rough and
the machine is not yet sure-footed enough to attempt kernel building.

--rich




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Bug#131709: chroot segfaults

2002-01-31 Thread Rich Johnson

package: boot-floppies
version: 3.0.18
architecture: powerpc
model: Mac 8500 /132 (old world firmware)
memory: 32M
scsi: on-board
cd-rom:apple, scsi interface

Manually invoking root.bin's /usr/sbin/chroot /target cmd from the
installer's shell always segfaults.

Perhaps this explains the Failure trying to run : chroot /target dpkg
encountered while installing the base system.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Bug#131709: chroot segfaults

2002-01-31 Thread Rich Johnson

summary of thread:

 On Thu, Jan 31, 2002 at 10:09:13AM -0500, Rich Johnson wrote:
  package: boot-floppies
  version: 3.0.18
  architecture: powerpc
  model: Mac 8500 /132 (old world firmware)
  memory: 32M
  scsi: on-board
  cd-rom:apple, scsi interface
 
  Manually invoking root.bin's /usr/sbin/chroot /target cmd from the
  installer's shell always segfaults.
 
  Perhaps this explains the Failure trying to run : chroot /target dpkg
  encountered while installing the base system.

 Does it segv before or after it chroots? It may be that cmd that it is
 trying to execute is segv'ing, and that would be an important bit of
 information.


reply 1(rich):
I poked around a bit more.   I've distilled some of the results below/

The machine state is the result of:
1)  booted from floppies (mac_hfs_boot, root.bin)
2)  downloaded kernel  drivers from ftp.us.debian.org
3)  downloaded base .debs from ftp.us.debian.org
4)  extracted base .debs from ftp.us.debian.org
5)  installation of base .debs failed with  Failure trying to run : chroot
/target dpkg

command result
-+

/usr/sbin/chroot / sh   works.
/usr/sbin/chroot /target sh
/usr/sbin/chroot /target /usr/bin/dpkg segfault
/target/usr/bin/dpkgprints a usage
message
/usr/sbin/chroot /target /bin/bash   segfault
/target/bin/bash  error loading

shared libraries ...libncurses.so.5

note:  /target/lib/libncurses.so.5 exists

/lib/libncurses.so.5 does not

#...but, if /target/lib/libncurses.so.5 is coped to /lib:
/target/bin/bash  segfault !!

Hmmm, It's just a guess, but perhaps the problem lies somewhere in the
truncated shared libraries?  Maybe a version skew?


reply 2(ben):

Try copying /bin/sh to /target/bin/bf-sh and do:

/usr/sbin/chroot /target /target/bin/bf-sh

I don't think this is a truncated libc problem, because the libc in the
chroot is not truncated.

reply 3(rich):

cp /bin/sh /target/bin/bf-sh
/usr/sbin/chroot /target /bin/bf-sh # segfault

Maybe truncated wasn't the right word.  But,  I get these results from ls -l:

size   date   path
--+--+--
   753604 Dec 20 /lib/libc2.2.4.so
   753604 Dec 20 /lib/libc.so.6

 1291932 Dec  5 /target/lib/libc2.2.4.so
 1291932 Dec  5 /target/lib/libc2.2.4.so.dpkg-tmp
   22 Jan 30 /target/lib/libc.so.6 -
/target/lib/libc2.2.4.so.dpkg-tmp

reply 4(ben):

I have a feeling that ppc ld.so or libc is broken. Could be wrong, but
try emailing the debian-ppc list to see what they say.

Yes, the libc on the boot disks is stripped down. But I assume the segv
is occuring in /target, not in chroot. Try doing this:

/target/usr/sbin/chroot /target /bin/sh

reply 5(rich)
 /target/usr/sbin/chroot /target /bin/sh
Another segfault; alas.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Bug#131361: MacOS dbootstrap not recognizing partitions from pdisk@dogstar-interactive.com

2002-01-28 Thread Rich Johnson

package: boot-floppies
version: 2.2.26
architecture: powerpc
model: Mac 8500 /132 (old world firmware)
memory: 32M
scsi: on-board
cd-rom:apple, scsi interface

dbootstrap doesn't recognize either ext2 or swap partitions on an
existing disk.
Partitioning was done from MacOS, and these partitions were previously
used for LinuxPPC.

fdisk (mac-fdisk) reports type Linux_PPC in the system column, but
Unknown in the type column





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]