Topic: Installation problem:signal 7 error&zlib-1.1.3

[Laurent Perez]

Hi

I  finally downloaded the 3.1 release last night (iso). Used nero (the last one) to burn it :

1st problem : while choosing File / Burn an image (I have the french version of Nero, hope the transl. is good), the file type "*.iso" is unknown, only the "*.nrg" is. Switching the dropdown of the File types to "*.*" (only 2 choices : .nrg or .*), a new window appears : you can select the mode - I think I'd better use the Mode 1 - and the byte size : 2048 or 2352. Only the 1st one works. 2 other fields are set to "0" and 2 other boxes are unchecked, and I don't know how to translate them.

THEN : when the cd is burnt, the problem is that every folder contains a file called "".

When I reboot with my rawrited floppy, every thing seems to be perfect : I mean "accept" and "proceed" are accepted. BTW, it installs itself on "hda6", is it normal (I have deleted the old partition table using fdisk linux)?
 But during the install procedure, the LAST package, called zlib-1.1.3-5, size 61k, crashes the install with a "signal 7" error !!!!

What is a signal7 error ? Is it a physical drive problem ?

The full screen printing is :

(written in red)
install exited abnormally -- recieved signal 7
sending terminations signals...done
sending kill signals...done
unmouting filesystems...
 /tmp/rhimage
 /mnt/boot
 /mnt/proc
 /proc
 /mnt
you may safely reboot your system.

[Joseph Morrison]

Hello Laurent,

Sorry to hear this! During the installation procedure, you can find out a bit more about what's going on by typing: Ctrl-Alt-F2, Ctrl-Alt-F3, and Ctrl-Alt-F4. The main installation runs on Ctrl-Alt-F1. Do the other screens show any error messages? That might provide a clue as to what's going on.

The rest of what you reported sounds normal. The TRANS.TBL files are normal. And yes, the / partition is on /dev/hda6.

Also, did you get to the point where it asked you to make an emergency boot floppy? If so, that might be useful.

Best regards,
- Joseph Morrison

[Laurent]

Unfortunatly, I didn't get to the point of the em-disk...
Ctrl+Alt F2 shows a blank screen, F4 & F5 nothing interesting.

But with F3 :
...<6> install uses obsolete /proc/pci interface
<7> iso 9660 Extensions : Microsoft Joliet Level 3
<7> iso 9660 Extensions : RRIP_1991A

And the treasure when the signal 7 happens :

<4>hdc : tray open (uh ! :O
<4>end_request : I/O error, dev 16:00 (hdc), sector (different numbers)
(about 20-30 lines with that error)
There is also a "Writing beyond limits" text error but it happens too fast too read it.

->CDR copy error ?

I've tried out one hour ago another HDD, a 540 megs one, and the error still remains.

The fact is that that signal 7 error only happens with the LAST package, Time remaining : 3 seconds (!!!). I don't think my download was corrupted, because it unzips without any kind of problem. The CDR has no stripes, it's a Philips one, and I've also tried with a Verbatim one : same problem.



.___.

[Joseph Morrison]

Hello Laurent,

> <4>hdc : tray open (uh ! :O <4>end_request : I/O
> error, dev 16:00 (hdc), sector (different numbers) (about 20-30
> lines with that error) There is also a "Writing beyond
> limits" text error but it happens too fast too read it.

Sounds very much like a bad CD-R. /dev/hdc is your CDROM drive, and it sounds like something is going wrong at a very low level.

As you say, your download is probably fine since you can unzip without any trouble. Do you have any other software for burning CDs? Or perhaps an option needs to be set differently on your CD burning software.

As a last resort, you can always order our printed CD and manual for US $40 plus shipping.

Good luck!
- Joe

[Laurent]

Grrrrrrr...

I finally managed to download a 30-days release of CDRWin37, limited to 1X-recording speed. And it worked fine with the *.iso file ! (even if i still have the "<.....table>" file in all of the cd folders).

During the install procedure, pressing Alt+F2 now prints a bash command line, and before it didn't (that's why I said there was a "blank screen").

Works great ! Configuration is quite simple, cool
1st reproch : (!) is there a way to know at which speed we're connected to the net, and for how many time ? (because in France internet phone calls are expensive).

Thanks

[Charlie Brady]

Laurent wrote:

> is there a way to know at which speed we're
> connected to the net, and for how many time ? (because in
> France internet phone calls are expensive).

At the moment there is no built-in way.

You can more or less tell the speed of the connection by pinging a close neighbour over the link.

You can analyse the connected time by looking in /var/log/messages for lines from pppd. "grep pppd /var/log/messages" will show you connect and disconnect times.

It might make sense for you to analyse your telco and ISP costs - maybe you should adjust some of the diald parameters to get the best economy on your connection. See the diald documentation under /usr/doc/diald* for details. If you do, please write up your results and email them to devinfo@e-smith.net.

Thanks

Charlie