Re: Shutting down my PowerBook G4 doesn't really shut down?
Hi, On Fri, Mar 17, 2017 at 4:57 AM, PhiLLip Pi wrote: > I noticed every time I do a shut down from Debian PPC stable/Jessie, it > doesn't fully shut down. I see its screen go black and stuff. I can't > even wake it up with keys (can't even ctrl+alt+F1 keys), trackpad and > its button, and power button. Holding its power button for five seconds > fully shuts down (can hear its fan and other shut down), and then I can > power up again. It seems to get stuck in its shut down. It even happens > in its X login screen. :( What do you see in the system log as you shutdown ? Does it get stuck on something (you may want to ssh onto your laptop and tail -f the log file). -M
Re: POWER6 not seeing memory above 2Gb
On Wed, Mar 22, 2017 at 09:07:49PM -0400, Adam Stouffer wrote: > Hello all, I'm new to the list and just installed jessie on my IBM > 8203-E4A box. It's a dual core 4.2Ghz with 16Gb of memory. > > But anyhow like the subject says the kernel is only reporting 2Gb of > available memory. I tried appending "mem=16G" as a boot argument but > no change. I assume this is an LPAR. How is it configured? Do you have an HMC or IVM connected to it? Cascardo. > > Here is the output from dmesg with kernel 3.16.0 > > [0.00] physicalMemorySize= 0x8000 > [0.00] Node 0 Memory: 0x0-0x8000 > [0.00] Early memory node ranges > [0.00] Memory: 1899264K/2097152K available (7360K kernel code, > 1792K rwdata, 1840K rodata, 960K init, 2071K bss, 197888K reserved) > [0.023173] Initializing cgroup subsys memory > [1.036652] Freeing initrd memory: 16384K (c348 - > c448) > [1.242857] Freeing unused kernel memory: 960K (c091 - > c0a0) > > Any ideas? Thanks. >
Re: Shutting down my PowerBook G4 doesn't really shut down?
On Thu, Mar 23, 2017 at 08:04:42AM +0100, Mathieu Malaterre wrote: > Hi, > > On Fri, Mar 17, 2017 at 4:57 AM, PhiLLip Pi wrote: > > I noticed every time I do a shut down from Debian PPC stable/Jessie, it > > doesn't fully shut down. I see its screen go black and stuff. I can't > > even wake it up with keys (can't even ctrl+alt+F1 keys), trackpad and > > its button, and power button. Holding its power button for five seconds > > fully shuts down (can hear its fan and other shut down), and then I can > > power up again. It seems to get stuck in its shut down. It even happens > > in its X login screen. :( > > What do you see in the system log as you shutdown ? Does it get stuck > on something (you may want to ssh onto your laptop and tail -f the log > file). For some reason, now the old PB G4 shuts down. I will check if it happens again. -- Quote of the Week: "Have I told you how much I like ants, huh? Especially fried in a subtle blend of mech fluid and grated gears?" --Rampage to Inferno, "Transmutate" in Transformers (Beast Wars) Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly. /\___/\Phil./Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net | |o o| | E-mail: phi...@earthlink.net/a...@zimage.com \ _ / If crediting, then please kindly use Ant nickname ( ) and AQFL URL/link.
Re: Shutting down my PowerBook G4 doesn't really shut down?
On 03/23/2017 10:43 AM, PhiLLip Pi wrote: > For some reason, now the old PB G4 shuts down. I will check if it > happens again. I would recommend hooking up a serial console or a netconsole to watch the kernel buffer while the machine is shutting down. This way you should be able to track down at which point during shutdown it hangs. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: debian-installer: virtio support for powerpc cdrom/netboot installs
can you tell me how to unsubscribe from this list... On Wed, Mar 15, 2017 at 10:13 AM, John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> wrote: > Hi Frederic! > > > virtio modules are more and more used in VMs and it would be nice to > have those > > into the netboot and cdrom installers for powerpc on which there are not > at the > > moment. I'm currently in need of these for ppc64 testing. > > That's a very reasonable request and I am pretty sure there is no problem > merging > your patch into the debian-installer repository. One of our sparc64 users > requested > the same change for that architecture as well. > > > Once again, I hit this. On a ppc64 vm, as it's not an official arch, > there no iso > > available and for installing I use netboot, but without virtio support I > don't > > have the network device recognized and I can't netboot. > > There will most likely images available in the near future. Debian > Developer James > Clarke has improved support in debian-installer for Ports architectures > and the > next upload should actually build fine on most of these architectures, > including > ppc64. > > I suggest sending your patch to the debian-boot mailing list. From my > experience, > trivial patches like this one usually get merged quickly. I assume it was > just > overlooked. > > Thanks, > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > > -- jogideas.com
Re: Shutting down my PowerBook G4 doesn't really shut down?
Hllo, i have installed jessie on powerbook g4 1,67 and am very happy with sound and video. can someone please show me how to achieve sleep when i shutdown lid? thank you very much, rich ps. there is supposedly an error with those powerbooks as many don't recognize the second 1gb ram bank. i had this problem on osx and was not able to ssolve it; possible that under linux it behaves differently? does anyone have an experience with the ram being recognized in linux? would be great to have 2gb on my machine here. Am 23/03/17 um 10:51 schrieb John Paul Adrian Glaubitz: On 03/23/2017 10:43 AM, PhiLLip Pi wrote: For some reason, now the old PB G4 shuts down. I will check if it happens again. I would recommend hooking up a serial console or a netconsole to watch the kernel buffer while the machine is shutting down. This way you should be able to track down at which point during shutdown it hangs. Adrian
Re: Shutting down my PowerBook G4 doesn't really shut down?
* Richard Kuenz [2017-03-23 10:55 +0100]: > Hllo, > > i have installed jessie on powerbook g4 1,67 and am very happy with sound > and video. > can someone please show me how to achieve sleep when i shutdown lid? pbbuttonsd should help here. > ps. there is supposedly an error with those powerbooks as many don't > recognize the second 1gb ram bank. You have to change the mainboard or look for a 2GB SO-DIMM. Elimar -- Learned men are the cisterns of knowledge, not the fountainheads ;-)
Re: POWER6 not seeing memory above 2Gb
It is 64-bit kernel? $ uname -a $ lscpu I think that i never tried more than 1 Gb RAM for test linux, because development AIX needs more RAM... Should try that on P7 or P8. Gasha On 03/23/2017 03:07 AM, Adam Stouffer wrote: Hello all, I'm new to the list and just installed jessie on my IBM 8203-E4A box. It's a dual core 4.2Ghz with 16Gb of memory. But anyhow like the subject says the kernel is only reporting 2Gb of available memory. I tried appending "mem=16G" as a boot argument but no change. Here is the output from dmesg with kernel 3.16.0 [0.00] physicalMemorySize= 0x8000 [0.00] Node 0 Memory: 0x0-0x8000 [0.00] Early memory node ranges [0.00] Memory: 1899264K/2097152K available (7360K kernel code, 1792K rwdata, 1840K rodata, 960K init, 2071K bss, 197888K reserved) [0.023173] Initializing cgroup subsys memory [1.036652] Freeing initrd memory: 16384K (c348 - c448) [1.242857] Freeing unused kernel memory: 960K (c091 - c0a0) Any ideas? Thanks.
Re: POWER6 not seeing memory above 2Gb
With 3 Gb assigned to LPAR (p7) it looks correct: gasha@power:~$ dmesg | grep Memory [ 0.00] physicalMemorySize = 0xc000 [ 0.00] Node 0 Memory: 0x0-0xc000 [ 0.00] Memory: 2811776K/3145728K available (7360K kernel code, 1792K rwdata, 1840K rodata, 960K init, 2071K bss, 333952K reserved) jessie 3.16.7 powerpc64 G On 03/23/2017 03:07 AM, Adam Stouffer wrote: Hello all, I'm new to the list and just installed jessie on my IBM 8203-E4A box. It's a dual core 4.2Ghz with 16Gb of memory. But anyhow like the subject says the kernel is only reporting 2Gb of available memory. I tried appending "mem=16G" as a boot argument but no change. Here is the output from dmesg with kernel 3.16.0 [0.00] physicalMemorySize= 0x8000 [0.00] Node 0 Memory: 0x0-0x8000 [0.00] Early memory node ranges [0.00] Memory: 1899264K/2097152K available (7360K kernel code, 1792K rwdata, 1840K rodata, 960K init, 2071K bss, 197888K reserved) [0.023173] Initializing cgroup subsys memory [1.036652] Freeing initrd memory: 16384K (c348 - c448) [1.242857] Freeing unused kernel memory: 960K (c091 - c0a0) Any ideas? Thanks.
Re: debian-installer: virtio support for powerpc cdrom/netboot installs
On Thu, Mar 23, 2017 at 09:54:01AM +, Jonni O'Gorman wrote: > can you tell me how to unsubscribe from this list... https://lists.debian.org/ -- Len Sorensen
Re: POWER6 not seeing memory above 2Gb
On Wed, Mar 22, 2017 at 09:07:49PM -0400, Adam Stouffer wrote: > Hello all, I'm new to the list and just installed jessie on my IBM > 8203-E4A box. It's a dual core 4.2Ghz with 16Gb of memory. > > But anyhow like the subject says the kernel is only reporting 2Gb of > available memory. I tried appending "mem=16G" as a boot argument but > no change. > > Here is the output from dmesg with kernel 3.16.0 Well I know running a 64 bit kernel on that model, does see 16GB ram. But I was doing that with no LPAR or anything else, just Debian installed straight onto the machine (IBM support people have a hard time understanding that people might do that). So either you somehow installed a 32 bit kernel, or you have an LPAR or something else restricting your memory size. -- Len Sorensen
problems with wheezy and xbmc
Hello , i have installed Debian Wheezy on my Powermac G5 Quad. please help me to solve one problem i have with graphics. whether i use xbmc or kodi or mpv for videoplayback, it always comes with rasterised graphics; no problem with vlc or mplayer or videoplayback directly on youtube. this is some output rich@debian:~$ glxinfo | grep -i renderer OpenGL renderer string: Gallium 0.4 on NV47 rich@debian:~$ vblank_mode=0 glxgears ATTENTION: default value of option vblank_mode overridden by environment. ATTENTION: default value of option vblank_mode overridden by environment. 1946 frames in 5.3 seconds = 364.961 FPS 1946 frames in 5.0 seconds = 388.572 FPS but rich@debian:~$ xbmc libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 what is wrong with my graphics? the card should be capable it it is 7800gtx 256mb. thank you very much
Re: POWER6 not seeing memory above 2Gb
On Thu, Mar 23, 2017 at 9:32 AM, Lennart Sorensen < lsore...@csclub.uwaterloo.ca> wrote: > > Well I know running a 64 bit kernel on that model, does see 16GB ram. > But I was doing that with no LPAR or anything else, just Debian installed > straight onto the machine (IBM support people have a hard time > understanding that people might do that). > > So either you somehow installed a 32 bit kernel, or you have an LPAR or > something else restricting your memory size. > > -- > Len Sorensen > No LPAR or VM, running just "bare metal". I had AIX installed previously and it recognized 16Gb. uname -a Linux new-host-4 3.16.0-4-powerpc64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) ppc64 GNU/Linux lscpu Architecture: ppc64 CPU op-mode(s):32-bit, 64-bit Byte Order:Big Endian CPU(s):4 On-line CPU(s) list: 0-3 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 2 NUMA node(s): 1 Model: IBM,8203-E4A Hypervisor vendor: pHyp Virtualization type: para L1d cache: 64K L1i cache: 64K NUMA node0 CPU(s): 0-3 Seems like a config issue? Wouldn't a 32 bit kernel see the 32 bit limit, under 4Gb?
Re: POWER6 not seeing memory above 2Gb
On Thu, Mar 23, 2017 at 10:14:27AM -0400, Adam Stouffer wrote: > No LPAR or VM, running just "bare metal". I had AIX installed previously > and it recognized 16Gb. > > uname -a > Linux new-host-4 3.16.0-4-powerpc64 #1 SMP Debian 3.16.39-1+deb8u2 > (2017-03-07) ppc64 GNU/Linux > > lscpu > Architecture: ppc64 > CPU op-mode(s):32-bit, 64-bit > Byte Order:Big Endian > CPU(s):4 > On-line CPU(s) list: 0-3 > Thread(s) per core:2 > Core(s) per socket:1 > Socket(s): 2 > NUMA node(s): 1 > Model: IBM,8203-E4A > Hypervisor vendor: pHyp > Virtualization type: para > L1d cache: 64K > L1i cache: 64K > NUMA node0 CPU(s): 0-3 > > Seems like a config issue? Wouldn't a 32 bit kernel see the 32 bit limit, > under 4Gb? That ought to be working. I know the p520 I worked with before it worked fine. Which bootloader are you using? I use grub2, just in case the bootloader has anything to do with memory detection in linux. -- Len Sorensen
Re: problems with wheezy and xbmc
On Thu, Mar 23, 2017 at 02:57:02PM +0100, Richard Kuenz wrote: > Hello , > > i have installed Debian Wheezy on my Powermac G5 Quad. > > > please help me to solve one problem i have with graphics. whether i use xbmc > or kodi or mpv for videoplayback, it always comes with rasterised graphics; > no problem with vlc or mplayer or videoplayback directly on youtube. > > > this is some output > > > rich@debian:~$ glxinfo | grep -i renderer > OpenGL renderer string: Gallium 0.4 on NV47 > > > rich@debian:~$ vblank_mode=0 glxgears > ATTENTION: default value of option vblank_mode overridden by environment. > ATTENTION: default value of option vblank_mode overridden by environment. > 1946 frames in 5.3 seconds = 364.961 FPS > 1946 frames in 5.0 seconds = 388.572 FPS > > > > > but > > > rich@debian:~$ xbmc > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > > what is wrong with my graphics? > the card should be capable it it is 7800gtx 256mb. Do you have the file it is mentioning? It should be in mesa-va-drivers or vdpau-va-driver package. -- Len Sorensen
Re: POWER6 not seeing memory above 2Gb
On Thu, Mar 23, 2017 at 10:21 AM, Lennart Sorensen wrote > > > > That ought to be working. I know the p520 I worked with before it > worked fine. > > Which bootloader are you using? I use grub2, just in case the bootloader > has anything to do with memory detection in linux. > > -- > Len Sorensen Ah, that might be the case. Yaboot seemed to have some install issues anyhow. What would be the best way to switch from yaboot to grub2?
Re: problems with wheezy and xbmc
Thank you very much, i would have installed now vdpau-va-driver and output changes rich@debian:~$ xbmc libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 but the problem rasterized graphics remains. someone in the kodi forum already told me about mesa something, but your mentioned driver-package seem awailable only from jessie-backports onto sid. what to do then? and , if install this mesa thing, would this break something in graphics, because outside of xbmc and mpv it looks really good with this graphics. regards, rihard On 23.03.2017 15:24, Lennart Sorensen wrote: On Thu, Mar 23, 2017 at 02:57:02PM +0100, Richard Kuenz wrote: Hello , i have installed Debian Wheezy on my Powermac G5 Quad. please help me to solve one problem i have with graphics. whether i use xbmc or kodi or mpv for videoplayback, it always comes with rasterised graphics; no problem with vlc or mplayer or videoplayback directly on youtube. this is some output rich@debian:~$ glxinfo | grep -i renderer OpenGL renderer string: Gallium 0.4 on NV47 rich@debian:~$ vblank_mode=0 glxgears ATTENTION: default value of option vblank_mode overridden by environment. ATTENTION: default value of option vblank_mode overridden by environment. 1946 frames in 5.3 seconds = 364.961 FPS 1946 frames in 5.0 seconds = 388.572 FPS but rich@debian:~$ xbmc libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 what is wrong with my graphics? the card should be capable it it is 7800gtx 256mb. Do you have the file it is mentioning? It should be in mesa-va-drivers or vdpau-va-driver package.
Re: problems with wheezy and xbmc
On Thu, Mar 23, 2017 at 04:48:27PM +0100, Richard Kuenz wrote: > Thank you very much, > > i would have installed now > > > vdpau-va-driver > > > > and output changes > > rich@debian:~$ xbmc > libva: VA-API version 0.32.0 > libva: va_getDriverName() returns 0 > libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so > libva: va_openDriver() returns -1 > > > > > > but the problem rasterized graphics remains. > > > someone in the kodi forum already told me about mesa something, but your > mentioned driver-package seem awailable only from jessie-backports onto sid. > what to do then? > and , if install this mesa thing, would this break something in graphics, > because outside of xbmc and mpv it looks really good with this graphics. No idea. Any good reason for not running Jessie? I see that vdpau-va-driver in wheezy does NOT include nouveau_drv_video.soA Starting in jessie it exists in the package. -- Len Sorensen
Re: problems with wheezy and xbmc
Thanks, well, i basically never had problems with wheezy, besides minor issues. also on powerpc wheezy was stable ; with jessie a whole different story, so i try to stick with what works well for my hardware ... but i see cannot remain indefinitely on older software. did already upgrade but then i did no more have graphical accelleration on jessie with nouveau(don't know why though) and had to install custom kernel to boot into GUI. - plus if i had gnome installed, i had to install kde first, then remove gnome, just to enter gui. otherwise it would say "oh no, something happened.." and i am no lemming. + if i would install on powermac jessie directly from dvd, for some reason i was not able to install firefox extensions, which is really odd. this debian is just a wonderful experience hope to find a workaround for wheez On 23.03.2017 17:05, Lennart Sorensen wrote: On Thu, Mar 23, 2017 at 04:48:27PM +0100, Richard Kuenz wrote: Thank you very much, i would have installed now vdpau-va-driver and output changes rich@debian:~$ xbmc libva: VA-API version 0.32.0 libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/powerpc-linux-gnu/dri/nouveau_drv_video.so libva: va_openDriver() returns -1 but the problem rasterized graphics remains. someone in the kodi forum already told me about mesa something, but your mentioned driver-package seem awailable only from jessie-backports onto sid. what to do then? and , if install this mesa thing, would this break something in graphics, because outside of xbmc and mpv it looks really good with this graphics. No idea. Any good reason for not running Jessie? I see that vdpau-va-driver in wheezy does NOT include nouveau_drv_video.soA Starting in jessie it exists in the package.
Re: POWER6 not seeing memory above 2Gb
On Thu, Mar 23, 2017 at 11:45:10AM -0400, Adam Stouffer wrote: > On Thu, Mar 23, 2017 at 10:21 AM, Lennart Sorensen > wrote > > > > > > > > That ought to be working. I know the p520 I worked with before it > > worked fine. > > > > Which bootloader are you using? I use grub2, just in case the bootloader > > has anything to do with memory detection in linux. > > > > -- > > Len Sorensen > > > Ah, that might be the case. Yaboot seemed to have some install issues > anyhow. What would be the best way to switch from yaboot to grub2? Good question. I installed the machine with grub2 originally years ago, so I didn't have to try (I wanted MD raid1 which yaboot couldn't handle at that time, so I wanted grub2 to work, no matter what it took). Took some work at the time, debugging disk issues and other issues in grub2, but eventually grub2 got to the point of working on the p520 properly. These days it ought to just work. I remember needing a Prep boot partition, which grub-install was then pointed at. I can't remember if yaboot does it the same way. It might be as simple as installing the grub-ieee1275 package and running grub-install /dev/sda1 (assuming sda1 is the PReP boot partition). -- Len Sorensen
Re: POWER6 not seeing memory above 2Gb
> Good question. I installed the machine with grub2 originally years ago, > so I didn't have to try (I wanted MD raid1 which yaboot couldn't handle > at that time, so I wanted grub2 to work, no matter what it took). Took > some work at the time, debugging disk issues and other issues in grub2, > but eventually grub2 got to the point of working on the p520 properly. > These days it ought to just work. > > I remember needing a Prep boot partition, which grub-install was then > pointed at. I can't remember if yaboot does it the same way. > > It might be as simple as installing the grub-ieee1275 package and running > grub-install /dev/sda1 (assuming sda1 is the PReP boot partition). > > -- > Len Sorensen So I have grub2 booting the same kernel but again the same result. Only 2Gb available.
Re: POWER6 not seeing memory above 2Gb
On Thu, Mar 23, 2017 at 03:22:46PM -0400, Adam Stouffer wrote: > So I have grub2 booting the same kernel but again the same result. > Only 2Gb available. What was on this machine before? Is it possible that you are in fact running inside an existing LPAR config, which might have limited memory assigned? -- Len Sorensen
Re: POWER6 not seeing memory above 2Gb
On Thu, Mar 23, 2017 at 3:29 PM, Lennart Sorensen wrote: > What was on this machine before? Is it possible that you are in fact > running inside an existing LPAR config, which might have limited memory > assigned? > > -- > Len Sorensen Len, you were right about it being an LPAR. Previously I was running PowerVM but removed the drive. I had no idea it configured the hardware itself. Good thing you can run the special HMC Linux distro within VMWare :) Here is the screenshot and cause of my woes http://i.imgur.com/4Jlc1zq.png Thanks again for your patience. Adam
