| 1 |
Mick wrote: |
| 2 |
> Can you set in your BIOS which controller IDE or SATA manages the |
| 3 |
> drives? I'm not sure why you have a symlink to your /usr/src/linux |
| 4 |
> files from /boot (I don't understand it). In /boot you should have the |
| 5 |
> image files themselves of your desired kernels (plus corresponding |
| 6 |
> System and .config files). |
| 7 |
|
| 8 |
I can but it seems to do the same thing either way. I don't reboot much |
| 9 |
so maybe it is something in my head. I'm pretty sure it used to list |
| 10 |
the drives on the main BIOS screen then when the controller screen comes |
| 11 |
up it detects them for AHCI. What gets me is them not being seen while |
| 12 |
I am in the BIOS itself. I know it used to see them there. Whenever I |
| 13 |
add a drive or something, I check to make sure it sees everything |
| 14 |
correctly before I even boot my OS. That way if I have a bad cable or |
| 15 |
forgot to connect something, I can fix it without booting and having to |
| 16 |
shutdown again. Saves time. |
| 17 |
|
| 18 |
I copy my kernels by hand. Always have. It appears that under arch is |
| 19 |
x86 and x86_64 and I copied from x86_64. Thing is, that is only a |
| 20 |
symlink to x86 so it becomes a link in /boot instead. Well, when grub |
| 21 |
tries to follow the link, root is not mounted yet and it can't see the |
| 22 |
file. So, this one was on me. I got to remember not to copy from the |
| 23 |
x86_64 even tho I have a 64 bit rig. |
| 24 |
|
| 25 |
Still puzzled about cfdisk tho. I did google and it appears to be quite |
| 26 |
common. I may make a backup to my spare drive and redo the partitions |
| 27 |
then copy back again. I used cfdisk to create them so one would think |
| 28 |
it could read them too. |
| 29 |
|
| 30 |
Weird. |
| 31 |
|
| 32 |
Dale |
| 33 |
|
| 34 |
:-) :-) |
Archives