Gus Wirth wrote:
> [snip]
> 
> I see that you have an AMD motherboard. Does it have a VIA chipset,
> specifically the KT133/KT133A ? If so you will have problems because
> there is a bug in the DMA operation with the PVR-150 card. I had to buy
> a new motherboard because of that. I got a cheap ($89) Fry's special
> combo of an ECS 755 with an SIS chipset and a Sempron processor that
> works great.
> 
> While doing your initial setup it may be more useful not to have the gdm
> (Gnome Display Manager) and X start up automatically. Debian doesn't
> believe in run levels (well, it does but not the same way as say RedHat)
> so you will need to manually hack some symlinks. The system will start
> up in run level 5. Use Ctr-Alt-F2 to get to a text login. Go to
> /etc/rc5.d In that directory you will see a symlink called S99gdm. This
> points to the startup script for gdm. Move it to K99gdm to prevent it
> from starting. The next time you reboot you will then be at a regular
> text login prompt.

Debian believes in run levels.  It's just that (x|g|k)dm is started via
an init script, and not via inittab like Redhat.  If I remember right,
if you have a screwed up video driver or x config in Redhat, it keeps
trying to respawning X forever, and you have to get to a terminal, be
quick and take manually to another init level, or reboot and manually
override the default run level.  I much prefer the Debian way for this
as when you screw up X, you're not fighting the box to get a shell
prompt to fix it.



> The other thing I noticed is that the system uses the original vi and
> not vim for an editor. This may be OK but it drove me crazy so I
> installed vim like this:
> 
> # apt-get update
> # apt-get install vim

Yeah, it is an issue, but easily corrected.   Wait until you try to
compile a kernel or build your own kernel and find out that ncurses-dev
isn't installed.  :)



-- 
Mark Wolfe           Lakeside, Ca.           http://www.wolfenet.org
gpg fingerprint = 42B6 EFEB 5414 AA18 01B7  64AC EF46 F7E6 82F6 8C71
Microsoft - We put the "backwards" into backwards compatibility.


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to