Thinkpad slicing and boot managing

[Lars]

Oh ok, thank you for your comments and corrections, 
I'll change my config accordingly.

On Sat, Jul 05, 2003 at 10:19:24AM -0700, Kevin Oberman wrote:
> > Date: Sat, 5 Jul 2003 11:43:02 +0200
> > From: Lars <lars at gmx.at>
> > Sender: owner-freebsd-mobile at freebsd.org
> > 
> > Date: Fri, 4 Jul 2003 18:56:20 +0200
> > From: Lars <lars at gmx.at>
> > 
> > On Fri, Jul 04, 2003 at 07:23:56PM +1000, Pisut Tempatarachoke wrote:
> > Hi Pisut,
> > 
> > I bought a Thinkpad R40 and did something similar.
> > 1	Yes, FAT32 or FAT16 can be written and read from both
> > 	WinXP and FreeBSD.
> > 2	I installed the FreeBSD Bootmanager in the MBR and
> > 	I can boot both FreeBSD and WinXP flawlessly;
> > 	however the WinXP entry shows up in the bootloader
> > 	as "???", but works anyway -so no sweat.
> 
> That's because the basic C/H/S MBR for BootEasy does not know what
> NTFS is. If you use boot0cfg to build a boot with the "-o packet"
> option, it should show that slice correctly. That option also allows
> you to boot FreeBSD from the second or third slice even if it is past
> cyl. 1024. 
> 
> The only reason that this is not the default is that really old
> hardware only supports CHS addressing in BIOS and can't boot with the
> newer code. The IBM is far too new to have this problem.
> 
> > 4	My XF86Config works alright, no 3D though and could/should
> > 	be optimised further, I also have 14" screen (1024x768).
> > 
> > Section "ServerLayout"
> > 	Identifier     "XFree86 Configured"
> > 	Screen      0  "Screen0" 0 0
> > 	InputDevice    "MouseTP" "CorePointer"
> > 	InputDevice    "KeyboardTP" "CoreKeyboard"
> > EndSection
> > 
> > Section "Files"
> > 	RgbPath      "/usr/X11R6/lib/X11/rgb"
> > 	ModulePath   "/usr/X11R6/lib/modules"
> > 	FontPath     "/usr/X11R6/lib/X11/fonts/misc/"
> > 	FontPath     "/usr/X11R6/lib/X11/fonts/Speedo/"
> > 	FontPath     "/usr/X11R6/lib/X11/fonts/Type1/"
> > 	FontPath     "/usr/X11R6/lib/X11/fonts/75dpi/"
> > 	FontPath     "/usr/X11R6/lib/X11/fonts/100dpi/"
> > EndSection
> > 
> > Section "Module"
> > 	Load  "dbe"
> > 	Load  "dri"
> > 	Load  "extmod"
> > 	Load  "glx"
> > 	Load  "pex5"
> > 	Load  "record"
> > 	Load  "xie"
> > 	Load  "xtrap"
> > 	Load  "speedo"
> > 	Load  "type1"
> > EndSection
> 
> For XFree86 V4.3, I think you really want 'Load freetype"'. Also, pex5
> and xie are no longer modules, so these just produce errors.
> 
> > Section "InputDevice"
> > 	Identifier  "KeyboardTP"
> > 	Driver      "keyboard"
> > 	Option	    "XkbRules" "xfree86"
> > 	Option	    "XkbModel" "pc101"
> > 	Option	    "XkbLayout" "de_CH"
> > EndSection
> 
> Of course, the XkbLayout option needs to be changed if you don't want
> Swiss-German. 
>  
> > Section "DRI"
> > 	Mode 0666
> > EndSection
> > 
> > Section "InputDevice"
> > 	Identifier  "MouseTP"
> > 	Driver      "mouse"
> > 	Option	    "Protocol" "MouseSystems"
> > 	Option	    "Device" "/dev/sysmouse"
> > EndSection
> 
> With any XFree86 V4, you probably want to set the protocol to
> "auto". It's far more likely to work well.
> 
> > Section "Monitor"
> > 	Identifier   "MonitorTP"
> > 	VendorName   "Monitor Vendor"
> > 	ModelName    "Monitor Model"
> > 	HorizSync    28.0 - 50.0
> > 	VertRefresh  43.0 - 75.0
> > EndSection
> 
> For most LCDs, the X software will "read" the BIOS for information on
> the scan rates, so this is usually not important.
> 
> > Section "Device"
> >         ### Available Driver options are:-
> >         ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
> >         ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
> >         ### [arg]: arg optional
> >         #Option     "NoAccel"            	# [<bool>]
> >         #Option     "SWcursor"           	# [<bool>]
> >         #Option     "Dac6Bit"            	# [<bool>]
> >         #Option     "Dac8Bit"            	# [<bool>]
> >         #Option     "ForcePCIMode"       	# [<bool>]
> >         #Option     "CPPIOMode"          	# [<bool>]
> >         #Option     "CPusecTimeout"      	# <i>
> >         #Option     "AGPMode"            	# <i>
> >         #Option     "AGPSize"            	# <i>
> >         #Option     "RingSize"           	# <i>
> >         #Option     "BufferSize"         	# <i>
> >         #Option     "EnableDepthMoves"   	# [<bool>]
> >         #Option     "CrtScreen"          	# [<bool>]
> >         #Option     "PanelSize"          	# [<str>]
> >         #Option     "UseFBDev"           	# [<bool>]
> > 	Identifier  "CardTP"
> > 	Driver      "ati"
> > 	VendorName  "ATI"
> > 	BoardName   "Radeon Mobility M6 LY"
> > 	BusID       "PCI:1:0:0"
> > EndSection
> > 
> > Section "Screen"
> > 	Identifier "Screen0"
> > 	Device     "CardTP"
> > 	Monitor    "MonitorTP"
> > 	DefaultDepth     24
> > 	SubSection "Display"
> > 		Depth     1
> > 	EndSubSection
> > 	SubSection "Display"
> > 		Depth     4
> > 	EndSubSection
> > 	SubSection "Display"
> > 		Depth     8
> > 	EndSubSection
> > 	SubSection "Display"
> > 		Depth     15
> > 	EndSubSection
> > 	SubSection "Display"
> > 		Depth     16
> > 	EndSubSection
> > 	SubSection "Display"
> > 		Depth     24
> > 		Modes    "1024x768" "800x600"
> > 	EndSubSection
> > EndSection
> 
> The A31p support 1600x1200, so you will want to adjust the "Modes" to
> allow that.
> -- 
> R. Kevin Oberman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> E-mail: oberman at es.net			Phone: +1 510 486-8634
>