Differences between i386 and ppc kernels?
dwa...@austin.ibm.com
Are there differences between the config files used to generate the
kernels shipped with Debian? I am specifically interested in i386 versus
ppc. I have a ThinkPad and PowerBook installed and configured identically
for Debian 2.2 (potato) except for X server and when I try to run dhcpd
on the PowerBook I get:
socket: Protocol not available - make sure CONFIG_PACKET and CONFIG_FILTER
are defined in your kernel configuration!
exiting.
The ThinkPad works fine. Is there a known problem with the dhcp package
or is this really evidence that different kernel config options are
used on the two architectures? If the latter is this intentional and
why?
Thanks
--
Dwayne Grant McConnell work: dwa...@austin.ibm.com
PowerPC Linux Team home: dg...@austin.rr.com
Linux Technology Center notes: dwa...@us.ibm.com
--
To UNSUBSCRIBE, email to debian-powe...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Adam C Powell IV
> The ThinkPad works fine. Is there a known problem with the dhcp package
> or is this really evidence that different kernel config options are
> used on the two architectures? If the latter is this intentional and
> why?
dhcp works fine with a kernel that supports it. As you say, the Debian i386
kernel has it, the Debian pmac kernel doesn't. Why? Got me!
Different configs are inevitable, as some things aren't available on some
platforms, and some things don't build everywhere, others don't run. Vastly
different configs as we have now are a problem, not sure of the reason. It's
currently being discussed in the "Motorola StarMax... quandry" thread.
-Adam P.
Welcome to the best software in the world today cafe!
Daniel Jacobowitz
> dwa...@austin.ibm.com wrote:
>
> > The ThinkPad works fine. Is there a known problem with the dhcp package
> > or is this really evidence that different kernel config options are
> > used on the two architectures? If the latter is this intentional and
> > why?
>
> dhcp works fine with a kernel that supports it. As you say, the Debian i386
> kernel has it, the Debian pmac kernel doesn't. Why? Got me!
Exactly what is needed? File a bug on kernel-image-2.2.17-pmac,
please.
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| d...@debian.org | | dm...@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
Brendan J Simon
Daniel Jacobowitz wrote:
> On Mon, Sep 25, 2000 at 06:32:53PM -0400, Adam C Powell IV wrote:
> > dwa...@austin.ibm.com wrote:
> >
> > > The ThinkPad works fine. Is there a known problem with the dhcp package
> > > or is this really evidence that different kernel config options are
> > > used on the two architectures? If the latter is this intentional and
> > > why?
> >
> > dhcp works fine with a kernel that supports it. As you say, the Debian i386
> > kernel has it, the Debian pmac kernel doesn't. Why? Got me!
dhcp appears works for me on my PowerMac-G4 and my PowerBook-G3.
I used the dhcpcd client.
Brendan Simon.
Adam C Powell IV
> On Mon, Sep 25, 2000 at 06:32:53PM -0400, Adam C Powell IV wrote:
> > dhcp works fine with a kernel that supports it. As you say, the Debian i386
> > kernel has it, the Debian pmac kernel doesn't. Why? Got me!
>
> Exactly what is needed? File a bug on kernel-image-2.2.17-pmac,
> please.
Done, see bug #72503.
Brendan J Simon wrote:
> dhcp appears works for me on my PowerMac-G4 and my PowerBook-G3.
> I used the dhcpcd client.
Do you use kernel 2.2.17-pmac from potato, or did you build your own?
-Adam P.
Welcome to the best software in the world today cafe!
dwa...@austin.ibm.com
>dhcp appears works for me on my PowerMac-G4 and my PowerBook-G3.
>I used the dhcpcd client.
The client works fine. Looks like the preferred DHCP client has changed
from dhcpcd to pump as of Debian 2.2 (potato. I am using pump on both
machines (and several others) successfully. My question was in reference
to the server package dhcp which runs the daemon, dhcpd. Looks like I'll
be opening a bug.
--
Dwayne Grant McConnell work: dwa...@austin.ibm.com
PowerPC Linux Team home: dg...@austin.rr.com
Linux Technology Center notes: dwa...@us.ibm.com
dwa...@austin.ibm.com
>On Mon, Sep 25, 2000 at 06:32:53PM -0400, Adam C Powell IV wrote:
>>
>> > The ThinkPad works fine. Is there a known problem with the dhcp package
>> > or is this really evidence that different kernel config options are
>> > used on the two architectures? If the latter is this intentional and
>> > why?
>>
>> kernel has it, the Debian pmac kernel doesn't. Why? Got me!
>
>Exactly what is needed? File a bug on kernel-image-2.2.17-pmac,
>please.
Okay, I'm in the process of submitting a bug and I realized I do not
actually have kernel-image-2.2.17-pmac installed. I have whatever kernel
is installed by the boot floppies. Does this mean I should
1. Submit the bug against kernel-image-2.2.17-pmac?
2. First install kernel-image-2.2.17-pmac, test again and then submit a bug?
3. Submit the bug against boot-floppies or some other package?
Just trying to do this right. My first bug report...
Adam C Powell IV
> >On Mon, Sep 25, 2000 at 06:32:53PM -0400, Adam C Powell IV wrote:
> >> dwa...@austin.ibm.com wrote:
> >>
> >> > The ThinkPad works fine. Is there a known problem with the dhcp package
> >> > or is this really evidence that different kernel config options are
> >> > used on the two architectures? If the latter is this intentional and
> >> > why?
> >>
> >> dhcp works fine with a kernel that supports it. As you say, the Debian i386
> >> kernel has it, the Debian pmac kernel doesn't. Why? Got me!
> >
> >Exactly what is needed? File a bug on kernel-image-2.2.17-pmac,
> >please.
>
> Okay, I'm in the process of submitting a bug and I realized I do not
> actually have kernel-image-2.2.17-pmac installed. I have whatever kernel
> is installed by the boot floppies. Does this mean I should
>
> 1. Submit the bug against kernel-image-2.2.17-pmac?
> 2. First install kernel-image-2.2.17-pmac, test again and then submit a bug?
> 3. Submit the bug against boot-floppies or some other package?
4. See what bugs have already been submitted vs. kernel-image-2.2.17-pmac by
visiting http://bugs.debian.org/ and determine whether it's best to submit a new
bug, send a new message to an old bug (e.g. mailto:72...@bugs.debian.org), or not
do anything because your problem is described completely by an existing bug.
Note: the index by package name seems to be a touch slow to update. If you search
for bug 72503 by number, it's there, but by package it's not. This is the bug I
just submitted earlier in response to this thread.
If you decide to submit a new bug, proceed with either 1 or 2 above, the only
disadvantage of 1 is that it will list the installed version as N/A.
It might be worth submitting a wishlist bug against boot-floppies requesting that
it register the installed kernel and modules with dpkg. The implementation might
be tricky, but it would make it easier to bug report against the installed kernel,
and to remove it, so it's worth asking for. Skimming the list of bugs against
boot-floppies doesn't turn up anything obvious. Do you want to do this or should
I?
-Adam P.
Welcome to the best software in the world today cafe!
dwa...@austin.ibm.com
>Daniel Jacobowitz wrote:
>
>> On Mon, Sep 25, 2000 at 06:32:53PM -0400, Adam C Powell IV wrote:
>> > dhcp works fine with a kernel that supports it. As you say, the Debian i3
>86
>> > kernel has it, the Debian pmac kernel doesn't. Why? Got me!
>>
>> Exactly what is needed? File a bug on kernel-image-2.2.17-pmac,
>> please.
>
One correction here is that the problem I have is with the DHCP server
not the DHCP client.
>Brendan J Simon wrote:
>
>> dhcp appears works for me on my PowerMac-G4 and my PowerBook-G3.
>> I used the dhcpcd client.
>
>Do you use kernel 2.2.17-pmac from potato, or did you build your own?
I used the one installed by the boot floppies which I assume to be
the same as kernel-image-2.2.17-pmac_2.2.17pre11-2.deb. I will build
my own to get around the problem but I wanted to get the bug reported
and better understand if Debian keeps the official config file as
similar as possible across architectures.
--
Dwayne Grant McConnell work: dwa...@austin.ibm.com
PowerPC Linux Team home: dg...@austin.rr.com
Linux Technology Center notes: dwa...@us.ibm.com
dwa...@austin.ibm.com
>> >>
>> >> > The ThinkPad works fine. Is there a known problem with the dhcp package
>> >> > or is this really evidence that different kernel config options are
>> >> > used on the two architectures? If the latter is this intentional and
>> >> > why?
>> >>
>386
>> >> kernel has it, the Debian pmac kernel doesn't. Why? Got me!
>> >
>> >Exactly what is needed? File a bug on kernel-image-2.2.17-pmac,
>> >please.
>>
>> actually have kernel-image-2.2.17-pmac installed. I have whatever kernel
>> is installed by the boot floppies. Does this mean I should
>>
>> 1. Submit the bug against kernel-image-2.2.17-pmac?
>> 2. First install kernel-image-2.2.17-pmac, test again and then submit a bug?
>> 3. Submit the bug against boot-floppies or some other package?
>
>4. See what bugs have already been submitted vs. kernel-image-2.2.17-pmac by
>visiting http://bugs.debian.org/ and determine whether it's best to submit a n
>ew
>bug, send a new message to an old bug (e.g. mailto:72...@bugs.debian.org), or
>not
>do anything because your problem is described completely by an existing bug.
>
>Note: the index by package name seems to be a touch slow to update. If you se
>arch
>for bug 72503 by number, it's there, but by package it's not. This is the bug
> I
>just submitted earlier in response to this thread.
>
>If you decide to submit a new bug, proceed with either 1 or 2 above, the only
>disadvantage of 1 is that it will list the installed version as N/A.
I think your bug report is sufficient. I'll install the kernel-image just
to make sure it does not fix the problem and then I'll build a kernel with
your supplied patch to make sure it fixes the problem.
>It might be worth submitting a wishlist bug against boot-floppies requesting t
>hat
>it register the installed kernel and modules with dpkg. The implementation mi
>ght
>be tricky, but it would make it easier to bug report against the installed ker
>nel,
>and to remove it, so it's worth asking for. Skimming the list of bugs against
>boot-floppies doesn't turn up anything obvious. Do you want to do this or sho
>uld
>I?
I'll open the wishlist bug against boot-floppies. Thanks for the advice.
Daniel Jacobowitz
> >It might be worth submitting a wishlist bug against boot-floppies requesting t
> >hat
> >it register the installed kernel and modules with dpkg. The implementation mi
> >ght
> >be tricky, but it would make it easier to bug report against the installed ker
> >nel,
> >and to remove it, so it's worth asking for. Skimming the list of bugs against
> >boot-floppies doesn't turn up anything obvious. Do you want to do this or sho
> >uld
> >I?
>
> I'll open the wishlist bug against boot-floppies. Thanks for the advice.
For reference, yes, you probably do have that kernel image package. At
present there is no way to register it at install, because we don't
install the whole kernel package - not its doc dir, for instance.
Maybe someday.
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| d...@debian.org | | dm...@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
Indraneel Majumdar
I'm new to the list (which I've joined after becoming bald in the last 2
days trying to sort out this problem ;-( I've looked at the archives (also
LinuxPPC archives) with no result. Please help.
I've downloaded potatoPPC 1st CD and have mounted it -o loop on my
SuSE/intel box and then exported it via nfs. I made boot and root disks
and installed the basic system on our PowerPC Workgroup Server 8550/200
with 2GB sda. Partitions look like:
Apple Partition map
/ 1.2GB
/var 600MB
swap 100MB
swap 100MB
after first reboot it asks for floppy again and doesn't boot from sda.
Booting from floppy is fine and I can also chroot to /target and work
there (but I can't continue the install). I've also tried to make
Apple_Bootstrap partition as hfs using MacOS CD and tried using ybin but
I'm obviously getting stuck somewhere. Can someone help? I'm using Mac for
the first time and have never worked on MacOS before (so I couldn't follow
many of the archive threads). I'm debating whether to use LinuxPPC but
debian is such a nice distro (on intel at least) that I don't want to
leave it.
TIA,
Indraneel
/************************************************************************.
# Indraneel Majumdar ¡ E-mail: indr...@123india.com #
# Bioinformatics Unit (EMBNET node), ¡ URL: http://scorpius.iwarp.com #
# Centre for DNA Fingerprinting and Diagnostics, #
# Hyderabad, India - 500076 #
`************************************************************************/
Ethan Benson
> Hi,
>
> I'm new to the list (which I've joined after becoming bald in the last 2
> days trying to sort out this problem ;-( I've looked at the archives (also
> LinuxPPC archives) with no result. Please help.
>
> I've downloaded potatoPPC 1st CD and have mounted it -o loop on my
> SuSE/intel box and then exported it via nfs. I made boot and root disks
> and installed the basic system on our PowerPC Workgroup Server 8550/200
> with 2GB sda. Partitions look like:
> Apple Partition map
> / 1.2GB
> /var 600MB
> swap 100MB
> swap 100MB
ok, not sure i get why you have 2 swap partitions, is this two disks?
or are you under the impression that the linux kernel still has a
limit of 128MB on swap partitions?
> after first reboot it asks for floppy again and doesn't boot from sda.
> Booting from floppy is fine and I can also chroot to /target and work
> there (but I can't continue the install). I've also tried to make
> Apple_Bootstrap partition as hfs using MacOS CD and tried using ybin but
don't do that, you cannot use the MacOS partitioner to create
GNU/Linux partitions including the bootstrap partition. see:
http://www.alaska.net/~erbenson/doc for help on partitioning with
mac-fdisk.
on other thing, you mention this is a 8550? is this correct? if so
you cannot use ybin/yaboot, as your machine is not a Newworld. the
bootloader you want is quik. also the bootstrap partition is not of
much use on oldworld macs unless you want to try and mess with
miboot. (which i don't want to go into..)
> I'm obviously getting stuck somewhere. Can someone help? I'm using Mac for
> the first time and have never worked on MacOS before (so I couldn't follow
> many of the archive threads). I'm debating whether to use LinuxPPC but
> debian is such a nice distro (on intel at least) that I don't want to
> leave it.
we need some more info, but i think your problem is trying to use
yaboot on an oldworld, that won't work.
--
Ethan Benson
http://www.alaska.net/~erbenson/
David Brown
> don't do that, you cannot use the MacOS partitioner to create
> GNU/Linux partitions including the bootstrap partition. see:
The 9.04 partitioner seemed to work fine for me, it even had an option to
make Linux/PPC partitions.
Dave
Adam C Powell IV
> On Tue, Sep 26, 2000 at 12:32:54PM -0500, dwa...@austin.ibm.com wrote:
> > I'll open the wishlist bug against boot-floppies. Thanks for the advice.
>
> For reference, yes, you probably do have that kernel image package. At
> present there is no way to register it at install, because we don't
> install the whole kernel package - not its doc dir, for instance.
> Maybe someday.
Hmm, on i386, du -s in the doc dir says it uses 7k (it tar-gzips into 3.2k), and the
rescue floppy comes with config.gz which is bigger than that, and about 40k free.
Of course there's the headache of registering existing files as an installed
package, though I suppose that has to be done for base-files anyway.
As you say, "maybe someday", the need is not that great but it seems a reasonable
wishlist bug.
-Adam P.
Welcome to the best software in the world today cafe!
Daniel Jacobowitz
> Hmm, on i386, du -s in the doc dir says it uses 7k (it tar-gzips into 3.2k), and the
> rescue floppy comes with config.gz which is bigger than that, and about 40k free.
> Of course there's the headache of registering existing files as an installed
> package, though I suppose that has to be done for base-files anyway.
Actually, base-files is different - we dpkg --extract it into the base
tarball, so it IS installed. Kernels are kept separately.
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| d...@debian.org | | dm...@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
Indraneel Majumdar
sorry for this late followup. I was busy with PostgreSQL. but potato is
still not booting on my 8550. Sorry for the long post, please help:
On Tue, 26 Sep 2000, Ethan Benson wrote:
> On Wed, Sep 27, 2000 at 02:23:24AM -0700, Indraneel Majumdar wrote:
> >
> > I've downloaded potatoPPC 1st CD and have mounted it -o loop on my
> > SuSE/intel box and then exported it via nfs. I made boot and root disks
> > and installed the basic system on our PowerPC Workgroup Server 8550/200
> > with 2GB sda. Partitions look like:
> > Apple Partition map
> > / 1.2GB
> > /var 600MB
> > swap 100MB
> > swap 100MB
>
> ok, not sure i get why you have 2 swap partitions, is this two disks?
> or are you under the impression that the linux kernel still has a
> limit of 128MB on swap partitions?
I thought any space after the first 128MB is left unused. Is this
incorrect? (previously swap partition _had_ to be less than 128MB to work
but that I guess was rectified).
>
> > after first reboot it asks for floppy again and doesn't boot from sda.
> > Booting from floppy is fine and I can also chroot to /target and work
> > there (but I can't continue the install). I've also tried to make
> > Apple_Bootstrap partition as hfs using MacOS CD and tried using ybin but
>
> don't do that, you cannot use the MacOS partitioner to create
> GNU/Linux partitions including the bootstrap partition. see:
>
> http://www.alaska.net/~erbenson/doc for help on partitioning with
> mac-fdisk.
>
I did. mac-fdisk is working fine, it was always working fine. I have
partitions like this now (in a bid to make easy test cycles):
Apple Partition map
/ 2.1GB
It still doesn't boot from sda
I'll explain again: I can stick in the boot floppy and install over NFS.
Everything is fine. I follow the installation menu and come to where it
wants to make linux directly bootable from hard disk. That happens (it
runs quik) and then wants to reboot. It reboots, ejects root floppy, and
shows gray screen of "?". Here is the quik.conf I can see when I boot
using floppy and mount the sda at /target:
partition=2 ## does not work even with partition=1
root=/dev/sda2
timeout=100
image=/vmlinuz
label=linux
read-only
I am able to run quik after booting from floppy with -C option. This is
the output:
Second-stage loader is on /dev/sda2
Config file is on partition 2
Writing first-stage QUIK boot block to /dev/sda2
Making /dev/sda2 bootable (map entry 2)
Writing block table to boot block on /dev/sda2
This is part of the dmesg output:
--------------
scsi0 : MESH
scsi1 : 53C94
scsi : 2 hosts.
mesh: rejecting message from target 0: 1 1 3
mesh: bs0=2f in msg_out
mesh: rejecting message from target 0: 19
mesh: bs0=2f in msg_out
mesh: rejecting message from target 0: f
Vendor: SEAGATE Model: ST32550N Rev: 3705
Type: Direct-Access ANSI SCSI revision: 01 CCS
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: ARCHIVE Model: Python 02830-XXX Rev: 576B
Type: Sequential-Access ANSI SCSI revision: 01
Vendor: MATSHITA Model: CD-ROM CR-8008 Rev: 8.0e
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi1, channel 0, id 3, lun 0
scsi : detected 3 SCSI generics 1 SCSI cdrom 1 SCSI disk total.
Uniform CD-ROM driver Revision: 3.11
SCSI device sda: hdwr sector= 512 bytes. Sectors= 4194058 [2047 MB] [2.0
GB]
eth0: MACE at 00:05:02:68:d9:09, chip revision 25.64
Partition check:
sda: sda1 sda2
--------------------
If this gets solved, we'll put debian on 2 more macs, so I'm really biting
my nails.
Thanks,
Indraneel
> on other thing, you mention this is a 8550? is this correct? if so
yeah, machine is a 8550/200
> you cannot use ybin/yaboot, as your machine is not a Newworld. the
> bootloader you want is quik. also the bootstrap partition is not of
> much use on oldworld macs unless you want to try and mess with
> miboot. (which i don't want to go into..)
>
> > I'm obviously getting stuck somewhere. Can someone help? I'm using Mac for
> > the first time and have never worked on MacOS before (so I couldn't follow
> > many of the archive threads). I'm debating whether to use LinuxPPC but
> > debian is such a nice distro (on intel at least) that I don't want to
> > leave it.
>
> we need some more info, but i think your problem is trying to use
> yaboot on an oldworld, that won't work.
>
> --
> Ethan Benson
> http://www.alaska.net/~erbenson/
>
/************************************************************************.
# Indraneel Majumdar ¡ E-mail: indr...@123india.com #
# Bioinformatics Unit (EMBNET node), ¡ URL: http://scorpius.iwarp.com #
# Centre for DNA Fingerprinting and Diagnostics, #
# Hyderabad, India - 500076 #
`************************************************************************/
Ethan Benson
>
> I thought any space after the first 128MB is left unused. Is this
> incorrect? (previously swap partition _had_ to be less than 128MB to work
> but that I guess was rectified).
yes that is an anchient long gone limitation of 2.0 kernels, 2.2 has
never had this problem.
your swap partition can now be up to 2GB on 32bit platforms and
alot bigger on 64bit platforms
> I did. mac-fdisk is working fine, it was always working fine. I have
> partitions like this now (in a bid to make easy test cycles):
> Apple Partition map
> / 2.1GB
> It still doesn't boot from sda
>
> I'll explain again: I can stick in the boot floppy and install over NFS.
> Everything is fine. I follow the installation menu and come to where it
> wants to make linux directly bootable from hard disk. That happens (it
> runs quik) and then wants to reboot. It reboots, ejects root floppy, and
> shows gray screen of "?". Here is the quik.conf I can see when I boot
> using floppy and mount the sda at /target:
yes you need to fix OF first, you do this by running
nvsetenv boot-device <path>
where <path> is the OpenFirmware path to the disk. the ofpath utility
included with recent ybin distributions has some support for oldworld
macs, i don't think its been tested on an 8550 however.
> partition=2 ## does not work even with partition=1
partition=2 is correct, that is your root partition.
> root=/dev/sda2
> timeout=100
> image=/vmlinuz
> label=linux
> read-only
this looks ok
> I am able to run quik after booting from floppy with -C option. This is
> the output:
>
> Second-stage loader is on /dev/sda2
> Config file is on partition 2
> Writing first-stage QUIK boot block to /dev/sda2
> Making /dev/sda2 bootable (map entry 2)
> Writing block table to boot block on /dev/sda2
looks good.
> This is part of the dmesg output:
[snip]
> --------------------
>
> If this gets solved, we'll put debian on 2 more macs, so I'm really biting
> my nails.
> Thanks,
> Indraneel
i am sure all you need to do is reconfigure OpenFirmware. this is not
done automatically unfortunatly. (though now it could on some
machines using ofpath)
Indraneel Majumdar
Some terrible seems to have happened. I tried this:
nvsetenv boot-device sd:2
it was:
boot-device /AAPL,ROM
earlier
Now on powering up the system I get nothing on the screen, no grey screen,
and it doesn't boot from floppy or Mac CD either. What do I do? Have I
changed some setting in the BIOS? Is there any motherboard jumper setting
to get back to original state?
I have no idea about OpenFirmware (I'm running a Mac for the first time
in my life). On x86 I hit del or F2, is there something like that on the
Mac? Also there is no ofboot program with ybin. There is a mkofboot but
the docs said it was for NewWorld Macs.
Please help, waiting anxiously,
Indraneel
On Thu, 5 Oct 2000, Ethan Benson wrote:
> yes you need to fix OF first, you do this by running
>
> nvsetenv boot-device <path>
>
> where <path> is the OpenFirmware path to the disk. the ofpath utility
> included with recent ybin distributions has some support for oldworld
> macs, i don't think its been tested on an 8550 however.
>
> i am sure all you need to do is reconfigure OpenFirmware. this is not
> done automatically unfortunatly. (though now it could on some
> machines using ofpath)
>
> --
> Ethan Benson
> http://www.alaska.net/~erbenson/
>
/************************************************************************.
Ethan Benson
> Hi,
>
> Some terrible seems to have happened. I tried this:
>
> nvsetenv boot-device sd:2
yeah that is not correct, only Newworlds have nice aliases like that
(and only for ATA)
the 7200 uses scsi/@sd:2:0
i am not entire sure what the 8550 is, like i said, try ofpath it may
already support that machine.
otherwise you have to look around /proc/device-tree/aliases/ and whatnot.
> it was:
> boot-device /AAPL,ROM
> earlier
>
> Now on powering up the system I get nothing on the screen, no grey screen,
> and it doesn't boot from floppy or Mac CD either. What do I do? Have I
> changed some setting in the BIOS? Is there any motherboard jumper setting
> to get back to original state?
hold down
command option p r
while COLD booting the machine
> I have no idea about OpenFirmware (I'm running a Mac for the first time
> in my life). On x86 I hit del or F2, is there something like that on the
> Mac? Also there is no ofboot program with ybin. There is a mkofboot but
> the docs said it was for NewWorld Macs.
ofpath not ofboot. all of ybin is newworld only except the ofpath
utility. if your looking at the ybin debian package you would have to
get the newwer debs out of proposed-updates, or the tarball on my web
page, the only part you need to extract is the ofpath utility
you can enter the OpenFirmware console but on those machines you
usually have to connect a serial terminal to do so, some of them have
a video driver and some don't in any event you at least have to change
the input and output devices to the keyboard and monitor.
if you want to attempt to enter the OF console without a serial
terminal run the following commands from linux:
nvsetenv input-device keyboard
nvsetenv output-device screen
then boot while holding down
command option o f
Indraneel Majumdar
> i am not entire sure what the 8550 is, like i said, try ofpath it may
> already support that machine.
>
(the kernel is at sda2 in usual potato location with symlink)
this is what ofpath gives when I run ofpath /dev/sda2:
/bandit/gc/mesh/sd@0:2
I did:
nvsetenv boot-device /bandit/gc/mesh/sd@0:2
(I also tried with these:
/bandit/gc/mesh/sd@0
/bandit/gc/mesh/sd@0:2\\vmlinux )
nvsetenv showed that the entries were updated. On rebooting it again
stopped at blank screen. I noticed however that the starting music played
twice (previously it was playing only once)
Do I need to run quik again after all this? I tried with and without
running quik, it didn't work. Also I am running ofpath directly after
booting from floppy. But I am running nvsetenv after doing chroot /target
> hold down
>
> command option p r
>
> while COLD booting the machine
Thanks a huge lot (wiping my forehead). It worked, that's how I could do
the above !
> utility. if your looking at the ybin debian package you would have to
> get the newwer debs out of proposed-updates, or the tarball on my web
> page, the only part you need to extract is the ofpath utility
that's what I ran
> --
> Ethan Benson
> http://www.alaska.net/~erbenson/
>
What do I have to put in the nvsetenv line? All the bandit stuff or scsi?
Will I have to put the kernel image location?
Thanks for your continued help (blood flows back into veins)
Indraneel
Ethan Benson
> On Thu, 5 Oct 2000, Ethan Benson wrote:
>
> > i am not entire sure what the 8550 is, like i said, try ofpath it may
> > already support that machine.
> >
>
> (the kernel is at sda2 in usual potato location with symlink)
> this is what ofpath gives when I run ofpath /dev/sda2:
> /bandit/gc/mesh/sd@0:2
>
> I did:
>
> nvsetenv boot-device /bandit/gc/mesh/sd@0:2
> (I also tried with these:
> /bandit/gc/mesh/sd@0
> /bandit/gc/mesh/sd@0:2\\vmlinux )
you want to use
/bandit/gc/mesh/sd@0:2
or the more common method:
/bandit/gc/mesh/sd@0:0
the partition 0 trick makes OF load the boot block from the partition
marked bootable, which is your root partition, so it really should not
make any difference
> nvsetenv showed that the entries were updated. On rebooting it again
> stopped at blank screen. I noticed however that the starting music played
> twice (previously it was playing only once)
hmm... not sure why it would reboot itself..
> Do I need to run quik again after all this? I tried with and without
> running quik, it didn't work. Also I am running ofpath directly after
> booting from floppy. But I am running nvsetenv after doing chroot /target
that should be ok... it never hurts to rerun quik if you change things..
>
> What do I have to put in the nvsetenv line? All the bandit stuff or scsi?
> Will I have to put the kernel image location?
nvsetenv boot-device '/bandit/gc/mesh/sd@0:0'
be sure to quote it, the shell sometimes does not care for @ in the
command line...
one other thing you should try if you have not already is:
nvsetenv input-device keyboard
nvsetenv output-device screen
if you still don't see anything but a black screen then you need a
serial terminal to see OF, (you have to reset those back to normal for
that to work again) if you have any other machine around and can
connect the serial ports together and use a terminal emulater you can
access OF and see better what is happening.
one other thing, you will probably need to use at least the final
2.2.17 kernel (from ftp.kernel.org) the debian kernels are older and
may not work.
also, make sure in your quik.conf that your image= line points to a
real kernel and not a symlink, for some reason quik does not work
reliably with symlinks.
Ethan Benson
> also, make sure in your quik.conf that your image= line points to a
> real kernel and not a symlink, for some reason quik does not work
> reliably with symlinks.
looking back at your posted quik.conf that is exactly what its doing,
try this instead, it assumes you have a vmlinux-2.2.17 in /boot:
timeout=20
partition=2
image=/boot/vmlinux-2.2.17
label=linux
root=/dev/sda2
read-only
Michael Schmitz
> > or are you under the impression that the linux kernel still has a
> > limit of 128MB on swap partitions?
>
> I thought any space after the first 128MB is left unused. Is this
> incorrect? (previously swap partition _had_ to be less than 128MB to work
> but that I guess was rectified).
The 128 NB limit is old news. Since before 2.2.6 (I think) the limit has
been increased.
Michael
Michael Schmitz
> Mouse is not working. My mouse fits into the keyboard and has 4 pins.
That would be an ADB mouse. Additional mouse buttons can be emulated by
keys using the adb_buttons=1,x,y kernel option (x and y being the keycodes
for the emulation keys).
> XF86Config has entries BusMouse and /dev/adbmouse . X reports that it is
Up to BenH's 2.2.17-pre series, /dev/adbmouse was used for ADB mice, with
the protocol set to BusMouse. Recently, mouse data have been switched to
/dev/input/mice with IMPS/2 procotol, see the description on BenH's web
page on how to set up devices and mouse button there.
Indraneel Majumdar
I'm terribly sorry for breaking off. I had to relocate my machines around
the lab due to emergencies. I'm online again.
On Fri, 6 Oct 2000, Ethan Benson wrote:
> you want to use
>
> /bandit/gc/mesh/sd@0:2
>
did not work
> or the more common method:
>
> /bandit/gc/mesh/sd@0:0
I did this and it worked, only once. Over enthused, I tried making a swap
partition and retried the process and it's not working anymore, even with
1 partition. I'm retrying it again, though.
>
> also, make sure in your quik.conf that your image= line points to a
> real kernel and not a symlink, for some reason quik does not work
> reliably with symlinks.
>
Yeah, I am running
quik -v -f -C /etc/quik.conf
after changing the image line in quik.conf
Hope it works this time.
Thanks a huge lot,
Indraneel
> --
> Ethan Benson
> http://www.alaska.net/~erbenson/
>
/************************************************************************.
# Indraneel Majumdar ¡ E-mail: indr...@123india.com #
# Bioinformatics Unit (EMBNET node), ¡ URL: http://scorpius.iwarp.com #
# Centre for DNA Fingerprinting and Diagnostics, #
# Hyderabad, India - 500076 #
`************************************************************************/
Indraneel Majumdar
A huge lot of thanks to you and all those who helped me out of this.
Everything is working fine now so you might as well add Workgroup
Server 8550/200 to the Debian Potato success list.
I have been able to make a swap and var partition and machine is rebooting
fine (an unhealthy way to test a machine, really). After installation and
booting from hard disk step (to get a premade quik.conf) I followed
Ethan's words to the core. I got the 'ofpath' script and ran it:
./ofpath /dev/sda
then i did
chroot /target
nvsetenv boot-device /bandit/gc/mesh/sd@0:0
then I ran quik (not working without this step):
quik -v -f -C /etc/quik.conf
with image pointing to actual kernel.
then exit and reboot
At startup first time I get the starting music twice, thereafter only
once. It takes a little while to start up after the music (about 5 to 10
sec) (that's how I learnt to be patient to achieve a good thing) and
eventually darkness disappears and the penguin shows the light.
It's working great and right now I'm struggling with X configuration.
Mouse is not working. My mouse fits into the keyboard and has 4 pins.
XF86Config has entries BusMouse and /dev/adbmouse . X reports that it is
providing value of 3 button mouse. below the single button mouse is
written "Apple Desktop Bus Mouse II, family No M2706". XF86Setup or
xf86config do not seem to be on my system (Probably I have to build the
second CD iso image). i'm thinking of giving 'alien' a try (last time I
used it I had a nightmare, but this is a fresh system ;-) i'll wake up
early tomorrow (after a few hours) and give the next Mac a try. That one's
a 8600 which should also work.
I cannot thank you enough for your help. I'm not a seasoned Debian user
but I'm trying to migrate from RedHat/SuSE to Debian/GNU/Slackware and
this is the first time I'm on a Debian list. Thank you very much for your
support. i think I'm beginning to understand what makes Debian the best.
Thanking you,
indraneel
On Fri, 6 Oct 2000, Ethan Benson wrote:
> you want to use
>
> /bandit/gc/mesh/sd@0:2
>
> or the more common method:
>
> /bandit/gc/mesh/sd@0:0
>
> the partition 0 trick makes OF load the boot block from the partition
> marked bootable, which is your root partition, so it really should not
> make any difference
>
> one other thing, you will probably need to use at least the final
> 2.2.17 kernel (from ftp.kernel.org) the debian kernels are older and
> may not work.
>
> also, make sure in your quik.conf that your image= line points to a
> real kernel and not a symlink, for some reason quik does not work
> reliably with symlinks.
>