Why not put it into the powerpc-utils package then? As far as I
Because Michael Schmitz thinks it is a bad idea, and doesn't really believe in
group maintenance ?
Sven, I've largely kept silent at your innuendo, but I think it's time to
speak plainly again.
This is nothing about me
$ more /proc/fb
0 ATI Radeon Lf
0 OFfb ATY,264LTP
1 OFfb ATY,264LTP
Might be the LCD is actually on the second one?
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
netbooting is the correct way on those, and the only tested way.
And the CDs are supposed to boot on the RS6000?
They should, but there seems to be some issue that need investigating. I fixed
something (missing icon) recently, so the daily builds and beta2 should be
better than sarge.
Solution is to fix partman-prep, and see if yaboot-installer behaves
then, or
to see if the excessive ramdisk size created by initramfs-tools caused the
compressed kernel + builtin initrd to cause trouble with the OFs
installer.
My bet would be on the latter. That should be
That would be interesting, since the B50 is exactly what those corean guys
have all this trouble dealing with.
Odd. We installed from a floppy using the woody netinstall CDs by just
following the instructions found at
http://www.kutilek.de/technik/debian-rs6k.en.php
You reqlise
On Mon, Mar 27, 2006 at 03:20:41PM +0200, Michael Schmitz wrote:
Well, nice to hear it's not the hardware that's holding things up. Now we
just need to find someone to volunteer to take over from you. Anyone?
FWIW (I forget if the relevant thread was CCed here), I've volunteered
FWIW, I've got a bunch of old Macs here (including Nubus), and one RS/6000
B50 that can be used for testing CD booting if necessary.
That would be interesting, since the B50 is exactly what those corean guys
have all this trouble dealing with.
Odd. We installed from a floppy using the
On Mon, Mar 27, 2006 at 02:20:11AM +0200, Frans Pop wrote:
There is no problem with initramfs-tools, just a problem with the
maintainer of the ppc port who is too quick to jump to conclusions again.
Since the debian-installer team clearly stated that debian would be better off
without me,
If the d-i team does not get their act together WRT daily builds, I can
offer to set up a 233 MHz G3 with accounts for d-i. Ditto for someone to
build kernels.
The real problem is not the machine, they can even use an account on the IBM
donated quad-power5 at augsbourg if needed. The real
Parted converts flags to funky partition type names, i think. Not idea,
but it
works, like said, i think parted is inherently broken on this, but there
is
not much we can do at this time.
They might have done this following a comment of mine (my memory id fuzzy
on this, not
Why? Because we don't know how MockOS will react to a partition _type_ set
I don't know any MockOS, please provide real examples.
s/MockOS/MacOS/g
to anything but Apple_Bootstrap, Apple_HFS, Apple_UNIX_SVR2 or Apple_Free.
If you're sure (or just reasonably confident) Linux_LVM will be
Ok. The main problem is that there is no LVM flag for mac partition tables, i
There is no such thing as flags for most things in Mac partition tables
(I'm sure there are some unused bits somewhere in the partition data but
that's all undocumented and Apple could come and change the meaning of
There is no such thing as flags for most things in Mac partition tables
Parted converts flags to funky partition type names, i think. Not idea, but it
works, like said, i think parted is inherently broken on this, but there is
not much we can do at this time.
They might have done this
Hi,
I have been browsing the following URL:
http://people.debian.org/~schmitz/3.0.24-2003-01-07/chrp/
Do you know who has been upgrading boot-floppies for powerpc, chrp in
particular?
The boot-floppies build on that machine was done by me, in order to help
out the boot-floppies team while
I think this bug should be dealt on boot-floppies side.
Shouldn't it ?
Eduard Bloch told me it's a debootstrap issue (there's no need for eject
in the initial installer, just in the basedebs since CD changing only
happens during second stage install).
Pass the blame, please...
Packed pixel format is in use for lots of other hardware so I'd assume it
is supported in some way?
Nope, I don't think bogl supports packed pixels at all. Christian and I
discussed this before if I remember right.
I don't remember, but you may be right ;-)
But what do we do
Packed pixel format is in use for lots of other hardware so I'd assume it
is supported in some way?
Nope, I don't think bogl supports packed pixels at all. Christian and I
discussed this before if I remember right.
Jeez, how dumb am I? I was thinking of planar pixels.
Jeez, how dumb am I? I was thinking of planar pixels. Packed pixels
should indeed be fine.
And planar was the problem on the Falcon anyway. Why one bit packed pixels
won't work on the TT is another question, but that machine has inverse
video as default (as has the SE/30).
Ah
I tried the newest version of the bf on ftp.debian.org on a Macintosh
SE/30. After the line about starting busybox, it went into an infinite
loop displaying bogl: don't know screen screen type 0.
Known issue; please report this to [EMAIL PROTECTED] I suspect it hits
machines with
Macintosh SE/30 32meg RAM
BF 3.0.22 from macinstall.tar.gz off of ftp.debian.org
tried both kernel from archive and mac sourceforge site
boot parameters: root=/dev/ram
Mitchell
can you use a non-monochrome video mode on your mac?
Not on the SE/30 - that's one of the 'fishtank'
On Tue, 12 Mar 2002, Debian Bug Tracking System wrote:
Processing commands for [EMAIL PROTECTED]:
reassign 137575 mac-fdisk
Bug#137575: boot-floppies: [powerpc] mac-fdisk hangs
Bug reassigned from package `boot-floppies' to `mac-fdisk'.
Thanks, I'll see what I can do about that. From all
Hi,
it seems the current m68k basedebs.tgz (as found at)
http://ftp.uni-erlangen.de/pub/mirrors/debian/dists/testing/main/disks-m68k/base-images-current/
is a plain tar archive, uncompressed. (Previously, it was gzip compressed,
at least the copy I have from around April last year).
The
I did it, but didn' work. It can'f find the device.
Well, certainly, you do not have a scsi disk that mac-fdisk can
find. Is it by chance a pc-formatted scsi? mac-fdisk would try to read
the partition table at the beginning of the disk, which is an Apple
format.
Did we get any information
are we sure we need /sbin/macfdisk on the _PReP_ root image? removing it
allows the root disk to build (and even leaves 10 kB free!).
You should not need mac-fdisk there.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
What package version did you use from woody?
Latest from unstable at the time the pkg was built. Probalby whatever
is still latest from unstable, it doesn't change often.
The latest version (-8) is from Dec. 7. I'd better install that from the
archive instead of using the one from my
So how do the ramdisks get built these days? Just copy the binaries over?
Well, they get stripped first, see scripts/rootdisk/strip-executables.sh.
I thought the binaries were stripped before but a look at the makefile
cured me of that :-)
The kind of ELF damage that we're seeing here
Hmmm.. looks like ash tries to execute mac-fdisk as a shell script?
Apparently the mac-fdisk binary is corrupted somehow. There's already a bug
open on this: I don't know if those builds of boot-floppies were just bad
for some reason, or the binary in the archive is actually broken,
Maybe the library reduction went astray? Not that mac-fdisk uses a lot of
weird libraries. Can you send me that binary for closer inspection?
It's all in
dists/woody/main/disks-powerpc/3.0.18-2001-12-21/powermac/ramdisk.image.gz
Bite me :-) At least you did provide part of an URL. I'll
It seems like some sort of bad build on my part. The package in woody
I don't think has changed since the previous build. Hmm.
What package version did you use from woody? ldd on your binary gives 'not
a dynamic executable'. objdump needs the -m flag to do anything with the
file (so the ELF
The problem is that even if DevFS is enabled, but not mounted,
/proc/partitions is in DevFS format, and libfdisk doesn't like it.
Good spotting - devfs was the only thing I could imagine to blame here :-)
See the function get_part_info in
boot-floppies/utitlities/libfdisk/fdisk.c.
I have
tags 122738 moreinfo
thanks
Have you verified that this still happens with the release kernel? It doesn't
merit being an RC bug if only 2.4 produces the problem.
With the current release kernel, the IDE disk is detected fine. I hadn't
tested with that machine for a long time so I did
Package: boot-floppies
Version: 3.0.17-2001-11-21
Severity: serious
boot-floppies 3.0.17 fails to find the builtin IDE drive on Atari
Falcon030 (kernel 2.4.15-m68k, that's straight from the m68k CVS kernel
repository). fdisk -l in the shell shows the partition table no problem.
I'll have to
Package: boot-floppies
Version: 3.0.17
Severity: important
Sorry but it's still happening (cf. #114603)- the only way around was a
restart of the install from scratch (including mke2fs). Architecture is
i386 for a change, BTW. Most probably caused by giving a bogus archive
URL for network
Well I guess I jumped the gun, the m68k install didn't quite finish. It
downloaded all the packages for base, unpacked them all, then stopped during
'Install essential packages'. I tried it twice and it stops in the same
place. no error messages, terminal 2 also freezes up. You can type a
I am currently uploading a new bf build from CVS to my auric page:
http://auric.debian.org/~cts/bf/
Once you see the [amiga|atari|mac]install.tar.gz files in 3.0.8-2001-07-15/
you can start downloading from there (in less than 1h I hope).
This is supposed to work with basedbs.tgz, which
On Fri, Jul 06, 2001 at 03:02:04PM -0500, Christian T. Steigies wrote:
I am uploading the latest m68k boot-floppies build to:
http://auric.debian.org/~cts/bf/
what a pitty that I have to follow up myself... trying to install this at
home, I get the following messages:
installing
partitions, except in sparc land, and mac-fdisk probably won't let
you anyway, so what's the dileo? If it was just a little bit more
annoying I'd go change it myself. Time for a nap instead, I think.
There are aliases that you can use for the begining number and length.
The problem
syslinux actually. and it can take a root= argument but if you don't
give a root= argument you get a root disk prompt.
Yeah, that's what I said/meant. The boot-floppy-hfs.img floppy
doesn't work the same way as the rescue floppy does for other
architectures. My point is that for
Ethan, your mac-fdisk document should really be added to the Debian/PPC install
doc. Invaluable.
Good idea - want to add that to CVS, Ethan?
I'm currently reworking the mac-fdisk man page (which should be in the
install section) to cover the 'reorder to place bootstrap partition before
I'm currently reworking the mac-fdisk man page (which should be in the
install section) to cover the 'reorder to place bootstrap partition before
ah cool, i did notice that the broken man page link seems to have been
fixed since last time i looked. i still think my doc would be useful
40 matches
Mail list logo
