Search results

Ah yes, I had to load the kernel image manually after unload, if not, then everything is loaded back into memory again on boot command. Thank you! :-)

Well, right now the behavior is a bit different: -get into bootloader command prompt (6 from the boot menu) -type "unload" to unload the kernel modules - after this no modules are loaded -type "boot" - kernel and modules are reloaded again and system is going boot My problem is caused by...

I have tried to use some source code hack on my 8.1-RELEASE with xf86-video-intel 2.7.1 driver version so the driver could at least recognize the card. I saw that previous Qxx chips were supported so this might work... so the card was recognized but no output device could be detected and used...

Hello! Anyone got this card working on FreeBSD? I have to use VESA driver, but this card is already working with acceleration on Linux Ubuntu Xorg... I am using driver version 2.7.1_3. Would this work on 2.9?

Well, okay, it's not only the Linux thing is to change everything all the time in a confusing way - when they changed to start counting from 1, it should impact all counting, I guess. Unfortunately, I can also use Windows bootloader to boot the FreeBSD, as the BSD's loader cannot load Linux...

Hello! I think unload is not working as expected anymore - when I go into bootloader prompt (6 at the boot menu) and type "unload", the modules are unloader (what I can also check with "lsmod"), but right after I type "boot" kernel and all modules are reloaded again. So what is the point...

Yeah, besides changing configuration parse, structure and location, and shortcuts in grub2, I just wonder why they decided to change partition numbering but did not change the disk numbering - this is why I dont like Linux anymore - it has no standard at all.