The Cache: Technology Expert's Forum
 
*
Welcome, Guest. Please login or register. August 20, 2008, 01:00:58 PM

Login with username, password and session length


Pages: [1]
  Print  
Author Topic: Muse Receptor Hacks  (Read 844 times)
perkiset
Olde World Hacker
Administrator
Lifer
*****
Online Online

Posts: 4852


Stars & Stripes! STARS & FRAGGIN STRIPES MAN!


View Profile
« on: May 13, 2008, 06:20:15 PM »

The Muse Receptor is simply a Linux box running VST plugins under Wine on RedHat 8. So I wanted to get in and muck about, and had difficulty at first. But I found a couple threads and pages that pushed me in the right direction.

Best one is here: http://ogg.kicks-ass.net/receptor/

but the most important first step is to get root access to the box. Instructions follow:

  • Connect VGA monitor and keyboard to Receptor
  • Start Receptor and interrupt the Grub bootloader by pressing the 'e' key as it shows up - might have to press and hold immediately, which also might leave lots of "e"s on the boot line editor... make sure you don't mess with the boot instructions - just press ESC to go back to the boot command list
  • Edit line 2, and add the number '1' after the kernel line, and press enter. The line should read:
    kernel /vmlinuz ro root=/dev/hda2 vga=0x317 splash=silent ide0=ata66 1
    when you're done, press ENTER to exit edit mode
  • Press 'b' to boot the selected and modified line - it will go through it's normal boot cycle but will end up in single user mode rather than the Receptor application.
  • Use the 'passwd' utility and to change the root password.
  • You'll want the root user to be able to ssh in, so edit /etc/ssh/sshd_config and un-comment the PermitRootLogin yes line. (VI is on the Receptor) Exit VI when this is done.
  • Add sshd to the startup sequence with this command: chkconfig --add sshd
  • Reboot the receptor

At this point the receptor will reboot into it's normal mode and the Receptor application will start - but you'll be able to SSH in and will no longer need a monitor and keyboard.

Just for the info: The linux kernel version is 2.4 and XFree86 is 4.2.

Next up: I'm going to get a touch screen monitor and try to interface with it so that I can take my Mac out of the loop for live applications.
Logged
thedarkness
Global Moderator
Lifer
*****
Offline Offline

Posts: 564



View Profile
« Reply #1 on: May 22, 2008, 06:34:59 PM »

kernel /vmlinuz ro root=/dev/hda2 vga=0x317 splash=silent ide0=ata66 1


kernel /vmlinuz ro root=/dev/hda2 vga=0x317 splash=silent ide0=ata66 single

is another way to write the line just FYI.

Looks like a some of the dev stuff for this (plugins etc.) is in C++ perk, sing out if you need a hand.

Cheers,
td
Logged

"I want to be the guy my dog thinks I am."
 - Unknown
perkiset
Olde World Hacker
Administrator
Lifer
*****
Online Online

Posts: 4852


Stars & Stripes! STARS & FRAGGIN STRIPES MAN!


View Profile
« Reply #2 on: May 22, 2008, 08:36:55 PM »

TD what exactly does that line mean? I've never played with the login/bootstrap stuff on the front side of a Linux box, so I was very hesitant here.

Essentially, when I power up the box (if I have a monitor attached) then I see the very very beginnings of the bios loader and the moment it goes to grub there's a splash screen and I can see nothing else. Next thing we know the primary application is up with mouse control - but no GNOME or KDE to speak of.

I'd like to be able to run another app on the box temporarily - I'll need to calibrate a capacitive touch screen I am purchasing for it, but have no idea on how to go about it. Do you have a moment to give me a primer on how/what/why the startup is what it is, and how I might be able to hotwire something of my own for a bit?

TIA,
-p

Logged
thedarkness
Global Moderator
Lifer
*****
Offline Offline

Posts: 564



View Profile
« Reply #3 on: May 24, 2008, 09:10:38 PM »

Sure perk, love to.

Have a look in /boot/ and tell me what is in there. Can you get into the bios? Boot from CD or USB?

let me know what's in /boot/ anyway to get started.

"kernel /vmlinuz" says look for a vmlinuz* kernel image in the root of the device "ro root=/dev/hda2" which is to be mounted read only. "vga=0x317" video mode (prolly frramebuffer) their should be lists of these modes on the net. http://forums.scotsnewsletter.com/index.php?showtopic=10793 for "splash=silent". "ide0=ata66" specifying the type of HDD controller I think. "1" or "single" is specifying the runlevel to start in, you can use 3 or 5 or whatever (but not 6 which is reboot.... that would be bad :-) )

Cheers,
td
Logged

"I want to be the guy my dog thinks I am."
 - Unknown
perkiset
Olde World Hacker
Administrator
Lifer
*****
Online Online

Posts: 4852


Stars & Stripes! STARS & FRAGGIN STRIPES MAN!


View Profile
« Reply #4 on: May 25, 2008, 01:52:58 AM »

Have a look in /boot/ and tell me what is in there. Can you get into the bios? Boot from CD or USB?

let me know what's in /boot/ anyway to get started.
Haven't tried to get to the bios... but I'll do that and check the /boot dir tomorrow.


"kernel /vmlinuz" says look for a vmlinuz* kernel image in the root of the device "ro root=/dev/hda2" which is to be mounted read only. "vga=0x317" video mode (prolly frramebuffer) their should be lists of these modes on the net. http://forums.scotsnewsletter.com/index.php?showtopic=10793 for "splash=silent". "ide0=ata66" specifying the type of HDD controller I think. "1" or "single" is specifying the runlevel to start in, you can use 3 or 5 or whatever (but not 6 which is reboot.... that would be bad :-) )
Hmmmm... so by adding the "1" at the end, I forced it into single user mode ... I didn't realize that this was run-level 1. So by adding a 3 at the end, I should be able to boot into text mode and 5 into X, correct?

It is my assumption that the drivers for the touch screen will need to be calibrated, but then I won't need to touch them again - I assume I can put the driver starter into... what, rc2 or something? What would the default run level be? How can I tell that?

Thanks man
Logged
thedarkness
Global Moderator
Lifer
*****
Offline Offline

Posts: 564



View Profile
« Reply #5 on: May 25, 2008, 11:38:53 PM »

Haven't tried to get to the bios... but I'll do that and check the /boot dir tomorrow.

'k

Hmmmm... so by adding the "1" at the end, I forced it into single user mode ... I didn't realize that this was run-level 1. So by adding a 3 at the end, I should be able to boot into text mode and 5 into X, correct?

Spot on.

It is my assumption that the drivers for the touch screen will need to be calibrated, but then I won't need to touch them again - I assume I can put the driver starter into... what, rc2 or something? What would the default run level be? How can I tell that?

Look at /etc/inittab, it should look something like this;

Code:
# Default runlevel. The runlevels used by RHS are:
#   0 - halt (Do NOT set initdefault to this)
#   1 - Single user mode
#   2 - Multiuser, without NFS (The same as 3, if you do not have networking)
#   3 - Full multiuser mode
#   4 - unused
#   5 - X11
#   6 - reboot (Do NOT set initdefault to this)
#
id:5:initdefault:

Hopefully they tell you if they've done anything funky with the run levels (or hopefully they are standard). The last line I've posted there, the one that starts with "id" tells you what the default runlevel is, in this case 5.

Try 2 or 3 and see how you go, you might be able to run the driver calibration software once and be good.

Cheers,
td
Logged

"I want to be the guy my dog thinks I am."
 - Unknown
Pages: [1]
  Print  
 
Jump to:  

Perkiset's Place Home   Best of The Cache   phpMyIDE: MySQL Stored Procedures, Functions & Triggers
Politics @ Perkiset's   Pinkhat's Perspective   
cache
mart
coder
programmers
ajax
php
javascript
Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC
Seo4Smf v0.2 © Webmaster's Talks


Valid XHTML 1.0! Valid CSS!