Bug#683124: debian-installer: incomplete serial console configuration

[christian mock]

Package: debian-installer
Severity: normal


The installer, when run with a serial console, does configure some
parts of the system to account for this, but not all.

When I run the installer (from debian-6.0.5-i386-businesscard.iso) and
edit the installer's kernel command line to include
"console=ttyS0,9600n8", the installed system then has a getty on ttyS0
configured in inittab, and "GRUB_TERMINAL=serial" plus
"GRUB_SERIAL_COMMAND" in /etc/default/grub, so the installed system
works with that serial console.

What is missing, however, is the matching "console=ttyS0..." parameter
in "GRUB_CMDLINE_LINUX", so the boot messages go to the VGA console
and (if the boot suceeds) the next thing I see on the serial console
is the login prompt.

regards,

cm.


-- 
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/20120728231306.533.40273.reportbug@localhost

Bug#515157: Installation Report Lenny RC2 SPARC R220 2x 450 MHz, 2 GM RAM, 2x 9.1 GB Disk

[Christian Mock]

Package: installation-reports

Boot method: 
Image version: 


Date: <2009-02-13>

Machine: 
Processor: 2x 450 MHz
Memory: 2GB
Partitions: <2x 9.1 GB, use entire disk>

Output of lspci -knn (or lspci -nn):

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

Initial boot:   [ O]
Detect network card:[O ]
Configure network:  [ E] DHCP failed, manually works, but late: 
getting ntp

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

Comments/Problems:

Partitioner detects 2x 9.1 disks but can use 2GB only. Manullay 
partitions with size <= 2GB works. Same error at 2 different R220. >





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

Bug#393718: installation-report: minor translation issues in german

[christian mock]

Package: installation-reports
Version: 2.17
Severity: minor



-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/debian-testing-i386-netinst.iso
 20061016
Date: 2006-10-17

Machine: VMware Workstation 5.5.1 build-19175
Partitions: guided partitioning


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]

Comments/Problems:

did a quick test of the graphical installer, keyboard and mouse are detected
fine in VMware. then I did an installation with the ascii-mode installer.

regarding the german translation (when selecting german as the installation
language):

while partitioning choice #3 reads "gefuehrt - gesamte platte mit verschl. LVM
einrichten"; the "verschl." was unclear to me at first (and supposedly would
be for a novice user), I'd suggest not abbreviating it.

later, the text uses "blockgeraeteverschluesselung" (block device encryption),
which sounds rather IBMese and is not what anybody actually says in german,
I'd suggest changing it to "festplattenverschluesselung" (hard disk
encryption), which is less exact, but much better sounding.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report.

Once you have filled out this report, mail it to [EMAIL PROTECTED]

==
Installer hardware-summary:
==

installation-report depends on no packages.

Versions of packages installation-report recommends:
ii  reportbug 3.30   reports bugs in the Debian distrib

-- no debconf information


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

Bug#271181: installation-reports: complete failure with 2.6 kernel on compaq proliant 3000

[christian mock]

Package: installation-reports
Version: N/A; reported 2004-09-11
Severity: critical
Justification: breaks the whole system

Debian-installer-version: sarge-i386-netinst.iso RC1, downloaded 2004-09-10
uname -a: n/a
Date: 2004-09-11
Method: netinst CD based install with "expert26"

Machine: Compaq Proliant 3000
Processor: 2x PII-450
Memory: 768MB
Root Device: SCSI, /dev/sda1
Root Size/partition table: 
   8 02055000 scsi/host0/bus0/target0/lun0/disc 8598 41254 99716 58900 8542 
149865 317002 2158920 0 141590 2217820
   8 11927768 scsi/host0/bus0/target0/lun0/part1 8594 41248 99690 58820 8542 
149865 317002 2158920 0 141510 2217740
   8 2  1 scsi/host0/bus0/target0/lun0/part2 0 0 0 0 0 0 0 0 0 0 0
   8 5 120456 scsi/host0/bus0/target0/lun0/part5 1 0 8 20 0 0 0 0 0 20 20

Output of lspci and lspci -n:
:00:00.0 Host bridge: ServerWorks CNB20-LE Host Bridge (rev 04)
:00:00.1 Host bridge: ServerWorks CNB20-LE Host Bridge (rev 02)
:00:03.0 System peripheral: Compaq Computer Corporation Advanced System Management 
Controller
:00:06.0 PCI bridge: Intel Corp. 80960RP [i960 RP Microprocessor/Bridge] (rev 05)
:00:06.1 Memory controller: Intel Corp. 80960RP [i960RP Microprocessor] (rev 05)
:00:09.0 Network controller: Compaq Computer Corporation Netelligent 10/100 TX PCI 
UTP (rev 10)
:00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 4d)
:00:11.0 Host bridge: ServerWorks CNB20-LE Host Bridge (rev 04)
:00:11.1 Host bridge: ServerWorks CNB20-LE Host Bridge (rev 02)
:01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC 
[Mach64 GT IIC] (rev 7a)
:02:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 14)
:02:04.1 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 14)
:02:08.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 05)

:00:00.0 0600: 1166:0007 (rev 04)
:00:00.1 0600: 1166:0005 (rev 02)
:00:03.0 0880: 0e11:a0f0
:00:06.0 0604: 8086:0960 (rev 05)
:00:06.1 0580: 8086:1960 (rev 05)
:00:09.0 0280: 0e11:ae32 (rev 10)
:00:0f.0 0601: 1166:0200 (rev 4d)
:00:11.0 0600: 1166:0007 (rev 04)
:00:11.1 0600: 1166:0005 (rev 02)
:01:00.0 0300: 1002:4756 (rev 7a)
:02:04.0 0100: 1000:000f (rev 14)
:02:04.1 0100: 1000:000f (rev 14)
:02:08.0 0200: 8086:1229 (rev 05)


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

Initial boot worked:[O]
Configure network HW:   [E]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [E]

Comments/Problems:

The problem is with hardware auto-discovery -- the system has a compaq
"remote insight board" (lights out management hardware) at PCI
:00:06.0 and :00:06.1, which is mis-detected as a megaraid
controller, and "insmod megaraid" then hangs.

This happens during non-expert install, but can be worked around by
using expert mode and deselecting the megaraid driver when is is
detected. Still, when rebooting from hard disk (grub in the drive's
boot sector), the autodetection in the initrd makes the same error, so
the system never completes the boot.

This means it's impossible to get a working 2.6 sarge install with
this card in the machine, since the "rescue" entry in the grub menu
isn't able to get around the initrd hw-detection stuff, and even
mounting the root fs from a knoppix boot and deleting the hw-detection
stuff doesn't help, as it is still in the initrd.

Note that the hardware detection seems to be severely broken WRT the
megaraid card, as it also shows up in the list of modules offered
after "detect network hardware" (together with the modules for the two
NICs that are correctly detected; no other modules are mis-detected as
network cards).

In the end, I booted the 2.4 installer and installed the 2.4.26
kernel, and it worked. Still had to deselect the megaraid module
during the install, but the installed OS boots fine.

As a personal comment: I think this "hold the user's hand" stuff is
going in the wrong direction for debian -- If I need a distro which
thinks it is smarter than me (thereby breaking stuff, as demonstrated
here), I can use SuSE, fedora or mandrake.

I would strongly suggest either

- removing hardware autodetection from the initrd and instead going
  with the fixed list of modules which were detected/used with d-i.

- providing some way to get around the autodetection in initrd (maybe
  there is such a way, but the d-i manual and FAQ don't describe it)

cm.



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

Bug#248047: Cobalt install

[christian mock]

On Thu, May 20, 2004 at 06:48:25PM +0100, Martin Michlmayr wrote:

> Ah, thanks for testing.  I'll try to get the ext2 revision 0 program
> pushed into testing before Sunday, so if you could do an installation
> of "testing" on Sunday this would be appreciated.  This should work
> 100% without any problems, and if there are any, we have to fix them
> for rc1.

Technically, it's already monday :-) -- OK, installing, with
everything freshly downloaded from
http://people.debian.org/~tbm/d-i/images/mipsel/daily/cobalt/netboot/
right now.

The installer starts, but when the "configuring network via DHCP" part
comes along, it fails, although (trumm is the DHCP server, remailer
the installing machine):

00:51:44.084701 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0xdcfa9144 secs:7 
[|bootp] [tos 0x10] 
00:51:44.085960 trumm.tahina.priv.at.bootps > remailer.tahina.priv.at.bootpc:  
xid:0xdcfa9144 secs:7 Y:remailer.tahina.priv.at S:bauer.tahina.priv.at [|bootp] [tos 
0x10] 
00:51:46.991307 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0xdcfa9144 secs:7 
[|bootp] [tos 0x10] 
00:51:46.992601 trumm.tahina.priv.at.bootps > remailer.tahina.priv.at.bootpc:  
xid:0xdcfa9144 secs:7 Y:remailer.tahina.priv.at S:bauer.tahina.priv.at [|bootp] [tos 
0x10] 

I select "try again", it sends no more DHCP packets, asks me for a
hostname, and continues. The system is alive on the net, I can ping
it.

I toggle the power, and try again. Now it works.

It asks for a hostname, although it has gotten one via DHCP.

All the predefined partitioning schemes are missing the cobalt boot
partition:

"Multi-user system":


  |   IDE1 master - 20.4 GB ST320423A   #   |   
  |   >  #1 primary  148.0 MB B f ext3   /  #   |   
  |   >  #5 logical5.0 GB   f ext3   /usr   #   |   
  |   >  #6 logical3.0 GB   f ext3   /var   #   |   
  |   >  #7 logical   16.4 MB   f ext3   /tmp   #   |   
  |   >  #8 logical   11.7 GB   f ext3   /home  #   |   
  |   >  #9 logical  518.1 MB   F swap   swap   #   |   

"All files in one partition":

  |   IDE1 master - 20.4 GB ST320423A   |   
  |   >  #1 primary   19.9 GB B f ext3   /  |   
  |   >  #5 logical  509.9 MB   f swap   swap   |   

"Separate partition for home directories":

  |   IDE1 master - 20.4 GB ST320423A   #   |   
  |   >  #1 primary5.6 GB B f ext3   /  #   |   
  |   >  #5 logical   14.3 GB   f ext3   /home  #   |   
  |   >  #6 logical  509.9 MB   f swap   swap   #   |   

So I keep the layout that's already on disk from the last installer run:

  |   IDE1 master - 20.4 GB ST320423A   #   |   
  |   >  #1 primary   98.6 MB B F ext2r0 /boot  #   |   
  |   >  #2 primary   19.8 GB   F ext3   /  #   |   
  |   >  #5 logical  518.1 MB   F swap   swap   #   |   


The rest of the installation was OK; network configuration happens
automatically (from the DHCP data), /etc/network/interfaces is
generated, machine boots, fine.

HTH,

cm.

-- 
** christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
...the [APL] Execution Environment (makes me think about sunny walls,
indifferent marksmen, and the offer of a blindfold and a cigarette)...
-- Mike Andrews


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

Bug#248047: Cobalt install

[christian mock]

On Thu, May 20, 2004 at 06:48:25PM +0100, Martin Michlmayr wrote:

> > installation report revealing a show-stopper:
> 
> The show-stopper is the network configuration, right?

yup.

> I'll forward this to the netcfg maintainer.  Can you check in
> /var/log/debian-installer/package-versions which version of netcfg was
> used?
> 
> But if you did the install today, I guess it was 0.64.  Yeah, must be
> 0.64.

Right.

> That's okay because those modules are only optional modules; those
> which are required were not shown.  Did the menu not make that clear?

No, that was quite clear; I just mentioned it to make the install
report as reproducible as possible.

> > [many hours later... boy, is that box slw!]
> 
> Really?  It takes about 45 minutes here (fast network connection).
> How long does it take for you (roughly)?

I didn't look at the clock, but 45 mins sounds about right -- y'know,
when you're used to installing woody on 1GHz++ machines...

> > - in base-config, there's no visual indication of the active button --
> >   both look exactely like this (i.e. no bold or inverse or stuff,
> >   cursor is somewhere else):
> >  . Is the hardware clock set to GMT? .  
> >  .  .  
> 
> Did you do the installation without a colour-enabled terminal program?

I'm using minicom in an rxvt, both from woody; I think I've never seen
color in minicom.

> > - line editing characters (^U, ^A, ...) don't work in text entry fields.
> 
> Do you know if that worked before?

It does work in the woody installer, and it did work in the original
installation test (during base-config).

> Ah, thanks for testing.  I'll try to get the ext2 revision 0 program
> pushed into testing before Sunday, so if you could do an installation
> of "testing" on Sunday this would be appreciated.  This should work
> 100% without any problems, and if there are any, we have to fix them
> for rc1.

OK, I'll try to find the time.

ciao,

cm.

-- 
** christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
> 'schweinesystem, repressives'.
Könnt ihr nicht wenigstens aus diesem Thread OS/400 raushalten?
  -- frank paulsen und fefe in dasr

Bug#248047: Cobalt install

[christian mock]

On Wed, May 19, 2004 at 01:40:15AM +0100, Martin Michlmayr wrote:

> > The LCD could be more verbose, i.e. after "loading debian-installer"
> > it could say "connect to the console now".
> 
> I will consider doing this unless we get SSH support.

With ssh, it should display "now telnet to xx.xx.xx.xx", like the
(inofficial?) woody installer
(http://devel.alal.com/pipermail/cobalt-22/2002-July/000298.html)
does.

> > >  - support installs via SSH, w/o serial console
> > Definitely. And an option to set the serial baudrate (from CoLo
> > onwards) to other speeds, i.e. 9600 like god intended.
> 
> d-i and colo should just support any baud rate... however, I have no
> idea how to change the Cobalt to something else.  Do you know?

I don't think you can change the baud rate used by the cobalt firmware
-- my idea would have been to let colo and the following steps use a
different speed than 115200, but I've got no idea how to tell colo
about it.

> > The partitioning tool doesn't set the swap partition type on the swap
> > partition (it works, so it's a cosmetic error).
> 
> I've seen this too recently.  I've to check if this is still there.

It does the right thing now.

> > inittab apparently has entries for virtual terminals, which those
> > messages:
> > INIT: Id "2" respawning too fast: disabled for 5 minutes
> > INIT: Id "3" respawning too fast: disabled for 5 minutes
> 
> This should be gone now (in unstable).

Yup, inittab looks good.

installation report revealing a show-stopper:

> Do you perhaps have time to test an installation from unstable?  You
> can use the initrd from
> http://people.debian.org/~tbm/d-i/images/mipsel/daily/cobalt/netboot
> (same kernel as before), and the install unstable rather than testing.

OK; I re-fetched the whole setup from that URL into /nfsroot on
bauer.tahina.priv.at (192.168.55.3), which is NFS-exported and has the
TFTP server:

# ls -lR
.:
total 4162
lrwxrwxrwx1 root root4 May 20 17:02 boot -> ./
-rw-rw-r--1 root root  213 May 19 02:22 default.colo
-rw-rw-r--1 root root  1448550 May 19 02:22 initrd.gz
-rw-rw-r--1 root root  2652775 May 19 02:23 vmlinux-2.4.25-r5k-cobalt
-rw-rw-r--1 root root44836 May 19 02:23 vmlinux.gz
-rw-rw-r--1 root root44836 May 19 02:23 vmlinux_RAQ.gz
-rw-rw-r--1 root root44836 May 19 02:23 vmlinux_raq-2800.gz

dhcpd.conf (2.0pl5-11):

host remailer {
hardware ethernet 00:10:E0:00:30:F5;
fixed-address remailer.tahina.priv.at;
option routers 192.168.55.1;
option root-path "/nfsroot";
next-server 192.168.55.3;
filename "/boot/default.colo";
}


Boots fine, menu comes up on LCD, select "TFTP", installer boots.
Interesting points:

- when the installer comes up on the serial console, the LCD
  still shows "loading debian-installer".

- it asks for an IP address and other network config data -- it should
  just use the data it already has gotten via DHCP (ISTR the woody
  netinst does just that)

- it mis-configures the IP address -- I entered
  "192.168.55.18", but it ifconfig's 192.168.55.255. Yes, I tried that
  twice to make sure I didn't mistype the address :-) 

~ # ifconfig
eth0  Link encap:Ethernet  HWaddr 00:10:E0:00:30:F5  
  inet addr:192.168.55.255  Bcast:192.168.55.255  Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:55 errors:1 dropped:0 overruns:0 frame:0
  TX packets:22 errors:4 dropped:0 overruns:0 carrier:4
  collisions:0 txqueuelen:1000 
  RX bytes:4221 (4.1 KiB)  TX bytes:968 (968.0 B)
  Interrupt:4 

  I went thru the process of configuring debian mirror and proxy,
  "execute a shell" afterwards and ifconfig manually with the correct
  values; exit from the shell, choose "Choose a mirror...", continue.

- The first time when asking for a debian mirror, it didn't ask if I
  wanted http or ftp; the second time around, it does. Also, it
  doesn't remember the country I selected first time around.

- it does configure /etc/resolv.conf with the nameservers I entered,
  but it doesn't add "search domain.name" or "domain domain.name";
  therefore I need to enter the FQDN of the proxy.

- select "unstable"

- in the "load installer components" screen, I selected "continue",
  all of the offered modules were unselected by default and left that
  way.

- partitioning: the disk already had partitions and file systems from
  the last test; choose "partitioning method: erase entire disk".

- partitioning scheme: "all files in one partition"; looks OK:

  |   IDE1 master (hda) - 20.4 GB ST320423A #   |   
  |   >  #1 primary   98.6 MB B f ext2r0 /boot  #   |   
  |   >  #2 primary   19.8 GB   f ext3   /  #   |   
  |   >  #5 logical  518.1 MB   f swap   swap   #   |   

[many hours later... boy, is that box slw!

Bug#248047: (no subject)

[christian mock]

Package: installation-reports

INSTALL REPORT

Debian-installer-version: 2004-05-08, from 
http://http.us.debian.org/debian/dists/testing/main/installer-mipsel/current/images/cobalt/netboot/
uname -a: 
Linux remailer 2.4.25-r5k-cobalt #1 Thu Apr 15 15:17:00 BST 2004 mips GNU/Linux
Date: 2004-05-08, about 19:00GMT
Method: netboot install on cobalt RAQ2/NASRAQ, boot from network (TFTP/NFS),
network install from http://ftp.at.debian.org/, proxied over
my local squid.

Machine: Cobalt NasRAQ
Processor: MIPS, Nevada V10.0  FPU V10.0
Memory: 64 MB
Root Device: IDE (Seagate ST320423A)
Root Size/partition table:  
Disk /dev/hda: 2490 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start End   #cyls#blocks   Id  System
/dev/hda1   *  0+  1   2- 16033+  83  Linux   /boot
/dev/hda2  223112310   18555075   83  Linux   /
/dev/hda3   23122489 1781429785   83  Linux   swap
/dev/hda4  0   -   0  00  Empty

Output of lspci and lspci -n:

:00:00.0 Memory controller: Marvell: Unknown device 4146 (rev 11)
:00:07.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43
 (rev 41)
:00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c860 (rev 02)
:00:09.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo 
VP] (rev 27)
:00:09.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT82
3x/A/C/VT8235 PIPC Bus Master IDE (rev 06)
:00:09.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] 
(rev 02)

:00:00.0 Class 0580: 11ab:4146 (rev 11)
:00:07.0 Class 0200: 1011:0019 (rev 41)
:00:08.0 Class 0100: 1000:0006 (rev 02)
:00:09.0 Class 0601: 1106:0586 (rev 27)
:00:09.1 Class 0101: 1106:0571 (rev 06)
:00:09.2 Class 0c03: 1106:3038 (rev 02)


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

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [ ]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[ ]
Reboot: [O]

Comments/Problems:

given that this is a beta on a rather off-mainstream platform, it worked
very well.



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

Re: Unable to install from hard disk or mounted partition

[christian mock]

> On Sun, 2002-01-27 at 21:22, Chris Tillman wrote:
> > I have these problems fixed, and will commit after 3.0.19 uploads. 
> 
> Very cool!  
> 
> So, can we get 3.0.19 rolling then?  Any objections to uploading it now?

I'd suggest fixing the SEGV in utilities/dbootstrap/baseconfig.c:155, 
as described in bug #126370; it's an easy fix, I'd suggest:

< if (bootargs.console[5]==',') ttyspeed=atoi(bootargs.console+6);
> if (bootargs.console && bootargs.console[5]==',') 
>ttyspeed=atoi(bootargs.console+6);

and it fixes a severe problem for installations over a serial console.

ciao,

cm.

-- 
(from a conversation at ork):
  "I can't see any data coming out of this Tolkien Ring card."
  "Well of course not, it confers invisibility."
  -- Anthony de Boer





msg15183/pgp0.pgp
Description: PGP signature

Bug#126370: serial console problem solved, I think...

[christian mock]

hi,

I think I found the solution to the "inittab doesn't get changed for 
serial console" problem. 

utilities/dbootstrap/baseconfig.c:155:

if (bootargs.console[5]==',') ttyspeed=atoi(bootargs.console+6);

is dereferencing a NULL pointer (bootargs.console) when there's no 
"console=ttyXX" on the kernel command line. 

this crashes dbootstrap just before it can adapt the inittab.

this bug only shows up if you've both got a serial console and don't 
give that explicitly on the kernel command line.

HTH,

cm.

-- 
** christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
Ich beraube mich doch nicht des Vergnügens zu beobachten, wie sich diese
zarte Knospe der Dummheit weiter entfaltet.
 Markus Pirchner ueber xxx in abm-mi




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

spurios crashes of dbootstrap, a trace...

[christian mock]

hi,

I've been testing b-f on PReP for a while, and encountered strange 
crashes (or restarts) of dbootstrap at the end or after the 
debootstrap step -- this is related to the serial console install 
problems related in #126370.

now, the conclusion I've come to is that by disabling line 89 in 
debootstrap's "woody" shell script, which reads

87:cat <$TARGET/dev/initctl >/dev/null &
88:CAT_PID=$!
89:on_exit "kill $CAT_PID >/dev/null 2>&1"

dbootstrap has a chance to survive the end of debootstrap; looks like 
that kill, which seems to just show up as ": no such pid" when 
you look closely, somehow manages to take dbootstrap with it.

my manual tests have shown that dbootstrap's exit code in this case 
is 143, which I also can't explain: apart from some "exit(1)" 
statements, the only one which sets such a high value is the 
exit(128+sig) at crash.c:45, but that is in a signal handler which 
only gets installed for SEGV, as far as I follow the code. 143 is 128 
+ SIGTERM.

well, I'm a bit confused -- the only clear thing is that with that 
line commented out, stuff which occurs in dbootstrap after 
debootstrap is finished does happen, while without that change it 
crashes reproducibly (and I've done quite a few test runs this night).

I hope somebody can solve that mystery...

ciao,

cm.

-- 
** christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
Rechtlich gesehen, besteht kein Anspruch auf Weiterleitung von
Artikeln, die Bilder von Führerscheinumschlägen enthalten.
 ghw in at.usenet





msg15131/pgp0.pgp
Description: PGP signature

Bug#131030: boot-floppies: DHCP doesn't work because kernel hasn't got CONFIG_PACKET and CONFIG_FILTER

[christian mock]

Package: boot-floppies
Version: N/A; reported 2002-01-26
Severity: normal

DHCP config of the network in dbootstrap doesn't work because the kernel
hasn't got the requisite CONFIG_PACKET and/or CONFIG_FILTER options set.

kernel is kernel-image-2.2.20-prep_2.2.20-2_powerpc

-- System Information
Debian Release: 3.0
Architecture: powerpc
Kernel: Linux bauer 2.2.19 #1 Sat Apr 14 22:26:28 CDT 2001 ppc
Locale: LANG=C, LC_CTYPE=C



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

Bug#130926: boot-floppies: selection of rescue disk source only shows floppies after network fail

[christian mock]

Package: boot-floppies
Version: N/A; reported 2002-01-26
Severity: normal

(b-f version is current CVS)

at the "install kernel and driver" step, I gave a network location which
contains a bad resc1440.bin; after confirming the "unable to mount the 
rescue floppy" error message, the next screen to come up is "select
floppy disk drive" which only offers me /dev/fd0 and /dev/fd1, it's missing
all the other options. "cancel" brings two more error messages and puts me
back to the main menu...

cm.

-- System Information
Debian Release: 3.0
Architecture: powerpc
Kernel: Linux bauer 2.2.19 #1 Sat Apr 14 22:26:28 CDT 2001 ppc
Locale: LANG=C, LC_CTYPE=C



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

Re: netbooting root.bin?

[christian mock]

> 
> For the most part, things go well.  The installer actually does load up.
> DHCP at this point fails (haven't sniffed the wire yet to see if it's
> requesting one) but a static IP assignment for this purpose is fine.  It
> does fetch machine packages over http.  However, at some point, it goes
> back to try and pull from the floppy disk, which of course I didn't boot
> off of.  I'm *assuming* that it wants to get the kernel off the boot
> floppy.

FWIW, I've been doing exactely that the last days, successfully; 
versions involved (on the server):

ii  syslinux   1.48-2 Bootloader for Linux/i386 using MS-DOS flopp
ii  dhcp   2.0pl4-2   DHCP server for automatic IP address assignm
ii  tftpd-hpa  0.14-2 HPA's tftp server

the DHCP and tftp server is a potato box; tftpd-hpa is the woody one 
built on potato (because the pxelinux [or was it the PXE bios?] needs
tftp tsize support, IIRC).

bootdisk images are potato/current, i.e. 2.2.26-2001-06-14, idepci/root.bin
and idepci/linux. 

pxelinux.cfg/default:

LABEL debian
KERNEL linux
APPEND load_ramdisk=1 ramdisk_size=16384 root=/dev/ram0 initrd=root.bin  disksize=1.44

DHCP from dbootstrap's "configure the network" step works, and the 
whole installation too; the machine I installed has no floppy drive, 
but at least I've seen no floppy-related error messages.

HTH,

cm.

-- 
** christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
Ich beraube mich doch nicht des Vergnügens zu beobachten, wie sich diese
zarte Knospe der Dummheit weiter entfaltet.
 Markus Pirchner ueber xxx in abm-mi





msg14828/pgp0.pgp
Description: PGP signature

Re: PReP hackers wanted

[christian mock]

[I said:]

> OK, next question: tftpboot.sh tries to gunzip the kernel image and 
> fails. is there any flavor of PPC which needs this, or can we just 
> cat the image like for i386 & other archs?

ignore. test before shooting. bootprep.bin gets built and works fine 
for tftpboot.

cm.

-- 
** christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
Ich beraube mich doch nicht des Vergnügens zu beobachten, wie sich diese
zarte Knospe der Dummheit weiter entfaltet.
 Markus Pirchner ueber xxx in abm-mi





msg14723/pgp0.pgp
Description: PGP signature

Bug#128258: boot-floppies: [powerpc/PReP] modules can't be found

[christian mock]

Package: boot-floppies
Version: N/A; reported 2002-01-08
Severity: important

at the module loading step, no modules can't be found, as dbootstrap
searches in /lib/modules/2.2.19, but the modules are in 
/lib/modules/2.2.19-prep; this is with the latest CVS build.

cm.

-- System Information
Debian Release: 3.0
Architecture: powerpc
Kernel: Linux bauer 2.2.19 #1 Sat Apr 14 22:26:28 CDT 2001 ppc
Locale: LANG=C, LC_CTYPE=C



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

Re: PReP hackers wanted

[christian mock]

> are we sure we need /sbin/macfdisk on the _PReP_ root image? removing it 
> allows the root disk to build (and even leaves 10 kB free!).

OK, next question: tftpboot.sh tries to gunzip the kernel image and 
fails. is there any flavor of PPC which needs this, or can we just 
cat the image like for i386 & other archs?

ciao,

cm.

-- 
** christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
Wahrscheinlich ist die Klage billiger als eine Inseratenkampagne: "Wir
haben das Internet nicht verstanden."
   -- Martin Hlustik ueber Ferrero in Sachen kinder.at





msg14720/pgp0.pgp
Description: PGP signature

Re: PReP hackers wanted

[christian mock]

> On Sun, 2002-01-06 at 14:15, Adam Di Carlo wrote:
> 
> > Well, the only reason I could see is if it either needs a kernel
> > config option enabled, not provided by the kernel-image-*-prep
> > package, or else if it needs a file from the kernel build not normally
> > provided by the package.  It should be pretty easy to read bootprep.sh
> 
> Probably.  But I have basically zero knowledge of the PReP architecture,
> and no way to test the resulting kernel image.  
> 
> So, I'd like to take this opportunity to call for anyone with a working
> knowledge of the PReP architecture, shell script, and preferably C to
> help work on the Debian boot-floppies for PReP.  Right now it doesn't
> even build because the root disk is too large. 

by 1954 bytes, yes.

are we sure we need /sbin/macfdisk on the _PReP_ root image? removing it 
allows the root disk to build (and even leaves 10 kB free!).

well, so far for today, I gotta get me a floppy drive to test this 
tomorrow...

ciao,

cm.

-- 
** christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
Vielleicht ist es aber auch nur einfach Zeit, dem Wolfi wieder den
root-Account wegzunehmen. Er ist noch zu klein dafuer.
 Ferdinand Goldmann in at.gesellschaft.politik





msg14709/pgp0.pgp
Description: PGP signature

Bug#126370: installer issues on "real" terminals

[christian mock]

> Hmm.  I wonder if this was the same problem as #124117, or something else.
> Can you try with boot-floppies 3.0.18 and see if it still happens?


the images from people.debian.org/~aph, I suppose? OK, I'm trying 
those right now. booting from the network, install via network 
(drivers + rescue from people.debian.org/~aph, the rest from 
ftp.at.debian.org).

The problem is still the same -- after installing the base packages, 
dbootstrap (/sbin/udbootstrap) exits and gets restarted; the inittab 
still references tty1...

Let me know if I can test anything more -- how complicated is it to 
build the boot-floppies myself? I've got a potato/woody prep box 
where I could build them...


BTW: the modules from the driver disk are in /lib/modules/
2.2.19-prep, while the "configure modules" step from dbootstrap seems 
to look in /lib/modules/2.2.19.

ciao,

cm.

-- 
** christian mock in vienna, austria -- http://www.tahina.priv.at/~cm/
What other OS provides not one but two INTERCAL compilers as part of
the standard distribution?
 Mark Brown about Debian




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

Bug#126370: installer issues on "real" terminals

[christian mock]

> In message <[EMAIL PROTECTED]>, Adam Di Carlo writes:
> >christian mock <[EMAIL PROTECTED]> writes:
> >> - the installer fails to set the terminal to ttyS0 (instead of tty1) 
> >> in the inittab so /usr/sbin/base-config doesn't work after the first 
> >> reboot in the install process.
> >
> >This bug is rather bad -- the others seem truly minor.  I wonder if
> >this particular issue has been fixed already for 3.0.19?
> 
> Sounds like another occurrence of #122142.

I just tried the install once more, in debug mode. /var/log/syslog 
says "serial console found on line 0", so that seems to work.

after installing the base system (and a brief flashing of "base 
system installed successfully"), dbootstrap exits and gets restarted 
by init. The last log message before that is "running cmd 'cp /etc/
inittab.install /target/etc/inittab'"; from following the program's 
logic, configure_base() apparently gets called and gets to call 
write_fstab(), as the /target/etc/fstab does exist and reflects the 
partitioning. It seems to crash or exit afterwards.

HTH,

cm.


-- 
Hat irgendwer schlechte Schwingungen in seiner globalen
Eierkuchen-Aura bekommen weil man ihm gesagt hat er soll bitte nicht
andauernd mit Vollquotes in 10 Gruppen gleichzeitig crossposten?
 Albert Koellner in at.usenet





msg14280/pgp0.pgp
Description: PGP signature

Bug#126370: installer issues on "real" terminals

[christian mock]

Package: install
Version: 3.0.17-2001-11-18
Severity: minor

Upon installing the testing distribution on a PReP PowerPC machine 
over the serial console (using a TI 924 terminal in VT100 mode), I 
came across the following minor issues:

- "progress bars" (while downloading packages) don't show up on this 
monochrome terminal, probably because they're designed to set the 
background color to red (IIRC from VGA-based installs), which is not 
available on a mono terminal.

- the screen shows a "alt-F4 to debug, alt-F1 to return" message 
which doesn't make sense if we're not on a virtual console.

- the installer fails to set the terminal to ttyS0 (instead of tty1) 
in the inittab so /usr/sbin/base-config doesn't work after the first 
reboot in the install process.

cm.

-- 
>> [1] MSFP nennt das dann "Hooverbutton",
>   ^^ Weils so gut saugt?
Das. Und weil's aussieht wie J. Edgar in Fummel.
  Martin Herrmann, Peter J. Holzer, Felix Deutsch in dasr




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