On Wednesday 16 March 2005 22:51, Matthias Urlichs wrote:
Any idea what the problem is? Should I wait for RC3?
I very much doubt that will fix it. Both RC2 and the current pre RC3
install without problems on the self-compiled Hercules 3.02 I run on my
Toshiba Satellite A40 (Pentium 4) laptop.
On Sunday 24 April 2005 18:39, Frans Pop wrote:
I have built the package for s390, but can not upload myself (still
waiting for DAM approval).
Joey Hess has just done the upload, so it's now complete for all archs.
Cheers,
FJP
pgp7ujbrzUqfp.pgp
Description: PGP signature
On Wednesday 27 July 2005 18:37, Frans Pop wrote:
I think I've managed to create a bootable CD image. It is available
for testing from [1]. Basically, I have revived the code that was
already available in Woody.
The primairy purpose of this image is to test if it boots. I may have
made
On Thursday 13 October 2005 04:24, Patrick Finnegan wrote:
[1] http://people.debian.org/~fjp/d-i/debian-testing-s390-netinst.iso
Now that I'm finally getting around to testing this on my real S/390
G5, the file has disappeared, and I can't find it anywhere. :/
Yes, I deleted it as I dislike
On Saturday 15 October 2005 02:31, Patrick Finnegan wrote:
Frans Pop declared on Thursday 13 October 2005 05:32 am:
As the builds for weekly images for testing has now been resumed, the
option to ipl from CD should now also be available in this image:
http://cdimage.debian.org/pub/weekly
On Tuesday 22 November 2005 17:17, Ivan Warren wrote:
I am trying to upgrade my linux kernel from 2.6.11-1 to 2.6.14-2
LOG
Setting up linux-image-2.6.14-2-s390 (2.6.14-2) ...
Using /usr/sbin/mkinitrd.yaird to build the ramdisk.
Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd
On Tuesday 22 November 2005 19:55, Frans Pop wrote:
If you need to install the 2.6.14 kernel, you will probably have to
look for the relevant check in yaird and comment it out. If not, your
best option is probably just to reinstall the 2.6.11 kernel and remove
the 2.6.14 kernel.
One other
On Tuesday 22 November 2005 21:54, Ivan Warren wrote:
Now.. Also tried using good ole mkinitrd but now this won't boot :
That definitely won't work...
Any clue ?
Well, did you try initramfs-tools? It's command to create the initrd is
'mkinitramfs'.
pgptEtwCIbh5s.pgp
Description: PGP
On Tuesday 22 November 2005 22:35, Ivan Warren wrote:
Hmm.. Should I report a initramfs-tools bugreport ? (now - I see there
is a bunch of bugs outstanding on initramfs, so no doubt this would be
a dup)..
Maybe not. I'm not sure anyone would have taken the plunge for s/390 yet.
Done.
ALERT×
(CC to d-s390 as there may be people who can provide additional
information.)
On Friday 02 December 2005 22:58, you wrote:
can you please retest if that device gets created?
OK. I've done some testing and made some progress.
First, the following modules need to be available in the initrd:
-
Some additional info.
I've done my research from a system (Hercules emulator) running 2.4.27.
For 2.4.27, the dasd modules are built into the kernel. The option to set
the dasd devices is therefore passed from the zipl bootloader.
The dasd= option in the [debian_26] section was of course
On Wednesday 07 December 2005 14:38, [EMAIL PROTECTED] wrote:
I want to know if I can download Debian S/390, burn a CD and do most of
the installation from the CD
on the OS/2 system that supports the HMC? I see from the site that
Support to ipl off an installation CD has been added back in
] 2.6.14-2 does not boot on IA64, waiting for 2.6.15
NOTE
A new 2.4.27 kernel for x86 has just been accepted into unstable so 2.4 kernel
udebs will also need updating soon.
Cheers,
Frans Pop
pgpbqwnLhuLeE.pgp
Description: PGP signature
On Monday 06 February 2006 19:08, Martin Michlmayr wrote:
* Adam Thornton [EMAIL PROTECTED] [2006-02-06 10:09]:
The short answer, though, is that the parted problem seems to be
basically done, pending rolling it in officially, which is Otavio's
I have gotten the patches from Otavio and have
On Tuesday 07 February 2006 00:13, Frans Pop wrote:
Parted seems to work fine again. It recognized my existing partitions
and partitioning in the installer worked fine too.
There are some issues that need to be looked into for the installation
(I managed to finish it with some minor manual
I've made a complete mess of CD images for Beta2 so far as the result of a
wrong assumption. This means, as some installation reports and comments
have shown, that CD images linked from [1] have been broken since last
Friday.
The good news is that there are now good Beta2 netinst and
(already sent to d-boot)
On Tuesday 07 March 2006 13:52, Frans Pop wrote:
I am very happy to announce that the debian-installer images targeted
for Beta2 are now in testing (except AMD64) and that daily (etch_d-i)
netinst and buisinesscard CD images using them are now available from
[1
On Thursday 09 March 2006 19:54, Helge Kreutzmann wrote:
Did you call linuxinfo and the ls as ordinary user? I wonder, because
the size looks ok.
Yes to both.
Do you have moment to spare and can I send you a patch to try? As I
am not a Debian developer, I do not have access to a s390 machine
Thanks Bastian.
On Thursday 16 March 2006 17:29, Bastian Blank wrote:
On Thu, Mar 16, 2006 at 04:13:21PM +0100, Frans Pop wrote:
Only problem was that the network interface did not come up. Trying
to manually start it resulted in:
You need a 2.6.16-rc5 kernel and sysconfig-hardware.
Yes
(This was supposed to be BCC'ed to d-ports...)
-- Forwarded Message --
Subject: [D-I] Post-release notes
Date: Saturday 18 March 2006 03:25
From: Frans Pop [EMAIL PROTECTED]
To: debian-boot@lists.debian.org
As the last action for the Beta 2 release, the links for the daily
On Friday 27 January 2006 14:24, Bastian Blank wrote:
I finaly finished a rudimentary hardware configuration. It have some
similarities with the redhat and suse sysconfig. (This was the simplest
schema I found.)
- A config for ccwgroup contains a CCWGROUP_CHANS array:
On Friday 24 March 2006 15:05, Bastian Blank wrote:
After loading the ctc module, a hwup ccw 0.0.0a00 works fine.
The ctc module is loaded. I have it in /etc/modules.
A manual 'hwup ccw 0.0.0a00' does indeed do the trick.
The problem seems to be that loading the ctc module does not trigger the
, Frans Pop wrote:
In more detail:
1) Upload new i386 kernel udebs for both 2.4 and 2.6 to s-p-u (I've
already prepared a set)
2) Get these acked by SRM so they actually show up in s-p-u; s-p-u
already has debian-installer sections, I'm not sure if the acceptance
queue and approval stuff
(This mail is a combination of installation-report and status overview for
the S/390 list.)
Mostly thanks to the efforts of Bastian Blank, S/390 has now made the
switch from 2.4 to 2.6 in the installer. The installer now also uses
partman instead of partitioner and partconf.
Both network
://ftp.nl.debian.org/debian/dists/sid/main/installer-arch/current/images/
Known issues:
- S/390 Beta 3 candidate images are broken; will be fixed with next upload
- Lowmem settings in Beta 3 images are not yet correct; see below
On Monday 24 July 2006 11:52, Frans Pop wrote:
One important TODO item
(Reply-to set to debian-boot; please only add relevant port if needed.)
Dear (d-i) porters,
First mass upload of kernel udebs
=
Today I have uploaded kernel udeb updates to 2.6.17-9 _for all arches_.
This is the first time using the 'massbuild' [1] script I wrote
On Friday 22 September 2006 16:39, Grant Grundler wrote:
I didn't see anything for parisc (HPPA).
I don't know of any problems with initramfs on parisc.
but I don't expect any surprises from the kernel on that.
Maybe I was not clear enough on this. The original text was:
* type of initrd used
On Thursday 05 October 2006 08:45, Shrirang B Kulkarni1 wrote:
i want to install Debian (With 2.6 kernel) on z/VM guest image. But i
am not able to find kernel.debian, initrd.debian, parmfile.debian.
plz can someone help in same from where i can download same ...
This page:
than English, consider installing in
that language; note that one last round of translation updates is
still planned, but reports of issues are still appreciated
TIA,
Frans Pop
[1]http://d-i.alioth.debian.org/manual/en.i386/ch06s03.html#di-partition
[2]http://d-i.alioth.debian.org/manual
Hello Adam,
On Friday 03 November 2006 20:47, Adam Thornton wrote:
I tried a few days ago to install Etch on an s390 system, and failed
to partition my DASD because kernel modules appropriate to the
installer kernel level weren't found. I presume this is a known
issue that will be resolved
On Friday 10 November 2006 14:16, Shrirang B Kulkarni1 wrote:
No kernel modules were found. This probably is due to a mismatch
between the kernel used by this version of the installer and the
kernel version available in the archive.
See
We are ready to make the switch to 2.6.18 for Debian Installer.
For most architectures the 2.6.18-6 (ABI -3) should now be available in
unstable.
Please update the kernel udebs for your architecture ASAP.
Cheers,
FJP
pgpA6QxMZLWGC.pgp
Description: PGP signature
On Wednesday 27 December 2006 10:48, Bastian Blank wrote:
On Mon, Dec 25, 2006 at 11:40:02PM +0100, Frans Pop wrote:
S/390: add Bastian Blank
S/390: remove Gerhard Tonn, he stepped back
Updated, thanks.
pgpkRKhsEqwzh.pgp
Description: PGP signature
Hello porters,
I've just announced the schedule [1] for the release of the Installation
Guide to be included with the Etch release.
That schedule leaves room for bigger updates until Dec 31 and for minor
ones until Jan 7. This means that if you have any updates you'd like to
get in for your
Hi all,
As you've probably noticed, what's intended to be the final kernel for
Etch has been uploaded yesterday.
I'm currently building and uploading the kernel udebs for all arches
(except arm and m68k for which images are not yet available). I'll also
upload new loop-aes module udebs for
Hello D-I porters,
Most architectures should now be able to switch to 2.6.20 for D-I (except
for arm, hppa and m68k). i386 and amd64 have already been switched.
Over the past two weeks Joey has done the needed work for i386 and amd64
(and necessary updates in kernel-wedge), but we've waited
On Tuesday 22 May 2007 19:10, Adam Thornton wrote:
On May 22, 2007, at 11:21 AM, Rod Clayton wrote:
Error informing the kernel about modifications to partition
/dev/dasda5 -- Invalid argument. This means Linux won't know about
any changes you made to /dev/dasda5 until you reboot -- so you
tags 445148 confirmed
reassign 445148 s390-tools
thanks
Install boot went as expected, up until the first re-boot. After
rebooting, system fails in fsck because one of the partitions is
already mounted.
Configuration is a 125 cylinder /dev/dasda1, which is to be mounted
as /boot, and a
, but not relevant.
I'm convinced there's a real bug here.
Cheers,
Frans Pop
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
-- Forwarded Message --
Subject: Re: Bug#445148: S390: Build w/ /boot partition succeeds, but
re-boot fails in fsck
Date: Monday 08 October 2007
I must say that I'm not sure what the benefits would be of having a
separate /boot partition on s390, but this still seems like a
with other Debian people how we want to resolve this.
Thanks very much for your replies, which did help in straightening this out
for me.
Cheers,
Frans Pop
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
severity 445148 serious
reassign 445148 debian-installer 20070308
thanks
On Monday 08 October 2007, Frans Pop wrote:
This does not seem to be an installation problem. Instead it looks like
either the boot loader or the kernel is not releasing the partition
holding /boot after the kernel
severity 445148 serious
reassign 445148 debian-installer 20070308
thanks
On Monday 08 October 2007, Frans Pop wrote:
This does not seem to be an installation problem. Instead it looks like
either the boot loader or the kernel is not releasing the partition
holding /boot after the kernel
Package: nfs-common
Version: 1:1.1.2-4
The Debian s390 port has a 32-bit userland, but has both a 32-bit (-s390)
and a 64-bit (-s390x) kernel.
If I try to mount an nfs4 file system using the 32-bit kernel all is OK, but
when I do the same with the 64-bit kernel it fails as follows:
# mount
Please do not start two separate threads for basically the same
question/problem in two days!
Shrirang Kulkarni wrote:
Steps
1. chccwdev -e 0.0.b001
2. echo 0x5005076305080310 /sys/bus/ccw/devices/0.0.b001/port_add
3. echo 0x40104001
2.6.26.8).
note that 2.6.25 might be an issue.
Hmmm? The Lenny RC1 image also uses 2.6.26, though based on a somewhat
older upstream stable update. So .25 cannot be an issue here.
PSF/PRSSD issue that's of some concern to me) 2.6.26 version updated by
Frans Pop should be fine.. and 2.6.27
On Thursday 09 July 2009, Frans Pop wrote:
I can confirm this. If I install the Lenny kernel on an already
installed Hercules system (running unstable) I also get the panic, so
it clearly is a kernel issue, not an installer issue.
But it will definitely need to be investigated
Hi,
On Thursday 09 July 2009, Shrirang Kulkarni wrote:
I am trying to install kernel 2.6 version from yesterday none of the
mirrors are working
If you really want help from people on a Debian mailing list, you will
really need to improve the way you ask your question...
1) Do not hijack an
(No need to CC me.)
On Monday 03 August 2009, Peter Senna Tschudin wrote:
How can I check if the kernel supports ext2, ext3 and cramfs? Looks
like it does not...
$ cat /proc/filesystems
But note the the installer will only get some file system modules
available when additional installer
Marco d'Itri wrote:
On Aug 31, Bastian Blank wa...@debian.org wrote:
I doubt that I would be able to push this port through another release
in the current state. The consequence would by that the port dies
completely and with it the only free and released distribution for this
machines.
Is
On 8 Juli 2009, Fernando Gieseler wrote:
Well, I trying install Debian Lenny on System z behavior z/VM.
The first attempt was: I downloaded the essentials files from the
official mirror ftp server
(ftp://ftp.debian.org/debian/dists/lenny/main/installer-s390/current/im
ages/generic/) but, the
First of all, when you ask a question on a mailing list, please always
follow up to that mailing list instead of replying to the person who
replied to you.
On Wednesday 23 September 2009, Martin, Larry D wrote:
I downloaded 5.0.3 from mirrors.usc.edu and that seemed to work fine. I
then
Hi all,
As reported yesterday by Larry Martin, Debian Installer fails to boot
from CD on s390.
I worked on that early in the Etch release cycle [1] and when it was
implemented in debian-cd it worked fine. But if I now try an Etch
image, that fails as well. The problem seems to be that it fails
STEPHEN POWELL wrote:
Hmm. These are the same symptoms as Debian bug report number 523942.
Does that mean that stock kernel image linux-image-2.6.26-2-s390
version 2.6.26-19 will work for me?
Current stable kernels should work fine.
Don't ask me why the version created by
make-kpkg works
Stephen Powell wrote:
I shall be happy to do all of the above. I do have access to a real
mainframe. It's a z/890 (2086). It's not one of the newest machines.
It's not a z9 or z10. But it is 64-bit. And I do have a spare LPAR I
can test with. And yes, I do know how to IPL Linux in an
Mike Kirjanov wrote:
1. We are trying to install Debian for S390 (lenny ) distribution on the
virtual machine (via z/VM 5.4 on the real mainframe ) and via Hercules
3.05 on the Linux Intel box. All our attempts is ended with the WARNING
**: bad d-i Packages file message. We are using local
Martin, Larry D wrote:
Does anyone know if the problem installing Debian on zSeries from CD-ROM
has been corrected?
Yes, it has.
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
(No need to CC me; I read the list; see the Debian mailing list policy.)
Hello Stephen,
A few misconceptions in your mail. Let me try to correct them and offer
some advise on who to proceed.
But first of all: please don't hijack an existing thread for an unrelated
issue; next time, please
On Monday 14 December 2009, Frans Pop wrote:
Stephen Powell wrote:
I *did* ask the kernel team.
Yes, and I gave several reasons that could explain why they may not have
replied.
P.S.
I never meant to imply that anything you did was wrong. I was just trying
to explain why
Stephen Powell wrote:
When I click on reply, the To field is pre-filled-in with the
poster's e-mail address.
So, it's a limitation of *your* email client. The choice of client is up to
you, but forcing its limitations on others is backwards.
I don't think I understand what you are trying to
Martin, Larry D wrote:
The S390 directory appears to me to be empty this week.
Yes, unfortunately there was a build error this week (which sometimes
happens for daily and weekly builds). The images should be back next
Monday.
There was stuff there last week (can I point to that?).
Afraid
Martin, Larry D wrote:
The iso directory for s390 is empty (as far as I can tell) again this
week.
Unfortunately the server that hosts the Debian Installer images for s390
looks to be down today, which means that the server that builds the CD
images could not download them and so the weekly
On Monday 21 December 2009, Frans Pop wrote:
Martin, Larry D wrote:
The iso directory for s390 is empty (as far as I can tell) again this
week.
Unfortunately the server that hosts the Debian Installer images for s390
looks to be down today, which means that the server that builds the CD
Martin, Larry D wrote:
All goes well until the install asks which site I want to use. I chose
ftp.us.debian.org (and a couple of others) and I get ...site either not
available or does not contain a valid release...
The ftp.us.debian.org mirror works perfectly for me (using the same CD).
Stephen Powell wrote:
OK, so if all three drivers support minidisks, then what is Debian
bug report 447755 all about? The issue here is the *format* of the
minidisk. A DASD device, be it a dedicated device or a minidisk,
can have one of four formats under Linux for s390: cdl, ldl, CMS
Stephen Powell wrote:
If I were to boil the problem definition down to one sentence it would
be:
Partman does not recognize the pre-existing partition on disks which
are pre-formatted in the CMS non-reserved format or the CMS reserved
format.
Right. That narrows it down a lot. Partman is
On Thursday 24 December 2009, Frans Pop wrote:
Stephen Powell wrote:
Partman does not recognize the pre-existing partition on disks
which are pre-formatted in the CMS non-reserved format or the CMS
reserved format.
Right. That narrows it down a lot. Partman is almost exclusively shell
On Thursday 24 December 2009, Frans Pop wrote:
To start with:
- What device name does such a partition have?
- How could it be distinguished from a partitionable dasd?
The output of the following command would be useful as well:
# parted /dev/device print
Please send the replies
Package: s390-tools
Version: 1.6.2-1
Severity: wishlist
Tags: patch
The 'optional' option is currently undocumented. Please find attached a
proposed patch.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: s390
Kernel: Linux
Package: s390-tools
Version: 1.6.2-1
Severity: important
$ sudo lstape
/sbin/lstape: 30: Syntax error: ( unexpected
Line 30 contains:
function RequireArgument() {
And 'function' is a bashism. Changing the shebang to /bin/bash fixed the
problem.
Other scripts in the package may well have the
reassign 486946 sysconfig-hardware
tag 486946 moreinfo
thanks
At install time Debian was not showing any FCP which is attached to
Guest image thought let me try to enable same after install of OS.
[...]
Once again I need repeat 1-6 steps for FCP to get enable
Enabling devices during system
From your last comment in this BR it looks as if it can be closed.
Agreed?
If not, the request should really be put to the upstream developers of
s390-tools. You can find contact information at:
http://www.ibm.com/developerworks/linux/linux390/s390-tools.html
Note that there have been several
Bastian,
I've packaged the new upstream version. Most debian/patches could be
refreshed or updated without too many problems. I've also updated the
packaging and fixed some BRs.
I've chosen to leave the following components disabled for now as I'm
unsure how relevant they are for Debian:
-
Given that, what are the guidelines for when to file the initial bug
report directly with upstream vs. when to file a bug report with Debian?
It's mostly a question of what's most effective.
The kernel team is already drowned in bug reports and has very little
manpower to deal with relatively
Frans Pop wrote:
I've packaged the new upstream version. Most debian/patches could be
refreshed or updated without too many problems. I've also updated the
packaging and fixed some BRs.
I found I'd missed updating the files to be installed. I've now updated
that too and made some other
FYI
I've taken over the daily builds of Debian Installer for s390 as lophos has
been down for well over a month now.
If the service on lophos is ever reinstated, or if someone wants to set up
(and manage) the builds on a regular buildd I'll be happy to stop them
again.
The link on the D-I
Stephen Powell wrote:
I finally found the cause of this pesky bug!
At some point, an aptitude full-upgrade seemed to fix this problem.
That was probably at times that sysconfig-hardware was broken... A next
fixed version of that package would have reintroduced your problem.
The problem is
Stephen Powell wrote:
So whenever a dynamically linked device showed up using one of the
device numbers 0400-0403, sysconfig-hardware was convinced it needed
to be brought online immediately! What I don't understand is why,
when it is *manually* varied offline *after* being brought online
I’m looking for someone who could give access to an s390 or ia64
to track down a test failure in git-core.
I can't help you with access to an s390 system, but one option could be for
yourself to use the Hercules s/390 emulator and run your own s390 system.
Hercules is available as a package
István Németh wrote:
How can I setup a buildd environment to join the autobuilder network? I
didn't find any working documentation.
I don't think this is the correct list for that question. I suggest you try
debian-wb-t...@l.d.o (although I'm not 100% that is the correct list
either, but they
I'm not sure this is the right place to request this, can someone give a
try to a rebuild of polyorb ?
Such requests should be sent to arch@buildd.debian.org.
Cheers,
FJP
--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
81 matches
Mail list logo
