You are not logged in.
Pages: 1
i recently upgraded my kernel 2.6.7 -> 2.6.8 , i did not change the configuration in the kernel, only did make bzImage....
when I boot my new kernel , instead of UDEV started DEVFS
what is happening? :?: :?:
i have installed udev 0.30-5, the last version available
irc.bsd.cl #linux
irc.freenode.org #archlinux-es
Offline
make sure devfs=nomount is in your lilo/grub config
Offline
I asume you forgot to append "devfs=nomount" to the kernel in your preferred bootloader configfile.
If you are going to build 2.6.8.1 as well, wich is really no point if you don't use nfs, you could just remove devfs-support fom your config.
Offline
:oops: :oops: :oops: :oops: :oops: , xD
thx
irc.bsd.cl #linux
irc.freenode.org #archlinux-es
Offline
I use a P4P800E.Deluxe mainboard with 2 older HDs and one S-ATA.
The promise-controller is deactivated as I don't want to use it as raid.
Everything worked fine and I made some kernels, just for trying to do that, up to 2.6.8rc4 without any problems.
When 2.6.8 was released I made a new one and also after 2.6.8.1
From this time on my s-ata drive is not seen, not while booting, not by fdisk -l
The same happened after installing the arch 2.6.8.1 kernel today.
I dont have any idea how to solve that. Maybe that is a special problem of my mainboard. Switching back to 2.6.7 no problem. But times go by....
Maybe someone has a workaround for this or a good idea for a longterm solution...
Isn´t it wonderful?
Offline
i've read on the forum that sata has changed from hdx to sdx try to look at this
http://bugs.archlinux.org/?do=details&id=1265
Offline
I Think that would be shown doing fdisk -l
but in this case it isn´t. No way to find it.
Isn´t it wonderful?
Offline
I have a SATA drive too, and I just upgraded to the latest kernel, however I do not use the scsi kernel. sata works fine with the ide kernel. i also get a kernel panic when trying to boot. so the only thing i have to do to fix this problem is edit my grub file and change hde to sda?
Offline
This maybe if you have exactly the same problem as it was descripted.
Kernel 2.6.8.1 has some more problems.
Here s-ata and one of my usb-storage are not found. not even by hwd .So not the same problem.
I checked out the debian-2.6.8.1, there the s-ata is found but also the usb problem. But some other not easy defineable problem there instead, internet is nearly impossible, slowed down very much...
up to now no way to fix that.
I just changed back to the 2.6.7 and wait for later kernel-releases.
Isn´t it wonderful?
Offline
how did you change back to 2.6.7 ?
Offline
My install starts, just without the s-ata and the usb-stick, so i changed to
/var/cache/pacman/pkg
directory and did as root
pacman -Uf kernel26-2.6.7-1.pkg.tar.gz
That did it.
Later I set the kernelpackage on hold in /etc/pacman.conf But take care on every update it will ask you if you want to update this too.
If you cannot boot, you could use Knoppix or something similar and chroot to your install.
(Maybe the pacman.iso is good for that too, I don´t know.)
Be sure the partition is mounted rw before. ADDED: If you use a separate /boot-partition, you must mount that too (indeed all partitions that are part of the reinstall.)
Let´s say it is hda5 with mountpoint /mnt/hda5
so you do as root:
chroot /mnt/hda5 /bin/bash
mount -t proc /proc proc
cd /var/cache/pacman/pkg
pacman -Uf kernel26-2.6.7-1.pkg.tar.gz
That should work (did not test this one as I did not have to, but similar things I did many times)
Forgot to say, what you mounted to do this you should umount later and leave chroot just by ctrl+D.
Grub stays the same with those kernels. It's called vmlinuz26 still. (btw, not a too good idea, as in case it doesn't work you cannot boot your old kernel. The files in /boot are overwritten. Most times thats comfortable, but in case...)
Lilo I am not sure as I don´t use it, but I think you could edit the /etc/lilo.conf if necessary and run lilo while still being chrooted, but maybe same as in grub, as the data should be same, you don't have to do anything.
Isn´t it wonderful?
Offline
downloaded knoppix 3.4... problem solved! i am now able to boot.
one thing, since i have a boot partition, i also had to mount that. so just in case you wonder why the steps listed above dont work, remember to mount your boot partition.
thanks a lot.
Offline
I checked out the debian-2.6.8.1, there the s-ata is found but also the usb problem. But some other not easy defineable problem there instead, internet is nearly impossible, slowed down very much...
up to now no way to fix that.
Not quite correct.
I've been experiencing this network slowdown issue on several machines, with totally different hardware, and only with the new kernel, so I investigated a bit. This site turned up, which explains the problem rather nicely, and even gives a workaround:
In the mean time, anybody running a current kernel who is having trouble connecting to a needed site can work around the problem with a command like:
echo 0 > /proc/sys/net/ipv4/tcp_default_win_scale
or by adding a line like:
net.ipv4.tcp_default_win_scale = 0
to /etc/sysctl.conf.
An alternative that also works:
echo "0" > /proc/sys/net/ipv4/tcp_window_scaling
to switch this stuff off altogether.
In short, the dynamic enlargement of TCP window sizes through a factor supplied in the initial handshake packet is broken by many routers, as they scrub the reserved field by setting it to zero on their reply, thus establishing a factor of zero for the TCP window size, which is, of course, a bad thing, often causing only the initial packet to get through at all.
If you're using a router at home, it might be at fault. Let someone knowledgable sniff the handshake to see whether it messes with the window size factor field if you care.
EDIT:
Note that putting anything in /etc/sysctl.conf has no effect by default, unless you add sysctl -p to run in your startup scripts, ie. /etc/rc.local!
I added this information to the Wiki, below the FAQs.
Regards,
Dennis
"That's the problem with good advice. Nobody wants to hear it."
-- Dogbert
Offline
Pages: 1