experiences with dell inspiron 530
Hi, Some experiences with grml 1.1 on a Dell Inspiron 530(nvidia chipset and graphics system) and a generic issue:
when running grml-x with a module option, but without windowmanager, it complains that the windowmanager with the name of the module doesn't exist. I'd expect it just says "you didn't specify a windowmanager", but instead it seems to try to take the last argument as windowmanager name.
As of the hardware support for inspiron: grml-x doesn't get an x system loaded - until I start it one time with the -fallback option.
_after_ this one start with fallback, I can start it again, without fallback - and then I get a better resolution and can work without the screen-scrolling that happens in fallback mode.
Let me know if you need and hints or info on the system.
Henning
BTW:
Henning Sprang wrote:
_after_ this one start with fallback, I can start it again, without fallback - and then I get a better resolution and can work without the screen-scrolling that happens in fallback mode.
This one is not reproducible - it worked once, but then again it didn't work without fallback, and sometimes it starts without fallback, but the resolution is still in "emulation mode" - don't know the right word - the X system runs on a resolution higher than the one shown on the screen, and it automatically scrolls in the invisiable parts when the mouse cursor comes close to the screen border.
Henning
Another thing I see here with grml 1.1: when doing a reboot, grml is so nice to stop and tell me to remove the cd. But when I do so, and hit return, it doesn't reboot nicely, but complains about the now missing device.
* Henning Sprang henning_sprang@gmx.de [20080603 15:40]:
Some experiences with grml 1.1 on a Dell Inspiron 530(nvidia chipset and graphics system) and a generic issue:
when running grml-x with a module option, but without windowmanager, it complains that the windowmanager with the name of the module doesn't exist. I'd expect it just says "you didn't specify a windowmanager", but instead it seems to try to take the last argument as windowmanager name.
Yeah, option parsing in shell isn't really fun. ;-)
I can recommend usage of zsh's completion mechanism so you get a valid command line. :)
As of the hardware support for inspiron: grml-x doesn't get an x system loaded - until I start it one time with the -fallback option.
_after_ this one start with fallback, I can start it again, without fallback - and then I get a better resolution and can work without the screen-scrolling that happens in fallback mode.
Does providing the -hsync and -vsync option help? Does using the vesa module (but without -fallback) change anything?
regards, -mika-
Michael Prokop wrote:
Does providing the -hsync and -vsync option help? Does using the vesa module (but without -fallback) change anything?
Vesa also worked sometimes, sometimes together with -fallback, but the results somehow did not seem really reproducible - though clearly, I didn't do really structured, documented testing :)
Unfortunately, the hardware is already gone now, but I can try again when I get at it in the next days/weeks.
Henning
participants (2)
-
Henning Sprang -
Michael Prokop