Monitor Blanking When Starting X; atombios stuck
Hello, I have a system running Debian Testing. It was freshly installed from the stable net-installer image then immediately upgraded to testing. I then installed xfce4 and configured it to start from console as per these[1] instructions. However, when I run `startx`, I get some output from it (the usual xserver messages), but then the monitor goes blank. Here's my kern.log from booting to the blank screen, then forcing a reboot again after that. http://dpaste.com/16R30GF.txt The relevant portion is here in the event the paste disappears: kernel: [ 22.631932] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting kernel: [ 22.631947] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CB32 (len 62, WS 0, PS 0) @ 0xCB4E kernel: [ 27.636246] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting kernel: [ 27.636277] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CB32 (len 62, WS 0, PS 0) @ 0xCB4E kernel: [ 27.636307] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C1DC (len 1136, WS 0, PS 0) @ 0xC576 kernel: [ 378.768505] sysrq: SysRq : SAK kernel: [ 378.768579] tty tty1: SAK: killed process 557 (bash): by session kernel: [ 378.768586] tty tty1: SAK: killed process 483 (login): by session kernel: [ 378.768651] tty tty1: SAK: killed process 483 (login): by controlling tty kernel: [ 378.768659] tty tty1: SAK: killed process 557 (bash): by controlling tty I have the following relevant packages installed: xserver-xorg-video-radeon firmware-linux firmware-linux-nonfree firmware-amd-graphics intel-microcode lspci shows my video card to be: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks LE [Radeon HD 5570/6510/7510/8510] (prog-if 00 [VGA controller]) Subsystem: VISIONTEK Turks LE [Radeon HD 5570/6510/7510/8510] Flags: bus master, fast devsel, latency 0, IRQ 34 Memory at e000 (64-bit, prefetchable) [size=256M] Memory at f7de (64-bit, non-prefetchable) [size=128K] I/O ports at dc00 [size=256] Expansion ROM at f7e0 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150] Advanced Error Reporting Kernel driver in use: radeon Kernel modules: radeon I would appreciate any help in tracking this issue down. Thank you, Steve [1] https://wiki.debian.org/Xfce#From_the_console
/etc/inittab not executed upon starting X with startx command
I have uncommented the following line in the /etc/inittab file on Debian Squeeze: T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 Basically, I am trying to output a login console on Serial Port 1 also. This works if my system starts up normally i.e. via xdm-fluxbox. However, I want to do a auto login into my fluxbox (instead of user typing in username and password in xdm) and I still want the basic login console on Serial Port 1. So I removed xdm package (apt-get purge xdm) and added the following line to my /etc/rc.local: su - user -c startx Now my system does the autologin into fluxbox but I no longer get my login console on Serial Port 1. It seems that the /etc/inittab file is not honored with this method (auto login). Any ideas how can I get my login console on Serial Port 1 and at the same time auto log into fluxbox? Thanks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/calxxvm5rdvkwlr1jb4kppvgl_rmbcigd92xxq1fdz3qkfr3...@mail.gmail.com
Re: /etc/inittab not executed upon starting X with startx command
Tech Geek wrote: I have uncommented the following line in the /etc/inittab file on Debian Squeeze: T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 Seems reasonable. I do that on server systems too. This works if my system starts up normally i.e. via xdm-fluxbox. Sure. However, I want to do a auto login into my fluxbox (instead of user typing in username and password in xdm) and I still want the basic login console on Serial Port 1. So I removed xdm package (apt-get purge xdm) and added the following line to my /etc/rc.local: su - user -c startx Now my system does the autologin into fluxbox but I no longer get my login console on Serial Port 1. It seems that the /etc/inittab file is not honored with this method (auto login). That seems very strange to me. I have not tested that exact combination but I would certainly not have expected it. And I am suspicious that something else is going on because it seems that there should not be a relationship between those two systems. I am so suspicious that I am compelled to ask if you are really sure that is the correlation? Please double check. Are there any messaged logged to /var/log/syslog concerning failure of getty to start on /dev/ttyS0? If you run 'ps' do you see the getting running? $ ps -ef |grep getty Any ideas how can I get my login console on Serial Port 1 and at the same time auto log into fluxbox? I have a system similarly configured using gdm (gdm 2.20.11, not gdm3) and have it configured with the following: File /etc/gdm/gdm.conf has this: [daemon] AutomaticLoginEnable=true AutomaticLogin=guest Both of these, the getting on the serial port and the gdm automated login, work fine together for me. Since this is using gdm configuration to automatically log in a user it is different from your using su and startx from the rc.local though. Bob signature.asc Description: Digital signature
Re: /etc/inittab not executed upon starting X with startx command
suspicious that I am compelled to ask if you are really sure that is the correlation? Please double check. Yes, I double checked that. As soon as I revert back to installing xdm, the login console appears on Serial Port 1. Are there any messaged logged to /var/log/syslog concerning failure of getty to start on /dev/ttyS0? No there are none. If you run 'ps' do you see the getting running? $ ps -ef |grep getty The above command returns nothing i.e it looks like getty is not started at all. Both of these, the getting on the serial port and the gdm automated login, work fine together for me. Since this is using gdm configuration to automatically log in a user it is different from your using su and startx from the rc.local though. May be that's the reason. But just like you even I am very surprised to see that /etc/inittab is not executed/sourced when using su and startx method via rc.local. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/calxxvm7lxrbh-0anjq1r9gbxnhzrbmoehl7vj4oikrxcm0-...@mail.gmail.com
Re: /etc/inittab not executed upon starting X with startx command
Tech Geek techgeek12...@gmail.com writes: […] However, I want to do a auto login into my fluxbox (instead of user typing in username and password in xdm) and I still want the basic login console on Serial Port 1. So I removed xdm package (apt-get purge xdm) and added the following line to my /etc/rc.local: su - user -c startx Now my system does the autologin into fluxbox but I no longer get my login console on Serial Port 1. I guess that the inittab(5) entry in question is only started after rc.local finishes. Therefore, starting startx(1) in the background may help. […] -- FSF associate member #7257 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/86r54m4ivc@gray.siamics.net
Re: /etc/inittab not executed upon starting X with startx command
Ivan Shmakov wrote: Tech Geek writes: However, I want to do a auto login into my fluxbox (instead of user typing in username and password in xdm) and I still want the basic login console on Serial Port 1. So I removed xdm package (apt-get purge xdm) and added the following line to my /etc/rc.local: su - user -c startx Now my system does the autologin into fluxbox but I no longer get my login console on Serial Port 1. I guess that the inittab(5) entry in question is only started after rc.local finishes. Therefore, starting startx(1) in the background may help. Good catch. Almost certainly that is the problem. The rc.local is still running. Here is an additional clue: $ ps -ef |grep getty The above command returns nothing I.e it looks like getty is not started at all. Not even other console logins? Normally there would be all of the virtual consoles there. $ ps -efH | less I expect that to show that rc.local is still running. And so it was never able to move on and complete the boot up sequence. Bob signature.asc Description: Digital signature
Re: /etc/inittab not executed upon starting X with startx command
Ivan, I guess that the inittab(5) entry in question is only started after rc.local finishes. Therefore, starting startx(1) in the background may help. That was it. Adding at the end of the command in rc.local did the trick! Thanks! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CALXXvm7tFvV4K04Gpv4DVdKpu=haoj7fgwfsp8y8vg15+dk...@mail.gmail.com
Re: sid: Console problems after starting X
On Fri, 2010-09-03 at 00:58 -1000, Joel Roth wrote: Hello all, Here's what happening. After boot: normal console font (about 80 characters wide) After startx: small console font (maybe 132 characters?) A little later: no display in console at all (Alt-F7 still gets me back to X) This problem appeared soon after converting to dependency-based boot process using insserv. I've been using a self-compiled amd64 kernel with 32-bit userland. No such problems before insserv. Thanks for any possible leads. I have no idea where to even start. thanks, Joel -- Joel Roth -- Passing along a tip from Wayne Topa that helped me. maybe it will help you. I did a dist-update a while back using a stock kernel had this same issue ,I think?? Do dpkg -l console-setup if you don't have it installed, install it. HTH Wayne -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1284046625.4792.5.ca...@beast.johnwfoster.info
Re: sid: Console problems after starting X
On Fri, 3 Sep 2010 00:58:21 -1000 Joel Roth jo...@pobox.com wrote: [...] What video card/driver are you using? -- Rares Aioanei debian.dev.list -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100906101456.3089ea1d.debian.dev.l...@localhost.localdomain
Re: sid: Console problems after starting X
On Mon, Sep 06, 2010 at 10:14:56AM +0300, Rares Aioanei wrote: On Fri, 3 Sep 2010 00:58:21 -1000 Joel Roth jo...@pobox.com wrote: [...] What video card/driver are you using? -- Rares Aioanei debian.dev.list The card is: lspci | grep -i radeon 01:05.0 VGA compatible controller: ATI Technologies Inc RS780MC [Radeon HD 3100 Graphics] The driver, I don't know. You can maybe find it in the /var/log/Xorg.0.log file pasted into a previous mail. The problem seemed to be solved by going to a stock kernel. Thanks for your questions. Joel -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100906224711.ga19...@sprite
Re: sid: Console problems after starting X
On Vi, 03 sep 10, 16:54:25, Joel Roth wrote: drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci::01:05.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: drmOpenMinor returns 11 drmOpenByBusid: drmGetBusid reports pci::01:05.0 (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. This, combined with the fact that you are running a self-compiled kernel would indicate that you might miss some module. Can you try a stock kernel? Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: sid: Console problems after starting X
On Sat, Sep 04, 2010 at 01:35:28PM +0300, Andrei Popescu wrote: On Vi, 03 sep 10, 16:54:25, Joel Roth wrote: drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci::01:05.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: drmOpenMinor returns 11 drmOpenByBusid: drmGetBusid reports pci::01:05.0 (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. This, combined with the fact that you are running a self-compiled kernel would indicate that you might miss some module. Can you try a stock kernel? Thanks for checking this out! Console *does* VT switching correctly under a stock 2.6.31-1-amd64 kernel. (But for some reason suspend doesn't work... will try a later kernel.) Why didn't I think of this? Probably because the kernel was working before. Mahalo Joel Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100904112051.gb2...@sprite
Re: sid: Console problems after starting X
On Sat, 04 Sep 2010 06:35:28 -0400 (EDT), Andrei Popescu wrote: On Vi, 03 sep 10, 16:54:25, Joel Roth wrote: drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci::01:05.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: drmOpenMinor returns 11 drmOpenByBusid: drmGetBusid reports pci::01:05.0 (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. This, combined with the fact that you are running a self-compiled kernel would indicate that you might miss some module. Can you try a stock kernel? Nice work, Andrei! -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1948183613.604400.1283605583354.javamail.r...@md01.wow.synacor.com
Re: sid: Console problems after starting X
On Sb, 04 sep 10, 09:06:23, Stephen Powell wrote: Nice work, Andrei! Not fair, you did the heavy lifting :) Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: sid: Console problems after starting X
On Sat, Sep 04, 2010 at 07:04:58PM +0300, Andrei Popescu wrote: On Sb, 04 sep 10, 09:06:23, Stephen Powell wrote: Nice work, Andrei! Not fair, you did the heavy lifting :) Both deserving of a beer, if not a pizza as well, to be collectible at some future FTF. -j Regards, Andrei -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100904190356.gb5...@sprite
Re: sid: Console problems after starting X
Hey, On Sat, 4 Sep 2010 01:20:51 -1000 Joel Roth jo...@pobox.com wrote: Thanks for checking this out! Console *does* VT switching correctly under a stock 2.6.31-1-amd64 kernel. (But for some reason suspend doesn't work... will try a later kernel.) Why didn't I think of this? Probably because the kernel was working before. I think the cause of the problem is that there was just an xorg and kernel update, this may have also updated the ATI driver, and as far i understand it, due to KMS, you have to upgrade the kernel modules in lockstep with the userspace bytes or unhappy things happen, like this. (I have very little experience with ATI and mainline graphics drivers, so I may be wrong! caveat emporium!) Mahalo Joel Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic If you still want to build your own kernel, build it off the updated debian src, or build the kernel modules into there own package. Or if you want to use a newer mainline, think about building the ati driver as well ;) -- Regards, Angus Hedger Debian GNU/Linux User PGP Public Key 0xEE6A4B97 signature.asc Description: PGP signature
Re: sid: Console problems after starting X
On Sat, Sep 04, 2010 at 08:37:55PM +0100, Angus Hedger wrote: Hey, On Sat, 4 Sep 2010 01:20:51 -1000 Joel Roth jo...@pobox.com wrote: Thanks for checking this out! Console *does* VT switching correctly under a stock 2.6.31-1-amd64 kernel. (But for some reason suspend doesn't work... will try a later kernel.) Why didn't I think of this? Probably because the kernel was working before. I think the cause of the problem is that there was just an xorg and kernel update, this may have also updated the ATI driver, and as far i understand it, due to KMS, you have to upgrade the kernel modules in lockstep with the userspace bytes or unhappy things happen, like this. (I have very little experience with ATI and mainline graphics drivers, so I may be wrong! caveat emporium!) Mahalo There do seem to be some kernel options that needed to be enabled, hence my success using a stock kernel. Thanks! Joel Joel Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic If you still want to build your own kernel, build it off the updated debian src, or build the kernel modules into there own package. Or if you want to use a newer mainline, think about building the ati driver as well ;) -- Regards, Angus Hedger Debian GNU/Linux User PGP Public Key 0xEE6A4B97 -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100904210255.ga2...@sprite
sid: Console problems after starting X
Hello all, Here's what happening. After boot: normal console font (about 80 characters wide) After startx: small console font (maybe 132 characters?) A little later: no display in console at all (Alt-F7 still gets me back to X) This problem appeared soon after converting to dependency-based boot process using insserv. I've been using a self-compiled amd64 kernel with 32-bit userland. No such problems before insserv. Thanks for any possible leads. I have no idea where to even start. thanks, Joel -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903105821.ga3...@sprite
Re: sid: Console problems after starting X
On Fri, Sep 03, 2010 at 12:58:21AM -1000, Joel Roth wrote: Hello all, Here's what happening. After boot: normal console font (about 80 characters wide) After startx: small console font (maybe 132 characters?) A little later: no display in console at all (Alt-F7 still gets me back to X) This problem appeared soon after converting to dependency-based boot process using insserv. I've been using a self-compiled amd64 kernel with 32-bit userland. No such problems before insserv. Thanks for any possible leads. I have no idea where to even start. Okay, here is one start. A boot message: udevd-work[905] kernel provided name 'uinput' and NAME='input/uinput' disagree. Please use SYMLINK+= or change kernel to provide proper name. This looks like a warning, not a failure. Another piece of the puzzle... I just did a dist-upgrade. (And another brokenness, suspend works once, second time is black screen (no backlight.) I should have known better not to dist-upgrade a well functioning system.) Regards, thanks, Joel -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903105821.ga3...@sprite -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903183300.gc3...@sprite
Re: sid: Console problems after starting X
On Fri, Sep 03, 2010 at 12:58:21AM -1000, Joel Roth wrote: Hello all, Here's what happening. After boot: normal console font (about 80 characters wide) After startx: small console font (maybe 132 characters?) A little later: no display in console at all (Alt-F7 still gets me back to X) This problem appeared soon after converting to dependency-based boot process using insserv. I've been using a self-compiled amd64 kernel with 32-bit userland. No such problems before insserv. Thanks for any possible leads. I have no idea where to even start. Yeah, that happened to me too, a while ago. It's the X driver. Specifically, it's the KMS settings that are messing you up. I hate KMS. It does solve certain problems for developers, but causes other problems for users. Maybe in a few years all these KMS-related bugs will get sorted out. But for now, they are a pain. How to fix it depends on your chipset. In one case, I had an nvidia card, and the upgrade switched me from the nv driver to the nouveau driver. I could get around it by blacklisting the nouveau driver and creating an explicit /etc/X11/xorg.conf file that specifies driver = nv in the appropriate place. For other chipsets, such as Intel, you may be able to set a module parameter like kms=0, or some such thing. Search the internet for your card manufacturer, Linux, and KMS, and maybe you'll find something. These techniques are only a temporary stopgap measure. Eventually, there will be no option. You will either have to use KMS or not use an X server at all. Oh joy. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1744286447.595363.1283545337251.javamail.r...@md01.wow.synacor.com
Re: sid: Console problems after starting X
On Fri, Sep 03, 2010 at 04:22:17PM -0400, Stephen Powell wrote: On Fri, Sep 03, 2010 at 12:58:21AM -1000, Joel Roth wrote: Hello all, Here's what happening. After boot: normal console font (about 80 characters wide) After startx: small console font (maybe 132 characters?) A little later: no display in console at all (Alt-F7 still gets me back to X) This problem appeared soon after converting to dependency-based boot process using insserv. I've been using a self-compiled amd64 kernel with 32-bit userland. No such problems before insserv. Thanks for any possible leads. I have no idea where to even start. Yeah, that happened to me too, a while ago. It's the X driver. Specifically, it's the KMS settings that are messing you up. I hate KMS. It does solve certain problems for developers, but causes other problems for users. Maybe in a few years all these KMS-related bugs will get sorted out. But for now, they are a pain. Good lead! For example, we have LKML posts such as: Re: Resume problem with radeon+KMS (2.6.34-rc2 and before) http://lkml.indiana.edu/hypermail/linux/kernel/1003.2/02225.html Which hits one of my problems as well. FWIW, here is my dmesg output regarding my ATI Radeon 3100 chip (RS780MC). I wonder about the 'loading firmware' bit, which seems to fail. [ 1478.833236] [drm] Initialized drm 1.1.0 20060810 [ 1478.934354] [drm] radeon kernel modesetting enabled. [ 1478.934483] radeon :01:05.0: setting latency timer to 64 [ 1478.939239] [drm] radeon: Initializing kernel modesetting. [ 1478.939410] [drm] register mmio base: 0x9630 [ 1478.939415] [drm] register mmio size: 65536 [ 1478.945526] ATOM BIOS: Tos_SCT10AP_MC [ 1478.945576] [drm] Clocks initialized ! [ 1478.945969] [drm] Detected VRAM RAM=256M, BAR=256M [ 1478.945978] [drm] RAM width 32bits DDR [ 1478.946151] [TTM] Zone kernel: Available graphics memory: 899812 kiB. [ 1478.946186] [drm] radeon: 256M of VRAM memory ready [ 1478.946191] [drm] radeon: 512M of GTT memory ready. [ 1478.946257] [drm] radeon: irq initialized. [ 1478.946263] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 1478.948761] [drm] Loading RS780 Microcode [ 1478.949103] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin [ 1479.022552] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin [ 1479.047423] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [ 1479.057460] r600_cp: Failed to load firmware radeon/R600_rlc.bin [ 1479.057476] [drm:r600_startup] *ERROR* Failed to load firmware! [ 1479.057483] radeon :01:05.0: disabling GPU acceleration [ 1479.057510] radeon :01:05.0: 88006df24000 unpin not necessary [ 1479.057517] radeon :01:05.0: 88006df24000 unpin not necessary [ 1479.057530] [drm] Enabling audio support [ 1479.057850] [drm] Radeon Display Connectors [ 1479.057855] [drm] Connector 0: How to fix it depends on your chipset. In one case, I had an nvidia card, and the upgrade switched me from the nv driver to the nouveau driver. I could get around it by blacklisting the nouveau driver and creating an explicit /etc/X11/xorg.conf file that specifies driver = nv in the appropriate place. For other chipsets, such as Intel, you may be able to set a module parameter like kms=0, or some such thing. Search the internet for your card manufacturer, Linux, and KMS, and maybe you'll find something. These techniques are only a temporary stopgap measure. Eventually, there will be no option. You will either have to use KMS or not use an X server at all. Oh joy. I expect it will be debugged in time. Regards, Joel -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1744286447.595363.1283545337251.javamail.r...@md01.wow.synacor.com -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903205759.ga4...@sprite
Re: sid: Console problems after starting X
On Fri, 03 Sep 2010 16:57:59 -0400 (EDT), Joel Roth wrote: FWIW, here is my dmesg output regarding my ATI Radeon 3100 chip (RS780MC). I wonder about the 'loading firmware' bit, which seems to fail. [ 1478.833236] [drm] Initialized drm 1.1.0 20060810 [ 1478.934354] [drm] radeon kernel modesetting enabled. [ 1478.934483] radeon :01:05.0: setting latency timer to 64 [ 1478.939239] [drm] radeon: Initializing kernel modesetting. [ 1478.939410] [drm] register mmio base: 0x9630 [ 1478.939415] [drm] register mmio size: 65536 [ 1478.945526] ATOM BIOS: Tos_SCT10AP_MC [ 1478.945576] [drm] Clocks initialized ! [ 1478.945969] [drm] Detected VRAM RAM=256M, BAR=256M [ 1478.945978] [drm] RAM width 32bits DDR [ 1478.946151] [TTM] Zone kernel: Available graphics memory: 899812 kiB. [ 1478.946186] [drm] radeon: 256M of VRAM memory ready [ 1478.946191] [drm] radeon: 512M of GTT memory ready. [ 1478.946257] [drm] radeon: irq initialized. [ 1478.946263] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 1478.948761] [drm] Loading RS780 Microcode [ 1478.949103] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin [ 1479.022552] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin [ 1479.047423] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [ 1479.057460] r600_cp: Failed to load firmware radeon/R600_rlc.bin [ 1479.057476] [drm:r600_startup] *ERROR* Failed to load firmware! [ 1479.057483] radeon :01:05.0: disabling GPU acceleration [ 1479.057510] radeon :01:05.0: 88006df24000 unpin not necessary [ 1479.057517] radeon :01:05.0: 88006df24000 unpin not necessary [ 1479.057530] [drm] Enabling audio support [ 1479.057850] [drm] Radeon Display Connectors [ 1479.057855] [drm] Connector 0: Aha! failed to load firmware! That may be your problem. You should always follow up on such messages. Do you have package firmware-linux-nonfree installed? If so, you need to install it. It is in the non-free section of the Debian archive; so make sure that the non-free and contrib sections of the archive are present in your /etc/apt/sources.list file. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/123733784.596256.1283548289546.javamail.r...@md01.wow.synacor.com
Re: sid: Console problems after starting X
On Fri, Sep 03, 2010 at 05:11:29PM -0400, Stephen Powell wrote: On Fri, 03 Sep 2010 16:57:59 -0400 (EDT), Joel Roth wrote: FWIW, here is my dmesg output regarding my ATI Radeon 3100 chip (RS780MC). I wonder about the 'loading firmware' bit, which seems to fail. [ 1478.948761] [drm] Loading RS780 Microcode [ 1478.949103] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin [ 1479.022552] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin [ 1479.047423] platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin [ 1479.057460] r600_cp: Failed to load firmware radeon/R600_rlc.bin [ 1479.057476] [drm:r600_startup] *ERROR* Failed to load firmware! [ 1479.057483] radeon :01:05.0: disabling GPU acceleration Aha! failed to load firmware! That may be your problem. You should always follow up on such messages. Do you have package firmware-linux-nonfree installed? If so, you need to install it. It is in the non-free section of the Debian archive; so make sure that the non-free and contrib sections of the archive are present in your /etc/apt/sources.list file. I installed firmware-linux-nonfree, and the *ERROR* message is gone. Also, the 'disabling GPU acceleration' message is gone. Which sounds like it can only be good. :-) However I have the same issue as before: First switch from X to virtual console: small font. Next switch: black screen. Thanks for your help with this. Joel -- .''`. Stephen Powell : :' : `. `'` `- -- Joel Roth -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100903213211.ga2...@sprite
Re: sid: Console problems after starting X
On Fri, 03 Sep 2010 17:32:12 -0400 (EDT), Joel Roth wrote: On Fri, Sep 03, 2010 at 05:11:29PM -0400, Stephen Powell wrote: Aha! failed to load firmware! That may be your problem. You should always follow up on such messages. Do you have package firmware-linux-nonfree installed? If so, you need to install it. It is in the non-free section of the Debian archive; so make sure that the non-free and contrib sections of the archive are present in your /etc/apt/sources.list file. I installed firmware-linux-nonfree, and the *ERROR* message is gone. Also, the 'disabling GPU acceleration' message is gone. Which sounds like it can only be good. :-) However I have the same issue as before: First switch from X to virtual console: small font. Next switch: black screen. Thanks for your help with this. Well, that needed to be done anyway. Unfortunately, it was not sufficient to solve the problem. But it's a step in the right direction. Please post the output of your /var/log/Xorg.0.log file. Maybe it will give me some ideas. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1313416886.599388.1283560530317.javamail.r...@md01.wow.synacor.com
Re: sid: Console problems after starting X
: vendor=X.Org Foundation compiled for 1.7.7, module version = 0.0.2 ABI class: X.Org Video Driver, version 6.0 (EE) open /dev/fb0: No such file or directory (II) RADEON(0): TOTO SAYS 9630 (II) RADEON(0): MMIO registers at 0x9630: size 64KB (II) RADEON(0): PCI bus 1 card 5 func 0 (II) RADEON(0): Creating default Display subsection in Screen section Default Screen Section for depth/fbbpp 24/32 (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) (==) RADEON(0): Default visual is TrueColor (II) Loading sub module vgahw (II) LoadModule: vgahw (II) Loading /usr/lib/xorg/modules/libvgahw.so (II) Module vgahw: vendor=X.Org Foundation compiled for 1.7.7, module version = 0.1.0 ABI class: X.Org Video Driver, version 6.0 (II) RADEON(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (==) RADEON(0): RGB weight 888 (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) (--) RADEON(0): Chipset: ATI Radeon 3100 Graphics (ChipID = 0x9613) (--) RADEON(0): Linear framebuffer at 0x8000 (II) RADEON(0): PCI card detected (II) Loading sub module int10 (II) LoadModule: int10 (II) Loading /usr/lib/xorg/modules/libint10.so (II) Module int10: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Video Driver, version 6.0 (II) RADEON(0): initializing int10 (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (II) RADEON(0): ATOM BIOS detected (II) RADEON(0): ATOM BIOS Rom: SubsystemVendorID: 0x1179 SubsystemID: 0xff6a IOBaseAddress: 0x6000 Filename: BR29079C.bin BIOS Bootup Message: Tos_SCT10AP_MC RS780MC DDR2 200e/500m (II) RADEON(0): Framebuffer space used by Firmware (kb): 20 (II) RADEON(0): Start of VRAM area used by Firmware: 0xfffb000 (II) RADEON(0): AtomBIOS requests 20kB of VRAM scratch space (II) RADEON(0): AtomBIOS VRAM scratch base: 0xfffb000 (II) RADEON(0): Cannot get VRAM scratch space. Allocating in main memory instead (II) RADEON(0): Default Engine Clock: 35 (II) RADEON(0): Default Memory Clock: 333000 (II) RADEON(0): Maximum Pixel ClockPLL Frequency Output: 120 (II) RADEON(0): Minimum Pixel ClockPLL Frequency Output: 0 (II) RADEON(0): Maximum Pixel ClockPLL Frequency Input: 13500 (II) RADEON(0): Minimum Pixel ClockPLL Frequency Input: 1000 (II) RADEON(0): Maximum Pixel Clock: 40 (II) RADEON(0): Reference Clock: 14320 drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci::01:05.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: drmOpenMinor returns 11 drmOpenByBusid: drmGetBusid reports pci::01:05.0 (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch. [dri] This chipset requires a kernel module version of 1.17.0, [dri] but the kernel reports a version of 2.0.0.[dri] If using legacy modesetting, upgrade your kernel. [dri] If using kernel modesetting, make sure your module is [dri] loaded prior to starting X, and that this driver was built [dri] with support for KMS. [dri] Disabling DRI. (II) RADEON(0): using shadow framebuffer (II) Loading sub module shadow (II) LoadModule: shadow (II) Loading /usr/lib/xorg/modules/libshadow.so (II) Module shadow: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.1.0 ABI class: X.Org ANSI C Emulation, version 0.4 (II) RADEON(0): Detected total video RAM=262144K, accessible=262144K (PCI BAR=262144K) (--) RADEON(0): Mapped VideoRAM: 262144 kByte (128 bit DDR SDRAM) (II) RADEON(0): Color tiling disabled (II) Loading sub module ddc (II) LoadModule: ddc (II) Module ddc already built-in (II) Loading sub module i2c (II) LoadModule: i2c (II) Module i2c already built-in (II) RADEON(0): PLL parameters: rf=1432 rd=12 min=9 max=12; xclk=4 (WW) RADEON(0): LVDS Info: XRes: 1280, YRes: 800, DotClock: 69300 HBlank: 136, HOverPlus: 48, HSyncWidth: 24 VBlank: 16, VOverPlus: 3, VSyncWidth: 6 (II) RADEON(0): Output LVDS has no monitor section (II) RADEON(0): I2C bus LVDS initialized. (II) RADEON(0): Output VGA-0 has no monitor section (II) RADEON(0): I2C bus VGA-0 initialized. (II) RADEON(0): Port0: XRANDR name: LVDS Connector: LVDS LCD1: INTERNAL_KLDSCP_LVTMA DDC reg: 0x7e50 (II) RADEON(0): Port1: XRANDR name: VGA-0 Connector: VGA CRT1: INTERNAL_KLDSCP_DAC1 DDC reg: 0x7e40 (II) RADEON(0): I2C device LVDS:ddc2 registered at address 0xA0. (II) RADEON(0): EDID for output LVDS (II) RADEON(0): Manufacturer: LPL Model: 120 Serial#: 0 (II) RADEON(0): Year: 2008 Week: 0 (II) RADEON(0): EDID Version: 1.3 (II) RADEON(0): Digital Display Input (II) RADEON(0): Max Image Size [cm]: horiz.: 33 vert.: 21 (II) RADEON(0): Gamma: 2.20 (II) RADEON(0): No DPMS capabilities specified (II) RADEON(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 (II) RADEON(0): First
black screen when starting X on radeon HD4850 with xserver-xorg-video-radeon 1:6.13
Hi everybody, Please, CC: me, as I am not subscribed to the list. I am running Debian sid on an Apple iMac 27, with a Mobility Radeon HD 4850 video card (ATI Technologies Inc M98L). The kernel I use is 2.6.33-2 from experimental, and I have disable KMS. Depending on the version of the radeon driver I use, I see or not something on the screen: - with 1:6.12.192-2, everything startx correctly when I launch startx from the command line. - with 1:6.13.0-1, the screen becomes black, and it is impossible to go back to a console using Alt+Ctl+F?. However, I can ssh to the system, and see using ps that the KDE session has indeed started. Here are in attachment the two logs: failed is with 6.13, and success is with 6.12.192. Has someone an idea of what is going on? Is there an option I could add to my (at the moment empty) xorg.conf to remedy this problem? Best regards, Cédric Xorg.0.log.failed2.gz Description: Binary data Xorg.0.log.success2.gz Description: Binary data signature.asc Description: Digital signature
lcd brightness goes up when starting X
Hi, I installed Lenny on my ThinkPad R51. It has an Intel 82852/855GM graphics card. After executing startx the LCD goes 100% bright. Same thing happens if I wake up the LCD from sleep (xset +dpms). My Fn + Home/End keys work fine and i can adjust the brightness. But its annoying to do it everytime I boot up and start X. Any solutions ? -Arun PS: Am not subscribed to the list, so please CC me while replying. Thanks. -- ...Keep Smiling... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
I recall seeing something along that line in the , known issues after installing Lenny , in the install notes. about the display not using all the screen, they had a fix for it also. thanks Norm On Tue, Feb 17, 2009 at 1:13 AM, S D sund...@yahoo.com wrote: --- On Tue, 2/17/09, Boyd Stephen Smith Jr. b...@iguanasuicide.net wrote: Probably need to add some modes or modelines to your xorg.conf. Might try dpkg-reconfigure xserver-xorg (or sth like that) to get the resolution you want. I checked xorg.conf, it already has 1600x1200 line entries. Besides, the KDE configuration utility (Control Center | Peripherals | Display) shows that the monitor *is* running in the 1600x1200 mode. However, the picture doesn't use the whole available screen space. Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
2009/2/17 S D sund...@yahoo.com --- On Tue, 2/17/09, Boyd Stephen Smith Jr. b...@iguanasuicide.net wrote: For the ati module, you need the package: p xserver-xorg-video-ati - X.Org X server -- ATI display driver Installed the xserver-xorg-video-ati package and it did resolve the issue somewhat. I was able to start X and KDE, KDE is running and and appears to be functional (v 3.5.10) but the picture looks very strange indeed. The picture now, for some reason, doesn't use the whole available screen space but leave unused areas about 3-5 cm from the left, right, top and bottom monitor edges. It looks something like this: +1--+ | | | | |+---2-+| || || || || || || |+-+| | | | | +---+ Where 1 is the monitor and 2 is the picture. I usually run my monitor in 1600x1200 mode and KDE shows it as the current resolution. Any ideas? Thanks I had a similar problem after the upgrade to Lenny. My problem was that at GDM login the screen was a bit to left but inside GNOME was fine. GNOME was forcing vertical refresh rate at 75 but X was using 60, thus I had tha difference. Try the following 1) inside GNOME/KDE open a terminal and run xvidtune and tune the settings as you wish. Then click on show button, this will print on the terminal the setting to be used in xorg.conf. 2) Use the above info to add a Modeline in the Monitor section on your xorg.conf Furthermore, make sure the same Modeline name is in the Screen Section Here is a snap of my xorg.conf, take a look at 1280x1...@75 Section Monitor Identifier SDM-HS75P HorizSync 28-80 VertRefresh 48-75 Option DPMS Modeline 1280x1...@75 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync EndSection Section Screen Identifier Default Screen Device Nvidia FX5500 Monitor SDM-HS75P DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1280x1...@75 1024x768 800x600 640x480 EndSubSection EndSection 3) restart X Hope it helps, Pavlos
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
--- On Tue, 2/17/09, pavlos.paris wrote: Try the following 1) inside GNOME/KDE open a terminal and run xvidtune and tune the settings as you wish. Then click on show button, this will print on the terminal the setting to be used in xorg.conf. Weird, when I try to run (as root) xvidtune from a terminal window I get: # xvidtune Error: Can't open display: And it's true, I don't have a Modeline entry in the Monitor section of the /etc/X11/xorg.conf Any ideas? Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
On Tue, 17 Feb 2009 12:08:26 -0800 (PST) S D sund...@yahoo.com wrote: --- On Tue, 2/17/09, pavlos.paris wrote: Try the following 1) inside GNOME/KDE open a terminal and run xvidtune and tune the settings as you wish. Then click on show button, this will print on the terminal the setting to be used in xorg.conf. Weird, when I try to run (as root) xvidtune from a terminal window I get: # xvidtune Error: Can't open display: And it's true, I don't have a Modeline entry in the Monitor section of the /etc/X11/xorg.conf Any ideas? Thanks You don't need root access in order to run that command. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
--- On Tue, 2/17/09, Pavlos Parissis p_pav...@freemail.gr wrote:
You don't need root access in order to run that
command.
True, but if I run it as a regular user, it gets even funnier:
$ which xvidtune
/usr/bin/xvidtune
$ `which xvidtune`
Please install the program before using
$ /usr/bin/xvidtune
Please install the program before using
It appears some people also had this issue but no solution was provided:
xvidtune always appeared accessible and judging from the below 'c' code the
message is internally generated.
http://www.x.org/pub/unsupported/pro...une/xvidtune.c
if (!AppRes.ad_installed) {fprintf(stderr, Please install the program before
using\n); return 3;}
Maybe an understanding of how the boolean ad_installed is set would clarify
matters.
Thanks
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
On Tue, 17 Feb 2009 13:06:48 -0800 (PST)
S D sund...@yahoo.com wrote:
--- On Tue, 2/17/09, Pavlos Parissis p_pav...@freemail.gr wrote:
You don't need root access in order to run that
command.
True, but if I run it as a regular user, it gets even funnier:
$ which xvidtune
/usr/bin/xvidtune
$ `which xvidtune`
Please install the program before using
$ /usr/bin/xvidtune
Please install the program before using
It appears some people also had this issue but no solution was provided:
xvidtune always appeared accessible and judging from the below 'c' code the
message is internally generated.
http://www.x.org/pub/unsupported/pro...une/xvidtune.c if
(!AppRes.ad_installed)
{fprintf(stderr, Please install the program before using\n); return 3;}
Maybe an
understanding of how the boolean ad_installed is set would clarify matters.
Thanks
[pparis...@spartacos][~]$
id -a
uid=1000(pparissis) gid=1000(pparissis)
groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),34(backup),40(src),44(video),46(plugdev),1000(pparissis)
[pparis...@spartacos][~]$
which xvidtune
/usr/bin/xvidtune
[pparis...@spartacos][~]$
dpkg -S /usr/bin/xvidtune
x11-xserver-utils: /usr/bin/xvidtune
[pparis...@spartacos][~]$
aptitude show x11-xserver-utils|grep Version
Version: 7.3+5
[pparis...@spartacos][~]$
xvidtune
Vendor: (null), Model: (null)
Num hsync: 1, Num vsync: 1
hsync range 0: 28.00 - 80.00
vsync range 0: 48.00 - 75.00
1280x1024 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
[pparis...@spartacos][~]$
cat /etc/debian_version
5.0
BTW, have you seen this ?
http://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#vga-output-bug
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
--- On Tue, 2/17/09, Pavlos Parissis p_pav...@freemail.gr wrote: [pparis...@spartacos][~]$ id -a uid=1000(pparissis) gid=1000(pparissis) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),34(backup),40(src),44(video),46(plugdev),1000(pparissis) [pparis...@spartacos][~]$ which xvidtune /usr/bin/xvidtune [pparis...@spartacos][~]$ dpkg -S /usr/bin/xvidtune x11-xserver-utils: /usr/bin/xvidtune [pparis...@spartacos][~]$ aptitude show x11-xserver-utils|grep Version Version: 7.3+5 [pparis...@spartacos][~]$ xvidtune Vendor: (null), Model: (null) Num hsync: 1, Num vsync: 1 hsync range 0: 28.00 - 80.00 vsync range 0: 48.00 - 75.00 1280x1024 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync [pparis...@spartacos][~]$ cat /etc/debian_version 5.0 I see no discrepancies when it comes to x11-xserver-utils or debian version. But my xvidtune doesn't run. BTW, have you seen this ? http://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#vga-output-bug Yes, I'm not using Intel Mobile GM965 though. I filed a bug, it has more info (http://bugs.debian.org/cgi-binbugreport.cgi?bug=515840 ). Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
After dist-upgrade from etch to lenny, I'm trying to run lenny using 2.6.18 kernel that I have left over from etch, as I'm having issues assembling mdadm RAID drives under the new 2.6.28 lenny kernel (For more info see http://groups.google.com/group/linux.debian.user/browse_thread/thread/b97fd9b0a450370f# ) The problem now is that when I try to start X, it fails complaining that: (EE) Failed to load module type1 (module doesn't exist, 0) (EE) Failed to load module ait (module doesn't exist, 0) (E) No drivers available. Fatal server error: no screens found, giving up Any ideas? Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
On Monday 16 February 2009 16:13:29 S D wrote: (EE) Failed to load module ait (module doesn't exist, 0) For the ati module, you need the package: p xserver-xorg-video-ati - X.Org X server -- ATI display driver -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
--- On Tue, 2/17/09, Boyd Stephen Smith Jr. b...@iguanasuicide.net wrote: For the ati module, you need the package: p xserver-xorg-video-ati - X.Org X server -- ATI display driver Installed the xserver-xorg-video-ati package and it did resolve the issue somewhat. I was able to start X and KDE, KDE is running and and appears to be functional (v 3.5.10) but the picture looks very strange indeed. The picture now, for some reason, doesn't use the whole available screen space but leave unused areas about 3-5 cm from the left, right, top and bottom monitor edges. It looks something like this: +1--+ | | | | |+---2-+| || || || || || || |+-+| | | | | +---+ Where 1 is the monitor and 2 is the picture. I usually run my monitor in 1600x1200 mode and KDE shows it as the current resolution. Any ideas? Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
On Monday 16 February 2009 21:58:13 S D wrote: The picture now, for some reason, doesn't use the whole available screen space but leave unused areas about 3-5 cm from the left, right, top and bottom monitor edges. It looks something like this: I usually run my monitor in 1600x1200 mode and KDE shows it as the current resolution. Probably need to add some modes or modelines to your xorg.conf. Might try dpkg-reconfigure xserver-xorg (or sth like that) to get the resolution you want. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Lenny upgrade: Failed to load modules ati and typ1 when starting X. No drivers available
--- On Tue, 2/17/09, Boyd Stephen Smith Jr. b...@iguanasuicide.net wrote: Probably need to add some modes or modelines to your xorg.conf. Might try dpkg-reconfigure xserver-xorg (or sth like that) to get the resolution you want. I checked xorg.conf, it already has 1600x1200 line entries. Besides, the KDE configuration utility (Control Center | Peripherals | Display) shows that the monitor *is* running in the 1600x1200 mode. However, the picture doesn't use the whole available screen space. Thanks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Small package on console after starting X
On Mon, Oct 08, 2007 at 11:41:41PM -0400, Patrick Wiseman wrote: On 10/8/07, Douglas A. Tutty [EMAIL PROTECTED] wrote: On Mon, Oct 08, 2007 at 05:15:55PM -0400, Patrick Wiseman wrote: I have this odd phenomenon, which I suspect indicates some sort of attack. After I start X, when I return to a console (with Ctl-Alt-Fx) there's what looks like a little package sitting in the bottom, right-hand quarter of my screen. After I Alt-7 back to X, and then Ctl-Alt-Fx back to a console, it's gone. Any ideas what it might be, and how to rid myself of it? I've used rkhunter and chkrootkit, neither of which reports anything amiss, but that may be meaningless. What does this package look like? Is it a single non-alphanumeric char? No, I don't think so, as it's bigger (maybe 4x) than the other characters on the console. And it's bright, where everything else, after I launch X, is dim. Weird, I know. I'll see if I can take a picture of it. Do you use a frame-buffer for your text console? If so, it could be video memory corruption (garbage left around during the switch). Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Small package on console after starting X
Hello: I have this odd phenomenon, which I suspect indicates some sort of attack. After I start X, when I return to a console (with Ctl-Alt-Fx) there's what looks like a little package sitting in the bottom, right-hand quarter of my screen. After I Alt-7 back to X, and then Ctl-Alt-Fx back to a console, it's gone. Any ideas what it might be, and how to rid myself of it? I've used rkhunter and chkrootkit, neither of which reports anything amiss, but that may be meaningless. Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Small package on console after starting X
On Mon, Oct 08, 2007 at 05:15:55PM -0400, Patrick Wiseman wrote: I have this odd phenomenon, which I suspect indicates some sort of attack. After I start X, when I return to a console (with Ctl-Alt-Fx) there's what looks like a little package sitting in the bottom, right-hand quarter of my screen. After I Alt-7 back to X, and then Ctl-Alt-Fx back to a console, it's gone. Any ideas what it might be, and how to rid myself of it? I've used rkhunter and chkrootkit, neither of which reports anything amiss, but that may be meaningless. What does this package look like? Is it a single non-alphanumeric char? Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Small package on console after starting X
On 10/8/07, Douglas A. Tutty [EMAIL PROTECTED] wrote: On Mon, Oct 08, 2007 at 05:15:55PM -0400, Patrick Wiseman wrote: I have this odd phenomenon, which I suspect indicates some sort of attack. After I start X, when I return to a console (with Ctl-Alt-Fx) there's what looks like a little package sitting in the bottom, right-hand quarter of my screen. After I Alt-7 back to X, and then Ctl-Alt-Fx back to a console, it's gone. Any ideas what it might be, and how to rid myself of it? I've used rkhunter and chkrootkit, neither of which reports anything amiss, but that may be meaningless. What does this package look like? Is it a single non-alphanumeric char? No, I don't think so, as it's bigger (maybe 4x) than the other characters on the console. And it's bright, where everything else, after I launch X, is dim. Weird, I know. I'll see if I can take a picture of it. Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X fails: out of scan range
libre fan wrote:
libre fan wrote:
Last Friday I updated Debian (lot of xorg stuff was updated) and when I
rebooted I got this message on the screen: out of scan range
I reconfigured several times trying to correct errors, and I compared the
original Xfree config file with the present xorg.config. I really don't know
how to put the matter straight.
Something else you may want to try:
1) Shutdown your system for maintenance if possible (otherwise stop X
from running)
2) Save a copy of your /etc/X/xorg.conf file somewhere (other than in
/etc/X)
3) Remove the 'xorg.conf' file in /etc/X
4) run dexconf ('man dexconf' to see what this command does)
HTH
--
Sincerely
Jose Alburquerque
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X fails: out of scan range
libre fan wrote: Last Friday I updated Debian (lot of xorg stuff was updated) and when I rebooted I got this message on the screen: out of scan range I reconfigured several times trying to correct errors, and I compared the original Xfree config file with the present xorg.config. I really don't know how to put the matter straight. I set the default depths at 16 then later at 24. I set the default and only resolution at 1024x768 because this has always worked. Here are snippets from the latest Xorg.log (/var/log/Xorg.0.log): (--) MGA(0): Chipset: mgag200 (**) MGA(0): Depth 24, (--) framebuffer bpp 32 (==) MGA(0): RGB weight 888 (==) MGA(0): Using AGP 1x mode (--) MGA(0): Linear framebuffer at 0xF500 (--) MGA(0): VideoRAM: 8192 kByte (II) MGA(0): Supported VESA Video Modes: ... (II) MGA(0): [EMAIL PROTECTED] (interlaced) (II) MGA(0): [EMAIL PROTECTED] (II) MGA(0): [EMAIL PROTECTED] (II) MGA(0): [EMAIL PROTECTED] (II) MGA(0): [EMAIL PROTECTED] ... (==) MGA(0): Min pixel clock is 17 MHz (--) MGA(0): Max pixel clock is 250 MHz (II) MGA(0): Sony CDP-110GS/EST: Using hsync range of 30.00-70.00 kHz (II) MGA(0): Sony CDP-110GS/EST: Using vrefresh range of 48.00-120.00 Hz (II) MGA(0): Clock range: 17.75 to 250.00 MHz (WW) (1024x768,Sony CDP-110GS/EST) mode clock 94.5MHz exceeds DDC maximum 0MHz (WW) (1024x768,Sony CDP-110GS/EST) mode clock 133.475MHz exceeds DDC maximum 0MHz (II) MGA(0): Not using default mode 1024x768 (hsync out of range) (--) MGA(0): Virtual size is 1024x768 (pitch 1024) (**) MGA(0): *Default mode 1024x768: 94.5 MHz, 68.7 kHz, 85.0 Hz (II) MGA(0): Modeline 1024x768 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync ... BTW I also get font errors, like this: (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/misc. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/misc). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/100dpi/.Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/100dpi/). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/75dpi/. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/75dpi/). (WW) `fonts.dir' not found (or not valid) in /usr/X11R6/lib/X11/fonts/100dpi. Entry deleted from font path. (Run 'mkfontdir' on /usr/X11R6/lib/X11/fonts/100dpi). ... I no longer get errors in the log file still the message out of scan range is displayed after I type startx. Your help would be much appreciated! cheers, libre fan -- View this message in context: http://www.nabble.com/starting-X-fails%3A-out-of-scan-range-tf2330274.html#a6633861 Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
starting X fails: out of scan range
Hello, I have a Debian Etch+Sid and Xubuntu Dapper dual-boot. Last Friday I updated Debian (lot of xorg stuff was updated) and when I rebooted I got this message on the screen: out of scan range Though X is started (I typed startx on a terminal) Wdm (my display manager) doesn't load. Is the message to do with the monitor config? Everyting worked fine before hand -- I have had Debian-based distros for about three years now without any hardware problems. What can I do? Can you help me? perhaps I could downgrade: comment the sid lines oin my sources.list, pat-get get update, uninstall x.org, reinstall it from the Etch repositories? There must be a simpler way. Run xorg config? Many thanks in advance! -- View this message in context: http://www.nabble.com/starting-X-fails%3A-out-of-scan-range-tf2330274.html#a6482623 Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X fails: out of scan range
libre fan wrote:
Hello,
I have a Debian Etch+Sid and Xubuntu Dapper dual-boot.
Last Friday I updated Debian (lot of xorg stuff was updated) and when I
rebooted I got this message on the screen: out of scan range
Though X is started (I typed startx on a terminal) Wdm (my display
manager) doesn't load.
Is the message to do with the monitor config? Everyting worked fine before
hand -- I have had Debian-based distros for about three years now without
any hardware problems.
What can I do? Can you help me? perhaps I could downgrade: comment the sid
lines oin my sources.list, pat-get get update, uninstall x.org, reinstall it
from the Etch repositories?
There must be a simpler way. Run xorg config?
Many thanks in advance!
Sounds to me like the error your getting is because your monitor
settings are not correct in your /etc/X/xorg.conf file. You probably
replaced your config when you updated. Reconfiguring the xserver-xorg
package ('sudo dpkg-reconfigure xserver-xorg') might fix your problem.
--
Sincerely
Jose Alburquerque
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X fails: out of scan range
Jos? Alburquerque-3 wrote:
libre fan wrote:
Last Friday I updated Debian (lot of xorg stuff was updated) and when I
rebooted I got this message on the screen: out of scan range
Sounds to me like the error your getting is because your monitor
settings are not correct in your /etc/X/xorg.conf file. You probably
replaced your config when you updated. Reconfiguring the xserver-xorg
package ('sudo dpkg-reconfigure xserver-xorg') might fix your problem.
I did reconfigure as you suggest. I get two error messages: no usable
screen and no frame buffer found. I see there's an option in the
dpkg-reconfigure xserver-xorg process to do without the frame buffer. i'll
check again if I disabled this option.
I compared the xorg.conf files in Debian and in Xubuntu, and corrected the
reference of the screen.
Cheers
--
View this message in context:
http://www.nabble.com/starting-X-fails%3A-out-of-scan-range-tf2330274.html#a6499854
Sent from the Debian User mailing list archive at Nabble.com.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X makes the screen go white (newb - new install)
Could have found what's causing the issue. I have no idea what he's talking about though... Looking in to it now, but any help is appreciated. Jeroen --- start quote --- Framebuffer/X notes New - I managed to replace the atyfb code of 2.4.27 with the one of 2.4.16. This means there are dozens of new drivers available for for users which need the framebuffer-patch. Due to its completely different design, 2.6.8.x kernels still bring along difficulties in respect of forward porting. Anyway, the resulting 2.4.27 kernel is available as a deb-package. Using kernel 2.4.16 with or without full-width console patch works fine with X. Mind that the following modeline is required: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 -hsync - vsync The atyfb of 2.4.18 and later seems to have changed a lot. The full- width console patch doesn't apply cleanly anymore - not even this one. If framebuffer support is compiled in, Xfree86 4.3 whites the screen slowly which doesn't look healthy. Not even the modeline entry helps. Xserver-mach64 works insufficiently (corrupts the screen and mouse-input is translated horribly). I'm trying to insert the 2.4.16 atyfb code into higher kernels (probably 2.6.8). Results will be published here upon success. --- end quote --- from http://gefechtsdienst.de/uman/c1ve-general.html On 06 Sep 2005, at 00:54, jeroen wrote: Sorry if this came in double, the resend i did might have tricked your mail rules (it did trick mine) Jeroen On 05 Sep 2005, at 22:19, Oliver Lupton wrote: I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. #gdm returns a command not found On 05 Sep 2005, at 22:25, Kent West wrote: jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. It's getting late now, and my primary concern is getting something of a GUI, ifup isn't that hard to type ;). But many thanks for pointing me to the solution. Greatly appreciated! Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? When i comment out the modeline (and un-comment out the HorizSync and VertRefresh) i get the same white screen. What other minor changes did you make? My complete config can now be found @ http://www.yuru.be/debian/XF86Config-4 other changes i made are: /OptionXkbLayoutukto -OptionXkbLayoutgb Probably nothing serious or X killing, just changed it to the working config i found on the cam.ac.uk site /IdentifierConfigured Mouse /OptionEmulate3Buttontrue /OptionZAxisMapping4 5 to -IdentifierConfigured Mouse -OptionButtons5 -OptionZAxisMapping5 4 Same here, just copied it, hoping it would work like a charm. Other changes are: Adding the modeline and commenting out the HorizSync and VertRefresh. The last thing i changed where all resolutions in the Display Subsections of the Screen Section (was 320x240 640x480) Ctrl-Alt-Backspace should kill it from within X. Hey cool, thanks! I was trying to do that with Ctrl-Alt-Delete... With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. You can double-check this possibility by installing another wm (aptitude install icewm, etc), or make sure you've got xterm installed (aptitude install xterm) and then put icewm or xterm in the file ~/.xinitrc (you'll probably have to create the file), and then run startx. If you put icewm in ~/.initrc, Icewm should start up; if you put xterm, you should get an xterm (with no window controls; you can type exit to shut down X in such a case). Tried this, with both suggested wms (and both .xinitrc and .initrc - was this a typo or are they indeed different?), they produce the same white screen. You where right that i had to create both files. I renamed them so there never was both a .xinitrc and and .initrc in my ~/. Remember that USB disk you mentioned? I bet it works with USB fobs as well. Doh! Thanks for that. It's the only floppy drive i have so i have to plug it in and out, it works, that's most important. I do have a problem with copying my XFree86.0.log, It gives a -36 error when i try to copy it over to my mac. I'll look into that
Re: starting X makes the screen go white (newb - new install)
This is starting to look like a blog ;) I installed the kernel found on the previously mentioned page (http:// gefechtsdienst.de/uman/c1ve-general.html). It doesn't look really nice. Full screen console is built in but is shifted (not placed correctly, with white band down the screen). Startx (with fvwm) works fine. That means i get to see the graphical login screen now... the screen itself doesn't really look nice, with stripes all over the place. As mentioned in the above page the problems with the white screen allegedly happen with Xfree86 4.3. I'm now looking into removing the version i have running now and replace it with a previous version. If i get this to work with the standard default kernel i will be a happy man. kernel compiling is a bit over the top for me right now i think. Maybe next week ;D Cheers, Jeroen On 06 Sep 2005, at 20:35, jeroen wrote: Could have found what's causing the issue. I have no idea what he's talking about though... Looking in to it now, but any help is appreciated. Jeroen --- start quote --- Framebuffer/X notes New - I managed to replace the atyfb code of 2.4.27 with the one of 2.4.16. This means there are dozens of new drivers available for for users which need the framebuffer-patch. Due to its completely different design, 2.6.8.x kernels still bring along difficulties in respect of forward porting. Anyway, the resulting 2.4.27 kernel is available as a deb-package. Using kernel 2.4.16 with or without full-width console patch works fine with X. Mind that the following modeline is required: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 - hsync -vsync The atyfb of 2.4.18 and later seems to have changed a lot. The full- width console patch doesn't apply cleanly anymore - not even this one. If framebuffer support is compiled in, Xfree86 4.3 whites the screen slowly which doesn't look healthy. Not even the modeline entry helps. Xserver-mach64 works insufficiently (corrupts the screen and mouse-input is translated horribly). I'm trying to insert the 2.4.16 atyfb code into higher kernels (probably 2.6.8). Results will be published here upon success. --- end quote --- from http://gefechtsdienst.de/uman/c1ve-general.html On 06 Sep 2005, at 00:54, jeroen wrote: Sorry if this came in double, the resend i did might have tricked your mail rules (it did trick mine) Jeroen On 05 Sep 2005, at 22:19, Oliver Lupton wrote: I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. #gdm returns a command not found On 05 Sep 2005, at 22:25, Kent West wrote: jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. It's getting late now, and my primary concern is getting something of a GUI, ifup isn't that hard to type ;). But many thanks for pointing me to the solution. Greatly appreciated! Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? When i comment out the modeline (and un-comment out the HorizSync and VertRefresh) i get the same white screen. What other minor changes did you make? My complete config can now be found @ http://www.yuru.be/debian/XF86Config-4 other changes i made are: /OptionXkbLayoutukto -OptionXkbLayoutgb Probably nothing serious or X killing, just changed it to the working config i found on the cam.ac.uk site /IdentifierConfigured Mouse /OptionEmulate3Buttontrue /OptionZAxisMapping4 5 to -IdentifierConfigured Mouse -OptionButtons5 -OptionZAxisMapping5 4 Same here, just copied it, hoping it would work like a charm. Other changes are: Adding the modeline and commenting out the HorizSync and VertRefresh. The last thing i changed where all resolutions in the Display Subsections of the Screen Section (was 320x240 640x480) Ctrl-Alt-Backspace should kill it from within X. Hey cool, thanks! I was trying to do that with Ctrl-Alt-Delete... With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. You can double-check this possibility by installing another wm (aptitude install icewm, etc), or make sure you've got xterm installed (aptitude install xterm) and then
Re: starting X makes the screen go white (newb - new install)
continuing blog i installed the x-server from woody, x starts up fine now, jeej! i guess this issue is closed, unless this was a bad idea. Thx for reading my ramblings, Jeroen On 06 Sep 2005, at 21:06, jeroen wrote: This is starting to look like a blog ;) I installed the kernel found on the previously mentioned page (http://gefechtsdienst.de/uman/c1ve-general.html). It doesn't look really nice. Full screen console is built in but is shifted (not placed correctly, with white band down the screen). Startx (with fvwm) works fine. That means i get to see the graphical login screen now... the screen itself doesn't really look nice, with stripes all over the place. As mentioned in the above page the problems with the white screen allegedly happen with Xfree86 4.3. I'm now looking into removing the version i have running now and replace it with a previous version. If i get this to work with the standard default kernel i will be a happy man. kernel compiling is a bit over the top for me right now i think. Maybe next week ;D Cheers, Jeroen On 06 Sep 2005, at 20:35, jeroen wrote: Could have found what's causing the issue. I have no idea what he's talking about though... Looking in to it now, but any help is appreciated. Jeroen --- start quote --- Framebuffer/X notes New - I managed to replace the atyfb code of 2.4.27 with the one of 2.4.16. This means there are dozens of new drivers available for for users which need the framebuffer-patch. Due to its completely different design, 2.6.8.x kernels still bring along difficulties in respect of forward porting. Anyway, the resulting 2.4.27 kernel is available as a deb-package. Using kernel 2.4.16 with or without full-width console patch works fine with X. Mind that the following modeline is required: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 - hsync -vsync The atyfb of 2.4.18 and later seems to have changed a lot. The full-width console patch doesn't apply cleanly anymore - not even this one. If framebuffer support is compiled in, Xfree86 4.3 whites the screen slowly which doesn't look healthy. Not even the modeline entry helps. Xserver-mach64 works insufficiently (corrupts the screen and mouse-input is translated horribly). I'm trying to insert the 2.4.16 atyfb code into higher kernels (probably 2.6.8). Results will be published here upon success. --- end quote --- from http://gefechtsdienst.de/uman/c1ve-general.html On 06 Sep 2005, at 00:54, jeroen wrote: Sorry if this came in double, the resend i did might have tricked your mail rules (it did trick mine) Jeroen On 05 Sep 2005, at 22:19, Oliver Lupton wrote: I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. #gdm returns a command not found On 05 Sep 2005, at 22:25, Kent West wrote: jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. It's getting late now, and my primary concern is getting something of a GUI, ifup isn't that hard to type ;). But many thanks for pointing me to the solution. Greatly appreciated! Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? When i comment out the modeline (and un-comment out the HorizSync and VertRefresh) i get the same white screen. What other minor changes did you make? My complete config can now be found @ http://www.yuru.be/debian/XF86Config-4 other changes i made are: /OptionXkbLayoutukto -OptionXkbLayoutgb Probably nothing serious or X killing, just changed it to the working config i found on the cam.ac.uk site /IdentifierConfigured Mouse /OptionEmulate3Buttontrue /OptionZAxisMapping4 5 to -IdentifierConfigured Mouse -OptionButtons5 -OptionZAxisMapping5 4 Same here, just copied it, hoping it would work like a charm. Other changes are: Adding the modeline and commenting out the HorizSync and VertRefresh. The last thing i changed where all resolutions in the Display Subsections of the Screen Section (was 320x240 640x480) Ctrl-Alt-Backspace should kill it from within X. Hey cool, thanks! I was trying to do that with Ctrl-Alt-Delete... With my limited knowledge i though i could have forgotten to add a window
starting X makes the screen go white (newb - new install)
Hello all, --intro I'm trying (finally) to get debian to work on my Vaio PCG-C1VE. Using the latest version of the installer (floppy images) i succeeded in installing 3.1 on the little b*st*rd. Previous versions didn't support USB disks (at least not on a noob level) so thx debian! I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Once i got the machine to boot from its own HD i though it would be nice to have GUI to learn my way around debian (and linux in general). --/intro fresh install i did: #apt-get install x-window-system #apt-get install gnome immediately after this i used vi to change my /etc/X11/XF86Config-4. The most important change i did was adding this modeline: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 -hsync - vsync together with some other minor changes i found on http://www- jcsu.jesus.cam.ac.uk/~mma29/c1/ #startx works fine (this means it starts up ;-/ ), the only thing i get to see is a black screen which bleeds to a very white blue (starting at the edges). Some vertical and horizontal lines can be seen as well, all at the edge of some very white colours. Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) The only way to get me out of this white hell is by tapping Ctrl-Alt- F1, followed by Ctrl-C to stop the X server. With my limited knowledge i though i could have forgotten to add a window manager (didn't i read somewhere that this is not included in gnome??) so i did #apt-get install fvwm nothing changed. So here i am writing this mail, hoping somebody here can put me on the right track. Thx for taking the time to read this, Jeroen I would include my XFree86.0.log but i have no idea how to get it of the laptop (skipped mail config in debian installer...) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X makes the screen go white (newb - new install)
jeroen wrote: Hello all, --intro I'm trying (finally) to get debian to work on my Vaio PCG-C1VE. Using the latest version of the installer (floppy images) i succeeded in installing 3.1 on the little b*st*rd. Previous versions didn't support USB disks (at least not on a noob level) so thx debian! I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Once i got the machine to boot from its own HD i though it would be nice to have GUI to learn my way around debian (and linux in general). --/intro fresh install i did: #apt-get install x-window-system #apt-get install gnome immediately after this i used vi to change my /etc/X11/XF86Config-4. The most important change i did was adding this modeline: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 -hsync - vsync together with some other minor changes i found on http://www- jcsu.jesus.cam.ac.uk/~mma29/c1/ #startx works fine (this means it starts up ;-/ ), the only thing i get to see is a black screen which bleeds to a very white blue (starting at the edges). Some vertical and horizontal lines can be seen as well, all at the edge of some very white colours. Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) The only way to get me out of this white hell is by tapping Ctrl-Alt- F1, followed by Ctrl-C to stop the X server. With my limited knowledge i though i could have forgotten to add a window manager (didn't i read somewhere that this is not included in gnome??) so i did #apt-get install fvwm nothing changed. So here i am writing this mail, hoping somebody here can put me on the right track. Thx for taking the time to read this, Jeroen I would include my XFree86.0.log but i have no idea how to get it of the laptop (skipped mail config in debian installer...) I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. I think that apt-get install gnome should have installed metacity, GNOME's window manager. Good luck. Oliver -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X makes the screen go white (newb - new install)
jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. Once i got the machine to boot from its own HD i though it would be nice to have GUI to learn my way around debian (and linux in general). --/intro fresh install i did: #apt-get install x-window-system #apt-get install gnome immediately after this i used vi to change my /etc/X11/XF86Config-4. The most important change i did was adding this modeline: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 -hsync - vsync together with some other minor changes i found on http://www- jcsu.jesus.cam.ac.uk/~mma29/c1/ #startx works fine (this means it starts up ;-/ ), the only thing i get to see is a black screen which bleeds to a very white blue (starting at the edges). Some vertical and horizontal lines can be seen as well, all at the edge of some very white colours. Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? What other minor changes did you make? The only way to get me out of this white hell is by tapping Ctrl-Alt- F1, followed by Ctrl-C to stop the X server. Ctrl-Alt-Backspace should kill it from within X. With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. (didn't i read somewhere that this is not included in gnome??) so i did #apt-get install fvwm nothing changed. So here i am writing this mail, hoping somebody here can put me on the right track. Thx for taking the time to read this, Jeroen I would include my XFree86.0.log but i have no idea how to get it of the laptop (skipped mail config in debian installer...) Remember that USB disk you mentioned? I bet it works with USB fobs as well. -- Kent West Technology Support /A/bilene /C/hristian /U/niversity -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X makes the screen go white (newb - new install)
Kent West wrote: jeroen wrote: With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. You can double-check this possibility by installing another wm (aptitude install icewm, etc), or make sure you've got xterm installed (aptitude install xterm) and then put icewm or xterm in the file ~/.xinitrc (you'll probably have to create the file), and then run startx. If you put icewm in ~/.initrc, Icewm should start up; if you put xterm, you should get an xterm (with no window controls; you can type exit to shut down X in such a case). -- Kent West Technology Support /A/bilene /C/hristian /U/niversity -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X makes the screen go white (newb - new install)
On 05 Sep 2005, at 22:19, Oliver Lupton wrote: I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. #gdm returns a command not found On 05 Sep 2005, at 22:25, Kent West wrote: jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. It's getting late now, and my primary concern is getting something of a GUI, ifup isn't that hard to type ;). But many thanks for pointing me to the solution. Greatly appreciated! Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? When i comment out the modeline (and un-comment out the HorizSync and VertRefresh) i get the same white screen. What other minor changes did you make? My complete config can now be found @ http://www.yuru.be/debian/XF86Config-4 other changes i made are: /OptionXkbLayoutukto -OptionXkbLayoutgb Probably nothing serious or X killing, just changed it to the working config i found on the cam.ac.uk site /IdentifierConfigured Mouse /OptionEmulate3Buttontrue /OptionZAxisMapping4 5 to -IdentifierConfigured Mouse -OptionButtons5 -OptionZAxisMapping5 4 Same here, just copied it, hoping it would work like a charm. Other changes are: Adding the modeline and commenting out the HorizSync and VertRefresh. The last thing i changed where all resolutions in the Display Subsections of the Screen Section (was 320x240 640x480) Ctrl-Alt-Backspace should kill it from within X. Hey cool, thanks! I was trying to do that with Ctrl-Alt-Delete... With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. You can double-check this possibility by installing another wm (aptitude install icewm, etc), or make sure you've got xterm installed (aptitude install xterm) and then put icewm or xterm in the file ~/.xinitrc (you'll probably have to create the file), and then run startx. If you put icewm in ~/.initrc, Icewm should start up; if you put xterm, you should get an xterm (with no window controls; you can type exit to shut down X in such a case). Tried this, with both suggested wms (and both .xinitrc and .initrc - was this a typo or are they indeed different?), they produce the same white screen. You where right that i had to create both files. I renamed them so there never was both a .xinitrc and and .initrc in my ~/. Remember that USB disk you mentioned? I bet it works with USB fobs as well. Doh! Thanks for that. It's the only floppy drive i have so i have to plug it in and out, it works, that's most important. I do have a problem with copying my XFree86.0.log, It gives a -36 error when i try to copy it over to my mac. I'll look into that tomorrow (when i follow your tips on the interfaces). Now it's time for me to go to bed, i'm on CET and have to work tomorrow. Thank you for your time, Jeroen jeroen wrote: Hello all, --intro I'm trying (finally) to get debian to work on my Vaio PCG-C1VE. Using the latest version of the installer (floppy images) i succeeded in installing 3.1 on the little b*st*rd. Previous versions didn't support USB disks (at least not on a noob level) so thx debian! I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Once i got the machine to boot from its own HD i though it would be nice to have GUI to learn my way around debian (and linux in general). --/intro fresh install i did: #apt-get install x-window-system #apt-get install gnome immediately after this i used vi to change my /etc/X11/XF86Config-4. The most important change i did was adding this modeline: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 - hsync - vsync together with some other minor changes i found on http://www- jcsu.jesus.cam.ac.uk/~mma29/c1/ #startx works fine (this means it starts up ;-/ ), the only thing i get to see is a black screen which bleeds to a very white blue (starting at the edges). Some vertical and horizontal lines can be seen as well, all at the edge of some very white colours. Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg
Re: starting X makes the screen go white (newb - new install)
Sorry if this came in double, the resend i did might have tricked your mail rules (it did trick mine) Jeroen On 05 Sep 2005, at 22:19, Oliver Lupton wrote: I'm a newbie too, but try running 'gdm' (GNOME Display Manager, I think) instead of 'startx' and see how that works. #gdm returns a command not found On 05 Sep 2005, at 22:25, Kent West wrote: jeroen wrote: I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Take a look at /etc/network/interfaces (also man interfaces for examples). Once configured, a simple /etc/init.d/networking restart (or reboot, which will run this script during bootup) should get your network up. It's getting late now, and my primary concern is getting something of a GUI, ifup isn't that hard to type ;). But many thanks for pointing me to the solution. Greatly appreciated! Some pictures i took during this happening can be found here: http://www.yuru.be/debian/startx_1.jpg (going from 1 to 6) These images look like your video settings are not suitable for your hardware; what happens if you remove that ModeLine you added? When i comment out the modeline (and un-comment out the HorizSync and VertRefresh) i get the same white screen. What other minor changes did you make? My complete config can now be found @ http://www.yuru.be/debian/XF86Config-4 other changes i made are: /OptionXkbLayoutukto -OptionXkbLayoutgb Probably nothing serious or X killing, just changed it to the working config i found on the cam.ac.uk site /IdentifierConfigured Mouse /OptionEmulate3Buttontrue /OptionZAxisMapping4 5 to -IdentifierConfigured Mouse -OptionButtons5 -OptionZAxisMapping5 4 Same here, just copied it, hoping it would work like a charm. Other changes are: Adding the modeline and commenting out the HorizSync and VertRefresh. The last thing i changed where all resolutions in the Display Subsections of the Screen Section (was 320x240 640x480) Ctrl-Alt-Backspace should kill it from within X. Hey cool, thanks! I was trying to do that with Ctrl-Alt-Delete... With my limited knowledge i though i could have forgotten to add a window manager I don't think so; this looks like a video sync -type issue. You can double-check this possibility by installing another wm (aptitude install icewm, etc), or make sure you've got xterm installed (aptitude install xterm) and then put icewm or xterm in the file ~/.xinitrc (you'll probably have to create the file), and then run startx. If you put icewm in ~/.initrc, Icewm should start up; if you put xterm, you should get an xterm (with no window controls; you can type exit to shut down X in such a case). Tried this, with both suggested wms (and both .xinitrc and .initrc - was this a typo or are they indeed different?), they produce the same white screen. You where right that i had to create both files. I renamed them so there never was both a .xinitrc and and .initrc in my ~/. Remember that USB disk you mentioned? I bet it works with USB fobs as well. Doh! Thanks for that. It's the only floppy drive i have so i have to plug it in and out, it works, that's most important. I do have a problem with copying my XFree86.0.log, It gives a -36 error when i try to copy it over to my mac. I'll look into that tomorrow (when i follow your tips on the interfaces). Now it's time for me to go to bed, i'm on CET and have to work tomorrow. Thank you for your time, Jeroen jeroen wrote: Hello all, --intro I'm trying (finally) to get debian to work on my Vaio PCG-C1VE. Using the latest version of the installer (floppy images) i succeeded in installing 3.1 on the little b*st*rd. Previous versions didn't support USB disks (at least not on a noob level) so thx debian! I used apt to get me the files i needed during the installation (i did have to do an 'ifup -a' to get the network up - and still have to after every reboot - but that's slightly OT here). Once i got the machine to boot from its own HD i though it would be nice to have GUI to learn my way around debian (and linux in general). --/intro fresh install i did: #apt-get install x-window-system #apt-get install gnome immediately after this i used vi to change my /etc/X11/XF86Config-4. The most important change i did was adding this modeline: ModeLine 1024x480 65.00 1024 1032 1176 1344 480 488 494 563 - hsync - vsync together with some other minor changes i found on http://www- jcsu.jesus.cam.ac.uk/~mma29/c1/ #startx works fine (this means it starts up ;-/ ), the only thing i get to see is a black screen which bleeds to a very white blue (starting at the edges). Some vertical and horizontal lines can be seen as well, all at the edge
Re: Trouble starting X [Was:Re: more info]
On 27 July 2005, Kent West wrote: snip [EE] xf860 penserial: cannot open device /dev/input/miceno such device [EE] configured mouse: cannot open input device [EE] PreInit failed for input device Configured Mouse I have a 5$ optical mouse that is made by MicroInnovations (or maybe there's a space in there). It connects to my ps/2 connector. Try running dpkg-reconfigure xserver-xfree86 and selecting ps2 as your mouse type when you get to that question. This only works, if he hasn't changed XF86Config-4 manually!!! If you have changed this config file (this is absolutly allowed in Debian!), you will find a comment at the beginning of this file, how you can reset this, so you can again use dpkg-reconfigure xserver-xfree86. (BTW: It then asks you the same questions, as it did, when you have had installed Debian) Peter -- peter_sulzer doesn't like spam and this is my domain: t-online.de
Trouble starting X [Was:Re: more info]
Dylan Evans wrote: when I typed startx at the command prompt, it made the same error messages it did initially, snip [EE] xf860 penserial: cannot open device /dev/input/miceno such device [EE] configured mouse: cannot open input device [EE] PreInit failed for input device Configured Mouse I have a 5$ optical mouse that is made by MicroInnovations (or maybe there's a space in there). It connects to my ps/2 connector. Try running dpkg-reconfigure xserver-xfree86 and selecting ps2 as your mouse type when you get to that question. lspci -vv says the following about my network card: :00:10.0 Ethernet Controller: Realtek semiconductor Co., Ltd. RTL -8139/8139C/8139C+ (Rev 10) Are you including this info because your network is not working? You'd probably do best to make a separate thread out of this question. additionally, when booting, the loader program has my kernel listed as 2.41something. I thought debian 3.1 was the latest version, and I'd have 2.6something. I also saw some error messages in the boot up that said things like: failed to load. kernel 2.6 required. did I get gypped with the dvds I bought? I always just use the official Debian CD files/netinst CDs, so I can't really speak to your DVD quality. However, I doubt that you've been gypped. I believe 2.4 is the default kernel in Sarge, but you can easily upgrade to 2.6 if you like. Try: #aptitude search kernel-image-2.6 | grep k7 for the available 2.6 kernels for the Athlon. If nothing appears, your DVDs don't have them, and you may want to configure your box to pull the kernel from the net. Otherwise, if some do appear, pick the one you want and install it with a command similar to: #aptitude install kernel-image-2.6.11-1-k7 If you see a message about initrd, make sure that your /etc/lilo.conf file has a line like initrd=/initrd.img in the stanza for the new 2.6 kernel. (This assumes that Sarge installed lilo rather than grub.) And is there a good tutorial/reference to learn how to access all your drives, like finding out what's on your floppy, or cd, or whatever. And how to transfer files to a windows partition. thanks for your help Probably, but I can't suggest one. You might do well to Google for this info. Or, as Martin as mentioned, he has a new book out for Debian adminstrators that might have all you want (or, then again, it might be too indepth since it's not for general use issues). See http://debiansystem.info/. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem starting x server
Hello! I'm new to Debian and this GNU/linux. I've installed from CD but the machine returns an error saying "I cannot start x server, it is likely that it is not set up correctly etc etc". Then next screen says "warning process set to nice value 0 instead of -10 as requested etc". Next screen "would you like to run the x config program etc" then "I will now try to restart x server again" then "I cannot start the x server". It either goes round in circles or I have to decline and get to the command prompt. The machine is not yet on either its network or the internet, the only way in is via CD (no-floppy). Can anyone tell me how (in simple terms please!) how to get through this and bring up the GUI? I copied the CD from a mirror. I've tried the faq's and other lists. Also I get loads of error messages, all the same, thus: ide2: unexpected interrupt, status=0xd0, count= (ascending number), I think it's because I've got a large SATA drive is this true? How canI lose the messages echoing to screen? Thanks Adrian [EMAIL PROTECTED]
Re: Problem starting x server
Adrian S. Glover wrote: Hello! I'm new to Debian and this GNU/linux. I've installed from CD but the machine returns an error saying I cannot start x server, it is likely that it is not set up correctly etc etc. Setting up X is one of the most common difficulties newbies have, especially if they're using the current Stable branch of Debian, Woody. Woody is ancient, and if this is what you have, you'd probably find life much easier if you could upgrade to Sarge (Testing) or Sid (Unstable), both of which are suitable for workstation use (whereas you'd probably do better to stick with Woody for a server, in which case, do you really need X?). Then next screen says warning process set to nice value 0 instead of -10 as requested etc. You can ignore this error; it's not the one causing you problems. Next screen would you like to run the x config program etc then I will now try to restart x server again then I cannot start the x server. It either goes round in circles or I have to decline and get to the command prompt. The machine is not yet on either its network or the internet Then upgrading to Sarge or Sid is more difficult. , the only way in is via CD (no-floppy). Can anyone tell me how (in simple terms please!) how to get through this and bring up the GUI? I copied the CD from a mirror. I've tried the faq's and other lists. Run lspci and see what video chipset you have; the output will look something like this: [EMAIL PROTECTED]:/home/westk/DOCS/KCARC/NEWSLETTERS/2005 lspci :00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] :00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] :00:09.0 Ethernet controller: Linksys NC100 Network Everywhere Fast Ethernet 10/100 (rev 11) :00:0b.0 VGA compatible controller: S3 Inc. 86c325 [ViRGE] (rev 06) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge :00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:11.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :00:11.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :00:11.4 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1b) :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 30) :01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 RL/VR AGP There are two lines referring to VGA controllers, indicating that this box has two video cards (yours probably (almost certainly) only has one); one is an S3 86c325; the other is an ATI Rage 128. Now that you know what video chipset you have, run dpkg-reconfigure xserver-xfree86, and select the corresponding driver for your chipset when prompted. After this program is finished, try starting X manually with the startx command. If it still fails, look on the screen (Shift-PgUP to scroll up) for any relevant error messages. Also you might look in /var/log/XFree86.0.log. As your other question is on a different topic, it really deserves its own thread. I'd still attempt answering it, however, if I were so qualified. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem starting x server
On Mon, 2004-12-27 at 17:08 +, Adrian S. Glover wrote: Hello! Adrian [EMAIL PROTECTED] Hi Adrian, in case of a misconfigured xserver you can do a couple of things that all come to basically the same thing: modifying your /etc/X11/XF86Config-4 This is your central xserver config file. You can run the configure tool again with a 'dpkg-reconfigure xserver-xfree86' or do it manually with a 'lspci' as root, find your graphics card and note it down. Edit the file with a 'nano /etc/X11/XF86Config-4', find a 'Section Device' and modify the 'Driver' statement to have the driver matching your card, don't forget to save. Start xfree86 again with a' /etc/init.d/gdm start'. Sincerely , Jan. -- John Smith [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
Hello cfk ([EMAIL PROTECTED]) wrote: Thank you very much for the tip. I did do a 'apt-get install x-window-system', and a number of good things happened. I can now do a startx and get twm. I can also right-click and get a tclsh8.4. Thats the good news. Unfortunately, being unfamiliar with apt-get yet, I dont know how to get say kde or gnome up. I am currently trying: apt-get install kde kdevelop kdelibs kdebase after a search of archives and it seems to be working. After that, I wonder what the incantation is to start kde and perhaps more importantly, where I can go to figure out a few steps after that, other then googling. kde should be started by default and be preferred over twm if you run startx. Anyway I suggest you install the KDE login manager kdm, which lets you select which WM/DE you want to log into. There are also other ways, like creating your own ~/.xsession and adding startkde (make sure that allow-user-xsession is in your /etc/X11/Xsession.options), or telling startx which command to run. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 ICQ #17079270 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps-sarge.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
On Sun, 19 Dec 2004 04:00:12 +0100, cfk wrote: after a search of archives and it seems to be working. After that, I wonder what the incantation is to start kde and perhaps more importantly, where I can go to figure out a few steps after that, other then googling. tasksel helps a lot with this. You're probably still missing a display manager from your Red Hat experience. Since you're into KDE, I suggest kdm. Though, being a GNOME geek, I also have to point out that GDM is much better ;-) -- Best Regards, | This signature is currently under construction. Sebastian | Please check back later! | | mailbox in From silently drops any mail 20k -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
On Sat, Dec 18, 2004 at 06:59:01PM -0800, cfk wrote: On Saturday 18 December 2004 18:14, Sam Watkins wrote: Dear Sam: Thank you very much for the tip. I did do a 'apt-get install x-window-system', and a number of good things happened. I can now do a startx and get twm. I can also right-click and get a tclsh8.4. Thats the good news. Unfortunately, being unfamiliar with apt-get yet, I dont know how to get say kde or gnome up. I am currently trying: apt-get install kde kdevelop kdelibs kdebase after a search of archives and it seems to be working. After that, I wonder what the incantation is to start kde and perhaps more importantly, where I can go to figure out a few steps after that, other then googling. Charles the following sequence yields: [EMAIL PROTECTED]:~$ ls /usr/bin | grep kde . kdebugdialog kde-config . startkde wkdemenu.pl It seems to be startkde, so startx `which startkde` should get you there -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
On Sun, Dec 19, 2004 at 12:18:14PM +0100, Sebastian Kapfer wrote: Since you're into KDE, I suggest kdm. Though, being a GNOME geek, I also have to point out that GDM is much better ;-) maybe we need an uber-display manager that lets the user choose what display manager they want to use before entering the login ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
beyond starting x
tasksel helps a lot with this. You're probably still missing a display manager from your Red Hat experience. Since you're into KDE, I suggest kdm. Though, being a GNOME geek, I also have to point out that GDM is much better ;-) -- Best Regards, | This signature is currently under construction. Sebastian | Please check back later! Thank you all that helped me last night. I did an 'apt-get install kde kdevelop kdelibs kdebase' and now the computer boots into an X logon screen for kde. At this point I can run kpackage or apt-get and add other 'stuff' and thats a good thing. I admit that my experience is with RedHat, so I dont know yet how to change back and forth between a text logon, a kde logon or a gnome logon in Debian. So, I cannot get back to the startx prompt at this time to experiment. I would enjoy experimenting with gnome versus kde versus text a bit as I am doing all this on my experimental computer, so I have the time to poke around. Unfortunately, my poking around for the last four years has all been RedHat and not Debian, so my incantations and cheat sheet doesnt help a great deal, only a little bit. Charles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: beyond starting x
cfk wrote: I admit that my experience is with RedHat, so I dont know yet how to change back and forth between a text logon, a kde logon or a gnome logon in Debian. So, I cannot get back to the startx prompt at this time to experiment. You can search the Debian archives; this has been covered many times. The short version: Ctrl-Alt-F[usually 1 - 6] will switch you to a virtual terminal (VT), aka a text console. Alt-F7 will (usually) switch you back to X. Unless you have a glitchy video system, you can switch to a VT (say, Ctrl-Alt-F2 for VT2), and login as a second person, and then start a second X session with something like startx -- :1 (the first X session is on display number 0). Then you can switch to VT3 with Ctrl-Alt-F3, login as a third person, and then start a third X session with startx -- :2. You can switch back and forth between the X sessions with Ctrl-Alt-F7, Ctrl-Alt-F8, and Ctrl-Alt-F9. Add more if you wish. This is great for a family computer; Mom can run Gnome; Dad can run Icewm, Baby Boy can run KDE, and Baby Girl can run Gnome too, just like Mommie, but without trashing Mommie's files and background wallpaper. If you want a different window manager/environment on those other X sessions, just create a one-liner .xinitrc file in each user's home directory with the name of the wm/e you wish to use. Or feed the wm/e name to the startx command as a parameter (I forget the syntax, though, so I just use ~/.xinitrc). If you want to disable KDM temporarily, there are half a dozen ways of doing it; I just put exit 0 as the first executable line in /etc/init.d/kdm. If you want to switch to a different login manager, dpkg-reconfigure xdm (pick a dm that's not currently the default - that is, if you're running KDM, don't reconfigure KDM, but rather xdm or wdm or gdm). Be aware you'll need to have these other dm's installed, like apt-get install xdm kdm wdm gdm. To remove a login manager, just apt-get --purge remove kdm (say, to remove KDM). This ought to help you get your feet wet. Freebie X Tip, just for joining this list: If your mouse gets knocked off the table and cracks and fails to work anymore, you can simulate a mouse with your numeric keypad. Just press Shift-Numlock to turn the simulation on (or off). Then the 5 key is the Click button, / sets 5 to be left-click; * sets 5 to be a middle-click, - sets 5 to be a right-click; the other number keys move the pointer in the corresponding direction; 0 is a click-and-hold; DEL is a release click. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
starting x
Gentlemen: Its my turn to be a newbie to Debian, although I have used Red Hat for a few years. Please bear with me and suggest how I may get my newly installed Sarge to start X. I try the incantation startx from either a user or root command prompt and get command not found. Charles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
On Saturday 18 December 2004 5:44 pm, cfk wrote: Gentlemen: Its my turn to be a newbie to Debian, although I have used Red Hat for a few years. Please bear with me and suggest how I may get my newly installed Sarge to start X. Searching through the archives would have told you you need to install X before you can run it a lot faster than asking the same thing again. -- Paul Johnson [EMAIL PROTECTED] http://ursine.dyndns.org/~baloo/ pgpxzewU9tnR6.pgp Description: PGP signature
Re: starting x
cfk wrote: Gentlemen: Its my turn to be a newbie to Debian, although I have used Red Hat for a few years. Please bear with me and suggest how I may get my newly installed Sarge to start X. I try the incantation startx from either a user or root command prompt and get command not found. Charles Perhaps `apt-get install xserver-xfree86' is needed smime.p7s Description: S/MIME Cryptographic Signature
Re: starting x
On Saturday 18 December 2004 17:42, Robert Vangel wrote: cfk wrote: Gentlemen: Its my turn to be a newbie to Debian, although I have used Red Hat for a few years. Please bear with me and suggest how I may get my newly installed Sarge to start X. I try the incantation startx from either a user or root command prompt and get command not found. Charles Perhaps `apt-get install xserver-xfree86' is needed Dear Robert: Thank you for your kind reply. I was in the midst of reading apt-get's commands and options as I come up to speed on Debian. I did try 'apt-get install xserver-xfree86' and apt-get finishes very quickly saying: Reading Package Lists... Done Building Dependency Tree ... Done xserver-xfree86 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded Then I invoke startx from the root prompt and get -bash: startx: command not found So, I did 'echo $PATH' and found /usr/bin/X11 was in the path, went there and saw there was no 'startx', but there was an 'X', which when run, gives me a modest blank X screen. Unfortunately, no menu or any right click mouse option such as 'open terminal'. I can go 'Alt-Ctrl-F1', F2 or F3 where F1 shows some error messages, F2 gets me back to the big blank X window and F3 gives me a new logon prompt with an inoperable keyboard. At this point I am pressing the reset switch and starting over and hoping for a bit more advice. Charles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
startx is not part of the X server, it is in the package x-base-clients. You should: apt-get install x-window-system-core or probably: apt-get install x-window-system you can look at what each of these meta packages depends on with: apt-cache show x-window-system-core you can see reverse dependencies with apt-cache rdepends xterm you can find out what package contains a certain file with apt-file: apt-get install apt-file apt-file search startx apt-cache rdepends x-base-clients etc. good luck! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting x
Sam Watkins wrote: startx is not part of the X server, it is in the package x-base-clients. You should: apt-get install x-window-system-core or probably: apt-get install x-window-system you can look at what each of these meta packages depends on with: apt-cache show x-window-system-core you can see reverse dependencies with apt-cache rdepends xterm you can find out what package contains a certain file with apt-file: apt-get install apt-file apt-file search startx apt-cache rdepends x-base-clients etc. good luck! x-window-system is the one I was thinking of, sorry! startx is actually part of xbase-clients, which installing x-window-system would end up installing. smime.p7s Description: S/MIME Cryptographic Signature
Re: starting x
On Saturday 18 December 2004 18:14, Sam Watkins wrote: startx is not part of the X server, it is in the package x-base-clients. You should: apt-get install x-window-system-core or probably: apt-get install x-window-system you can look at what each of these meta packages depends on with: apt-cache show x-window-system-core you can see reverse dependencies with apt-cache rdepends xterm you can find out what package contains a certain file with apt-file: apt-get install apt-file apt-file search startx apt-cache rdepends x-base-clients etc. good luck! Dear Sam: Thank you very much for the tip. I did do a 'apt-get install x-window-system', and a number of good things happened. I can now do a startx and get twm. I can also right-click and get a tclsh8.4. Thats the good news. Unfortunately, being unfamiliar with apt-get yet, I dont know how to get say kde or gnome up. I am currently trying: apt-get install kde kdevelop kdelibs kdebase after a search of archives and it seems to be working. After that, I wonder what the incantation is to start kde and perhaps more importantly, where I can go to figure out a few steps after that, other then googling. Charles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Extra commands when starting X
Some sites tell me to do things like Please add the following line to the ~/.xsession or ~/.xinitrc. export [EMAIL PROTECTED] exec uim-xim But in Debian, neither ~/.xsession nor ~/.xinitrc exist by default. And if you create them, you cannot use them for *adding* things to the X start-up process. If you do, X refuses to start. They can only be used to specify the *whole* X start-up process. For instance, calling the window manager should be the last line. This may be a frosty FAQ, but I could not find the answer in spite of much Googling. What is the Debian way to execute some extra commands (preferably on a per-user basis) each time X is started? Regards, Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Wed, Jul 14, 2004 at 12:08:39AM +0100, Steven Satelle wrote: On Tue, 13 Jul 2004 20:28:56 +0300, Micha Feigin wrote: Same behavior (I am using wdm and no xdmcp and the no listen on tcp switch). It seems like /usr/X11R6/bin/X is whats causing the trouble, running tcpdump when X startx shows the name lookup BTW: you know, I think we're barking up the wrong tree, in fact I dont even think we are in the woods at all ;-) It might well be a bug. but a bug in what? Try without any x sessions running run 'X' as root and see how long does it take to start, that way you can see if it is xfree or (I assume your using it) gnome. Running just X also hangs in the same way, so its X that's giving the problems. I am not running gnome btw, I'm running FVWM (gnome is too slow,heavy and not configurable enough). Also running wdm gives the same problem and its not starting .xsession or gnome-session so thats not the problem. Assuming it starts quickly, next you want to type: $ export DISPLAY=localhost:0.0 $ gnome-session (or enter the name of your wm's main app) If what I think the problem is is right this should be slow to launch, so exit it (not X just the wm) and this time on another console run 'netstat -c' This will show all network connections and refresh them every few seconds. then relaunch your wm and see does any new datagrams or streams open up in netstat, esp ones that sit in a state of 'SYN_SENT' You are going to get a few going no further than /tmp/.orbit-root, I'm fairly sure they will be streams, they are what gives gnome its network transparency, even local only connections open up sockets. Thats what I think the problem is, gnome is trying to open up a network socket to somewhere. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Tue, Jul 13, 2004 at 01:49:29AM +0100, Steven Satelle wrote: On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote: BTW I got the following reply after I tried reporting a bug on netbase on this: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. what package are you getting host from, I dont have it on my system. whats /usr/bin/host in your /etc/resolv.conf, mine has search personal.ie nameserver 192.168.1.1 domain luna.local nameserver 192.168.0.1 I think you should have nameserver 127.0.0.1 in there before any remote binds, I dont, but then, I dont have a problem ;-) I think If you have 127.0.0.1 in there as the first nameserver it will check the local one first (/etc/hosts) Doesn't work. apart from that what happens if you run startx without gdm running? Same behavior (I am using wdm and no xdmcp and the no listen on tcp switch). It seems like /usr/X11R6/bin/X is whats causing the trouble, running tcpdump when X startx shows the name lookup BTW: 20:25:55.791908 IP litshi.luna.local.32784 rice.luna.local.domain: 6405+ A? -.luna.local. (30) 20:25:55.792612 IP litshi.luna.local.32785 rice.luna.local.domain: 7688+ PTR? 1.0.168.192.in-addr.arpa. (42) 20:25:55.793239 IP rice.luna.local.domain litshi.luna.local.32784: 6405 NXDomain* 0/1/0 (80) 20:25:55.793411 IP litshi.luna.local.32786 rice.luna.local.domain: 6406+ A? -. (19) 20:25:55.793894 IP rice.luna.local.domain litshi.luna.local.32785: 7688* 1/1/0 PTR[|domain] 20:25:55.794140 IP litshi.luna.local.32787 rice.luna.local.domain: 7689+ PTR? 3.0.168.192.in-addr.arpa. (42) 20:25:55.794252 IP rice.luna.local.domain litshi.luna.local.32786: 6406 NXDomain 0/1/0 (94) 20:25:55.794411 IP litshi.luna.local.32788 rice.luna.local.domain: 6407+ A? -.luna.local. (30) 20:25:55.795182 IP rice.luna.local.domain litshi.luna.local.32787: 7689* 1/1/0 PTR[|domain] 20:25:55.795591 IP rice.luna.local.domain litshi.luna.local.32788: 6407 NXDomain* 0/1/0 (80) 20:25:55.795645 IP litshi.luna.local.32788 rice.luna.local.domain: 6408+ A? -. (19) 20:25:55.796280 IP rice.luna.local.domain litshi.luna.local.32788: 6408 NXDomain 0/1/0 (94) 20:25:55.796419 IP litshi.luna.local.32788 rice.luna.local.domain: 6409+ A? local:root.luna.local. (39) 20:25:55.797114 IP rice.luna.local.domain litshi.luna.local.32788: 6409 NXDomain* 0/1/0 (89) 20:25:55.797158 IP litshi.luna.local.32788 rice.luna.local.domain: 6410+ A? local:root. (28) 20:25:55.797800 IP rice.luna.local.domain litshi.luna.local.32788: 6410 NXDomain 0/1/0 (103) 20:26:00.790557 arp who-has litshi.luna.local tell rice.luna.local 20:26:00.790591 arp reply litshi.luna.local is-at 08:00:46:5b:70:62 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Tue, 13 Jul 2004 20:28:56 +0300, Micha Feigin wrote: Same behavior (I am using wdm and no xdmcp and the no listen on tcp switch). It seems like /usr/X11R6/bin/X is whats causing the trouble, running tcpdump when X startx shows the name lookup BTW: you know, I think we're barking up the wrong tree, in fact I dont even think we are in the woods at all ;-) It might well be a bug. but a bug in what? Try without any x sessions running run 'X' as root and see how long does it take to start, that way you can see if it is xfree or (I assume your using it) gnome. Assuming it starts quickly, next you want to type: $ export DISPLAY=localhost:0.0 $ gnome-session (or enter the name of your wm's main app) If what I think the problem is is right this should be slow to launch, so exit it (not X just the wm) and this time on another console run 'netstat -c' This will show all network connections and refresh them every few seconds. then relaunch your wm and see does any new datagrams or streams open up in netstat, esp ones that sit in a state of 'SYN_SENT' You are going to get a few going no further than /tmp/.orbit-root, I'm fairly sure they will be streams, they are what gives gnome its network transparency, even local only connections open up sockets. Thats what I think the problem is, gnome is trying to open up a network socket to somewhere. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Mon, Jul 12, 2004 at 12:06:41AM +0100, Steven Satelle wrote: Ping uses the hosts file but host seems to ignore it. So if the nameserver is not reachable then ping hostname works but host hostname returns 192.168.0.1 connect: Network is unreachable Nameserver not reachable litshi.luna.local A record not found, try again my /etc/hosts has the following lines: 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi (I know pointing hostname to 127.0.0.1 is not advised, but its a laptop and has several possible IPs). Any ideas? right you are getting me puzzled now :-) I suppose a bit of fishing is in order what's in /etc/host.conf, it should say 'order hosts,bind' order hosts,bind multi on that file tells the sys how to resolve hosts in the network, you want it to check the local hosts file before going to bind also whats in /etc/hostname? It should, at least on my sys, have the litshi hostname of the sys, not the fqdn, just the hostid.If It doesnt use 'hostname litshi' to set it, ignore the fqdn for now, just try with that. If that doesnt work, have you looked at m$ windows recently ;-) If even that doesnt work you could try (dont tell anyone I said this) a reboot, after setting the hostname and entering it into /etc/hosts, the files may just need to be re-read hostname returns litshi now I tried pulling the cable and testing again: ping litshi PING litshi.luna.local (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.112 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.082 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.082 ms host litshi Nameserver not responding litshi.luna.local A record not found, try again (after reconnecting cable) host litshi litshi.luna.local A 192.168.0.3 /etc/hosts file: cat /etc/hosts 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi Tried everything as root and checked read permissions for all the files ll /etc/ | grep -v .r..r..r total 1620 -rw---1 root root 144 2002-01-18 10:13 at.deny -rw---1 root root 549 2004-04-27 04:07 group- -rw-r-1 root shadow467 2004-05-08 16:54 gshadow -rw---1 root root 457 2004-04-27 04:07 gshadow- -rw---1 root root 998 2004-05-08 16:55 passwd- -rw-r-1 root shadow745 2004-05-08 16:55 shadow -rw---1 root root 685 2004-04-01 15:52 shadow- -r--r-1 root root 302 2004-04-01 06:14 sudoers Anything else that could cause the problem? BTW I got the following reply after I tried reporting a bug on netbase on this: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote: BTW I got the following reply after I tried reporting a bug on netbase on this: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. what package are you getting host from, I dont have it on my system. whats in your /etc/resolv.conf, mine has search personal.ie nameserver 192.168.1.1 I think you should have nameserver 127.0.0.1 in there before any remote binds, I dont, but then, I dont have a problem ;-) I think If you have 127.0.0.1 in there as the first nameserver it will check the local one first (/etc/hosts) apart from that what happens if you run startx without gdm running? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
Incoming from Steven Satelle: On Mon, 12 Jul 2004 17:58:40 +0300, Micha Feigin wrote: [...] this is how it's supposed to work. host(1) is an interface to the resolver library, which does not use /etc/hosts by design. The problem is that it seems that a few other things seem to be ignoring the /etc/hosts file also. what package are you getting host from, I dont have it on my system. whats in your /etc/resolv.conf, mine has search personal.ie nameserver 192.168.1.1 If you want to augment that, it may be dependent on the package/transport you use to set up your network. I use pppd and I see there's a /etc/ppp/resolv/provider that lists nameserver xxx.xxx.xxx.xxx records to be used to create resolv.conf -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
starting X hangs on network timeout
I'm not sure yet on what package to report this bug, but was wondering if anyone else experiences it too. When starting X with a configured network and no cable, it hangs for about 30 seconds until it starts (which is consistent with network timeouts). If I disable the network or not configure the ethernet card it starts immediately. This started now with the latest X upgrade (it seems like more and more things are bypassing the /etc/hosts file, don't know if its this though). And this is after finally fixing exim4 not to hang with no network cable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout
--- Micha Feigin [EMAIL PROTECTED] wrote: I'm not sure yet on what package to report this bug, but was wondering if anyone else experiences it too. Have a look at the bugpage for 'xserver-xfree86'. If it isn't listed there, then maybe consider filing one. -- Thomas Adam = The Linux Weekend Mechanic -- http://linuxgazette.net TAG Editor -- http://linuxgazette.net shrug We'll just save up your sins, Thomas, and punish you for all of them at once when you get better. The experience will probably kill you. :) -- Benjamin A. Okopnik (Linux Gazette Technical Editor) ___ALL-NEW Yahoo! Messenger - so many all-new ways to express yourself http://uk.messenger.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout
On Sun, 11 Jul 2004 20:18:19 +0100, Thomas Adam wrote: --- Micha Feigin [EMAIL PROTECTED] wrote: I'm not sure yet on what package to report this bug, but was wondering if anyone else experiences it too. Have a look at the bugpage for 'xserver-xfree86'. If it isn't listed there, then maybe consider filing one. no, its caused by the machine trying to resolve its name over eth0 AFAIR. If the network is up. If you've configured the network, you've set a hostname, so it is trying to resolvethat. add the hostname to /etc/hosts and you shouldnt have any further problems. at least AFAIR -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
On Sun, Jul 11, 2004 at 08:33:15PM +0100, Steven Satelle wrote: On Sun, 11 Jul 2004 20:18:19 +0100, Thomas Adam wrote: --- Micha Feigin [EMAIL PROTECTED] wrote: I'm not sure yet on what package to report this bug, but was wondering if anyone else experiences it too. Have a look at the bugpage for 'xserver-xfree86'. If it isn't listed there, then maybe consider filing one. no, its caused by the machine trying to resolve its name over eth0 AFAIR. If the network is up. If you've configured the network, you've set a hostname, so it is trying to resolvethat. add the hostname to /etc/hosts and you shouldnt have any further problems. at least AFAIR Ping uses the hosts file but host seems to ignore it. So if the nameserver is not reachable then ping hostname works but host hostname returns 192.168.0.1 connect: Network is unreachable Nameserver not reachable litshi.luna.local A record not found, try again my /etc/hosts has the following lines: 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi (I know pointing hostname to 127.0.0.1 is not advised, but its a laptop and has several possible IPs). Any ideas? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] +++ This Mail Was Scanned By Mail-seCure System at the Tel-Aviv University CC. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout
On Sun, 11 Jul 2004 22:53:09 +0200, Otto Wyss wrote: On Sun, 11 Jul 2004 20:18:19 +0100, Thomas Adam wrote: no, its caused by the machine trying to resolve its name over eth0 AFAIR. If the network is up. If you've configured the network, you've set a hostname, so it is trying to resolvethat. add the hostname to /etc/hosts and you shouldnt have any further problems. at least AFAIR What do you enter into /etc/hosts if you get the ip via DHCP? O. Wyss I dont know, try typing 'uname -n' that prints off the hostname your using. if by any chance your using a static dhcp address (thats what I tend to use, but I configure my own dhcp server) you will always be assigned the same address and therefore always get the same name and you could enter that into /etc/hosts. another easy option would be to set a hostname on the pc. just enter a name into /etc/hostname. That will set a perminent hostname on the pc, then enter that into /etc/hosts -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting X hangs on network timeout (hosts file ignored)
Ping uses the hosts file but host seems to ignore it. So if the nameserver is not reachable then ping hostname works but host hostname returns 192.168.0.1 connect: Network is unreachable Nameserver not reachable litshi.luna.local A record not found, try again my /etc/hosts has the following lines: 127.0.0.1 localhost 127.0.0.1 litshi.luna.local litshi (I know pointing hostname to 127.0.0.1 is not advised, but its a laptop and has several possible IPs). Any ideas? right you are getting me puzzled now :-) I suppose a bit of fishing is in order what's in /etc/host.conf, it should say 'order hosts,bind' that file tells the sys how to resolve hosts in the network, you want it to check the local hosts file before going to bind also whats in /etc/hostname? It should, at least on my sys, have the hostname of the sys, not the fqdn, just the hostid.If It doesnt use 'hostname litshi' to set it, ignore the fqdn for now, just try with that. If that doesnt work, have you looked at m$ windows recently ;-) If even that doesnt work you could try (dont tell anyone I said this) a reboot, after setting the hostname and entering it into /etc/hosts, the files may just need to be re-read -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
problem starting x
hello all firstly, i am not a member of the group. so, may i request you to send your replies to my e-mail address also? i have a hp pc running win xp. it has an hp72 monitor. from control panel - device managers following information is available. monitor - hp d 8904 display adapter - rage 128 pro gl i have made the system a double boot one by installing debian 3.0. the installation went on without any problem. however, now x refuses to start. i have attached the error file as well as the config file. could someone help me in setting it right? thanks in advance, sandip ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the ### BEGIN DEBCONF SECTION line above, and/or after the # ### END DEBCONF SECTION line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.gz. Section Files FontPathunix/:7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/100dpi FontPath/usr/lib/X11/fonts/75dpi EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadpex5 Loadrecord Loadspeedo Loadtype1 Loadvbe Loadxie EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol PS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection Section Device Identifier Generic Video Card Driver i810 VideoRam8192 Option UseFBDev true EndSection Section Monitor Identifier Generic Monitor HorizSync 30-54 VertRefresh 50-85 Option DPMS EndSection Section Screen Identifier Default Screen Device Generic Video Card Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 1 Modes 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse InputDevice Generic Mouse EndSection Section DRI Mode0666 EndSection ### END DEBCONF SECTION This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted
Re: problem starting x
Hello Sandip P Deshmukh ([EMAIL PROTECTED]) wrote: firstly, i am not a member of the group. so, may i request you to send your replies to my e-mail address also? [XFree does not start with ATI rage 128 pr GL] (II) I810: Driver for Intel i810 chipset: i810, i810-dc100, i810e, i815 (II) Primary Device is: PCI 01:00:0 (EE) No devices detected. You try to use the wrong driver. I think you need to change it to ATI, you can check on xfree86.org under Support and Documentation. Run dpkg-reconfigure xserver-xfree86 and change the driver. Also try to set Use Kernel Framebuffer to no if still won't work with the correct driver. best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem starting x
Sandip P Deshmukh wrote: What you told us you have . . . display adapter - rage 128 pro gl What you've told X you have . . . Section Device Identifier Generic Video Card Driver i810 VideoRam 8192 Option UseFBDev true EndSection What does lspci say you have? You might try running dpkg-reconfigure xserver-xfree86 and tell X to use ati or r128 (I'm not sure which you'll want). -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems starting x
Which XF86config file? When dpkg-reconfigure xserver-xfree86 is run, it writes to /etc/X11/XF86Config-4 You'll also notice that in /etc/X11/XF86Config there is only one entry, regarding naming the input device, but in /etc/X11/XF86Config-4 there exists all the conf info that was written by dpkg-reconfigure. i dont appear to have /etc/X11/XF86Config, only a /etc/X11/XF86Config-4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
another problem starting X with sarge-install
I did an install using the sarge install cd last night. Initially I was working on a very small installation because of my plans on setting up LVM. I installed the minimum software necessary. installed lvm10 using 'apt-get install lvm10' set up lvm disks. This went fine. Then I ran TaskSel and selected only the X-Window-Server. An interesting note to make here is that the installation and configuration was extremely fast and simple. However, there was one oddity in the X-Window-Server set-up that I didn't expect. Initially there was an autodetect made of my hardware, including my video card, all of which went fine. It completely recognized my video card and the memory available on my Matrox G400. At what I expect was the completion of the process, it started over again at the beginning asking me about my Geniric Video Card and how much memory it had. I assume this is an installation bug of the sarge-install process. Installed and configured all of those packages and tested X. X worked for both root and regular users. I was able to login using xdm and get to a twm (default) desktop as root and non-root users. I then ran dselect, which selected a number of files by default. I selected no other packages for installation except the package for msft fonts and continued with the install. After this completed, I rebooted (new kernel) and was able to start up xdm (did not start automatically). I could login using XDM to the WindowMaker desktop as root. As a non-root user, my login failed and I was sent back to the XDM login screen. Something was introduced of the MANY packages that has severely broken the X-Windows installation in a way that are a little difficult to debug because there are so many and I'm unable to find any specific errors that really have meaning. In every case there was an error about not being able to find mga_hal driver, but since it worked initially with this error I don't think it really matters and the 'EE' statement in XFree86.0.log is superficial. The only other 'EE' statement found was about a generic mouse configuration. Again, removing that configuration option in XF86Config-4 did nothing to fix the problem. At this point I will retry installation of Debian using only -stable packages to see if this can be set up correctly with those packages. I used this exact hardware for 4 years with Debian on it and only recently removed the installation. But now I'm unable to get back. ugh! I'm not sure where to go next. But I've been running without a workstation for almost two weeks and kind of need something. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: another problem starting X with sarge-install
Tom Allison wrote: I did an install using the sarge install cd last night. I installed the minimum software necessary. This went fine. Then I ran TaskSel and selected only the X-Window-Server. Initially there was an autodetect made of my hardware, including my video card, all of which went fine. It completely recognized my video card and the memory available on my Matrox G400. At what I expect was the completion of the process, it started over again at the beginning asking me about my Geniric Video Card and how much memory it had. Do you perhaps have two video cards in the system? Or is the G400 dual-headed? I assume this is an installation bug of the sarge-install process. Installed and configured all of those packages and tested X. X worked for both root and regular users. I was able to login using xdm and get to a twm (default) desktop as root and non-root users. I then ran dselect, which selected a number of files by default. I selected no other packages for installation except the package for msft fonts and continued with the install. After this completed, I rebooted (new kernel) and was able to start up xdm (did not start automatically). Odd that it did not start automatically. I could login using XDM to the WindowMaker desktop as root. As a non-root user, my login failed and I was sent back to the XDM login screen. Instead of using XDM, can you start X as a normal user with just the startx command? My first suspicion would be /etc/X11/Xwrapper.config having the line allowed_users=root instead of allowed_users=console. If so, you can change it manually or run dpkg-reconfigure xserver-common and properly answer the question about who can run X. At this point I will retry installation of Debian using only -stable packages to see if this can be set up correctly with those packages. Yikes! No need to reinstall. This is just an X issue, not an OS issue. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: another problem starting X with sarge-install
Tom Allison wrote: Do you perhaps have two video cards in the system? Or is the G400 dual-headed? No... Just one G400, single head. After this completed, I rebooted (new kernel) and was able to start up xdm (did not start automatically). Odd that it did not start automatically. Yes... it is. I could login using XDM to the WindowMaker desktop as root. As a non-root user, my login failed and I was sent back to the XDM login screen. Instead of using XDM, can you start X as a normal user with just the startx command? No I cannot run startx as normal user. My first suspicion would be /etc/X11/Xwrapper.config having the line allowed_users=root instead of allowed_users=console. If so, you can change it manually or run dpkg-reconfigure xserver-common and properly answer the question about who can run X. I was never asked, under Medium dialog, who could run this. I will check it when I get in front of my computer. If this does solve the matter, then I will consider filing a bugreport against the installation. Thanks for the suggestion. At this point I will retry installation of Debian using only -stable packages to see if this can be set up correctly with those packages. Yikes! No need to reinstall. This is just an X issue, not an OS issue. Normally true. But when I run into goofy stuff that I can't seem to identify after the experience overall and time on this one... It's faster to reinstall sometimes. This is a very new setup. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problems starting x
On Sun, Nov 16, 2003 at 09:53:42PM +, navaja wrote: i noticed that dpkg-reconfigure didnt seem to update the XF86config file, even though i ran it several times, thats why this error kept showing up. any ideas why it wasnt overwritten by the dpkg-reconfigure program? Which package were you attempting to reconfigure? It might be that dexconf is invoked for xserver-xfree86 and you were trying to reconfigure x-window-system, for example. -- Jon Dowland http://jon.dowland.name/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
virtual terminals become unusable when starting x on sid
hi, i boot up, and get command prompt login. can use all vitual termninals. then i start x, with startx (with login manager i get the same problem). x starts, then i try to go back to a virtual terminal, and all i see is messed up lines going down my screen. thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: virtual terminals become unusable when starting x on sid
On Mon, Nov 17, 2003 at 12:38:16PM +, navaja wrote: hi, i boot up, and get command prompt login. can use all vitual termninals. then i start x, with startx (with login manager i get the same problem). x starts, then i try to go back to a virtual terminal, and all i see is messed up lines going down my screen. video driver? kernel module(s) where applicable? framebuffer for vts? -- Jon Dowland http://jon.dowland.name/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: virtual terminals become unusable when starting x on sid
navaja wrote: hi, i boot up, and get command prompt login. can use all vitual termninals. then i start x, with startx (with login manager i get the same problem). x starts, then i try to go back to a virtual terminal, and all i see is messed up lines going down my screen. thanks And what happens if you then go back to X (alt-ctrl-F7) and back again to the virtual terminal? Hugo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: virtual terminals become unusable when starting x on sid
on Mon, Nov 17, 2003 at 12:38:16PM +, navaja ([EMAIL PROTECTED]) wrote: hi, i boot up, and get command prompt login. can use all vitual termninals. then i start x, with startx (with login manager i get the same problem). x starts, then i try to go back to a virtual terminal, and all i see is messed up lines going down my screen. You need to provide more information. I'd very strongly recommend you read the following excellent essay by Simon Tatham, How to Report Bugs Effectively: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html The essay How To Ask Questions The Smart Way by Eric S. Raymond and Rick Moen essay is is also good: http://www.catb.org/~esr/faqs/smart-questions.html Please note that you are the person in the best position to know what you're trying to do, what you've done, how the system's responded, and generally how it's configured. It's very helpful if you can post: - *Exact* commands or steps tried. - *Exact* error output or log messages. Often, entering the error messages into a good search engine such as AlltheWeb (http://www.alltheweb.com/) or Google (http://www.google.com/) will help set you on the road to resolving your problems. While others can offer suggestions, guidance, and experience, we cannot see into either your mind or your machine's state. This is very much a case of you have to help us help you. Good luck. Peace. -- Karsten M. Self [EMAIL PROTECTED]http://kmself.home.netcom.com/ What Part of Gestalt don't you understand? The truth behind the H-1B IT indentured servant scam: http://heather.cs.ucdavis.edu/itaa.real.html pgp0.pgp Description: PGP signature
