Bug#224758: rootskel: kernel panic when trying to unmount initrd
Thiemo Seufer wrote: Joe Nahmias wrote: This can be fixed by removing the 'umount initrd' line ... which was added to fix another bug. Of course :) Current CVS has umount initrd || true, this should fix the problem (modulo the error message). Fair enough! Thiemo Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#224758: rootskel: kernel panic when trying to unmount initrd
Package: rootskel Version: 0.56 Severity: critical Tags: patch Justification: breaks the whole system Hello, I'm testing the daily netboot images built by sjogren and I get the following kernel panic when /sbin/init is run: Setting up filesystem, please wait ... umount: Cannot open /proc/mounts umount: initrd: Invalid argument Kernel panic: Attempted to kill init! This can be fixed by removing the 'umount initrd' line at the top of the /sbin/init script, as done in the attached patch. This allows me to boot into main-menu and to proceed through the installation until I hit the debootstrap bug of the day... :) Thanks, Joe -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux laptop 2.4.22-1-686 #6 Sat Oct 4 14:09:08 EST 2003 i686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 --- src/sbin/init.orig 2003-12-14 17:30:08.0 -0500 +++ src/sbin/init 2003-12-21 16:24:21.0 -0500 @@ -1,7 +1,6 @@ #!/bin/sh -e # Set up filesystem as root and pivot into it. echo Setting up filesystem, please wait ... -umount initrd mount -t proc proc proc if grep -q tmpfs /proc/filesystems; then mount -t tmpfs -o size=100M tmpfs mnt
Re: Bug#220518: installation-reports: routing broken with netboot via PXE install
Glenn McGrath wrote: On Wed, 12 Nov 2003 22:27:43 -0500 Joe Nahmias [EMAIL PROTECTED] wrote: Anyone seen this before or have any clue what the problem could be?? There was a bug with busybox relating to round-robin dns http://busybox.net/lists/busybox/2003-October/009579.html The bug has been fixed in busybox cvs but it hasnt made it into debian-installer yet. The problem is more basic than that, I can't talk to hosts on my local LAN even when using their IP address (no DNS!). If it is this bug you could try using a server that doesnt use round robin DNS, i dont know which ones that is though. In any case, I tried this using archive.progeny.com and the same result -- Host name lookup failure, again this is probably because it can't route packets to the DNS server to resolve the hostname -- not because of any DNS failure. Thanks, Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
All problems resolved
Hello, It seems all the problems I reported in this bugreport have been fixed in today's (2003-11-12) netboot image. Thanks to everyone who helped! Joe PS - Expect a new install report sometime soon with all the new ones :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220518: installation-reports: routing broken with netboot via PXE install
Package: installation-reports Severity: normal Tags: d-i INSTALL REPORT Debian-installer-version: netboot image from daily build on 2003-11-12 uname -a: Linux (none) 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686 unknown Date: 2003-11-12 9:30p Method: netboot via PXE Machine: Dell Inspiron 1100 laptop Processor: Intel Celeron 2GHz Memory: 256MB Root Device: n/a Root Size/partition table: n/a Output of lspci: n/a Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [?] Detect CD: [ ] Load installer modules: [E] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Installer boots correctly. It detects the builtin NIC and loads the right module for it (b44). However anna dies after choosing the mirror with the error message: anna: wget: ftp.us.debian.org: Host name lookup failure It seems that the network is not configured 100%...because even when using the ip address, this fails with the error No route to host. However, when I run `route -n` in vc2, it prints the correct info: ~ # route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.1.0 * 255.255.255.0 U 0 00 eth0 default 192.168.1.1 0.0.0.0 UG0 00 eth0 I have also double-check the interface, and it is properly configured: ~ # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:0D:56:35:B7:17 inet addr:192.168.1.158 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:64 errors:0 dropped:0 overruns:0 frame:0 TX packets:92 errors:0 dropped:0 overruns:0 carrier:2 collisions:0 txqueuelen:100 RX bytes:4381 (4.2 KiB) TX bytes:6982 (6.8 KiB) Interrupt:11 Additionally, this machine also has Windows XP installed on it and the network functions properly in that OS... :( Anyone seen this before or have any clue what the problem could be?? -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux laptop 2.4.22-1-686 #6 Sat Oct 4 14:09:08 EST 2003 i686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
[ I don't know why, but for some reason installation-reports go to ] [ debian-testing, so I'm forwarding this to debian-boot for discussion ] Package: installation-reports Version: netboot daily image from 2003-11-10 Severity: normal Tags: d-i INSTALL REPORT Debian-installer-version: daily netboot image from http://people.debian.org/~sjogren/d-i/images/2003-11-10/ uname -a: Linux (none) 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686 unknown Date: Tue Nov 11 01:03:47 EST 2003 Method: netboot via PXE Machine: Dell Inspiron 1100 laptop Processor: Intel Celeron 2GHz Memory: 256MB Root Device: N/A Root Size/partition table: N/A Output of lspci: /bin/sh: lspci: not found Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [E] Config network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Alright, here are the highlights of how this install went: 0) OK, after much struggling (and dealing with my nemesis error message 'VFS: Cannot open root device or 3a:04') I managed to get the d-i netboot image to work via PXE. For posterity (and the installation guide) the magic kernel options I needed to make this work are ramdisk_size=8192 root=/dev/ram0. If anyone would like assistance setting up a PXE testbed or copies of various configs I use please don't hesitate to ask. 1) Install boots into the main menu. Interface looks alot snazzier than the old text interface, however the line-drawing characters are all messed up on my terminal (corners are displayed as '', c.) Known bug? 2) Picking Choose language doesn't get very far. This is what I can piece together from syslog: DEBUG: Menu item 'languagechooser' selected DEBUG: configure languagechooser, status: 4 WARNING **: Configuring 'languagechooser' failed with error code 1 WARNING **: Menu item 'languagechooser' failed. Any ideas? Known unfiled bug? File a new bug against languagechooser? 3) After doing 'Select a Keyboard Layout', I chose 'Detect network hardware'. This generated the following two (fatal looking) errors: a. An error occured while running 'modprobe -v floppy false`. b. An error occured while running 'modprobe -v ide-cd false`. Since this is a netboot install, these errors should not be fatal. 4) When finally presented with a list of ethernet drivers to pick from, the requisite driver for this laptop -- b44 -- is missing. I tried switching to vc2 and doing 'modprobe -v b44', but this fails since the module doesn't exist on the image. How do we get it added? Well, that's as far as I got. Hope this helps! Joe PS - This particular laptop doesn't have a serial port, so all output/error messages are hand-typed and subject to typos, c. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux laptop 2.4.22-1-686 #6 Sat Oct 4 14:09:08 EST 2003 i686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#220180: cdrom-detect: Debconf templates polishing
OK, here are my edits:
Template: cdrom-detect/manual_config
+_Description: Manually select the CD-ROM module and device?
^^^ use 'a' instead of 'the'.
+ No common CD-ROM reader was detected.
+ .
+ Your CD-ROM reader may be an old Mitsumi or another non-IDE, non-SCSI
+ CD-ROM reader. In that case you may choose which module to load and
^^^ should
+ which device to use. If you don't know what module and device are
^ the which
+ needed, look for some documentation or try a network installation
^
(insert) performing
+ instead of a CD-ROM installation.
Template: cdrom-detect/is_cd_inserted
+_Description: Perform manual CD-ROM configuration?
+ Your installation CD-ROM couldn't be mounted.
+ .
+ That probably means that the CD-ROM is not yet inserted. If that's the case,
This ^^ has^ (insert) been ^^ is
+ just insert it and don't perform the manual configuration. The CD-ROM mount
+ will be re-tried.
+ .
+ If your CD-ROM was already in the drive, some other problem happened. You
^^^ is occured
+ should then try the manual CD-ROM configuration.
(delete)
Template: cdrom-detect/cdrom_module
+_Description: Module needed for accessing the CD-ROM:
+ The automatic detection didn't find any CD-ROM reader. You can try to
^^^ a ^^ drive
+ load a specific module if you have a specific CD-ROM reader (that is
unusual^^ drive
neither IDE nor SCSI).
Template: cdrom-detect/cdrom_device
+_Description: Device file for accessing the CD-ROM:
+ In order to get access to your CD-ROM reader, please enter which device file
^^^(delete)^^ the device file that ^
+ should be used. Non-standard CD-ROM readers use non-standard device
+ files (such as /dev/mcdx).
.
You may switch to the shell on the second terminal (ALT+F2) to check the
+ available devices in /dev with ls /dev. You can come back to this screen
^ return
+ with ALT+F1.
by pressing
Template: cdrom-detect/success
+_Description: CD-ROM detected
+ The CD-ROM autodetection was successful. A CD-ROM reader has been found. It
+ currently contains this CD: ${cdname}. The installation process may continue.
The CD-ROM autodetection was successful. A CD-ROM drive has been found
and it currently contains the CD '${cdname}'. The installation will now
continue.
Template: cdrom-detect/no-cd
+_Description: No CD detected
+ Please check that a CD has been inserted in the CD-ROM reader.
^^ into ^^ drive
Template: cdrom-detect/wrong-cd
+_Description: Non-Debian CD-ROM detected
+ A CDROM has been detected, but it isn't a Debian CD.
The CD-ROM drive contains a non-debian CD.
+ .
Please make sure that the correct CD is inserted.
Please insert a Debian CD to continue with the installation.
Template: cdrom-detect/skip_autodetection
+_Description: Skip CD-ROM automatic detection?
+ You should skip the CD-ROM automatic detection only if it is causing trouble.
If the CD-ROM automatic detection causes trouble, you may skip this step.
+ If you skip it, a manual intervention will be required to mount the
However, you will need to manually mount the
+ CD-ROM on /cdrom before you can proceed.
Template: mirror/distribution
+_Description: Distribution branch to install:
Debian distribution to install:
+ Please select which of the Debian distribution branches you want to install:
(delete) (delete) wish
.
+ - woody is the current stable release of Debian;
+ - sarge is the testing unreleased version of Debian;
+ - sid is unstable and will never be released.
These descriptions will need to be re-written for the release of sarge,
no? Also, shouldn't sarge be the first on the list? The list doesn't
have to (shouldn't) be in chronological order. How about this:
- sarge is the current stable distribution of Debian (3.X)
- sid is the unstable distribution and will never be released
- woody is the previous stable distribution of Debian (3.0)
Hope this helps!
Joe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
Colin Watson wrote: On Tue, Nov 11, 2003 at 11:15:01AM +0100, Gaudenz Steinlin wrote: Am Die, den 11.11.2003 schrieb Joe Nahmias um 09:16: [ I don't know why, but for some reason installation-reports go to ] [ debian-testing, so I'm forwarding this to debian-boot for discussion ] probably someone should reassign the pseudo-package installation-reports to debian-boot. If this is the general opinion of d-i folks, then ftpmaster are the people to ask. (I thought sending it to -testing was originally deliberate, though.) If installation-reports just contains feedback about d-i, I can't see why that should go to -testing and not -boot. Additionally, both the install and installation pseudo-packages point to -boot, why not this one? Do I just file a bug against ftp.debian.org? Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#220163: installation-reports: netboot install attempt via PXE (fwd)
Gaudenz Steinlin wrote: Am Die, den 11.11.2003 schrieb Joe Nahmias um 09:16: Alright, here are the highlights of how this install went: 0) OK, after much struggling (and dealing with my nemesis error message 'VFS: Cannot open root device or 3a:04') I managed to get the d-i netboot image to work via PXE. For posterity (and the installation guide) the magic kernel options I needed to make this work are ramdisk_size=8192 root=/dev/ram0. If anyone would like assistance setting up a PXE testbed or copies of various configs I use please don't hesitate to ask. It would be nice, if you could write a short addition to the INSTALLATION-HOWTO about your way to install d-i via PXE boot. There is already a very short section on netbooting the installer. If you send a patch to debian-boot, I will look at it and commit it to CVS. This was already requested (hi tbm!) and sent to the BTS and the debian-testing list (where the request originated). I titled the message How to create a PXE d-i netboot testbed in 10 easy steps (MSG-ID: [EMAIL PROTECTED]). Please look at it in one of these places. 1) Install boots into the main menu. Interface looks alot snazzier than the old text interface, however the line-drawing characters are all messed up on my terminal (corners are displayed as '', c.) Known bug? not know bug, please file one. Sorry I don't know which package to blame for that. Any takers on where I should file the bug? slang? btw the installation should not boot into main-menu but directly go into languagechooser. That probably happened b/c of the next problem :) 2) Picking Choose language doesn't get very far. This is what I can piece together from syslog: DEBUG: Menu item 'languagechooser' selected DEBUG: configure languagechooser, status: 4 WARNING **: Configuring 'languagechooser' failed with error code 1 WARNING **: Menu item 'languagechooser' failed. Any ideas? Known unfiled bug? File a new bug against languagechooser? bug not know. You should have languagechooser 1.03 on your image, which is the same as on the beta1 which works for most people. Please file a bug. Yes, the image contains version 1.03. I will file a bug. 3) After doing 'Select a Keyboard Layout', I chose 'Detect network hardware'. This generated the following two (fatal looking) errors: a. An error occured while running 'modprobe -v floppy false`. b. An error occured while running 'modprobe -v ide-cd false`. Since this is a netboot install, these errors should not be fatal. please file a bug on hw-detect (or ethdetect?). It's strange that these are tried for network hardware detection. Probably the installer tries to load additional modules from a floppy? I really don't know why it's happening. I will file a bug on hw-detect. 4) When finally presented with a list of ethernet drivers to pick from, the requisite driver for this laptop -- b44 -- is missing. I tried switching to vc2 and doing 'modprobe -v b44', but this fails since the module doesn't exist on the image. How do we get it added? known bug. As of linux-kernel-di 0.12 this driver is in nic-extra-modules. This means you have to load it from an additional floppy. If this is a common NIC then we could add it to nic-modules, which is on the netboot initrd. I believe it is a common NIC and it is used on all of the newer Dell Laptops. For the netboot images, why don't we include nic-extra-modules?? Wouldn't this make sense to do since we know that a network install is being attempted? It's not like we're trying to cram stuff onto a floppy here, so why not put all the network modules we have into this image? PS - This particular laptop doesn't have a serial port, so all output/error messages are hand-typed and subject to typos, c. You could try to save /var/log/messages and /var/log/syslog to an already formatted partition. Unfortunately, I don't have a partition available that I can write to from linux, and fdisk isn't available yet to create one. Thanks for the help! Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#199955: lilo-installer: typo in templates file breaks install to partition
Package: lilo-installer
Version: 0.0.15 (not installed)
Severity: important
Tags: patch
Hello,
There is a typo in debian/lilo-installer.templates that makes any
attempt to install LILO to a partition (ie. not the MBR) fail. Patch
below fixes this.
Thanks,
Joe Nahmias
--- lilo-installer-0.0.15/debian/lilo-installer.templates.orig 2003-06-02
03:57:30.0 -0400
+++ lilo-installer-0.0.15/debian/lilo-installer.templates 2003-07-03
21:07:25.0 -0400
@@ -11,7 +11,7 @@
LILO is configured to use serial port ${PORT} as the console.
The serial port speed is set to ${SPEED}.
-Template: lilo-installer/activate_part
+Template: lilo-installer/activate-part
Type: select
Choices: yes, no
Default: yes
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux a750.nahmias.net 2.4.20 #1 Thu Jan 9 11:22:09 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2003-06-02 Install failure report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Tillman wrote: On Tue, Jun 03, 2003 at 09:04:10AM -0400, Joe Nahmias wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Sj?gren wrote: tis 2003-06-03 klockan 06.44 skrev Joe Nahmias: 3) Finally, we have (yet another) segfault during base-installer. This one also occurs during the debootstrap run. It is caused by the get() function, called by download_release(), not being passed the correct args. snip Actually, using http://people.debian.org/~tfheen/d-i/images/2003-06-02/archive/netboot-initrd.gz I cannot reproduce this. base-installer and debootstrap run just fine... Hmm, I am able to reproduce this (just tried now) -- exactly the same problem. The md5sum for the netboot-initrd.gz i'm using is: 3c2cdebc05b03ecfe45bac93f71e81a6, which should match yours. Very peculiar...Can anyone else confirm/deny? In any case, looks like we just got a new version of busybox-cvs. I will try to test tonight's image and report back. This sounds like an intermittent problem with debootstrap that kept popping up on boot-floppies. It must be some hardware uniqueness or some timing problem, and I'm sure glad you're on the case and can repeat it ... we always had it happen to users who weren't up to running the bug down. Thanks for the (implied) compliment! Well, consider this problem intermittent no longer, the new busybox-cvs didn't help a bit... :-( I am able to reproduce this both with the original images I tried (2003-06-02), and with today's (2003-06-04). Any ideas on how to proceed? Do we need a gdb-udeb? Also, should I file a bug? If so, against which package? busybox-cvs? Joe Nahmias -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+3qd7Kl23+OYWEqURAhNSAJ9amZbzE5g3F1GJR+l1+KbSBg3EBQCbB1oM 5P5IrfjtO5YGsbYfXPOG0jk= =K1+V -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2003-06-02 Install failure report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Sjögren wrote: tis 2003-06-03 klockan 06.44 skrev Joe Nahmias: 3) Finally, we have (yet another) segfault during base-installer. This one also occurs during the debootstrap run. It is caused by the get() function, called by download_release(), not being passed the correct args. snip Actually, using http://people.debian.org/~tfheen/d-i/images/2003-06-02/archive/netboot-initrd.gz I cannot reproduce this. base-installer and debootstrap run just fine... Hmm, I am able to reproduce this (just tried now) -- exactly the same problem. The md5sum for the netboot-initrd.gz i'm using is: 3c2cdebc05b03ecfe45bac93f71e81a6, which should match yours. Very peculiar...Can anyone else confirm/deny? In any case, looks like we just got a new version of busybox-cvs. I will try to test tonight's image and report back. Joe -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+3JzCKl23+OYWEqURAjGNAJ9VkuE0AsIALfqd7c/R/ZlLdyD7ygCgjnoS N+z4kCMmKxOYC8Vesao18rc= =3LFr -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
2003-06-02 Install failure report
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
It's time once more for another edition of Joe's d-i installation
failure report. As usual, this install was performed via PXE using
Tollef's netboot image from today (2003-06-02). Here are today's
issues:
0) First of all, at startup/boot we have multiple error messages:
[...]
Cannot open template file /var/lib/cdebconf/templates.dat
info: Trying to enable linux framebuffer.
modprobe: Can't locate module vesafb
modprobe: Can't locate module vga16fb
Debian Installer Main Menu
[...]
The framebuffer used to load/work properly at some point not too long
ago (ie. less than a month ago)...Did the kernel in the image change and
now doesn't include the necessary modules?
1) Next, when running netcfg-dhcp we have lots of extraneous
prompts/messages that don't need to be there. This includes asking for
the hostname, asking for a confirmation, and then another gratuitous
prompt saying I will now configure the network.
I don't think any of these prompts are necessary...perhaps we should try
to configure the network, and then -- only if it fails -- show the
prompts. What do others think of this suggestion?
2) When hw-detect-full runs, it still tries to use the eepro100 module
instead of e100. I presume this will be fixed when the transition to
discover2 has been completed.
3) Finally, we have (yet another) segfault during base-installer. This
one also occurs during the debootstrap run. It is caused by the get()
function, called by download_release(), not being passed the correct
args. Specifically, if we look at lines 367-8 of
/usr/lib/debootstrap/functions, we have the following:
367:local debdest=$TARGET/$($DLDEST deb $details)
368:if get $m/${details##* } $debdest $md5 $size; then
When I run debootstrap with -x, I see that debdest is getting set
correctly:
+ local debdest=/target/var/cache/apt/archives/adduser_3.50_all.deb
But, the value mysteriously disappears from the call to get():
+ get http://ftp.us.debian.org/debian/pool/main/a/adduser/adduser_3.50_all.deb
ba9224fe6c2f9ba88eecca3848005889 77474
There isn't even an extra space, which would be there if debdest were
simply empty/null. The ommiting of the destination for the package
causes all kinds of problems that eventually result in a segfault. How
and why this happens is a complete mystery to me...
Anyone have any ideas? Should I file a bug against busybox-cvs? I have
the complete trace from debootstrap (with -x) if anyone is interested...
Well, that concludes another edition of Joe's d-i installation reports.
Be sure to tune in next week for more -- same bat time, same bat
channel.
Joe Nahmias, DD wannabe
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+3CeuKl23+OYWEqURAkTaAJ4vLHlcvfIMFXi2TmogYDWji8gM9QCeJI3A
bbyrEtzHPTHL8HVEMdzQhMY=
=zcuu
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#186443: base-installer: can't find /target/etc/fstab
Thorsten Sauter wrote: On Thu, Mar 27, 2003 at 12:29:11AM -0500, Joe Nahmias wrote: Package: base-installer Version: N/A; reported 2003-03-26 Severity: grave Justification: renders package uninstallable I was testing Tollef's daily build of the net-inst images from today, 2003/03/26, and after hacking around the missing mkswap, you need to download the busybox-cvs-udeb package manually. This package contains the mkswap command. Ok, this worked. I ran into this error in base-installer's postinst: cp: /target/etc/fstab: No such file or directory yes, please. Please check, if the fstab generation file exists: /usr/lib/prebaseconfig.d/40fstab If it's exist try to run it from hand on console 2 (tty2) and check teh output, maybe this program failes with some errors. I was able to run this successfully ($?=0) from tty2, with no error messages. It created the correct /target/etc/fstab. How can I diagnose why this didn't get automatically done? Did you have mounted something under /etc? no. Sorry for the questions, but I don't know the contents and the start of the autobuilded images. no problem. I get them from Toleff's site http://people.debian.org/~tfheen/d-i/images/daily/. In this case you would want to check the 2003-03-26 directory instead of daily. Let me know what the next step is. I can reproduce this ad nauseum... Thanks for your help! Joe Nahmias, DD wannabe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#186443: base-installer: can't find /target/etc/fstab
Thorsten Sauter wrote:
On Thu, Mar 27, 2003 at 07:15:21PM -0500, Joe Nahmias wrote:
Thorsten Sauter wrote:
you need to download the busybox-cvs-udeb package manually. This package
contains the mkswap command.
Ok, this worked.
this is fixed in cvs already. So please wait for the next upload of
di-utils.
sounds good.
So, please take a look at
/usr/share/debian-installer/mount/mount.sh
this script should run the fstab script at the following position.
#
# create now the filesystems
do_mount() {
[...]
# update fstab for baseinstaller
sh /usr/lib/prebaseconfig.d/40fstab
return 0
}
maybe you can put a set -x before the 40fstab file?
I see the file; unfortunately, I cannot edit it since nano is broken
since it cannot find libslang.so.1-UTF8
Oh, and btw it works for me here.
naturally... ;-)
Also, after running .../40fstab manually, when I try to continue the
installation, wget segfaults when trying to retrieve
http://ftp.us.debian.org/debian/dists/sarge/main/binary-i386/Packages.gz.
Any ideas?
Thanks for your help!
Joe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#186443: base-installer: can't find /target/etc/fstab
Matt Kraai wrote: Run sh -x /usr/lib/prebaseconfig.d/40fstab Okay... No suprise, it worked. It also worked previously when I ran it manually without the '-x'. Are you interested in anything in particular from the output? In any case, my problem seems to be that /target/etc/fstab wasn't being created, which means that this (.../40fstab) wasn't being run by mount.sh (since I verified that it does the right thing when run manually)... I tried running /usr/share/debian-installer/mount/mount.sh with the -x option, but there was too much output, and I'm not quite sure what I should be looking for... Joe Nahmias, DD wannabe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#186443: base-installer: can't find /target/etc/fstab
Package: base-installer Version: N/A; reported 2003-03-26 Severity: grave Justification: renders package uninstallable I was testing Tollef's daily build of the net-inst images from today, 2003/03/26, and after hacking around the missing mkswap, I ran into this error in base-installer's postinst: cp: /target/etc/fstab: No such file or directory This causes the postinst to fail, and sends the install into a loop. Note: I was able to successfully partition my disk, create all filesystems (except swap), and mount the partitions. It just seems this data was never recorded in the proper file. If you need more details on my test system or installation method, let me know and I will supply them. Joe Nahmias, DD wannabe -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux a750.nahmias.net 2.4.20 #1 Thu Jan 9 11:22:09 EST 2003 i686 Locale: LANG=C, LC_CTYPE=C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Top level README has wrong URL
Hello! I just checked out d-i from cvs, and started reading the docs. The top level readme has an incorrect URL for tfheen's autobuilt images. Following is a patch to fix this. Enjoy, Joe Nahmias, DD wannabe --- debian-installer/README.orig2003-03-14 20:45:50.0 -0500 +++ debian-installer/README 2003-03-20 12:49:02.0 -0500 @@ -35,6 +35,6 @@ Every day, tfheen is autobuilding debian-installer images from whatever is in the archive. The daily builds will end up at - http://people.debian.org/~tfheen/debian-installer/images/daily, and + http://people.debian.org/~tfheen/d-i/images/daily, and the build logs from the last build will be at - http://people.debian.org/~tfheen/debian-installer/$date/. + http://people.debian.org/~tfheen/d-i/$date/. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Image file too large for low memory
Owen, Would you mind posting the relevant parts of your working dhcp.conf Thanks! Joe Nahmias I figured it out. The example dhcp.conf from the install manual for using PXE is apparently wrong. I used the conf they suggest for non-PXE and just specified pxelinux.0 as the filename. Worked like a charm. Thanks for the help everyone! /Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem installing Potato: can't find HD
Hello, I am having trouble installing Debian 2.2 on my PC. I have a 3CD i386 binary set, which when I boot from the first CD -- doesn't see my hard-drive and thinks I'm doing a diskless install. Current config: Abit KA7-100 Motherboard AMD Athlon 750 256MB PC133 RAM Seagate ST320420A (20GB) HD on Highpoint HPT370 UDMA100 Controller Plextor PX-W8432T CD-RW WinFast GeForce 256 DDR AGP video card Netgear FA310TX 10/100 PCI ethernet card Soundblaster PCI 128 Askey 28.8 (V.34) ISA Modem That's probably more information than necessary, but what the hey! I have a feeling that the stock kernel doesn't have support for the Highpoint controller since it's kind of on the new side... but let me know if this is the problem and what the workaround is. Thanks in advance for your help! Joe Nahmias PS - If you have any pointers or suggestions to get the rest of my hardware up and running under linux, it would be appreciated! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
