CDROM and eth0 not detected on reboot
I burned a CD at work and could not read it at home on any computer. (XP home, XP pro, Caldera 2.4, lindows 3.0, lindows 4.0). Everytime the first big jpeg file gets accessed (6 million bytes), everybody just hangs. Windows explorer won't even shut down, requiring a reboot. I dual boot lindows 3.0 and windows XP pro. So, after a hang reading this CD in XP pro and a reboot into lindows, booting lindows results in no eth0 device detected, and the cdrom isn't detected. In the bios setup up the eth0 is enabled and the cdrom is detected. The cdrom problem is especially bad since I can't run any of the diagnostic software I think might be on the motherboards's CD. Is this just a new motherboard going bad? Could XP crashing have damaged the linux partition? I had the linux partition disabled in XP before the problem began. Any suggestions appreciated. Joel ___ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc - http://www.linux-sxs.org/mailman/listinfo/linux-users
Re: CDROM and eth0 not detected on reboot
Well, I booted back into XP Pro, and both those problem devices work fine. So, I must conclude that when XP Pro went down, it damaged the lindows partition, even though lindows resides on a different drive and this drive was removed from the device list in XP. Joel Sat, Jul 26, 2003 at 08:00:14AM -0400, Joel Hammer wrote: I burned a CD at work and could not read it at home on any computer. (XP home, XP pro, Caldera 2.4, lindows 3.0, lindows 4.0). Everytime the first big jpeg file gets accessed (6 million bytes), everybody just hangs. Windows explorer won't even shut down, requiring a reboot. I dual boot lindows 3.0 and windows XP pro. So, after a hang reading this CD in XP pro and a reboot into lindows, booting lindows results in no eth0 device detected, and the cdrom isn't detected. In the bios setup up the eth0 is enabled and the cdrom is detected. The cdrom problem is especially bad since I can't run any of the diagnostic software I think might be on the motherboards's CD. Is this just a new motherboard going bad? Could XP crashing have damaged the linux partition? I had the linux partition disabled in XP before the problem began. Any suggestions appreciated. Joel ___ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc - http://www.linux-sxs.org/mailman/listinfo/linux-users ___ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc - http://www.linux-sxs.org/mailman/listinfo/linux-users
Re: CDROM and eth0 not detected on reboot
On 07/26/03 13:29, Joel Hammer wrote: Well, I am not in lindows right now, so I cannot give you the exact error. (It is amazing how useless a computer becomes when it can't be networked), but: The bios finds it and XP finds it. When I put in a cd, the automounter doesn't do anything, whereas before it would automatically mount it. (Hate that stuff.) When I try to mount it with mount /dev/cdrom1, which is in fstab, it returns no such device or some such. Have you fscked the filesystem lately? Does the device exist? -- ~ L. Friedman[EMAIL PROTECTED] Linux Step-by-step TyGeMo:http://netllama.ipfox.com 1:35pm up 11 days, 16:18, 2 users, load average: 0.25, 0.18, 0.15 ___ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc - http://www.linux-sxs.org/mailman/listinfo/linux-users
Re: CDROM and eth0 not detected on reboot
Joel Hammer wrote: Well, I am not in lindows right now, so I cannot give you the exact error. (It is amazing how useless a computer becomes when it can't be networked), but: The bios finds it and XP finds it. When I put in a cd, the automounter doesn't do anything, whereas before it would automatically mount it. (Hate that stuff.) When I try to mount it with mount /dev/cdrom1, which is in fstab, it returns no such device or some such. Joel does /dev/cdrom1 exist? If you are running devfs and have upgraded lindows, did it over-write /etc/devfsd.conf. If you are using devfs look and see if the line to use oldcompat for cdroms isn't hashed out. As always, just a thought -- Ted Ozolins (VE7TVO) Westbank, B. C. ___ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc - http://www.linux-sxs.org/mailman/listinfo/linux-users
Re: CDROM and eth0 not detected on reboot
On Saturday 26 July 2003 08:00 am, Joel Hammer wrote: I burned a CD at work and could not read it at home on any computer. (XP home, XP pro, Caldera 2.4, lindows 3.0, lindows 4.0). Everytime the first big jpeg file gets accessed (6 million bytes), everybody just hangs. Windows explorer won't even shut down, requiring a reboot. The first thing that i would suspect is that the cd file is bad. I have also seen this when its burnt on an older cd-writer and the new laser will not read the old burnt cd. I dual boot lindows 3.0 and windows XP pro. So, after a hang reading this CD in XP pro and a reboot into lindows, booting lindows results in no eth0 device detected, and the cdrom isn't detected. In the bios setup up the eth0 is enabled and the cdrom is detected. The cdrom problem is especially bad since I can't run any of the diagnostic software I think might be on the motherboards's CD. First up is the cdrom and eth0 seen in dmesg ? If not what does dmesg say about them ? How can you run motherboard diagnostics which are for windows in linux, even if it is lindows. Is this just a new motherboard going bad? Could XP crashing have damaged the linux partition? I had the linux partition disabled in XP before the problem began. Why suspect the motherboard when you say its detected in bios ? and also seen in XP but not read. Any suggestions appreciated. Joel ___ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc - http://www.linux-sxs.org/mailman/listinfo/linux-users -- Keith Antoine (GANDALF) aka 'SKIPPY' 18 Arkana St, The Gap, Queensland 4061, Australia:: PH:61733002161 Practising Geriatric, Retired Electronics Engineer, Knowall, Brain in storage ___ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc - http://www.linux-sxs.org/mailman/listinfo/linux-users
Re: CDROM and eth0 not detected on reboot
On Saturday 26 July 2003 08:23 am, Joel Hammer wrote: Well, I booted back into XP Pro, and both those problem devices work fine. So, I must conclude that when XP Pro went down, it damaged the lindows partition, even though lindows resides on a different drive and this drive was removed from the device list in XP. AFAIK there is no way that XP crashing can or will have effect on linux/lindows or how it boots. Especially as its on a differing drive, you are whistling in the wind mate! -- Keith Antoine (GANDALF) aka 'SKIPPY' 18 Arkana St, The Gap, Queensland 4061, Australia:: PH:61733002161 Practising Geriatric, Retired Electronics Engineer, Knowall, Brain in storage ___ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc - http://www.linux-sxs.org/mailman/listinfo/linux-users
