never thought I'd say it but it does.
Initially wanted to use Evas but the doco convinced me that Edje was what I wanted ... but ... all I got was that, documentation.
Evas used to have sample/test code, now it's gone. The 'edje' executable in the doc don't exist. WTF.
How the f**k can I QUICKLY experiment when I have to do so much exploration!
Please give us the test codes, or tell us where the f**k they are.
No wonder no-one uses it.
Monday, September 1, 2008
Monday, June 16, 2008
direct wireless (ad-hoc) between OSX Tiger and windows
I was hoping to be able to network my PCs via wireless. Since I don't have enough money for a wireless switch I bought an Aztech USB wireless adapter. Unfortunately it was not an easy task (and I only get 11mbs from the ad-hoc network but that's another story).
It took quite a while tinkering to eventually stumble on a solution.
The problem was that the builtin Mac wireless was not able to join a network (not for me anyways). But eventually I got the windows PC to join the Mac network. Here's how I did it.
Ensure there is no network with the ID that you want to use eg 'booger'. I then create a new network connection via 'system preferences'.

Choose 'network' then 'network port configurations'

then create a new network based on airport

now choose the new network

manually set the ip address

now open the 'network status'

now select the new network and press connect

now create a new wireless network

now press the 'network:' tab and 'create network' then set an ad-hoc network name and add a password

now you can connect to it via windows.
you could now ping from the Mac or Windows assuming you don't have a restrictive firewall.
It took quite a while tinkering to eventually stumble on a solution.
The problem was that the builtin Mac wireless was not able to join a network (not for me anyways). But eventually I got the windows PC to join the Mac network. Here's how I did it.
Ensure there is no network with the ID that you want to use eg 'booger'. I then create a new network connection via 'system preferences'.

Choose 'network' then 'network port configurations'

then create a new network based on airport

now choose the new network

manually set the ip address

now open the 'network status'

now select the new network and press connect

now create a new wireless network

now press the 'network:' tab and 'create network' then set an ad-hoc network name and add a password

now you can connect to it via windows.
you could now ping from the Mac or Windows assuming you don't have a restrictive firewall.
Monday, April 28, 2008
merlin u530 ubuntu powerbook g4 setup
I finally worked out how to use my Merlin U530 on my Ubuntu PPC Powerbook G4.
After googling around the web and contemplating recompiling the kernel (and kicking the crap out of the PC) I finally noticed a forum, regarding a Xen kernel, where it mentions that one should not start its console because it would conflict with serial_cs. I knew the Gutsy version recognised the card because that was why I overwrote my Edgy version when using the liveCD. The frustrating thing was that after installation Ubuntu Gutsy was never able to recognise the card again. Even the liveCD!
After noticing the forum discussion it thought I'd give it a go. Got nothing to lose anyways.
I looked at the messages log and noticed:
Apr 25 14:47:52 macpower kernel: [ 67.488926] PCI: Enabling device 0001:10:12.0 (0004 -> 0006)
Apr 25 14:47:52 macpower kernel: [ 69.385802] pmac_zilog: 0.6 (Benjamin Herrenschmidt)
Apr 25 14:47:52 macpower kernel: [ 69.385903] ttyS0 at MMIO 0x80013020 (irq = 22) is a Z85c30 ESCC - Serial port
Apr 25 14:47:52 macpower kernel: [ 69.386232] ttyS1 at MMIO 0x80013000 (irq = 23) is a Z85c30 ESCC - Serial port
Apr 25 14:47:52 macpower kernel: [ 70.040975] pccard: PCMCIA card inserted into slot 0
Apr 25 14:47:52 macpower kernel: [ 70.340953] cs: memory probe 0x80000000-0xafffffff: excluding 0x80000000-0x807fffff 0x90000000-0xa07fffff
Apr 25 14:47:52 macpower kernel: [ 70.386534] cs: memory probe 0xf3000000-0xf3ffffff: excluding 0xf3000000-0xf33fffff
Apr 25 14:47:52 macpower kernel: [ 70.538273] pcmcia: registering new device pcmcia0.0
Apr 25 14:47:52 macpower kernel: [ 70.538487] pcmcia: registering new device pcmcia0.1
Apr 25 14:47:52 macpower kernel: [ 71.022916] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Apr 25 14:47:52 macpower kernel: [ 71.166315] serial_cs: Unknown symbol serial8250_unregister_port
Apr 25 14:47:52 macpower kernel: [ 71.166653] serial_cs: Unknown symbol serial8250_resume_port
Apr 25 14:47:52 macpower kernel: [ 71.166806] serial_cs: Unknown symbol serial8250_register_port
Apr 25 14:47:52 macpower kernel: [ 71.166968] serial_cs: Unknown symbol serial8250_suspend_port
Apr 25 14:47:52 macpower kernel: [ 71.177218] snd-aoa-fabric-layout: found bus with layout 51
Apr 25 14:47:52 macpower kernel: [ 71.221263] snd-aoa-fabric-layout: can use this codec
Apr 25 14:47:52 macpower kernel: [ 71.231547] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Apr 25 14:47:52 macpower kernel: [ 71.246667] serial_cs: Unknown symbol serial8250_unregister_port
Apr 25 14:47:52 macpower kernel: [ 71.247003] serial_cs: Unknown symbol serial8250_resume_port
Apr 25 14:47:52 macpower kernel: [ 71.247159] serial_cs: Unknown symbol serial8250_register_port
Apr 25 14:47:52 macpower kernel: [ 71.247322] serial_cs: Unknown symbol serial8250_suspend_port
See how pmac_zilog uses /dev/ttyS0 and ttyS1. Since it has used the ports lets remove it:
rmmod pmac_zilog
The ttyS0 and ttyS1 should now be unused.
Now:
modprobe serial_cs
Logs:
Apr 28 13:30:41 macpower kernel: [ 435.356029] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Apr 28 13:30:41 macpower kernel: [ 435.384928] pcmcia: request for exclusive IRQ could not be fulfilled.
Apr 28 13:30:41 macpower kernel: [ 435.384941] pcmcia: the driver needs updating to supported shared IRQ lines.
Apr 28 13:30:41 macpower kernel: [ 435.426154] 0.0: ttyS0 at I/O 0x3f8 (irq = 53) is a 16550A
WooHoo. It worked. All I had to do was set up my chatscript and ppp.
No serial...never mind as long as I have my net. :)
debug
noauth
connect "/usr/sbin/chat -v -f /etc/chatscripts/celcom"
usepeerdns
/dev/ttyS0 115200
defaultroute
crtscts
lcp-echo-failure 0
includes the first newline
TIMEOUT 35
ECHO ON
ABORT '\nBUSY\r'
ABORT '\nERROR\r'
ABORT '\nNO ANSWER\r'
ABORT '\nNO CARRIER\r'
ABORT '\nNO DIALTONE\r'
ABORT '\nRINGING\r\n\r\nRINGING\r'
'' \rAT
OK 'AT+CGDCONT=1,"IP","celcom3g","",0,0'
OK ATD*99***1#
CONNECT ""
After googling around the web and contemplating recompiling the kernel (and kicking the crap out of the PC) I finally noticed a forum, regarding a Xen kernel, where it mentions that one should not start its console because it would conflict with serial_cs. I knew the Gutsy version recognised the card because that was why I overwrote my Edgy version when using the liveCD. The frustrating thing was that after installation Ubuntu Gutsy was never able to recognise the card again. Even the liveCD!
After noticing the forum discussion it thought I'd give it a go. Got nothing to lose anyways.
I looked at the messages log and noticed:
Apr 25 14:47:52 macpower kernel: [ 67.488926] PCI: Enabling device 0001:10:12.0 (0004 -> 0006)
Apr 25 14:47:52 macpower kernel: [ 69.385802] pmac_zilog: 0.6 (Benjamin Herrenschmidt
Apr 25 14:47:52 macpower kernel: [ 69.385903] ttyS0 at MMIO 0x80013020 (irq = 22) is a Z85c30 ESCC - Serial port
Apr 25 14:47:52 macpower kernel: [ 69.386232] ttyS1 at MMIO 0x80013000 (irq = 23) is a Z85c30 ESCC - Serial port
Apr 25 14:47:52 macpower kernel: [ 70.040975] pccard: PCMCIA card inserted into slot 0
Apr 25 14:47:52 macpower kernel: [ 70.340953] cs: memory probe 0x80000000-0xafffffff: excluding 0x80000000-0x807fffff 0x90000000-0xa07fffff
Apr 25 14:47:52 macpower kernel: [ 70.386534] cs: memory probe 0xf3000000-0xf3ffffff: excluding 0xf3000000-0xf33fffff
Apr 25 14:47:52 macpower kernel: [ 70.538273] pcmcia: registering new device pcmcia0.0
Apr 25 14:47:52 macpower kernel: [ 70.538487] pcmcia: registering new device pcmcia0.1
Apr 25 14:47:52 macpower kernel: [ 71.022916] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Apr 25 14:47:52 macpower kernel: [ 71.166315] serial_cs: Unknown symbol serial8250_unregister_port
Apr 25 14:47:52 macpower kernel: [ 71.166653] serial_cs: Unknown symbol serial8250_resume_port
Apr 25 14:47:52 macpower kernel: [ 71.166806] serial_cs: Unknown symbol serial8250_register_port
Apr 25 14:47:52 macpower kernel: [ 71.166968] serial_cs: Unknown symbol serial8250_suspend_port
Apr 25 14:47:52 macpower kernel: [ 71.177218] snd-aoa-fabric-layout: found bus with layout 51
Apr 25 14:47:52 macpower kernel: [ 71.221263] snd-aoa-fabric-layout: can use this codec
Apr 25 14:47:52 macpower kernel: [ 71.231547] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Apr 25 14:47:52 macpower kernel: [ 71.246667] serial_cs: Unknown symbol serial8250_unregister_port
Apr 25 14:47:52 macpower kernel: [ 71.247003] serial_cs: Unknown symbol serial8250_resume_port
Apr 25 14:47:52 macpower kernel: [ 71.247159] serial_cs: Unknown symbol serial8250_register_port
Apr 25 14:47:52 macpower kernel: [ 71.247322] serial_cs: Unknown symbol serial8250_suspend_port
See how pmac_zilog uses /dev/ttyS0 and ttyS1. Since it has used the ports lets remove it:
rmmod pmac_zilog
The ttyS0 and ttyS1 should now be unused.
Now:
modprobe serial_cs
Logs:
Apr 28 13:30:41 macpower kernel: [ 435.356029] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
Apr 28 13:30:41 macpower kernel: [ 435.384928] pcmcia: request for exclusive IRQ could not be fulfilled.
Apr 28 13:30:41 macpower kernel: [ 435.384941] pcmcia: the driver needs updating to supported shared IRQ lines.
Apr 28 13:30:41 macpower kernel: [ 435.426154] 0.0: ttyS0 at I/O 0x3f8 (irq = 53) is a 16550A
WooHoo. It worked. All I had to do was set up my chatscript and ppp.
No serial...never mind as long as I have my net. :)
debug
noauth
connect "/usr/sbin/chat -v -f /etc/chatscripts/celcom"
usepeerdns
/dev/ttyS0 115200
defaultroute
crtscts
lcp-echo-failure 0
includes the first newline
TIMEOUT 35
ECHO ON
ABORT '\nBUSY\r'
ABORT '\nERROR\r'
ABORT '\nNO ANSWER\r'
ABORT '\nNO CARRIER\r'
ABORT '\nNO DIALTONE\r'
ABORT '\nRINGING\r\n\r\nRINGING\r'
'' \rAT
OK 'AT+CGDCONT=1,"IP","celcom3g","",0,0'
OK ATD*99***1#
CONNECT ""
Wednesday, January 9, 2008
Subscribe to:
Comments (Atom)
