Slackware for Pandora 14.0

[mcobit]

Maybe you just need to add yourself to the relevant groups manually.


Maybe linuxswat can tell us what they are from his head.

 

[F_Slim]

Look at post #272 in this thread:

 

[Linux-SWAT]

maybe the step of pressing "UP" can be automated / skipped in some way? LS, can't you simply modify the responsible script? Or is this more complicated?

Will probably look at this, but when other annoyances will be resolved.

 

[Askarus]

You may be interested in the German user groups:


http://rwiki.sciview...s:r_user_groups

That's useful.


I'll keep it in mind.


Thank you for that.


As soon as I have more spare time I'll learn R.


EDIT:


My SD is named "MAIN".


If I insert it I get a MAIN and MAIN1 folder in "media".


My SD is MAIN1. MAIN is empty.


That's annoying caus playlists for music player won't work as well as emulator rom lists.

 

[Linux-SWAT]

It's probably because that one day, you removed the media without unmounting it, so the folder stayed.


Remove your card (after having unmounted ;^p), then


su


rm -rf /media/MAIN

 

[widdly]

Thanks for all your work on this Linux-SWAT. I just got my Pandora on the weekend and have installed this slackware almost straight away. I found the angstrom a bit lite for my needs, not man pages, no alsa etc.


I mainly want to use my Pandora for audio/midi stuff. It seems there are some issues with the audio in slackware. The ALSA works with some apps and the OSS works with some stuff but it seems to be inconsistent. I've gotten Puredata running with OSS and output only. Running it with ALSA gives an error "invalid parameters" when opening the output device. I've gotten ecasound running with input and output using ALSA. Using the Audacity PND under Angstrom I was able to get output only using ALSA. The same PND in slackware wont work for either OSS or ALSA.


I've got a fair bit of experience with linux development and audio drivers so I'll try and sort out these issues and share my findings. Any ideas/tips/observations on audio stuff. would be appreciated.

 

[Linux-SWAT]

Zaxxon has alsa. What do you miss on it ?


Well your help is very welcome !


I didn't managed to have a working volume slider with alsamixer, so maybe you can solve this (asoundrc ?) ?


Also, i ship a realtime kernel:


http://pandorawiki.org/Software_projects/OS/Slackware#Kernel_updates


No need to grab an update pack, all is in the rootfs.


So it's not possible to have a realtime jack server with the internal sound card, but it works with an external usb one:

 

[John D.]

So, liking SL4P so much I decided to put it on my largest, fastest SD card. But, I still want to use this card occasionally on Windows. So I partitioned it like this:


unallocated - 4MB


partition 1 - 16GB fat32 (label=Storage)


partition 2 - 14GB ext2 (label=SLACK)


partition 3 - 512MB swap


Since Win only looks at the first partition of flash media, the first partition must be the fat32 one.


I installed RC5 to the SLACK partition with no problem, all the files are there. But the card will not boot. I've tried everything I can think of, but nothing works.


I also tried editing the /etc/fstab, which I changed to show the corect partitions:


/dev/mmcblk0p2 / auto defaults,noatime 1 1


proc /proc proc defaults 0 0


devpts /dev/pts devpts mode=0620,gid=5 0 0


usbfs /proc/bus/usb usbfs defaults 0 0


tmpfs /var/volatile tmpfs defaults 0 0


tmpfs /dev/shm tmpfs mode=0777 0 0


tmpfs /media/ram tmpfs defaults 0 0


/dev/mmcblk0p3 swap swap defaults 0 0


Help?

 

[TrashyMG]

I take it you know the basics, to boot from an SD card you need to power on while holding the right trigger button and selecting to boot off SD right?


If you did know that, I'm not sure, the fstab looks good.. but I'm not familure with slackware for Pandora and surprised it doesn't use the typical boot.txt.

 

[John D.]

Ah ha! I did not edit the boot.txt (autoboot in this case) I should change the partition there. I'll give it a go. Thank you, Crow TrashyMG.

 

[John D.]

Well, nuts. That didn't work, but it was a great idea.


EDIT:


I changed the autoboot.txt file to boot.txt in hope that I might get more info. Sure did. This is what happened:

reading boot.txt


MMC: block number 0xffffa061 exceeds max(0x3aa6000)


158 bytes read


## Executing plain script at 82000000, size 158


script failed

Because it is mentioning block number size, does this have something to do with my SD card being 32GB?


Here is boot.txt:

setenv bootargs root=/dev/mmcblk0p2 ro rootwait vram=6272K omapfb.vram=0:3000K mmc_core.removable=0


ext2load mmc 0:2 0x80300000 /boot/uImage


bootm 0x80300000

 

[hmc]

On first glance I don't see a problem with your boot.txt or autoboot.txt.


Is it located on the fat32 partition in the root directory?


Probably, because it says "reading boot.txt".


One more idea:


"MMC: block number 0xffffa061 exceeds max(0x3aa6000)"


Maybe uBoot is not able to reach the ext2 partition, because it's so far away (due to the large FAT partition in between)?


If you have the time, you might try the exact same setup, but with a much smaller FAT partition and the ext2 partition beginning earlier (so totally repartitioning the card). I don't know the limits of uBoot. But if you reduce the FAT partition size to 1GB, that limit should not be a problem anymore. If it works then, you know it's such a limit. If it still doesn't work, it must be somethign else...


Some time ago I wrote a section about that topic in the Pandora Wiki. Maybe this will give you some more ideas or hints:


http://pandorawiki.org/Running_Linux_from_an_SD_card#Setting_up_mutliple-partition_SD_cards_for_booting

 

[hmc]

Oh wait, before repartitioning everything, there may be another solution:


Copy the kernel to the FAT partition and point boot.txt to the FAT partition (don't forget to change ext2load to fatload then, see the Wiki article! Then uBoot should not have a problem loading the kernel.

 

[Linux-SWAT]

Keep autoboot.txt, so you won't have to press R.


Yup, put kernel stuff on first partition.


LO compile failed with an error :/.


I'm retrying it with a full distro, in case of a missing dependency.


If it fails again, i will try the previous version, because compilation went better.

 

[Askarus]

I crashed it.


That's what I get after file system is checked:

SLACK: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY

(i.e. without -a or -p options)


**************************************************************

***An error occured during the rot filesystem check.

***You will now given the chance to log into the	

***system in single-user mode to fix the problem.

***																		

***If you are using the ext2 filesystem, running	

***'e2fsck -v -y <partition> might help					

**************************************************************

Then I can login:


Type control-d to proceed with normal startup,


(or give root password for system maintenance):


I logged in and tried: e2fsck -v-y SLACK


but all get is that the device doesn't exist.


Can I fix this or do I have to reinstall?

 

[John D.]

Thanks for the ideas hmc and Linux-SWAT. Moving the kernel to FAT was next on the list, but -


I decided to resize the FAT32 to 11GB, and it worked! Interesting that there would be some sort of "hidden" size limitation...


BTW, congrats Linux-SWAT on receiving a 1GHz Pandora!!!

 

[Linux-SWAT]

I crashed it.


That's what I get after file system is checked:

SLACK: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY

(i.e. without -a or -p options)


**************************************************************

***An error occured during the rot filesystem check.

***You will now given the chance to log into the	

***system in single-user mode to fix the problem.

***																		

***If you are using the ext2 filesystem, running	

***'e2fsck -v -y <partition> might help					

**************************************************************

Then I can login:

Type control-d to proceed with normal startup,

(or give root password for system maintenance):





I logged in and tried: e2fsck -v-y SLACK

but all get is that the device doesn't exist.





Can I fix this or do I have to reinstall?

It's

e2fsck /dev/mmcblk0p1

 

[Askarus]

It's

e2fsck /dev/mmcblk0p1

DOH!!


EDIT:


Yay!


Slackware's back.


Go for the big screen.


Thank you.


I didn't want to instal it again.


BTW:


Is it possible to make the next RC already compiled for DisplayLink (Step 2 in the manual). It took about 5 hours to do this. (I know, you compiled days)

 

[Linux-SWAT]

I will, i will.


LO didn't compiled.


Will retry.

 

[Askarus]

Why is LO such a problem?


I runs fine on Debian but Slackware is much more optimized for Pandora.


Maybe try the older version that did compile better.


(You may use your GHz Pandora for some gaming, too )