Hi,
I have a Toshiba satellite 1905-S277, installed Beos pro 5.03 on it. Tried the radeon driver version 5.1.3.1 on it but it doesn’t seem to work (nothing happens).
My love/hate story is a long relation punctuated with many install/deinstall…It used to work before with one radeon driver provided on bebits … 2 years ago, any hints?
Besides that, this model used to be quite fit for Beos as everything used to work except the sound card which is a CS4299-A.
Quentin
Hello Prophet!
This is not so difficult 
Firs step: Check the Device ID of Your videocard. (looks like this: 0x4153)
Second step: You need the sources (You can get this from the BeBits), and the DevTools.
Third step: Search and if You dont found, add your videocard DeviceID to the list.
Fourth step: Compile the driver, and put the driver to the correct place. Dont forget the symlink!
I’m hungarian, and my english skill is not the best, but I hope, You can understand me.
Best Regards,
[miqlas]
Many thanks Miqlas, I fully understand your English, and even if I did not understand (which is not the case), still many thanks.
I will try as soon as possible and give a feedback here
best bets would be to post the syslog (the file in \var\log) and we can see why the driver doesn’t like your laptop.
Well, after installation impossible to log into BeOS, so I got fed up and got rid of the partition and put it into ntfs as an archive place. I know that’s not the way to follow for improving things, my apologies. When I’ll be patient enough, I might reinstall BeOS and try to have a beautiful syslog 
in Xmas…or wait for Haiku…next year bis
–update–
As Xmas is becoming closer, yesterday I was just inspired to reinstall BeOS once more.
I installed the radeon driver from
http://www.haikuware.com/view-details/drivers/video/183-haiku-radeon-driver
However…nothing happens.
When I am looking at my Device, my video card is correctly detected with the ID:4c59 (Mobility Radeon M6 16Mo).
I could not find any log in “/var/log” and the directory did not exist either (maybe because nothing happens…)
Could it be that the script provided missed to create some links?
Quentin
delete all radeon files.
reboot
re-install drivers
Make sure you a symbolic link from /kernel/bin/radeon to /kernel/dev/graphics/radeon
Hello!
The /var directory is hidden. you need write the pathi to the address bar in an Tracker window, and you can see, what contains this directory…
Then You need write this: /var
If You don’t see the path input box, You need enable the navbar in the tracker preferences… (Or You can use the Terminal ( cd /boot/var )
Sorry for my english…
Bye!
miqlas
I still do not manage to make it work.
There is an error message in the syslog but it only says that a symbol could not be loaded (doesn’t specify which one). What can I do to have more information?
To be more precise, the message is :
“instantiate_object failed : failed to find an entry defining the class name (Name not found)”
without further explanations…
Do this:
[quote=Prophet]
Could it be that the script provided missed to create some links?
Quentin[/quote]
You should check manually.
For Radeon, I have two files; radeon & radeon.accelerant because I’m user newer drivers. Assumption, your driver is called “radeon” if it is called radeon.driver then change accordingly.
Now, you can also use /boot/home/config/add-ons/…
but I prefer installing drivers to the system ( /boot/beos/system ) vs the user ( /boot/home/config ) directories:
“radeon” goes into
/boot/beos/system/add-ons/kernel/drivers/bin
then you need to create a symbolic link in the following directory
/boot/beos/system/add-ons/kernel/drivers/dev/graphics
( ie: In terminal change to directory above & then type in; ln -s …/…/bin/radeon ); Use ls -l to verify the link. ( ie; radeon -> …/…/bin/radeon )
This link is important to find & use the driver.
Ok, I’ve followed the procedure with “radeon.driver” and it still does not work…
I have the syslog, but which section is interesting as I cannot post the whole think here.
Search it for “radeon”, “ati” & “vesa” and post those lines here:
On my system I have Geforce2 MX & with “radeon” I get the last two lines:
KERN ‘sh’[32]: agp_man: bus module V0.02: init
KERN ‘sh’[32]: agp_man: found 2 AGP capable device(s)
KERN ‘sh’[32]: Radeon - init_hardware: Version: 5.1.6.0
KERN ‘sh’[32]: Radeon - Radeon_CardDetect: no supported devices found
You can also look through syslog for other video cards.
I’m guessing you’re using Vesa mode.
Look in ( config directory ):
/boot/home/config/settings/kernel/drivers
If you find any file named vesa, remove it.
I hope I am not too stupid…, my syslog does not seem so obvious…
The part concerning “radeon”:
KERN ‘app_server’[24]: LOADER: system add-on /boot/beos/system/add-ons/kernel/drivers/bin/radeon.driver linking against kernel.so!
KERN ‘app_server’[24]: vga_init_driver()
KERN ‘app_server’[24]: boot_frame_buffer = 0
KERN ‘app_server’[24]: vga_init_driver()
KERN ‘app_server’[24]: base_registers (0x00aab508) points to 24 bytes of memory
KERN ‘app_server’[24]: re: base_registers[] - index: 6, vga_count * 6: 6
KERN ‘app_server’[24]: VGA_MAP_MAP_NTH(0) out of 2
KERN ‘app_server’[24]: trying to set 0x002f7acc to 0x30330000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg0 mapping at 0x30330000
KERN ‘app_server’[24]: trying to set 0x002f7ad4 to 0x38330000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg2 mapping at 0x38330000
KERN ‘app_server’[24]: returning the mangled pcii info
KERN ‘app_server’[24]: VGA_MAP_MAP_NTH(1) out of 2
KERN ‘app_server’[24]: trying to set 0x002f7acc to 0x30330000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg0 mapping at 0x30330000
KERN ‘app_server’[24]: trying to set 0x002f7ad4 to 0x38330000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg2 mapping at 0x38330000
KERN ‘app_server’[24]: returning the mangled pcii info
KERN ‘app_server’[24]: VGA_MAP_MAP_NTH(0) out of 2
KERN ‘app_server’[24]: trying to set 0x002f7acc to 0x30336000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg0 mapping at 0x30336000
KERN ‘app_server’[24]: trying to set 0x002f7ad4 to 0x38336000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg2 mapping at 0x38336000
KERN ‘app_server’[24]: returning the mangled pcii info
KERN ‘app_server’[24]: VGA_MAP_MAP_NTH(1) out of 2
KERN ‘app_server’[24]: trying to set 0x002f7acc to 0x30336000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg0 mapping at 0x30336000
KERN ‘app_server’[24]: trying to set 0x002f7ad4 to 0x38336000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg2 mapping at 0x38336000
KERN ‘app_server’[24]: returning the mangled pcii info
KERN ‘app_server’[24]: VGA_MAP_MAP_NTH(0) out of 2
KERN ‘app_server’[24]: trying to set 0x002f7acc to 0x3033c000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg0 mapping at 0x3033c000
KERN ‘app_server’[24]: trying to set 0x002f7ad4 to 0x3833c000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg2 mapping at 0x3833c000
KERN ‘app_server’[24]: returning the mangled pcii info
KERN ‘app_server’[24]: VGA_MAP_MAP_NTH(1) out of 2
KERN ‘app_server’[24]: trying to set 0x002f7acc to 0x3033c000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg0 mapping at 0x3033c000
KERN ‘app_server’[24]: trying to set 0x002f7ad4 to 0x3833c000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg2 mapping at 0x3833c000
KERN ‘app_server’[24]: returning the mangled pcii info
KERN ‘app_server’[24]: VGA_MAP_MAP_NTH(0) out of 2
KERN ‘app_server’[24]: trying to set 0x002f7acc to 0x30342000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg0 mapping at 0x30342000
KERN ‘app_server’[24]: trying to set 0x002f7ad4 to 0x38342000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg2 mapping at 0x38342000
KERN ‘app_server’[24]: returning the mangled pcii info
KERN ‘app_server’[24]: VGA_MAP_MAP_NTH(1) out of 2
KERN ‘app_server’[24]: trying to set 0x002f7acc to 0x30342000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg0 mapping at 0x30342000
KERN ‘app_server’[24]: trying to set 0x002f7ad4 to 0x38342000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg2 mapping at 0x38342000
KERN ‘app_server’[24]: returning the mangled pcii info
KERN ‘app_server’[24]: VGA_MAP_MAP_NTH(1) out of 2
KERN ‘app_server’[24]: trying to set 0x002f7acc to 0x30348000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg0 mapping at 0x30348000
KERN ‘app_server’[24]: trying to set 0x002f7ad4 to 0x38348000 + 0x00000000
KERN ‘app_server’[24]: create_pci_area: pci_bus1_dev0_func0_reg2 mapping at 0x38348000
KERN ‘app_server’[24]: returning the mangled pcii info
Thers is nothing with “ati” and “vesa”, however when I look at
"4c59" (the ID of the VGA card discovered under BeOS in devices manager with Ati technologies as vendor):
KERN ‘BOOT’: bus 1 device 0 function 0: vendor 1002 device 4c59 revision 00
KERN ‘BOOT’: class_base = 3 class_function = 00 class_api = 00
KERN ‘BOOT’: line_size=08 latency_timer=00 header_type = 00 BIST=00
KERN ‘BOOT’: rom_base=00000000 pci 00000000 size=00020000
KERN ‘BOOT’: cardbus_CIS 00000000 subsystem id ff00 subsystemn vendor id 1179
KERN ‘BOOT’: interrupt_line=05 interrupt_pin=01 min_grant=08 max_latency=00
KERN ‘BOOT’: base reg 0: host addr f0000000 pci f0000000 size 08000000, flags 08
KERN ‘BOOT’: base reg 1: host addr 00003000 pci 00003000 size 00000100, flags 01
KERN ‘BOOT’: base reg 2: host addr e8000000 pci e8000000 size 00010000, flags 00
KERN ‘BOOT’: base reg 3: host addr 00000000 pci 00000000 size 00000000, flags 00
KERN ‘BOOT’: base reg 4: host addr 00000000 pci 00000000 size 00000000, flags 00
KERN ‘BOOT’: base reg 5: host addr 00000000 pci 00000000 size 00000000, flags 00
Hope the listing is useful and not too long
Quentin
I don’t believe the radeon.driver you got was properly compiled for BeOS. Search your system & you’ll see that you don’t have kernel.so library ( used to build Haiku kernel? ). And the driver should not be linking to it anyways. What you have:
KERN ‘app_server’[24]: LOADER: system add-on /boot/beos/system/add-ons/kernel/drivers/bin/radeon.driver linking against kernel.so!
What I get in my syslog & you should get too:
KERN ‘sh’[32]: Radeon - init_hardware: Version: 5.1.6.0
KERN ‘sh’[32]: Radeon - Radeon_CardDetect: no supported devices found
Actually the line above should detect your Radeon card.
I have Haiku radeon driver compiled for Dano ( BeOS 5.1 ). And may have a compiled version for R5 netserver or bone. I believe the Dano one may also work for you.
Enable your Email in Profile & I can send them to you to try ( best way ) . Or post your email on here like: name[remove-this]@address.com to avoid spam email.
PS I had a Radeon 8500 in my 2nd system & it worked great in BeOS but I moved it over to use on my main system. Also, my onboard CS4236 has sound - hurray and I think the driver supports your sound card too.
I looked & the Haiku driver supports your video card. You just need a version compiled for BeOS & to make sure it gets installed right. Then you’ll finally have 2D accelerated video.
Thank you all for your help. It works now with the driver Euan has posted.
Tonestone, I will be interested in trying your audio driver, though I have doubts it will work.
My email: song(dot)qk(at)gmail(dot)com
Quick update for those reading this thread.
I sent the audio driver to Prophet and now his CS4299A works in BeOS.
He is very happy to have accelerated 2D video & sound in BeOS. And his network card works too. So, his system is completely functional and working with BeOS.