Re: Fedora 9 Freeze At Login

On 31-Aug-08, at 4:59 PM, Timothy Murphy wrote:

> Kyle Lanigan wrote:
>
>>>> So I've put in Fedora 9 just the other day, but it doesn't matter
>>>> when
>>>> I login into Fedora 9 after booting up into it, that everything
>>>> freezes once the login screen goes away after entering my username
>>>> and
>>>> password. I'm not sure what I'm suppose to do to get this working.
>>>
>>> How long do you wait?
>>> I find a surprisingly long wait -
>>> about 30 seconds - after logging in,
>>> with very little disk activity until near the end.
>>> I don't know what the computer is doing?
>>>
>>> But that doesn't sound like your problem.
>>> Have you tried logging in in text mode?
>>>
>>
>> Well last night around 8pm I logged in, it froze and I left it until
>> about 12:30 this afternoon and it made no progress sadly.
>> Text mode log in is when I access the DOS style terminal before login
>> right?
>
> When you say it froze, do you mean the cursor could not be moved?
> In that case there is probably nothing can be done at that stage.
>

Re: eject: unable to find or open device for: `cdrom'

On Sun, Aug 31, 2008 at 11:35 PM, Nataraj <incoming-fedora-list <at> rjl.com> wrote:
>> >> >> When I try to open the DVD burner tray with the command eject, I get
>> >> >> the following problem:
>> >> >>
>> >> >> $ eject
>> >> >> eject: unable to find or open device for: `cdrom'
>> >> >> $
>> >> >>
>> >> >> Any ideas?
>> >> >
>> >> > Use "eject /dev/name-of-dvd-device". If you're not sure what the device
>> >> > name is, an easy way to find out is by firing up k3b, which will look
>> >> > for it (there are probably quicker ways but this works).
>> >>
>> >> Thanks, Patrick. K3b does not see the inserted CD.
>> >>
>> >> The problem that I am reporting did not occur before. I suspect that
>> >> some updates may have destroyed what was correctly working.
>> >>
>> >> Any further ideas?
>> >
>> > /dev/sr0
>> > /dev/sr1
>>
>> No progress:
>>
>> $ eject /dev/sr0
>> eject: unable to find or open device for: `/dev/sr0'
>> $ eject /dev/sr1
>> eject: unable to find or open device for: `/dev/sr1'

Re: New windows open in background

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: eject: unable to find or open device for: `cdrom'

On Mon, 2008-09-01 at 00:19 +0100, Paul Smith wrote:
> I think the problem is not Linux specific.
> My machine has also got MS Windows, and MS Windows cannot also detect
> my burner. I suspect that the problem is caused by the fact that I did
> recently a BIOS update.
> 
> My motherboard is a Gigabyte GA-8I945PL-G and my burner is an IDE one.

Can the BIOS see the drive? Reboot and look for it under the BIOS boot
options (or just try booting from it using  Live CD). If it's not there
you may have either a bad drive or a connector problem.

poc

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: New windows open in background

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: eject: unable to find or open device for: `cdrom'

On Mon, Sep 1, 2008 at 12:31 AM, Patrick O'Callaghan
<pocallaghan <at> gmail.com> wrote:
>> I think the problem is not Linux specific.
>> My machine has also got MS Windows, and MS Windows cannot also detect
>> my burner. I suspect that the problem is caused by the fact that I did
>> recently a BIOS update.
>>
>> My motherboard is a Gigabyte GA-8I945PL-G and my burner is an IDE one.
>
> Can the BIOS see the drive? Reboot and look for it under the BIOS boot
> options (or just try booting from it using  Live CD). If it's not there
> you may have either a bad drive or a connector problem.

I cannot boot from a Live CD, although the option CDROM appears as a
boot option. I am going to try to downgrade the BIOS update.

Paul

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: eject: unable to find or open device for: `cdrom'

Paul Smith wrote:
> 
> How can I check whether lspci shows 00:04:06 as a SCSI or IDE controller?
> 
Well, mine shows up as:

00:14.1 IDE interface: ATI Technologies Inc Dual Channel Bus Master
PCI IDE Controller

on this machine.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: cifs WinXP problem

On Sun, 31 Aug 2008 17:32:46 -0500, Mikkel L. Ellertson wrote:

[...]
> This is the way it is supposed to be:
> 
> The default order is lmhosts, host, wins, bcast and without any entry in
> the smb.conf file the name resolution methods will be attempted in this
> order.
> 
> Did you double check that the IP address is correct? I don't remember if
> you could "ping abcd10". I guess it is possible that abcd30 is in
> lmhosts, and abcd10 is not, and it is only checking lmhosts. Just a shot
> in the dark - then again, I have made typos more then once when doing
> this.
> 
[...]

ping abcd10 works correctly.  Following your comments I also tried
lmhosts -- it didn't work.  I checked spellings; I did remove some
extra tabs from /etc/hosts .  It looks like the order you indicate
isn't happening for the XP box. Very peculiar.  BTW you are saying
"host"; I have "hosts". A typo?

Mike.

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: eject: unable to find or open device for: `cdrom'

Paul Smith wrote:
> 
> Thanks, Nataraj and Mikkel. I think the problem is not Linux specific.
> My machine has also got MS Windows, and MS Windows cannot also detect
> my burner. I suspect that the problem is caused by the fact that I did
> recently a BIOS update.
> 
> My motherboard is a Gigabyte GA-8I945PL-G and my burner is an IDE one.
> 
> Any ideas?
> 
Does it show up in the BIOS? Is the drive jumpered properly? If it
was jumpered slave, or jumpered Cable Select and it was on the
center connector of a CS cable, the BIOS may not detect it with the
upgrade.

Also check that the BIOS didn't do something strange with the
upgrade like turning off the second IDE controller. SOmetie after an
update, you are better off resetting all the BIOS options, and then
resetting them to what you want/need.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Re: eject: unable to find or open device for: `cdrom'

On Mon, Sep 1, 2008 at 12:55 AM, Mikkel L. Ellertson
<mikkel <at> infinity-ltd.com> wrote:
>> Thanks, Nataraj and Mikkel. I think the problem is not Linux specific.
>> My machine has also got MS Windows, and MS Windows cannot also detect
>> my burner. I suspect that the problem is caused by the fact that I did
>> recently a BIOS update.
>>
>> My motherboard is a Gigabyte GA-8I945PL-G and my burner is an IDE one.
>>
>> Any ideas?
>>
> Does it show up in the BIOS? Is the drive jumpered properly? If it
> was jumpered slave, or jumpered Cable Select and it was on the
> center connector of a CS cable, the BIOS may not detect it with the
> upgrade.
>
> Also check that the BIOS didn't do something strange with the
> upgrade like turning off the second IDE controller. SOmetie after an
> update, you are better off resetting all the BIOS options, and then
> resetting them to what you want/need.

I have downgraded the BIOS update to the one that was working before,
but no progress: the BIOS cannot see the drive. I did not do anything
physically to the computer. So, I guess the driver is correctly
jumpered.

Paul

--

-- 
fedora-list mailing list
fedora-list <at> redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines