You are not logged in.
i get a kernel panic when i use this kernel. it says something about the filesystem. i have tryed redoing the partitions but i still get a kernel panic with it. The 2.6.12 archck kernel worked great for me. i want my ati drivers back
Offline
Did you use devfs? There is no DevFS in that kernel so the paths in your bootloader are probably wrong...
Maybe I should have added an install script that says as much...
Offline
You need to change the boot line from /dev/disc/... to /dev/hd...
Yes Dibble it would be worth doing that as its a definite change from the 2.6.12 series.
Offline
I'll have to rebuild the whole kernel....pacman suck like that...
Offline
so i switched over to udev and im geting this error when i boot
WARNING: Unable to open an initial console
i tryed the fix in the wiki but it didnt work
http://wiki.archlinux.org/index.php/Ude … al_console
Offline
You need to change the boot line from /dev/disc/... to /dev/hd...
Yes Dibble it would be worth doing that as its a definite change from the 2.6.12 series.
I thought udev supported either one.
I just switched over to udev, and am still using the /dev/disc/blah... format..and it is working just fine.
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
Cotton wrote:You need to change the boot line from /dev/disc/... to /dev/hd...
Yes Dibble it would be worth doing that as its a definite change from the 2.6.12 series.
I thought udev supported either one.
I just switched over to udev, and am still using the /dev/disc/blah... format..and it is working just fine.
In menu.lst? /dev/discs/disc/whatever works fine for me when mounting other partitions, but hangs on boot up if I leave it as discs/disc/crapt. You compiled it out of your kernel and all that funky jazz?
Offline
if you read the original topic you would know.............. but i figered out i needed to boot to a livecd to do it. i was useing a falesafe kernel i had installed.
im on 2.6.13 right now.
thanks guys.
Offline
In menu.lst? /dev/discs/disc/whatever works fine for me when mounting other partitions, but hangs on boot up if I leave it as discs/disc/crapt. You compiled it out of your kernel and all that funky jazz?
Not unless I did it in my sleep...
works fine here..lol..
/me shrugs
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
The /dev/discs/.. scheme works because udev creates a symlink. I was using it when I first installed Arch Linux (with udev) but recently I switched to the /dev/hda scheme in case the symlink is removed from udev.
Offline
so my system complains of unknown block devices if I label my root partition /dev/discs/discwhydoesithavetobesolong/partandsenseless in menu.lst instead of /dev/hdxy when using udev and nobody else's does :? :x
Offline
Maybe I'm wrong but it could be that at boot time, udev haven't started yet so there's not symlinks. It arise with the newest kernel. IIRC, I had this issue so it could the reason I switched to /dev/hda*.
Not sure if it's related, but I use lilo.
Offline
I have the same problem as Penguin - along with about 200 other people
Offline
I thought udev supported either one.
I just switched over to udev, and am still using the /dev/disc/blah... format..and it is working just fine.
It's poor form.... udev doesn't support that - those symlinks were added to the arch defualt rules because so many people still use the devfs naming scheme...
So, *udev* doesn't support it, *Arch* does.
Offline
Hi,
I did pacman -Syu and it upgraded to
kernel26archck 2.6.13.archck5-1 from community and after reboot
glxinfo shows no 3d acceleration.
I rebooted and checked and it does not load fglrx module in startup anymore.
I tried to compile the drivers to the new kernel and it gives me errors.
Is the new kernel compatible with ati-drivers pacakge in community. If not could you please fix this. I switched back to archck1 and 3d acceleration is back.
Thank you in advance.
Powered by Arch Linux
Offline
if youre running testing then its a gcc problem, both kernel and drivers need to be built with same gcc version either rebuild the kernel with gcc4
or rollback gcc complie flgx then upgrade it again
Offline
I am not running testing.
But why the new kernel26archk5 broke compatibility with ati-drivers in community?
Powered by Arch Linux
Offline
Because ati-drivers, and any other package that installs new driver modules, has to be built for a specific kernel. Give dibble a chance, and I'm sure he'll get around to it - or if you're in a hurry, go to the wiki and find out how to do it yourself.
Offline
You know, on the long run breaking ATI drivers on every kernel revision for a period of time isn't the best way to go around.
If one finds time to put out a new kernel revision into [community], couldn't it be ensured that there is also time for a new ati-drivers package which would be supplied simultaneously for user convenience? I've been using arch since it has been conveniently enough hid the low levelish stuff from me. (I'm not a fan of finding a new patch for the ATI drivers every time by hand if I know my distro could do that for me too.)
Sorry for the negative tone of this post. Just couldn't find a better way to say this, perhaps I'm just too tired.
Anyway, the situation has vastly improved and I hope it'll improve further in the near future. Thanks for all the TU for your work so far.
Offline
Hi,
I did pacman -Syu and it upgraded to
kernel26archck 2.6.13.archck5-1 from community and after reboot
glxinfo shows no 3d acceleration.
I rebooted and checked and it does not load fglrx module in startup anymore.
I tried to compile the drivers to the new kernel and it gives me errors.Is the new kernel compatible with ati-drivers pacakge in community. If not could you please fix this. I switched back to archck1 and 3d acceleration is back.
Thank you in advance.
I have not yet rebuilt them against the new archck kernel - the reason being the stock kernel will have the necessary support for the drivers from now and I am waiting for that to move to [current] then i will build the drivers against the stock kernel
Offline
If one finds time to put out a new kernel revision into [community], couldn't it be ensured that there is also time for a new ati-drivers package which would be supplied simultaneously for user convenience?
No-one notices what I do until I don't do it. Yes, I do normally do this but have not done it this time for the reasons described above.
Offline
....... if I know my distro could do that for me too.
In this context, your distro is not doing anything for you - various combinations of devs and TUs are doing the work, unpaid, and in their spare time. If you're in that much of a hurry, follow the advice I gave above and do it yourself - it's really not that hard.
Offline
Rotonen wrote:....... if I know my distro could do that for me too.
In this context, your distro is not doing anything for you - various combinations of devs and TUs are doing the work, unpaid, and in their spare time. If you're in that much of a hurry, follow the advice I gave above and do it yourself - it's really not that hard.
I think giorgio tried that, mate, and it still borked on him
Offline
Well I was already using a vanilla source kernel built by hand at the time of posting. I just don't like the extra work that comes along with this approach.
Thanks for the answer without flame added, though.
Btw, would it be too much of a hassle to manage a different ati-drivers package for each kernel Arch Linux provides..? There are only 5 different kernels provided (out of which 4 are continued). This would allow people to choose more freely and ati-users wouldn't be bound to one kernel you provide. (Well there is always the option of compile & manually install, but..)
Offline
I tried to compile the drivers to the new kernel and it gives me errors.
Apologies giorgio - I missed that line in your original post.
Offline