|
Ok results of requested commands. I don’t think I have a boot
partition as such. Fdisk –l gave me nothing, no error, just goes to next
prompt. [EMAIL PROTECTED]:/boot# ls config-2.4.27-2-386 initrd.img-2.4.27-2-386 vmlinuz-2.4.27-2-386 grub
System.map-2.4.27-2-386 [EMAIL PROTECTED]:/boot# cd grub [EMAIL PROTECTED]:/boot/grub# ls device.map
fat_stage1_5
menu.lst
reiserfs_stage1_5 stage2 e2fs_stage1_5 jfs_stage1_5 minix_stage1_5 stage1
xfs_stage1_5 [EMAIL PROTECTED]:/boot# mount /dev/hda1 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) devpts on /dev/pts
type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/hda3 on /cache type ext2 (rw) /dev/mapper/mythvg-mythvid
on /myth type ext3 (rw) /dev/hda6 on /myth/mythtvburn
type ext3 (rw) /dev/hda5 on /usr
type ext3 (rw) usbfs on /proc/bus/usb type usbfs (rw) It appears, like everthing
else with linux, Grub has outgrown a single config file and has fragmented them into a hundred (well
12) pieces. The docs have not
caught up yet leaving me in confusion yet again. I found something in X that let me config boot params. Extrapolating from another post that
mentioned adding the video param to the grub boot
screen makes me think I can just put it after the “root=/dev/hda1 ro” in the parameters box. Will this work? Or more precisely will this fubar my boot if it doesn’t work. As long as I can fix it I will try it. Thanks -----Original Message----- On 03/12/05, Brent
Kilgore <[EMAIL PROTECTED]>
wrote:
The other likely reason would be that your system's
using Lilo, that should become evident from the ls -l /boot command. |
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
