antiX installed on HP Omni Book 4150 - Page 4

TheForsaken · posted: 2010-11-25 12:10

Failed to execute login command

I thought I was so stupid to forget my user name and password but actually I haven't forgotten these information as I've never in my whole life ... it's just the laptop is trying to act smart along with antiX.

Now, I understand what happened when I first tried to enter the correct user name and password. It was so fast at that time so I couldn't read it. Now, I can.

Code: Select all

Failed to execute login command

Is what I get when I type the correct username and password. Same if I want to login as root. That's from the graphical login screen where it says"ANTIX" at the right bottom edge of the screen.

I don't know what's going on with this laptop or it could be antiX?

This is the final try, really and if no one knows what's the next step, please let me know because I started to hate the day I touched that laptop.

Thank you __{{emoticon}}__

rokytnji · posted: 2010-11-25 14:17

I ran into this after doing a liqourix kernel upgrade on my IBM A22m. Like you slim login would just loop de loop. I was able to login as root however.

From grub menu. Pick init3 boot. You will boot to before slim kicks in.

Login there. Then Login again as root user (using sux). Then try startx icewm. I was able to get into a default /user/share/icewm setup screen from there. Unfortunately, I did not figure out how to fix slim loop de loop login from there.

TheForsaken · posted: 2010-11-25 15:11

Everyone,

Please be informed that whenever I choose"init-3" mode, I got this error:

root (/dev/hda,0)
Error 23: Error while parsing number

Press any key to continue ...

I'm very sick today and I can't handle this thing anymore. I'm going to format and re-install again. If it didn't work, I really can't do this any longer, this is too much. I spent almost a month now with no success.

Thank you everyone and if someone has one last thing to tell me, please shoot. Otherwise, I'll have some rest and then decide what to do.

anticapitalista · posted: 2010-11-25 15:55

You did type only the number 3 and leave a space after the previous entry?

TheForsaken · posted: 2010-11-25 15:57

anticapitalista wrote:You did type only the number 3 and leave a space after the previous entry?

Code: Select all

root=/dev/sda1 nomce quiet nosplash vga=791 (space) 3

One space only between 791 and 3

However, nothing happened. I mean I got exactly the same options I got before. Just like that 3 did absolutely nothing.

anticapitalista · posted: 2010-11-25 16:02

Did you get the error?

TheForsaken · posted: 2010-11-25 16:04

anticapitalista wrote:Did you get the error?

Ok, let me say it again __{{emoticon}}__

When I write (3) after 791 ... there's nothing will happen and nothing will be changed. adduser does not even exist as a command. This is what it says.

When I choose init-3 mode, I got error 23 as explained previously.

So which one are we talking about?

anticapitalista · posted: 2010-11-25 16:14

To get adduser to work, you must login as root user and then type adduser.

I'm thinking that even if this works, there is some crud left on the hard disk when you installed other distros and this is stopping you getting to a gui. If that is the case then you will need to re-install making sure you completely blank the hard drive first.

Got to go, so hope others can help.

TheForsaken · posted: 2010-11-25 16:16

anticapitalista wrote:To get adduser to work, you must login as root user and then type adduser.

Already done, anticapitalista but it just does not work at all.

I'm thinking that even if this works, there is some crud left on the hard disk when you installed other distros and this is stopping you getting to a gui. If that is the case then you will need to re-install making sure you completely blank the hard drive first.

Got to go, so hope others can help.

How come if I'm formatting the whole thing before installing the new OS?

Well, looks like it's getting harder for me and you guys.

TheForsaken · posted: 2010-11-25 22:20

I re-installed antiX.

The old process:
1- Disconnected the HDD from the laptop
2- Put it in the mobile HD enclosure which has USB cable to be connected to the PC
3- Disconnected all the internal HDDs in my PC
4- Plugged the USB cable and turned the laptop's HDD on
5- Wiped the whole thing
6- Installed antiX

After the first restart, I got the grub prompt and that's all.

Code: Select all

grub>

is all what I got.

Oh man, why it's happening to me?

wayne128 · posted: 2010-11-25 23:39

When you have a grub prompt, it said Grub has already got into the MBR, which is a good news. However Grub does not know where is the partition to go to, something is missing or not properly installed, so Grub gives you a prompt and wait for your instruction.
Assuming your hard disk is good and the rest of your installation when well, then just try these steps :

1. at grub prompt type find /boot/grub/stage2 , then <enter>
you should see a list of (hd0,x) that contain partitions with grub stage 2, which is where the grub is installed at your partition that house your antiX, I have multi boot so I have a few there, you should expect only one line, you will use that line for next command:

grub> find /boot/grub/stage2
(hd0,5)
(hd0,6)
(hd0,7)
(hd0,8)
(hd0,11)
(hd0,16)

grub>

2. Next command is grub> root (hd0,5) then <enter>
you should see a line below Filesystem type is....,

grub> root (hd0,5)
Filesystem type is ext2fs, partition type 0x83

grub>

3. Next command is grub> setup (hd0) <enter>

grub> setup (hd0)
Checking if"/boot/grub/stage1" exists... yes
Checking if"/boot/grub/stage2" exists... yes
Checking if"/boot/grub/e2fs_stage1_5" exists... yes
Running"embed /boot/grub/e2fs_stage1_5 (hd0)"... 17 sectors are embedded.
succeeded
Running"install /boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,5)/boot/grub/stage2
/boot/grub/menu.lst"... succeeded
Done.

grub>

4. If you see the above you are in good shape,
final command is grub> quit <enter>
You will be back to the root prompt

[root@localhost ~]#

5. Reboot .

TheForsaken · posted: 2010-11-25 23:42

I forgot to add:

The laptop's HDD is still inside the mobile HD enclosure and still connected to my PC. I won't return it back unless I make sure it works on my PC. If it did not work on P4 with 512MB of RAM, then how it would work in P2 and 64MB of RAM?
Something that I think you guys need to know: I tried to install Ubuntu 10.04 few days back on the laptop's HDD while it's connected to my PC and it worked. I was able to restart and use Ubuntu. I did that to see whether there's something wrong in the HDD or not? it worked so at least that should tell me/us that it's working.
Note that Ubuntu uses GRUB2 and I have a feeling that GRUB is not working on that HDD while GRUB2 does.

TheForsaken · posted: 2010-11-25 23:48

wayne128 wrote:When you have a grub prompt, it said Grub has already got into the MBR, which is a good news. However Grub does not know where is the partition to go to, something is missing or not properly installed, so Grub gives you a prompt and wait for your instruction.
Assuming your hard disk is good and the rest of your installation when well, then just try these steps :

1. at grub prompt type find /boot/grub/stage2 , then <enter>
you should see a list of (hd0,x) that contain partitions with grub stage 2, which is where the grub is installed at your partition that house your antiX, I have multi boot so I have a few there, you should expect only one line, you will use that line for next command:

grub> find /boot/grub/stage2
(hd0,5)
(hd0,6)
(hd0,7)
(hd0,8)
(hd0,11)
(hd0,16)

grub>
2. Next command is grub> root (hd0,5) then <enter>
you should see a line below Filesystem type is....,

grub> root (hd0,5)
Filesystem type is ext2fs, partition type 0x83

grub>
3. Next command is grub> setup (hd0) <enter>
grub> setup (hd0)
Checking if"/boot/grub/stage1" exists... yes
Checking if"/boot/grub/stage2" exists... yes
Checking if"/boot/grub/e2fs_stage1_5" exists... yes
Running"embed /boot/grub/e2fs_stage1_5 (hd0)"... 17 sectors are embedded.
succeeded
Running"install /boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,5)/boot/grub/stage2
/boot/grub/menu.lst"... succeeded
Done.

grub>
4. If you see the above you are in good shape,
final command is grub> quit <enter>
You will be back to the root prompt

[root@localhost ~]#
5. Reboot .

Hi there,

Could you please check my previous post and see if any of what I wrote is valid or could effect your steps in your post?

Thank you __{{emoticon}}__

Edit:
To make it easier for you:

The laptop's HDD is still inside the mobile HD enclosure and still connected to my PC. I won't return it back unless I make sure it works on my PC. If it did not work on P4 with 512MB of RAM, then how it would work in P2 and 64MB of RAM?
Something that I think you guys need to know: I tried to install Ubuntu 10.04 few days back on the laptop's HDD while it's connected to my PC and it worked. I was able to restart and use Ubuntu. I did that to see whether there's something wrong in the HDD or not? it worked so at least that should tell me/us that it's working.
Note that Ubuntu uses GRUB2 and I have a feeling that GRUB is not working on that HDD while GRUB2 does.

wayne128 · posted: 2010-11-26 00:23

Your earlier post said you installed it with antiX WITHOUT internal hard disk, so I expect to see this USB drive as the first boot drive and it should be seen by antiX as (hd0) on its hard disk.

The instructions from Grub prompt is the same.
Go ahead to use them while it is attached as USB drive on your PC.

TheForsaken · posted: 2010-11-26 00:36

wayne128 wrote:Your earlier post said you installed it with antiX WITHOUT internal hard disk, so I expect to see this USB drive as the first boot drive and it should be seen by antiX as (hd0) on its hard disk.

The instructions from Grub prompt is the same.
Go ahead to use them while it is attached as USB drive on your PC.

Yes, I unplugged the internal HDDs of my PCs and the only HDD is the laptop's HDD which is inside the HD enclosure case which has USB connection.

It says sda so yes, that should be.

I'll do that and will report back.

Thanks a lot __{{emoticon}}__