You are not logged in.
Hey there.
I'm looking for some guidance if possible.
I installed Arch in an external hard drive to test out the compatibility with my laptop (a LG P1-J331P > http://pastie.org/8548089 ) with an ATI Mobility Radeon X1400 video card. All following the beginner's guide [https://wiki.archlinux.org/index.php/Beginners%27_Guide] and relevant wiki for the external/usb device installation [https://wiki.archlinux.org/index.php/Usb_installation].
Running arch with "nomodeset" on kernel parameter, it runs normally, except that the screen resolution was fixed at 1024x768@61.0, though it should be maxed at 1280x800@60.
When "nomodeset" is set:
$dmesg | grep radeon
[ 10.859500] [drm] VGACON disable radeon kernel modesetting.
[ 10.859507] [drm:radeon_init] *ERROR* No UMS support in radeon module!
Without using "nomodeset", the system detects correctly the screen resolution but it freezes few seconds later after logging. Can't Ctrl+Alt+F1.
Tried:
- added "radeon" to MODULES array in the mkinitcpio file. And run the subsequent "mkinitcpio -p linux";
- created a "/etc/rc.d/rc.local" file with contents:
modprobe -r radeon
modprobe -r drm
modprobe radeon modeset=1
- tested "radeon.pcie_gen2=0", "pci=nomsi", "noapic" and "acpi=off" to the kernel parameter.
- created a "/etc/X11/xorg.conf.d/10-monitor.conf" file with contents: http://pastie.org/private/bhcbfvs3zvplvspwamxa2q
Video card drivers installed: mesa, xf86-video-vesa and xf86-video-ati.
lsmod > http://pastie.org/private/orfrp0qg8kijqwuvrrxqag
uname -r > http://pastie.org/private/u89igykam0slvnv2ffhhpq
lspci | grep VGA >
dmesg | grep radeon >
journalctl --since=today >
cat /var/log/Xorg.0.log > http://pastie.org/private/thgrsplegancpggsfsbjlw
top -b > http://codepad.org/iojWRb9U
Any advice for this newbie would be appreciated.
Last edited by T-Cypher (2014-03-11 16:00:55)
Offline
- Tried creating a "/etc/X11/xorg.conf.d/20-radeon.conf" file with contents:
Section "Device"
Identifier "ATI Mobility Radeon X1400"
Driver "radeon"
Option "SWcursor" "off" #software cursor might be necessary on some rare occasions, hence set off by default
Option "EnablePageFlip" "on" #supported on all R/RV/RS4xx and older hardware, and set on by default
Option "AccelMethod" "EXA" #valid options are XAA, EXA and Glamor. EXA is the default
Option "RenderAccel" "on" #enabled by default on all radeon hardware
Option "ColorTiling" "on" #enabled by default on RV300 and later radeon cards
Option "EXAVSync" "off" #default is off, otherwise on. Only works if EXA activated
Option "EXAPixmaps" "on" #when on icreases 2D performance, but may also cause artifacts on some old cards. Only works if EXA activated
Option "AccelDFS" "on" #default is off, read the radeon manpage for more information
EndSection
And the subsequent Xorg.0.log > http://pastie.org/private/goyhnu9bzxhzybl4sisaa
With this file and using "nomodeset", the boot would be stuck at :
[ OK ] Reached target Graphical Interface.
But without "nomodeset" parameter, it would successfully launch the graphical login but still freezes a few seconds after logging in.
xdpyinfo | grep -B2 resolution
screen #0:
dimensions: 1280x800 pixels (338x211 millimeters)
resolution: 96x96 dots per inch
Offline
- tested "modprobe.blacklist=sdhci,sdhci_pci,mmc_core" to the kernel parameter.
- tried using live environments: - Puppy Linux (precise-5.7.1.iso), Ubuntu 12.04.3 LTS (ubuntu-12.04.3-desktop-i386.iso)
Puppy Linux managed to stay up and running for a few minutes while I was messing with the temporary configurations.
- tried installing Ubuntu 12.04.3 LTS (ubuntu-12.04.3-alternate-i386.iso) on the external HDD and using Unity 2D on logging in.
Without "nomodeset", I barely logged in and it froze. It didn't even give me enough time to access logs. With "nomodeset" it ran OK, just like on Arch with "nomodeset" (relatively speaking). Managed to get some logs but I don't think those are relevants due the usage of "nomodeset".
- under Ubuntu, tested "modprobe.blacklist=iwlegacy,iwl3945,cfg80211" to the kernel parameter.
Some of these "testings" might not even be related to my problem, but I'm at the point of testing anything remotely similar to see if there is any change.
Anyway I should reinstall Arch again so I am ready to test another solution when given the chance.
Any advice or should I just forget to use Arch (or any other distro) on this machine?
Offline
According to http://wiki.cchtml.com/index.php/Hardware, it needs to use kernel <= 2.6.28 and Xserver <= 1.5. Tested it with a Live CD of Ubuntu 8.04 and it works fine.
Offline