Author Topic: EeePC bootup problem  (Read 2517 times)

Offline vc

  • Hero Member
  • *****
  • Posts: 519
EeePC bootup problem
« on: July 29, 2010, 02:24:42 PM »
My newer 701SD EeePC has gradually developed some sort of bootup difficulty.  Whenever I turn it on now and attempt to boot up, the kernel panics - thus forcing me to hold the power switch for several seconds in order to turn the thing off.  Yet oddly, when I almost-immediately turn the power back on again, it then boots successfully - how is that possible?  To my thinking, something is either wrong or it isn't - how could a boot partition be detectable on one attempt, but not on another?  As far as I'm aware, no changes are being made to /etc/fstab or to /boot/grub/menu.lst at all, in between.

Could someone please tell me if they've encountered similar, and also of any possible directions to proceed in?

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15847
  • LXDE! Coffee, Bacon and Cheesecake!
Re: EeePC bootup problem
« Reply #1 on: July 29, 2010, 02:57:13 PM »
Try this:
From the liveCD, logged in as root, run a fsck on the / partition.

[root@localhost ~]# fsck -f /dev/<whatever>                   <Enter>

Change the <whatever> to the correct designation for your / partition. For any questions asked, press the <Enter> key to accept the default choice.


Offline vc

  • Hero Member
  • *****
  • Posts: 519
Re: EeePC bootup problem
« Reply #2 on: July 29, 2010, 03:33:42 PM »
Thank you, Neal.  Because this unit is a 701SD model, it has only one 'drive', which is an 8GB mini-PCIe SSD module.  It was partitioned as follows:

/dev/sda1 --- 4GB --- /
/dev/sda2 --- remainder --- /home

Both partitions were formatted as ReiserFS, and are mounted with the default options, as per the attached fstab below.  Both also passed the fsck checks perfectly, with no problems being found in either.
« Last Edit: July 29, 2010, 03:36:15 PM by vc »

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15847
  • LXDE! Coffee, Bacon and Cheesecake!
Re: EeePC bootup problem
« Reply #3 on: July 29, 2010, 03:44:22 PM »
vc,
 ??? I can't think of what this might be, if it isn't a file system problem. ??? I have not had the problem and have no way to recreate it. I've moved this thread to the netbook section in the hope that some of our netbook users will have some ideas.

Offline vc

  • Hero Member
  • *****
  • Posts: 519
Re: EeePC bootup problem
« Reply #4 on: July 29, 2010, 04:06:34 PM »
Thank you, Neal.  I had posted it in the 'Advanced' section because of the GRUB-related problems I have consistently encountered on all of my other EeePC units (http://www.pclinuxos.com/forum/index.php/topic,71812.0.html), and am therefore left wondering if it may really be more due to some sort of deep-seated GRUB issue or such.  I know it is not an EeePC-specific hardware issue, as I have attempted to perform similarly-configured installations upon other hardware, and those installs all failed in the same manner, with GRUB being unable to find the boot partition upon rebooting following the installation.
« Last Edit: July 29, 2010, 04:13:28 PM by vc »

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15847
  • LXDE! Coffee, Bacon and Cheesecake!
Re: EeePC bootup problem
« Reply #5 on: July 29, 2010, 04:17:27 PM »
In your grub menu list, you have vga=314 splash=silent vga=788. Is there some special reason for the vga=314 to be there?

Offline vc

  • Hero Member
  • *****
  • Posts: 519
Re: EeePC bootup problem
« Reply #6 on: July 29, 2010, 04:28:07 PM »
In your grub menu list, you have vga=314 splash=silent vga=788. Is there some special reason for the vga=314 to be there?

EeePC.

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15847
  • LXDE! Coffee, Bacon and Cheesecake!
Re: EeePC bootup problem
« Reply #7 on: July 29, 2010, 04:30:24 PM »
Oh! I didn't know about that.

Offline vc

  • Hero Member
  • *****
  • Posts: 519
Re: EeePC bootup problem
« Reply #8 on: July 29, 2010, 04:34:45 PM »
Oh! I didn't know about that.

All of the "7-inch" EeePCs have a display resolution of 800 x 480, and many distros have encountered difficulties with that particular problem, due to the unusual mode number.

Offline Neal ManBear

  • Administrator
  • Super Villain
  • *****
  • Posts: 15847
  • LXDE! Coffee, Bacon and Cheesecake!
Re: EeePC bootup problem
« Reply #9 on: July 29, 2010, 04:51:26 PM »
I see. I've learned something new today. Thank you, vc.

Offline vc

  • Hero Member
  • *****
  • Posts: 519
Re: EeePC bootup problem
« Reply #10 on: July 29, 2010, 08:32:57 PM »
You're welcome, Neal - and thank you again for the helpful tip in the other thread, as well.  The early EeePCs were somewhat of odd ducks for hardware, and many distros seemed to have issues with them at the time.  The best fit I ever found was with Minime 08 - that install functioned very well, but has long since outlasted any modern compatibility - it cannot browse a significant number of important websites now (such as YouTube, for instance, amongst others), and it cannot be updated.  I keep that old Eee handy mostly for the memories... for more than a year, it really was my 'main' machine!  I have it completely imaged, so if I ever manage to trash anything I'm still able to restore the system entirely.  It should last about as long as the actual hardware does, and it's already survived quite a surprising amount of abuse and disaster - the keyboard is starting to wear out, legibility-wise, but Deal Extreme is still selling replacements at very reasonable prices.  I've already managed to completely burn out one SDHC card in that unit, yet the internal SSD still seems to be holding okay - and, it's also one of the very early ones, so it does have the second internal mini-PCIe SSD expansion slot connector, and I would be able to install a replacement module should the internal onboard SSD ever fail.

The only thing I didn't like about them was their crappy display resolution (and later, as I discovered, the fact that the internal mini-PCIe connector for the wifi module is BIOS-locked, so that only a useless wifi module may be installed into that port successfully.).  I couldn't see the excuse for Asus not at least offering a higher-resolution screen for a premium price - not when a 1280 x 768 screen of the same size had already been sold some years earlier, in the Toshiba U-100 series.  Those, and also the missing internal 56K analogue modem module, and the musing that the external SVGA connector could have been of so much greater use in my work had it only been a true serial port, instead.  Asus missed a good opportunity on that one - I bought that EeePC for use as a service tool, and I was the service manager of a national ATM firm at the time.  I wanted our company's field technicians to each have one, because they're small and rugged enough to survive being thrown into a toolbox; they could hold all firmware update files for every model of ATM machine in our fleet, and were capable of uploading same to same via serial connections (USB-serial dongle) or through CF cards (USB card reader on the PC side; CF-PCMCIA adapter on the ATM side); they'd run for two hours straight on a full charge, and automotive chargers are available; they play multimedia, such as training videos, and, they connect to the Internet too, through the magic of USB cellmodem dongles - so the techs could file their service reports straight into the corporate website, while still at the client's location!  And the blasted things even have a silly little webcam, that could be used to take some really crappy evidence photos in cases of ATM damage or theft... I tell you; it all seemed so *ideal*.....

And then KDE changed.  And then PCLinuxOS changed.  And then there was an ulcer, and then my employment status changed, and then more recently a stroke... and now nothing is the same, and my EeePCs are sitting idle and are unused, because I am unable to run PCLinuxOS on them in the way that I really wish to.  I can't even install 2010 to them successfully, now.  It's all becoming rather depressing.  The only machine I was able to get 2010 installed into successfully was my newer 701SD model, because it has an 8GB SSD so I didn't have to split the install across multiple drives - but now, even that install's not faring so well any longer, and so develops this booting problem....

Oh well.   :-/
« Last Edit: July 29, 2010, 09:09:44 PM by vc »

Online kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 3996
Re: EeePC bootup problem
« Reply #11 on: July 30, 2010, 03:44:02 AM »
It isn't GRUB-related. It's kernel, BIOS or hardware-related.

It sounds as if when shut down it loses some vital configuration which the initial attempt to boot sets up too late to use, so it can only be used by a second boot. How is the main and motherboard battery? Alternatively, it's shutdown-related. What happens if you reboot once it's up? Does it always fail on each alternate boot (shutdown problem) or does it have to be left for a minute/hour/day/week (battery problem)?

Clearly, GRUB can find the / partition, but the kernel can't at first attempt. That points to the chipset configuration or kernel modules.

« Last Edit: July 30, 2010, 03:45:56 AM by kjpetrie »
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline vc

  • Hero Member
  • *****
  • Posts: 519
Re: EeePC bootup problem
« Reply #12 on: August 07, 2010, 07:13:49 AM »
It isn't GRUB-related. It's kernel, BIOS or hardware-related.

I don't think so, kjpetrie - because I have tried different BIOS versions, different kernels, and even different hardware entirely; yet the problem remains reproducible overall.

Set up a machine with more than one hard drive, then attempt to perform a 'split' install with most of the system on one drive but with one of the 'system' partitions (such as /usr) on another - and observe what happens.  I think it likely that you'll end up rebooting from the live CD and then manually editing fstab, in order to enable the new installation to boot.