subject:"Wheezy"


maybe this is of help?


https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/570228



On 03.04.2017 19:11, Mathieu Malaterre wrote:

On Mon, Apr 3, 2017 at 7:07 PM, Richard Kuenz  wrote:

"script.log"

see attachment please


uh ?

You really need to see this in your terminal:

$ /usr/share/bug/xorg/script 3>/tmp/script.log

Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?

also the system recognizes 2 monitors although i have only one attached 
- a samsung 19inch 5:4

that is being scaled down to a 4:3 due to "mirroring" the two displays.

On 03.04.2017 18:17, John Paul Adrian Glaubitz wrote:

On 04/03/2017 06:16 PM, Mathieu Malaterre wrote:

Technically for a full bug report we would want:

/usr/share/bug/xorg/script 3>/tmp/script.log


Oh, yeah, completely forgot about that one ;-). Even better!

Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?

2017-04-03 Thread Mathieu Malaterre

On Mon, Apr 3, 2017 at 7:07 PM, Richard Kuenz  wrote:
> "script.log"
>
> see attachment please

uh ?

You really need to see this in your terminal:

$ /usr/share/bug/xorg/script 3>/tmp/script.log

Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?


"script.log"

see attachment please

thanks

On 03.04.2017 18:17, John Paul Adrian Glaubitz wrote:

On 04/03/2017 06:16 PM, Mathieu Malaterre wrote:

Technically for a full bug report we would want:

/usr/share/bug/xorg/script 3>/tmp/script.log


Oh, yeah, completely forgot about that one ;-). Even better!

#!/bin/sh

PATH="/sbin:$PATH"
CONFIG_DIR=/etc/X11
SERVER_BINARY=/usr/bin/Xorg
SERVER_SYMLINK="$CONFIG_DIR/X"
XORGCONFIG="$CONFIG_DIR/xorg.conf"
XORGCONFIG_DIR="$CONFIG_DIR/xorg.conf.d"
CONFIG_AUX_DIR=/var/lib/x11
X11R6_LIBS=/usr/X11R6/lib
LOCAL_LIBS=/usr/local/lib

# Pretty echo, underline the specified string:
pecho() {
echo "$@"
echo "$@"|sed 's/./-/g'
}

exec >&3

if [ -e "$SERVER_SYMLINK" ]; then
pecho "X server symlink status:"
ls -dl "$SERVER_SYMLINK"
ls -dl "$(readlink "$SERVER_SYMLINK")"
else
echo "$SERVER_SYMLINK does not exist."
fi

if ! [ -L "$SERVER_SYMLINK" ]; then
echo "$SERVER_SYMLINK is not a symlink."
fi

if ! [ -x "$SERVER_SYMLINK" ]; then
echo "$SERVER_SYMLINK is not executable."
fi

echo

if ldd "$SERVER_BINARY" | grep -qs "$LOCAL_LIBS"; then
   pecho "The server is using local libraries!"
   ldd "$SERVER_BINARY" | grep "$LOCAL_LIBS"
   echo
fi

if ldd "$SERVER_BINARY" | grep -qs "$X11R6_LIBS"; then
   pecho "The server is using obsolete libraries!"
   ldd "$SERVER_BINARY" | grep "$X11R6_LIBS"
   echo
fi

if dpkg-divert --list | grep -qs -i libgl; then
pecho "Diversions concerning libGL are in place"
dpkg-divert --list | grep -i libgl
echo
fi

if which lspci > /dev/null 2>&1; then
pecho "VGA-compatible devices on PCI bus:"
LC_ALL=C lspci -nn | grep 'VGA compatible controller'
else
echo "The lspci command was not found; not including PCI data."
fi

echo

if [ -e "$XORGCONFIG" ]; then
pecho "Xorg X server configuration file status:"
ls -dl "$XORGCONFIG"
echo
pecho "Contents of $XORGCONFIG:"
iconv -c -t ascii "$XORGCONFIG"
else
echo "$XORGCONFIG does not exist."
fi

echo

if [ -d "$XORGCONFIG_DIR" ]; then
pecho "Contents of $XORGCONFIG_DIR:"
ls -l "$XORGCONFIG_DIR"
else
echo "$XORGCONFIG_DIR does not exist."
fi

echo

KMS_CONFS_DIR=/etc/modprobe.d
KMS_CONFS=$(ls $KMS_CONFS_DIR/*-kms.conf 2>/dev/null)

if [ -n "$KMS_CONFS" ]; then
pecho "KMS configuration files:"
for CONF in $KMS_CONFS; do
  echo "$CONF:"
  # Indent, and get rid of empty lines:
  sed 's/^/  /' < "$CONF"|egrep -v '^\s*$'
done
else
echo "$KMS_CONFS_DIR contains no KMS configuration files."
fi

echo

KERNEL_VERSION=/proc/version

if [ -e "$KERNEL_VERSION" ]; then
pecho "Kernel version ($KERNEL_VERSION):"
cat /proc/version
else
echo "No kernel version found (missing $KERNEL_VERSION)."
fi

echo

XORG_LOGS=$(ls -dt /var/log/Xorg.*.log 2>/dev/null)

if [ -n "$XORG_LOGS" ]; then
pecho "Xorg X server log files on system:"
ls -dlrt /var/log/Xorg.*.log 2>/dev/null
echo
for LOG in $XORG_LOGS; do
if [ -f "$LOG" ]; then
pecho "Contents of most recent Xorg X server log file ($LOG):"
cat "$LOG"
# the log files are large; only show the most recent
break
fi
done
else
echo "No Xorg X server log files found."
fi

echo

if [ -x /sbin/udevadm ]; then
pecho "udev information:"
/sbin/udevadm info --export-db | awk -F '\n' -v RS='\n\n' '/E: ID_INPUT/ { print; print "" }'
echo
fi

if [ -x /bin/dmesg ]; then
pecho "DRM Information from dmesg:"
dmesg | egrep -i 'drm|agp'
echo
fi

# vim:set ai et sts=4 sw=4 tw=0:

Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?


when i play my favorite youtube player with mpv i get


libEGL warning: DRI2: failed to authenticate





On 03.04.2017 18:17, John Paul Adrian Glaubitz wrote:

On 04/03/2017 06:16 PM, Mathieu Malaterre wrote:

Technically for a full bug report we would want:

/usr/share/bug/xorg/script 3>/tmp/script.log


Oh, yeah, completely forgot about that one ;-). Even better!

Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?


"dmesg" fright after boot


sorry but i could not go up enough in terminal to catch first phrases


[  106.379882] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.386336] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.389599] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.393050] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.398380] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.404125] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.411236] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.414331] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.417940] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.423619] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.429620] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.434866] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.437580] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.440365] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.445106] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.450342] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.455345] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.458055] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.460839] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.465588] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.471068] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.477432] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.480240] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.483837] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.489203] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.494950] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.502204] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.505221] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.508946] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.514897] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.521056] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.526583] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.529211] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.532120] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.537101] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.542697] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.547951] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.550586] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.553469] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.558428] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.563851] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.570226] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.573206] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.576574] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.582085] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.587822] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.596256] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.599211] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.602835] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.608569] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.614725] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.619957] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.622583] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.625451] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.630321] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.635825] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.641086] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.643692] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.646561] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.651182] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.656693] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.663210] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.666211] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.669467] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.674717] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[  106.680444] snd_firewire_speakers fw2.0: iPCR0: plug is already in use
[

Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?


Hello ,

thank you very much for considering this


"glxinfo"

rich@debian:~$ glxinfo
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, 
GLX_OML_swap_method,

GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_MESA_copy_sub_buffer, GLX_INTEL_swap_event
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile,
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_framebuffer_sRGB,
GLX_EXT_create_context_es2_profile, GLX_MESA_copy_sub_buffer,
GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control,
GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read,
GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample,
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group,
GLX_EXT_texture_from_pixmap, GLX_INTEL_swap_event
GLX version: 1.4
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_MESA_multithread_makecurrent, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
GLX_SGIX_pbuffer, GLX_EXT_texture_from_pixmap
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 8.0.5
OpenGL shading language version string: 1.20
OpenGL extensions:
GL_ARB_multisample, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_copy_texture,
GL_EXT_polygon_offset, GL_EXT_subtexture, GL_EXT_texture_object,
GL_EXT_vertex_array, GL_EXT_compiled_vertex_array, GL_EXT_texture,
GL_EXT_texture3D, GL_IBM_rasterpos_clip, GL_ARB_point_parameters,
GL_EXT_draw_range_elements, GL_EXT_packed_pixels, 
GL_EXT_point_parameters,

GL_EXT_rescale_normal, GL_EXT_separate_specular_color,
GL_EXT_texture_edge_clamp, GL_SGIS_generate_mipmap,
GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp,
GL_SGIS_texture_lod, GL_ARB_multitexture, 
GL_IBM_multimode_draw_arrays,

GL_IBM_texture_mirrored_repeat, GL_3DFX_texture_compression_FXT1,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add, 
GL_ARB_transpose_matrix,
GL_EXT_blend_func_separate, GL_EXT_fog_coord, 
GL_EXT_multi_draw_arrays,

GL_EXT_secondary_color, GL_EXT_texture_env_add,
GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias,
GL_INGR_blend_func_separate, GL_MESA_resize_buffers, 
GL_NV_blend_square,

GL_NV_light_max_exponent, GL_NV_texgen_reflection,
GL_NV_texture_env_combine4, GL_SUN_multi_draw_arrays,
GL_ARB_texture_border_clamp, GL_ARB_texture_compression,
GL_EXT_framebuffer_object, GL_EXT_texture_env_combine,
GL_EXT_texture_env_dot3, GL_MESA_window_pos, 
GL_NV_packed_depth_stencil,

GL_NV_texture_rectangle, GL_NV_vertex_program, GL_ARB_depth_texture,
GL_ARB_occlusion_query, GL_ARB_shadow, GL_ARB_shadow_ambient,
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar,
GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat,
GL_ARB_window_pos, GL_ATI_envmap_bumpmap, GL_ATI_fragment_shader,
GL_EXT_stencil_two_side, GL_EXT_texture_cube_map, GL_NV_depth_clamp,
GL_NV_fragment_program, GL_NV_point_sprite, GL_NV_vertex_program1_1,
GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, 
GL_ARB_draw_buffers,
GL_ARB_fragment_program, GL_ARB_fragment_shader, 
GL_ARB_shader_objects,

GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ATI_draw_buffers,
GL_ATI_texture_env_combine3, GL_EXT_depth_bounds_test,
GL_EXT_shadow_funcs, GL_EXT_stencil_wrap, GL_MESA_pack_invert,
GL_MESA_ycbcr_texture, GL_ARB_depth_clamp, 
GL_ARB_fragment_program_shadow,

GL_ARB_half_float_pixel, GL_ARB_occlusion_query2, GL_ARB_point_sprite,
GL_ARB_shading_language_100, GL_ARB_sync, 
GL_ARB_texture_non_power_of_two,

GL_ARB_vertex_buffer_object, GL_ATI_blend_equation_separate,
GL_EXT_blend_equation_separate, GL_OES_read_format,
GL_ARB_pixel_buffer_object, GL_ARB_texture_compression_rgtc,
GL_ARB_texture_rectangle, GL_ATI_texture_compression_3dc,
GL_EXT_pixel_buffer_object, GL_EXT_texture_compression_rgtc,
GL_EXT_texture_mirror_clamp, GL_EXT_texture_rectangle,
GL_EXT_texture_sRGB, GL_EXT_texture_shared_exponent,
GL_ARB_framebuffer_object, GL_EXT_framebuffer_blit,
GL_EXT_framebuffer_multisample, GL_EXT_packed_depth_stencil,
GL_NV_fragment_program_option, GL_APPLE_object_purgeable,
GL_ARB_vertex_array_object, GL_ATI_separate_stencil,
GL_ATI_texture_mirror_once, GL_EXT_draw_buffers2, 
GL_EXT_draw_instanced,

Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?

2017-04-03 Thread John Paul Adrian Glaubitz

On 04/03/2017 06:16 PM, Mathieu Malaterre wrote:
> Technically for a full bug report we would want:
> 
> /usr/share/bug/xorg/script 3>/tmp/script.log

Oh, yeah, completely forgot about that one ;-). Even better!

-- 
 .''`.  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: Radeon Graphics Acceleration for Debian wheezy / Hwoto?

2017-04-03 Thread Mathieu Malaterre

Richard,

On Mon, Apr 3, 2017 at 6:09 PM, John Paul Adrian Glaubitz
<glaub...@physik.fu-berlin.de> wrote:
> Hello Richard!
>
> On 04/03/2017 05:07 PM, Richard Kuenz wrote:
>> Got a very nice Powermac 7,3 Dual CPU with a Radeon 9650 Graphics Card. The 
>> System runs smooth and silent;
>>
>> Would like to use Debian Wheezy on this Computer.
>>
>> I installed it and it runs very fine, but i get no graphics acell.
>
> Could you please provide your /var/log/Xorg.0.log file as well as the
> output from the commands "glxinfo" and "dpkg -l libgl\*". Plus, the
> output of "dmesg" right after the machine has booted.
>
> It should be possible to install a newer kernel from wheezy-backports
> as well as updated MESA and X.Org drivers from there (if available).

Technically for a full bug report we would want:

/usr/share/bug/xorg/script 3>/tmp/script.log

Thanks for your time

Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?

2017-04-03 Thread John Paul Adrian Glaubitz

Hello Richard!

On 04/03/2017 05:07 PM, Richard Kuenz wrote:
> Got a very nice Powermac 7,3 Dual CPU with a Radeon 9650 Graphics Card. The 
> System runs smooth and silent;
> 
> Would like to use Debian Wheezy on this Computer.
> 
> I installed it and it runs very fine, but i get no graphics acell.

Could you please provide your /var/log/Xorg.0.log file as well as the
output from the commands "glxinfo" and "dpkg -l libgl\*". Plus, the
output of "dmesg" right after the machine has booted.

It should be possible to install a newer kernel from wheezy-backports
as well as updated MESA and X.Org drivers from there (if available).

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

Re: Radeon Graphics Acceleration for Debian wheezy / Hwoto?

Please consider this post obsolete


i will live without 3d acceleration on this computer for now



thank you for consideration


and sorry for disturbing


richie



> On 03 Apr 2017, at 17:07, Richard Kuenz <richard.ku...@web.de> wrote:
> 
> Hello ,
> 
> i would kindly need your help.
> 
> Got a very nice Powermac 7,3 Dual CPU with a Radeon 9650 Graphics Card. The 
> System runs smooth and silent;
> 
> 
> Would like to use Debian Wheezy on this Computer.
> 
> I installed it and it runs very fine, but i get no graphics acell.
> 
> 
> 
> Could someone here please show me a way on how to achieve this, without need 
> of upgrading to Jessie et. al.
> — i tried already to install firmware-linux-nonfree and then the famous 
> mate.debs for mesa , but this broke the system.
> 
> 
> Thank you very much,
> 
> Wish you a great day,
> 
> Richard

Radeon Graphics Acceleration for Debian wheezy / Hwoto?

Hello ,

i would kindly need your help.

Got a very nice Powermac 7,3 Dual CPU with a Radeon 9650 Graphics Card. The 
System runs smooth and silent;


Would like to use Debian Wheezy on this Computer.

I installed it and it runs very fine, but i get no graphics acell.



Could someone here please show me a way on how to achieve this, without need of 
upgrading to Jessie et. al.
 — i tried already to install firmware-linux-nonfree and then the famous 
mate.debs for mesa , but this broke the system.


Thank you very much,

Wish you a great day,

Richard

Re: problems with wheezy and xbmc

2017-03-23 Thread Richard Kuenz


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: problems with wheezy and xbmc

2017-03-23 Thread Lennart Sorensen

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

2017-03-23 Thread Richard Kuenz


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

2017-03-23 Thread Lennart Sorensen

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

problems with wheezy and xbmc

2017-03-23 Thread Richard Kuenz




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: Wheezy

2016-03-29 Thread kaleb white

I found the rescue install option in an Ubuntu install.Debian and Ubuntu are 
basically identical except for the GUI. I use the install-free option (or 
something like that).


Sent from MSN



From: Brock Wittrock <brockwittr...@gmail.com>
Sent: March 29, 2016 11:00 AM
To: Steven Grunza; debian-powerpc@lists.debian.org
Subject: Re: Wheezy

When you boot from the Jessie install CD, hit tab at the yaboot prompt.  Should 
be a rescue option listed among others.  So simply type rescue and hit Enter.  
Once booted into rescue mode, it'll feel like you are working through a normal 
install until you get to the step where you'll be asked what drive/partition 
you want to mount to make changes on.  Your choice will vary depending on how 
you partitioned the drive during the install, but you'll want to mount the 
partition containing the root filesystem.  If you aren't sure, you can always 
just start going through the list and selecting each one until it finds a valid 
root fs.

Once you have properly updated your /etc/yaboot.conf file and ran ybin (-v if 
you want output of the results) to apply the changes go ahead and exit rescue 
mode and reboot your system hopefully to a working login screen.  I know, these 
steps were quite vague, but I don't have a system in front of me to provide 
more details from at the moment, but hopefully it at least puts you in the 
right direction.

Also, you don't necessarily have to update your initrd symlink to point to your 
new initrd.  Just provide the full name of the new initrd in your yaboot file.

PPC systems can be a bit of pain to get up and running, but I personally enjoy 
that aspect of using them as it's good way to get an even stronger handle on 
how computers work and how things work specifically on Linux.

Brock

On Tue, Mar 29, 2016 at 8:56 AM, Steven Grunza 
<steven.gru...@gmail.com<mailto:steven.gru...@gmail.com>> wrote:
The install of jessie went ok.  I haven't downloaded Wheezy yet.  And yes, the 
crash happened while updating /etc/yaboot.conf; I had just started typing "ln 
-s " when nouveau took a serious dislike to something.

My guess is that there is some way to boot the jessie CD in a rescue mode, 
mount /boot, and fix the problem.  I just haven't figured out how yet.

I've been using various *nix since '95 when I started using Slackware loaded 
from 3.5" floppies.  I'm most comfortable in Fedora (my TabletPC convertible 
runs Fedora 22) but I've had a few professional projects come around for 
quoting that required Ubuntu or Debian so I'm trying to expand my knowledge 
base a little.  Of course using an old PowerPC G5 might not be the best way of 
doing it (especially with the nVidia video card) but it's what I've got...





On Mon, Mar 28, 2016 at 9:36 PM, Brock Wittrock 
<brockwittr...@gmail.com<mailto:brockwittr...@gmail.com>> wrote:
So the initial install of Wheezy went okay? Do you mean the crash happened 
while updating your /etc/yaboot.conf file with the new initrd info?  Can you 
boot into rescue mode off of the installer and mount your /boot and update 
things accordingly?

If you'd like, we can try and work through the Jessie install again as well.  I 
was hoping to reply sooner but am just getting to it now.


Brock

On Mon, Mar 28, 2016 at 7:39 PM, Steven Grunza 
<steven.gru...@gmail.com<mailto:steven.gru...@gmail.com>> wrote:
Killed the machine.  :(

While trying to change the symlinks in /boot to point to the new initrd the 
nouveau driver crashed the OS causing a panic and reboot.

Since the initrd file is not defined in /boot the machine is no longer bootable.

I've installed debian and ubuntu about five or six times each, trying different 
flavors, etc.  None work.

I'm starting to understand while the machine was given away for free

On Sat, Mar 26, 2016 at 2:49 AM, Risto Suominen 
<risto.suomi...@gmail.com<mailto:risto.suomi...@gmail.com>> wrote:
I don't know the answer, but I doubt it would help because the problem
(those 64k pages) has been there for quite long.

What went wrong with the 4.4.0-rc7-powerpc64 kernel?

Risto

Re: Wheezy

2016-03-29 Thread Brock Wittrock

When you boot from the Jessie install CD, hit tab at the yaboot prompt.
Should be a rescue option listed among others.  So simply type rescue and
hit Enter.  Once booted into rescue mode, it'll feel like you are working
through a normal install until you get to the step where you'll be asked
what drive/partition you want to mount to make changes on.  Your choice
will vary depending on how you partitioned the drive during the install,
but you'll want to mount the partition containing the root filesystem.  If
you aren't sure, you can always just start going through the list and
selecting each one until it finds a valid root fs.

Once you have properly updated your /etc/yaboot.conf file and ran ybin (-v
if you want output of the results) to apply the changes go ahead and exit
rescue mode and reboot your system hopefully to a working login screen.  I
know, these steps were quite vague, but I don't have a system in front of
me to provide more details from at the moment, but hopefully it at least
puts you in the right direction.

Also, you don't necessarily have to update your initrd symlink to point to
your new initrd.  Just provide the full name of the new initrd in your
yaboot file.

PPC systems can be a bit of pain to get up and running, but I personally
enjoy that aspect of using them as it's good way to get an even stronger
handle on how computers work and how things work specifically on Linux.

Brock

On Tue, Mar 29, 2016 at 8:56 AM, Steven Grunza <steven.gru...@gmail.com>
wrote:

> The install of jessie went ok.  I haven't downloaded Wheezy yet.  And yes,
> the crash happened while updating /etc/yaboot.conf; I had just started
> typing "ln -s " when nouveau took a serious dislike to something.
>
> My guess is that there is some way to boot the jessie CD in a rescue mode,
> mount /boot, and fix the problem.  I just haven't figured out how yet.
>
> I've been using various *nix since '95 when I started using Slackware
> loaded from 3.5" floppies.  I'm most comfortable in Fedora (my TabletPC
> convertible runs Fedora 22) but I've had a few professional projects come
> around for quoting that required Ubuntu or Debian so I'm trying to expand
> my knowledge base a little.  Of course using an old PowerPC G5 might not be
> the best way of doing it (especially with the nVidia video card) but it's
> what I've got...
>
>
>
>
>
> On Mon, Mar 28, 2016 at 9:36 PM, Brock Wittrock <brockwittr...@gmail.com>
> wrote:
>
>> So the initial install of Wheezy went okay? Do you mean the crash
>> happened while updating your /etc/yaboot.conf file with the new initrd
>> info?  Can you boot into rescue mode off of the installer and mount your
>> /boot and update things accordingly?
>>
>> If you'd like, we can try and work through the Jessie install again as
>> well.  I was hoping to reply sooner but am just getting to it now.
>>
>>
>> Brock
>>
>> On Mon, Mar 28, 2016 at 7:39 PM, Steven Grunza <steven.gru...@gmail.com>
>> wrote:
>>
>>> Killed the machine.  :(
>>>
>>> While trying to change the symlinks in /boot to point to the new initrd
>>> the nouveau driver crashed the OS causing a panic and reboot.
>>>
>>> Since the initrd file is not defined in /boot the machine is no longer
>>> bootable.
>>>
>>> I've installed debian and ubuntu about five or six times each, trying
>>> different flavors, etc.  None work.
>>>
>>> I'm starting to understand while the machine was given away for free
>>>
>>> On Sat, Mar 26, 2016 at 2:49 AM, Risto Suominen <
>>> risto.suomi...@gmail.com> wrote:
>>>
>>>> I don't know the answer, but I doubt it would help because the problem
>>>> (those 64k pages) has been there for quite long.
>>>>
>>>> What went wrong with the 4.4.0-rc7-powerpc64 kernel?
>>>>
>>>> Risto
>>>>
>>>
>>>
>>
>

RE: Wheezy

2016-03-29 Thread luigi burdo

Wheezy for my experience is the only one distro who worked without problems on 
Quad G5 with nvidia boardthe only tip i can say put the linux as the first hd 
slot a on G5 Quad for the remaining all was working on an 7800gtx flashed too. 
on nvidia 6600 al was good.radeon was gave problems but you need to boot the 
system with kernel appends... like is radeon.agpmode=-1 or radeon.modeset=1 or 
video=radeonfb:on
What im facing today is with all distros and all flawors is the bug of xorg 
with dual gfx boards from jessie to sid and all ubuntu flawors ... this was my 
last post on ubuntu forums about 
this bug effected all the PPC world i think because it is in the X5000 too.What 
i discovered :if i set radeon.modeset=0 nouveau.modeset=1xorg turn on the 
radeon driver and turn off the nouveau but because the radeon driver is off 
by the kernel the result is the black screen.same is if i set radeon.modeset=1 
nouveau.modeset=0setting the two boards as 1  i have te fbdev working on 
radeon (?) but xorg dont find  video boards.if i set the two as 0 nothing 
woking but xorg --configure set the new xorg with the two video boards This 
bug was present since 15.0 of (X) (L) (mate)ubuntu ... and now one had been 
fixed it ...


CiaoLuigi
Date: Mon, 28 Mar 2016 20:36:27 -0500
Subject: Re: Wheezy
From: brockwittr...@gmail.com
To: steven.gru...@gmail.com
CC: risto.suomi...@gmail.com; debian-powerpc@lists.debian.org

So the initial install of Wheezy went okay? Do you mean the crash happened 
while updating your /etc/yaboot.conf file with the new initrd info?  Can you 
boot into rescue mode off of the installer and mount your /boot and update 
things accordingly?
If you'd like, we can try and work through the Jessie install again as well.  I 
was hoping to reply sooner but am just getting to it now. 

Brock
On Mon, Mar 28, 2016 at 7:39 PM, Steven Grunza <steven.gru...@gmail.com> wrote:
Killed the machine.  :(
While trying to change the symlinks in /boot to point to the new initrd the 
nouveau driver crashed the OS causing a panic and reboot.
Since the initrd file is not defined in /boot the machine is no longer bootable.
I've installed debian and ubuntu about five or six times each, trying different 
flavors, etc.  None work.
I'm starting to understand while the machine was given away for free
On Sat, Mar 26, 2016 at 2:49 AM, Risto Suominen <risto.suomi...@gmail.com> 
wrote:
I don't know the answer, but I doubt it would help because the problem

(those 64k pages) has been there for quite long.



What went wrong with the 4.4.0-rc7-powerpc64 kernel?



Risto

Re: Wheezy

2016-03-28 Thread Brock Wittrock

So the initial install of Wheezy went okay? Do you mean the crash happened
while updating your /etc/yaboot.conf file with the new initrd info?  Can
you boot into rescue mode off of the installer and mount your /boot and
update things accordingly?

If you'd like, we can try and work through the Jessie install again as
well.  I was hoping to reply sooner but am just getting to it now.

Brock

On Mon, Mar 28, 2016 at 7:39 PM, Steven Grunza <steven.gru...@gmail.com>
wrote:

> Killed the machine.  :(
>
> While trying to change the symlinks in /boot to point to the new initrd
> the nouveau driver crashed the OS causing a panic and reboot.
>
> Since the initrd file is not defined in /boot the machine is no longer
> bootable.
>
> I've installed debian and ubuntu about five or six times each, trying
> different flavors, etc.  None work.
>
> I'm starting to understand while the machine was given away for free
>
> On Sat, Mar 26, 2016 at 2:49 AM, Risto Suominen <risto.suomi...@gmail.com>
> wrote:
>
>> I don't know the answer, but I doubt it would help because the problem
>> (those 64k pages) has been there for quite long.
>>
>> What went wrong with the 4.4.0-rc7-powerpc64 kernel?
>>
>> Risto
>>
>
>

Re: Wheezy

2016-03-28 Thread Steven Grunza

Killed the machine.  :(

While trying to change the symlinks in /boot to point to the new initrd the
nouveau driver crashed the OS causing a panic and reboot.

Since the initrd file is not defined in /boot the machine is no longer
bootable.

I've installed debian and ubuntu about five or six times each, trying
different flavors, etc.  None work.

I'm starting to understand while the machine was given away for free

On Sat, Mar 26, 2016 at 2:49 AM, Risto Suominen 
wrote:

> I don't know the answer, but I doubt it would help because the problem
> (those 64k pages) has been there for quite long.
>
> What went wrong with the 4.4.0-rc7-powerpc64 kernel?
>
> Risto
>

Re: Wheezy

2016-03-28 Thread kaleb white

Probably something BIG. I can't figure it out.
Sorry I couldn't help.

Sent from MSN

From: Risto Suominen <risto.suomi...@gmail.com>
Sent: March 25, 2016 11:49 PM
To: Steven Grunza
Cc: PowerPC List Debian
Subject: Re: Wheezy

I don't know the answer, but I doubt it would help because the problem
(those 64k pages) has been there for quite long.

What went wrong with the 4.4.0-rc7-powerpc64 kernel?

Risto

Re: Wheezy

2016-03-26 Thread Christophe De Natale

Le vendredi 25 mars 2016 à 18:22 -0400, Steven Grunza a écrit :
> Since jessie doesn't seem to work with my flavor of iMac G5, is there
> a place from which I can download a previous version?  I think it was
> called wheezy.

Hello Steven,

>From my side, Jessie installation works OOB on iMac G5 rev B & C / 17 &
20 with Mate & XFCE desktop.
Some adjustements are needed to have Airport, sound, iSight working
(firewire is not fixed, a workaround is needed on video performance but
it is very acceptable).
I was be able to boot on a cd & usb key (support created on my wife's
iMac), see here (in French, sorry) :
https://wiki.debian.org/InstallingDebianOn/Apple/iMac%20G5%
20iSight/Jessie


If you really want to install Wheezy, see here :
https://www.debian.org/releases/wheezy/debian-installer/

Regards,

Christophe

Re: Wheezy

2016-03-26 Thread Risto Suominen

I don't know the answer, but I doubt it would help because the problem
(those 64k pages) has been there for quite long.

What went wrong with the 4.4.0-rc7-powerpc64 kernel?

Risto

Wheezy

2016-03-25 Thread Steven Grunza

Since jessie doesn't seem to work with my flavor of iMac G5, is there a
place from which I can download a previous version?  I think it was called
wheezy.

See the list messages about "Debian on iMac G5" for details of my efforts
with 8.3.0

Re: ibook G3 suddenly fails to resume after suspend with Debian wheezy

2015-09-08 Thread Michel Dänzer

On 25.08.2015 10:00, Juergen Hench wrote:
> Dear Debian-for-PPC developers and users
> 
> I am using an old 2003 G3 ibook with debian wheezy (3.2.0-4-powerpc #1
> Debian 3.2.68-1+deb7u3 ppc GNU/Linux), initially installed as linux
> mint. It had all been working fine until yesterday when the
> resume-from-suspend stopped working. I have performed an upgrade to the
> current version of all installed packages. I have been using lxde and
> xfce4 on the system.
> 
> There was one "anomaly" when waking up from suspend since Debian had
> been installed. When closing the lid, the computer would go to suspend.
> When re-opening, it would wake up for a few seconds, then go back to
> suspend without user interaction. Pressing a keyboard key would then
> wake it up again, and it would function fine.
> 
> Now, since the upgrade (did not note the versions I had been using
> before) [...]

FWIW, you can see which packages were upgraded from which versions in
/var/log/aptitude* or /var/log/dpkg.log* .


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

ibook G3 suddenly fails to resume after suspend with Debian wheezy

2015-08-24 Thread Juergen Hench

Dear Debian-for-PPC developers and users

I am using an old 2003 G3 ibook with debian wheezy (3.2.0-4-powerpc #1
Debian 3.2.68-1+deb7u3 ppc GNU/Linux), initially installed as linux mint.
It had all been working fine until yesterday when the resume-from-suspend
stopped working. I have performed an upgrade to the current version of all
installed packages. I have been using lxde and xfce4 on the system.

There was one anomaly when waking up from suspend since Debian had been
installed. When closing the lid, the computer would go to suspend. When
re-opening, it would wake up for a few seconds, then go back to suspend
without user interaction. Pressing a keyboard key would then wake it up
again, and it would function fine.

Now, since the upgrade (did not note the versions I had been using before)
the system goes to suspend. When re-opening, it does power up the screen
backlight, and the caps lock key as well as num lock key LEDs work,
however, nothing else starts up, and there is no network connection either.
Thus, it is impossible to see what exactly fails. All the remains is to
turn off the power and to reboot.

I wonder if there has been any change to packages that could explain this
behavior. I have found several old posts about older Debian versions with
similar symptoms and have tried to exchange pbbuttonsd for pmud. It all
remains the same. No waking up from suspend anymore.

Does anyone have an ibook / powerbook G3 with the current Debian wheezy
running and suspend still works? Which packages are installed? I would be
grateful for a list. Are there any customizations needed? I do not recall
that I had to adapt any file after the installation for suspend/resume to
work. Unfortunately, now, when trying to find the problem, I have added and
removed quite some packages and the whole thing seems to boil down do the
kernel rather than the ppbuttonsd etc. level.

Has anyone else with an ibook / pb G3 experience the same problem recently?

Any idea is appreciated

Best

Juergen

Fwd: Re: ibook G3 suddenly fails to resume after suspend with Debian wheezy

2015-08-24 Thread Juergen Hench

Hi Roosevelt

Thank. You for your hint. My F2 key works as expected if pbbuttonsd is
installed. However, after waking up from suspend, the whole system seems
stuck. There is no reaction to anything, i.e. it is not a display problem.

From old posts I figured some previous updates (of which packages?) Have
led to ther same or simiulare failure. It would be great to get a starting
point to solve this issue.

Best

Juergen

On Aug 25, 2015 4:35 AM, Roosevelt Littleton knowledgeispowe...@gmail.com
wrote:

 I once had debian on my powerbook. When ever the screen was black. All I
had to do is press the apple key with the sun on it(F2). This worked for me.

 On Mon, Aug 24, 2015 at 9:00 PM, Juergen Hench jurgen.he...@gmail.com
wrote:

 Dear Debian-for-PPC developers and users

 I am using an old 2003 G3 ibook with debian wheezy (3.2.0-4-powerpc #1
Debian 3.2.68-1+deb7u3 ppc GNU/Linux), initially installed as linux mint.
It had all been working fine until yesterday when the resume-from-suspend
stopped working. I have performed an upgrade to the current version of all
installed packages. I have been using lxde and xfce4 on the system.

 There was one anomaly when waking up from suspend since Debian had
been installed. When closing the lid, the computer would go to suspend.
When re-opening, it would wake up for a few seconds, then go back to
suspend without user interaction. Pressing a keyboard key would then wake
it up again, and it would function fine.

 Now, since the upgrade (did not note the versions I had been using
before) the system goes to suspend. When re-opening, it does power up the
screen backlight, and the caps lock key as well as num lock key LEDs work,
however, nothing else starts up, and there is no network connection either.
Thus, it is impossible to see what exactly fails. All the remains is to
turn off the power and to reboot.

 I wonder if there has been any change to packages that could explain
this behavior. I have found several old posts about older Debian versions
with similar symptoms and have tried to exchange pbbuttonsd for pmud. It
all remains the same. No waking up from suspend anymore.

 Does anyone have an ibook / powerbook G3 with the current Debian wheezy
running and suspend still works? Which packages are installed? I would be
grateful for a list. Are there any customizations needed? I do not recall
that I had to adapt any file after the installation for suspend/resume to
work. Unfortunately, now, when trying to find the problem, I have added and
removed quite some packages and the whole thing seems to boil down do the
kernel rather than the ppbuttonsd etc. level.

 Has anyone else with an ibook / pb G3 experience the same problem
recently?

 Any idea is appreciated

 Best

 Juergen

KMS on Wheezy

2014-12-21 Thread Herminio Hernandez

I have changed from Jessie to Wheezy on my PowerBook G4. I want to get 3D 
acceleration but whenever I set radeon.agpmode=-1 I get a blank screen. I have 
my config file and log file. It looks like when I created my xorg.conf file it 
made a two monitor configuration but I do not have two monitors. Would that be 
related? Any help will be appreciated. Thanks!

Herminio

My_10-radeon.conf
Description: Binary data


My_xorg.conf
Description: Binary data


my_Xorg.0.log
Description: Binary data



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Wheezy install with dark screen after boot

2014-03-12 Thread Ala de Dragón

2014-03-03 17:53 GMT+01:00, Aaron Valdes aaron78val...@gmail.com:
I wonder if the problem with your card was related to Phantom Ports.

I just had a similar symptoms with Pro Mac G5 with GeForce FX 5200
Ultra.

We did manage to get this working.

On Jan 20, 2014, at 10:53 PM, Risto Suominen risto.suomi...@gmail.com
wrote:

Hi Kristen,

2014/1/21, Kristen R kris...@atmyhome.org:

Advice as to what I should do? Like, how does one drop to a shell so
I might
access the xorg.config file?

Adding '1' to yaboot command line should bring you to single user
mode.

Risto

Thank you Risto

I never did get a chance to actually try entering a 1 to the boot:
query. Instead I purchased a ATI Radeon 9800 Pro video card for Mac's.
When I tried to boot to Debian everything worked as expected.

No computer lockups at the login screen
No half screen of black and white for the login screen

So changing the video card solved my problem.

It would seem there is a problem with the hardware detection phase and
the build of the xorg.conf file

Kristen

I solved a similar problem changing the video conector from one dvi to
the other in the video card. I't seems that there is no monitor
detection under the instalation so the system didn't know in wich dvbi
you have conected the monitor.

Have a nice day
:)
--
El cielo es para los dragones
lo que el agua es para las ninfas

--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/ca+924hsjm4cqr7cqkft0xhm1du6ohkdp-xxca_c7c4d+hzx...@mail.gmail.com

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

2014-03-03 Thread Risto Suominen

2014-03-03 2:16 UTC+02.00, Aaron Valdes aaron78val...@gmail.com:

 boot: Linux video=DVI-I-1:d video=DVI-I-2:1280x1024:@75 video=TV-1:d

This is basically the same as my solution: unused outputs ADC and TV
are disabled, in addition the screen resolution is specified for DVI.

Risto


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cacyrqa3g+xnpwjkqlf9i_uewjvhjrlyfe_d+_z3lnnsdqxa...@mail.gmail.com

Re: Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

Risto,

I must be blind.

I am going try this as soon as the machine is up and running.

Thanks

Aaron


=

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

To: Aaron Valdes aaron78val...@gmail.com
Cc: debian-powerpc@lists.debian.org
Subject: Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX
5200 Ultra
From: Risto Suominen risto.suomi...@gmail.com
Date: Sun, 2 Mar 2014 08:52:36 +0200
Message-id:
cacyrqa0inazbppoxuipm7njdlwawepqp9nqsmgubttozo2w...@mail.gmail.com
In-reply-to: 1393736530.17451.8.camel@debianWheezy
References: 1393719836.14751.5.camel@debianWheezy
1393736530.17451.8.camel@debianWheezy


X Probabl selects wrong output. I'm using DVI, and the following
/etc/X11/xorg.conf makes it work:
--
Section Device
Identifier  Configured Video Device
BusID   PCI:240:16:0
Driver  nouveau
Option  Monitor-TV-1  Configured Monitor
Option  NoAccel   true
EndSection

Section Monitor
Identifier  Configured Monitor
Option  Ignoretrue
EndSection

Section Screen
Identifier  Default Screen
Device  Configured Video Device
EndSection
--
The idea is to disable the TV output that X thinks is active. There is
no connector on that output, but it exists on the chip.

Risto


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1393848712.23890.38.camel@debianWheezy

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

I re-installed Debian Wheezy on my Pro Mac G5 with GeForce FX 5200
Ultra.

I had to boot yaboot with...

boot: Linux video=DVI-I-1:d video=DVI-I-2:1280x1024:@75 video=TV-1:d

This is working right now.




On Sat, 2014-03-01 at 19:23 -0500, Aaron Valdes wrote:
 Hello All,
 
 I have installed Debian Wheezy on my Power Mac G5 and I am getting a
 black screen.
 
 The output from the lspci:
 
 root@ValdesPowerMac:/home/aaron/Downloads1# lspci  | grep  NVIDIA
 
 :f0:10.0 VGA compatible controller: NVIDIA Corporation NV34
 [GeForceFX 5200 Ultra] (rev a1)
 
 The binaries on the NVIDIA site do not support this video card for this
 architecture.
 
 Does anybody have the steps I need to follow to get this Video card
 working correctly.
 
 I have have been able to SSH into the machine.
 
 Aaron
 



-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1393851660.23890.40.camel@debianWheezy

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

Risto,

Thanks for your help.

The port I am using is DVI (DVI-I-2)

When booting I ran with this line and the display came up.

boot: Linux video=TV-1:d

My xorg.conf is:

Section Device
IdentifierFX5200
BusIDPCI:240:16:0
Driver  nouveau
Option  Monitor-DVI-I-1 ADC_Port
Option  Monitor-DVI-I-2 DVI_Port
Option  Monitor-TV-1 TV_Port
EndSection

Section Monitor
IdentifierDVI_Port
EndSection

Section Monitor
Identifier  ADC_Port
Option  Ignore true
EndSection

Section Monitor
IdentifierTV_Port
Option  Ignore true
EndSection

Section Screen
IdentifierDefault Screen
DeviceFX5200
DefaultDepth24
   SubSection   Display
 Depth24
 Virtual 1280 1024
   EndSubSection
EndSection

Section ServerLayout
Identifier  Default Layout
Screen  Default Screen
EndSection

Can you please post what your xorg.conf file is?

Is there a solution where I don't need to run this line.

boot: Linux video=TV-1:d

I am using Debian Wheezy.

Thanks again for pointing me in the correct place.

Aaron


On Sun, 2014-03-02 at 17:11 +0200, Risto Suominen wrote:
 2014-03-02 15:12 UTC+02.00, Aaron Valdes aaron78val...@gmail.com:
 
  This is Debian Wheezy on the Power Mac G5 with GeForce FX 5200 Ultra.
 
 I have exactly the same machine. Kernel is 3.1.0-1-powerpc64.
 
 Which output connector are you using, DVI (DVI-I-2) or ADC (DVI-I-1)?
 
 If you can ssh into the machine, take a look at /var/log/Xorg.0.log.
 
 Risto



-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1393861758.23890.48.camel@debianWheezy

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

2014-03-03 Thread Risto Suominen

You are right, Aaron. I also have that 'video=TV-1:d' on the kernel
command line.

It comes from /etc/yaboot.conf (so you don't need to write it on every boot):

append= video=TV-1:d

F.ex.:

image=/boot/vmlinux
label=Linux
read-only
initrd=/boot/initrd.img
append= video=TV-1:d

Then you have to run 'ybin' (as root) (yaboot install).

Risto


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CACyRQa2qdAcf=06q3xkjknsywajoqgfab7jk2t8oifmuqcg...@mail.gmail.com

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

Risto,

Thanks.

This works. :)

Can you post your xorg.conf?

Aaron

On Mon, 2014-03-03 at 18:21 +0200, Risto Suominen wrote:
 You are right, Aaron. I also have that 'video=TV-1:d' on the kernel
 command line.
 
 It comes from /etc/yaboot.conf (so you don't need to write it on every boot):
 
 append= video=TV-1:d
 
 F.ex.:
 
 image=/boot/vmlinux
   label=Linux
   read-only
   initrd=/boot/initrd.img
   append= video=TV-1:d
 
 Then you have to run 'ybin' (as root) (yaboot install).
 
 Risto



-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1393864932.23890.51.camel@debianWheezy

Re: Re: Wheezy install with dark screen after boot

I wonder if the problem with your card was related to Phantom Ports.

I just had a similar symptoms with Pro Mac G5 with GeForce FX 5200
Ultra.

We did manage to get this working.




On Jan 20, 2014, at 10:53 PM, Risto Suominen risto.suomi...@gmail.com
wrote:

 Hi Kristen,
 
 2014/1/21, Kristen R kris...@atmyhome.org:
 
 Advice as to what I should do? Like, how does one drop to a shell so
I might
 access the xorg.config file?
 
 Adding '1' to yaboot command line should bring you to single user
mode.
 
 Risto

Thank you Risto

I never did get a chance to actually try entering a 1 to the boot:
query. Instead I purchased a ATI Radeon 9800 Pro video card for Mac’s.
When I tried to boot to Debian everything worked as expected.

No computer lockups at the login screen
No half screen of black and white for the login screen

So changing the video card solved my problem.

It would seem there is a problem with the hardware detection phase and
the build of the xorg.conf file

Kristen


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1393865625.23890.56.camel@debianWheezy

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

2014-03-03 Thread Risto Suominen

2014-03-03 18:42 UTC+02.00, Aaron Valdes aaron78val...@gmail.com:

 Can you post your xorg.conf?

Here it is:
--
Section Device
Identifier  Configured Video Device
BusID   PCI:240:16:0
Driver  nouveau
Option  Monitor-TV-1  Configured Monitor
Option  NoAccel   true
EndSection

Section Monitor
Identifier  Configured Monitor
Option  Ignoretrue
EndSection

Section Screen
Identifier  Default Screen
Device  Configured Video Device
EndSection
--
It's kind of minimal. It only tells X to ignore the phantom TV output,
and leaves it the freedom to choose resolutions etc.

Risto


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cacyrqa0ap88e0xhf0xobmnkdujjw8_n-u8wbdrbhfrnn1c_...@mail.gmail.com

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

I took nouveau out of the black list.

I backed up my xorg.conf.

I made a new xorg.conf with these settings.

I rebooted and still have the black screen.

It even kills the terminal from coming up.

This is Debian Wheezy on the Power Mac G5 with GeForce FX 5200 Ultra.




On Sun, 2014-03-02 at 08:52 +0200, Risto Suominen wrote:
 X Probabl selects wrong output. I'm using DVI, and the following
 /etc/X11/xorg.conf makes it work:
 --
 Section Device
 Identifier  Configured Video Device
 BusID   PCI:240:16:0
 Driver  nouveau
 Option  Monitor-TV-1  Configured Monitor
 OptionNoAccel   true
 EndSection
 
 Section Monitor
 Identifier  Configured Monitor
 Option  Ignoretrue
 EndSection
 
 Section Screen
 Identifier  Default Screen
 Device  Configured Video Device
 EndSection
 --
 The idea is to disable the TV output that X thinks is active. There is
 no connector on that output, but it exists on the chip.
 
 Risto



-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1393765975.23250.1.camel@debianWheezy

Re: Re: Wheezy install with dark screen after boot

Kristen,

I installed Debian Wheezy on Mac Pro G5.

This is my video card.

:f0:10.0 VGA compatible controller: NVIDIA Corporation NV34 [GeForce
FX 5200 Ultra] (rev a1)

Geforce FX 5200 Ultra

Which Video cards where you having problems with before you changed to
the ATI Radeon?

Aaron


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1393766909.23890.1.camel@debianWheezy

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

2014-03-02 Thread Risto Suominen

2014-03-02 15:12 UTC+02.00, Aaron Valdes aaron78val...@gmail.com:

 This is Debian Wheezy on the Power Mac G5 with GeForce FX 5200 Ultra.

I have exactly the same machine. Kernel is 3.1.0-1-powerpc64.

Which output connector are you using, DVI (DVI-I-2) or ADC (DVI-I-1)?

If you can ssh into the machine, take a look at /var/log/Xorg.0.log.

Risto


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cacyrqa2xr4-sod8mbhe6z0m-ybso863qzqj7ztz8xu9iicv...@mail.gmail.com

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

2014-03-02 Thread David Gosselin

A tad off-topic but, if you can’t get this working and the apps you expect to 
run don’t require the muscle of your video card, then you can install your X 
clients on the machine and forward their displays to a X server on another 
machine on your network.  This is what I do for my PowerMac G5 7,3 running 
Debian 7.3.0 because I didn’t want to spend too much time getting the in-built 
graphics card to work.

On Mar 2, 2014, at 10:11 AM, Risto Suominen risto.suomi...@gmail.com wrote:

 2014-03-02 15:12 UTC+02.00, Aaron Valdes aaron78val...@gmail.com:
 
 This is Debian Wheezy on the Power Mac G5 with GeForce FX 5200 Ultra.
 
 I have exactly the same machine. Kernel is 3.1.0-1-powerpc64.
 
 Which output connector are you using, DVI (DVI-I-2) or ADC (DVI-I-1)?
 
 If you can ssh into the machine, take a look at /var/log/Xorg.0.log.
 
 Risto
 
 
 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/cacyrqa2xr4-sod8mbhe6z0m-ybso863qzqj7ztz8xu9iicv...@mail.gmail.com
 


--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/90f0e6a0-c972-474f-98c2-fb40aea5d...@appleside.org

Re: Wheezy install with dark screen after boot

2014-03-02 Thread Kristen R

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03/02/2014 04:28 AM, Aaron Valdes wrote:


Aaron,

I was using the stock card that comes with the G4 Mystic. Its an ATI
128 Rage with DVI and ADC connectors. I think it has 16M of memory on it.

Kristen

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlMTl6QACgkQMHfhKU1PiziIsgCcCNzmjezMgPJk0nPP302Lia7N
PE0AoLrs9tP+BXNjOT9An1rTgho7NSBF
=GvQ+
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/531397a4.6010...@atmyhome.org

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

That's very interesting.

Can you guide me to a good document on how to try this?


On Sun, 2014-03-02 at 14:36 -0500, David Gosselin wrote:
 A tad off-topic but, if you can’t get this working and the apps you expect to 
 run don’t require the muscle of your video card, then you can install your X 
 clients on the machine and forward their displays to a X server on another 
 machine on your network.  This is what I do for my PowerMac G5 7,3 running 
 Debian 7.3.0 because I didn’t want to spend too much time getting the 
 in-built graphics card to work.
 
 On Mar 2, 2014, at 10:11 AM, Risto Suominen risto.suomi...@gmail.com wrote:
 
  2014-03-02 15:12 UTC+02.00, Aaron Valdes aaron78val...@gmail.com:
  
  This is Debian Wheezy on the Power Mac G5 with GeForce FX 5200 Ultra.
  
  I have exactly the same machine. Kernel is 3.1.0-1-powerpc64.
  
  Which output connector are you using, DVI (DVI-I-2) or ADC (DVI-I-1)?
  
  If you can ssh into the machine, take a look at /var/log/Xorg.0.log.
  
  Risto
  
  
  -- 
  To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
  with a subject of unsubscribe. Trouble? Contact 
  listmas...@lists.debian.org
  Archive: 
  https://lists.debian.org/cacyrqa2xr4-sod8mbhe6z0m-ybso863qzqj7ztz8xu9iicv...@mail.gmail.com
  
 



-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1393794759.23890.14.camel@debianWheezy

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

2014-03-02 Thread David Gosselin


In my case, I wanted to run the X client for emacs.  All I needed to do was
# apt-get install emacs
I allowed apt to install the dependencies that it required but this did not 
install all of X.  From my Windows machine, which is running Xming, I ssh 
with PuTTY and enable X11 fowarding in the PuTTY config.  After login to the 
powermac, I can echo the DISPLAY variable and see that it is set to 
something like localhost:10.0.  If I run emacs from the command line, the 
GUI X client is drawn on my Xming server running on my Windows machine.


Let me know if you have specific questions, like how to configure PuTTY or, 
if you don't have Windows, I can show you how to use another Linux machine 
where you may have X11 running already.


Thanks,
Dave


-Original Message- 
From: Aaron Valdes

Sent: Sunday, March 02, 2014 4:12 PM
To: David Gosselin
Cc: Risto Suominen ; PowerPC List Debian
Subject: Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

That's very interesting.

Can you guide me to a good document on how to try this?


On Sun, 2014-03-02 at 14:36 -0500, David Gosselin wrote:
A tad off-topic but, if you can’t get this working and the apps you expect 
to run don’t require the muscle of your video card, then you can install 
your X clients on the machine and forward their displays to a X server on 
another machine on your network.  This is what I do for my PowerMac G5 7,3 
running Debian 7.3.0 because I didn’t want to spend too much time getting 
the in-built graphics card to work.


On Mar 2, 2014, at 10:11 AM, Risto Suominen risto.suomi...@gmail.com 
wrote:


 2014-03-02 15:12 UTC+02.00, Aaron Valdes aaron78val...@gmail.com:

 This is Debian Wheezy on the Power Mac G5 with GeForce FX 5200 Ultra.

 I have exactly the same machine. Kernel is 3.1.0-1-powerpc64.

 Which output connector are you using, DVI (DVI-I-2) or ADC (DVI-I-1)?

 If you can ssh into the machine, take a look at /var/log/Xorg.0.log.

 Risto


 -- 
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact 
 listmas...@lists.debian.org
 Archive: 
 https://lists.debian.org/cacyrqa2xr4-sod8mbhe6z0m-ybso863qzqj7ztz8xu9iicv...@mail.gmail.com







--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact 
listmas...@lists.debian.org

Archive: https://lists.debian.org/1393794759.23890.14.camel@debianWheezy


--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/215C00A2BDB14116B53F61AA1B184F7D@Sam

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra

Long story short.

I installed LinuxMintPPC and had the same problem.

Screen would go dark.

I found a post in the LinuxMint forums.

From yaboot I tried with the following line.

boot: Linux video=DVI-I-1:d video=DVI-I-2:1280x1024:@75 video=TV-1:d

It worked

I don't know if this same thing will work for Debian issue but
LinuxMintPPC is based on Debian Wheezy.

I am not even sure what this line does.

Original LinuxMintPPC Link:

http://www.mintppc.org/forums/viewtopic.php?f=15t=810sid=5d2ba9f25014dc538d9f63fe937fcdf8start=10






On Sat, 2014-03-01 at 19:23 -0500, Aaron Valdes wrote:
 Hello All,
 
 I have installed Debian Wheezy on my Power Mac G5 and I am getting a
 black screen.
 
 The output from the lspci:
 
 root@ValdesPowerMac:/home/aaron/Downloads1# lspci  | grep  NVIDIA
 
 :f0:10.0 VGA compatible controller: NVIDIA Corporation NV34
 [GeForceFX 5200 Ultra] (rev a1)
 
 The binaries on the NVIDIA site do not support this video card for this
 architecture.
 
 Does anybody have the steps I need to follow to get this Video card
 working correctly.
 
 I have have been able to SSH into the machine.
 
 Aaron
 



-- 
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1393805779.23890.23.camel@debianWheezy

Re: Power Mac G5 Debian Wheezy / Problem with GeForce FX 5200 Ultra