You are not logged in.
Tried the new method recently posted in the Wiki and I'm having the same problem of USB-SD cards not mounting properly so I reinstalled my previous 3 method.
Offline
So, here is an idea...Since there seems to be questions as to which parts to modify, and in what order, etc. Can somebody with better linux skillz than I have write a script that does the following:
Backs up current startsimple.sh and startfull.sh files, and then writes the changes into both files, in the correct order? Then we can just download the script and run it. Also, if there needs to be a change to the script when somebody finds some other cool tweak, it can have a version number and be updated.
Just a thought.
Offline
lucboucim wrote:
Tried the new method recently posted in the Wiki and I'm having the same problem of USB-SD cards not mounting properly so I reinstalled my previous 3 method.
Sadly, I am also having this problem. Is there a way to fix this or do I have to go back again?
Offline
I messed up the install somehow -- I think by missing "step 0" the first time, and now I cannot set up advanced mode.
I tried restoring to defaults (F9), and it did do so, and then I tried again to install Advanced mode properly, WITH "Step 0" but nothing has changed.
I get many prompts to resolve discrepancies, but they won't resolve.
What can I try next?
Thanks.
Offline
Well, I did method one first, followed by 3 and lastly, I followed the new method and everything works great. Maybe it's the order? I don't know. Or maybe you could revert to the original and do the process over.
Offline
There is again another method (somewhere in this forum), by choosing the kdebase package after u select the package manager by
keying kdesu synaptic within a console.
Offline
Used method 3 and it boots into advanced mode after restart. However as now stated in the wiki I have no USB / SDHC detection. I guess more hapens when easy mode lanches than has been writen into the script.
The fact that when you change to easy mode the detection happens twice sugests that whatever code thats suposed to run on the launch of the advanced mode is running on exit.
I noticed startfull.sh has to have "/opt/xandros/bin/start_netserv " I guess there is another one for the USB / SDHC detection (not found it yet, hope someone else is looking).
I can live with this for now as the new script keeps my desktop icons. and if I want to use the SDHC card then I have to do some switching.
Last edited by alanking (2007-11-13 7:41:05 am)
Offline
alanking wrote:
The fact that when you change to easy mode the detection happens twice sugests that whatever code thats suposed to run on the launch of the advanced mode is running on exit.
I reconnected a USB drive five times in Advanced Desktop with nothing happened, but after switching to Easy Mode, the dialogue for those five times appeared together, along with the latest sixth. So it appears that the Advanced Desktop is seeing the USB drives, but something is missing which allows the process to complete.
Offline
You guys are starting to worry me. I used method 1 followed by 2 and only use advanced. I don't have an SDHC card to test but I do have a 2GB non-SDHC card and it is recognized every time. Are you saying that once I get an SDHC card it might not work any longer? Also when I plug my USB mouse in it works immediately. Should this convince me that I have USB detection, or again are you referring to detection of specific USB devices?
Offline
Workaround for no automount in advanced mode
Enter these commands into the terminal. (If you open file manager and select “Open Console Window” from the “Tools” menu you will be able to copy and paste)
mkdir /home/user/SD
mkdir /home/user/USB
sudo mount /dev/sdb1 /home/user/SD
sudo mount /dev/sdc1 /home/user/USB
The code above first creates 2 new directories in the “My Home” folder called SD and USB it then mounts a USB Stick and an SD card at those folders. If either device is not plugged in error messages will occor but no harm will be done
You must unmount the devices before unplugging them (or power down the machine) to unmount use these commands:
sudo umount /dev/sdb1
sudo umount /dev/sdc1
You have to hit the refresh button in file manager to see mount/umount changes
Offline
docprego
it's method 3 (1 then 3 if you count package updates) that screws up automount, and method 2 has been removed from the wiki anyway, but you can find it in these forums. The advantage of method 3 is the fast boot and and being able to switch back to easy mode...................
I have just tried method 2 which I assume to be the one from lucboucim
post no 33
and it all works and brings up the advanced desktop in 35 secs, but looks like its doing a dual boot to me.
Last edited by alanking (2007-11-13 11:03:38 am)
Offline
alanking wrote:
I have just tried method 2 which I assume to be the one from lucboucim
post no 33
and it all works and brings up the advanced desktop in 35 secs, but looks like its doing a dual boot to me.
And it's something in that double-boot that allows it to detect SD cards. When I get some spare time, I'll see if I can isolate it, but I'm stuck in a boot loop and debating between F9 and www.pendrivelinux.com (if I can use my camera as a card reader
). I hope there are other's looking as well. Otherwise, we could add alanking's mount steps to the script.
Offline
The EEE is obviously still detecting the USB drives, and my other USB devices, including mouse and external keyboard all still work automatically. It's not worth F9'ing due to these reasons I don't feel, as someone's bound to come up with the fix sooner or later, and until then it's only a slight inconvenience of switching to Easy Desktop where the automount will work to access external drives.
Offline
Updated:
SD mounts properly using the mount command.
DVD writer connected via USB isn't being detected unless I enable easy mode and switch back to full desktop. I clicked on the disk icon and ejected it, which it did. I also unplugged the writer and plugged it in the USB again and the autodetect worked.
Last edited by lorsban (2007-11-13 10:54:58 pm)
Offline
Purely through trial and error, this is the script that works for me:
startfull.sh:
change "tmp/kdesession" to "home/user/.kdesession" in order for it to survive a reboot
startsimple.sh:
#!/bin/sh
sudo /usr/bin/sessreg -d -l :0.0 -u /var/run/utmp user
xhost + si:localuser:root # Allow local user root only to access the diplay
if [ -f /home/user/.kdesession -a ! -f /home/user/.easysession ]; then #changed from /tmp to /home/user in order to survive a reboot
sudo /usr/bin/sessreg -a -l :0.0 -u /var/run/utmp user
[ -f /usr/bin/dispwatch ] && /usr/bin/dispwatch &
for i in /sys/block/s[dr]?/uevent ; do
sudo /bin/sh -c "echo add > $i"
done
(sleep 8; /opt/xandros/bin/start_netserv) & #added to support windows network
(sleep 16; /usr/local/bin/asusosd) & #added to support display-related events
sudo rm -f /tmp/nologin #changed to not kill the .kdesession file, so it will boot into the last mode used
exec startkde
else
sudo /usr/bin/sessreg -a -l :0.0 -u /var/run/utmp user
if [ -f /home/user/.easysession ]; then
# we are switching from full to easy mode
sudo rm -f /home/user/.kdesession #added, so that it will not boot into advanced mode, now that we've switched back to easy mode
for i in /sys/block/s[dr]?/uevent ; do
sudo /bin/sh -c "echo add > $i"
done
fi
/opt/xandros/bin/AsusLauncher &
icewmtray &
[ -n "$XIM_PROGRAM" ] && $XIM_PROGRAM &
powermonitor &
minimixer &
networkmonitor ath0 eth0 &
wapmonitor &
(sleep 3; /usr/bin/keyboardstatus) &
(sleep 8; /opt/xandros/bin/start_netserv) &
(sleep 16; /usr/local/bin/asusosd) &
sudo rm /tmp/nologin
[ -f /usr/bin/dispwatch ] && /usr/bin/dispwatch &
exec icewm
fi
I've removed the section that deals with the first run (which must already be complete, if you're editing your script), and the sections that mess with the desktop, since they don't seem necessary (and don't work anyway).
I've updated the wiki. Please try it and let us know if it works for you, or if you experience other side-effects. No guarantees and, as always, don't forget to backup your existing scripts before making changes. I'd also suggest having a bootable CD, SD or USB card that allows you read-write access to the EeePC's filesystem, so you can easily recover.
Last edited by deadDuck (2007-11-14 10:26:34 am)
Offline
Hey, it works! 30sec boot, autoreads sd, usb, plug in dvd writer. Awesome job!
I wonder if anyone could post the stock scripts for startfull.sh and startsimple.sh? That way anyone can just cut and paste in case anything goes wrong.
Last edited by lorsban (2007-11-14 4:13:49 am)
Offline
deadDuck wrote:
P
Edit: I've updated the wiki. Please try it and let us know if it works for you, or if you experience other side-effects. No guarantees and, as always, don't forget to backup your existing scripts before making changes. I'd also suggest having a bootable CD, SD or USB card that allows you read-write access to the EeePC's filesystem, so you can easily recover.
My flash drive won't properly load, "You do not have enohgh permissions to read /home/user/FlashDisc". Not sure if this is a side effect or not, this is my first time connecting a flash drive. The flash disk I tried was a Memorex FlashDisc v 1.04 (15.5MB).
On the flipside, my IOGEAR MicroSD reader with a 2G PNY card loads fine with no permission errors.
How odd, maybe this behavior is normal.
Last edited by godofnightmares (2007-11-14 10:10:58 am)
Offline
Someone asked for the standard startsimple.sh. This seems to be it: (use your own backed up copy, though). I've added comments to explain what each part seems to do.
#!/bin/sh #identifies this file as a shell script
sudo /usr/bin/sessreg -d -l :0.0 -u /var/run/utmp user #deletes the user session variable
xhost + si:localuser:root # Allow local user root only to access the diplay
if ! [ -f /home/user/.firstrundone ]; then # Runs only once. This section can be removed.
sudo /usr/bin/sessreg -a -l :0.0 -u /var/run/utmp user # sets a new user session variable.
sudo /usr/bin/firstrunwizard # runs the wizard
if [ $? -eq 0 ]; then # if successful
touch /home/user/.firstrundone # adds this file in the user's home directory
else
sudo /bin/kill -USR2 1 # ???
fi
elif [ -f /tmp/kdesession -a ! -f /home/user/.easysession ]; then # if the user is switching from easy mode to advanced mode. Clicking on the Full Desktop button in the shutdown dialog of easy mode runs startfull.sh, which creates the file /tmp/kdesession. This is on the tmp filesystem, meaning it doesn't survive a reboot.
sudo /usr/bin/sessreg -a -l :0.0 -u /var/run/utmp user # the the user session variable
if [ ! -d /home/user/Desktop ]; then # if the Desktop directory (contains your desktop) doesn't exist
if [ -d /home/.Desktop ]; then # if the hidden Desktop directory exists (which is created below)
mv /home/user/.Desktop /home/user/Desktop # restore the Desktop
fi
fi # this section doesn't actually work. Something must be creating an empty desktop when the computer starts up, so this section can be removed entirely, starting at if [ ! -d ...
[ -f /usr/bin/dispwatch ] && /usr/bin/dispwatch & # this is a display-related utility
for i in /sys/block/s[dr]?/uevent ; do # for every drive (sda, sdb, etc) that contains a uevent
sudo /bin/sh -c "echo add > $i" # ???
done
sudo rm -f /tmp/kdesession /tmp/nologin # remove the kdesession and nologin files. allows you to switch back to easy mode
exec startkde
else # if we're starting the computer from off, or switching from advanced mode to easy mode
sudo /usr/bin/sessreg -a -l :0.0 -u /var/run/utmp user # set the user session variable
if [ -d /home/user/Desktop ]; then # if the desktop exists
if [ -d /home/user/.Desktop.bak ]; then # if there's a backup desktop
rm -rf /home/user/.Desktop.bak # delete the backup
fi
if [ -d /home/user/.Desktop ]; then # if the hidden desktop directory exists
mv /home/user/.Desktop /home/user/.Desktop.bak # back it up
fi
mv /home/user/Desktop /home/user/.Desktop # remove the desktop to the hidden desktop directory
fi # this simply has the effect of killing your desktop, since the restore doesn't work. This whole section can be removed, starting from if [ -d /home ...
if [ -f /home/user/.easysession ]; then
# we are switching from full to easy mode
for i in /sys/block/s[dr]?/uevent ; do # for each drive (sda, sdb, etc)
sudo /bin/sh -c "echo add > $i" # ???
done
fi
/opt/xandros/bin/AsusLauncher & # run the AsusLauncher (easy mode "desktop")
icewmtray & # and the tray program
[ -n "$XIM_PROGRAM" ] && $XIM_PROGRAM & # and the input method editor
powermonitor & # and the power monitor
minimixer & # and the volume manager
networkmonitor ath0 eth0 & # and the network monitor
wapmonitor & # and this
(sleep 3; /usr/bin/keyboardstatus) & # and the keyboard status (numlock, capslock indicators)
(sleep 8; /opt/xandros/bin/start_netserv) & # and the netserv utility (for windows networks?)
(sleep 16; /usr/local/bin/asusosd) & # and this display utility (to respond to function keys? eg. volume up/down, mute, wireless on/off, etc.)
sudo rm /tmp/nologin # remove the nologin file (probably to allow people who aren't automatically logged in to switch from easy to advance mode and back with logging in each time.
[ -f /usr/bin/dispwatch ] && /usr/bin/dispwatch & # run the display utility
exec icewm # and launch the window manager
fi
Offline
Sorry for the crosspost, you're all going to hate me... ![]()
I managed to install Advanced Mode. I haven't modified the scripts yet, or do the "double boot" thing displayed in the wiki. I've managed to get into Advanced Mode once; I then restarted, and got sent into Easy Mode as expected. Going back into Advanced Mode has put me into an endless reboot sequence, which doesn't terminate until I hit the power button. Firing the Eee back up afterwards puts me back in endless reboot - I can't even get to Easy Mode. My old post was here.
Can anyone tell me what's going on and how to fix it? I really want to tinker with Advanced, but it hates me.
Offline
Duck, Thanks for your continued work on this! It's greatly appreciated. I do have one request though:
When a user comes to this site and goes to the WIKI and sees the advanced desktop mode how to, they are going to go for it, thinking that it is a reliable source. As we have found with your previous script, it did one thing, but caused problems in another area. I would request that we keep the WIKI "Gold" with scripts and procedures that we know work. Post mods here, let it ride for a day or so til all the bugs get worked out, THEN update the WIKI with known good configs. That way, a newb won't come in and hose up their eee right out the gate. I know that at this point, I have enough programs and time invested in my e, that I don't want to do an F9 reset if I get stuck in a boot loop. I'm sure others are probably in the same position.
Thanks man!
Offline
paradigm wrote:
Going back into Advanced Mode has put me into an endless reboot sequence, which doesn't terminate until I hit the power button. Firing the Eee back up afterwards puts me back in endless reboot - I can't even get to Easy Mode.
Can anyone tell me what's going on and how to fix it? I really want to tinker with Advanced, but it hates me.
What I had to do was: disconnect the battery for a moment (with the power off). Then turn it back on and press F9 immediately. Once it was back to factory settings, I tinkered.
I was also able to get Ubuntu 7.10 to boot from a 2GB SD card. I could then edit my EeePC's file (found in /media/system) and I could have fixed the offending startsimple.sh script from there.
As a suggestion, if you're tinkering take it slowly. Just change one or two things at a time and see what they do. And don't install or change a bunch of other things, if there's some chance you might end up in a boot loop and/or reset to factory settings for any reason.
Offline
deadDuck wrote:
What I had to do was: disconnect the battery for a moment (with the power off). Then turn it back on and press F9 immediately. Once it was back to factory settings, I tinkered.
As a suggestion, if you're tinkering take it slowly. Just change one or two things at a time and see what they do. And don't install or change a bunch of other things, if there's some chance you might end up in a boot loop and/or reset to factory settings for any reason.
I can restore factory settings easily enough, but I'm trying to get Advanced to work reliably and every time I try, it lands me in an endless reboot. All I'm doing is following the instructions in the Wiki, and it's not getting me anywhere. Hence the whining :p
Offline
TheBronze wrote:
I would request that we keep the WIKI "Gold" with scripts and procedures that we know work. Post mods here, let it ride for a day or so til all the bugs get worked out, THEN update the WIKI with known good configs.
I agree 100%. Maybe I just got excited. Anyway, the wiki is at least in better shape now than it was last time we thought we had it working. And, in defence of my frequent editing of "method 2 & 3", I hope that a newbie would only try "method 1", which was never changed and which always worked well. (At least, well enough for most people.)
Method 2 was, imho, never really any different in RESULTS from method 1 and method 3 never really worked fully. I hope it's working now and appreciate anyone willing to risk testing it on their EeePC. All I can say is that it works for me.
Offline
Paradigm,
I got stuck there once too. Had to do an F9 reset
This is an unfortunate state of this OS. In a typical Linux distro, you could hit CTL+ALT+F1 and get a command prompt and then edit your files back to their original config, or fix your error. For whatever reason, that feature is not present here.
So...F9 during the POST will bring up the restore screen. It will wipe any data and settings you may have had in place. It only takes a few minutes to run though, so you will be back up in no time. Once you are done, I would suggest doing a copy paste of the startsimple.sh of your choice. Backup your original using this command from the /user/bin directory "cp startsimple.sh startsimple.orig" - or whatever file name you want it to be. Then use nano to edit the startsimple.sh file. You can copy the script text from a browser on your e and then paste it into the editor. Unfortunately, I haven't figured out how to delete all the text in the original one other than using backspace or delete. haha. Once the file is clear, right click with mouse and select paste. Then ctrl O to save, and ctrl X to exit. reboot.
As a side, I have been fairly successful in using the startsimple.sh text from page 2, posted by lucboucim.
Good luck!
Offline
paradigm wrote:
I can restore factory settings easily enough, but I'm trying to get Advanced to work reliably and every time I try, it lands me in an endless reboot. All I'm doing is following the instructions in the Wiki, and it's not getting me anywhere. Hence the whining :p
Did you install kdebase or ksmserver and kicker? I assume you did, since you got into advanced mode once.
Did you back up your scripts? sudo cp /usr/bin/startsimple.sh /usr/bin/startsimple.sh.bak (same with startfull.sh)
Did you edit the startfull.sh script to change from "touch /tmp/kdesession" to "touch /home/user/.kdesession"? That steps VERY IMPORTANT and missing it could cause the problem you seem to be having.
Did you copy and paste the new startsimple script, as opposed to typing it by hand?
- On your EeePC, open the web and navigate to www.eeeuser.com and go to the wiki. Open the instructions. Copy the startsimple script.
- sudo kwrite /usr/bin/startsimple.sh
- select all (ctrl-a) and paste (ctrl-v)
Offline