Archived Forum

See this thread about using raspi-config from earlier today.

thanks.

But, not to offend anybody, why isn't it fixed in the so-called ready to go image? it doesn't seem to have been tested at all if it fails at the first input. It will save all you guys a lot of time and it has been around for some months now.

and I would love to do the testing of the ISO and documentation, but I don't have the knowledge to make the new ISO

Now i was able to configure it. Thanks.

I set it to boot to GUI. but now it just boots into a black screen.

Hi haden,

Setting the "raspi-config" flag so that the menu doesn't pop up is on my "wish list" for the next image which hopefully isn't too far away. This hasn't really been seen as an issue previously probably because 99.99% of OEM users use the Pi (for this application) via ssh and so they do not see the menu.

The extending of partitions and expanding rootfs will continue to be an issue as it's a complex subject that raspi-config can automate if several criteria are met which basically amount to a very basic 2 partition set-up on a SD card, once you move outside those parameters, which we do by having a 3rd partition or a harddrive,  raspi-config doesn't know what to do and therefore leaves it to the user to sort out, it's really aimed at basic systems and new users etc.

Glad you got it sorted

Thanks. if you need someone to test i be glad to help.

Is the screen supposed to be black when booted to desktop?

The "boot to desktop" mode will only work if there is a screen/keyboard connected or you use a vnc "remote desktop", It should open to a "Desktop" with a taskbar, desktop icons and a huge raspberry with a white background by default. If you start without "boot to desktop" mode enabled or just ssh in from another PC it will open a terminal window, which is all black with a command prompt, from the command prompt you can use the "startx" command to start the desktop (not over ssh) 

Early adopters & testers are always welcome as is their feedback, I'm sure Trystan will announce when a new image is in the making or available.

 Paul

I have attached the Pi to a TV using HDMI, no problem seeing the initial boot process but as it should switch to desktop it goes to a black screen. Trying with Raspbian I get a nice desktop.

Currently there is only attached keyboard/mouse and the TV as monitor

"it goes to a black screen"

Is there a command prompt ? if so what happens if you type run "startx" ?

I can't say I've ever booted the "SD card image" to a desktop directly and I can't currently get a monitor to a Pi to try it, Are there any error messages in the  initial boot process ?

There is no prompt

I will take a second look for errormessages tonight.

no errors during boot.

The last line it writes before going black is: Starting RPI

Okay did a reflash of the image and attached it to the network. I'm able to SSH to it, and it seems to be browsable :-) but still not able to see anything on the video output. could be nice if you have a screen attached.
 

Unfortunately I'm not able to do any experimenting with a screen at the moment but I have previously used a screen with read-only Raspbian although I cannot recall what mode it was in at the time maybe it was in write mode, I cannot be sure. 

Since reflashing have you tried setting raspi-config ? 1st time round you got some errors, which may of had implications that hung around after you put it in write mode. with a screen and keyboard try

skipping raspi-config menu at start up by exiting menu
log-in at the command prompt
switch to write mode using "rpi-rw" command
try manually starting gui desktop using "startx" command

if that doesn't work there may be something set in the "image" preventing it working

If does work and takes you to the desktop it's likely to either be an issue booting into desktop in read-only mode or it was just a problem caused by previously running raspi-config while in read-only mode, so try

"logging out" of gui to command prompt
confirm still in write mode using "rpi-rw"
set "boot to desktop" in the menu by using "sudo raspi-config" command
exit menu and reboot 

if it works, fantastic if not you may need to either run in write mode full time or find a work around like editing the auto-start script if you can locate it to issue "rpi-rw" before "startx"

Sorry I can't be more specific, or even sure of what i'm suggesting

Paul