[ltp] something for the experts
Behdad Esfahbod
linux-thinkpad@linux-thinkpad.org
Thu, 13 Nov 2003 06:29:26 -0500
On Thu, 13 Nov 2003, [ISO-8859-1] Andr=E9 Wyrwa wrote:
> Hi everybody,
>
> I'm having two little problems here on my T23, which keep me wondering
> and wondering...
>
> 1. Even though I thought i solved this problem, it turned out, I didn't:
> When trying to mount drives as user, which require kernel modules to
> be modprobed, they don't get modprobed automatically (namely the ones
> needed to enable scsi-ide emulation). Modprobe seems not even to be
> called by the kernel. When doing it as root everything works fine.
> Any ideas?
do cat /proc/sys/kernel/modprobe, see if it's /sbin/modprobe?
> 2. The partition table of my harddrive might be considered a bit wired,
> I have to admit:
>
> /dev/hda1 * 1 7 52888+ 83 Linux
> /dev/hda2 8 285 2101680 7 HPFS/NTFS
> /dev/hda3 286 5168 36915480 f Win95 Ext'd (LBA)
> /dev/hda4 5141 5168 211680 a0 IBM Thinkpad
> hibernation
> /dev/hda5 286 979 5246608+ 7 HPFS/NTFS
> /dev/hda6 980 3754 20978968+ c Win95 FAT32 (LBA)
> /dev/hda7 3755 3789 264568+ 82 Linux swap
> /dev/hda8 3790 4483 5246608+ 83 Linux
> /dev/hda9 4484 4761 2101648+ 83 Linux
> /dev/hda10 4762 5038 2094088+ 7 HPFS/NTFS
>
> Please don't ask why I want to have both Win2k and WinXp.
>
> What I want to do is to make my boot selection with lilo...or maybe
> grub later on, but for the time being its still lilo.
>
> I have everything set up on the linux side, I'd say, here's
> lilo.conf:
>
> boot =3D /dev/hda1
>
> install =3D /boot/boot-bmp.b
> #bitmap =3D /boot/img/logo64a.bmp
> #bmp-colors =3D 6,9,0,15,9,0
> #bmp-table =3D 59,5,1,18
> #bmp-timer =3D 66,28,6,8,0
>
> #bitmap =3D /boot/img/ins64a.bmp
> #bmp-colors =3D 14,11,,15,9,0
> #bmp-table =3D 21,287p,2,4,175p
> #bmp-timer =3D 73,29,12,8,0
>
> bitmap =3D /boot/img/ibmtp1.bmp
> bmp-colors =3D 4,0,15,1,0,15
> bmp-table =3D 60,20,1,5
> bmp-timer =3D 2,24,3,0,15
>
> vga =3D 791
> read-only
> lba32
> prompt
> timeout =3D 30
> #message =3D /boot/message
>
> append=3D"hde=3Dide-scsi"
>
> other =3D /dev/hda2
> label =3D win2k
>
> image =3D /boot/lfskernel
> label =3D lfs
> root =3D /dev/hda8
> initrd =3D /boot/initrd.splash
> append =3D "hdc=3Dide-scsi hde=3Dide-scsi hdf=3Dide-scsi idebus=3D66
> splash=3Dsilent"
> read-write
>
> image =3D /boot/lfskernel.2.4.22
> label =3D lfssave
> root =3D /dev/hda8
> read-write
>
> image =3D /boot/lfskernel.2.4.19
> label =3D failsafe
> root =3D /dev/hda8
>
> # image =3D /boot/vmlinuz.suse
> # label =3D suse
> # root =3D /dev/hda9
> # initrd =3D /boot/initrd.suse
>
> other =3D /dev/hda5
> label =3D winxp
>
> My problem is how to get rid of the stupid win bootmenu?
> If I boot to win2k (/dev/hda2), I get the boot menu with entries for
> winxp and win2k, but if i boot to winxp (/dev/hda5) it just doesn't do
> anything. I once did this already on an older system which i haven't
> anymore and i don't find the guide anymore which i followed back then.
>
> I mirrored ntldr, ntdetect.sys and boot.ini as well as arcldr.exe and
> arcsetup.exe to both win partitions. And I know what modifications I'd
> have to do to the boot.ini files, but I remember that I was supposed to
> do a call to some executable under winxp, to install the bootloader on
> the xp partition as well.
>
> Any ideas are very much appreciated.
>
> Andre.
>
>
>