Re: [Cooker] Cooker glitches - Follow up
- Original Message - From: Pixel <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 21, 1999 10:13 AM Subject: Re: [Cooker] Cooker glitches - Follow up > "Hoyt" <[EMAIL PROTECTED]> writes: > > lilo also failed, with a cylinder too big message. This was probably my > > fault as I was installing to a partition above 1024 cylinders and did not > > provide for a /boot partition below that since I wanted to see what would > > happen. Of course, had I been able to make a boot disk, this would not have > > ben an issue, but I wanted to see what the install program would do in this > > case since larger hard drives are becoming more common. > > didn't diskdrake told you you were running into problems? > Of course, but I "knew" what I was doing; I just wanted to see what would happen; your typical newbie is not too aware of the 1024 cylinder limit and may just have a large disk. (I have a 13G hda and 6.4G hdb; hda has 16 partitions - I boot three different Linux distros, Win98 and BeOS). Everything would have been fine if I could have made a bootdisk (I could also use loadlin from DOS/Windows, but I would need a copy of the kernel that isn't available until after the install. It would be nice to be able to have the install program copy the kernel to /dev/ha1, typically the c:\ drive on a dual boot system, or have a copy on the CD - I know you have -lots_ of space left, but matbe when you get to 2 CDs?). Perhaps a specefic warning that lilo _will_ not run successfully if /boot is above the limit? I recall that the warning given was pretty general. But, this was not a cooker problem, just a generic Linux/lilo thing. Hoyt
Re: [Cooker] Cooker glitches - Follow up
"Hoyt" <[EMAIL PROTECTED]> writes: [...] > very difficult to read. It would be nice for numlock to be turned on by > default for data enrty, but I know what a pain the numlock thing can be with > X. very hard. > It was very nice to have the option of _no_ password - who really needs > one on a home system anyway? Since I was able to get through all the install > screens, I must say I am very impressed with what you guys have done. > > I did have other problems. > > mkbootdisk failed with an error message about install_steps_gtk.pm line 50. > I tried mkbootdisk after I rebooted cooker with a rescue disk and it failed > because awk (gawk) was not installed; installing that package fixed it. ok thanks a lot :) fixed the missing requires > > lilo also failed, with a cylinder too big message. This was probably my > fault as I was installing to a partition above 1024 cylinders and did not > provide for a /boot partition below that since I wanted to see what would > happen. Of course, had I been able to make a boot disk, this would not have > ben an issue, but I wanted to see what th einstall program would do in this > case since larger hard drives are becoming more common. didn't diskdrake told you you were running into problems? > > I was able to boot cooker from a rescue disk from the Peanut distro ( I like > it because it has mc available on the boot floppy). Giving the lilo command > root=/dev/hda12 (my cooker install partition) booted me up in cooker with a > few non-fatal kernel compatability messages and allowed me to debug > mkbootdisk and install gawk and create a boot disk, then boot "for real". > > I had a problem with KDE in that kfm would not run; KDE would start and I > would see a blank desktop and was unable to run programs. I used alt-F2 to > bring up the command line and ran xterm and started kfm from it to see the > error messages. It seems that libjpeg.so.62 and libtiff.so.3 were not > installed automagically. Installing them brought kfm to life. that's strange as kdebase requires libjpeg and libtiff... can you mail me: - /root/ddebug.log - /root/install.log - /root/auto_inst.cfg.pl - Mandrake/base/depslist > > Some of the drakconf packages also did not get installed automagically (like > sound), but I have not fixed that yet. As I try to make things work one by > one, I'll keep a list of what did not install if that will be helpful to > you. > i'm waiting for your remarks! > Still, overall, a nice job. > thanks :)
Re: [Cooker] Cooker glitches - Follow up
I downloaded tthe updated /mdkinst over the weekend. That seems to have gotten me past the mouse problems. The error message for that one was: Gdk-Warning **:shmget failed! at /usr/bin/perl-install/install_steps_gtk.pm line 752. But as I said, I got past that, and my generic PS/2 mouse worked just fine. Other observations: In the package install screen, the use of color to deliniate packages that are part of the base install, selected packages and unselected packages is a very good idea, but initially confusing without a key to tell me what it was I was seeing. Some of teh script was doubled and slightly offset and was very difficult to read. It would be nice for numlock to be turned on by default for data enrty, but I know what a pain the numlock thing can be with X. It was very nice to have the option of _no_ password - who really needs one on a home system anyway? Since I was able to get through all the install screens, I must say I am very impressed with what you guys have done. I did have other problems. mkbootdisk failed with an error message about install_steps_gtk.pm line 50. I tried mkbootdisk after I rebooted cooker with a rescue disk and it failed because awk (gawk) was not installed; installing that package fixed it. lilo also failed, with a cylinder too big message. This was probably my fault as I was installing to a partition above 1024 cylinders and did not provide for a /boot partition below that since I wanted to see what would happen. Of course, had I been able to make a boot disk, this would not have ben an issue, but I wanted to see what th einstall program would do in this case since larger hard drives are becoming more common. I was able to boot cooker from a rescue disk from the Peanut distro ( I like it because it has mc available on the boot floppy). Giving the lilo command root=/dev/hda12 (my cooker install partition) booted me up in cooker with a few non-fatal kernel compatability messages and allowed me to debug mkbootdisk and install gawk and create a boot disk, then boot "for real". I had a problem with KDE in that kfm would not run; KDE would start and I would see a blank desktop and was unable to run programs. I used alt-F2 to bring up the command line and ran xterm and started kfm from it to see the error messages. It seems that libjpeg.so.62 and libtiff.so.3 were not installed automagically. Installing them brought kfm to life. Some of the drakconf packages also did not get installed automagically (like sound), but I have not fixed that yet. As I try to make things work one by one, I'll keep a list of what did not install if that will be helpful to you. Still, overall, a nice job. By the way, I have a few suggestions for a few improvements in /dosutils. Who is handling that for Mandrake? Hoyt
