Adam Williamson wrote: > Hi there, just thought i'd report on my experiences installing Cooker in > case it's of any use to anyone. Decided to do so because my 8.2 > installation was a bit messed up (my fault) and i'd installed quite a > lot of stuff from Cooker on it anyway. I did this all yesterday (June > 19) using the Cooker stuff available at ftp.ciril.fr . > > I didn't have any 700mb CDs handy so I couldn't really use the ISO > images to do a CD install, so I decided to try an FTP-based > installation. I wrote the boot floppy for this, booted it up, and found > it just doesn't work - it gives the installation screen, so I do F1 and > 'expert'. It lets me set up my network stuff, which judging from the > console output runs fine, then as soon as it's brought up the network > the system crashes, reporting "install terminated abnormally - received > signal 11" or something like that. Same happens despite twiddling with > the networking setup and trying HTTP install. So I gave up on that, > downloaded the whole tree to my hard disk (thank heavens for ADSL) and > tried a hard disk install instead. > > Had much more success with this - the installation went almost as > flawlessly as with 8.2. I used the same partitioning scheme as my 8.2 > installation, with a 500 meg root partition, 400 meg swap partition (I > have 192mb RAM) and two 7 gig partitions for /home and /usr. All > hardware setup went flawlessly. However, during package installation a > number of packages reported problems. In a rare burst of sense, I noted > down the names of all the packages in case it'd be of use later. The > ones that gave errors were: > > libdb3.3 > urpmi > gurpmi > bonobo-activation > libbonobo-activation > esound > libesound > samba-common > gedit > gnome-guile > glaxium > ltris > memprof > tuxpuck > > The upshot of this was an almost functional installation ;). The system > boots pretty much cleanly, but it wouldn't start GNOME at all (my guess > is this was to do with the bonobo-activation errors). KDE3 started OK, > though, so I decided to use that and see if I couldn't fix GNOME (GNOME > is my standard desktop). I started KDE and decided to try a couple of my > favourite applications, Evolution and Galeon, which also failed to work. > As did Mozilla. At this point I went back to the list of failed packages > and decided to do something about those. Several of them appeared to be > missing from the download directory entirely, though I can't see how I > could have missed downloading them (I used ncftpget with the -R switch > to download the entire Cooker tree). I downloaded the missing ones and > reinstalled them all (except glaxium, ltris, memprof and tuxpuck which I > haven't got around to doing yet); all installed without errors, which > wasn't what I was expecting. I tried Mozilla, Galeon and Evolution > again, but with no luck. > > So I thought i'd see if GNOME had got fixed and if they'd work in that. > GNOME was indeed fixed, and started up happily (GNOME2 is nice, isn't > it?), but the three programs still weren't working. (By 'not working', I > just remembered to mention, I mean that running Mozilla produced no > obvious errors but it just didn't load at all - when run from a console, > the console went back to a prompt after a couple of seconds and gave no > output at all; Galeon would crash with a segmentation fault on startup; > and Evolution complained about not being able to find ConfigDatabase). > So I uninstalled and reinstalled all three (using RPM), which - I was > surprised but happy to find - worked perfectly, and all three are now > running happily. Finally I installed NVIDIA's linux drivers, which was a > much happier experience than it was under 8.2. I compiled them from > source and they installed almost perfectly - only glitch was the actual > loading of the driver kernel module. NVIDIA's 'make install' script adds > a 'modprobe NVdriver' line to the end of rc.modules; for some reason > this didn't turn up on its own line but appended itself to the final > line of the original file, making it 'donemodprobe NVdriver' instead of > just 'done', which obviously wasn't helping anything. So I returned > rc.modules to its original state and added a line just reading > 'NVdriver' to /etc/modules and everything now works fine. > > So overall i'm quite impressed - with just that relatively minor bit of > twiddling I now have a very functional installation, and I have GNOME2 > to play about with :). Thanks a lot to the Cooker team, and hope some of > the above is helpful to someone. > > System specs are: > > Gigabyte GA-7IXEH motherboard (KT133E chipset) > Duron 1GHz (Morgan core) running at 1.1.GHz (100MHz FSB) > 192MB RAM (PC133, CAS2) > Asus V6600 Deluxe graphics card (Geforce 1 SDR) > 2x IDE hard disks (one 17gig, one 20gig) > DVD drive > Sony CDRW drive (which seems to be setup perfectly, great job!) > 10/100Mbit network card (uses tulip driver) > Soundblaster 16 PCI soundcard (uses an Ensoniq chip) > Microsoft Intellimouse Optical (USB connected) > Genius keyboard (PS/2 connected) > Daewoo 15" monitor (yes, Daewoo. The people who make cars. I have no > idea why. We got it cheap from some dodgy shop in Manchester...) > > And since I don't have a floppy drive in this system, I used the USB one > from my Sony Vaio C1XD to run the bootdisks. I'm not trying Cooker on > that just yet though, I don't think :). (It runs SUSE at the moment). > > Again, big thanks to the team, and I hope this is the right place to > send this and that someone finds it useful. Bye!
Haj, Had this problem a while ago, didn't think it's still there. Try not to set a hostname when asked. Just hit Enter on that one and go on with the default name. That always works here. If my solution does work, then maybe we have a little bugz0rz. Have fun, boban Göteborg, Sweden.
