Hi all,

Just got my RPi! YAY

Is it possible to PXE boot the RPi?
Would putting etherboot/gPXE on the SD-Card and have the RPi boot it work?
Is etherboot/gPXE ARM compatible?

no, the raspi is not capable of pxe boot, see the faqs.

Yes, I'm aware of that.
It doesn't boot from a USB external HD either, but you can make it so by having the SD-card make the initial boot and then "transfer" the boot process to the USB HD...

I made my old pentium-III pc, which did not have a PXE-capable NIC, network-boot by booting a floppy with etherboot, which then mounted an NFS share and booted through that. (sorry for all the "boots" on the same sentence )

In theory, one could do the same with the RPi... but I have no idea if the etherboot/gPXE code is ARM compatible or not.

With ARM normally the devices use the u-boot loader which supports TFTP booting and is the method documented in the Slackware ARM install docs.
The Rpi doesn't use the u-boot loader though afaik.

This looks promising U-Boot for Raspberry Pi

Nice. Didn't know there is a slack version for the pi. I been running mine as a server for a few weeks. Cool little machine.

In the short term I found netsurf to have too many dependencies compared to dillo-3.0.2 which only required fltk-1.3.0 on my slackware arm current install. I compiled both with modified slackbuilds based on the slackbuilds for dillo-2.2.1 at slackbuilds.org which included Alien Bob's new ARCH handling code block that optimises for Pi packages. Dillo is a bit spartan and uses text files for configuration but is fast on my Pi compared to Seamonkey and Firefox. dillo-2.2.1 was based on fltk2 which apparently has been dropped by its the developers as unstable so dillo has fallen back to versioning 1.X.X.

I`ve built Midori for ARMedslack 13.37. It`s very fast compared to firefox.

http://slackware.spit-ct.ro/raspberrypi/old/extra/

Hey, cheers, I remember midori working well from your image. I couldn't get libunique to budge so took the parh of least resistance. I'll have to have another squiz, thanks for the link. Anyway I think el Cid will be happy to know dillo made it onto a pi.

I wondering if there is a bug on the "setup" program in the image "raspi-slack-installer_01Aug12.img.xz".

The installation went ok, but when choosing the default Windows manager, XFCE was not listed.
I decided to run the setup again, then realized the "xfce" series package was not listed on the PACKAGE SERIES SELECTION screen.
I verified my PACKAGES.TXT file and it contains all the XFCE packages listed there.

What could be happening?

EDIT:

I looked the "SetPKG" script, and there is no mention to XFCE. It happens that the "xfce" series is new in the 14.0 version, and the setup scripts were based on the 13.37, so they doesn't expect a XFCE option.

Yes, I installed current a couple weeks back and that was the case for me as well. I installed from /slackware on a mounted (via powered hub) usb drive. I just mounted the usb again after booting up and installed all the packages in /slackware/xfce. I think I was able to run the window manager selection ap again from the command line with something like wmsetup or wmconfig but I can't check that right now.

You are right. I did the following:

Then choose the XFCE as default

I just got my Pi yesterday and have been testing it out.
Is the Slackware ARM image only 'visible' when connected via hdmi (and ethernet)?
I have an sd card I put the raspi-slack-installer_01Aug12.img.xz image on (also tested the same card w/ the 9-18-2012 Raspbian and it works just fine) then connected my USB to Serial cable to the Pi and Putty'd to it. It doesnt do or show anything, whereas with Raspbian I would immediately see the startup messages. I'm not connecting anything else to it, in either case, like ethernet. Just wondering if I need to go out and get hdmi cables/connectors to play with Slack.

Ah, I got in. had to edit the cmdline.txt and add: console=ttyAMA0,115200 kgdboc=ttyAMA0,115200

http://demin.ws/blog/english/2012/07...-serial-cable/

1 members found this post helpful.

Here's some more info I wanted to share.
So, the Pi was still acting odd sometimes when rebooting and not presenting a screen to Putty. I read on the armedslack mailing list about copying over start.elf and loader.bin, which I did from the latest rasbpian image and that worked great, which got me to setup reliably.
I installed from a fat32 formatted usb which had slackware arm 14.0 on it.
The terminal would freeze though and become unresponsive in the normal installation, so I tried setting TERM=vt100 before running setup and picking terse messaging, that seemed to help. After nervously watching the packages scroll by, the install eventually finished.
I then ran the recommended cleanup of removing extra kernels and then mounted the boot partition and installed the raspi-extra/kernel/* /raspi-extra/raspi* packages.
Those overwrote the custom changes I had done for ttyAMA0 though!
I was then seeing the boot process finally, but hanging up on something.
So, I added loglevel=6 to the end of cmdline.txt and also (since thats where I thought I was hanging up on initially). But now I dont think I was actually hanging, I think I was still getting bit ttyAMA0 not being set up, so after some more reading/searching, I edited /etc/inittab and added:
as well as /etc/securetty to add ttyAMA0 instead of ttys0
and now I'm in...