1 |
Walter Dnes <waltdnes@××××××××.org> wrote: |
2 |
|
3 |
> I just finished installing Gentoo on an older AMD laptop. There was |
4 |
> one major problem that I hacked around, and things appear to be working |
5 |
> OK, but I still get warnings when installing lilo. |
6 |
> |
7 |
> When I first did the install, I got the warning message... |
8 |
> "Could not determine root partition!". I ran lilo and rebooted, but got |
9 |
> a kernel panic, because the kernel couldn't find the boot device. I dug |
10 |
> into this. Apparently the lilo ebuild tries to outsmart the user, and |
11 |
> figure out the root partition itself, with the bash syntax... |
12 |
> |
13 |
> rootpart="$(mount | grep -v "tmpfs" | grep -v "rootfs" | grep "on / " | cut -f1 -d " ")" |
14 |
> |
15 |
> I don't know if I screwed up during the install, but *IN THE CHROOT*, |
16 |
> mount returns a null string. I remembered vaguely that "mount" returns |
17 |
> the contents of /etc/mtab. I looked at it, and /etc/mtab was also |
18 |
> empty. I applied the "rootpart=" stuff against another machine, and |
19 |
> found out which line it homed in on. I manually edited /etc/mtab in |
20 |
> the chroot, inserting the short line... |
21 |
> |
22 |
> 805 |
23 |
> |
24 |
> ...Then I emerged lilo again. This time I got... |
25 |
> |
26 |
> ##################################################################### |
27 |
> >>> Installing (1 of 1) sys-boot/lilo-23.2-r2 |
28 |
> |
29 |
> * Checking for LILO ... Yes, on /dev/sda |
30 |
> * Running DOLILO to complete the install ... |
31 |
> You can move /etc/conf.d/dolilo.example to /etc/conf.d/dolilo and edit it to set your preferences. |
32 |
> fdisk: cannot open 80: No such file or directory |
33 |
> fdisk: cannot open 80: No such file or directory |
34 |
> Bootsector updated succesfully. |
35 |
> ##################################################################### |
36 |
> |
37 |
> The important part is that the laptop now boots up OK. However, when I |
38 |
> re-install lilo, on the natively-booted laptop, I still get the above |
39 |
> messages. I'm using the same partitioning scheme and fstab that I've |
40 |
> been using for years without problems. Here they are... |
41 |
> |
42 |
> outfput from "fdisk -l" |
43 |
> ##################################################################### |
44 |
> Disk /dev/sda: 320.1 GB, 320072933376 bytes, 625142448 sectors |
45 |
> Units = sectors of 1 * 512 = 512 bytes |
46 |
> Sector size (logical/physical): 512 bytes / 512 bytes |
47 |
> I/O size (minimum/optimal): 512 bytes / 512 bytes |
48 |
> Disk identifier: 0x612cf108 |
49 |
> |
50 |
> Device Boot Start End Blocks Id System |
51 |
> /dev/sda1 2048 625142447 312570200 5 Extended |
52 |
> /dev/sda5 4096 618495 307200 83 Linux |
53 |
> /dev/sda6 620544 17397759 8388608 83 Linux |
54 |
> /dev/sda7 17399808 625142447 303871320 83 Linux |
55 |
> ##################################################################### |
56 |
> |
57 |
> /etc/fstab |
58 |
> ######################################################################### |
59 |
> /dev/sda5 / ext2 noatime,nodiratime,async 0 1 |
60 |
> /dev/sda7 /home ext3 noatime,nodiratime,async 0 1 |
61 |
> /home/bindmounts/opt /opt auto bind 0 0 |
62 |
> /home/bindmounts/var /var auto bind 0 0 |
63 |
> /home/bindmounts/usr /usr auto bind 0 0 |
64 |
> /home/bindmounts/tmp /tmp auto bind 0 0 |
65 |
> /dev/sda6 none swap sw 0 0 |
66 |
> /dev/cdrom /mnt/cdrom iso9660 noauto,users,ro 0 0 |
67 |
> /dev/sr0 /mnt/dvd auto noauto,users,ro 0 0 |
68 |
> |
69 |
> devpts /dev/pts devpts defaults 0 0 |
70 |
> ######################################################################### |
71 |
> |
72 |
> Any ideas? |
73 |
|
74 |
I don't let theebuild muck with lilo.conf,I edit it myself, so the root |
75 |
is no problem -- its an initrd anyway. |
76 |
|
77 |
|
78 |
-- |
79 |
Your life is like a penny. You're going to lose it. The question is: |
80 |
How do |
81 |
you spend it? |
82 |
|
83 |
John Covici |
84 |
covici@××××××××××.com |