Matt,
Could we not use fdisk in a non-interactive means? We already should
know which harddrive it's on (ie - /dev/hda or /dev/sda) and then run the
command 'fdisk -l $rootdev' and examine the results for a partition type '41'...
Running fdisk in this fashion is equivilent to hitting 'p' to
On Fri, Jan 21, 2000 at 03:11:36PM -0500, Jeremy T. Bouse wrote:
> Yeah... I found inside the Documentation/powerpc/zImage_layout.txt
> some directions from Cort Dougan who says that in the PReP build you merely
> 'dd' the zImage to the Type 41 boot partition... This was done by the PReP
> bo
> Its just a bug in the boot-floppies more then anything. There are some
> steps you can follow to make the install happen. They require that you
> either have a realnetwork(tm) or somefreetime(tm) or a linuxppc cd.
>
> I sent someone some directions on how to do this / to get potato working,
> > usb is not available on every powerpc machine. We fixed console-data
> > yesterday, lets hope this will doit what we want for potato.
>
> Could you please post the definitive fix? I tried the fix posted yesterday,
> and
> it still gave me errorsor are you just going to update the consol
On Fri, Jan 21, 2000 at 10:47:35PM +0100, Hartmut Koptein wrote:
> > i am trying to run debian on a g3 notebook and i did as follows:
> >
> > 1. downloaded kernel, drivers, base2_2.tgz, bootx, etc...
> > 2. booting does not work, doenloaded g3 linux from linuxppc.org
> > 3. rename root.bin to
> i am trying to run debian on a g3 notebook and i did as follows:
>
> 1. downloaded kernel, drivers, base2_2.tgz, bootx, etc...
> 2. booting does not work, doenloaded g3 linux from linuxppc.org
> 3. rename root.bin to ramdisk.image.gz
> 4. booting now does work, it even loads the ramdisk
>
hi,
i am trying to run debian on a g3 notebook and i did as follows:
1. downloaded kernel, drivers, base2_2.tgz, bootx, etc...
2. booting does not work, doenloaded g3 linux from linuxppc.org
3. rename root.bin to ramdisk.image.gz
4. booting now does work, it even loads the ramdisk
5. dibo
> Can anyone think of why PowerPC's boot disks for potato should still
> be in sid? I would think if PPC was gonna try and make it in the potato
> release it should be in potato not sid... Or am I missing somethin from the
> big picture?
We move powerpc from sid to potato at the end of the
Can anyone think of why PowerPC's boot disks for potato should still
be in sid? I would think if PPC was gonna try and make it in the potato
release it should be in potato not sid... Or am I missing somethin from the
big picture?
Respectfully,
Jeremy T. Bouse
Under
Yeah... I found inside the Documentation/powerpc/zImage_layout.txt
some directions from Cort Dougan who says that in the PReP build you merely
'dd' the zImage to the Type 41 boot partition... This was done by the PReP
boot disk set I used to install... But it seems none of the kernel-image
> Apologies since I haven't yet file a bug report or fixed the kernel-image
> packages installer to not attempt to use quik on PReP systems. I'm trying
> but am low on time and swimming in email. :-/
>
> Anybody care to fix this?
sure :-) i'm working on 2.2.14 now, not very easy to create an c
On Fri, Jan 21, 2000, Kevin Puetz <[EMAIL PROTECTED]> wrote:
>Yes, it does show up in /proc/pci. It also has /dev nodes (that I created by
>hand). But it's not going to show up in the /proc/device-tree, as OF knows
>nothing about it.
>
/proc/device-tree should, with a few rare exceptions, show
[EMAIL PROTECTED] said:
> This would be a poor test - I have a 3rd party USB card in my beige
> G3, and it
> works fine. However, my OF doesn't know about it, and there are no
> such
> devices.
> That's right, does this card show up on /proc/pci ? My builtin USB
> shows up ...
Yes, it does sh
Hi,
> That's right, does this card show up on /proc/pci ? My builtin USB shows
> up ...
>
> > So at least leave a way to bypass whatever suggestion is going to be made
> > because of this test.
>
> Seems Hartmut found another way, no reason to worry.
Sorry, not for usb; the architecture/subar
Hartmut Koptein wrote:
> usb is not available on every powerpc machine. We fixed console-data
> yesterday, lets hope this will doit what we want for potato.
Could you please post the definitive fix? I tried the fix posted yesterday, and
it still gave me errorsor are you just going to update
> [EMAIL PROTECTED] said:
> > The absence of the USB option would be indicated by the absence of the
> > usb-* entries in /proc/device-tree/aliases (the fact that there just
> > isn't any USB hardware actually connected at boot time results in
> > empty files there).
>
> This would be a poor tes
[EMAIL PROTECTED] said:
> The absence of the USB option would be indicated by the absence of the
> usb-* entries in /proc/device-tree/aliases (the fact that there just
> isn't any USB hardware actually connected at boot time results in
> empty files there).
This would be a poor test - I have a
> Anyway :
>
> pb1 : the Blizzard powerup scsi detection is not working for me, thus no
> access to the scsi disks. Will have to fix the kernel-image used.
>
What do you mean? What kernel and what bootstrap are you currently using?
I think the new bootstrap and an unmodified kernel would be able
On Fri, Jan 21, 2000 at 07:41:43AM -0500, Jeremy T. Bouse wrote:
> der.hans was said to been seen saying:
> > How're you installing the new kernel? Do you have a partition of type 41
> > at the beginning of the disk onto which you dd the kernel?
> >
> Yes... the system has 3 partitions on a
der.hans was said to been seen saying:
> How're you installing the new kernel? Do you have a partition of type 41
> at the beginning of the disk onto which you dd the kernel?
>
Yes... the system has 3 partitions on a SCSI harddrive... sda1 is
the ext2 / partitions, sda2 is the Type 41 PPC
> > More info in /proc/device-tree/aliases (see adb-mouse, adb-keyboard,
> > usb-mouse, usb-keyboard; empty files mean device not present).
> > Hartmut: which of these would break on PPC models other than Powermacs?
>
> usb is not available on every powerpc machine. We fixed console-data
> yest
> /proc/hardware has a lot more information in it than /proc/pci, on
> my powerpc/apus system. but all info from /proc/cpuinfo seems to be
> included into /proc/hardware.
Same on m68k. The function for /proc/hardware in the kernel calls the
one for /proc/cpuinfo.
Roman
On Fri, Jan 21, 2000 at 11:51:13AM +, Sergio Brandano wrote:
>
> >sure, that is the problem. Because of the i386 package all binary all -6
> >packages got erased, making enlightenment uninstallable on powerpc.
>
> Great. This enforces my original messages:
>
> > As this happened before for
>sure, that is the problem. Because of the i386 package all binary all -6
>packages got erased, making enlightenment uninstallable on powerpc.
Great. This enforces my original messages:
> As this happened before for other packages, I would say that, in
> principle, it is not a good thing to del
On Fri, Jan 21, 2000 at 11:39:15AM +, Sergio Brandano wrote:
>
> > So it was built by the build daemon since your last mail.
>
> Nope. The i386 version was available several days ago.
sure, that is the problem. Because of the i386 package all binary all -6
packages got erased, making enligh
> So it was built by the build daemon since your last mail.
Nope. The i386 version was available several days ago.
> How so ?
It compiles, but there are problems when using it. On the other hand,
if you had no problems, why not making it available as a bin package?
Sergio
On Thu, Jan 20, 2000 at 11:01:25AM -0500, [EMAIL PROTECTED] wrote:
> Hi. I'm in the process of trying yet another installation attempt
> of debian-ppc on a Starmax 5000.
>
> I didn't go through the entire installation process, because the
> kernel and module files hadn't downloaded right, but I go
On Fri, Jan 21, 2000 at 11:16:56AM +, Sergio Brandano wrote:
>
> >What happens here is that the themes and data are architecture all,
> >so are the one built for i386, who has enlightenment 0.16.3-6.
>
> ... enlightenment 0.16.3-7 (I am running it, and no compilation was
> required).
So it
Hello, ...
after another build of the debian/powerpc/apus boot floppies (from modified
2.2.4). I noticed the following problems. Some of them might actually be
solved already since then.
Anyway :
pb1 : the Blizzard powerup scsi detection is not working for me, thus no
access to the scsi disks. W
>What happens here is that the themes and data are architecture all,
>so are the one built for i386, who has enlightenment 0.16.3-6.
... enlightenment 0.16.3-7 (I am running it, and no compilation was
required).
> Just get the source package and recompile it. (apt-get source should
> do the wo
On Fri, Jan 21, 2000 at 09:47:50AM +0100, Michael Schmitz wrote:
> > > Configuring packages ...
> > > Please report this bug: no keymaps described for architecture m68k/
> > amiga 2000
> >
> > This is a known problem. Fixing it as well.
> >
> > So now it seems that /proc/hardware on ppc
On Fri, Jan 21, 2000 at 08:42:32AM +, Sergio Brandano wrote:
>
> Hey Laurence!
>
> Could you *please* fix the dependencies with this package?
>
> > enlightenment depends on enlightenment-data (= 0.16.3-6)
> >
> > enlightenment depends on enlightenment-data (= 0.16.3-6)
> > enlightenment su
> No machine: line here. I suggest the PowerPC port add /proc/hardware to
> the kernel (the machine: stuff isn't strictly info about the CPU). Or read
> /proc/device-tree/model for the model ID (on PowerMac models at least).
> More info in /proc/device-tree/aliases (see adb-mouse, adb-keyboard,
> u
> > Configuring packages ...
> > Please report this bug: no keymaps described for architecture m68k/ amiga
> 2000
>
> This is a known problem. Fixing it as well.
>
> So now it seems that /proc/hardware on ppc is not useful. Is there
> also a "machine" field on m68k ? That would be nic
Hey Laurence!
Could you *please* fix the dependencies with this package?
> enlightenment depends on enlightenment-data (= 0.16.3-6)
>
> enlightenment depends on enlightenment-data (= 0.16.3-6)
> enlightenment suggests epplets
out of the actual distribution:
>enlightenment-data_0.16.3-7.deb
On Thu, 20 Jan 2000, Jeremy T. Bouse wrote:
> Okay... I've work'd with Intel and Alpha machines for quite some time now
> and have no problem installing a new kernel on them... However this PowerPC
> is kickin my butt and laughin at me all the while when I try to install a
> new kernel... I'm not
Okay... I've work'd with Intel and Alpha machines for quite some time now
and have no problem installing a new kernel on them... However this PowerPC
is kickin my butt and laughin at me all the while when I try to install a
new kernel... I'm not even tryin to be fancy and compile my own kernel, I'm
37 matches
Mail list logo
