Hello.
I have HP 6820s laptop with radeon x1300. After upgrade of opensuse from 12.2 to 12.3 I’ve got a problem. I can’t boot with modeset enabled. It freezes after writing a line
fb: conflicting fb hw usage radeon drmfb vs VESA VGA - removing generic driver.
If I boot with nomodeset, it not freezes, but X can’t start. I can start X, if I reload radeon module with modeset enabled:
#modprobe -r radeon
#modprobe radeon modeset=1
How can I solve this problem, or how can I reload radeon module automatically just before starting X? Plz help…
A possible kernel regression perhaps? Can you boot in failsafe mode okay?
Can you post your config in /etc/default/grub?
Can you edit the /etc/X11/xorg.conf.d/50-device.conf file to load the radeon model ? ie something the following (ignore the comment statements):
Section "Device"
Identifier "Default Device"
#
Driver "radeon"
#
# ## Required magic for radeon/radeonhd drivers; output name
# ## (here: "DVI-0") can be figured out via 'xrandr -q'
# #Option "monitor-DVI-0" "Default Monitor"
#
EndSection
and then also boot with nomodeset ? Does that work ?
On Thu, 14 Mar 2013 05:36:01 GMT
eyenie <eyenie@no-mx.forums.opensuse.org> wrote:
>
> Hello.
> I have HP 6820s laptop with radeon x1300. After upgrade of opensuse
> from 12.2 to 12.3 I’ve got a problem. I can’t boot with modeset
> enabled. It freezes after writing a line
> fb: conflicting fb hw usage radeon drmfb vs VESA VGA - removing
> generic driver.
> If I boot with nomodeset, it not freezes, but X can’t start. I can
> start X, if I reload radeon module with modeset enabled:
> #modprobe -r radeon
> #modprobe radeon modeset=1
> How can I solve this problem, or how can I reload radeon module
> automatically just before starting X? Plz help…
>
>
I tried booting with ‘nomodeset’ on a Radeon machine because of
graphics troubles with GRUB2 and found it stalled at ‘Reached target
Graphical Interface.’ I then tried on another machine with Intel
Arrandale graphics and got the same result.
[The problem booting with GRUB2 was fixed by altering the graphics mode
to 800x600.]
–
Graham P Davis, Bracknell, Berks.
openSUSE 12.3-RC2 (64-bit); KDE 4.10.00; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
Can you post your config in /etc/default/grub? Can you boot in failsafe mode okay?
GRUB_DISTRIBUTOR=openSUSE
GRUB_DEFAULT=saved
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=8
GRUB_CMDLINE_LINUX_DEFAULT=" video=1440x900 resume=/dev/disk/by-id/ata-FUJITSU_MHZ2250BH_G2_K617T882LMEA-part9 splash=silent quiet showopts"
GRUB_CMDLINE_LINUX_RECOVERY=“showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe”
GRUB_CMDLINE_LINUX=“”
GRUB_TERMINAL=gfxterm
GRUB_GFXMODE=auto
GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt
GRUB_BACKGROUND=/boot/grub2/themes/openSUSE/background.png
In failsafe mode it stalls on line:
Reached target Graphical Interface
Can you edit the /etc/X11/xorg.conf.d/50-device.conf file to load the radeon model and and then also boot with nomodeset ? Does that work ?
It doesn’t work, had the same file. It stalls on line: Reached target Graphical Interface
Changing GRUB graphic mode doesn’t change anything
On Thu, 14 Mar 2013 14:06:01 GMT
eyenie <eyenie@no-mx.forums.opensuse.org> wrote:
> > Can you edit the /etc/X11/xorg.conf.d/50-device.conf file to load
> > the radeon model and and then also boot with nomodeset ? Does that
> > work ?
> It doesn’t work, had the same file. It stalls on line: Reached target
> Graphical Interface
This appears to be a bug associated with ‘nomodeset’ that has nothing
to do with the particular graphics device. I’ve raised a bug on the
matter - https://bugzilla.novell.com/show_bug.cgi?id=809361
>
> Changing GRUB graphic mode doesn’t change anything
The problem I had with Radeon graphics only manifested itself in GRUB2,
GRUB was OK. https://bugzilla.novell.com/show_bug.cgi?id=803026
–
Graham P Davis, Bracknell, Berks.
openSUSE 12.3 (64-bit); KDE 4.10.00; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nouveau driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306
try the following,
when “Reached target Graphical Interface” is reached
press alt-F1, this should take you to a terminal login
try logging in as root and then
start yast and /etc/sysconfig editor
search for KMS then press goto
then make sure NO_KMS_IN_INITRD is set to no
save then reboot
hth
another point,
if the above does not work
any proprietary graphics driver needs to be removed!
a re-install can always be tried later
I’ve already tried to set NO_KMS_IN_INITRD to yes - it doesn’t help. And I have not any proprietary drivers installed.
Yes, I can.
When I boot with nomodeset, I have next in Xorg log:
…
36.534] (++) using VT number 7
36.535] (II) [KMS] drm report modesetting isn’t supported.
36.535] (II) [KMS] drm report modesetting isn’t supported.
36.535] (II) [KMS] drm report modesetting isn’t supported.
36.535] (EE) Screen 0 deleted because of no matching config section.
36.535] (II) UnloadModule: “radeon”
36.535] (EE) Screen 0 deleted because of no matching config section.
36.535] (II) UnloadModule: “radeon”
36.535] (EE) Device(s) detected, but none match those in the config file.
36.535] Fatal server error:
…
After reloading radeon with modeset:
#modprobe -r radeon
#modprobe radeon modeset=1
#systemctl start xdm.service
I have next in Xorg log:
…
235.124] (++) using VT number 7
235.125] (II) [KMS] Kernel modesetting enabled.
235.125] (II) RADEON(0): Creating default Display subsection in Screen section
“Default Screen Section” for depth/fbbpp 24/32
235.125] (==) RADEON(0): Depth 24, (–) framebuffer bpp 32
235.125] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
235.125] (==) RADEON(0): Default visual is TrueColor
235.125] (==) RADEON(0): RGB weight 888
235.125] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
235.125] (–) RADEON(0): Chipset: “ATI Mobility Radeon X1350” (ChipID = 0x7196)
…
in 12.3 KMS is needed in the initrd if the native driver is to be used
NO_KMS_IN_INITRD if set to no means KMS is loaded (negative logic)
“I’ve already tried to set NO_KMS_IN_INITRD to yes - it doesn’t help.
And I have not any proprietary drivers installed.”
double check that this parameter is set to no
also check the following
start
- yast
– Boot Loader
– check that ‘set Boot from Root Partition’ flag is checked
then from
—Boot Loader Settings
– check ‘set active Flag in Partition Table for Boot Partition’ flag is checked
also delete modeset and/or nomodeset from the cmd line
then press ok and reboot
any help?
With such settings it freezes at the beginning - on line:
Starting udev…
unfortunately every driver has different characteristics and effects
can you post the contents of the following files
/etc/X11/xorg.conf.d/50-device.conf
/etc/X11/xorg.conf.d/50-monitor.conf
/etc/X11/xorg.conf.d/50-screen.conf
/etc/X11/xorg.conf
the above may exceed the 4k posting limit,
if they do split them into two posts or
send them to the paste page
cheers
50-device.conf:
Section “Device”
Identifier “Default Device”
Driver “radeon”
EndSection
50-monitor.conf:
#only comments
50-screen.conf:
#only comments
xorg.conf
haven’t such file
Someone reporting a similar issue here:
KMS, linux kernel 3.7 and ati mobility radeon x1350 - Super User
I think you should add to the bug report that cloddy created.
nothing detrimental in the .conf files (nothing really there)
(on this desktop those files don’t even exist with Radeon HD 3200)
can you post a copy to SUSE Paste of the file
/var/log/Xorg.0.log
pps. commenting out the active lines in file
50-device.conf
could be tried, this then allows kms to do all selections
quote from output of cmd ‘info radeon’
“RV505/RV515/RV516/RV550 Radeon X1300/X1400/X1500/X1550/X2300”
I think it’s kernel regression.
I added to blacklist radeon module:
If I try #modprobe radeon modeset=1 then OS freezes
If I try #modprobe radeon modeset=0
#modprobe -r radeon
#modprobe radeon modeset=1
then everything is ok, and I’m able to start X
Also found topic with the same problem: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=845745
And Kernel 3.4 works
Thx guys.
I experienced exactly the same problem as eyenie with a radeon "RV100 Radeon 7000(VE) " card so I was waiting on a solution on it. Now that eyenie find a solution I will jump in to ask few questions. Should I add the info to the existing bug? My screen is garbled when starting with nomodeset, not readable. Or should I just try blacklisting as per eyenie solution?
here is my Xorg.log SUSE Paste
Why a monitor of type DELL is present as I never connected that type from this OS. How doe it get there? passed from BIOS? I’m using a BENQ monitor on it. If someone can spot anything can you tell me what? I looked and I cannot find anything to be able to say is wrong, most probably because I don’t know what to look for. Thank you and sorry if jumped in.
Well I tried eyenie solution but no joy for me:
modprobe radeon modeset=0
montserrat:/home/dan # modprobe -r radeon
FATAL: Module radeon is in use.
montserrat:/home/dan # modprobe radeon modeset=1
init 5 gets me to a screen on which I can see the lizard and the vine on the bottom right corner but there is nothing else and no mouse or keyboard. Any ideas?