Fedora Test 2 will not log in to Gnome?

[Sean Earp]

Hello all-

I have not been able to install Fedora Test 2 since it came out (RH 9 
and Severn Beta 1 worked just fine).  Today I tried installation with 
the updated Anaconda, and it works. (great!)

However, on the first boot after installation, I can not log on to the 
Gnome desktop.  KDE works just fine.   The interesting thing is that I 
chose the customized install, and had Gnome checked, and KDE UNCHECKED. 
  Just in case I missed something, I have formatted the drive 3 times 
and reinstalled, making SURE that gnome was selected, and KDE was not.  
When I attempt to log in to gnome, the screen exhibits the same 
behavior as if i choose the "restart X Server" option on the login 
screen.  Is anyone else experiencing this?  Can someone give me the 
command line option to verify that Gnome is even installed? (I'm a 
linux newbie, so be gentle)  Any assistance would be greatly 
appreciated.  Thanks,

-Sean

[seth vidal]

>  However, on the first boot after installation, I can not log on to
> the 
>  Gnome desktop.  KDE works just fine.   The interesting thing is that I 
>  chose the customized install, and had Gnome checked, and KDE UNCHECKED. 
>    Just in case I missed something, I have formatted the drive 3 times 
>  and reinstalled, making SURE that gnome was selected, and KDE was not.  
>  When I attempt to log in to gnome, the screen exhibits the same 
>  behavior as if i choose the "restart X Server" option on the login 
>  screen.  Is anyone else experiencing this?  Can someone give me the 
>  command line option to verify that Gnome is even installed? (I'm a 
>  linux newbie, so be gentle)  Any assistance would be greatly 
>  appreciated.  Thanks, 

which gnome-session

if you don't get
/usr/bin/gnome-session then it is not installed

-sv

[Thiago Vinhas de Moraes]

Dude, forget about Gnome. It sucks. Use KDE.


Em Ter, 2003-09-30 às 18:32, Sean Earp escreveu:

>  Hello all-
>  
>  I have not been able to install Fedora Test 2 since it came out (RH 9 
>  and Severn Beta 1 worked just fine).  Today I tried installation with 
>  the updated Anaconda, and it works. (great!)
>  
>  However, on the first boot after installation, I can not log on to the 
>  Gnome desktop.  KDE works just fine.   The interesting thing is that I 
>  chose the customized install, and had Gnome checked, and KDE UNCHECKED. 
>    Just in case I missed something, I have formatted the drive 3 times 
>  and reinstalled, making SURE that gnome was selected, and KDE was not.  
>  When I attempt to log in to gnome, the screen exhibits the same 
>  behavior as if i choose the "restart X Server" option on the login 
>  screen.  Is anyone else experiencing this?  Can someone give me the 
>  command line option to verify that Gnome is even installed? (I'm a 
>  linux newbie, so be gentle)  Any assistance would be greatly 
>  appreciated.  Thanks,
>  
>  -Sean
>  
>  
>  --
>  fedora-test-list mailing list
>  fedora-test-list(a)redhat.com
>  http://www.redhat.com/mailman/listinfo/fedora-test-list

[seth vidal]

On Tue, 2003-09-30 at 17:40, Thiago Vinhas de Moraes wrote:
>  Dude, forget about Gnome. It sucks. Use KDE.
>   
Dude, don't troll.

-sv

[Jim Cornette]

Sean Earp wrote:
>  Hello all-
>  
>  I have not been able to install Fedora Test 2 since it came out (RH 9 
>  and Severn Beta 1 worked just fine).  Today I tried installation with 
>  the updated Anaconda, and it works. (great!)
>  
>  However, on the first boot after installation, I can not log on to the 
>  Gnome desktop.  KDE works just fine.   The interesting thing is that I 
>  chose the customized install, and had Gnome checked, and KDE UNCHECKED. 
>   Just in case I missed something, I have formatted the drive 3 times and 
>  reinstalled, making SURE that gnome was selected, and KDE was not.  When 
>  I attempt to log in to gnome, the screen exhibits the same behavior as 
>  if i choose the "restart X Server" option on the login screen.  Is 
>  anyone else experiencing this?  Can someone give me the command line 
>  option to verify that Gnome is even installed? (I'm a linux newbie, so 
>  be gentle)  Any assistance would be greatly appreciated.  Thanks,
>  
>  -Sean
>  
>   
When I installed Severn beta1, I could not get GNOME to get further than 
the splash screen startup. This problem was related to the interaction 
with my 3Com ethernet. After the card was replaced with a 2 yr newer 
3com NIC GNOME, Mozilla and a host of other problems went away.

My guess is that GNOME is outputting to /dev/lockup (in my case it was 
my NIC). Basically, I assume that the program is outputting, but not 
even to a bit bucket (AKA - like windows blue screen.)

You might have some hardware conflicts which are causing GNOME not to start.

I filed but closed three inactive bugs which GNOME was a casualty. I got 
rid of the NIC so the bug is mre for informational, just in case 
anything was useful, within my GNOME problem.

Have you tried to boot into int level 3 and start GNOME with startx? I 
am curious if you see the splash screen, then GNOME goes no further.

Run the below from a terminal, just to be safe. I take it that you are 
using kdm, gdm or some graphical login manager.

switchdesk gnome
startx

Getting into text mode, multiuser was discussed earlier.

Hope it points you to why GNOME fails for you. KDE is my failsafe 
windows manager. I like the bluecurve changes to it. I install both.

Jim


-- 
The opposite of a correct statement is a false statement. But the opposite
of a profound truth may well be another profound truth.
		-- Niels Bohr

[Alexander Larsson]

On Wed, 2003-10-01 at 03:07, Jim Cornette wrote:
>  Sean Earp wrote:
>  > Hello all-
>  > 
>  > I have not been able to install Fedora Test 2 since it came out (RH 9 
>  > and Severn Beta 1 worked just fine).  Today I tried installation with 
>  > the updated Anaconda, and it works. (great!)
>  > 
>  > However, on the first boot after installation, I can not log on to the 
>  > Gnome desktop.  KDE works just fine.   The interesting thing is that I 
>  > chose the customized install, and had Gnome checked, and KDE UNCHECKED. 
>  >  Just in case I missed something, I have formatted the drive 3 times and 
>  > reinstalled, making SURE that gnome was selected, and KDE was not.  When 
>  > I attempt to log in to gnome, the screen exhibits the same behavior as 
>  > if i choose the "restart X Server" option on the login screen.  Is 
>  > anyone else experiencing this?  Can someone give me the command line 
>  > option to verify that Gnome is even installed? (I'm a linux newbie, so 
>  > be gentle)  Any assistance would be greatly appreciated.  Thanks,
>  > 
>  > -Sean
>  > 
>  > 
>  
>  When I installed Severn beta1, I could not get GNOME to get further than 
>  the splash screen startup. This problem was related to the interaction 
>  with my 3Com ethernet. After the card was replaced with a 2 yr newer 
>  3com NIC GNOME, Mozilla and a host of other problems went away.
>  
>  My guess is that GNOME is outputting to /dev/lockup (in my case it was 
>  my NIC). Basically, I assume that the program is outputting, but not 
>  even to a bit bucket (AKA - like windows blue screen.) 
This is very interesting. Was this a 3c590 NIC?

If so, i'm getting the same on my card. See
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=98832

It seems to be a kudzu bug, but bill couldn't reproduce it on his 3c590.
Getting more data might make this fixable.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
                   alexl(a)redhat.com    alla(a)lysator.liu.se 
He's a scarfaced Catholic sorceror from the Mississippi delta. She's a 
tortured French-Canadian soap star with an evil twin sister. They fight crime!

[Jim Cornette]

The bug was with an:

EtherLink XL PCI
3C900B-TPO
03-0147-000
REV-A

bugs 104793 through 104795 contain information regarding the check cable 
and avalanche effects for the NIC card.

Jim

-----------------------

Alexander Larsson wrote:
>  On Wed, 2003-10-01 at 03:07, Jim Cornette wrote:
>  
> >Sean Earp wrote:
> >
> >>Hello all-
> >>
> >>I have not been able to install Fedora Test 2 since it came out (RH 9 
> >>and Severn Beta 1 worked just fine).  Today I tried installation with 
> >>the updated Anaconda, and it works. (great!)
> >>
> >>However, on the first boot after installation, I can not log on to the 
> >>Gnome desktop.  KDE works just fine.   The interesting thing is that I 
> >>chose the customized install, and had Gnome checked, and KDE UNCHECKED. 
> >> Just in case I missed something, I have formatted the drive 3 times and 
> >>reinstalled, making SURE that gnome was selected, and KDE was not.  When 
> >>I attempt to log in to gnome, the screen exhibits the same behavior as 
> >>if i choose the "restart X Server" option on the login screen.  Is 
> >>anyone else experiencing this?  Can someone give me the command line 
> >>option to verify that Gnome is even installed? (I'm a linux newbie, so 
> >>be gentle)  Any assistance would be greatly appreciated.  Thanks,
> >>
> >>-Sean
> >>
> >>
> >
> >When I installed Severn beta1, I could not get GNOME to get further than 
> >the splash screen startup. This problem was related to the interaction 
> >with my 3Com ethernet. After the card was replaced with a 2 yr newer 
> >3com NIC GNOME, Mozilla and a host of other problems went away.
> >
> >My guess is that GNOME is outputting to /dev/lockup (in my case it was 
> >my NIC). Basically, I assume that the program is outputting, but not 
> >even to a bit bucket (AKA - like windows blue screen.)
>  
>  
>  This is very interesting. Was this a 3c590 NIC?
>  
>  If so, i'm getting the same on my card. See
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=98832
>  
>  It seems to be a kudzu bug, but bill couldn't reproduce it on his 3c590.
>  Getting more data might make this fixable.
>  
>  =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>   Alexander Larsson                                            Red Hat, Inc 
>                     alexl(a)redhat.com    alla(a)lysator.liu.se 
>  He's a scarfaced Catholic sorceror from the Mississippi delta. She's a 
>  tortured French-Canadian soap star with an evil twin sister. They fight crime! 
>  
>  
>  --
>  fedora-test-list mailing list
>  fedora-test-list(a)redhat.com
>  http://www.redhat.com/mailman/listinfo/fedora-test-list
>   
-- 
We have lingered long enough on the shores of the Cosmic Ocean.
		-- Carl Sagan

[Alexander Larsson]

On Thu, 2003-10-02 at 13:29, Jim Cornette wrote:
>  The bug was with an:
>  
>  EtherLink XL PCI
>  3C900B-TPO
>  03-0147-000
>  REV-A
>  
>  bugs 104793 through 104795 contain information regarding the check cable 
>  and avalanche effects for the NIC card. 
Does this card work if you remove kudzu from the init scripts?

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
                   alexl(a)redhat.com    alla(a)lysator.liu.se 
He's a one-legged amnesiac cop in drag. She's a foxy streetsmart bounty hunter 
with only herself to blame. They fight crime!

[Jim Cornette]

Alexander Larsson wrote:
>  On Thu, 2003-10-02 at 13:29, Jim Cornette wrote:
>  
> >The bug was with an:
> >
> >EtherLink XL PCI
> >3C900B-TPO
> >03-0147-000
> >REV-A
> >
> >bugs 104793 through 104795 contain information regarding the check cable 
> >and avalanche effects for the NIC card.
>  
>  
>  Does this card work if you remove kudzu from the init scripts? 
I have the card lying around here. The problem seems that the card is 
recognized as the below card. This card worked fine from RHL 5.2 through 
all versions up to Severn.

I haven't really looked into the init scripts before. Which one would 
concern disabling Kudzu for Ethernet Cards?

The 3c590 driver seemed to work for this card. It seems that the 3c900 
is being attempted to use instead. The working card in my system is what 
it states. A tornado 3c900 based. This one is not as detected.

Jim

See Documentation/networking/vortex.txt
01:01.0: 3Com PCI 3c900 Cyclone 10Mbps TPO at 0xdc00. Vers LK1.1.18-ac
  00:10:5a:14:8d:ee, IRQ 10
   product code 504e rev 00.4 date 08-02-98
   Internal config register is 1800000, transceivers 0x8.
   8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
   MII transceiver found at address 24, status 1809.

>  
>  =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>   Alexander Larsson                                            Red Hat, Inc 
>                     alexl(a)redhat.com    alla(a)lysator.liu.se 
>  He's a one-legged amnesiac cop in drag. She's a foxy streetsmart bounty hunter 
>  with only herself to blame. They fight crime! 
>   
-- 
Everything you know is wrong!

[Alexander Larsson]

On Sun, 2003-10-05 at 18:07, Jim Cornette wrote:
>  Alexander Larsson wrote:
>  > On Thu, 2003-10-02 at 13:29, Jim Cornette wrote:
>  > 
>  >>The bug was with an:
>  >>
>  >>EtherLink XL PCI
>  >>3C900B-TPO
>  >>03-0147-000
>  >>REV-A
>  >>
>  >>bugs 104793 through 104795 contain information regarding the check cable 
>  >>and avalanche effects for the NIC card.
>  > 
>  > 
>  > Does this card work if you remove kudzu from the init scripts?
>  
>  I have the card lying around here. The problem seems that the card is 
>  recognized as the below card. This card worked fine from RHL 5.2 through 
>  all versions up to Severn.
>  
>  I haven't really looked into the init scripts before. Which one would 
>  concern disabling Kudzu for Ethernet Cards?
>  
>  The 3c590 driver seemed to work for this card. It seems that the 3c900 
>  is being attempted to use instead. The working card in my system is what 
>  it states. A tornado 3c900 based. This one is not as detected. 
I had problems with a 3com card where kudzu probing would essentially
"break" the network card. It couldn't see or send any packages at all.
Just temporary moving away /etc/rc5.d/S05kudzu and rebooting made
networking work.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
                   alexl(a)redhat.com    alla(a)lysator.liu.se 
He's an uncontrollable misogynist astronaut moving from town to town, helping 
folk in trouble. She's a transdimensional communist traffic cop with the power 
to see death. They fight crime!

[Jim Cornette]

Alexander Larsson wrote:
>  On Sun, 2003-10-05 at 18:07, Jim Cornette wrote:
>  
> >Alexander Larsson wrote:
> >
> >>On Thu, 2003-10-02 at 13:29, Jim Cornette wrote:
> >>
> >>
> >>>The bug was with an:
> >>>
> >>>EtherLink XL PCI
> >>>3C900B-TPO
> >>>03-0147-000
> >>>REV-A
> >>>
> >>>bugs 104793 through 104795 contain information regarding the check cable 
> >>>and avalanche effects for the NIC card.
> >>
> >>
> >>Does this card work if you remove kudzu from the init scripts?
> >
> >I have the card lying around here. The problem seems that the card is 
> >recognized as the below card. This card worked fine from RHL 5.2 through 
> >all versions up to Severn.
> >
> >I haven't really looked into the init scripts before. Which one would 
> >concern disabling Kudzu for Ethernet Cards?
> >
> >The 3c590 driver seemed to work for this card. It seems that the 3c900 
> >is being attempted to use instead. The working card in my system is what 
> >it states. A tornado 3c900 based. This one is not as detected.
>  
>  
>  I had problems with a 3com card where kudzu probing would essentially
>  "break" the network card. It couldn't see or send any packages at all.
>  Just temporary moving away /etc/rc5.d/S05kudzu and rebooting made
>  networking work. 
The card would come up and say thet my network cable was unplugged. 
This was during the system coming up. After all of the processes 
completed. I noticed that I had no network connection.

I did an ifconfig and there was no address for getting out through my 
router. So I just decided to run dhclient from the command line and it 
got me connected. The first time I tried it was going from a 7.3 
installation and it hosed GNOME, Mozilla and a slew of other 
applications. KDE and konquerer worked alright though.

I let this installation be dormant for awhile, then submitted a bug for 
the editing feature of redhat-config-network crashing when I tried to 
add or remove a network device. The bug was closed as fixed in rawhide.

I then upgraded with a clean install of Severn1 and 
redhat-config-network would still go crazy when trying to edit devices.

I'm in agreement with you that kudzu might be severely misidentifying 
this device and breaking a whole lot of pieces for the distribution. I 
was just surprised that one hardware device malfunctioning could cause 
so much to go wrong.

If I would not run dhclient until I tried to launch Gnome. Gnome would 
launch alright. But getting GNOME to shut down was not working.

I was also seeing file permission errors. This I believe was related to 
the device being sort of one-way (having the ability to write the file, 
but was not recognized as the same entity that wrote the file originally.)

I closed my outstanding bugs because except for the ethernet problem, 
all of the other problems were symptoms of the wrong driver for the 
ethernet card.

If it would be of some use. I could get the output from kudzu for my 
RHL9 and the output for the severn kudzu. RH9 and below work alright for 
this ethernet card. Severn toasted the NIC into uselessness.

I believe this card is pretty popular with corporate users. Figuring out 
where this card and other 3c590 NICs were broken seems like something 
that needs to be fixed.

I saw a posting about a 3c590 card mentioned for someone that was 
installing it on a laptop. I'm not sure if he was using a PCMCIA plugin 
card or if the card was builtin to his laptop. My card was PCI, But I 
have a few 3com ISA cards lying around also. I haven't tried them out to 
see if they are hosed or not. They all have worked with earlier versions 
  of Red Hat.

Jim

>  
>  =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>   Alexander Larsson                                            Red Hat, Inc 
>                     alexl(a)redhat.com    alla(a)lysator.liu.se 
>  He's an uncontrollable misogynist astronaut moving from town to town, helping 
>  folk in trouble. She's a transdimensional communist traffic cop with the power 
>  to see death. They fight crime! 
>   
-- 
  "I've finally learned what `upward compatible' means.	It means we
   get to keep all our old mistakes."
  -- Dennie van Tassel