Slack 13: I messed things up
How did it all go so wrong?
PC (Q6600 2GB) with dualboot using lilo on mbr: - Slackware 12.2 (private life) - Vista Business (work related) Upgraded 12.2 via slackpkg. Went wrong: X was killed; something to do with the Nvidia driver that went bust. hmm.. time to try Slack 13, as I have the DVD laying around, but never found the need/time to upgrade. Installed Slackware 64 13, on new partitions. I had some space left on the disk :) ( new / and /home ) / in ext3 for compatibility towards 12.2 Did do a lilo install from within installation, since I thought this might work.. did fail on a table-error. Fixed by editing the lilo.conf and running lilo from within 12.2. Now I have 2 non-running slackware installations: - Slack 12.2 -> Loads with 4 devils instead of penguins: Damn: upgraded kernel? Yes: it loads a 64bit kernel! x is dead, can't do anything: 64bit kernel within slack32 :) - Slack 64 13 -> unable to determine tty1 name (or similar) error: loads the right kernel, but I can't login! How to fix things? Is my lilo.conf wrong? ( I guess ) and how did slack 12.2 lost it's capability to run X in the first place. Did I do something wrong with the slackpkg update/grade thingy? wrong mirror so I updated a 64bit with 32bit sources? that would be plain wrong.. And: If I re-install 13, (since it's still quite empty, it's probably the best) could I use ext4, or will /home be inaccessable from 12.2 ( if I can reanimate that installation ) |
Quote:
|
Quote:
Anywayz; I did do a reinstall of Slackware64 13 and got things going again.. Lilo didn't go that smooth, but I did manage to boot with the DVD and install Lilo afterwards. |
All times are GMT -5. The time now is 08:26 AM. |