SliTaz SliTaz Forum

You are not logged in.

#1 2014-04-06 17:56:45

vergote
Member
Registered: 2014-03-31
Posts: 27

one slitaz per graphic chip

why its not possible to have a flavor for nvidia ; ati ; intel ..   so many people a just wasting time when facing a black screen after boot !!!

Offline

#2 2014-04-06 19:43:25

devl547
Administrator
Registered: 2011-06-01
Posts: 285

Re: one slitaz per graphic chip

>so many people a just wasting time when facing a black screen after boot !!!

standart vesa driver handles everything just fine.

Offline

#3 2014-04-06 20:14:48

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

Hi Reptile,

Is the last rolling a vesa driver ? because now it works

At least something appears on the screen. But no way to output on an external screen , neither to change the screen resolution ... sad

Offline

#4 2014-04-09 10:04:22

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

is it normal that i have  screen0 , screen1 , screen2 , screen3

(and same for devices, monitor)  in /etc/X11/xorg.conf.d    ?

I've got an hybrid  Intel HD Haswell + Radeon 8850m in my laptop , should I turn off one of them at boot ?  What can I  do ?

Offline

#5 2014-04-09 11:32:14

Guest
Guest

Re: one slitaz per graphic chip

Linux/BSD allows you to have, if I remember rightly, 12 screens (VT,s) by default, usually 8 are configured, but this can be tweeked.

Most window manager/desktop environments have 4 desktops configured by default, again, this can be changed.

It isn't like MS Windows, it is a much more flexible OS - with lots to learn if you want to.

#6 2014-04-09 14:07:06

bellard
Administrator
Registered: 2011-03-28
Posts: 657

Re: one slitaz per graphic chip

> Linux/BSD allows you to have, if I remember rightly, 12 screens (VT,s) by default, usually 8 are configured, but this can be tweeked.

The linux kernel supports up to 63 (1..63) VT.

VT 1 to 6 are text (# grep getty /etc/inittab), X11 may use  VT 7 or more (you can start more X servers)

# conspy -f 1

# conspy -f 2

...

# conspy -fcs 8

# conspy -fcs 63

# chvt 63

...

Offline

#7 2014-04-09 18:10:16

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: one slitaz per graphic chip

@vergote   "Is the last rolling a vesa driver ? because now it works"

no last rolling seems to be with wayland... quite interesting...

Offline

#8 2014-04-09 18:31:23

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: one slitaz per graphic chip

somehow not true - sorry I mixed it up - only wayland was cooked not included in the iso....

Offline

#9 2014-04-10 17:07:36

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

I'm ready to to do a step by step process with one of you and give the output. I think it may be usefull for slitaz's prospectives as i'm the owner of the lastest intel cpu coupled with an extra graphic chip ; this seems to be a new trend among laptop constructors.

Offline

#10 2014-04-11 08:04:29

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: one slitaz per graphic chip

please post the output of lspci -nnvv

most of theese laptops have 2 grafic cards - an intel + nvida or amd

at least the intel card you should get easy

boot with the option  "screen=text" log in - get root and run tazx and select the intel driver log out to tux with "exit" and startx

Offline

#11 2014-04-11 21:02:05

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 09)

    Subsystem: Dell Device [1028:0609]

    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

    Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-

    Latency: 0

    Capabilities: <access denied>

00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller])

    Subsystem: Dell Device [1028:0609]

    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

    Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

    Latency: 0

    Interrupt: pin A routed to IRQ 7

    Region 0: Memory at c0000000 (64-bit, non-prefetchable) [size=4M]

    Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]

    Region 4: I/O ports at 5000 [size=64]

    Expansion ROM at <unassigned> [disabled]

    Capabilities: <access denied>

00:1b.0 Audio device [0403]: Intel Corporation Lynx Point-LP HD Audio Controller [8086:9c20] (rev 04)

    Subsystem: Dell Device [1028:0609]

    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

    Latency: 0, Cache Line Size: 64 bytes

    Interrupt: pin A routed to IRQ 22

    Region 0: Memory at c0810000 (64-bit, non-prefetchable) [size=16K]

    Capabilities: <access denied>

    Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation Lynx Point-LP PCI Express Root Port 3 [8086:9c14] (rev e4) (prog-if 00 [Normal decode])

    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

    Latency: 0, Cache Line Size: 64 bytes

    Bus: primary=00, secondary=01, subordinate=01, sec-latency=0

    I/O behind bridge: 00004000-00004fff

    Memory behind bridge: c0700000-c07fffff

    Prefetchable memory behind bridge: 00000000c0400000-00000000c04fffff

    Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-

    BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-

        PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

    Capabilities: <access denied>

    Kernel driver in use: pcieport

00:1c.3 PCI bridge [0604]: Intel Corporation Lynx Point-LP PCI Express Root Port 4 [8086:9c16] (rev e4) (prog-if 00 [Normal decode])

    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

    Latency: 0, Cache Line Size: 64 bytes

    Bus: primary=00, secondary=02, subordinate=02, sec-latency=0

    Memory behind bridge: c0600000-c06fffff

    Prefetchable memory behind bridge: 000000009fb00000-000000009fbfffff

    Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-

    BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-

        PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

    Capabilities: <access denied>

    Kernel driver in use: pcieport

00:1c.4 PCI bridge [0604]: Intel Corporation Lynx Point-LP PCI Express Root Port 5 [8086:9c18] (rev e4) (prog-if 00 [Normal decode])

    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

    Latency: 0, Cache Line Size: 64 bytes

    Bus: primary=00, secondary=03, subordinate=03, sec-latency=0

    I/O behind bridge: 00003000-00003fff

    Memory behind bridge: c0500000-c05fffff

    Prefetchable memory behind bridge: 00000000a0000000-00000000afffffff

    Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-

    BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-

        PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

    Capabilities: <access denied>

    Kernel driver in use: pcieport

03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Venus PRO [Radeon HD 8850M] [1002:6823] (prog-if 00 [VGA controller])

    Subsystem: Dell Device [1028:0609]

    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

    Interrupt: pin A routed to IRQ 11

    Region 0: Memory at a0000000 (64-bit, prefetchable) [disabled] [size=256M]

    Region 2: Memory at c0500000 (64-bit, non-prefetchable) [disabled] [size=256K]

    Region 4: I/O ports at 3000 [disabled] [size=256]

    Expansion ROM at c0540000 [disabled by cmd] [size=128K]

    Capabilities: <access denied>

Offline

#12 2014-04-11 21:04:54

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

For the second step, it's already done and then, did the first step after

Offline

#13 2014-04-12 08:31:59

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: one slitaz per graphic chip

so I guess the intel card is working correctly ???

for the hybrid grafics - I think, it should work -  switcheroo is built in the kernel

3340 CONFIG_VGA_SWITCHEROO=y

for the ati grafic card this should be installed

firmware-radeon

xorg-xf86-video-ati

mesa

mesa-dri

mesa-dri-ati

mesa-demos

more info you get in  the Arch Wiki

https://wiki.archlinux.org/index.php/hybrid_graphics

Offline

#14 2014-04-12 21:34:21

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

Hi Kultex,

1° The basic vesa in the rolling works but no extra resolution in lxrandr neither  external screen available

2° and I've installed all the intel stuff  "xorg-video-intel" with it's dependencies and made of it a new iso. Reboot. But same problem than before  (don't even know if it's still vesa render ? how I can I know ?)

3° did the same than point 2° but for xorg-xf86-video-ati (and all dependencies) 

tazx leads to a configuration but xorg error

Offline

#15 2014-04-12 21:41:57

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

within my iso with intel , i just install all the packages you suggest for ati and then did a tazx in a terminal with ati choice

X.Org X Server 1.12.4

Release Date: 2012-08-27

X Protocol Version 11, Revision 0

Build Operating System: SliTaz GNU/Linux

Current Operating System: Linux slitaz 3.2.53-slitaz #1 SMP Sat Mar 22 05:55:11 UTC 2014 i686

Kernel command line: BOOT_IMAGE=/boot/bzImage initrd=/boot/intel.gz rw root=/dev/null lang=fr_FR kmap=de-latin1

Build Date: 03 January 2014  02:01:10PM

Current version of pixman: 0.28.2

        Before reporting problems, check http://www.slitaz.org/

        to make sure that you have the latest version.

Markers: (--) probed, (**) from config file, (==) default setting,

        (++) from command line, (!!) notice, (II) informational,

        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(==) Log file: "/var/log/Xorg.2.log", Time: Sun Apr 13 01:36:25 2014

List of video drivers:

        radeon

        ati

        intel

        fbdev

        vesa

(++) Using config file: "/root/xorg.conf.new"

(==) Using config directory: "/etc/X11/xorg.conf.d"

Backtrace:

0: Xorg (xorg_backtrace+0x46) [0x8171dba]

1: Xorg (0x8048000+0x12cc42) [0x8174c42]

2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]

Segmentation fault at address (nil)

Fatal server error:

Caught signal 11 (Segmentation fault). Server aborting

Please consult the The X.Org Foundation support

         at http://www.slitaz.org/

for help.

Please also check the log file at "/var/log/Xorg.2.log" for additional information.

Server terminated with error (1). Closing log file.

Aborted

Offline

#16 2014-04-16 15:00:58

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: one slitaz per graphic chip

to know which server:

check /var/log/xorg.0.log

if it is stil vesa - change it in

/etc/X11/xorg.conf.d/60-Device.conf

Driver      "intel"

Offline

#17 2014-04-17 18:52:40

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

On last cooking .

Before Intel driver installation

Section "Device"

        ### Available Driver options are:-

        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",

        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",

        ### <percent>: "<f>%"

        ### [arg]: arg optional

        #Option     "ShadowFB"               # [<bool>]

        #Option     "Rotate"                 # <str>

        #Option     "fbdev"                  # <str>

        #Option     "debug"                  # [<bool>]

    Identifier  "Card0"

    Driver      "fbdev"

    BusID       "PCI:0:2:0"

EndSection

Section "Device"

        ### Available Driver options are:-

        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",

        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",

        ### <percent>: "<f>%"

        ### [arg]: arg optional

        #Option     "ShadowFB"               # [<bool>]

        #Option     "Rotate"                 # <str>

        #Option     "fbdev"                  # <str>

        #Option     "debug"                  # [<bool>]

    Identifier  "Card1"

    Driver      "fbdev"

    BusID       "PCI:3:0:0"

EndSection

Section "Device"

        ### Available Driver options are:-

        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",

        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",

        ### <percent>: "<f>%"

        ### [arg]: arg optional

        #Option     "ShadowFB"               # [<bool>]

        #Option     "DefaultRefresh"         # [<bool>]

        #Option     "ModeSetClearScreen"     # [<bool>]

    Identifier  "Card2"

    Driver      "vesa"

    BusID       "PCI:0:2:0"

EndSection

Section "Device"

        ### Available Driver options are:-

        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",

        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",

        ### <percent>: "<f>%"

        ### [arg]: arg optional

        #Option     "ShadowFB"               # [<bool>]

        #Option     "DefaultRefresh"         # [<bool>]

        #Option     "ModeSetClearScreen"     # [<bool>]

    Identifier  "Card3"

    Driver      "vesa"

    BusID       "PCI:3:0:0"

EndSection

Offline

#18 2014-04-17 18:59:33

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

then install Intel video

....

xorg-xf86-video-intel (2.21.9) est installé.

X.Org X Server 1.12.4

Release Date: 2012-08-27

X Protocol Version 11, Revision 0

Build Operating System: SliTaz GNU/Linux

Current Operating System: Linux slitaz 3.2.53-slitaz #4 SMP Fri Jan 31 23:12:06 CET 2014 i686

Kernel command line: BOOT_IMAGE=/boot/bzCook initrd=/boot/cook.gz rw root=/dev/null lang=fr_FR kmap=be-latin1

Build Date: 03 January 2014  02:01:10PM

Current version of pixman: 0.28.2

        Before reporting problems, check http://www.slitaz.org/

        to make sure that you have the latest version.

Markers: (--) probed, (**) from config file, (==) default setting,

        (++) from command line, (!!) notice, (II) informational,

        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(==) Log file: "/var/log/Xorg.2.log", Time: Thu Apr 17 22:55:23 2014

List of video drivers:

        intel

        fbdev

        vesa

(++) Using config file: "/root/xorg.conf.new"

(==) Using config directory: "/etc/X11/xorg.conf.d"

Backtrace:

0: Xorg (xorg_backtrace+0x46) [0x8171dba]

1: Xorg (0x8048000+0x12cc42) [0x8174c42]

2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]

Segmentation fault at address (nil)

Fatal server error:

Caught signal 11 (Segmentation fault). Server aborting

Please consult the The X.Org Foundation support

         at http://www.slitaz.org/

for help.

Please also check the log file at "/var/log/Xorg.2.log" for additional information.

Server terminated with error (1). Closing log file.

Aborted

root@slitaz:~#

Offline

#19 2014-04-17 19:04:14

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

obviously, no changes in the 60-Device.conf

Offline

#20 2014-04-17 19:34:15

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: one slitaz per graphic chip

ok, first try to remove xorg-xf86-video-fbdev + xorg-xf86-video-vesa, before you install the intel driver

if this does not help, post the /var/log/Xorg.2.log after the fail.

Offline

#21 2014-04-17 20:31:37

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

X.Org X Server 1.12.4

Release Date: 2012-08-27

X Protocol Version 11, Revision 0

Build Operating System: SliTaz GNU/Linux

Current Operating System: Linux slitaz 3.2.53-slitaz #4 SMP Fri Jan 31 23:12:06 CET 2014 i686

Kernel command line: BOOT_IMAGE=/boot/bzCook initrd=/boot/cook.gz rw root=/dev/null lang=fr_FR kmap=be-latin1

Build Date: 03 January 2014  02:01:10PM

Current version of pixman: 0.28.2

        Before reporting problems, check http://www.slitaz.org/

        to make sure that you have the latest version.

Markers: (--) probed, (**) from config file, (==) default setting,

        (++) from command line, (!!) notice, (II) informational,

        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(==) Log file: "/var/log/Xorg.2.log", Time: Fri Apr 18 00:30:08 2014

List of video drivers:

        intel

No devices to configure.  Configuration failed.

Server terminated with error (2). Closing log file.

sed: /root/xorg.conf.new: No such file or directory

sed: /root/xorg.conf.new: No such file or directory

sed: /root/xorg.conf.new: No such file or directory

sed: /root/xorg.conf.new: No such file or directory

sed: /root/xorg.conf.new: No such file or directory

sed: /root/xorg.conf.new: No such file or directory

rm: can't remove '/root/xorg.conf.new': No such file or directory

Offline

#22 2014-04-18 20:47:41

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: one slitaz per graphic chip

I organiced the touring laptop from the theatre, which has a dual grafic chip with intel + nvidia and I just end up with a black screen and I dont come out - so at the moment I can not help you - first I have to solve this on this laptop.

Offline

#23 2014-04-23 17:03:07

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

thanks Kultex for helping. Don't forget that disabling the extra gpu could be a solution and the possibilty to connect an external screen on the vga is the effective goal

Offline

#24 2014-04-23 19:32:07

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: one slitaz per graphic chip

disabeling the extra gpu I think is not possible - at least with the laptop I have. I wanted to do this already in windows, because the intel card makes problems with isadora.

but in general, we have to finde a solution for those dual grafic laptops - it would be nice, if you could stay on this tread - because next week I hope I find some time to look into it

Offline

#25 2014-04-24 20:55:25

vergote
Member
Registered: 2014-03-31
Posts: 27

Re: one slitaz per graphic chip

all right,  and you can even create a sticky topic to call and invite other slitaz users using dual graphic laptops too

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.021 seconds, 8 queries executed - Memory usage: 1.61 MiB (Peak: 1.77 MiB) ]