Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2009-03-07 Thread Martin Michlmayr
* Giuseppe Sacco giuse...@eppesuigoccas.homedns.org [2009-01-24 23:43]:
 Il giorno sab, 24/01/2009 alle 20.57 +0100, Martin Michlmayr ha scritto:
 [...]
  However, just for the record: adding pci(0) in all cases is a bad idea
  since it will break the Indy.  So if adding pci(0) is needed (and from
  what you say this may not be true), we should only do it on IP32.
 
 I confirm it is not compulsory since I am booting the O2 every day
 without the pci(0) part.

So can this bug report be closed?
-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2009-03-07 Thread Giuseppe Sacco
Il giorno sab, 07/03/2009 alle 22.22 +0100, Martin Michlmayr ha scritto:
 * Giuseppe Sacco giuse...@eppesuigoccas.homedns.org [2009-01-24 23:43]:
  Il giorno sab, 24/01/2009 alle 20.57 +0100, Martin Michlmayr ha scritto:
  [...]
   However, just for the record: adding pci(0) in all cases is a bad idea
   since it will break the Indy.  So if adding pci(0) is needed (and from
   what you say this may not be true), we should only do it on IP32.
  
  I confirm it is not compulsory since I am booting the O2 every day
  without the pci(0) part.
 
 So can this bug report be closed?

I think so, since the other reported problem is now on a different
report #510130.

Bye,
Giuseppe




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2009-01-24 Thread Martin Michlmayr
* Giuseppe Sacco giuse...@eppesuigoccas.homedns.org [2009-01-14 12:11]:
 Later on, I halted the system, plugged in the pci card again, booted and
 looked at those values. They were still without the pci(0) part and
 the system booted correctly.
 
 So, I think something changed these values, maybe because I had this pci
 board installed, but the variables value doesn't require the pci(0),
 at least until you boot using the internal controller :-)

Pretty strange that it didn't fail to boot initially then.  BTW, I
looked at my local docs for IP32 and I in fact used the pci(0)
parameter.  However, since my IP32 is dead, I cannot do any further
tests.

However, just for the record: adding pci(0) in all cases is a bad idea
since it will break the Indy.  So if adding pci(0) is needed (and from
what you say this may not be true), we should only do it on IP32.

-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2009-01-24 Thread Giuseppe Sacco
Il giorno sab, 24/01/2009 alle 20.57 +0100, Martin Michlmayr ha scritto:
[...]
 However, just for the record: adding pci(0) in all cases is a bad idea
 since it will break the Indy.  So if adding pci(0) is needed (and from
 what you say this may not be true), we should only do it on IP32.

I confirm it is not compulsory since I am booting the O2 every day
without the pci(0) part.

Bye,
Giuseppe




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2009-01-14 Thread Giuseppe Sacco
Il giorno mer, 31/12/2008 alle 16.54 +0100, Martin Michlmayr ha scritto:
 * Giuseppe Sacco giuse...@eppesuigoccas.homedns.org [2008-12-29 01:36]:
  ... installation goes to the end and print this message about PROM:
  
xsetenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)  a 
  x   
xsetenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)  a 
  x   
xsetenv OSLoader arcboota 
  x   
xsetenv OSLoadFilename Linuxa 
  x   
  
  then rebooted the machine, but I found that first two variables are
  missing a pci(0) in front. Correct values seems to be:
  setenv SystemPartition pci(0)scsi(0)disk(1)rdisk(0)partition(8)
  setenv OSLoadPartition pci(0)scsi(0)disk(1)rdisk(0)partition(0)
 
 I'm pretty sure it worked without pci(0) for me.  I guess you need the
 pci(0) because your O2 has some PCI cards in it whereas mine didn't.
 Thomas, do you think this is correct?  And is the SCSI controller
 always pci(0)?  If so, I can add this to the message.

I just removed the PCI card and found the very same values. This is
probably normal since these values where stored when then pci card was
inserted. Then I changed both values removing the pci(0) part and the
system booted correctly.

Later on, I halted the system, plugged in the pci card again, booted and
looked at those values. They were still without the pci(0) part and
the system booted correctly.

So, I think something changed these values, maybe because I had this pci
board installed, but the variables value doesn't require the pci(0),
at least until you boot using the internal controller :-)

Bye,
Giuseppe




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2008-12-31 Thread Martin Michlmayr
* Giuseppe Sacco giuse...@eppesuigoccas.homedns.org [2008-12-29 01:36]:
 ... installation goes to the end and print this message about PROM:
 
   xsetenv SystemPartition scsi(0)disk(1)rdisk(0)partition(8)  a x 
   
   xsetenv OSLoadPartition scsi(0)disk(1)rdisk(0)partition(0)  a x 
   
   xsetenv OSLoader arcboota x 
   
   xsetenv OSLoadFilename Linuxa x 
   
 
 then rebooted the machine, but I found that first two variables are
 missing a pci(0) in front. Correct values seems to be:
 setenv SystemPartition pci(0)scsi(0)disk(1)rdisk(0)partition(8)
 setenv OSLoadPartition pci(0)scsi(0)disk(1)rdisk(0)partition(0)

I'm pretty sure it worked without pci(0) for me.  I guess you need the
pci(0) because your O2 has some PCI cards in it whereas mine didn't.
Thomas, do you think this is correct?  And is the SCSI controller
always pci(0)?  If so, I can add this to the message.
-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2008-12-29 Thread Frans Pop
On Monday 29 December 2008, Giuseppe Sacco wrote:
 Comments/Problems:
 0) only the internal ethernet board is recognized. The network pci
 board is not found by the first kernel. It is found after reboot with a
 final kernel;

Please try to find out why by comparing the output of lsmod and dmesg for 
the installer and installed system. My guess would be that maybe a module 
is missing in D-I.

 1) fdisk give errors when creating a second partition (I found a
 workaround)
 2) an unexistant partition 17 is displayed in partition list when
 selecting partition usage
 4) information about PROM is slightly wrong

These should probably be discussed on the debian-mips mailing list as it 
is a port-specific issue (IIRC mips is the only port that does not use 
partman). Please make sure that any results are either implemented by the 
porters directly or communicated clearly to the D-I team.

 3) no LVM and device mapper available at installation time (no big
 problem, I think)

If mips does not use partman I think lvmcfg can be loaded as an optional 
component. I'm not sure whether or not it should be loaded by default.

Cheers,
FJP



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2008-12-29 Thread Martin Michlmayr
* Frans Pop elen...@planet.nl [2008-12-29 09:26]:
  0) only the internal ethernet board is recognized. The network pci
  board is not found by the first kernel. It is found after reboot with a
  final kernel;
 
 Please try to find out why by comparing the output of lsmod and dmesg for 
 the installer and installed system. My guess would be that maybe a module 
 is missing in D-I.

We don't include any network modules, except for the one that's
built-in on the O2.  This could easily be changes post-lenny if
there's sufficient interest.
-- 
Martin Michlmayr
http://www.cyrius.com/



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2008-12-29 Thread Giuseppe Sacco
Il giorno lun, 29/12/2008 alle 10.32 +0100, Martin Michlmayr ha scritto:
 * Frans Pop elen...@planet.nl [2008-12-29 09:26]:
   0) only the internal ethernet board is recognized. The network pci
   board is not found by the first kernel. It is found after reboot with a
   final kernel;
  
  Please try to find out why by comparing the output of lsmod and dmesg for 
  the installer and installed system. My guess would be that maybe a module 
  is missing in D-I.
 
 We don't include any network modules, except for the one that's
 built-in on the O2.  This could easily be changes post-lenny if
 there's sufficient interest.

I am afraid, there will be no interest at all, since O2 are now rare and
they have a built-in network card.

The only problem I really care, related to this report, is the fdisk
error. I am looking at its source code to check if I find the bug.

Bye,
Giuseppe




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2008-12-29 Thread Giuseppe Sacco
Il giorno lun, 29/12/2008 alle 10.38 +0100, Giuseppe Sacco ha scritto:
[...]
 The only problem I really care, related to this report, is the fdisk
 error. I am looking at its source code to check if I find the bug.

I just found this problem and reported it against util-linux as bug
#510130. I will try to understand the second important problem: why d-i
is listing partition number 17.

Whenever #510130 will be closed, I'll write a note here, so that d-i
image could be regenerated with a corrected fdisk command

Bye,
Giuseppe.





-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2008-12-28 Thread Giuseppe Sacco
Package: installation-reports

Boot method: network via tftp
Image version: 
http://cdimage.debian.org/cdimage/lenny_di_rc1/mips/jigdo-dvd/debian-testing-mips-DVD-1.jigdo
Date: 29 December 2008

Machine: Silicon Graphics O2
Processor: r5...@200mhz
Memory: 384Mb
Partitions:
sgi:~# cat /proc/partitions 
major minor  #blocks  name  

   8 0   71819496 sda   
   8 13204967 sda1  
   8 2 803250 sda2  
   8 3   67802332 sda3  
   8 9   2048 sda9  
   811   71818582 sda11 
   816   17847430 sdb   
   817   17842176 sdb1  
   825   5120 sdb9  
   827   17847296 sdb11
Output of lspci -knn (or lspci -nn):

~ # lspci -knn
00:01.0 SCSI storage controller [0100]: Adaptec AIC-7880U [9004:8078]
Kernel driver in use: aic7xxx
00:02.0 SCSI storage controller [0100]: Adaptec AIC-7880U [9004:8078]
Kernel driver in use: aic7xxx
00:03.0 PCI bridge [0604]: NetMos Technology Device [9710:9250] (rev 01)
01:08.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
01:08.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43)
01:08.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04)
01:09.0 FireWire (IEEE 1394) [0c00]: Agere Systems FW323 [11c1:5811] (rev 61)
01:0a.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8169 
Gigabit Ethernet [10ec:8169] (rev 10)

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [E]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

summary:
0) only the internal ethernet board is recognized. The network pci board
is not found by the first kernel. It is found after reboot with a final
kernel;
1) fdisk give errors when creating a second partition (I found a
workaround)
2) an unexistant partition 17 is displayed in partition list when
selecting partition usage
3) no LVM and device mapper available at installation time (no big
problem, I think)
4) information about PROM is slightly wrong

installation details:

booted with:
 bootp(): append=console=ttyS0,38400 
debian-installer/allow_unauthenticated=true

Disk /dev/sda (SGI disk label): 255 heads, 63 sectors, 8941 cylinders
Units = cylinders of 16065 * 512 bytes

- partitions -
Pt#Device  Info Start   End   Sectors  Id  System
 1: /dev/sda1  boot 1  8940 143621100  83  Linux native
 9: /dev/sda2   0 0  4096   0  SGI volhdr
11: /dev/sda3   0  8940 143637165   6  SGI volume
- Bootinfo -
Bootfile: /unix
- Directory Entries -
 0: arcbootsector4 size   72492

Command (m for help): d
Partition number (1-16): 11

Command (m for help): d
Partition number (1-16): 9

Command (m for help): d
Partition number (1-16): 1

Command (m for help): p

Disk /dev/sda (SGI disk label): 255 heads, 63 sectors, 8941 cylinders
Units = cylinders of 16065 * 512 bytes

- partitions -
Pt#Device  Info Start   End   Sectors  Id  System
- Bootinfo -
Bootfile: /unix
- Directory Entries -
 0: arcbootsector4 size   72492

Command (m for help): n
Partition number (1-16): 1
Attempting to generate entire disk entry automatically.
First cylinder (1-8940, default 1): 
Using default value 1
 Last cylinder (1-8940, default 8940): 2000

Command (m for help): p

Disk /dev/sda (SGI disk label): 255 heads, 63 sectors, 8941 cylinders
Units = cylinders of 16065 * 512 bytes

- partitions -
Pt#Device  Info Start   End   Sectors  Id  System
 1: /dev/sda1  boot 1  2000  3213  83  Linux native
 9: /dev/sda2   0 0  4096   0  SGI volhdr
11: /dev/sda3   0  8940 143637165   6  SGI volume
- Bootinfo -
Bootfile: /unix
- Directory Entries -
 0: arcbootsector4 size   72492


Command (m for help): n
Partition number (1-16): 2
First cylinder (1-0): 1
Value out of range.
First cylinder (1-0): 0
Value out of range.
First cylinder (1-0): 2001

Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2008-12-28 Thread Christian Perrier
Quoting Giuseppe Sacco (giuse...@eppesuigoccas.homedns.org):
 Package: installation-reports
 
 Boot method: network via tftp
 Image version: 
 http://cdimage.debian.org/cdimage/lenny_di_rc1/mips/jigdo-dvd/debian-testing-mips-DVD-1.jigdo


Have you tested with the daily buildsĀ ?



signature.asc
Description: Digital signature


Bug#510060: installation report for lenny d-i rc1 on silicon graphics O2

2008-12-28 Thread Giuseppe Sacco
Il giorno lun, 29/12/2008 alle 08.06 +0100, Christian Perrier ha
scritto:
 Quoting Giuseppe Sacco (giuse...@eppesuigoccas.homedns.org):
  Package: installation-reports
  
  Boot method: network via tftp
  Image version: 
  http://cdimage.debian.org/cdimage/lenny_di_rc1/mips/jigdo-dvd/debian-testing-mips-DVD-1.jigdo
 
 
 Have you tested with the daily builds ?

not yet. I will test it tonight.




-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org