[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#427500: marked as done (s390 Etch Install Problems level 2 guest LAN Error)

Your message dated Wed, 08 Sep 2010 03:58:26 +0000
with message-id <E1OtBnm-0005ax-Js@ravel.debian.org>
and subject line Closing old installation report #427500
has caused the Debian Bug report #427500,
regarding s390 Etch Install Problems level 2 guest LAN Error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
427500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427500
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports
Version: Etch
When doing a network install of Etch under VM using
guest LANs for connectivity, the installation appears
to work fine untill re-boot. When the system re-boots
you get the error that level 2 networking is not
supported on VM Guest LAN. You get this message even
though you specify no level 2 networking during the
install. 
The problem is caused by the installer inserting a
line for level 2 networking in the startup file. I
found the following solution mentioned on the debian
system administration web site:

There is a bug in the layer2 config stuff I think. The
way I fixed it on an actual mainframe (not
hercules...so maybe its not the same issue.), was to
simply remove the line containing layer2 from
/etc/sysconfig/scripts/hardware/hwup-ccw-group.
Once this was removed, I didn't get the corresponding
error you see at boot time and the network started
without issue. Until I made this change, I couldn't
see the hsi0 device through an ifconfig -a either. The
network also worked perfectly during the install, but
failed on the subseqent boot. I believe there may be a
place to set this in a config file rather than delete
the line that sets it in setup script, but its
location eludes me at this time. I hope this helps
someone else! I'll try to submit a bug report when I
get the time.

Editing the file mentioned and removing the level 2
line fixed the problem for me.


Rod Clayton
Amateur Radio Call KA3BHY
Columbia, MD 21045

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

--- End Message ---
--- Begin Message --- 
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---
Reply to: