Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: Ubuntu instability, will openSUSE do the same

  1. #1

    Default Ubuntu instability, will openSUSE do the same

    Based on the information below, do you think I will experience the same stability issues witih openSUSE as with Ubuntu? (I know I'll probably just have to install openSUSE and find out for myself).

    Here's my problem, copied from my unanswered thread on ubuntuforums.org.

    I have two problems with Ubuntu 8.04, which may be unrelated to each other. I'm running an emachine t5234 with an AMD Athlon 64x2 4200+ processor and 2 gigs of RAM.

    Printing ties up a lot of the CPU and sometimes freezes the system to the extent that CTRL+ALT+BACKSPACE and REISUB won't free it up. I have turned off Advanced Desktop Affects and this is still happening.

    Syslog from the last lock up looked like this:
    Sep 11 09:36:48 ubuntu kernel: [ 9805.930824] ppdev0: registered pardevice
    Sep 11 09:37:17 ubuntu kernel: [ 9834.447941] ppdev0: unregistered pardevice
    Sep 11 09:37:27 ubuntu parport0: prnt/backend/hp.c 496: unable to connect hpssd socket 2207: Connection refused
    Sep 11 09:37:27 ubuntu kernel: [ 9844.571837] ppdev0: unregistered pardevice
    Sep 11 09:37:27 ubuntu parport0: prnt/backend/hp.c 496: unable to connect hpssd socket 2207: Connection refused
    Sep 11 09:37:27 ubuntu kernel: [ 9844.599790] ppdev0: registered pardevice
    Sep 11 09:37:27 ubuntu kernel: [ 9844.681880] audit(1221143847.299:10): type=1503 operation="inode_permission" requested_mask="::rw" denied_mask="::rw" name="/dev/tty" pid=6726 profile="/usr/sbin/cupsd" namespace="default"
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926337] sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926354] Pid: 6735, comm: hpijs Tainted: P 2.6.24-19-generic #1
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926371] [set_fail+0x45/0x60] set_fail+0x45/0x60
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926383] [sysctl_check_table+0x296/0x5b0] sysctl_check_table+0x296/0x5b0
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926389] [sysctl_head_finish+0x18/0x30] sysctl_head_finish+0x18/0x30
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926401] [sysctl_check_table+0x2aa/0x5b0] sysctl_check_table+0x2aa/0x5b0
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926407] [sysctl_head_finish+0x18/0x30] sysctl_head_finish+0x18/0x30
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926418] [sysctl_check_table+0x2aa/0x5b0] sysctl_check_table+0x2aa/0x5b0
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926423] [sysctl_head_finish+0x18/0x30] sysctl_head_finish+0x18/0x30
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926433] [sysctl_check_table+0x2aa/0x5b0] sysctl_check_table+0x2aa/0x5b0
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926439] [sysctl_head_finish+0x18/0x30] sysctl_head_finish+0x18/0x30
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926450] [sysctl_check_table+0x2aa/0x5b0] sysctl_check_table+0x2aa/0x5b0
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926456] [sysctl_head_finish+0x18/0x30] sysctl_head_finish+0x18/0x30
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926466] [sysctl_check_table+0x2aa/0x5b0] sysctl_check_table+0x2aa/0x5b0
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926472] [sysctl_set_parent+0x19/0x30] sysctl_set_parent+0x19/0x30
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926482] [ipv6:register_sysctl_table+0x50/0x150] register_sysctl_table+0x50/0xa0
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926492] [<f8a9d90e>] parport_device_proc_register+0xae/0xe0 [parport]
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926506] [<f8a9be29>] parport_register_device+0x139/0x260 [parport]
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926524] [<f8afa765>] pp_ioctl+0x445/0x830 [ppdev]
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926530] [<f8afa240>] pp_irq+0x0/0x50 [ppdev]
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926545] [do_ioctl+0x78/0x90] do_ioctl+0x78/0x90
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926554] [vfs_ioctl+0x22e/0x2b0] vfs_ioctl+0x22e/0x2b0
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926561] [do_sys_open+0xbe/0xe0] do_sys_open+0xbe/0xe0
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926569] [sys_ioctl+0x56/0x70] sys_ioctl+0x56/0x70
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926576] [sysenter_past_esp+0x6b/0xa9] sysenter_past_esp+0x6b/0xa9
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926596] =======================
    Sep 11 09:37:27 ubuntu kernel: [ 9844.926598] ppdev0: registered pardevice
    Sep 11 09:37:27 ubuntu hpijs: io/hpmud/pp.c 627: unable to read device-id ret=-110

    I don't have the syslog from a random shutdown in front of me, but I have looked at it in the past and there were no error messages of any sort from those times. Temperature is between 90 and 115 degrees. Temperature-related auto shutdown isn't even enable in the BIOS. I have replaced the power supply.

    I tried replacing powernowd with cpudyn last night for the heck of it. Don't know if this will do any good at all.

    Any help is much appreciated.

  2. #2
    Join Date
    Jun 2008
    Location
    Belgrade, Serbia
    Posts
    719

    Default Re: Ubuntu instability, will openSUSE do the same

    Oh no... in my opinion, ubuntu is a garbage. I was forced to use it for 3 months here on work, and yesterday finally got my hands untied to install openSUSE.
    At home, all two of my putters runs suse and no problem whatsoever.

  3. #3
    Join Date
    Jul 2008
    Location
    USA
    Posts
    13

    Default Re: Ubuntu instability, will openSUSE do the same

    beli0135 wrote...
    Oh no... in my opinion, ubuntu is a garbage
    That is a really offensive thing to say. In a world where Linux is just struggling to get a foothold, the last thing the community needs is infighting and bashing amongst distros. Most importantly, I highly doubt that Ubuntu customizations have anything to do with the posters problem at all. Keep in mind, neither Ubuntu nor Suse projects write print drivers. Thus, assuming one distribution or another will make a difference here is probably unrealistic.

    MTod, you don't provide enough info here to help you debug. It looks to me that you are trying to print over an HP Jet direct port. If so, that works flawlessly in Hardy as long as you use the "hplip" package. Please provide:

    * printer make and model
    * Method of printing (usb, jetdirect, networked cups, etc)
    * uname -a
    * try to print and then : sudo tail -n 100 dmesg
    * tail -n100 messages
    * any cups logs

  4. #4

    Default Re: Ubuntu instability, will openSUSE do the same

    It's an HP Deskjet 940c
    It's directly connected to the computer via serial port (jet direct?)
    matt@ubuntu:~$ uname -a
    Linux ubuntu 2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686 GNU/Linux
    matt@ubuntu:~$ sudo tail -n 100 dmesg
    tail: cannot open `dmesg' for reading: No such file or directory
    Here is syslog for the print job:
    Sep 11 17:51:23 ubuntu parport0: prnt/backend/hp.c 496: unable to connect hpssd socket 2207: Connection refused
    Sep 11 17:51:23 ubuntu kernel: [20647.477573] ppdev0: registered pardevice
    Sep 11 17:51:23 ubuntu kernel: [20647.550188] audit(1221173483.450:4): type=1503 operation="inode_permission" requested_mask="::rw" denied_mask="::rw" name="/dev/tty" pid=10746 profile="/usr/sbin/cupsd" namespace="default"
    Sep 11 17:51:23 ubuntu kernel: [20647.795061] sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
    Sep 11 17:51:23 ubuntu kernel: [20647.795078] Pid: 10755, comm: hpijs Tainted: P 2.6.24-19-generic #1
    Sep 11 17:51:23 ubuntu kernel: [20647.795094] [set_fail+0x45/0x60] set_fail+0x45/0x60
    Sep 11 17:51:23 ubuntu kernel: [20647.795105] [sysctl_check_table+0x296/0x5b0] sysctl_check_table+0x296/0x5b0
    Sep 11 17:51:23 ubuntu kernel: [20647.795111] [sysctl_head_finish+0x18/0x30] sysctl_head_finish+0x18/0x30
    Sep 11 17:51:23 ubuntu kernel: [20647.795120] [sysctl_check_table+0x2aa/0x5b0] sysctl_check_table+0x2aa/0x5b0
    Sep 11 17:51:23 ubuntu kernel: [20647.795126] [sysctl_head_finish+0x18/0x30] sysctl_head_finish+0x18/0x30
    Sep 11 17:51:23 ubuntu kernel: [20647.795133] [sysctl_check_table+0x2aa/0x5b0] sysctl_check_table+0x2aa/0x5b0
    Sep 11 17:51:23 ubuntu kernel: [20647.795138] [sysctl_head_finish+0x18/0x30] sysctl_head_finish+0x18/0x30
    Sep 11 17:51:23 ubuntu kernel: [20647.795145] [sysctl_check_table+0x2aa/0x5b0] sysctl_check_table+0x2aa/0x5b0
    Sep 11 17:51:23 ubuntu kernel: [20647.795151] [sysctl_head_finish+0x18/0x30] sysctl_head_finish+0x18/0x30
    Sep 11 17:51:23 ubuntu kernel: [20647.795158] [sysctl_check_table+0x2aa/0x5b0] sysctl_check_table+0x2aa/0x5b0
    Sep 11 17:51:23 ubuntu kernel: [20647.795163] [sysctl_head_finish+0x18/0x30] sysctl_head_finish+0x18/0x30
    Sep 11 17:51:23 ubuntu kernel: [20647.795170] [sysctl_check_table+0x2aa/0x5b0] sysctl_check_table+0x2aa/0x5b0
    Sep 11 17:51:23 ubuntu kernel: [20647.795175] [sysctl_set_parent+0x19/0x30] sysctl_set_parent+0x19/0x30
    Sep 11 17:51:23 ubuntu kernel: [20647.795182] [ipv6:register_sysctl_table+0x50/0x150] register_sysctl_table+0x50/0xa0
    Sep 11 17:51:23 ubuntu kernel: [20647.795189] [<f8a6b90e>] parport_device_proc_register+0xae/0xe0 [parport]
    Sep 11 17:51:23 ubuntu kernel: [20647.795201] [<f8a69e29>] parport_register_device+0x139/0x260 [parport]
    Sep 11 17:51:23 ubuntu kernel: [20647.795212] [<f8d51765>] pp_ioctl+0x445/0x830 [ppdev]
    Sep 11 17:51:23 ubuntu kernel: [20647.795218] [<f8d51240>] pp_irq+0x0/0x50 [ppdev]
    Sep 11 17:51:23 ubuntu kernel: [20647.795227] [do_ioctl+0x78/0x90] do_ioctl+0x78/0x90
    Sep 11 17:51:23 ubuntu kernel: [20647.795235] [vfs_ioctl+0x22e/0x2b0] vfs_ioctl+0x22e/0x2b0
    Sep 11 17:51:23 ubuntu kernel: [20647.795241] [do_sys_open+0xbe/0xe0] do_sys_open+0xbe/0xe0
    Sep 11 17:51:23 ubuntu kernel: [20647.795248] [sys_ioctl+0x56/0x70] sys_ioctl+0x56/0x70
    Sep 11 17:51:23 ubuntu kernel: [20647.795255] [sysenter_past_esp+0x6b/0xa9] sysenter_past_esp+0x6b/0xa9
    Sep 11 17:51:23 ubuntu kernel: [20647.795265] =======================
    Sep 11 17:51:23 ubuntu kernel: [20647.795269] ppdev0: registered pardevice

    I'll install hplip-gui.

  5. #5
    Join Date
    Jul 2008
    Location
    USA
    Posts
    13

    Default Re: Ubuntu instability, will openSUSE do the same

    From the look of your log file, it seems you are having a driver issue. Here is what I would suggest trying:

    1. System/Administration/Priting
    2. Delete any printers installed
    3. sudo apt-get install hplip (This is the hp driver module that works very well with your printer series.
    4. During installation of HPLIP, it may prompt you to install your device. If not, then System/Preferences/HPLIP Toolbox, then Device/Setup New Device.

    Follow the above instructions works for 99% of hp printers connected directly to the computer or via JetDirect (the network connectivity for some HP printers). In fact, my mom runs a HP 960 on Hardy with HPLIP.

    If that does not work, then I need to see your kernel ring buffer (my mistake on the command, it is:
    > sudo dmesg | tail -n 100

    If the above does not work for some reason, then I would guess the issue is a misidentification of your serial port type. I don't recall off the top of my head, but I think your printer requires either ECP or EPP parallel port. IF you have configured as one type in the bios, but not the other, it will not work. Hence, check your parallel port setup and try the other value. Some Bioses have support for both EPP and ECP at once.

    If that STILL does not fix your problem, then it is is time to post your issue to Launchpad, not the user forum. A quick search found a few similar issues:

    https://bugs.launchpad.net/ubuntu/+s...ys/+bug/221087
    https://answers.launchpad.net/hplip/+question/27498

    Good luck and let us know how it goes.

  6. #6

    Default Re: Ubuntu instability, will openSUSE do the same

    I uninstalled the printer, then set it up again as a new device. I can print, but TOP shows that HP is using 99% of the CPU for the print job.

    matt@ubuntu:~$ sudo dmesg | tail -n 100
    [ 27.388279] sd 2:0:0:0: [sdb] Attached SCSI removable disk
    [ 27.388303] sd 2:0:0:0: Attached scsi generic sg2 type 0
    [ 27.389434] sd 2:0:0:1: [sdc] Attached SCSI removable disk
    [ 27.389455] sd 2:0:0:1: Attached scsi generic sg3 type 0
    [ 27.390521] sd 2:0:0:2: [sdd] Attached SCSI removable disk
    [ 27.390543] sd 2:0:0:2: Attached scsi generic sg4 type 0
    [ 27.391524] sd 2:0:0:3: [sde] Attached SCSI removable disk
    [ 27.391543] sd 2:0:0:3: Attached scsi generic sg5 type 0
    [ 29.482129] Linux agpgart interface v0.102
    [ 29.600827] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    [ 29.641770] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    [ 29.724683] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x1c00
    [ 29.724697] i2c-adapter i2c-1: nForce2 SMBus adapter at 0xf400
    [ 29.747909] nvidia: module license 'NVIDIA' taints kernel.
    [ 30.144342] input: Power Button (FF) as /devices/virtual/input/input2
    [ 30.176161] ACPI: Power Button (FF) [PWRF]
    [ 30.176226] input: Power Button (CM) as /devices/virtual/input/input3
    [ 30.204125] ACPI: Power Button (CM) [PWRB]
    [ 30.215459] ACPI: PCI Interrupt Link [AIGP] enabled at IRQ 23
    [ 30.215463] ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [AIGP] -> GSI 23 (level, low) -> IRQ 16
    [ 30.215470] PCI: Setting latency timer of device 0000:00:0d.0 to 64
    [ 30.216437] NVRM: loading NVIDIA UNIX x86 Kernel Module 169.12 Thu Feb 14 17:53:07 PST 2008
    [ 30.827812] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
    [ 30.827817] ACPI: PCI Interrupt 0000:00:05.0[B] -> Link [AAZA] -> GSI 22 (level, low) -> IRQ 17
    [ 30.827833] PCI: Setting latency timer of device 0000:00:05.0 to 64
    [ 30.862305] hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
    [ 31.203682] ACPI: PCI Interrupt Link [APC6] enabled at IRQ 16
    [ 31.203692] ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [APC6] -> GSI 16 (level, low) -> IRQ 20
    [ 31.203702] PCI: Setting latency timer of device 0000:03:00.0 to 64
    [ 31.203727] sky2 0000:03:00.0: v1.20 addr 0xfdcfc000 irq 20 Yukon-FE (0xb7) rev 3
    [ 31.204003] sky2 eth0: addr 00:1e:90:65:a3:11
    [ 31.226435] input: PC Speaker as /devices/platform/pcspkr/input/input4
    [ 31.917868] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input5
    [ 31.957517] parport_pc 00:09: reported by Plug and Play ACPI
    [ 31.957561] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
    [ 31.989357] parport0: Printer, HEWLETT-PACKARD DESKJET 940C
    [ 32.743723] loop: module loaded
    [ 32.764076] lp0: using parport0 (interrupt-driven).
    [ 32.829240] Adding 4096532k swap on /dev/sda1. Priority:-1 extents:1 across:4096532k
    [ 33.374751] EXT3 FS on sda2, internal journal
    [ 34.082620] kjournald starting. Commit interval 5 seconds
    [ 34.082882] EXT3 FS on sda3, internal journal
    [ 34.082886] EXT3-fs: mounted filesystem with ordered data mode.
    [ 34.474836] ip_tables: (C) 2000-2006 Netfilter Core Team
    [ 34.496904] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
    [ 34.550377] NET: Registered protocol family 10
    [ 34.550578] lo: Disabled Privacy Extensions
    [ 34.563376] ip6_tables: (C) 2000-2006 Netfilter Core Team
    [ 35.902273] ppdev: user-space parallel port driver
    [ 36.049460] audit(1221174412.384:2): type=1503 operation="inode_permission" requested_mask="a::" denied_mask="a::" name="/dev/tty" pid=5014 profile="/usr/sbin/cupsd" namespace="default"
    [ 37.312491] vboxdrv: Trying to deactivate the NMI watchdog permanently...
    [ 37.312496] vboxdrv: Successfully done.
    [ 37.312499] vboxdrv: Found 2 processor cores.
    [ 37.312519] vboxdrv: fAsync=1 u64DiffCores=2171971.
    [ 37.312557] vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'.
    [ 37.312561] vboxdrv: Successfully loaded version 1.6.4 (interface 0x00080000).
    [ 38.471808] sky2 eth0: enabling interface
    [ 38.475096] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 40.211298] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
    [ 40.212353] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 40.850407] No dock devices found.
    [ 41.011664] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
    [ 41.011670] apm: disabled - APM is not SMP safe.
    [ 42.448566] NET: Registered protocol family 17
    [ 54.948906] eth0: no IPv6 routers present
    [ 1674.771824] ppdev0: registered pardevice
    [ 1674.792692] ppdev0: unregistered pardevice
    [ 1715.455166] ppdev0: registered pardevice
    [ 1715.537245] ppdev0: unregistered pardevice
    [ 1715.670590] ppdev0: registered pardevice
    [ 1715.842084] audit(1221176091.031:3): type=1503 operation="inode_permission" requested_mask="::rw" denied_mask="::rw" name="/dev/tty" pid=6061 profile="/usr/sbin/cupsd" namespace="default"
    [ 1716.490428] sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
    [ 1716.490444] Pid: 6070, comm: hpijs Tainted: P 2.6.24-19-generic #1
    [ 1716.490462] [<c01459c5>] set_fail+0x45/0x60
    [ 1716.490474] [<c0145c76>] sysctl_check_table+0x296/0x5b0
    [ 1716.490478] [<c0134228>] sysctl_head_finish+0x18/0x30
    [ 1716.490489] [<c0145c8a>] sysctl_check_table+0x2aa/0x5b0
    [ 1716.490494] [<c0134228>] sysctl_head_finish+0x18/0x30
    [ 1716.490503] [<c0145c8a>] sysctl_check_table+0x2aa/0x5b0
    [ 1716.490508] [<c0134228>] sysctl_head_finish+0x18/0x30
    [ 1716.490516] [<c0145c8a>] sysctl_check_table+0x2aa/0x5b0
    [ 1716.490521] [<c0134228>] sysctl_head_finish+0x18/0x30
    [ 1716.490530] [<c0145c8a>] sysctl_check_table+0x2aa/0x5b0
    [ 1716.490535] [<c0134228>] sysctl_head_finish+0x18/0x30
    [ 1716.490544] [<c0145c8a>] sysctl_check_table+0x2aa/0x5b0
    [ 1716.490549] [<c0132da9>] sysctl_set_parent+0x19/0x30
    [ 1716.490558] [<c01345d0>] register_sysctl_table+0x50/0xa0
    [ 1716.490564] [<f8abe90e>] parport_device_proc_register+0xae/0xe0 [parport]
    [ 1716.490577] [<f8abce29>] parport_register_device+0x139/0x260 [parport]
    [ 1716.490590] [<f8d54765>] pp_ioctl+0x445/0x830 [ppdev]
    [ 1716.490597] [<f8d54240>] pp_irq+0x0/0x50 [ppdev]
    [ 1716.490609] [<c019e048>] do_ioctl+0x78/0x90
    [ 1716.490618] [<c019e28e>] vfs_ioctl+0x22e/0x2b0
    [ 1716.490623] [<c01900ce>] do_sys_open+0xbe/0xe0
    [ 1716.490630] [<c019e366>] sys_ioctl+0x56/0x70
    [ 1716.490636] [<c01043c2>] sysenter_past_esp+0x6b/0xa9
    [ 1716.490650] =======================
    [ 1716.490654] ppdev0: registered pardevice
    [ 1794.730648] ppdev0: unregistered pardevice
    [ 1794.773506] ppdev0: unregistered pardevice

    And the HP Device Manager keeps giving me an "Error: Device Not Found" message.

  7. #7
    Join Date
    Jul 2008
    Location
    USA
    Posts
    13

    Default Re: Ubuntu instability, will openSUSE do the same

    Wow..I should have checked this first, but your printer model is not supported with hplip using a parallel port at all. However, it is supported via USB.

    HPLIP Supported Printers
    HP Deskjet 940c

    If HP itself does not have a Linux driver for your printer over a parallel port, then that explains why you have had such a tough time. Come to think of it, my mom uses a USB cable on her printer.

    My guess is that ubuntu found the closest PPD file out there that emulates you printer. However, there is just not that much effor put into PPDs when HP provides such fantastic support of the Linux community. For example, HPLIP provides full functionality for status of ink levels, error codes, etc. (Yes, I worked for HP for 10 years and participated in OSS).

    Hey, on the plus side, this also proves that this is not a distribution issue. While I love OpenSuse, it would not resolve this issue.

    Please try the USB cable and let us know how that goes.

  8. #8

    Default Re: Ubuntu instability, will openSUSE do the same

    Cool. Thank you very much. God knows where the USB cable is. I will try to track one down at Best Buy.

    Since you solved one problem, would you like to hazard a guess as to my mystery shutdowns? Like I said, I don't have any logs available from those times the machine shut down, but there were no obvious "error," "unable to," or "device not found" messages. And the machine is running fairly cool.

  9. #9
    Join Date
    Jul 2008
    Location
    USA
    Posts
    13

    Default Re: Ubuntu instability, will openSUSE do the same

    Sure, but we should take this back to the Ubuntu forums. Can you please post your Ubuntu forum thread link that has details about your issues?

  10. #10

    Default Re: Ubuntu instability, will openSUSE do the same


Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •