After install reboot something wrong !

Started by bryn1u, 2012/01/19, 01:06:14

Previous topic - Next topic

bryn1u

Hello.

After install i got something like that:

http://imageshack.us/photo/my-images/835/20120119005141.jpg/
And notebook has stopped.
My graphic card it: AMD Radeon HD 6720G2 1 GB Dedicated 1 VRAM.

devil

You need firmware-linux-nonfree

greetz
devil

towo

And it is nessesary, that /etc/X11/xorg.conf is removed after installing firmware-linux-nonfree.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

bryn1u

Siduction asked me before install if he may install firmware-linux-nonfree a marked "YES".  Soo how can i install firmware-linux-nonfree when i cant change terminal i see only what is on screen.

Greetz.

towo

Boot your system with radeon.modeset=0 as bootcheat, then you will see anything.
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Geier0815

Try to boot in Runlevel 3 and than change your config. Have a look here
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

bryn1u

Quote from: "towo"Boot your system with radeon.modeset=0 as bootcheat, then you will see anything.

And another question from newbie :P. Where should i put this command and how?

towo

That's not a command, it's a cheatcode.
Hit "e" at the grub bootscreen and add that cheatcode at the end of the kernel-line. Then hit ctrl+x, thats all.
Ever read the bluewater-manual?
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

bryn1u

Sure. Always read. I mean "command" not command. I asked becouse i put cheatcode in grub bootscreen once in aptosid and didnt work, that's why i asked about basic question.

Thx. I will try when i back from work.
Greetz.

bryn1u

Hey.

I have installed siduction well. I downloaded firmware-linux and install but i still have to use cheatcode to normally boot my siduction. How can i resolve this problem ?

Greetz.

devil

The needed firmware package is calledfirmware-linux-nonfree

greetz
devil

piper

Quote from: "bryn1u"Hey.

I have installed siduction well. I downloaded firmware-linux and install but i still have to use cheatcode to normally boot my siduction. How can i resolve this problem ?

Greetz.

You can try and put the cheatcode in/etc/default/grub
The line you want it in looks like this
GRUB_CMDLINE_LINUX_DEFAULT="quiet"so when all is done, it will look like thisGRUB_CMDLINE_LINUX_DEFAULT="quiet radeon.modeset=0"

There has to be a space between quiet and radeon.modeset=0

save and update-grub and reboot

**EDIT** : this is of course if apt-get update && apt-get install firmware-linux-nonfree doesn't work
I have a Lucky Rabbit:    "Svoot" ..... (It's Swedish)

I am MAGA

blackone

Do you have

deb http://ftp.uk.debian.org/debian unstable main non-free

within your /etc/apt/sources.list.d/debian.list

Also you get around having to edit the new and complex grub2 configuration you can as a permanent insert place

options radeon.modeset=0

into

/etc/modprobe.d/radeon.conf (if you have that).

If you are able to install the linux-firmware-nonfree package then you may have in /etc/modprobe.d/radeon-kms.conf.  Just place the line option radeon modeset=0 in there instead of /etc/modprobe.d/radeon.conf.

Kms will be permanently disabled this way.

And while you are about it if you have pcie card as opposed to agp you can place "options radeon agpmode=-1" into /etc/modprobe.d/radeon-kms.conf or /etc/modprobe.d/radeon.conf (depending on what you have).

tuxic

If it's possible PLEASE make an illustrated tutorial.  I'm having the same problem for weeks and I can't install it and make it run.  On the other hand I installed the other OS (no pun intended) recently without problems.  I don't know if it's a bug but if it is please fix it.  I'm not a geek bou love your approach to Linux...
"Many people live and die..., and all they do is process groceries."
                  H. Peavey

michaa7

please, which line in the above description is unclear? You simply have to follow step by step. This wont change with whatever illustration. So give it a try. You are wellcome to report each error message. But you have to open your CLI (command line interface) yourself.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake