I have been trying to find the package or meta-package in TDE that depends (installs) the x-window system, ie xorg. Would it be a good idea to depend on xorg ,or similar, if TDE does not do so ? It is atypical ,afaikt, for most DE to not include the x-window system.
Are most ou you installing TDE after installing another DE ?
especially since Xorg is only an implementation of the X11 protocol, not the only one. With upcoming things like wayland's x11 wrapper and even people who might use Xvesa another stripped down X version, it would be a good idea not too I think.
On 13 February 2014 19:13, Greg Madden gomadtroll@gci.net wrote:
I have been trying to find the package or meta-package in TDE that depends (installs) the x-window system, ie xorg. Would it be a good idea to depend on xorg ,or similar, if TDE does not do so ? It is atypical ,afaikt, for most DE to not include the x-window system.
Are most ou you installing TDE after installing another DE ?
--
Peace,
Greg
On Thu, Feb 13, 2014 at 7:13 PM, Greg Madden gomadtroll@gci.net wrote:
Are most ou you installing TDE after installing another DE ?
That is how I would do it, in order to ensure that any hardware issues were resolved before putting TDE on the machine. I would not want to have anything where I could mistake TDE for causing the error, where it was actually an issue of graphics compatibility or such.
Curt-
said Curt Howland:
| That is how I would do it, in order to ensure that any hardware issues | were resolved before putting TDE on the machine. I would not want to | have anything where I could mistake TDE for causing the error, where | it was actually an issue of graphics compatibility or such.
while we're at it . . .
in december i built a new machine, which has nvidia graphics instead of the previous ATI. moving the drives over went smoothly enough, but booting is peculiar: if i just boot from the grub2 screen, it goes along for a bit and then locks solid before getting fully booted. if, however, i choose to boot in repair mode, which oddly goes into framebuffer and then produces a normal text-based screen of choices and select "boot normally," it boots . . . normally.
i suppose i could look upon this as a security feature, but i'd just as soon fix it. there seems to be a lot of silliness that gets loaded up front, such as the framebuffer stuff, for reasons not at all apparent to me. ideally, i would have a nice, no-frame-buffer boot, all in text, all printed to the screen in nice, pure text mode, until the time comes for the starting of X. indeed, if after logging in i had to type startx as in the old days, that would be fine. but at this point i would settle for a working default boot. any ideas?
On 14/02/2014 13:22, dep wrote:
said Curt Howland:
| That is how I would do it, in order to ensure that any hardware issues | were resolved before putting TDE on the machine. I would not want to | have anything where I could mistake TDE for causing the error, where | it was actually an issue of graphics compatibility or such.
while we're at it . . .
in december i built a new machine, which has nvidia graphics instead of the previous ATI. moving the drives over went smoothly enough, but booting is peculiar: if i just boot from the grub2 screen, it goes along for a bit and then locks solid before getting fully booted. if, however, i choose to boot in repair mode, which oddly goes into framebuffer and then produces a normal text-based screen of choices and select "boot normally," it boots . . . normally.
You don't say what OS or Version but I would take a look at the grub command line to she exactly how it's booting. It sounds like the original command line from your previous install. It needs tweaking by the sounds of things.
i suppose i could look upon this as a security feature, but i'd just as soon fix it. there seems to be a lot of silliness that gets loaded up front, such as the framebuffer stuff, for reasons not at all apparent to me. ideally, i would have a nice, no-frame-buffer boot, all in text, all printed to the screen in nice, pure text mode, until the time comes for the starting of X. indeed, if after logging in i had to type startx as in the old days, that would be fine. but at this point i would settle for a working default boot. any ideas?
Again, you don't say which OS/Verson but to boot to the command prompt instead of X just set it up that way in /etc/inittab (eg. id:2:initdefault:) or alternatively, for later Fedora etc versions set it using the systend methodology.
Cheers, Mike.
--
said Michael Howard:
| > in december i built a new machine, which has nvidia graphics instead | > of the previous ATI. moving the drives over went smoothly enough, but | > booting is peculiar: if i just boot from the grub2 screen, it goes | > along for a bit and then locks solid before getting fully booted. if, | > however, i choose to boot in repair mode, which oddly goes into | > framebuffer and then produces a normal text-based screen of choices | > and select "boot normally," it boots . . . normally. | | You don't say what OS or Version but I would take a look at the grub | command line to she exactly how it's booting. It sounds like the | original command line from your previous install. It needs tweaking by | the sounds of things.
a debian-derivative -- ubuntu or kubuntu, don't remember which -- 12.04 LTS, 64-bit.
and yes, i agree it needs tweaking -- just don't know the tweaks. the whole frame buffer thing is a little nutty to me. could have dealt with it in lilo, but i do not know grub or grub2 at all well.
On Friday 14 February 2014 06:28:23 you wrote:
said Michael Howard: | > in december i built a new machine, which has nvidia graphics | > instead of the previous ATI. moving the drives over went smoothly | > enough, but booting is peculiar: if i just boot from the grub2 | > screen, it goes along for a bit and then locks solid before | > getting fully booted. if, however, i choose to boot in repair | > mode, which oddly goes into framebuffer and then produces a | > normal text-based screen of choices and select "boot normally," | > it boots . . . normally. | | You don't say what OS or Version but I would take a look at the | grub command line to she exactly how it's booting. It sounds like | the original command line from your previous install. It needs | tweaking by the sounds of things.
a debian-derivative -- ubuntu or kubuntu, don't remember which -- 12.04 LTS, 64-bit.
and yes, i agree it needs tweaking -- just don't know the tweaks. the whole frame buffer thing is a little nutty to me. could have dealt with it in lilo, but i do not know grub or grub2 at all well.
investigate rebuilding your initrd.img, it may have the wrong video drivers.
-
Calvin Morrison -
Curt Howland -
dep -
Greg Madden -
Michael Howard