Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)
user debian-boot@lists.debian.org usertags 541831 sparc tags 541831 moreinfo thanks Hi Stephen, On Wednesday 26 August 2009, Frans Pop wrote: On Monday 17 August 2009, Stephen Gran wrote: It sounds like the rsc console is something different, which could explain what you saw. Maybe we need special handling for this case. The rsc is much like an iLo or alom. It's just another management interface that offers a 'console' interface to manage the OS. I did the install using this interface, obtained by running 'break -c'. [...] Can you find out what /var/run/console-device contains at that point? I'd expect /dev/ttyS0, but it would be good to know for sure. You can probably find out by booting with BOOT_DEBUG=3 and then in /sbin/reopen-console add a 'set -x' plus near the end a 'sleep 30' so you have time to read the output. [...] We have solved similar problems in that past. The only thing that's needed is *some* way of identifying this case. Possibly there's something in /proc from openprom? We could then do something similar as was done for powerpc (see the code after # Set up virtualized... in [3]). The final option would be to add a dialog that's displayed if we are uncertain and that just asks what to use. Might be useful for other cases too. Main question is if you're willing and able to do a bit more digging :-) Are you interested in persuing this further? In case you're not, I'm tagging the BR for posterity. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)
Processing commands for cont...@bugs.debian.org: user debian-boot@lists.debian.org Setting user to debian-boot@lists.debian.org (was sg...@debian.org). usertags 541831 sparc Bug#541831: installation-reports: Sunfire T2000 success (one minor issue) There were no usertags set. Usertags are now: sparc. tags 541831 moreinfo Bug #541831 [finish-install] installation-reports: Sunfire T2000 success (one minor issue) Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)
This one time, at band camp, Frans Pop said: Hi Stephen, Hi Frans, Are you interested in persuing this further? In case you're not, I'm tagging the BR for posterity. I am interested - my problem at the moment is that the machine has been promised for the sparc64 port. I'm waiting on doko to let us know what he needs with the machine before I take it up and down for various tests. Unfortunately, I haven't heard anything recently. I'll ping doko again and see what the state of things are. FWIW, I've been pointed at http://lists.debian.org/debian-sparc/2009/04/msg00024.html . The follow up suggests it may already have some fixes in? It's possible I may not have gotten the r1 image, although I thought I was using the latest image. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)
On Wednesday 16 September 2009, Frans Pop wrote: Yep, I know about that post, but I'm not sure whether that's related or not. AFAIK that issue was about having no console output at all, not about incorrect configuration of the installed system. Well, the second part of the mail is this issue. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)
On Wednesday 16 September 2009, Stephen Gran wrote: FWIW, I've been pointed at http://lists.debian.org/debian-sparc/2009/04/msg00024.html . The follow up suggests it may already have some fixes in? It's possible I may not have gotten the r1 image, although I thought I was using the latest image. Yep, I know about that post, but I'm not sure whether that's related or not. AFAIK that issue was about having no console output at all, not about incorrect configuration of the installed system. However, both that and this issue really need some quality time from someone with access to a box to help us make any needed changes in the installer. And we simple have no sparc users or porters providing any quality input. I'm pretty sure that any tweaks will turn out to be fairly minor, but they'll never happen if nobody provides the needed info and testing. Frans -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)
On Monday 17 August 2009, Stephen Gran wrote: It sounds like the rsc console is something different, which could explain what you saw. Maybe we need special handling for this case. The rsc is much like an iLo or alom. It's just another management interface that offers a 'console' interface to manage the OS. I did the install using this interface, obtained by running 'break -c'. OK. So the problem is that there is no direct link between the rsc and the (serial) console to be used for the installed system. Questions: - What were the contents of /etc/inittab after the installation? Were the entries for tty[1-6] commented out or not? [contents of /etc/inittab] So regular consoles were enabled. That's expected. I mainly asked to confirm. #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 I had to uncomment T0 to get a console with 'console -f' from the rsc. So the rsc is somehow linked to ttyS0. ~ # console-type serial This is at least one clue: D-I *does* detect it's a serial connection. ~ # readlink /proc/self/fd/0 /dev/console That's a logical value if it isn't /dev/ttyS0. - If the first is not serial and/or the last is not /dev/ttyS0, then how could the need to set up serial console be detected? That's a very good question. Interestingly, I see this in dmesg: [ 32.032662] console handover: boot [earlyprom0] - real [tty0] So at least at that point, the kernel thinks it _is_ tty0. That's fairly normal. In the past we've also seen on sparc: [0.00] console [earlyprom0] enabled [ 53.918290] Console: colour dummy device 80x25 [ 53.971361] console handover: boot [earlyprom0] - real [tty0] [ 59.676537] Console: switching to mono PROM 80x34 [ 64.238061] Console: ttyS0 (SAB82532) [ 64.308951] console [ttyS0] enabled Is there anything after that first message in your case? The full boot log would be useful to have for this issue. Unfortunately, I don't know enough about whether there is a difference between what you attach to with 'console -f' in the rsc and what you attach to with 'break -c'. I naively think that they should be the same thing, but it is possible that they are not. /me is completely lost here. - Does the installer work correctly and does a listener for serial console get set up for the installed system if you boot D-I with console=ttyS0? No: steal-ctty: No such file or directory steal-ctty: No such file or directory steal-ctty: No such file or directory Over and over. That might be a bug in itself that's worth fixing. The source for steal-ctty is at [1]. It is called by [2], which does the actual detection. The loop is probably because init keeps failing and resets. Can you find out what /var/run/console-device contains at that point? I'd expect /dev/ttyS0, but it would be good to know for sure. You can probably find out by booting with BOOT_DEBUG=3 and then in /sbin/reopen-console add a 'set -x' plus near the end a 'sleep 30' so you have time to read the output. So, this doesn't look like a problem the installer can fix. It's just odd that the OS doesn't see the serial console on the same device as the installer does: sg...@zee:~$ readlink /proc/self/fd/0 /dev/ttyS0 Well, I'm a bit mystified about how this could be fixed, so I don't mind if you want to close it as unresolvable or punt it over to the sparc porters to see if they can shed any light on it. We have solved similar problems in that past. The only thing that's needed is *some* way of identifying this case. Possibly there's something in /proc from openprom? We could then do something similar as was done for powerpc (see the code after # Set up virtualized... in [3]). The final option would be to add a dialog that's displayed if we are uncertain and that just asks what to use. Might be useful for other cases too. Main question is if you're willing and able to do a bit more digging :-) Cheers, FJP [1]http://svn.debian.org/wsvn/d-i/trunk/packages/rootskel/src/sbin/steal-ctty.c [2]http://svn.debian.org/wsvn/d-i/trunk/packages/rootskel/src/sbin/reopen-console-linux [3]http://svn.debian.org/wsvn/d-i/trunk/packages/finish-install/finish-install.d/90console -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)
This one time, at band camp, Frans Pop said: reassign 541831 finish-install 2.22 thanks On Sunday 16 August 2009, Stephen Gran wrote: Comments/Problems: The only complaint from the install is that after the install was completed and the machine rebooted, there was no getty listening on ttyS0. Was the installation itself done over ttyS0? If it was, it surprises me a lot that there was no inittab entry for it. It sounds like the rsc console is something different, which could explain what you saw. Maybe we need special handling for this case. The rsc is much like an iLo or alom. It's just another management interface that offers a 'console' interface to manage the OS. I did the install using this interface, obtained by running 'break -c'. Questions: - What were the contents of /etc/inittab after the installation? Were the entries for tty[1-6] commented out or not? # Note that on most Debian systems tty7 is used by the X Window System, # so if you want to add more getty's go ahead but skip tty7 if you run X. # 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 # Example how to put a getty on a serial line (for a terminal) # #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 I had to uncomment T0 to get a console with 'console -f' from the rsc. - Can you reboot the installer, activate a debug shell and give the output of: - console-type ~ # console-type serial - readlink /proc/self/fd/0 ~ # readlink /proc/self/fd/0 /dev/console - # 'pidof debian-installer' does not work in lenny, so we need: ps | grep [/]sbin/debian-installer readlink /proc/pid from command above/fd/0 ~ # pidof debian-installer ~ # ps | grep [/]sbin/debian-installer 912 root 1600 S/bin/sh /sbin/debian-installer ~ # readlink /proc/912/fd/0 /dev/console - If the first is not serial and/or the last is not /dev/ttyS0, then how could the need to set up serial console be detected? That's a very good question. Interestingly, I see this in dmesg: [ 32.032662] console handover: boot [earlyprom0] - real [tty0] So at least at that point, the kernel thinks it _is_ tty0. Unfortunately, I don't know enough about whether there is a difference between what you attach to with 'console -f' in the rsc and what you attach to with 'break -c'. I naively think that they should be the same thing, but it is possible that they are not. - Does the installer work correctly and does a listener for serial console get set up for the installed system if you boot D-I with console=ttyS0? No: steal-ctty: No such file or directory steal-ctty: No such file or directory steal-ctty: No such file or directory Over and over. So, this doesn't look like a problem the installer can fix. It's just odd that the OS doesn't see the serial console on the same device as the installer does: sg...@zee:~$ readlink /proc/self/fd/0 /dev/ttyS0 Well, I'm a bit mystified about how this could be fixed, so I don't mind if you want to close it as unresolvable or punt it over to the sparc porters to see if they can shed any light on it. If changes are needed, that would probably be in the script /usr/lib/finish-install.d/90console (from finish-install). Looks like it's unlikely to need any patching. Cheers, -- - | ,''`.Stephen Gran | | : :' :sg...@debian.org | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)
Package: installation-reports Severity: normal -- Package-specific info: Boot method: network Image version: http://ftp.nl.debian.org/debian/dists/lenny/main/installer-sparc/current/images/netboot/boot.img Date: 2009-08-15 Machine: Sun Sunfire T2000 Partitions: sg...@zee:~$ df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/zeevg-root ext3 7688360 1008076 6289732 14% / tmpfstmpfs16563896 0 16563896 0% /lib/init/rw udev tmpfs 10240 152 10088 2% /dev tmpfstmpfs16563896 0 16563896 0% /dev/shm /dev/sda1 ext3 186667 16120160909 10% /boot /dev/mapper/zeevg-home ext3 9611492152704 8970548 2% /home /dev/mapper/zeevg-srv ext328834812176196 28658616 1% /srv sg...@zee:~$ sudo fdisk -l Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sda (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sda1 0241927801 Boot /dev/sda224 8924 71489250 fd Linux raid autodetect /dev/sda3 0 8924 716820305 Whole disk Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sda1 (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sda1p1 0241927801 Boot /dev/sda1p224 8924 71489250 fd Linux raid autodetect /dev/sda1p3 0 8924 716820305 Whole disk Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sda3 (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sda3p1 0241927801 Boot /dev/sda3p224 8924 71489250 fd Linux raid autodetect /dev/sda3p3 0 8924 716820305 Whole disk Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sdb (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sdb1 024192780 83 Linux native /dev/sdb224 8924 71489250 fd Linux raid autodetect /dev/sdb3 0 8924 716820305 Whole disk Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sdb1 (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sdb1p1 024192780 83 Linux native /dev/sdb1p224 8924 71489250 fd Linux raid autodetect /dev/sdb1p3 0 8924 716820305 Whole disk Detected sun disklabel with wrong version [0x]. Detected sun disklabel with wrong sanity [0x]. Detected sun disklabel with wrong num_partitions [0]. Warning: Wrong values need to be fixed up and will be corrected by w(rite) Disk /dev/sdb3 (Sun disk label): 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device FlagStart EndBlocks Id System /dev/sdb3p1 024192780 83 Linux native /dev/sdb3p224 8924 71489250 fd Linux raid autodetect /dev/sdb3p3 0 8924 716820305 Whole disk 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: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O]
Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)
reassign 541831 finish-install 2.22 thanks On Sunday 16 August 2009, Stephen Gran wrote: Comments/Problems: The only complaint from the install is that after the install was completed and the machine rebooted, there was no getty listening on ttyS0. Was the installation itself done over ttyS0? If it was, it surprises me a lot that there was no inittab entry for it. It sounds like the rsc console is something different, which could explain what you saw. Maybe we need special handling for this case. Questions: - What were the contents of /etc/inittab after the installation? Were the entries for tty[1-6] commented out or not? - Can you reboot the installer, activate a debug shell and give the output of: - console-type - readlink /proc/self/fd/0 - # 'pidof debian-installer' does not work in lenny, so we need: ps | grep [/]sbin/debian-installer readlink /proc/pid from command above/fd/0 - If the first is not serial and/or the last is not /dev/ttyS0, then how could the need to set up serial console be detected? - Does the installer work correctly and does a listener for serial console get set up for the installed system if you boot D-I with console=ttyS0? If changes are needed, that would probably be in the script /usr/lib/finish-install.d/90console (from finish-install). Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)
Processing commands for cont...@bugs.debian.org: reassign 541831 finish-install 2.22 Bug #541831 [installation-reports] installation-reports: Sunfire T2000 success (one minor issue) Bug reassigned from package 'installation-reports' to 'finish-install'. Bug #541831 [finish-install] installation-reports: Sunfire T2000 success (one minor issue) Bug Marked as found in versions finish-install/2.22. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
