I guess it is but not for me anymore
I left the Ubuntu community, because of the frequent complete crashes. I think
I filed a bug report on that as well.
So I am now running Mepis 7, and have a very robust OS
--
Simple backup stopped working after upgrade to Feisty
Actually I was too early with that statement.
It was still unstable with the new MB. Not as instable as before but I did not
remember the bug report as I tried out a few other distros that were all
stable, so I have found my solution.
For your reference
Ubuntu, Mepis and Linux Mint were all
** Attachment added: lspci.txt
http://launchpadlibrarian.net/8136355/lspci.txt
--
Network interface becomes unstailble and then the machinge
https://bugs.launchpad.net/bugs/121224
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/8136356/dmesg.txt
--
Network interface becomes unstailble and then the machinge
https://bugs.launchpad.net/bugs/121224
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
The whole interface stuff is odd. I am not using anything else then one
WLAN interface. Why I have two is odd, and even more so why I get lots
of activity on eth0..
** Attachment added: lsmod.txt
http://launchpadlibrarian.net/8136941/lsmod.txt
--
Network interface becomes unstailble and then
Due to HW failure I had to change my MB and CPU. CPU broke and my first
guess was the MB. Anyway with the new MB, the system is stabile. All
other parts remain the same. The old MB was an ASUS P5NSLI
--
Feisty complete freeze
https://bugs.launchpad.net/bugs/111033
You received this bug
Public bug reported:
With the update from 6.10 to 7.04 simple backup stoped working. First it
was because me external HD has been renamed
drwxr-xr-x 4 johan root 4096 2007-04-27 21:54 IOMEGA_HDD
drwx-- 3 johan root 32768 1970-01-01 01:00 IOMEGA_HDD_
This for me would be one bug. Why is the
Public bug reported:
I am having complete crashes of my Feisty. It is not a HW issue, the PC
has been rock solid with 6.10 and 6.06.
Unfortunately the logs do not give any indications to why
Apr 29 15:45:54 johans kernel: [14417.645844] Inbound IN=eth0 OUT= MAC=
SRC=192.168.0.100
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7463985/Dependencies.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/7463986/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://librarian.launchpad.net/7463987/ProcStatus.txt
--
Feisty
Linux johans 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686
GNU/Linux
** Attachment added: dmesg.log
http://librarian.launchpad.net/7464627/dmesg.log
--
Feisty complete freeze
https://bugs.launchpad.net/bugs/111033
You received this bug notification because you are a member of
** Attachment added: lspci.log
http://librarian.launchpad.net/7464632/lspci.log
--
Feisty complete freeze
https://bugs.launchpad.net/bugs/111033
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
11 matches
Mail list logo