Xorg 7.0.0 failing on powermac G3

2006-09-24 Thread Wakko Warner
I am not subscribed to this list, please always CC me.

X worked on this machine until I added an ethernet card.  Seems X wants to
use the I/O ports for the ethernet card and not for the ATI card.  I don't
have the Xorg log for when it worked.  Apparently, it does not matter which
type of ethernet card I used (Both a 3com 3x905 and a mac 100 enet card (tulip
chip) have the same result).  In the lspci list below, there are 2 ethernet
cards.  The PCNet was not installed with the 3com and still has the same
error.  Seems the problem occurs with a card installed in the top slot.

I tried specifying the IO base and trying with UseFBDev true and false.

I then tried moving the mac enet card to the middle slot (removing the pcnet
card).  X this time didn't complain as it shows below but locked the system
hard.

This is what is shown on the console when I attempt to start X.

# X
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/narf:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.8-powerpc-smp ppc
Current Operating System: Linux narf 2.6.17 #4 Tue Sep 19 20:32:37 EDT 2006 ppc
Build Date: 16 March 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Sep 24 13:23:25 2006
(==) Using config file: "/etc/X11/xorg.conf"
(WW) INVALID IO ALLOCATION b: 0xfe001000 e: 0xfe0010ff correcting
(EE) end of block range 0xfdff < begin 0xfe00
(EE) ATI(0): Unable to register the following bus resources:
[0] 0   0   0xfe000400 - 0xfe0004ff (0x100) IS[B]
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
#

lspci -vv shows:
:00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort+ SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Sep 24 13:23:25 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) |   |-->Monitor "Generic Monitor"
(**) |   |-->Device "ATI Technologies, Inc. 3D Rage I/II 215GT [Mach64 GT]"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/X11R6/lib/X11/fonts/misc" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/Type1" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi" does not exist.
Entry deleted from font path.
(WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not 
exist.
Entry deleted from font path.
(**) FontPath set to 
"/usr/share/fonts/X11/misc,/usr/share/fonts/X11/cyrillic,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,/usr/share/fonts/X11/misc/,/usr/share/fonts/X11/TTF/,/usr/share/fonts/X11/OTF,/usr/share/fonts/X11/Type1/,/usr/share/fonts/X11/CID/,/usr/share/fonts/X11/100dpi/,/usr/share/fonts/X11/75dpi/"
(==) RgbPath set to "/usr/share/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.2
X.Org Video Driver: 0.8
X.Org XInput driver : 0.5
X.Org Server Extension : 0.2
X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 7.0.0, module version = 1.0.0
Module class: X.Org Font Renderer

Re: Xorg 7.0.0 failing on powermac G3

2006-10-15 Thread Wakko Warner
Sorry for the long delay.  I have not touched the mac until today.  Also,   
noone else on the powerpc list responded.

brian wrote:
> hi, i also have a beige currently running
> sarge/2.6.8-3/Xfree4.3 -- procrastinating
> on the upgrade although i have already done
> on two other ppc/macs (one old w. one new)

I downgraded the xserver to xfree86 4.3 from sarge (breaking several X
packages, but oh well =).  It does work.

> i have a kne100TX which uses a tulip driver
> in the beige; also an old powerbook which uses
> a revised tulip driver de2114x. i heard that 
> before they had it the old tulip driver used
> to hang e/net. also in etch i recently for a little
> while discover was trying to overload the old
> driver again (updates fixed a few weeks ago).

I believe that's the same NIC I have, but I tried 3 different chips with the
same result.  Also doesn't matter which slot the card is in.

> i do not have usb, but i have 2nd graphics card.
> i remember i think i had to move the e/net, i believe
> i would not try and move it from what it is now.

I have not tried this, however, adding another video card was not an option. 
I needed more than 1 10/100 nic and the usb card.  (Because the mac keyboard
and mouse SUCK! =)

> i tried moving the gfx card once and it was unstable,
> so i have to leave it, i guess what you call
> the third slot ? that would be the one furthest
> from the motherboard. one problem i do have not
> yet too bad but disapointing is that the builtin
> interface is ignored, that prevents me from doing
> some sort of routing, with this machine (like if
> you want a webserver with a personal line also -- 
> i had hoped the builtin could go to internet and
> fast card to my LAN). anyway the one card does work
> in sarge, apparently, dows not crash X or anything,
> but i have also yet to do my LAN work with Linux...

The onboard nic works fine with the other cards installed.  Not sure about
with an addon video card.

> no usb here, but i wonder why you did not speak
> of trying to move/remove that card ?? 

Because that card did not make a difference.  I originally had it in the
bottom slot, now it's in the top slot.

> should i expect breakage on my upgrade ? well i will
> try it anyway, if you want to wait a little bit,
> maybe this will get me moving...

If you have the same thing I have, then it probably will break.

I have reported the bug to xserver-xorg-core package.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Problems with Dial-up on Old World Mac

2006-10-25 Thread Wakko Warner
Jeffrey Rolland wrote:
> Hello, all!
> 
> I have a Power Macintosh 7500 running Debian Sarge. I have a US  
> Robotics 56.6K modem.
> 
> When I try to dial up, Debian gets the modem to dial, and the modem  
> negotiates a connection, but then the remote computer can't hear  
> anything Debian says, and Debian can't hear anything the remote  
> computer says. I have tested with KPPP and C-Kermit, and on two  
> different PAP authenticating ISPs and on two BBS - same thing.
> 
> Using the same computer and modem with Mac OS 8.6, I am able to log  
> into both the ISPs and the BBSs. Thus, I don't believe the problem is  
> the modem.
> 
> On a possibly related note, I am unable to detect an Apple  
> Laserwriter 4/600 PS I have hooked up via ethernet, an ethernet  
> switch, and an AsanteTalk ethertalk-to-localtalk bridge. Again, it  
> prints just fine from the same computer running Mac OS 8.6 and from  
> an iBook G3 running OS 10.4.8 hooked up the the ethernet switch.  
> Thus, I don't believe the problem is the AsanteTalk bridge.

If this USR is a sportster, that is an init string that you need to give it
or you will run into problems like this.  I don't remember what it was off
the top of my head, but it is the modem (according to past experiences with
USR modems)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Problems with Dial-up on Old World Mac

2006-10-25 Thread Wakko Warner
[EMAIL PROTECTED] wrote:
> > If this USR is a sportster, that is an init string that you need to give
> > it
> > or you will run into problems like this.  I don't remember what it was off
> > the top of my head, but it is the modem (according to past experiences
> > with
> > USR modems)
> 
> It is indeed a sportster.. If you could remember the init string or tell
> me where to look it up, I would be eternally grateful.

Here is the string I used on a 56k sportster at work:
AT&F&C1&D2S11=50&B1

I believe &B1 is the part that makes it work for me.  S11=50 makes the modem
dial as fast as it can.  You may not want this especially if your phone co
can't handle it.

You should verify the commands with the manual before blindly using the one
I gave you.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Problems with Dial-up on Old World Mac

2006-10-26 Thread Wakko Warner
[EMAIL PROTECTED] wrote:
> > Here is the string I used on a 56k sportster at work:
> > AT&F&C1&D2S11=50&B1
> >
> > I believe &B1 is the part that makes it work for me.  S11=50 makes the
> > modem
> > dial as fast as it can.  You may not want this especially if your phone co
> > can't handle it.
> >
> > You should verify the commands with the manual before blindly using the
> > one
> > I gave you.
> 
> IT WORKED!! (Well, sorta ...)
> 
> I couldn't find my manual (only the manual for an old SupraExpress), so I
> had to try your init string "blindly".
> 
> AT&F&B1 didn't work, so I tried AT&F&C1&D2&B1 - and IT WORKED!

USR modems have some non-standard commands.  I don't think (IIRC) that &B
works on most modems.

> Unfortunately, my "system adminstrator" (the guy at the Linux Users' Group
> who helped me set up my system) has my Debian box set up as a DHCP (sp?)
> server (so that I can log into my Debian box from my iBook using the
> "Connect to Server" in the Finder) so I wan't immediately able to use the
> connection (at least, I believe the DHCP server settings were the
> problem). I'll have to contact the "system administrator" about what to do
> now, but it definitely did log into my ISP.

Glad it worked for you.  I think I tried a few things and that was the only
thing that worked for me (&B1 that is).

> I could kiss you, WW! Thanks so much!

Lets not go there =)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Flickering screen on a cinema display.

2007-04-27 Thread Wakko Warner
Charles Plessy wrote:
> I have just installed Etch on a powermac7,3 with a cinema display, but
> very unfortunately, the screen flickers, making it difficult to work
> with the computer.
> 
> I have found a hint on the fglrx page
> (http://www.stanchina.net/~flavio/debian/fglrx-installer.html): it seems
> necessary to reduce the refreshing frequency of the screen. However, in
> /etc/X11/xorg, there are two ranges of, horizontal and vertical, so I
> do not know how to tell xorg to refresh at 50 Hz.
> 
> Did anybody experience the same problem and found a solution ?

Yes, I had this with a radeon 9200 on a PC and a 1600x1200 LCD connected via
DVI (Did not occur with VGA).  I had to tell xorg to ignore edid and I
modified each mode line's dot clock to the absolute lowest it would go (down
to 2 decimal places).  I still had flickering at 1600x1200.  I've since
replaced it with a Fire GL X1 card and the flicker is completely gone.

It seems to be the fact there's not enough bandwidth on a single link DVI
cable.  I didn't have a dual link to test with so I'm not sure if that helps
or not.

My monitor is a Samsung SyncMaster 204T 20" LCD

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Flickering screen on a cinema display.

2007-04-28 Thread Wakko Warner
Charles Plessy wrote:
> Le Fri, Apr 27, 2007 at 10:22:21PM -0400, Wakko Warner a ?crit :
> > Yes, I had this with a radeon 9200 on a PC and a 1600x1200 LCD connected via
> > DVI (Did not occur with VGA).  I had to tell xorg to ignore edid and I
> > modified each mode line's dot clock to the absolute lowest it would go (down
> > to 2 decimal places).  I still had flickering at 1600x1200.  I've since
> > replaced it with a Fire GL X1 card and the flicker is completely gone.
> > 
> > It seems to be the fact there's not enough bandwidth on a single link DVI
> > cable.  I didn't have a dual link to test with so I'm not sure if that helps
> > or not.
> 
> As everything works OK on osX, I wonder what kind of black magick is
> used by Apple... My problem is that I can not ask for a new graphical
> card just because I can not install linux on my work computer: working
> with linux is more comfortable in some cases, but as anyway osX is
> required for many things (flash, MS office, ...) so I can not justify
> such spending :(

I'm not sure I would call this black magic.  They just drive the monitor at
50hz instead of 60hz.  I only replaced my video card for one that was better
and it had the added benefit of no flicker (with the same configuration as
the older one)

> How did you tell xorg to ignore "edid" ?

man radeon and look for "EDID".  I'm not sure what video chip is in your
mac but the option should work for other drivers.  The options go in the
section where the video card is defined.

You can also use xvidtune to show you your current modeline that you would
place in the monitor section of the xorg.conf.  There is a warning, but if
all you're going to do is have it show that information, it won't do any
damage.  You'll probably have to run that from the terminal since it shows
the modeline on the screen.

It shows this for mine at 1600x1200:
"1600x1200"   135.00   1600 1664 1856 2160   1200 1201 1204 1250

If want to lower the hz from 60 to 50, you'll have to lower the 2nd number
(this is the dot clock) until its as low as it'll go.  It probably took me
10 minutes per resolution that I use to get all at 50hz.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Flickering screen on a cinema display.

2007-05-01 Thread Wakko Warner
Charles Plessy wrote:
> Thanks for the hint. I added the following line in xorg.conf:
> 
> ModeLine"1920x1200" 138 1920 2048 2256 2592 1200 1201 1204 
> 1242
> 
> Howerver, I can not go lower than 138 (it freezes the system), and it is still
> too high to solve the problem. I also added:

You probably can't go lower.  That's the dot clock.  The higher the
resolution, the higher the dot clock for the same refresh rate.

> Option  "IgnoreEDID""on"

Did you try "true" instead of "on"?

> with no success neither.
> 
> Is there something else I can try?

Option  "DisplayPriority" "HIGH"
Option  "MergedFB" "false"

Those are the only other 2 options I have in my config file.  It may also
just be your video card.  Have you tried running it in analog mode instead
of digital? (or can you?)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Bug#415543: xorg: xserver crashes on beige G3 PowerMac

2007-05-22 Thread Wakko Warner
Brice Goglin wrote:
> Could somebody have a look at bug #415543? Rob has a strange problem on
> his PowerMac. Basically, Xorg and network cannot work at the same time.
> I suspect a hardware or kernel problem, but I am not familiar enough
> with powerpc to debug further. Help would be appreciated.

I had a problem like this.  If I installed a nic (3com, tulip, or amd
pcnet32), X wouldn't work.  I forgot the details now.

> > Hi, first of all thanks for your reply. My /proc/interrupts looks as 
> > follows:
> >
> >   CPU0
> >  18:583   PMAC-PIC  Edge  MESH
> >  20:  0   PMAC-PIC  Edge  PMac
> >  21:  0   PMAC-PIC  Edge  PMac Output
> >  22:  0   PMAC-PIC  Edge  PMac Input
> >  23:217   PMAC-PIC  Level eth0
> >  25:  0   PMAC-PIC  Edge  SWIM3
> >  27:   1559   PMAC-PIC  Edge  ide0
> >  29:   5078   PMAC-PIC  Edge  ADB
> > BAD:  0
> >  
> > eth0 doesn't appear to share the interrupt with anything else. I really 
> > can't tell which one my graphic card is supposed to be. The network card's 
> > number is 23 which explains the "Disabling IRQ#23" message when I get 
> > thrown out of the network. On a hunch I moved the ethernet card to another 
> > pci slot but that had the same result.
> >
> > The sordid debian installation story for my power mac is as follows. I had 
> > both xfree86 and network working together with sarge, the 2.6.8  kernel and 
> > bootx (the bootloader). With bootx you boot into os9 and then from there 
> > boot into linux. I then completely erased os9 and sarge and installed sarge 
> > and then etch using quik. Quik (also a bootloader) allows you to boot 
> > directly into linux. Because I couldn't get xfree86 or xorg working at all 
> > with quik (similar problem with screen freezing), I installed etch with os9 
> > and bootx.
> >
> > Beats me if I broke something along the way...
> >
> > Anyways, thanks for your help up till now. At least I know now what 
> > interrupts and IRQs are. As always, more help is appreciated.
> >
> > yours, rob homsi
> >   
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 
-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]