On SQL 2005, no, not unless you have trace flag 1222 or 1204 enabled or had a server-side trace running.
If you're worried about deadlocks enable 1222 (only) globally and future deadlocks will be written to the SQL Error Log:
DBCC TRACEON (1222, -1)
If you want this running all the time you can add it to the SQL Server startup parameters, or setup a SQL Agent job to "start when the services start" to enable the trace flag.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato