zibi1981 Posted May 31, 2007 Report Share Posted May 31, 2007 I searched around the web and this board of course, but couldn't find solution to my new problem :sad: And here it is... Yesterday I replaced my old motherboard - ASUS A7V600-X - with "new" one, bought on an Internet auction - ASUS A7V880. These two don't seem to vary a lot, they both have the same southbridge (VIA VT8237) i.e., but my new mobo has Dual RAM access and better northbridge. Nonetheless I only replaced motherboard, all the other components remain the same. Firstly I installed Windows XP on a two SATA HDDs based RAID 0 without any complications. Then I installed Mandriva Spring on a ATA-133 Maxtor HDD. The installation process ended without any problems, but when it came to first boot, it went only as far as GRUB menu. When I chose first option (normal boot), the progress bar didn't even move... Then I remembered that there was some issues with ACPI described around the web, so on the next couple of restarts I have tried to add to kernel options almost all combinations off noapic nolapic acpi=off I also tried to alternatingly turn off and on all the ACPI/APIC options i BIOS - the only effect was, that progress bar did finally move forward, but when it came to the stage of displaying KDE login menu, the screen turned black but remained on. And till now I couldn't manage to change that I also tried to first start in failsafe mode, and then after login in type in console startx, but when I did that as a normal user I got xauth: creating new authority file /home/zibi1981.2153xauth: creating new authority file /home/.Xauthority xauth: creating new authority file /home/.Xauthority Authentification failed - cannot start X server. Perhaps you do not have console ownership? giving up xinit: Network is unreachable (errno101): unable to connect to X server xinit: No such process (errno3): Server error Then I logged in as root and typed startx again, but the screen turned black, as I described above. Could anyone help me with this? :unsure: Quote Link to comment Share on other sites More sharing options...
scarecrow Posted May 31, 2007 Report Share Posted May 31, 2007 (edited) It could be many things... for starters, could you post your /etc/pam.d/login contents? Edited May 31, 2007 by scarecrow Quote Link to comment Share on other sites More sharing options...
zibi1981 Posted June 1, 2007 Author Report Share Posted June 1, 2007 Thx for your reply. And here are the logs you asked #%PAM-1.0 auth required pam_securetty.so auth required pam_nologin.so auth include system-auth account include system-auth password include system-auth session optional pam_console.so session include system-auth Quote Link to comment Share on other sites More sharing options...
AussieJohn Posted June 2, 2007 Report Share Posted June 2, 2007 (edited) Since your new board is similar to your earlier one (I also have, and am using the same model as your earlier one) try removing the noapic nolapic acpi=off entirely so the only item you have in the bootup is splash =silent and nothing else. Cheers. John. Edited June 2, 2007 by AussieJohn Quote Link to comment Share on other sites More sharing options...
zibi1981 Posted June 2, 2007 Author Report Share Posted June 2, 2007 (edited) Thanks for your suggestion John, but boot parameters of my Mandriva system are as follows BOOT_IMAGE=linux root=LABEL= System resume=/dev/hda2 splash=silent vga=791 so splash=silent is already included. When I'm trying to boot using these parameters without any modifications, nothing happens. When I add acpi=off, the system loads until KDE login menu, where screen turns black and nothing happens. Edited June 2, 2007 by zibi1981 Quote Link to comment Share on other sites More sharing options...
AussieJohn Posted June 2, 2007 Report Share Posted June 2, 2007 You could also try removing ......resume=/dev/hda2........as well. Try adding pci=nomsi. In the bios do the following....make sure INTERRUPT MODE is set to APIC, and Plug 'n' Play mode is set to NO. It is worth a try. Cheers. John Quote Link to comment Share on other sites More sharing options...
zibi1981 Posted June 2, 2007 Author Report Share Posted June 2, 2007 Didn't know how to make sure INTERRUPT MODE is set to APIC but the other things weren't helpful :sad: Quote Link to comment Share on other sites More sharing options...
AussieJohn Posted June 3, 2007 Report Share Posted June 3, 2007 (edited) I presume you know how to enter the bios but if not then click repeatedly on the delete key as the machine starts up. Use the arrow keys to move about. Select...... Boot.........then go down to........ Plug & Play O/S....... and set it to...... NO. Then move down to......Interrupt Mode.....and set it to...... APIC. It is likely on PIC by default. Then click F10 key and Enter or OK. Cheers. John. Edited June 3, 2007 by AussieJohn Quote Link to comment Share on other sites More sharing options...
zibi1981 Posted June 3, 2007 Author Report Share Posted June 3, 2007 In my BIOS setup it all looks quite different, than in yours John. I didn't find anything such as Interrupt mode anywhere, and the other option is located in Advanced -> PCIPnP -> Plug And Play O/S, and I've already set it to [No]. Quote Link to comment Share on other sites More sharing options...
zibi1981 Posted June 11, 2007 Author Report Share Posted June 11, 2007 So no one has an idea what am I doing wrong? I'd really want to have my Mandriva back, but since I've replaced my old mobo I could only successfully install Windows Xp :sad: :sad: :sad: Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted June 12, 2007 Report Share Posted June 12, 2007 I would say it's a problem with your X server, since it goes black after it's booted. From the console, login as root, and then: service dm stop service xfs stop then run mcc from the command line and reconfigure your display for vesa, and see if it gets any better. Run startx after this, and if you get it working, chances are it was some problem with your config. Quote Link to comment Share on other sites More sharing options...
zibi1981 Posted June 16, 2007 Author Report Share Posted June 16, 2007 It seems to me You may have right ianw1974, it could be something with my X server. It's totally incomprehensible to me, as I never had this kind of problem with my old motherboard, an with my "new" one I already reinstalled Mandriva three times but without avail :sad: I did as You advise me, and was able to start X server as a root. Mandriva seemed to be working properly for me. Then I logged out, and typed startx as a normal user, and I got xauth: creating new authority file /home/zibi1981/.serverauth.2619Authentication failed - cannot start X server. Perhaps you do not have console ownership?xinit: Server error. I checked, and there wasn't any file of a name serverauth.2619 created. What next would You suggest? Quote Link to comment Share on other sites More sharing options...
ffi Posted June 16, 2007 Report Share Posted June 16, 2007 I think you should look for a similar file in /root and delete it (and maybe .Xauthority too). Quote Link to comment Share on other sites More sharing options...
zibi1981 Posted June 23, 2007 Author Report Share Posted June 23, 2007 (edited) Uff, I finally managed to install Mandriva making use of Ian's suggestions. Now I got another problems: 1. after I updated the system, it doesn't shut down or restart anymore. The screen just turns black and nothing happens until I'll eventually press "restart" button... Below is GRUB's menu.lst file [zibi1981@localhost ~]$ cat /boot/grub/menu.lst timeout 15 color black/cyan yellow/cyan gfxmenu (hd0,0)/boot/gfxmenu default 4 title linux kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=/dev/hda1 noapic nolapic resume=/dev/hda2 splash=silent vga=791 initrd (hd0,0)/boot/initrd.img title linux-nonfb kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=/dev/hda1 noapic nolapic resume=/dev/hda2 initrd (hd0,0)/boot/initrd.img title failsafe kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=/dev/hda1 noapic failsafe nolapic initrd (hd0,0)/boot/initrd.img title 2.6.17-13 kernel (hd0,0)/boot/vmlinuz-2.6.17-13mdv BOOT_IMAGE=2.6.17-13 root=/dev/hda1 noapic nolapic resume=/dev/hda2 splash=silent vga=791 initrd (hd0,0)/boot/initrd-2.6.17-13mdv.img title 2.6.17-14 kernel (hd0,0)/boot/vmlinuz-2.6.17-14mdv BOOT_IMAGE=2.6.17-14 root=/dev/hda1 noapic nolapic resume=/dev/hda2 splash=silent vga=791 initrd (hd0,0)/boot/initrd-2.6.17-14mdv.img Maybe I should add acpi=off? :unsure: I'm not sure... 2. I'm forced to use Vesa display driver until ATI releases theirs with X.org 7.2 support. And because of it my monitor's refresh rate is set to 60 Hz, although KDE tells me, that it is 86 Hz... Again... My eyes are going to explode soon... Well, I tried the trick with gtf, but as far with no avail. And here is my xorg.conf file # File generated by XFdrake (rev 142098) # ********************************************************************** # Refer to the xorg.conf man page for details about the format of # this file. # ********************************************************************** Section "Files" # font server independent of the X server to render fonts. FontPath "unix/:-1" # minimal fonts to allow X to run without xfs FontPath "/usr/share/fonts/misc:unscaled" EndSection Section "Extensions" Option "Composite" EndSection Section "ServerFlags" #DontZap # disable <Crtl><Alt><BS> (server abort) #DontZoom # disable <Crtl><Alt><KP_+>/<KP_-> (resolution switching) AllowMouseOpenFail # allows the server to start up even if the mouse does not work EndSection Section "Module" Load "dbe" # Double-Buffering Extension Load "v4l" # Video for Linux Load "extmod" Load "type1" Load "freetype" Load "glx" # 3D layer Load "dri" # direct rendering EndSection Section "InputDevice" Identifier "Keyboard1" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "pl" Option "XkbOptions" "compose:rwin" EndSection Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "ExplorerPS/2" Option "Device" "/dev/mouse" EndSection Section "InputDevice" Identifier "Mouse2" Driver "evdev" Option "product" "0xc01d" Option "HWheelRelativeAxisButtons" "7 6" Option "vendor" "0x046d" EndSection Section "Monitor" Identifier "monitor1" VendorName "Sony" ModelName "CPD E-230" HorizSync 38.5-85.0 VertRefresh 48-170 # 1024x768 @ 75.00 Hz (GTF) hsync: 60.15 kHz; pclk: 81.80 MHz Modeline "1024x768_75.00" 81.80 1024 1080 1192 1360 768 769 772 802 -HSync +Vsync # TV fullscreen mode or DVD fullscreen output. # 768x576 @ 79 Hz, 50 kHz hsync ModeLine "768x576" 50.00 768 832 846 1000 576 590 595 630 # 768x576 @ 100 Hz, 61.6 kHz hsync ModeLine "768x576" 63.07 768 800 960 1024 576 578 590 616 EndSection Section "Device" Identifier "device1" Driver "vesa" Option "DPMS" EndSection Section "Screen" Identifier "screen1" Device "device1" Monitor "monitor1" DefaultColorDepth 24 Subsection "Display" Depth 8 Modes "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240" EndSubsection Subsection "Display" Depth 15 Modes "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240" EndSubsection Subsection "Display" Depth 16 Modes "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240" EndSubsection Subsection "Display" Depth 24 Modes "1024x768" "832x624" "800x600" "640x480" "480x360" "320x240" EndSubsection EndSection Section "ServerLayout" Identifier "layout1" InputDevice "Keyboard1" "CoreKeyboard" InputDevice "Mouse1" "CorePointer" InputDevice "Mouse2" "SendCoreEvents" Screen "screen1" EndSection I'm counting on Your advises guys ;) Edited June 23, 2007 by zibi1981 Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted June 23, 2007 Report Share Posted June 23, 2007 acpi=off won't help, because it'll disable ACPI which is what is responsible for shutting your machine down. I'd check the acpi packages are installed: rpm -qa | grep -i acpi if you don't have any, check the list of installable packages and install the acpi ones. As for your video card, have you tried using the open-source ATI (fglrx) that comes with Mandriva. Don't install the ati packages or dkms-ati if they don't work, just switch from vesa to ATI (fglrx) and see if it makes a difference. If your monitor is a flat panel LCD, 60Hz is enough anyway. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.