Re: Debian PowerPc installer initramfs-tools generates malformed yaboot.conf created when alternate partitions use UUID= in fstab
On Die, 2010-07-13 at 21:54 -0300, Rogério Brito wrote: On 06/28/2010 02:42 PM, Rogério Brito wrote: We could, perhaps, offer two boot loaders for NewWorld ppc machines in Debian and phase out yaboot once we know that GRUB2 works fine. (That still leaves those users of miboot and quik without good alternatives). My primary powerpc machine (an iBook G3) is halting in some ways that I have not yet figured out, which I suppose are related to heat. That being said, I would like to go on and take some care of powerpc (as I have some embedded machines that use it). In particular, I would like to upload a new version of yaboot, to be a little more in sync with upstream. Two questions, therefore: 1 - is there any problem with that? 2 - would there be anybody to sponsor a possible upload to unstable? I guess I could do that, if nobody more active than me volunteers. Also, it would be very nice if we had reports from people that tried to use GRUB2 on powerpc. There should be several reports of mine in the debian-powerpc list archives. In summary, it's been working on my PowerBook for at least a year or so, but I'm not sure it's ready in general as a replacement for yaboot yet. But at least offering it as an alternative for advanced users might be good anyway. P.S. AFAICT the current yaboot maintainer is 'Debootloaders Yaboot Maintainers Team debootloaders-yab...@lists.alioth.debian.org', which I can't seem to find in the list of recipients. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1279104844.515.43.ca...@thor.local
Re: Has anybody recently done a Debian install on a playstation-3?
On Tue, 2010-02-16 at 11:27 -0800, Geoff Levand wrote: Hi, On 02/15/2010 09:13 PM, Rick Thomas wrote: Norberto is having trouble getting Debian to install on his PS3. It's a bit out of my usual line, so any advice from somebody who has done it will be much appreciated! I just tested the current daily-build (08-Feb-2010 00:09) from here: http://d-i.debian.org/daily-images/powerpc/daily/powerpc64/netboot/ The installer fails on network config. If I run 'dhclient eth0' from a console I can see the request at the dhcp server, and dhclient reports the correct address, but networking does not function properly. If I run 'netcfg' from a console I get: netcfg: undefined symbol: _savegpr_19 I think this symbol is used by gcc when compiling with -Os. Maybe libgcc or something is getting stripped down too much for netcfg / the installer environment in general. -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1266397544.19618.3612.ca...@thor.local
Re: Is Debian on PowerPC dead? [Re: Bug still present [Re: Bug#562575: installation-reports: Buisnesscard PowerPC installer loops with Segmentation faults]]
On Thu, 2010-01-14 at 16:23 -0500, Rick Thomas wrote: This bug is still present in the Thu Jan 14 16:08:46 UTC 2010 businesscard CD downloaded from http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/arch-latest/powerpc/iso-cd/ So far as I can tell, this bug has not been looked at by the debian- installer folks. Is PowerPC simply so unimportant that resources cannot be spared to even *look* at a problem that renders the installer unusable on that hardware? It means there hasn't been a volunteer so far. Are you volunteering? -- Earthling Michel Dänzer |http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: grub2 on powerpc
On Fri, 2006-09-08 at 08:17 +0200, Robert Millan wrote:
- Checkout d-i source.
- Apply my patch and build grub-installer udeb.
- Put the udeb in installer/build/localudebs, and add it to the cd with:
echo grub-installer installer/build/pkg-lists/local
- Build a netboot image as normal.
Did that, but I also had to build dmidecode-udeb with powerpc added to
its debian/control arch list. It might make more sense to drop the
grub-installer dependency on dmidecode-udeb on powerpc instead.
- Boot the resulting image in expert mode, and when queried about using grub2
answer Yes.
- Check wether it boots (and have a rescue disk at hand!)
I couldn't get past the prompt for where to install grub2. I tried (hd0)
as well as (hd0,1) ('NewWorld bootblock' on hda2) but got an error for
both. Then I found http://grub.enbug.org/TestingOnPowerPC and decided
it's too much hassle for me right now. In case someone else wants to
give it a spin though:
http://people.debian.org/~daenzer/debian-installer-netboot-powerpc-grub2.iso
--
Earthling Michel Dänzer | http://tungstengraphics.com
Libre software enthusiast | Debian, X and DRI developer
Bug#367149: kbd-chooser: [powerpc] does not detect ADB keyboards
On Mon, 2006-05-15 at 07:27 +0200, Frans Pop wrote: The current daily images now show the AT keymap list. I've tested this on Frank Lichtenheld's Powerbook G4 laptop, and all keys are mapped OK for the German keyboard. The only change from the USB-MAC keymaps is that the apple key no longer works as the modifier key. Instead these can be accessed using Fn-Alt, which can probably be explained as that is probably equivalent to the right-Alt key on regular AT keyboards on i386. AFAICT the options are: - should the AT keymaps be made to support the apple key as modifier key or - should we go back to using the USB-MAC keymaps for powerpc This may still be necessary, as some Apple keyboards tend to have different layouts from 'standard' PC keyboards. Just as one example, the Swiss German Apple keyboard has the @ symbol on the G key. AFAIK in some other countries the layout can be completely different. - should powerpc users learn to use Fn-Alt instead of the apple key Not sure if the fact that newer Apple laptops treat the fn key differently matters for this, but at any rate the whole fn concept seems to be rather unintuitive and/or inconvenient for people, at least initially. Going back to USB-MAC keymaps is possibly not the prefered option because as I understand it the input layer of the 2.6 kernel translates everything to AT, so in principle all architectures should now use AT keymaps. I'm not very familiar with all the issues involved, but I suspect you may be mixing up keycodes (and/or keysyms?) and keymaps here. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Re: missing amigamouse device (?)
On Son, 2002-11-03 at 00:39, Andreas Wüst wrote: I couldn't find any mouse device for a normal Amiga mouse connected to the mouseport. I luckily had some advice from earlier days to create it as follows: # cd /dev/input Do you really mean this or just /dev? # mknod amigamouse c 10 4 Or either of MAKEDEV misc MAKEDEV m68k-mice -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian 3.0 Woody Boot-Floppies Installation
[ CC: to debian-boot, where this belongs IMO ]
I'm not sure if the boot-floppies will ever be updated again, but thanks
for the patches anyway.
On Tue, 2002-08-13 at 18:17, Giorgio Terzi wrote:
i have just finished to install on my Amiga (APUS) the last Debian
Woody release from scratch. I have used the Boot-Floppies software
from CVS Repository.
I have used an AMIGA hard-disk partition to begin the installation
and loading the base system. I have used an ADSL connection (PPPOE)
to download the remaining packages.
I wish to submit a few (three) small patches that i have added.
I attach the patch file which I use to patch the sources from CVS.
1) The first merely changes the kernel version number that APUS
uses, the Debian package is available.
2) The second adds three lines to the file powerpc.rules:
these are needed because without the APUSKVER variable is
not used and the kernel file and the modules when installed
are named with the KVER variable.
3) The last is in dbootstrap/choose_medium.c file:
Without being able to read ms-dos formatted Rescue image-file
is impossible to extract install the kernel, the symbol map
and the config file. By the way i have added also the capability
to read Amiga formatted diskettes (I have made some small batches
to create Amiga rescue disks from the disk images created by
Boot-Floppies.
2 installing notes:
When i have tried to mount the /boot partition dbootstrap has
refused to mount it. It shutted down itself restarting the installation
from the beginning. I have mounted /boot by hand using the second
virtual terminal. For the other partitions there was no problem.
I was not able to find a dbootstrap menu voice to start a ppp
configuration but pppoe pppoeconf was installed in the base system
so i was able to configure start a internet connection using the
2nd virtual terminal.
Could be possible in future to have a ppp menu configuration from
dbootstrap?
Thank you for your attention,
Giorgio Terzi
diff -ruN boot-floppies/config boot-floppies_new/config
--- boot-floppies/config Mon Aug 5 14:49:03 2002
+++ boot-floppies_new/config Wed Aug 7 09:54:58 2002
@@ -29,7 +29,7 @@
ifeq $(architecture) powerpc
kver := 2.2.20
pcmcia_kver := 2.2.20-pmac
-apuskver := 2.2.10
+apuskver := 2.4.17
# NewWorld powermacs really need a 2.4 kernel
kver_newpmac := 2.4.18
endif
diff -ruN boot-floppies/make/powerpc.rules boot-floppies_new/make/powerpc.rules
--- boot-floppies/make/powerpc.rules Mon Aug 5 12:06:08 2002
+++ boot-floppies_new/make/powerpc.rules Wed Aug 7 09:54:58 2002
@@ -13,6 +13,10 @@
modulesapus.tgz sys_mapapus.gz configapus.gz linuxapus.bin modcontapus:
kernel.sh
$(ROOTCMD) ./kernel.sh $(archive) $(apuskver) apus
+resc1440apus.bin: $(root_for_rescue) rescue.sh $(arch_rescue_deps) linuxapus.bin
+ $(ROOTCMD) ./rescue.sh $(archive) apus $(apuskver) $ \
+ 1440 $(debianversion) $(LINGUA) $(SFONT)
+
# The pmacnew images use a different kernel version than the pmac ones
modulesnewpmac.tgz sys_mapnewpmac.gz confignewpmac.gz linuxnewpmac.bin
modcontnewpmac: kernel.sh
$(ROOTCMD) ./kernel.sh $(archive) $(kver_newpmac) newpmac
$(packages_with_modules)
diff -ruN boot-floppies/utilities/dbootstrap/choose_medium.c
boot-floppies_new/utilities/dbootstrap/choose_medium.c
--- boot-floppies/utilities/dbootstrap/choose_medium.cMon Aug 5 12:06:20
2002
+++ boot-floppies_new/utilities/dbootstrap/choose_medium.cWed Aug 7 09:54:58
2002
@@ -38,7 +38,10 @@
#include dirent.h
/* ED: floppy filesystem type is not the same for all architectures */
-#if #cpu(sparc) || #cpu(powerpc)
+
+#if #cpu(powerpc)
+const char *fs_type_tab[] = { msdos, ext2, affs, NULL };
+#elif #cpu(sparc)
const char *fs_type_tab[] = { ext2, NULL };
#else
const char *fs_type_tab[] = { auto, msdos, vfat, fat, minix, ext2, NULL
};
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: trying to clean up a bit with the questions concerning'Initialize...'
On Mon, 2002-03-18 at 18:55, Andreas Wüst wrote: *Michel Dänzer said:* I've already reported this problem with bf-3.0.19 to both of these lists. On linux-apus-devel I was told this would be a kernel issue, Well, I said it seems to be a kernel issue, seeing as it works with one kernel but not the other. Aieeeh. Now we have a statement against statement. Chris claims it dbootstrap related, Michel kernel related. I'm jumping out of the line of fire now!! You put too much weight on my words. ;) I said it _seems_... I had no additional information to base a judgement on. But thinking about the 2.4.9 vs. 2.4.17 thingy, I am going to belief it could be kernel related after all. But as you say that mke2fs and mount work with 2.4.17, it definitely looks like dbootstrap. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Still unable to 'Initialize a Linux Partition' with bf 3.0.21
On Son, 2002-03-17 at 00:32, Andreas Wüst wrote:
I've already reported this problem with bf-3.0.19 to both of these lists. On
linux-apus-devel I was told this would be a kernel issue,
Well, I said it seems to be a kernel issue, seeing as it works with one
kernel but not the other.
I wonder about this, because the 'Initialize..' part worked perfectly well with an
2.4.9 apus kernel
I've compared the configs of the 2.4.{9,17} APUS kernels, and the only
changes even remotely related to the problem at hand are that ext3 and
the not-yet-working driver for the Cyberstorm SCSI are enabled.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: b-f 3.0.19 on PowerBook G4
On Mon, 2002-03-04 at 06:06, Colin Walters wrote: On Sun, 2002-03-03 at 18:31, Michel Dänzer wrote: I hope I'll find time to test it tomorrow or at least sometime this week. Cool; that would be much appreciated. BTW, I mistyped the original URL; it's actually at http://penguinppc.org/~walters/debian/installer-current/ Thanks, but as Matt says it doesn't work yet... The basic layout was fine, but I couldn't type 'special' symbols like |. I suspect it was the sg map (for a PC keyboard), not mac-usb-de_CH. Ahh. If your keyboard isn't in the US layout, that would explain the difference. My knowledge about console keymaps and such is very close to zero, so I hope someone else can fix this... Well, in general you simply want the mac-usb variant if it exists or the standard PC one otherwise. Maybe that's already done but the inconsistent naming for the Swiss German keymaps (sg vs. mac-usb-de_CH) causes the wrong one to be used there? -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: b-f 3.0.19 on PowerBook G4
On Son, 2002-03-03 at 20:03, Colin Walters wrote: On Sat, 2002-03-02 at 13:30, Michel Dänzer wrote: It claimed yaboot couldn't handle an ext2 /boot, which obviously isn't true. I already reported this to Colin Walters on IRC and I think he's working on this or has even already fixed it. Matt Kraai came up with much better logic for the code; I just need to find a way to test it now. Michel, if you wouldn't mind testing the partitioning code in the installer at http://penguinppc.org/~walters/debian/installer-cvs on your pismo, I'd appreciate it. I hope I'll find time to test it tomorrow or at least sometime this week. The keymap I chose wasn't for a Mac. I think the new-powermac flavour should at least offer Mac keymaps by default. This is very strange. I just picked the default keymap (I can't remember what it was called), and it worked fine. The basic layout was fine, but I couldn't type 'special' symbols like |. I suspect it was the sg map (for a PC keyboard), not mac-usb-de_CH. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: using ancient kernels
On Mit, 2002-02-27 at 18:10, Eduard Bloch wrote: apuskver:= 2.2.10 I was going to ask if this could be updated to something current. :) It's not too important though because APUS users can use other kernels for the boot-floppies. Success has been reported with 2.4.17 kernels from upstream. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Testing boot-floppies on iMac
On Sam, 2002-02-16 at 21:27, Matt Zimmerman wrote: After all packages were installed, I set about trying to get X working, and (after using the debconf prompts to get an initial configuration) co-workers and I fiddled with it for some time before discovering that we had to specify the PCI BusID in XF86Config-4, and google for the correct monitor sync information. I don't know why I had to specify the BusID, as it detected the video card (an ATI) at the correct PCI bus/slot/func during initialization. I had a Device section specifying Driver ati, but until I added the BusID parameter, it said that it couldn't find a matching device section for the card. A device section without a bus ID is normally assigend to the primary adapter; unfortunately, the primary adapter isn't recognized reliably yet on Macs. Providing the bus ID is the safe bet, and there's a debconf question for it now. Also, how can I help to test future PowerPC boot-floppies? Is there some way to network-boot this beast, or do I have to continue to use CD-Rs? You can boot the installer kernel with the ramdisk from HD with yaboot, or am I missing something? -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0.18 testing needed
On Wed, 2002-01-02 at 22:29, Michel Lanners wrote: Hey all, Some further checking on the ramdisk... On 2 Jan, this message from Michel Dänzer echoed through cyberspace: On Wed, 2002-01-02 at 01:05, Philip Blundell wrote: In message [EMAIL PROTECTED], Michel Lanners writes: - trying to use mac-fdisk from a shell, I get this error: /sbin/mac-fdisk: 1: Syntax error: ( unexpected 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, or something else. One of the PPC folks probably needs to look at it. I'd suggest rebuilding bf and see if it consistently creates crap. daenzer@pismo file /mnt/sbin/mac-fdisk~ /mnt/sbin/mac-fdisk: ELF 32-bit MSB executable, no machine, version 1 (SYSV), dynamically linked (uses shared libs), stripped OK, I get the same. daenzer@pismo /mnt/sbin/mac-fdisk ~ zsh: exec format error: /mnt/sbin/mac-fdisk Same. (1)daenzer@pismo /mnt/sbin/fdisk ~ mac-fdisk: bad usage - no device argument mac-fdisk [-h|--help] mac-fdisk [-v|--version] mac-fdisk [-l|--list [name ...]] mac-fdisk [-r|--readonly] name ... mac-fdisk name ... Hehehe. Got you ;-) So /sbin/mac-fdisk is hosed for some reason, but /sbin/fdisk seems to be a working mac-fdisk. Nope: [root@piglet /mnt/jaz]# file sbin/fdisk sbin/fdisk: Bourne shell script text Ah? Hmm, let's see: [root@piglet /mnt/jaz]# cat sbin/fdisk #!/bin/sh # # fdisk, a wrapper to use the right fdisk on Linux/PowerPC [snip] case $Arch in [snip] Power*|iMac*|[Pp]ower[bB]ook*) # if Power Macintosh /sbin/mac-fdisk $@ exit 0 ;; Thank you for showing us you have a working /sbin/mac-fdisk :-)) Very convincing though, wasn't it? ;) Which also explains why the step 'partioning hd' in debootstrap brings me back to debootstrap immediately: exit 0! Yeah, I was wondering about that... Well, that's what I get for wanting to check out things too quickly, sorry for the fuss. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 3.0.18 testing needed
On Wed, 2002-01-02 at 01:05, Philip Blundell wrote: In message [EMAIL PROTECTED], Michel Lanners writes: - trying to use mac-fdisk from a shell, I get this error: /sbin/mac-fdisk: 1: Syntax error: ( unexpected 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, or something else. One of the PPC folks probably needs to look at it. daenzer@pismo file /mnt/sbin/mac-fdisk~ /mnt/sbin/mac-fdisk: ELF 32-bit MSB executable, no machine, version 1 (SYSV), dynamically linked (uses shared libs), stripped daenzer@pismo /mnt/sbin/mac-fdisk ~ zsh: exec format error: /mnt/sbin/mac-fdisk (1)daenzer@pismo /mnt/sbin/fdisk ~ mac-fdisk: bad usage - no device argument mac-fdisk [-h|--help] mac-fdisk [-v|--version] mac-fdisk [-l|--list [name ...]] mac-fdisk [-r|--readonly] name ... mac-fdisk name ... So /sbin/mac-fdisk is hosed for some reason, but /sbin/fdisk seems to be a working mac-fdisk. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppy short-term status
Adam Di Carlo wrote: Please do check unstable for your arch has the newest tasksel, base-config, and busybox -- you may have to port it for your arch. For powerpc, busy-box is at 1.0.51-5 which is pretty close, so someone is keeping it up. The other two are the same as i386. I will get it to be the very newest... I wish some of the powerpc porters would do a bit of work to make sure stuff in base needed by boot-floppies were up to date, esp. tasksel, busybox, stuff like that. It would save me time... I think the buildd on voltaire usually takes care of that, but the machine was down because it was moved. Anyway, if you need something just post to the powerpc list and I or someone else will pick it up. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot-floppies: test list other
Giorgio Terzi wrote: Compressed image too large! Aborting. crc errorDecompression error -- aborting Looks like an old boothack with a kernel size limit. We should probably upgrade to the latest one where that limit is lifted. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Alan Buxey wrote: Do we need Minix fs support yet? Not for installation. the ramdisk image no longer uses MiniFS? if so minifs could be dropped ages ago. You mean our test ramdisk.image.gz ? I asked eons ago if we should convert it to ext2, if it's still Minix we should do that now. We could use it as a rescue or other fancy stuff with a current glibc etc. I guess we also dont need OCS gfx support...as PowerPC cards only work on ECS and AGA systems. On this line of thought...sound isnt essential, neither is parallel port?, joystick.. I already considered all this and am now at 848 K. How much space exactly do we have? -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Sven LUTHER wrote: But, we definitively need 2 batches of kernels, since i suppose some guys would want the networking stuff also. They can use the non floppy version though. Can't they use the modules? I'd really like to have a single .config, otherwise maintenance is a nightmare. Is this small enough? I guess I could squeeze out a few more K... Do we need support for foreign partition maps? not really, they could be modules. No they can't. I've removed anything but Amiga, I think those who really need something else should build their own kernels. Also do you have pm2fb and co in there ? maybe this 880 ko kernels would be only for aga, this way we have only 1 possible video= mode in the amiboot script. Other modes can be choosen later on. I don't think this is feasible as some people won't have anything connected to their AGA output. Right now all the Amiga framebuffer devices are in. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Geert Uytterhoeven wrote: On Thu, 17 May 2001, Michel Dänzer wrote: I already considered all this and am now at 848 K. How much space exactly do we have? IIRC you have 837 kB free on an OFS-formatted floppy. Since we all use FFS these days it (at least the kernel) should fit. And don't use DC-FFS since it will waste^H^H^H^H^Hconsume even more diskspace. :) AFAIR FFS gives the full 880K minus a few? BTW if we could use bzip2, we'd be all set already: michdaen@pismo du -sk vmapus.bz2 ~/src/apus-cvs/2.4 776 vmapus.bz2 -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Alan Buxey wrote: I already considered all this and am now at 848 K. How much space exactly do we have? well, if we need the following s:startup-sequence - a few bytes... libs:ppc.library (for powerup - not needed for A1200, but for a3k/a4k a1200 has this in ROM) *or* we go with WarpUPwhich ever has the smallest libraries envarc: a few bytes of required env: variables for WarpUP (if used) the boot tool (eg one i'm working on.) tens of K could be compressed (eg with stonecracker) if needed) bootstrap + the bootstrap_pup or bootstrap_wup - 100's of k's How much fits onto one 880K formatted disk, i cant recall, its been so longis it 856k? I can see the kernel needing to be ~500k nastycould 2.2.10 get this small? I doubt it. Brainstorming: We could throw out _all_ disk drivers except that for the floppy; everything else would have to be loaded as modules. This brings it down to 660K. OTOH the modules will take lots of space; is there some kind of limit, e.g. from the ramdisk size? We could make one floppy with just the kernel on it and another one which boots, copies everything to RAM: and... you get the idea. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Sven LUTHER wrote: I am trying to understand why... For an 880k floppy the space problem makes impossible to do it. But i wish to be contraddicted... :)) Well, we could split the kernel in 2 and join it in ram: before launching it. Or we could try for a less than 880Ko modular kernel, but i have not big hopes on this one. I am experimenting, and it looks promising. I basically moved everything except video and disk drivers to modules and here's what it gives so far: michdaen@pismo gzip -cv9 vmlinux vmapus.gz ~/src/apus-cvs/2.4 vmlinux: 60.1% michdaen@pismo ll vmapus.gz~/src/apus-cvs/2.4 -rw-r--r--1 michdaen src888321 May 16 19:49 vmapus.gz michdaen@pismo du -k vmapus.gz ~/src/apus-cvs/2.4 868 vmapus.gz Is this small enough? I guess I could squeeze out a few more K... Do we need support for foreign partition maps? Do the fbcon packed pixels modules work? Do we need Minix fs support yet? The other side of the story will probably be the space needed for the modules... -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Geert Uytterhoeven wrote: You don't need fbcon-cfb24 and fbcon-cf32 since no one wants to run an install console in those depths anyway. I don't think you need it for half-supported gfx cards with amiboot -v, only depth 16. Will this prevent X from running in those depths? Thanks for your feedback! michdaen@pismo du -sk src/apus-cvs/2.4/vmapus.gz~ 856 src/apus-cvs/2.4/vmapus.gz More suggestions welcome... -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
Geert Uytterhoeven wrote: On Tue, 15 May 2001, Sven LUTHER wrote: On Tue, May 15, 2001 at 11:11:38AM +0200, Geert Uytterhoeven wrote: On Tue, 15 May 2001, Sven LUTHER wrote: You cannot boot from 1.4 MB floppies, only from 880 kB or 1760 kB floppies. Well, ok no problem, just make a tarball that can be copied to 1760Kb floppies, it is even better, since we have more place for stuff. I don't think we can ever fit a kernel and amiboot in 880kb, could we ? My 2.4.4 zImage is only 458036 bytes long. I have lots of modules, but it could work. I remember I once did. Can we use modules for the install on APUS? Our strategy has been to include all possible hardware into the kernel. -- Earthling Michel Dänzer (MrCooper)\ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \XFree86 and DRI project member -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.
Sven LUTHER wrote: On Sun, Jul 09, 2000 at 01:36:41PM -0700, Daniel Jacobowitz wrote: On Sun, Jul 09, 2000 at 10:24:36PM +0200, Michel Dänzer wrote: $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt And see if it can be mounted ... It works if I omit the '=/dev/loop0' , and now on the second try (after getting back to the installer main menu) df shows /dev/loop0 . So the problem must be elsewhere, any ideas? Oho! Now that is interesting. Is /dev/loop0 created properly (I think someone doublechecked that earlier...)? If so, then I would blame the APUS kernel patches. Ok, but remember, when i install the base tarball by hand, the above works without problem, with the exact same kernel. But then modules are installed, that is the only difference, but the loop module is builtin. Could there be another module that has soime influence on this ? You can find out very easily: lsmod will tell after you have mounted the image. What really caught my eye in the log though was that dbootstrap doesn't even use the -o loop[=...] mount option, it apparently uses losetup to initialize the loop device and then mounts from it directly. I feel the problem might be there somewhere. Michel -- ...and that is how we know the Earth to be banana-shaped. __ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.
Sven LUTHER wrote:
Everything works fine, but when i come to the step where i would normally do
:
* install os kernel modules
i give the corrct place in the requester, and dbootstrap tries to loop mount
the rescue.bin image to fetch the kernel and the modules, and fail.
Confirm that. ("Roger that" ;)
Messages from VT 3 I consider relevant:
running cmd 'mount -r -t ext2 /dev/loop0 /floppy'
Mounting /dev/loop0 on /floppy failed: invalid argument
Looks like it tries to use /dev/loop0 as a fake floppy drive and fails.
I then tried testing by hand, with :
$ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
Mounting rescue.bin on /mnt failed : block device required
It has just worked for me with just '-o loop', and I notice that it seems to
be mounted from /dev/loop1 (df output).
$ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
And see if it can be mounted ...
It works if I omit the '=/dev/loop0' , and now on the second try (after
getting back to the installer main menu) df shows /dev/loop0 .
So the problem must be elsewhere, any ideas?
Michel
--
Software is like sex; it's better when it's free - Linus Torvalds
__
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.
Sven LUTHER wrote: i give the corrct place in the requester, and dbootstrap tries to loop mount the rescue.bin image to fetch the kernel and the modules, and fail. Should drivers.tgz be in rescue.bin? It's not. If the config.gz in rescue.bin is the config of the kernel you use, it does indeed include the loopback device and vfat. Now the strange thing, is that when i continue the installation stuff and reboot with the same kernel on the partition just installed from the base tarball, i can mount the rescue.bin image with the exact command given above. Thus i suspsect the problem lie with the root.bin image. or maybe the dbootstrap mount command. That's a strong indication. BTW what's the fs type of root.bin supposed to be? I can't mount it here. Michel -- Apologies are so hard to give. Would you accept some potatoes instead? __ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
