zamri wrote: > > Jeff, > > I had experiences the same problem with bering 1.2 as you did a > couple of week ago and after a couple of 'try and error' I had > guess that it was a hardware problem ( mine was probably a NIC problem > ). > > What I encountered is, the system works fine if I unplug the network > cable but will pop-up the kernel panic messages if I plug the cable > on NIC. Maybe anyone on the list could explain this :) > > I still don't know the exact problem why this was happen > ( since using all this NIC on M$ machine works just fine ) > > My system was IBM 300PL with pentium II 350Mhz and 128MB RAM. > Problem NIC was D-Link 538TX with rtl8139 chipset.
Hi Zamri, You will probably have to go into details with your "trial and error" bit. :) If you take a look at your local D-Link web page you will see that there is no available Linux support for your specific NIC: http://www.dlink-intl.com/technical/drivers.nsf/LAN+Adapters+on+web?OpenView&Start=1&Count=30&Expand=14#14 although Windows support abounds everywhere. It's usually better to just buy one of the common cards which has lots of driver support. If someone asks me if their network card has support with Linux there is usually two places to look at as references, the documentation that is shipped with the kernel that the person will be using and Donald Becker's site http://www.scyld.com/network/ - if it's not listed there then it's a good time to try writing one's own driver! :) There are so many ways in getting kernel panics but Jeff's own problems remind me of a time when I was installing Slackware with the 2 floppy disk setup, before the bootable CD iso's started coming out. The first disk was the bootdisk with the kernel loading then when that was finished one was prompted with the second disk, the rootdisk. It happened at times that I got a kernel panic because the root filesystem was corrupted when its loading was finished, the problem being that the floppy had physical errors. Switching from the standard 1440 to 1680 and vice versa, formatting them back and forth, made them go berserk! :) The line where he is starting to have problems is where virtual space is addressed. Since I didn't gather if Jeff was using one floppy drive on one machine and two drives on the other I would suspect that the problem could be having to do with the line: PKGPATH=/dev/fd0u1680,/dev/fd1u1680 where he may have needed the diskwait=yes option instead, used for the single floppy drive setup. http://leaf.sourceforge.net/doc/guide/bubooting.html which sort of reminded me of my own previous problems...that's just guessing, though. Regards, -- Patrick Benson Stockholm, Sweden ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
