Slackware inside Pandora.

[Linux-SWAT]

There has to be, as the sdinstaller app seems to do this, but maybe you could let the user select the card he wants to install to?

My actual choice is right or left slot.


I'd prefer not to get the card ID, because can be the same if two similar cards are inserted.

 

[Linux-SWAT]

Here is the typical pnd mount error that i don't understand:

=======================================================================================

PND			 : /media/SD32/pandora/menu/schwerkraft.pnd

PND_FSTYPE	  : #

APPDATADIR	  : /media/SD32/pandora/appdata/schwerkraft

APPDD_FSTYPE    : vfat

PND_CPUSPEED    : <unset>

EXENAME		 : ./schwerkraft.sh

ARGUMENTS	   : <unset>

=======================================================================================

[ START ]--- Mount the PND ----------

ERROR Unknown filesystem type : #

ERROR: The Union File-system is not mounted !

+++++++

Loopback devices :

Are mounted on :

For these Union :

[ FAILED]--- Mount the PND ----------

=======================================================================================

Return code is : 6

 

[sebt3]

What is the result of ?


file -b /media/SD32/pandora/menu/schwerkraft.pnd


It should be either ISO something, directory or Squashfs...


by the log you show, it's "#" which is kinda surprising

 

[Linux-SWAT]

# ISO 9660 CD-ROM filesystem data 'CDROM


Mmm a sorting error ? I use:


export LANG=en_US.UTF-8


export LC_COLLATE=C

 

[sebt3]

# ISO 9660 CD-ROM filesystem data 'CDROM

On every system I've seen the replys is the same but without that '#'. You might want to check what's going on with this "file" (aka change /usr/share/file/magic)

 

[Linux-SWAT]

grep 9660 /etc/file/magic/*

/etc/file/magic/filesystems:# not iso9660_stage1_5

/etc/file/magic/filesystems:# 0=stage2 1=ffs 2=e2fs 3=fat 4=minix 5=reiserfs 6=vstafs 7=jfs 8=xfs 9=iso9660 a=ufs2

/etc/file/magic/filesystems:!:mime application/x-iso9660-image

/etc/file/magic/filesystems:>38913 string   !NSR0	  ISO 9660 CD-ROM filesystem data

/etc/file/magic/filesystems:37633 string    CD001	 ISO 9660 CD-ROM filesystem data (raw 2352 byte sectors)

/etc/file/magic/filesystems:!:mime application/x-iso9660-image

Humpf. Dunno what to do :/ .

 

[sebt3]

failing that you could add a work around to pnd_run.sh. Line 686, instead of :


PND_FSTYPE=$(file -b "$PND" | awk '{ print $1 }')


let's have :


PND_FSTYPE=$(file -b "$PND" | awk '{ print $1 }')


[[ $PND_FSTYPE = '#' ]] && PND_FSTYPE=$(file -b "$PND" | awk '{ print $1 }')

 

[Linux-SWAT]

Was:

[[ $PND_FSTYPE = '#' ]] && PND_FSTYPE=$(file -b "$PND" | awk '{ print $2 }')

Thank you VERY much !


Do you think it's something that can be upstreamed ?


It's harmless for Zaxxon, and may help on other distros too.

 

[mcobit]

Any news about the sdinstaller?

 

[Linux-SWAT]

I searched here and there, but i found nothing about knowing which slot is used :/


If i'm not wrong, when not using the mmc_core.removable=0, blk0 was left, and blk1 right, whatever the insertion order.


But as we now need this kernel option to get the suspend to ram, i feel stuck.


This is a bit scary because i have to put hundreds of warnings, and i really don't want to wipe out anyone's data.

 

[sebt3]

Do you think it's something that can be upstreamed ?

Debian, arch, angstrom, redhat and a few others distro dont have the problem. this sound like a slackware only issue.

 

[Linux-SWAT]

Good news, Slackers.


Thank to sebt3, the pnd compatibility is extended. Grab the package and update:


http://pandorawiki.o...pecific_updates


-EDIT:


You can also apply it to -current.

 

[Linux-SWAT]

Hey ! You have an issue with my name !


Well i'll ask anyway as it's harmless.

 

[Linux-SWAT]

About the bluetooth, still the same old problem.


Running the official script twice in a row gives:

bash-4.2# sh op_bluetooth.sh

Can't get device info: No such device

Texas module LMP version : 0x03

Texas module LMP sub-version : 0x1126

internal version freeze: 38

software version: 2

chip: brf6300 (4)

Opening firmware file: /etc/firmware/brf6300.bin

Uploading firmware...

Firmware upload successful.

Device setup complete

1718

1749

Can't set scan mode on hci0: Network is down (100)


bash-4.2# hciconfig

hci0: Type: BR/EDR  Bus: UART

BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0

DOWN INIT RUNNING

RX bytes:0 acl:0 sco:0 events:0 errors:0

TX bytes:28 acl:0 sco:0 commands:7 errors:0


bash-4.2# sh op_bluetooth.sh

Wanted to write 4 bytes, could only write 0. Stop

Can't initialize device: Success

1718

1749

hci0

Can't init device hci0: Connection timed out (110)


bash-4.2# hciconfig

hci0: Type: BR/EDR  Bus: UART

BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0

DOWN

RX bytes:0 acl:0 sco:0 events:0 errors:0

TX bytes:112 acl:0 sco:0 commands:23 errors:0

 

[Linux-SWAT]

That's tricky, i re-checked all this, and still the same result.


Googling around gave nothing.

 

[Linux-SWAT]

Ok fixed now, was a problem with /pandora/scripts/op_bluetooth files.


Another ambush:


When using a self-compiled or the rootfs fbgrab, i have this

 

[Linux-SWAT]

I also noticed that the MHz settings are not taken into account at start.


What is supposed to do those settings ?


I see that the config file is /etc/pandora/conf/cpu.conf, but what launches it ?

 

[Linux-SWAT]

Why is the color 16 bit instead of 24/32 ?

 

[Linux-SWAT]

I have a problem compiling xf86-video-omapfb with gcc-4.7.1 and xorg-server-1.12.2, and using the --enable-neon.


I patched as usual:


./autogen.sh


patch -p1 < ../0001-blacklist-tv-out.patch


patch -p1 < ../0002-Revert-Set-virtual-size-when-configuring-framebuffer.patch


patch -p1 < ../0003-force-plain-mode.patch


./configure --prefix=/usr --enable-neon


make

/tmp/cczHBooL.s: Assembler messages:

/tmp/cczHBooL.s:178: Error: selected processor does not support ARM mode `vld1.u8 {d0},[ip]!'

/tmp/cczHBooL.s:181: Error: selected processor does not support ARM mode `vld1.u8 {d1},[r4]!'

/tmp/cczHBooL.s:182: Error: selected processor does not support ARM mode `vld1.u8 {q1},[r2]!'

/tmp/cczHBooL.s:183: Error: selected processor does not support ARM mode `vzip.u8 d0,d1'

/tmp/cczHBooL.s:184: Error: selected processor does not support ARM mode `vld1.u8 {q2},[r1]!'

/tmp/cczHBooL.s:185: Error: selected processor does not support ARM mode `vst2.u8 {q0,q1},[r3]!'

/tmp/cczHBooL.s:186: Error: selected processor does not support ARM mode `vmov.u8 q1,q2'

/tmp/cczHBooL.s:187: Error: selected processor does not support ARM mode `vst2.u8 {q0,q1},[r0]!'

/tmp/cczHBooL.s:234: Error: selected processor does not support ARM mode `vld1.u8 {d0},[ip]!'

/tmp/cczHBooL.s:237: Error: selected processor does not support ARM mode `vld1.u8 {d1},[r4]!'

/tmp/cczHBooL.s:238: Error: selected processor does not support ARM mode `vld1.u8 {q1},[r2]!'

/tmp/cczHBooL.s:239: Error: selected processor does not support ARM mode `vzip.u8 d0,d1'

/tmp/cczHBooL.s:240: Error: selected processor does not support ARM mode `vld1.u8 {q2},[r1]!'

/tmp/cczHBooL.s:241: Error: selected processor does not support ARM mode `vst2.u8 {q0,q1},[r3]!'

/tmp/cczHBooL.s:242: Error: selected processor does not support ARM mode `vmov.u8 q1,q2'

/tmp/cczHBooL.s:243: Error: selected processor does not support ARM mode `vst2.u8 {q0,q1},[r0]!'

make[2]: *** [image-format-conversions.lo] Error 1

make[2]: Leaving directory `/root/xf86-video-omapfb/src'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/root/xf86-video-omapfb'

make: *** [all] Error 2

Works without neon.

 

[pndrafan]

Hello, just got OP and installed Slackware. I'm totally new to Slack. Noticed port 6000 is open by default. What is the best way to turn this port off?


I checked /etc/X11/xdm/xdm-config, but DisplayManager.requestPort: is set to 0 there.


Thanks. Slackware is working great so far on the Pandora!