On Thu, May 30, 2002 at 09:56:02AM +0700, hangga@hotpop.com wrote:
I've loaded 8.0 on AMD 5x86 (486 class) 133Mhz with 64Mb Edo-Ram (I think you should increase memory to 128Mb for Linux with KDE), VGA 2Mb S3 Trio64V+, and 1.2Gb Hard Disk (You should have 3Gb HardDisk to install all of them). Suse and KDE 3.0 work fine on this computer. The only problem is not about the processor and motherboard chipset, because they all detected correctly.
First Problem: Suse cannot fix the Y2K compliance. Everytime I start the computer, I always set the year to 2002 from 2099. So please Mr. Suse Developer, you said that minimal requirement for this distro is i386. I think every computer from 386 until 486, have the Y2K problem.
This isn't really SuSE's problem - it's your motherboard. You can't really expect SuSE to reprogram your machine's BIOS... However, assuming the machine has a suitable network connection, you can probably get it to sync to a timeserver when it boots, which should hopefully work around the problem.
Second Problem: Suse cannot detect my soundcard. This is Creative Soundblaster ISA 16PNP, the most popular soundcard in the world! I've read the hardware database frow Suse website, they only support for Soundblaster 32, 64, and above.
I'm sure that it should support the SB16. However, ISA PNP stuff is a big minefield, and one in which I have little experience. I would recommend reading the manual for isapnptools, and that might help. If you're still stuck, come back and ask for help.
Third Problem: Suse cannot detect my modem. This is PCI Modem with Rockwell-Connexant HCF chipset. This is not software modem, since this modem also support slow machine like 486 system (support 33Mhz FSB). I bought this modem 1,5 years ago!! I've checked from internet, and found that the driver for this modem still in beta version. Connexant still develop the driver for linux.
Just because the modem is 1.5 years old, doesn't mean it's a hardware one. Winmodems have been around for longer than that. Also the fact that it needs a driver makes me think that it might be a software modem. However, assuming you are correct, and it is a hardware modem... Run dmesg | less, and look for where the kernel detects your serial ports (it should look something like "ttyS0 IO=0x0238, IRQ=4 is a 16550A". Look to see if the serial port for your modem is listed). If it is listed, then start up minicom on that port, and see what happens when you send it "AT". If you get an "OK" in response, then your modem is there. If you don't, then something is going wrong with with either your serial port detection/settings, or the modem itself. HTH... -- David Smith | Tel: +44 (0)1454 462380 Home: +44 (0)1454 616963 STMicroelectronics | Fax: +44 (0)1454 617910 Mobile: +44 (0)7932 642724 1000 Aztec West | TINA: 065 2380 Almondsbury | Work Email: Dave.Smith@st.com BRISTOL, BS32 4SQ | Home Email: David.Smith@ds-electronics.co.uk