From: Andreas <an...@po...> - 2002-03-16 23:38:24
|
Hi 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, but on debian-boot, Chris told me it would be a dbootsrap issue and should be fixed. Today I've downloaded the root.bin from http://people.debian.org/~aph/debian/dists/woody/main/disks-powerpc/3.0.21-2002-03-13/apus/images-1.44/ Adam built and replaced the 3.0.19 root.bin in the apus/images-1.44/ folder with the new one. Still using the 2.4.17 apus kernel. But, unlucky me, nothings seems to have changed, the bug still appears, and so I still can't Initialize a Linux partition. I've quoted myself in the following lines just to give a short overview over the problem itself: > [First thing is,] that it is not possible to execute the point "Initialize a > Linux Partition". After selecting this point in the menu, the screen goes > white, and the installer system restarts! > > On console 3 I could read: > > Mar 3 ... (none) user.info init: Process '/sbin/udbootstrap' (pid 140) exited. Scheduling it for restart > > Mar 3 ... (none) user.info init: Starting pid 146, console /dev/console: '/sbin/udbootstrap' Here I have to say that it now also didn't want to work with a virgin disk without an already valid root partition (but of course already partitioned from the AmigaOS side). I wonder about this, because the 'Initialize..' part worked perfectly well with an 2.4.9 apus kernel (but this isn't much use to me, as 2.4.9 doesn't support dhcp, and so I can't install the rest of the system after the reboot *snif*). I hope you can see my dilemma: kernel 2.4.9 is the only one which supports my NIC and I can 'Initialize...', but it doesn't support DHCP. 2.4.17 does support my NIC and DHCP, but I can't 'Initialize...'.. ps: Why are the driver-1.bin and rescue.bin files in .../apus/images-1.44/ still built, although they doesn't seem to be needed? pps: Does the new color of the selection bar really have to be red? It gives a very bad contrast with the underlying text. Lucky me I've already tried to install debian that much that I can recall the selection lines from my mind. And oh, concerning the ongoing 'malformed release file' discussion: I very often got this message in the last few weeks (when I've been trying to install with other kernels than 2.4.17, but, as I said, no success with them, because of the lacking dhcp support..)!! -- Thanks for any idea, kind regards, Andi |
From: Colin W. <wa...@de...> - 2002-03-17 19:05:32
|
On Sat, 2002-03-16 at 18:32, Andreas W=C3=BCst wrote: > I wonder about this, because the 'Initialize..' part worked perfectly wel= l with an > 2.4.9 apus kernel (but this isn't much use to me, as 2.4.9 doesn't suppor= t dhcp, and so I can't install > the rest of the system after the reboot *snif*). By "2.4.9 doesn't support dhcp", I'm assuming you mean it was compiled without CONFIG_FILTER or CONFIG_PACKET; I'll look into fixing that if so. Anyways, have you tried diffing the .configs between the 2.4.9 apus kernel and your 2.4.17 kernel? |
From: Andreas <an...@po...> - 2002-03-17 19:14:23
|
Hi Colin > On Sat, 2002-03-16 at 18:32, Andreas W=C3=BCst wrote: >> I wonder about this, because the 'Initialize..' part worked perfectly = well >> with an 2.4.9 apus kernel (but this isn't much use to me, as 2.4.9 doe= sn't >> support dhcp, and so I can't install the rest of the system after the >> reboot *snif*). >=20 > By "2.4.9 doesn't support dhcp", I'm assuming you mean it was compiled > without CONFIG_FILTER or CONFIG_PACKET; I'll look into fixing that if > so. Yep, exactly. But Michel had already uploaded a dhcp enabled kernel, the latest 2.4.17 kernel to say. I just can't imagine that compiling those network options broke the abili= ty to initialize a partition.. Either it has something to do with the kernel itself (2.4.9 vs. 2.4.17), = or its surroundings (whatever that may be, kernel detection on installer sys= tem, compiler options, etc.) > Anyways, have you tried diffing the .configs between the 2.4.9 apus > kernel and your 2.4.17 kernel? Nope! What should I be looking for? I am now going to file a bug against bf's, as Chris advised me. --=20 Thanks for your answer, Andi |
From: Colin W. <wa...@de...> - 2002-03-17 19:57:08
|
On Sun, 2002-03-17 at 14:09, Andreas W=C3=BCst wrote: > > Anyways, have you tried diffing the .configs between the 2.4.9 apus > > kernel and your 2.4.17 kernel? >=20 > Nope! What should I be looking for? I don't know; like important platform-specific config options that you might have missed. > I am now going to file a bug against bf's, as Chris advised me. OK, but as far as I know no one is actively working on and testing apus support in the boot-floppies, so it is unlikely this bug will be fixed (ever, since the b-f code base is being terminated after woody). |
From: Andreas <an...@po...> - 2002-03-17 22:08:33
|
Hi Colin > On Sun, 2002-03-17 at 14:09, Andreas W=C3=BCst wrote: >=20 >>> Anyways, have you tried diffing the .configs between the 2.4.9 apus >>> kernel and your 2.4.17 kernel? >>=20 >> Nope! What should I be looking for? >=20 > I don't know; like important platform-specific config options that you > might have missed. Having a look at it in the next days! >> I am now going to file a bug against bf's, as Chris advised me. >=20 > OK, but as far as I know no one is actively working on and testing apus > support in the boot-floppies, so it is unlikely this bug will be fixed > (ever, since the b-f code base is being terminated after woody). Testing? Well, I do!! Quite intensively unfortunately.. Well, if it doesn't get fixed, it would mean that a whole release would b= e uninstallable by network for all the x-surf users outthere without tricki= ng around? (but to be fair: there doesn't seem to be too much users with a x-surf NIC, so I can understand your point!) --=20 Thanks again for input, best wishes, Andi |
From: Michel <da...@de...> - 2002-03-17 23:50:05
|
On Son, 2002-03-17 at 00:32, Andreas W=FCst wrote: >=20 > 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 wel= l 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. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |