No boot after upgrade

[djitts]

After upgrading to V1.8, I get a strange problem.

When the boot-up concludes, I get "Vortex Box login:" request, followed by

"Password" request.* I have no idea what to enter.

In the meantime, I can access VortexBox just fine on the Web Browser and my internet devices appear to find VortexBox, no trouble.

What I cannot do is access the Linux GUI, nor the Command prompt on the VortexBox computer.

I am guessing that I stuffed something in the boot record on the Linux machine and do not know enough about Linux to fix it.

Anybody able to give me some guidance here?* Thanks.

[Ron Olsen]

Hit the Enter key. *You should get a login: prompt. *Enter root. *You should get a password: prompt. *Enter vortexbox (or whatever password you specified if you did an iso install).

See*http://info.vortexbox.org/tiki…..Login**for other ways to login to your VortexBox.

[djitts]

Ron, you are a magician. It works fine.

Many thanks

[djitts]

Sorry Ron,

I need a bit more help.

What you told me to do worked fine in as much as I was able to get into the Command line.

However, when I type "startx", I get a lengthy error message which ends up with:
"...Fatal server error
no screens found, etc"

As far as I remember, startx worked fine to invoke the Fedora GUI before I upgraded VortexBox.

Is there an easy fix, please.

Many thanks

[Ron Olsen]

djitts said:

Sorry Ron,

I need a bit more help.

What you told me to do worked fine in as much as I was able to get into the Command line.

However, when I type "startx", I get a lengthy error message which ends up with:
"...Fatal server error
no screens found, etc"

As far as I remember, startx worked fine to invoke the Fedora GUI before I upgraded VortexBox.

Is there an easy fix, please.

Many thanks


What GUI do you have installed? Gnome? KDE? *Do you have another user ID defined on your VortexBox besides root? *Gnome and KDE won't let you login as root. You will have to login as a non-root user to bring up the GUI.

You could also edit /etc/inittab to boot directly to the GUI login screen:

Change the line


id:3:initdefault:



to


id:5:initdefault:



and reboot. *You should get the Gnome Display Manager (gdm) with a login screen. Login as a non-root user. *Then bring up Gnome terminal and su to root to get root access.

[djitts]

Thanks for your help, Ron.

Sorry, I do not know which GUI I have loaded and no, I have not used any other username or password for the VortexBox installation.

Being a complete "nubie" with Linux, it took me a little time to sort out your Linux-speak but I finally got my head around how to edit the "inittab" file and save it.

The reboot seemed to stall at "Starting DAAP Server"

In the meantime, the VortexBox is up and running. I could even access it from ITunes and maybe I should just be happy with that - feel free to tell me to get lost because I realise I might be a bit frustrating to you.

[Ron Olsen]

djitts said:

Thanks for your help, Ron.

Sorry, I do not know which GUI I have loaded and no, I have not used any other username or password for the VortexBox installation.


How did you install the GUI on your VortexBox? *Surely you remember what you did! Did you take any notes? You should have if you didn't. *Always take notes when you solve a computer-related problem! *They are invaluable for future reference.

If you don't have any other user id besides root, it's doubtful that you can login to either the Gnome or KDE GUI. *Don't know how you did this before.


Being a complete "nubie" with Linux, it took me a little time to sort out your Linux-speak but I finally got my head around how to edit the "inittab" file and save it.*The reboot seemed to stall at "Starting DAAP Server"


The reboot most likely did not stall. *There is a known issue with not getting an "OK" for the DAAP server. *But you should still get a login: prompt. *Hit Enter to get it again. Once you're logged in, try the startx command again and see what happens. *I don't know if this is going to work, since I don't know what GUI you have installed on your VortexBox. If it fails, post all the output you see on the screen.


In the meantime, the VortexBox is up and running. I could even access it from ITunes and maybe I should just be happy with that - feel free to tell me to get lost because I realise I might be a bit frustrating to you.


Glad that most things are working the way they should.

Everyone was a "nubie"*once; nothing to apologize for. *I've been using Unix and Linux for 35 years, so it's second nature to me now. *I'll be glad to help; just post detailed info on what you try and what output you get (very important) -- can't debug without it.

[djitts]

Thanks, Ron. I will try and be a lot more systematic when I indulge in Unix.

I can press Enter till I'm black in the face, but cannot get pass the DAAP server, but seeing as how I can access The VortexBox from ITunes, I guess the DAAP server is up and running.

I guess I'll just fool around a bit more, bearing your guide-lines in mind.

Again, my thanks for your kindness and understanding.

[Jon-Lars]

Hello,

I am here to beg for help.

*My VBA will no longer play through my Slim DEvices SB V3, since I updated the VBA software last week.

*I am hooked up a montor and I am seing the same error messages:



eth1: error fetching interface information: Device not found

br0: error fetching interface information: Device not found



..and the last message is the Starting DAAP server, which never leaves.

When I look at the VBA update page through http://vortexbox/upgrade.php, the last line reads

Upgrade complete. Please reboot your Vertexbox.

.. even though I have rebooted it through the GUI buttons, and by pressing & releasing the power button.



I can play back my files by accessing the VBA through my network and playing it through the computer (Puget Systems and Windows 7), so I know they are in there. I have tested my wireless router (working), switched out the cable, loaded the latest Squeezebox software (7.5.3) and (132), to no avail.



Everything was fine a week ago! What can I do now? My programming skills are limited - I'm the driver, not the mechanic.



Sorry to make this my first post, as it is pretty sad. Thanks for your support,

*Jon-Lars Sorenson

[andrew]

Hi Jon-Lars, welcome to the forum. Please make a new post when posting a new problem don't "hijack" another thread. Also for help please post to the help forum.

I am on the SqueezeBox forum a lot and have seen this happen to may SqueezeBox users. This is across all users not just VortexBox owners. Usually the solution is to factory reset your SqueezeBox. The SqueezeBox forum may be able to help your more.