Re: TFTP booting MVME2604
Hello, my name is Ton van den Broek, software engineer at Leica Microsystems Lithography in Best, the Netherlands. Right now we are using OS-9 as operating system, but since we are losing our faith in it we are considering moving to Linux. We are using an MVME2604 Power PC board, and it looks like Debian is the only one supporting this board. I've downloaded your bootfull.bin from 16 may 2002, 10:12, and boot the CPU-board with TFTP. That is working, but it doesn't recognize the SCSI-harddisk, which means the end of installing Linux. The drive and cable must be allright, because OS-9 does recognize it. ... A.T.J. van den Broek Software engineer ... Hello Ton, I don't know about the 16 may version, but the 21th version contain the ncr driver, but not the sym one according to: $ pwd /home/ftp/pub1/debian/dists/woody/main/disks-powerpc/3.0.23-2002-05-21/prep $ zgrep 53c8 sysmap.gz c0053c88 t get_env c011dd7c t ncr53c8xx_select_queue_depths c011de94 T ncr53c8xx_queue_command c011df40 t ncr53c8xx_intr c011e050 t ncr53c8xx_timeout c011e128 T ncr53c8xx_reset c011e244 T ncr53c8xx_abort c011ebf4 t ncr53c8xx_proc_info c011ec94 T ncr53c8xx_info c0173da8 D ncr53c8xx_lock c0173eb4 d proc_scsi_ncr53c8xx c018b914 t sym53c8xx__setup c018bd44 t sym53c8xx_pci_init c018c1dc t sym53c8xx__detect c018e2d0 T ncr53c8xx_setup c018e2f0 T ncr53c8xx_detect The sym53c8xx_ entries are from drivers/scsi/sym53c8xx_comm.h which is included in the ncr driver: $ cd /usr/src/kernel-source-2.4.18 $ find . -type f | xargs grep sym53c8xx_comm.h | grep include ./drivers/scsi/ncr53c8xx.c:#include sym53c8xx_comm.h The ncr driver supports: $ grep -A12 'Supported N' drivers/scsi/ncr53c8xx.c ** Supported NCR/SYMBIOS chips: ** 53C810 (8 bits, Fast SCSI-2, no rom BIOS) ** 53C815 (8 bits, Fast SCSI-2, on board rom BIOS) ** 53C820 (Wide, Fast SCSI-2, no rom BIOS) ** 53C825 (Wide, Fast SCSI-2, on board rom BIOS) ** 53C860 (8 bits, Fast 20, no rom BIOS) ** 53C875 (Wide, Fast 20, on board rom BIOS) ** 53C895 (Wide, Fast 40, on board rom BIOS) ** 53C895A (Wide, Fast 40, on board rom BIOS) ** 53C896 (Wide, Fast 40, on board rom BIOS) ** 53C897 (Wide, Fast 40, on board rom BIOS) ** 53C1510D(Wide, Fast 40, on board rom BIOS) ** Hope that helps. Regards, /Karl PS. . the debian-powerpc list is probably a better place for your problem . please set up your mailer to wrap lines, yours are to long --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 18 26 09 00 Computers Sweden +46 10 270 26 67 Consulting --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debootstrap breaks with libc6.1 2.2.4-2 postinst
I also had problem with libc6 when I installed a Sun U5 yesterday. Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 10 270 26 67 Computers Sweden Consulting --- From: Gerhard Tonn [EMAIL PROTECTED] Subject: Re: debootstrap breaks with libc6.1 2.2.4-2 postinst Date: Thu, 27 Sep 2001 07:29:22 +0200 On Thursday 27 September 2001 01:27, Ethan Benson wrote: why is this only a problem on ia64/x86? i don't see this on powerpc. I have got the same problem on s390. Regards, Gerhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation loop because of a 53c810 SCSI adapter
The SYM driver do not support some old 53c810 chips, it might be what you are seeing, use the NCR driver for thoose. If that does not work, ask on [EMAIL PROTECTED] mailing list. Have you checked your cabling and terminations? Strange that you get the ncr53c8xx_reset message, have you copied it wrong, or are you using the ncr driver? $ grep ncr53c8xx_reset *.c ncr53c8xx.c:int ncr53c8xx_reset(Scsi_Cmnd *cmd, unsigned int reset_flags) ncr53c8xx.c:int ncr53c8xx_reset(Scsi_Cmnd *cmd) ncr53c8xx.c:printk(ncr53c8xx_reset: pid=%lu reset_flags=%x serial_number=%ld serial_number_at_timeout=%ld\n, ncr53c8xx.c:printk(ncr53c8xx_reset: command pid %lu\n, cmd-pid); $ grep sym53c8xx_reset *.c sym53c8xx.c:int sym53c8xx_reset(Scsi_Cmnd *cmd, unsigned int reset_flags) sym53c8xx.c:int sym53c8xx_reset(Scsi_Cmnd *cmd) sym53c8xx.c:printk(sym53c8xx_reset: pid=%lu reset_flags=%x serial_number=%ld serial_number_at_timeout=%ld\n, sym53c8xx.c:printk(sym53c8xx_reset: command pid %lu\n, cmd-pid); For 2), cp /disks-i386/current/images-1.44/compact/kernel-config /linux/.config choose NCR driver instead of SYM mount resque floopy as /mnt build and copy the bzImage to rescue floppy as linux cd /mnt; ./rdev.sh cd; umount /mnt Try it out Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 10 270 26 67 Computers Sweden Consulting --- From: Jone Silva da Costa [EMAIL PROTECTED] Subject: Installation loop because of a 53c810 SCSI adapter Date: Sat, 15 Sep 2001 22:13:27 GMT [Error: Message contained 6 reserved characters] Hello! I'm trying to install Debian 2.2.17 on a PC with a Comtrade SCSI host adapter which is based on NCR/LSI 53c810 chip but I got stuck in an endless loop of the following messages: SCSI host 0 abort (pid0) timed out resetting SCSI bus is being reset for host 0 channel 0. ncr53c8xx_reset: pid=0 reset_flags=2 serial_number=XX serial_number_at_timeout=XX Where XX begins with 0 and get incremented. (Is it possible to catch these to a file) The messages I've been able to find in the archives point to kinds of solutions: 1) boot with parameters sym53c8xx=safe:y or sym53c8xx=mpar:n 2) Remove sym53c8xx from the kernel and make ncr53c8xx default I've already tried both parameter's without any changes so I'd like to try the 2 kind but I unfortunately don't know how so I beg someone to be kind enough to teach me. Also please tell me if I'm following a wrong way. Thanks in advance, Jone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BF 2.3.6 install - 2 glitches
The modconf is wrong, according 3c509.c:
#ifdef MODULE
/* Parameters that may be passed into the module. */
static int debug = -1;
static int irq[] = {-1, -1, -1, -1, -1, -1, -1, -1};
static int xcvr[] = {-1, -1, -1, -1, -1, -1, -1, -1};
and somewhare on http://www.scyld.com (in 3c509.html):
Only the IRQ and transceiver setting may be overridden when using
the driver as a module. Setting two cards to 10base2/IRQ10 and
AUI/IRQ11 is done by using the xcvr and irq module options:
options 3c509 xcvr=3,1 irq=10,11
(xcvr: 0 = default, 1 = AUI, 2 = undefined, 3 = 10base2, 10baseT)
you simply can't set the io base address for the 3c509 module.
/usr/share/modconf/descr.gz has said the wrong thing for a long time,
it is reported in
http://lists.debian.org/debian-testing-9901/msg4.html
under ERROR 2.
Regards,
/Karl
---
Karl HammarAspö Data [EMAIL PROTECTED]
Lilla Aspö 2340 +46 173 140 57Networks
S-742 94 Östhammar +46 10 270 26 67 Computers
Sweden Consulting
---
From: Filip Van Raemdonck [EMAIL PROTECTED]
Subject: BF 2.3.6 install - 2 glitches
Date: Sat, 16 Jun 2001 19:10:20 +0200
...
Second issue, bigger problem: I needed the 3c509 module. Modconf suggested
setting io and irq parameters, so I did (had them ready anyway). This failed
with the error: invalid parameter parm_io.
I tried a couple of variations (ioaddr, iobase, ...) but nothing worked.
I went to see in the kernel sources on another machine, and lo and behold
there was no io parameter for the 3c509 module indeed. (Granted, it was a
Z.4.5 source, but apparently 2.2 didn't have that parameter as well)
I suppose this could puzzle some other users as well, could this be fixed to
only suggesting to set irq and not io? (Probably this is a modconf bug?)
Regards,
Filip
...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies 2.2.25 with i386 2.2.19 upgrade
From my understanding someone has problems with a Tekram DC390U3W or similar card. That card has a Symbios 53C1010 chip and is fully supported by the 2.2.19 linux kernel. The kernel driver version is 1.7.1. I don't think it is supported by the 2.2.13 kernel. The debian boot discs should have no problems with this card. If the problem is outside of the debian boot discs, please move the discussion to linux-scsi at vger.kernel.org to get scsi specific help. If the user do get the scsi bios message at boot and the boot disk is reported as a boot device, linux should have no problem at all booting from that disk, as long as the driver is compiled in or loaded from initrd. The problem you can face is hw oriented: . make sure it is set to 33MHz, 32bit unless you have a motherboard that supports wider/faster pci . make sure there are no irq conflicts . cables and terminations . no scsi bios banner: reflash the card . some disks need to be set at a lower transfer speed in the scsi bios . some motherboard don't do pci master parity, if so try ncr53c8xx=mpar:n boot line argument Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 10 270 26 67 Computers Sweden Consulting --- From: Adam Di Carlo [EMAIL PROTECTED] Subject: Re: boot-floppies 2.2.25 with i386 2.2.19 upgrade Date: 13 Jun 2001 12:59:22 -0400 Brian Schramm [EMAIL PROTECTED] writes: On Mon, 14 May 2001 [EMAIL PROTECTED] wrote: LSI Logic Symbios pci scsi bios. I think that is what you are looking for. Not really, no. I wanted a chip number. www.tekram.com, flip, flip, flip. It's a Symbos 53C1010, which appears to be more or less compatible with the 53C8xx chips used in the earlier tekram cards. At least, there're references to them in the 2.4 series kernels' 53c8xx driver sources, so I assume they work, but there's no mention of them in my copy of the 2.2.13 sources I have here, so you may require a 2.4 kernel to use this card. You should check the 2.2.19 sources. OK, is there anyone building or has a set of 2.4 kernel disks? I'm confused. The potato boot floppies includes CONFIG_SCSI_SYM53C8XX in both the vanilla set and the compact set. You have to identify what config option is required by your card, then grep in the 'kernel-config' files in the b-f area, e.g., URL:http://http.us.debian.org/debian/dists/potato/main/disks-i386/current/ There's not really much else I can do for the user. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: installation problem
Power-ON step, BIOS screens:
USB keyboard worked regardless of bios setting
Lilo prompt:
Needed USB keyboard support in the bios, else no input chars.
From here down, USB keyboard support enabled in the bios.
Kernel loading:
I have made a kernel with USB keyboard support compiled in
I don't know the difference between CONFIG_USB_UHCI{,_ALT}, but they
are possible interchangable, UHCI* is for some usb controllers,
OHCI is for some other.
$ diff config-2.2.19-[23]
541c541
CONFIG_USB=m
---
CONFIG_USB=y
545,547c545,546
CONFIG_USB_UHCI=m
CONFIG_USB_UHCI_ALT=m
CONFIG_USB_OHCI=m
---
CONFIG_USB_UHCI=y
CONFIG_USB_OHCI=y
554,558c553,555
CONFIG_USB_HID=m
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
CONFIG_INPUT_KEYBDEV=m
CONFIG_INPUT_MOUSEDEV=m
---
CONFIG_USB_HID=y
CONFIG_INPUT_KEYBDEV=y
CONFIG_INPUT_MOUSEDEV=y
The USB support is initialized late in the kernel startup.
I have not tested ^S or ^Q, but they are possible unavilable till USB
is initialized.
System running:
Kernel-2.2.19-2:
No reaction from USB keyboard (no PS/2 keyboard connected, I did
not test what happens when both connected).
Kernel-2.2.19-3:
I had no problem using it with a USB keyboard, or a PS/2 keyboard.
When both USB and PS/2 keyboard was connected I could use both.
The downside with using a USB keyboard is that USB steals an
intterupt (the PS/2 keyboard does that to, but it seems hardwired
to irq 1 and unavailable for other use).
Regards,
/Karl
PS.
With two keyboards/mice/monitors, the computer can serve two users
i X, some minor patching was needed (I have not tested this
myself), ref. http://cambuca.ldhs.cetuc.puc-rio.br/multiuser.
---
Karl HammarAspö Data [EMAIL PROTECTED]
Lilla Aspö 2340 +46 173 140 57Networks
S-742 94 Östhammar +46 10 270 26 67 Computers
Sweden Consulting
---
From: Adam Di Carlo [EMAIL PROTECTED]
Subject: Re: installation problem
Date: 01 Jun 2001 14:32:35 -0400
Karl Hammar [EMAIL PROTECTED] writes:
The other issue is if the boot-floppies should be able to use a
usb-keyboard.
I think the answer here is yes, if possible.
I have CC'd Herbert Xu, the i386 kernel images maintainer.
According to kernel_source/Documentation/usb/input.txt:
2. Simple Usage
~~~
For the most usual configuration, with one USB mouse and one
USB keyboard, you'll have to load the following modules (or have
them built in to the kernel):
input.o
mousedev.o
keybdev.o
usbcore.o
usb-[uo]hci.o
hid.o
After this, the USB keyboard will work straight away, and the USB mouse
will be available as a character device on major 13, minor 63:
To be able to use it at boot we will need to compile thoose in, or
load them without user intervention.
Can't we compile in just enough for the keyboard?
Is this kernel 2.2 or 2.4? We're still using 2.2 on i386.
Keyboard support seems to be built as a module
$ grep USB_KBD 2.2.25-2001-05-12/kernel-config
CONFIG_USB_KBD=m
I don't know what will happen if it is compiled in and you have a
standard keyboard, but I might be able to test it in the weekend.
A very good question.
--
.Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: USB on X86 platform boot
Strange behaviour, you can use the USB without USB support in the bios
nor the kernel, the only thing you need is a PS/2 keyboard connected.
This makes one wonder whether it is the hw or the linux kernel that
needs to be fooled to believe that you have a PS/2 kbd. when you really
are using a USB kbd.
Interesting question, but I wont pursue it further. You have to find
someone knowledgable in the PS/2 input hardware and linux keyboard
low level routines for that.
BTW, the send_data routine mentioned is only used by:
void pckbd_leds(unsigned char leds)
{
if (kbd_exists (!send_data(KBD_CMD_SET_LEDS) || !send_data(leds))) {
send_data(KBD_CMD_ENABLE); /* re-enable kbd if any errors */
kbd_exists = 0;
}
}
in the same file. I have not found a reference to it anywhare else in
the kernel source:
$ find . -name \*.c -or -name \*.h | sort | xargs grep send_data | less
Regards,
/Karl
---
Karl HammarAspö Data [EMAIL PROTECTED]
Lilla Aspö 2340 +46 173 140 57Networks
S-742 94 Östhammar +46 10 270 26 67 Computers
Sweden Consulting
---
From: Erich Mueller [EMAIL PROTECTED]
Subject: Re: USB on X86 platform boot
Date: Fri, 1 Jun 2001 22:43:34 +0200 (CEST)
On 1 Jun 2001, Adam Di Carlo wrote:
Erich Mueller [EMAIL PROTECTED] writes:
sorry for having lost the thread again now, I changed machines several
times between home and workplace and also subscribed fom another address.
The temporary fix or workaround based on the hint from this list, I think
it was Karl Hammar [EMAIL PROTECTED] forwarded to me by Adam. The
(borrowed) PS2 keyboard in place in addition to the USB keyboard of the
machine did help to get past the critical point. Now the machine is
loading its guts over the network and will soon be singing and dancing.
(The original problem is still not fixed, maybe a later kernel does.
Should this workaround be advertized in the faqs or docs somewhere?)
I shall add a todo item that we need to try to fix this.
Please clarify some matters for me so I can get it right.
The problem is that you cannot use the USB keyboard during the install
process, no matter the BIOS settings, you had to use a PS/2 keyboard,
right?
The USB keyboard worked according to BIOS settings or not (USB CHIP and
KEYBOARD/MOUSE on/off work as advertised) The problem that I was
confronted with was that after the kernel boot messages displayed that
keyboard timout message no keyboard attached the USB keyboard was ignored
regardless of bios settings. After attaching the PS/2 keyboard (togather
with the (enabled in BIOS) USB keyboard I used the USB keyboard all the
way for all input with no problems at all. The lack of PS/2 keyboard only
surfaced when trying to hit the enter key at the first requested input
after the booting of the kernel noticed that no AT style keyboard present.
I hope this clarifies the problem I did not do one single keystroke on
the PS/2 keyboard all the inputs are taken from the USB keyboard. BIOS
settings, SYSLINUX and all the bootstrap interaction worked with no hickup
when the PS/2 keyboard is plugged in(but unused for input). I would
dare to speculate that the code in the kernel that branched off to spit
out the message about keyboard timout also detaches all the
subsequent communication process with the input devices (regardless of the
perfectly supported ad sevicable USB keyboard available)
The message stems form /usr/src/linux/drivers/char/pc_keyb.c
-snip--
static int send_data(unsigned char data)
{
int retries = 3;
do {
unsigned long timeout = KBD_TIMEOUT;
acknowledge = 0; /* Set by interrupt routine on receipt of
ACK
Re: installation problem
[to Erich] http://www.msi-technology.de/download/bios/63xx/K7T%20Pro-Turbo%20v2.7.zip is available. If you have problems downloading it, I have put it up as ftp://kalle.csb.ki.se/pub/tmp/K7T_Pro-Turbo_v2.7.zip I.e. without spaces (there seem to be some problems with netscape and their site), but I don't think it will solve your problem. According the the manual available at: http://www.msi.com.tw/support/manual/6xxx/6330lite/6330litev10a.zip there is a ps2 keyboard connector on the motherboard. Do you have one to connect ? I don't think you can use the usb-keyboard with current boot-floppies (see below). [to list] The other issue is if the boot-floppies should be able to use a usb-keyboard. According to kernel_source/Documentation/usb/input.txt: 2. Simple Usage ~~~ For the most usual configuration, with one USB mouse and one USB keyboard, you'll have to load the following modules (or have them built in to the kernel): input.o mousedev.o keybdev.o usbcore.o usb-[uo]hci.o hid.o After this, the USB keyboard will work straight away, and the USB mouse will be available as a character device on major 13, minor 63: To be able to use it at boot we will need to compile thoose in, or load them without user intervention. Keyboard support seems to be built as a module $ grep USB_KBD 2.2.25-2001-05-12/kernel-config CONFIG_USB_KBD=m I don't know what will happen if it is compiled in and you have a standard keyboard, but I might be able to test it in the weekend. Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 10 270 26 67 Computers Sweden Consulting --- From: Erich Mueller [EMAIL PROTECTED] Subject: Re: [Karl Hammar [EMAIL PROTECTED]] Re: installation problem Date: Wed, 30 May 2001 17:37:39 +0200 (CEST) ... The case bears a Compaq Presario sticker Inside is a MSI 6330 LITE (K7T) bios version 2.6 (in the meantime a version 2.7 has been made available and apearantly retracted again, since I can no longer download it(says not not avaiable when I ask for http://msi-1.colt-isc.de/download/bios/63xx/K7T Pro-Turbo v2.7.zip The keyboard actually doas work for the initial selection and help with the functionkeys. No problem to do input at the first prompt when it asks for selectors and boot parameters. Hmm, ok, this is the syslinux stuff. All input from keyboard works ok here still. The machine then proceeds with the boot process and some line come up stating no AT keyboard, keyboard timeout. Then the boot continues until the first screen of acknowledgements comes up and there it hangs waiting for input to continue past that screen. If you press ctrl-s while the kernel is booting (that's for pause), does the scrolling stop? FYI, you can stop pausing with ctrl-q. Only before the message about missing AT keyboard is shown. I'm trying to figure
Re: installation problem
Can't he (Erich) enable legacy keyboard support in the BIOS. You then don't need usb-drivers to use the keyboard if I remember right. Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 10 270 26 67 Computers Sweden Consulting --- From: Adam Di Carlo [EMAIL PROTECTED] Subject: Re: installation problem Date: 29 May 2001 10:10:39 -0400 Erich Mueller [EMAIL PROTECTED] writes: do all the debian distribution boot images insist on AT style keyboards? Unfortunately my usb keyboard seems to be unsuported at least in the initial bootup phase the keyboard timeout and lack of AT-type keyboard prevents the completion of the booting process of the distribution images. (when the first input is requested by the curses screen) The modules are of little use since they get loaded much later. Is there a workaround for this? I don't know... I am CC'ing the list. I am very unfamiliar with USB in Linux -- sounds like we should support this. Erich, which architecture are you? -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Unidentified subject!
Check with: http://www.linuxdoc.org/HOWTO/Hardware-HOWTO.html Regards, /Karl --- Karl HammarAsp Data [EMAIL PROTECTED] Lilla Asp 2340 +46 173 140 57Networks S-742 94 sthammar +46 10 270 26 67 Computers Sweden Consulting --- From: "Ken Rudy" [EMAIL PROTECTED] Subject: Date: Thu, 8 Mar 2001 15:45:49 -0500 I am looking for a SCSI 2 Card that will work with the Debian O/S. This card must be PCI and must have software to support the hardware. I am pretty clueless in UNIX-LINUX but i am getting the hang of it. I just need a place to start to purchase this card. Thank You Kenneth Rudy System's Administrator 140 Broad Street Red Bank NJ 07701 1-732-450-1100 Ext. 111 [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing Potato: can't find HD
Linux 2.2.18 with ide-patch applied should work. To Joe Nahmias: Try the images at http://people.debian.org/~aph/current/images-1.44/udma66/ and report back. OR The Abit KA7-100 has four IDE channels, the two first is driven by the HPT 370 chip and the other two is connected to the VIA controller. It thus resembles the KT7-Raid mentioned in: http://lists.debian.org/debian-boot-0101/msg00407.html Try the same procedure as outlined there. Regards, /Karl --- Karl HammarAsp Data [EMAIL PROTECTED] Lilla Asp 2340 +46 173 140 57Networks S-742 94 sthammar +46 10 270 26 67 Computers Sweden Consulting --- From: [EMAIL PROTECTED] (H.Heinold) Subject: Re: Problem installing Potato: can't find HD Date: Thu, 1 Mar 2001 15:51:55 +0100 On Thu, Mar 01, 2001 at 09:44:04AM -0500, Joe Nahmias wrote: 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 ^^^ Sorry but the potato kernel dont include any UDMA100 controllers. The only thing you can do is build a floppy with a kernel which fits you hardware. If you had have search the mailingslist acrhive, you would know it by your self. -- Henning Heinold -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new install
You ask: Q How to download files and install inside of windows? A Windows has ftp/www clients, use them to download to e.g. c:\tmp then reboot to linux; mount your_win_part /mnt and your downloaded files are available in /mnt/tmp Q KNE100TX, drivers: A vanilla 2.2.12 uses: tulip.c:v0.89H 5/23/98 [EMAIL PROTECTED] vanilla 2.2.18 uses: tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED] lastest drivers and mailing list, see: http://www.scyld.com/network/ I don't have any problems with the kne100tx and 2.2.18. You are probably experiencing that auto negotiation is not working. Regards, /Karl PS. I think you used the wrong list. Try debian-user next time. According to http://www.debian.org/MailingLists/subscribe: "Creating and modifying of the boot floppies is the subject of this list." --- Karl HammarAsp Data [EMAIL PROTECTED] Lilla Asp 2340 +46 173 140 57Networks S-742 94 sthammar +46 10 270 26 67 Computers Sweden Consulting --- From: "Chris Parker" [EMAIL PROTECTED] Subject: new install Date: Sat, 17 Feb 2001 22:51:46 -0500 Hello I want to install the latest kernel in the stable set. I am currently using windoze me. How to download files and install inside of windows? My ethernet card is a pce kingston kne100txand under 2.2.12 it wouldn't work using the tulip driver. Is thier another driver or module to use? Anyways how do I download and install under windoze? Theanks in advance for any help. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Help with multi install
After you have installed one - you could: 1) check whats node specific: cd /etc find . -type f | xargs grep your_ip_number find . -type f | xargs grep your_hostname # above are the files to edit later enable SULOGIN=yes in /etc/default/rcS shutdown -h now while more_disks do connect your disks as (ide disks assumed) primary slave, secondary master and slave boot and login at first login dd if=/dev/hda of=/dev/hdb dd if=/dev/hda of=/dev/hdc dd if=/dev/hda of=/dev/hdd for i in all_partitions; do fsck -f $i; done for i in root_partitions do mount $i /mnt $EDITOR /mnt/etc/$above_files; umount /mnt done shutdown -h now disconnect drives and install them in target pc's done 2) dpkg --get-selections list while more_pcs do base install it fetch file list above dpkg --set-selections list dpkg something_I_forgot or dselect # go to install, or apt-get -i `cat list` done Regards, /Karl --- Karl HammarAsp Data [EMAIL PROTECTED] Lilla Asp 2340 +46 173 140 57Networks S-742 94 sthammar +46 10 270 26 67 Computers Sweden Consulting --- From: "Laubacher Libor" [EMAIL PROTECTED] Subject: Help with multi install Date: Mon, 5 Feb 2001 21:45:00 +0100 Hi, I have 11 identical PC's and wonna install potato on all those PC's Is there any way how to install potato to one (first) and use some trick to transer installation to others 10 PC's ? Any help would be appreceiated. Regards, Libor Libor Laubacher Progress DBA - Novell/WinNT/AiX/LiNUX Czech Insurance - Headquarters, Prague, CZ http://www.cpoj.cz phone: +420 2 6799 1828 mobile: +420 603 280555 fax: +420 2 793 37 42 -- Improvement is impossible without change. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#82018: udma66 boot floppies should use current 2.2.1?-ide kernel
Actually, since I have not tested them myself, I cannot make such a statement. Regards, /Karl --- Karl HammarAsp Data [EMAIL PROTECTED] Lilla Asp 2340 +46 173 140 57Networks S-742 94 sthammar +46 70 511 97 84 Computers Sweden Consulting --- From: Adam Di Carlo [EMAIL PROTECTED] Subject: Bug#82018: udma66 boot floppies should use current 2.2.1?-ide kernel Date: 12 Jan 2001 19:11:11 -0500 You're not exactly clear. The remedy for this bug (and the others mentioned) is simply to use the kernel-image-2.2.18-ide package rather than kernel-image-2.2.18pre21-ide ? -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ata 100 drivers for debian.(Promise Ultra100 IDE Controller PDC20265)
Understood and agreed. So we won't file bug reports about it? Regards, /Karl --- Karl HammarAsp Data [EMAIL PROTECTED] Lilla Asp 2340 +46 173 140 57Networks S-742 94 sthammar +46 70 511 97 84 Computers Sweden Consulting --- From: Glenn McGrath [EMAIL PROTECTED] Subject: Re: ata 100 drivers for debian.(Promise Ultra100 IDE Controller PDC20265) Date: Thu, 11 Jan 2001 19:29:41 +1100 Adam Di Carlo wrote: Karl Hammar [EMAIL PROTECTED] writes: I assume you have two ordinary ide controllers on your motherboard. In that case you can: connect disc on std. ide install debian download lk-2.2.18 and latest ide-patches roll your own kernel and install it move disc to udma100 controller find out what the discs new name by rebooting and studying boot messages, probably /dev/hde reboot with root=/dev/hde??, s/hda/hde/g in /etc/fstab I send a similar mail with subject 'Re: UDMA66 boot problem/HPT370' today, it contains more details. Karl, doesn't all this indicate that there's some stuff not supported on our kernel-image-2.2.18pre21-ide package which *should* be? If so, could you please file a bug on this package? I'm trying to get one more point release of Debian out the door and this would be really helpful if we could get this last round of kernel issues solved (it will help for woody too). All we can do as far as supporting ata100 is make sure that the IDA and UDMA kernels have the latest ide patch applied, which is Herberts domain. Patches from http://www.kernel.org/pub/linux/kernel/people/hedrick/ide-2.2.18/ Glenn ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ata 100 drivers for debian.(Promise Ultra100 IDE ControllerPDC20265)
From my understanding, this is a case of tracking upstream. Is it really a bug? Regards, /Karl --- Karl HammarAsp Data [EMAIL PROTECTED] Lilla Asp 2340 +46 173 140 57Networks S-742 94 sthammar +46 70 511 97 84 Computers Sweden Consulting --- From: Adam Di Carlo [EMAIL PROTECTED] Subject: Re: ata 100 drivers for debian.(Promise Ultra100 IDE Controller PDC20265) Date: 10 Jan 2001 22:49:36 -0500 Karl Hammar [EMAIL PROTECTED] writes: I assume you have two ordinary ide controllers on your motherboard. In that case you can: connect disc on std. ide install debian download lk-2.2.18 and latest ide-patches roll your own kernel and install it move disc to udma100 controller find out what the discs new name by rebooting and studying boot messages, probably /dev/hde reboot with root=/dev/hde??, s/hda/hde/g in /etc/fstab I send a similar mail with subject 'Re: UDMA66 boot problem/HPT370' today, it contains more details. Karl, doesn't all this indicate that there's some stuff not supported on our kernel-image-2.2.18pre21-ide package which *should* be? If so, could you please file a bug on this package? I'm trying to get one more point release of Debian out the door and this would be really helpful if we could get this last round of kernel issues solved (it will help for woody too). -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ata 100 drivers for debian.(Promise Ultra100 IDE Controller PDC20265)
I don't have that card any more. I delivered it to a customer. Regards, /Karl --- Karl HammarAsp Data [EMAIL PROTECTED] Lilla Asp 2340 +46 173 140 57Networks S-742 94 sthammar +46 70 511 97 84 Computers Sweden Consulting --- From: Glenn McGrath [EMAIL PROTECTED] Subject: Re: ata 100 drivers for debian.(Promise Ultra100 IDE Controller PDC20265) Date: Thu, 11 Jan 2001 21:29:31 +1100 Karl Hammar wrote: Understood and agreed. So we won't file bug reports about it? Regards, /Karl I assume the next release will use the kernel-image-2.2.18-ide image (rather than pre18), maybe you could check if this image recognises your card. Im not sure how to check which patches were used to build a kernel image... Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dbootstrap problem
I saw the same symtoms when booting from cd. So I created floppies instead and booted from them. They worked ok. Regards, /Karl --- Karl HammarAsp Data [EMAIL PROTECTED] Lilla Asp 2340 +46 173 140 57Networks S-742 94 sthammar +46 70 511 97 84 Computers Sweden Consulting --- From: Richard Giles [EMAIL PROTECTED] Subject: dbootstrap problem Date: Sat, 6 Jan 2001 00:08:02 + Pentium II PC 350MHz 64MB RAM All hardware already runs Caldera Linux 2.4 OK. Hi - Please can you help ??? I am trying to replace Caldera Open Linux 2.4 with Debian 2.2r2 (from official CDs). I want to use the exisiting partitions. Dbootstrap doesn't let me get past "Configure Device Driver Modules" When I go in to this section it asks me if I want to skip it, and whatever I say it returns me to the previous screen (an infinite loop!). I gather that dbootstrap remembers information it has gathered previously and presumably it does this in a file on my existing Linux partition. I suspect the cure may be to make it start afresh but I don't know how to do this (doesn't say in install.en.txt as far as I can see). Thanks for your time. Keep up the good work. Richard Giles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: UDMA66 boot problem/HPT370
To install debian potato on an abit kt7-raid motherboard: (well, this is what I roughly did) 1 Connect your disk to the first ide controller, not to the HTP370 controller 2 I used the debian/dists/potato/main/disks-i386/ 2.2.20.0.1-2000-12-03/images-1.44/idepci disk set 3 boot and install as usual 4 download and unpack kernel/v2.2/linux-2.2.18.tar.gz 5 download and apply patch kernel/people/hedrick/ ide.2.2.18.1209.patch.gz 6 make menuconfig - Block devices: [*]Generic PCI IDE chipset support ... [*] HPT366 chipset support Don't know about theese two but they seem to work for me [*]HPT366 Fast Interrupt support (WIP) [*]HPT366 mode three unsupported (WIP) (Note! this driver has no raid support, you just get the udma100 support and two more controllers, only connect discs to hpt controller) and whatever else you want in the kernel 7 make dep; make bzImage; make modules; make modules_install 8 cp arch/.../bzImage System.map to /boot 9 add new image to lilo.conf with root=/dev/hdexx instead of hda 10 run lilo 11 change hda to hde in /etc/fstab 12 shutdown -h now 13 poweroff 14 move disk cable to first HPT370 connector 15 boot Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting --- -- From: "Alexander Sawallich" [EMAIL PROTECTED] Subject: UDMA66 boot problem/HPT370 Date: Tue, 12 Dec 2000 21:46:46 +0100 When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100 controller, with the UDMA66 boot floppies, the system halts during the boot process. ... ... Abit KT7-Raid Motherboard ... Alexander -- From: Jon Branch [EMAIL PROTECTED] Subject: RE: UDMA66 boot problem/HPT370 Date: Wed, 13 Dec 2000 02:01:37 -0500 (EST) Hi Alexander Sorry no solution from me. I'm faced with a near identical problem using the HPT 370 on-board controller with a 2theMax BX7 +100 motherboard (actually with five of them). So I'll be interested to see the solution if/when you get one. Regards Jon Branch ... -- From: "Alexander" [EMAIL PROTECTED] Subject: RE: UDMA66 boot problem/HPT370 Date: Thu, 14 Dec 2000 23:18:15 +0100 I´m desperate to install debian eventhough it doesn´t seem to work with me. I had Suse installed a year ago, but I don´t want to put up with there funny rc.config-thingy any more. It seems that my onboard HPT370 controller should be supported on the udma66 floppies. I just got unlucky and so it doesn´t work. I already received a few replies by some other KT7 owners indicating that I´m not alone. I can boot into the setup assistant just fine from the regular 2.2r2 CD, but then I have no harddisk. There´s an option in the setup menu that lets you load modules from floppy, and I tried loading something from the UDMA66 driver1-4 disks, but then I only got an error telling me that the system is unable to mount the floppy (???). Also I´m not so sure if there´s a useful driver on those disks anyhow. When I boot from the udma66 floppies it just stops half way (see description below) . I really don´t know what more to do. Maybe I could boot from the CD by supplying a bunch of boot parameters, describing my disk. So if you have a clue what I (and many others) could do I would really appreciate if you send me a reply. Under Windows the HPT370 controller(ide2 ide3 ( counting from 0)) seems to run as a scsi device. If you need any information youst ask me. Thanks a lot. Alexander ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: netcfg
Regarding ip calculations.
The main formula for ip calculations is:
nna = nip nsm; /* numeric network addr. = numeric ip bitwise and
numeric subnetmask */
nbc = nip | ~nsm; /* -"-broadcast addr. = -"- -"- or bitwise
inverse of -"- -"- */
You can try my ipcalc (source below).
$ ~/sw/prg/c/ipcalc
Usage:
/home/karl/sw/prg/c/ipcalc [opt] ip.nr/netmask
/home/karl/sw/prg/c/ipcalc [opt] ip.nr subnetmask
Synopsis:
without [opt], will print out the network address, ip.nr, broadcast address,
subnet mask and cidr
opt = -i, used with ifconfig
opt = -r, used with route
Examples:
$ /home/karl/sw/prg/c/ipcalc 192.168.3.34/24
192.168.3.0 192.168.3.255
$ /home/karl/sw/prg/c/ipcalc 192.168.3.34 255.255.255.0
192.168.3.0 192.168.3.255
# ifconfig eth0 `/home/karl/sw/prg/c/ipcalc -i 192.263.3.35/27`
# route add `/home/karl/sw/prg/c/ipcalc -i 192.263.3.35/27`
$ ~/sw/prg/c/ipcalc 192.168.93.22 255.255.255.224
192.168.93.0 192.168.93.22 192.168.93.31 255.255.255.224 27
$ ~/sw/prg/c/ipcalc 192.168.93.22/27
192.168.93.0 192.168.93.22 192.168.93.31 255.255.255.224 27
# ~karl/sw/prg/c/ipcalc -i 192.168.92.24/24
192.168.92.24 netmask 255.255.255.0 broadcast 192.168.92.255
# ~karl/sw/prg/c/ipcalc -r 192.168.92.24/25
-net 192.168.92.0 netmask 255.255.255.128
# ifconfig eth0 `~karl/sw/prg/c/ipcalc -i 192.168.92.24/25`
# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:C0:F0:57:BE:82
inet addr:192.168.92.24 Bcast:192.168.92.127 Mask:255.255.255.128
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0xa700
#
Regards,
/Karl
-------
Karl HammarAspö Data [EMAIL PROTECTED]
Lilla Aspö 2340 +46 173 140 57Networks
S-742 94 Östhammar +46 70 511 97 84 Computers
Sweden Consulting
---
From: Joey Hess [EMAIL PROTECTED]
Subject: Re: netcfg
Date: Thu, 7 Dec 2000 21:45:57 -0800
David Whedon wrote:
I'm starting to look at network configuration. I'm using dbootstrap/netconfig.c
as a guide, debconf'ing the messages to start.
I hope you're not actually copying the code twitch, just the flow.
I have a little debconf C client library that makes it fairly painless
to telk to debconf from C, you can use things like this:
debconf_command("TITLE", "This is my little peice of debian-installer", NULL);
debconf_command("INPUT", "medium", "foo/bar", NULL);
debconf_command("GO", NULL);
debconf_command("GET", "foo/bar", NULL);
if (strcmp(debconf_ret, "true") == 0) {
/* yes, do foo/bar */
}
debconf.{c,h} are currently scattered accross the d-i tree; I intend to
move them into a library that we can link to (shared/static I dunno) soon,
as the current situation is ridiculous.
I figure this is a good place
to start. Other than autodetection and giving the user the option of answering
fewer questions, is there anything new people are looking for in the network
setup? Anything from the current installer that was a problem in the past?
It's always seemed pretty well done to me. I like how it calculates the
third value from the first two. Anyone who understands networking or has
the appropriate numbers on paper can use it pretty well.
We might want to toss in a dotted-quad data type into cdebconf (and
perhaps debconf itself too) to facilitate entering IPs, I don't really
know.
In any case, I'm sort of claiming the network setup,
Great. It definitly needs to be done soon.
Are you going to do just the manual setup, leave dhcp for later? They
should be seperate packages unless they wind up sharing tons of code and
being rather small.
--
see shy jo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
/** Copyright: Karl Hammar, Aspö Data
** Copyright terms: GPL
**/
#include stdio.h
#include string.h
#include ctype.h
#include stdlib.h
#include unistd.h
typedef unsigned char u8;
typedef unsigned short u16;
typedef unsigned int u32;
/*typedef unsigned long long u64;*/
int Usage(char *cmd);
int parse1( u32 *nip, u32 *nsm, int *cidr, char *str);
int parse2( u32 *nip, u32 *nsm, int *cidr, char *ip, char *sm);
int mksm( u32 *sm, long int cidr);
char * dot2num( u32 *num, char *dot);
void num2dot( u32 num, char *dot);
u32 tab[] = {
0x,
Re: Booting loops (Downloading SCSI SCRIPTS)
safe:y implies mpar:n
(see ${your_kernel-2.2.17-dir}/drivers/scsi/README.ncr53c8xx line 862..884)
Somehow someone added, for some reason, the ncr-810 safe:y line.
This together with the fact that there is a shortage of lines at the
boot screens, made suggest a minimal change, just to be able to boot.
Then in a production environment, safe:y is grossly suboptimal.
But at least, we made it install.
Hälsningar,
/Karl
---
Karl HammarAspö Data [EMAIL PROTECTED]
Lilla Aspö 2340 0173 140 57 Nätverk
S-742 94 Östhammar 070 511 97 84 PC/Sun datorer
SwedenLinux/Unix konsulting
---
From: Adam Di Carlo [EMAIL PROTECTED]
Subject: Re: Booting loops (Downloading SCSI SCRIPTS)
Date: 29 Nov 2000 09:41:20 -0500
Karl Hammar [EMAIL PROTECTED] writes:
*** linux-scsi:
Regarding master parity error. It seems that the moderboard was erring.
I put the same Tekram DC390U in another machine and there it worked with
pci parity checking on (see dmesg last in mail).
*** debian-boot and Adam Di Carlo:
Don't file a bug against the kernel.
It fix is almost already there
I suggest the following patch (and similar for other languages):
$ diff -u f6.txt.~1~ f6.txt
--- f6.txt.~1~ Thu Nov 23 07:37:20 2000
+++ f6.txt Thu Nov 23 07:43:29 2000
@@ -11,7 +11,7 @@
BusLogic SCSI Hosts 0fbuslogic=0biobase07
Certain DELL machines0faic7xxx=no_probe07
Future Domain TMC-8xx/9500ftmc8xx=0bmem_base0f,0birq07
-NCR-810 SCSI controller 0fsym53c8xx=safe:y07
+NCR-based SCSI controllers 0fsym53c8xx=safe:y07
Pro Audio Spectrum 0fpas16=0biobase0f,0birq07
PS/2 ESDI (MCA) 0fed=0bcyl0f,0bhead0f,0bsec07
Seagate ST-0x0fst0x=0bmem_base0f,0birq07
Ok, applied.
So we don't need to document "sym53c8xx=mpar:n" ?
And possible mention in the release-notes that we switched from the
ncr to the sym-driver which checks for parity errors on the pci bus.
Which results in driver loops during boot for some bad controller-
motherboard combinations. Fix as above.
I'll send this to the release notes maintainer for his consideration.
--
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Booting loops (Downloading SCSI SCRIPTS)
debian-boot and Frank:
From what I recognize what Gérard says, we could boot the Tekram
DC390U with:
boot: linux sym53c8xx=mpar:n
to disable the pci master parity checking.
I have tested this and it works (tested with boot floppies v2.2.17).
Gérard:
Thank you for your quick and kind help.
(the url seems to be
ftp://ftp.tux.org/roudier/drivers/portable/experimental/sym-2.0.4-20001112.tar.gz)
^^^
Regards,
/Karl
---
Karl HammarAspö Data [EMAIL PROTECTED]
Lilla Aspö 2340 +46 173 140 57Networks
S-742 94 Östhammar +46 70 511 97 84 Computers
Sweden Consulting
---
From: Gérard Roudier [EMAIL PROTECTED]
Subject: Re: Booting loops (Downloading SCSI SCRIPTS)
Date: Wed, 22 Nov 2000 20:11:34 +0100 (CET)
The error indicates that the device, acting as a master, detected a PCI
parity error, either in data received, or the PCI target having signaled
such an error condition.
Historically, the FreeBSD ncr and the Linux ncr53c8xx drivers didn't care
about the Enable Parity Error Response bit in the PCI command register. By
the way, only a few PCI device drivers are caring about it, even nowadays.
Result is that most systems are running PCI devices with PCI parity error
just ignored.
I have changed that in sym53c8xx, since PCI parity checking is not a
option for this kind of device, but is mandatory. So, the driver is not
the cause of the problem you report but it is the hardware that is not PCI
compliant. Which part of the hardware ? is the question. I donnot know is
my response. :-)
I have implemented some work-around in the FreeBSD sym driver, and this
driver has muted to SYM-2 driver. SYM-2 also supports Linux and is
currently available for testing:
ftp://ftp.tux.org/drivers/portable/experimental/sym-2.0.4-20001112.tar.gz
Btw, the work-around consists in early detecting (in snooptest) the
hardware PCI parity breakage and disabling PCI parity checking by the
master. Nothing actually magic.:)
The change is small enough to be merged with sym53c8xx-1.7.x, but, in my
limited time, I do prefer to work on SYM-2, which is intended to replace
3 drivers by a single one.
Gérard.
On Wed, 22 Nov 2000, Karl Hammar wrote:
Problem verified.
The sym53c8xxx driver won't boot with a Tekram DC390U card installed.
I have tested this with two different DC390U (53c875e) cards, and with
a DC310 card.
The ncr53c8xxx driver boots ok.
Kernels 2.0.38, 2.2.{0,10,15,17-whith sym-driver 1.7.1} tested.
debian-boot:
The quick fix is to make another boot diskette, but replace the
sym-driver with the ncr-driver.
linux-scsi:
Is this known? From the docs I get the impression that the 875 is
supported by sym driver.
Regards,
/Karl
---
Karl HammarAspö Data [EMAIL PROTECTED]
Lilla Aspö 2340 +46 173 140 57Networks
S-742 94 Östhammar +46 70 511 97 84 Computers
Sweden Consulting
---
From: Frank Heckenbach [EMAIL PROTECTED]
Subject: Booting loops (Downloading SCSI SCRIPTS)
Date: Tue, 21 Nov 2000 18:13:43 +0100
I'm trying to install Debian GNU/Linux 2.2 (LinuxLand -- official
i386 Binary (2814)), but booting (from CD or disk) hangs in an
endless loop of the following messages:
sym53c875-0: restart (scsi reset)
sym53c875-0: Downloading SCSI SCRIPTS
sym53c875-0:1: ERROR (40:0) (e-ae-0) (0/5)e(script 68:1e00)
sym53c875-0: script cmd=f31c0004
sym53c875-0: regdump: da 10 80 05 47 00 01 0f 71 0e 00 ae 80 00 0e 00
...
Frank
--
Frank Heckenbach, [EMAIL PROTECTED]
http://fjf.gnu.de/
PGP and GPG keys: http://fjf.gnu.de/plan
...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Booting loops (Downloading SCSI SCRIPTS)
*** linux-scsi: Regarding master parity error. It seems that the moderboard was erring. I put the same Tekram DC390U in another machine and there it worked with pci parity checking on (see dmesg last in mail). *** debian-boot and Adam Di Carlo: Don't file a bug against the kernel. It fix is almost already there I suggest the following patch (and similar for other languages): $ diff -u f6.txt.~1~ f6.txt --- f6.txt.~1~ Thu Nov 23 07:37:20 2000 +++ f6.txt Thu Nov 23 07:43:29 2000 @@ -11,7 +11,7 @@ BusLogic SCSI Hosts 0fbuslogic=0biobase07 Certain DELL machines0faic7xxx=no_probe07 Future Domain TMC-8xx/9500ftmc8xx=0bmem_base0f,0birq07 -NCR-810 SCSI controller 0fsym53c8xx=safe:y07 +NCR-based SCSI controllers 0fsym53c8xx=safe:y07 Pro Audio Spectrum 0fpas16=0biobase0f,0birq07 PS/2 ESDI (MCA) 0fed=0bcyl0f,0bhead0f,0bsec07 Seagate ST-0x0fst0x=0bmem_base0f,0birq07 And possible mention in the release-notes that we switched from the ncr to the sym-driver which checks for parity errors on the pci bus. Which results in driver loops during boot for some bad controller- motherboard combinations. Fix as above. Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting --- From: Adam Di Carlo [EMAIL PROTECTED] Subject: Re: Booting loops (Downloading SCSI SCRIPTS) Date: 22 Nov 2000 19:35:38 -0500 Well, what is the upshot here for the purposes of boot-floppies? Document the argument to workaround? File a bug against the kernel to disable the one driver in favor of the other as Karl recommended? -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/ -- From: Karl Hammar [EMAIL PROTECTED] Subject: Re: Booting loops (Downloading SCSI SCRIPTS) Date: Wed, 22 Nov 2000 21:52:50 +0100 debian-boot and Frank: From what I recognize what Gérard says, we could boot the Tekram DC390U with: boot: linux sym53c8xx=mpar:n to disable the pci master parity checking. I have tested this and it works (tested with boot floppies v2.2.17). Gérard: Thank you for your quick and kind help. (the url seems to be ftp://ftp.tux.org/roudier/drivers/portable/experimental/sym-2.0.4-20001112.tar.gz) ^^^ Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting --- From: Gérard Roudier [EMAIL PROTECTED] Subject: Re: Booting loops (Downloading SCSI SCRIPTS) Date: Wed, 22 Nov 2000 20:11:34 +0100 (CET) The error indicates that the device, acting as a master, detected a PCI parity error, either in data received, or the PCI target having signaled such an error condition. Historically, the FreeBSD ncr and the Linux ncr53c8xx drivers didn't care about the Enable Parity Error Response bit in the PCI command register. By the way, only a few PCI device drivers are caring about it, even nowadays. Result is that most systems are running PCI devices with PCI parity error just ignored. I have changed that in sym53c8xx, since PCI parity checking is not a option for this kind of device, but is mandatory. So, the driver is not the cause of the problem you report but it is the hardware that is not PCI compliant. Which part of the hardware ? is the question. I donnot know is my response. :-) I have implemented some work-around in the FreeBSD sym driver, and this driver has muted to SYM-2 driver. SYM-2 also supports Linux and is currently available for testing: ftp://ftp.tux.org/drivers/portable/experimental/sym-2.0.4-20001112.tar.gz Btw, the work-around consists in early detecting (in snooptest) the hardware PCI parity breakage and disabling PCI parity checking by the master. Nothing actually magic.:) The change is small enough to be merged with sym53c8xx-1.7.x, but, in my limited time, I do prefer to work on SYM-2, which is intended to replace 3 drivers by a single one. Gérard. ... sym53c8xx: at PCI bus 0, device 11, function 0 sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up) sym53c8xx: 53c875E detected with Tekram NVRAM sym53c8xx: at PCI bus 0, device 9, function 1 sym53c8xx: setting PCI_COMMAND_PARITY
Re: Setting up a debian archive
Just get all files from some ftp mirror, from the debian directory and down,
and copy them to your harddisk. You'll need some 10-20GB for that.
But if you just want to do new i386 installs with the stable
release (potato) you can skip the following directories (assuming you are
standing in the debian directory):
dists/sid(for unreleased architectures I think i was)
dists/woody (the next release which is not released yet)
dists/*/*/binary-xxx (where xxx != i386 or your preferred arch)
dists/*/*/dists-xxx (where xxx != i386 or your preferred arch)
dists/*/*/upgrade-* (for upgrades)
dists/*/*/source (unless you want the source code as well)
project (I don't think you'll need that stuff)
That will leave you with, hmm:
$ find . -type f | egrep -v './dists/(sid|woody)' |
egrep -v '/source/|/upgrade-|/project' |
egrep -v '(disks|binary)-(alpha|arm|m68|powerpc|sparc)' ~/lst
$ wc -l ~/lst
5882 /home/karl/lst
$ cat ~/lst | xargs ls -l | cut -b31-42 |
perl -e '$s=0; while() { $s+=$_;} print "$s\n";'
2696193910
about 6000 files (plus links and directories) and less than 3GB disk space.
A little to much to download from the internet unless you have a very good
connection. But easily handled with CD-roms or tapes. If you take
the officially released i386 cd's and simply copy their contents to a
directory named debian somewhere on your disk, you'll be set.
If you don't want the complete i386 (or other arch) thing, well then I
cannot help you.
Regards,
/Karl
---
Karl HammarAspö Data [EMAIL PROTECTED]
Lilla Aspö 2340 +46 173 140 57Networks
S-742 94 Östhammar +46 70 511 97 84 Computers
Sweden Consulting
---
From: total [EMAIL PROTECTED]
Subject: Setting up a debian archive
Date: Thu, 02 Nov 2000 23:41:01 -0800
I'm new to debian - if this isn't the correct place to ask this, please
point me to the correct place. Thanks :) (I posted a similar question
in debian-user yesterday got no knowledgeable response.)
I'm installing debian from files in my w95 c:/linux directory onto free
space in hda. I've got all the starting files there (install.bat
loadlin linux base2_2 drivers root rescue) and the install goes fine.
After the basic system is setup on the HD, the installer boots off the
HD, and continues by asking me if I want to install from ppp. I have
gone through this several times, and each time it dl's about 5 MB. I
have saved the dl'd debs.
The next time I do an install, I would like to have it grab the control
info and these 1st base system debs off my HD, not dl them from the
net. After experimenting with the options available, it seems that the
option I desire is to have the installer get the files from a "debian
archive" that is currently mounted.
The options it presents are:
"Install from ppp? (no)
Choose the method apt should use to access the debian archive: cdrom,
ftp, http, filesystem, edit sources by hand"
How do I set up a "debian archive" on my w95 c: drive (filesystem)?
What doc's tell what a "debian archive" is, and how to set one up?
I suspect it is more than just the appropriate deb files in a properly
structured tree - I'm guessing there needs to be some "overview" files
that the package installer reads to find out what the latest version of
the various deb files are - something like "packages" "release" or
"sources" (those are some of the words I thought I saw as the installer
started dl'ing information.)
(Note: I have found out how to have dselect get debs that are wanted
later on, when I want more packages installed, by putting them in
/var/cache/apt/archives. So, how do I get the installer to grab all the
info it needs (including the control files) from my HD, without having
to connect to the net? (Sorta like doing an install from a cd.))
Your help, comments, pointers, are greatly appreciated! Thank you. :-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: potato hard disk install bug
I usually do hard-disk and ftp installs with no special problems with the media method. Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting --- From: David West [EMAIL PROTECTED] Subject: potato hard disk install bug Date: Thu, 2 Nov 2000 14:10:06 -0500 Something like this has been mentioned previously by someone else, but I haven't seen an official bug number for it, or any subsequent mentions, so I'll report it here in the hope that it doesn't get overlooked. I'm not sure whether the error messages I'm getting refer directly to a bug, or whether they are a result of an earlier phase failing. I'm using the Oct 14 materials in http://auric.debian/org/~aph/bf/ in particular the 1.2MB boot floppies and base2_2.tgz. After problems getting the install script to find the kernel and drivers (I have them, but they apparently are not found, even after I create some symlinks which satisfy what the install script says it wants), I copied the debian kernel to my bootable hard disk's Slackware partition, rebooted into Slackware, set up lilo.conf to boot the debian kernel mounting the new debian partition as root, reran lilo, and rebooted, choosing the debian installation when lilo ran. All went well until after the message Starting internet superserver indetd Then it said Template does not contain a template: line at /usr/lib/perl5/Debian/DebConf/Template.pm line 66 TEMPLATE_IN chunk 1371 INIT: Id "1" respawning too fast: disabled for 5 minutes At this point I gave up. Remarks and questions: Given that I have base2_2.tgz and a compatible set of kernel+drivers, a working Slackware installation on another partition, and a working knowledge of lilo, the only reason I started by booting from the floppies is a suspicion that just untarring base2_2.tgz into an empty partition is not enough to create a "correct" minimal install, i.e. that dbootstrap may need to be run to do something that I didn't know needed to be done. Can anyone give definitive info on this point? The debian install doc says, under hard disk install, says the boot floppies are not actually necessary, and that "any other boot method" can be used. I think the doc needs to be more explicit on this point, and also on the issue of exactly how much directory structure is necessary to get the installable files recognized. I really wanted to install the idepci kernel instead of the larger default kernel, but the floppy install didn't seem to offer this as an option. (For the manual install attempt, I used the default kernel just to be on the safe side.) I would guess that all of the above indicates that hard-disk installs are so infrequent that the relevant parts of the install scripts are much less well debugged than is the case for, e.g., CD installs (I'm only doing this because I don't have a CD drive), just as 1.2M floppy installs are so infrequent that no-one (apparently) tried one before potato was released. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
