On Fri, Feb 06, 2004 at 01:17:20AM -0500, Alex deVries wrote:1. Problem installing
When I went through the Debian installer, I got to a step labelled something like 'Install Kernel and Modules', which didn't. The installer segfaulted, and there was no kernel at all in /target/boot. The only way I could proceed was to manually locate the kernel .deb, transfer it and install that, and then rerun the installer, carefully skipping that step. Is this a known problem, or is it worth my time to reproduce?
I've never seen this happen, but it's possible there is a bug. The installer is being completely rewritten for the next release, though, so I can't say whether this bug would be fixed, especially if it's not reproducible.
Okay, when I have some extra time (ha!) I'll run through it again to make sure I can reproduce it. Maybe this isn't worth fixing, although it sounds like the new installer could use some testing.
2. My apt sources
Whenever I do anything with apt-get, I get a stream of complains that look like: W: Couldn't stat source package list http://security.debian.org stable/main Packages (/var/lib/apt/lists/security.debian.org_dists_stable_main_binary-s390_Packages) - stat (2 No such file or directory)
I get one for stable/main, stable/contrib, stable/non-free, and then the whole listing again. What should be in my /etc/apt/sources.list file?
You probably also get a message saying to run apt-get update, which is the solution to that problem. Those messages mean that you have certain sources specified in /etc/apt/sources.list, but haven't downloaded the lists of packages available from those sources (which is what apt-get update does).
So I ran 'apt-get update', and that too gave me the same stream of errors. What's next?
3. fdasd didn't work
fdasd didn't work out of the box because it was an old version. I have built a s390-tools_1.2.4-1_s390.deb package, how do I get it out there?
I'm not sure I understand the question. If you're asking how to install a .deb, you should use "dpkg --install".
Did you build this package from source, or did you download it from testing or unstable? In the latter case, it is unlikely to install on woody, and needs to be recompiled.
Let me rephrase:
I couldn't find an s390-tools_1.2.4-1_s390.deb package out there anywhere, so I created and built my own. I'm sure there are other people who have had this problem too. Would anyone like this package?
4. Getting hipersockets working in the installer
There's some mention of setting up a second ramdisk with the OCO drivers, but I never actually found the script to create such a disk. Given that there are now open source drivers for this, is there a replacement installer kernel, and where're the build instructions for the install kernel?
I believe the instructions for the ramdisk are in the redbook. Information about replacing the installer kernel is here:
http://www.debian.org/releases/stable/s390/ch-boot-floppy-techinfo.en.html#s-rescue-replace-kernel
Okay, I'll give it a shot!
Thanks.
- A
-- Alex deVries Principal Architect, One Fish Two
