system freezes after login - ubuntu 10.10

xeleema · 01-31-2011, 06:50 PM

Quote:

Originally Posted by bluegospel

Like I said, 4x was the only speed that worked for me.

Dude, with all due respect. If burning that ISO at 4x fixes The Oate's problems, I'll be *very* impressed.
(Because 'burn speed' hasn't been the root cause of any issue I've seen since Total Annihilation came out in 1997)

bluegospel · 01-31-2011, 07:04 PM

I'm certainly not arguing with you, xeleema. You obviously are more experienced than me and I've benefited from your advice in the past. I just know this worked for me, so why not give it a whirl?

The Oate · 01-31-2011, 07:23 PM

Quote:

Originally Posted by bluegospel

I'm certainly not arguing with you, xeleema. You obviously are more experienced than me and I've benefited from your advice in the past. I just know this worked for me, so why not give it a whirl?

Ok, here's the newest syslog with booting off a new cd I burned at the slowest speed I could set the drive to (10x) with a different burning program. It doesn't seem like the issues from the cd drive that were there before on in this log. However, it took me more than one attempt at booting with this cd before it actually made it all the way in to the os. The first couple of tries hung at different points.

bluegospel · 01-31-2011, 07:34 PM

Well, all I can say is if you're still struggling with this down the road, try 4x before giving up on Linux altogether. It's a fun OS.

The Oate · 01-31-2011, 07:40 PM

Quote:

Originally Posted by bluegospel

Well, all I can say is if you're still struggling with this down the road, try 4x before giving up on Linux altogether. It's a fun OS.

I won't be giving up on linux, I'll be giving up on this system. Any free software for burning you'd suggest? Both programs I've got won't let me set the write speed below 10x.

bluegospel · 01-31-2011, 08:00 PM

Yes, Nero 10 ROM Burn is free for I believe 15 days. That's what I used.

xeleema · 01-31-2011, 08:31 PM

Quote:

Originally Posted by bluegospel

I'm certainly not arguing with you, xeleema. You obviously are more experienced than me and I've benefited from your advice in the past. I just know this worked for me, so why not give it a whirl?

My apologies, I re-read my post and I sound like a Windows Admin....my coffee veins must have too much blood in them...

bluegospel · 01-31-2011, 08:40 PM

lol, funny xeleena!

xeleema · 01-31-2011, 09:01 PM

@ The Oate
Okay, I've gone over the syslog file from this most-recent boot-up (01feb11), and compared it to the one from earlier (31jan11). Here's what I can tell;
The first one had serious issues reading from the CD/DVD-ROM drive, but that's not the case this time around.
However, there's something USB-wise that keeps interrupting the boot-up process.

By chance is there an external media card reader attached?
(I doubt that's the root-cause here, I'm just curious)

Since the first syslog showed problems with the ROM, and you had to boot and reboot several times to get this new burned ISO to read, my vote is the ROM drive bit the dust sometime way back, and your recent attempts to stick an Operating System on the box have exacerbated the situation.

Here's what I'd do (in most-to-least lazyness)
1) Check all cables & connections to the ROM & the MoBo. If you can, swap something around.
2) Get one of those fancy ROM drive cleaners. Like this.
3) Use some canned-air on the inside of the ROM drive (just don't turn the can upsidedown and freeze the internals. The residue will kill the lens.)
4) Consider getting a new ROM drive. Shouldn't have to spring more than $30 for one over at NewEgg.com. Hell they've got BD-ROMs for ~$80.
(I buy locally, myself. However I do use NewEgg to figure out how much I should expect to pay)

The Oate · 01-31-2011, 09:27 PM

Quote:

Originally Posted by xeleema

@ The Oate
Okay, I've gone over the syslog file from this most-recent boot-up (01feb11), and compared it to the one from earlier (31jan11). Here's what I can tell;
The first one had serious issues reading from the CD/DVD-ROM drive, but that's not the case this time around.
However, there's something USB-wise that keeps interrupting the boot-up process.

By chance is there an external media card reader attached?
(I doubt that's the root-cause here, I'm just curious)

Since the first syslog showed problems with the ROM, and you had to boot and reboot several times to get this new burned ISO to read, my vote is the ROM drive bit the dust sometime way back, and your recent attempts to stick an Operating System on the box have exacerbated the situation.

Here's what I'd do (in most-to-least lazyness)
1) Check all cables & connections to the ROM & the MoBo. If you can, swap something around.
2) Get one of those fancy ROM drive cleaners. Like this.
3) Use some canned-air on the inside of the ROM drive (just don't turn the can upsidedown and freeze the internals. The residue will kill the lens.)
4) Consider getting a new ROM drive. Shouldn't have to spring more than $30 for one over at NewEgg.com. Hell they've got BD-ROMs for ~$80.
(I buy locally, myself. However I do use NewEgg to figure out how much I should expect to pay)

I'll do a check on the cables for the ROM drive. As far as the USB, there is a reader from the front of the case that's currently attached. I can always unhook that because I don't think I've ever used it, so not having it would be no different.

xeleema · 01-31-2011, 10:23 PM

Quote:

Originally Posted by The Oate

I'll do a check on the cables for the ROM drive. As far as the USB, there is a reader from the front of the case that's currently attached. I can always unhook that because I don't think I've ever used it, so not having it would be no different.

Okay, cool. If you get a chance to test it whilst experimenting on the unsuspecting optical drive, that'd be awesome.

Quote:

Originally Posted by bluegospel

Burn speed, I mentioned it thrice, well, now four times. The Oate promised to check it.

I should have commented on this earlier; glad to see another member of Team CoCo in our midst.

The Oate · 01-31-2011, 10:37 PM

Quote:

Originally Posted by xeleema

@ The Oate
Okay, I've gone over the syslog file from this most-recent boot-up (01feb11), and compared it to the one from earlier (31jan11). Here's what I can tell;
The first one had serious issues reading from the CD/DVD-ROM drive, but that's not the case this time around.
However, there's something USB-wise that keeps interrupting the boot-up process.

By chance is there an external media card reader attached?
(I doubt that's the root-cause here, I'm just curious)

Since the first syslog showed problems with the ROM, and you had to boot and reboot several times to get this new burned ISO to read, my vote is the ROM drive bit the dust sometime way back, and your recent attempts to stick an Operating System on the box have exacerbated the situation.

Here's what I'd do (in most-to-least lazyness)
1) Check all cables & connections to the ROM & the MoBo. If you can, swap something around.
2) Get one of those fancy ROM drive cleaners. Like this.
3) Use some canned-air on the inside of the ROM drive (just don't turn the can upsidedown and freeze the internals. The residue will kill the lens.)
4) Consider getting a new ROM drive. Shouldn't have to spring more than $30 for one over at NewEgg.com. Hell they've got BD-ROMs for ~$80.
(I buy locally, myself. However I do use NewEgg to figure out how much I should expect to pay)

Checked the cables and connections and all seem good. I did try various power cables to the ROM drive, and the only one that would ever work (actually allow the system to boot off the cd) was the one originally connected. Now that it seems to be trending towards the ROM drive being the issue, I do actually recall having some past issues burning things on it in the past. I always blamed this on other things (bad discs, running too many other programs, etc.), but perhaps the drive was actually the problem.

The Oate · 01-31-2011, 10:40 PM

Quote:

Originally Posted by xeleema

Okay, cool. If you get a chance to test it whilst experimenting on the unsuspecting optical drive, that'd be awesome.

I should have commented on this earlier; glad to see another member of Team CoCo in our midst.

Ok, here's one last syslog for the night. This time I pulled the cord on the card reader so maybe that issue will be gone. I will say I probably had to try about 10 times before I finally got things to boot back up to this point.

xeleema · 01-31-2011, 11:11 PM

Awesome!
Okay, here's the syslog output chunks just before a driver is bound to the CD/DVD-ROM.

In first syslog, we see the following happen (note the lines in bold and their times);

Code:

Jan 31 23:31:01 ubuntu kernel: [    3.928748] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 31 23:31:01 ubuntu kernel: [    3.928898]  sda: sda1 sda2 < sda5 >
Jan 31 23:31:01 ubuntu kernel: [    3.969404] sd 3:0:0:0: [sda] Attached SCSI disk
Jan 31 23:31:01 ubuntu kernel: [    4.010946] scsi 0:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
Jan 31 23:31:01 ubuntu kernel: [    4.011564] scsi 0:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
Jan 31 23:31:01 ubuntu kernel: [    4.012187] scsi 0:0:0:2: Direct-Access     Generic  USB SM Reader    1.02 PQ: 0 ANSI: 0
Jan 31 23:31:01 ubuntu kernel: [    4.012810] scsi 0:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
Jan 31 23:31:01 ubuntu kernel: [    4.013735] sd 0:0:0:0: Attached scsi generic sg2 type 0
Jan 31 23:31:01 ubuntu kernel: [    4.015350] sd 0:0:0:1: Attached scsi generic sg3 type 0
Jan 31 23:31:01 ubuntu kernel: [    4.016407] sd 0:0:0:2: Attached scsi generic sg4 type 0
Jan 31 23:31:01 ubuntu kernel: [    4.016610] sd 0:0:0:3: Attached scsi generic sg5 type 0
Jan 31 23:31:01 ubuntu kernel: [    4.017982] sd 0:0:0:0: [sdb] Attached SCSI removable disk
Jan 31 23:31:01 ubuntu kernel: [    4.019810] sd 0:0:0:1: [sdc] Attached SCSI removable disk
Jan 31 23:31:01 ubuntu kernel: [    4.023636] sd 0:0:0:2: [sdd] Attached SCSI removable disk
Jan 31 23:31:01 ubuntu kernel: [    4.024428] sd 0:0:0:3: [sde] Attached SCSI removable disk
Jan 31 23:31:01 ubuntu kernel: [    4.241031] ata4: SATA link down (SStatus 0 SControl 310)

Pretty normal. The kernel detects sda, it's partitions, then starts listing the 'scsi' stuff of the usb multiformat card reader.

Here's the 2nd syslog (note the differences);

Code:

Feb  1 01:14:50 ubuntu kernel: [    3.964849] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb  1 01:14:50 ubuntu kernel: [    3.965168]  sda: sda1 sda2 <
Feb  1 01:14:50 ubuntu kernel: [    3.985943] scsi 2:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
Feb  1 01:14:50 ubuntu kernel: [    3.986570] scsi 2:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
Feb  1 01:14:50 ubuntu kernel: [    3.987193] scsi 2:0:0:2: Direct-Access     Generic  USB SM Reader    1.02 PQ: 0 ANSI: 0
Feb  1 01:14:50 ubuntu kernel: [    3.987818] scsi 2:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
Feb  1 01:14:50 ubuntu kernel: [    3.988486] sd 2:0:0:0: Attached scsi generic sg2 type 0
Feb  1 01:14:50 ubuntu kernel: [    3.990319] sd 2:0:0:0: [sdb] Attached SCSI removable disk
Feb  1 01:14:50 ubuntu kernel: [    3.990630] sd 2:0:0:1: Attached scsi generic sg3 type 0
Feb  1 01:14:50 ubuntu kernel: [    3.991266] sd 2:0:0:2: Attached scsi generic sg4 type 0
Feb  1 01:14:50 ubuntu kernel: [    3.992928] sd 2:0:0:1: [sdc] Attached SCSI removable disk
Feb  1 01:14:50 ubuntu kernel: [    3.994140] sd 2:0:0:3: Attached scsi generic sg5 type 0
Feb  1 01:14:50 ubuntu kernel: [    3.994692] sd 2:0:0:2: [sdd] Attached SCSI removable disk
Feb  1 01:14:50 ubuntu kernel: [    3.996909] sd 2:0:0:3: [sde] Attached SCSI removable disk
Feb  1 01:14:50 ubuntu kernel: [    3.998226]  sda5 >
Feb  1 01:14:50 ubuntu kernel: [    3.998599] sd 3:0:0:0: [sda] Attached SCSI disk

Now the third (without the multicard reader);

Code:

Feb  1 04:29:34 ubuntu kernel: [    3.920801] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb  1 04:29:34 ubuntu kernel: [    3.920971]  sda: sda1 sda2 < sda5 >
Feb  1 04:29:34 ubuntu kernel: [    3.959976] sd 0:0:0:0: [sda] Attached SCSI disk
Feb  1 04:29:34 ubuntu kernel: [    4.232031] ata2: SATA link down (SStatus 0 SControl 310)
Feb  1 04:29:34 ubuntu kernel: [    4.544029] ata4: SATA link down (SStatus 0 SControl 310)
Feb  1 04:29:34 ubuntu kernel: [    4.544629] scsi 4:0:0:0: CD-ROM            TSSTcorp CD/DVDW TS-H652L 0603 PQ: 0 ANSI: 5
Feb  1 04:29:34 ubuntu kernel: [    4.548026] sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
Feb  1 04:29:34 ubuntu kernel: [    4.548030] Uniform CD-ROM driver Revision: 3.20
Feb  1 04:29:34 ubuntu kernel: [    4.548149] sr 4:0:0:0: Attached scsi CD-ROM sr0
Feb  1 04:29:34 ubuntu kernel: [    4.548225] sr 4:0:0:0: Attached scsi generic sg1 type 5

During boot-up, lots of things happen (seemingly simultaneously), so sometimes outputs get an "interruped" look to them (like with syslog #2).
However, it looks like something is delaying the system from detecting the CD/DVD-ROM, possibly while the multicard reader was plugged in.
(Or the kernel could be taking it's sweet time on the empty sata ports it scans next, I would need to "know" the system better.)

If you have another system laying around you can "sacrafice" a DVD-ROM from, throw it in this system, leave the multicard reader off (just in case), and give it another boot. Should start right up.

If not, it's the power supply.

P.S: Goodnight, all. I've completed my 36-hour day and am in need of some sleep.

The Oate · 02-01-2011, 10:35 AM

Quote:

Originally Posted by xeleema

Awesome!
During boot-up, lots of things happen (seemingly simultaneously), so sometimes outputs get an "interruped" look to them (like with syslog #2).
However, it looks like something is delaying the system from detecting the CD/DVD-ROM, possibly while the multicard reader was plugged in.
(Or the kernel could be taking it's sweet time on the empty sata ports it scans next, I would need to "know" the system better.)

If you have another system laying around you can "sacrafice" a DVD-ROM from, throw it in this system, leave the multicard reader off (just in case), and give it another boot. Should start right up.

If not, it's the power supply.

P.S: Goodnight, all. I've completed my 36-hour day and am in need of some sleep.

No spare ROM drives, so I've ordered a new one. If it solves the problem, great, if not I'm building a new system soon anyway so I can throw it in there. I'll let you know what happens.