Main > Linux
32/64bit Groovy Arcade Linux LiveCD/Install
bitbytebit:
I'm compiling USB Mass storage support in the kernel, actually most likely will get a USB stick myself and do some tests to get this working since I'd like to run it this way too. So hopefully will have liveCD/USB and installation support in a day or so, if it all works it's definitely more than I'd hoped getting working this soon :). I'm just not fully sure yet if the liveCD stuff and USB bootup are somehow going to differ in it expecting to mount a CDROM instead of the USB stick, I'll have to research that and test it to see.
Quinny:
When I boot up with a monitor connected (DVI-0) and a TV connected (DVI-1) switchres tries to update the monitor. If I use xrandr to put that same mode on to DVI-1 (the TV) then the resolution changes. I tried this with pacman and the resolution was not so good as the image wobbled quite a bit. The resolution for mace was reasonably good though.
When first starting X the resolution is still no good and it shows me the "three screens" issue.
If I just boot up with the TV connected it still thinks it's DVI-1 and for some reason using switchres will break it. I have to type the modes into xrandr to see the change. As you can imagine that is quite tedious. :)
Maybe using xrandr instead of switchres isn't as effective at changing the resolutions?
Using switchres --monitor pal changes the values for the modeline and switchres still doesn't work. The screen goes black and I get it back by using xrandr.
bitbytebit:
--- Quote from: Quinny on December 07, 2010, 10:09:39 am ---When I boot up with a monitor connected (DVI-0) and a TV connected (DVI-1) switchres tries to update the monitor. If I use xrandr to put that same mode on to DVI-1 (the TV) then the resolution changes. I tried this with pacman and the resolution was not so good as the image wobbled quite a bit. The resolution for mace was reasonably good though.
When first starting X the resolution is still no good and it shows me the "three screens" issue.
If I just boot up with the TV connected it still thinks it's DVI-1 and for some reason using switchres will break it. I have to type the modes into xrandr to see the change. As you can imagine that is quite tedious. :)
Maybe using xrandr instead of switchres isn't as effective at changing the resolutions?
Using switchres --monitor pal changes the values for the modeline and switchres still doesn't work. The screen goes black and I get it back by using xrandr.
--- End quote ---
One thing is that having a monitor connected and a TV/Arcade monitor is really hard to get working with xrandr mode changing, since it likes to try and have all monitors the same unless the xorg.conf is setup very carefully. It'll end up refusing to change it at all, but also it sounds like something else is going on which might have to do or not (not sure about it) with the boot option change to have all the output's enabled with video=HxWec (the 'e' added now). If you can, in the grub menu see if you can change the command line to not include that 'e' and using just the TV see if you get anything better.
Also I'm curious about what your 'xrandr -q' output looks like, with just the TV connected and with both TV/Monitor connected at boot. That might give me more information on what it's doing exactly there.
It also sounds like the PAL modeline generation is a bit 'off' which I did suspect could be possible, since the values used might be wrong and I wasn't sure yet what to use for those exactly. What would be interesting is if you had a modeline generated with lrmc for each of the ones that look bad, and compared the two, I might be able to start figuring out more with that information quicker. It definitely sounds like if I can get this working on the USB stick I guess it'll be at least easier to change out the kernel or alter the grub.conf bootup. Is your /etc/X11/xorg.conf file generated saying it's PAL at the top, and what does it look like at the bottom with the modeline generated for it? If the console is working it in theory should be using the exact same modeline now for X but there might be something going wrong with generating the xorg.conf properly I am guessing. Unfortunately too, the dual monitor support is probably going to be very 'weird', at least I suspect, since the way I'm doing setup of the xorg.conf doesn't take into account for that and I'm not fully sure what exactly will happen :). So hopefully the output of xrandr -q and possibly even the /var/log/Xorg.0.log file would help some too, the output of `dmesg` might even be good I thinik, after you've done switches (also the /var/log/dmesg might help since that's the bootup info, while the dmesg output will fill up the buffer quite fast and lose information from startup).
Quinny:
--- Quote from: bitbytebit on December 07, 2010, 10:33:29 am ---One thing is that having a monitor connected and a TV/Arcade monitor is really hard to get working with xrandr mode changing, since it likes to try and have all monitors the same unless the xorg.conf is setup very carefully. It'll end up refusing to change it at all, but also it sounds like something else is going on which might have to do or not (not sure about it) with the boot option change to have all the output's enabled with video=HxWec (the 'e' added now). If you can, in the grub menu see if you can change the command line to not include that 'e' and using just the TV see if you get anything better.
--- End quote ---
This works and shows only one monitor with xrandr. However, it is still using a mode (1024x768 I think) which is not compatable with PAL on startup.
--- Quote from: bitbytebit on December 07, 2010, 10:33:29 am ---Also I'm curious about what your 'xrandr -q' output looks like, with just the TV connected and with both TV/Monitor connected at boot. That might give me more information on what it's doing exactly there.
--- End quote ---
I am not sure how to get this info from the computer I am testing on to this one I am using now.
This is with both the TV and monitor connected.
Both DVI-0 and DVI-1 have the exact same parameters.
DVI-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1024x768 60.0*
800x600 60.3
640x480 59.9
512x384 120.0
400x300 120.6
320x240 120.1
With just the TV (with video=HxWec):
Same as above.
Just TV with video=HxWc:
Same as above.
--- Quote from: bitbytebit on December 07, 2010, 10:33:29 am ---It also sounds like the PAL modeline generation is a bit 'off' which I did suspect could be possible, since the values used might be wrong and I wasn't sure yet what to use for those exactly. What would be interesting is if you had a modeline generated with lrmc for each of the ones that look bad, and compared the two, I might be able to start figuring out more with that information quicker. It definitely sounds like if I can get this working on the USB stick I guess it'll be at least easier to change out the kernel or alter the grub.conf bootup. Is your /etc/X11/xorg.conf file generated saying it's PAL at the top, and what does it look like at the bottom with the modeline generated for it? If the console is working it in theory should be using the exact same modeline now for X but there might be something going wrong with generating the xorg.conf properly I am guessing. Unfortunately too, the dual monitor support is probably going to be very 'weird', at least I suspect, since the way I'm doing setup of the xorg.conf doesn't take into account for that and I'm not fully sure what exactly will happen :). So hopefully the output of xrandr -q and possibly even the /var/log/Xorg.0.log file would help some too, the output of `dmesg` might even be good I thinik, after you've done switches (also the /var/log/dmesg might help since that's the bootup info, while the dmesg output will fill up the buffer quite fast and lose information from startup).
--- End quote ---
There is no file /etc/X11/xorg.conf.
Again, not sure how to get those files from that PC to this one.
Sorry I can't provide more info with the logs. I'll see if I can figure out a way to get the files across.
bitbytebit:
--- Quote from: Quinny on December 07, 2010, 11:31:37 am ---
--- Quote from: bitbytebit on December 07, 2010, 10:33:29 am ---One thing is that having a monitor connected and a TV/Arcade monitor is really hard to get working with xrandr mode changing, since it likes to try and have all monitors the same unless the xorg.conf is setup very carefully. It'll end up refusing to change it at all, but also it sounds like something else is going on which might have to do or not (not sure about it) with the boot option change to have all the output's enabled with video=HxWec (the 'e' added now). If you can, in the grub menu see if you can change the command line to not include that 'e' and using just the TV see if you get anything better.
--- End quote ---
This works and shows only one monitor with xrandr. However, it is still using a mode (1024x768 I think) which is not compatable with PAL on startup.
--- Quote from: bitbytebit on December 07, 2010, 10:33:29 am ---Also I'm curious about what your 'xrandr -q' output looks like, with just the TV connected and with both TV/Monitor connected at boot. That might give me more information on what it's doing exactly there.
--- End quote ---
I am not sure how to get this info from the computer I am testing on to this one I am using now.
This is with both the TV and monitor connected.
Both DVI-0 and DVI-1 have the exact same parameters.
DVI-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1024x768 60.0*
800x600 60.3
640x480 59.9
512x384 120.0
400x300 120.6
320x240 120.1
With just the TV (with video=HxWec):
Same as above.
Just TV with video=HxWc:
Same as above.
--- Quote from: bitbytebit on December 07, 2010, 10:33:29 am ---It also sounds like the PAL modeline generation is a bit 'off' which I did suspect could be possible, since the values used might be wrong and I wasn't sure yet what to use for those exactly. What would be interesting is if you had a modeline generated with lrmc for each of the ones that look bad, and compared the two, I might be able to start figuring out more with that information quicker. It definitely sounds like if I can get this working on the USB stick I guess it'll be at least easier to change out the kernel or alter the grub.conf bootup. Is your /etc/X11/xorg.conf file generated saying it's PAL at the top, and what does it look like at the bottom with the modeline generated for it? If the console is working it in theory should be using the exact same modeline now for X but there might be something going wrong with generating the xorg.conf properly I am guessing. Unfortunately too, the dual monitor support is probably going to be very 'weird', at least I suspect, since the way I'm doing setup of the xorg.conf doesn't take into account for that and I'm not fully sure what exactly will happen :). So hopefully the output of xrandr -q and possibly even the /var/log/Xorg.0.log file would help some too, the output of `dmesg` might even be good I thinik, after you've done switches (also the /var/log/dmesg might help since that's the bootup info, while the dmesg output will fill up the buffer quite fast and lose information from startup).
--- End quote ---
There is no file /etc/X11/xorg.conf.
Again, not sure how to get those files from that PC to this one.
Sorry I can't provide more info with the logs. I'll see if I can figure out a way to get the files across.
--- End quote ---
Interesting, it's having the default modelines used it seems, so I suspect it's not creating an xorg.conf which sounds like what your seeing so it's trying to use the default modes then. Oddly it sounds like for some reason the xorg.conf isn't getting setup right, not sure why that's occuring though, it might be from the custom command line change it's not working with my check for the command line. Good to know though that the 'e' option causes the issue, although that also might be a fix for Jpac and Arcade monitors, so might have to do some more exact forcing of things to work on the first output like Soft15Khz has to do.
What does this show, `cat /proc/cmdline`? When you get the 1024x768 resolutions for X, that would be interesting to see since that's what it parses to setup the monitor config. Also is the home directory your using writable, is there a .gentooarcade/ directory in /home/arcade/ (/home/arcade/.gentooarcade/), and what does the config file contain in that directory? Another thing you can do, at the command prompt as root run `create_xorg.pl pal > /etc/X11/xorg.conf` and copy that to /home/arcade/.gentooarcade/ and it'll at least force it to use the right xorg.conf setup, and also can check and make sure that really works too.
I think I've figured out the fuzzy pacman issue, why some resolutions are not good like that one. Has to do with some calculations in switchres which needed a check for strict Horizontal freq displays like a TV and how it's interlaced normally and has an extra half line I guess. I'll check with Calamity to see what he thinks, but I think I have a good fix for it. Also think some of the timing information needs to be slightly altered too for the front porch/back porch possibly to make sure things are more correct with the resolutions generated for TV's.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version