Lilo issue with two linux dristros (Slack 13.1 and UbuntuStudio 10.4)
Hi All,
Need a little help here.... After giving up on Ubuntu and Unity/Gnome3, I decided to come home to Slackware for normal Desktop usage. And, as always, it installed and runs great. However, after a few days of playing with kernels and rt patches and SlackBuilds, etc... I decided to just install Ubuntu Studio for my recording desktop because it works so well. I made a new partition for it on /dev/sda and installed. I skipped the loader install because I figured I already had lilo from Slack and I like that mush better. The issue is that Ubuntu seems to have re-ordered my drives from the order Slack used. It has moved /dev/sda to sdb...sdb to sdc.... and sdc to sda.... How is that possible??? What went wrong??? I thought the BIOS handled that.... I tried forcing the drive order in my lilo.conf: ---------- Code:
# LILO configuration file But 'lilo -t -v3 > /tmp/lilo.dump' gives the following: ---------- Code:
LILO version 22.8 (test mode), Copyright (C) 1992-1998 Werner Almesberger Where did "device codes (canonical)=7" come from? Is that normal?? Is that the problem??? Never noticed it before.... I have tried wiping the mbr with dd, and removing the map and boot files from the /boot folder. Then re-running lilo to install it. But anytime I try to boot the Studio image, the kernel swaps /dev/sda, /dev/sdb, /dev/sdc, and fails. I know I must be missing something here..... any help you can give is appreciated. Thanks, Sno |
Bump
::Bump::
|
Moderator response
Hi,
Please do not manually bump your thread unless you provide additional information; Quote:
Please use the vbcode tags # or Quote when posting long lists or data. |
Should ask in an ubuntu forum. The canonical might be an ubuntu thing (canonical is the ubuntu corp.)
out of curiosity why install 13.1? |
Quote:
As to why 13.1??? Can't stand Gnome 3/unity. Like Gnome 2.3. Gnome-Slackbuild 2.3 was only available for 13.1. 13.37 was Gnome 3. Played around with putting gsb 2.3 on Slack 13.37. Had it mostly working. But decided to just wipe it and move back to 13.1 rather then spending more time trying to get it all to work. -Sno |
I think I knew that 13.37 was using gnome3 but conveniently forgot. I don't use gnome or kde. I used to use kde but it never got better. The mindset in the gnome/kde camps seems to be "more features means better". I keep it simple/light and use fluxbox. Sorry I can't offer much on the boot problem as I don't know ubuntu. I would reduce the lilo.conf down to the bare minimum and try until some pattern emerges that might lead to a new insight. Also check the GPT is enabled, etc.
|
Hi,
Quote:
:hattip: |
Quote:
Back to my original questions.....any new ideas out there????? -Sno |
Good to know they dropped gnome. It's gone off the rails it seems.
Did you attempt my suggestions and none of them worked? What happened if you did try? Is your system shared with others? I always wondered why people ran a gdm when they were the only one using it. You may already know that you can just login on a terminal and do xinit ~/.xinitrc -- /usr/bin/Xorg |
Quote:
As to why gdm... yes, my computer is occasionally used by others (Wife, guests, children). GDM is quite useful for that. -Sno |
[Solved]....kinda
Well.... I finally got around to setting up the networking on the Ubuntu side. Upgraded the kernel and bang.... fixed... no more adding "root=/dev/sdb7" to the prompt. It orders the drives correctly.
Still not sure what was wrong with the original tho..... -Sno |
All times are GMT -5. The time now is 09:11 AM. |