Re: New miboot-enabled d-i daily builds set up

2006-05-15 Thread Hans Ekbrand
On Mon, May 15, 2006 at 12:35:51AM +0200, Jerome Warnier wrote:
 Le mercredi 03 mai 2006 à 01:11 +0100, Colin Watson a écrit :
  Hi,
  
  I've set up miboot-enabled daily builds of d-i powerpc floppies, to go
  with my normal daily builds:
  
http://people.debian.org/~cjwatson/d-i/powerpc-miboot/
  
  Thanks to Sven Luther for the miboot package used to build these. Let me
  know if there are any problems; I haven't been able to test them myself.
 I checked it on a PowerMac G3 beige.

Here's my results from a Performa 5400 (24 MB RAM):

2006-05-15: Boot ends with Instruction dump:
7ca6 ... ... ... [ a lot of numbers in two lines]

 Version 2006-05-14 didn't boot at all.
2006-05-14: not tested (suspected the same problem as with 06-05-15)

 Version 2006-05-13 boots, and it already gets pretty far, but it cannot
 detect any disk
2006-05-13: Boots OK (didn't put out the floppy automatically though,
I had to use a paperclip to get it out). The root image also works
good, until hw-detection.

Doesn't find my ide disk.

~  # ls /lib/modules/2.6.16-1-powerpc-miboot/kernel/drivers
baseieee1394net scsi

No ide here!

I found the ide drivers on the cd-drivers.img. That should be
documented somewhere, since a net-install will fail without
hd-support.

Also after loading the net-drivers.img the installer failed to detect
my ethernet de2104x PCI. I tried to load tulip dc21x4x manually but
it failed.

This was still an interesting test, since I have not been able to boot
2.6.16 on this machine, but that must be a problem with the initrd
created by initramfs (or possibly something with the way quik boots)

-- 
Hans Ekbrand (http://sociologi.cjb.net) [EMAIL PROTECTED]
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?


signature.asc
Description: Digital signature


Re: New miboot-enabled d-i daily builds set up

2006-05-15 Thread Jerome Warnier
Le lundi 15 mai 2006 à 10:49 +0200, Hans Ekbrand a écrit :
 On Mon, May 15, 2006 at 12:35:51AM +0200, Jerome Warnier wrote:
  Le mercredi 03 mai 2006 à 01:11 +0100, Colin Watson a écrit :
   Hi,
   
   I've set up miboot-enabled daily builds of d-i powerpc floppies, to go
   with my normal daily builds:
   
 http://people.debian.org/~cjwatson/d-i/powerpc-miboot/
   
   Thanks to Sven Luther for the miboot package used to build these. Let me
   know if there are any problems; I haven't been able to test them myself.
  I checked it on a PowerMac G3 beige.
 
 Here's my results from a Performa 5400 (24 MB RAM):
 
 2006-05-15: Boot ends with Instruction dump:
 7ca6 ... ... ... [ a lot of numbers in two lines]
 
  Version 2006-05-14 didn't boot at all.
 2006-05-14: not tested (suspected the same problem as with 06-05-15)
 
  Version 2006-05-13 boots, and it already gets pretty far, but it cannot
  detect any disk
 2006-05-13: Boots OK (didn't put out the floppy automatically though,
 I had to use a paperclip to get it out). The root image also works
 good, until hw-detection.
You're right, I got used to the paperclip stuff with the previous
versions, so I didn't even bother to specify it, but it is surely not
practical at all.

 Doesn't find my ide disk.
Same thing here, except that I'm not actually sure it is an IDE disk,
and not an SCSI one (I think I have both in the machine, and none is
detected).

 ~  # ls /lib/modules/2.6.16-1-powerpc-miboot/kernel/drivers
 base  ieee1394net scsi
 
 No ide here!
 
 I found the ide drivers on the cd-drivers.img. That should be
 documented somewhere, since a net-install will fail without
 hd-support.
Thanks, I will try this.

 Also after loading the net-drivers.img the installer failed to detect
 my ethernet de2104x PCI. I tried to load tulip dc21x4x manually but
 it failed.
It detects mine (this is the second NIC I talked about in my mail).

 This was still an interesting test, since I have not been able to boot
 2.6.16 on this machine, but that must be a problem with the initrd
 created by initramfs (or possibly something with the way quik boots)
-- 
Jérôme Warnier
FLOSS Consultant
http://beeznest.net



Re: New miboot-enabled d-i daily builds set up

2006-05-15 Thread Jérôme Warnier
Le lundi 15 mai 2006 à 18:16 +0200, Jerome Warnier a écrit :
 Le lundi 15 mai 2006 à 10:49 +0200, Hans Ekbrand a écrit :
  On Mon, May 15, 2006 at 12:35:51AM +0200, Jerome Warnier wrote:
   Le mercredi 03 mai 2006 à 01:11 +0100, Colin Watson a écrit :
Hi,

I've set up miboot-enabled daily builds of d-i powerpc floppies, to go
with my normal daily builds:

  http://people.debian.org/~cjwatson/d-i/powerpc-miboot/

Thanks to Sven Luther for the miboot package used to build these. Let me
know if there are any problems; I haven't been able to test them myself.
   I checked it on a PowerMac G3 beige.
  
  Here's my results from a Performa 5400 (24 MB RAM):
  
  2006-05-15: Boot ends with Instruction dump:
  7ca6 ... ... ... [ a lot of numbers in two lines]
  
   Version 2006-05-14 didn't boot at all.
  2006-05-14: not tested (suspected the same problem as with 06-05-15)
  
   Version 2006-05-13 boots, and it already gets pretty far, but it cannot
   detect any disk
  2006-05-13: Boots OK (didn't put out the floppy automatically though,
  I had to use a paperclip to get it out). The root image also works
  good, until hw-detection.
 You're right, I got used to the paperclip stuff with the previous
 versions, so I didn't even bother to specify it, but it is surely not
 practical at all.
Some more news on this side: it seems that once the cd-drivers floppy is
loaded, it can (and actually does) eject the floppies after reading
them. Could it be that the eject utility is located on this floppy
image? In this cas, it would probably be a good idea to move it to the
root floppy (at least on OldWorld PPC, or only on PPC floppies).

  Doesn't find my ide disk.
 Same thing here, except that I'm not actually sure it is an IDE disk,
 and not an SCSI one (I think I have both in the machine, and none is
 detected).
It seems I have at least a SCSI one, but it does not work nicely (again,
once the cd-drivers floppy is loaded): it gets detected multiple times,
and at least the first one doesn't work like expected, it is impossible
to partition and format.

  ~  # ls /lib/modules/2.6.16-1-powerpc-miboot/kernel/drivers
  baseieee1394net scsi
  
  No ide here!
  
  I found the ide drivers on the cd-drivers.img. That should be
  documented somewhere, since a net-install will fail without
  hd-support.
 Thanks, I will try this.
 
  Also after loading the net-drivers.img the installer failed to detect
  my ethernet de2104x PCI. I tried to load tulip dc21x4x manually but
  it failed.
 It detects mine (this is the second NIC I talked about in my mail).
 
  This was still an interesting test, since I have not been able to boot
  2.6.16 on this machine, but that must be a problem with the initrd
  created by initramfs (or possibly something with the way quik boots)



Re: New miboot-enabled d-i daily builds set up

2006-05-14 Thread Jerome Warnier
Le mercredi 03 mai 2006 à 01:11 +0100, Colin Watson a écrit :
 Hi,
 
 I've set up miboot-enabled daily builds of d-i powerpc floppies, to go
 with my normal daily builds:
 
   http://people.debian.org/~cjwatson/d-i/powerpc-miboot/
 
 Thanks to Sven Luther for the miboot package used to build these. Let me
 know if there are any problems; I haven't been able to test them myself.
I checked it on a PowerMac G3 beige.
Version 2006-05-14 didn't boot at all.
Version 2006-05-13 boots, and it already gets pretty far, but it cannot
detect any disk (I thing there is only one, connected to the embedded
Symbios Logic 53c875). It tries to reset the SCSI bus several times, but
gets anyway to the message rejection I/O to offline device about sda.
I loaded the net-drivers[1] and it downloaded the required d-i modules
through my Internet connection, so the network (including DHCP) is
working fine.

Also, how hard would it be to provide CDROM images? It's increasingly
difficult to find working floppies nowadays. I have tons of broken ones,
though.

[1] I have a second NIC in the machine and both got detected fine.

 Cheers,
-- 
Jérôme Warnier
FLOSS Consultant
http://beeznest.net



Re: New miboot-enabled d-i daily builds set up

2006-05-03 Thread Wolfgang Pfeiffer
Thanks a lot for your work 

On Wed, May 03, 2006 at 01:11:48AM +0100, Colin Watson wrote:
 Hi,
 
 I've set up miboot-enabled daily builds of d-i powerpc floppies, to go
 with my normal daily builds:
 
   http://people.debian.org/~cjwatson/d-i/powerpc-miboot/
 
 Thanks to Sven Luther for the miboot package used to build these. Let me
 know if there are any problems; I haven't been able to test them myself.

On a alubook 5,8, testing the 
debian-testing-powerpc-businesscard.iso 

--
1: It boots correctly
2: Choose language/Country: Works (for German)

3: Choose keyboard: Does work with restrictions for a German one:
   German umlauts are unavailable on the (ncurses) installer menu:
   Umlauts work on the console.

4: The installer hung for minutes, giving me no messages whatsoever on
   tty4 for the reason of this issue: Then, after - for my taste - a
   much too long time it gave me back a crashed installerscreen to choose
   the network card. At this point I couldn't even change to tty4 or
   tty(2?). After a few minutes of waiting I pressed the power button
   for a new try.

   The reason for the crash *might* have been either that I chose the
   wrong network card (eth1) or the fact that I tried umlauts on the choose
   hostname screen: The latter meant I typed an umlaut which ended in
   something like F1 or E4 and similarly wrong output. Then trying
   the key on the right side of the Apple key then unexpectedly worked as an
   ENTER key, thus setting the Rechnername (something like machine
   name in English?) with these wrong umlaut substitutes.

5: The installer did not not recognise an attached SCSI disk, that was
   connnected to the machine via Firewire 400. I expected the disk on
   sda, and I tried to see it with mac-fdisk and with a simple 
   ls /dev/ and then typing TAB to see the optional devices ...
   
   I chose Festplatten erkennen, something like detect hard discs,
   to no avail ...
   
/dev/hda inside the machine, was detected correctly with all
partitions, as it seems ... 
 
6: Network (Internet) connection, manually configured because I do not
   use DHCP on the router, seems to work 

After the partitioning screen I rebooted (just to be sure it didn't
change anything ... :)

More tests on the business card iso? Let me know if yes, please ..

Best Regards
Wolfgang

-- 
Wolfgang Pfeiffer: /ICQ: 286585973/ + + +  /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer

Key ID: E3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113fingerprint=on


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: New miboot-enabled d-i daily builds set up

2006-05-03 Thread Wolfgang Pfeiffer
On Wed, May 03, 2006 at 03:58:26PM +0200, Wolfgang Pfeiffer wrote:
 Thanks a lot for your work 
 
 On Wed, May 03, 2006 at 01:11:48AM +0100, Colin Watson wrote:
  Hi,
  
  I've set up miboot-enabled daily builds of d-i powerpc floppies, to go
  with my normal daily builds:
  
http://people.debian.org/~cjwatson/d-i/powerpc-miboot/
  
  Thanks to Sven Luther for the miboot package used to build these. Let me
  know if there are any problems; I haven't been able to test them myself.
 
 On a alubook 5,8, testing the 
 debian-testing-powerpc-businesscard.iso 

The report below seems to be true also for the 
debian-testing-powerpc-netinst.iso   

 
 --

 [ ... ]


 4: The installer hung for minutes, giving me no messages whatsoever on
tty4 for the reason of this issue: Then, after - for my taste - a
much too long time it gave me back a crashed installerscreen to choose
the network card. At this point I couldn't even change to tty4 or
tty(2?). After a few minutes of waiting I pressed the power button
for a new try.
 
The reason for the crash *might* have been either that I chose the
wrong network card (eth1) or the fact that I tried umlauts on the choose
hostname screen: The latter meant I typed an umlaut which ended in

Not being sure any more which installer screen it really was (choose
hostname, or choose machine name. No matter which one it was: the
installer crashed with the businesscard.iso ... The reason, as I wrote
before, could also have been that I chose the wrong NIC ... please see
below ..

something like F1 or E4 and similarly wrong output. Then trying
the key on the right side of the Apple key then unexpectedly worked as an
ENTER key, thus setting the Rechnername (something like machine
name in English?) with these wrong umlaut substitutes.

This time it crashed after first choosing the (wrong) eth1 NIC when
trying to configure the network, then manually configuring the NIC and
then typing the Rechnername (machine name) with Umlauts.

And it took about 7 minutes until I had back the crashed installer
screen (some possible timeout netcfg set too high?) ... But I could go
back to tty2 and reboot from there ...

When configuring the network with the wrong NIC (eth1) and then *not*
setting the machine name with umlauts does not crash the installer
screen here: I simply change the NIC to eth0 and everything moves on
as expected ...

Not being sure whether all this really helps 'tho ..


 
 5: The installer did not not recognise an attached SCSI disk, that was
connnected to the machine via Firewire 400. I expected the disk on
sda, and I tried to see it with mac-fdisk and with a simple 
ls /dev/ and then typing TAB to see the optional devices ...

I chose Festplatten erkennen, something like detect hard discs,
to no avail ...

This time I switched off and on again the SCSI disk: When switching it
on I got on tty4:

kernel: ieee1394: Error parsing configrom for node 0-00:1023
kernel: ieee1394: Node changed: 0-00:1023 - 0-02:1023


 /dev/hda inside the machine, was detected correctly with all
 partitions, as it seems ... 

Ditto with debian-testing-powerpc-netinst.iso, as it seems ..

Regards
Wolfgang

-- 
Wolfgang Pfeiffer: /ICQ: 286585973/ + + +  /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer

Key ID: E3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113fingerprint=on


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: New miboot-enabled d-i daily builds set up

2006-05-03 Thread Wolfgang Pfeiffer
On Wed, May 03, 2006 at 06:02:10PM +0200, Wolfgang Pfeiffer wrote:
 On Wed, May 03, 2006 at 03:58:26PM +0200, Wolfgang Pfeiffer wrote:
  Thanks a lot for your work 
  
  On Wed, May 03, 2006 at 01:11:48AM +0100, Colin Watson wrote:
   Hi,
   
   I've set up miboot-enabled daily builds of d-i powerpc floppies, to go
   with my normal daily builds:
   
 http://people.debian.org/~cjwatson/d-i/powerpc-miboot/
   
   Thanks to Sven Luther for the miboot package used to build these. Let me
   know if there are any problems; I haven't been able to test them myself.
  
  On a alubook 5,8, testing the 
  debian-testing-powerpc-businesscard.iso 
 
 The report below seems to be true also for the 
 debian-testing-powerpc-netinst.iso   


Just realised I'm in the wrong thread: my test reports in the current
thread are referring to the isos in

http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/

My apologies for the confusion 

Regards
Wolfgang


-- 
Wolfgang Pfeiffer: /ICQ: 286585973/ + + +  /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer

Key ID: E3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113fingerprint=on


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: New miboot-enabled d-i daily builds set up

2006-05-02 Thread Eugen Paiuc

Colin Watson wrote:


Hi,

I've set up miboot-enabled daily builds of d-i powerpc floppies, to go
with my normal daily builds:

 http://people.debian.org/~cjwatson/d-i/powerpc-miboot/

Thanks to Sven Luther for the miboot package used to build these. Let me
know if there are any problems;
 


sorry , boot.img can't  change the initial gui to console.

tested on 7200/90

regards,
eugen


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]