cant boot linux into gui from a usb drive

[Old-Polack]

Gave PCC a try but the gui won't start after reboot.  I get the login screen like before.

OK. Starting a multi step process. First step, boot from the liveCD/DVD. In a terminal, su to root. Then to see the partition table;

[root@localhost ~]# fdisk -l                               <Enter>

Post your results, and note what is on each partition.

Example:

[root@fatman ~]# fdisk -l /dev/sde

Disk /dev/sde: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe2158f77

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1            2048     4196351     2097152   83  Linux                                         <--- Boot partition
/dev/sde2         4196352     8390655     2097152   82  Linux swap / Solaris
/dev/sde3         8390656    60819455    26214400   83  Linux                                    <--- New install / partition
/dev/sde4        60819456  1465149167   702164856    5  Extended
/dev/sde5        60821504   480251903   209715200   83  Linux                                 <--- First data partition
/dev/sde6       480253952   899684351   209715200   83  Linux                                <--- Second data partition

[docnascar]

Had to try a video. It does play in full screen now.    This driver seems to work to a point I guess.

Haven't tried the reboot thing so I"m not sure why I got dumped into the terminal login on reboot.  Also, I'm curious if I may get the ext errors again on subsequent reboots, but only time will time.

OP, I'll try your other stuff later.

[Old-Polack]

Had to try a video. It does play in full screen now.    This driver seems to work to a point I guess.

Haven't tried the reboot thing so I"m not sure why I got dumped into the terminal login on reboot.  Also, I'm curious if I may get the ext errors again on subsequent reboots, but only time will time.

OP, I'll try your other stuff later.

Get your sleep. We'll pick up on this later. 

[docnascar]

sdc1 is the usb disk with pclinux. Keep in mind sda and sdb are windows drives, but grub is not tied to them. I

Code: [Select]

[root@localhost ~]# fdisk -l

Disk /dev/sda: 250.1 GB, 250058268160 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488395055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xad48cc5d

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63   488392064   244196001    7  HPFS/NTFS

Disk /dev/sdb: 20.4 GB, 20419854336 bytes
255 heads, 63 sectors/track, 2482 cylinders, total 39882528 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000080

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63    39873329    19936633+   7  HPFS/NTFS

Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xce5973cb

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *          63    61866314    30933126   83  Linux
/dev/sdc2        61866315   156296384    47215035    5  Extended
/dev/sdc5        61866378    70043399     4088511   82  Linux swap / Solaris
/dev/sdc6        70043463   156296384    43126461   83  Linux
[root@localhost ~]# ^C


[Old-Polack]

sdc1 is the usb disk with pclinux. Keep in mind sda and sdb are windows drives, but grub is not tied to them. I

Code: [Select]

[root@localhost ~]# fdisk -l

Disk /dev/sda: 250.1 GB, 250058268160 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488395055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xad48cc5d

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63   488392064   244196001    7  HPFS/NTFS

Disk /dev/sdb: 20.4 GB, 20419854336 bytes
255 heads, 63 sectors/track, 2482 cylinders, total 39882528 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000080

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63    39873329    19936633+   7  HPFS/NTFS

Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xce5973cb

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *          63    61866314    30933126   83  Linux
/dev/sdc2        61866315   156296384    47215035    5  Extended
/dev/sdc5        61866378    70043399     4088511   82  Linux swap / Solaris
/dev/sdc6        70043463   156296384    43126461   83  Linux
[root@localhost ~]# ^C


Boot a PCLinuxOS liveCD, open a terminal, su to root, then;

[root@localhost ~]# fsck -fy /dev/sdc1                                      <Enter>

[root@localhost ~]# fsck -fy /dev/sdc6                                      <Enter>

When both have completed, try again to boot the installed system.

Post your results.

[docnascar]

Hi OP. Trying reboot soon, but got this so far.

[root@localhost ~]# fsck -fy /dev/sdc1
fsck from util-linux-ng 2.18
e2fsck 1.42 (29-Nov-2011)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdc1: 90251/1937088 files (0.1% non-contiguous), 815435/7733248 blocks
[root@localhost ~]# fsck -fy /dev/sdc6
fsck from util-linux-ng 2.18
e2fsck 1.42 (29-Nov-2011)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sdc6: 2194/2698080 files (1.3% non-contiguous), 269290/10781615 blocks
[root@localhost ~]#

[docnascar]

Still booted to the terminal login.

[Old-Polack]

Still booted to the terminal login.

Log in as root, then enter the command pcc. You'll get the ncurses version  that does the same things as the GUI version, but you have to navigate using the arrow keys, Tab, and the space bar. When you want to select something press the Enter key. Choose Display, and just like the GUI version, set the monitor first, then the graphic card, and last the resolution. When you configure the graphic card it will also ask if it should use the proprietary driver. say yes. When done leave pcc and try the startx command, or reboot.

[docnascar]

Log in as root, then enter the command pcc. You'll get the ncurses version  that does the same things as the GUI version, but you have to navigate using the arrow keys, Tab, and the space bar. When you want to select something press the Enter key. Choose Display, and just like the GUI version, set the monitor first, then the graphic card, and last the resolution. When you configure the graphic card it will also ask if it should use the proprietary driver. say yes.

Using NVIDIA driver, Did this again from terminal

When done leave pcc and try the startx command,

Typically will load GUI, but after reboot I get the terminal login.

, or reboot.

Running PCC from boot to terminal login, and then rebooting, still boots to terminal login. Startx will load GUI.

Note: Run Graphical interface at startup option is checked in PCC.

Why would the GUI fail to load but startx will load GUI? If I go back to the xorg NV driver its likely that the GUI will load on reboot.

Also, does ACPI have anything to do with this? acpi is off. I think I may have set it to that to get around the EXT errors. I can't remember.

[Old-Polack]

Log in as root, then enter the command pcc. You'll get the ncurses version  that does the same things as the GUI version, but you have to navigate using the arrow keys, Tab, and the space bar. When you want to select something press the Enter key. Choose Display, and just like the GUI version, set the monitor first, then the graphic card, and last the resolution. When you configure the graphic card it will also ask if it should use the proprietary driver. say yes.

Using NVIDIA driver, Did this again from terminal

When done leave pcc and try the startx command,

Typically will load GUI, but after reboot I get the terminal login.

, or reboot.

Running PCC from boot to terminal login, and then rebooting, still boots to terminal login. Startx will load GUI.

Note: Run Graphical interface at startup option is checked in PCC.

Why would the GUI fail to load but startx will load GUI? If I go back to the xorg NV driver its likely that the GUI will load on reboot.

Also, does ACPI have anything to do with this? acpi is off. I think I may have set it to that to get around the EXT errors. I can't remember.

From the console, log in as root, then;

[root@localhost ~]# apt-get update                              <Enter>

[root@localhost ~]# apt-get install --reinstall kdm                                <Enter>

If the kdm login manager has become corrupted, this should fix it.

Post your results.

[docnascar]

The update went well. Side Question: Should I still use ftp.nluug.nl or should we go back to ibiblio? I'm confused.
http://www.pclinuxos.com/forum/index.php/topic,112036.msg956839.html#msg956839
http://www.pclinuxos.com/forum/index.php/topic,87378.0.html

Install was successful.

Did a reboot from terminal and it booted to the login screen <bummer>.

[docnascar]

There is another message I get when booting and I"m wondering if its related.

After the Welcome 2013 a bunch of stuff loads and they say OK, then the screen goes blank and I get "agpgart-ali 0000:00:00.0: unsupported ALI chipset [10b9/1689])

I google some of this and my mobo comes up - Gigabtye K8-U
https://www.google.com/search?q=aagpgart-ali%200000%3A00%3A00.0%3A%20unsupported%20ALI%20Chipset%20%5B10b9%2F16891%5D%0A

There are post about this and nvidia. Is this related? hmm....
http://ubuntuforums.org/showthread.php?t=876737&s=bee952de2e4b821f0bd2ec9d5b451059

[Old-Polack]

There is another message I get when booting and I"m wondering if its related.

After the Welcome 2013 a bunch of stuff loads and they say OK, then the screen goes blank and I get "agpgart-ali 0000:00:00.0: unsupported ALI chipset [10b9/1689])

I google some of this and my mobo comes up - Gigabtye K8-U
https://www.google.com/search?q=aagpgart-ali%200000%3A00%3A00.0%3A%20unsupported%20ALI%20Chipset%20%5B10b9%2F16891%5D%0A

There are post about this and nvidia. Is this related? hmm....
http://ubuntuforums.org/showthread.php?t=876737&s=bee952de2e4b821f0bd2ec9d5b451059

The plot sickens!

I've never seen that particular error, but I always use motherboards with either nVidia nforce or AMD/ATI chip sets. You could try the work around suggestions from the third link... what have you got to lose?

[docnascar]

There is another message I get when booting and I"m wondering if its related.

After the Welcome 2013 a bunch of stuff loads and they say OK, then the screen goes blank and I get "agpgart-ali 0000:00:00.0: unsupported ALI chipset [10b9/1689])

I google some of this and my mobo comes up - Gigabtye K8-U
https://www.google.com/search?q=aagpgart-ali%200000%3A00%3A00.0%3A%20unsupported%20ALI%20Chipset%20%5B10b9%2F16891%5D%0A

There are post about this and nvidia. Is this related? hmm....
http://ubuntuforums.org/showthread.php?t=876737&s=bee952de2e4b821f0bd2ec9d5b451059

The plot sickens!

I've never seen that particular error, but I always use motherboards with either nVidia nforce or AMD/ATI chip sets. You could try the work around suggestions from the third link... what have you got to lose?

Any idea how I do this? Maybe I know, maybe I don't... My plan would be as follows based on my surfing and I found this link which seem to have those setting for NvAGP and what they do. Not sure how accurate it is...


If I run "sysctl -a hw.nvidia.registry",  I get a large list of setting but I don't see NvAGP in it. Also if I try "sysctl -a hw.nvidia.registry | grep NvAGP" (did I do that correctly?) I don't see any NvAGP settings.

Should I try to add "sysctl hw.nvidia.registry.NvAgp=2" line to the end of the /etc/sysctl.conf file (which has no NvAGP settings in it currently) to duplicate what was said in this thread ?

I can only use kernel agp (via the agpgart backend sis_agp) by setting NvAGP "2".

Crash recovery plan: copy sysctl.conf as a backup and if system won't boot at all, boot with  livecd and replace edited file with backed up sysctl.conf file I made.

[Old-Polack]

Any idea how I do this? Maybe I know, maybe I don't... My plan would be as follows based on my surfing and I found this link which seem to have those setting for NvAGP and what they do. Not sure how accurate it is...


If I run "sysctl -a hw.nvidia.registry",  I get a large list of setting but I don't see NvAGP in it. Also if I try "sysctl -a hw.nvidia.registry | grep NvAGP" (did I do that correctly?) I don't see any NvAGP settings.

Should I try to add "sysctl hw.nvidia.registry.NvAgp=2" line to the end of the /etc/sysctl.conf (which has no NvAGP settings in it currently) file to duplicate what was said in this thread ?

I can only use kernel agp (via the agpgart backend sis_agp) by setting NvAGP "2".

Crash recovery plan: copy sysctl.conf as a backup and if system won't boot at all, boot with  livecd and replace edited file with backed up sysctl.conf file I made.

That sounds like a plan.