That is the same thing I've found It has nothing to do with processor power its just finding a video card and NIC that will work well with it
I've made the same call here for us If it doesn't have PCI slots it is gone Anyone else? > -----Original Message----- > From: Jeff Roberts [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, March 26, 2002 8:59 AM > To: [EMAIL PROTECTED] > Subject: [Ltsp-discuss] usablility of 486 Was:Nothing happens after kernel > boot > > This post got me wonerding something again. In all of your opinions,Is > the > performance/quality of a low-end 486 worth the trouble of getting it to > work? > > I tried a few when I was first installing ltsp and I wasnt satisfied with > the video. It was also harder to get them to work. The availability of the > cheap linksys pci adapter with a boot rom installed encouraged me to find > more pci systems. I decided not to use anything that didnt have pci slots > as my cut off point. It cost me very little to replace the isa systems > with > slightly less older pci capable systems. > > I do have quite a few of these ancient systems packed away now. Most of > them > only have 8 megs of ram an 1 meg isa video. My experience was that the > cost > of more ram and better vlb or isa video was almost as much as a new/used > pci > system. > > Has anyone else had any better experience trying to use machines older > than > this, or have you had the same problems that I did? > > -Jeff > > > Micha, > > > > The problem is 4mb of ram is NOT enough. > > > > To get booted, the workstation needs to load the kernel > > and the initrd image into ram. It needs more than 4mb > > to do that. > > > > It is possible to build a Linux kernel that doesn't need > > the initrd. you would have to pick your network card > > driver and compile it in, rather than making it a module. > > > > There is some information on kernel building in the LTSP-3.0 > > documentation. > > > > Jim McQuillan > > [EMAIL PROTECTED] > > > > > > On Tue, 26 Mar 2002, [iso-8859-2] Micha³ Fryska wrote: > > > >> > >> Hi all. > >> > >> I'v got a problem with my workstation, that "hangs up" after booting > >> the kernel from server. It looks like it cannot start NFS, but it > >> gives me no error messages. Neither on workstation, nor in system logs > >> on server. > >> > >> The workstation is very "poor" ;-) cos it's 486SX/40MHz, 4MB Ram, > >> 3C509 ISA, Trident 512Kb ISA, but i think it should work with Linux at > >> all. The server (PIII 933, 128Kb - for now) runnig Mandrake 8.1. > >> > >> Everything goes well. It gets reply from dhcp, gets the kernel from > >> tftp, starts loading... > >> > >> Whole messages look OK. This are only a few last ones: > >> > >> [....] > >> RAMDISK: Compressed image found at block 0 > >> Freeing initrd memory: 452k freed > >> VFS: Mounted root (ext2 filesystem). > >> Freeing unused kernel memory: 68k freed > >> > >> It stops here and nothing happens. > >> > >> Here's my configuration: > >> Server A - running dhcpd > >> Server B - running the other nessesary services for LTSP. > >> > >> --- /etc/dhcpd.conf begin > >> ddns-update-style ad-hoc; > >> default-lease-time 21600; > >> max-lease-time 21600; > >> option subnet-mask 255.255.255.0; > >> option broadcast-address 192.168.1.255; > >> option routers 192.168.1.1; > >> option domain-name-servers 192.168.1.1; > >> option domain-name "pewik"; > >> option root-path "192.168.1.13:/home/ltsp/i386"; > >> option option-128 code 128 = string; > >> option option-129 code 129 = text; > >> > >> shared-network WORKSTATIONS { > >> > >> subnet 192.168.1.0 netmask 255.255.255.0 { > >> range 192.168.1.200 192.168.1.250; > >> option broadcast-address 192.168.1.255; > >> } > >> > >> subnet 192.168.2.0 netmask 255.255.255.0 { > >> range 192.168.2.200 192.168.2.250; > >> option broadcast-address 192.168.2.255; > >> } > >> > >> subnet 192.168.3.0 netmask 255.255.255.0 { > >> range 192.168.3.200 192.168.3.250; > >> option broadcast-address 192.168.3.255; > >> } > >> } > >> > >> host 3com3300w { > >> hardware ethernet 00:50:99:21:E8:98; > >> fixed-address 192.168.1.8; > >> } > >> > >> group { > >> use-host-decl-names on; > >> option log-servers 192.168.1.13; > >> next-server 192.168.1.13; > >> > >> host ws001 { > >> hardware ethernet 00:20:af:05:63:a9; > >> fixed-address 192.168.1.99; > >> filename "vmlinuz-2.4.9-ltsp-5"; > >> option option-128 e4:45:74:68:00:00; > >> option option-129 "NIC=3c509"; > >> } > >> } > >> > >> --- /etc/dhcpd.conf end > >> > >> --- /etc/exports begin > >> /home/ltsp/i386 > >> 192.168.1.0/255.255.255.0(ro,no_root_squash) > >> /var/opt/ltsp/swapfiles > >> 192.168.1.0/255.255.255.0(rw,no_root_squash) > >> > >> --- /etc/exports end > >> > >> --- /etc/hosts begin > >> 127.0.0.1 localhost.localdomain localhost > >> 192.168.1.13 elrond.pewik elrond > >> 192.168.1.99 ws001.pewik ws001 > >> > >> --- /etc/hosts end > >> > >> Any ideas? > >> > >> Szum. > >> > >> > >> > >> > >> _____________________________________________________________________ > >> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > >> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > >> For additional LTSP help, try #ltsp channel on irc.openprojects.net > >> > > > > -- > > > > > > _____________________________________________________________________ > > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > > For additional LTSP help, try #ltsp channel on irc.openprojects.net > > > > _____________________________________________________________________ > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > For additional LTSP help, try #ltsp channel on irc.openprojects.net _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
