Could be something as simple as having the Trigger Mode set to "Normal" instead of "P-P Auto" with no signal input, or having the traces moved up, down, left or right offscreen with the V and H position controls. Many times I've seen scopes that were "not working, no trace" that were simply set wrong and actually had nothing wrong with them. Let's hope that is the case here as well.
I just fired up my 2213A (which is fully functional, a great little scope) with no input, set it to "Normal" Trigger Mode (which blanks the screen unless the scope is triggered) , and duplicated this:
The beam find function does allow me to see a dot and it can be positioned with the X Y controls. If I set it to line I can see a small horizontal trace about an inch or so but on int its only a dot.
Exactly what mine does.
So the very first thing to do would be to make sure that the "P-P Auto" Trigger Mode button is depressed and the Trigger Source is set to "Int" , Trigger Holdoff fully CCW ("normal") and vertical and horizontal position controls set to mid-range. (Set "Intensity" to 3/4 or fully CW just for this test, then back it off to a dull roar if the trace shows up). If no visible trace, then move the H and V controls through full range to see if the trace is just hanging out offscreen somewhere. All of this applies to the "A" trigger, see the manual pages I referenced above.