Bug#268792: Unicode (UTF-8) bug still present and failure to download libc6-udeb
On Thu, Oct 28, 2004 at 11:31:29PM +0200, Erik C.J. Laan wrote: Stephen R Marenka wrote: I've tried to document all the magic in http://d-i.alioth.debian.org/manual/en.m68k/index.html. But, I tried finding the string initrd22 in the document from the URL above. In chapter 3.3.1.1 in the document I found reference to a .txt and a .pdf version. The .txt version gave me a 404, so I downloaded the .pdf version. My acrobat reader could not find the string in there. Next I checked all HTML documents, also to no avail. So it looks like the magic is not yet in the manual ;-). May I suggest chapter 4.4 Preparing Rats, you're right! Okay, that's on the TODO. P.S. The installation crashed with an oops, and the second attempt has stalled. Both at trying to write the partition table. Low-mem troubles? Likely. I'll retry at a later time, and update the bugreport accordingly. Thanks, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#268792: Unicode (UTF-8) bug still present and failure to download libc6-udeb
Stephen R Marenka wrote: On Thu, Oct 28, 2004 at 11:31:29PM +0200, Erik C.J. Laan wrote: Stephen R Marenka wrote: I've tried to document all the magic in http://d-i.alioth.debian.org/manual/en.m68k/index.html. But, I tried finding the string initrd22 in the document from the URL above. In chapter 3.3.1.1 in the document I found reference to a .txt and a .pdf version. The .txt version gave me a 404, so I downloaded the .pdf version. My acrobat reader could not find the string in there. Next I checked all HTML documents, also to no avail. So it looks like the magic is not yet in the manual ;-). May I suggest chapter 4.4 Preparing Rats, you're right! Okay, that's on the TODO. No problem. P.S. The installation crashed with an oops, and the second attempt has stalled. Both at trying to write the partition table. Low-mem troubles? Likely. My third attempt is running smoothly uptil now. It is at Installing base packages ... which is 61% into the Installing the Debian base system step. It took just over 6 hours to get here, but it's happily doing it's thing on the disk, occasionaly updating the screen... ;-). I'll report back when it's done or crashes or otherwise. Erik -- -- Erik C.J. Laan elaan at dds.nl Please reply below the message, please cut unrelevant pieces from a reply. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#268792: Unicode (UTF-8) bug still present and failure to download libc6-udeb
Hi, As per Joey's request I've downloaded the daily build of the debian installer initial ramdisk image, and the kernel, and retried the installation. This information is also relevant to bug #238601 as that is my first and mostly successful installation attempt on m68k. So this is a followup on that one. Both reports are of installations with the same machine. So this report provides new information from a newer version of the installer. Because that bug (#238601) is a success-report, and the second attempt had more failures I opened another bug (#268792) to descibe those. Maybe these bugs should be joined/merged? But as I don't know if that should be done, and if so how to acheive that, I'll leave that up to you. Now for the actual report. First of: the Unicode (UTF-8) bug described first in this bug is still present. On top op that I now have problems with the step Downloading installer components. It fails to download libc6-udeb from my own local mirror (apt-proxy using ftp.nl.debian.org and ftp.tiscali.nl), from any Dutch mirror from the mirror's list, and from the primary US mirror ([ht|f]tp.us.debian.org). The installer that wants to drop me into the menu, but the only message I see on screen is fclose: No space left on device. There don't seem to be any other virtual consoles available with additional debug information. Keep up the good work, Erik. -- -- Erik C.J. Laan elaan at dds.nl Please reply below the message, please cut unrelevant pieces from a reply. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#268792: Unicode (UTF-8) bug still present and failure to download libc6-udeb
On Thu, Oct 28, 2004 at 10:50:44AM +0200, Erik C.J. Laan wrote: As per Joey's request I've downloaded the daily build of the debian installer initial ramdisk image, and the kernel, and retried the installation. Exactly which image from which day? Thanks, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#268792: Unicode (UTF-8) bug still present and failure to download libc6-udeb
On Thu, Oct 28, 2004 at 08:25:03PM +0200, Erik C.J. Laan wrote: Stephen R Marenka wrote: On Thu, Oct 28, 2004 at 10:50:44AM +0200, Erik C.J. Laan wrote: As per Joey's request I've downloaded the daily build of the debian installer initial ramdisk image, and the kernel, and retried the installation. Exactly which image from which day? Hi Stephen, I used your image downloaded about 10 hours ago from: http://people.debian.org/~smarenka/d-i/images-m68k/2004-10-27/nativehd/initrd.gz. Please try the initrd22.gz image in the same directory. It is intended for 2.2 kernels, whereas the initrd.gz kernel is intended for 2.4 kernels. I'll check that image on my box too. Thanks, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#268792: Unicode (UTF-8) bug still present and failure to download libc6-udeb
On Thu, Oct 28, 2004 at 09:27:57PM +0200, Erik C.J. Laan wrote: Erik C.J. Laan wrote: Stephen R Marenka wrote: On Thu, Oct 28, 2004 at 08:25:03PM +0200, Erik C.J. Laan wrote: Stephen R Marenka wrote: On Thu, Oct 28, 2004 at 10:50:44AM +0200, Erik C.J. Laan wrote: As per Joey's request I've downloaded the daily build of the debian installer initial ramdisk image, and the kernel, and retried the installation. Exactly which image from which day? Hi Stephen, I used your image downloaded about 10 hours ago from: http://people.debian.org/~smarenka/d-i/images-m68k/2004-10-27/nativehd/initrd.gz. Please try the initrd22.gz image in the same directory. It is intended for 2.2 kernels, whereas the initrd.gz kernel is intended for 2.4 kernels. I'll check that image on my box too. OK, will do. I was already wondering that the -22 was about. Hi Stephen, Magic hint that. The Unicode trouble is gone, and it has just gotten past retreiving libc6-udeb en unpacking libc6-udeb successfully. I'll update the installation report after the installation has finished completely (probably tomorrow morning Central European Time). Excellent! I've tried to document all the magic in http://d-i.alioth.debian.org/manual/en.m68k/index.html. Please feel free to give it a read and give me some feedback. Thanks for testing, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#268792: Unicode (UTF-8) bug still present and failure to download libc6-udeb
Stephen R Marenka wrote: On Thu, Oct 28, 2004 at 09:27:57PM +0200, Erik C.J. Laan wrote: Erik C.J. Laan wrote: Stephen R Marenka wrote: Please try the initrd22.gz image in the same directory. It is intended for 2.2 kernels, whereas the initrd.gz kernel is intended for 2.4 kernels. I'll check that image on my box too. OK, will do. I was already wondering that the -22 was about. Hi Stephen, Magic hint that. The Unicode trouble is gone, and it has just gotten past retreiving libc6-udeb en unpacking libc6-udeb successfully. I'll update the installation report after the installation has finished completely (probably tomorrow morning Central European Time). I've tried to document all the magic in http://d-i.alioth.debian.org/manual/en.m68k/index.html. I was still using the installation howto I printed on March 3rd when I first tested d-i after you're call for testers on the debian-68k maillist. With the handwritten addition that a 13000 bytes ramdisk was enough. I picked up that knowledge from another message from you to [EMAIL PROTECTED], but I don't know when exactly. I'm not on debian-boot. So that's why I didn't know about initrd22.gz. Please feel free to give it a read and give me some feedback. Maybe I'll do, but I still have quite some documents printed ready to review (for my work and other hobbies). But, I tried finding the string initrd22 in the document from the URL above. In chapter 3.3.1.1 in the document I found reference to a .txt and a .pdf version. The .txt version gave me a 404, so I downloaded the .pdf version. My acrobat reader could not find the string in there. Next I checked all HTML documents, also to no avail. So it looks like the magic is not yet in the manual ;-). May I suggest chapter 4.4 Preparing Files for Hard Disk Booting for this information? That's where I looked first. Also, it is still kinda small overall. Back to the installation: The first installation attempt with initrd22.gz crashed with an oops. Probably because I did swapon /dev/sdd4 before the partitioning. I subsequently wanted /dev/sdd4 used for swap, but could not get the partitioner to not touch /dev/sdd4 (probably my own fault), so I had to swapoff /dev/sdd4. This took quite some time, and maybe later resulted in the oops? The second attempt has stalled at the same point: trying to write the partition table. Low-mem troubles? The 4 messages on VC3 are: Log file trincated to save memory. # Twice Segmentation fault # Twice And the last few lines on VC4 are: timestamp main-menu[505]: DEBUG: Menu item 'partman' selected timestamp main-menu[505]: DEBUG: configure partman, status: 2 timestamp main-menu[505]: DEBUG: configure libc6, status: 0 timestamp main-menu[505]: DEBUG: virtual package libc6 timestamp main-menu[505]: DEBUG: configure libparted1.6-0, status: 0 timestamp main-menu[505]: DEBUG: virtual package libparted1.6-0 timestamp main-menu[505]: DEBUG: configure harddrive-detection, status: 0 timestamp main-menu[505]: DEBUG: virtual package harddrive-detection timestamp+17 minutes partman: userdevfs: update-dev # I think those 17 minutes where the time I took to do the partman-magic of selecting the root-filesystem, marking it to become ext2, to be mounted on / and yes: format it. timestamp+1h13m init: ^MStarting pid 478, console /dev/vc/2: '/bin/sh' # That was when I wanted to check the debugging and cat /proc/meminfo which gives (layout changed for readability): total Mem: 23207936 Swap: 0 used Mem: 22962176 Swap: 0 free: Mem: 245760 Swap: 0 shared Mem:741376 buffers Mem: 13115392 cached Mem:577536 MemTotal: 22664 kB MemFree: 240 kB MemShared: 724 kB Buffers: 12808 kB Cached: 564 kB SwapTotal: 0 kB SwapFree: 0 kB Thanks for all the good work and HTH, Erik. -- -- Erik C.J. Laan elaan at dds.nl Please reply below the message, please cut unrelevant pieces from a reply. -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
