Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
01-23-2010, 01:39 PM
|
#16
|
Member
Registered: Nov 2009
Location: Chicago
Distribution: Arch and OpenBSD
Posts: 104
Original Poster
Rep:
|
Well I got it installed and every thing was working and I got into gnome. The next time I booted up, it showed the same screen with 2 lines
Last edited by itsbrad212; 01-23-2010 at 01:41 PM.
|
|
|
01-23-2010, 02:46 PM
|
#17
|
Member
Registered: Nov 2009
Location: Chicago
Distribution: Arch and OpenBSD
Posts: 104
Original Poster
Rep:
|
Quote:
Originally Posted by leopard
Question: Have you started HAL in rc.conf?
Question: Is only ONE exec DE/WM in xinitrc?
Post some info!!
Of key importance:
Xorg.0.log (after failed session) [please just 10 or so lines]
Xorg.conf
dmesg|tail (after failed session)
lspci
modprobe -l|grep vga
That can help in diagnosis of the problem!
|
Yes I have started hal
Yes there is only one in xinitrc
lspci:
Code:
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem (rev 03)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
02:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01)
I think it might be a video ir graphics problem
Last edited by itsbrad212; 01-23-2010 at 07:14 PM.
|
|
|
01-23-2010, 07:25 PM
|
#18
|
Member
Registered: Nov 2009
Location: Chicago
Distribution: Arch and OpenBSD
Posts: 104
Original Poster
Rep:
|
I also posted this on the Arch user forum, but I'm hoping I can get a response here.
|
|
|
01-23-2010, 08:37 PM
|
#19
|
Member
Registered: Jan 2010
Distribution: Arch, Gentoo, FreeBSD
Posts: 64
Rep:
|
can you post reponse to "grep -F DAEMONS /etc/rc.conf"? Also, I saw your .xinitrc on the Arch forums, once you have verified that "dbus hal" are in the daemons array, try using "exec ck-launch-session gnome-session" instead.
|
|
|
01-23-2010, 08:44 PM
|
#20
|
Member
Registered: Nov 2009
Location: Chicago
Distribution: Arch and OpenBSD
Posts: 104
Original Poster
Rep:
|
Quote:
Originally Posted by slightlystoopid
can you post reponse to "grep -F DAEMONS /etc/rc.conf"? Also, I saw your .xinitrc on the Arch forums, once you have verified that "dbus hal" are in the daemons array, try using "exec ck-launch-session gnome-session" instead.
|
DAEMONS=(syslog-ng network netfs crond hal)
I read somewhere that you don't need to add dbus because it is started with hal. I have no idea if that is correct, that's just what I read. Should I add it and try again?
|
|
|
01-23-2010, 08:59 PM
|
#21
|
Member
Registered: Jan 2010
Distribution: Arch, Gentoo, FreeBSD
Posts: 64
Rep:
|
well, it's what I did based on recommendations in the HAL wiki simply because of failed dbus unloads, but you're right, the DBUS wiki doesn't mention it. I'm only suggesting this because of the consolekit errors I saw, which is used by dbus, you might only have to modify the .xinitrc accordingly.
|
|
|
01-23-2010, 09:05 PM
|
#22
|
Member
Registered: Nov 2009
Location: Chicago
Distribution: Arch and OpenBSD
Posts: 104
Original Poster
Rep:
|
Quote:
Originally Posted by slightlystoopid
well, it's what I did based on recommendations in the HAL wiki simply because of failed dbus unloads, but you're right, the DBUS wiki doesn't mention it. I'm only suggesting this because of the consolekit errors I saw, which is used by dbus, you might only have to modify the .xinitrc accordingly.
|
If I read that correctly, I need to modify .xinitrc? What would I need to add? Or could I just add dbus to the list of daemons?
EDIT: here is my everything.log http://www.sendspace.com/file/2w3mn1
Last edited by itsbrad212; 01-23-2010 at 09:08 PM.
|
|
|
01-23-2010, 09:26 PM
|
#23
|
Member
Registered: Jan 2010
Distribution: Arch, Gentoo, FreeBSD
Posts: 64
Rep:
|
does http://pastebin.com/ have a file size limit? it's a nice tool, considering I don't want to download your everything.log.
and you'd just change your line with "gnome-session" or "exec gnome-session" on it to "exec ck-launch-session gnome-session".
|
|
|
01-23-2010, 09:34 PM
|
#24
|
Member
Registered: Nov 2009
Location: Chicago
Distribution: Arch and OpenBSD
Posts: 104
Original Poster
Rep:
|
Quote:
Originally Posted by slightlystoopid
does http://pastebin.com/ have a file size limit? it's a nice tool, considering I don't want to download your everything.log.
and you'd just change your line with "gnome-session" or "exec gnome-session" on it to "exec ck-launch-session gnome-session".
|
I tried pastebin before uploading it but the file was to big
I also have tried using "exec ck-launch-session gnome-session" before and it didn't work. I'll go try again though.
|
|
|
01-23-2010, 09:52 PM
|
#25
|
Member
Registered: Nov 2009
Location: Chicago
Distribution: Arch and OpenBSD
Posts: 104
Original Poster
Rep:
|
No luck I ran it as both root and regular user and it didn't work
|
|
|
01-23-2010, 10:51 PM
|
#26
|
Senior Member
Registered: Mar 2009
Location: USA
Distribution: Arch
Posts: 1,022
Rep:
|
Post some info!!
Question: Have you installed your Video Card with pacman -S 'xf86-video-yourcard' ?
Of key importance:
Xorg.0.log (after failed session) [please just 10 or so lines]
Xorg.conf
dmesg|tail (after failed session)
modprobe -l|grep vga
That can help in diagnosis of the problem!
Try putting these in the rc.conf:
dbus_enable="YES"
polkitd_enable="YES"
hald_enable="YES
|
|
|
01-24-2010, 01:15 AM
|
#27
|
Member
Registered: Jan 2010
Distribution: Arch, Gentoo, FreeBSD
Posts: 64
Rep:
|
Quote:
Try putting these in the rc.conf:
dbus_enable="YES"
polkitd_enable="YES"
hald_enable="YES
|
Arch doesn't use that style rc.conf.
But yes, please, post those things that the previous posters mentioned.
|
|
|
01-24-2010, 04:31 PM
|
#28
|
Member
Registered: Nov 2009
Location: Chicago
Distribution: Arch and OpenBSD
Posts: 104
Original Poster
Rep:
|
Quote:
Originally Posted by leopard
Post some info!!
Question: Have you installed your Video Card with pacman -S 'xf86-video-yourcard' ?
Of key importance:
Xorg.0.log (after failed session) [please just 10 or so lines]
Xorg.conf
dmesg|tail (after failed session)
modprobe -l|grep vga
That can help in diagnosis of the problem!
Try putting these in the rc.conf:
dbus_enable="YES"
polkitd_enable="YES"
hald_enable="YES
|
My video card is integrated into my motherboard. I don't know what type it is. But it worked the first time so I don't think it is because I don't have it installed.
Here is my video card though. I might need to add it to Xorg.conf:
Code:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Ok here it is:
Xorg.0.log (tell me if you need more)
Code:
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
Xorg.conf:
Code:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "dbe"
Load "glx"
Load "extmod"
Load "dri"
Load "dri2"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card0"
Driver "vesa"
VendorName "Intel Corporation"
BoardName "Mobile 4 Series Chipset Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
dmesg|tail
Code:
ACPI Video Device [OVGA] (multi-head:yes rom:no post:no)
[drm] Initialized:915 1.6.0 20080730 for 000:00:02.0 on minor 0
HDA Intel 0000:00:16.0: PCI Int A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:16.0: Setting latency timer to 64
modprobe -l | grep vga
Code:
kernel/drivers/video/vgastate.ko
kernel/drivers/video/svgalib.ko
kernel/drivers/usb/misc/sisusbvga/sisusbvga.ko
I hope that helps.
Here is an image of the screen I get. It is weird because it works perfectly the first time, but when I reboot, it does this:
http://itsbrad212.emenace.com/upload/img_3486.jpg
Notice the two white lines at the top.
Last edited by itsbrad212; 01-24-2010 at 04:39 PM.
|
|
|
01-24-2010, 06:00 PM
|
#29
|
Member
Registered: Nov 2009
Location: Chicago
Distribution: Arch and OpenBSD
Posts: 104
Original Poster
Rep:
|
I solved the problem by installing xf86-video-intel and change vesa to intel in xorg.conf
|
|
|
01-25-2010, 08:03 AM
|
#30
|
Senior Member
Registered: Mar 2009
Location: USA
Distribution: Arch
Posts: 1,022
Rep:
|
First install your video card like so:
Quote:
pacman -S xf86-video-intel
|
Also, you can use 'hwdetect' to aid your the OS in finding your hardware:
Then, try putting these lines into your Xorg.conf...
Quote:
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30.0 - 130.0
VertRefresh 50.0 - 100.0
EndSection
|
Quote:
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768" "800x600" "640x480" # Your screen resolution here.
|
Try those, and post back if the error remains.
Last edited by lupusarcanus; 01-25-2010 at 08:04 AM.
|
|
|
All times are GMT -5. The time now is 02:51 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|