aptosid.com

Upgrade Warnings - [SOLVED] New udev (and /run)

etorix - 06.04.2011, 03:11
Post subject: [SOLVED] New udev (and /run)
Latest udev in sid installs a partly implemented /run ditrectory

and may make your system un-bootable

please be sure to use fixed udev version from aptosid repo

udev 167-1+c0.aptosid.1


see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620995

and http://lwn.net/Articles/436012/

UPDATE: basefiles 6.3 will remove /run/ again, thereby avoiding this issue

UPDATE: the /run directory usage aint implemented yet, but it will be

UPDATE: new sysvinit Installed: 2.88dsf-13.6, implements /run
seems works fine

also see http://lists.debian.org/debian-devel/20 ... 00598.html

and http://wiki.debian.org/ReleaseGoals/RunDirectory

UPDATE: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627446
bluewater - 06.04.2011, 04:13
Post subject:
if you're affected, this workaround may fix it

Hit [e] during grub, to edit your grub entry and change "ro" to "rw" in the line linux /boot/vmlinuz-2.6.38-2.slh.3-aptosid-686 root=/dev/mapper/vg--progress-debian ro quiet libata.ignore_hpa=1 ...or whatever your kernel is

if you're lucky, that will allow you to boot but ensure you install the fixed udev package from the aptosid repo [ udev 167-1+c0.aptosid.1 ] as the first step after booting up
drb - 06.04.2011, 08:44
Post subject:
Not sure if this is related. I have the aptosid udev version but when I boot I have no mouse or keyboard.

      Code:
apt-cache policy udev
udev:
  Installed: 167-1+c0.aptosid.1
  Candidate: 167-1+c0.aptosid.1
  Version table:
 *** 167-1+c0.aptosid.1 0
        500 http://debian.tu-bs.de/project/aptosid/debian/ sid/fix.main i386 Packages
        100 /var/lib/dpkg/status
     167-1 0
        500 http://ftp.de.debian.org/debian/ sid/main i386 Packages

armin - 06.04.2011, 08:49
Post subject:
      drb wrote:
Not sure if this is related. I have the aptosid udev version but when I boot I have no mouse or keyboard.

      Code:
apt-cache policy udev
udev:
  Installed: 167-1+c0.aptosid.1
  Candidate: 167-1+c0.aptosid.1
  Version table:
 *** 167-1+c0.aptosid.1 0
        500 http://debian.tu-bs.de/project/aptosid/debian/ sid/fix.main i386 Packages
        100 /var/lib/dpkg/status
     167-1 0
        500 http://ftp.de.debian.org/debian/ sid/main i386 Packages


same here at login kdm page. If you disconnect and reconnect mouse and keyboard, it works again.
drb - 06.04.2011, 08:52
Post subject:
I tried that and it didn't work, but I booted as above with rw instead of ro and then a reboot and everything now OK.

drb
snvv - 06.04.2011, 09:42
Post subject:
I have the same issue with mouse and keybord.

Unplug and plug "solves" the problem but only with usb mouse & keyboard.

Regards
DeepDayze - 06.04.2011, 13:44
Post subject:
I tried to change the "ro" to "rw" in Grub and get Grub error 'alloc magic broken at 0x75747. Aborted. Press any key to continue'.

Right now using a livecd to be able to use my laptop. Haven't updated my desktop yet. Any ideas?
rick1053 - 06.04.2011, 13:48
Post subject: Re: New udev [and /run]
      etorix wrote:
Latest udev in sid installs a partly implemented /run ditrectory

and may make your system un-bootable

please be sure to use fixed udev version from aptosid repo

udev 167-1+c0.aptosid.1


see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620995


First, Thanks for the warning. I have not 'd-u'ed in the last two days. So I haven't had to fix this.
Next, Can or should I put on hold udev until initscripts and udev are resolved, or is this counter-productive or unadvisable.
Thak you in advance,
Rick
DeepDayze - 06.04.2011, 13:56
Post subject: RE: Re: New udev [and /run]
Can we rollback to udev in testing till the issue is resolved. The fixed package does not solve the problem
clubex - 06.04.2011, 13:59
Post subject:
see also the base-files bug

#621036 - base-files creates an unuseable /run, breaking udev and the whole system

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620995

Looks to me like a real show stopper until it's fixed
DeepDayze - 06.04.2011, 14:03
Post subject:
Looks like we'd need to downgrade base-files and udev from testing...can this be confirmed to be a fix till the broken udev and base-files are fixed?

perhaps aptosid team can repackage the testing versions of these packages in the fixes repo to make it easier for people to fix their systems?

Now why for the life of me why change the existing udev infrastructure to add some new directory? udev's a very complicated system and changes to it are very disruptive
dibl - 06.04.2011, 14:09
Post subject:
      DeepDayze wrote:


perhaps aptosid team can repackage the testing versions of these packages in the fixes repo to make it easier for people to fix their systems?


That would be nice.

I can dist-upgrade my netbook via ethernet, and I just did. So I have udev 167-1+c0.aptosid.1 installed. But, no keyboard and no mouse in init 5, and no wireless. Using Alt-SysRq R S E, I can exit the KDM greeter, and then log in to the tty1 and work with ethernet only. I guess we're waiting ....
DeepDayze - 06.04.2011, 14:59
Post subject:
OK, I downgraded base-files, udev, libudev0, libgudev to the versions in testing and my laptop works fine again. Also removed the /run directory in init 1 to be safe before going to init 5. Will hold off on dist-upgrades till it is safe to do so again after its confirmed that udev and base-files packages are fixed.
snvv - 06.04.2011, 16:12
Post subject:
I downgraded udev from testing and now mouse and keyboard work without problem.
clubex - 06.04.2011, 16:53
Post subject:
An explanation for the new /run directory from the systemd maintainer.

http://lwn.net/Articles/436012/

It's addressed to Fedora but I think it would also apply to other distros including Debian.
muchan - 06.04.2011, 17:18
Post subject:
      clubex wrote:
An explanation for the new /run directory from the systemd maintainer.

http://lwn.net/Articles/436012/

It's addressed to Fedora but I think it would also apply to other distros including Debian.


On Debian:
BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620191
debian-devel http://lists.debian.org/debian-devel/20 ... 01150.html
JohnML - 06.04.2011, 18:51
Post subject:
      bluewater wrote:
if you're affected, this workaround may fix it

Hit [e] during grub, to edit your grub entry and change "ro" to "rw" in the line linux /boot/vmlinuz-2.6.38-2.slh.3-aptosid-686 root=/dev/mapper/vg--progress-debian ro quiet libata.ignore_hpa=1 ...or whatever your kernel is

if you're lucky, that will allow you to boot but ensure you install the fixed udev package from the aptosid repo [ udev 167-1+c0.aptosid.1 ] as the first step after booting up


usb-keyboard and mouse are up again, thanks a lot , bluewater Smile)
Carnophage - 06.04.2011, 20:42
Post subject:
In my case, the trick with rw in grub allowed to login to the system (before the reboot I had the aptosid version of udev installed).
After succesfull login
      Code:
rm -rf /run
as suggested here → http://bugs.debian.org/cgi-bin/bugrepor ... =621036#77 seems to solve the problem for now.
nh2 - 06.04.2011, 21:48
Post subject:
After a D-U and a reboot today on my netbook (aptosid 32 bit) the mouse and the keyboard didn't respond in KDM login screen.
I pressed the power button to make a clean shutdown and rebooted in maintenance mode. Then I renamed the /run/ directory:
      Code:
# mv /run /run.bak

and rebooted once again... Everything seems to work fine now!
mheyes - 06.04.2011, 21:55
Post subject:
yes, and base-files 6.3 corrects the problem until udev gets fixed.
DeepDayze - 06.04.2011, 22:54
Post subject:
Seems there's so many moving parts for such a critical infrastructure and when something gets screwed up sure can cause total breakage
bmorency - 06.04.2011, 23:28
Post subject:
      Code:
# mv /run /run.bak


On my system (amd64) I was able to boot but both of my network cards were not working. They are not wireless.My keyboard and mouse were also working. When I ran the code above and rebooted both my network cards were working again.
dibl - 06.04.2011, 23:49
Post subject:
It's starting KDE when I boot with "rw" instead of "ro", and I have the keyboard and mouse, but kwin is using 43% of the CPU resources on my netbook, so ....

waiting
DeepDayze - 07.04.2011, 00:10
Post subject:
      dibl wrote:
It's starting KDE when I boot with "rw" instead of "ro", and I have the keyboard and mouse, but kwin is using 43% of the CPU resources on my netbook, so ....

waiting


With issues like that I just simply downgraded to udev and base-files in testing and deleted the /run directory to get the full functionality back. This is too serious to get half-baked fixes and hacks. Going to wait to see if this issue gets fully resolved before i dist-upgrade again
dibl - 07.04.2011, 00:41
Post subject:
      DeepDayze wrote:

With issues like that I just simply downgraded to udev and base-files in testing and deleted the /run directory to get the full functionality back. This is too serious to get half-baked fixes and hacks. Going to wait to see if this issue gets fully resolved before i dist-upgrade again


Right. Thanks, DD. I can live without my netbook for a few days or a week. The desktop is not getting a d-u until this is fully sorted. Patience may be the best mode for this one.
slam - 07.04.2011, 05:56
Post subject:
A temporary fix for udev (167-1+c0.aptosid.1) is in our repos, thanks to slh.
Install it and re-boot.
Greetings,
Chris
snvv - 07.04.2011, 11:40
Post subject:
The fix does not solve the keyboard & mouse issues in aptosid 32 bit. Downgraded udev again from testing in order to work witout problem.
titan - 07.04.2011, 11:53
Post subject:
I upgraded my 32 bit system a few hours ago which pulls in SLH's udev and all seems fine, usb mouse works OK
slam - 07.04.2011, 12:12
Post subject:
      snvv wrote:
The fix does not solve the keyboard & mouse issues in aptosid 32 bit. Downgraded udev again from testing in order to work witout problem.
Works fine here - your problem might have other reasons.
Greetings,
Chris
drb - 07.04.2011, 13:04
Post subject:
Didn't work here initially with a PS2 mouse . . . installing the aptosid udev immediately froze the mouse and keyboard forcing a hard reset . . .
jheaton5 - 07.04.2011, 14:03
Post subject:
I have installed the aptosid udev with patch. My wireless returned just fine. To activate the usb mouse I have to unplug/replug it. The keyboard, however, does not work in X. it does work in terminal.
dibl - 07.04.2011, 14:14
Post subject:
Try booting with "rw" instead of "ro" in the kernel boot line. It fixes the keyboard and mouse on my netbook. The new udev alone does not fix the issue in all cases, apparently.
jheaton5 - 07.04.2011, 14:51
Post subject:
      dibl wrote:
Try booting with "rw" instead of "ro" in the kernel boot line. It fixes the keyboard and mouse on my netbook. The new udev alone does not fix the issue in all cases, apparently.

That worked for me. Thanks.
wofritz - 07.04.2011, 15:04
Post subject:
A new base-files package arrived and seems to fix the problem.

I removed /run, dist-upgraded and rebooted. Keyboard and mouse is working.
ne - 07.04.2011, 17:00
Post subject:
      drb wrote:
Didn't work here initially with a PS2 mouse . . . installing the aptosid udev immediately froze the mouse and keyboard forcing a hard reset . . .


Same here with PS2 mouse and keyboard.

Edit: booted with an old liveCD and removed /run, then booted aptosid. Everything seems to be working.
Mte90 - 07.04.2011, 17:15
Post subject:
i have fixed the problem removed the run folder.
i have the fixed package but not fix the problem.
oldie - 07.04.2011, 17:30
Post subject:
MEZ 18:26 DU, PS2 mouse and keyboard, 64 bit - no problems, everything ok.

Oldie
arwa - 08.04.2011, 11:06
Post subject:
What is the state of this issue? Is everything ok again for sure? Then this thread should be marked solved. Or is it still risky to upgrade?

Thanks,
arwa
Luis_P - 08.04.2011, 20:17
Post subject:
Dist-upgraded ten minutes ago, and all is fine. My system is AMD64.

Regards.

Luis_P.

Edit: And the my wife's laptop (32 bit) also, and also fine.
oldie - 08.04.2011, 21:28
Post subject:
We are still trying it with aptosid without admin + service from the aprtosid team - aptosid still a name - not alive!

Try or die.

sorry , Oldie
muchan - 08.04.2011, 21:44
Post subject:
      oldie wrote:
We are still trying it with aptosid without admin + service from the aprtosid team - aptosid still a name - not alive!

Try or die.

sorry , Oldie


??? the first two posters of this thread are aptosid team members, you know? ???
and the problem is temporary solved by aptosid team's hot-fix...
I don't understand what you are talking.
slam - 09.04.2011, 08:01
Post subject:
      oldie wrote:
We are still trying it with aptosid without admin + service from the aprtosid team - aptosid still a name - not alive!

Try or die.

sorry , Oldie
Thanks for your valuable contribution, which was a key to solve the very topic. Wink
Greetings,
Chris
spock - 09.04.2011, 17:49
Post subject:
      Luis_P wrote:
Dist-upgraded ten minutes ago, and all is fine. My system is AMD64.

Regards.

Luis_P.

Edit: And the my wife's laptop (32 bit) also, and also fine.


All working fine here now as well, thanks to slh's temporary udev fix. I just DU'ed my two workstations (one 64-bit and one 32-bit).

Before this DU my 64-bit machine had major GRUB problems (stopping bootup even before GRUB menu) following a DU last week amidst all these changes. So I dived in with aptosid live USBstick and chrooted to update-grub, as in the fine manual. I don't know if this was a related issue, but all OK now. Very Happy
muchan - 09.04.2011, 17:55
Post subject:
      muchan wrote:
      clubex wrote:
An explanation for the new /run directory from the systemd maintainer.

http://lwn.net/Articles/436012/

It's addressed to Fedora but I think it would also apply to other distros including Debian.


On Debian:
BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620191
debian-devel http://lists.debian.org/debian-devel/20 ... 01150.html


now better version of explanation on Debian site.
http://wiki.debian.org/ReleaseGoals/RunDirectory
oldie - 09.04.2011, 19:48
Post subject:
sorry - but

I think my contribution was but even more beautiful alarm clock for the forum + aptosid

thanks for the wake.

oldie
ghstryder - 10.04.2011, 01:14
Post subject:
I'm thinking a few things too, but I'll keep them to myself.
dibl - 10.04.2011, 01:24
Post subject:
      ghstryder wrote:
I'm thinking a few things too, but I'll keep them to myself.


Good job, Michigan! Ohio too! Wink
blackhole - 10.04.2011, 05:45
Post subject:
      Quote:
Thanks for your valuable contribution, which was a key to solve the very topic. Wink
Greetings,
Chris


I think that the misunderstandings can arise from some decisions made from aptosid team:

1) no more official solutions on the left side column in news or some other official sections, not only the forum.
2) no more support for that little app in system tray for news about dist-upgrade (hermes).

Or maybe is not a decison, it is only lack of time and contributions.

I am sure that some of us could contribute to this.
muchan - 10.04.2011, 11:03
Post subject:
2) I think there was never hermes on aptosid... I think qt4 transition was sidux time...
(correct me, if I'm wrong)

1) since the project moving to sidux to aptosid, forum organisation has changed,
you can see here http://aptosid.com/index.php?name=PNphpBB2
the first three forums, "All the news about aptosid", "Upgrade warnings" and
"Bug reports <current>" are Official forums, following Support forum,
then Community forum, and Experimental forum.
I'm not a team member, but since I accepted the role of the moderator of
Official forums, I take it as... Official forum. That is:

When a team member post alarm in Upgrade warnings (like etorix did),
it is a official warning, and you should take it as it is.

And about the state of this warning, until Debian's repo is fixed,
it is not compeletely solved, and so not marked [Solved], while
aptosid's hot-fix offers temporary solution, that users with aptosid
fix-main repo activated can proceed d-u without being affected by the problem.
(correct me if I'm wrong)
drb - 10.04.2011, 11:37
Post subject:
      Quote:
that users with aptosid
fix-main repo activated can proceed d-u without being affected by the problem.
(correct me if I'm wrong)


A number of us had a problem with the fix (freezing keyboard and mouse). base-files has since been upgraded and I've been OK since but there still seem to be a mix of successes and failures reading above.
Ilinsekt - 11.04.2011, 05:37
Post subject:
Just to make sure: Is there anything to say against putting udev, base-files and init-scripts on hold, then dist-upgrading as usual?
wofritz - 11.04.2011, 06:00
Post subject:
      Quote:

Just to make sure: Is there anything to say against putting udev, base-files and init-scripts on hold, then dist-upgrading as usual?


If you are not having the problem right now, you can simply d-u without putting anything on hold. The issue has been fixed with a new base-files package which does not create /run.
Ilinsekt - 11.04.2011, 06:18
Post subject:
Just d-u'd without problems. Also I should say, a new version of udev (167-2) is in sid.
micha_52 - 12.04.2011, 05:38
Post subject:
after a d-u this morning my keyboard and mouse were frozen (udev 167-2). So I rebooted in safe mode and performed a 'rm -rf /run' and restarted udev by invoking '/etc/init.d/udev restart'. Now the box is working as usual.
titan - 12.04.2011, 07:13
Post subject:
I just d-u my 32 bit system and Aptosid udev was replaced with udev 167-2 with no problems, mouse works as normal ( PS2 keyboard) and no /run folder is created.
dario - 12.04.2011, 11:59
Post subject:
I confirm, d-u fine on both 32 and 64 bit this morning with udev 167-2.
vinur - 12.04.2011, 21:08
Post subject:
I can post that no problems from this.
full D-U yesterday
udev 167-2

michael@eyland:~$ infobash -v3
Host/Kernel/OS "eyland" running Linux 2.6.38-2.slh.3-aptosid-amd64 x86_64 [ aptosid 2011-01 Γῆρας - kde-lite - (201102051540) ]
CPU Info 4x AMD Phenom II X4 955 512 KB cache flags( sse3 ht nx lm svm ) clocked at [ 3215.066 MHz ]
Videocard nVidia G96 [GeForce 9400 GT] X.Org 1.9.5 [ 1920x1080@60.0hz ]
Network cards D-Link System Inc DGE-560T PCI Express Gigabit
Processes 123 | Uptime 3days | Memory 406.1/8005.9MB | HDD ST3500418AS,ST3500418AS Size 1000GB (40%used) | GLX Renderer Software Rasterizer | GLX Version Yes | Client Shell | Infobash v3.35
usgs - 10.05.2011, 02:50
Post subject:
From some past d-u, I have udev=167-3. Minutes ago I enabled the Debian testing repo and tried to downgrade to 167-2 but cannot. I continue to have the startup problem where I'm forced to change ro to rw. Even though this startup problem is erratic (sometimes I reach X without being forced to change ro to rw), if I don't do that, I never reach X.

What should I do to make the startup go to X permanently? Is it bad that I have udev=167-3?

My kernel: Linux version 2.6.35-7.slh.1-aptosid-686 (Debian 2.6.35-3Cool
My base-files=6.3
CaesarTjalbo - 12.05.2011, 15:46
Post subject:
I don't have a /run directory, i do see udev warnings and fallback behavior when booting.

What is the recommended fix? Manually create /run? Re-install package initscripts? Other?
yossarian - 12.05.2011, 16:03
Post subject:
      CaesarTjalbo wrote:
I don't have a /run directory, i do see udev warnings and fallback behavior when booting.

What is the recommended fix? Manually create /run? Re-install package initscripts? Other?

http://aptosid.com/index.php?name=PNphpBB2&file=viewtopic&t=1193
etorix - 12.05.2011, 20:53
Post subject:
do NOT create a /run; it will fail

the new initscrppts will handle it, when ready
etorix - 15.05.2011, 02:47
Post subject:
UPDATE: new sysvinit Installed: 2.88dsf-13.6, implements /run, and populates it
seems works fine

also see http://lists.debian.org/debian-devel/20 ... 00598.html

and http://wiki.debian.org/ReleaseGoals/RunDirectory
DeepDayze - 15.05.2011, 03:20
Post subject:
      etorix wrote:
UPDATE: new sysvinit Installed: 2.88dsf-13.6, implements /run, and populates it
seems works fine


Ditto...looks like this transition is finally complete
bentbear - 19.05.2011, 00:54
Post subject:
i d-u'd 16may11. kernel 2.6.38 is unbootable while kernel 2.6.37 still boots. Cannot rd -r /run, "directory in use". Any other workarounds?

thanx, bentbear
p.s. running amd e-240 processor on satelite c655d-s5130
devil - 19.05.2011, 07:02
Post subject:
      Quote:

kernel 2.6.38 is unbootable while kernel 2.6.37 still boots.

are you sure, this is /run related?
do any errors or warnings point there?

greetz
devil
Spaceferret - 20.05.2011, 03:14
Post subject:
I'm using Liquorix 2.6.38 and --
root@ethernity:/home/spaceferret# apt-cache policy udev
udev:
Installed: 168-2
Candidate: 168-2
Version table:
*** 168-2 0
500 http://ftp.de.debian.org/debian/ unstable/main i386 Packages
100 /var/lib/dpkg/status

and also /run directory, and everything's fine Smile
slam - 20.05.2011, 08:14
Post subject:
Spaceferret, your kernel is unsupported here, and your info thererfore of no value for our users.
Greetings,
Chris
devil - 20.05.2011, 08:56
Post subject:
why would a unsupported Liquorix Kernel make the installed udev version of no value?
being unfriendly for the sake of it?

greetz
devil
slam - 20.05.2011, 11:41
Post subject:
Udev, kernel and initscripts are working together very closely, and ned to fit - as you definitely know, devil. Unsupported 3rd party kernels (and initscripts, etc) do have no support in our forums for exactly this reason, and - even more - no place in our official "Upgrade Warnings". Feel free to discuss them in "User Scripts & Dragons". This is very much in the interest of our users who expect and rely on officially supported advice.

Making this clear is not (and also not intended to be) unfriendly at all.

Thanks for understanding.

Greetings,
Chris
clubex - 20.05.2011, 12:56
Post subject:
I should have thought that spaceferret's input was of some value. It shows that aptosids udev, initscripts and a Liquorix kernel work together while they don't if you use aptosid kernel. Surely that's of interest to the devs and therefore the users and maybe even a basis to solve the op's problem.

By the way who are the official team? I don't see them listed anywhere Perhaps the list is on the website somewhere but I can't find it (won't be the first time I've missed something Smile ).
Spaceferret - 20.05.2011, 13:00
Post subject:
Just a closing argument,Your Honor:-) It was not my intention to obtain an unsupported kernel should I succeed in having nvidia kernel module load with 2.6.38 slh which I never did despite all my desperate attempts, in my opinion it's better to use an unsupported kernel than not to be able to use my computer.I have 3 kernels installed and 2 of them boot into x with no problems whatsoever ( Liquorix and Frickelplatz ) and slh won't. Unfortunately.
Spaceferret - 20.05.2011, 13:08
Post subject:
All this reminds me the policies of the former communist regimes.It doesn't matter that there's nothing to eat and family of 8 shares a one-bedroom apartment,it doesn't matter that everything is falling apart,as long as you follow ideology you are better off than those damn capitalists,so what if they are doing so much better, they don't live by out ideology and that is why they are cursed from the faith of Earth , I hope I won't be traced down and send to aptosid Gulag for using Damentz kernel (still better than our Canadian winter ) Smile
drb - 20.05.2011, 13:27
Post subject:
@Spaceferret

I managed to install the nvidia blob on the 2.6.38 slh kernels. At some stage nvidia appear to have updated the blob with the offending command
muchan - 20.05.2011, 14:04
Post subject:
OT question but,
      clubex wrote:
By the way who are the official team? I don't see them listed anywhere Perhaps the list is on the website somewhere but I can't find it (won't be the first time I've missed something :-) ).


http://manual.aptosid.com/en/credits-en.htm#cred-team
The list is not updated since devil had left the developers team so he's still listed there.

For @Spaceferret, you are free to use whatever kernel, whatever software on your PC.
But please don't advocate using them on Official forums of aptosid.

{ ...and this is not nvidia+kernel thread. Please stay on topic }
clubex - 20.05.2011, 15:11
Post subject:
muchan: Thank you. I just knew there just had to have been a list somewhere. I think it might be more appropriate to place the list in "Meet the Team" under the top left Menu.

Edit: I might put this forward in the Suggestions forum.
bentbear - 21.05.2011, 03:07
Post subject:
Thanks for the response Devil

there is no message booting 2.6.38. it just freezes and hangs. i don't notice any unusual messages in the 2.6.37 kernel. i'm not connected to the web because no wireless driver and the ethernet cable isn't convenient. incidently, i'm dual booting with win 7. Toshiba also seems to run some services in the background.

i'll try d-u ing again and see if that helps.

thanks again, bentbear
slh - 21.05.2011, 13:21
Post subject:
I'm closing this thread now, as the initial issue about the /run/ introduction has been fixed by now - and while new issues may look similar to the user, they're technically completely different and deserve their own thread.
All times are GMT - 12 Hours
Powered by PNphpBB2 © 2003-2010 The Zafenio Group
Credits