Bug#236293: unresolved symbols when insmod 8390

2004-06-05 Thread Shaul Karl
I have tried with 20040528, from unstable. 1) aic7xxx issues. According to section 2.1.1 of the Installation HOWTO, If you have a SCSI CD drive and a relatively uncommon SCSI controller, then you may also need one driver floppy to let the installer see your CD drive.

Bug#236293: unresolved symbols when insmod 8390

2004-05-29 Thread Shaul Karl
On Tue, May 25, 2004 at 07:09:43PM +0100, Martin Michlmayr wrote: Can you try new images from http://gluck.debian.org/cdimage/testing/sarge_d-i/ and say whether any of this issue is still there? That URL is of no use to me because I can't burn CDs. Am I right that there are no floppy images

Bug#239004: Do you have target/etc/fstab?

2004-03-20 Thread Shaul Karl
The following might be related: http://lists.debian.org/debian-user/2004/debian-user-200403/msg02509.html -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have an idea and we exchange these ideas,

Can you help with debugging the problem?

2004-03-14 Thread Shaul Karl
The installation fails because the kernel-image package is not installed during the installation of the base system. The error message that was written to var/log/messages is: /usr/sbin/mkinitrd: Cannot determine root device Any suggestion what to do in order to get more information

Re: Can you help with debugging the problem?

2004-03-14 Thread Shaul Karl
On Sun, Mar 14, 2004 at 04:30:48PM +0100, Petter Reinholdtsen wrote: [Shaul Karl] The installation fails because the kernel-image package is not installed during the installation of the base system. The error message that was written to var/log/messages is: /usr/sbin/mkinitrd

Bug#237834: /usr/sbin/mkinitrd: Cannot determine root device

2004-03-13 Thread Shaul Karl
Package: install Version: 20040312 (floppies) Severity: normal 1. Installation of the kernel fails because mkinitrd cannot determine the root device. The following is taken from var/log/messages: Reading Package Lists... Building Dependency Tree... The following extra packages will be

d-i: Main menu pops up before the base system gets installed.

2004-03-12 Thread Shaul Karl
I am using the floppies of 20040312. The main menu pops up during the installation of the base system, even though the base system is not fully installed. I believe it happens when I should be prompted for the selection of the kernel, but I am not sure. The main menu hides most of the base

Bug#236293: unresolved symbols when insmod 8390

2004-03-06 Thread Shaul Karl
On Fri, Mar 05, 2004 at 02:41:02PM +0100, sferriol wrote: Shaul Karl a ?crit : Package: install Version: 20040303 (floppies) Severity: normal I have used the net-drivers.img (20040303) floppy. Since I have problems with my nic I tried to insmod 8390 try 'modprobe 8390' instead

Bug#236293: unresolved symbols when insmod 8390

2004-03-06 Thread Shaul Karl
Rethinking about it, the installer didn't move on because of the missing aic7xxx module. It did prompt about it. This is probably why I went in circles. I expected that by `Continue' it will pick up the network modules. The question about aic7xxx remains. -- If you have an apple and I have

Bug#236293: unresolved symbols when insmod 8390

2004-03-06 Thread Shaul Karl
On Fri, Mar 05, 2004 at 02:41:02PM +0100, sferriol wrote: Shaul Karl a ?crit : Package: install Version: 20040303 (floppies) Severity: normal I have used the net-drivers.img (20040303) floppy. Since I have problems with my nic I tried to insmod 8390 try 'modprobe 8390' instead

Bug#236293: unresolved symbols when insmod 8390

2004-03-05 Thread Shaul Karl
Package: install Version: 20040303 (floppies) Severity: normal I have used the net-drivers.img (20040303) floppy. Since I have problems with my nic I tried to insmod 8390 from the command line of the console (2nd VT, alt+F2). I got: Using

Re: debian-installer: A boot parameter for a serial console?

2004-03-05 Thread Shaul Karl
In the original post I wrote about a problem I encountered with the serial console and the d-i of 20040303. I had a hardware problem. There fore, my report should be ignored. -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple.

debian-installer: A boot parameter for a serial console?

2004-03-04 Thread Shaul Karl
I used the floppies of 20040303 and tried, at the boot prompt, to revert to a serial console. I failed. If you wonder why would I use the real console (tty0) to revert to a serial console, the answer is that I tried to get back as quickly as possible to my desk to continue the installation

Bug#216976: The 2003-10-21 i386 bootfloppy-image.img - Kernel panic.

2003-10-21 Thread Shaul Karl
Package: install Severity: grave The 2003-10-21 i386 bootfloppy-image.img creates a kernel panic. Last messages are BusyBox usage message which includes the `Currently defined functions' and then there is a Kernel panic message because of an attempt to kill init. -- Shaul Karl,shaulk

The current implementation of the progress bar is useless with monochrome monitors.

2002-01-12 Thread Shaul Karl
monochrome? Weren't old installation had a menu item for this? -- Shaul Karl email: shaulka(at-no-spam)bezeqint.net Please replace (at-no-spam) with an at - @ - character. (at-no-spam) is meant for unsolicitate mail senders only. -- To UNSUBSCRIBE, email to [EMAIL

Re: The current implementation of the progress bar is useless with monochrome monitors.

2002-01-12 Thread Shaul Karl
Shaul Karl [EMAIL PROTECTED] cum veritate scripsit: With a monochrome monitor the current implementation of the progress bar is useless since it keeps shown as it was shown on the beginning of the process. That is, it keep shows that the process has not been started (or, if you

Re: One should be patient with root.bin and modules.dep

2002-01-07 Thread Shaul Karl
On Sun Jan 06, 2002 at 02:58:53PM -0500, Adam Di Carlo wrote: Shaul Karl [EMAIL PROTECTED] writes: When using the latest root.bin that I could find (18-dec-2001) the screen get flooded with messages about modprobe not being able to read the modules.dep. Altough it is able

nfs directory was not umounted when the installed system reboot?

2002-01-07 Thread Shaul Karl
not remember the name of the other module and did not bother to find it since the installation seemed to work properly. -- Shaul Karl email: shaulka(at-no-spam)bezeqint.net Please replace (at-no-spam) with an at - @ - character. (at-no-spam) is meant

smc-ultra module: woody has the same problem as potato? An odd work around?

2002-01-06 Thread Shaul Karl
be that the reboot should be done after using debootstrap to load the modules, even that it fails to do so. The required parameters for the smc-ultra module in my case were irq=10 io=0x280, although I do not think this is irrelevant. -- Shaul Karl email: shaulka(at-no-spam)bezeqint.net

One should be patient with root.bin and modules.dep

2002-01-06 Thread Shaul Karl
When using the latest root.bin that I could find (18-dec-2001) the screen get flooded with messages about modprobe not being able to read the modules.dep. Altough it is able to recover and continue the installation process one should be patient in order for this to happen. -- Shaul Karl

Re: smc-ultra module: woody has the same problem as potato? An odd work around?

2002-01-06 Thread Shaul Karl
In message E16NBzz-00072g-00@rakefet, Shaul Karl writes: When trying to load the smc-ultra module I get an error. What is the exact error message that you see? I tried to reproduce it and failed. Now it works as expected, apart from a few messages about not being able to create /target

Re: Still no base tarball

2001-08-20 Thread Shaul Karl
Shaul Karl [EMAIL PROTECTED] writes: What if I bought the CDs and now I want to `ship it' to my other 1 or 2 home machines, which doesn't have a CDROM drive and need installing base via floppies? Then, obviously, you won't be able to use the CDs to install with. IMHO base

Re: Still no base tarball

2001-08-19 Thread Shaul Karl
..[EMAIL PROTECTED]...URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Shaul Karl [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble