OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

4 Pages V  < 1 2 3 4 >  
Reply to this topicStart new topic
> Upgrading Beta1/beta3 To Pdaxii13, on all clamshell models
InSearchOf
post Feb 24 2007, 08:33 PM
Post #16





Group: Admin
Posts: 1,210
Joined: 20-January 06
From: York, Pennsylvania
Member No.: 8,961



do a xrandr -o 1 or 2 or 3 or 4 until it is correct and add it the bottom of your .xinitrc under your home dir...

Late

PS. Sorry I'm so vague... I didnt develop for pdaXii..
Go to the top of the page
 
+Quote Post
Meanie
post Feb 24 2007, 10:57 PM
Post #17





Group: Members
Posts: 2,808
Joined: 21-March 05
From: Sydney, Australia
Member No.: 6,686



QUOTE(grog @ Feb 25 2007, 02:30 PM)
C860 user here with the first problem  tongue.gif. The upgrade (from beta1) went without error, and the reboot went fine & X starts ok. But the display comes up rotated 90 degrees clockwise, so it's sitting sideways pointed the wrong way when the unit is in clampshell mode (i.e. the keyboard is visible), and rotates upside down when the unit screen is rotated to portrait mode.

Any idea how I can fix this? thks
*


if I had a tarball of a beta1 system (prior to upgrading) then it would help me out as a guide in general. in order to fix the upside down rotation problem, i need the startx script under /usr/X11R6/bin


to create the tarball, please do the following:

CODE
tar czf /mnt/card/corgi.tgz /bin /etc /home /lib /root /sbin /usr
Go to the top of the page
 
+Quote Post
Meanie
post Feb 25 2007, 02:53 AM
Post #18





Group: Members
Posts: 2,808
Joined: 21-March 05
From: Sydney, Australia
Member No.: 6,686



QUOTE(grog @ Feb 25 2007, 01:07 PM)
QUOTE(Meanie @ Feb 24 2007, 07:35 AM)
QUOTE(grog @ Feb 24 2007, 11:25 PM)
QUOTE(Meanie @ Feb 24 2007, 06:43 AM)
QUOTE(scoutme @ Feb 24 2007, 10:03 PM)
this is what I was looking for!
*
the SD module to support >1GB SD cards won't be available to c7x0/c8x0 models.
*

I was starting to get really interested too, until I read this post of course sad.gif sad.gif. I guess the issue is that the c7x0 models still use the 2.6.18 kernel instead of the 2.6.20, right? There's no way to get that working for us poor older clampshells?
*

actually, there is a driver for 2.4.18 that works on Sharp ROM and can in theory be copied to pdaXrom with modified sd scripts but I am unable to test this without having one of those models...
*

There's an eager tester right here! smile.gif I've got the driver (installed & working under Cacko). If you can walk me through what I'd need to do, I'll be your guinea pig. wink.gif
*



install this package on beta1 and see what happens with the SD card (of course don't install this package from a SD card directly smile.gif
Attached File(s)
Attached File  sdcard_hack_2.4.18_armv5tel.ipk ( 145.29K ) Number of downloads: 44
 
Go to the top of the page
 
+Quote Post
grog
post Feb 25 2007, 06:44 AM
Post #19





Group: Members
Posts: 692
Joined: 27-January 04
From: Canada
Member No.: 1,564



QUOTE(InSearchOf @ Feb 24 2007, 10:33 PM)
do a xrandr -o 1 or 2 or 3 or 4 until it is correct and add it the bottom of your .xinitrc under your home dir...
*

'xrandr -o 1' did the trick for landscape mode, but then rotating the screen flips it wrong again both in that & portrait, so I have to run it again (I assume the rotate script is hard coded for this value). No problem though, this gets me running properly in the mean time. thanks
Go to the top of the page
 
+Quote Post
grog
post Feb 25 2007, 07:17 AM
Post #20





Group: Members
Posts: 692
Joined: 27-January 04
From: Canada
Member No.: 1,564



QUOTE(Meanie @ Feb 25 2007, 12:57 AM)
QUOTE(grog @ Feb 25 2007, 02:30 PM)
C860 user here with the first problem  tongue.gif. The upgrade (from beta1) went without error, and the reboot went fine & X starts ok. But the display comes up rotated 90 degrees clockwise, so it's sitting sideways pointed the wrong way when the unit is in clampshell mode (i.e. the keyboard is visible), and rotates upside down when the unit screen is rotated to portrait mode.

Any idea how I can fix this? thks
*
if I had a tarball of a beta1 system (prior to upgrading) then it would help me out as a guide in general. in order to fix the upside down rotation problem, i need the startx script under /usr/X11R6/bin

to create the tarball, please do the following:

CODE
tar czf /mnt/card/corgi.tgz /bin /etc /home /lib /root /sbin /usr
*

It seems I can't upload a 32mb file to the board rolleyes.gif, so you can grab it here.

Thanks for all of your help & hard work (past, present & future smile.gif). It's MUCH appreciated.
Go to the top of the page
 
+Quote Post
adf
post Feb 25 2007, 06:37 PM
Post #21





Group: Members
Posts: 2,821
Joined: 13-September 04
From: Wasilla Ak.
Member No.: 4,572



any chance we can see pdaxii13 format big SD cards to FAT?
Go to the top of the page
 
+Quote Post
Meanie
post Feb 25 2007, 07:03 PM
Post #22





Group: Members
Posts: 2,808
Joined: 21-March 05
From: Sydney, Australia
Member No.: 6,686



QUOTE(adf @ Feb 26 2007, 12:37 PM)
any chance we can see pdaxii13 format big SD cards to FAT?
*


what are you asking? FAT16 has a 2GB limit, that's one of the reason FAT32 was created...
Go to the top of the page
 
+Quote Post
Meanie
post Feb 25 2007, 08:23 PM
Post #23





Group: Members
Posts: 2,808
Joined: 21-March 05
From: Sydney, Australia
Member No.: 6,686



QUOTE(Meanie @ Feb 25 2007, 08:53 PM)
QUOTE(grog @ Feb 25 2007, 01:07 PM)
QUOTE(Meanie @ Feb 24 2007, 07:35 AM)
QUOTE(grog @ Feb 24 2007, 11:25 PM)
QUOTE(Meanie @ Feb 24 2007, 06:43 AM)
QUOTE(scoutme @ Feb 24 2007, 10:03 PM)
this is what I was looking for!
*
the SD module to support >1GB SD cards won't be available to c7x0/c8x0 models.
*

I was starting to get really interested too, until I read this post of course sad.gif sad.gif. I guess the issue is that the c7x0 models still use the 2.6.18 kernel instead of the 2.6.20, right? There's no way to get that working for us poor older clampshells?
*

actually, there is a driver for 2.4.18 that works on Sharp ROM and can in theory be copied to pdaXrom with modified sd scripts but I am unable to test this without having one of those models...
*

There's an eager tester right here! smile.gif I've got the driver (installed & working under Cacko). If you can walk me through what I'd need to do, I'll be your guinea pig. wink.gif
*



install this package on beta1 and see what happens with the SD card (of course don't install this package from a SD card directly smile.gif
*



so who tried it? does it work?
Go to the top of the page
 
+Quote Post
Meanie
post Feb 25 2007, 08:30 PM
Post #24





Group: Members
Posts: 2,808
Joined: 21-March 05
From: Sydney, Australia
Member No.: 6,686



QUOTE(grog @ Feb 26 2007, 12:44 AM)
QUOTE(InSearchOf @ Feb 24 2007, 10:33 PM)
do a xrandr -o 1 or 2 or 3 or 4 until it is correct and add it the bottom of your .xinitrc under your home dir...
*

'xrandr -o 1' did the trick for landscape mode, but then rotating the screen flips it wrong again both in that & portrait, so I have to run it again (I assume the rotate script is hard coded for this value). No problem though, this gets me running properly in the mean time. thanks
*



edit /usr/X11R6/bin/startx and remove

CODE
-screen 480x640@270
Go to the top of the page
 
+Quote Post
adf
post Feb 25 2007, 09:09 PM
Post #25





Group: Members
Posts: 2,821
Joined: 13-September 04
From: Wasilla Ak.
Member No.: 4,572



Beta # only sees 4gig FAT 32 as 1 gig. I thought you knew--formatting at 4 gig to FAT32 yeilds a 1 gig FAT32 sd in beta3. Thought I'd ask if there was hope for a fix in PDaxii13. I'm guessing there won't be--seems like some fundamental sort of problem with the way the module handles FAT32--but I thought I'd ask. 4 gigs that would pop into pretty much any box would be handy.

kernel 2.6 doesn't seem to have this problem which I why I suspect it isn't going to be fixed
Go to the top of the page
 
+Quote Post
Meanie
post Feb 25 2007, 09:55 PM
Post #26





Group: Members
Posts: 2,808
Joined: 21-March 05
From: Sydney, Australia
Member No.: 6,686



QUOTE(adf @ Feb 26 2007, 03:09 PM)
Beta # only sees 4gig FAT 32 as 1 gig. I thought you knew--formatting at 4 gig to FAT32 yeilds a 1 gig FAT32 sd in beta3. Thought I'd ask if there was hope for a fix in PDaxii13.  I'm guessing there won't be--seems like some fundamental sort of problem with the way the module handles FAT32--but I thought I'd ask.  4 gigs that would pop into pretty much any box would be handy.

kernel 2.6 doesn't seem to have this problem which I why I suspect it isn't going to be fixed
*



erm... i've been using a 4GB SD card in pdaXii13 for like since build1....
Go to the top of the page
 
+Quote Post
adf
post Feb 26 2007, 12:33 AM
Post #27





Group: Members
Posts: 2,821
Joined: 13-September 04
From: Wasilla Ak.
Member No.: 4,572



I have also been using a 4 gig for about as long as we've known the module could be imported. I might hve been among the first to try it, in fact. that isn't the point.
try this:
backup your 4 gig sd
fdisk it to type 6 (windows FAT32..or was it type b--I always have to check)
format it vfat -F 32
check the size
I bet it will say 1 gig

type 82/ext2 works just fine.

this is actually a known issue.

I had originally been mildly curious as to whether anyone knew a fix, not intending to inform you of a defect. I think the problem maybe has something to do with the module, since the kernel can see >4 gig FAT32 on other media, and since the issue doesnt exist in 2.6 based roms. I seem to remember hrw saying it had something to do with block sizes.

Have you really never run into this? there was a thread running about it last fall.
Go to the top of the page
 
+Quote Post
daniel3000
post Feb 26 2007, 02:07 AM
Post #28





Group: Members
Posts: 1,002
Joined: 28-April 05
From: Germany
Member No.: 7,027



QUOTE(adf @ Feb 26 2007, 10:33 AM)
I have also been using a 4 gig for about as long as we've known the module could be imported.  I might hve been among the first to try it, in fact.  that isn't the point. 
try this:
backup your 4 gig sd
fdisk it to type 6 (windows FAT32..or was it type b--I always have to check)
format it  vfat -F 32
check the size
I bet it will say 1 gig

type 82/ext2 works just fine.

this is actually a known issue.

I had originally been mildly curious as to whether anyone knew a fix, not intending to inform you of a defect.  I think the problem maybe has something to do with the module, since the kernel can see >4 gig FAT32 on other media, and since the issue doesnt exist in 2.6 based roms.  I seem to remember hrw saying it had something to do with block sizes.

Have you really never run into this?  there was a thread running about it last fall.
*



I had this issue and found it seems to be a buggy mkfs version under beta3.
When you use the D+B boot emergency system and format the card's partition there with
CODE
mkfs.vfat -F 32 /dev/mmcda1

it will have 4GB again, with Fat32 FS (I tried this only with a 2GB card, though).

I have copied the mkfs versions from there to the main system now, so I can format cards without booting into D+B.

daniel
Go to the top of the page
 
+Quote Post
grog
post Feb 26 2007, 08:06 AM
Post #29





Group: Members
Posts: 692
Joined: 27-January 04
From: Canada
Member No.: 1,564



QUOTE(Meanie @ Feb 25 2007, 10:23 PM)
install this package on beta1 and see what happens with the SD card (of course don't install this package from a SD card directly smile.gif
*

QUOTE
so who tried it? does it work?
*

Busy with family stuff most of the weekend, so not much time. Tried it now, modules seem to be loaded

CODE
root-:) lsmod
Module                  Size  Used by    Tainted: P
sharp_mmcsd_m          25888   0  (unused)
sdmmc_linux            12680   1  (initializing)
sd_memory               4680   0  [sdmmc_linux]
sd_core                17908   0  [sdmmc_linux sd_memory]
sd_linux               11496   0  [sdmmc_linux sd_memory sd_core]
mousedev                4496   1
pxa_bi                 21388   0  (unused)
net_fd                 25000   0  (unused)
usbdcore               34456   0  [pxa_bi net_fd]
usbdmonitor             5216   0

but lots of errors from dmesg

CODE
edc
r10: c15b4000  r9 : 00034cd8  r8 : c5b00da8
r7 : 00000010  r6 : 00000000  r5 : c5b01258  r4 : 00000010
r3 : c5ac5ff8  r2 : 00000010  r1 : 0000000f  r0 : c5b01258
Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: 197F  Table: A16B4000  DAC: 00000015  PID:  0
Process insmod (pid: 707, stackpage=c15b5000)
Stack: (0xc15b5ec0 to 0xc15b6000)
5ec0: c5b00c14 c011f66c 80000013 ffffffff c15b5f04 c15b5ee0 c5b00c14 c011f654
5ee0: 00000000 c5b011b0 c5b00000 c159d000 00000060 ffffffea c15b5fa4 c15b5f08
5f00: c0044088 c5b00aa8 c159d000 c15b5f1c c159e000 0000000b c3e0cd00 00000060
5f20: c5af0000 c5b00060 00003188 00000000 00000000 00000000 00000000 00000000
5f40: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
5f60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000005
5f80: c5b00000 00000000 00000080 c002f9e4 c15b4000 00000000 00000000 c15b5fa8
5fa0: c002f840 c0043974 00000005 c003f934 00021ad0 00034cd8 ffffffff 40016000
5fc0: 00000005 c5b00000 00000000 0002eb28 00003188 00000000 00000000 0000000b
5fe0: 400e8aa0 bfffba80 0000c938 400e8aac 60000010 00021ad0 00000000 00000000
Backtrace:
Function entered at [<c011f648>] from [<c5b00c14>]
Function entered at [<c5b00a9c>] from [<c0044088>]
r8 = FFFFFFEA  r7 = 00000060  r6 = C159D000  r5 = C5B00000
r4 = C5B011B0
Function entered at [<c0043968>] from [<c002f840>]
Code: e3530000 0a000004 e1530000 0a000008 (e5933020)
SD: RCA=0xb368
SD: SD memory is detected
Unable to handle kernel NULL pointer dereference at virtual address 00000063
pgd = c0004000
*pgd = a0002001, *pmd = a0002001, *pte = a000108f, *ppte = a000100f
Internal error: Oops: ffffffff
CPU: 0
pc : [<c003ff2c>]    lr : [<c0041240>]    Tainted: P
sp : c16bdf74  ip : c16bdf98  fp : c16bdf94
r10: c0282fe4  r9 : c5ac0bb8  r8 : 20000013
r7 : c5ac2128  r6 : 00000000  r5 : c16bc000  r4 : 00000000
r3 : 00000001  r2 : c16bc000  r1 : c16bc0e8  r0 : 00000063
Flags: nzCv  IRQs off  FIQs on  Mode SVC_32  Segment kernel
Control: 197F  Table: A35F4000  DAC: 0000001D  PID:  0
Process ttach (pid: 710, stackpage=c16bd000)
Stack: (0xc16bdf64 to 0xc16be000)
df60:          c0041240 c003ff2c 20000093 ffffffff 00000000 c16bc000 00000000
df80: c5ac2128 c2d1cb10 c16bdfa4 c16bdf98 c0041240 c003ff18 c16bdfb4 c16bdfa8
dfa0: c0045fbc c0041220 c16bdfc4 c16bdfb8 c0046264 c0045f50 c16bdff4 c16bdfc8
dfc0: c5ac023c c004624c c2d1cb50 00000000 c03c4000 c03c4000 c03c4348 c03c4338
dfe0: 00000001 c03c5fbc 00000000 c16bdff8 c0030c04 c5ac00b0 00000000 00000000
Backtrace:
Function entered at [<c003ff0c>] from [<c0041240>]
r8 = C2D1CB10  r7 = C5AC2128  r6 = 00000000  r5 = C16BC000
r4 = 00000000
Function entered at [<c0041214>] from [<c0045fbc>]
Function entered at [<c0045f44>] from [<c0046264>]
Function entered at [<c0046240>] from [<c5ac023c>]
Function entered at [<c5ac00a4>] from [<c0030c04>]
Code: e3883080 e121f003 e5903000 e2833001 (e4803004)
Unable to handle kernel paging request at virtual address ffffffff
pgd = c0004000
*pgd = 00000000, *pmd = 00000000
Internal error: Oops: 0
CPU: 0
pc : [<c004bb20>]    lr : [<c0046168>]    Tainted: P
sp : c16bde4c  ip : c16bde60  fp : c16bde5c
r10: ffffffff  r9 : ffffffff  r8 : c003ff2c
r7 : ffffffff  r6 : 0000000b  r5 : c16bc000  r4 : c16bc000
r3 : a0000093  r2 : a0000093  r1 : ffffffff  r0 : c16bc000
Flags: NzCv  IRQs off  FIQs on  Mode SVC_32  Segment kernel
Control: 197F  Table: A35F4000  DAC: 0000001D  PID:  0
Process ttach (pid: 710, stackpage=c16bd000)
Stack: (0xc16bde3c to 0xc16be000)
de20:                                                                c0046168
de40: c004bb20 a0000093 ffffffff c3c8fae0 c16bde6c c16bde60 c0046168 c004baf0
de60: c16bde88 c16bde70 c00341a8 c0045f50 00000063 c16bdf2c 00000000 c16bdea8
de80: c16bde8c c0034ee4 c00340ac c16bc000 e4803004 c16bdf2c 00000063 c16bdec0
dea0: c16bdeac c0034f98 c0034e88 ffffffff 00000004 c16bdef8 c16bdec4 c0036b60
dec0: c0034f50 c16bdf2c c3190000 00000000 00000063 c16bc000 00000024 00000003
dee0: c02111e4 c02111c0 ffffffff c16bdf28 c16bdefc c0035694 c00369c4 c16bdf2c
df00: ffffffff c16bdf60 00000000 c5ac2128 20000013 20000093 c0282fe4 c16bdf94
df20: c16bdf2c c002f480 c003562c 00000063 c16bc0e8 c16bc000 00000001 00000000
df40: c16bc000 00000000 c5ac2128 20000013 c5ac0bb8 c0282fe4 c16bdf94 c16bdf98
df60: c16bdf74 c0041240 c003ff2c 20000093 ffffffff 00000000 c16bc000 00000000
df80: c5ac2128 c2d1cb10 c16bdfa4 c16bdf98 c0041240 c003ff18 c16bdfb4 c16bdfa8
dfa0: c0045fbc c0041220 c16bdfc4 c16bdfb8 c0046264 c0045f50 c16bdff4 c16bdfc8
dfc0: c5ac023c c004624c c2d1cb50 00000000 c03c4000 c03c4000 c03c4348 c03c4338
dfe0: 00000001 c03c5fbc 00000000 c16bdff8 c0030c04 c5ac00b0 00000000 00000000
Backtrace:
Function entered at [<c004bae4>] from [<c0046168>]
r4 = C3C8FAE0
Function entered at [<c0045f44>] from [<c00341a8>]
Function entered at [<c00340a0>] from [<c0034ee4>]
r6 = 00000000  r5 = C16BDF2C  r4 = 00000063
Function entered at [<c0034e7c>] from [<c0034f98>]
r7 = 00000063  r6 = C16BDF2C  r5 = E4803004  r4 = C16BC000
Function entered at [<c0034f44>] from [<c0036b60>]
r4 = 00000004
Function entered at [<c00369b8>] from [<c0035694>]
Function entered at [<c0035620>] from [<c002f480>]
Function entered at [<c003ff0c>] from [<c0041240>]
r8 = C2D1CB10  r7 = C5AC2128  r6 = 00000000  r5 = C16BC000
r4 = 00000000
Function entered at [<c0041214>] from [<c0045fbc>]
Function entered at [<c0045f44>] from [<c0046264>]
Function entered at [<c0046240>] from [<c5ac023c>]
Function entered at [<c5ac00a4>] from [<c0030c04>]
Code: e5843334 e10f2000 e3823080 e121f003 (e5913000)
SD: bus 0 is unregistered.
Unable to handle kernel paging request at virtual address c5ac603c
pgd = c1770000
*pgd = a3f47021, *pmd = a3f47021, *pte = 00000000, *ppte = 00000000
Internal error: Oops: 0
CPU: 0
pc : [<c006b430>]    lr : [<00000000>]    Tainted: P
sp : c1851ec0  ip : a0000013  fp : c1851ee8
r10: c3a6f060  r9 : c3f1b73c  r8 : 00003c00
r7 : c1fedd20  r6 : fffffffa  r5 : 3c000000  r4 : c3f1b720
r3 : c5ac6028  r2 : c1fedd20  r1 : c3a6f060  r0 : c3f1b720
Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  Segment user
Control: 197F  Table: A1770000  DAC: 00000015  PID:  0
Process mount (pid: 885, stackpage=c1851000)
Stack: (0xc1851eb0 to 0xc1852000)
1ea0:                                     00000000 c006b430 a0000013 ffffffff
1ec0: c3a6f060 c1fedd20 c1fedd20 c32d9268 c02541d4 c1850000 0001e89c c1851f00
1ee0: c1851eec c006b638 c006b3c8 c3a6f060 c32d9260 c1851f30 c1851f04 c00b2dd8
1f00: c006b610 c1851f20 c1851f14 c006ed30 c1fedd20 c3a6f060 00000000 c03be360
1f20: c3b1c6c0 c1851f54 c1851f34 c006390c c00b2d08 00020000 00020000 00000000
1f40: c3f1c000 c002f9e4 c1851f84 c1851f58 c0063804 c0063814 c3b1c6c0 c03be360
1f60: c006eab8 c005b128 c3f1c000 00000001 00000001 00000003 c1851fa4 c1851f88
1f80: c0063b60 c00637c4 bfffdff8 00020210 00000000 00000005 00000000 c1851fa8
1fa0: c002f840 c0063b28 bfffdff8 c00356f4 00020210 00020000 00000000 00006000
1fc0: bfffdff8 00020210 00000000 00020210 bffff658 bffff668 0001e89c 00020230
1fe0: 40137e7c bfff57e8 400db290 400db264 60000010 00020210 4021c26c 401ef29c
Backtrace:
Function entered at [<c006b3bc>] from [<c006b638>]
Function entered at [<c006b604>] from [<c00b2dd8>]
r5 = C32D9260  r4 = C3A6F060
Function entered at [<c00b2cfc>] from [<c006390c>]
r8 = C3B1C6C0  r7 = C03BE360  r6 = 00000000  r5 = C3A6F060
r4 = C1FEDD20
Function entered at [<c0063808>] from [<c0063804>]
r8 = C002F9E4  r7 = C3F1C000  r6 = 00000000  r5 = 00020000
r4 = 00020000
Function entered at [<c00637b8>] from [<c0063b60>]
r4 = 00000003
Function entered at [<c0063b1c>] from [<c002f840>]
r7 = 00000005  r6 = 00000000  r5 = 00020210  r4 = BFFFDFF8
Code: e5840018 e5943018 e3530000 0a000048 (e5931014)


no /dev/mmcd/disc0/part devices created, just a /dev/mmcd/disc0/disc, which fails to mount

CODE
root-:) mount /dev/mmcd/disc0/disc /mnt/card
Segmentation fault
Go to the top of the page
 
+Quote Post
grog
post Feb 26 2007, 09:55 AM
Post #30





Group: Members
Posts: 692
Joined: 27-January 04
From: Canada
Member No.: 1,564



QUOTE(Meanie @ Feb 25 2007, 10:30 PM)
QUOTE(grog @ Feb 26 2007, 12:44 AM)
QUOTE(InSearchOf @ Feb 24 2007, 10:33 PM)
do a xrandr -o 1 or 2 or 3 or 4 until it is correct and add it the bottom of your .xinitrc under your home dir...
*
'xrandr -o 1' did the trick for landscape mode, but then rotating the screen flips it wrong again both in that & portrait, so I have to run it again (I assume the rotate script is hard coded for this value). No problem though, this gets me running properly in the mean time. thanks
*

edit /usr/X11R6/bin/startx and remove

CODE
-screen 480x640@270
*

That did the trick. thks
Go to the top of the page
 
+Quote Post

4 Pages V  < 1 2 3 4 >
Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 18th December 2014 - 12:12 PM