LarsB

Thanks Gowator for your response. It is not the firewall, that problem was there before I activated it. So the question remains, if it is writing to the log all the time, then why is it doing that. I did not have this "feature" on Mandrake 9,0. What about EXT3 I think I used ReiserFS on 9.0. Reards Lars

Have you tried 16 bit, my Toshiba was hopeless with 24 bit

Start of first psot from Lars Hello, any advice concerning this. I have a download 9.2 on a Toshiba Tecra laptop. Used 9.0 before (without any greater problems). The install did not accept CD2, so right now it's a CD1 installation. The HD does something all the time (for no apparent purpose) Does this dump tell anybody anything. Feb 4 15:26:34 localhost kernel: 80.186.57.248 sent an invalid ICMP type 3, code 3 error to a broadcast: 80.186.59.255 on eth0 Feb 4 15:27:36 localhost last message repeated 2 times Feb 4 15:28:03 localhost kernel: Shorewall:net2all:DROP:IN=eth0 OUT= MAC=00:30:bd:01:64:f4:00:90:1a:40:1f:db:08:00 SRC=80.183.89.136 DST=80.186.57.248 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=8441 DF PROTO=TCP SPT=3576 DPT=4480 WINDOW=16384 RES=0x00 SYN URGP=0 Feb 4 15:28:06 localhost kernel: Shorewall:net2all:DROP:IN=eth0 OUT= MAC=00:30:bd:01:64:f4:00:90:1a:40:1f:db:08:00 SRC=80.183.89.136 DST=80.186.57.248 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=8647 DF PROTO=TCP SPT=3576 DPT=4480 WINDOW=16384 RES=0x00 SYN URGP=0 Feb 4 15:28:07 localhost kernel: 80.186.57.248 sent an invalid ICMP type 3, code 3 error to a broadcast: 80.186.59.255 on eth0 Feb 4 15:28:38 localhost kernel: 80.186.57.248 sent an invalid ICMP type 3, code 3 error to a broadcast: 80.186.59.255 on eth0 Feb 4 15:29:40 localhost last message repeated 2 times ..... Feb 4 16:03:46 localhost kernel: 80.186.57.248 sent an invalid ICMP type 3, code 3 error to a broadcast: 80.186.59.255 on eth0 Feb 4 16:04:17 localhost kernel: 80.186.57.248 sent an invalid ICMP type 3, code 3 error to a broadcast: 80.186.59.255 on eth0 Feb 4 16:05:19 localhost last message repeated 2 times Feb 4 16:06:21 localhost last message repeated 2 times Feb 4 16:07:23 localhost last message repeated 2 times Feb 4 16:08:25 localhost last message repeated 2 times Feb 4 16:09:27 localhost last message repeated 2 times Feb 4 16:10:29 localhost last message repeated 2 times Feb 4 16:11:31 localhost last message repeated 2 times Feb 4 16:12:33 localhost last message repeated 2 times Feb 4 16:13:35 localhost last message repeated 2 times Feb 4 16:14:37 localhost last message repeated 2 times Feb 4 16:15:39 localhost last message repeated 2 times Feb 4 16:16:41 localhost last message repeated 2 times Feb 4 16:17:43 localhost last message repeated 2 times Feb 4 16:18:45 localhost last message repeated 2 times Feb 4 16:19:47 localhost last message repeated 2 times Feb 4 16:20:49 localhost last message repeated 2 times Feb 4 16:21:51 localhost last message repeated 2 times Feb 4 16:22:53 localhost last message repeated 2 times Feb 4 16:23:55 localhost last message repeated 2 times Feb 4 16:24:57 localhost last message repeated 2 times Feb 4 16:25:59 localhost last message repeated 2 times Feb 4 16:26:05 localhost dhclient: DHCPREQUEST on eth0 to 212.54.0.225 port 67 Feb 4 16:26:05 localhost dhclient: DHCPACK from 212.54.0.225 Feb 4 16:26:05 localhost dhclient: bound to 80.186.57.248 -- renewal in 1793 seconds. Feb 4 16:26:30 localhost kernel: 80.186.57.248 sent an invalid ICMP type 3, code 3 error to a broadcast: 80.186.59.255 on eth0 Feb 4 16:27:01 localhost kernel: 80.186.57.248 sent an invalid ICMP type 3, code 3 error to a broadcast: 80.186.59.255 on eth0 Feb 4 16:28:03 localhost last message repeated 2 times Feb 4 16:28:07 localhost drakconf.real[3008]: ### Program is starting ### What about the shorewall information. In general about the installation: The 9.0 did not recognize the Belkin PCMCIA card (had to do some editing) the 9.2 had no problems. Both 9.0 and 9.2 suggest 24 bit for the screen, should be 16 bit. On 9.0 I was never able to get my poor Canon BJC-1000 to work. (I gave up). On 9.2 it works OK. (In my experience it is always best to have all hardware connected during install, rather than trying to do it later) The sound piece is not detected but it is possible to do it later with sndconf (with a trial and error method). End of frist post from Lars. (www.theregister.co.uk/content/archive/23452.html)